On the P.60.01 Tagged Items Planning screen, you can create and maintain planning items for which you want to have tracking capability by milestone. Planning work can be performed on items that have not yet been created by an MTO or by manual entry in the requisition module. If the project default ZP_MS_CRT is set to Y and if the system later finds these items (when creating a requisition manually on R.30.01 or by MTO job), a link from the planning item to the actual item it represents is created. Regardless of how a link is found, recognition or creation of a link is always based on the unique identifier – the tag number. If the tag numbers are not unique in a project, this function does not work. The PO link for planning items is created as soon as a PO is created that contains this tag number.
If you start the planning of tagged items that are already present in Smart Materials, you can select the tag number from the LOV in the Tag Number field when you create a new planning item.
On the P.60.01 screen, you create and maintain the planning setup for specific tagged items.
This screen is a core workflow screen. For more information, see Core Workflow Screens.
The fields in the first (Planned Tagged Items) block uniquely identify your planning item throughout the whole requisitioning and procurement workflow. Furthermore, if you enter planning items here, you must choose and assign the milestone set by which the item is to be tracked.
The Tag Number field shows the tag number of the item to be tracked. When you create a new planning item, enter the tag number manually or select it from the LOV in this field. The LOV displays all tagged items (TWM) available on bills of material (BOM) as well as on manual requisitions.
The Link to Req field indicates if this planning item is linked to a requisition. The displayed status can be:
-
No Relation - The tag number cannot be found on any requisition line item.
-
Linked - A link exists.
The Link to Agreement field indicates if this planning item is linked to an agreement. The displayed status can be:
-
No Relation - The tag number cannot be found on any agreement line item.
-
Linked - A link exists.
As soon as the given tag number appears on an agreement line item, 'Linked' will be displayed in this field.
To assign a planning group to this planning item select a pre-defined group from the LOV in the Planning Group field. You can double-click in this field to open the P.10.64 Planning Groups screen where planning groups are defined. New planning groups can either be defined on the P.10.64 screen or here on this screen, provided you have the rights to create new records on P.10.64. If you enter a name that does not match with P.10.64 Planning Groups and you have the right to insert new values in this screen, a box appears asking you if you want this new planning group to be created. Click Yes to continue or No to cancel. If you do not have the right for inserting new values, an appropriate message comes up. In this case, you can only select a pre-defined planning group from the LOV.
Enter the value for the first/second budget in the Labor Budget 1/2 field.
For every tagged item of the specified planning group the weight factor 1/2 for all finished milestones is summed up and the sum is then multiplied with budget 1/2 of the requisition or tagged item. After that, the results of all requisitions and tagged items are again summed up. Finally, this sum is set in relation to the budget 1/2 of this planning group and the result displayed in the Progress 1/2 field.
Select a pre-defined milestone set from the LOV in the Milestone Set field. You can double-click in this field to open the P.10.62 Milestone Sets screen.
You can refresh the milestone set assigned to the planning item via the shortcut
menu in the Tag Number field.
Thus, the overall milestone plan can be adjusted based on changes that have been made in the corresponding milestone set on P.10.62.
In the ROS Date field, select the date when the material is required on site from the LOV.
-
There is no further downstream functionality behind this field.
-
In the case of the automatic creation of data due to the setting of project default ZP_MS_CRT, this information is not copied over from the requisition line item.
In the Client Req Number field, you can enter the name (number) of the client's associated requisition, and in the Client Agreement Number field the name (number) of the client's associated agreement. You can enter any comment in the Comment field.
In the Account Code field, you can assign an account code to this planning item, using the LOV in this field. If you enter an account code that does not match with A.10.30 Account Codes and you have the right to insert new values on this screen, a box appears asking you if you want this new account code to be created. Click Yes to continue or No to cancel. If you do not have the right to insert new values, an appropriate message comes up. In this case, you can only select a pre-defined account code from the LOV. You can double-click in this field to open the A.10.30 Account Codes screen.
You can click the Attributes button to open the A.50.21 Attached Attributes screen where you can view and maintain the attributes assigned to the selected planned tagged item. For more information, see Attached Attributes.
If you want the forecasted dates to be calculated for all planned tagged items of the login project, you click the Calc All Forecasted button.
You cannot restrict the number of calculated tagged items by running a restricted
query. Depending on the number of planned tagged items and milestones, this process
may take some time.