Oracle EBS R12 General ledger interface tables

The Oracle apps General Ledger Interface Table – GL_INTERFACE is the entry point for all journals accounting data which have been imported from other systems. The Journal Import Program validates the accounting data received in the GL_INTERFACE Table and imports the available data into Journal entries in the Oracle Apps GL Application.

The Journal Import Program uses the GL_INTERFACE Table Column data to store the accounting data into the Journal defined categories.

Below given are few of the main columns for which Journal Import uses during processing

Column Name	Column Description
STATUS	Value could be ‘P’ – Posted , ‘U’ – Unposted or ERROR Number when returns Error while processing
LEDGER_ID	Ledger ID FROM gl_ledgers
USER_JE_SOURCE_NAME	Provide the Source for which Journal have been received ( Few Sources could be – REMEASUREMENT, Receivables, Global Intercompany, Cost Management, TRANSLATION, Spreadsheet, Payables, Global Intercompany RVRSE )
USER_JE_CATEGORY_NAME	Provide the Category for which Journal have been received ( Few categories could be – Travel , Inventory, Purchase Invoices, Reverse, AX Receivables, Payroll, Receiving, REMEASUREMENT, Statisticals, Sales Invoices )
ACCOUNTING_DATE	Date when journal entries have been accounted in Oracle Apps GL Application
CURRENCY_CODE	Journal Currency
ACCOUNTED_DR	Accounted Debit Amount for journal
ACCOUNTED_CR	Accounted Credit Amount for journal
JE_BATCH_ID	Journal Batch ID
GROUP_ID	Journal Group ID

Interface Table Column Name	Null?	Date Type
STATUS	NOT NULL	VARCHAR2 (50)
LEDGER_ID	NOT NULL	NUMBER (15)
USER_JE_SOURCE_NAME	NOT NULL	VARCHAR2 (25)
USER_JE_CATEGORY_NAME	NOT NULL	VARCHAR2 (25)
ACCOUNTING_DATE	NOT NULL	DATE
CURRENCY_CODE	NOT NULL	VARCHAR2 (15)
DATE_CREATED	NOT NULL	DATE
CREATED_BY	NOT NULL	NUMBER (15)
ACTUAL_FLAG	NOT NULL	VARCHAR2 (1)
ENCUMBRANCE_TYPE_ID		NUMBER
BUDGET_VERSION_ID		NUMBER
CURRENCY_ CONVERSION_DATE		DATE
USER_CURRENCY_ CONVERSION_TYPE		VARCHAR2 (30)
CURRENCY_ CONVERSION_RATE		NUMBER
SEGMENT1 through SEGMENT30		VARCHAR (25)
ENTERED_DR		NUMBER
ENTERED_CR		NUMBER
ACCOUNTED_DR		NUMBER
ACCOUNTED_CR		NUMBER
TRANSACTION_DATE		DATE
REFERENCE1		VARCHAR2 (100)
REFERENCE2		VARCHAR2 (240)
REFERENCE3		VARCHAR2 (100)
REFERENCE4		VARCHAR2 (100)
REFERENCE5		VARCHAR2 (240)
REFERENCE6 through REFERENCE9		VARCHAR2 (100)
REFERENCE10		VARCHAR2 (240)
REFERENCE11 through REFERENCE20		VARCHAR2 (100)
REFERENCE21 through REFERENCE30		VARCHAR2 (240)
GROUP_ID		NUMBER (15)
JE_BATCH_ID		NUMBER (15)
PERIOD_NAME		VARCHAR2 (15)
JE_HEADER_ID		NUMBER (15)
JE_LINE_NUM		NUMBER (15)
CHART_OF_ACCOUNTS_ID		NUMBER (15)
FUNCTIONAL_ CURRENCY_CODE		VARCHAR2 (15)
CODE_COMBINATION_ID		NUMBER (15)
DATE_CREATED_IN_GL		DATE
WARNING_CODE		VARCHAR2 (4)
STATUS_DESCRIPTION		VARCHAR2 (240)
DESCR_FLEX_ERROR_ MESSAGE		VARCHAR2 (240)
STAT_AMOUNT		NUMBER
REQUEST_ID		NUMBER (15)
SUBLEDGER_DOC_ SEQUENCE_ID		NUMBER
SUBLEDGER_DOC_ SEQUENCE_VALUE		NUMBER
USSGL_TRANSACTION_CODE		VARCHAR2 (30)
ATTRIBUTE1 through ATTRIBUTE20		VARCHAR2 (150)
CONTEXT , CONTEXT2, CONTEXT3		VARCHAR2 (150)
INVOICE_DATE		DATE
INVOICE_AMOUNT		NUMBER
INVOICE_IDENTIFIER		VARCHAR2 (20)
TAX_CODE		VARCHAR2 (15)

