Shipment Groups - 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)

A shipment group is used to collect item shipments with the same promised ship date (or current/revised promised ship date if already set), routing method, incoterm, delivery place, and carrier (MOC) from an order. It can be useful for the expediter to work with shipment groups for tracking purposes. Shipment groups are maintained on the P.70.31 Shipment Groups screen. You can open this screen via fastcall from the P.70.61 Logistics Overview screen or with a double-click in the Shipment Group field on the Item Shipments tab of the P.70.72 Expediting Details screen.

In addition to the automatically generated shipment groups, you can create manual shipment groups, but this creation is only possible after the automatic generation has been carried out. Create a new record in the second (Shipment Groups) block, and enter the criteria for the Curr/Rev Prom Ship field, Delv. Desig. field, and so forth. Next, use the LOV in the first field of the third block to select the item shipments to be assigned to this manual shipment group. After saving these item shipments, former members of other shipment groups are now shifted to this manual shipment group. If after saving, one of the automatically generated shipment groups has no more item shipments because you have moved all of them to a manual shipment group, this (now) empty shipment group disappears from the second block.

If you make any changes to a manual shipment group or to an item shipment belonging to a manual shipment group, these changes have no influence on the connection between the shipment group and the item shipment. (Remember: if you change one or more of the relevant items of a shipment group, these changes are made to all corresponding item shipments. If you make any changes to an item shipment, this item shipment is shifted to another shipment group or a new shipment group is created. If only one item shipment belongs to the shipment group and you change relevant items of the shipment group, the shipment group is also updated).

If you delete an item shipment of a manual shipment group, this item shipment is shifted to the shipment group that it would be part of after an automatic generation (Create SG button).

If you delete a manual shipment group with one or more item shipments (deletion in the second block), all item shipments are shifted back.

A deletion of all shipment groups (Delete SG button) is only possible if no manual shipment group exists; otherwise, a message informs you. In this case, first delete the manual shipment groups (the corresponding item shipments are shifted back), and then click Delete SG again.

Each time the value of any criteria that are used for building the shipment groups changes on any of the involved item shipments, the shipment groups are rebuilt.

Shipment groups for which values for

  • Invoice Value

  • Currency

  • Total Net Weight

  • Total Gross Weight

  • Total Volume

have been entered on the P.70.61 Logistics Overview screen are not re-created to keep this information. Item shipments can be removed or added but the shipment groups themselves are not re-created to ensure that the information is not lost.

Order Header

In the first (Order Header) block, the selected agreement is displayed.

The Groups indicator shows whether shipment groups exist for this order.

The Order Number field shows the number/name of the selected agreement. The Type field shows the order type for the agreement, either PO for purchase orders or NC for notices of commitment. If the project default ZP_CO_TYPE is set to Y (default is N), CO is displayed as the type if at least one approved change order exists for the current agreement.

The Suppl field shows the agreement supplement number. If project default ZP_COSUPPL is set to N (default), the supplement number of the order itself is displayed, even if change orders have already been created and approved. If ZP_COSUPPL is set to Y, the supplement of the highest approved change order is shown. In any case, only the data of the latest change order is available.

The Origin field shows the origin for the agreement.

The Supplier field shows the name of the supplier assigned to this agreement.

You can click the Inspection button to open the P.70.53 Inspection Application Infos screen. For more information, see Inspection Application Info.

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

Click the Create SG button to create an item shipment group for the selected agreement. This button is only enabled if no shipment group exists. A shipment group contains item shipments with the same promised ship date (or current/revised promised ship date if already set), routing method, incoterm, delivery place, and carrier (MOC) from an order. Before shipment groups are actually created, the CIP m_pck_exp_custom.check_create_sg is executed. Only if this CIP does not raise an error are the shipment groups created.

The software:

  • checks the various values of the grouping criteria on the item shipments of the order

  • generates a corresponding number of shipment groups

  • and assigns item shipments to the generated shipment groups.

The name for every shipment group is generated by concatenating the name of the order with a sequential number. You can change this shipment group name.

