Sign in
< Back to Top

X12 856 (As X12 945 Warehouse Shipping Advice)

This article has two parts. The first explains how to process a 945 inbound warehouse shipping advice received from a 3PL Trading Partner. The second part explains how to translate the 945 to EDI 856 and send it to the Buyer Trading Partner.

Processing an inbound 945

When an inbound 945 is received from the 3PL Trading Partner (inbound endpoint), the InboundAzureEV event is triggered and InboundPreprocessorBPS is executed. This BPS involves ReceiveEDIEvent, which searches for a matching inbound route.

This section explains how to configure the integration to process the Inbound Warehouse shipping advice received from 3PL Trading Partners.

How to Configure

  1. Configure the Inbound Route: The Inbound Route is set up with Sender ID as 3PL Warehouse Trading Partner name and Receiver ID as the customer name supplied in the Wizard properties file (wizard-input.properties file residing in the resources folder). If there are changes, you must modify _TP_945v4010IR - in com.cleo._customer_.d365scm._tp_.inbound.n945.v4010. 945 inbound objects are referenced from the Warehouse Trading Partner project.
  2. Configure the 997 Enveloper: The 997 envelope details and the Trading Partner Endpoint to which the 997 is to be sent must be configured in _TP_997ENV - in the Trading Partner project under the com.cleo._customer_.d365scm._tp_.outbound.n997 package.

How to Run the Flow

  1. Before proceeding, ensure that the following Projects have been deployed. If any of these Projects are already deployed and remain unmodified, there is no need to redeploy them. Similarly, if any of these Projects were not checked out to your Workspace, they can be skipped from the deployment process.
    • com.cleo._customer_.edi
    • com.cleo._customer_.edi.booster.d365scm
    • com.cleo._customer_.edid365scm
    • com.cleo._customer_.d365scm._tp_ (Warehouse TP)
    • com.cleo._customer_.d365scm._tp_ (Buyer TP)
    • com.cleo.b2bcloud.core
    • com.cleo.b2biaas.clarify
    • com.cleo.cic.cockpit.core
    • com.cleo.cic.cockpit.core.n810
    • com.cleo.cic.cockpit.core.n850
    • com.cleo.cic.cockpit.core.n855
    • com.cleo.cic.cockpit.core.n856
    • com.cleo.cic.cockpit.core.n940
    • com.cleo.cic.cockpit.core.n945
    • com.cleo.cic.connector.d365scm
  2. Configure the Exit Points as follows:
    Exit Point Name Event Name
    Inbound Acknowledgement Error com.cleo.b2bcloud.core.events.B2BCloud_ExitPointInboundAckErrorEV
    Inbound Duplicate Interchange com.cleo.b2bcloud.core.events.B2BCloud_ExitPointIDuplicateInterchangeEV
    Inbound EDI Route Error com.cleo.b2bcloud.core.events.B2BCloud_ExitPointRouteErrorEV
    Inbound EDI Route Note Found com.cleo.b2bcloud.core.events.B2BCloud_ExitPointEDIRouteNotFoundErrorEV
    Inbound EDI Process Binding Not Found com.cleo.b2bcloud.core.events.B2BCloud_ExitPointEDIRouteProcessBindingNotFoundEV
    Inbound Interchange Processed  
  3. Configure the Data Flow: Add a new Data Flow and select the required source endpoint and Transformation as the target Endpoint and select the event com.cleo._customer_.edid365scm.inbound.InboundAzureEV.

    mceclip1.png

  4. Monitor the flow
    • Log Entries (Studio Auditor)
    • Message Tiles (Cockpit)
    • Jobs (Cockpit)
    • Dashboard > Charts (Cockpit)

Note: The existing accelerator does not process the Warehouse shipping advice data (EDI 945) in D365SCM. It just uses this data to convert it into ASN EDI 3PL. The above inbound configuration is required for creating ASN using 3PL Trading Partner 945 information.