Oracle EBS R12 SQL to delete GL budget lines

General Ledger SELECT Query to get the details for the Budget Name and Budget Entity Name

SELECT GBI.* FROM GL_BUDGET_INTERFACE GBI
WHERE 1=1
AND GBI.LEDGER_ID = <PROVIDE_LEDGER_ID>
AND GBI.BUDGET_NAME= '<PROVIDE_BUDGET_NAME>'
AND GBI.BUDGET_ENTITY_NAME= '<PROVIDE_BUDGET_ENTITY_NAME>'
AND GBI.FISCAL_YEAR = '<PROVIDE_FISCAL_YEAR>' --2016

Get the count for the Budget lines from the Budget Interface Table that need to be deleted

SELECT count(1) FROM GL_BUDGET_INTERFACE GBI
WHERE 1=1
AND GBI.LEDGER_ID = <PROVIDE_LEDGER_ID>
AND GBI.BUDGET_NAME= '<PROVIDE_BUDGET_NAME>'
AND GBI.BUDGET_ENTITY_NAME= '<PROVIDE_BUDGET_ENTITY_NAME>'
AND GBI.FISCAL_YEAR = '<PROVIDE_FISCAL_YEAR>'

General Ledger DELETE Query to remove /delete the budget lines for the provided Budget Name and Budget Entity Name

DELETE FROM GL_BUDGET_INTERFACE
WHERE 1=1
AND GBI.LEDGER_ID = <PROVIDE_LEDGER_ID>
AND GBI.BUDGET_NAME= '<PROVIDE_BUDGET_NAME>'
AND GBI.BUDGET_ENTITY_NAME= '<PROVIDE_BUDGET_ENTITY_NAME>'
AND GBI.FISCAL_YEAR = '<PROVIDE_FISCAL_YEAR>'

Oracle EBS R12 SQL to get Journal Batch workflow Item details

General Ledger SQL Query to get Journal Batch workflow Item and process activities:

SELECT WF_PROCESS.PROCESS_NAME,
WF_IT_ACT_STATUS.*
FROM WF_ITEM_ACTIVITY_STATUSES WF_IT_ACT_STATUS,
WF_PROCESS_ACTIVITIES WF_PROCESS
WHERE 1=1
AND ITEM_KEY LIKE '%<PROVIDE_JE_BATCH_ID>%'
AND WF_IT_ACT_STATUS.ITEM_TYPE = 'GLBATCH'
AND WF_PROCESS.INSTANCE_ID = WF_IT_ACT_STATUS.PROCESS_ACTIVITY
ORDER BY BEGIN_DATE, END_DATE

Oracle EBS R12 SQL to get user supervisor authorized limit

SQL Query in Oracle apps R12 to get user supervisor details with user authorized limit

SELECT
FU.USER_NAME                                      " USER ID" ,
PER_PEOPLE.FULL_NAME                              " USER FULL NAME",
PER_ASSIGN.D_SUPERVISOR_ID                        " SUPERVISOR USER ID" ,
GL_AUTH_LIMIT1.AUTHORIZATION_LIMIT                " USER AUTH LIMIT" ,
GL_AUTH_LIMIT2.AUTHORIZATION_LIMIT                " SUPERVISOR AUTH LIMIT"
FROM
FND_USER FU,
PER_ALL_PEOPLE_F PER_PEOPLE,
PER_ASSIGNMENTS_V7 PER_ASSIGN,
GL_AUTHORIZATION_LIMITS_V GL_AUTH_LIMIT1,
GL_AUTHORIZATION_LIMITS_V GL_AUTH_LIMIT2
WHERE 1=1
AND FU.EMPLOYEE_ID=PER_PEOPLE.PERSON_ID
AND PER_PEOPLE.PERSON_ID=PER_ASSIGN.PERSON_ID(+)
AND FU.EMPLOYEE_ID= GL_AUTH_LIMIT1.EMPLOYEE_ID(+)
AND PER_ASSIGN.SUPERVISOR_ID= GL_AUTH_LIMIT2.EMPLOYEE_ID(+)
AND FU.USER_NAME IN (<PROVIDE_USER_NAME>)