Click the Delete SG button to delete the shipment groups that were created by the software. A deletion of these shipment groups is only possible if no manual shipment group exists. Before the shipment groups are actually deleted, the CIP m_pck_exp_custom.check_delete_sg is executed. Only if this CIP does not raise an error are the shipment groups deleted.

Shipment Groups

In the second (Shipment Groups) block, the shipment groups assigned to the selected agreement are maintained. A shipment group contains a number of item shipments with the same promised ship date (or current/revised promise ship date if already set), routing method, incoterm, delivery place, and carrier (MOC). You can update any field on the shipment groups. For example, updating the names of the shipment groups allows you to replace the generated names with your own.

The project default ZP_HIDE_MT controls which shipment groups of the order are visible. If the project default is set to Y, the shipment groups that contain only master tags without any detail tags are hidden, and the Item Shipments block shows all item shipments of the selected shipment group except master tags (normal item shipments and detail tags). If the project default is set to N, all shipment groups of the order are visible, and the Item Shipments block shows all item shipments including master tags.

The Shipment Group field displays the code that uniquely identifies this shipment group.

The Manual indicator shows whether this shipment group was created manually.

The ISH Counter field shows how many item shipments belong to the selected shipment group.

The Curr/Rev Prom Ship Date field shows the current/revised promised ship date for the items of this group.

The Delv. Desig. field displays the name of the delivery designation.

The Routing Method field displays the name of the routing method.

The Incoterm field shows the name of the incoterm.

The Delivery Place field shows the delivery place of the material.

The Carrier Name field shows the name of the carrier.

The actual date to deliver all items in this group is displayed in the PO Actual field.

The promised date, when all items in this group can be inspected, is displayed in the Prom Inspect field.

The final date, when all items in this group will be inspected, is displayed in the Final Inspect field.

The date when all items of this group are predicted to be ready for shipment is displayed in the Ready Predicted field.

The date when all items in this group are actually ready to be shipped from the vendor is displayed in the Ready Actual field.

The date when all items of this group are predicted to be shipped is displayed in the Pred Ship field.

The actual date the supplier shipped all items of this group is displayed in the Actual Ship field.

The actual date for arrival on site is displayed in the Actual On Site field.

The date predicted (estimated) for the arrival on site is displayed in the Pred On Site field. If the project default ZP_EXPDATE is set to Y, this field is filled with the promised ship date plus the sum of transit days of the routing method when an item shipment is created. Furthermore, this date is recalculated automatically if one of the following fields is modified:

  • Curr/Rev Prom Ship

  • Pred Ship

  • Actual Ship

  • Routing Method

  • Carrier Name

If a carrier name was entered, the predicted on site date is calculated as the ATA (actual time of arrival) date of the carrier or the ETA (estimated time of arrival) date, if the ATA date is not available, plus the sum of transit days. The transit days are taken from the entries within the schedule of the routing method, which are located between the entries with date type 'Traffic Arrival' (which is included) and 'Arrival On Site' (which is not included). If the ETA date of the carrier is also empty or if the routing method schedule does not contain an entry of date type 'Traffic Arrival', the carrier is ignored. Instead, the software looks for the actual ship date, predicted ship date, revised promised ship date, or promised ship date (in this order, until a date is found) and adds the sum of transit days of the routing method to calculate the predicted on site date. This latter variant also applies in cases where no carrier name was entered. If the project default ZP_EXPDATE is set to N, this date remains empty when an item shipment is created and is not automatically recalculated if one of the above mentioned fields is modified.

The date when the most components (or quantity) of the line items is ordered is displayed in the Maj Matl Order field.

The date when the most components (or quantity) of the line item arrived at the supplier is displayed in the Maj Matl Recv field.

The day the supplier started the fabrication of all items of this group is displayed in the Actual Fab Start field.

The Comp % field shows the percentage of completion for fabrication.

The date when 50% of the fabrication is actually completed is displayed in the 50 % Comp field.

The Prom Fab Comp field shows the current promised fabrication complete date of the supplier.

The Actual Fab Comp field shows the actual date the fabrication has been completed by the supplier.

Item Shipments

In the third (Item Shipments) block, you can see all item shipments of the order that are assigned to the selected shipment group. The project default ZP_HIDE_MT controls whether master tags are hidden (ZP_HIDE_MT is set to Y) or shown (ZP_HIDE_MT is set to N) in this block.

