Open nmfujimoto opened 3 years ago
Need to make sure the order API call includes all 3 types of requests:
The Shipping Document trigger the orders to be ready for BizMobl by setting Proflag12 = "S".
The Delivery (Shipping Document) request we receive from FarEye will split the orders for us. Meridian does NOT need to split the orders. We should be able to use the Shipping Document request to recreate the cargo records and set ProFlag12 to "S" for BizMobl download.
Electrolux will be sending examples of the requests to us before calling the API with the same examples.
@prashantaggarwal1999 Electrolux will not provide a Shipping Document (tracking number) until the Delivery request. We need to devise a solution where we can populate the Contract # field with a unique value that we can overwrite once we receive the valid number from Electrolux.
Possible approach: For Order/ASN requests we can populate using "O-" + Order Number (74.....) value so it would look like O-74123456789. The "O-" would designate to us that this is a placeholder value since the Contract # is required in M4PL and must be unique.
When a Delivery request is received the tracking number (Contract # in M4PL) will be provided. At this time the "O-74123456789" value currently in the Contract # will be overwritten.
Need to implement the enhancement to split an existing order into separate orders if the line item delivery dates are different. The Shipping Document (78... number) is the Tracking Number relating the two orders together. Once the orders are split each will need to be statused individually.