Logistics Overview - Intergraph Smart Materials - Version 2020 (10.0) - Help - Hexagon PPM

Intergraph Smart Materials Classic Help (2020)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
2020 (10.0)

The P.70.61 Logistics Overview screen can be used as an overview screen similar to the P.70.71 Expediter Workload screen, but showing more detailed information and allowing some updates.

Each order or notice of commitment is displayed once unless multiple shipment groups are created.

Your view on orders can be restricted by sections that are assigned to your user securities on A.20.06.02 or to your role on A.30.03. For more information, see Sections.

On the P.10.74 Configure Logistics Screens screen, you can configure the layout of the P.70.61 and the P.70.62 screen. For more information, see Configure Logistics Screens. In detail, you can:

  • define which fields are displayed,

  • define the order in which these fields are displayed,

  • define the label of the displayed fields,

  • define the field widths,

  • select up to 30 attributes attached on the order header or shipment group level,

  • select up to 10 CIP functions for calculations or displays not provided by the standard fields,

  • determine for some fields whether they are placed in the non-scrollable or in the scrollable area of the screen.

In addition to these configurations that can be made per project and user, you can modify the order by criteria of the displayed records using the Order By... button.

You can use the Fastcall field on the toolbar to open the following screens:

  • A.10.23 Companies

  • C.20.01 Prepare MRR by PO

  • D.90.21 Attachments

  • P.50.07 Maintain Agreements

  • P.70.31 Shipment Groups

  • P.70.41 Close Order

  • P.70.51 Inspection Applications

  • P.70.53 Inspection Application Infos

  • P.70.62 Logistics Details

  • P.70.72 Expediting Details

The following picture shows the P.70.61 Logistics Overview screen.

All approved agreements of type PO (purchase order) and NC (notice of commitment, NOC) are displayed. NOCs are only displayed as long as no PO has been created from this NOC and has been approved.

The Ordered by field at the top of the screen shows by which fields the displayed records are ordered. By default, the records are ordered by:

  • order type

  • order number

  • supplement

You can click the Order By ... button to change the order criteria.

The Order Number field displays the number/name of the agreement, with its supplement in the Suppl field and the type (PO or NC) in the Type field. If the project default ZP_CO_TYPE is set to Y, CO is displayed as the type if at least one approved CO exists for the selected PO/NOC.

You can double-click in the Order Number field to open the P.70.62 Logistics Details screen with the details of the selected agreement.

If change orders have been created and approved for the selected agreement, the supplement of the latest approved change order (CO) is shown in the Latest Suppl field and the approval date of this CO in the CO Date field.

The PO/NOC description is shown in the Description field.

In the Origin field, the name of the office that is responsible for the agreement is displayed.

The Section field shows the section assigned to this agreement.

The name of the supplier's company is displayed in the Supplier Name field. The Manufacturing Company field shows the name of the manufacturer's company.

In the Shipment Group field, the name of the shipment group is shown. To create shipment groups for the selected agreement, you can click the Create SG button at the bottom of the screen. Alternatively, use the fastcall to open the P.70.31 Shipment Groups screen or the P.70.32 Shipment Groups View screen. You can double-click in the Shipment Group field to open the P.70.31 Shipment Groups screen.

In the Carrier Name field, you can select the name of the carrier (that is, the means of conveyance) from the LOV. The carriers pre-defined on the P.80.41 Means of Conveyance screen or the P.80.51 Traffic Fast screen can be selected. A carrier can be assigned to an item shipment. If the item shipments of an order or a shipment group have been assigned to different carriers, 'n Different' is displayed instead of the carrier name. You can update the carrier if no carrier is assigned to the item shipments or if all item shipments are assigned to the same carrier. The predicted on site date will be re-calculated if you update the carrier name and if the project default ZP_EXPDATE is set to Y. You can double-click in this field to open the P.80.42 Means of Conveyance (Multi) screen.

The Voy Flt Num field displays the number of the voyage or the flight. If not all item shipments of the order or shipment group have the same value, 'n Different' is displayed.

The Loading Point field shows the name of the loading point. If not all item shipments of the order or shipment group have the same loading point, 'n Different' is displayed.

The estimated time (date) of departure is shown in the ETD Date field. If not all items shipments of the order or shipment group have the same ETD date, 'n Different' is displayed.

The actual time (date) of departure is shown in the ATD Date field. If not all items shipments of the order or shipment group have the same ATD date, 'n Different' is displayed.

The B/L (AWB) Date field shows the date of the bill of lading (B/L) or the air way bill (AWB).

The name of the unloading point is displayed in the Unloading Point field

The estimated time (date) of arrival is shown in the ETA Date field. If not all item shipments of the order or shipment group have the same ETA date, 'n Different' is displayed.

The actual time (date) of arrival is shown in the ATA Date field. If not all item shipments of the order or shipment group have the same ATA date, 'n Different' is displayed.

The Name 1/Name 2 field shows the first/second name of the vessel, plane, truck, and so forth. If not all item shipments of the order or shipment group have the same value, 'n Different' is displayed instead.

The next fields are quantity fields. The quantities of the line items are added up regardless of the quantity units. The background color of these fields is set to red if different quantity units have been used for the order line items. The Total Line Item Quantity field displays the total quantity of all order line items. This total quantity only contains the quantities of unsplit items and the quantities of master tags. The quantities of detail tags on the order line item level are summed up in the Total Line Item Split Quantity field. The Total ISH Quantity field displays the total quantity of all item shipments. This total only contains the quantities of unsplit items and the quantities of master tags. The quantities of detail tags on the item shipment level are summed up in the Total ISH Split Quantity field.

The invoice number is displayed in the Invoice Number field. If not all item shipments of the order or shipment group have the same invoice number, 'n Different' is displayed. You can update the invoice number. If the record belongs to a shipment group, all records of this shipment group will be updated accordingly.

The value of the invoice is displayed in the Invoice Value field. You can update this value.

The Currency field shows the currency of the order. If the PO is assigned to a shipment group and not all POs of this shipment group have the same currency, 'n Different' is displayed instead.

In the Total Net Weight field, you can enter the total net weight of all assigned items in kg.

In the Total Gross Weight field, you can enter the total gross weight of all items in kg.

The Total Volume field shows the total volume of all assigned items in m³.

The date the PO/NOC was approved is displayed in the Approved field.

The date when the PO/NOC was issued to the supplier is displayed in the Issued field.

The Contract Date field shows the actual contract date or delivery date of the order. This field contains the earliest contract date of all item shipments. If the PO Actual field is already filled for an item shipment, this date will be taken into account. Otherwise, the date of the Prom Contract field is taken into account. If not all item shipments have the same contract date, the background color of this field is set to red.

The Incoterm field shows the name of the incoterm, and the Rev Incoterm field shows the revised incoterm. If not all item shipments of the order or shipment group have the same incoterm, 'n Different' is displayed.

The Delivery Place field shows the delivery place of the material, and the Revised Delivery Place shows the name of the revised delivery place. If not all order line items have the same delivery place assigned, 'n Different' is displayed. The Revised Delivery Place field can be modified if no revised delivery place is assigned to the item shipments or if the same delivery place is assigned to all item shipments. In the case of shipment groups, only the item shipments of that group are updated.

The Delivery Designation field shows the name of the delivery designation. A delivery designation can be assigned to an item shipment. If different delivery designations have been assigned to the item shipments of the order or shipment group, 'n DIFFERENT' is displayed instead. This field can be modified if no delivery designation is assigned to the item shipments or if the same delivery designation is assigned to all item shipments. You can only enter delivery designations pre-defined on the A.10.39 Delivery Designations screen. Use the LOV to select a valid delivery designation. Changing the delivery designation implies that also the value of the routing method must be updated. Therefore, the routing method is filled automatically with the default defined on A.10.39 when another delivery designation is selected. If no default has been defined, the routing method is cleared.

The Routing Method field shows the name of the routing method. A routing method can be assigned to an item shipment. If different routing methods have been assigned to the item shipments of the order or shipment group, 'n DIFFERENT' is displayed instead. This field can be modified if no routing method is assigned to the item shipments or if the same routing method is assigned to all item shipments. You can only enter routing methods pre-defined on the P.10.53 Routing Methods screen. Use the LOV to select a valid routing method. You can only enter routing methods with a delivery designation that was selected in the Delivery Designation field. At the time item shipments are created, the routing method will be filled primarily with the routing method defined for the order header. If this routing method is not valid for the delivery designation, the default routing method defined on A.10.39 is used. If no default has been determined, the Routing Method field remains empty. If you modify this field and the project default ZP_EXPDATE is set to Y, the predicted on site date is re-calculated. If you include the Delivery Designation field in your configuration on P.10.74 but not the Routing Method field, this Routing Method field is displayed nonetheless due to the interdependency.

In the Comment field, you can add any comment on the order or shipment group.

The Tag Number field displays the tag number of the item shipment. If not all order line items have the same tag number, 'n Different' is displayed.

