Site Arrival - 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 Arrival On Site Destination field displays the name of the first/second/third destination (in the routing method) that has been marked as 'Arrival On Site.' If this destination represents the contractual delivery date, the background color of this field is set to magenta. A destination marks the contractual delivery date if the Delivery Date check box has been set for it on the P.10.53 Routing Methods screen. You can double-click in this field to open the Expediting Dates window, which provides a tabular view of all expediting dates. For more information, see Expediting Dates.

The Arrival On Site Planned field shows the planned date of the first/second/third destination (in the routing method) that has been marked as 'Arrival On Site.' You can double-click in this field to open the Expediting Dates window.

The Arrival On Site Forecasted field shows the forecasted date of the first/second/third destination (in the routing method) that has been marked as 'Arrival On Site.' If the forecasted date has been set manually, it is highlighted by a cyan background color. You can double-click in this field to open the Expediting Dates window.

The Arrival On Site Actual field shows the actual date of the first/second/third destination (in the routing method) that has been marked as 'Arrival On Site.' You can double-click in this field to open the Expediting Dates window.

The Ident Short Description field displays the ident short description, which is derived by executing the CIP procedure m_pck_std_custom.ident_desc.

If an ident deviation has occurred for the item shipment, that is, if the attribute that has been assigned to project default ZP_DEVATTR is attached to the item shipment, the value of this attribute is shown in the Ident Deviation field because this value is assumed to be the new correct ident short description. In the Ident Short Description field, the description of the ident that is actually on the item shipment is always displayed.

In the Outstanding Work List field, you can enter an outstanding list of work. Typically, you describe here the work that has to be done when the item shipment has arrived on site.

To see whether this work is still outstanding, check the OWL Comp indicator.

The OWL Comp indicator shows if an OWL (Outstanding Work List) for this item shipment is completed. The indicator is marked if the work has been done; it is not marked if the work is still outstanding. When you assign a release note to an item shipment with an OWL still incomplete, a warning appears.

In the Non Conformity Report field, you can enter a non conformity report (NCR). A release note can only be created for an item shipment if no NCR exists or if an NCR exists but the NCR Comp check box is marked. An NCR can be entered as long as no release note has been assigned to an item shipment. Once a release note has been created for an item shipment, the NCR cannot be changed or inserted any longer.

The NCR Comp indicator shows whether the NCR (non conformity report) has been completed.

A release note can only be assigned to an item shipment if no NCR exists or if an NCR exists and this check box has been checked. This check box can be updated as long as no release note has been assigned to an item shipment. Once a release note has been created, this check box cannot be modified any longer.

You can click the Order By ... button to change the order by criteria for the displayed records. When you click this button, a list of values is opened, offering you all the columns currently visible in the form. Select the field by which you want the data to be ordered by in the first place. Then a second list of values comes up, allowing you to select a second field. In this way, you can select up to four fields by which the data is to be ordered. If you do not need any further fields as order by criteria, just click the Cancel button in the LOV box. After the last LOV has been closed, your last query is performed again, this time using the new order by criteria. The data is always sorted in ascending order. The selected and changed order by criteria are displayed in the Ordered by field.

Select the History check box to view all item shipments of an order cycle, even the outdated ones. Then it switches into the history mode where even item shipments of previous requisition supplements are displayed that are no longer available for expediting because they have been replaced by change orders. When looking at item shipments in history mode, you cannot apply any changes regardless of whether the data is outdated or not. If you need to apply modifications, you must return to the non-history mode by clearing this check box. In history mode, the Expediting Dates and Associated Requisition Line Items windows are also available, but you cannot apply any changes.

Select the Highlight Changes check box to see which fields have changed compared to the previous acknowledged order supplement. All fields that have been modified are shown using a red color. To make it easier to see whether any item shipment was changed, all Pos fields are displayed in a red color for all affected item shipments, although the value of this field itself will not change from supplement to supplement. Changes are only highlighted for item shipments that have not been acknowledged so far. That is, only if the Acknow indicator is not marked are the field values displayed in red. If no previous supplement exists at all, that is, if only order supplement 0 has been created so far, no item shipment is highlighted regardless of the setting of the Acknow check box. If no previous supplement exists for an order line item, the Pos and Item Ship Quantity fields will be highlighted. If an item shipment was not included on the previous supplement and it has been created because of a surplus quantity, the Pos and Item Ship Quantity fields will be highlighted for all item shipments without a release note of the affected order line item. If an item shipment was not included on the previous supplement and it has been created because of a shortage quantity, nothing will be highlighted at all for the associated order line item. Look-up fields or calculated fields such as PO-Req Delta or Total ISH Weight are not highlighted even if the value changed.

