Professional Documents
Culture Documents
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
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
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.
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
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).
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
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
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,
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.
The entire Drop shipment process flow can be best understood as figure below:
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)
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:
Where the seller sends the purchase order to the supplier for the full quantity that the customer
had ordered
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.
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)
4.
5.
6.
7.
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.
Reference Notes
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.
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.
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.
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.
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
Similar 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.
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)
Normally pick release SRS program runs in background . Once the program get completed these
are the table get affected:
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
7.Enter Invoice
This is also called Receivables interface, that mean information moved to accounting area for
invoicing details.
Table which get affected into this stage are recievables base table.
o
o
8.Complete Line
In this stage order line leval table get updated with Flow status and open flag.
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.
These are the typically data flow of a order to cash model for a standard order.
Posted in Oracle Order Management | 22 Comments
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:
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.
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.
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.
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
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)
Pricing
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.
I hope this information given above will be useful in your Oracle Advanced Pricing endeavors.
Posted in Oracle Pricing | 6 Comments
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:
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 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.
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.
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.
Select:
Customer:
Customer Number:
Order Type:
Customer PO:
Date Ordered:
Customer Contact:
Order Number:
Price List:
Ship To:
Salesperson:
Status:
Currency:
Bill To:
Payment Terms:
Sales Channel:
Warehouse:
Shipping Method:
Line Set:
Freight Terms:
FOB:
Shipment Priority:
Shipping Instruct:
Packing Instructions:
Tax Handling:
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
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:
Payment Type:
Amount:
Check Number:
Credit Card Type:
Credit Card Num:
Card Holder:
Card Expiration Date:
Approval Code:
Order Source:
Order Source Rule:
Line:
Ordered Item:
Qty:
Return Reason:
Line Type:
Reference:
Order:
Line:
Invoice:
Invoice Line:
Credit Invoice:
Item Revision:
UOM:
Unit Selling Price:
Select:
Change Order Type To:
New Order Number:
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.
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
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:
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.
Select:
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.
Select:
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:
Select:
RMA Num:
Line Num:
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:
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.
below
topics
To
create
To
apply
To view Sales Order Holds.
Application:
Order Management
Process:
are
explained
Sales
Sales
in
this
Order
Order
article.
Holds.
Holds.
Objectives:
Prerequisites:
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:
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
Workflow Activity:
Effective Dates:
Responsibility:
Select:
You may apply a Sales Order Hold to any of the following entities:
Customers
Orders
Customer Site
Items
Warehouse
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:
Criteria Value:
Hold Name
Hold Until Date
If applicable, Multi-select the orders/order lines you would like to apply the hold.
Choose the Actions button and select Apply Hold.
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:
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.