Oracle EBS R12 GL Journal Header attributes SQL

Query to get the Journal Header Level Attributes for the Journal Batches

Journal Posted Date is NOT NULL
Period Name let you fetch records for a particular Period
Source Name provides from which Source it is being received
Category Name provides for which category Journal is being received

SELECT GJH.JE_BATCH_ID
, GJB.NAME " JOURNAL BATCH NAME"
, GJH.NAME " JOURNAL NAME"
, SOB.SHORT_NAME ||'-'||GL.NAME " LEDGER NAME"
, GJH.PERIOD_NAME " PERIOD NAME"
, GJH.STATUS " JOURNAL STATUS"
, GLS.USER_JE_SOURCE_NAME " JOURNAL SOURCE"
, GLC.USER_JE_CATEGORY_NAME " JOURNAL CATEGORY"
, GJH.CURRENCY_CODE " CURRENCY"
, GJH.POSTED_DATE " POSTED DATE"
, GJH.CREATION_DATE " CREATION DATE"
FROM GL_LEDGERS GL ,
GL_JE_BATCHES GJB,
GL_JE_HEADERS GJH,
GL_JE_SOURCES GLS,
GL_JE_CATEGORIES GLC,
GL_SETS_OF_BOOKS SOB
WHERE 1=1
AND GL.LEDGER_ID = SOB.SET_OF_BOOKS_ID
AND GJB.JE_BATCH_ID = GJH.JE_BATCH_ID
AND GLS.JE_SOURCE_NAME = GJH.JE_SOURCE
AND GLC.JE_CATEGORY_NAME = GJH.JE_CATEGORY
AND GJH.POSTED_DATE IS NOT NULL
AND GJH.PERIOD_NAME ='MAR-16'

Oracle EBS R12 Account Receivables Transaction Source Setup

Transaction Source Setup describes the behavior for the Account Receivable (AR) transactions. Whenever a transaction is processed in Oracle Apps R12 and associated to the transaction source , it validates with the Transaction Source Setup to determine the validations to be performed.

The below given are the field details for the Transaction Source Setup and the field validations in the Transaction Source Tabs to be provided:

Name : Transaction Source Name

2. Type: Transaction Source type could be Manual / Imported

Manual: Prefer manual batch sources with transactions that has been entered manually in the Transaction and Transactions Summary windows

Imported: Prefer imported batch sources to import transactions into Receivables using Auto Invoice

3. Active : Transaction Source can be made Inactive by unchecking the check box

4. Automatic Batch Numbering: If you need to automatically generate batch number for the transaction source, check the Automatic Batch Numbering check box and enter a Last Number.

5. Automatic Transaction Numbering: If you need to automatically generate number for new transactions for the transaction source, check the Automatic Transaction numbering check box and enter a Last Number.

6. Effective Dates: The Start date is the current date when transaction source is being created and made Active . If no end date is provided , then transaction batch source will be active indefinitely

Invalid Line: provides the option for how AutoInvoice to handle imported transactions with Invalid Lines by entering either ‘Reject Invoice’ or ‘Create Invoice’ .

Create Clearing : Select this option if you want to compare the revenue amount to be equal to ( Unit Selling Prices X Quantity) for each transaction line.

GL Date in a Closed Period: provides the option for how AutoInvoice to handle imported transactions that have lines in the Interface Lines table which are in a closed period

Adjust: When selected this option, AutoInvoice automatically adjust the GL dates to the first GL date of the next open or future enterable period, enter ‘Adjust’ in the GL Date in a Closed Period field
Reject: When selected this option, AutoInvoice rejects the transactions

Grouping Rule: AutoInvoice uses the following hierarchy to determine which rule to use:

