You can double-click in the Order Number field or use the fastcall on the P.70.61 Logistics Overview screen to open the P.70.62 Logistics Details screen. Alternatively, you can open the screen from the menu tree.
This screen shows you all the details of interest for logistics purposes. You can query for all item shipments that belong to approved purchase orders or notices of commitment. Some detail information can be updated. Fields that can be modified are easily recognized by their white background color. Please see the description of the individual fields for cases of restricted update.
To a certain degree, you can configure the appearance of the P.70.62 screen on the P.10.74 Configure Logistics Screens screen. Here you can:
-
define which fields you want to see
-
define the order in which these fields are to be displayed
-
define the prompt (or label) for the displayed fields
-
define the field width
-
select up to 100 attributes attached on the item shipment level
-
select up to 10 CIP functions for calculations or displays not provided by the standard fields
-
determine for some fields whether they are to appear in the non-scrollable or in the scrollable area of the screen.
This configuration can be made per project and user. For more information, see Configure Logistics Screens.
Your view on orders and therefore on their item shipments can be restricted by sections; for more information, see Sections.
If you call this screen from P.70.61, all item shipments of the selected order are queried automatically. If shipment groups have been created for the order, only the item shipments of the selected shipment group are displayed. But you can run a new query that allows you to query for the item shipments of any other order or shipment group as well.
If project default ZP_HIDE_MT is set to Y, master tags are hidden. If ZP_HIDE_MT is set to N, master tags are shown. The detail tags are shown in any case.
With the project default ZP_CLR_DSC, you can control how the description of the detail tag is generated. For more information, see Split Tag.
All item shipments of all approved orders of type 'PO' (purchase order) are available. The item shipments of approved orders of type 'NC' (notice of commitment, NOC) are available as long as no order of type 'PO' has been created from this NOC and been approved.
The Ordered by field at the top of the screen shows by which fields the displayed records are sorted. By default, the data is ordered by order type, order number, supplement, pos, sub, IS pos, and IS sub. To change the order criteria, you must click the Order By ... button at the bottom of the screen.
The Order Number field shows the number/name of the purchase order or notice of commitment. The background color of this field depends on the shipping status of the item shipment. The shipping status is determined by the CIP function m_pck_logistic_custom.get_shipping_status. The only argument of this CIP is the primary key of on item shipment, that is, the item_ship_id column. The function returns a number value. In a standard installation, the different shipping statuses are defined as follows:
-
0 – The order number not highlighted. The material is already shipped. The ATD date of the assigned means of conveyance is in the past.
-
1 – The order number is highlighted with a red background color. The material is not shipped so far. No means of conveyance is assigned to this item shipment.
-
2 - The order number is highlighted with a cyan background color. The material is next to be shipped. The item shipment is assigned to a means of conveyance that has a future ETD date.
-
9 - The order number is highlighted with a magenta background color . A means of conveyance is assigned to the item shipment but the ETD date lies in the past and the ATD date is not set or is a future date.
-
In all other cases, the background color is set to magenta.
If you double-click in the Order Number field, all item shipments of the selected order are shown. If you have called this screen from P.70.61, you will only see the item shipments of the combination order - shipment group that you have selected on P.70.61.
The Suppl field shows the supplement of the selected order or notice of commitment.
If change orders have already been created and approved for the order, the supplement of the latest approved change order is shown in the Latest Suppl field.
If change orders have already been created and approved for the order, the date of the approval of the latest change order is shown in the CO Date field here.
The Pos field displays the order line item number, the Sub field the order sub line item number, the IS Pos field the item shipment line item number, and the IS Sub field the item shipment sub line item number. For item shipments created by the buyer, the position number is increased; for item shipments created by the expediter, the position number is kept and the sub line item number is increased. Item shipments created by the buyer have a sub line item number of 1.
The Commodity Code field displays the the commodity code of the ident placed on this item shipment, and the Ident Code field displays the ident code of the ident. If the attribute assigned to project default ZP_DEVATTR is assigned either to the corresponding order line item or to the item shipment, the Ident Code field is shown with a red background color, which indicates a changed order description (ident short description).
The Tag Number field displays the tag number of the item shipment. When you double-click in the Tag Number field, the S.80.25 Tag Description and History screen opens with the Tag Description and Tag History tabs displayed in case the item rule of the ident is SWT, TFM, TOM, or TWM. For other item rules, only the Tag History tab is visible. If the item rule of the ident is TAB, S.80.25 shows the Ident Layout and Tag History tabs. The double-click is only possible if the tag number is not like '---' and not like 'UNTAGGED'.
For idents with rules TAB, TFM, TOM, and TWM, it is also possible to 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. The S.80.24 screen allows you to check all documents in which the tag number is used before changing it. Moreover, you have the choice of updating only the commodity code, only the tag number, or both commodity code and tag number in the case of item rule TFM, TOM, and TWM. For idents of rule TAB, you can only update the tag number itself. If you decide in favor of an immediate update, both commodity code and tag number are updated for item rules TFM, TOM, and TWM. For idents of rule TAB, only the tag number is changed. Any changes of the tag number and/or commodity code must be committed.
The history of all changes of the tag number is shown on S.80.25 Tag History.
After a tag number has been changed, the tag number is marked to inform you of the situation. If a tag number is changed, you are asked to acknowledge after a double-click on this item and opening S.80.25. If you answer with Yes, the tag number is no longer marked.
The Size 1 to 5 fields display the sizes (inputs) one through five of the selected ident.
The Item Shipment Quantity field displays the quantity of the item shipment. When a new item shipment is inserted, the quantity is automatically filled with the remaining order line item quantity, but you can overwrite this value if necessary.
In the case of an order for the corporate or FIM warehouses, quantity changes in
expediting have no effect on the quantities available in these warehouses.
If you update the quantity of a detail tag created on the order line item level, you are asked whether you want to update the order line item quantity as well. This feature allows you to update the order line item quantity of newly created detail tags; that is, the detail tags are created by expediting after the approval of the order. For more information about splitting tagged items, see Split Tag.
The Quantity Unit field shows the quantity unit of the item shipment. You can only update the quantity unit of detail tags.
The PO Actual field shows the actual contract date or delivery date of the item shipment.
The Last Info Date field shows the last date on which any information has been entered for the item shipment. This date is automatically filled with the system date when the item shipment is created. Afterwards, you can change the date.
The Prom Inspect field shows the promised date when the item can be inspected.
The Inspectable check box indicates whether this item shipment is to be inspected or not. You can only enter a release/waiver date or an NCR remark if this check box is selected. When you clear this indicator, all inspection information data is cleared as well. That is, the release/waiver date, the NCR date, the NCR release date, and the NCR remarks are cleared. When you update this check box, you are asked whether you want the new setting to be copied over to all item shipments of the order if project default ZP_GLB_UPD is set to Y. If you insert a new line, the Inspectable indicator is set automatically corresponding to the project default ZP_INSPDEF. But you can overwrite this default if necessary.
The Release/Waiver Date field displays the date of either release note or waiver. You can only modify this date if the item is to be inspected, that is the Inspectable check box is selected on the P.70.55 PO Inspection Releases/NCR screen. When you update this field, you are asked whether you want the new date to be copied over to all inspectable item shipments of the order if project default ZP_GLB_UPD is set to Y. If project default ZP_UPD_FID is set to Y, you are asked whether you want the new date to be copied over as the final inspection date for the current item shipment when you update this field.
In the NCR Remarks field, you can enter remarks on the inspection of the item shipment. You can only enter remarks if the item is to be inspected, that is, the Inspectable check box is selected on the P.70.55 PO Inspection Releases/NCR screen.
The Incoterm field shows the name of the incoterm. In the Rev Incoterm field, you can enter a revision of the incoterm.
The Delivery Place field shows the delivery place of the material. In the Revised Delivery Place field, you can enter a revised delivery place.
The Delivery Designation field shows the name of the delivery designation. Delivery designations are maintained on the A.10.39 Delivery Designations screen. Changing the delivery designation implies that the value of the routing method must be changed as well. Therefore, the routing method is filled automatically with the default defined on A.10.39 when another delivery designation is selected. If no default is defined, the routing method is cleared. But you can select any other routing method of this delivery designation.
The Routing Method field shows the name of the routing method. Routing methods are defined on the P.10.53 Routing Methods screen. You can only enter routing methods with a delivery designation equal to the one entered in the Delivery Designation field. At the time item shipments are created, the routing method is 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, this field remains empty. If you modify the routing method, the predicted on site date is re-calculated if the project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N).
The Curr/Rev Prom Ship field displays the current promise of the supplier to ship that item. As long as this date is not changed by the expediter, it has the same value as the Prom Ship date. Modifying this field leads to a recalculation of the predicted on site date if project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N). When setting 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-2012, 04-JUN-2012, and 02-AUG-2012, the 02-AUG-2012 date is copied over to the master tag.
The Carrier Name field shows the name of the carrier. You can only enter carriers that are pre-defined on the P.80.41 Means of Conveyance or the P.80.51 Traffic Fast screens. A list of values containing all valid carriers is available. If you modify the carrier name, the predicted on site date is re-calculated if project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N). You can double-click in this field to open the P.80.42 Means of Conveyance (Multi) screen.
The Voy or Flt Num field displays the number of the voyage or flight.
The estimated time (date) of departure is displayed in the ETD Date field.
The actual time (date) of departure is displayed in the ATD Date field.
The date of the bill of lading (B/L) or the air way bill (AWB) is displayed in the B/L (AWB) Date field.
The estimated time (date) of arrival is displayed in the ETA Date field. If you modify this date, the predicted on site date is re-calculated if project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N).
The ATA Date field displays the actual time (date) of arrival. If you modify this date, the predicted on site date is re-calculated if project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N).
The Loading Point field shows the name of the loading point, and the Unloading Point field shows the name of the unloading point.
The first name of the vessel, plane, truck, and so forth is displayed in the Name 1 field, and the second name in the Name 2 field.
The Pred Traffic Arrival field shows the predicted traffic arrival date.
The Actual Traffic Arrival field shows the actual traffic arrival date.
The Pred On Site field displays the date predicted (estimated) for the arrival on site.
If the project default ZP_EXPDATE is set to Y and basic expediting is used (ZP_NEW_EXP is set to N), this date is re-calculated automatically if one of the following fields is modified on this screen:
-
Curr/Rev Prom Ship
-
Routing Method
-
Carrier Name
-
ETA Date (if carrier name has been specified)
-
ATA Date (if carrier name has been specified)
If a carrier name has been provided, the predicted on site date of the item shipment 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 also not set, 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 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.
The Actual On Site field displays the actual date for arrival on site.
The Type field shows the type of the order. This type can be PO for purchase orders or NC for notices of commitment. If ZP_CO_TYPE is set to Y (the default is N), the type displayed is CO if at least one approved change order exists for the current purchase order/notice of commitment.
The Origin field shows the name of the origin of the order.
The Section field shows the name of the section. Your view on orders and therefore on their item shipments can be restricted by sections; for more information, see Sections.
The Shipment Group field displays the name of the shipment group. You can double-click in this field to open the P.70.31 Shipment Groups screen.
You can enter an invoice number in the Invoice Number field.
Select the expediter assigned to the order or notice of commitment from the LOV in the Expediter field. All users with the EXPEDITER privilege assigned are available for selection. Although you are looking at item shipments, the assignment of the expediter affects all item shipments of the order because you can only assign an expediter on the order header level, not on the item shipment level.
The Supplier Name field shows the name of the supplier's company.
In the Manufacturing Company field, you can select the name of the manufacturer's company from the LOV. An update of this field affects all item shipments of the order because the manufacturer's company is assigned on the order header level, not on the item shipment level.
The date the order or notice of commitment was approved is displayed in the Approved field.
You can enter any comment in the Comment field.
Attributes are displayed as configured on the P.10.74 Configure Logistics Screens screen and attached to the item shipment, or, if not found there, to the order. An attribute value is not displayed if the attribute has been assigned based on an attribute set and if the display indicator has not been set for expediting and orders respectively on the A.50.04 Attribute Sets screen. If the attribute selected on P.10.74 has not been assigned to the item shipment nor to the order, this field remains empty but can be modified (if you enter a value, this attribute is assigned to the item shipment).
You can update the attribute value if the attribute has been assigned to the item shipment or the order and is not locked, that is, the kind of the attribute is 'Other'. These updates are subject to the same restrictions and limitations as on A.50.21. In other words, valid values that have been entered on A.50.01 Attributes are taken into account in the same way as the width of a field has to be respected. If so far the attribute is only assigned to the order, it will be assigned to the item shipment if you update the attribute value. The value of the attribute on the order level remains unchanged.
If the update of an attribute is restricted because it was originally part of an attribute set and the Update allowed for expediting indicator is not selected on A.50.04 Attribute Sets, you cannot modify the attribute value.
The CIP Fields are displayed as configured on the P.10.74 Configure Logistics Screens screen. The fields display the return value of the function entered for this CIP field on P.10.74.
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 as configured on P.10.74 Configure Logistics Screens. 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 six 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.
The order by criteria are saved when closing the screen for every user and are applied
when opening the screen again.
If you want to initialize the order by criteria, click the Order By button to open the LOV box and click the Cancel button. The records are then displayed in a random order. Then, close the screen and re-open it to display the data ordered by the default criteria (order type, order number, supplement, pos, sub, IS pos, and IS sub).
Select the name of the CIP procedure you want to execute from the LOV in the CIP Name field. The LOV contains all procedures from package M_PCK_LOGISTIC_CUSTOM, the name of which starts with 'P7062_'. Only those procedures that have two parameters, both of type NUMBER can be selected. The first input parameter is the primary key of table m_po_headers (poh_id), and the second is the primary key of table m_shipment_groups (sg_id).
Click the Execute CIP button to execute the CIP procedure entered in the CIP Name field. Before the CIP actually starts, you are asked whether you want to execute the CIP only for the current record or for all queried records.
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).
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 if 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/created on the item shipment level.
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 two splits created directly.
If project default ZP_HIDE_MT is set to Y, master tags are hidden. If ZP_HIDE_MT is set to N (default), master tags are shown. 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 is set to Y and the cursor is placed 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.
With the project default ZP_CLR_DSC, you can control how the descriptions of the detail tags are generated. If ZP_CLR_DSC is set to Y, the descriptions of the new detail tags are generated differently. The first detail tag gets exactly the same description as the master tag, and all following detail tags get an empty description (-).
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. On this screen, this feature is available for the following fields:
-
PO Actual
-
Prom Inspect
-
Release/Waiver Date
-
Pred On Site
-
Actual On Site
The population of values from a master tag to its detail tags works for splits created on the order line item level and splits created on the item shipment level.
The latest date of all detail tags is copied over to the master tag 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 not set):
-
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 next-to-last detail tag, the remaining detail tag is also deleted. Thus, it is prevented that a master tag with only one detail tag exists. The sub position of the master is reset to 1.