Previous  Next          Contents    Library

Import Requisitions

Unit of Measure Conversion

Import Requisitions creates two requisition types:

Internal Requisitions are produced in Unit of Issue and Purchase Requisitions are produced in Unit of Purchase.

Purchase Requisitions

If the requisition type is Purchase, Oracle Purchasing checks for a valid AutoSource Rule. The number one ranked vendor and the lowest sequence numbered document for that vendor are used as the quotation.

The unit of measure on the quotation line becomes the unit of measure on the vendor-sourced requisition line. The quantity is converted to this unit of measure and rounded to the nearest integer.

Pricing Rules

A valid shipment line must have:

If there is no valid AutoSource rule, the unit of measure on the requisition line is the primary unit of measure and the price is the list price for the item.

Example

The four pricing rules are demonstrated in this example. Follow each of the four products through the pricing process.

Requisition Line
Item Unit of Measure Quantity System Date
S1000 Each 100 1.JAN.95
S2000 Each 200 1.JAN.95
S3000 Each 300 1.JAN.95
S4000 Each 400 1.JAN.95

Quotation
Item Unit of Purchase Price
S1000 Box 10 95

Qty Unit of Purchase Price Effective
10 Box 10 80 1.JAN.95 - 1.DEC.95
1 Box 100 75 1.JAN.95 - 1.DEC.95

S2000 Box 10 95

5 Box 10 80 1.JAN.95 - 1.DEC.95
10 Box 10 50 1.AUG.95 - 1.DEC.95
20 Box 10 40 1.JAN.95 - 1.DEC.95

S3000 Box 10 100

1 Box 100 50 1.JAN.95 - 1.DEC.95
2 Box 100 30 1.AUG.95 - 1.DEC.95

S4000 Box 10 -

Result Requisition Lines
Item Unit of Measure Quantity Price
S1000 Box 10 10 80
S2000 Box 10 20 40
S3000 Box 10 30 100
S4000 Box 10 10 0

Internal Requisitions

If the requisition type is Internal, Oracle Applications retrieves the Unit of Issue for the item in the source organization on the requisition line. If no Unit of Issue exists, the primary Unit of Measure is used. The quantity ordered and unit price are converted to the new Unit of Measure.

Internal Requisition Accounting

Imported Requisitions use AutoAccounting to determine the account combinations for Internal Requisitions of delivery type Inventory. Each segment of the account is derived from the subinventory replenishment account, the item replenishment account or a constant.

For example, if your accounting structure is:

Company -- Cost Centre -- Account

you may decide that your AutoAccounting definition is:

Company 01 Cost Centre MTL_SECONDARY_INVENTORIES Account MTL_SYSTEM_ITEMS

This definition says that the replenishment account is generated using "01" for the Company value, the Cost Centre value is from the destination subinventory and the Account value is taken from the item.

Suppose you have an item X1000, with a replenishment expense account of 01-000-3100. If you order item X1000 to be delivered to WARD-1 with a replenishment expense account of 01-200-5000, then AutoAccounting will generate an account combination of 01-200-3100 on the requisition line. If AutoAccounting cannot generate an account, then the default is the A/P accrual account defined in Oracle Inventory.

Note: To achieve consistent accounting between Internal requisitions that are Imported and Internal requisitions that are entered via Enter Requisitions, the FlexBuilder rules for Enter Requisitions must be set up to reflect the AutoAccounting rules that you have set up.


         Previous  Next          Contents    Library