The grouping rule specified in the Transaction Sources window for the batch source of the transaction line.

The grouping rule specified in the Customer Profile Classes window for the bill-to customer and bill-to site of the transaction line.

The grouping rule specified in the Customer Profile Classes window for the bill-to customer of the transaction line.

The default grouping rule specified in the System Options window.

Customer Information – Values Passed (ID, Value, Segment)

Bill To and Ship To
Address
Contact
Payment Method

Invoicing Rule: indicates if AutoInvoice will validate the Invoicing Rule for the batch source using identifiers or values

Accounting Rule: indicates if AutoInvoice will validate the Accounting Rule for the batch source using identifiers or values

Accounting Flexfield: indicates if AutoInvoice will validate the Accounting Flexfield for the batch source using identifiers or values

Payment Terms : indicates if AutoInvoice will validate the Payment Terms for the batch source using identifiers or values

Revenue Account Allocation: indicates if the AutoInvoice to validate the Revenue Account Allocation data for the batch source using Amount or Percent

Transaction Source Accounting Information

Oracle EBS R12 Account Receivables (AR) Tables

The below given are the Account Receivables (AR) Tables used for AR Setup , AR Transactions.

AR Table Name	AR Table Description
AR Setup tables
RA_BATCH_SOURCES	AR Table for storing the transaction sources
RA_CUST_TRX_TYPES_ALL	The table stores information about each transaction type for all classes of transactions, for example, invoices, commitments, and credit memos
AR_RECEIPT_CLASSES	The table stores the different receipt classes that you define
AR_RECEIPT_METHODS	The table stores information about Payment Methods, receipt attributes that you define and assign to Receipt Classes to account for receipts and their applications
AR Transaction Tables
RA_CUSTOMER_TRX_ALL	AR Transaction Header table
RA_CUSTOMER_TRX_LINES_ALL	AR Transaction Lines table along with Tax lines
RA_CUST_TRX_LINE_GL_DIST_ALL	AR Distribution Table for Transaction Lines
RA_CUST_TRX_LINE_SALESREPS_ALL	Salesrep information for Transaction Lines
AR Transaction Interface Tables
RA_INTERFACE_LINES_ALL	AR Transaction Lines interface
RA_INTERFACE_SALESCREDITS_ALL	AR Transaction Sales credit information
RA_INTERFACE_DISTRIBUTIONS_ALL	AR Transaction Distribution information
RA_INTERFACE_ERRORS_ALL	AR Transaction errors table
AR_PAYMENTS_INTERFACE_ALL	AR Interface table to import receipts
AR_INTERIM_CASH_RECEIPTS_ALL	AR Lockbox transfers the receipts that pass validation to the interim tables
AR_INTERIM_CASH_RCPT_LINES_ALL	AR Lockbox transfers the receipts that pass validation to the interim tables
AR Receipt Tables
AR_CASH_RECEIPTS_ALL	The Table provides Cash Receipt Header details
AR_RECEIVABLE_APPLICATIONS_ALL	The Table provides AR Receipt Application details .
AR_PAYMENT_SCHEDULES_ALL	The table is updated when an activity occurs against an invoice, debit memo, charge back, credit memo, on-account credit, bills receivable . The table stores all of the activity that is contained for the life cycle of a receipt
AR_CASH_RECEIPT_HISTORY_ALL	The table provides the complete history of the receipt and each row represents a step for the receipt execution . The status field for that row tells you which step the receipt has reached. The statuses could be Approved, Confirmed, Remitted, Cleared, and Reversed.

Oracle EBS R12 Account Receivables (AR) Transaction Type Setup

Transaction Types are used in Oracle Account Receivables (AR) to define the accounting for the debit memos, credit memos, on-account credits, chargebacks, commitments, and invoices which are created in Oracle Account Receivables (AR) . Transaction types are also used to determine whether transaction(s) updates customers’ balances and if the Account Receivables (AR) posts the transactions to the General Ledger

Oracle Account Receivables (AR) provides the following transaction types:

Invoice
Credit Memo ,
Projects Credit Memo ,
Projects Invoice ,
Intercompany

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Transaction Types

Field details for the Transaction Types Setup :

Operating Unit: OU which will use these transaction type

Name : Name of the Transaction Type

