The Job Number Format mask identifies the job numbering structure in the Sage Timberline® Office Job Cost Accounting database. WMS will not be able to receive job information from Job Cost if the mask does not match the job numbering structure exactly. These settings should be configured for each division's database. See the following section "Job Section Mapping Scenarios" for information to determine what mapping makes sense.
From the Integration menu select Timberline Accounting > Accounting DB Settings.
Or, select the Accounting DB Settings 
icon from the toolbar.
Verify the database currently selected in the Accounting Databases field list is the correct database for which this setting will be defined. If necessary, click on a different database.
Click the Timberline Accounting Configuration tab.
Enter the mask in the Job Number Format field
Enter the # symbol to represent each character.
Enter the appropriate number of characters in each section.
Separate the sections of the job number with the- symbol.
For example, if the job numbers have 8 characters with 2 in the first section, 2 in the second section, and 4 in the last section, the mask would be ##-##-####.
Click the Save 
button at the top of the screen to save any changes.
|
Note |
|
If the auto-numbering option will be used for numbering purchase orders, the job number, excluding the separating characters such as- is limited to 9 characters. |
In the Timberline Accounting Configuration tab, verify the correct job number mask by clicking the Verify icon next to the Job Number Format field.
The numbers appearing in the Section fields represent the number of # characters entered in the Job Number Format field. Click Verify in the lower right side.
If the mask is correct the Information dialog appears, "Current sections match Accounting data."
If the mask is not correct, the error message appears, "Current sections do not match Accounting data." In this case, the user needs to change the mask until it matches the Sage Timberline® Office Job Cost Accounting job number structure exactly.
Adjust the mask as necessary.
If using job section mapping, continue to the following section. Otherwise, click OK, then Save.
See the topic JC Cost Code Format for instructions on assigning the Job Cost cost code format.
EachMap To field can be assigned a code from the available list. This code is used to interpret the value in the assigned section of the job number. For example, if section one of the job number is mapped to the division code, the value in section one of the job number must contain a valid division code. Once a code is assigned to a Map To field, that code is no longer available in the remaining Map To lists.
|
Note |
|
Job section mapping only applies when importing new jobs into WMS from Sage Timberline Office Accounting. It can be used as a filtering tool for keeping out unwanted jobs. Job section mapping will not affect any current jobs that already exist within WMS. |
Several common mapping scenarios are outlined below.
In this scenario, map any Map To field (corresponding to section 1, 2, or 3) to the division code (it does not have to be mapped to the first section). If any section is assigned to the division code, the import process looks for the value in that specific position within the job number. The process must find a match on the division code within the job to import to the division code of the division currently selected in WMS. If no match is found, the job does not import into WMS.
In this scenario, map any two of the Map To fields to the division code and the area number. The import process searches for the division code match, then the area number. The division code must match the division currently selected in WMS, and the area number must match an area within that division. If a match is not found for both the division code and area number, the job will not import into WMS. If a match is found for both, the area ID on the job record is updated, assigning the job to the area matching the area number in the job number section.
In this scenario, map any two of the Map To fields to the division code and the sales code. The import process searches for the division code match, then the sales code. The division code must match the division currently selected in WMS, and the sales code must match an area within that division. If a match is not found for both the division code and sales code, the job will not import into WMS. If a match is found for both, the area ID on the job record is updated, assigning the job to the area matching the sales code in the job number section.
In this scenario, map any one of the Map To sections (corresponding to section 1, 2, or 3) to the area number (it does not have to be mapped to the first section). The import process searches for an area with a matching area number within the current division. If a match is found, the job is imported and the area ID on the job record is updated, assigning the job to the area matching the area number in the job number section.
|
Note |
|
If this mapping scenario is employed, unique area numbers must exist across all divisions. |
In this scenario, map any one of the Map To sections (corresponding to section 1, 2, or 3) to the sales code (it does not have to be mapped to the first section). The import process searches for an area with a matching sales code within the current division. If a match is found, the job is imported and the area ID on the job record is updated, assigning the job to the area matching the sales code in the job number section.
|
Note |
|
If this mapping scenario is employed, unique sales codes must exist across all areas in the division. |
From the Timberline Accounting Configuration tab, click on the Verify icon next to the Job Number Format field if not already open.
Establish the Map To field values as desired. The options are Division Code, Area Number, Sales Code, Phase and Lot Number. Populate only those fields needed, in any order.
Click OK when complete.
Click the Save button in the toolbar.
Job Number Format Mapping: Phase Release
Path to Job Cost Accounting Database