Accounting entries from Sub-ledger are posted to GL.
1. General LEdger Transfer program, from the respective subledger which will move the data into the GL_INTERFACE table.
2. These entries are imported to GL as Journals with the help of Journal Import program. This information is stored in GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES, GL_IMPORT_REFERENCES.
3. This will result in Posting control ID which will be a source of reference to track the various entities posted as part of the current posting process.
4. JE_BATCH_ID will be the primary key on GL_JE_BATCHES which will help track, the headers, lines and import references for the Journals.
5. Import references are stored in GL_IMPORT_REFERENCES, which will help in Drill down from GL to subledger. This is controlled by the Journal Source setup in GL.
6. The imported Journals are the posted to GL. This information hits the GL_BALANCES table.
To identify the various transactions that were posted with the batch,
1. GL provides drilldown from front end in the Journal entry form.
2. From backend, refer to
GL_IMPORT_REFERENCES to obtain the POSTING_CONTROL_ID from REFERENCE_1 and then map it to the subledger accounting tables like RA_CUST_TRX_LINES_GL_DIST_ALL.POSTING_CONTROL_ID.
3. If the Import references are not created, then the only way to drill down will be to refer to the Batch name in GL_JE_BATCHES, obtain the POSTING_CONTROL_ID from the string and map it to the base subledger tables.
Wednesday, September 29, 2010
Wednesday, July 7, 2010
Receivables Invoicing Techno-Functional perspective
Receivables represent the revenues in any business.
Typical Receivables documents include;
1. Transactions (Revenue Document)
2. Receipts (Actual Revenue)
3. Credit Memos (Dispute settlement)
4. Debit Memos
5. Gaurantee
6. Deposit
7. Write-off & Adjustments
Transactions or invoices are created when a sale is made. This can be referenced to a sales order created in OM or service contract or Loans or manual invoice.
Invoice when created results in the following accounting entries:
DR CR
REV 1000
REC 1110
FRE 10
TAX 100
REV - Revenue account
REC - Receivables Account
FRE - Freight Account
Tax - Tax Account
The credit entry into the REV account represents the net revenue, while Tax and Freight accounts are updated accordingly.
There are multiple methods of entering invoices;
a) Autoinvoice (Import invoices from OM, OKC, LNS etc)
b) Manual Invoice entry (ARXTWMAI)
Receipts are created to represent the payments received.
This is applied against an invoice or debit memo.
This results in following accounting entries:
DR CR
Cash Clearing 1110
REC 1110
There are two methods of creating the receipts in Oracle Apps,
a) Manual Receipts (ARXRWMAI)
b) Receipt Batches (Automatic & Manual)
Credit Memos are created when a dispute is settled and customer wins it. Typical sceanrio includes;
A Sale is made and invoice is sent to the customer.
Customer is not satisfied with the service provided and decides to challenge the invoice. Customer disputes the invoice (iReceivables). When the dispute is settled and customer wins the challenge then CM is generated, else invoice stands and customer needs to make a payment. Credit note can be created in multiple ways;
1. Imported from RMA in OM.
2. Manual Credit Memos or Credit Transactions.
I shall discuss Autoinvoice process in the next section.
Typical Receivables documents include;
1. Transactions (Revenue Document)
2. Receipts (Actual Revenue)
3. Credit Memos (Dispute settlement)
4. Debit Memos
5. Gaurantee
6. Deposit
7. Write-off & Adjustments
Transactions or invoices are created when a sale is made. This can be referenced to a sales order created in OM or service contract or Loans or manual invoice.
Invoice when created results in the following accounting entries:
DR CR
REV 1000
REC 1110
FRE 10
TAX 100
REV - Revenue account
REC - Receivables Account
FRE - Freight Account
Tax - Tax Account
The credit entry into the REV account represents the net revenue, while Tax and Freight accounts are updated accordingly.
There are multiple methods of entering invoices;
a) Autoinvoice (Import invoices from OM, OKC, LNS etc)
b) Manual Invoice entry (ARXTWMAI)
Receipts are created to represent the payments received.
This is applied against an invoice or debit memo.
This results in following accounting entries:
DR CR
Cash Clearing 1110
REC 1110
There are two methods of creating the receipts in Oracle Apps,
a) Manual Receipts (ARXRWMAI)
b) Receipt Batches (Automatic & Manual)
Credit Memos are created when a dispute is settled and customer wins it. Typical sceanrio includes;
A Sale is made and invoice is sent to the customer.
Customer is not satisfied with the service provided and decides to challenge the invoice. Customer disputes the invoice (iReceivables). When the dispute is settled and customer wins the challenge then CM is generated, else invoice stands and customer needs to make a payment. Credit note can be created in multiple ways;
1. Imported from RMA in OM.
2. Manual Credit Memos or Credit Transactions.
I shall discuss Autoinvoice process in the next section.
Thursday, July 1, 2010
Serialized Items in OM, Inventory and AR
Item setup falls under two broad categories,
Serialized items
Non-Serialized items.
From domain perspective this setup comes handy when defining Cell phones and its accessories in oracle inventory.
Serialized Item - Cell Phone
Non-Serialized Item - Accessories
All items are stored at Master Org and other child org levels. This information is stored in
MTL_SYSTEM_ITEMS_B. The primary key to this table is INVENTORY_ITEM_ID and all the information pertaining to item attributes can be retrieved by using ORGANIZATION_ID filter.
Each Serialized item is associated with SKU (Stock keeping Unit) which is stored in SEGMENT1 of MTL_SYSTEM_ITEMS_B while the serial numbers under each SKU will be stored in,
MTL_SERIAL_NUMBERS.
Serial number information is stored at the granular level of organization id, which means, a SKU, serial number combination is unique at the organization level.
Ex.
SKU = MY PHONE100
Serial numbers: 1000, 1001, 1002.
Usual industry process recommends that this number is 13-15 characters long and will uniquely identify a handset.
When a serialized item is sold, this information is captured in:
OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_PRICE_ADJUSTMENTS, WSH_DELIVERY_DETAILS.
All the outgoing serial numbers are captured in WSH_SERIAL_NUMBERS.fm_serial_number. This table is joined to WSH_DELIVERY_DETAILS using DELIVERY_DETAIL_ID, which in turn joins to OE_ORDER_LINES_ALL using SOURCE_LINE_ID and SOURCE_HEADER_ID.
All the Sales invoice details are captured in RA_CUSTOMER_TRX_ALL ,RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, AR_PAYMENT_SCHEDULES_ALL.
All the information pertaining to an invoice can be tracked using CUSTOMER_TRX_ID.
Incase of returns on serialized items, the information can tracked in
RCV_SERIAL_TRANSACTIONS table, which joins with RCV_TRANSACTIONS using TRANSACTION_ID. RCV_TRANSACTIONS can be joined to OE_ORDER_LINES_ALL using OE_ORDER_LINE_ID.
This will help track the Serialized item sales and returns.
Trackig the items:
When items are received into Inventory at SKU level.
This information is captured in following tables:
MTL_MATERIAL_TRANSACTIONS - SKU (Segment1) level
MTL_UNIT_TRANSACTIONS - Serial number level.
These two tables are joined via, Transaction ID.
Ex. A serial number enabled item ABC is received into inventory,
MTL_MATERIAL_TRANSACTIONS
Trx ID Trx Type ID Inventory Item ID Trx Qty
10000 10 200 5
MTL_UNIT_TRANSACTIONS
Trx ID Inventory Item ID Serial Number
10000 200 1
10000 200 2
10000 200 3
10000 200 4
10000 200 5
Inventory balances are increased by quantity of 5.
This information is available in:
MTL_ONHAND_QUANTITIES_DETAIL
Serial number enabled items can be tracked using the details in:
MTL_SERIAL_NUMBERS
Latest Subinventory - CURRENT_SUBINVENTORY
Latest Status - CURRENT_STATUS
Non Serialized items cannot be tracked, at SKU level available quantity of any item can be determined but not which ones. These items can be tracked at the LOT NUMBER level so long as lots are enabled.
Serialized items
Non-Serialized items.
From domain perspective this setup comes handy when defining Cell phones and its accessories in oracle inventory.
Serialized Item - Cell Phone
Non-Serialized Item - Accessories
All items are stored at Master Org and other child org levels. This information is stored in
MTL_SYSTEM_ITEMS_B. The primary key to this table is INVENTORY_ITEM_ID and all the information pertaining to item attributes can be retrieved by using ORGANIZATION_ID filter.
Each Serialized item is associated with SKU (Stock keeping Unit) which is stored in SEGMENT1 of MTL_SYSTEM_ITEMS_B while the serial numbers under each SKU will be stored in,
MTL_SERIAL_NUMBERS.
Serial number information is stored at the granular level of organization id, which means, a SKU, serial number combination is unique at the organization level.
Ex.
SKU = MY PHONE100
Serial numbers: 1000, 1001, 1002.
Usual industry process recommends that this number is 13-15 characters long and will uniquely identify a handset.
When a serialized item is sold, this information is captured in:
OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, OE_PRICE_ADJUSTMENTS, WSH_DELIVERY_DETAILS.
All the outgoing serial numbers are captured in WSH_SERIAL_NUMBERS.fm_serial_number. This table is joined to WSH_DELIVERY_DETAILS using DELIVERY_DETAIL_ID, which in turn joins to OE_ORDER_LINES_ALL using SOURCE_LINE_ID and SOURCE_HEADER_ID.
All the Sales invoice details are captured in RA_CUSTOMER_TRX_ALL ,RA_CUSTOMER_TRX_LINES_ALL, RA_CUST_TRX_LINE_GL_DIST_ALL, AR_PAYMENT_SCHEDULES_ALL.
All the information pertaining to an invoice can be tracked using CUSTOMER_TRX_ID.
Incase of returns on serialized items, the information can tracked in
RCV_SERIAL_TRANSACTIONS table, which joins with RCV_TRANSACTIONS using TRANSACTION_ID. RCV_TRANSACTIONS can be joined to OE_ORDER_LINES_ALL using OE_ORDER_LINE_ID.
This will help track the Serialized item sales and returns.
Trackig the items:
When items are received into Inventory at SKU level.
This information is captured in following tables:
MTL_MATERIAL_TRANSACTIONS - SKU (Segment1) level
MTL_UNIT_TRANSACTIONS - Serial number level.
These two tables are joined via, Transaction ID.
Ex. A serial number enabled item ABC is received into inventory,
MTL_MATERIAL_TRANSACTIONS
Trx ID Trx Type ID Inventory Item ID Trx Qty
10000 10 200 5
MTL_UNIT_TRANSACTIONS
Trx ID Inventory Item ID Serial Number
10000 200 1
10000 200 2
10000 200 3
10000 200 4
10000 200 5
Inventory balances are increased by quantity of 5.
This information is available in:
MTL_ONHAND_QUANTITIES_DETAIL
Serial number enabled items can be tracked using the details in:
MTL_SERIAL_NUMBERS
Latest Subinventory - CURRENT_SUBINVENTORY
Latest Status - CURRENT_STATUS
Non Serialized items cannot be tracked, at SKU level available quantity of any item can be determined but not which ones. These items can be tracked at the LOT NUMBER level so long as lots are enabled.
Subscribe to:
Posts (Atom)