Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Introduction of myself:
Well its 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 its a flagship company of A Group manufacturing Steering parts located at Chennai. Its
a Support project where I was handling day to day issues. My Next project was B Ltd located at Mumbai, its an up
gradation project from 11.5.10.2 to 12.1.1 version .Then my next project was C Ltd, and its 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.
Its 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 endusers 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
What is MRC?
How to prepare
FSG?
What is a Roll
up Group?
What is
Translation?
What is
Revaluation?
What is
Cumulative
translation
Adjustment
Account?
What is
Recurring
journal? Types
of Recurring
journal?
What is the
difference in
structure
between R12
and 11i?
On what basis
we create
operating units?
What is org_id
and
organisation_id?
What is BR 100
and which stage
we are
preparing?
What is
Flexfield?
What is KFF
(Key
Flexfield)?
What is Key
flexfield name
in GL?
What is DFF
(Descriptive
Flexfield)?
How to create
DFF?
Why Allow
Dynamic
Inserts?
Use of Cross
Validate
Segments?
What is
segment? How
many no. of
segments in
Accounting
Flexfield?
How many
flexfield
structures can
you create for
GL?
What is value
set?
It is a set of values
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
require
validations?
No
How many
Different
Security Type in
value set?
No security,Hierarchical,Non-Heirarchical
What is
Flexfield
qualifiers?
Types and
Purpose of
Flexfield
Qualifier?
What is
Segment
qualifiers?
How do you
define parent
Child
relationship for
segment values?
What is Security
Rule?
What is
CVR(Cross
validation rule)?
Never Opened,Open,Closed,Permanently
closed,future
What is an Accounting
calender?
Name,Prefix month,type,year,Num,from,To,If
adjustment then click on Adjusting
What is transaction
calender?
What is monetary
currency?
Set up,journal,category
GL_BUDGET
GL_BUDGET_types
GL_DAILY_RATES
GL_Consolidation
GL_Balances
Asset,Liability,Expense,revenue,Owners Equity
What is COA?
Segment,Value set,Flexfield
qualifier,Values,Segment Qualifier
What is Suspense
Account?
What is Encumbrance
Account?Types?
With General Ledger you can record preexpenditures commonly known as encumbrances.
The primary purpose of tracking encumbrances is
to avoid overspending a budget. Encumbrances
can also be used to predict cash outflow and as a
general planning tool.
Predefined Types:-1.Commitment,2.Obligation
No
What is Budget?Types of
Budget?
AP->SLA->GL
In the case of
modification of
entry,What account taking
from payble to GL?
SLA?
What is the pre requisite
for a journal?
Period,currency,Category,Source
GL_BUDGET_INTERFACE
GL_DAILY_RATES_INTERFACE
GL_IEA_INTERFACE
GL_IEA_INTERFACE
GL_INTERFACE
GL_INTERFACE_CONTROL
GL_INTERFACE_HISTORY
GL_ACCOUNT_HIERARCHIES
GL_ALLOC_BATCHES
GL_ALLOC_FORMULAS
GL_ALLOC_FORMULA_LINES
GL_ALLOC_HISTORY
GL_BALANCES
GL_BUDGETS
GL_BUDGET_ASSIGNMENTS
GL_BUDGET_ASSIGNMENT_RANGE
S
GL_INTERFACE
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
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
Rule-based accounting engine, toolset & repository to support E-Biz modules
There are no SLA responsibilities
Users do not login to SLA
How to join
GL tables with
XLA
(SubLedger
Accounting)
tables
GL_JE_BATCHES
(je_batch_id)
.=>
GL_JE_HEADERS
(je_header_id)
.=>
GL_JE_HEADERS
(je_batch_id)
GL_JE_LINES
(je_header_id)
GL_IMPORT_REF
ERENCES
(je_header_id,
je_line_num)
GL_JE_LINES
(je_header_id,
je_line_num)
.=>
GL_IMPORT_REFER
ENCES
(gl_sl_link_table,
gl_sl_link_id)
.=>
XLA_AE_LINES
(gl_sl_link_table
, gl_sl_link_id)
XLA_AE_LINES
(application_id,
ae_header_id)
.=>
XLA_AE_HEADE
RS
(application_id,
ae_header_id)
XLA_AE_HEADERS
(application_id,
event_id)
.=>
XLA_EVENTS
(application_id,
event_id)
.=>
XLA.XLA_TRANS
ACTION_ENTITIE
S
(application_id,
entity_id)
XLA_EVENTS
(application_id,
entity_id)
->
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.
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).
FINAL POST will create journal entries in Final Mode, Transfer them to GL and Post them.
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').
Scinario-II:Create Accounting (Concurrent Program): (For more entities
1. Accounting Mode: Draft
It is same as Draft online accounting.
2. Accounting Mode: Final, Transfer to GL: No
It is same as Final online accounting.
3. Accounting Mode: Final, Transfer to GL: Yes, Post to GL: No
Once it is finally accounted you can NOT run create accounting on the particular transaction
(specifically on that event).
XLA_AE_HEADERS.accounting_entry_status_code is 'F'
XLA_EVENTS.process_status_code is 'P'
XLA_EVENTS.event_status_code is 'P'
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'
GL_JE_HEADERS.status is 'U'.
4. Accounting Mode: Final, Transfer to GL: Yes, Post to GL: Yes
It is same as Final Post online accounting.
Key Tables For Sub-Ledger
XLA_AE_HEADERS xah
XLA_AE_LINES xal
XLA_TRANSACTION_ENTITIES xte
XLA_DISTRIBUTION_LINKS xdl
GL_IMPORT_REFERENCES gir
Below are the possible joins between these XLA Tables
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
xah.application_id = (Different value based on Module)
xte.entity_code =
'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'
XLA_DISTRIBUTION_LINKS table join based on Source Distribution Types
xdl.source_distribution_type = 'AP_PMT_DIST'
and xdl.source_distribution_id_num_1 = AP_PAYMENT_HIST_DISTS.payment_hist_dist_id
--------------xdl.source_distribution_type = 'AP_INV_DIST'
and xdl.source_distribution_id_num_1 = AP_INVOICE_DISTRIBUTIONS_ALL.invoice_distribution_id
--------------xdl.source_distribution_type = 'AR_DISTRIBUTIONS_ALL'
and xdl.source_distribution_id_num_1 = AR_DISTRIBUTIONS_ALL.line_id
and AR_DISTRIBUTIONS_ALL.source_id =
AR_RECEIVABLE_APPLICATIONS_ALL.receivable_application_id
--------------xdl.source_distribution_type = 'RA_CUST_TRX_LINE_GL_DIST_ALL'
and xdl.source_distribution_id_num_1 = RA_CUST_TRX_LINE_GL_DIST_ALL.cust_trx_line_gl_dist_id
--------------xdl.source_distribution_type = 'MTL_TRANSACTION_ACCOUNTS'
and xdl.source_distribution_id_num_1 = MTL_TRANSACTION_ACCOUNTS.inv_sub_ledger_id
--------------xdl.source_distribution_type = 'WIP_TRANSACTION_ACCOUNTS'
and xdl.source_distribution_id_num_1 = WIP_TRANSACTION_ACCOUNTS.wip_sub_ledger_id
--------------xdl.source_distribution_type = 'RCV_RECEIVING_SUB_LEDGER'
and xdl.source_distribution_id_num_1 = RCV_RECEIVING_SUB_LEDGER.rcv_sub_ledger_id
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++
Accounts
Payable
Payable
Particulars
R12
11i
Invoice
Yes
No
Invoice
Yes
No
Invoice
Yes
No
Invoice
Yes
No
Invoice
Yes
At invoice header
Invoice
Yes
No
Invoice
No
Yes
Invoice
Header level
Near to Match
Invoice
DFF at Header
Yes
No
Invoice
DFF at Distribution
Yes
No
Invoice
Create Accounting
Draft,Final,Fina
only
l Post
Invoice
Yes
No
Invoice
Yes
No
Payment
Yes
No
Payment
Yes
No
Payment
Payment manager
Yes
Payment Batch
Supplier
HTML Form
Yes
No(Java Form)
Supplier
MOAC Access
Yes
No
Supplier
Yes
No
Supplier
No
Yes
Supplier
Yes
No
Supplier
No
Yes
Payable
Option
Accounting,Method,Transfe
r to GL
No
Yes
Payable
system set
up
Yes
At financial
option
AR
Particulars
R12
11i
Invoice
Auto GL date
Yes
Customized
Invoice
Copy invoice
Yes
No
Invoice
Create Accounting
Draft,Final,Fina
only
l Post
Receipt
Customer master
Yes
No
Receipt
AP-AR Netting
Yes
No
Receipt
Receipt
Yes
No
Set Up
EB tax
Yes
No
Accounts
Receivab
le
Consolidated
billing (Proxima
payment term)
Receipt
Automated Refunds
Yes
No
Receipt
Daily revenue
Yes
No
Receipt
Revenue Contingencies
Yes
No
Receipt
Yes
No
Set Up
Sub ledger
Accounting(SLA)
Yes
No
Set Up
Yes
No
Set Up
Yes
No
GL
Particulars
R12
11i
Journal
Yes
No
Journal
Approve option
Yes
No
Journal
Yes
No
Ledger
Yes
3C Currency,
COA, Calendar
(Set of books)
Ledger
Sub ledger
Accounting(SLA)
Yes
No
Ledger
Yes
No
FA
Particulars
R12
11i
Depreciatio
n
Auto
Manual
Ledger
Sub ledger
Yes
No
General
Ledger
Fixed
Asset
Accounting(SLA)
Ledger
Yes
No
Particulars
R12
11i
Cash
Manage
ment
CM
Set up
Yes
Internal Banks
defined in AP and
that is shared by
AP,AR,CE,
Payroll and
Treasury and they
are bank accounts
often copy in
multiple
Operating Units
Set up
Yes
Bank Define At
Operating Unit
Level
Ledger
Yes
No
AP
Asset
GL
Document Description
Business Process
Architecture
(BP)
BP.010
BP.020
BP.030
BP.040
BP.050
BP.060
BP.070
BP.080
BP.090
Business
Requirements
Definition (RD)
RD.010
RD.020
RD.030
RD.040
RD.050
RD.060
RD.070
RD.080
Business
Requirements
Mapping
BR.010
BR.020
BR.030
BR.040
BR.050
BR.060
BR.070
BR.080
BR.090
BR.100
BR.110
Application and
Technical
Architecture
(TA)
TA.010
TA.020
TA.030
TA.040
TA.050
TA.060
TA.070
TA.080
TA.090
TA.100
TA.110
TA.120
TA.130
TA.140
TA.150
Module Design
and Build (MD)
MD.010
MD.020
MD.030
MD.040
MD.050
MD.060
MD.070
MD.080
MD.090
MD.100
MD.110
MD.120
Data
Conversion
(CV)
CV.010
CV.020
CV.030
CV.040
CV.050
CV.060
CV.070
CV.080
CV.090
CV.100
CV.110
CV.120
CV.130
Documentation
(DO)
DO.010
DO.020
DO.030
Prepare glossary
DO.040
DO.050
DO.060
DO.070
DO.080
DO.090
Business System
Testing (TE)
TE.010
TE.020
TE.030
TE.040
TE.050
TE.060
TE.070
TE.080
TE.090
TE.100
TE.110
TE.120
TE.130
PERFORMAC
E
TESTING(PT)
PT.010
PT.020
PT.030
PT.040
PT.050
PT.060
PT.070
PT.080
PT.090
PT.100
PT.110
PT.120
Adoption and
Learning (AP)
AP.010
AP.020
AP.030
AP.040
AP.050
AP.060
AP.070
AP.080
AP.090
AP.100
AP.110
AP.120
AP.130
AP.140
AP.150
AP.160
AP.170
AP.180
Production
Migration (PM)
PM.010
PM.020
PM.030
PM.040
PM.050
Set Up Applications
PM.060
PM.070
PM.080
Begin Production
PM.090
PM.100
Maintain System
PM.110
PM.120
PM.130
PM.140
Responsibility
Menu group
Request Group
Data
group
Application
DJ_India Local
Receivables
AR_NAVIGATE_GUI
- India
JAI_Receivables
_RG
Standa
rd
Asia/Pacific
Localizations
DJ_India Local
Payables
AP_NAVIGATE_GUI
12 - India
JAI_Payables_R
G
Standa
rd
Asia/Pacific
Localizations
DJ_HR_Foundation
HR Foundation
HR Foundation
Standa
rd
Human
Resources
DJ Cash Mgmt
CE_SUPERUSER
Cash Forecast
Reports
Standa
rd
Cash
Management
DJ Desktop
Integrator
Desktop
Integration Menu
Standa
rd
Web
Applications
Desktop
Integrator
DJ Fixed Assets
Integrator
FA_WEBADI_MENU
Standa
rd
Assets
DJ India Fixed
Assets
FA_MAIN
Standa
rd
Assets
India HRMS
Navigator
IN HRMS
Reports and
Processes
Standa
rd
Human
Resources
INV_NAVIGATE India
JAI_Inventory_R
G
Standa
rd
Asia/Pacific
Localizations
DJ Primary Ledger
User
GL_SUPERUSER
GL Concurrent
Program Group
Standa
rd
General
Ledger
DJ Secondary
Ledger User
GL_SUPERUSER
GL Concurrent
Program Group
Standa
rd
General
Ledger
DJ Tax Manager
E-Business Tax
Responsibility
menu
Standa
rd
Oracle
iProcurement
DJ India Local
Order
Management
ONT_SUPER_USER
- India
JAI_OrderMgmt
_RG
Standa
rd
Asia/Pacific
Localizations
DJ Fixed Assets
Manager
FA_MAIN
Standa
rd
Assets
Password
New password
DJ HEAD FINANCE
welcome
xxxxxxx
DJ OU1 USER
welcome
xxxxxxx
Application
Name
Description
Human
Resources
DJL_GRADE_FLEX
FIELD
DJL_GRADE_FLEX
FIELD
People Group
Flex field
Payroll
DJL_PEOPLE_GRO
UP_FLEXFIELD
DJL_PEOPLE_GRO
UP_FLEXFIELD
Human
Resources
DJL_JOB_FLEXFIE
LD
DJL_JOB_FLEXFIE
LD
Cost Allocation
KF
Payroll
DJL_COST_ALLOC
_FLEXFIELD
DJL_COST_ALLOC
_FLEXFIELD
Human
Resources
DJL_POSITION_FL
EXFIELD
DJL_POSITION_FL
EXFIELD
Competence Flex
field
Human
Resources
DJL_COMPETENC
E_FLEXFIELD
DJL_COMPETENC
E_FLEXFIELD
General Ledger
DJL_COA_ACCOU
NTING_FLEXFIEL
D
DJL_COA_ACCOU
NTING_FLEXFIEL
D
Accounting Flex
field
Flexfield
Value set
Security
type
Flexfield
Qualifier
Allow
dynamic
inserts
Grade
Flex field
DJL_GRA
DE_NAM
No
Security
No
Yes
Freeze
flexfield
definitio
n
Yes
E_VS
People
Group
Flex field
DJL_PEOP
LE_GROU
P_VS
No
Security
No
Yes
Yes
Job Flex
field
DJL_JOB_
CODE_VS
No
Security
No
Yes
Yes
Cost
Allocatio
n KF
DJL_COA_
COMPAN
Y
Non
Heirarchi
cal
Security
No
Yes
Yes
DJL_COA_
COST
CENTER
Non
Heirarchi
cal
Security
No
Yes
Yes
DJL_COA_
NATURAL
ACCOUN
T
Non
Heirarchi
cal
Security
No
Yes
Yes
DJL_COA_
FUTURE_
USE_1
Non
Heirarchi
cal
Security
No
Yes
Yes
DJL_COA_
FUTURE_
USE_2
Non
Heirarchi
cal
Security
No
Yes
Yes
Position
Flexfield
DJL_POSI
TION_VS
No
Security
No
Yes
Yes
Compete
nce
Flexfield
DJL_SKILL
No
_NAME_V
Security
S
Yes
Yes
Yes
DJL_ROLE
No
_NAME_V
Security
S
No
Yes
Yes
No
Yes
Yes
DJL_LEVE
L_NAME_
No
Security
VS
Accounti
ng
Flexfield
DJL_COA_
COMPAN
Y
Non
Heirarchi
cal
Security
Balancin
g
segment
Yes
Yes
DJL_COA_
COST
CENTER
Non
Heirarchi
cal
Security
Cost
centre
segment
Yes
Yes
DJL_COA_
NATURAL
ACCOUN
T
Non
Heirarchi
cal
Security
Natural
account
segment
Yes
Yes
DJL_COA_
FUTURE_
USE_1
Non
Heirarchi
cal
Security
No
Yes
Yes
DJL_COA_
FUTURE_
USE_2
Non
Heirarchi
cal
Security
No
Yes
Yes
6th step: Create Business Group and Attach all felxfield in to Business group
BUSINESS
GROUP
DJ Group of
Companies
7th Step:
Particular
Name
Create calendar
DJ_Calender
DJ INDIA LTD
Create ledger
DJ_Primary Ledger
COMPLETE STATUS
Click on create legal entity
on accounting set up screen
and create operating unit
Run Replicate Seed Data in
Sys Admin Responsibility
(parameter-OU)
Go and see OU at
organization as OU created
from ledger
8th Step: Assign these profile option to all responsibility
S.No
Profile Option
Parameter
HR: Security
Profile
BG Name
MO: Security
Profile
BG Name
3 HR:User Type
HR with
Payroll User
GL Ledger
Name
DJ_PRIMARY
LEDGER
HR:Business
Group
DJ Group of
Companies
MO: Default
6 Operating
Unit
OU
MO:
7 Operating
Unit
OU
9th Step:
Create inventory
calendar
IMO
INV ORG 1
INV ORG 2
Particulars
Purchasing options
Set up-purchasing document type
Creation of JOB and Position and Group people
flexfield
Create person and assign to the User
Create Buyer as person
Create Job group in HRMS responsibility
Create Job in Purchase responsibility
Create Position in Purchase responsibility
Attach job and position in assignment in people
and maintain in HRMS resp
Create Approval group with document total and
account range
Assign to Approval assignments
Open the period for purchasing and Inventory
and GL
Particulars
AP
Financial option
Payable option
Module
Particulars
Order management
Particulars
AR
System options
Create payment terms
Create transaction type-:Create for credit
memo ,invoice
Create transaction source:-Attach in the
transaction type
Create customer
Set Auto Accounting
Set EBTAX -party tax profile for legal entity and
Operating Unit
Create Receivable Activities
Create Receipt methods
Create Receipt Classes
Particulars
Remarks
Fixed Asset
Asset key
Asset
Category
Asset
location
Create fiscal year
Create Calendar
DJ_FISCAL
YEAR
Create prorate
convention
DJ_CALENDE
R
Create system
control
DJ_PRORATE
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::\\\end\\\\
Answer
Prepayment?
Standard concurrent
program in AP
Purchasing,GL
Expenses Ac
Dr 100
To Supplier Ac Cr 100
5 types i.e.Bills
payable,Check,Electronic,Outsourced
Check,Wire
What is prepayment
settlement date in payable
option?
Yes
Payable
What is Zero-Payment in
AP?
AP_INVOICES
No
Due,Discount,None
Never opened,Future,Open,Closed,Permanently
closed
http://dillipkumarjena.blogspot.in/2012/09/mont
h-end-activity-for-oracle-r12.html
Fund transfer
yes
Provide the item and quantity and need by date then save (Requisition number will generate)
Then click on Approve tab and following screen will appear
Then convert this requisition to PO through auto create. See the below screen
Remove the buyer name and provide requisition number and click on find tab
Tick on requisition and click on automatic tab and below screen will appear.
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
Provide Receipt routing as direct delivery, Inspection required and Standard receipt which one required for the
client.
Then click on Distribution and provide the PO charge account if it is not picking from Item else organization set up.
Click on Term tab on Po screen and provide Pay on = Receipt for transacting ERS invoice creation.
Click on OK .Here if the PO approval is required for more than one person then click on forward the approval path
to concern person otherwise else.
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.
Provide the Po else Receipt number and click on find ,the above screen will appear.See the routing is showing
Inspection required.
Step 5: Receiving Transaction
Provide the receipt number and submit request. Go to request and view the invoice number generated.
Take that Invoice number and go to payable invoice screen
Provide the payment method and payment process profile and save.
Once we will run create accounting these request will run to impact the GL balances.
GL Balances
PO_VENDORS
PO_VENDOR_SITES_ALL
PO_VENDOR_CONTACTS
AP_SUPPLIERS
AP_INVOICE _INTERFACE
AP_INVOICES_LINES_INTERFACE
AP_INVOICE_ALL
AP_INVOICES_DISTRIBUTIONS_ALL
AP_INVOICE_DISTRIBUTIONS_ALL holds
the distribution line information that you enter
for invoices. There is a row for each invoice
distribution. A distribution line must be
associated with an invoice. An invoice can have
multiple distribution lines.
AP_HOLDS_ALL
AP_PAYMENT_SCHEDULES_ALL
AP_PAYMENT_SCHEDULES_ALL contains
information about scheduled payments for an
invoice. You need one row for each time you
intend to make a payment on an invoice. Your
Oracle Payables application uses this information
to determine when to make payments on an
invoice and how much to pay in an automatic
payment batch.
AP_INVOICE_PAYMENTS_ALL
AP_CHECKS_ALL
AP_INTERFACE_REJECTIONS
AP_INTERFACE_REJECTIONS stores
information about invoice data from the
AP_INVOICES_INTERFACE and
AP_INVOICE_LINES_INTERFACE tables
which could not be processed by Payables Open
Interface Import.
AP_AE_LINES_ALL
AP_AE_HEADERS_ALL
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
Item Creation
MTL_SYSTEM_ITEMS_FV
L
Purchase
Requisition
Creation
PO_REQUISITION_
HEADERS_ALL
PO_REQUISITION_HEADE
RS_ALL stores 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_REQUISITION_
LINES_ALL
PO_REQUISITION_LINES
stores information about
requisition lines. You need one
row for each requisition line
you create. Each row contains
the line number, item number,
item category, item
description, need-by date,
deliver-to location, item
quantities, units, prices,
requestor, notes, and
suggested supplier information
for the requisition line.
PO_REQ_DISTRIBUTIONS_
ALL
PO_REQ_DISTRIBUTIONS_
ALL stores information about
the accounting distributions
associated with each
requisition line. Each
requisition line must have at
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.
Purchase Order
Creation
PO_HEADERS_ALL
PO_HEADERS_ALL contains
header information for all
purchasing documents. 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
PO_LINES_ALL stores
current information about each
purchase order line. You need
one row for each line you
attach to a document.
PO_DISTRIBUTIONS_ALL
PO_DISTRIBUTIONS_ALL
contains accounting
distribution information for a
purchase order shipment line.
You need one row for each
distribution line you attach to
a purchase order shipment.
RCV_TRANSACTIONS
PO_REQUISITIONS_
INTERFACE_ALL
PO_DISTRIBUTIONS_ALL
contains accounting
distribution information for a
purchase order shipment line.
You need one row for each
distribution line you attach to
a purchase order shipment.
PO_RESCHEDULE_
INTERFACE
PO_HEADERS_INTERFACE
PO_HEADERS_INTERFACE
is the interface table that holds
header information for the
PDOI program to create
standard/blanket
purchase orders and catalog
quotations.
PO_LINES_INTERFACE
PO_LINES_INTERFACE is
the interface table that holds
lines information for the PDOI
program to create
standard/blanket purchase
orders and catalog quotations.
PO_DISTRIBUTIONS_INTE
RFACE
PO_DISTRIBUTIONS_INTE
RFACE is the interface table
that holds distribution
information for the PDOI
program to create
standard purchase order.
PO_VENDORS
PO_VENDORS is a view
which contains selected
columns of AP_SUPPLIERS
PO_VENDOR_SITES_ALL
PO_VENDORS is a view
which contains selected
columns of AP_SUPPLIERS
PO_VENDOR_CONTACTS
> 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
Opg Bal
"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.
Reconciling AP to GL is accomplished with the use of the following reports.
Posted Invoice Register
Posted Payment Register
Accounts Payable Trial Balance (current and last period)
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.
Common Reasons for balance mismatch between AP & GL
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.
Customized Reports for reconciliation:
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
Sig
n
Particulars
Rs.
100
Supplier Ledger
100
120
20
100
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,
RA_CUST_TRX_LINE_GL_DIST_ALL ,
AR_PAYMENT_SCHEDULES_ALL
Receivable Ac Dr
Bank Ac Dr
To Revenue Ac Cr
Receivables Ac Cr
Cash /
To
While we are defining Order transaction type>Finance Tab we have to assign Accounting rule
and Invoicing rule
Earned/Unearned discount,Refund,TDS
receivable
Incomplete,Unaccounted,Not posted to GL
NO
Receivables Ac
Dr xx
1000
To Unbilled Receivables xx
750 (Invoice
rule in Arrear)
To Revenue xx
250 (Accounting
Rule-4 Monthly)
Receivables Ac Dr xx
To Unearned Revenue xx
rule in advance)
1000
750 (Invoice
To Revenue xx
Rule-4 Monthly)
250 (Accounting
Late charge
on account
Unapplied and on account is same but if we will do onaccount ,it will hit the customer balance.
Unapplied
Unidentified
No customer
Remit to address
Yes
Yes
Back Orders
Drop Shipment
Configurator
Modifier
Qualifier
set ups
How we are linking from order management to
AR
Invoice,BR,DM,CM,Guarantee,Deposit
No
Receivable to revenue
MOAC,SLA,AP/AR Netting,Deffered
COGS,Chargeback,Refund process,Legal
Entity,BFB,day wise revenue recognition
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.
STEPS
Particulars
Step-1
Invoice Transaction
Step-2
Create Accounting
Step-3
Receipt applied to AR
transaction
Step-4
Create Accounting
Step-5
Transfer Journal
Entries to GL
Step-6
Journal Import
Step-7
GL Balances
Invoice:
Amou
nt
Ac Code
Ac Description
JV
Asset
Receivable Ac
Dr
1122
Income
To Revenue Ac
Cr
1000
Asset
To Tax Ac
Cr
10
Asset
To VAT
Cr
Asset
To Service Tax
Cr
10
Income
To frieght Inward
Cr
100
Ac Description
JV
Receipt
s
Ac Code
Amou
nt
Asset
Bank /Cash Ac Dr
Dr
1122
Asset
To Receivable Ac Cr
Cr
1122
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 persons 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 persons 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
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';
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-1
Step-2
Step-3
Step-4
Step-5
Step-6
Ship Confirm
Step-7
Step-8
Step-9
Step-10
Step-11
Interface Lines
Step-12
Step-13
Step-14
Invoice Transaction
Step-15
Step-16
Step-17
Create Accounting
Step-18
Step-19
Create Accounting
Step-20
Step-21
Journal Import
Step-22
GL Balances
Ac
Description
JV
Asset
Deferred
COGS
account
(item_cost)
Dr
1000
Asset
Inventory
Valuation
Account
(item_cost)
Cr
1000
Ac
Description
JV
Amount
COGS
Recogniti
on
transactio
n
Ac Code
Amount
Expenses
COGS
(Actual
revenue
percentage
)
Dr
1000
Asset
Deffered
COGS
(Actual
revenue
percentage
)
Cr
1000
Ac Code
Ac
Description
JV
Asset
Inventory
RM
Account
Dr
1000
Asset
Inventory
RM
Account
Cr
1000
Ac Code
Ac
Description
JV
Asset
Receivable
Ac
Dr
1122
Income
To Revenue
Ac
Cr
1000
Asset
To Tax Ac
Cr
10
Asset
To VAT
Cr
Asset
To Service
Tax
Cr
10
Income
To frieght
Inward
Cr
100
Stores
Amount
Invoice:
Amount
Receipts
Ac Code
Ac
Description
JV
Asset
Bank /Cash
Ac Dr
Dr
1122
Asset
To
Receivable
Ac Cr
Cr
1122
Amount
OE_ORDER_LINES_ALL
OE_PRICE_ADJUSTMENTS
OE_ORDER_PRICE_ATTRIBS
OE_ORDER_HOLDS_ALL
Booked
OE_ORDER_HEADERS_ALL
WSH_DELIVERY_DETAILS
Pick Released
WSH_DELIVERY_DETAILS
WSH_PICKING_BATCHES
MTL_RESERVATIONS
Full Transaction
MTL_MATERIAL_TRANSACTIONS
No records in
MTL_MATERIAL_TRANSACTIONS
MTL_TXN_REQUEST_HEADERS
MTL_TXN_REQUEST_LINES
WSH_DELIVERY_DETAILS
Released to warehouse
WSH_NEW_DELIVERIES
WSH_DELIVERY_ASSIGNMENTS
Pick Confirmed
WSH_DELIVERY_DETAILS
Ship Confirmed
WSH_DELIVERY_DETAILS
MTL_MATERIAL_TRANSACTIONS
WSH_NEW_DELIVERIES
OE_ORDER_LINES_ALL
WSH_DELIVERY_LEGS
OE_ORDER_HEADERS_ALL
Auto Invoice
WSH_DELIVERY_DETAILS
RA_INTERFACE_LINES_ALL
RA_CUSTOMER_TRX_ALL
RA_CUSTOMER_TRX_LINES_ALL
Customer Information
HZ_PARTIES
HZ_PARTY_SITES
HZ_LOCATIONS
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_CUST_ACCOUNTS
HZ_CUST_ACCOUNT_SITES_ALL
HZ_CUST_SITE_USES_ALL
RA_CUSTOMERS
Price Details
QP_LIST_HEADERS_B
QP_LIST_LINES
Items On Hand Qty
MTL_ONHAND_QUANTITIES
Payment Terms
RA_TERMS
Payment terms
OE_HOLD_AUTHORIZATIONS
OE_HOLD_SOURCES_ALL
OE_ORDER_HOLDS_ALL
Hold Release
OE_HOLD_RELEASES_ALL
Credit Check Details
OE_CREDIT_CHECK_RULES
Cancel Orders
OE_ORDER_LINES_ALL
Document Sequence
FND_DOCUMENT_SEQUENCES
FND_DOC_SEQUENCE_CATEGOR
IES
FND_DOC_SEQUENCE_ASSIGNM
ENTS
Default Rules For Price List
OE_DEF_ATTR_DEF_RULES
OE_DEF_ATTR_CONDNS
AK_OBJECT_ATTRIBUTES
End User Details
CSI_T_PARTY_DETAILS
Sales Credit
OE_SALES_CREDITS
Attaching Documents
FND_ATTACHED_DOCUMENTS
FND_DOCUMENTS_TL
Processing Constraints
OE_PC_ASSIGNMENTS
OE_PC_EXCLUSIONS
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
select line_id move_order_line_id,
header_id move_order_header_id,
line_number,
inventory_item_id,
organization_id,
quantity_delivered,
line_status,
txn_source_id,
transaction_type_id,
pick_slip_date
from MTL_TXN_REQUEST_LINES
where line_id in (174779, 174780, 174781)
MTL_TXN_REQUEST_HEADERS
select header_id move_order_header_id,
request_number move_order_number,
move_order_type,
organization_id,
header_status move_order_status
from MTL_TXN_REQUEST_HEADERS
where header_id in (55272, 55273)
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
Y)
Since the order is now booked, delivery details of the order are created in
WSH_DELIVERY_DETAILS table. WSH_DELIVERY_DETAILS has delivery lines and LPNs.
OE_ORDER_LINES_ALL.line_id = WSH_DELIVERY_DETAILS.source_line_id
These delivery details information can been viewed form Shipping Transactions Form and the
delivery status in the application will be as Ready to Release
WSH_DELIVERY_DETAILS.released_status =R
SELECT lookup_type,
lookup_code,
meaning,
description
FROM fnd_lookup_values
WHERE lookup_type = 'PICK_STATUS'
AND LANGUAGE
= 'US';
WSH_DELIVERY_ASSIGNMENTS assigns delivery details to a delivery and/or a parent
delivery detail (LPN).
WSH_DELIVERY_ASSIGNMENTS.delivery_detail_id =
WSH_DELIVERY_DETAILS.delivery_detail_id
WSH_DELIVERY_ASSIGNMENTS.delivery_id will be NULL as still pick release operation is
not performed as final delivery is not yet created.
At the same time when order is booked Demand interface program is triggered in the
background and demand of the item with specified quantity is created and these demand information is
stored in MTL_DEMAND
MTL_DEMAND.demand_source_line = OE_ORDER_LINES_ALL.line_id
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 SRSprogram 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:
WSH_DELIVERY_ASSIGNMENTS.delivery_id = WSH_NEW_DELIVERIES.delivery_id
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.trx_source_line_id = OE_ORDER_LINES_ALL.line_id
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.
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
AR Reconciliation Report
GL Date from 01-JAN-2012 to 31-JAN-2012
Sig
n
Particulars
Beginning Balance as of 31-DEC-2011
Transaction Register
Rs.
10,000.00
500.00
2,500.00
3,500.00
+
-
Adjustments Register
20
Invoice Exceptions
0.00
0.00
Rounding (*)
0.00
4,520.00
4,520.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.
The Arithmetic process for reconciling Oracle Receivables
Open Aging
+ Transaction Register balance
+/- Adjustment Register balance
(-) Invoice Exception balance
(-) Unapplied Receipts balance
(-) Applied Receipts balance
------------------------------------------------------------Arithmetic total should be equal to Closing Aging
------------------------------------------------------------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.
Technical (Table details):
Query to Identify the Code Combination ID (assuming Account code is of 5 segments separated by a period)
select code_combination_id from gl_code_combinations
where (segment1||'.'||segment2||'.'||segment3||'.'||segment4||'.'||segment5) =
'000.CC.99999.IC.99 '
Query that gives the Accounting Entries to be passed in GL
Select
ad.source_type, ara.postable, segment1||'.'||segment2||'.'||segment3||'.'||segment4||'.'||segment5
acc, sum(ad.acctd_amount_dr), sum(ad.acctd_amount_cr) from ar_distributions_all ad,
ar_receivable_applications_all ara, gl_code_combinations gc
where ara.payment_schedule_id in
(select crh.payment_schedule_id from ar_distributions_all ad, ar_receivable_applications_all crh
where ad.code_combination_id= <ID from the above query>
and crh.receivable_application_id=ad.source_id
and ad.source_type='REC' and crh.posting_control_id<0 and crh.gl_date between '&From_GL_date' and
'&To_Gl_Date' and crh.org_id=&Org_id) and gc.code_combination_id = ad.code_combination_id and
ara.receivable_application_id = ad.source_id group by ad.source_type,ara.postable,
segment1||'.'||segment2||'.'||segment3||'.'||segment4||'.'||segment5
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.
Interface/Conversion examples and details:
The below list of interfaces/conversions are covered in this section. Details like pre-requisites
required, interface tables, interface program, base tables, validations that need to be performed
after inserting the details into the interface tables and required columns that need to be populated
in the interface table are discussed for each interface.
Order Import Interface (Sales Order Conversion)
Item import (Item conversion)
Inventory On-hand quantity Interface
Customer conversion
Auto Invoice Interface
AR Receipts
Lockbox Interface
AP Invoices
Vendor
Purchase Orders
Requisition
Receiving
Journal import
Budget import
Daily Conversion Rates
3. Closed orders
Order Import API OE_ORDER_PUB.GET_ORDER and PROCESS_ORDER can also be used
to import orders.
Some important columns that need to populated in the interface tables:
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
Item import (Item conversion)
The Item Interface lets you import items into Oracle Inventory.
Pre-requisites:
Creating an Organization
Code Combinations
Templates
Defining Item Status Codes
Defining Item Types
Interface tables:
MTL_SYSTEM_ITEMS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE (If importing revisions)
MTL_ITEM_CATEGORIES_INTERFACE (If importing categories)
MTL_INTERFACE_ERRORS (View errors after import)
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 item type.
Check for valid part_id/segment of the source table.
Validate part_id/segment1 for master org.
Validate and translate template id of the source table.
Check for valid template id. (Attributes are already set for items, default attributes for
that template, i.e., purchasable, stockable, etc)
Check for valid item status.
Validate primary uom of the source table.
Validate attribute values.
Validate other UOMs of the source table.
Check for unique item type. Discard the item, if part has non-unique item type.
Check for description, inv_um uniqueness
Validate organization id.
Load master records and category records only if all validations are passed.
Load child record if no error found.
Some important columns that need to populated in the interface tables:
MTL_SYSTEM_ITEMS_INTERFACE:
TRANSACTION_TYPE = CREATE
SET_PROCESS_ID = 1
Each row in the mtl_item_revisions_interface table must have the REVISION
and EFFECTIVITY_DATE in alphabetical (ASCII sort) and chronological
order.
Inventory On-hand quantity Interface
This interface lets you import the on hand inventory into Oracle.
Interface tables:
MTL_TRANSACTIONS_INTERFACE
MTL_MTL_TRANSACTION_LOTS_INTERFACE (If the item is Lot controlled)
MTL_SERIAL_NUMBERS_INTERFACE (If the item is Serial controlled)
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
Check if item is assigned to organization
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.
Validate organization_id, organization_code.
Validate inventory item id.
Transaction period must be open.
Some important columns that need to be populated in the interface tables:
MTL_TRANSACTIONS_INTERFACE:
TRANSACTION_SOURCE_NAME (ANY USER DEFINED VALUE),
TRANSACTION_HEADER_ID (MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL)
TRANSACTION_INTERFACE_ID (MTL_MATERIAL_TRANSACTIONS_S.NEXTVAL If
item is lot or serial controlled, use this field to link to mtl_transactions_interface otherwise leave
it as NULL),
TRANSACTION_DATE,
TRANSACTION_TYPE_ID,
PROCESS_FLAG (1 = Yet to be processed, 2 = Processed, 3= Error)
TRANSACTION_MODE (2 = Concurrent to launch a dedicated transaction worker
to explicitly process a set of transactions.
3 = Background will be picked up by transaction manager
polling process and assigned to transaction
worker. These will not be picked up until the
transaction manager is running)
SOURCE_CODE,
SOURCE_HEADER_ID,
SOURCE_LINE_ID (Details about the source like Order Entry etc for tracking purposes)
TRANSACTION_SOURCE_ID
Source Type
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 legacy values fetched are valid.
Check if customer address site is already created.
Check if customer site use is already created.
Check is customer header is already created.
Check whether the ship_to_site has associated bill_to_site
Check whether associated bill_to_site is created or not.
Profile amounts validation:
Validate cust_account_id, validate customer status.
Check if the location already exists in HZ_LOCATIONS. If does not exist, create new location.
Some important columns that need to be populated in the interface tables:
RA_CUSTOMERS_INTERFACE_ALL:
ORIG_SYSTEM_CUSTOMER_REF
SITE_USE_CODE
ORIG_SYSTEM_ADDRESS_REF
INSERT_UPDATE_FLAG (I = Insert, U = Update)
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
Trading Community Architecture (TCA) is an architecture concept designed to support complex
trading communities. These APIs utilize the new TCA model, inserting directly to the HZ tables.
API Details:
Set the organization id
Exec dbms_application_info.set_client_info(204);
Create a party and an account
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
Create a physical location
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 legacy values fetched are valid.
Check if customer address site is already created.
Check if customer site use is already created.
Check is customer header is already created.
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
Sales Tax rate
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.
Validate bill to the customer.
Get bill to site use id.
Get the customer trx id for this particular transaction number.
Get payment schedule date for the customer trx id.
Lockbox interface
AutoLockbox lets us automatically process receipts that are sent directly to the bank instead of
manually feeding them in Oracle Receivables.
AutoLockbox is a three step process:
1. Import: During this step, Lockbox reads and formats the data from your bank file
into interface table AR_PAYMENTS_INTERFACE_ALL using a SQL *Loader
script.
2. Validation: The validation program checks data in this interface table for
compatibility with Receivables. Once validated, the data is transferred into
QuickCash tables (AR_INTERIM_CASH_RECEIPTS_ALL and
AR_INTERIM_CASH_RCPT_LINES_ALL).
3. Post QuickCash: This step applies the receipts and updates your customers
balances.
Pre-Requisites:
Banks
Receipt Class
Payment Method
Receipt Source
Lockbox
Transmission format
AutoCash Rule sets
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:
Check for valid record type, transmission record id.
Validate sum of the payments within the transmission.
Identify the lockbox number (no given by a bank to identify a lockbox).
Some important columns that need to be populated in the interface tables:
AR_PAYMENTS_INTERFACE_ALL:
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:
AP_INVOICES_ALL header information
AP_INVOICE_DISTRIBUTIONS_ALL lines info
Concurrent program:
Payables Open Interface Import
Validations:
Check for valid vendor
Check for Source, Location, org_id, currency_codes validity
Check for valid vendor site code.
Check if record already exists in payables interface table.
Some important columns that need to be populated in the interface tables:
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.
Pre-requisites setups required:
Payment terms
Pay Groups
CCID
Supplier classifications
Bank Accounts
Employees (if employees have to set up as vendors)
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:
Supplier Open Interface Import
Supplier Sites Open Interface Import
Supplier Site Contacts Open Interface Import
Validations:
Check if vendor already exists
PO_DISTRIBUTIONS_ALL
PO_LINE_LOCATIONS_ALL
Validations:
Header:
Check if OU name is valid
Check if Supplier is valid
Check if Supplier site is valid
Check if buyer is valid
Check if Payment term is valid
Check if Bill to and ship to are valid
Check if FOB, freight terms are valid
Lines:
Check if Line_type, ship_to_org, item, uom, ship_to_location_id, requestor, charge_account,
deliver_to_location are valid
General:
Check for duplicate records in interface tables
Check if the record already exists in base tables.
Some important columns that need to be populated in the interface tables:
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:
INTERFACE_LINE_ID, INTERFACE_HEADER_ID, LINE_NUM, SHIPMENT_NUM, ITEM,
REQUISITION_LINE_ID, UOM, UNIT_PRICE, FREIGHT_TERMS, FOB
PO_DISTRIBUTIONS_INTERFACE:
INTERFACE_LINE_ID, INTERFACE_HEADER_ID, INTERFACE_DISTRIBUTION_ID,
DISTRIBUTION_NUM, QUANTITY_ORDERED, QTY_DELIVERED, QTY_BILLED,
QTY_CANCELLED, DELIVER_TO_LOCATION_ID, DELIVER_TO_PERSON_ID,
SET_OF_BOOKS, CHARGE_ACCT, AMOUNT_BILLED.
Import Blanket Purchase Agreements:
Interface Tables:
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
Interface program:
Base tables:
PO_REQUISITIONS_HEADERS_ALL
PO_REQUISITION_LINES_ALL
PO_REQ_DISTRIBUTIONS_ALL
Concurrent program:
REQUISITION IMPORT
Validations:
Check for interface transaction source code, requisition destination type.
Check for quantity ordered, authorization status type.
Some important columns that need to be populated in the interface tables:
PO_REQUISITIONS_INTERFACE_ALL:
INTERFACE_SOURCE_CODE (to identify the source of your imported
Requisitions)
DESTINATION_TYPE_CODE
AUTHORIZATION_STATUS
PREPARER_ID or PREPARER_NAME
QUANTITY
CHARGE_ACCOUNT_ID or charge account segment values
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
ITEM_ID or item segment values (values if the SOURCE_TYPE_CODE or
DESTINATION_TYPE_CODE is INVENTORY)
PO_REQ_DIST_INTERFACE_ALL:
CHARGE_ACCOUNT_ID or charge account segment values
DISTRIBUTION_NUMBER
DESTINATION_ORGANIZATION_ID
DESTINATION_TYPE_CODE
INTERFACE_SOURCE_CODE
ORG_ID
DIST_SEQUENCE_ID (if MULTI_DISTRIBUTIONS is set to Y)
PO Receipts Interface
The Receiving Open Interface is used for processing and validating receipt data that
comes from sources other than the Receipts window in Purchasing.
Pre-requisites:
Set of Books
Code combinations
Employees
Items
Interface tables:
RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
PO_INTERFACE_ERRORS
Concurrent program:
RECEIVING OPEN INTERFACE
Base tables:
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
RCV_TRANSACTIONS
Validations:
Check that SHIPPED_DATE should not be later than today.
Check if vendor is valid.
If Invoice number is passed, check for its validity
Check if Item is valid
Some important columns that need to be populated in the interface tables:
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
VALIDATION_FLAG (Indicates whether to validate a row or not, values Y, N)
RCV_TRANSACTIONS_INTERFACE:
INTERFACE_TRANSACTION_ID
GROUP_ID
TRANSACTION_TYPE (SHIP for a standard shipment (an ASN or ASBN)
or RECEIVE for a standard receipt)
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
Flex field Value sets
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
Journal Posting populates GL_BALANCES
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
B enter budget id.
Check if accounting date or GL date based period name is valid (i.e., not closed).
Check if accounting date falls in open or future open period status.
Check chart of accounts id based on Sob id.
Check if code combination is valid and enabled.
Check if record already exists in GL interface table.
Check if already journal exists in GL application.
Some important columns that need to be populated in the interface tables:
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
Flex field Value sets
Code Combinations
Interface tables:
GL_BUDGET_INTERFACE
Base tables:
GL_BUDGETS
GL_BUDGET_ASSIGNMENTS
GL_BUDGET_TYPES
Concurrent program:
Budget Upload
Validations:
Check if CURRENCY_CODE is valid.
Check if SET_OF_BOOKS_ID is valid.
Check if BUDGET_ENTITY_NAME (budget organization) is valid.
Some important columns that need to be populated in the interface tables:
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
SEGMENT1 through SEGMENT30
GL daily conversion rates
This interface lets you load the rates automatically into General Ledger.
Pre-requisites:
Currencies
Conversion rate Types
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.
Check if USER_CONVERSION_TYPE is valid.
Some important columns that need to be populated in the interface tables:
GL_DAILY_RATES_INTERFACE:
FROM_CURRENCY
TO_CURRENCY
FROM_CONVERSION_DATE
TO_CONVERSION_DATE
USER_CONVERSION_TYPE
CONVERSION_RATE
MODE_FLAG (D= Delete, I = Insert, U = Update)
INVERSE_CONVERSION_RATE
Related Articles:
Importing Blanket Purchase Agreements(BPA)
Oracle Internet Expenses Overview
admin
Srini says:
October 4, 2012 at 4:11 pm
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:
September 15, 2012 at 2:10 am
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:
July 23, 2012 at 11:34 pm
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:
syed says:
March 20, 2012 at 12:52 pm
Excellent effort, . Thanks
binsar says:
March 15, 2012 at 9:04 am
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:
March 13, 2012 at 11:59 am
let me keep it simpleJUST WONDERFUL
swathi says:
February 21, 2012 at 12:33 pm
Hi can you please share import bill and routing open interface validation code.
Sambasiva says:
February 15, 2012 at 12:34 pm
Hi,
This is Sambasiva. please can you send the Inventory Status Change Interface details..
babita says:
February 14, 2012 at 4:29 pm
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:
December 30, 2011 at 12:03 pm
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:
December 10, 2011 at 12:13 am
need validations for columns
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:
November 22, 2011 at 7:10 pm
I love this. This most important who want to know about interfaces and conversions. could send
bank conversion source code through APIs i dont have experience in APIs.
Thanks in advance
Adarsh
ycadarshanreddy@gmail.com
vijay says:
November 17, 2011 at 12:36 pm
its very clearly,thanks a lot for providing valible information.
tirumalarao says:
November 9, 2011 at 3:39 pm
the information you had provided is really use full THANKS BROTHER
G MUNIRAMAIAH says:
September 30, 2011 at 8:55 am
very nice anser and very use fully to every people
Ravikumar says:
September 29, 2011 at 12:50 pm
Excellent document related to Conversions/Interfaces.
Krishna says:
September 14, 2011 at 8:32 pm
Its looking like all Fruits in one Tree.Nice article..Thanks
TCalado says:
September 14, 2011 at 4:15 pm
Hello,
thanks for the information you provided.
Where is accounting_date when transferred from gl_interface to base tables ? Im not finding the
date Im passing.
Thanks in advance
krrish says:
September 9, 2011 at 11:14 pm
this data is very nice who wats to know about intefaces and conversions..
Jithendra says:
August 24, 2011 at 11:44 am
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:
August 20, 2011 at 8:45 am
How to handle the errors in interface and how to send this errors to client pls tell?
Prasant says:
July 15, 2011 at 9:56 pm
Can any one plz send me the open sales order conversion script..
Rasheed says:
July 7, 2011 at 8:05 pm
Love it! Great Article. Please keep up the GREAT work!
Don says:
June 16, 2011 at 12:12 am
Very nicely put together. Thanks a ton
Could you let me know what are the DB packages for each of the stages for Lockbox?
Thanks in advance
Don
sreenath says:
June 10, 2011 at 10:28 am
It is very useful to learn for new members/Freshers. Keep it up. Really good.
Lakshmikanth says:
May 19, 2011 at 5:25 pm
This Article which you have given is very much usefull for every one who wants to know about
interfaces and conversions
Regards
Lakshmikanth
Leave a Reply Cancel reply
Top of Form
Connect with:
Name
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>
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
Sysadmin and AOL
Tools
Workflow
XML Publisher
Connect
Register
Log in
Entries RSS
Comments RSS
WordPress.org
Beginner Articles
Order to Cash cycle Video
Assemble to Order Cycle Video
Oracle Apps Images
Dependent Parameters in Concurrent Program using Special Value Set
FNDLOAD to transfer AOL Objects from one instance to other
Recent Posts
Order to Cash cycle Video
Assemble to Order Cycle Video
Oracle Apps Images
Dependent Parameters in Concurrent Program using Special Value Set
Launch Workflow from PL/SQL
2011 erpSchools