Depending on the number of item shipments, the display of data may take some time. The default setting of this check box is determined by the setting of project default ZP_HC_DFLT.

Click the Create Item Shipment button to create an additional item shipment for the current order line item. To avoid the unintended creation of item shipments by simply clicking in empty lines, the usual insert functionality via toolbar or via function key F6 has been disabled. Instead, you must use this button deliberately to split quantities. This button is not active for tagged master items or sub items. Before the item shipment is actually created, the CIP m_pck_exp_custom.check_create_ish is called. Only if this CIP does not raise any error is the item shipment created.

If you want to create more than just one split, you can use the No. of Splits field to enter the number of splits before you click the Split Tag button. The default value of this field is 1. In case the first split is created, two splits are created (at least), regardless of the value of this field.

You can click the Split Tag button to split an item shipment. For more information, see Split Tag.

You cannot create a split if additional item shipments were created using the Create Item Shipment button (not to be confused with detail tags). If the order to which an item shipment belongs has been created for the corporate or FIM warehouses, a tagged item cannot be split either. Splits can be created even if an MCS, an IRC, or a release note is already assigned to the item shipment. When you split such tags, the MCS, IRC, or release note number of the master tag is copied over to the new detail tags, and afterwards the MCS, IRC, or release note number is removed from the master tag. As, for example, the item shipment quantity cannot be modified if an MCS has already been assigned to an item shipment, and as likewise, the IRC quantity cannot be changed if a release note is already assigned, and an intermediate step must be performed. A window opens where you can enter the quantity for the new detail tags before they are actually created.

Splits cannot be created any longer if a release note has already been assigned and the item shipment has been placed in a package or the release note has been approved or the item shipment has already been received on site.

Whether a split is created here on the order line item level or the item shipment level depends on the current status of the line item and on the setting of project default ZP_SP_POLI. If a split has already occurred on the line item level or ZP_SP_POLI is set to Y, additional splits are created on the order line item level. If the first split has been carried out on the item shipment level, if no split exists so far, or if ZP_SP_POLI is set to N, splits are added or created on the item shipment level. The number of detail tags to be created in one step is determined by the value in the No. of Splits field.

When splitting a tag for the first time, two splits are created if the number of requested splits is 1.

You cannot create additional item shipments using the Create Item Shipment button for a master tag. Once a detail tag has been created, the master cannot be placed on any MCS, IRC, or release note; only the detail tags can be tracked, controlled, and received.

The project default ZP_HIDE_MT (default = 'N') enables you to hide the master tags (ZP_HIDE_MT = 'Y') or show the master tags (ZP_HIDE_MT = 'N'). The detail tags are shown in any case. Depending on this project default, the label of the split button changes to <Split Master Tag> if ZP_HIDE_MT = 'Y' and the cursor is on a detail tag; and back to <Split Tag> in all other cases if the cursor is on a master tag or any tag that can be split.

If you update the values of the master tag, you can decide whether you want these modified values to be copied over to the detail tags or not. This feature is only available for the following fields:

  • PO Actual

  • Prom Inspect

  • Final Inspect

  • Ready Predicted

  • Ready Actual

  • Pred On Site

  • Actual On Site

  • Req On Site

  • Maj Matl Order

  • Maj Matl Recv

  • Actual Fab Start

  • Comp %

  • 50% Comp

  • Prom Fab Comp

  • Actual Fab Comp

  • Fab Location

  • Fab Ctrl Number

  • Inspection Location

  • Weight Unit

  • Volume Unit

The population of values from a master tag to its detail tags works for both splits created on the order line item level and splits created on the item shipment level. When you set one of the following dates for the last detail tag (that is, there are no more detail tags for which this date is empty), the latest date of all detail tags is copied over to the master tag:

  • Curr/Rev Prom Ship

  • PO Actual

  • Final Inspect

  • Ready Actual

  • Actual Ship

  • Actual On Site

  • Actual Fab Start

  • Actual Fab Comp

If you delete the second-to-last detail tag, the remaining detail tag is also deleted. Thus, it is prevented that a master tag exists with only one detail tag. The sub position of the master is reset to 1.

You can click the Attributes button to open the A.50.21 Attached Attributes screen where the attributes attached to the item shipment are maintained. For more information, see Attached Attributes.