Oracle Apps LDT Download/Upload Commands

LDT Commands for Download/Upload files from UNIX:- 

Concurent Program :-

• Download :  FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XXNAME_CP.ldt PROGRAM APPLICATION_SHORT_NAME="XX_CUSTOM" CONCURRENT_PROGRAM_NAME="XXCPNAME"

• Upload : FNDLOAD apps/<pwd> O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XXNAME_CP.ldt

---------------------------------------------------------------------------------------------------------------------------

Data Definition :-

• Download : FNDLOAD apps/<pwd> O Y DOWNLOAD  $XDO_TOP/patch/115/import/xdotmpl.lct XXNAME_DD.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME='XX_CUSTOM' DATA_SOURCE_CODE='XX_SOURCE' TMPL_APP_SHORT_NAME='XX_CUSTOM' TEMPLATE_CODE='XX_TEMP'

• Upload : FNDLOAD apps/<pwd> O Y UPLOAD $XDO_TOP/patch/115/import/xdotmpl.lct XXNAME_DD.ldt

---------------------------------------------------------------------------------------------------------------------------

Request Group :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_Request_Grp.ldt REQUEST_GROUP REQUEST_GROUP_NAME="ALL Programs" APPLICATION_SHORT_NAME="XX"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_REQUEST_GRP.ldt

---------------------------------------------------------------------------------------------------------------------------

Responsibility :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XXX_CUSTOM_RESP.ldt FND_RESPONSIBILITY RESP_KEY="XXX_CUST_RES"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XXX_CUSTOM_RESP.ldt

---------------------------------------------------------------------------------------------------------------------------

Menu :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXX_CUSTOM_MENU.ldt MENU MENU_NAME="XXX_CUST_MENU"

• Upload : FND_TOP/bin/FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afsload.lct XXX_CUSTOM_MENU.ldt

---------------------------------------------------------------------------------------------------------------------------

Lookup Type :-

• Download : FNDLOAD apps/pwd 0 Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct XX_OA_STATUTORY_ACCT_MAPPING.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME="XX" LOOKUP_TYPE="XX_OA_STATUTORY_ACCT_MAPPING"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLAOD $FND_TOP/patch/115/import/aflvmlu.lct XX_OA_STATUTORY_ACCT_MAPPING.ldt

---------------------------------------------------------------------------------------------------------------------------

Value Set Only :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME="value set name"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

---------------------------------------------------------------------------------------------------------------------------

Value Set with Values :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME="value set name"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt

---------------------------------------------------------------------------------------------------------------------------

Descriptive Flexfield :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct XX_CUSTOM_DFF.ldt DESC_FLEX APPLICATION_SHORT_NAME="FND" DESCRIPTIVE_FLEXFIELD_NAME="FND_COMMON_LOOKUPS" DESCRIPTIVE_FLEX_CONTEXT_CODE="XX_CUST_MAP"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afffload.lct XX_CUSTOM_DFF.ldt

---------------------------------------------------------------------------------------------------------------------------

Concurrent Program assignment to Request Group :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XXOAGLTSIMP_RG.ldt REQUEST_GROUP REQUEST_GROUP_NAME=" DTC Global" APPLICATION_SHORT_NAME="XX" REQUEST_GROUP_UNIT UNIT_NAME="XXOAGLTSIMP"

• Upload : FNDLOAD <apps>/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct XXOAGLTSIMP_RG.ldt REQUEST_GROUP REQUEST_GROUP_NAME=" DTC Global" APPLICATION_SHORT_NAME="XX" REQUEST_GROUP_UNIT UNIT_NAME="XXOAGLTSIMP"

---------------------------------------------------------------------------------------------------------------------------

Workflow [wft file] :-

• Download : WFLOAD APPS/<pwd> 0 Y DOWNLOAD <workflow_name>.wft <workflow_name>

• Upload : WFLOAD apps/<pwd> 0 Y FORCE  <workflow_name>.wft

