Sei sulla pagina 1di 61

Posted on December 3rd, 2008 by Sanjit Anand |

Print This Post |

Email This Post

How Inventory Passes Journals To General Ledger (GL)


Inventory Transactions transfer to GL normally done by Program called INCTGL.
The accounting information related to
transactions in INV module is
transferred to GL by running the
Transfer Transactions to GL
concurrent program. This is part of
Period End Process' . However, you
can run explicitly any time during an
open period. When you run this
process and in case if more than one
period is open, all the transactions
from the earliest open period to the
date up to which the process is run
(Transfer Date) are considered for
transfer to GL.
When you run this program all the accounting information is inserted into gl_interface table.
Journal Import and Post Journals processes in Oracle General Ledger can then be used to post
the information in General Ledger.
The level of detail that is transferred to GL for the accounting information related to these
transactions depends on the value chosen in the Organization Parameters Screen
Navigation: Oracle Inventory > Setup > Organization > Parameters
Each parameter has there own significance.
1. Organization Code : This is one of inventory organization, for which the gl transfer has to
be done.
2. Date :A date in any open period.
3. Current Period
4. GL Description
The possible values for the Transfer to GL field (in Organization Parameters Screen) are
Detail, Summary, None.

When Summary is selected :The accounting information pertaining to the transactions is


summarized and the summary entries are posted to GL. One of the advantage of running
the process in 'Summary' mode over 'Detail' mode is minimising the posting times.
When Detail is selected :The detailed accounting entries are transferred to GL. In this
case, the posting times are larger due to a larger number of records. The advantage of this

mode is creation of detailed accounting records in GL for every transaction in


Inventory/WIP.
When none is selected: This case no transfer of accounting information to GL is done
for this organization.

Running Transfer to GL process


You can run Transfer Transactions to GL process can be run from Oracle Inventory
Accounting Close Cycle .. General Ledger Transfers
Technical Details
These are the tables which get affected By transfer Program.

GL_INTERFACE : Based out of Program logic, new row inserted into this table. The
connecting link are established by these columns.GROUP_ID, REFERENCE21,
REFERENCE22,ACCOUNTING_DATE,
USER_JE_CATEGORY_NAME,GL_SL_LINK_TABLE
o Action on this table :Insert
MTL_TRANSACTION_ACCOUNTS : Mtl_transaction_accounts holds the accounting
information for each
material transaction in mtl_material_transactions.
o Action on this table :Select/Update
WIP_TRANSACTION_ACCOUNTS :This table stores the accounting information for
each resource transaction in wip_transactions.
o Action on this table :Select/Update
MTL_PARAMETERS :This table maintains a set of defaults and controls like general
ledger accounts; locator, lot, and serial controls; inter-organization options; costing
method; etc. for each organization defined in Oracle Inventory.
o Action on this table :Select
ORG_GL_BATCHES :This table holds history rows for every batch of transactions that
have been interfaced to the gl_interface table.
o Action on this table :Insert/Delete/Update
ORG_ACCT_PERIODS :This table holds the open and closed financial periods for
organizations.
o Action on this table :Select
ORG_ORGANIZATION_DEFINITIONS : Defination of the Org is derived from this
table
o Action on this table :Select
GL_SET_OF_BOOKS : Table holds the setof book data used for joining purpose.
o Action on this table :Select

Query for Subledger Transfer to GL

If you want to get details of different journals transferred to GL, use this to get the result. You
can also fine tune with period , currency or clearing company code or Journal Type.
Here is the query:
<pre>
SELECT

gjh.period_name
"Period name"
,gjb.name
"Batch name"
,gjjlv.header_name
"Journal entry"
,gjjlv.je_source
"Source"
,glcc.concatenated_segments "Accounts"
,mmt.subinventory_code
"Subinventory"
,glcc3.segment4
"Costcenter"
,gjjlv.line_entered_dr
"Entered debit"
,gjjlv.line_entered_cr
"Entered credit"
,gjjlv.line_accounted_dr
"Accounted debit"
,gjjlv.line_accounted_cr
"Accounted credit"
,gjjlv.currency_code
"Currency"
,mtt.transaction_type_name "Transaction type"
,TO_CHAR(mta.transaction_id)"Transaction_number"
,mta.transaction_date
"Transaction_date"
,msi.segment1
"Reference"
FROM apps.gl_je_journal_lines_v gjjlv,
gl_je_lines gje,
mtl_transaction_accounts mta,
mtl_material_transactions mmt,
mtl_system_items_b msi,
gl_je_headers gjh,
gl_je_batches gjb,
apps.gl_code_combinations_kfv glcc,
apps.gl_code_combinations_kfv glcc2,
mtl_secondary_inventories msin,
mtl_transaction_types mtt,
MTL_SECONDARY_INVENTORIES cost,
gl_code_combinations glcc3
WHERE
gjjlv.period_name BETWEEN 'NOV-2008' AND 'DEC-2008'
AND
gje.code_combination_id = gje.code_combination_id
AND
gjjlv.line_je_line_num = gje.je_line_num
AND
gl_sl_link_table
= 'MTA'
AND
gjjlv.je_header_id = gje.je_header_id
AND
mmt.inventory_item_id = msi.inventory_item_id
AND
gje.je_header_id = gjh.je_header_id
AND
gjh.je_batch_id = gjb.je_batch_id
AND
mmt.organization_id
= msi.organization_id
AND
mmt.organization_id
= msin.organization_id
AND
mmt.subinventory_code= msin.secondary_inventory_name
AND
mta.gl_sl_link_id= gje.gl_sl_link_id
AND
mta.reference_account = glcc.code_combination_id
AND
msin.expense_account = glcc2.code_combination_id
AND
mmt.transaction_id = mta.transaction_id
AND
mtt.transaction_type_id = mmt.transaction_type_id
AND
cost.organization_id(+) = mmt.organization_id
AND
cost.secondary_inventory_name(+) = mmt.subinventory_code
AND
glcc3.code_combination_id(+) =

cost.expense_account

Posted in Oracle Order Management | 1 Comment

Internal versus External Drop-Ship: Whats the


difference?
Posted on September 15th, 2008 by Sanjit Anand |

Print This Post |

Email This Post

Difference between "Internal" and "External" Drop-Ship


In Oracle Context External Drop-Shipping means your Oracle Order Management uses purchase
orders to outside suppliers that are automatically generated from sales orders for goods supplied
directly from the supplier. The external supplier ships the goods directly to the 3rd Party
customer and confirms the shipment through the use of an Advanced Shipment Notice(ASN).
You should take a note,Oracle uses this ASN to record a receiving transaction into inventory
followed by an immediate logical shipping transaction. From these transactions, conveyance of
title takes place and the customer can be invoiced and the suppliers invoice can be processed.
where as Internal context Drop-Shipping functions in a similar fashion. The key difference is
that no inventory transactions take place on the books of the selling operating unit; transfer of
ownership of the goods from shipper to seller to customer with the only physical movement of
the goods being out of the shipping organization.
Read the rest of this entry
Posted in Oracle Order Management | 5 Comments

Drop Shipment Functional Setup and flow


Posted on September 13th, 2008 by Sanjit Anand |

Print This Post |

Email This Post

A Drop Shipment occurs when a customer order is sourced from and delivered by a supplier.
Order Management sends information to the Purchasing Application to create that PO, and then
when that PO is received (to indicate shipment from the supplier to your customer), the order
line is automatically updated to indicate that it was fulfilled.
In this process, the company running Order Management is modeled as the company to whom
the end customer places the original order.

Drop Shipment - Setup


You need to make sure these are attribute setup Correctly:

Item Attributes

Purchased : Enabled
Purchasable : Enabled
Transactable : Enabled
Stockable : Optional
Reservable : Optional
Inventory Item : Optional
Customer Ordered : Enabled
Customer Order Enabled : Enabled
Internal Ordered : Disabled
OE Transactable : Enabled
Shippable : Optional

And ,your do set up for Order Source Type as External

Drop Shipment Your Setup checklist

Ensure you have created your Order Management Transaction Types and linked your
Transaction Types to order and line workflows that support drop shipments.
Ensure the Oracle Workflow Background Engine is running.
Ensure all Drop ship locations you will use to perform drop shipments have the Ship To
Site and Receiving Site defined.
Ensure you have defined the Internal Ship To Locations for your drop shipment
customers (Oracle Receivables Standard Customer window, Business Purpose Details
Tab).
Ensure your standard items have an associated List Price defined within your PO
Inventory organization (Oracle Payables Financial Options window, Supplier-Purchasing
Tab).

Drop Shipment - Process Steps

Create a Sales Order with line where the line source is External
Book and Schedule the Sales Order
Run Requisition Import Process
Now the line status will be in Awaiting Receipt
Login to the Receiving Organization (Purchasing) who has been setup as an Approver
Run Requisition Import
Create Purchase Order from the Requisition
Approve the PO
Receive the full quantity
Run Auto Invoice

Verify Invoice in Sales Order

Check the details here .


Things not to forget in a DropShipment

Release 11i/12 does not support Drop Shipment across operating units.
Blanket PO's will not used with Drop Shipment , the reason the PO must be created when
OM notifies PO that a Drop Ship order has been created.
You can't cancelled Drop Shipments once Oracle Purchasing obtains the receipt.
Standard Items can be used for Drop Shipment.
In 11i, PTO's and ATO's cannot be drop shipped

Similar Post on Drop Shipment

Understand Drop Shipment in Order Management?


Understand Drop Shipment in Order Management? -Part II
Drop Shipment, BackOrders and Back to Back Order
Drop Shipment - Functional Setup and flow

Posted in Oracle Order Management | 3 Comments

Drop Shipment, BackOrders and Back to Back Order

Posted on April 11th, 2008 by Sanjit Anand |

Print This Post |

Email This Post

This was yet another query asked by one of the reader..so thought to combine in a post so that
others can also understand.
Lets try to understand these key terms from Oracle Apps Product side:
Back Orders

The Oracle "term" backorder is a "status" on the order line or delivery line
indicating that you have tried to release an order for picking in your warehouse,
but that the pick release was UNSUCCESSFUL because there was no available
inventory.(Backorder can be partial or complete). The Oracle term backorder does
NOT mean that you have open purchase orders for the out-of-stock item from
your vendors.
The term backorder is also used in business a little differently than in Oracle. The
term "An item is on backorder" usually means that the item is not in stock, but the
shipping company has already placed purchase orders from their suppliers to
restock the item.

Back Order is when you do not fulfill the Sales Order, or if the inventory is out of
stock for delivery to customer.

Drop Shipment

Drop shipment on the other hand is a method of order fulfillment where the
organization taking the order does NOT maintain their own inventory for the
drop-shipped product, but fulfill their orders through 3rd party vendors who
directly ship to the end customer ordering the product.

For example,

A orders item x from B


B orders item x from C
C ships Item x to A.
B bills A for the order, C bills B for the order

Back to Back Orders


In Back to Back order the shipment process is also completed through OM as a standard order
after the item is received against a PO.
What is the major difference between drop shipment and back to back order ?

In B2B the source will be internal but the item would be procured after the order is
created or after the demand is made.
In Drop Ship the source will be external
In Drop Ship orders, material is directly shipped to the customer from the supplier.
Thus, inventory is not affected. In this case, only logical receiving is done. But in
the case of Back-to-Back orders, material is taken from inventory.
Drop Ship orders may have many Purchase Orders connected to them. In Back-toBack orders one PO is tied to one Sales Order.

More on Drop Shipment & Back to Back Orders(Functional)


High Points for EBS Base Functionality for Drop Shipment

Drop shipment order processing in EBS is managed using workflow


Drop ship functionality is based on source type of an order line (Internal/External)
You can automate your PO/BPA release creation based on ASL/sourcing rule
information
Drop ship process uses standard OM workflows.
You can use Sales order Purchase order discrepancy report to identify discrepancies
between the OM and the PO
There is a links OM and PO to provide visibility through entire supply chain Flow.

The entire Drop shipment process flow can be best understood as figure below:

Points for Implementation Considerations

Order line attribute: Source Type (need to be external). You can be defaulted from item
or order type
o Menu -> Responsibility Order Entry Super User/setup/Orders/Types
o Setup an order type using the cycle defined in the previous step (a),an order
number source, a valid standard value rule set.
Item attributes (OM and Purchasing)

You need to do the setup for these attributes:


-Purchased (PO) Enabled
-Purchasable (PO) Enabled

-Transactable (INV) Enabled


-Stockable (INV) Optional
-Reservable (INV) Optional
-Inventory Item (INV) Optional
-Customer Ordered (OE) Enabled
-Customer Orders Enabled (OE) Enabled
-Internal Ordered (OE) Disabled
-Internal Orders Enabled (OE) Disabled
-Shippable (OE) Optional
-OE Transactable (OE) Enabled

Setup requisition import parameters


You can also use grouping by Vendor
You can also set the multiple distributions set to No
ASL and/or Sourcing rule relationship need to be setup for Automatic PO creation
Oracle recommends using a logical organization for drop shipment. Exclude this
organization for planning purposes. It can be worked around using non nettable Dropship
subinventory

Back to Back Order


As mention above this is ability to create specific supply orders for customer sales orders.
These are main features avaible in EBS

Designate specific items as B2B orderable


Enter sales order lines for these items, and have the supply automatically created via a
requisition
Have the requisition converted into a Purchase Order or a release of a blanket Purchase
Order
View the requisition number or PO number and its status from the Sales Order (using
reservation details window)
Reserve the supply from the Requisition to the PO and finally to the Sales Order once the
PO is received
Pick, ship and finally invoice the customer for the product.
Note to Buyer's field in the requisition captures the Sales order information
Line status information shows the progress of the order
PO Req Created
PO Req Requested
PO Created
PO Received
If line is manually reserved it progresses to "Awaiting Shipping"
Changes and Cancellations on sales orders:
o Reservation is changed
o Notification sent to Buyer

Hope this makes a clarity on topics.


Posted in Oracle Order Management | 11 Comments

Understand Drop Shipment in Order Management? -Part


II
Posted on April 5th, 2008 by Sanjit Anand |

Print This Post |

Email This Post

Most of us heard about e-commerce site like ebay,ubid.com,amazon,com which is very common
place in advance countries like USA, UK & Singapore where people can sell or buy there
product. Have you ever think ,what is similar situation in real world , when the the word 'drop
shipment' comes to your mind. ......a business situation when the retailer or trader has no stock
himself, instead giving customer details directly to the seller, and then saler than fills the order
and send it to customer directly.How its sounds...
Drop shipping still remains a hot topic among SCM practitioner and apps Implementer , but even
though it has many benefits, it isnt the best option for every business. I am not going to walk
through the pros and cons of the process , rather would like to walk through some of the key
steps and processes which exist in real world which is important to understand the concept which
helps during configuration with the product.

As in one of the last post , we have seen drop shipments is a method of fulfilling sales orders by
selling products without the order taker handling, stocking, or delivering the products. The seller
buys a product and the supplier ships the product directly to the sellers customer .
In other word ,drop Shipment is a process where the customer places a purchase order on a
company and this company instructs its supplier to directly ship the items to the customer.
Drop shipments are done because of the following reasons:

Customer requires an item that is not normally stocked


Customer requires a large quantity of the item which is not available with you
It is more economical when the supplier ships directly to the customer

Types of drop shipment


If you see the real world scenarios this can be best categorize as mainly under three heads as:

Type 1 : Full Drop Shipment

Where the seller sends the purchase order to the supplier for the full quantity that the customer
had ordered

Type 2 : Normal Shipments and Partial Drop Shipment

Under this scenario, If the seller has only part of the quantity available for shipping to the
customer, then that quantity is shipped; a purchase order is created for the remaining quantity
which the seller was not able to fulfill. This is typically true for single based item.

Type 3 : Normal Shipments and Full Drop Shipment

In this scenario, the seller ships some goods from inventory to the customer, and the other goods
are always shipped from an external source (supplier).
Process Flow for Drop Shipment (Adopted from User Guide)

Drop Shipments for Standard Items


1.
2.
3.
4.
5.
6.

Enter an order for drop ship item


Book the order
Run Requisition Import
Create a purchase order from the requisition
Approve the purchase order
Receive against the purchase order

Forward drop ship flow for ATO model