You can update fields like Rev Prom Ship, Routing Method, and so forth. The software then checks the other dates of the shipment group and if applicable, assigns the item shipment to a different shipment group or even creates a new one. If an additional shipment group is created, the values of the following fields are copied over to the new shipment group:

  • Currency

  • Invoice Value

  • Total Net Weight

  • Total Gross Weight

  • Total Volume

These fields are maintained and displayed on the P.70.61 Logistics Overview screen.

A new shipment group is created for new item shipments if a matching shipment group exists (because of the group-by criteria) but any of the fields mentioned above are already filled.

The Pos field shows the line item number on the order, and the Sub field shows the order sub line item number

The IS Pos field displays the sequence number identifying the related shipments of an order line item. The IS Sub field shows an additional sequence number identifying split shipments of an order.

The Prom Ship Date field displays the promised shipping date (first promise date by the supplier). If the project default ZP_EXPDATE is set to N, you can update this date.

The Curr/Rev Prom Ship field displays the current promised shipping date for the item. When you set this date on a detail tag. the latest date of all detail tags is copied over to the master tag. For example, if the current promised ship dates of the detail tags are 22-MAR-2001, 04-JUN-2001, and 02-AUG-2001, 02-AUG-2001 will be copied to the master tag. This copy operation can result in the re-assignment of the master tag to a different shipment group.

The Delv. Desig. field displays the name of the delivery designation, the Routing Method field the name of the routing method, and the Incoterm field the name of the incoterm. To revise the incoterm, enter a new value in the Rev Incoterm field.

The Delivery Place field shows the delivery place of the material. To revise the delivery place, enter the new value in the Revised Delivery Place field.

The name of the carrier is displayed in the Carrier Name field.

The actual date to deliver this item is displayed in the PO Actual field.

The promised date when this item can be inspected is displayed in the Prom Inspect field.

The final date when this item will be inspected is displayed in the Final Inspect field.

The date when this item is predicted to be ready for shipment is displayed in the Ready Predicted field.

The date when this item is actually ready to be shipped from the vendor is displayed in the Ready Actual field.

The date when this item is predicted to be shipped is displayed in the Pred Ship field.

The actual date the supplier shipped this item is displayed in the Actual Ship field.

The actual date this item actually arrived on site is displayed in the Actual On Site field.

The date predicted (estimated) for the arrival on site is displayed in the Pred On Site field. If the project default ZP_EXPDATE is set to Y, this field is filled with the promised ship date plus the sum of transit days of the routing method when an item shipment is created. Furthermore, it is recalculated automatically if one of the following fields is modified:

  • Curr/Rev Prom Ship

  • Pred Ship

  • Actual Ship

  • Routing Method

  • Carrier Name

If a carrier name was entered, the predicted on site date is calculated as the ATA (actual time of arrival) date of the carrier or the ETA (estimated time of arrival) date, and if the ATA date is not available, plus the sum of transit days. The transit days are taken from the entries within the schedule of the routing method, which are located between the entries with date type 'Traffic Arrival' (which is included) and 'Arrival On Site' (which is not included). If the ETA date of the carrier is also empty or if the routing method schedule does not contain an entry of date type 'Traffic Arrival', the carrier is ignored. Instead, the software looks for the actual ship date, predicted ship date, revised promised ship date, or promised ship date (in this order, until a date is found) and adds the sum of transit days of the routing method to calculate the predicted on site date. This latter variant also applies in cases where no carrier name was entered. If the project default ZP_EXPDATE is set to N, this date remains empty when an item shipment is created and is not automatically recalculated if one of the above mentioned fields is modified.

The Req On Site field displays the date when the arrival on site is required by contract or schedule.

The date when the most components (or quantity) of the line item is ordered is displayed in the Maj Matl Order field.

The date when the most components (or quantity) of the line item arrived at the supplier is displayed in the Maj Matl Recv field.

The day the supplier started the fabrication of this item is displayed in the Actual Fab Start field.

The Comp % field shows the percentage of completion for fabrication.

The date when 50% of the fabrication is actually completed is displayed in the 50 % Comp field.

The Prom Fab Comp field shows the current promised fabrication complete date of the supplier.

The Actual Fab Comp field shows the actual date the fabrication has been completed by the supplier.

The Item Ship Weight field displays the weight of this shipment position/sub position, with the weight unit in the Weight Unit field.

The Item Ship Volume field displays the volume of this shipment position/sub position with the volume unit in the Volume Unit field.

The x, y, and z dimensions of the item are displayed in the Dimension field.

The Fab Location field shows the fabrication location of this item. The Fab Ctrl Number field shows the control number of the fabrication.

The Item Ship Quantity field shows the quantity of the selected item shipment, with the quantity unit in the Qty Unit field. The tag number of the item shipment is displayed in the Tag Number field. If the item rule of the ident is SWT, TFM, TOM, or TWM, you can double-click in this field to open the S.80.25 Tag Description and History screen showing the Tag Description and Tag History tabs. If the item type is SWT and if the tag number and the commodity code are identical and ATTR_NUM3 contains the ident, only the Tag History tab is shown. For other item rules like SOT, only the Tag History tab is available. If the item rule of the ident is TAB, the Ident Layout and Tag History tabs of S.80.25 are displayed. You can only open S.80.25 with a double-click if the tag number is not like '---' and not like 'UNTAGGED'.

For idents with item rule TAB, TFM, TOM, or TWM, you can update the tag number. When doing so, you are asked whether you want to use the S.80.24 Rename Tagged Items screen for this change or if you want to update the tag number immediately. S.80.24 allows you to check all documents in which the tag number is used prior to changing it. Moreover, you can update only the commodity code, only the tag number, or both commodity code and tag number in the case of item rules TFM, TOM, and TWM. For idents of rule TAB, you can only update the tag number itself. If you decide to immediately update, both the commodity code and the tag number are updated for item rules TFM, TOM, and TWM. For idents of rule TAB, only the tag number is changed.

The Ident Code field shows the ident code for the ident placed on the item shipment. The background color of this field is set to red if the attribute defined by project default ZP_DEVATTR has been assigned either to the corresponding order line item or to the item shipment itself.

The Ident Short Description field shows the ident short description that is derived by executing the CIP procedure m_pck_std_custom.ident_desc.

You can click the Split Tag button to create splits for order line items or item shipments. For more information, see Split Tag. You cannot create a split if additional item shipments have already been created using the New record button (not to be confused with detail tags). A tagged item cannot be split if the order to which an item shipment belongs has been created for the corporate or a FIM warehouse.

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.

If an order line item or item shipment matches these criteria, the button is only active when the focus is in this block.

The project default ZP_HIDE_MT enables you to hide the master tags (ZP_HIDE_MT is set to Y) or show the master tags (ZP_HIDE_MT is set to N which is the default). The detail tags are shown in any case. If ZP_HIDE_MT is set to Y and a detail tag is selected, the label of the button changes to Split Master Tag, You can only create one detail tag at a time. So if you need to create three detail tags, you must click the button three times. Only when splitting a tag for the first time are the two splits created directly.

Depending on where the split occurs, either the Pos and Sub fields (split on the order line item level) or the Pos, Sub, IS Pos, and IS Sub fields (split on the item shipment level) are displayed in a blue color. If you update the values of the master tag, you can decide whether these modified values are copied over to the detail tags or not. The following fields are not populated with the master tag values:

  • Curr/Rev Prom Ship

  • Pred Ship

  • Actual Ship

  • Item Ship Weight

  • Item Ship Volume

  • Dimensions

  • Delivery Designation

  • Routing Method

These fields are excluded because it makes no sense to populate them (weight, volume, dimensions), or the validations that must be performed are too complex (delivery designation and routing method must match), or the automatic calculation of further date fields is triggered, taking into account the transit days of the routing methods that can differ for each detail tag (Curr/Rev Prom Ship, Pred Ship, Actual Ship). 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.

The population mechanism only works in this third block. Changes are not populated when applied in the second (Shipment Groups) block.

When one of the following dates for the last detail tag (that is, there are no more detail tags for which this date is empty) is set, 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.