Last updated on FEBRUARY 17, 2017
Applies to:Oracle Supply Chain Globalization - Version 22.214.171.124 and later
Information in this document applies to any platform.
EXECUTABLE:INVCMVT - Movement Statistics Processor
When the Movement Statistics (MS) Processor runs, it populates mtl_movement_statistics.delivery_terms for arrivals and dispatches based upon the underlying transaction details. For dispatches, it retrieves the AR FOB lookup code value from wsh_delivery_details.fob_code. This AR quickcode has seeded values with meanings such 'Loading Dock', 'Customer Site', etc.
However, when the Movement Statistics Exception Report is run using the seeded validation rule, an exception is generated for each dispatch. This is because the exception report is validating the Movement Statistics 'Delivery Terms' field (populated by the MS Processor with FOB codes) against the 'MVT_DELIVERY_TERMS' AOL Lookup type. This AOL lookup code has seeded values as expected (e.g. EXW, DDP, CIR, etc).
1 .Why is the MS Processor populating the delivery terms field on mtl_movement_statistics based on seeded FOB codes when the MS Exception Report is validating that data against the
'MVT_DELIVERY_TERMS' AOL Lookup type with different seeded values ?
2. Shouldn't the MS Processor be populating mtl_movement_statistics.delivery_terms with the 3 character codes (e.g. EXW, DDP, CPT) that correspond to the seeded AR Freight Terms (e.g. Ex Works, delivered duty paid, carriage paid to) ?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms