Expediting Dates - Intergraph Smart Materials - Version 2016 R4 (8.4.0) - Help - Hexagon PPM

Intergraph Smart Materials Classic Help (2016)

PPMProduct
Intergraph Smart Materials
PPMCategory_custom
Help
Version_SPMat
2016 R4 (8.4)

You can open the Expediting Dates window with a double-click in the Pos, Sub, IS Pos, IS Sub, or any of the Destination, Planned, Forecasted, or Actual fields on the Item Shipments tab to get an overview of all dates associated with the item shipment.

These expediting dates are populated automatically when you set or modify the routing method of an item shipment if you work with extended expediting; that is, ZP_NEW_EXP is set to Y. No records will be displayed here if you work with basic expediting.

The number of date fields assigned to an item shipment depends on its routing method. Each destination corresponds to a date field. For each date field, three values exist: a planned date, a forecasted date, and an actual date.

As the actual inspection date is automatically set when assigning an IRC to an item shipment, you cannot update the actual date of the destination that has been marked as 'Inspection.' This behavior also applies to the actual IRC date.

To make sure that all item shipments of a release note have the same delivery date and subsequent dates, you cannot update any forecasted or actual date once a release note has been assigned to an item shipment. For further updates of the dates, you must use the Release Note Dates window, to be accessed from the Release Notes tab with a click on the Dates button.

If detail tags have been created for a tagged item, the expediting dates of the master cannot be modified any longer.

Some events trigger an automatic setting of a forecasted or an actual date:

  • Assignment of IRC -> Actual inspection and actual IRC

  • Assignment of release note -> Forecasted delivery date

  • Ready date for release note -> Actual hand-over date

  • ETD date for means of conveyance -> Forecasted shipping

  • ATD date for means of conveyance -> Actual shipping

  • ETA date for means of conveyance -> Forecasted traffic arrival

  • ATA date for means of conveyance -> Actual traffic arrival

  • Posting of MRR -> Actual arrival on site

See the descriptions of the Forecasted Date and Actual Date fields for more details.

For the description of the fields at the top of the window, see Item Shipments.

The Destination field displays the name of the destination.

The value in the Date Type field determines which type of date this destination represents. This information is necessary for the automatic calculation of planned and forecasted dates in the extended expediting module.

The Delivery Date indicator shows whether the destination represents the contractual delivery date. You must select this indicator for exactly one destination for each routing method if you work with extended expediting; that is, the project default ZP_NEW_EXP is set to Y.

The Planned Date field shows the date for which this event is planned. You cannot update this field. It is automatically filled by the software. Each time you change the routing method of an item shipment, commit modifications on the schedules of a routing method on P.10.53 Routing Methods, or update the promised contractual delivery date of an item shipment, the planned dates are calculated anew. The calculation starts at the destination marked as 'Delivery Date' using the transit days needed between two individual destinations (as entered on P.10.53). The planned date of the destination that has been identified as 'Delivery Date' is set to the contractual delivery date of the item shipment, that is, to the value of the Prom Contract field on the Item Shipments tab of the P.50.07 Maintain Agreements screen.

The planned date will remain empty if you fail to select one destination for 'Delivery Date' on P.10.53, or if the promised contractual delivery date of the item shipment is empty.

The Forecasted Date field shows the date for which this event has been forecasted. When item shipments are created, the planned dates are copied over as the default values for the forecasted dates. The forecasted dates are updated automatically when entering an actual date for a destination. See the description of Actual Dates below for more details on how this calculation works. Despite the default value and the automatic calculation, you can update a forecasted date. Once you have set it manually, the modification of the actual date of any destination lying before this destination has no effect on this forecasted date any longer. That is, the automatic calculation stops when it finds a forecasted date that has been set manually. If you update the forecasted date, the forecasted dates of all following destinations are calculated again based on the transit days. When updating the forecasted date of the destination marked as the delivery date, the forecasted dates of all previous destinations are also recalculated. But, again, these calculations end as soon as the forecasted date of a destination has been modified manually. If project default ZP_SET_MAN is set to Y, forecasted dates that have been set manually are highlighted by a cyan background color. If the project default is set to N (default), manual changes of the forecasted dates are not highlighted.

To make sure that all item shipments of a release note have the same forecasted delivery date, you cannot update any forecasted date of any destination behind and including the one marked as the delivery date once a release note has been assigned to an item shipment.

The following events trigger the forecasted date of specially marked destinations to be set automatically (but nonetheless, this date is marked as having been set manually):

  • If a release note is assigned to an item shipment, the forecasted delivery date of this release note is copied over as the forecasted date of the destination marked on P.10.53 as 'Delivery Date.'

  • If a means of conveyance (MOC) is defined for the release note of an item shipment, the ETD date of the means of conveyance is copied over if the loading point of this transportation is a destination marked as date type 'Shipping.' This also refers to the item shipments on release notes that have been grouped on an MMT that is assigned to a MOC. If the loading point does not represent such a destination but a shipping destination has been assigned to the release note on the MOC, the ETD date of the MOC is copied over to that shipping destination.

  • If a means of conveyance (MOC) is defined for the release note of an item shipment, the ETA date of the means of conveyance is copied over for the destination marked as date type 'Traffic Arrival' if the unloading point of this transportation equals the delivery designation of the release note / item shipment. Again, this also refers to the item shipments on release notes that have been grouped on an MMT that is assigned to a MOC. If the unloading point does not fulfill this criterion but a shipping destination has been assigned to the release note on the MOC, and this shipping destination is the last or only shipping destination of the associated routing method, the ETA date of the MOC is copied over to the destination of type 'Traffic Arrival.' In both cases, if no destination of type 'Traffic Arrival' exists but a destination of type 'Arrival On Site' exists, this one will be updated instead.

  • If more than one shipping destination has been defined for a routing method and a shipping destination has been provided for the release note on a MOC, the ETA/ATA date of the MOC is copied over as the forecasted date for the next shipping destination within the routing method.

The Actual Date field shows the date on which this event actually took place. If you save an actual date to the database, an automatic calculation of the forecasted dates starts. This calculation uses the transit days for the routing method of the item shipment entered on P.10.53. The automatic calculation stops if another actual date has been found or if the forecasted date has been set manually. If you enter an actual date for a destination the sequence of which is lower than the sequence of another destination for which an actual date has already been entered, the calculation stops at the destination of higher sequence. If you delete an actual date, the calculation uses the actual date of any destination with a lower sequence where the actual date is still set. If such a destination cannot be found, the forecasted date of the actual destination is used as the starting point for the recalculation of the forecasted dates of the next destinations.

The actual dates must be in ascending order. If, nevertheless, the actual dates are not in an ascending order, this situation has been caused by a change of the routing method of the item shipment or an update of the routing method schedule. In this case, the sequence of some date types has been changed. For example, the event 'Shipping' now takes place after the destination marked as 'IRC Date,' but actual dates were already set for 'IRC Date' and 'Shipping,' which had a reverse order before the updates were done.

Once a release note has been assigned to an item shipment, you cannot update any actual date of any destination behind and including the one marked as the delivery date.

The following events cause the actual date to be set automatically.

  • If an IRC is assigned to an item shipment, the actual inspection date is copied over to the destination that has been marked on P.10.53 as 'Inspection.' The IRC date is copied over to the destination of type 'IRC.'

  • If the date of readiness is set for a release note of an item shipment on P.70.74 Packages, this date is copied over to the destination marked as 'Hand-Over Point.'

  • If the ATD date is entered for a means of conveyance (MOC) to which the release note of the item shipment has been assigned and the loading point of which is a destination marked as 'Shipping,' this ATD date is copied over as the actual date for this destination. This also refers to the item shipments on release notes that have been grouped on an MMT that is assigned to a MOC. If the loading point does not represent such a destination but a shipping destination has been assigned to the release note on the MOC, the ATD date of the MOC is copied over to that shipping destination.

  • If the ATA date is entered for a means of conveyance (MOC) to which the release note of the item shipment has been assigned and the unloading point of which is the delivery designation of the release note / item shipment, this ATA date is copied over as the actual date for the destination marked as 'Traffic Arrival.' Again, this also refers to the item shipments on release notes that have been grouped on an MMT that is assigned to a MOC. If the unloading point does not fulfill this criterion but a shipping destination has been assigned to the release note on the MOC and this shipping destination is the last (or only) shipping destination of the associated routing method, the ATA date of the MOC is copied over to the destination of type 'Traffic Arrival.' In both cases, if no destination of type 'Traffic Arrival' exists but a destination of type 'Arrival On Site,' this one will be updated instead.

  • If you post a material receiving report (MRR), the actual date of the destination that is of type 'Arrival On Site' is filled. Depending on the setting of project default ZC_UPD_EXP, this is either the date of the material receipt ('Y') or the posting date of the MRR ('N').