Order to cash flow cycle in order management in detail

Order To Cash Flow Cycle In Order Management in Detail
The Order to Cash f low is the complete process of entering an order into the sy stem (Sales Order), deliv ery the good(s) (Shipping), and then
producing the Inv oice f or the good(s). This inf ormation will prov ide guidance on procedures to complete the Order to Cash Business Flow. It is
intended to be generic and does not relate to a specif ic organization or industry . Step by step best practices with tips and troubleshooting
ref erences are prov ided to assist y ou through each phase.
The Order to Cash process is a critical process that can cause conf usion regarding data dependencies between products, workf low status' and
the steps that need to be perf ormed. This inf ormation giv es y ou one place to f ind best practices and troubleshooting inf ormation to help reduce
Order to Cash issues.
The goal is to prov ide an ov erall understanding and assistance with Setup, Process, Troubleshooting and Debugging the Order t o Cash Business
Process.
The end result will be a working Order to Cash Business Process. The ability to take a Sales Order through the f ollowing phases: Entry , Booking,
Shipping, and Inv oice. Showing the working steps through each phase.
The areas of f ocus are:
 Required Setup
o Create Customer
o Create Item
o Organization Ov erv iew
o Av ailable Inv entory
o Price List
o Def aulting Rules
 Create Order
 Shipments
o Pick Release
o Ship Conf irm
o Interf ace Trip Stop (ITS)
 Inv oice
All users who wish to set up, troubleshoot or debug a basic Order to Cash cy cle in Order Management (OM), that is to say f rom order creation to
inv oicing.
Create customer
Def ine a customer that y ou will enter in the sales order. You could use an existing customer def ined in the Vision Database, in which case this
step would be optional f or the testf low. Howev er, it is highly recommended that y ou create y our own customer if y ou need to make changes to
customer specif ic setup.
If y ou plan on using an existing customer, some common customers used of ten f or testing OM in Vision are :
A. C. Networks, AT&T Univ ersal Card, Business World (Customer Number 1608)
1. Nav igate to Customers -> Standard.
o Enter a new customer name in the Name f ield, and press Find.
o If the customer name already exists, go back and enter a name that does not already exist. Press the 'Create' button.
2. In the Addresses tab, click on New
3. Enter the f ollowing inf ormation in the Customer Address screen.
Address : Enter the required f ields (they will f ist appear in y ellow).
<Business Purposes tab>
Usage = Bill To : Check the Primary f lag. Sav e.
Usage = Ship To : Check the Primary f lag.
Select the Bill to Location created abov e f rom the LOV. Sav e.
4. Notice the 'Open' button in the abov e screenshot. This is where y ou can enter additional details specif ic to the business purpose. So, if the
cursor is on the 'Ship To' row as seen here, clicking on Open will allow to enter inf ormation specif ic to the Ship To Location. This can be examined
f urther in the Def aulting Rules section.
Create Item
Create an item that will be entered in the sales order. Use existing items def ined in the Vision Database, in which case this step would be optional
f or this testf low. Howev er, it is highly recommended to create own item if needed to make changes to item specif ic setup.
Some commonly used items in the Vision Database f or testing in OM are :
AS54888, CM13139, CM18759
1. Nav igate to Inv entory > Items > Master Items

2. When prompted, select 'M1 Seattle Manuf acturing' f rom the Organizations list. If this list did not come up, go to Inv entory > Change
Organization, and make sure y ou select this organization.
 Notice when the screen opens, the Organization f ield shows V1 (Vision Operations). This is because we hav e opened the Master
Items f orm, and V1 is the master organization of M1. See the Organization Ov erv iew section f or more details on this relationship.
3. Enter a name f or the Item and Description.
4. Go to Tools > Copy From.
Select the Template 'Purchased Item'.
Click on 'Apply ' and then click on 'Done'.
5. The seeded template 'Purchased Item' will assign the necessary item attributes to go through this basic OM testf low. For example, check some
of the f ollowing item attributes that y ou did not need to set manually because they were assigned f rom the template.
<Inv entory tab>
Inv entory Item, Stockable, Transactable, Reserv able
<Order Management tab> (click on the arrow to the right of all the tabs)
Customer Ordered, Customer Orders Enabled, Shippable, OE Transactable
6. So f ar def ined the item in the Item Master Organization, V1. Next, go to Tools > Organization Assignment. Alternativ ely , click on the 3rd tab on
the lef t side of the screen as circled in red in the below screenshot.
This is where y ou will f ind a list of organizations (child organizations) that hav e V1 as their master organization. M1 shows at the top because we
had selected it in Step 2. The item attributes def ined in V1 can be assigned to the child organizations by checking the Assigned box.
 Check the Assigned box f or the organization M1. Items needs to be enabled in the organizations in which they will be transacted.
Organization Overview
In this section, we will go ov er the basic structure of the def inition of an inv entory organization by looking at the data already def ined in the Vision
database.
Do not change any data we see below.
1. Nav igate to Inv entory > Setup > Organizations > Organizations.
 Query by the name 'Seattle Manuf acturing'. This is the organization (organization code M1) we commonly use in the Vision Database
to create Inv entory transactions, including shipment of sales orders.
2. Notice the entry 'Inv entory Organization' under Organization Classif ications. Place the cursor on that row, and click on t he button Others.
3. Select 'Accounting Inf ormation' f rom the list.
 Place cursor any where in the Accounting Inf ormation f ield to see details.
 Notice this is where the organization is associated with its 'Set of Books, Legal Entity and Operating Unit'.
 The concept of Operating Unit will of ten come up, so it is good to know where this relationship is def ined, ie. which Operating Unit the
Inv entory Organization (warehouse) belongs to.
 Close the Accounting Inf ormation window and Additional Organization Inf ormation screen.
4. Place the cursor on the classif ication Inv entory Organization again, click on the Others button and select 'Inv entory Information' from the list.
 Notice this is where the Inv entory organization parameters are def ined.
 This screen can also be accessed directly f rom Inv entory > Setup > Organizations > Parameters.
 Notice this is where the organization code 'M1' is specif ied, and the Item Master Organization is specif ied as 'Vision Operat ions' (V1).
This sets the relationship f or Seattle Manuf acturing (child org) and Vision Operations (master org).
5-a. As an optional step, y ou can query the organization 'Vision Operations' and check that it is classf ied as both a Legal Entity and Operating
Unit (see Step 3) as well as an Inv entory Organization. If y ou check the Inv entory Organization Parameters f or 'Vision Operat ions' y ou will notice
that the organization code is def ined as 'V1'. The master org is itself .
5-b. As another optional step, y ou can go to Edit > Pref erences > Prof iles, and run a query with the prof ile name 'MO:%'. You will see the v alue
f or the prof ile option 'MO: Operating Unit' being 'Vision Operations'. This is the Operating unit in which the OM transactions are created when
logged into the responsibility used in this testf low (f or R11i).
In R12, the Multi-Org Access Control (MOAC) f eature enables users to access to one or more Operating Units within one user responsibility .
Create stock for item using Miscellaneous Receipt
1. Make sure y ou are in the organization M1. If not, nav igate to Inv entory > Change Organization, and select the organization M1 Seattle
Manuf acturing.

2. Nav igate to Inv entory > Transactions > Miscellaneous Transaction, and enter the f ollowing inf ormation:
Ty pe : Miscellaneous receipt
Click on the Transaction Lines button
3. In the Miscellaneous receipt (M1) f orm, enter the f ollowing inf ormation:
Item : <y our item>
Subinv entory : FGI
Quantity : 100
Account : Inv oke the LOV and enter the Account Alias 'Miscellaneous'
Sav e changes.
4. (Optional) Check the material transaction that was just created.
- Nav igate to Inv entory > Transactions > Material Transactions
- Enter y our item in the Find Material Transactions screen and click on Find.
- Verif y that the Miscellaneous Receipt transaction exists.
5. (Optional) Check the On-hand quantity f or y our item.
- Nav igate to Inv entory > On-hand, Av ailability > On-hand Quantity
- Enter y our item in the Query Material screen and click on Find.
- Verif y that the On-hand quantity exists.
Assign item to Price List
1. Nav igate to Pricing > Price Lists > Price List Setup. You could create a new price list, but in this testf low, we will assign y our item to an existing
price list 'Corporate'.
Query the price list 'Corporate'.
2. Mov e the cursor to the List Lines section, and add a new line using Ctrl + Down Arrow on y our key board, or by going to File > New. Enter the
f ollowing inf ormation :
Product Context : Item
Product Attribute : Item Number
Product Value : <y our item name>
Value : 100
The rest of the required f ields should def ault in.
Defaulting Rules
Def aulting rules determine the v alues that y ou want to get def aulted into a sales order to reduce the amount of inf ormation y ou need to enter
manually . You could create and modif y def aulting rules, in which case the Def aulting Generator concurrent program needs to be run.
In this testf low, howev er, we will only look at an existing seeded def aulting rule f or the f ield Order Type. Based on that, we will set up a def ault
v alue f or the Order Ty pe at the customer's Inv oice To location lev el.
1. Nav igate to Setup > Rules > Def aulting.
-Click on the Flashlight icon, and select the entity Order Header.
- In the Attributes section, place the cursor on the line with Attribute = Order Ty pe, and click on the Def aulting Rules button.
2. Examine the setup f rom the f ollowing screenshot. This is say ing that when entering a sales order, the Order Ty pe will def ault to the v alue set
up at the Inv oice To, Ship To, and f inally the Customer, wherev er it is f ound f irst in that sequence.
3. So, let's set up a def ault v alue f or Order Ty pe at the customer's Inv oice To lev el.
Nav igate to Customers > Standard.
 In the Find/Enter Customer screen, enter y our customer name and click on Find.
 In the next Match Results screen, make sure y ou place the cursor on the row with a v alue in the Customer Number f ield, and click on
OK.
 In the Addresses tab, place the cursor on the row f or y our address and click on Open.
 In the Business Purpose tab, place the cursor on the row f or the usage 'Bill To' and click on Open. This is the 'Inv oice To' lev el we saw
in the prev ious step.
 Go to the Order Management tab, and enter the Order Ty pe 'Mixed'. Sav e.
4. In the next 'Create Order' section, y ou will notice that the Order Ty pe will def ault to Mixed, due to this setup.
Create Order

We are now ready to create a sales order.
1. Nav igate to Orders, Returns > Sales Orders and make sure the f ollowing inf ormation is entered. Notice how some of these f ields (in addition to
others), get def aulted due to the Def aulting Rules setup.
*Order Inf ormation tab (Order Header)
<Main tab>
Customer Name : <y our customer name>
Make sure the Ship To/Bill To Locations are def aulted in.
Order Ty pe : Mixed
Price List : Corporate
Salesperson : No Sales Credit
<Others tab>
Pay ment Terms : N30
Warehouse : M1
Sav e.
2. Go to the Line Items tab, and enter the f ollowing inf ormation.
*Line Items tab (Order Lines)
<Main tab>
Ordered Item : <y our item name>
Qty : 10
UOM : Def aults to Ea
Sav e.
* In the Pricing tab, notice that the Price List Corporate has def aulted f rom the Header, and that the List Price 100 is the price y ou set up in the
price list. The Unit Selling Price is the same as the List Price in this example, but it will show a dif f erent v alue if there is a discount or surcharge
applied to the list price. For example, if y ou apply a 10% discount modif ier, the List Price will be 100 and the Selling Price will be 90.
* In the Shipping tab, notice that the Warehouse is M1. This is the warehouse f rom which the item will be shipped out to the customer.
Book the Order.
Click on the button 'Book Order' in the header or lines.
*You should see a note say ing Order has been booked. Notice the status of the order header has changed f rom Entered to 'Booked', and the
status of the line (check the Status f ield in the Main tab of the lines) has changed f rom Entered to 'Awaiting Shipping'.
SQL Tips:
<Finding deliv ery detail inf ormation based on the order_line_id>
select source_header_number, source_header_id, source_line_id, deliv ery _detail_id, released_status
f rom wsh_deliv ery _details
where source_code = 'OE' and source_line_id = 201594;
SOURCE_HEADER_NUMBER SOURCE_HEADER_ID SOURCE_LINE_ID DELIVERY_DETAIL_ID RELEASED_STATUS
64153 98956 201594 279193 R
--R=Ready to Release
*Optional : Run the f ollowing queries to understand the distinction between the shipping warehouse and operating unit columns in the order
header/lines tables. Ref er to the Organization Ov erv iew section f or concepts. 207 is the ID f or Seattle Manuf acturing. 204 is the ID f or Vision
Operations.
SQL Tips:
ORG_ID = Operating Unit which perf ormed this transaction
SHIP_FROM_ORG_ID = Ship From Organization Id - Warehouse (the Inv entory Organization)
select order_number, header_id, ship_f rom_org_id, org_id
f rom oe_order_headers_all where header_id = 98956;
ORDER_NUMBER HEADER_ID SHIP_FROM_ORG_ID ORG_ID
------------ ---------- ---------------- ----------
64153 98956 207 204
select header_id, line_id, line_number, ship_f rom_org_id, org_id
f rom oe_order_lines_all where header_id = 98956;
HEADER_ID LINE_ID LINE_NUMBER SHIP_FROM_ORG_ID ORG_ID
---------- ---------- ----------- ---------------- ----------
98956 201594 1 207 204
Pick Release
1. Nav igate to Shipping > Release Sales Orders > Release Sales Orders
 In the Order tab, enter y our order number.

 In some cases, y ou may need to remov e the def aulted 'To' v alue f or 'Scheduled Ship Dates' and 'Requested Dates' f ields, if the order
line y ou created has a f uture date f or these f ields. Pick release will only consider lines within the dates specif ied.
*Go to the Inv entory tab and enter the warehouse M1. Set the f ollowing v alue if it is not def aulted.
Auto Allocate = Yes
*Go to the Shipping tab. Set the f ollowing v alue if it is not def aulted.
Autocreate Deliv ery = Yes
Auto Pick Conf irm = Yes
2. Click on the Concurrent button.
Ship Confirm
1. Nav igate to Shipping > Transactions.
 In the Query Manager screen, enter y our order number in the From Order Number f ield and tab out. Then, click on the Find butt on.
2. Notice the f ollowing in the Lines/LPNs tab.
Detail : The deliv ery detail of the shipment
Deliv ery : The deliv ery that got autocreated during pick release
Line Status : Staged/Pick Conf irmed
Next Step : Ship Conf irm/Close Trip Stop
SQL Tip:
Note, the same query as bef ore shows that the released_status is now Y (Staged).
select source_header_number, source_header_id, source_line_id, deliv ery _detail_id, released_status
SOURCE_HEADER_NUMBER SOURCE_HEADER_ID SOURCE_LINE_ID DELIVERY_DETAIL_ID RELEASED_STATUS
64153 98956 201594 279193 Y
<Finding the deliv ery associated to the deliv ery detail and its status>
select wnd.deliv ery _id, wnd.status_code
f rom wsh_new_deliv eries wnd, wsh_deliv ery _assignments wda, wsh_deliv ery _details wdd
where wdd.deliv ery _detail_id = wda.deliv ery _detail_id
and wda.deliv ery _id = wnd.deliv ery _id
and wdd.deliv ery _detail_id = 279193;
DELIVERY_ID STATUS
----------- ---------
106904 OP
3. Go to the Deliv ery tab and click the Ship Conf irm button. In the Conf irm Deliv ery window, accept the def ault parameters and click on OK.
*Not checking the Def er Interf ace checkbox, as shown here, ensures that the next step, running the Interf ace Trip Stop (ITS) concurrent program,
happens automatically . Def erring ITS (checking this box) means y ou need to run the concurrent in a separate step.
Interf ace Trip Stop (ITS) can be done f rom Shipping > Interf aces > Run (Interf ace Trip Stop - SRS).
*You will get a message that the deliv ery has been conf irmed. (Sometimes it could show some warning message that could be ignored f or the
purposes of this test).
4. Go to View > Requests, and v erif y that the Interface Trip Stop completed successf ully .
SQL Tip:
<Finding if ITS has successf ully interfaced the deliv ery detail to OM and INV>
select deliv ery _detail_id, released_status, oe_interf aced_f lag, inv _interfaced_flag
DELIVERY_DETAIL_ID R O I
------------------ - - -
279193 C Y Y

* released_status = C (Shipped) -- becomes Shipped af ter ship conf irm, ev en bef ore ITS
* oe_interf aced_f lag = Y -- signif ies ITS has interf aced shipping data to OM
* inv _interf aced_f lag = Y -- signif ies ITS has interf aced shipping data to INV
5. As an optional step, y ou can check if the item has actually been shipped out of inv entory .
*Make sure y ou are in the organization M1. If not, nav igate to Inv entory > Change Organization and select M1.
*Nav igate to Inv entory > Transactions > Material Transactions
*Enter the f ollowing inf ormation in the Find Material Transactions screen and click on Find
Transaction Date : Ensure the transaction date is within the range specif ied
Source Ty pe : Sales Order
Source :
-Ev oke the LOV and click on the button Combinations
-Enter y our Sales Order Number and Order Ty pe Mixed, then click OK
-Example : 58095.Mixed.ORDER ENTRY
*Go to the Transaction Ty pe tab, and notice the line with Transaction Ty pe = Sales Order Issue. This is the Inv entory Transac tion that happened
when the item was shipped out of the warehouse M1, hence the negativ e quantity -10.
*The other two lines with Transaction Ty pe = Sales Order Pick, are f or the mov e order transaction that happened automatically during Pick
Release (automatic as per the pick release parameters we had set in this testf low), when the item was mov ed f rom the pick-f rom subinv entory to
the staging subinv entory . Hence there is one line each f or a negativ e and positiv e transaction f rom/to each subinv entory . The f inal shipment to
the customer (sales order issue) is made f rom the staging subinv entory .
Invoice
1. First let's check the status of the order line.
*Nav igate to the sales order f orm, and query y our sales order. Go to the Line Items tab and check that the status of the line is 'Shipped'.
*While still on the line, go to Tools > Workf low Status.
*Verif y that the order line workf low is now at the Fulf ill - Def erred activ ity with a status of Def erred. This means that the next steps is to run the
Workf low Background Process.
2. Nav igate to Reports, Requests > Run Requests.
*Run the Workf low Background Process with the f ollowing parameters.
Item Ty pe : OM Order Line
Process Def erred : Yes
Process Timeout : No
3. Go to View > Requests, and v erif y that the Workf low Background Process (WFBP) has completed successf ully. In addition, not ice that the AR
concurrent requests Autoinv oice and Autoinv oice Import Program get kicked of f automatically to import the inv oices into AR. OM inserts inv oice
data into the AR interf ace tables through 'Inv oice Interf ace', which runs in the background (notice the workf low activ ity 'Invoice Interf ace' in the
screenshot f rom Step 4 below). AR picks up the data f rom the interf ace tables through the 'Autoinv oice' concurrent program.
*In case y ou f ind that the inv oice did not get imported into AR (as shown in Step 5 below), run Autoinv oice manually by nav igating to Receiv ables
> Interf aces > Autoinv oice, and selecting the Autoinv oice Master Program.
Enter the f ollowing parameters and submit the concurrent request :
Inv oice Source : ORDER ENTRY
Def ault Date : <today 's date>
(Low) Sales Order Number / (High) Sales Order Number : <y our order#>
Af ter submission of the concurrent request, go to View > Requests.
You should see the Autoinv oice Master Program f ollowed by the Autoinv oice Import Program.
Af ter completion, click on the View Output button f or the Autoinv oice Import Program to check f or the error messages. Autoinv oice needs to be
resubmitted af ter the errors are f ixed.
4. Query the order in the sales order f orm, and go to the lines. Notice the status is now Closed. Note that the Closed status in the order lines
signif ies that OM has successf ully passed the inv oice data into the AR interf ace tables, and does not necessarily signif y that the inv oice has been
successf ully imported into AR (in case there was some error during that process).
*The workf low status f or the order line (go to Tools > Workf low Status) should now show the f ollowing progression.
SQL Tip :
Finding the status and inv oice_interf ace_status_code of the order line
select line_id, open_f lag, f low_status_code, inv oice_interf ace_status_code
f rom oe_order_lines_all
where line_id = 201594;
LINE_ID O FLOW_STATUS_CODE INVOICE_INTERFACE_STATUS_CODE
---------- - ------------------------------ ------------------------------

