Expediter Workload - Intergraph Smart Materials - Version 10.1 - Help - Hexagon

Intergraph Smart Materials Classic Help

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Help
Smart Materials/Smart Reference Data Version
10.1

The P.70.71 Expediter Workload screen is the starting point for the expediters and inspectors. Here you get an overview of all orders available for expediting and inspection, and critical orders are indicated by different background colors and check boxes.

Your view on orders can be restricted by sections that are assigned to your user securities on A.20.06.02 or to your role on A.30.03. For more information, see Sections.

After you have selected the order that you want to work on, double-click in the Order Number field to get access to the expediting and inspection details.

You can use the display context to reduce the number of displayed orders.

This screen is a core workflow screen. For more information, see Core Workflow Screens.

Here you can see all orders available for expediting. Depending on whether you have included the Engineering Requisition, Suppl, and Req Origin fields in your configuration, you see either one record per each combination of order and requisition or just one record per order regardless of the number of associated requisitions.

If all approved supplements of an order have been closed, the order disappears from the workload. If an order has been closed by mistake or if any changes must be applied nevertheless, you can reverse the close of the order and the order can be selected in this workload again.

You can close an order or reverse the close on the P.70.79 Close Order screen. For more information, see Close Order.

You can use the Context field at the top of the screen to restrict the number of orders that are displayed. You can define the default value of this field on the A.60.61 User Preferences screen in the Expediter Display Context field. Double-click in the Context field to open A.60.61. For more information, see User Preferences.

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 project, order type (descending), order number, and requisition, or only by project, order type (descending), and order number if the requisition information is not included in the configuration. To change the order criteria, click the Order By ... button at the bottom of the screen, or select either the Order by this field ascending or the Order by this field descending item from the pop-up menu available on the field level. If you select Order by this field descending, the field name includes ‘(desc)’ to show that the data is currently displayed in a descending order.

The Project field displays the name of the project. If you have the MULTI PROJECT privilege, you can see the expediting data of all projects to which you have access. With which privileges you are actually allowed to modify the data depends on the selected project. If, for example, you have access to projects A and B, and your role for project A grants you unlimited rights and your role for project B only grants you update rights for item shipments but not for release notes, you will be able to see the data of both projects. You can also modify the data of both projects. But in project B you will not be able to change release note data. If you do not have the MULTI PROJECT privilege, you can only view and work on data created in the project you are logged in.

The Order Number field displays the name/number of the order. Double-click in this field to view the expediting data of an order cycle on the P.70.72 Expediting Details screen. Depending on the settings of the project defaults ZP_DELAY_Y and ZP_DELAY_R on the one hand and the planned and forecasted delivery dates of the item shipments of an order on the other hand, the background color of this field may change to show whether any delivery date is delayed. For this purpose, the planned and forecasted dates of the delivery date are compared. If the difference of any item shipment exceeds the number of weeks specified by the project defaults, the order number is displayed with a yellow (ZP_DELAY_Y) or a magenta (ZP_DELAY_R) background color.

The Type field shows the type of the order. This type can be PO for purchase orders or NC for notices of commitment. Other order types are not available for expediting. If the project default ZP_CO_TYPE is set to Y (default value is N), the displayed type is CO if at least one approved change order exists for the current purchase order/notice of commitment.

The Supplier field displays the name of the assigned supplier.

The Origin field shows the name of the office responsible for the order.

The Acknow check box indicates whether expediting has already noticed that a new order supplement has been approved. As soon as a buyer approves an order supplement, this check box is cleared to show the expediter that any changes have occurred. After the expediter has noticed these changes, he selects this check box to acknowledge the modifications.

The Exp Lic Req check box indicates whether any item shipment requires an export license. If the Exp Lic Req check box is selected on the Item Shipments tab of P.70.72 Expediting Details for any item shipment of the order, this indicator is checked. Only if not a single item shipment requires an export license is this indicator not checked.

The Exp Event check box indicates whether critical expediting events must be performed within the next range of days. With the project default ZP_RDCRITE, you define a range of days within which a critical expediting event or task must be managed. All expediting events and tasks for which a planned date but no actual date has been set and for which the critical indicator has been selected are checked against this range of days and the current date. If any event or task is found that has to happen or to be done within the next range of days, this flag is set.

The Insp Event check box indicates whether critical inspection events must be performed within the next range of days. With the project default ZP_RDCRITI, you define a range of days within which a critical inspection event or task must be managed. All inspection events and tasks for which a planned date but no actual date has been set and for which the critical indicator has been selected are checked against this range of days and the current date. If any event or task is found that has to happen or to be done within the next range of days, this flag is set.