The Prom Contr Min field shows the minimum value of all promised contract dates. If for any item shipment the promised contract date is not set, this field remains empty.

The Prom Contract Max field shows the maximum value of all promised contract dates. If no value is found, this field remains empty.

The Prom Contract field shows the date for which the delivery of the item has been promised. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The PO Actual Min field shows the minimum value of all actual contract dates. If for any item shipment this value is not set, this field remains empty.

The PO Actual Max field shows the maximum value of all actual contract dates. If no value is found, the field remains empty.

The PO Actual field shows the date when the item was actually delivered. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Prom Inspect Min field shows the minimum value of all promised inspection dates. If for any shipment this value is not set, this field remains empty.

The Prom Contract Max field shows the maximum value of all promised contract dates. If no value is found, the field remains empty.

The Prom Inspect Date field shows the date for which the inspection of the item has been promised. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Final Inspect Min field shows the minimum value of all final inspection dates. If for any item shipment this value is not set, this field remains empty.

The Final Inspect Max field shows the maximum value of all final inspection dates. If no value is found, the field remains empty.

The Final Inspect Date field shows the date on which the final inspection took place. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Ready Pred Min field shows the minimum value of all ready predicted dates. If for any item shipment this value is not set, this field remains empty.

The Ready Pred Max field shows the maximum value of all ready predicted dates. If no value is found, the field remains empty.

The Ready Predicted field shows the date for which it is predicted that the item will be ready. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Ready Actual Min field shows the minimum value of all ready actual dates. If for any item shipment this value is not set, this field remains empty.

The Ready Actual Max field shows the maximum value of all ready actual dates. If no value is found, the field remains empty.

The Ready Actual field shows the date when the item was actually ready. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Prom Ship Min field shows the minimum value of all promised ship dates. If for any shipment this value is not set, this field remains empty.

The Prom Ship Max field shows the maximum value of all promised ship dates. If no value is found, the field remains empty.

The Prom Ship field shows the date for which the shipment of the item has been promised. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Rev Prom Ship Min field shows the minimum value of all revised promised ship dates. If for any item shipment this value is not set, this field remains empty.

The Rev Prom Ship Max field shows the maximum value of all revised promised ship dates. If no value is found, the field remains empty.

The Rev Prom Ship field shows the revised promised ship date. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Pred Traffic Arrival Min field shows the minimum value of all predicted traffic arrival dates. If for any item shipment this value is not set, this field remains empty.

The Pred Traffic Arrival Max field shows the maximum value of all predicted traffic arrival dates. If for any item shipment this value is not set, this field remains empty.

The Pred Traffic Arrival field shows the date for which the traffic arrival of the item has been predicted. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Actual Traffic Arrival Min field shows the minimum value of all actual traffic arrival dates. If for any item shipment this value is not set, this field remains empty.

The Actual Traffic Arrival Max field shows the maximum value of all actual traffic arrival dates. If for any item shipment this value is not set, this field remains empty.

The Actual Traffic Arrival field shows the date of the actual traffic arrival of the item. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Prom On Site Min field shows the minimum value of all promised on site dates. If for any item shipment this value is not set, this field remains empty.

The Prom On Site Max field shows the maximum value of all promised on site dates. If no value is found, the field remains empty.

The Prom On Site field shows the date for which the arrival of the item on site has been promised. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Pred On Site Min field shows the minimum value of all dates predicted (estimated) for the arrival on site. If for any item shipment this value is not set, this field remains empty.

The Pred On Site Max field shows the maximum value of all dates predicted (estimated) for the arrival on site. If no value is found, the field is left empty.

The Pred On Site field shows the date predicted (estimated) for the arrival on site. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead. If the project default ZP_EXPDATE is set to Y, the predicted on site dates of the corresponding item shipments are re-calculated automatically if you change the routing method or the carrier on this screen. If a carrier name has been provided, the predicted on site date is calculated as the ATA date of the carrier (or ETA date, if the ATA date is not available) plus the sum of transit days of those entries within the schedule of the routing method located between the entries with date types 'Traffic Arrival' (which is included) and 'Arrival On Site' (which is excluded). If the ETA date of the carrier is empty, too, or if the routing method schedule does not contain an entry of date type 'Traffic Arrival', the carrier is ignored, and the system looks for the actual ship date/predicted ship date/revised promised ship date/promised ship date (in this order, if the respective date looked for is empty) and adds the (total) sum of transit days of the routing method of the item shipment for calculating its predicted on site date. This latter variant also applies in cases where no carrier name has been provided. If ZP_EXPDATE is set to N, the predicted on site dates of the corresponding item shipments are not re-calculated if one of the above mentioned fields is modified.