201594 N CLOSED YES
5. While on the sales order line, click on the Actions button and select 'Additional Line Inf ormation'.
*Go to the Inv oices / Credit Memos tab. If the inv oice data is shown here, this means that the inv oice was created in AR. Click on the Inv oice
Details button to v iew the inv oice.
Here the O2C cy cle end.
Order Management Functional Document
Order Management
1) Oracle Order Management Recommended Setup
Setup involves several phases, including setting up other integrated applications, which include Oracle General Ledger, Oracle
Receivables,and Oracle Inventory.
Some setup steps are optional,depending on whether you have the integrating applications installed and whether you usethe associated
feature. For example, if your business supports drop shipments, you shouldalso setup Oracle Purchasing.
If you are using a multiple organization structure, your system administrator must change the OM: Item
Validation Organization parameter to be visible and updatable at the responsibility level. This change allows
Order Management to default code and revenue account information accurately.
Step 1
Flexfields
Define key and descriptive flexfields to capture additional information about orders and transactions.
Accounting (Oracle General Ledger)
Defining your Accounting key flexfield is part of setting up your sets of books.
Item Catalogs (Oracle Inventory)
If you make entries for items in a standard industry catalog or if you want to group items according to certain
descriptive elements, you need to configure this flexfield. Even if you do not use item cataloguing, you must
enable at least one segment of this flexfield and compile it before you define your items.
Item Categories (Oracle Inventory)
You must set up this flexfield before you define items because all items must be assigned to categories.
Sales Orders (Oracle Inventory)
Use the Sales Orders key flexfield to differentiate sales order transactions that Order Management interfaces
to Oracle Inventory. You must define this flexfield before placing demand or reservations in Order
Management. The profile option OM:Source Code defaults the source code you use in the third flexfield
segment.
Stock Locators (Oracle Inventory)

If you want to track items by a specific aisle or row, use this key flexfield to capture additional information
about inventory stock locators. If you use this flexfield, you must set theOM: Inventory Stock Location profile
option.
System Items (Oracle Inventory)
Before you define items, set up this flexfield in order to record and report item information. The OM: Item
Flexfield profile option needs to be set.
Sales Tax Location (Oracle Receivables)
Use this flexfield to charge your customers for tax based on their shipping addresses.
Territory (Oracle Receivables)
The Territory flexfield can be associated with salespeople, invoices, and customer site addresses. Use it to
record and report territory information.
Descriptive Flexfields
Additional Line Detail Information (Oracle Order Management)
This descriptive flexfield displays any additional line detail information at the time of order entry.
Industry Attribute (Oracle Order Management)
This descriptive flexfield records industry-specific information for items in your order.
Pricing Attributes (Oracle Order Management and Oracle Advanced Pricing)
Pricing attributes modify an item’s pricewithout requiring that you create a new item. For example, you sell computer software and t he
price of the software is different depending on the number of users.You define a pricing attributecalled
Number Of Users. When you enter an order line, the Pricing Attributes flexfield opens a window to capture the
number of users. Order Management uses this information along with the item and unit of measure to derive
the item list price.
The Pricing Attributes descriptive flexfield contains 15 user-definable flexfield segments to be used as pricing
attributes. Once defined, the attributes can be used in the lines block of the Sales Orders window, the Line
Options window, the Shipment Schedules window, the lines block of the Price Lists window, and the Item
Groups window in Order Management; and in the Services and Renew Service windows in Oracle Service.
Step 2
Multiple Organizations
Define multipleorganizations in OracleInventory.
Step 3

Inventory Organizations
Define inventory organizations(warehouses),organization parameters,sub-inventories,and pickingrules in
OracleInventory.
You must define at leastone item validation organization and atleastone organization thatacts as an
inventory sourcefor orders fulfilled internally.If you plan to drop ship some orders, you must also defineat
leastone logical organization for receivingpurposes.Your item validation organization can bethe
same as your inventory sourceor your logical receivingorganization,butyou cannot useone organization for
all three purposes.
Step 4
Profile Options
Define profileoptions to specify certain implementation parameters, processingoptions,and system options.
Some of the profile options are
OM: Allow Negative Pricing
OM: ApplyAutomatic Attachments
OM: Auto schedule
OM: Customer
Step 6
Invoicing
Define invoicinginformation,includingpayment terms, invoicingand accountingrules,Auto Accounting
parameters, territories,and invoicesources.See the followingtopics in the Oracle Receivables User’s Guide for
more information:Payment terms, Invoicewith Rules,Transaction Types, Auto Accounting, Territories,and
InvoiceBatch Sources.
Step 7
Salespersons
Define information on your sales representatives.
Step 8
Tax
Define tax features, such as codes,rates, exceptions, and exemptions.
Step 9

QuickCodes
Define QuickCodes that providecustom values for many lists of values throughout Order Management
Some of the quick codes are,
- Cancellation Codes
Credit Cards
Freight Terms
Hold Types
Note Usage Formats
Release Reasons
Sales Channels
Shipment Priorities
Step 10
Workflow
Define order and lineprocessingflows to meet different order and linetype requirements.
Step 11
Document Sequences (Order Numbering)
Define Document Sequences for automatic or manual numbering of orders.
Step 12
Order Import Sources
Define sources for importingorders into Order Management.
Step 13
Units of Measure
Define the units of measure in which you supply items.
Step 14
Item Information

Define item information,includingitemattribute controls,categories,and statuses.DefiningItem Attribute
Controls,DefiningCategories, and DefiningItem Status Codes.
Step 16
Configurations
Define the configurations thatyou sell.See: Creatinga Bill of Material,OracleBillsof Material User’s Guide.
Step 17
Customer Classes
Define customer profileclasses.See: Defining Customer ProfileClasses:page, Oracle Receivables User’s Guide
.
Step 18
Customers
Define information on your customers. See: Entering Customers, Oracle Receivables User’s Guide.
Step 19
Item Cross References
Define item cross references for orderingby customer partnumber, UPC, or any generic item number.
See: Oracle Inventory’s User’s Guide.
Step 20
Sourcing
Define your sourcing rules for schedulingsupply chain ATP functions.See: OracleAdvanced Supply Chain
Planning User’s Guide.
Step 21
Transaction Types (Order and Line Types)
Define transaction types to classify orders and returns.For each order type, you can assign a defaultpricelist,
defaultingrules,order lines,return lines,linetypes, workflow assignments,payment terms, and freight terms.
See: DefiningTransaction Types
Step 22
Cost of Goods Sold (COGS)

Set up your Cost of Goods Sold Accounting Flexfield combination (COGS Account) in OracleInventory.
See: Oracle Inventory User’s Guide.
Step 23
Processing Constraints
Define processingconstraints to prevent users from addingupdating,deleting, splittinglines,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. See: Defining Processing
Constraints,DefiningValidation Templates,and DefiningRecord Sets
Step 24
Defaulting Rules
Define defaultingrules to determine the sourceand prioritization for defaultingorder information to reduce
the amount of information you must enter manually in the Sales Orders window. See: DefiningDefaulting
Rules
Step 25
Credit Checking
Define your credit checkingrules.See: Automatic Credit Checkingof Orders,DefiningCredit Check Rules,
and Defining Sales CreditTypes
Step 26
Holds
Define automatic holds to apply to orders and returns. See: Defining Holds
Step 27
Attachments
Define standard documents to attach automatically to orders and returns.
Step 28
Freight Charges and Carriers
Define freight charges and freight carriers to specify on orders. See: Defining
Freight Costs and DefiningFreight Carriers, Oracle Shipping Execution User’s Guide.
Step 29

