Clients First USA
Clients First knows their software, but they are also astute business people, and they really understand manufacturing and distribution in particular.
Jimmy Witcher, COO, Merrick
Read More
About UsService OfferingsProduct OfferingsIndustries ServedDownloadsBlog
 

Subscribe to our mailing list

* indicates required
    Interested in    
Hot Topics
 

Latest Articles

JobOps for MAS90, MAS200 Sage ERP 100 release 4.4 R4 Coming

Wednesday, April 25th, 2012

Below just came in from JobOps.  JobOps is our integrated solution for manufacturing in a Sage MAS 90, Sage MAS 200 and Sage ERP 100 environment focusing heavily on Make to Order manufacturing.

JobOps 4.4 R4 release information – early to mid-May, 2012

We have re-written the Crystal File Generation utility to the new Sage Business Object format.  The old Crystal File Generation utility will still be available for a few releases, giving you time to upgrade your reports.  This will probably be removed in version 5.0.  Three big benefits of the Crystal File generation re-write are:

1. Allows the inclusion of Work Ticket UDF’s

2. Report specific Crystal File Generation

3. Total of 2 files rather than 13

There is a more detailed overview within the main page of the Partner Portal.

Work Ticket Printing has also been re-written into the business object and therefore, any custom Work Ticket Forms created in prior versions must be rewritten before going live with JobOps 4.4 R4.  The following Warning has been included as part of the install for 4.4 R4 as an additional reminder:

clip_image001

These changes are important as Job Ops moves forward into the Business Framework and helps in providing for a more customizable solution.

Currently there are still no release dates for a version that is compatible with Sage 100 Premium 4.5 (The new name for MAS 200 SQL).

Tuesday, April 24th, 2012

Boyum Pack for SAP Business One

Boyum has created a short new video listing the 10 key reasons to purchase the Boyum Suite.  Boyum’s Suite adds extensive functional and usability enhancements to standard Business One putting it on par or above other products in terms of the ability for consultants and end users to customize the solution without source code modifications.

Doing it this way is less expensive, more reliable and more importantly and allows you to upgrade SAP Business One more frequently and far less cost since you don’t have to pay for source code customizations to be re-developed for each new version.

Here is the Video.

 

Ten Reasons to Use Boyum’s B1UP Suite

Tuesday, April 24th, 2012

Boyum Pack for SAP Business One

Boyum has created a short new video listing the 10 key reasons to purchase the Boyum Suite.  Boyum’s Suite adds extensive functional and usability enhancements to standard Business One putting it on par or above other products in terms of the ability for consultants and end users to customize the solution without source code modifications.

Doing it this way is less expensive, more reliable and more importantly and allows you to upgrade SAP Business One more frequently and far less cost since you don’t have to pay for source code customizations to be re-developed for each new version.

Here is the Video.

 

Salesperson Security in Epicor 9

Monday, April 23rd, 2012

Manage Salespeople in Epicor 9.05

How to keep Salespeople from only working with the information they need?

In Epicor 9 to Epicor 9.05 in addition to the standard Epicor security there is special security setup for Salespeople. Buyers and Salesperson setup is a fairly straight forward process. That is once you figure out the Salespersons are actually entered in Work Force Maintenance. I am not going into detail on all fields in Work Force Maintenance and if I skip a particular field, field help will explain the field.

If you don’t take the time to properly configure Salesperson Security, it is quite easy for your customer list to walk out the door when your salespeople do.

Work Force Maintenance:

Before entering Sales People into Epicor, a corporate decision needs to be made on how to use territories. How to use territories is a company by company decision. For example, some companies the territory is defined geographically, others by Product, others by Customer type. Once this decision is made, the next decision is which sales people are limited to a territory or can view all territories. Next is to decide which sale people can see the entire Company Sales Pipeline. This is normally restricted to Sales Management.  The Commissions fields are the next important fields to be decided upon.

 

image

The other security feature that is special for a salesperson is defined on the Authorized User tab in Work Force Maintenance. This defines the other salespeople authorized to work on this salesperson quotes and SO’s in case of vacation or emergency. Even thought the current salesperson was defined on the Detail tab, the salesperson must be added as an authorized user for their own SO’s. The default buyer flag is set on this row. In the above example, after defining Scott in the detail tab, add Scott as the default authorized user. Other Authorized users can be another buyer but is normally the sales Person’s immediate supervisor.

For Scott Popiel I have set up the authorized users like below (This is also visible in the tree on the first screen shot above):

image

SAP Business One Common Table Names and Queries

Sunday, April 22nd, 2012

A List of Common Table Names and Queries:

All Marketing Documents (PO, Sales Order, AP Invoice, AR Invoice) have different file/table names, but their field names are the same. You can quickly write a query over the Purchase Order file and then just copy it and change the table names and the query will still work.

/* Business Partners */
SELECT * FROM OCRD

/* Chart of Accounts */
SELECT * FROM OACT

/* Item Master */
SELECT * FROM OITM

/* Terms Codes */
SELECT * FROM OCTG

/* Business Partners and their assigned payment terms */
SELECT OCTG.PymntGroup, OCRD.* FROM OCRD
LEFT OUTER JOIN OCTG ON OCRD.GroupNum = OCTG.GroupNum

/* Employee Master (HR) */
SELECT * FROM OHEM

/* Sales Quotations and their Line Items */
SELECT * FROM OQUT
INNER JOIN QUT1 ON OQUT.DocEntry = QUT1.DocEntry

/* Sales Orders and the Line Items */
SELECT * FROM ORDR
INNER JOIN RDR1 ON ORDR.DocEntry = RDR1.DocEntry

/* Credit Memos and the Line Items */
SELECT * FROM ORIN
INNER JOIN RIN1 ON ORIN.DocEntry = RIN1.DocEntry

/* Incomming Payments and the line level Information */
/* I have not validated this link */
SELECT * FROM ORCT
INNER JOIN RCT1 ON ORCT.DocNum = RCT1.DocNum

Thanks to Ed Monk of SBOnotes.com