The Actual On Site Min field shows the minimum value of all actual dates for arrival on site. If for any item shipment this value is not set, this value will be empty.

The Actual On Site Max field shows the maximum value of all actual dates for arrival on site. If no value is found, the field remains empty.

The Actual On Site date shows the date when the item actually arrived on site. If the date values of the corresponding item shipments differ, 'n Different' is displayed instead.

The Req On Site Min field shows the minimum value of all required on site dates. If for any item shipment this value is not set, this field remains empty.

The Req Site Max field shows the maximum value of all required on site dates. If no value is found, the field remains empty.

The Req Site field shows the date on which the item is required on site. If the date values of the corresponding item shipments differ, 'n Different' is displayed where n gives the number of different values.

The Exp Lic Req field shows if an export license is required for this item. If not all item shipments of the order or shipment group have the same value, 'n Different' is displayed instead.

The Ident Short Description field displays the description of the ident. If the corresponding item shipments point to different idents (that is, the descriptions are different), 'n Different' is displayed instead.

The Attribute 1 to 30 fields display attribute values as configured on P.10.74. If the Order Level indicator is checked, the attribute is assigned on the order level. Otherwise, the attribute is assigned on the shipment group level. If no shipment group exists and the attribute is defined as shipment group related, the attribute value is stored on the order level. In the case of order-related attributes, an attribute value is not displayed if the attribute is assigned based on an attribute set and if the display indicator has not been set for orders on the A.50.04 Attribute Sets screen. If the attribute selected on P.10.74 is not assigned to the order or shipment group respectively, this field remains empty. If you modify this field, this attribute is added to the order or shipment group. If the attribute is assigned to the order or shipment group and it is not locked (that is, the kind of the attribute is 'Other'), you can update the attribute value, with the same restrictions and limitations as on A.50.21 Attached Attributes. In other words, valid values specified on A.50.01 Attributes are taken into account in the same way as the defined width of a field. If the update of an attribute is restricted because it was originally part of an attribute set and the Update allowed for orders indicator is not selected on A.50.04 Attribute Sets, you cannot modify the attribute value. Even if the order is approved, it is possible to update attribute values and/or to insert new attributes when the following conditions are fulfilled (this is only valid for attached attributes of type 'Other'). If the project default ZX_MODATTR is set to Y, you can attach attributes on approved orders. These new attributes can be updated or deleted afterwards. If ZX_MODATTR is set to N, it is not possible to attach new attributes on approved orders. Whether an attribute can be modified on an approved order depends on the Allow Update indicator on A.50.01 and the Locked indicator on A.50.21. If Allow Update is selected and Locked is not selected, you can update the attribute value on an approved order. It is not possible to delete the attribute.

The CIP Field 1 to 10 fields display the return value of the CIP function entered for this field on P.10.74 for the selected order.

You can click the Order By ... button to change the order by criteria for the displayed records. When you click this button, an LOV opens, showing all fields currently displayed on the screen. Select the field by which the data should be ordered first. The LOV opens again allowing you to select a second field, and so forth. If you don’t want to select another field, click the Cancel button. The last query is now performed again, this time using the new order by criteria.

The data is always ordered in an ascending order. The selected order by criteria is displayed in the Ordered by field.

The order by criteria are saved and used again when the screen is opened again, for each user. If you want to initialize the order by criteria, click the Order By button and then Cancel. The records are displayed in a random order. If you then close the screen and re-open the screen, the data is ordered again by the default criteria (order type, order number, supplement).

Use the LOV in the CIP Name field to select a pre-defined CIP procedure that you want to execute. The LOV contains all procedures from the package M_PCK_LOGISTIC_CUSTOM, the name of which starts with 'P7061_'. Only those procedures that have two parameters, both of type NUMBER can be selected. The first input parameter is the primary key of m_po_headers (poh_id), and the second is the primary key of m_shipment_groups (sg_id). Click the Execute CIP button to execute the selected CIP procedure. Before the CIP starts, you will be asked whether you want to execute the CIP only for the current record or for all queried records.

The Create SG button is only enabled for orders for which no shipment groups have been created so far. When you click this button, shipment groups are created in the same way as on the P.70.31 Shipment Groups screen. For more information, see Shipment Groups.

You can use the fastcall to the P.70.31 Shipment Groups screen to modify or delete shipment groups.