Note: For Deployment, please stop the workflow listener , First Deploy and after deployment please start workflow listener.

---------------------------------------------------------------------------------------------------------------------------

Forms :-

• Download : FNDLOAD apps/<pwd> O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXFRMNAME.ldt FORM APPLICATION_SHORT_NAME="PN" FORM_NAME="XXFRMNAME"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD @FND:patch/115/import/afsload.lct XXFRMNAME.ldt

---------------------------------------------------------------------------------------------------------------------------

Functions :-

• Download : FNDLOAD apps/<pwd> O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct XXFUNNAME.ldt FUNCTION FUNC_APP_SHORT_NAME="PN" FUNCTION_NAME="XXFUNNAME"

• Upload : FNDLOAD apps/<pwd> O Y UPLOAD @FND:patch/115/import/afsload.lct XXFUNNAME.ldt

---------------------------------------------------------------------------------------------------------------------------

Forms Personalization :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct XX_PERWSHRG.ldt FND_FORM_CUSTOM_RULES function_name="PERWSHRG-404"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct XXGLJOURNALIMP.ldt

---------------------------------------------------------------------------------------------------------------------------

FND Load for DFF Context  :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct XX_PERWSHRG.ldt FND_FORM_CUSTOM_RULES function_name="PERWSHRG-404"

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct XXGLJOURNALIMP.ldt

---------------------------------------------------------------------------------------------------------------------------

FND Load for Messages  :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='ICX' MESSAGE_NAME=XX_ICX_POR_LIFECYCLE_PAY_TIP
• or for all messages: FNDLOAD apps/<pwd> 0 Y DOWNLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ALL_GMS_MESSAGES_00.ldt FND_NEW_MESSAGES APPLICATION_SHORT_NAME='XXGMS'

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $FND_TOP/patch/115/import/afmdmsg.lct XX_ICX_POR_LIFECYCLE_PAY_TIP.ldt

---------------------------------------------------------------------------------------------------------------------------

FND Load for Alert  :-

• Download : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $ALR_TOP/patch/115/import/alr.lct Email_to_requestes_for_PO_Receipt.ldt ALR_ALERTS APPLICATION_SHORT_NAME='PO' ALERT_NAME=' Email to requestes for PO Receipt'

• Upload : FNDLOAD apps/<pwd> 0 Y UPLOAD $ALR_TOP/patch/115/import/alr.lct Email_to_requestes_for_PO_Receipt.ldt

---------------------------------------------------------------------------------------------------------------------------

XML Publisher Data Definition  and Templates :-

• To download all Templates defined for a particular Data Definition : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct ldt_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=[APPSHORTNAME] DATA_SOURCE_CODE=[DATADEFINITIONCODE]

• To download for a particular Template and Data Definition : FNDLOAD apps/<pwd> 0 Y DOWNLOAD $XDO_TOP/patch/115/import/xdotmpl.lct ldt_name.ldt XDO_DS_DEFINITIONS APPLICATION_SHORT_NAME=[APPSHORTNAME] DATA_SOURCE_CODE=[DATADEFSHORTCODE] TMPL_APP_SHORT_NAME=[APPSHORTNAME] TEMPLATE_CODE=[TEMPLATECODE]

Oracle EBS SQL Script for Key Flexfield

 SQL Script to display the Parent Value for a given Child Accounting Flexfield Segment  Value :-

Below Query to fetch the Parent Key Flexfield for a specific Child Segment value

SELECT

    ffvv_parent.flex_value        AS parent_segment_value,
    ffvt_parent.description        AS parent_segment_description,
    ffvv_child.flex_value           AS Child_segment_value,
    ffvs.flex_value_set_name

FROM

    FND_FLEX_VALUE_HIERARCHIES ffvh,
    FND_FLEX_VALUES_VL ffvv_child,
    FND_FLEX_VALUES_VL ffvv_parent,
    FND_FLEX_VALUE_SETS ffvs,
    FND_FLEX_VALUES_TL ffvt_parent 