Description: Description of the Transaction Type

Class: Invoice, Chargeback, Credit Memo, Debit Memo, Deposit, or Guarantee

Legal Entity: provide the Legal Entity Name

Open Receivables: Select if transactions with the defined type is to be used to update customer balances

Post to GL: Select if transactions with the defined type is to be posted to General Ledger . The check box must be checked if the class is Deposit or Guarantee. If transaction is defined as a ‘void’ transaction type, do not check this box

Create Sign : For Credit Memo , set value as Negative Sign , for others set value as Positive Sign

Printing Option: Default Printing Option for the transaction type

Transaction Status : Open / Closed / Pending / Void

Natural Application: The check box must be checked if the class is Deposit or Guarantee

Allow Freight : To allow freight to be entered for transactions with this transaction type, check the Allow Freight check box

Receivable Account : Provide the Receivable Account for transactions with the transaction type. Receivables uses it with AutoAccounting definition, to determine the receivable accounts for transactions with these transaction types. Receivables creates a receivables transaction record using this account so you can transfer to your general ledger and create a journal entry if Post To GL is Yes for this transaction type.

For guarantee transaction types, provide the Accounting Flexfield for the Unbilled Receivable account

For Guarantee and Deposit transaction types, provide the Accounting Flexfield for the Unearned Revenue account if Allow Freight is set to No

Credit Memo transaction types Receivable Account is not required

SQL Query to get the list of Active Transaction Types in Oracle Apps R12 AR:

SELECT RCTTA.ORG_ID,RCTTA.NAME , RCTTA.DESCRIPTION, RCTTA.POST_TO_GL, RCTTA.STATUS, RCTTA.ACCOUNTING_AFFECT_FLAG,
RCTTA.DEFAULT_STATUS , RCTTA.ALLOW_FREIGHT_FLAG, RCTTA.ALLOW_OVERAPPLICATION_FLAG,
RCTTA.START_DATE, RCTTA.TAX_CALCULATION_FLAG,RCTTA.SET_OF_BOOKS_ID
FROM RA_CUST_TRX_TYPES_ALL RCTTA
WHERE RCTTA.STATUS =’A’

Oracle EBS R12 Account Receivables (AR) Payment Terms Setup

Oracle Account Receivables (AR) defines Payment Terms Setup for the Customers in Oracle Apps R12. Payment terms are used to determine the amount of each installment. Oracle Account Receivables allows to distribute tax and freight charges across all installments, or allocate all freight and tax amounts in the first installment of a split term invoice. Oracle Account Receivables shows all the active payment terms defined in the setup as list of values (LOV) in the Customers, Customer Profile Classes, and Transactions windows.

Responsibility: Receivables Manager

Navigation: Setup > Transactions > Payment Terms

Oracle Account Receivables (AR) provides two predefined payment terms:

30 NET: The balance of the transaction is due within 30 days.
IMMEDIATE: The balance of the transaction is due immediately (i.e. on the transaction date). These payment terms can be user with Chargebacks and Debit memos

Oracle Account Receivable AR Payment Terms

Please find below the details for the fields being used in the Payment Terms Setup

Name : Name provided for the Payment Term

Description: provides the purpose for what payment term is being defined

Installment Options: Include tax and freight in first installment

Base Amount : Default value is 100 but can be changed as per requirement.

If the Relative Amount is different than the Base Amount , then Account Receivables uses the below given equation to determine the original amount due for each installment of invoices to which you assign the payment term

Amount Due = Relative Amount/Base Amount * Invoice Amount

If Installment Options Include tax and freight’ as the First Installment field value for a payment term, the base amount and the relative amounts indicate how the original line amounts of the invoices are distributed across different installments

Amount Due = (Relative Amount/Base Amount * Base Line Amount) + Base Freight Amount + Base Tax Amount

Print Lead Days : If transactions assigned to the payment term to be printed before the due date, enter a number of Print Lead Days

Discount Basis: Account Receivables uses this value when calculating discounts for the invoices

