If the material received on an MRR does not match the PO shipment because it is received damaged, it does not pass inspection, or it has problems for any other reason, an OS&D report describing the problem and suggesting a solution must be generated.
You can create OS&Ds for Receiving on the C.20.09.01 OSD for Receiving screen.
Query the first (Item Shipments) block to display the shipping information of the affected ident.
To create an OS&D report in the second (Over, Short or Damages) block, enter the overage or shortage quantity in the OSD Quantity field. The OSD Number will be generated automatically based on the pre-defined OSD rule assigned to the user. If no OSD rule was assigned, the OSD rule marked as default will be used. Then select the type of the OS&D from the drop-down list in the OSD Type field. The available types are listed below.
-
Over (quantity higher than expected)
-
Short (quantity lower than expected)
-
Damaged (delivered material is damaged)
-
Not to spec (material not delivered in accordance with the specification)
-
Incorrectly received (something wrong with the delivered material)
-
Correctly received (everything is ok)
-
Damaged-Repair (delivered material is damaged and must be repaired)
The m_pck_site_custom.retrieve_osd_def CIP can be used to customize the entries in
the OSD Type drop-down lists in OSD screens. It permits limitation of the availability of OSD
types on project level and even translation and/or redefinition of the semantics of
the existing OSD types. For more information, see RETRIEVE_OSD_DEF.
The current date is entered by default in the OSD Create Date field. When needed, use the LOV to change the date. Specify who is responsible for resolving the problem by entering the name in the Responsible Person field. If it is to be the home office, select the HO Responsible check box. If site personnel are responsible, leave the check box blank.
If you want request procurement expeditor or supplier to take action to resolve the OSD issue before a specific date to avoid the construction delay, enter this date in the Expected Close Date field.
Specify the required action in the Required Action field. If the home office is responsible, expediting must take care of it. Otherwise, the site personnel must take action. Whoever is responsible for taking action is also responsible for closing the OS&D after the problem has been resolved. This is done by entering the date of closing this OS&D in the OS&D Closed Date field and specifying what action was taken to resolve the problem in the Action Taken field.
You can attach documents (like Word documents, PDFs, photos, and so forth) to an OS&D using the fastcall to the D.90.21 Attachments screen.
The Manual check box at the top of the second block indicates a manually created OS&D report.
Select the Query Only OSDs check box if you want to query OSDs in the second block without querying the first block before. This allows you to search for an OSD without knowing its master record.
The project default ZC_OSD_ONE controls whether only one or multiple OSDs are allowed for each MRR (material receiving report). When the project default is set to Y, the number of OSDs (Over, Short, or Damaged) that can be created for material receivings are restricted to one OSD for each MRR (material receiving report). If ZC_OSD_ONE is set to N (default), you can create multiple OSDs for each MRR.