Working with Service Order Transactions when Integrated with Distribution SX.e
Material transactions
When adding a material transaction, the item cost, price, and discount percentage are all populated from Distribution SX.e using APIs.
A service order material transaction is prevented from posting when the ship quantity of the associated Distribution SX.e order is less than the transaction quantity to be posted. These conditions must be met to prevent the transaction from posting:
- The Distribution SX.e integration is enabled and Enforce Allocations is selected on the Integration Parameters form.
- The quantity on the material transaction is greater than the Ship Qty of the Distribution SX.e order line.
- The transaction type of the material transaction is not Return.
TWL
You can use Total Warehouse Logistics (TWL) to pick, pack, and ship sales orders for material transactions. In Distribution SX.e, sales orders are assigned the Tag and Hold disposition to prevent TWL processing until after the service order is invoiced. When an order is for a TWL warehouse, service order transactions cannot be added, changed, or deleted when the material transaction is already set to Picked.
When working with a TWL warehouse, the read-only WLType field on the Warehouses form shows TWL.
Supersede products
Supersede products are a Distribution SX.e feature that are supported on the Service Order Transactions form and the mobile and back office versions of the SRO Material Entry form as supersede items. On those forms, if you select an item that is superseded by another item, then the item is automatically updated to the supersede item.
Use the Supersede Item field on the Items form to review which items are superseded.
Read only fields
These read-only fields are displayed on the tabs of the Service Order Transactions form:
- SX.e Product Line: This field is displayed on the Planned Material tab and shows the Distribution SX.e product line displayed for the item.
- Create SX.e Purchase Order: This field is displayed on the Planned Material tab. This check box is selected or cleared based on the setting of the Create SX.e Purchase Order field on the SX.e Catalog/Non-Stock Query form. When selected, a PO is created by default in Distribution SX.e when a planned material transaction is created.
- External Sales Order Line: This field is displayed on the Planned Material, Planned Miscellaneous, and Planned Labor tabs. When a transaction is created for an assembly SRO that is linked to a Distribution SX.e sales order through APICreateSROFromExternalOrder, this field is populated with the associated Distribution SX.e sales order line number, when applicable.
Many other fields on the Planned Material tab are set to read-only after a pick list is printed in Distribution SX.e for a Service Management planned material transaction. This is done to prevent the printed pick list from being edited.
To prevent potential errors when working with service order transactions, these fields are set to read-only on the Service Order Transactions form:
- The Warehouse field on the Labor tab and Miscellaneous tab
- When Impact Inventory is set on the Service Parameters form, the cost fields on the Material tab are set to read-only
Rush
The Rush field is displayed on the Planned Material tab on the Service Order Transactions form. This check box is selected or cleared based on the setting of the Rush field on the SX.e Catalog/Non-Stock Query form. When selected, Distribution SX.e rushes the PO.
On the display grid of a planned material transaction for a stocked item that is not cross-referenced to an ISM purchase order, you can select or clear the Rush option if the option is cleared.
After the planned material transaction is cross-referenced, for both stocked and non-stocked items, the Rush option on the grid cell is set to read-only if the or the options are selected.
Transfer Orders
When a transfer order is received in Distribution SX.e, the Sync.ReceiveDelivery BOD is sent to Service Management. When the BOD is received in Service Management, the associated planned SRO material transaction is posted.
Core Return Serial Number
During SRO material transaction entry, If the Auto Allocate Core Returns integration parameter is enabled and a dirty core product is returned, that item is automatically allocated to the related remanufactured core product on the same SRO line and operation. A message is displayed if a related material transaction is not found.
In Service Management, the Sync.ServiceOrder BOD generation includes reference information about the allocation, identifying the SRO number and Row ID of the allocated transaction. The Sync.ServiceOrder BOD consumption captures the allocation reference information, which includes the order number, line, and serial numbers related to the returned dirty core items.
In Distribution SX.e, the downstream shipping, which is performed during Process.Invoice BOD consumption, and the invoicing, which is performed by OEEPI, are processed without additional manual intervention.
In the unlikely event that a dirty core is associated with multiple remanufactured items, the allocation routine automatically selects the first material transaction that it encounters. Optionally, to change the selected material transaction, you can edit the Core Trans Number.