The Exp Task check box indicates whether critical expediting tasks must be performed within the next range of days. With the project default ZP_RDCRITE, you define a range of days within which a critical expediting event or task must be managed. All expediting events and tasks for which a planned date but no actual date has been set and for which the critical indicator has been selected are checked against this range of days and the current date. If any event or task is found that has to happen or to be done within the next range of days, this flag is set.

The Insp Task check box indicates whether critical inspection tasks must be done within the next range of days. With the project default ZP_RDCRITI, you define a range of days within which a critical inspection event or task must be managed. All inspection events and tasks for which a planned date but no actual date has been set and for which the critical indicator has been selected are checked against this range of days and the current date. If any event or task is found that has to happen or to be done within the next range of days, this flag is set.

The OSD Traffic/OSD Site check box is selected if traffic/site has created an OSD (Over, Short, or Damaged) for any release note, package, package item or item shipment associated with this order and that has not been closed so far. In the case that an OSD exists, you can double-click in the check box to open either the P.70.72 Expediting Details screen or the P.70.74 Packages screen. There you can scroll through all item shipments and release notes of the order to see for which objects an OSD has actually been created. If OSDs have been created for item shipments and release notes, packages, or package items, you will be asked which module you want to call. You can double-click in the OSD Traffic check box on P.70.72 to open the appropriate OSD screen. On P.70.74, the OSD Traffic check box is available on each level, that is, for release notes, packages, and package items. When you double-click in this check box, the corresponding OSD screen opens.

With the Avail. for Supplier indicator, you can control whether you want the supplier to be able to enter data for this order or not when using the E-Supplier login. By default, all orders are available. If you are logged in as a supplier, freight forwarder, or packer, you will only see your 'own' orders for which this indicator is set. Whether you are identified as a supplier or not depends on the setting of project default ZP_SUPROLE. For more information, see ZP_SUPROLE.

This indicator is always set on the order level. That is, regardless of how many requisitions are associated with an order, the order is either available for a supplier or not. You cannot allow modifications for a specific combination of order and requisition and not allow it for another combination of the same order with a different requisition.

The VDR check box indicates whether VDRs have been assigned to the order. If this check box is selected, you can double-click in the check box to open the D.90.21 Attachments screen. For more information, see Attachments.

The Engineering Requisition field displays the name/number of the engineering requisition. If the requisition has been created manually by engineering, the background color is set to cyan. If the requisition has been created because the order type of a manually created order has been switched, the background color is set to red. The highest supplement of the requisition associated with this order is shown in the Suppl field. The origin of the engineering requisition is shown in the Origin field.

The Buyer field shows the name of the buyer who is responsible for the order.

The Section field shows the name of the section. The view on orders can be restricted by sections that are assigned to your user securities on A.20.06.02 or to your role on A.30.03. For more information, see Sections.

The Issued by field shows the name of the office that has issued the order.

The date of last/next contact with the supplier is displayed in the Last Contact/Next Contact field. Depending on whether requisitions are on display or not and whether different requisitions have been assigned to an order cycle or not, this date either refers only to the current requisition (requisition data on display) or to all requisitions (requisition data not on display). If just one requisition code has been assigned to an order, this date always refers to that requisition, regardless of whether requisition data are on display or not.

The Complete check box is marked if the order is complete, that is, an actual contract delivery date has been entered for all item shipments. In the case of tagged master items for which sub items have been created, only the sub items are taken into account.

The Complete Date field shows the latest actual contract delivery date that can be found for a completed order. If an order is not completed so far, the field remains empty.

The date when the first order of the order cycle has been approved is displayed in the First Approved Date field.

The last date when a supplement of the order cycle has been approved is displayed in the Last Approved Date field.

The Supplier Name field shows the name of the supplier's company.

The Expediter field shows the expediter for the order. Here the expediter is shown as assigned on the P.70.73 Order Reference screen. If the expediter is identical for all supplements of the order and all its tagged items, this expediter is shown here. If no expediter has been assigned, the field remains empty. If different expediters have been assigned to the individual supplements of the order or its tagged items, the value DIFFERENT is displayed. When you update the expediter, this affects the data on the P.50.07 and P.70.73 screens. All users who have the EXPEDITER privilege can be selected. If the project default ZX_PRIVREQ is set to N (default), any user can assign an expediter to an agreement. If this project default is set to Y, only users with the ASSIGN EXPEDITER privilege can assign expediters to agreements.

The Shop Expediter field shows the shop expediter for the order as assigned on the P.70.73 Order Reference screen. If the shop expediter is identical for all supplements of the order and all its tagged items, this shop expediter is shown here. If no shop expediter has been assigned, the field remains empty. If different shop expediters have been assigned to the individual supplements of the order or its tagged items, the value DIFFERENT is displayed.