Invoice Amount: Calculate the discount amount based on the sum of the tax, freight charges, and line amounts of your invoices.
Lines Only: Calculate the discount amount based on only the line amounts of your invoices.
Lines, Freight Items and Tax: Calculate the discount amount based on the amount of line items, freight, and tax of your invoices, but not freight and charges at the invoice header level.
Lines and Tax, not Freight Items and Tax: Calculate the discount amount based on the line items and their tax amounts, but not the freight items and their tax lines, of your invoices

Effective Date: Range of Effective Dates for this payment term. If no end date provided, the payment term will be active indefinitely

Receivables uses the following hierarchy to determine the default payment term for your transactions, stopping when one is found:

Bill-to site, defined at the Site level profile of the customer record
Customer, defined at the Account level profile of the customer record
Transaction Type

NOTE: Once a payment term has transactions associated to it, it cannot be updated. A new payment term would need to be created.

SQL Query to get the defined Payment Terms in Oracle Apps R12:

SELECT RA.TERM_ID, RA.NAME PAYMENT_TERM_NAME , RA.DESCRIPTION DESCRIPTION , RA.BASE_AMOUNT, RA.PREPAYMENT_FLAG, RA.CYCLE_NAME
FROM APPS.RA_TERMS RA

Oracle EBS R12 AR Navigation Path

The blog provides the Oracle EBS R12 Navigation Path for the main AR Windows

