Search Results ap_batches_s2
Overview
APPS.AP_WEB_EXPORT_ER is a PL/SQL package body in the Oracle E-Business Suite Payables (AP) module, classified under the Internet Expenses (OIE) product family. Its purpose is to export approved expense report data into the Oracle Payables invoice interface tables so that expense reports can be converted into supplier invoices and subsequently paid. In the context of Oracle EBS 12.1.1 and 12.2.2, the package acts as the bridge between the expense reporting workflow in Internet Expenses (AP_WEB) and the Payables invoice import process driven by AP_IMPORT_INVOICES_PKG.
The object resides in the APPS schema with a status of VALID and is classified as an OTHER module API. It is not referenced by any other database object, indicating that it functions as a top-level integration utility invoked directly by concurrent programs, forms, or workflow background processes rather than being called from other PL/SQL packages. The dependency list confirms it reads from expense report headers, lines, and distributions and writes into the Payables open interface tables.
Key Procedures and Functions
The package exposes seven documented procedures and functions. Their names indicate the following functions:
- EXPORTERTOAP — The primary driver routine. It orchestrates the export of approved expense report data into the Payables invoice interface, coordinating validation, vendor resolution, and interface insertion.
- VALIDATEERLINES — Validates expense report lines prior to export. The routine identifies data inconsistencies or missing attributes and records rejections for lines that cannot be exported.
- INSERTINVOICEINTERFACE — Inserts header-level records into AP_INVOICES_INTERFACE, establishing the invoice shell that will be imported into Payables.
- INSERTINVOICELINESINTERFACE — Inserts the corresponding line-level records into AP_INVOICE_LINES_INTERFACE, including distribution and accounting information.
- GETVENDORINFO — Retrieves supplier and supplier site information required to populate the invoice interface, using supplier and payee data.
- CREATEPAYEE — Creates or resolves the payee (employee or external party) for the expense report so that payment can be directed correctly.
- UPDATEDISTSWITHRECEIPTINFO — Updates expense report distributions with receipt-related information, aligning invoice line detail with expense line receipt data.
Tables Accessed
The package references a broad set of tables through APPS synonyms. Expense report data is read from AP_EXPENSE_REPORT_HEADERS, AP_EXPENSE_REPORT_HEADERS_ALL, AP_EXPENSE_REPORT_LINES, AP_EXPENSE_REPORT_LINES_ALL, and AP_EXP_REPORT_DISTS / AP_EXP_REPORT_DISTS_ALL. Interface output is written to AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE. Supplier and payee resolution uses AP_SUPPLIERS and AP_SUPPLIER_SITES, while employee data is obtained from PER_ALL_PEOPLE_F. Credit card expenses are sourced from AP_CREDIT_CARD_TRXNS_ALL. Rejected rows are logged to AP_INTERFACE_REJECTIONS, and AP_INVOICES is referenced for invoice-side context. Supporting setup data is drawn from AP_SYSTEM_PARAMETERS, FND_CURRENCIES, GL_CODE_COMBINATIONS, and GL_PERIOD_STATUSES.
Usage Notes
AP_WEB_EXPORT_ER is invoked during the Internet Expenses-to-Payables integration flow, typically by the Payables Invoice Import concurrent program or by OIE-specific export processing. It should be executed only after expense reports have been fully approved through AP_WEB_EXPORT_WF and associated workflow. Because it writes directly to the open interface tables, standard import must be run afterward to create actual invoices, and rejection records in AP_INTERFACE_REJECTIONS should be reviewed for failures. The presence of AP_BATCHES_S2 in the dependency list reflects invoice batch sequencing used during export. Customizations should call the package in conformance with the delivered AP_IMPORT_INVOICES_PKG conventions and should not bypass interface validation.
-
SYNONYM: APPS.AP_BATCHES_S2
12.1.1
owner:APPS, object_type:SYNONYM, object_name:AP_BATCHES_S2, status:VALID,
-
SEQUENCE: AP.AP_BATCHES_S2
12.2.2
owner:AP, object_type:SEQUENCE, object_name:AP_BATCHES_S2, status:VALID,
-
SEQUENCE: AP.AP_BATCHES_S2
12.1.1
owner:AP, object_type:SEQUENCE, object_name:AP_BATCHES_S2, status:VALID,
-
SYNONYM: APPS.AP_BATCHES_S2
12.2.2
owner:APPS, object_type:SYNONYM, object_name:AP_BATCHES_S2, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.AP_WEB_EXPORT_ER
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AP_WEB_EXPORT_ER, status:VALID,
-
PACKAGE BODY: APPS.AP_IMPORT_UTILITIES_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:AP_IMPORT_UTILITIES_PKG, status:VALID,
-
PACKAGE BODY: APPS.AP_IMPORT_UTILITIES_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:AP_IMPORT_UTILITIES_PKG, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_BATCHES_S2
12.2.2
-
APPS.AP_WEB_EXPORT_ER dependencies on AP_BATCHES_S2
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_BATCHES_S2
12.1.1
-
APPS.AP_WEB_EXPORT_ER SQL Statements
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_BATCHES_S
12.2.2
-
APPS.AP_WEB_EXPORT_ER dependencies on AP_BATCHES
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_BATCHES_S
12.1.1
-
APPS.AP_WEB_EXPORT_ER dependencies on DUAL
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on DUAL
12.2.2
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on DUAL
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG SQL Statements
12.2.2
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_BATCHES
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.AP_WEB_EXPORT_ER
12.1.1
-
PACKAGE BODY: APPS.AP_IMPORT_UTILITIES_PKG
12.1.1
-
PACKAGE BODY: APPS.AP_IMPORT_UTILITIES_PKG
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_IMPORT_INVOICES_PKG
12.1.1
-
APPS.AP_IMPORT_UTILITIES_PKG dependencies on AP_IMPORT_INVOICES_PKG
12.2.2