WHERE
    1=1 
AND ffvs.flex_value_set_name = 'XX_GL' -- Replace with your value set name
AND ffvv_child.flex_value_set_id = ffvs.flex_value_set_id
AND ffvv_child.flex_value IN ( 'XXXX' ,'XXXX') -- Replace with the child segment value
AND ffvh.flex_value_set_id = ffvv_child.flex_value_set_id
AND ffvh.child_flex_value_low = ffvv_child.flex_value
AND ffvv_parent.flex_value_set_id = ffvs.flex_value_set_id
AND ffvv_parent.flex_value = ffvh.parent_flex_value
AND ffvt_parent.flex_value_id = ffvv_parent.flex_value_id

AND ffvt_parent.language = USERENV('LANG');

Oracle EBS SQL Script for data extracts

 SQL Script to display the Employee and Supervisor hierarchy details:-

Below Query to fetch the specific person's supervisor details upto higher position level wise

SELECT
        LEVEL seq        ,
        e.person_id      ,
        e.grade_id       ,
        e.job_id         ,
        e.supervisor_id  ,
        e.employee_number,
        e.full_name
FROM
        (
                SELECT DISTINCT
                        paf.person_id      ,
                        paf.grade_id       ,
                        paf.job_id         ,
                        paf.supervisor_id  ,
                        ppf.employee_number,
                        ppf.full_name
                FROM
                        per_all_people_f ppf
                LEFT JOIN
                        per_all_assignments_f paf
                ON        ppf.person_id = paf.person_id
                AND     paf.person_id IS NOT NULL
                AND     (
                                                    SYSDATE BETWEEN ppf.effective_start_date AND ppf.effective_end_date )
                AND     (
                                                    SYSDATE BETWEEN paf.effective_start_date AND paf.effective_end_date ) 
  ) e
CONNECT BY person_id = PRIOR supervisor_id

START WITH person_id = :P_PERSON_ID ORDER BY LEVEL

Oracle EBS SQL Scripts for data extracts

 SQL Script to display the REQUISITION Approver details:-

select

        a.SEGMENT1           ,

        b.creation_date        ,

        b.ACTION_DATE    ,

        b.employee_id          ,

        b.ACTION_CODE    ,

        max(SEQUENCE_NUM),

        c.full_name

from

        po_requisition_headers_all a ,

        po_action_history                  b ,

        per_all_people_f                    c

where

        OBJECT_TYPE_CODE = 'REQUISITION'

and     AUTHORIZATION_STATUS in ( 'APPROVED' ) 

and     a.REQUISITION_HEADER_ID = b.OBJECT_ID

and     b.employee_id  = c.person_id

and     a.SEGMENT1 = '&REQ'          -- Enter Req No.

and     a.ORG_ID   = &ORG               -- Enter Org

GROUP BY

        a.SEGMENT1        ,

        b.creation_date     ,

        b.ACTION_DATE ,

        b.employee_id       ,

        b.ACTION_CODE ,

        c.full_name

order by

        b.creation_date desc;

SQL Script to display the Purchase Order Approver details:-

SELECT

        ph.segment1                  AS po_number,

        ph.creation_date          AS po_creation_date,

        ph.approved_date        AS po_approved_date,

        pah.action_code           AS po_action_code,

        pah.action_date           AS po_action_date,

        fu.user_name               AS approver_username ,

        ppf.full_name              AS approver_name

FROM

        po_headers_all ph

JOIN

        po_action_history pah

ON

        ph.po_header_id = pah.object_id

JOIN

        fnd_user fu

ON

        pah.employee_id = fu.employee_id

LEFT JOIN

        per_people_f ppf

ON

        fu.employee_id = ppf.person_id

WHERE

        pah.object_type_code = 'PO'

AND     pah.action_code     = 'APPROVE' -- Filter for approval actions

AND     ph.segment1             = '&PO'           -- Replace with your desired PO number

ORDER BY

        pah.action_date DESC;

Notes:-

