The OS&D report is logged by a recipient of a shipment, together with a claim, and sent to the carrier of the shipment. It details what items listed in the shipping documents have been received over-shipped, short-shipped, or in an unsatisfactory or damaged condition.
The OS&D process takes place at various points in the supply chain.
Prior to final inspection, no OS&D is issued. If during final inspection a problem is discovered, a Non-Conformance Report (NCR) is issued to identify the problem and ensure a resolution.
The OS&D process starts the moment a release note (release for shipment) is issued. At that point, for example, it could be discovered that a portion of the promised shipment/quantity is unavailable, and thus the paperwork must be adjusted.
An OS&D for a release note that describes the problem is issued, and the problem is assigned to the individual who will coordinate with the supplier to expedite a resolution. The next OS&D point is during the pre-transport inspection if the package is found to be damaged or the paperwork is discovered to be out of order. The issue of the OS&D ensures that the appropriate individuals are involved in resolving the issue, thus preventing any further delay.
A similar situation can also occur at the stage in which the items are packaged, and the package is linked to an approved release note, thus resulting in an OS&D being issued.
Damage can also occur during item shipment (means of conveyance stage). When this happens, an OS&D is issued to ensure that corrective action is taken.
If material arrives at the site/shop in an incorrect quantity or of poor quality, an OS&D for receipt is created and issued.
When material is received correctly but was damaged during storage and transport, an OS&D for inventory is issued.
OS&D reports are created automatically when posting MRRs on the receiving screens C.20.01, C.20.01.02, C.20.04, or C.20.05 when the Auto create OSDs check box is selected and the received quantity is over or short.
Or, you can create the OS&D report manually in the Traffic module of MSCM (screens PT.30.01-.04) and in the Site module on the C.20.09.xx screens.
At the end of the OSD creation procedure, the CIP m_pck_site_custom.post_osd_creation is called. By default, this CIP is empty, which means it does not modify any data or perform any checks. You can use this CIP, for example, to fill in additional information, for example, you want the Required Action be inserted automatically when the OSD is created.