1. Enter a sales order for your drop shipped ATO model.
2. Select your options.
3. Schedule and book order (schedule date should default to request date for all
lines).
4. Create you configured item by progressing your order ATO Model line or
running the Autocreate Configuration batch process.
5. Verify order and line status.
6. Create a supply order (dropship requisition) by progressing your
configuration item line or running the Autocreate Dropship Requisition batch
process
7. Run the Oracle Purchasing Requisition Import to create a purchase
requisition.
8. Create a purchase order for the requisition.
9. Approve the purchase order.
10. Receive the purchase order.
Forward drop ship flow for ATO Item
1. Enter a sales order for your drop shipped ATO item
2. Schedule and book order (schedule date should default to request date for all
lines).
3. Create a supply order (dropship requisition) by progressing your
configuration item line or running the Autocreate Dropship Requisition batch
process.
4. Run the Oracle Purchasing Requisition Import to create a purchase
requisition.
5. Create a purchase order for the requisition.
6. Approve the purchase order.
7.
Receive the purchase order.
Non-SMC PTO model with drop shipped standard options
1. Enter a sales order for your PTO model.
2. Select options; source type on the components will default.
3. Schedule and book the order.

4.
5.
6.
7.

Run requisition import to create a purchase requisition.


Create a purchase order for the requisition.
Approve the purchase order.
Receive the purchase order.

Drop Shipment (Technical)


This section is going to help those who asked to provide some more granular details for drop
shipment some time back.
As discussed above and in last post drop shipment is the process by which an organization takes
orders from their customer and gets it fulfilled by a 3rd party. The selling organizatoin places a
purchase order to teh 3rd party (supplier) who ships the ordered products to the end customer
directly. There are a large number of tables that contain data related to drop ship orders. For
example:

oe_order_headers_all and lines_all (order info)


po_requisition_lines_all, headers_all etc.( req. info)
po_headers_all, lines_all (po info)
oe_drop_ship_sources_all (this table contains the link between the req, po and the
original order)

Moreover, there are many more tables involved in this therefore its better to have a
understanding by corresponding ER diagram.

There is always a need to develop some of the custom report, therefore understanding of
understanding table is very very important. Here are the same of underline tables details.

PO_LINE_LOCATIONS_ALL
o This table stores document shipment schedules for purchase orders, purchase
agreements, quotations, and RFQs.
PO_LINES_ALL
o This table stores purchase document lines for purchase orders, purchase
agreements, quotations, and RFQs.
PO_HEADERS_ALL
o This table stores document headers for purchase orders, purchase agreements,
quotations, and RFQs.
PO_DISTRIBUTIONS_ALL
o This table stores purchase order distributions.
PO_REQUISITION_HEADERS_ALL
o This table stores requisition headers.
PO_REQUISITION_LINES_ALL
o This table stores requisition lines.
PO_REQ_DISTRIBUTIONS_ALL
o This table stores requisition distributions.
PO_REQUISITIONS_INTERFACE_ALL
o This is the Requisition Import interface table.
OE_ORDER_LINES_ALL
o This table stores information for all order lines in Oracle Order Management.
OE_DROP_SHIP_SOURCES
o This table stores relationships 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.
RCV_SHIPMENT_LINES
o This table stores receiving shipment line information.

Drop Ship @Release 12


There are no Changes in R12 for Drop Ship Flow same as R11 only
Date flow for Drop Shipment

Understand Drop Shipment in Order Management?

Reference Notes

Note 225434.1 : Drop Ship FAQ document


Note 130702.1 rop Shipments process

Posted in Oracle Order Management | 15 Comments

Order Management(OM) Integration Options

Posted on February 25th, 2008 by Sanjit Anand |

Print This Post |

Email This Post

OM is one of the most complex modules in EBS, and in typical complex business model, the
integration of other product or third party can't be denied. Processing an Order requires
integration with many other business areas. Most integration points with other Oracle products
are implemented via PL/SQL-based APIs.Here is brief discussion for Order Management EBS
Integration points.

How Order Management integrated with iStore?


OM records customer orders placed via iStore, Order Capture and other CRM applications. It
validates setup for shipping and payment options along with providing order status and the
shipping information to customers. Once the quote is converted into an order, you can only make
changes to the order through Order Management, prior to booking.
How Order Management integrated with Telesales?
Telesales' eBusiness Center has several integrations with Order Management. There is an Order
tab to view order history and create new orders.
How Order Management integrated with Cost Management?

OM call the the Cost Management CST_COST_API to obtain cost from cst_item_costs or
cst_quantity_layers when the Gross Margin feature of OM is enabled.
How Order Management integrated with Field Service?
Field Service Report requires specifically that you setup Price Lists, Units of Measure (UOM),
and two Inventory Item Attributes in Order Management. Price Lists contain the list price for an
item. Items could be material, but also labor and expenses like units of driving distance. Once
material, expense and labor transactions for a task have been taken down on the Field Service
Debrief, this information is updated to Charges. In Charges the list price for the item is received
from Order Management and is used to generate an invoice for a customer.
How Order Management integrated with Depot Repair?
This is used by Depot Repair to create RMA and Sales Orders, validate customer accounts, and
invoice customers for repairs.
How Order Management integrated with Install Base?
Information about Install Base trackable items is interfaced to Install Base in the following ways:

Shippable Items: For both orders and returns, information is interfaced to Install Base via
Inventory Interface.
Non-Shippable Items: For both order and returns, information is interfaced to Install Base
via the Order Management Fulfillment workflow activity Install Base also supports
Internal Sales Order transactions by appropriately creating /updating item instances as a
result of transactions between internal organizations such as pick transactions, shipments,
and receipts.

How Order Management integrated with Service Contracts?


Service Contracts need to pulls information from the Install Base newly created customer records
and creates an ownership record.

Warranty: A Warranty contract is created when a Serviceable product is shipped.


Extended Warranty: An Extended Warranty contract is created when an Extended
Warranty is sold on a sales order. Oracle EAM & OM integration
Subscription: Fulfillment starts after the contract approval process.
RMA: Service Contracts sends Order Management RMA information
How Order Management integrated with Advanced Planning System/Global Order
Promising/ ASCP?
Order Management uses Advanced Supply Chain Planning's Global Order Promising
functionality to check the availability of ordered items and to schedule order lines.Scheduled
Order Lines are viewed as demand by the Advanced Planning System.

How Order Management integrated with Purchasing?


Order Management integrates with Oracle Purchasing in the following functional areas:

Return Receipts: Order Management uses the Oracle Purchasing Receipt functionality to
handle Return receipts. When an item is received, Purchasing calls Order Management to
indicate delivery and to get COGS information.
Internal Orders: Oracle Purchasing uses Order Import to create internal orders.
Drop-Ship Orders: Order Management integrates with Purchasing to fulfill drop-ship
orders. It populates the PO requisitions interface table with information for order lines
that need to be fulfilled via an external source.

How Order Management integrated with Bills of Material ?


This is integrated with BOM when models and kits are entered on sales orders.Normally OM
uses the Bill of Material defined for the model or kit or explode the model into its components,
for the purpose of the user selecting options and for shipping purposes.
How Order Management integrated with Workflow ?
Oracle Workflow is heavily used in EBS and specially to manage Order and Line processing.
These PL/SQL based Workflow is a natural replacement for Order Cycles functionality. It
provides a Graphical User Interfaces for defining activities, notifications, flows and viewing flow
status.
How Order Management integrated with Advanced Pricing ?
OM is tightly integrated with Advance Pricing which includes price lists, modifiers, and
agreements. Order Management, through its Sales Agreement functionality, creates price lists
and pushes them into the Advanced Pricing tables. Order Management calls the Pricing Engine
to make pricing requests during the processing of orders, and receives pricing information back
from Advanced Pricing.
How Order Management integrated with Configurator ?
Order Management integrates with Oracle Configurator to support ordering and validation of
configurations. The Configurator window is a Java Applet that can be launched from the Sales
Order form.
How Order Management integrated with Oracle Payment ?
As we know Oracle payment is new product and OM accepts Credit Card information when
entered on orders. It integrates with Oracle Payment to validate this information and get Credit
Card authorizations. This information is then interfaced to Receivables.