In Oracle Apps PO_ACTION_HISTORY table, OBJECT_TYPE_CODE identifies the specific type of purchasing document involved in an approval/workflow action.

Example:

      A text field indicating the document category.

                'PO'               : Purchase Order.

                'REQ'            : Requisition.

                'RELEASE'  : Blanket Release.

                'PA'               : BPA

Oracle EBS SQL Scripts for data extracts

 SQL Script to display the Supplier Invoices are fully matched with Purchase Order(PO) and Requisition(REQ)  along with Bill-To & Ship-To details:-

SELECT 
        DISTINCT 
prha.segment1              AS requisition_number ,
        pha.segment1                                         AS po_number          ,
        aia.invoice_num                                   AS Invoice_Number     ,
        aia.invoice_date                                   AS Invoice_Date       ,
        aia.description          AS Invoice_Description,
        aia.invoice_amount                             AS Invoice_Amount     ,
        aia.gl_date                 AS Invoice_GL_Date    ,
        pv.vendor_id                                        AS Supplier_ID        ,
        pv.vendor_name                                 AS Supplier_Name      ,
        pvs.vendor_site_code                       AS Supplier_Site      ,
        pv.segment1                                         AS Supplier_Number    ,
        hl_ship.location_code                        AS ship_to_location   ,
        hl_ship.address_line_1                      AS ship_to_address    ,
        hl_bill.location_code                         AS bill_to_location   ,
        hl_bill.address_line_1                       AS bill_to_address
FROM 
        ap_invoices_all aia
JOIN 
        ap_invoice_lines_all aila ON aia.invoice_id = aila.invoice_id
JOIN 
        ap_invoice_distributions_all aida ON aia.invoice_id = aida.invoice_id 
        AND aila.line_number = aida.invoice_line_number
JOIN 
        po_distributions_all pda ON aida.po_distribution_id = pda.po_distribution_id
JOIN 
        po_headers_all pha ON pda.po_header_id = pha.po_header_id
JOIN 
        po_req_distributions_all prda ON pda.req_distribution_id = prda.distribution_id
JOIN 
        po_requisition_lines_all prla ON prda.requisition_line_id = prla.requisition_line_id
JOIN 
        po_requisition_headers_all prha ON prla.requisition_header_id = prha.requisition_header_id
JOIN 
        po_vendors pv ON aia.vendor_id = pv.vendor_id
JOIN 
        po_vendor_sites_all pvs ON aia.vendor_site_id = pvs.vendor_site_id
JOIN 
        hr_locations_all hl_ship ON pha.ship_to_location_id = hl_ship.location_id
JOIN 
        hr_locations_all hl_bill ON pha.bill_to_location_id = hl_bill.location_id
WHERE 
        1=1 --aida.match_status_flag = 'A' 
        AND aia.cancelled_date IS NULL -- Exclude Cancelled Invoices
        AND aia.invoice_amount <> 0 -- Exclude Zero Amount Invoices
        AND aia.org_id = &ORG_ID                   -- Filter by specific Org
        --AND aia.invoice_date >= '01-JAN-2025'    -- Specific Date filter
        AND aia.invoice_date BETWEEN '01-MAY-2020' AND '31-DEC-2024'
ORDER BY 

        aia.invoice_date DESC;

Oracle EBS Module Wise Major Table Details

 Oracle EBS PO Table Names and Description :-

PO_ACTION_HISTORY :- Document approval and control action history table, It stores records for each action (approval, rejection, etc.), linking to the document, user, action type, and date, making it crucial for understanding a document's journey. 

PO_AGENTS :- The central table for buyer/purchasing manager details, linking to human resources.Stores buyer ID (AGENT_ID), defaults (category, ship-to), and links to FND_USER and HR_EMPLOYEES.

PO_DISTRIBUTIONS_ALL :- Purchase order distributions

PO_HEADERS_ALL :- Document headers (for purchase orders, purchase agreements, quotations, RFQs)

