OST ASN V2 for BOOKING (or CONSOL)
PLEASE NOTE: If party name that has failed translation shows 'OBL', email Happy @OST (happyhuang.szx@orientstargroup.com) and request they update and resend their EDI message due to invalid party name. Reference the OST ShipmentID located in the /BL header. Assign yourself to ticket and mark the ticket as Closed and tag as Resolved/OST ASN.
Any Questions, see Debbie Strojan
OST ASN V2 for BOOKING (Steps also apply for CONSOL)
ERROR: Chain.io Flow: logical_fail – OST ASN V2 for BOOKING (or CONSOL)
CAUSE: Party Organization Code is not present within the OST ASN V2 for Booking flow (or Consol flow)
HANDLED BY: EDI Support Team
SUPPORT PROCESS Summary: Locate the correct Organization Code for the Party Name listed in the Fresh Service Ticket. Search by variations on Name and Address to locate applicable Org Code. If not found, Add a New Organization Code for the party in question. Update chain.io portal flow with Party Name/Org Code pair and resubmit the file(s) for re-processing in the flow.
DETAILED STEPS:

- Locate the Organization Code for the Party in CargoWise Production

a. Search by name variations to locate org code.

b. If none found, click link in ticket to view file and locate party address; search by address for org code



- Once the organization code has been found, click on the ‘Settings’ link on the Error page. Add the Party Name from the support ticket and the related Organization Code to the OST ASN V2 for Booking Flow under ‘Source File Type’.


- Click ADD, enter details, then choose SAVE and then DEPLOY changes. Wait for deployment of new map to be completed before moving to the next step.

- Refresh the Error page and then click ‘Resubmit’ on that same page (the page will reflect changes have been made to the flow since it last ran.)

- Verify the resubmission was successful by viewing the file in the flow OR by checking the ‘Linked Executions’ from the Error message in the flow


- Mark the ticket as ‘Closed’. Assign to yourself (if not already done) and add the TAGS ‘RESOLVED’ and ‘OST ASN’ to the ticket. This is necessary for monthly tracking of tickets by client.

