Correcting Reservation Errors
Use the Correct Demand Errors component to view and correct order lines with data errors identified during reservations processing when reserving, promising, or shipping demand lines coming from a unfulfilled state. The following points apply to this component:
This page does not display work orders from PeopleSoft Maintenance Management.
For all order lines staged in PeopleSoft Inventory's IN_DEMAND table, the unit of measure (UOM) conversion is validated to confirm that the requested quantity was correctly converted to the item's standard (base) UOM and that all precision and rounding rules for the units of measure were followed.
You can opt for additional data validation for order lines by selecting the Perform Validation option on the Setup Fulfillment-Fulfillment Tasks page.
When working with a return to vendor stock request:
You cannot change the quantity fields.
You cannot delete the address override.
You cannot change the ship to customer ID.
See Processing Return to Vendor Stock Requests in Demand Fulfillment.
Warning! Changes to the order line fields that appear on the pages of the Correct Demand Errors component may lead to discrepancies in the order data. Oracle recommends that you control access to these pages tightly and analyze the impact of planned modifications carefully before implementing the changes.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
DEMAND_INF_E_INV |
Correct errors in order line data, such as quantity conversion errors or errors in shipping information. |
|
|
DEMAND_INF_E2_INV |
Correct errors in order line data related to shipping information, such as a missing schedule date or an invalid carrier. Use the Errors 2 page to correct data related to interunit transfer shipments. |
There are two types of errors that can be detected during reservation processing:
Simple data entry errors on the order line.
Errors reflecting process rule violations.
For simple data errors (such as invalid customer ID or ship to location) no error message appears in the Edit Errors region of the page. To know which of the fields that appear on the Reservation Errors - Errors 1 page or the Reservation Errors - Errors 2 page is invalid, save the page. An error message appears and the invalid field is highlighted. Correct the field and save the page again. If another error exists, another error message appears. You cannot save the page until all of the order line fields that appear represent valid data.
If the validation was performed by the fulfillment engine and a process rule violation was found, an error message appears in the Edit Errors group box. Follow the instructions in the message to correct the problem. If the validation was performed online, the demand row is identified as being in error, but an individual error message is not created. To find the error, attempt to save the page. The field in error is now highlighted.
Note: All of the fields that appear in the Demand Fields group boxes in the Correct Demand Errors component must be valid before the order line can complete any method of reservation processing.
Use the Reservation Errors - Errors 1 page (DEMAND_INF_E_INV) to correct errors in order line data, such as quantity conversion errors or errors in shipping information.
Navigation:
Field or Control |
Description |
|---|---|
Override GL (override general ledger) |
If this is an interunit expensed issue, you can override the General Ledger business unit against which the transaction is costed. The system validates the destination business unit's ChartFields against the new value, costs the issue using the defined interunit transfer price, and records interunit accounting entries for an interunit expensed issue. If an override value was entered on the stock request, that value appears here; otherwise, the field is blank upon entry to the page. Note: The business unit defaults established on the Inventory Display Options page govern whether this field appears upon entry to the page. If the default is Yes, the field appears; if the default is No, the field does not appear. This field is only available for internal requests, not for interunit transfers or external requests. |
The shipping information for external order lines, which includes intercompany transfers, is defined by the Customer, Ship To, and Location fields. The Customer is validated against the sold to customer defined for the Src BU (source business unit). The ship to customer must be valid for the sold to customer and the location must be valid for the ship to customer.
Field or Control |
Description |
|---|---|
Name, Ship Cust (ship to customer), and Location |
Enter for internal order lines that include interunit transfers. |
Location |
Only this field is validated for internal order lines. The location must be defined for the SetID of the Inventory business unit fulfilling the order. Locations are established using the Location component in the Define General Options menu. |
Qty Req (quantity requested) and Qty Base (quantity base) |
All order lines staged to the business unit's IN_DEMAND table must include a quantity requested in a valid ordering unit of measure (UOM) for the business unit. In addition, the Qty Base field on the order line must accurately reflect the conversion of the Qty Req field to the standard unit of measure for the item. Neither of these values can be negative. Conversion validation protects against taking orders for out-of-date UOMs. For example, old catalogs may show that 1 case of an item equals 12 each. However, new packaging requirements force the business unit to redefine 1 case as 10 each. If the order line requests 1 case, but calculates a base quantity of 12 each, an error is detected during reservation processing. |
Dist Type (distribution type) |
The value for this field must be a defined distribution type for the SetID of the Inventory business unit fulfilling the order. Distribution types are established on the Distribution Type page accessed in the Design Inventory Accounting menu. This field is optional. |
ChartField Overrides |
Click to correct any invalid or missing ChartField override data. The ChartFields must be defined for the SetID of the Inventory business unit fulfilling the order. ChartFields are optional. |
Important! Although you can modify the values in the Source and Src BU fields, PeopleSoft recommends against this. Changes to either of these fields break the logical tie with the business unit in which the order line was created and can cause discrepancies in the order data.
The Edit Errors group box displays the Field Name, Msg Seq (message sequence) number, and the Msg (message) text for errors related to process rule violations.
Use the Reservation Errors - Errors 2 page (DEMAND_INF_E2_INV) to correct errors in order line data related to shipping information, such as a missing schedule date or an invalid carrier.
Use the Errors 2 page to correct data related to interunit transfer shipments.
Navigation:
Demand Fields
Field or Control |
Description |
|---|---|
FERC Code (federal energy regulatory commission code) |
The code entered for the order line must be defined for the SetID of the Inventory business unit fulfilling the order. FERC codes are established on the FERC Code page. A blank field value is valid. |
State and Country |
The state code entered for an order line is validated to make sure that it is defined for the country. If the Country field has no states defined, the State field is unavailable for entry. State codes are established on the State page. A blank field value is valid. The country code entered for an order line is validated for the SetID of the Inventory business unit fulfilling the order. Country codes are established on the Country component. A blank field value is populated by the default country code specified on the Installation Options - Overall/GL page. |
Load ID |
The load ID entered for an order line must be defined for the Inventory business unit fulfilling the order. Load IDs are established on the Manage Loads page. A blank field value is valid. |
Freight Trm (freight term) |
The code entered for the order line must be defined for the SetID of the Inventory business unit fulfilling the order. Freight term codes are established on the Freight Terms page. A blank field value is valid. |
Ship Via |
The code entered for the order line must be defined for the SetID of the Inventory business unit fulfilling the order. These codes are established on the Ship Via Codes page. A blank field value is valid. |
Sched Date (schedule date) and Sched Time (schedule time) |
Every order line must have a schedule date. The schedule time is optional. |
Packaging |
The code entered for the order line must be defined for the Inventory business unit fulfilling the order. Packaging codes are established on the Item Packaging Codes page. A blank field value is valid. |
Carrier ID |
The ID entered for an order line must be defined for the SetID of Inventory business unit fulfilling the order. Carriers are established on the Carrier Table component. A blank field value is valid. |
Hold Code |
The code entered for an order line that is put on hold is validated to confirm that it is defined for the SetID of the Inventory business unit fulfilling the order. |
Route Code |
The code entered for the order line must be defined for the Inventory business unit fulfilling the order. If you do not enter a route code, the system automatically searches for an appropriate route when you save the page. This field only appears if routes are active for the business unit. |
Reason Code |
A user defined reason code selected from the values that have a reason type of Shipments. |
InterUnit |
Any order designated as an interunit transfer (including intercompany transfers) must have a destination unit that is different from the Inventory business unit fulfilling the order. |
Currency |
The code for the source business unit on interunit transfers is validated against the codes established on the Currency Codes page. |
Transfer and Markup % (price markup percentage) |
A transfer price, a price markup percentage, or both can be entered on the demand line of an interunit transfer or an interunit expensed issue. PeopleSoft Cost Management does not support interunit pricing for non-cost items. |
Important! Although you can modify the InterUnit check box and the values in the Dest Unit field, PeopleSoft recommends against it. Changes to either of these fields can cause discrepancies in the order data.
The Edit Errors group box displays the field name, message sequence number, and the message text for errors related to process rule violations. For example, suppose that both a transfer price and the price markup percentage are specified for an interunit transfer, you receive a message that only one or the other is allowed.