PO_LINES_ALL :- Purchase document lines (for purchase orders, purchase agreements, quotations, RFQs)

PO_LINE_LOCATIONS_ALL :- Document shipment schedules (for purchase orders, purchase agreements, quotations, RFQs)

PO_RELEASES_ALL :- Purchase order releases

PO_LINES_ARCHIVE_ALL :- Archived purchase order lines

PO_LINE_LOCATIONS_ARCHIVE_ALL :- Archived purchase order shipments

PO_HEADERS_ARCHIVE_ALL :- Archived purchase orders

PO_LINE_TYPES_B :- Line types

PO_RELEASES_ARCHIVE_ALL :- Archived releases

PO_REQUISITION_HEADERS_ALL :- Requisition headers

PO_REQUISITION_LINES_ALL :- Requisition lines

PO_REQ_DISTRIBUTIONS_ALL :- Requisition distributions

RCV_TRANSACTIONS :- Receiving transactions

RCV_SHIPMENT_HEADERS :- Shipment and receipt header information

RCV_SHIPMENT_LINES :- Receiving shipment line information  

 Oracle EBS Inventory Table Names and Description :-

MTL_CATEGORIES_B :- Code combinations table for Item Category, the core base table for item categories, storing category definitions and linking items to them within Category Sets

MTL_CATEGORY_SETS_B :- is the base table defining Category Sets, which are grouping schemes (like "Purchasing Categories," "Inventory Categories") for items, linked to flexfield structures and controlled at item or item/org levels

MTL_CUSTOMER_ITEMS :- Customer item Information

MTL_CUSTOMER_ITEM_XREFS :- Relationships between customer items and inventory items

MTL_DEMAND :- Sales order demand and reservations

MTL_DEMAND_HISTORIES :- Sales order demand and reservations

MTL_ITEM_LOCATIONS :- Definitions for stock locators

MTL_ITEM_REVISIONS_B :- Item revisions

MTL_ITEM_TEMPLATES_B :- Item template definitions

MTL_ITEM_TEMPL_ATTRIBUTES :- Item attributes and attribute values for a template

MTL_LOT_NUMBERS :- Lot number definitions

MTL_MATERIAL_TRANSACTIONS :- Material transaction table

MTL_MATERIAL_TRANSACTIONS_TEMP :- Temporary table for processing material transactions

MTL_ONHAND_QUANTITIES_DETAIL :- FIFO quantities by control level and receipt,it is a core Inventory table storing detailed, real-time, stack-based on-hand quantities per item, organization, subinventory, locator, and lot, acting as a running log for receipts and issues, allowing accurate availability checks by summing quantities for matching criteria

MTL_PARAMETERS :- It stores organization-level parameters that govern the operational behavior and default settings for each specific inventory organization. It contains records only for organizations classified as Inventory Organizations.

MTL_RESERVATIONS :- Reservations

MTL_SECONDARY_INVENTORIES :- Subinventory definitions

MTL_SECONDARY_LOCATORS :- Item-subinventory-locator assignments

MTL_SERIAL_NUMBERS :- is the core table storing definitions and current status for every unique serial number, linking to item details in MTL_SYSTEM_ITEMS_B

MTL_SYSTEM_ITEMS_B :- is the core base table for item master definitions, storing key attributes for inventory, engineering, and purchasing items across different organizations

MTL_TRANSACTION_ACCOUNTS :- Material transaction distributions

MTL_TRANSACTION_TYPES :- Inventory Transaction Types Table

MTL_TXN_REQUEST_HEADERS :- Move Order headers table

MTL_TXN_REQUEST_LINES :- Move order lines table

MTL_UNIT_TRANSACTIONS :- Serial number transactions 

Oracle EBS General Ledger Table Names and Description :-

GL_CODE_COMBINATIONS :- is the core table storing valid, unique Accounting Flexfield (Chart of Accounts) combinations, identified by CODE_COMBINATION_ID, linking segments (like Company, Account, Cost Center) to specific ledger IDs, and holding flags for enablement, budget/posting, and account type, crucial for joining GL data with subledgers like AP, AR, and PO