Window Name	Navigator Path
Account Details	Collections->Account Details
Account Overview	Collections->Account Overview
Accounting Calendar	Set Up->Financials->Calendars-> Periods
Accounting Periods	Accounting->Open/Close Periods
Aging	Collections->Aging
Alternate Name Receipt Matches	Customers->Alternate Name Matches
Adjustment Approval Limits	Set Up->Transactions->Adjustment Limits
Aging Buckets	Set Up->Collections->Aging Buckets
Aging	Collections->Aging
Approve Adjustments	Control->Adjustments->Approve Adjustments
Assign Flexfield Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Assign Key Flexfield Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Assign Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
AutoCash Rule Sets	Set Up->Receipts->AutoCash Rule Sets
AutoInvoice Grouping Rules	Set Up->Transactions->AutoInvoice ->Grouping Rules
Automatic Accounting	Set Up->Transactions-> AutoAccounting
Automatic Payment Programs	Set Up->Receipts->Receipt Programs
Bank Charges	Set Up->Receipts->Bank Charges
Banks	Set Up->Receipts->Bank
Category Codes	Set Up->Transactions->Item-> Category->Define->Category
Category Sets	Set Up->Transactions->Item-> Category Define->Default Sets
Clear/Risk Eliminate	Receipts->Clear/Risk Eliminate
Collectors	Set Up->Collections->Collectors
Completed Requests	Control->Requests->View
Concurrent Requests Summary	Control->Concurrent
Conversion Rate Types	Set Up->Financials->Currencies-> Rates->Types
Copy Transactions	Transactions->Copy
Correspondence	Collections->Correspondence
Countries and Territories	Set Up->System->Countries
Create AutoAdjustments	Control->Adjustments->Create AutoAdjustments
Credit Transactions	Transactions->Credit Transactions
Cross Validation Rules	Set Up->Financials->Flexfields-> Key-> Rules
Currencies	Set Up->Financials->Currencies-> Define
Customer Accounts	Collections->Customer Account
Customer Calls	Collections->Record A Call
Customer Interface	Interfaces->Customer
Customer Merge	Customers->Merge
Customer Profile Classes	Customers->Customer Profile Classes
Customers Quick	Customers->Customer Quick
Customers Standard	Customers->Customer Standard
Customers Summary	Customers->Customer Summary
Daily Rates	Set Up->Financials->Currencies-> Rates->Daily
Default Category Sets	Set Up->Transactions->Item-> Category->Define->Sets
Define Security Rules	Set Up->Financials->Flexfields-> Descriptive->Security->Define
Descriptive Flexfield Segments	Set Up->Financials->Flexfields-> Descriptive->Segments
Distribution Sets	Set Up->Receipts->Distribution Sets
Document Sequences	Application->Document->Define (use System Administrator responsibility)
Dunning History	Collections->Account Details. Choose Dunning History button.
Dunning Letter Sets	Set Up->Print->Dunning Letter Sets
Dunning Letters	Set Up->Print->Dunning Letters
F4 Define Organization	Set Up->System->Organization
Freight Carriers	Set Up->System->QuickCodes-> Freight
GL Accounts	Set Up->Financials->Combinations
Interface: Customer	Interfaces->Customer
Interfaces: AutoInvoice	Interfaces->AutoInvoice
Inventory Delete Items	Set Up->Transactions->Item->Delete Items
Invoice Line Ordering Rules	Set Up->Transactions->AutoInvoice ->Line Ordering
Invoicing and Accounting Rules	Set Up->Transactions->Rules
Item Status Codes	Set Up->Transactions->Item->Status
Item Tax Rate Exceptions	Set Up->Tax->Exceptions
Key Flexfield Security Rules	Set Up->Financials->Flexfields->Key ->Security->Define
Lockbox Transmission History	Receipts->Lockbox->Transmission History
Lockboxes	Set Up->Receipts-> Lockbox->Lockbox
Lockbox Transmission Data	Receipts->Lockbox->Maintain Transmission Data
Memo Lines	Set Up->Transactions->Memo Lines
Open/Close Accounting Periods	Accounting->Open/Close Periods
Payment Methods	Set Up->Receipts->Receipt Classes
Payment Programs	Set Up->Receipts->Receipt Programs
Payment Terms	Set Up->Transactions->Payment Terms
Period Rates	Set Up->Financials->Currencies-> Rates->Period
Period Types	Set Up->Financials->Currencies-> Rates->Type
Print Accounting Reports	Reports->Accounting
Print Dunning	Print->Documents->Dunning
Print Invoices	Print->Documents->Invoices
Print Statements	Print->Documents->Statements
Profile User Values	Control->Profile Options
Quick Codes Demand Class	Set Up->System->QuickCodes-> Demand Class
Quick Find by Alternate Name	Customers->Quick Find by Alternate Name
Receipt Batches Summary	Receipts->Receipts Summary
Receipt Batches	Receipts->Batches
Receipt Classes	Set Up->Receipts->Receipt Classes
Receipt Sources	Set Up->Receipts->Receipt Sources
Receipts Summary	Receipts->Receipts Summary
Receipts	Receipts->Receipts
Receivables Activities	Set Up->Receipts->Receivable Activity
Receivables Quick Codes	Set Up->System->QuickCodes-> Receivable
Remit-To Addresses	Set Up->Print->Remit To Addresses
Remittances Summary	Receipts->Remittances
Remittances	Receipts->Remittances
Request Sets (User Mode)	Control->Requests->Set
Requests Accounting	Reports->Accounting
Requests Collection	Reports->Collections
Requests Listing	Reports->Listing
Requests Other	Reports->Other
Requests Submit	Control->Requests->Run
Run AutoInvoice	Interfaces->AutoInvoice
Run Customer Interface	Interfaces->Customer
Run General Ledger Interface	Interfaces->General Ledger
Run Revenue Recognition	Control->Accounting->Revenue Recognition
Run Tax Rate Interface page	Interfaces->Tax Rate
Sales Tax Rates	Set Up->Tax->Sales Tax Rates
Salespersons	Set Up->Transactions->Salespersons
Scheduler	Collections->Scheduler
Segment Values	Set Up->Financials->Flexfields-> Descriptive->Values
Set of Books	Set Up->Financials->Books
Shorthand Aliases	Set Up->Financials->Flexfields->Key ->Aliases
Standard Memo Lines	Set Up->Transactions->Memo Lines
Standard Messages	Set Up->Print->Standard Messages
Statement Cycles	Set Up->Print->Statement Cycles
Submit Lockbox Processing	Interfaces->Lockbox
System Options	Set Up->System->System Options
Tax Authorities	Set Up->Tax->Authorities
Tax Codes and Rates	Set Up->Tax->Codes
Tax Exemptions	Set Up->Tax->Exemptions
Tax Locations and Rates	Set Up->Tax->Locations
Tax Options	Set Up->Tax->GL Tax Assignments
Territories	Set Up->Transactions->Territories
Transaction Batches Summary	Transactions->Batches Summary
Transaction Batches	Transactions->Batches
Transaction Overview	Collections->Transaction Overview
Transaction Sources	Set Up->Transactions->Sources
Transaction Summary	Transactions->Transaction Summary
Transaction Types	Set Up->Transactions->Transaction Types
Transactions	Transactions->Transactions
Transactions Summary	Transactions->Transactions Summary
Transmission Formats	Set Up->Receipts->Lockbox Transmission
Units of Measure Classes	Set Up->System->UOM->Class
Units of Measure	Set Up->System->UOM->UOM
Viewing Requests	Other->Requests->View

