Professional Documents
Culture Documents
Oracle Financial Functional Questions Best
Oracle Financial Functional Questions Best
Introduction of myself:
Well it’s a pleasure to introduce myself. Myself Dillip Kumar Jena holding MBA(Finance) from Madras University,
as well as Completed B.com & M.Com, CS(Inter-I),CA-PEE-I.
I am having more than XX years of experience in the field of finance and Audits out of which XX yrs of experience
in Oracle Apps .I started my Oracle career with DJ Ltd in Month of 20xx.I have worked on various kinds of
projects, they are Support, Implementation, Post production support, Up-gradation projects and Having good
knowledge on India localization and well versed with project accounting.
My first project was A Ltd it’s a flagship company of A Group manufacturing Steering parts located at Chennai. It’s
a Support project where I was handling day to day issues. My Next project was B Ltd located at Mumbai, it’s an up
gradation project from 11.5.10.2 to 12.1.1 version .Then my next project was C Ltd, and it’s an end to end
implementation project and its flagship company of C group which belongs to service.
Currently working on D Ltd, D ltd. is a fast emerging leader in the field of quality testing and on-line monitoring
and services for the textile industry worldwide. D Ltd is a part of the $ 210Mn D group, located at Kolkatta.
It’s a Re implementation project. Now I am giving post production support, and my responsibilities are to solve the
day to day issue and giving the new end user training, raising the service request with oracle, interacting with end-
users for clarification on issues, and defining the FSG reports for revenue and expenses, and Giving assistance to the
generate the MIS reports to Technical Team, Preparing the process for the customized reports, Conducting the
meeting for better understanding the issues and clarifications. Interact with DBA for Database issue, and for apply
the patch for relating issue and running the scripts and Data Fixes.
GL interview questions :
Question Answer
Multiple reporting currencies are a set of unique feature
What is MRC? which permits an organization to report in multiple
functional currency.
What are the
Responsibility Data group, Menu group, Request group
setups?
How to prepare
Row set, Column set
FSG?
What is
Cumulative
It is to account the net difference needed to balance the
translation
translated COA while doing the translation.
Adjustment
Account?
A recurring journal is a journal entry that should be entered
and posted periodically. Each time the journal should have
What is the same accounts but the amounts could be different. To
Recurring create a recurring journal, you define a recurring journal
journal? Types template that you use to generate almost automatically the
of Recurring journals periodically. Recurring Journal templates can
journal? include fixed amounts or formulas to find amounts based
on balances of pre-determined accounts.
Types:-Regular,Skeleton,Formula-Statistical,Formula-Currency
What is the
difference in
structure 3C in 11i whereas 4C in R12,SLA,MOAC
between R12
and 11i?
On what basis
we create Ledger and legal entity
operating units?
What is org_id
Org_Id means OU Id and organisation_Id means
and
Inventory Org ID
organisation_id?
What is BR 100
and which stage Its a document for all set up .Before User Manual it has to
we are sign off.
preparing?
What is
A flexfield is a field made up of sub fields or segments.
Flexfield?
What is Key
flexfield name Accounting Key Flexfield
in GL?
What is DFF
To store the additional information (Data stored in
(Descriptive
ATTRIBUTES fields)
Flexfield)?
How to create
Go to DFF query as based on application and create DFF.
DFF?
Use of Cross
controls the combinations of values you can create when
Validate
you enter values for key flexfields
Segments?
What is
segment? How
A segment is a single sub field within a flexfield.A
many no. of
segment is represented in database as a single table
segments in
column. Maximum 30 segment,14 Attribute in DFF
Accounting
Flexfield?
How many
flexfield
structures can In Oracle GL,We can create N no. Of flexfield structures.
you create for
GL?
What is value
It is a set of values
set?
You do not always want a user to enter junk free text into
Why do we need
all the fields. Hence, Oracle Apps uses value set to validate
value sets?
that correct data is being entered in the fields in screen.
Is value set
attached to all
the fields that No
require
validations?
What is
A flexfield qualifier identifies a particular segment of a key
Flexfield
flexfield.
qualifiers?
Types and
Purpose of Balancing segment,Natural Account,Cost
Flexfield centre,management,Secondary tracking,Intercompany
Qualifier?
What is
A segment qualifier identifies a particular type of value in
Segment
a single segment of a key flexfield
qualifiers?
How do you
define parent
In segment value enable the parent value,define the child
Child
range and enter the low high ranges of child value.
relationship for
segment values?
What is
CVR(Cross CVR restricts particular code of combination at COA level.
validation rule)?
Name,Prefix month,type,year,Num,from,To,If
How to Creating Calender?
adjustment then click on Adjusting
What is monetary
It is currency which has a monetary value.
currency?
A process that converts foreign currency
What is conversion type? transaction in to functional
currency.I.e.Corporate,reporting,spot,user
Can I delete sub ledger Run request Program - Delete Journal Import
entries? Data,parameter Source,request ID,Ledger
GL_BUDGET
GL_BUDGET_types
5 Tables relating to GL? GL_DAILY_RATES
GL_Consolidation
GL_Balances
What is Retain earning It will carry forward the last year balance to the
account? current year.
In the case of
modification of
Modified Entry from SLA
entry,What account taking
from payble to GL?
GL_BUDGET_INTERFACE
GL_DAILY_RATES_INTERFACE
GL_IEA_INTERFACE
Name few GL interface
GL_IEA_INTERFACE
tables?
GL_INTERFACE
GL_INTERFACE_CONTROL
GL_INTERFACE_HISTORY
GL_JE_Batches
GL_JE_headers
GL_JE_Lines
GL_DAILY_RATES_INTERFACE is the
interface you use to create, update, and delete daily conversion rates. Customers should use this
table to load rates into the GL_DAILY_RATES table.
Foreign Keys
Primary Key Table Primary Key Column Foreign Key Column
FND_CURRENCIES CURRENCY_CODE FROM_CURRENCY
FND_CURRENCIES CURRENCY_CODE TO_CURRENCY
FND_USER USER_ID USER_ID
GL_DAILY_CONVERSION_TYPES USER_CONVERSION_TYPE
USER_CONVERSION_TYPE
Not null columns
FROM_CURRENCY
TO_CURRENCY
FROM_CONVERSION_DATE
TO_CONVERSION_DATE
USER_CONVERSION_TYPE
CONVERSION_RATE
MODE_FLAG
GL_IEA_INTERFACE is used to import data into the Global Intercompany System from
external systems. The data entered into this table is processed by the GIS Import program.
Foreign Keys
Primary Key Table Primary Key Column Foreign Key Column
FND_CONCURRENT _REQUESTS REQUEST_ID REQUEST_ID
FND_CURRENCIES CURRENCY_CODE CURRENCY_CODE
GL_CODE_COMBINATIONS CODE_COMBINATION_ID
SENDER_CODE_COMBINATION_ID
GL_CODE_COMBINATIONS CODE_COMBINATION_ID
SENDER_CODE_COMBINATION_ID
GL_IEA_SUBSIDIARIES SUBSIDIARY_ID SENDER_SUBSIDIARY_ID
GL_IEA_SUBSIDIARIES SUBSIDIARY_ID RECEIVER_SUBSIDIARY_ID
GL_IEA_TRANSACTION_TYPES TRANSACTION_TYPE_ID TRANSACTION_TYPE_ID
NOT NULL Columns
GROUP_ID
TRANSACTION_TYPE_ID
TRANSACTION_STATUS_CODE
CURRENCY_CODE
GL_DATE
SENDER_SUBSIDIARY_ID
RECEIVER_SUBSIDIARY_ID
LINE_TYPE
This article explain how to access org-specific data from Sqlplus in Multi-Org (MOAC) environment
Solution:
You have to run the following:
begin
fnd_global.apps_initialize(&user_id,&responsibility_id,&responsibility_appli
cation_id);
mo_global.init('&product_short_name');
end;
Example:
select user_id
from fnd_user
where user_name = 'USER1';
-- returns 12345 (say)
select responsibility_id
from fnd_responsibility_tl
where responsibility_name = 'Receivables Manager';
-- returns 20678
begin
fnd_global.apps_initialize(12345, 20678, 222);
mo_global.init('AR');
end;
After the above, if the user USER1 has access to the responsibility 'Receivables Manager' org specific data can be
viewed from sqlplus.
Note:
Alternatively, you can set the Org Context.
Provide operating_unit_id for the following.
exec apps.fnd_client_info.set_org_context ('&org_id');
Query:
SELECT DISTINCT frt.responsibility_name, fmt.user_menu_name
FROM apps.fnd_responsibility_tl frt,
apps.fnd_responsibility fr,
apps.fnd_menus_tl fmt,
apps.fnd_menus fm,
apps.fnd_application_tl fat,
apps.fnd_application fa
WHERE frt.responsibility_id(+) = fr.responsibility_id
AND fr.menu_id = fmt.menu_id
AND fr.menu_id = fm.menu_id
AND fat.application_id = fa.application_id
AND fa.application_id = fr.application_id
AND frt.LANGUAGE = 'US';
Query to find Values of a lookup
Business Case:
Queries:
Lookup Information:
select *
from fnd_lookup_types_VL
Where lookup_type = '&Enter_lookup_type';
=> Tip:You can use the above table to find lookups available in the system
Values of a lookup:
select *
from fnd_lookup_values
Where lookup_type = '&Enter_lookup_type';
Background:
Query 1:
Provide Concurrent Program name to the following query.
It lists all the Request Sets which are created with the Concurrent Program given.
Query 2:
Sets the value of a profile option permanently to the database, at any level.
Note: This routine will NOT actually commit the changes. The caller must commit.
returns TRUE if successful, FALSE if failure.
Syntax:
FND_PROFILE.SAVE(<Profile_Option_Name>, <Profile_Option_Value>, <Level SITE/APPL/RESP/USER>,
<Level_Value>, <Level_Value_App_id>);
Parameters Explanation:
Profile_Option_Name : Profile name you are setting
Profile_Option_Value : Profile value you are setting
Level : Level that you're setting at. It could be 'SITE', 'APPL','RESP', or 'USER'
Level_Value : Level value that you are setting at,
e.g. user id for 'USER' level. This is not used at site level
Level_Value_App_id : Only used for 'RESP' level. Application_Id of the responsibility.
Useful tables:
select * from fnd_profile_options;
select * from fnd_profile_option_values;
Examples:
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'SITE');
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'APPL', 321532);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'RESP', 321532, 345234);
FND_PROFILE.SAVE('P_NAME', 'P_VAL', 'USER', 123321);
Oracle Sub ledger Accounting is a rules-based engine for generating accounting entries based on source
transactions from ALL Oracle Applications
Sub ledger Accounting is a Service, not an Application
SLA forms and programs are embedded within standard Oracle Application responsibilities (e.g. Payables
Manager)
Replaces various disparate 11i setups, providing single source of truth for financial and management analysis
Highly granular level of detail in the Sub ledger accounting model retained
GL_JE_BATCHES .=
GL_JE_HEADERS (je_batch_id)
(je_batch_id) >
GL_JE_HEADERS .=
GL_JE_LINES (je_header_id)
(je_header_id) >
GL_JE_LINES .= GL_IMPORT_REFERENCES
(je_header_id, je_line_num) > (je_header_id, je_line_num)
xla.xla_transaction_entities (source_id_int_1, etc) after filtering by application_id, entity_code and ledger_id ->
subledger's table(its key columns mentioned in xla_entity_id_mappings) for that ledger_id
For Example:
xla.xla_transaction_entities (source_id_int_1) filtered by application_id 100, entity_code AP_INVOICES and
ledger_id -> ap_invoices_all (invoice_id) for that set_of_books_id.
xla.xla_transaction_entities (source_id_int_1) filtered by application_id 100, entity_code AP_PAYMENTS and
ledger_id -> ap_checks_all (check_id) for that set_of_books_id.
DRAFT will create Journal Entries, which are NOT final, which means they are NOT ready to be transferred to GL.
● You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'D'
XLA_EVENTS.process_status_code is 'D'
XLA_EVENTS.event_status_code is 'U'
● You can run create accounting on this transaction again and again, which will delete the old journal
entries and create new ones.
● You can't transfer these journal entries to GL.
FINAL will create journal entries, which can be transferred to GL.
● You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'F'
XLA_EVENTS.process_status_code is 'P'
XLA_EVENTS.event_status_code is 'P'
● Once it is finally accounted you can NOT run create accounting on the particular transaction (specifically
on that event).
● You can transfer them to GL using Transfer Journal Entries to GL program.
FINAL POST will create journal entries in Final Mode, Transfer them to GL and Post them.
● You can see the accounting in XLA_AE_HEADERS and XLA_AE_LINES.
XLA_AE_HEADERS.accounting_entry_status_code is 'F'
XLA_EVENTS.process_status_code is 'P'
XLA_EVENTS.event_status_code is 'P'
● Once it is finally accounted you can NOT run create accounting on the particular transaction (specifically
on that event).
● It will transfer the journal entries to GL using Journal Import and you can find the data in GL_JE_HEADERS
and GL_JE_LINES.
XLA_AE_HEADERS.transfer_status_code is Y.
It will post to gl_balances also (GL_JE_HEADERS.status is 'P').
XLA_AE_HEADERS xah
XLA_AE_LINES xal
XLA_TRANSACTION_ENTITIES xte
XLA_DISTRIBUTION_LINKS xdl
GL_IMPORT_REFERENCES gir
xah.ae_header_id = xal.ae_header_id
xah.application_id = xal.application_id
xal.application_id = xte.application_id
xte.application_id = xdl.application_id
xah.entity_id = xte.entity_id
xah.ae_header_id = xdl.ae_header_id
xah.event_id = xdl.event_id
xal.gl_sl_link_id = gir.gl_sl_link_id
xal.gl_sl_link_table = gir.gl_sl_link_table
'TRANSACTIONS' or
'RECEIPTS' or
'ADJUSTMENTS' or
'PURCHASE_ORDER' or
'AP_INVOICES' or
'AP_PAYMENTS' or
'MTL_ACCOUNTING_EVENTS' or
'WIP_ACCOUNTING_EVENTS'
xte.source_id_int_1 =
'INVOICE_ID' or
'CHECK_ID' or
'TRX_NUMBER'
xdl.source_distribution_type = 'AP_PMT_DIST'
---------------
xdl.source_distribution_type = 'AP_INV_DIST'
---------------
xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'
---------------
xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'
---------------
xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'
---------------
xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'
---------------
xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Dear Friends,
As we face each interview at market for oracle finance, the interviewer will be much more concentrating about the
oracle version changes though there are changes in facts.
Payable Accounting,Method,Transfer
No Yes
Option to GL
Payable
About Supplier related info
system set Yes At financial option
(Supplier numbering)
up
Accounts
Receivabl
e
Draft,Final,Final
Invoice Create Accounting only
Post
Consolidated billing
Receipt Balance forward billing (Proxima payment
term)
General
Ledger
3C Currency, COA,
4c, Currency, COA, Calendar,
Ledger Yes Calendar (Set of
Account convention
books)
Fixed
Asset
Cash
Manage
ment
Internal Banks
defined in AP and
that is shared by
AP,AR,CE, Payroll
Bank and Branch become part
Set up Yes and Treasury and
of TCA Parties
they are bank
accounts often
copy in multiple
Operating Units
AP Complete All invoices ,Cr memos,Dr Memos,Prepayment invoices for the period
Review the invoice on hold report ----Hold and release invoice untick on accounted
The sub ledger accounting program report generated by the create accounting program
Reconcile payments to Bank statement activity for the period as described in cash management.
Post to the GL
Review the sub-ledger period close exception report and unposted transaction report
Run Depreciation
Create Accounting
AIM
Docume
ntation
Business Process
Architecture (BP)
Business
Requirements
Definition (RD)
Business
Requirements
Mapping
Application and
Technical
Architecture
(TA)
Module Design
and Build (MD)
Data Conversion
(CV)
Documentation
(DO)
Business System
Testing (TE)
PERFORMACE
TESTING(PT)
Adoption and
Learning (AP)
AP.010 Define Executive Project Strategy
Data
Responsibility Menu group Request Group Application
group
AP_NAVIGATE_GUI12 - Asia/Pacific
DJ_India Local Payables JAI_Payables_RG Standard
India Localizations
Cash Forecast
DJ Cash Mgmt CE_SUPERUSER Standard Cash Management
Reports
Web Applications
Desktop Integration
DJ Desktop Integrator Standard Desktop
Menu
Integrator
IN HRMS Reports
DJ India HRMS Manager India HRMS Navigator Standard Human Resources
and Processes
Asia/Pacific
DJ India Local Inventory INV_NAVIGATE - India JAI_Inventory_RG Standard
Localizations
GL Concurrent
DJ Primary Ledger User GL_SUPERUSER Standard General Ledger
Program Group
Applicatio
Flex field Name Description
n
People
Group Flex Payroll DJL_PEOPLE_GROUP_FLEXFIELD DJL_PEOPLE_GROUP_FLEXFIELD
field
Cost
Allocation Payroll DJL_COST_ALLOC_FLEXFIELD DJL_COST_ALLOC_FLEXFIELD
KF
Position Human
DJL_POSITION_FLEXFIELD DJL_POSITION_FLEXFIELD
Flex field Resources
Competenc Human
DJL_COMPETENCE_FLEXFIELD DJL_COMPETENCE_FLEXFIELD
e Flex field Resources
Create value for each value set and attach to respective each flex field
Note: Refer Value Set created at 3rd Step
Freeze
Allow
Security Flexfield flexfield
Flexfield Value set dynami
type Qualifier definitio
c inserts
n
Grade Flex
DJL_GRADE_NAME_VS No Security No Yes Yes
field
People
Group Flex DJL_PEOPLE_GROUP_VS No Security No Yes Yes
field
Job Flex
DJL_JOB_CODE_VS No Security No Yes Yes
field
Cost Non
Allocation DJL_COA_COMPANY Heirarchica No Yes Yes
KF l Security
Non
DJL_COA_COST CENTER Heirarchica No Yes Yes
l Security
Non
DJL_COA_NATURAL
Heirarchica No Yes Yes
ACCOUNT
l Security
Non
DJL_COA_FUTURE_USE_
Heirarchica No Yes Yes
1
l Security
Non
DJL_COA_FUTURE_USE_
Heirarchica No Yes Yes
2
l Security
Position
DJL_POSITION_VS No Security No Yes Yes
Flexfield
Competenc
DJL_SKILL_NAME_VS No Security Yes Yes Yes
e Flexfield
Non Balancin
Accounting
DJL_COA_COMPANY Heirarchica g Yes Yes
Flexfield
l Security segment
Non Cost
DJL_COA_COST CENTER Heirarchica centre Yes Yes
l Security segment
Non Natural
DJL_COA_NATURAL
Heirarchica account Yes Yes
ACCOUNT
l Security segment
Non
DJL_COA_FUTURE_USE_
Heirarchica No Yes Yes
1
l Security
Non
DJL_COA_FUTURE_USE_
Heirarchica No Yes Yes
2
l Security
7th Step:
Particular Name
DJ_Primary
Create ledger
Ledger
DJ Group of
5 HR:Business Group
Companies
9th Step:
INV ORG 1
INV ORG 2
10th Step: Purchase Set up
Module Particulars
AP Financial option
Payable option
Creation of supplier
Open GL period
Open AR period
Create Bank
Create transaction type for order type and attach order line with
this order
Create FG item
Do misc receipt for Item for avoid backorder before that open
the period for inventory
Module Particulars
AR System options
Create customer
Set EBTAX -party tax profile for legal entity and Operating Unit
Asset Category
Asset location
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::\\\end\\\\
Question Answer
Batch payment process Its a 11i bulk payment for multiple supplier
What are the criteria for Supplier, Supplier site, payment term, payment
entering a standard invoice? method, distribution account
What is the work of payment We can make payment supplier category wise and
manager? for multiple supplier payment in a one struck.
Can we sweep invoice which No, We have hold and release that then we can
is in hold position? close the period.
How can we default supplier Enable primar pay check box in supplier site for that
site at invoice level? particular site.
What is EB Tax and set up. 1. Define party tax profiles 2. Define regime 3.
How its linking to the AP and Create Tax 4. Create tax Status 5.Create tax rate
AR module? 6.update tax configuration options
What does the Unaccounted It will sweep the transaction to next period.
Transaction Sweep Report
do?
How to approve ‘n’ no. of You can be Approved n number of invoices using the
invoices? Request "Invoice Validation"
Can you cancel the invoice? If Yes, but before create accounting
yes, explain?
What is the report used to "Supplier Audit Report" can be used to help identify
identify duplicate suppliers? potential duplicate suppliers.
If you choose the Perpetual Accrual Method within
Purchasing, Purchasing records an accounts payable
liability to an AP accrual account for goods received
but not invoiced. When Payables matches and
approves the invoice for the received goods,
Payables clears the accounts payable accrual
What is meant by accrual
account and records the actual liability amount to
write off?
the invoice accounts payable liability account.After
you have entered your receipt transactions and
matched and approved your invoices, you can run
the Accrual Reconciliation Report to identify any
differences between your Purchasing receipts and
Payables invoices.
What is meant by RTS Return to supplier which has to assign at the time of
transactions? creating supplier.
How to assign Cash clearing While doing bank creation, we have to give cash
Account clearing account.
Transaction:
1st step: create purchase Requisition
Path:- see below screen (left)
Provide the item and quantity and need by date then save (Requisition number will generate)
Tick on requisition and click on automatic tab and below screen will appear.
Provide the supplier name
Then click on create tab .It will automatically create a PO on behalf of that Requisition.
Step 2 : Creation of PO
Above screen is the PO. Click on shipment tab and below screen will appear
Here provide match approval Level as
4way = PO Quantity vs. Receipt Quantity vs. Invoice Quantity vs. Inspection Quantity
Now you see the status on PO is showing Approve which was Status as Incomplete.
Step 3 : Creation of Receipt
Tick on Receipt and Save. Click on Header tab You can see the receipt number generated.
Step 4: Receiving Transaction summary
Provide the Po else Receipt number and click on find ,the above screen will appear.See the routing is showing
Inspection required.
Draft = It will impact to only sub ledger tables neither GL table. Any time we want we can delete this entry and we
can change and post to GL.
PO_VENDOR_CONTACTS
AP_INVOICE_PAYMENTS_ALL
SELECT *
FROM ap_invoices_all
WHERE cancelled_date IS NOT NULL
AND invoice_date BETWEEN TO_DATE ('&From_Date', 'DD-MON-YYYY') AND TO_DATE
('&TO_DATE', 'DD-MON-YYYY');
Item Creation
Requisition
Requisition Approval
Request for Quote (RFQ)
Quotat ion
Quote Analysis (Track/check record)
Issue Purchase Order (PO)
PO Approval
Goods Receipt Note (GRN)
ERS invoice (Pay on receipt) or PO matching invoice
Invoice validation
Invoice Approval
Create Accounting
Payment
Create Accounting
Transfer to GL (Payables transfer to GL program)
Journal Import
GL Balances
Key Table
Key Table Name Description
Item Creation
Item Master
MTL_SYSTEM_ITEMS_FVL
details
Purchase Requisition
Creation
PO_REQUISITIO
N_HEADERS_A
PO_REQUISITION_ LL stores
HEADERS_ALL information
about
requisition
headers. You
need one row
for each
requisition
header you
create. Each
row contains
the requisition
number,
preparer,
status, and
description.
PO_REQUISITIO
N_LINES stores
information
about
requisition
lines. You need
one row for
each
requisition line
you create.
Each row
contains the
line number,
item number,
PO_REQUISITION_
item category,
LINES_ALL
item
description,
need-by date,
deliver-to
location, item
quantities,
units, prices,
requestor,
notes, and
suggested
supplier
information for
the requisition
line.
PO_REQ_DISTR
IBUTIONS_ALL
stores
information
about the
accounting
distributions
associated with
each
requisition line.
Each
requisition line
must have at
PO_REQ_DISTRIBUTIONS_ALL least one
accounting
distribution.
You need one
row for each
requisition
distribution
you create.
Each row
includes the
Accounting Flex
field ID and
requisition line
quantity.
PO_HEADERS_
ALL contains
header
information for
all purchasing
documents.
PO_HEADERS_ALL You need one
row for each
document you
create. There
are six types of
documents
that use
PO_HEADERS_
ALL: 1.RFQs
2.Quotations
3.Standard
purchase
orders
4.Planned
purchase
orders
5.Blanket
purchase
orders
Contracts
PO_LINES_ALL
stores current
information
about each
purchase order
PO_LINES_ALL
line. You need
one row for
each line you
attach to a
document.
PO_DISTRIBUTI
ONS_ALL
contains
accounting
distribution
information for
a purchase
order shipment
PO_DISTRIBUTIONS_ALL
line. You need
one row for
each
distribution
line you attach
to a purchase
order
shipment.
RCV_TRANSACTIONS
PO_DISTRIBUTI
ONS_ALL
contains
accounting
distribution
information for
a purchase
PO_REQUISITIONS_ order shipment
INTERFACE_ALL line. You need
one row for
each
distribution
line you attach
to a purchase
order
shipment.
PO_RESCHEDULE_
INTERFACE
PO_HEADERS_I
NTERFACE is
the interface
table that holds
header
information for
the PDOI
PO_HEADERS_INTERFACE
program to
create
standard/blank
et
purchase order
s and catalog
quotations.
PO_LINES_INTE
RFACE is the
PO_LINES_INTERFACE interface table
that holds lines
information for
the PDOI
program to
create
standard/blank
et
purchase order
s and catalog
quotations.
PO_DISTRIBUTI
ONS_INTERFAC
E is the
interface table
that holds
distribution
PO_DISTRIBUTIONS_INTERFACE
information for
the PDOI
program to
create
standard purch
ase order.
PO_VENDORS
is a view which
contains
PO_VENDORS
selected
columns of
AP_SUPPLIERS
PO_VENDORS
is a view which
contains
PO_VENDOR_SITES_ALL
selected
columns of
AP_SUPPLIERS
PO_VENDOR_CONTACTS
AP vs. GL Reconciliation
Before doing Reconciliation, we have to run the concurrent program “Payable Transfer to General Ledger” where
this programme will transfer data from AP to GL.
For this whenever we are doing setups in “payable option” in payable module, one check box is there (payable
invoice transfer GL) that check box we must enable after that in payable level, we run the report Payable transfer
to GL.
“OR”
In GL responsibility import screen (Navigation:-GL Responsibility->journal->Import) we will import the data from
payable to GL.
> Month End reconciliation between GL and AP is mandatory. If AP is interfaced to GL, verifying the balance
between the two modules is usually done through comparing account balances of the liability account.
To reconcile your accounts payable activity for 30-Nov-12, make the following calculation:
Sign Particulars
+ "Posted Invoice Register" for the period between 1-Nov-12 and 30-Nov-12
- "Posted Payment Register" for the period between 1-Nov-12 and 30-Nov-12
> If total is not matching you will need to find out the root cause of difference:
E.g. Invalidated Invoice for the period
> For the PTD activity check the "period Close Exception" if there are any invoices and payments which are not
transferred to GL.
> If the current period does not reconcile, please complete the reconciliation process for all prior periods from the
most recent to the earliest until you get to one that reconciles.
These reports ensure that your Trial Balance accurately reflects your accounts payable liability by matching the
Posted invoices and payments with the AP liability account. You can also compare your AP liability accounts to GL
by doing a query of the accounts in GL to identify the account or accounts out of balance. The trial balance total
should be the same as your GL liability account.
If not:
Run the GL “Account Analysis” report for the liability account and for the date range in question. Look for
transactions with a source other than Payables. This can quickly pinpoint any transactions incorrectly charged to
the account. Make sure that you have not made manual
Journal entries to your liability account in General Ledger. When you identify the accounts you go back to AP and
do a query on the account to find the invoices out of balance.
The last step is to create a journal entry in GL to balance the account or accounts that is out of balance.
1. If
the AP batch is still in the GL Interface, it will not be reflected in the GL reports and this will cause a difference
between AP and GL.
2.If you have deleted any AP batches or lines from AP batches out of the GL Interface, this will cause AP and GL to be
out of balance
Any AP batches that are un posted in GL will cause a difference between AP and GL
4.You performed a data fix in the past where you used the undo accounting script and swept a transaction forward
from a closed period to re account it; this will cause an imbalance between AP and GL. The imbalance will be
corrected in the period in which you made a GL adjustment to account for the fix.
5.Any correction you make during the journal import process will result in the line being changed in the general
ledger, but not in AP
6.Manual journal entries in the general ledger that involve an AP liability account will cause the AP Trial balance not
to reconcile to the GL. These entries are not included in the AP sub ledger so they will not be reflected on the AP
Trial Balance Report.
7.Run the "GL Account Analysis" report for the liability account and for the date range in question. Look for
transactions with a source other than Payable. This can quickly pinpoint any transactions incorrectly charged to the
account.
1) Supplier Ledger
2) Supplier Trial Balance
3) Supplier Advance (Pre payment) Register
4) Supplier Advance Adjustment (Pre payment) Register
5) Supplier Liability Report
6) Supplier Aging Report
7) AP Reconciliation Report
With the help of this new customized reports, we can reconcile AP and make 100% reconciliation in oracle payable
R12
AP Reconciliation Report
= Rs.100(GL(Rs.110) and SLA (Rs.100)
100
If GL SLA then displays all the information of rest of Transaction for Rs.10)
This reports are very accurate (100%) even we can fire with back dated also.
How is the as-of-date used in the “Accounts Payable Trial Balance” report?
A: The as-of-date is used to determine which invoices and payments should be included on the report. Any
invoices or payments with an accounting date AFTER the entered as-of-date will not be displayed on this report.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
END
Question Answer
RA_CUSTOMER_TRX_ALL ,
RA_CUSTOMER_TRX_LINES_ALL,
What are the Major tables in AR?
RA_CUST_TRX_LINE_GL_DIST_ALL ,
AR_PAYMENT_SCHEDULES_ALL
How revenue recognition linked While we are defining Order transaction type->Finance Tab we have to
AR to Order management? assign Accounting rule and Invoicing rule
What is Aging Bucket? Ageing report for debtor whether 4 bucket,7 bucket
What are the checkbox available Allow open receivable,Post to GL,Allow overapplication,default tax
in Transaction Type? classification,Allow frieght
Its functions through the auto cash rule that post program to apply the
How Auto lockbox functions in receipt aount to customer account open items.In transition format
Oracle? importing the data from lock box file to receivalce through control file in
to the interface.
Net for payable and receivable transaction for a same supplier and
What is AP & AR netting?
customer
Receivables Ac Dr xx 1000
Accounting for Billing in Advance To Unearned Revenue xx 750 (Invoice rule – in advance)
To Revenue xx 250 (Accounting Rule-4 Monthly)
Enter the default Grouping Rule Name you want Auto Invoice to use.
Grouping Rule.--system option we
Auto Invoice uses grouping rules to group revenue and credit
have to attach mandatorily, why?
transactions into invoices, debit memos, and credit memos.
What is the use of Realized Gain / At the time currency fluctuation, the difference amount will impact this
loss - get impacted? account
How Cancelling an Invoice? Remove at transaction type -open receivable and post to GL
Unapplied and on account is same but if we will do on-account ,it will hit the
on account
customer balance.
Unidentified No customer
How to Cancel an Receipt. Its not possible to cancel receipt, we have reverse the receipt.
Adjustments - Approval Limits - User wise we have to assign for approval limit for receipt write
Process off,adjustment,credit memo,
Credit Note - RMA - Approval We will tick the Allow overapplication at transaction type ,It will create
Process automatically credit memo to the invoice already made.
Receivable activity,An unearned discount is one taken after the discount period
passes. You cannot choose this option if the system option Unearned Discounts
What is Un earned Discount and
is set to No.
entry?
Earned/Unearned Discount Dr 100
To Receivable Ac Cr 100
1.A balance forward bill includes all of a customer's transactions for the
billing period and any balance carried forward from the previous billing
period.
2.A balance forward bill can have a daily, weekly, or monthly billing
What is Balance forward Billing? period depending on the balance forward billing cycle assigned to the
payment term.
3.Refer for more in
http://www.oracleappshub.com/release12/r12/balance-forward-
billing-in-r12/
This was in 11i which has abolished from R12 where we are giving the
What is Proxima payment term?
cut off day for the payment term.
Dunning - generate a dunning Use dunning letters to inform your customers of past due invoices,
letter for a customer. debit memos, and chargebacks. When you print your dunning letters,
Receivables prints a copy of each invoice which has line items that are
past due.
Can we Copy INVOICES in AR? Yes,Its new function in R12.Go to transaction-> copy invoice
Custom Object creation - MD50 / Customer wise TDS report,Debtor ageing report
70
how to assign a tax to a specific Attach tax category in Item Category then attach item category in
vendor ?not tax category Supplier additional information
• 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
What is the major difference • In Drop Ship orders, material is directly shipped to the customer from
between drop shipment and back the supplier. Thus, inventory is not affected. In this case, only logical
to back order? 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-to-Back orders one PO is tied to one Sales Order
It will create * item for all sum item created at BOM for that particular
Configurator
FG.
To reduce manual work and make user friendly.Each document will get
What is document sequence?
serial numbered.
Q. What Are The Tables That Replaced RA_CUSTOMERS, RA_ADDRESSES_ALL and RA_SITE_USES ?
A. Following tables on the left are replaced with the tables on the right
RA_CUSTOMERS => HZ_CUST_ACCOUNTS
RA_ADDRESSES_ALL => HZ_LOCATIONS
RA_SITE_USES => HZ_CUST_ACCOUNT_SITE_USES.
Make a note that RA_CUSTOMERS, RA_ADDRESSES_ALL and RA_SITE_USES are still available as views in R12.
Key Tables for Account Receivables and
Receivable Work Flow
Receivable Work Flow and Key Tables
STEPS Particulars
Step-7 GL Balances
Accounting Entry for O2C Cycle
Invoice:
Asset To Tax Ac Cr 10
Asset To VAT Cr 2
Receipts
The major tables containing parties and customer accounts information in Oracle Receivables are grouped by
business function.
• HZ_PARTIES
• HZ_CUST_ACCOUNTS
• HZ_PARTY_SITES
• HZ_CUST_ACCT_SITES_ALL
• HZ_CUST_SITE_USES_ALL
• HZ_LOCATIONS
• HZ_PARTY_RELATIONSHIPS
• HZ_ORGANIZATION_PROFILES
• HZ_CONTACT_POINTS
• HZ_CUST_ACCOUNT_ROLES
• HZ_PERSON_PROFILES
• HZ_ORG_CONTACTS
Transaction Tables
• RA_CUSTOMER_TRX_ALL
• RA_CUSTOMER_TRX_LINES_ALL
• RA_CUST_TRX_LINE_GL_DIST_ALL
• AR_PAYMENT_SCHEDULES_ALL
• AR_CASH_RECEIPTS_ALL
• AR_CASH_RECEIPT_HISTORY_ALL
• AR_RECEIVABLE_APPLICATIONS_ALL
• AR_ADJUSTMENTS_ALL
HZ_PARTIES
A party is an entity that can enter into a business relationship.
This table stores basic information about parties, which is true regardless of this relationship to the deploying
company. Entities are modeled only once in HZ_PARTIES, regardless of how many roles they play. For example, if
an organization is a customer, a distributor, and a partner, there is still only one record for them in HZ_PARTIES.
HZ_LOCATIONS
A location is a point in geographical space described by an address and/or geographical Indicators such as latitude
or longitude.
• This table stores information about an address such as: street address and postal code.
• This table provides physical location information about parties (organizations and people) and customer
accounts.
• Records in HZ_LOCATIONS can store delivery and postal code information about a location, store latitude and
longitude, and can be used to determine the appropriate calculations and tax rates for sales tax and VAT
calculations.
HZ_PARTY_SITES
This table links a party (HZ_PARTIES) and a location (HZ_LOCATIONS) and stores location-Specific party information
such as a person’s mail stops at their work address.
• One party can point to one or more party sites.
• One location can point to one or more party site.
• Party sites serve as the intersection between parties and locations, allowing for a many-to-many relationship
between the two.
HZ_RELATIONSHIPS
This table stores information about relationships between two entities, for example, one party and another party.
• The SUBJECT_ID and OBJECT_ID columns specify the relationship that exists between two parties. For example, if
the party relationship type is “Parent Of,” then a holding company could be the “SUBJECT_ID” in the relationship
while one of its subsidiaries could be the OBJECT_ID. Creating a party contact causes a party relationship to be
created.
• A party can have different relationships with one or more other parties that can change over time.
HZ_ORGANIZATION_PROFILES
This table stores a variety of information about a party of type Organization.
• This table gets populated when a party of type ORGANIZATION is created.
• Historical data is also stored in this table.
HZ_PERSON_PROFILES
This table stores a variety of information about a party of type Person.
• For example, this table could contain the correct spelling and phonetic pronunciation of the person’s name.
• Some information in this table may also be entered into the HZ_PARTIES table.
HZ_ORG_CONTACTS
This table stores a variety of information about an organization contact.
• The records in this table provide information about a contact position such as job title, rank, and department.
• This table is not used to store information about a specific person or organization. For example, this table may
include a record for the position of Vice President of Manufacturing that indicates that the contact is a senior
executive, but it would not include the name of the person in that position.
HZ_CUST_ACCOUNTS
This table stores information about customer/financial relationships established between a Party and the
deploying company.
• Because a party can have multiple customer accounts, this table may contain several records for a single party.
For example, an individual person may establish a personal account, a family account, and a professional account
for a consulting practice.
HZ_CUST_ACCT_SITES_ALL
This table stores information about customer/financial account sites information.
It stores information about customer sites. One customer account can have multiple sites.
HZ_CUST_SITE_USES_ALL
This table stores information about the business purposes assigned to a customer account site.
• A customer account site can have multiple purposes, but each record in this table only specifies one purpose for
a customer account site. For example, a customer account site may be assigned as a ship-to site in one record and
as a bill-to site in another record.
HZ_CUST_ACCOUNT_ROLES
This table stores information about a role or function that a party performs as related to a customer account. For
example, Jane Doe might be the Legal Contact for a specific customer account of Corporation ABC. Note that
account ownership such as financial responsibility for an account is determined by the single party ID that is stored
directly on the HZ_CUST_ACCOUNTS table.
HZ_CONTACT_POINTS
This table stores information about how to communicate with parties or party sites using electronic media or
methods such as Electronic Data Interchange (EDI), e-mail, telephone, telex, and the Internet.
• Each medium or method should be stored as a separate method in this table. For example, the attributes of a
complete telephone number connection should be stored in a record, while EDI information should be stored in a
different record.
RA_CUSTOMER_TRX_ALL
This table stores invoice, debit memo, commitment, charge back, bills receivable, and credit memo header
information.
• Each row includes general invoice information such as customer, transaction type, and printing instructions.
• You need one row for each invoice, debit memo, commitment, and credit memo you create in Oracle Receivables
and these are all distinguished by their transaction types stored in RA_CUST_ TRX_ TYPES_ALL.
RA_CUSTOMER_TRX_LINES_ALL
This table stores information about invoice, debit memo, credit memo, bills receivable, and commitment lines. It
describes to the customer the charges that appear on these documents.
AR_PAYMENT_SCHEDULES_ALL
This table stores all transactions except adjustments and miscellaneous cash receipts. A miscellaneous cash receipt
is one that is not connected to a customer.
• All customer-related activity is logged in this table.
• This table is updated when an activity occurs against an invoice, debit memo, chargeback, credit memo, on-
account credit, bills receivable,
receipt, or commitments.
RA_CUST_TRX_TYPES_ALL
This table stores information about each transaction type for all classes of transactions, for example, invoices,
commitments, and credit memos.
• Each row includes Auto Accounting information
as well as standard defaults for the resulting invoices. The primary key for this table is CUST_TRX_TYPE_ID.
AR_TRANSACTION_HISTORY_ALL
This table is a Bills Receivable-specific table containing the history of a transaction’s lifecycle.
• A new row is created each time there is activity on the transaction or the status of the transaction has changed.
• This table stores the header for the Receivables posting information.
AR_DISTRIBUTIONS_ALL
This table stores the accounting distributions for cash receipts, miscellaneous receipts, adjustments, credit memo
applications, cash receipt applications, and bills receivable transactions.
AR_CASH_RECEIPTS_ALL
This table stores one record for each receipt entry.
• All cash receipts are logged in this table.
• Oracle Receivables creates records concurrently in the AR_CASH _RECEIPT_ HISTORY_ ALL, AR_PAYMENT_
SCHEDULES_ ALL, AR_DISTRI-BUTIONS_ALL, and AR_ RECEIVABLE_ APPLICA-TIONS_ALL tables for invoice-related
receipts.
• For receipts that are not related to invoices, records are created in the AR_MISC_CASH_ DISTRIBUTIONS_ALL
table instead of the AR_RECEIVABLE_APPLICATIONS_ ALL table.
AR_CASH_RECEIPT_HISTORY_ALL
This table stores all of the activity that is contained for the life cycle of a receipt.
• Each row represents one step.
• The status field for that row tells you which step the receipt has reached.
• Possible statuses are Approved, Confirmed, Remitted, Cleared, and Reversed.
AR_RECEIVABLE_APPLICATIONS_ALL
This table stores all accounting entries for cash and credit memo applications.
• Each row includes the amount applied, status, and accounting flex field information.
AR_MISC_CASH_DISTRIBUTIONS_ALL
This table stores all accounting entries for miscellaneous cash applications.
• Miscellaneous cash cannot be invoiced, such as stock revenue, interest income, and investment income.
• AR_CASH_RECEIPTS_ALL stores one record for each payment, and this table stores one record for each
distribution of the receipt.
AR_RECEIPT_CLASSES
This table stores the different receipt classes that you define.
• Receipt classes determine whether the receipt[s] belonging to this class are created manually or automatically,
and whether the receipts go through the different steps in a receipt’s life-cycle.
AR_RECEIPT_METHODS
This table stores information about Payment Methods, receipt attributes that you define and assign to Receipt
Classes to account for receipts and their applications.
• For automatically created receipts, a Payment Method defines the rules for creating these receipts.
• For manually created receipts, a Payment Method defines a user-definable type for the receipt.
• Each Payment Method is associated with a set of bank accounts, which forms the set of bank accounts you can
assign to your receipt.
AR_ADJUSTMENTS_ALL
This table stores information about the adjustment applied to the Invoices.
TECHNICAL DATA FLOW IN AR INVOICE TO CASH
Workflow Background Process executes Auto invoice master, Auto invoice Import Program.
The date is first transferred from Shipping to RA_INTERFACE_LINES_ALL.
Then the Auto invoice Import program validates the records and populates the base table in Account Receivable.
RA_CUSTOMER_TXN_ALL , RA_CUSTOMER_TXN_LINES_ALL
RA_CUSTOMER_TRX_ALL
select interface_header_attribute1,
customer_trx_id,
trx_number,
cust_trx_type_id,
complete_flag,
ship_date_actual
from RA_CUSTOMER_TRX_ALL
where interface_header_attribute1 = '10001'
AR to GL Query
Business Case:
Provide Set of book id, Period name, AR invoice/Transaction to the following query. It will give all GL Batch Name,
GL Header and Line details along with the Posted status at the line level.
Query:
SELECT gjl.reference_4 AR_Transaction,
gjb.je_batch_id,
gjb.name batch_name,
gjh.je_header_id,
gjh.name Journal_Header_Name,
DECODE (gjh.ACTUAL_FLAG,
'A', 'Actual',
'B', 'Budget',
'E', 'Encumbrance')
Balance_Type,
gjl.subledger_doc_sequence_value Doc_Seq_Value,
gjl.effective_date GL_Date,
gjl.code_combination_id,
gjl.accounted_dr,
gjl.accounted_cr,
gjl.description Description,
DECODE (gjl.status, 'P', 'Posted', 'U', 'Unposted', gjl.status)
Journal_Line_Status
FROM gl_je_headers gjh, gl_je_lines gjl, gl_je_batches gjb
WHERE gjh.je_source = 'Receivables'
AND gjh.je_header_id = gjl.je_header_id
AND gjh.JE_BATCH_ID = gjb.JE_BATCH_ID
AND gjh.JE_HEADER_ID = gjl.JE_HEADER_ID
AND gjh.period_name = gjb.default_period_name
AND gjh.set_of_books_id = &sob_id
AND gjh.period_name = '&Period_Name'
AND gjl.reference_4 = '&AR_trx_number';
Query:
SELECT rc.customer_number,
rc.CUSTOMER_NAME,
hp.party_id,
hp.party_type,
rc.TAX_REFERENCE,
hca.cust_account_id,
hca.PAYMENT_TERM_ID,
hps.location_id,
hcsu.location,
hcsu.site_use_code,
hcsa.bill_to_flag,
hcsu.GL_ID_REC Receiving_acc_ccid,
hl.address1,
hl.address2,
hl.address3,
hl.city,
hl.state,
hl.country,
hl.postal_code
FROM ra_customers rc,
hz_parties hp,
hz_party_sites hps,
hz_locations hl,
hz_cust_accounts_all hca,
hz_cust_acct_sites_all hcsa,
hz_cust_site_uses_all hcsu
WHERE rc.party_id = hp.party_id
AND hp.party_id = hps.party_id
AND hps.location_id = hl.location_id
AND hp.party_id = hca.party_id
AND hcsa.party_site_id = hps.party_site_id
AND hcsu.cust_acct_site_id = hcsa.cust_acct_site_id
AND hca.cust_account_id = hcsa.cust_account_id
AND rc.customer_number = '&Customer_Number';
STEPS Particulars
Step-22 GL Balances
Sales
Order
Inventory Valuation
Asset Account (item_cost) Cr 1000
COGS
Recogniti
on
transactio
n
Stores
Invoice:
Asset To Tax Ac Cr 10
Asset To VAT Cr 2
Receipts
Booked
Pick Released
Full Transaction
MTL_MATERIAL_TRANSACTION No records in
S MTL_MATERIAL_TRANSACTIONS
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES
Pick Confirmed
Ship Confirmed
Auto Invoice
Customer Information
HZ_CUST_ACCOUNTS
HZ_CUST_ACCOUNT_SITES_ALL
HZ_CUST_SITE_USES_ALL
RA_CUSTOMERS
Price Details
QP_LIST_LINES
Payment Terms
OE_HOLD_AUTHORIZATIONS
OE_HOLD_SOURCES_ALL
OE_ORDER_HOLDS_ALL
Hold Release
Cancel Orders
Document Sequence
FND_DOC_SEQUENCE_CATEGOR
IES
FND_DOC_SEQUENCE_ASSIGNM
ENTS
OE_DEF_ATTR_CONDNS
AK_OBJECT_ATTRIBUTES
Sales Credit
Attaching Documents
OE_BLANKET_LINES_ALL
Processing Constraints
STEP 1:
Enter order received from customer in Order Management (Sales Order)
Also enter the line level information of items ordered for. On saving the information, the data will be inserted in
OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL Order_number will be automatically generated,
Header and line Flow_status_code = ‘ENTERED’
OE_ORDER_HEADERS_ALL
select header_id,
order_number,
request_date,
transactional_curr_code,
shipping_method_code,
ship_from_org_id,
ship_to_org_id,
org_id,
flow_status_code,
salesrep_id,
booked_date
from OE_ORDER_HEADERS_ALL
where flow_status_code = 'CLOSED'
and order_number = '10001'
OE_ORDER_LINES_ALL
select header_id,
line_id,
line_number,
ordered_item,
inventory_item_id ,
request_date,
promise_date,
schedule_ship_date,
pricing_quantity,
ordered_quantity,
cancelled_quantity,
shipped_quantity,
invoiced_quantity,
payment_term_id,
visible_demand_flag,
actual_shipment_date,
unit_selling_price,
tax_value,
cancelled_flag,
flow_status_code
from OE_ORDER_LINES_ALL
where header_id = 20001
STEP 2:
Book the order. Header Flow_status_code = ‘BOOKED’
Line Flow_status_code = ‘AWAITING SHIPPING’
The data is captured in WSH_DELIVERY_DETAILS.
WSH_DLIVERY_ASSIGNMENTS is the intermediate table between WSH_DELIVERY_DETAIL and
WSH_NEW_DELIVERIES.
WSH_DELIVERY_DETAILS
select delivery_detail_id,
source_header_id,
source_line_id,
source_code,
customer_id,
inventory_item_id,
item_description,
ship_from_location_id,
ship_to_location_id,
move_order_line_id,
requested_quantity,
shipped_quantity,
subinventory,
released_status,
ship_method_code,
carrier_id,
net_weight,
unit_weight,
unit_volume,
unit_price,
inspection_flag,
source_header_number,
batch_id
from WSH_DELIVERY_DETAILS
where source_header_id = 20001
WSH_DELIVERY_ASSIGNMENTS
select delivery_detail_id ,
delivery_id,
parent_delivery_detail_id,
creation_date
from WSH_DELIVERY_ASSIGNMENTS
where delivery_detail_id in (216151, 216152, 216153) -- from above query
WSH_NEW_DELIVERIES
select delivery_id,
name,
status_code,
customer_id ,
gross_weight,
net_weight,
weight_uom_code,
confirm_date,
delivery_type,
source_header_id,
hash_string
from WSH_NEW_DELIVERIES
where delivery_id in (65881, 65882) -- from above query
STEP 3:
You can enter, view and update the Sales order information using Sales Order window.
Release the sales Order
Once the order is released, the data is updated in WSH_DELIVERY_DETAILS.The released_status becomes ‘Y’
and MOVE ORDER is generated in MTL_TXN_REQUEST_HEADERS and LINES. The move_order_line_id is
also populated in WSH_DELIVERY_DETAILS
STEP 4:
Ship Confirm will update the data in WSH_DELIVERY_DETAILS. Released_status = ‘C’ and Shipped_quantity
gets updated.
If you choose Tools >> Workflow Status then you will see that the workflow activity is in Deferred stage.
The concurrent program Workflow Background Engine needs to be executed to proceed further.
MTL_TXN_REQUEST_LINES
MTL_TXN_REQUEST_HEADERS
MTL_MATERIAL_TRANSACTIONS
select transaction_id,
inventory_item_id,
organization_id,
subinventory_code,
transaction_type_id,
transaction_action_id,
transaction_quantity,
transaction_uom,
transaction_date,
distribution_account_id,
invoiced_flag,
shipment_number delvery_name
from MTL_MATERIAL_TRANSACTIONS
where shipment_number in ('65881', '65882')
Workflow Background Process executes Auto invoice master, Auto invoice Import Program.
The date is first transferred from Shipping to RA_INTERFACE_LINES_ALL.
Then the Auto invoice Import program validates the records and populates the base table in Account Receivable.
RA_CUSTOMER_TXN_ALL , RA_CUSTOMER_TXN_LINES_ALL
RA_CUSTOMER_TRX_ALL
select interface_header_attribute1,
customer_trx_id,
trx_number,
cust_trx_type_id,
complete_flag,
ship_date_actual
from RA_CUSTOMER_TRX_ALL
where interface_header_attribute1 = '12001'
Order Entry
Sales Order entry consists of two parts, Order header and Order lines.
Order Header
As order header information is entered and saved a record is created in OE_ORDER_HEADERS_ALL only and this
record will be linked to many other tables and we shall discuss about those dependent tables now.
Transaction Type:
Transaction type is used to select the workflow path/process and it also defaults many other fields on the sales order.
This transaction type is associated with a sequence which is responsible for providing the sales order number for the
sales order.
--Transaction Type
SELECT oha.order_number ,
oha.order_type_id ,
ott.name ,
ott.description
FROM oe_order_headers_all oha,
oe_transaction_types_tl ott
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND oha.order_type_id=ott.transaction_type_id
AND ott.LANGUAGE = 'US';
Actually order transaction type details are stored in OE_TRANSACTION_TYPES_ALL but in the above query we
have used _TL table (multilingual table) as we want to display transaction name.
Price List:
Price list information is stored in QP_LIST_HEADERS_B table but we need to refer to its multilingual table
QP_LIST_HEADERS_TL
--Price List
SELECT oha.order_number ,
oha.price_list_id ,
qlht.name ,
qlht.description
FROM oe_order_headers_all oha,
qp_list_headers_tl qlht
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND oha.price_list_id=qlht.list_header_id
AND qlht.LANGUAGE = 'US';
Sales Person:
--Sales Person
SELECT oha.order_number ,
jrre.source_name ,
jrre.source_email
FROM oe_order_headers_all oha,
jtf_rs_salesreps jrs ,
jtf_rs_resource_extns jrre
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND oha.salesrep_id =jrs.salesrep_id
AND jrs.resource_id = jrre.resource_id;
Order Header Status:
--Header Status
SELECT oha.order_number,
flv.lookup_type ,
flv.lookup_code ,
flv.meaning ,
flv.description
FROM fnd_lookup_values flv,
oe_order_headers_all oha
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND oha.flow_status_code = flv.lookup_code
AND lookup_type = 'FLOW_STATUS'
AND LANGUAGE = 'US';
Payment Terms:
--Payment terms
SELECT oha.order_number,
name ,
description
FROM oe_order_headers_all oha,
ra_terms rt
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND rt.term_id = oha.payment_term_id ;
Shipping Method:
--Shipping Method
SELECT oha.order_number,
wcsm.service_level
FROM oe_order_headers_all oha,
wsh_carrier_ship_methods wcsm
WHERE 1 =1
AND oha.order_number = '&ur_order#'
AND oha.shipping_method_code= wcsm.ship_method_code
AND wcsm.organization_id = oha.ship_from_org_id;
Order Lines
Order lines consist of item ordered as part of the sales order.
On Hand Quantity of Item:
Reservations
This step is required for doing reservations SCHEDULE ORDER PROGRAM runs in the background(if scheduled)
and quantities are reserved. Once this program get successfully get completed, the MTL_DEMAND and
MTL_RESERVATIONS tables are updated. OE_ORDER_LINES_ALL.line_id =
MTL_RESERVATIONS.demand_source_line_id
Pick Release
Pick Release is the process of putting reservation on on-hand quantity available in the inventory and pick them for
particular sales order.
Pick release can be done from ‘Release Sales Order’ form or ‘Pick Selection List Generation – SRS‘program can be
scheduled in background. In both of these cases all lines of the order gets pick released depending on the Picking
rule used. If specific line/s needs to be pick release it can be done from ‘Shipping Transaction form. For this case
Pick Release is done from ‘Release Sales Order’ form with Pick Confirm=NO.
Once pick release is done these are the tables get affected:
● If material reservation is not done then MTL_RESERVATIONS gets updated now.
● A new record is created in WSH_NEW_DELIVERIES with status_code = ‘OP’ (Open).
WSH_NEW_DELIVERIES has the delivery records.
●
WSH_DELIVERY_ASSIGNMENTS.delivery_id = WSH_NEW_DELIVERIES.delivery_id
● WSH_DELIVERY_DETAILS.released_status changes to ‘S’ (‘submitted for release’)
● A move order is created in Pick Release process which is used to pick and move the goods to staging area
(here move order is just created but not transacted). MTL_TXN_REQUEST_HEADERS,
MTL_TXN_REQUEST_LINES are move order tables
● MTL_MATERIAL_TRANSACTIONS_TEMP (link to above tables through
move_order_header_id/line_id, this table holds the record temporally)
In shipping transaction form order status remains “Released to Warehouse” and all the material still remains in
source sub-inventory. We need to do Move Order Transaction for this order. Till this no material transaction has
been posted to MTL_MATERIAL_TRANSACTIONS
Pick Confirm
Pick Confirm is to transact the move order created in Pick Release process. In move order transaction items are
transferred from source sub-inventory to staging Sub-inventory. Here material transaction occurs.
Order line status becomes ‘Picked’ on Sales Order and ‘Staged/Pick Confirmed’ on Shipping Transaction Form.
● MTL_MATERIAL_TRANSACTIONS_TEMP (Record gets deleted from here and gets posted to
MTL_MATERIAL_TRANSACTIONS)
● OE_ORDER_LINES_ALL.flow_status_code =’PICKED’
● MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Pick Transaction
MTL_MATERIAL_TRANSACTIONS.trx_source_line_id = OE_ORDER_LINES_ALL.line_id
● MTL_TRANSACTION_ACCOUNTS is updated with accounting information
● WSH_DELIVERY_DETAILS. released status=‘Y’ (‘Released’)
● WSH_DELIVERY_ASSIGNMENTS, MTL_ONHAND_QUANTITIES are updated accordingly
Note: Pick Confirm step can be eliminated if ‘Auto Pick Confirm’ is selected as ‘YES’ while performed manual
pick release. If Pick release is done through shipping transactions form and if you want to perform auto pick confirm
then picking rules setup has to be done.
Ship Confirm
Shipping execution of the order starts here. The goods are picked from staging area and given to shipping. “Interface
Trip Stop” program runs in the backend.
● OE_ORDER_LINES_ALL .flow_status_code =‘SHIPPED’
● WSH_DELIVERY_DETAILS. released_status=‘C’ (‘Shipped’)
● Data from MTL_TRANSACTIONS_INTERFACE is moved to MTL_MATERIAL_TRANACTIONS and
MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Issue transaction.
● Data is deleted from MTL_DEMAND, MTL_RESERVATIONS and WSH_NEW_DELIVERIES
● Item deducted from MTL_ONHAND_QUANTITIES
● MTL_TRANSACTION_ACCOUNTS is updated with accounting information.
Generating Invoice
After shipping the order the order lines gets eligible to get transfered to RA_INTERFACE_LINES_ALL. Workflow
background engine picks those records and post it to RA_INTERFACE_LINES_ALL. 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. At the same time records also goes in the table
RA_INTERFACE_SALESCREDITS_ALL which hold details of sales credit for the particular order.
OE_ORDER_LINES_ALL.invoice_interface_status_code = ‘YES’
ra_interface_lines_all (interface table into which the data is transferred from order management) Then Auto invoice
program imports data from this table which get affected into this stage are receivables base table (especially
ra_customer_trx_all and ra_customer_trx_lines_all).
RA_CUSTOMER_TRX_LINES_ALL.line_attribute_1 = OE_ORDER_HEADERS_ALL.order_number
RA_CUSTOMER_TRX_LINES_ALL.line_attribute_6 = OE_ORDER_LINES_ALL.line_id
Close Order
Last step of the process is to close the order which happens automatically once the goods are shipped
OE_ORDER_LINES_ALL.flow_status_code =’CLOSED’
OE_ORDER_LINES_ALL.open_flag = ‘N’
Header is closed in the month end, its general oracle standard process
The "AR Reconciliation Report" shows the summary amounts of various AR reports that are used to reconcile AR.
This report mainly has 3 parts
a) Period Beginning Balance
b) Period Activity in different Areas and their differences
c) Period Ending Balance
AR Reconciliation Report
+ Adjustments Register 20
- Invoice Exceptions 0.00
(*) These can occur only in the case of foreign currency transactions.
Oracle 11.5.10.2 Standard Reconciliation can be done at the Operating Unit level alone.
• Run the AGING - 7 BUCKETS report as of the closing of previous month for taking the opening balance for the
current month.
• Run TRANSACTION REGISTER to identify the Invoices, Credit memos, Debit Memos and Supplementary Invoice
details.
• Run APPLIED RECEIPT REGISTER to identify the receipts which are adjusted against invoices/Debit memo.
• Run UN APPLIED RECEIPT REGISTER to identify the receipts which are lying unapplied to any invoice/Debit memo.
• Run ADJUSTMENT REGISTER to identify the small balance adjustments those were done on invoices.
• Run INVOICE EXCEPTION REPORT to adjust the Transaction Register for any transactions that are not opens to
Receivables and therefore do not show up on your Aging.
• Run the AGING - 7 BUCKETS report as of the current months closing for closing balance.
Now compare the AGING - 7 BUCKETS – GL ACCOUNT with the TRIAL BALANCE to see if the balance in the Sub
Ledger as shown by the Aging report is the same as in the Trial Balance.
Query to Identify the Code Combination ID (assuming Account code is of 5 segments separated by a period)
erpSchools Office @ KPHB, Hyderabad. Class room batch starts 19-Jan-13, Contact No: 9000333598
Top of Form
Bottom of Form
Home
Oracle News
Articles
Interview Questions
Scripts
User Guides
Video Tutorials
Jobs
Images
Contact
About
Interfaces and Conversions
Apr142011
Overview:
Oracle provides flexible and flexible tools in the form of Interface programs to import the master and
transactional data like Customers, Invoices, and Sales Orders etc from external systems into Oracle
Applications.
Conversion/Interface Strategy:
Data Mapping
During the data mapping process, list of all the data sets and data elements that will need to be moved
into the Oracle tables as part of conversion are identified. Data mapping tables are prepared as part of
this activity that show what are the data elements that are needed by the target system to meet the
business requirements and from where they will be extracted in the old system.
Download Programs
After the conversion data mapping is complete, download programs are developed that are used to
extract the identified conversion data elements from the current systems in the form of an ASCII flat file.
The structure of the flat file must match the structure of the Oracle standard interface tables. These flat
files generated may be in text form or a comma or space delimited, variable or fixed format data file.
Upload Program
Once the data has been extracted to a flat file, it is then moved to the target file system and the data
from the file is loaded into user defined staging tables in the target database using SQL Loader or
UTL_FILE utilities. Then programs are written and run which validate the data in the staging tables and
insert the same into the Oracle provided standard Interface tables.
Interface Program
Once the interface tables are populated, the respective interface program (each data element interface
has a specific interface program to run) is submitted. The interface programs validate the data, derive
and assign the default values and ultimately populate the production base tables.
Customer conversion
AR Receipts
Lockbox Interface
AP Invoices
Vendor
Purchase Orders
Requisition
Receiving
Journal import
Budget import
Order Import enables you to import Sales Orders into Oracle Applications instead of manually entering
them.
Pre-requisites:
Order Type
Line Type
Items
Customers
Sales Person
Sales Territories
On hand Quantity
Interface tables:
OE_HEADERS_IFACE_ALL
OE_LINES_IFACE_ALL
OE_ACTIONS_IFACE_ALL
OE_ORDER_CUST_IFACE_ALL
OE_PRICE_ADJS_IFACE_ALL
OE_PRICE_ATTS_IFACE_ALL
Base tables:
OE_ORDER_HEADERS_ALL
OE_ORDER_LINES_ALL
Concurrent Program:
Order Import
Validations:
Check for sold_to_org_id. If does not exist, create new customer by calling create_new_cust_info API.
Check for sales_rep_id. Should exist for a booked order.
Notes:
If importing customers together with the order, OE_ORDER_CUST_IFACE_ALL has to be populated and
the base tables are HZ_PARTIES, HZ_LOCATIONS.
1. Entered orders
2. Booked orders
3. Closed orders
Order Import API OE_ORDER_PUB.GET_ORDER and PROCESS_ORDER can also be used to import orders.
OE_HEADERS_IFACE_ALL:
ORIG_SYS_DOCUMENT_REF
ORDER_SOURCE
CONVERSION_RATE
ORG_ID
ORDER_TYPE_ID
PRICE_LIST
SOLD_FROM_ORG_ID
SOLD_TO_ORG_ID
SHIP_TO_ORG_ID
SHIP_FROM_ORG_ID
CUSTOMER_NAME
INVOICE_TO_ORG_ID
OPERATION_CODE
OE_LINES_IFACE_ALL
ORDER_SOURCE_ID
ORIG_SYS_DOCUMENT_REF
ORIG_SYS_LINE_REF
ORIG_SYS_SHIPMENT_REF
INVENTORY_ITEM_ID
LINK_TO_LINE_REF
REQUEST_DATE
DELIVERY_LEAD_TIME
DELIVERY_ID
ORDERED_QUANTITY
ORDER_QUANTITY_UOM
SHIPPING_QUANTITY
PRICING_QUANTITY
PRICING_QUANTITY_UOM
SOLD_FROM_ORG_ID
SOLD_TO_ORG_ID
INVOICE_TO_ ORG_ID
SHIP_TO_ORG_ID
PRICE_LIST_ID
PAYMENT_TERM_ID
The Item Interface lets you import items into Oracle Inventory.
Pre-requisites:
Creating an Organization
Code Combinations
Templates
Interface tables:
MTL_SYSTEM_ITEMS_INTERFACE
Concurrent Program:
Item import
In the item import parameters form, for the parameter ‘set process id’, specify
the ‘set process id’ value given in the mtl_item_categories_interface table. The
parameter ‘Create or Update’ can have any value. Through the import process, we
can only create item category assignment(s). Updating or Deletion of item category assignment is not
supported.
Base tables:
MTL_SYSTEM_ITEMS_B
MTL_ITEM_REVISIONS_B
MTL_CATEGORIES_B
MTL_CATEGORY_SETS_B
MTL_ITEM_STATUS
MTL_ITEM_TEMPLATES
Validations:
Check for valid template id. (Attributes are already set for items, default attributes for
Check for unique item type. Discard the item, if part has non-unique item type.
Load master records and category records only if all validations are passed.
MTL_SYSTEM_ITEMS_INTERFACE:
7 = Import succeeded)
SET_PROCESS_ID = 1
ORGANIZATION_ID
DESCRIPTION
MATERIAL_COST
REVISION
TEMPLATE_ID
SUMMARY_FLAG
ENABLED_FLAG
PURCHASING_ITEM_FLAG
MTL_PARAMETERS.SALES_ACCOUNT)
COST_OF_SALES_ACCOUNT)
MTL_ITEM_CATEGORIES_INTERFACE:
INVENTORY_ITEM_ID or ITEM_NUMBER.
PROCESS_FLAG = 1
SET_PROCESS_ID (The item and category interface records should have the
same set_process_id, if you are importing item and category assignment together)
MTL_ITEM_REVISIONS_INTERFACE:
REVISION
CHANGE_NOTICE
ECN_INITIATION_DATE
IMPLEMENTATION_DATE
IMPLEMENTED_SERIAL_NUMBER
EFFECTIVITY_DATE
ATTRIBUTE_CATEGORY
ATTRIBUTEn
REVISED_ITEM_SEQUENCE_ID
DESCRIPTION
PROCESS_FLAG = 1
TRANSACTION_TYPE = ‘CREATE’
SET_PROCESS_ID = 1
order.
This interface lets you import the on hand inventory into Oracle.
Interface tables:
MTL_TRANSACTIONS_INTERFACE
Concurrent Program:
Launch the Transaction Manager through Interface Manager or explicitly call the API –
INV_TXN_MANAGER_PUB.PROCESS_TRANSACTIONS () to launch a dedicated transaction worker to
process them.
The Transaction Manager picks up the rows to process based on the LOCK_FLAG, TRANSACTION_MODE,
and PROCESS_FLAG. Only records with TRANSACTION_MODE of 3, LOCK_FLAG of ’2′, and
PROCESS_FLAG of ’1′ will be picked up by the Transaction Manager and assigned to a Transaction
Worker. If a record fails to process completely, then PROCESS_FLAG will be set to ’3′ and ERROR_CODE
and ERROR_EXPLANATION will be populated with the cause for the error.
Base Tables:
MTL_ON_HAND_QUANTITIES
MTL_LOT_NUMBERS
MTL_SERIAL_NUMBERS
Validations:
Validate organization_id
Validate disposition_id
Check if the item for the org is lot controlled before inserting into the Lots interface table.
Check if the item for the org is serial controlled before inserting into Serial interface table.
Check if inventory already exists for that item in that org and for a lot.
MTL_TRANSACTIONS_INTERFACE:
TRANSACTION_HEADER_ID (MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL)
TRANSACTION_DATE,
TRANSACTION_TYPE_ID,
SOURCE_CODE,
SOURCE_HEADER_ID,
SOURCE_LINE_ID (Details about the source like Order Entry etc for tracking purposes)
TRANSACTION_SOURCE_ID
Source Type Foreign Key Reference
Account GL_CODE_COMBINATIONS.CODE_COMBINATION_ID
ITEM_SEGMENT1 TO 20,
TRANSACTION_QTY,
TRANSACTION_UOM,
SUBINVENTORY_CODE,
ORGANIZATION_ID,
LOC_SEGMENT1 TO 20.
MTL_TRANSACTION_LOTS_INTERFACE:
TRANSACTION_INTERFACE_ID,
LOT_NUMBER,
LOT_EXPIRATION_DATE,
TRANSACTION_QUANTITY,
SERIAL_TRANSACTION_TEMP_ID (This is required for items under both lot and serial control to identify
child records in mtl_serial_numbers_interface)
MTL_SERIAL_NUMBERS_INTERFACE:
TRANSACTION_INTERFACE_ID,
FM_SERIAL_NUMBER,
TO_SERIAL_NUMBER,
VENDOR_SERIAL_NUMBER
Customer conversion
Interface tables:
RA_CUSTOMERS_INTERFACE_ALL
RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL
Base tables:
RA_CUSTOMERS
RA_ADDRESSES_ALL
RA_CUSTOMER_RELATIONSHIPS_ALL
RA_SITE_USES_ALL
Concurrent program:
Customer Interface
Validations:
Check if the location already exists in HZ_LOCATIONS. If does not exist, create new location.
RA_CUSTOMERS_INTERFACE_ALL:
ORIG_SYSTEM_CUSTOMER_REF
SITE_USE_CODE
ORIG_SYSTEM_ADDRESS_REF
CUSTOMER_NAME
CUSTOMER_NUMBER
CUSTOMER_STATUS
PRIMARY_SITE_USE_FLAG
LOCATION
ADDRESS1
ADDRESS2
ADDRESS3
ADDRESS4
CITY
STATE
PROVINCE
COUNTY
POSTAL_CODE
COUNTRY
CUSTOMER_ATTRIBUTE1
CUSTOMER_ATTRIBUTE2
CUSTOMER_ATTRIBUTE3
CUSTOMER_ATTRIBUTE4
CUSTOMER_ATTRIBUTE5
LAST_UPDATED_BY
LAST_UPDATE_DATE
CREATED_BY
CREATION_DATE
ORG_ID
CUSTOMER_NAME_PHONETIC
RA_CUSTOMER_PROFILES_INT_ALL:
INSERT_UPDATE_FLAG
ORIG_SYSTEM_CUSTOMER_REF
ORIG_SYSTEM_ADDRESS_REF
CUSTOMER_PROFILE_CLASS_NAME
CREDIT_HOLD
LAST_UPDATED_BY
LAST_UPDATE_DATE
CREATION_DATE
CREATED_BY
ORG_ID
RA_CONTACT_PHONES_INT_ALL:
ORIG_SYSTEM_CONTACT_REF
ORIG_SYSTEM_TELEPHONE_REF
ORIG_SYSTEM_CUSTOMER_REF
ORIG_SYSTEM_ADDRESS_REF
INSERT_UPDATE_FLAG
CONTACT_FIRST_NAME
CONTACT_LAST_NAME
CONTACT_TITLE
CONTACT_JOB_TITLE
TELEPHONE
TELEPHONE_EXTENSION
TELEPHONE_TYPE
TELEPHONE_AREA_CODE
LAST_UPDATE_DATE
LAST_UPDATED_BY
LAST_UPDATE_LOGIN
CREATION_DATE
CREATED_BY
EMAIL_ADDRESS
ORG_ID
Customer API
API Details:
Exec dbms_application_info.set_client_info(’204′);
HZ_CUST_ACCOUNT_V2PUB.CREATE_CUST_ACCOUNT()
HZ_CUST_ACCOUNT_V2PUB.CUST_ACCOUNT_REC_TYPE
HZ_PARTY_V2PUB.ORGANIZATION_REC_TYPE
HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE
HZ_LOCATION_V2PUB.CREATE_LOCATION()
HZ_LOCATION_V2PUB.LOCATION_REC_TYPE
Create a party site using party_id you get from step 2 and location_id from step 3.
HZ_PARTY_SITE_V2PUB.CREATE_PARTY_SITE()
HZ_PARTY_SITE_V2PUB.PARTY_SITE_REC_TYPE
Create an account site using account_id you get from step 2 and party_site_id from step 4.
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_ACCT_SITE()
HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_ACCT_SITE_REC_TYPE
Create an account site use using cust_acct_site_id you get from step 5 ans site_use_code = ‘BILL_TO’.
HZ_CUST_ACCOUNT_SITE_V2PUB.CREATE_CUST_SITE_USE()
HZ_CUST_ACCOUNT_SITE_V2PUB.CUST_SITE_USE_REC_TYPE
HZ_CUSTOMER_PROFILE_V2PUB.CUSTOMER_PROFILE_REC_TYPE
Base table:
HZ_PARTIES
HZ_PARTY_SITES
HZ_LOCATIONS
HZ_CUST_ACCOUNTS
HZ_CUST_SITE_USES_ALL
HZ_CUST_ACCT_SITES_ALL
HZ_PARTY_SITE_USES
Validations:
Check if the location already exists in HZ_LOCATIONS. If does not exist, create new location.
http://www.erpschools.com/Apps/oracle-applications/articles/financials/Receivables/Customer-TCA-
Architecture-and-API/index.aspx
Auto Invoice interface
This interface is used to import Customer invoices, Credit memos, Debit memos and On Account credits.
Pre-requisites:
Set of Books
Code combinations
Items
Sales representatives
Customers
Payment Terms
Transaction Types
Freight Carriers
FOB
Batch Sources
Accounting Rules
Interface tables:
RA_INTERFACE_LINES_ALL
RA_INTERFACE_SALESCREDITS
RA_INTERFACE_DISTRIBUTIONS
Base tables:
RA_BATCHES
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
AR_PAYMENT_SCHEDULES_ALL RA_CUSTOMER_TRX_LINE_SALESREPS
RA_CUST_TRX_GL_DIST_ALL
RA_CUSTOMER_TRX_TYPES_ALL
Concurrent Program:
Validations:
Check for amount, batch source name, conversion rate, conversion type.
RA_INTERFACE_LINES_ALL:
AGREEMENT_ID
COMMENTS
CONVERSION_DATE
CONVERSION_RATE
CONVERSION_TYPE
CREDIT_METHOD_FOR_ACCT_RULE
CREDIT_METHOD_FOR_INSTALLMENTS
CURRENCY_CODE
CUSTOMER_BANK_ACCOUNT_ID
CUST_TRX_TYPE_ID
DOCUMENT_NUMBER
DOCUMENT_NUMBER_SEQUENCE_ID
GL_DATE
HEADER_ATTRIBUTE1–15
HEADER_ATTRIBUTE_CATEGORY
INITIAL_CUSTOMER_TRX_ID
INTERNAL_NOTES
INVOICING_RULE_ID
ORIG_SYSTEM_BILL_ADDRESS_ID
ORIG_SYSTEM_BILL_CONTACT_ID
ORIG_SYSTEM_BILL_CUSTOMER_ID
ORIG_SYSTEM_SHIP_ADDRESS_ID
ORIG_SYSTEM_SHIP_CONTACT_ID
ORIG_SYSTEM_SHIP_CUSTOMER_ID
ORIG_SYSTEM_SOLD_CUSTOMER_ID
ORIG_SYSTEM_BATCH_NAME
PAYMENT_SERVER_ORDER_ID
PREVIOUS_CUSTOMER_TRX_ID
PRIMARY_SALESREP_ID
PRINTING_OPTION
PURCHASE_ORDER
PURCHASE_ORDER_DATE
PURCHASE_ORDER_REVISION
REASON_CODE
RECEIPT_METHOD_ID
RELATED_CUSTOMER_TRX_ID
SET_OF_BOOKS_ID
TERM_ID
TERRITORY_ID
TRX_DATE
TRX_NUMBER
Receipt API
To bring in Unapplied Receipts and Conversion Receipts for Open Debit items to reduce the balance to
the original amount due.
Pre-requisites:
Set of Books
Code combinations
Items
Quick Codes
Sales representatives
Customers
API:
AR_RECEIPT_API_PUB.CREATE_CASH
AR_RECEIPT_API_PUB.CREATE_AND_APPLY
Base tables:
AR_CASH_RECEIPTS
Validations:
Check the currency and the exchange rate type to assign the exchange rate.
Lockbox interface
AutoLockbox lets us automatically process receipts that are sent directly to the bank instead of manually
feeding them in Oracle Receivables.
1. Import: During this step, Lockbox reads and formats the data from your bank file
script.
2. Validation: The validation program checks data in this interface table for
AR_INTERIM_CASH_RCPT_LINES_ALL).
3. Post QuickCash: This step applies the receipts and updates your customer’s
balances.
Pre-Requisites:
Banks
Receipt Class
Payment Method
Receipt Source
Lockbox
Transmission format
Interface tables:
AR_PAYMENTS_INTERFACE_ALL (Import
data from bank file)
AR_INTERIM_CASH_RECEIPTS_ALL
AR_INTERIM_CASH_RCPT_LINES_ALL (Validate data in interface table and place in quick cash tables)
Base Tables:
AR_CASH_RECEIPTS
AR_RECEIVABLES_APPLICATIONS
AR_ADJUSTMENTS
AR_DISTRIBUTIONS_ALL
AR_PAYMENT_SCHEDULES_ALL
Concurrent program:
Lockbox
Validations:
STATUS
RECORD_TYPE
LOCKBOX_NUMBER
BATCH_NAME
TRANSIT_ROUTING_NUMBER
ACCOUNT
CHECK_NUMBER
REMITTANCE_AMOUNT
DEPOSIT_DATE
ITEM_NUMBER
CURRENCY_CODE
DEPOSIT_TIME
AP invoice interface
This interface helps us to import vendor invoices into Oracle applications from external systems into
Oracle Applications.
Pre-requisites:
Set of Books
Code combinations
Employees
Lookups
Interface tables:
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
Base tables:
Concurrent program:
Validations:
AP_INVOICES_INTERFACE:
INVOICE_ID
INVOICE_NUM
INVOICE_DATE
VENDOR_NUM
VENDOR_SITE_ID
INVOICE_AMOUNT
INVOICE_CURRENCY_CODE
EXCHANGE_RATE
EXCHANGE_RATE_TYPE
EXCHANGE_DATE
DESCRIPTION
SOURCE
PO_NUMBER
PAYMENT_METHOD_LOOKUP_CODE
PAY_GROUP_LOOKUP_CODE
ATTRIBUTE1 TO 15
ORG_ID
AP_INVOICE_LINES_INTERFACE:
INVOICE_ID
INVOICE_LINE_ID
LINE_TYPE_LOOKUP_CODE
AMOUNT
DESCRIPTION
TAX_CODE
PO_NUMBER
PO_LINE_NUMBER
PO_SHIPMENT_NUM
PO_DISTRIBUTION_NUM
PO_UNIT_OF_MEASURE
QUANTITY_INVOICED
DIST_CODE_CONCATENATED
DIST_CODE_COMBINATION_ID
ATTRIBUTE1
ATTRIBUTE2
ATTRIBUTE3
ATTRIBUTE4
ATTRIBUTE5
ORG_ID
Vendor conversion/interface
This interface is used to import suppliers, supplier sites and site contacts into Oracle applications.
Payment terms
Pay Groups
CCID
Supplier classifications
Bank Accounts
Interface tables:
AP_SUPPLIERS_INT
AP_SUPPLIER_SITES_INT
AP_SUP_SITE_CONTACT_INT
Base Tables:
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
Interface programs:
Validations:
AP_SUPPLIERS_INT:
AP_SUPPLIER_SITES_INT:
AP_SUP_SITE_CONTACTS_INT:
The Purchasing Document Open Interface concurrent program was replaced by two new concurrent
programs Import Price Catalogs and Import Standard Purchase Orders. Import Price Catalogs concurrent
program is used to import Catalog Quotations, Standard Quotations, and Blanket Purchase Agreements.
Import Standard Purchase Orders concurrent program is used to import Unapproved or Approved
Standard Purchase Orders.
Pre-requisites:
Buyers
Line Types
Items
Interface Tables:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
PO_INTERFACE_ERRORS (Fallouts)
Interface Program:
Base Tables:
PO_HEADERS_ALL
PO_LINES_ALL
PO_DISTRIBUTIONS_ALL
PO_LINE_LOCATIONS_ALL
Validations:
Header:
Lines:
General:
PO_HEADERS_INTERFACE:
INTERFACE_HEADER_ID (PO_HEADERS_INTERFACE_S.NEXTVAL), BATCH_ID, ORG_ID,
INTERFACE_SOURCE_CODE, ACTION (‘ORIGINAL’,'UPDATE’,'REPLACE’), GROUP_CODE,
DOCUMENT_TYPE_CODE, PO_HEADER_ID (NULL), RELEASE_ID, RELEASE_NUM, CURRENCY_CODE, RATE,
AGENT_NAME, VENDOR_ID, VENDOR_SITE_ID, SHIP_TO_LOCATION, BILL_TO_LOCATION,
PAYMENT_TERMS
PO_LINES_INTERFACE:
PO_DISTRIBUTIONS_INTERFACE:
Interface Tables:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
Interface program:
Base tables:
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
Example:
Suppose you want to create a blanket with one line and two price breaks and the details for the price
break are as below:
’31-JUN-2006′
’01-JAN-2007′
To create the above the BPA, you would create ONE record in PO_HEADERS_INTERFACE and THREE
records in PO_LINES_INTERFACE
LINE1: It will have only the line information. LINE NUM would be 1.
LINE2: For the first Price Break details, LINE NUM will be the same as above i.e. 1. SHIPMENT_NUM
would be 1 and SHIPMENT_TYPE would be ‘PRICE BREAK’
LINE3: For the second Price Break details, LINE NUM will be the same as above i.e. 1. SHIPMENT_NUM
would be 2 and SHIPMENT_TYPE would be ‘PRICE BREAK’
All the line-level records above must have the same INTERFACE_HEADER_ID.
http://www.erpschools.com/Apps/oracle-applications/articles/financials/Purchasing/Import-Blanket-
Purchase-Agreements/index.aspx
Requisition import
You can automatically import requisitions into Oracle Applications using the Requisitions Open Interface
Pre-requisites:
Set of Books
Code combinations
Employees
Items
Define a Requisition Import Group-By method in the Default region of the Purchasing
Options window.
Associate a customer with your deliver-to location using the Customer Addresses
Interface tables:
PO_REQUISITIONS_INTERFACE_ALL
PO_REQ_DIST_INTERFACE_ALL
Base tables:
PO_REQUISITIONS_HEADERS_ALL
PO_REQUISITION_LINES_ALL
PO_REQ_DISTRIBUTIONS_ALL
Concurrent program:
REQUISITION IMPORT
Validations:
Requisitions)
DESTINATION_TYPE_CODE
AUTHORIZATION_STATUS
PREPARER_ID or PREPARER_NAME
QUANTITY
DESTINATION_ORGANIZATION_ID or DESTINATION_ORGANIZATION_
CODE
DELIVER_TO_LOCATION_ID or DELIVER_TO_LOCATION_CODE
DELIVER_TO_REQUESTOR_ID or DELIVER_TO_REQUESTOR_NAME
ORG_ID
DESTINATION_TYPE_CODE is ‘INVENTORY’)
PO_REQ_DIST_INTERFACE_ALL:
DISTRIBUTION_NUMBER
DESTINATION_ORGANIZATION_ID
DESTINATION_TYPE_CODE
INTERFACE_SOURCE_CODE
ORG_ID
The Receiving Open Interface is used for processing and validating receipt data that
Pre-requisites:
Set of Books
Code combinations
Employees
Items
Interface tables:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
PO_INTERFACE_ERRORS
Concurrent program:
Base tables:
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
RCV_TRANSACTIONS
Validations:
RCV_HEADERS_INTERFACE:
HEADER_INTERFACE_ID
GROUP_ID
PROCESSING_STATUS_
CODE
RECEIPT_SOURCE_CODE
TRANSACTION_TYPE
SHIPMENT_NUM
RECEIPT_NUM
VENDOR_NAME
SHIP_TO_
ORGANIZATION_CODE
SHIPPED_DATE
INVOICE_NUM
INVOICE_DATE
TOTAL_INVOICE_
AMOUNT
PAYMENT_TERMS_ID
EMPLOYEE_NAME
RCV_TRANSACTIONS_INTERFACE:
INTERFACE_TRANSACTION_ID
GROUP_ID
TRANSACTION_DATE
PROCESSING_STATUS_CODE =’PENDING’
CATEGORY_ID
QUANTITY
UNIT_OF_MEASURE
ITEM_DESCRIPTION
ITEM_REVISION
EMPLOYEE_ID
AUTO_TRANSACT_CODE
SHIP_TO_LOCATION_ID
RECEIPT_SOURCE_CODE
TO_ORGANIZATION_CODE
SOURCE_DOCUMENT_CODE
PO_HEADER_ID
PO_RELEASE_ID
PO_LINE_ID
PO_LINE_LOCATION_ID
PO_DISTRIBUTION_ID
SUBINVENTORY
HEADER_INTERFACE_ID
DELIVER_TO_PERSON_NAME
DELIVER_TO_LOCATION_CODE
VALIDATION_FLAG
ITEM_NUM
VENDOR_ITEM_NUM
VENDOR_ID
VENDOR_SITE_ID
ITEM_ID
ITEM_DESCRIPTION
SHIP_TO_LOCATION_ID
GL Journal interface
This interface lets you import journals from other applications like Receivables, Payables etc to integrate
the information with General Ledger.
Pre-requisites:
Set of Books
Code Combinations
Currencies
Categories
Journal Sources
Interface tables:
GL_INTERFACE
Base tables:
GL_JE_HEADERS
GL_JE_LINES
GL_JE_BACTHES
Concurrent Program:
Journal Import
Validations:
Validate SOB, journal source name, journal category name, actual flag
A – Actual amounts
B – Budget amounts
E – Encumbrance amount
If you enter E in the interface table, then enter appropriate encumbrance ID, if
Check if accounting date or GL date based period name is valid (i.e., not closed).
GL_INTERFACE:
STATUS
SET_OF_BOOKS_ID
ACCOUNTING_DATE
CURRENCY_CODE
DATE_CREATED
CREATED_BY
ACTUAL_FLAG
USER_JE_CATEGORY_NAME
USER_JE_SOURCE_NAME
CURRENCY_CONVERSION_DATE
ENCUMBRANCE_TYPE_ID
BUDGET_VERSION_ID
USER_CURRENCY_CONVERSION_TYPE
CURRENCY_CONVERSION_RATE
SEGMENT1 to
ENTERED_DR
ENTERED_CR
ACCOUNTED_DR
ACCOUNTED_CR
TRANSACTION_DATE
PERIOD_NAME
JE_LINE_NUM
CHART_OF_ACCOUNTS_ID
FUNCTIONAL_CURRENCY_CODE
CODE_COMBINATION_ID
DATE_CREATED_IN_GL
GROUP_ID
GL budget interface
Budget interface lets you load budget data from external sources into Oracle Applications.
Pre-requisites:
Set of Books
Code Combinations
Interface tables:
GL_BUDGET_INTERFACE
Base tables:
GL_BUDGETS
GL_BUDGET_ASSIGNMENTS
GL_BUDGET_TYPES
Concurrent program:
Budget Upload
Validations:
GL_BUDGET_INTERFACE:
BUDGET_NAME NOT
BUDGET_ENTITY_NAME
CURRENCY_CODE
FISCAL_YEAR
UPDATE_LOGIC_TYPE
BUDGET_ENTITY_ID
SET_OF_BOOKS_ID
CODE_COMBINATION_ID
BUDGET_VERSION_ID
PERIOD_TYPE
DR_FLAG
STATUS
ACCOUNT_TYPE
PERIOD1_AMOUNT through PERIOD60_AMOUNT
This interface lets you load the rates automatically into General Ledger.
Pre-requisites:
Currencies
Interface tables:
GL_DAILY_RATES_INTERFACE
Base tables:
GL_DAILY_RATES
GL_DAILY_CONVERSION_TYPES
Concurrent Program:
You do not need to run any import programs. The insert, update, or deletion of rates in
GL_DAILY_RATES is done automatically by database triggers on the GL_DAILY_RATES_INTERFACE. All
that is required is to develop program to populate the interface table with daily rates information.
Validations:
Check if
FROM_CURRENCY and TO_CURRENCY are valid.
GL_DAILY_RATES_INTERFACE:
FROM_CURRENCY
TO_CURRENCY
FROM_CONVERSION_DATE
TO_CONVERSION_DATE
USER_CONVERSION_TYPE
CONVERSION_RATE
INVERSE_CONVERSION_RATE
Related Articles:
admin
Srini says:
Hi,
I am working on Purchasing (PO)Conversions. Can you please share the information about the Contract
Purchase Agreements import? Is there any API or open interface program? If so please give the details
of the same.
Thanks,
Srini
Bharadwaj says:
Hi Prudhvi, Thanks for this useful blog and sincerely appreciate your efforts and help to the oracle
community. I am new to conversions in manufacturing and need some help from you in some approach
details.let me know how can i communicate with you ,prudhvi.
Thanks
Bharadwaj
Thamizhan says:
Really good for beginners. This article will provide a very good idea about Conversion/Interface related
programs. It is good to share with others too. Good job and keep us alive with current updates.
santhosh says:
nice info
syed says:
binsar says:
Hi Prudhvi,
I just wondering if there is any API which can be used to do AP Invoice matching to Receipts ?
Appreciate your thoughts on this. …
Thank you
Binsar
Mukul says:
swathi says:
Hi… can you please share “import bill and routing” open interface validation code.
WOW…Excellent Effort
Sambasiva says:
Hi,
This is Sambasiva. please can you send the Inventory Status Change Interface details..
babita says:
how to create java based interface for healthcare and how to connect this interface to oracle 10g to
store this data in oracle10g through this interface.please mail me full document
Sana says:
Dear sir ,
the article which you have given is very useful for beginners but along with that if you could have
provide the procedure and pakages coding of the interfaces which you have given can be more helpful.I
appreciate if you could do the needful.
Thank You
prasad says:
eshwer says:
November 23, 2011 at 2:30 pm
In GL interface when we are submitting Standard concurrent program data will be loaded first into
GL_JE_HEADERS (OR)
GL_JE_BATCHES
adarshan says:
I love this. This most important who want to know about interfaces and conversions. could send bank
conversion source code through API’s i dont have experience in API’s.
Thanks in advance
Adarsh
ycadarshanreddy@gmail.com
vijay says:
U did Good Job. thanks a lot for providing valible information. We should be help to others
tirumalarao says:
the information you had provided is really use full THANKS BROTHER
G MUNIRAMAIAH says:
Ravikumar says:
Krishna says:
TCalado says:
Hello,
Where is accounting_date when transferred from gl_interface to base tables ? I’m not finding the date
I’m passing.
Thanks in advance
krrish says:
this data is very nice who wats to know about intefaces and conversions…..
Jithendra says:
Thank you very much Prudhvi. The article is very much useful and is like a ready recokner. Thank you
very much for sharing the info.
mallikarjuna says:
How to handle the errors in interface and how to send this errors to client pls tell?
Prasant says:
Can any one plz send me the open sales order conversion script..
Rasheed says:
Don says:
Could you let me know what are the DB packages for each of the stages for Lockbox?
Thanks in advance
Don
sreenath says:
It is very useful to learn for new members/Freshers. Keep it up. Really good.
This is most, import Article, i am very thankful, to those who write this, it is very helpful for me and
others also
Lakshmikanth says:
This Article which you have given is very much usefull for every one who wants to know about interfaces
and conversions………
Regards
Lakshmikanth
Top of Form
Connect with:
Name *
E-mail *
URI
CAPTCHA Code *
Your Comment
You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b>
<blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Bottom of Form
Like erpSchools !!
About Me
My short bio
Prudhvi Avuthu
Email: Prudhvi@erpschools.com
Categories
Alerts
Articles
Data Loader
Discoverer
Financials
Forms
Fusion Middleware
General
HRMS
iexpenses
Interview Questions
Manufacturing
Oracle Reports
Order Management
Payables
Personalization
Purchasing
Receivables
Scripts
Shell Script
SQL Loader
Tools
Workflow
XML Publisher
Connect
Register
Log in
Entries RSS
Comments RSS
WordPress.org
Beginner Articles
Recent Posts