Ordhead Rev

This field contains an incremental counter of the number of revisions for a particular Orders dates. Revision number 1 will correspond to the original order sent to the supplier via EDIDL850.

This field indicates whether the record is an order version submitted to a supplier from Oracle Retail or an order revision submitted to Oracle Retail from the supplier. Value values are: V - Version R - Revision

Contains the number that uniquely identifies an order within the system.

Indicates the type of order and which Open To Buy bucket will be updated. Valid values include: N/B - Non Basic ARB - Automatic Reorder of Basic BRB - Buyer Reorder of Basic.

Contains the first date that delivery of the order will be accepted.

This field contains the status of the revision for the NOT_BEFORE_DATE field. Valid values are: 0 - change for NOT_BEFORE_DATE is not accepted, 1 - change for NOT_BEFORE_DATE has been accepted, 2 - change for NOT_BEFORE_DATE has been rejected.Code ORVS.

Contains the last date that delivery of the order will be accepted.

This field contains the status of the revision for the NOT_AFTER_DATE field. Valid values are: 0 - change for NOT_AFTER_DATE is not accepted, 1 - change for NOT_AFTER_DATE has been accepted, 2 - change for NOT_AFTER_DATE has been rejected.Code ORVS.

This field contains the date the revision was processed by Oracle Retail.

Contains the department number for orders limited to a single department and will be Null for orders involving items in more than one department.

Contains the number associated with the buyer for the order.

Contains the vendor number who will provide the merchandise specified in the order.

Supplier address sequence number differentiates supplier address within the same type.

This field contains the type of location in the location field. Valid values are: Valid values are S (Store) or (Warehouse).

This field contains the location all items on the order will be delivered to if populated. i.e. It will mean a single location order.

Contains the ad number associated with the order to provide a link between the order dialog and the promotions dialog.

Determines whether or not quality control will be required when items for this order are received. Valid values are Y and N.

Contains the date the order was created within the system.

This field contains the OTB budget bucket the order amount should be placed into.

The earliest shipping date. Oracle Retail target column EARLIEST_SHIP_DATE on ORDHEAD_REV.

The latest shipping date. Oracle Retail target column LATEST_SHIP_DATE on ORDHEAD_REV.

Contains the date when the order is closed.

Indicator identifying the sales terms for the order. These terms specify when payment is due and if any discounts exist for early payment.

Indicator that references what freight terms are related to the order.

Indicates where the order originated. Valid values include: 0 - Current System Generated (used by automatic replenishment), 1 - Past System Generated, 2 - Manual, 3 - Buyer Worksheet, 4 - Consignment Sales Generated PO, 5 - Vendor Generated, 6 - AIP Generated PO, 7 - SIM Generated PO, 8 - Allocation Generated PO, 9 - Consignment Transfer Generated PO, 10 - Consignment Ownership Generated PO. Values are defined by code_type 'OROR'.

The payment method for this order.

This field contains the type of backhaul allowance that will be applied to the order. Some examples are Calculated or Flat rate

This field will contain the backhaul allowance value.

The shipping method for this order.

The purchase type for this order.

15 - Completed Oracle Retail target column STATUS on ORDHEAD_REV.

Contains the date that the order was originally approved.

Indicates where the order was approved. It will be the user ID of the person approving the order for all orders manually approved on-line and will contain Replen for orders automatically approved in the replenishment process.

Code indicating the payment terms for freight charges associated with the order. Valid values include: CC - Collect CF - Collect Freight Credited Back to Customer DF - Defined by Buyer and Seller MX - Mixed PC - Prepaid but Charged to Customer PO - Prepaid Only PP - Prepaid by Seller.

Contains the code indicating the type of the location that is responsible for the transportation of the order.

User entered field describing the code for the location responsible for the transportation of the order.

Indicator used to determine where the title for goods is passed from the vendor to the purchaser. Examples include city, factory, or origin.

User entered field describing the code where the title of the merchandise is to be passed. Could be a city name, factory name, or place of origin.

This field indicates whether or not the order has been sent via EDI.

Indicates whether or not the order will be transmitted to the supplier via an Electronic Data Exchange transaction. Valid values are: Y = Submit via EDI N = Do not use EDI

Indicate whether this is an import order or not.

The country where this import order is coming from.

Indicates that a buyer generated purchase order has been acknowledged by the vendor with a separate EDI transaction.

Indicator to determine if the order should be included in on-order calculations. Valid values include Yes (include the order in the on-order calculations), No (do not include the order in the on-order calculations).

Contains the vendors unique identifying number for an order.

The exchange rate for this order.

The factory name where this order is shipping from.

The agent name for this order.

The name of the discharging port.

The name of the lading port. Oracle Retail target column LADING_PORT on ORDHEAD_REV.

The freight contract number. Oracle Retail target column FREIGHT_CONTRACT_NO on ORDHEAD_REV.

Contains the value associated with the PO_TYPE for the order.

This field indicated whether or not a supplier has agreed to break an order into separate boxes so that the boxes can be sent directly to stores.

Contains a code for the reason why the order was rejected during the automatic replenishment approval process. Valid values include: CCF (Credit Check Failed), CUST (Custom approval failed.), ITM (Item not present on order), LC (Missing Letter of Credit Details), LTL (Less than Full Truckload), NASA (Inadequate Supplier Availability), OC (Approval Threshold Exceeded), PT (Missing Purchase Type), QV (Quantity Variance Limit Exceeded), SNA (Supplier Site is not Active), SO (Order Scaling Errors), VM (Vendor minimum not met), NC (Negative cost calculated on an item), UOM (UOM convert error due to incomplete data), UR (User role approval amounts exceeded), HTS (HTS information incomplete). Values are defined by the CODE TYPE OREN and OARR.

Contains the currency code for the order. When creating an order within Oracle Retail, this field will always default to the currency of the supplier, but it can be overwritten.

This is an optional field which contains the contract number associated with this order.

Contains the date when the order can be picked up from the Supplier. This field is only required if the Purchase Type of the order is Pickup.

This field contains the status of the revision for the PICKUP_DATE field. Valid values are: 0 - change for PICKUP_DATE is not accepted, 1 - change for PICKUP_DATE has been accepted, 2 - change for PICKUP_DATE has been rejected.

This column will store the original order number from which the split orders were generated from. It will be for references purposes only. The purpose is to allow users a means of grouping orders that were split from an original super order. The original order, once split, will however be removed from the system.

Contains the location at which the order will be picked up, if the order is a Pickup order.

Contains the reference number of the Pickup order.

This column will hold the appointment date/time for receipt at the warehouse.

Any miscellaneous comments attached to the purchase order.