How Order Management integrated with Receivables ?


Order Management integrates with Oracle Receivables in the following function areas:

Invoice Interface: Order Management sends invoices and credit memos to Receivables
via the Invoice Interface workflow activity. The seeded Invoice Interface - Line
workflow sub-process populates the Receivables interface table.
Receipts: Order Management calls Receivables' Receipt API to create receipts for prepaid
credit card orders. Order Management receives a payment-set id from AR when the
receipt is created, and then passes that id back to AR in the autoinvoice tables at
invoicing time so that the invoice can be matched to the receipt.
Tax: Order Management calls the Global Tax Engine APIs to default the Tax Code
(ARP_TAX.GET_DEFAULT_TAX_CODE) and to calculate estimated tax
(ARP_PROCESS_TAX.SUMMARY) for the order Line. The estimated tax value is now
stored on the line and re-calculated only when any of the attributes affecting tax change.
Information about the tax value is also stored as Line Price Adjustments.
Credit Management: If the Credit Management product is installed, notifications are sent
to it by Order Management when an order or line goes on credit hold, to initiate a credit
review. If the credit review results in a decision to approve the order, a business event is
posted which OM subscribes to and then releases the credit hold.

How Order Management integrated with Payables ?


OM accesses the AP Bank Accounts table to populate the Credit Card LOV when an order is
being entered with a payment type of Credit Card. Additionally, if a new credit card number is
entered and the authorization of that card through iPayment is successful, Order Management
calls an AR API to create a new bank account record for the customer in the Bank Accounts
table.
How Order Management integrated with Inventory Management ?

Order Management integrates with Oracle Inventory Management through Managing


Reservations.
You can create reservations to on-hand quantities from the Sales Orders form.

How Order Management integrated with Trade Management ?


Order Management can receive RMA orders and lines from Oracle Trade Management as part of
its dispute handling functionality.
Posted in Integration, Oracle Order Management | 6 Comments

Quick notes : Order 2 Cash Cycle


Posted on February 21st, 2008 by Sanjit Anand |

Print This Post |

Email This Post

Things you should Know about Order to Cash Cycle.


Order Management

You enter sales and return orders within an operating unit.


You define price list and discount names for the entire instance. You can also define price
list lines, discount lines, and quantity breaks for the entire instance. If you have more than
one validation organization in the instance, you may experience error messages when
querying a price list if the inventory item is not valid in your operating unit's OM
validation organization. Thus it is best to define price lists by operating unit.
You can check credit within an operating unit.
You assign order lines and shipments to a specific warehouse (inventory organization).
You pick release orders and print pick slips by operating unit.
You ship confirm orders and print shipping documents by inventory organization. You
can ship from another operating unit, even if in a different set of books.
You receive returned goods in the inventory organization specified on the return.
Inventory and Manufacturing integration functions, such as reservations, available to
promise checking, sales order demand, and assemble to order job creation are processed
in the appropriate inventory organization.

Order Management /Account Receivable

You setup customers for the entire instance but addresses for each operating unit.
You merge customers and addresses within an operating unit.
You report supplier/customer netting within an operating unit.

Account Receivable

You setup receivable account defaults within an operating unit.


You produce invoices, statements, and dunning letters within an operating unit.
You enter and track customer commitments within an operating unit.
You setup bank accounts and associated cash accounts within an operating unit till
Release 11i, as subsequent changes has been made in R12.
Till Release 11i you can enter deposits and individual receipts by bank account within an
operating unit.

Similar Post

What is Order To Cash in Oracle?


Understanding Multi-Organization Structure in EBS
Understanding Multi-Organization Structure in EBS(Technical) - Part II

Posted in Oracle Order Management, Oracle Receivable | 2 Comments

Understanding data flow for Internal Orders

Posted on August 6th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

The process flow for Internal Orders


Internal orders normally start with creation of requisitions in
Oracle Purchasing (which is created as Internal Sales Orders)
.
Once the requisitions created from the MRP and Inventory
modules, the Requisition Import program must be run in
order to move records from the requisition interface tables to
the historical PO_REQUISITION_HEADERS_ALL,
PO_REQUISITION_LINES_ALL and
PO_REQ_DISTRIBUTIONS_ALL.
Now next is to create internal requisitions from Purchasing
module.When each requisition is approved, data will be
inserted into the MTL_SUPPLY table. When the items on the
requisition are stocked in inventory, the supply data can be
viewed from the inventory form called Item Supply/Demand.
Once the Internal Requisition is approved, a user should run
Create Internal Sales Orders (from a Purchasing
responsibility) to load the internal sales orders interface
tables called in Order Entry.
After the Creation of Internal Sales Orders has completed, a
Import Orders concurrent program need to run from an Order
Management.
at this stage, Oracle order Workflow will process the internal sales order using the workflow
definition listed for the Transaction Type definition in Order Management. When the workflow
completes the Shipping Network is checked to see if the Transfer Type between the source and
destination organization is In transit or Direct.
You can use Oracle Order Entry/Shipping to define order cycles, approvals and holds.
Internal Requisitions use the Account Generator, which automatically builds account
distributions. You can specify only one accounting distribution per inventory sourced line.
This internal requisition process provides the features needed to define your inter- organization
shipping network. For transfers between two organizations, you can specify whether to use in
transit or direct shipments. You can also require internal requisitions for transfers between
specific organization.
The Data Flow for Internal orders

Posted in Oracle Order Management | 3 Comments

Understanding data flow for Standard Order


Posted on August 5th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

Last week, got a mail from one of reader who requested for providing data flow of standard
orders and Return Orders. So,here are the information for data flow. Normally standard sales
order can be split into nine sub steps , which jointly carried out by some module like INV,OM,

Pricing, Shipping and AR. Lets take each sub steps with data flow conditions. These are based
out of the flow which is available in 11.5.10.2.
1. Order Entry
This is first stage when Order in enter in system.When the order is entered it basically create a
record in order headers and Order Lines table.

oe_order_headers_all (Here the


flow_status_code as entered)
oe_order_lines_all (flow_status_code as
entered) ( order number is generated)

2.Order Booking
This is next stage , when Order which is entered in step
1 is booked and Flow status changed from Entered to
Booked.At this stage , these table get affected.

oe_order_headers_all (flow_status_code as
booked ,booked_flag updated)
oe_order_lines_all (flow_status_code as
awaiting shipping, booked_flag updated)
wsh_new_deliveries (status_code OP open)
wsh_delivery_details (released_status
R ready to release)

Same time, Demand interface program runs in


background And insert into inventory tables
mtl_demand
3. Reservation
This step is required for doing reservations SCHEDULE
ORDER PROGRAM runs in the background and
quantities are reserved.Once this program get
successfully get completed , the mtl_reservations table
get updated.
4. Pick Release
Ideally pick release is the process which is defined in
which the items on the sales order are taken out from
inventory.

Normally pick release SRS program runs in background . Once the program get completed these
are the table get affected:

oe_order_lines_all (flow_status_code PICKED )


