Adherence to Delivery Dates - Intergraph Smart Materials - 10.2 - Help - Hexagon

Intergraph Smart Materials Web Help (10.2)

Language
English
Product
Intergraph Smart Materials
Subproduct
Web
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.2

The Adherence to Delivery Dates report can be used to view the delay in material delivery. The report displays two pie charts and the corresponding timelines.

The Required On Site vs. Delivered chart shows the result of the comparison of the required on site date with the receiving on site date. That means, it shows how accurate the required on site date has been planned. The required on site date is set by engineering on the requisition, copied to the agreement, and possibly modified by expediting. The receiving on site date is set on the MRR line item; it’s the date when the material is booked into the inventory when it arrives on site.

This chart covers the entire material supply chain, including the supplier and all freight forwarders, until the goods arrive at the final destination. It depends on the agreed incoterm until which step the responsibility and risk is borne by the supplier.

The Supplier Promised Contract vs. Actual Contract Date chart shows the result of the comparison of the promised contract date with the actual contract date. That means, it shows how reliable the supplier is concerning the adherence of agreed delivery schedules. With the promised contract date, which is part of the contractual obligations and specified in the agreement, the supplier confirms to make the ordered material available at this date and at the delivery place defined by the agreed incoterm. The actual contract date indicates the date when the material is actually available for further usage.

For example, if the incoterm is FOB (free on board), the contractual obligation of the supplier is to deliver the material on a ship until a certain point in time. Or, if the incoterm is EXW (ex works), the supplier must provide the material ready for collection until the agreed date. The picture below illustrates both examples.

BIRAdherenceToDeliveryDate

The assessment matrix on the picture below presents, how the delivery is considered as being on-time or delayed, and which situations are not considered at all.

BIRAdherenceToDeliveryDateMatrix

Before you run this report, you must execute a database job that prepares the data for the report. It is recommended to run this job at least once a day. For more details see Manage Synchronization Jobs.

Only agreements with order type Purchase Order (PO) are considered by this report.

After selecting a project, the report shows the calculation result for all suppliers and the selected project over the past 12 activity months (this means, months without any activity are not considered/displayed).

To show the values for a supplier and a project, select the supplier and the project.

To change the observation period, select another value from the Show past list. The available values are 6 months, 12 months, 24 months, and all.

The pie charts show the total quantity that is on time in blue, and the total quantity that is delayed in red. The line charts show the average days delayed on a monthly base.

The delay for Required on Site vs. Delivered is calculated as follows:

Days delayed = Actual Received Date – Required on Site Date.

  • Actual Received Date is fetched from the latest receiving date of the item shipment (Recv Date field on Receiving screen in the Inventory Receipts block). Only posted MRRs are considered.

  • Required on Site Date is fetched from the required on site date of the corresponding item shipment (Req On Site field on P.70.72 screen).

The delay for Supplier Promised Contract vs. Actual Contract Date is calculated as follows:

Days delayed = Supplier Delivered – Supplier Promised

  • Supplier Delivered is fetched by the m_pck_bir_custom.get_actual_ship_date CIP function. By default, the function returns the actual contract date (PO Actual field on P.70.72 screen).

  • Supplier Promised is fetched by the m_pck_bir_custom.get_planned_ship_date CIP function. By default, the function returns the promised contract date (Prom Contract field on P.70.72 screen).

If you want to use other dates to be fetched, you must customize the mentioned CIPs. For more information about CIPs, see Customer-installed procedure (CIP) Tasks.

You can click on a pie chart segment to open the Expediting report where the details are displayed. For more information, see Expediting.

Data Sources

The table below shows the Smart Materials screen(s) where the data is entered that is displayed in this report. Additionally, this table shows the synchronization table and the CIPs used by the report, and the name of the log file created by the sync job or the report.

Screen

P.70.72 Expediting Details

C.20.01-.05 Receiving (-> Actual Received Date)

Table

P170_IR_DATA

CIP

m_pck_bir_custom.get_actual_ship_date (-> Supplier Delivered)

m_pck_bir_custom.get_planned_ship_date (-> Supplier Promised)

Log File

n/a

The following table shows all values displayed in the report, with the related Smart Materials screen and field where the value is displayed, the database table and column where the value is stored, and CIPs, functions, or procedures that are used to retrieve the value. Optionally, additional comment on the value is entered in the last column.

Value

Screen

Field

Database Column

Other Source/Comment

Supplier

P.70.71

Supplier

m_po_headers.sup_id (-> m_suppliers.sup_code)

Project

P.70.71

Project

m_req_to_pos.proj_id

Delayed Quantity

MRR date later than ROS date
or
No MRR and SYSDATE later than ROS date

On-time Quantity

MRR date earlier than ROS date

Delayed Supplier Quantity

Supplier Delivered later than Supplier Promised
or
Supplier has not yet delivered and SYSDATE later than Supplier Promised

On-time Supplier Quantity

Supplier Delivered earlier than Supplier Promised