Pricing
Define pricelists for each combination of item and unitof measure that you sell.
Optionally,you can define pricingrules and parameters to add flexibility.
Step 30
Shipping
Define shippingpreferences in OracleShippingExecution. See: Oracle Shipping Execution User’s Guide.
Step 15
Items
Define the items that you sell,as well as container items.
2) Definitions
Account Generator
The Account Generator in OracleOrder Management utilizes OracleWorkflow.You can view and customize
Account Generator processes through the OracleWorkflowBuilder.
Order Management and OracleShippingExecution inserta Costof Goods Sold AccountingFlexfield
combination (COGS Account) for each inventory transaction lineinto OracleInventory via the Inventory
Interface program. You can usethe COGS Account as a basis for costof goods sold analysisin OracleInventory.
The Account Generator dynamically creates a COGS Account to transfer from
Order Management and OracleShippingExecution to OracleInventory for each order and return linewhen it
completes the Inventory Interface cycleaction.You can customize the default process to make your costof
goods sold analysismoremeaningful.
Accounting rules
Auto Invoiceuses to specify revenue recognition schedules for transactions.You can define an accountingrule
where revenue is recognized over a fixed or variableperiod of time. For example, you can define a fixed
duration accountingrulewith monthly revenue recognition for a period of 12 months.
AutoInvoice
A programthat imports invoices,creditmemos, and on account credits from other systems to Oracle
Receivables.
Available To Promise (ATP)
The quantity of current on-hand stock, outstandingreceipts and planned production which has not been
committed through a reservation or placingdemand.

backorder
An unfulfilled customer order or commitment. OracleOrder Management allows you to create backorders
automatically or manually fromreleased order lines.
Base Price
The original pricefor an item obtained from the PriceList; the pricebefore any priceadjustments areapplied.
Also known as ListPrice.
bill of lading
A carrier’s contractand receiptof goods transported from one location to another.
bill of material
A listof component items associated with a parent item and information about how each item relates to the
parent item.
carriers code (SCAC)
The Standard Carrier Alpha Code is required on carrier supplied bills of lading.
category
Code used to group items with similarcharacteristics, such asplastics,metals,or glass items.
category set
A feature in Inventory where users may define their own group of categories. Typical category sets include
purchasing,materials,costing,and planning.
credit check rule
A rulethat defines the components used to calculatea customer’s outstandingcreditbalance.Components
includeopen receivables,uninvoiced orders,and orders on hold. You can includeor exclude components in
the equation to derive credit balances consistentwith your company’s credit policies.
credit memo
A document that partially or fully reverses an original invoiceamount.
cumulative discounts
Discounts whosepercentages are summed up before applyingthe discountarereferred to as Cumulative
Discounts.
customer class

A method to classify and group your customers. For example, you could group them by their business type,
size, or location.You can create an unlimited number of customer classes.
customer profile
A method used to categorize customers based on creditinformation.OracleReceivables uses creditprofiles to
assign statement cycles,dunningletter cycles,salespersons,and collectorsto your customers. You can also
decide whether you want to charge your customers interest. OracleOrder Management uses the order
and total order limits when performing creditchecking.
customer profile class
These allowfor groupingof customers with similar creditworthiness,businessvolume,and payment cycles.
For each profileclass you can defineinformation such as creditlimits,payment terms, statement cycles,
invoicing,and discountinformation.Thecustomer profileclasswhen assigned to a customer provides the
default values for this information.
defaulting rules
Information OracleOrder Management automatically enters depending on other information you enter.
demand class
A demand class may represent a particular groupingof customers,such as government and commercial
customers. Demand classes may also representdifferent sources of demand, such as retail,mail order,and
wholesale.
discount amount
This is the difference between the listpriceand the sellingpricefor the item. If the discountwas specified as
an “amount” discount,then this valuewill notchange even if the pricelistchanges.For example, if Item A’s list
priceis $10,and we have a 20% discount,then the discountamount is $2.If we then change pricelists,and
Item A will cost$20 on the new pricelist,the discountamount for that same 20% discountnow becomes $4. If
however, the discountwas not a percentage and was an “amount” discountof $2, then whether the listprice
for the associated pricelistis $10,$20,or $5, the discountamount will always be$2.
discounts
Is a Modifier type in OraclePricingthatcreates PricingAdjustments which allows PricingEngineto extend a
reduced pricefor an order, specific lineitem,or group of lines.
drop shipment
A method of fulfillingsales orders by sellingproducts withouthandling,stocking,or deliveringthem. The
sellingcompany buys a product from a supplier and has the supplier s hip theproduct directly to customers.
dropship item
An item which is goingto be sourced externally from the vendor directly to our customer.

dunning letters
A letter you send to your customers to informthem of pastdue debit items. OracleReceivables lets you
specify the text and format of each letter. You can chooseto includeunapplied and on-accountpayments.
exchange rate type
A specification of the source of an exchange rate. For example, a user exchange rate or a corporateexchange
rate. see corporate exchange rate, spot exchange rate.
extended price
The extended priceis the costof the line. This is computed by multiplyingthe sellingpriceper unitby the
number of units ordered on that line.Thus, if two of item A cost$10.00 each, the extended priceis $20.00 for
the line.
FIFO costing
Costingmethod where itis assumed that items that were received earliestaretransacted first.
fixed price discount
A discountthat fixes the final sellingpriceof the item so itis not affected by changes to the listpriceof the
item. It is a method of implementing discounts to the listpricewhere the final priceis contractually fixed
regardless of changes to the listprice,as is thecasewith GSA prices.For example, if Item A has a listpriceof
$100,a fixed pricediscountspecifyinga sellingpriceof $90 results in a sellingpriceof $90 even if the listprice
later increases to $110.
freight on board (FOB)
The point or location where the ownership title of goods is transferred from the seller to the buyer.
freight charges
A shipment-related chargeadded duringship confirmation and billed to your customer.
freight terms
An agreement indicatingwho pays the freight costs of an order and when they areto be paid.Freight terms do
not affect accountingfreight charges.
GRN (Goods Received Note)
Goods Received Note. Synonym for receipt or material receipt.
gross weight
The weight of the fully loaded vehicle,container,or item, includingpacked items and packagingmaterial.
GSA (General Services Administration)

