Search Results ap_web_oa_mainflow_pkg




Overview
Explore in AI Chat

Overview

AP_WEB_OA_MAINFLOW_PKG is the central PL/SQL package underpinning the Oracle E-Business Suite Internet Expenses (OIE) mainflow — the end-to-end flow an employee traverses when creating, validating, approving, and submitting an expense report through the self-service web interface. Residing in the APPS schema, it is the orchestrator that mediates between the Oracle Application Framework (OAF) expense-entry pages, the expense report data model, the HR employee hierarchy, and the Oracle Workflow engine that routes reports for approval. The package is classified as an OTHER API in ETRM, indicating it is a supporting internal package rather than a formally published open interface; nevertheless, its procedures are called extensively by other OIE packages and forms.

The package is documented as VALID in both 12.1.1 and 12.2.2. Its scope spans report-header validation, receipt-line validation, account-segment derivation and rebuild, employee lookup, currency information, and full lifecycle actions such as submit, withdraw, duplicate, and delete.

Key Procedures and Functions

ETRM documents 20 procedures/functions. Their purposes are:

  • DELETEEXPENSEREPORT / DELETEREPORT — Remove an expense report and its dependent lines, integrating with related charges.
  • GETEMPLOYEEIDFROMBOTHPAYPARENT — Resolve the employee identifier from both pay and parent relationships in HR.
  • GETEMPLOYEEINFO — Retrieve employee attributes (e.g., name, organization) for display and validation.
  • GETGENERALINFO — Return general system/setup information used by the mainflow.
  • ISGRANTSENABLED — Determine whether Grants Accounting integration is active, affecting accounting behavior.
  • VALIDATEREPORTHEADER — Apply header-level business rules before submission.
  • VALIDATERECEIPTLINE — Validate individual receipt/expense lines (amounts, categories, required fields).
  • OASUBMITWORKFLOW — Initiate the approval workflow for a submitted report.
  • GETITEMDESCLOOKUPCODE — Resolve the lookup code for an expense item description.
  • GETUSERID — Return the FND_USER identifier of the current user.
  • WITHDRAWEXPENSEREPORT — Reverse a submitted report back to the employee for correction.
  • GETFUNCTIONALCURRENCYINFO — Supply functional currency details for conversion and display.
  • DUPLICATEEXPENSEREPORT — Clone an existing report (header and lines) as a new draft.
  • GETORGIDFROMHR — Derive the HR organization identifier for the employee.
  • GETDEFAULTACCTGSEGVALUES — Return default accounting flexfield segment values for a report/line.
  • VALIDATEACCOUNTSEGMENTS — Validate the accounting segments against the chart of accounts.
  • REBUILDACCOUNTSEGMENTS — Reconstruct account segment strings after changes.
  • UPDATEEXPENSEDAMOUNT — Adjust the expense amount on a report.
  • UPDCHARGESFROMDELETEDREPORT — Update credit-card charges affected by deletion.

Tables Accessed

The package reads and writes the core OIE and Payables tables via APPS synonyms: AP_EXPENSE_REPORT_HEADERS and AP_EXPENSE_REPORT_HEADERS_S (report header current and audit/shadow), AP_EXPENSE_REPORT_LINES and AP_EXPENSE_REPORT_LINES_ALL (detail lines), AP_EXPENSE_REPORTS, AP_EXPENSE_REPORT_PARAMS (report parameters), AP_CREDIT_CARD_TRXNS (corporate card transactions), AP_SUPPLIERS, AP_SYSTEM_PARAMETERS, FND_USER, and PLITBLM (line-level PL/SQL table). It also references HR_EMPLOYEES_CURRENT_V and OIE OIE_PDM_* collection types for in-memory processing, plus AP_WEB_PARENT_PKG and AP_OIE_KFF_SEGMENTS_T for accounting key flexfield handling.

Usage Notes

AP_WEB_OA_MAINFLOW_PKG is invoked primarily by the OAF-based Internet Expenses forms (AP_WEB_EXPENSE_FORM) and by the OIE workflow (AP_WEB_EXPENSE_WF) during submit and approval processing. Other packages — AP_WEB_ACCTG_PKG, AP_WEB_DB_AP_INT_PKG, AP_WEB_DB_CCARD_PKG, and AP_WEB_OA_DISC_PKG — call into it, and it is referenced by 6 packages total in ETRM. Customizations should treat it as an internal dependency; because its procedures are not a published API, direct calls should be limited to extensions that must replicate mainflow behavior, with careful attention to OIE validation and accounting rules. In 12.2.2 the structure is unchanged from 12.1.1, so custom code dependent on these procedures generally remains portable across both releases.