The Inspector field shows the inspector for the order as assigned on the P.70.73 Order Reference screen. If the inspector is identical for all supplements of the order and all its tagged items, this inspector is shown here. If no inspector has been assigned, the field remains empty. If different inspectors have been assigned to the individual supplements of the order or its tagged items, the value DIFFERENT is displayed.

The Shop Inspector field shows the shop inspector for the order as assigned on the P.70.73 Order Reference screen. If the shop inspector is identical for all supplements of the order and all its tagged items, this shop inspector is shown here. If no shop inspector has been assigned, the field remains empty. If different shop inspectors have been assigned to the individual supplements of the order or its tagged items, the value DIFFERENT is displayed.

The Expediting Level field shows the level of expediting. If the expediting level of all requisition supplements and all their tagged items is identical, this level is shown here. If no expediting level has been assigned so far, this field remains empty. If different expediting levels have been assigned to the requisition supplements or any tagged item, the value DIFFERENT is displayed. Revised levels of expediting maintained on the Mod. Expediting Level field are taken into account. If a revision has taken place, the original level of expediting is not considered any longer.

The Inspection Level field shows the level of inspection. If the inspection level of all requisition supplements and all their tagged items is identical, this level is shown here. If no inspection level has been assigned so far, this field remains empty. If different inspection levels have been assigned to the requisition supplements or any tagged item, the value DIFFERENT is displayed. Revised levels of inspection maintained in the Mod. Expediting Level field are taken into account. If a revision has taken place, the original level of inspection is not considered any longer.

The Last Info Date field displays the last date on which any information has been entered for any item shipment associated with the order or combination of order and requisition.

The Last Info Type field shows the type of the last information update.

The Delivery Date field displays the latest first promised delivery date. This field shows you the latest date for which the supplier promises to deliver the first item of this order over all supplements. That is, the maximum value of the First Delivery field (displayed on P.50.07) for all approved supplements of the order is displayed.

The Req On Site field displays the latest date when the material is required on site. This field shows the latest required on site date of this order including all supplements. In other words, the maximum value of the Req On Site date of P.50.07 is displayed here.

The No. of Documents field shows the number of documents attached on the item shipment level that are relevant for expediting and inspection. Whether a document is of interest for expediting and inspection is determined by the project default ZP_E_I_DOC. Only documents with the type equal to the type assigned to this project default are relevant for expediting and inspection. If at least one document is found, you can double-click in this field to open the D.90.21 Attachments screen where you can see all relevant documents. For more information, see Attachments.

D.90.21 can only be opened to get an overview of the documents. You cannot apply any modifications. If any changes have to be done, you must go to the P.70.72 Expediting Details screen and double-click in the Doc check box to open D.90.21 in a mode that allows you to modify data.

The order descriptions are displayed in the Short Desc and Description fields.

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 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 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 will always be sorted in ascending order. The selected and changed order by criteria are displayed in the Ordered by field.

The Export button allows you to export data to an Excel workbook. A box opens where you can enter the export template with the entire path in the Template for Export field.

Select the Without MCS check box if you want to export only item shipments without MCS number. The MCS sheet of the export file is not filled in this case.

Click the Export button to start the export. Click Cancel to close the box without exporting.

The format of the export file is controlled by a template file, which must reside on the application server. This feature is only available for orders that have been created in the project you are currently logged in. The sort order of the expediting export is determined by the last selected sort order on P.70.72 defined for the current configuration. If no sort order is available, the current default sort order (Pos/Sub/IS Pos/IS Sub) is used.

Click the Delivery Lots button to define delivery lots for splitting huge quantities on bulk agreements. You can define delivery lots on the P.70.76 Delivery Lots screen. For more information, see Delivery Lots.

Click the Pending Quantities button to perform expediting for pending quantities on the P.70.75 Pending Quantities screen. For more information, see Pending Quantities. This button is only active for orders of the project you are currently logged in.

You can click the Order Reference button to maintain expediting reference data such as expediting and inspection levels, events and tasks, or vendor progress. You can see and maintain this data on the P.70.73 Order Reference screen. For more information, see Order Reference.

Click the Inspection button to open the P.70.51 Inspection Applications screen. For more information, see Inspection Applications.

Different methods for inspection are available. You can either use the Inspectable, Release Note, Waiver, Release/Waiver Date, NCR Date, NCR Release Date, and NCR Remarks fields provided on the P.70.72 Expediting Details screen, or work with IRCs (Inspection Release Certificates) on the P.70.72 screen, or you can use the features provided on the P.70.51 Inspection Applications screen and its subsequent screens, P.70.52 Attached Inspection Documents and P.70.54 Attached Inspection Attributes.