Sending an 856 to the Buyer Trading Partner

If the global variable, CreateAsnFromWarehouseShipmentAdviceFlag (located in DynamicsSCMGV) is set to Yes, the warehouse shipping advice EDI 945 is used to look up a matching outbound route. If there is a match, the EDI 945 from the Warehouse 3PL Trading Partner is translated to EDI 856 and sent to the Buyer Trading Partner.

This section explains how to configure the integration to retrieve EDI 945 data and transform it to EDI X12 856 format for the Buyer Trading Partner.

How to Configure

856 3PL outbound objects are referenced from the Buyer Trading Partner project

  1. Configure the Outbound Route:
    • 856 3PL outbound objects are referenced from the Buyer Trading Partner project.
    • The Trading Partner id in the EDI X12 856 identifies the Buyer Trading Partner to whom the 856 is to be sent. The target trading partner is set to the buyer trading partner name mentioned in wizard-input.properties file by default. If the Trading Partner name does not match the ‘tpname’ while creating the project using the Wizard, you must update the Outbound Route to reflect the matching name in _TP_856_3PLv4010OR in the com.cleo._customer_.d365scm._tp_.outbound.n856.3PL.v4010 package.
  2. Configure the Enveloper: The X12 856 envelope details and the Trading Partner Endpoint to which the X12 856 is to be sent should be configured in _TP_856_3PLv4010ENV - in the Buyer Trading Partner project under com.cleo._customer_.d365scm._tp_.outbound.n856.n3PL.v4010 package. By default, the Customer name and the TP Name entered in the wizard-input.properties file are added to the sender and receiver id, respectively. If there are any changes to the enveloping details the same object must be updated. The 856 Enveloper contains sender ids as the Customer name and receiver ids as the Buyer Trading Partner name specified in the wizard-input.properties file.

How to Run the Flow

  1. Prior to running the flow, any Project that has been edited must be redeployed. These may include some or all of the following:
    • com.cleo._customer_.edi
    • com.cleo._customer_.edi.booster.d365scmv
    • com.cleo._customer_.edid365scm
    • com.cleo._customer_.d365scm._tp_ (Warehouse TP)
    • com.cleo._customer_.d365scm._tp_ (Buyer TP)
    • com.cleo.b2bcloud.core
    • com.cleo.b2biaas.clarify
    • com.cleo.cic.cockpit.core
    • com.cleo.cic.cockpit.core.n810
    • com.cleo.cic.cockpit.core.n850
    • com.cleo.cic.cockpit.core.n855
    • com.cleo.cic.cockpit.core.n856
    • com.cleo.cic.cockpit.core.n940
    • com.cleo.cic.cockpit.core.n945
    • com.cleo.cic.connector.d365scm
  2. Automatically run the flow: LaunchD365ScmAsn_3PLBPS.bps kicks off automatically when an EDI 945 is received based on the flag value.

    CreateAsnFromWarehouseShipmentAdviceFlag.DynamicsSCMGV.globalVar and the 856 3PL flow is triggered.

  3. Monitor the flow
    • Log Entries (Studio Auditor)
    • Message Tiles (Cockpit)
    • Jobs (Cockpit)
    • Dashboard > Charts (Cockpit)

In case of errors, a ticket is generated; information will also be visible in the Message and Job views in CIC Cockpit. 

For Outbound EDI validation use cases, see Validation Rules in the Transformation Settings object.

How to Customize

  1. Add more details to the X12 856 from the Warehouse Shipment 945 file. The values mapped are documented in the Integration Design Spec template present in com.cleo._customer_.edid365scm project under the docs folder. If you want to add more fields, you must update the ruleset _TP_856_3PLv4010RS in com.cleo._customer_.d365scm._tp_.outbound.n856.n3pl.v4010 package.
  2. Contact Cleo support if you need assistance.

Related Topics

Related articles

Comments

0 comments

Please sign in to leave a comment.