GSA (General Services Administration):a customer classification thatindicates the customer is a U.S.
government customer. For products on the GSA pricelist,a fixed pricemust be used, defined on the GSA
contract. The items contained on the GSA pricelistcannotbe sold to commercial customers for the same or
less pricethan the government price.In other terms, the priceoffered to the government must be the
minimum in the market.
GSA Discounts
Discounts thatcan be specifically defined for giving the lowest sellingpriceto some or all of the GSA
customers. A customer classification thatindicates thecustomer is a U.S. government customer and pricingfor
products on the GSA pricesheet should reflectthe fixed pricingof the GSA contract. Whenever a productis on
the GSA pricesheet, itcannot be sold to commercial customers for the same or less pricethan the government
customer.
guarantee
A contractual obligation to purchasea specified amountof goods or services over a predefined period of time.
Inbound/Outbound Lines
In the Order Management schema, lines on a header are either ALL outbound; meaning sales order lines,in
which material on the header is leavingthe warehouse to go to a customer, or they are ALL inbound; meaning
return lines,in which material on the header is arrivingatthe warehouse to be credited back to the
customer. In Order Management, headers can be ‘RETURN’ (all inbound),‘ORDER’ (all outbound),or ‘MIXED’
(both inbound and outbound lines).
Inbound Purchase Order
Inbound PurchaseOrder refers to the action of receivingpurchasinginformation fromcustomers and creating
valid sales orders within OracleOrder Management.
intangible item
A non-physical itemsold to your customers such as consultingservices or a warranty.Intangibleitems arenon-
shippableand do not appear on pick slipsand pack slips.
intermediate ship-to
The delivery point for a shipment prior to an ultimatedestination.
inventory organization
An organization thattracks inventory transactions and balances, and/or thatmanufactures or distributes
products.
invoicing rules

Rules that OracleReceivables uses to determine when you bill your invoices.You can bill In Advanceor In
Arrears.
LIFO costing
Costingmethod where itis assumed that items that were received most recently aretransacted first.
loading order
Determines the order in which items areloaded on a truck for delivery in the requested production sequence.
The loadingorder can be forward,reverse - inverted, or non-inverted.
locator
Physical area within a subinventory where you store material,such as a row, aisle,bin,or shelf.
lockbox
A servicecommercial banks offer corporate customers to enable them to outsource their accounts receivable
payment processing.Lockbox processors setup special postal codes to receive payments, depositfunds and
provideelectronic account receivableinputto corporate customers. A lockbox operation can process millions
of transactions a month.
logical organization
A business unitthattracks items for accountingpurposes but does not physically exist.
LOOKUP
Attributes arevalidated by a lookup type. The lookup code is stored in the attribute, but the code’s translated
meaning will bedisplayed whenever the attribute value is viewed by an end user.
lookup code
The internal name of a valuedefined in an OracleWorkflowlookup type.
lookup type
An OracleWorkflowpredefined listof values.Each valuein a lookup type has an internal and a display name.
modifier
Defines the terms of how OraclePricingwill make adjustments.For example, a modifier can take the form of:
discounts,or surcharges.In OraclePricing,when you setup modifiers,you define the adjustments your
customers may receive. You control the application of modifiers by the pricingengineby also settingup rules
that specify qualifiersand attributes governingtheir use.
modifier list
A groupingof modifiers in OraclePricing.

order category
An Order Transaction Typecan be for any of the followingOrder Categories: ‘ORDER’, ‘RETURN’ or ‘MIXED’.
Line Transaction Types can be for any of the categories: ‘ORDER’ or ‘RETURN’. When an Order is created with a
particularTransaction Type,the Order Category code determines which lines arepermitted for that order. If
the category code is ‘ORDER’, then the order can have only regular Lines.If the category code is ‘RETURN’,
then the order can have only return lines.If the category code is ‘MIXED’, then the order can have both kinds
of lines.
order cycle
A sequence of actions you or Order Management perform on an order to complete the order. An order cycle
lets you define the activity an order follows frominitial entry through closing.You can define as many order
cycles as your business requires.Order cycles areassigned to order types.
Order Import
Order Import is an OracleOrder Management’s Open Interface that imports orders from an internal or
external source,Oracleor Non-Oraclesystem, which performs all the validationsbeforeimporting the order.
Order Processing Cycle
A sequence of actions you or Order Management performs on an order to complete the order. An order cycle
lets you define the activity an order follows frominitial entry through closing.Each order linegoes through a
cycleappropriateto the order type, linetype (standard,return or internal) and item type (standard,model,
shippable,transactable,etc.) of that line.
payment terms
The due date and discountdate for payment of an invoice.For example, the payment term ’2% 10, Net 30’lets
a customer take a two percent discountif payment is received within 10 days,with the balancedue within 30
days of the invoicedate.
pick release
An order cycleaction to notify warehouse personnel that orders areready for picking.
pick release rule
A user-defined set of criteria to define what order lines should beselected duringpick release.
pick slip
Internal shippingdocument pickers useto locate items to ship for an order. If you use standard pick slips,each
order will haveits own pick slip within each pickingbatch.If you use the cons olidated pick slip,the pick slip
contains all orders released in thatpickingbatch.
pick slip grouping rule

Criterion for grouping together various types of pick slips.The ruledictates how the Pick Slip Report program
groups released lines into different pick slips.
pick-to-order
A configure-to-order environment where the options and included items in a model appear on pick slips and
order pickers gather the options when they ship the order. Alternative to manufacturingthe parent item on a
work order and then shippingit.Pick-to-order is also an itemattribute that you can apply to standard,model,
and option class items.
picking rule
A user-defined set of criteria to define the priorities Order Management uses when pickingitems out of
finished goods inventory to ship to a customer. Pickingrules aredefined in OracleInventory.
PO Change Request Vs. SalesOrder
The term ‘sales order’refers to the sales order data as stored in the baseOracleOrder Entry tables.The term
‘PO Change Request’ or ‘PO Change Request process’refers to the pending sales order data as stored and
processed in this new change order process.Accepted PO Change Request resultin an updated Sales Order in
the baseOracleOrder Management tables.There may be more than one pending change order request in the
process for a given purchaseorder.
price adjustment
The difference between the listpriceof an item and its actual sellingprice.Priceadjustments can have a
positiveor negative impacton the listprice.Priceadjustments that lower the listpricearealso commonly
aknown as discounts.Priceadjustments can be for an order lineor the entire order.
price breaks
Discounts for buyinglargequantities or values of a particularitemof a particular UOM,item category or any
enabled pricingattribute.
price list
A listcontainingthe basesellingpriceper unitfor a group of items, item categories or serviceoffered. All
prices in a pricelistarefor the same currency.
pricing components
Combinations of pricingparameters you use when definingpricingrules.Pricingcomponents can be made up
of one or multiplepricingparameters.
pricing contracts
Used to setup a contractwith associated contractlines which specifies theitems that customer will purchase.
Usingthe contract lines users will beableto setup items , their price,effective dates and pricebreaks for that
item. Users will beableto have multipleversions of the contractand contract lines with different effective
dates.

