Maintaining MSDS for Customers Overview

Use the Material Safety Data Sheets (MSDS) application to track which MSDS have been sent to a customer.

For example, events can flow as follows:

On January 15, on Sales Order 1 shipping on January 20, a customer orders Product A, which requires MSDS #1.
Then, on January 18, on Sales Order 2 shipping on January 21, the customer orders Product B, which also requires MSDS #1. Because you need to send an MSDS only when a customer first purchases a product requiring that MSDS, the system does not require sending an MSDS with Product B.
Next, on January 20, the customer cancels Sales Order 1 before it ships. Finally, on January 21, Sales Order 2 ships without an MSDS for Product B.

The MSDS application tracks this sequence of events so you know the customer requires MSDS #1 to be shipped for Product B.

Use the following MSDS programs to maintain MSDS for customers:

MSDS Exception Queue - Determines which MSDS needs to be sent to customers and records when MSDS have been sent to customers. Before you can use the queue, you must build it or schedule it to build at regular intervals.
MSDS Sheets Sent Report - Creates a list of the MSDS that were sent to customers.