Required Item Codes

When configuring SAP Business One for use with Eralis Job, the following item codes are required: 

1. Item codes that need to be created and defined. 

• Recovery item code 

• Rounding item code 

2. Item codes that are automatically created. These codes are used with the consolidated invoicing functions that were introduced with the release of Eralis Job 8.80.300. 

• Con_S (Staff timesheet lines) 

• Con_R (Resource lines) 

• Con_M (Material and expense lines) 

• Con_H (Rental billing lines) 

The codes that are automatically created relate to each of the four main transactions types that are available within Eralis Job and have the prefix Con_*. 

All the item codes, both automatically and manually created, are non-inventory item codes. 

It is important to understand the how the various item codes are used. The Recovery item code is used in the under/over recovery billing process, where there is a difference between the system calculated value and the user defined value. Eralis Job will add a new line to the job to balance the values using the recovery item code on the line. 

The Rounding item code is used in the pro-rata billing process along with the make-to-stock process where there are values that cannot be allocated to specific job lines. A new line is added to the job using the rounding item code for the value that cannot be allocated to the existing job line.  

The item codes to use for these two categories are defined in the Eralis Job System Initialization screen.  

The item codes that are created automatically are the item codes that are required for the consolidated invoicing process in Eralis Job. With the consolidated invoice process, the system does not post lines to the A/R invoice for each job line; rather it posts a single line for each transaction category per user-selected grouping option. This reduces the number of lines on the A/R invoice and provides more flexibility on how the invoice is presented.  

For each line that is posted to the A/R invoice, the system will automatically use one of the Con_* codes depending on the transaction category being used.