pricing information
Information that pricing calculation isbased on such as pricingdate,pricelistand unitprice.
pricing parameters
A parameter you use to create components to be used in a pricingrule.Valid pricingparameters include
segments of your item flexfield or PricingAttributes descriptiveflexfield.
pricing rule
A mathematical formula used to define item pricing.You create a pricingruleby combiningpricing
components and assigninga valueto the components. OracleOrder Management automatically creates list
prices based on formulas you define.
profile option
A set of changeableoptions that affect the way your applicationsrun.In general,profileoptions can be set at
one or more of the followinglevels:site,application,responsibility,and user.
proof of delivery
A document that the customers receivingdock signs to show how much they received. It may be used as the
basis of billingby a haulagecompany.
QuickCodes
Codes that you define for the activities and terminology you use in your business.For example, you can define
QuickCodes for personal titles,(for example, ‘Sales Manager’) so you can refer to people usingthese titles.You
can define QuickCodes for sales channels so thatyou can specify the various sales channelsused for different
kinds of orders. An OracleAssets feature that allows you to enter standard
descriptions for your business.You can enter QuickCode values for your Property Types, Retirement Types,
Asset Descriptions,Journal Entries,and Mass Additions Queue Names.
return material authorization (RMA)
Permission for a customer to return items. Receivables allows you to authorizethe return of your sales orders
as well as sales madeby other dealers or suppliers,as longas theitems are partof your item master and price
list.
scheduling
Order schedulingincludesassigningdemand or reservations,warehouses,shipment dates, and lots or
subinventories to an order line.
selling price
The sellingpriceis theunit costfor a particularitem. Thus, if two of item A cost$10.00 each, the sellingpriceis
$10.00 for each unit.

set of books
A financial reportingentity that partitions General Ledger information and uses a particular chartof accounts,
functional currency,and accountingcalendar.This conceptis the same whether or not the Multi -organization
supportfeature is implemented.
shippable item
An item with the Shippableinventory item attribute set to Yes, indicatingthatthis item will appear on pick
slips and pack slips.
shipping documents
Shippingrelated reports, such as the Bill of Lading,Commercial Invoice,MailingLabel,Pack Slip,VehicleLoad
Sheet Summary, and Waybill.
territory flexfield
A key flexfield you can use to categorize customers and salespersons.
trip stop
A location atwhich the trip is due for a pick-up or drop-off.
Workflow
This determines the header flow for an order transaction type or lineflows possiblefor a linetransaction type.
There can be only one header flow associated with an Order Transaction Type but a lineTransaction Typecan
be coupled with different Order Types and Item Types and there can be different flow couplings for the
permitted Transaction Type, Item Type combinations.
Workflow Engine
The OracleWorkflowcomponent that implements a workflow process definition.The WorkflowEngine
manages the state of all activities,automatically executes functions,maintains a history of completed
activities,and detects error conditions and starts error processes.TheWorkflow Engine is implemented in
server PL/SQL and activated when a call to an engine API is made. See Account Generator, activity, function,
item type.
Standard Order Flow
Create sales order
Schedule it
Book it
Pick release
Ship confirm

Scheduling – Auto/Manual.
Available –isthe actual available
Qty on Hand – isthe actual available +ReservedItems+unreservedItems
Reservable –isthe reserveditems
Order header Status – Entered, Booked
Order Line status – Entered, awaiting status, picked
Pick Release Order status – Unreleased, All, Back ordered
Ship Transaction Status – Staged, not staged, back ordered, Shipped, Not Shipped, Cancel
Public Table List
Table Name Description
AK_FOREIGN_KEYS Foreign keys for an object
AK_FOREIGN_KEY_COLUMNS Links an attribute to a foreign key
AK_OBJECTS Defines an object and the application id of the owner of the
object
AK_OBJECT_ATTRIBUTES Links an attribute to an object - Contain API packages
AK_UNIQUE_KEYS Unique keys for an object
AK_UNIQUE_KEY_COLUMNS Links an attribute to a unique key
BOM_INVENTORY_COMPONENTS Bill of material components
FND_APPLICATION Applications registered with OracleApplication ObjectLibrary
FND_CONCURRENT_REQUESTS Concurrent requests information
FND_CURRENCIES Currencies enabled for use at your site
FND_DOCUMENTS Documents
FND_DOCUMENT_SEQUENCES Document sequences registered with Oracle Application ObjectLibrary
FND_DOC_SEQUENCE_ASSIGNMENTS Assigns a sequence to a document
FND_LANGUAGES National dialects

FND_LOOKUP_VALUES Quick Code values
FND_RESPONSIBILITY Responsibilities
FND_USER Application users
GL_DAILY_CONVERSION_TYPES Foreign currency daily conversion rate
HR_ALL_ORGANIZATION_UNITS Organization unit definitions
HR_ORGANIZATION_INFORMATION Additional attributes of an organization,dependent on class
or organization information type
MTL_CUSTOMER_ITEMS Customer item Information
MTL_CUSTOMER_ITEM_XREFS Relationshipsbetween customer items and inventory items
MTL_LOT_NUMBERS Lot number definitions
MTL_RELATED_ITEMS Item relationships
MTL_SYSTEM_ITEMS_B Inventory item definitions
MTL_UNITS_OF_MEASURE_TL Unit of measure definitions
OE_ACTIONS_IFACE_ALL This is a multi–org table for sales order actions (holds, booking etc.) open
interface.
OE_ACTION_PRE_REQS A temporary table used duringthe WF upgrade into R11i.
OE_AGREEMENTS_B stores all information aboutpricingagreements.
OE_AGREEMENTS_TL stores the translatablecolumn,i.e. name of the agreement, in each of the available
languages in the database.
OE_ATTACHMENT_RULE_ELEMENTS stores the attributes and attribute values that make up the attachment
rule.
OE_CREDITS_IFACE_ALL This is a multi–org tablefor sales order/linecredits open interface
OE_CREDIT_CHECK_RULES This tablestores information about the creditcheck rules.
OE_CUST_ITEM_SETTINGS OE_CUST_ITEM_SETTINGS stores the shipment and return tolerances for
customer–item, item–site and item combinations
OE_CUST_TOTAL_AMTS_ALL Stores the accumulated order valuefor a customer over three periods
OE_DEF_ATTR_CONDNS Associates the defaultingcondition,defined at the entity level , to a specific attribute

