Automatic Ship Transactions
EDI eCommerce Document Import (35.1) imports ASNs to create PO shipper documents. When the shippers are for supplier items controlled using kanban loops, the system automatically updates kanban card status and creates kanban transaction history (kbtr_hist) to indicate that the kanban has been shipped. Because the supplier’s ASN does not include an kanban ID, the system searches for loops that have cards to be shipped based on data from the inbound ASN.
Important: Before selecting a loop that is eligible to have cards shipped, the system validates that Kanban Supplier is Yes in Supplier Data Maintenance (2.3.1) for the loop’s supplier. Otherwise, kanban data is not updated during import of ASNs from that supplier.
To determine which loops can have cards selected, the system first attempts to match the purchase order and line from the ASN line to loop records set up in Kanban Master Maintenance, first for discrete purchase orders and then for orders released from a blanket PO. If no loops are found, the system continues to search for loops based on item number and supplier address code. If the search does not find any qualifying loops, the system continues to process the ASN without creating kanban records.
Important: If the search results in the selection of multiple loops, the following fields in Kanban Master Maintenance must have the same values for all loops. Otherwise, an error message displays and the PO shipper cannot be created from the ASN.
• Kanban Quantity
• Quantity Mismatch Method
• Rounding Threshold
After identifying one or more loops, the system calculates the required number of cards by dividing the quantity shipped (converted into the inventory unit of measure as required) by the kanban quantity in Kanban Master Maintenance.
If the quantity shipped is not a multiple of the kanban quantity, the system uses rounding rules defined in Kanban Master Maintenance. See
Quantity Mismatch Method.
The system then searches all eligible loops for active cards that can be filled without violating transaction sequence rules defined in Kanban Master Maintenance. It searches for cards across all loops in the following order, based on the latest recorded kanban transaction event, until it finds a sufficient number:
1 Acknowledge
2 Authorize
3 Consume
4 Fill
5 Ship
For multiple cards within an event status, the system selects cards based on the authorize date and time, with the oldest cards selected first. In some cases, this may result in the selection of cards from more than one loop.
Important: The ASN creation process can be completed only if each individual shipper line is completed successfully. For example, if sufficient cards are not available to meet the quantity shipped on a line, the system displays an error message and rolls back any database updates that took place as part of import processing.