On the P.60.03 Requisitions Planning screen, you can create and maintain requisition planning items (also called planned requisitions) for which you want to have tracking by milestone. Furthermore, this screen allows you to perform all the tasks that are related to the tracking of milestone dates.
You can do this planning work even if those requisitions have not been created yet by MTO or by manual entry in the requisition module. Later on, when the requisitions to be planned and tracked are created (by MTO or manually) and if the project default ZP_MS_CRT is set to Y, a link from the planning item to the actual requisition it represents will be established automatically.
Regardless of how this option is set, recognition of engineering requisitions for creation of a link is always done by the requisition code and the origin. The PO link for planning items will be created as soon as the PO has been created.
If you start the planning requisitions that are already present in Smart Materials, you can select the requisition number from the LOV in the Engineering Requisition field when you create a new planning item.
On the P.60.03 screen, you create and maintain the planning setup for specific requisitions.
This screen is a core workflow screen. For more information, see Core Workflow Screens.
The information specified in the first (Planned Requisitions) block will be used to create the link to the requisition, which is represented by this requisition planning item (planned requisition). Furthermore, if you create new planning items here, you must choose and assign the milestone set by which the requisition is to be tracked.
If you enter planned requisitions for which the engineering requisition does not exist yet in the requisitioning module, enter the expected requisition code in the Engineering Requisition field and the requisition information in the following fields. If the requisition has been created and the link cannot be found because the requisition code is different than was expected, you can update these fields later on. If the requisition was already created, you can select the requisition number from the LOV in this field.
You can select Supplement planning from the shortcut menu in the Engineering Requisition field to open Window 11, where you can add and view requisition supplements. Supplement planning can be enabled by setting project default ZP_MS_SUPP to Y. If the project default is set to E, supplement planning is enforced on P.60.03, which means that at least one supplement plan must exist for each planned requisition.
The Engineering Requisition field shows the requisition with its supplement in the Suppl field, and the origin is shown in the Origin field.
The value in the Scope field determines the scope of planning covered by this planned requisition. You can use this field to limit the planning and, subsequently, the tracking of milestones to focus on either the inquiry-only requisition or the requisition for purchase.
If you set the scope to Inquiry-only, the software tries to link the planned requisition with a matching inquiry-only engineering requisition. Even if requisitions for purchase originate from that inquiry-only requisition at a later point in time, these requisitions for purchase will not link with the Inquiry-only scoped planned requisition. This setting enables dedicated planning of the inquiry cycle. Consequently, an Inquiry-only scoped planned requisition will never be linked with an agreement.
If you set the scope to Purchase-only, the software tries to link the planned requisition with a matching engineering requisition for purchase. An inquiry-only engineering requisition from which the matching requisition for purchase might have originated from is ignored. Instead, subsequent agreements based on the linked requisition for purchase are also linked with this Purchase-only scoped planned requisition. This setting enables dedicated planning of the agreement cycle.
The default scope value is Unrestricted, which does not impose any restriction on planning and tracking. When a planned requisition is created with Unrestricted scope, the attempt to link the planned requisition with a matching engineering requisition favors an inquiry-only engineering requisition over a purchase requisition (if both are available and match in terms of requisition number and origin). Any purchase requisition that has originated from the original inquiry-only requisition is also linked with this planned requisition, so that the detail milestones provide a comprehensive overview of all the objects that are related to the original inquiry-only engineering requisition.
You can create planned requisitions of different scopes but with the same requisition number and origin at the same time.
Select a date from the LOV in the ROS Date field. The ROS Date field is editable as long as no engineering requisition supplement is available. If a supplement exists for the requisition, the value in the ROS Date field cannot be changed and the minimum ROS date of all requisition line items that belong to this engineering requisition supplement appears.
Enter a value in the Lead Time field. The value in the Lead Time field is interpreted as weeks by default. This type can be changed at the M_PCK_MS_CUSTOM.CALC_PLANNED_ISSUE_DATE CIP, for example, if you want to enter number of days or months. The Planned Issue date is calculated automatically as the ROS Date - Lead Time, and this date cannot be changed.
If you copy an existing supplement plan using the Duplicate Record Above function (called using F4 key or from the Edit menu), the attributes that have been attached to the original supplement plan are also copied. The copied milestone plan contains only the milestone labels that are found in the milestone plan of the original supplement.
Click Close to close Window 11 to return to the main screen.
The setting of project default ZX_ORIGIN is used as the default value for the Origin field. You can change this value by selecting the origin of the requisition from the LOV in the Origin field. You can double-click in this field to open the A.10.33 Origins screen.
Select the type of the requisition from the drop-down list in the Requisition Type field. The available types are Order and Subcontract. The requisition type influences which agreement type is available for the requisition later on.
Select the type of the agreement from the LOV in the Agreement Type field. The available agreement types depend on the purchase indicator of the requisition, the requisition type, and the setting of project default ZP_CONSPCI. If the requisition can only be used for inquiries and ZP_CONSPCI is set to Y (default), only agreement type Blanket Order is available for requisition type Order and only agreement type Master Agreement is available for requisition type Subcontract. If the requisition can be used for purchasing or if project default ZP_CONSPCI is set to N, more options are available. If the requisition type is set to Order, you can select one of the following types:
Blanket Order (BO)
Purchase Order (PO)
Notice of Commitment (NOC)
Notice to Proceed (NTP)
Blanket Order Release (BOR)
Field Order (FO)
Rental Order (RO)
If the requisition type is set to Subcontract, the following types are available:
Master Agreement (MA)
Notice of Commitment (NOC)
Notice to Proceed (NTP)
Service Agreement (SA)
Work Order (WO)
When a BO is assigned to a requisition, a PO (= BOR) based on this BO can be created; when an MA is assigned to a requisition, a WO based on this MA can be created. A NOC can be converted into a PO.
Enter the planned requisition descriptions in the Short Desc and Description fields.
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 planned requisition using the shortcut menu in the Engineering Requisition 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. You can only work with this field if the requisition type is Order. If you select a non-working day as the ROS date, a corresponding warning appears; you can save the date nevertheless.
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.
In the Client Req Number field, you can enter the name (number) of the client's associated requisition.
The Link to Req field indicates if this requisition planning is linked to a requisition. The displayed status can be:
No Relation - The given combination of requisition number and origin does not exist in the requisition module within the current project.
Linked - A link exists.
The Higher Suppl check box is selected if supplement planning is enabled, that is, if project default ZP_MS_SUPP is set to Y (supplement planning is optional) or E (supplement planning is mandatory and thus enforced by the software). If this check box is selected, supplement planning is lagging behind existing engineering requisition supplements that are linked to the currently selected planned requisition. If the check box is not selected, the meaning depends on the setting of ZP_MS_SUPP. If the project default is set to E, planning is up-to-date. However, if the project default is set to Y, the check box not being selected can also be caused by the fact that the currently selected planned requisition has not been provided with supplement plans at all (supplement planning is optional in this scenario). So if supplement planning is enabled, this check box allows for easily retrieving those planned requisitions from the database that are outdated by their engineering requisition counterparts.
The Link to Agreement field indicates if this requisition planning is linked to an agreement. The displayed status can be:
Linked - A link exists.
As soon as an agreement has been created for the engineering requisition linked with this planning item, Linked will be displayed in this field.
When project default ZP_MS_DUP is set to Y, agreement-specific requisition planning and milestone tracking is enabled, which means whenever an agreement is linked to a planned requisition, the software ensures that this agreement is exclusively associated with that planned requisition. If another agreement appears to be linked to the planned requisition, the planned requisition is duplicated for exclusive linking with the new agreement. The linked agreement is displayed in the Agreement Number field.
To assign a planning group to this requisition planning, 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 requisition and tag 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.
You can enter any comment in the Comment field. For example, you can use it to enter the description of the package contained in the requisition, like medium vessels, water pumps, cs piping, and so forth.
In the Client Agreement Number field, enter the name (number) of the client's associated agreement.
Select the pricing type from the LOV in the Pricing Type field. You can double-click in this field to open the P.10.66 Pricing Types screen.
Enter the budget of the agreement in the Agreement Budget field. This value refers to the project cost budget for material, subcontracts, or services made a part of the agreement later on.
The Currency field shows the currency of the budget. The currency assigned to project default ZX_CURCY is used as the default value, but this value can be overwritten. You can double-click in this field to open the A.10.12 Units of Measure screen.
Select the goods and services type from the LOV in the Goods/Service Type field. You can double-click in this field to open the P.10.65 Goods and Services Types screen.
In the Account Code field, you can assign an account code to this requisition planning 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 in 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 for inserting 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.
Select the date on which the awarding has been scheduled from the LOV in the Scheduled Award Date field. Select the date on which the mobilization has been scheduled from the LOV in the Scheduled Mobilize Date field. The mobilization date must be later than the awarding date. Select the date on which the completion has been scheduled from the LOV in the Scheduled Completion Date field. The completion date must be later than the mobilization date. The Scheduled Award Date, Scheduled Mobilize Date, and Scheduled Completion Date fields are only available for requisition type Subcontract. If you enter a non-working day in any of these fields, a warning appears; but the dates can be saved nevertheless.
Select the Sel check box for all requisition plannings to be downloaded into an Excel workbook using the Export button.
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 requisitions of the login project, you click the Calc All Forecasted button.
You cannot restrict the number of calculated planned requisitions by running a restricted query. Depending on the number of planned requisitions and milestones, this process may take some time.
Click the Export button to download the selected planned requisitions with existing milestone data into an Excel workbook. A window displays the download folder, the filename being created, and the template file used for the export.
Clear the Export Selected Requisitions Only check box if you want to export all requisitions. Click Export to start the job. When the export operation succeeds, you can open or save the file. An example file appears below.
After editing the Excel file, you can import milestone labels of planned requisitions into Smart Materials. Click Import, and a browser window opens. Click Browse, select the file, and click Submit Query. The selected file is uploaded to the application server. Close the browser window.
On the Export/Import Options window, click OK to continue.
When you click the Create Inquiry button, an inquiry is created based on the data of the selected planned requisition. This is of special interest if you have already defined potential bidders. Working with this feature allows you to prepare the request for quote (RFQ) at a very early stage without having an engineering requisition. Later on, after the requisition has been created, you just have to link that requisition to the inquiry. This action can be done on the Requisitions tab of the P.30.21 Prepare RFQ screen, using the LOV in the Engineering Requisition field to pick the requisition. For more information, see Requisitions.
Potential bidders can only be copied over if one record has been marked as the default for inquiries on the A.10.25 Address Types screen because the address type is a mandatory field for bidders assigned to an inquiry.
The required delivery date for bidders assigned to an inquiry is calculated as on P.30.21 Prepare RFQ based on the ROS date provided for the planned requisition and the setting of project default ZP_X_WEEKS. The formula used for the calculation is:
ROS date - ZP_X_WEEKS * 7
If the ROS date is not defined or the project default is not set, the required delivery date is not set.
You can only create one inquiry based on a planned requisition. Unless you delete the inquiry on the P.30.11 Inquiries screen, this button will not be re-enabled once you have used it.