OE_DEF_ATTR_DEF_RULES Defaultingrules for an attribute for a defaultingcondition.
OE_DEF_CONDITIONS This tablestores defaultingconditions for an entity
OE_DROP_SHIP_SOURCES This table stores relationship between Order Lines in oe_order_lines_all table
and associated oracle purchasing requisitions in PO_REQUISITIONS_ALL and Oracle purchasing purchase
orders in PO_LINES_ALL.
OE_EVENT_ATTRIBUTES This tablestores order header and lineattributes which trigger repricing,when
modified, at various pricingevents.
OE_HEADERS_IFACE_ALL This is a multi–org table for sales order headers open
interface. OE_HEADER_ACKS This tables stores information about the acknowledgements for Order Headers.
OE_HOLD_AUTHORIZATIONS Stores information aboutwho has the authority to apply and releaseholds.–
Retrofitted
OE_HOLD_DEFINITIONS This tablestores information abouthold name and its validity
period. OE_HOLD_RELEASES This tables stores information aboutall the holds that has been released.
OE_INVOICE_NUMBERS This tableis used for generating invoicenumbers based on the delivery name.
OE_ITEM_CUST_VOLS_ALL This tablestores accumulated order quantity and valuefor an item of a customer
over three periods.
OE_LINES_IFACE_ALL This is a multi–org table for sales order lines open interface.
OE_LINE_ACKS This tablestores information about the acknowledgements for Order Lines.
OE_LINE_SETS This tablestores information about Sets.
OE_LOTSERIALS_IFACE_ALL This is a multi–orgtable for return linelotserials open
interface. OE_LOTSERIAL_ACKS This tablestores information about the acknowledgements for lotserials
OE_LOT_SERIAL_NUMBERS This tablestores customer reported lotserial numbers for lot and / or serial
number controlled return lines.
OE_ORDER_HEADERS_ALL stores header information for orders in Order Management.
OE_ORDER_HOLDS_ALL This table stores information of all the orders and lines that are on hold and the link
to hold sources and hold releases.
OE_ORDER_LINES_ALL stores information for all order lines in Oracle Order Management.
OE_ORDER_LINES_HISTORY stores history of quantity changes on order lines.
OE_ORDER_PRICE_ATTRIBS This table stores pricing attributes and asked for promotions, deals and
coupon number entered by the user.

OE_ORDER_SOURCES Feeder System Names that create orders in Order Management tables.
OE_PRICE_ADJS_IFACE_ALL This is a multi–org open interface table for sales order/line price
adjustments.
OE_PRICE_ADJUSTMENTS This table is used to store price adjustments that have been applied to an order
or a line.
OE_PRICE_ADJ_ASSOCS This tablestores the association between Order lines and priceadjustments and
also between priceadjustments
OE_PRICE_ADJ_ATTRIBS This table stores information on qualifiers and pricingattributes,which the
correspondingpriceadjustmentlinequalified for.
OE_PRICE_ATTS_IFACE_ALL This is a multi–orgInterface table to populate OE_ORDER_PRICE_ATTRIBS.
OE_PURGE_ORDERS stores the order details for orders included in a purge set.
OE_RESERVTNS_IFACE_ALL This is a multi–orgtable for inventory reservations open
interface. OE_SALES_CREDITS This table stores information aboutsales credits.
OE_SALES_CREDIT_TYPES This tablestores information about sales credittypes.
OE_SETS OE_SETS stores information on linesets.
OE_SYSTEM_PARAMETERS_ALL This table is used for storingall systemparameter information.
OE_TRANSACTION_TYPES_ALL This table stores information about the order and line transaction types
OE_TRANSACTION_TYPES_TL This is a mult–lingual tablefor OE_TRANSACTION_TYPES_ALL table.
OE_WORKFLOW_ASSIGNMENTS This tableassociates assignments to order types and linetypes.
ONT_PRT_MARGIN_ANALYSIS contains margin analysisinformation grouped by customer, item, territory, and
sales person for three different time periods,lastweek, last30 days,and last90 days
PO_DISTRIBUTIONS_ALL Purchaseorder distributions
PO_HEADERS_ALL Document headers (for purchaseorders,purchaseagreements, quotations,RFQs)
PO_INTERFACE_ERRORS Requisition importinterfaceerrors
PO_LINES_ALL Purchasedocument lines (for purchaseorders,purchaseagreements, quotations,RFQs)
PO_LINE_LOCATIONS_ALL Document shipment schedules (for purchaseorders,purchaseagreements,
quotations,RFQs)
PO_REQUISITIONS_INTERFACE_ALL Requisition Import interface table
PO_REQUISITION_HEADERS_ALL Requisition headers

PO_REQUISITION_LINES_ALL Requisition lines
PO_REQ_DISTRIBUTIONS_ALL Requisition distributions
QP_LIST_HEADERS_B QP_LIST_HEADERS_B stores the header information for all lists.Listtypes can be, for
example, PriceLists,DiscountLists or Promotions.
RA_BATCH_SOURCES_ALL Sources of invoice, credit memo and commitments
RA_CUSTOMER_TRX_LINES_ALL Invoice, debit memo, chargeback, credit memo and commitment lines
RA_CUST_TRX_TYPES_ALL Transaction type for invoices, commitments and credit memos
RA_RULES Invoicing and accounting rules
RA_SALESREPS_ALL Information about salespeople
RA_TERMS_B Payment Term information
RA_TERMS_TL Multi–lingual support (MLS) for Payment Terms
RCV_SHIPMENT_LINES Receiving shipment lineinformation
WF_ITEM_TYPES Item type definition
WSH_FREIGHT_COSTS
WSH_NEW_DELIVERIES
Pricing
QP_ATTRIBUTE_DEFNS QP_ATTRIBUTE_DEFNS is the table on which the Qualifier
and PricingAttribute DescriptiveFlexfields arebased.Itis used for the entity and attribute definiton in
attribute sourcing.
QP_COUPONS QP_COUPONS stores any Coupons which have been issued.
QP_EVENT_PHASES QP_EVENT_PHASES stores the mapping between pricingevents and pricingphases.
QP_LIST_HEADERS_B QP_LIST_HEADERS_B stores the header information for all lists.Listtypes can be, for
example, PriceLists,Discount
QP_LIST_HEADERS_TL QP_LIST_HEADERS_TL stores the translatablecolumns,nameand description of the
list,in each of the availablelanguages in the database.
QP_LIST_LINES QP_LIST_LINES stores all listlinesfor listsin
QP_LIST_HEADERS_B. QP_PRICE_FORMULAS_B QP_PRICE_FORMULAS_B stores the pricingformula header
information.

QP_PRICE_FORMULAS_TL This table stores the translatablecolumns,name & description of the pricing
formulas,in each of the availablelanguages in thedatabase.
QP_PRICE_FORMULA_LINES QP_PRICE_FORMULA_LINES stores each component that makes up the formula.
QP_PRICE_REQ_SOURCES QP_PRICE_REQ_SOURCES stores the mappingbetween PricingRequest Types and
Source Systems.
QP_PRICING_ATTRIBUTES QP_PRICING_ATTRIBUTES stores product information and pricingattributes.
QP_PRICING_PHASES QP_PRICING_PHASES stores all pricingphases.
QP_QUALIFIERS QP_QUALIFIERS stores qualifier attributeinformation.
QP_QUALIFIER_RULES QP_QUALIFIER_RULES stores the header information for all qualifier rules
QP_RLTD_MODIFIERS QP_RLTD_MODIFIERS stores the relationship between modifier
lines.QP_UPGRADE_ERRORS QP_UPGRADE_ERRORS holds details of the errors which occured in upgrading
pricingdata.
RA_RULES Invoicingand accountingrules
RA_SALESREPS_ALL Information about salespeople
RA_TERMS_B Payment Term information

Order to cash flow cycle in order management in detail

More Related Content

What's hot (20)

Similar to Order to cash flow cycle in order management in detail (20)

Recently uploaded (20)

Order to cash flow cycle in order management in detail