Order Management - Steps

Step 1: Define Flexfields Define key and descriptive flexfields to capture additional information about orders and transactions. This step is required for Key Flexfields, and optional if you plan on using the functionality surrounding Descriptive Flexfields. Several defaulting values are provided. Step 2: Multiple Organizations Define multiple organizations in Oracle Inventory. This step is optional. Step 3: Inventory Organizations Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory. You must define at least one item validation organization and at least one organization that acts as an inventory source for orders fulfilled internally. If you plan to drop ship some orders, you must also define at least one logical organization for receiving purposes. Your item validation organization can be the same as your inventory source or your logical receiving organization, but you cannot use one organization for all three purposes. This step is required. Step 4: Profile Options Define profile options to specify certain implementation parameters, processing options, and system options. This step is required. Step 5: Parameters Set your Order Management Parameters to validate items, enable customer relationships, and operating unit defaults. This step is required. Step 6: Invoicing Define invoicing information, including payment terms, invoicing and accounting rules, Autoaccounting parameters, territories, and invoice sources. This step is required if you plan on transferring invoicing information to Oracle Receivables. Several defaulting values are provided. Step 7: Salespersons Define information on your sales representatives. This step is optional. Step 8: Tax Define tax features, such as codes, rates, exceptions, and exemptions. This step is required. Step 9: QuickCodes Define QuickCodes that provide custom values for many lists of values throughout Order Management. This step is required if you plan on creating user defined Quickcodes for utilization within Order Management. Defaulting values are provided. Step 10: Workflow

Define order and line processing flows to meet different order and line type requirements. This step is required. Step 11: Document Sequences (Order Numbering) Define Document Sequences for automatic or manual numbering of orders. This step is required. Step 12: Order Import Sources Define sources for importing orders into Order Management. This step is required if you plan on importing orders or returns into Order Management. Step 13: Units of Measure Define the units of measure in which you supply items. This step is required. Step 14: Item Information Define item information, including item attribute controls, categories, and statuses. This step is required. Step 15: Items Define the items that you sell, as well as container items. This step is required. Step 16: Configurations Define the configurations that you sell. This step is required if you plan on generating orders or returns for configured items. Several defaulting values are provided. Step 17: Pricing Define price lists for each combination of item and unit of measure that you sell. Optionally, you can define pricing rules and parameters to add flexibility. This step is required. Step 18: Customer Classes Define customer profile classes. This step is required if you plan on using the functionality surrounding Customer Profiles. Several defaulting values are provided. Step 19: Customers Define information on your customers. This step is required. Step 20: Item Cross References Define item cross references for ordering by customer part number, UPC, or any generic item number. This step is required if you plan on using the functionality surrounding item cross referencing. Several defaulting values have been provided. Step 21: Sourcing Define your sourcing rules for scheduling supply chain ATP functions. This step is optional. Step 22: Order Management Transaction Types (Order and Line Types) Define Order Management transaction types to classify orders and returns. For each order type, you can assign a default price list, defaulting rules, order lines, return lines, line types,

workflow assignments, payment terms, and freight terms. This step is required. Note: Order Management provides NO seeded OM transaction types. For existing Oracle Order Entry customers, Order Management will update existing Order Types to OM transaction type during the upgrade process. Step 23: Cost of Goods Sold (COGS) Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account) in Oracle Inventory. This step is required if you plan on utilizing the functionality surrounding COGS. Step 24: Processing Constraints Define processing constraints to prevent users from adding updating, deleting, splitting lines, and cancelling order or return information beyond certain points in your order cycles. Use the constraints Order Management provides, which prevent data integrity violations, or create your own. This step is optional. Several default values for processing constraints have been defined. Step 25: Defaulting Rules Define defaulting rules to determine the source and prioritization for defaulting order information to reduce the amount of information you must enter manually in the Sales Orders window. This step is optional. Several Defaulting rules and corresponding values for have been defined. Step 26: Credit Checking Define your credit checking rules. This step is required if you plan on performing any type of order credit checking. Step 27: Holds Define automatic holds to apply to orders and returns. This step is required if you plan on performing automatic hold for orders or returns. Step 28: Attachments Define standard documents to attach automatically to orders and returns. This step is optional. Step 29: Freight Charges and Carriers Define freight charges and freight carriers to specify on orders. This step is required if you plan on charging customers for freight or additional order charges. Step 30: Shipping Define shipping parameters in Oracle Shipping Execution. This step is required.