266487
DHL MTS
Check action code to delete BKG or ASN
FUNCTIONAL SPECIFICATION - 10.4.7
- 1.0
Reference: FS 266487 AA-7STHUF
Client Requirement
Currently ESI rejects if BKG or ASN file received with Delivery Priority "04" or Quantity "0.00". We have asked ESI to change the validation they does and should accept the file if it has priority 04 or quantity 0.00. We would like to implement the below validations in MTS• When MTS receives a Quantity 0.00 with Action Code = 3 (Delete request “X”) then MTS should not check the Quantity just delete BKG or ASN. Aramco will send the quantity zero due to their system internal process and this will be in a very minimal quantity as compare Insert and Update of BKG or ASN.In BKG Aramco will send an Order Quantity 0.00 with action code “X”Or in ASN Aramco will send an ASN Quantity 0.00 or DU Quantity 0.00 with action code “X”.• When MTS receives a Delivery Priority “04” in BKG or ASN message with action code = 2 (Update request “U”) then MTS should delete the BKG or ASN. Below is the email which we have sent to ESI; "Saudi Aramco gets the below two errors when validation failed for the BKG and ASN messages ; - Data Error: The value '0.000' of element 'Quantity' is not valid. ; - Data Error: The value '04' of element 'DeliveryPriority' is not valid. ; We want ESI to remove the validation which causes above errors that mean ESI should accept if quantity is "0.0000" and should accept if priority is "04" and do the other steps same as ESI does for other Booking and ASN (sends acknowledgment back to SAP and sends the .csv file to MTS) ; Below are the flow names we want require the change ; - SAP XML to MTS CSV - Booking flow for Saudi Aramco ; - SAP XML to MTS CSV - ASN flow for Saudi Aramco ‘
Solution
All validation changes will be made in INT_MSG package on the Saudi Aramco Database.
Currently, when processing ASN and BKG records, if the quantity is 0, the record will be rejected. The validation change will allow records with quantity 0 to be successfully processed if the action is DELETE.
Currently the system does not receive any records with DEL_PRIORITY ‘04’., these records will now be received and in cases where the DEL_PRIORITY is 04 and the action is UPDATE, the record will be deleted.
In the following cases, deletions should not be processed, the code will be checked to confirm this is the case:
- If a BKG or ASN has an order which is not UNSCHEDULED
- If an ASN has already been received and Aramco then send a delete of BKG, the delete will be ignored.
Scope
This change will be applied to system version 10.4.7 on SARTST and once approved SARPRD. .
Set-up
Pre-requisites
If not applicable enter None
Menu Structure
Unchanged
Data
The data we receive from ESI will be changing to include DELIVERY PRIORITY 04 and QUANTITY 0.00.
Currently records containing these values would be rejected, changes will be implemented to allow the successful processing of records with this data.
Currently code within the READ_ASN_BOOKING_DETAIL procedure of the INT_MSG package checks the value of the quantity field and rejects the record out right if the quantity is 0.00
In the PR_READ_ASN_BOOKING_TABLE the records which have been successfully received are processed. Currently records are deleted if V_BOOKING.ACTION = ‘X’. This condition will be amended to
If V_BOOKING.ACTION = X OR (V_BOOKING.ACTION = ‘U’ AND V_BOOKING.DEL_PRIORITY = ‘04’
Functional Description
The changes will result in more records being received and processed successfully.
Existing delete functionality will be investigated to ensure that a deletion is cancelled in the following circumstances
An order exists on the BKG or ASN with a status of UNSCHEDULED.
If an ASN has been received for a BKG and then a deletion for the BKG is received.
References
| EST-266487 AA-7STHUF Check action code to delete BKG or ASN v1.0.doc | |||
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
