Registry Shop Order (sys-viewer-vshpordr)


This registry entry is used to set defaults for the Shop Order and related functions such as Requisitioning (which generates automatic shop orders).

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Important Fields:

Id:  sys-viewer-vshpordr

Intercompany Note:

If Intercompany is enabled, the system will now check for company security level registry settings when running this function; an error will be displayed if these registries (sys-viewer-vshpordr-securityid) are not found.

Branch Users:

This release supports Requisitioning at the Branch level: the  ‘From’ and ‘Staging’ location may be specified for each Branch. Branch settings now override the non-branch standard settings (branch derived from WO/Job):

Id: sys-viewer-vshpordr-branchid

Note On Work Orders:
In Version 8.0 and above, the Work Order Required Resource tab’s Quantity On-Hand and Available calculations use branch-specific Material Requisitioning registry entries (sys-viewer-vshpordr-branchid) when available.

Prevent Use of Completed Job Cost Code or Billing Items

Setting Key: CostCodeDateCompletedValidation Setting Value: error

Setting Key: BillingItemDateCompletedValidation Setting Value: error

Currently, the system warns you if you enter a billing item or job cost code whose Date Completed exceeds the effective transaction date. These options change the warning to an error.

It's also important to note that the validation logic implemented by this registry entry only applies when either a Cost Code Id or a Billing Item Id field's value is explicitly changed by the data entry user.  The Cost Code and Billing Item registry entries are independent from one another.  Note that these options may be specified in Registry Entry Global Settings registry entry for a more far-reaching implementation.

Material Requisitioning Defaults

Registry Options for Stocked Items

Setting Key: MaterialRequisitionToLocation Setting Key: staginglocationid

Setting Key: MaterialRequisitionFromLocation Setting Value: stockinglocationid

These registry options specify To and From locations for Shop Transfer Orders that are automatically generated by the Work Order Materials Wizard for Stocked materials.

Note that the option mode keystone should NOT be implemented if the above registry options are used.

Example: no branches or security

Setting Key: MaterialRequisitionToLocation Setting Value: Stage

Setting Key: MaterialRequisitionFromLocation Setting Value: Main

Registry Option for NonStocked Items

This release supports a new registry option for a default location for non-stocked inventory items in the sys-viewer-vshpordr / sys-viewer-vshpordr-branchid

Setting Key: MaterialRequisitionFromLocationNonStocked

Setting Value: LocationIdforNonStocked

Placeholder Item for Requisitioning

Setting Key: MaterialRequisitionItemId Setting Value: ItemId

This registry entry specifies a ‘placeholder’ inventory item record that is used by the system when shop transfers orders are auto-generated. Note that ItemId should be replaced by an actual Inventory Item Id that has been created for this purpose only.

Important Note: when creating this item for Required Parts, the user must select an Inventory Group which has the “GL WIP Account” Set up as an inventory account  - not a cost of sales account. With the Requisitioning functionality, when the items are transferred and then IMPORTED back into the workorder, the system creates a GL Journal Entry. If this was to a cost of sales account during the Import processes (for WO Inventory items) it would result in double costing.

Option to Require at Least One ‘overhead’ item

In order to include overhead costs in the production of inventory items, 'overhead cost' inventory items may be added to shop orders. This registry entry prevents the closing of a shop order unless at least one such item is included on the shop order.

Setting Key: requiredInventoryGroups Setting Value: groupList

where groupList is the Id of an Inventory Group or a list of Inventory Group Ids separated by commas.

Setting Key: requiredInventoryGroups Setting Value: chovrhd, inmanovrhd, azovrhd

Note that only one of the required groups (not all of the groups) need be present in order to close the Shop Order. If Sampro does not find the requiredInventoryGroups requirement in the Registry or if the groupList is blank, the Shop Order automatically passes this test. Otherwise, the user will be warned to add an overhead item.

Suppress Posting to the Shop Orders Parent Record

The following registry setting disables posting the shop order's parent record during the closing process.

Setting Key: PostParentForClosedOrders Setting Value: true

This would only be implemented if the customer is using the Shop Order viewer as the inventory transfer mechanism like Material Requisitioning.  As with requisitioning, the Inventory Item in the Shop Order parent record is not a 'real' assembly.  That means they didn't want the act of closing the shop order to add to the on-hand quantity of the parent item.

Registry to Use WO RR Location (Deprecated)

This registry option is not recommended. When shop orders are generated for Materials Requisitioning, the user-specified location (in the Work Order Required Resource Tab) will only override the default location ‘From’ registry settings for the From location if this registry is in effect:

 Setting Key: UseWORequiredResourceLocation Setting Value: true

Set Mode to Auto Create Job and Shop Order Id (Deprecated)

Setting Key: mode Setting Value: Keystone

If this entry is made, the following features will be implemented for Shop Order processing:

1. The Shop Order Id will be automatically generated by the system when it is saved.

2. The system will automatically create a Job record and a Cost Code record for the shop order you are creating. These records will be based on the model found in the existing Job record with Id=new (note that new must be all lowercase) and its associated Cost Code, Mat. A Cost Category, Mat, should also exist: this will be the default Cost Category for history entries for the new item.

3. The Job Id will be set to the Shop Order Id - unless the jobprefix option discussed below is implemented. In this case, Shop Order Id will be appended to the prefix.

Specify Prefix for Shop Order Jobs

Setting Key: jobprefix Setting Value: soprefix

This option enables you to prepend a prefix to the autogenerated Job Id's (when the mode is set to Keystone) created when a new Shop Order is created. This option is recommended since it enables you to distinguish those jobs created for Shop Orders, and to avoid possible collisions with existing Job Id's. The job number generated will consist of the prefix plus the shop order id.


If jobprefix is set to so, the jobs generated by shop order processing will have the following Id's: