Notifications

ASN

ASN are electronic messages that provide product and shipment information to a customer before delivery.

EDI tables maintain ASN data, and this enables you to quickly change ASN data to send timely messages to customers. If the changes must also be reflected in the demand and shipping tables, you can make those changes through the appropriate application at a later time. You can also roll up totals and updates to related records.

You can set up customer rules and preferences to specify whether to perform ASN tracking. The rules and preferences determine how long the system waits for an ASN acknowledgment to be received before sending a message, and the workflow process name to be initiated. For example, to be informed that an ASN was not acknowledged within twenty minutes, the customer rules specify twenty minutes. If the wait time expires, the system sends an E-mail to the designated personnel.

Acknowledgments

When you receive an EDI acknowledgment or application advice, the System/47 ASN database is updated with the acknowledgment date and time, and the status. The system processes these transactions for the ASN and the invoice.

You use customer rules to determine what type of activity takes place at each status. Statuses are:

• Rejected

• Accepted with Errors

• Accepted

Each of these statuses can optionally initiate a workflow process that can send a message or an email. You can correct any required data or mapping issues and resubmit the ASN for transmission.

Demand Adjustments

When a shipment is confirmed, the system issues an XAPI message with shipment information and adjusts the demand to handle remaining, partial requirements if the actual amount that is shipped is less than the amount that is required.

Demand is adjusted after the system receives the inbound demand and processes the associated order. The system uses the shipment confirmation message to communicate the actual quantity that is shipped to the rest of the system. The system uses the quantity shipped (including cartons) to adjust the original demand request and the associated cumulative quantities.

For product messages (sales order detail lines), the system sends this information:

• Demand ID

• Branch/plant

• Sold To address book number

• Ship To address book number

• Quantity shipped

• Unit of measure

• Shipment number

• Actual shipment date

• Actual shipment time

For carton messages, the system sends this information:

• Branch/plant

• Sold To address book number

• Ship To address book number

• Customer carton number

• Number of cartons

The system uses the statuses of the ahead and behind calculation to determine whether to perform the update.

The system also updates cumulative shipped amounts for products and cartons if you have activated cumulative tracking.

Demand Workflow Notification

The contents of EDI and the way it is transmitted, varies from customer to customer. To accommodate those differences, a default workflow has been created that contains known business processes used by many trading partners. Each activity in this workflow represents a business process. The user has the option to use this default workflow, or copy the workflow and modify the activities. When modified, the user can define which Branch/Plant, Sold To, and Ship To combinations should use the new workflow. The user has the option to not launch a workflow for a particular customer, in which case the user does not define a workflow for the Branch/Plant, Sold To, and Ship To combination.

Demand Net Variance Workflow Notification

The Net Change Variance Workflow initiates a single messaging function activity to alert production or other personnel about a net variance change that exceeds the user-defined tolerance. Parameters passed in the data structure of the workflow permit the customer to customize the workflow or messaging as business practices may require.

Invoicing

The system creates the invoice after shipment confirmation. The system uses the Print Invoices program (R42565) to collect the required data from the related system files, and then converts the data into Electronic Commerce (47) system files.

The system then uses the EDI Invoice Extraction Conversion program (R47042C) to create a flat file. The translator maps the flat file into an 810 or INVOIC format, which you send to the customer.