Transaction Type Definition(OM Setups)

-


·        Transaction Types / Order types are used to associate workflows for various phases of sales document processing.
·         Transaction Types can be used to create various order types like Standard Order, Return etc., and associate them to various sales document types like Quotes, Sales Agreement etc.
·         Transaction Types have to defined for each operating unit.

Order type details are stored in the following table:
         select * from apps.oe_transaction_types_tl
         where transaction_type_id=oe_order_headers_all.order_type_id


·         In the Operating Unit field on the header, select an operating unit from the list of values.
·         If Multi-Org Access Control is enabled, Transaction Types can be managed across all Operating Units accessible to you via your MO:Security Profile
·         In the Sales Document Type, select Sales Order or Sales Agreement.
·         In the Order Category field, select a category from the list of values. For Order Types, you can specify a value of Order, Return, or Mixed. For Line Types you can specify Order or Return.
·         When an order type is assigned to an order, the category determines whether both order and return lines can go on the order. A category of Mixed enables an order to have both kinds of lines i.e. outbound and inbound.


·         In the Default Order Line Type field, select an order line type from the list of values.
·         In the Price List field select a price list from the list of values to serve as a defaulting source. The list of values displays global price lists and price lists defined for the Operating Unit selected.
·         On the Main Tab in the Credit Check Rule Region:
In the Ordering field, select an ordering credit check rule from the list of values. This field is optional.


·         Warehouses are synonymous with inventory organizations in Oracle Manufacturing.
·         Select the appropriate Shipping Method from the list of values.
·         The Shipment Priority field gets its values from Quick Codes.
·         Freight Terms are defined using Order Management Quick Codes.
·         Select the Scheduling Level for the Transaction Type.


·         In the Source Region on the Finance tab, within the Invoice Source field, select a Source from the list of values.
·         Select the receivables transaction that you would want to be created when data is interface to Account Receivables.
·         Select the COGS account from the list of values
·         Select the Tax Event from the LOV. To specify when the tax would be calculated for the sales order line.


                     ·         Assign Line Transaction Types to the Order Transaction Type.
                     ·         Combination of the OrderType, LineType, ItemType and Process Name determine the line Workflow

Comments

Post a Comment

Popular posts from this blog

Oracle Purchasing Module Step by Step in R12

-
Image
PURCHASING  All the Purchasing related activity information will be declared in Purchasing              Procure 2 Pay Cycle : Requisition à RFQ à Quotation à Quotation Analysis à Purchasing à Receiving à Invoice  à  Payment à Reconciliation PO-Integration :  PO  is integrated by GL, AP, I Supplier, Procurement, and Project Accounting  PO  Responsibility             Step1: Define  PO  Responsibility                         Nav: System administrator à Security à Responsibility à Define             Step2: Assign  PO  options to the PO Responsibility                         Nav: System administrator à Profile à system             Step3: Assign  PO  Responsibility to User                         Nav: System administrator à security à user à define Note:  PO  is including some of i.e. Options, Supplier, Item, Expenses, and Purchasing . Options : Options nothing but a Controlling future at the operating unit level.                         Th
Read more

Sub Ledger Accounting SLA (Complete Functional Information)

-
Image
SubLegder Accounting in R12 SLA Part -1 In these article, we will explore the very basics of SLA and why it exists. Firstly, what exactly does SLA do? SLA is a module which now sits between the SubLedgers like AP/AR etc and the General Ledger. Have a look at this diagram below.  As you will notice, SLA can act as a mediator between the subledgers and Oracle General Ledger. Before we progress, some terminologies of R12 must be revisited. In 11i we had set of books, and in R12 we call them Ledgers. Likewise in R12 we also have secondary ledgers and reporting ledgers. Hence from 11i perspective think of Ledger as Set of Books. As for Subledger, a Subledger is nothing but a module like AP/AR/PO/Inventory etc. In the diagram below, the second scenario is explained whereby let's say that payables module generates a charge account segment combination for an invoice distribution line as A.B.C.D. In such case, if SLA module is not customized, then the very same A.B.C.D
Read more

Difference between ATO and PTO in oracle apps

-
Difference between ATO and PTO in oracle apps 1) MAKE TO ORDER: This is based on Customer specification, you make the product and supply it to them. This is applicable for Engineering items or any Product which you can make based on Customer order Example: Engineering Items 2) ASSEMBLE TO ORDER: This is you have items in parts and it needs to be assembled according to customer requirements For example you have Laptop coming with standard configuration of 160GB Hard disk and 1 GB RAM. But there are customer orders coming in asking for 200GB Hard Disk and 2 GB RAM and if you can assemble them to suit Customer Requirement 3) CONFIGURE TO ORDER: This is Configuring the Product itself to suit Customer requirements Example. The Thread Manufacturing unit Machineries are configured. I have seen Laxmi Machine Works in INDIA which manufactures textile Machineries configure the machineries based on No.of spindles 4) PICK TO ORDER: This is same as Computer Example in ATO. But the  difference is
Read more