wsh_delivery_details (released_status S submitted for release )
mtl_txn_request_headers
mtl_txn_request_lines
(move order tables.Here request is generated to move item from saleble to staging
sub inventory)
Mtl_material_transactions_temp (link to above tables through
move_order_header_id/line_id

5.Pick Confirm
Items are transferred from saleble to staging Subinventory.

mtl_material_transactions
mtl_transaction_accounts
wsh_delivery_details (released_status YReleased )
wsh_delivery_assignments

6.Ship Confirm
Here ship confirm interface program runs in background . Data removed from
wsh_new_deliveries

oe_order_lines_all (flow_status_code shipped)


wsh_delivery_details (released_status C Shipped)
mtl_transaction_interface
mtl_material_transactions(linked through Transaction source header id)
mtl_transaction_accounts
Data deleted from mtl_demand,mtl_reservations
Item deducted from mtl_onhand_quantities

7.Enter Invoice
This is also called Receivables interface, that mean information moved to accounting area for
invoicing details.

Invoicing workflow activity transfers shipped item information to Oracle


Receivables.
ra_interface_lines_all (interface table into which the data is transferred from order
management)T
Then Autoinvoice program imports data from this

Table which get affected into this stage are recievables base table.

o
o

ra_customer_trx_all (cust_trx_id is primary key to link it to trx_lines table


and trx_number is the invoice number)
ra_customer_trx_lines_all (line_attribute_1 and line_attribute_6 are linked to
header_id (or order number) and line_id of the orders)

8.Complete Line
In this stage order line leval table get updated with Flow status and open flag.

oe_order_lines_all (flow_status_code shipped, open_flag N)

9.Close Order
This is last step of Order Processing . In this stage only oe_order_lines_all table get updated.
These are the table get affected in this step.

oe_order_lines_all (flow_status_code closed,open_flag N)

These are the typically data flow of a order to cash model for a standard order.
Posted in Oracle Order Management | 22 Comments

Understand Date Tracking in HRMS


Posted on July 14th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

Irrespective of installation , whether it's full or shared, it is important to understand the "date
tracking" concept that oracle utilizing in HRMS.
Effective Dates
Date Tracking is a means of maintaining a history of changes to personnel records. It applies to
the following parts of a person's record in Oracle HR: People, Assignments. Each of the areas
that are date tracked within a record are date tracked independently.
We can 'date track' by setting an Effective Date. An effective date is the date at a particular point
in time when a person's record is effective. When you set an effective date for your work,
DateTrack ensures that only information effective on that day is used for any processing,
validation, enquiries and reporting you carry out.
Lets understand this in this simple diagram , which is consider as timeline of a personal record.

It shows how the person's Status has changed over time to reflect their changing circumstances.
As the changes are made in Oracle, the system keeps a record of each change. These records can
be thought of as different slices - or different pages in a file that show each change. Date tracking
allows you to visit each slice or page at any time. If you set the effective date to 17 July 2001..
for example, the record would show that this individual is Married. Reset back to today and the
marital status would show as divorced.
Take a another example for employee Assignment

In this example the assignment record shows how this person's Position changes over time.
When this person originally started in company , their position was Programmer 1. Over time
their position get changed and Oracle keep maintaining the history of this. In addition, this
individual has been told that they have a new position which will take effect as of the 01 Jan
2008. Using date tracking you can record that this position change will take effect in advance of
it happening - simply by setting the Effective Date to 01 Jan 2008 and making the change. Until
that date actually arrives, the position will still show as the current one.
Insert
If there are future dated entries in the system (as in the assignment example above), and you wish
to record a new change that will occur prior to the forthcoming change then Oracle will prompt

you to Insert the record as part of the update. In this scenario, Oracle will insert a new 'slice' of
history up to the date of the future change only.

In above diagram example, a future dated change was entered to record that this individual's
position is changing from Programmer Level 3 to Analyst on 1 Jan 2007. However, subsequent
to this change being entered and saved in Oracle, this person will have a new supervisor from
July 1st - i.e. before taking up the new position. If you now record the new supervisor change,
Oracle will prompt you to 'insert' it. As such, a further slice of history will exist from 1 July 2007
to 1 Jan 2008.
Which columns in Oracle hold these values
To control these date tracking rows, every DateTracked table must include these columns:

EFFECTIVE_START_DATE DATE NOT NULL

EFFECTIVE_END_DATE DATE NOT NULL

Understanding Multi-Organization Structure in


EBS(Technical) Part II
Posted on July 14th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

The multiple organization support feature uses native database features to build a security layer
on top of a single installation of Oracle Applications. This layer of security provides the
necessary data partitioning; while at the same time minimizes the number of potentially
destabilizing changes to the application code itself. The security layer is provided using database
views, which allow access to the partitioned data without any changes to the applications code.

For ERP applications, data partitioning is performed by database views. These views reside in
the APPS Oracle schema and derive the appropriate operating unit context from an RDBMS
variable.
All applications code is run against the APPS schema. The Applications database architecture is
now the same for a Multiple Organizations and non-Multiple Organizations implementation.

Multi Organization Tables

Multiple Organizations in Oracle Applications is enabled by partitioning some database


tables by operating unit. Other tables are shared across operating units (and thus across
sets of books).
In general, the following criteria determine if a table would be partitioned:
o The table contains a GL Account Code (code combination ID).
o There is a business reason for the table to be partitioned (for example, the entity
should not be shared).
o The table contains transaction data.
o The table is an interface table where data being loaded is partitioned.

Applications with Partitioned tables


o Oracle Cash Management
o Oracle Order Management and Shipping Execution
o Oracle Payables
o Oracle Property Manager
o Oracle Projects
o Oracle Purchasing
o Oracle Release Management
o Oracle Receivables
o Oracle Sales Compensation
o Oracle Sales and Marketing
o Oracle Service
o European Localizations
o Latin America Localizations
o Regional Localizations
RDBMS Variable
A global variable exists in the Oracle database called CLIENT_INFO, which is 64 bytes long.

The first 10 bytes are used to store the operating unit ID (or ORG_ID) for the Multiple
Organization Support feature. The CLIENT_INFO context is derived from a profile option that
the user sets for each responsibility as part of the Multi-Org setup steps.

Org_id column in the warehouse contains the Operating Unit ID


Organization_id column contains the warehouse / Inventory Org.

select * from <table name>_ALL


where ORG_ID = SUBSTRB(USERENV('CLIENT_INFO'),1,10);
Posted in Oracle Order Management | 4 Comments

Understand Drop Shipment in Order Management?


Posted on July 4th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

Order Management allows you to enter drop-ship sales orders as well as standard sales orders.
It means you can receive orders for items that you do not stock or for which you lack sufficient
inventory, and have a supplier provide the items directly to your customer.

The best can be described as:

These are the following activity takes place when you have drop shipment

Supplier
o Warehouse Item
o Ship order
o Shipment notification
Order Entry
o Enter customer
o Enter order
o Demand order (optional)
o Cancel order (optional)
o Close order
Purchasing
o Create and send Purchase Order

Enter shipment notification in system


Receivables
o Create invoice
o Collection of payment
o Receipt

hence, drop ship order items ship directly from a supplier to the customer of the order processing
company. A purchase requisition, then a purchase order, is generated to notify the supplier of the
requirement. After the supplier ships the order, it notifies Purchasing to enter this information in
the Purchasing module.
What are the advantages of Drop Shipment Orders?
These are the benefits:

No inventory is required
Reduced order fulfillment processing costs
Reduced flow times
Elimination of losses on non-sellable goods
Elimination of packing and shipping costs
Reduced inventory space requirements
Reduced shipping time to your customer

Allows you to
offer a variety of products
to your customers
How to understand the
dataflow for Drop
shipment Orders?
To understand, here are
the processes divided in
sub process and the
underline activity is
highlighted here:
Here are the Details as per
Mark
1.Order Entry
Here the activity is
entering process where
oe_order_headers_all
(flow_status_code as
entered)

oe_order_lines_all . The order is booked as DROP SHIP


2. Order Booking
3. The Purchase Release program passes information about eligible drop-ship order lines to
Oracle Purchasing.The interface table which gets populated is
po_requisitions_interface_all
4. After Purchase Release has completed successfully, run Requisition Import in Oracle
Purchasing to generate purchase requisitions for the processed order lines. The Requisition
Import program reads the table po_requisitions_interface_all validates your data, derives or
defaults additional information and writes an error message for every validation that fails into the
po_interface_errors table.The validated data is then inserted into the requisition base tables
po_requisition_headers_all,po_requisition_lines_all,po_requisition_distributions_all.Then use
autocreate PO fuctionality to create purchase orders and then perform receipts against these
purchase orders
7. After the goods are successfully received invoices for vendors are created in accounts
payables as in normal purchase orders.
8. Invoices are generated for customers In account receivables.
9. oe_order_lines_all (flow_status_code 'shipped', open_flag "N")
10. oe_order_lines_all (flow_status_code 'closed', open_flag "N")
Hope this is great help to understand the flow.

Pricing

Oracle Pricing API


Posted on March 28th, 2007 by Sanjit Anand |

Print This Post |

Email This Post

Some time back, I had opportunity to work some conversion in oracle pricing module; Though It
was pretty simple task for mine only price list and qualifier need to convert. A week back, when
a friend of mine asked some information about Pricing Module, I thought to share the
information, which I collected at that time. So here are the lists of Application Program
Interfaces (APIs) that Oracle Pricing has. These APIs can be used in custom programs or for
doing conversion or migration activity for using some of the pricing functions.

QP_Price_formula_PUB.Get_Price_Formula (Formula Calculation API): The


Formula Calculation package consists of entities to calculate the value of a formula.
QP_Price_formula_PUB.Process_Price_Formula (Update Formula Prices API): The
Update Formula Prices package consists of entities to update formula prices.
QP_CUSTOM.Get_Custom_Price (Get Custom Price API): You may add custom code
to this customizable function. The pricing engine while evaluating a formula that contains
a formula line (step) of type "function" calls this API.
QP_PREQ_GRP.Price_Request (Price Request API): The Price Request Application
Program Interface (API) is a public API that allows you to get a base price and to apply
price adjustments, other benefits, and charges to a transaction.
QP_MODIFIERS_PUB.Process_Modifiers (Business Object for Modifier Setup API):
The Business Object for Modifier Setup package consists of entities to set up modifiers.
QP_QUALIFIER_RULES_PUB.Process_Qualifier_Rules (Qualifiers API): The
Qualifiers package consists of entities to set up qualifiers.
QP_ATTR_MAPPING_PUB. Build_Contexts (Attribute Mapping API): The Attribute
Mapping package consists of entities to map attributes.
QP_Price_List_PUB.Process_Price_List (Price List Setup API): The Price List Setup
package consists of entities to set up price lists.

I hope this information given above will be useful in your Oracle Advanced Pricing endeavors.
Posted in Oracle Pricing | 6 Comments

Oracle Pricing Module A Note


Posted on March 25th, 2007 by anand |

Print This Post |

Email This Post

It provides an advanced, highly flexible pricing engine that executes pricing calculations for
Oracle Order Management. Some of the features which Pricing allows you are:

Apply a surcharge
Discounts by percentage or amount
Calculate the price of order lines using list prices specified in price lists and pricing
formulas.
Apply price modifiers/qualifiers that you define to a line.
Calculate freight charges and show it as a separate component in Order Management

Concepts in pricing
Price Lists
Price lists are essential to ordering products because each item entered on an order must have a
price. Each price list contains basic list information like price list name, effective dates, currency,
pricing controls,rounding factor,shipping defaults such as freight terms and freight carrier,and
one or more pricing lines, pricing attributes.
Pricing Formulas
Formulas are mathematical expressions that the pricing engine uses to determine the list prices of
items and the discounts that apply to those items.
Price List Qualifiers/Modifiers
Price List Qualifiers/Modifiers Modifiers enable you to setup price adjustments (for example,
discounts and surcharges) and freight and special charges (modifier lists) that the pricing engine
applies immediately to pricing requests.Using modifiers you can:

Setup a modifier list with multiple modifier lines


Create eligibility rules for modifiers by assigning list and line level qualifiers
Qualifiers help the pricing engine to determine who is eligible for the modifier.

Pricing Attributes
Pricing attributes are characteristics of products and services that specify when the characteristics
help to determine the price of a product or service. Distance, age of a related product, customer
class, product family group, and level of service are examples of pricing attributes. You can
specify one or a combination of pricing attributes and assign them to a product. At order entry
time, the pricing engine evaluates the attributes you have specified during formula setup to
calculate the price.
Steps for pricing an order

Create a price list (one time)


This includes creation of price list headers and lines(which associates items to a
particular price)
Create pricing formulas (optional)
Create price list modifiers/qualifiers (optional)
Create an order.

Attach the price list to that order.

RMA in Order Management


The following topics will be discussed in this article:
1. Overview of RMA
2. Creating a New Return (RMA with Credit)
3. Creating a Return using the Copy Function (RMA with Credit)
4. Creating a New Return (RMA no Credit)
5. Creating a New Return (RMA Credit Only)
6. RMA Receipt
7. Viewing the status of RMA
8. Close RMA
Pre-requisites:
1. Return Order Categories and Transaction Types have been defined.
2. Items exist in the Item Master with the attribute Returnable enabled.
3. Those items must exist on a Price List.
4. Customers exist in the Customer Master.
5. Return reasons have been defined.
6. Discounts have been defined.
7. Salespersons have been defined.
1. Overview
Order Management allows the customers to return the goods to you. OM also enables you to authorize
the return of your sales orders as well as sales made by other dealers or suppliers, as long as the items
are part of your item master and price list. You can authorize returns for replacement that returns with or
without credit.
RMA can be created in two different ways in Oracle:

Create a New Return which will create the RMA from scratch
Copy an original order into an order with an RMA Order Type

R2i supports four different RMA Order Types, each with a different Order Cycle:

RMA with Credit is used when the customer returns the physical product and also receives
credit as a result of the return.

This type applies for:


Defective Product
Customer does not like the product
Product does not meet the customers expectations

RMA no Credit is used when the customer will return the product but will not be receiving a credit
as a result of the return.

These returns would be for:


Evaluation Orders
Samples
Other orders where the customer was not originally charged for the product.

RMA Credit Only is used when the customer will receive a credit, but the physical return of the
product is not required.

These credits are generally used by software companies when the customer destroys the CD or disk
and erases the software from their machine, but no physical thing to return.

RMA with Credit and Approval is used in the same manner as an RMA with Credit but this
order cycle includes an approval process that requires someone to approve the RMA before it is
booked. In order for an order/return or order/return line approval workflow to work correctly the
profile option OM: Notification Approver must have a value.

2. Creating a new return (RMA with return)


Select:
Navigate to:

Order Management responsibility


Orders, Returns > Order Organizer or

Select:

Orders, Returns > Sales Orders


New Order button if using the Order Organizer

Customer:
Customer Number:
Order Type:
Customer PO:
Date Ordered:
Customer Contact:
Order Number:
Price List:
Ship To:
Salesperson:
Status:
Currency:
Bill To:

Order Information Others

Enter Customer Name (Customer Number will default in).


Alternatively, enter Customer Number and the Customer Name will default
in.
RMA Order with Credit
Enter a Customer PO number if the order type you selected requires it.
The Current Date will default in as the Order Date. You may change this
date or accept the current date.
Enter a Customer contact (optional).
Oracle will assign the RMA number as soon as the information is saved if
automatic numbering is enabled.
Select a price list from the list of values
Enter the customers ship-to address from the list of values or accept the
default. (Not required for Returns)
Enter the Salesperson
The initial entry status for an RMA is Entered. After Booking the RMA status
will changed to Booked.
Select the currency for the RMA from the list of values or accept the default.
Enter the customers bill-to address from the list of values or accept the
default.

Payment Terms:

Sales Channel:

Warehouse:
Shipping Method:
Line Set:
Freight Terms:
FOB:
Shipment Priority:
Shipping Instruct:
Packing Instructions:
Tax Handling:

Payment Terms are user-definable and must be setup in advance.


(Setup>Orders>Payment Terms). Select from the list of values or accept the
default. (Not required for Returns)
Sales Channels are user-definable and must be setup in advance (Order
Management Quick Codes). Select a Sales Channel from the list of values
or accept the default.
Select a Warehouse (inventory organization) from which Returns will be
received.
Not used for Returns
Not used for Returns

Defaults (In order, from Ship-To, Bill-To, Customer, Order Type, or Price
List)
Defaults from Order Type
Shipping instructions are printed on the pick slip. Since this is a return do
not use this field.
Packing instructions are printed on the pack slip. Since this is a return do
not use this field.
Select from the following:
Exempt Indicates that this order is exempt for a normally

taxable customer site and/or item. If you select exempt


you must enter a reason for exemption.
Require Indicates that this order is taxable for a normally nontaxable customer and/or item.
Standard Indicates that taxation should be based on existing
exemption rules. If the customer has a tax exemption
defined, Order Management displays any certificate
number and reason for the exemption in the

Tax Exempt Number:

corresponding fields.
If you choose Exempt in the Tax Handling field then select an existing
certificate number for the ship-to customer, or enter a new, unapproved
exemption certificate number.
If you chose Standard in the Tax Handling field, an existing exemption rule
may display a certificate number in this field.

Exempt Reason:

Unapproved exemption certificate numbers can be approved using the Tax


Exemptions window.
If you chose Exempt in the Tax Handling field then select an exemption
reason.
If you chose Standard in the Tax Handling field, an existing exemption rule
may display an exemption reason in this field.
You can define tax exemption reasons using the Receivables Quickcodes
window.

Payment Type:
Amount:
Check Number:
Credit Card Type:
Credit Card Num:
Card Holder:
Card Expiration Date:
Approval Code:
Order Source:
Order Source Rule:

Optional unless the payment type selected requires it.


Optional unless the payment type selected requires it.
Optional unless the payment type selected requires it.
Optional unless the payment type selected requires it.
Optional unless the payment type selected requires it.
Optional unless the payment type selected requires it.
Optional unless the payment type selected requires it.
If the RMA is copied from an existing order/return Copy will appear in this
field.
If the RMA is copied from an existing order/return the original order/return
number will appear in this field.

Line Items Tab - Returns

Line:
Ordered Item:
Qty:
Return Reason:
Line Type:

Reference:

Order:
Line:

Invoice:

This field will automatically be populated.


Enter the Ordered Item from the list of values.
Enter the quantity to be returned.
Select a defined reason from the list of values.
Select a line type. A line type may default depending on the transaction type
setup. Select a line type from the list of values if you wish to change the
defaulted value.
Select the appropriate Reference Type. Use the Reference Type if you want
to refer to a specific Invoice, Purchase Order, or Sales Order. These
references must be for transactions originally placed in Oracle. You have
the option of leaving them blank, in which case the customers credit will be
placed On Account when it interfaces to Accounts Receivable. On Account
credit memos may be applied to invoices at a future time.
If referencing a Sales Order then enter the Sales Order number.
If referencing a Sales Order enter the appropriate line number from the
Sales Order referenced.
Note: If creating the RMA using the copy function the information in the
copied Sales Order will automatically populate in this field.
If you enter Sales Order or Invoice in the Reference field, then you have the
option of selecting a specific invoice in the Invoice field. This would allow for
a Credit Memo to be created and directly applied to this invoice. Leaving this

Invoice Line:

field blank will yield an On Account credit memo in Receivables.


If referencing an Invoice, enter the appropriate line number from the Invoice
referenced.

Credit Invoice:
Item Revision:

Line Items Tab Main

UOM:
Unit Selling Price:

The UOM will default in based on the item selected to be returned.


The price defaults in from the invoice, purchase order, sales order, or
invoice if selected in the reference field, otherwise, it will default from the
price list selected on the Return.

3. Creating a Return using the Copy Function (RMA with Credit)


Select:
Navigate to:
Query:
Select:
Select:
Quick Copy Tab:

Order Management responsibility


Orders, Returns > Order Organizer
Query an existing order or return to copy from.
Actions button in the Order Organizer window
Copy

Select:
Change Order Type To:
New Order Number:

Create New Order


Select RMA Order with Credit
Enter a new RMA number for RMA order types that require manual
numbering.

Copy Header Tab

To exclude child entities (lines, sales credits, notes, descriptive flex, and holds) or to re-price, navigate to
the Copy Header, Copy Line, and Pricing Options tabs and deselect options as desired.
Note:

The OM: Credit Card Privileges profile option determines whether you are
able to copy customer credit card information.

Copy Lines Tab

Change Line Type To:


Return Reason Code:
Include Lines:
Include Descriptive Flex:
Include Attachments:
Include Fully Cancelled
Lines:

Select RMA Line with Credit


Select a return reason from the list of values.
Includes the lines from the original order/return.
Includes the descriptive flexfield values from the original order/return.
Includes the attachments from the original order/return.
Determine whether to include/exclude fully cancelled lines when using the
copy feature. If fully cancelled lines are included, the lines are copied over
with the original ordered quantity.

A common use of the Copy function is in the case where a customer wants to return all or part of a
previous sales order. You may use the Copy function to create the return based directly on the
information contained in the original sales order.
Another advantage of using the Copy function to create your RMAs is in the case where the customer will
be receiving a credit for the return, Oracle can use the original sales order number to identify the original
invoice in Accounts Receivable, and apply the credit directly against the original invoice.
When creating returns for configurations, copy the model line. Select the specific order lines and copy
them as return lines to return individual components of a PTO configuration.
Pricing Tab

At Original Selling Price:

Re-price as of this date:

Select:

Select this option if you want the return to contain the original selling price in
the originating order or return. Retaining the original pricing will retain all
discounts and charges and the Calculate Price Flag is set to Partial for
return lines.
If you choose to re-price, specify the pricing date. Manual discounts and
charges are removed and automatic discounts and charges are
recalculated.
OK button. This will perform the copy and close the window.

If any validation errors occur, message(s) in the Messages window are displayed and indicates that an
order was successfully created.
Select:

Continue button. The newly copied order is available through Order


Organizer.

To update and book the RMA, select the RMA from Todays Orders in the Order Organizer window.
Select:

Open button.

The original sales order from which this RMA was created is identified both at the header level (in
the Order Source field of the Others tab) and at the line level (in the Order Source field of the
Main tab).

You have the option to manually make changes to this RMA before booking it. For example, the customer
may only want to return part of one line or not return another line at all.
You may optionally update the Receive From and Credit To Addresses using the Addresses Tab in the
Line Items Tab.
Under the Actions button, there are several other options:
Promotions/Pricing Attributes You may optionally apply Discounts to each lines at this time (assuming that
Discounts have been defined and you have the appropriate discounting privileges). A Discount will
decrease the amount of the credit the customer will receive.
Return Lot/Serial Numbers You can enter lot and serial numbers for the return.
Sales Credits - If the Sales Credits button was checked in preparing the Copy then Sales Credits for the
return will be derived from the original order. You may change the Sales Credits for the return if you wish
by using this option.
To book the order, select the Book Order button.

4. Creating a New Return (RMA no Credit)


Select:
Navigate to:

Order Management responsibility


Orders, Returns > Order Organizer or

Select:

Orders, Returns > Sales Orders


New Order button if using the Order Organizer

The process for creating an RMA no Credit is identical to creating an RMA with Credit. You have the
option to create the RMA using the New Return option or the Copy option. The only difference between
the two processes is that the Invoice Interface does not exist in the workflow for an Order Type of RMA
no Credit. As a result, no credit memo will be created for this RMA.
Note:

Oracle does not provide a seeded workflow process to handle RMAs with
Receipt no Credit; therefore, the R2i control environment provides a custom
process to fulfill this need. For further information on this custom process
refer to OM Transaction Types Setup and R2i OM Order Line Workflow
Package.

5. Creating a New Return (RMA Credit Only)


Select:
Navigate to:

Order Management responsibility


Orders, Returns > Order Organizer or

Select:

Orders, Returns > Sales Orders


New Order button if using the Order Organizer

The process for creating an RMA Credit Only is identical to creating an RMA with Credit. You have the
option to create the RMA using the New Return option or the Copy option. The only difference between
the two processes is that the Fulfillment activity does not exist in the workflow for an Order Type of RMA
no Credit. As a result, no physical return of product is required.
6. RMA Receipt
Select:
Navigate to:
Select:
Select:

Purchasing Super User R2i responsibility


Receiving > Receipts
The Inventory Organization for the Receipt (not Global).
OK button.

Select:
RMA Num:
Line Num:

Line Type:

The Customer tab in the Find Expected Receipts window.


Optionally enter a specific RMA number.
Optionally enter a specific line number on a specific RMA.
Note: Can only enter a line number if you have enter a number in the RMA
Num field.
This field will populate automatically if you enter a value in RMA Num. If you
do not enter a value in RMA Num you can optionally select a line type.

Customer:
Customer Num:
Customer Item Num:

Optionally select a customer from the LOV. If you enter a value in RMA
Num, this field will populate automatically.
Optionally select a customer number from the LOV. If you enter a value in
RMA Num, this field will populate automatically.
Optionally select a customer item number from the LOV.

You can further search for expected receipts using the Item, Date Ranges, and Shipments tabs.

Select:

Find button.

All the receipt lines that meet the search criteria are displayed in the Receiving Transaction form.
Only lines with a Destination Type of Inventory can be delivered to Inventory.
Select:
Quantity:
Subinventory:

Checkbox next to receipt line to be delivered to inventory.


Enter the Quantity to be delivered.
Enter the subinventory where the items will be delivered to.

Save. Once the transaction is saved a receipt number is assigned.

For more information on Receiving Transactions in Purchasing refer to related R2i Purchasing Training
documentation.
7. Viewing the Status of an RMA

The Sales Orders window displays the RMA header status in the Main tab of the Order Information
tabbed region. The RMA line status is displayed in the Main tab of the Line Items tabbed region.
The Workflow Status option on the Sales Order window Tools menu launches the workflow status page.
The window shows all the activities an RMA header or line has completed and the corresponding results
in tabular format.

Note:

In order to view workflow status from the Order Organizer the menu
attached to the responsibility in use must have two functions assigned to it:
Monitor Activities List and Workflow Status. For more information see the
appropriate AOL documentation.

8. Close the RMA


Closing RMAs that are complete enhances performance, since many programs, windows and report
queries retrieve open RMAs only.
An RMA line is closed automatically once it has completed its corresponding workflow successfully. An
RMA header is closed at the end of the month once all the lines have been closed.

Sales Order Holds in Order Management


The

below

topics

To
create
To
apply
To view Sales Order Holds.

Application:

Order Management

Process:

Apply Sales Order Hold

are

explained
Sales
Sales

in

this

Order
Order

article.
Holds.
Holds.

Objectives:

To create Sales Order Holds.


To apply Sales Order Holds.
To view Sales Order Holds.

Prerequisites:

Hold Types have been defined.


Workflow items and activities have been defined.
Transaction Order and Line Types have been defined.
Responsibilities have been defined.
Release Reasons have been defined.
For Credit Check Holds:
A Credit Check Rule has been defined.
Payments Terms have been defined with Credit Checking enabled.
Customers exist in the Customer Master with Credit Checking enabled.
Customers have order and total dollar limits defined in their customer profile.
Transaction Order Types have been defined with Credit Checking enabled.

Oracle provides the ability to create, apply, and release user-defined Sales Order Holds.
Holds are assigned a Hold Type and are authorized for application and release for specific
Responsibilities.
You can define holds that are effective only at certain steps of the order or line workflow, as well as, holds
that apply regardless of the stage in the orders flow. Holds can be defined to be specific for pick, pack,
or ship activities.
Holds may be designed to be applied automatically, or may be applied manually based on set criteria you
define.
Hold Sources
Hold sources allow you to apply a particular hold to a group of existing orders, returns, or their lines, and
to new orders or lines meeting your criteria. A hold source is the combination of a parameter (i.e.
customer) and hold name that you specify. Hold sources are valuable when you want to hold all current
and future orders for an item, customer, order, warehouse or customer site (bill-to and ship-to locations).
For example, you create a hold source to hold an unreleased item. Once the item is available, you simply

remove the hold source for the item, and all holds on individual order lines are released. A hold source
can:

Hold all existing and new orders, returns, or their lines that meet your hold source criteria.
Hold some existing and new orders, returns, or their lines from the Order Organizer window.
Hold only new orders, returns, or their lines that meet your hold criteria.

Credit Checking
You can automatically prevent shipping of products to customers with unacceptable outstanding credit
exposure using automatic credit checking.
In the Transaction Order Type set-up you may opt to have Credit Checking occur at Sales Order Booking,
at Shipping, or both (which you may want if you have long lead times between Booking and Shipping).
The Credit Checking can be enabled in the following 3 places:

For the specific Payment Term


For the specific Customer
For the specific Transaction Order Type

You must define Credit Limits for each of your Customers. You can determine balances to include when
calculating total credit exposure, and set total exposure limits for a customer or customer site.
These limits may default in with the Profile Class or be manually maintained in the Profile: Amounts
alternate region in the Customer Master.
You must define a Credit Limit which is the total limit at any one time for the Customer, as well as an
Order Credit Limit, which is specific to an individual sales order.
Oracle uses all of these criteria to place sales orders on Credit Check Hold.
You can control who is authorized to release Credit Check holds when you want to make an exception or
when the customer's credit balance is acceptable.
Also, Oracle maintains a complete audit trail of credit check holds so you can track who applied or
removed each hold, the date it was applied or removed, and why.
Hold Release:
Holds are released automatically when you supply a hold expiration date. Once the date is reached, the
Order can proceed along its workflow. Releasing a hold source release all the orders, returns, and lines
to which that hold source applied.
Note: You must set up and run Release Expired Holds concurrent program on a nightly basis to take
advantage of the expiration date based release of holds.

Create Holds
Navigate to:

Setup>Orders>Holds

Enter the following:


Name:
Description:
Type
Workflow Item:

Workflow Activity:

Effective Dates:
Responsibility:

Enter the name of the new Hold


Enter a Description for the new hold
Select a valid Type of hold from the list of values
Select a Workflow Item from the List of Values. The Hold activates as soon
as the workflow item has a status for the applicable order. For example, will
go into effect as soon as the sales order has a status for that cycle action.
For example, the Hold example below will go into effect as soon as the sales
order line becomes Pick Release Eligible. If you leave this field blank, the
Hold prevents the order from processing as soon as it is applied, regardless
of the workflow item.
Enter the Workflow Activity for the hold. The order cycle determines where
in the workflow the hold will be placed. All other lines will be processed
except for the line against which the hold is effective.
Optionally, enter the Effective Dates for the activity-specific hold to control
when you can use this hold.
Optionally, determine which user responsibilities have authority to apply or
release activity-specific holds by entering combinations of responsibilities,
authorized actions, and effective dates. Give responsibilities the authority to
apply and release holds.

Save your work.


Apply Holds
Navigate to:

Orders, Returns>Order Organizer

Select:

Tools>Create Hold Source

You may apply a Sales Order Hold to any of the following entities:

Customers
Orders
Customer Site
Items
Warehouse

In the Criteria tabbed region:

To apply the Hold, select the Criteria (For example, customer) to which this Hold applies in the Hold
Selection Criteria block.
Hold Name
Hold Type:
Hold Criteria:

Select the Name of the Hold which you are applying.


Hold type defaults from Hold definition.
Enter the Hold Criteria (up to two criteria can be used).

Criteria Value:

Customer-applies holds source to orders specific customers.


Customer Site-applies holds to orders to or returns specific customer
sites.
Warehouse-applies holds to orders or returns specific warehouses.
Item-applies holds to orders or returns specific to an item.
Order-applies holds to orders or returns specific to an item.

Select Criteria Value.

In the Hold Name tabbed region:

Hold Name
Hold Until Date

Select the Name of the Hold to which you are applying.


Optionally, enter a Date to hold the orders until the date when the hold is
released automatically.
Hold Comments
Optionally, enter a Hold Comment.
Hold Future Orders/Lines Enable this field to activate the hold later to new orders and returns that
satisfy the hold criteria.
Hold Existing Orders/Lines Enable the Hold Existing Orders/Lines check box to activate the hold for
existing orders or returns only that satisfy the hold criteria.
Choose the Apply Holds button to create the hold source.
Order Level Hold Example:
Navigate to the Order Organizer window and query the order/order lines or return/return lines you would
like to apply the hold.

If applicable, Multi-select the orders/order lines you would like to apply the hold.
Choose the Actions button and select Apply Hold.

In the Apply Holds window:

Enter the Hold Name, Hold Until Date, Hold Comments.


Choose the Apply Holds button.

Viewing Holds
One method to view existing Holds is to run the Outstanding Holds Report.
You may run this report for all Holds or use the report parameters to run it only for specific Holds or for
Holds for specific Customers or Items.
To view all of the activity generated by one or more Holds or Hold Types, run the Hold Source Activity
Report. Once again, you may run this report for all Holds or use the report parameters to run it only for
specific Holds or for Holds for specific Customers or Items.
You can also view all of the current Holds which are in place based on the criteria you enter in the Find
Holds form. This is used to release Holds.
Navigate to
The Find Holds form displays:

Orders, Returns>Order Organizer>Holds Information

Enter as much detail as required. Holds matching the criteria entered will be displayed.
Customer, Item, Order, Warehouse or Customer Site can be the criteria to narrow down the search by
selecting them in the drop down box.
Choose the Find button to query the order.

Select the Actions button in the Order Organizer.


Select Additional Information from the Actions menu.