GL_SETS_OF_BOOKS :- (from 11i) is largely replaced by GL_LEDGERS, which stores ledger information like currency, chart of accounts, and calendar, but GL_SETS_OF_BOOKS still exists for legacy support and reference, linked to key tables like GL_CODE_COMBINATIONS, GL_JE_HEADERS, and GL_BALANCES to define financial structures. Understanding these tables helps in querying account balances, journal entries, and set up details in Oracle General Ledger. 

GL_IMPORT_REFERENCES :- Stores individual transactions from subledgers

GL_DAILY_RATES :- Stores the daily conversion rates for foreign currency Transactions

GL_PERIODS :- The core table holding definitions for each accounting period (e.g., 'JAN-24') within a specific calendar, including START_DATE, END_DATE, PERIOD_TYPE, and fiscal year info.

GL_JE_BATCHES :- Stores journal entry batches

GL_BALANCES :- Stores actual, budget, and encumbrance balances for detail and summary accounts

GL_BUDGETS :- Stores Budget definitions

GL_BUDGET_INTERFACE :- Upload budget data from external sources

GL_DAILY_RATES_INTERFACE :- Import daily conversion rates

GL_PERIOD_SETS :- Defines the accounting calendars (like 'Corporate Calendar'), linking to GL_PERIODS, established in the Accounting Calendar form.

GL_PERIOD_STATUSES :- Tracks the open/closed/future status (CLOSING_STATUS) for periods, often tied to specific applications/ledgers.

GL_PERIOD_TYPES :- Stores period types (e.g., 'Monthly', 'Quarterly') used in calendars, defined via the Period Types form.

GL_JE_HEADERS :- Holds header info for journal entries (batches, categories, sources).

GL_JE_LINES :- Contains the detailed debit/credit lines for journal entries.

GL_INTERFACE :- A staging table for data imported from external systems before Journal Import processes it into GL. 

Oracle EBS XLA-Subledger Accounting Table Names and Description :-

XLA_EVENTS :- The XLA_EVENTS table record all information related to a specific event. This table is created as a type XLA_ARRAY_EVENT_TYPE.

XLA_TRANSACTION_ENTITIES :- The table XLA_ENTITIES contains information about sub-ledger document or transactions.

XLA_AE_HEADERS :- The XLA_AE_HEADERS table stores subledger journal entries. There is a one-to-many relationship between accounting events and journal entry headers.

XLA_AE_LINES :- The XLA_AE_LINES table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines.

XLA_DISTRIBUTION_LINKS :- The XLA_DISTRIBUTION_LINKS table stores the link between transactions and subledger journal entry lines.

XLA_ACCOUNTING_ERRORS :- The XLA_ACCOUNTING_ERRORS table stores the errors encountered during execution of the Accounting Program.

XLA_ACCTG_METHODS_B :- The XLA_ACCTG_METHODS_B table stores Subledger Accounting Methods (SLAM) across products. SLAMs provided by development are not chart of accounts specific. Enabled SLAMs are assigned to ledgers.

XLA_EVENT_TYPES_B :- The XLA_EVENT_TYPES_B table stores all event types that belong to an event class.

XLA_GL_LEDGERS :- This table contains ledger information used by subledger accounting.

Oracle EBS CE - Cash Management Table Names and Description :-

CE_BANK_ACCOUNTS :- This table contains bank account information. Each bank account must be affiliated with one bank branch.

CE_BANK_ACCT_BALANCES :- This table stores the internal bank account balances

CE_BANK_ACCT_USES_ALL :- This table stores information about your bank account uses.

CE_STATEMENT_HEADERS :- Bank statements

CE_STATEMENT_LINES :- Bank statement lines

CE_STATEMENT_HEADERS_INT :- Open interface for bank statements

CE_STATEMENT_LINES_INTERFACE :- Open interface for bank statement lines

CE_TRANSACTION_CODES :- Bank transaction codes