Query To get On Hold Concurrent Request in Oracle Apps R12

The blog provides the query to identify the HOLD Requests by mapping with the below given tables to get the session and process specific details for the Running Concurrent Requests having Hold.

APPS.FND_CONCURRENT_REQUESTS
GV$PROCESS
GV$SESSION
GV$LOCKED_OBJECT
GV$LOCK
DBA_OBJECTS

QUERY TO GET THE HOLDS ON THE CONCURRENT REQUESTS:

SELECT
FCR.REQUEST_ID,
FCR.HOLD_FLAG,
GV_SESSION.SERVICE_NAME,
GV_SESSION.SQL_TRACE,
GV_PROCESS.PROGRAM,
GV_SESSION.MODULE,
GV_SESSION.ACTION,
GV_PROCESS.ADDR,
GV_PROCESS.PGA_USED_MEM,
GV_PROCESS.PGA_ALLOC_MEM,
GV_SESSION.LOCKWAIT,
GV_SESSION.STATUS SESSION_STATUS,
GV_SESSION.MACHINE,
GV_SESSION.PORT,
GV_SESSION.CLIENT_IDENTIFIER,
GV_SESSION.BLOCKING_SESSION_STATUS IS_SESSION_BLOCKED,
GV_SESSION.WAIT_CLASS,
GV_SESSION.SECONDS_IN_WAIT,
GV_LOCK_OBJ.OBJECT_ID,
GV_LOCK_OBJ.SESSION_ID,
OBJECT_NAME,
OBJECT_TYPE,
DECODE( GV_LOCK.BLOCK
, 0, 'Not Blocking'
, 1, 'Blocking'
, 2, 'Global'
) STATUS
,      DECODE( GV_LOCK_OBJ.LOCKED_MODE
, 0, 'None'
, 1, 'Null'
, 2, 'Row-Share (SS)'
, 3, 'Row-Xclusive (SX)'
, 4, 'Share'
, 5, 'S/Row-Xclusive (SSX)'
, 6, 'Exclusive'
, TO_CHAR(LMODE)
) MODE_HELD
FROM   APPS.FND_CONCURRENT_REQUESTS FCR
,      GV$PROCESS GV_PROCESS
,      GV$SESSION GV_SESSION
,      GV$LOCKED_OBJECT GV_LOCK_OBJ
,      GV$LOCK GV_LOCK
,      DBA_OBJECTS DBA_OBJ
WHERE 1=1
AND FCR.PHASE_CODE = 'R'
AND    FCR.ORACLE_PROCESS_ID = GV_PROCESS.SPID (+)
AND    GV_PROCESS.ADDR = GV_SESSION.PADDR (+)
AND    GV_SESSION.SID = GV_LOCK_OBJ.SESSION_ID (+)
AND    GV_LOCK_OBJ.OBJECT_ID = DBA_OBJ.OBJECT_ID (+)
AND    GV_LOCK_OBJ.OBJECT_ID = GV_LOCK.ID1 (+)
AND    FCR.HOLD_FLAG ='Y'

FND_CONCURRENT_REQUESTS Status Codes and Phase Code values

We execute very frequently SQL on the table – FND_CONCURRENT_REQUESTS to get the details on the Concurrent details to analysis and know the parameters and other details but not sure if we actually have details on all Status Codes and Phase Codes getting used in the table – FND_CONCURRENT_REQUESTS

MEANING FOR THE PHASE_CODE COLUMN VALUES:
C Completed
I Inactive
P Pending
R Running

MEANING FOR THE STATUS_CODE COLUMN VALUES:
A Waiting
B Resuming
C Normal
D Cancelled
E Error
F Scheduled
G Warning
H On Hold
I Normal
M No Manager
Q Standby
R Normal
S Suspended
T Terminating
U Disabled
W Paused
X Terminated
Z Waiting