EDI Dispatch List Transmittal
You can use EDI eCommerce to export a kanban dispatch list in the form of a special type of shipping schedule that includes typical schedule data such as the item, purchase order number, quantity, and due date, along with kanban-specific data such as the card ID, supermarket site and ID, and so on.
To send dispatch lists in EDI format, you must:
• Define EDI eCommerce transformation records, including appropriate definitions for an application document, exchange file, implementation, and transformation map.
Note: The export gateway that supports this feature uses the same SNF and the same exchange definition as standard 830 and 862 schedules. Although a kanban-specific implementation definition is required, you can use the current Schedule exchange definition for exporting dispatch lists.
• Correctly set up EDI eCommerce trading partner cross-references between the receiving site and the kanban loop supplier, including the following settings in Trading Partner Parameter Maint (35.13.10):
• Send Kanban Dispatch: logical parameter set to Yes
• Kanban Dispatch Doc Name: character parameter set to Kanban-Dispatch
• Kanban Dispatch Doc Ver: integer parameter set to 1
• Ensure that the loop is associated with a valid, open purchase order in Kanban Master Maintenance, or that a blanket purchase order matching the supplier and item is available for release.
• In the Kanban Master Maintenance Dispatch List Processing frame, set EDI to Yes for the loop.
• In Kanban Dispatch List Processing, set EDI to Yes.
When those conditions are met and Update Dispatched Cards is Yes, the system attempts to create an EDI eCommerce application document repository record and populate it as specified in the applicable implementation definition. If it succeeds, it next begins the export process, transforming the document based on mappings in the transformation definition and creating records in the exchange repository. Finally, the system creates a standards neutral format (SNF) file that can be sent as specified for the supplier’s transmission group.
If any errors occur before the system successfully creates the repository record, the Kanban Dispatch List Processing output report displays related error messages and does not dispatch the card. For example, if the purchase order associated with a loop has been closed, cards cannot be added to the dispatch list.