You use this program to identify existing purchase orders (and live requisitions with a user code of MRP) that require corrective action to meet the planning of the snapshot files.
The planning indicated within the snapshot files is generated by the Requirements Calculation program, or by subsequent manual manipulation of the snapshot files using the Requirements Planning Query program.
Suggested requisitions created during the running of the Requirements Calculation program can be printed, as well as purchase orders and requisitions that require no action.
- Report Options
- Additional Options 1
- Additional Options 2
- Output Options
- Report Details
- Order Action Messages
| Field | Description | ||||
|---|---|---|---|---|---|
| Sequence | |||||
| Supplier | Select this to print the report in supplier sequence. | ||||
| Stock code |
Select this to print the report in stock code sequence. This does not apply if pegging was not created during the run of the Requirements Calculation program. |
||||
| Print options | |||||
| New page per supplier |
Select this to print a new page upon change of the supplier This only applies when the report is run in Supplier sequence. |
||||
| Print value totals | Select this to print the total values of the purchase orders/requisitions for each stock item. | ||||
| Print pegging |
Select this to print pegging information that was created when running the Requirements Calculation program. Only pegging between the from/to suggested line due dates which you selected/indicated are printed. Dock-to-stock is taken into account. For example: If the Requirements Planning Setup option: Number of days after stock arrives that it can be used is set to 1 and the Dock to stock field against the item is set to 1, the pegging for the item will include any demands dated between two working days after the from Line due date to two working days after the to Line due date inclusive.
|
||||
| Convert quantity to alternate uom for suggested requisitions |
Select this to display the quantity required for a suggested requisition in its alternate unit of measure. For example, you have: Stock code: CODE-1 Unit of measure: EA Alternate unit of measure: BOX Conversion: 1 BOX = 10 EACH A quantity of 100 EA is required for a suggested requisition. If you select this option, then the quantity field against the detail line for the suggested requisition is displayed as 10 and the unit of measure is displayed as BOX. |
||||
![[Note]](images/note.png)
| Field | Description |
|---|---|
| Stock code selection | Indicate the stock code(s) for which you want to include purchase orders and requisitions in the report. |
| Warehouse selection | Indicate the warehouse(s) for which you want to include purchase orders and requisitions in the report. |
| Supplier selection |
Indicate the supplier(s) for whom you want to include purchase orders and requisitions in the report. This selection is not available if you selected to generate the report in Stock code sequence. |
| Product class selection | Indicate the product class(es) for which you want to include purchase orders and requisitions in the report. |
| Field | Description |
|---|---|
| Method of valuation for suggested requisitions | Indicate how you want to value suggested requisition items for the report. |
| Current cost | Select this to value suggested requisitions at the current cost of the item. |
| Last price paid | Select this to value suggested requisitions at the last price paid for the item(s). |
| Default p/order review price | Select this to value suggested requisitions at the default purchase order review price for the item. |
| Field | Description |
|---|---|
| Buyer selection |
Indicate the buyer(s) for whom to include purchase orders and requisitions in the report. The buyer defined against the purchase order and requisition is used for the selection. If the buyer is not defined, then the buyer against the defined against the stock code is used. This selection is ignored for non-stocked items. |
| Planner selection | Indicate the planner(s) for whom to include purchase orders and requisitions in the report. |
| Order date selection | Indicate the order date(s) for which to include purchase orders and requisitions in the report. |
| Line due date selection | Indicate the line due date(s) for which to include purchase orders and requisitions in the report. |
| Field | Description |
|---|---|
| Action selections |
This enables you to select the information to print according to the actions identified by the Requirements Calculation program. The following action selections can be made:
|
| Exclude actions | |
| Less than (days) | If the number of days by which a purchase order or
requisition must be rescheduled is less than the entry made
here, then the purchase order or requisition is excluded from
the report. This is only relevant if you selected to print orders/requisitions with the Action messages: Change and/or Delay. |
| Exception selections |
This enables you to select the information to print according to the exceptions identified by the Requirements Calculation program. |
| Late | Select this to include orders identified as late. Late orders are orders with an Order Date (the date on which the suggestion was placed) which is before the calculation date - meaning that the order was not raised in time. |
| Overdue | Select this to include orders identified as overdue. Overdue orders are orders with a Due Date which is before the calculation date - meaning that the order was due before the latest calculation date and it has not yet been receipted. |
| Include orders with no exception | Select this to include all orders that are not late or overdue. |
| Item selection | |
| Stocked | Select this to include information for stocked items in the report. |
| Non-stocked | Select this to include information for non-stocked items in the report. |
| Statistical parts | |
| Include | Select this to include statistical parts in the report. |
| Exclude | Select this to exclude statistical parts from the report. |
| Only | Select this to include only statistical parts in the report. |
These options enable you to apply a theme to the report and to define multiple output destinations for the report once it has been compiled (SRS Output Options).
If, after running the Purchase Order Actions report, you maintain existing purchase orders and add lines before existing stocked lines, the Line due date for the original stocked lines will be displayed as 00/00/00 when you rerun the Purchase Order Actions report. The reason is that the detail lines in the live system no longer match those in the snapshot and the only way to overcome this is to rerun the requirements calculation.
The Qty Available is the quantity available held on the MrpRequirement Master table. It is calculated in Requirements Calculation. The calculation is dependent on what you enabled at the Include in requirements calculation option (Requirements Planning Setup). In its simplest form, it is the Opening balance for a day. Starting with the quantity free in the warehouse, the supply/demand, etc., is netted off from this amount to give the closing balance for that date. That in turn becomes the opening balance for the next date with movement.
Values for suggested requisitions for non-stocked items are zero because they are calculated using QotNonStk or QotNonPurPrc tables for non-stocked warehouses (**).
For suggested requisitions, the information is extracted from the snapshot files.
For existing purchase orders and requisitions, the files copied to the snapshot directory by the Requirements Calculation program are compared to the live files.
Requisition stores issues and transfers are included in the report, even though they are ignored by the Requisition Review program.
The vessel is printed on the report for purchase order detail lines attached to an LCT (Landed Cost Tracking) shipment.
The Original Line Due Date field on the report corresponds to the Original Line Due Date field on the Purchase Order (i.e. the MOrigDueDate field on the database) and is the line due date captured when the purchase order was created. The original due date does not change when the line due date is changed; the Line due date on the Purchase order reflects the current due date after the change.
The following table lists the action messages that could be printed on the report.
| Action | Description |
|---|---|
| Reschedule in | The suggested due date of all (or some) lines of the order are earlier than the live order planned date. |
| Reschedule out | The suggested due date of all (or some) lines of the order are later than the live order planned date. |
| Reduce quantity | The suggested quantity to order for some (or all) lines on the order are less than the planned quantity on the live purchase order. This is normally due to manipulation of the purchase order quantity in the snapshot file (using the Material Requirements Review program), or the quantity having been changed using the Purchase Order Maintenance program since the snapshot was taken. |
| Increase quantity | The suggested quantity to order for some (or all) lines on the order exceeds the planned quantity on the live purchase order. This is normally due to manipulation of the purchase order quantity in the snapshot file (using the Material Requirements Review program), or the quantity having been changed using the Purchase Order Maintenance program since the snapshot was taken. |
| Cancel | All of this purchase order's merchandise lines can be cancelled (this is indicated by the suggested line due date being pushed out to beyond the year 2040) and there are no non-merchandise lines (e.g. freight) or LCT lines, which have not been completed against |
| Part cancel | It is suggested one (or more) lines of the order should be cancelled, but not the entire order. |
| Change | This message is displayed if more than one of the above actions have been suggested for a particular order. This could happen (for example) where some lines have a suggested due date earlier than planned, and others later than planned, or both the quantities and the dates require changing. |
| Delay | This message can be displayed for an Overdue exception if the purchase order is overdue, but the demand is still in the future. For example a purchase order due last Wednesday is overdue, but the demand is only for next Friday. The exception will be 'overdue', but the action will be to 'delay' delivery until next Thursday. |