Previous | Next | Contents | Index | Glossary | Library |
Sales Orders | |
---|---|
Owner | Oracle Inventory |
Flexfield Code | MKTS |
Table Name | MTL_SALES_ORDERS |
Number of Columns | 20 |
Width of Columns | 40 |
Dynamic Inserts Possible | Yes |
Unique ID Column | SALES_ORDER_ID |
Structure Column | None |
Table 1 - 31. (Page 1 of 1) |
The Sales Order Flexfield is a key flexfield used by Oracle Inventory to uniquely identify sales order transactions Oracle Order Entry interfaces to Oracle Inventory.
Your Sales Order Flexfield should be defined as Order Number, Order Type, and Order Source. This combination guarantees each transaction to Inventory is unique.
You must define this flexfield before placing demand or making reservations in Oracle Order Entry.
You must set up the OE: Source Code profile option to determine the source code you will use in for the third segment of this flexfield to guarantee that each transaction is unique. (Oracle Inventory defaults the value of the OE: Source Code profile option to 'ORDER ENTRY'.)
For your value sets, you must use Dynamic Inserts. The Validation Type should be None. Value Required should be Yes to improve performance of concurrent programs. The value set must be alphanumeric. The value set maximum size must be 40.
You should set the Required field to Yes in the Validation Information region when enabling the flexfield segments. Setting this field to Yes, improves performance when updating existing demand or reservations by guaranteeing that Oracle Order Entry always supplies a value.
Set Right-justify Zero-fill Numbers to No so sales order numbers are not padded with zeros.
Oracle Inventory defines a unique ID for each order in MTL_SALES_ORDERS based on this flexfield. The Inventory unique ID, as opposed to the Order Entry unique ID, is used throughout Oracle Manufacturing applications.
Previous | Next | Contents | Index | Glossary | Library |