Search Results fun_dist_lines_s
Overview
FUN_TRX_PUB is the public PL/SQL package body owned by the APPS schema that supports Oracle E-Business Suite Funds Capture and disbursement transaction processing. It sits within the Funds Disbursement (FUN) module and serves as a published API layer sitting above the private implementation package FUN_TRX_PVT. Its principal role is to accept a transaction (batch) creation request, validate and stage the associated header, line, and distribution records, and hand control to the Funds Capture workflow for downstream processing. The package has been certified as VALID and is classified as a public (PUB) API, meaning it is intended to be called by external consumers such as concurrent programs, forms, or custom code rather than being restricted to internal use within the FUN module.
Key Procedures and Functions
The documented ETRM metadata lists a single public entry point for this package body:
- CREATE_BATCH — The public API for creating a funds capture or disbursement batch. It serves as the orchestration procedure through which a caller submits a batch request. Internally it validates the incoming data, resolves ledger and legal-entity context, persists the transaction rows into the FUN_TRX_* tables, records any failures in the interface rejection tables, and coordinates message handling via FND_MSG_PUB.
Although only CREATE_BATCH is documented as public, the dependency list shows that FUN_TRX_PUB calls the private package FUN_TRX_PVT for its core implementation logic, and invokes FUN_WF_COMMON, FUN_INITIATOR_WF_PKG, and FUN_TCA_PKG to drive workflow initiation and trading community (TCA) lookups. Error conditions are raised through APP_EXCEPTION and the FND_API utility stack.
Tables Accessed
The package reads from and writes to a well-defined set of FUN and XLE tables, including the sequence-backed primary objects and their interface staging counterparts:
- Transaction header tables — FUN_TRX_HEADERS and FUN_TRX_HEADERS_S store the batch header and its primary key sequence; these represent the persisted transaction being created.
- Transaction line tables — FUN_TRX_LINES and FUN_TRX_LINES_S hold the line-level detail of each disbursement or capture transaction.
- Batch distribution tables — FUN_BATCH_DISTS, FUN_BATCH_DIST_S, FUN_DIST_LINES, and FUN_DIST_LINES_S hold accounting distribution data associated with the batch. The _S suffixed objects are the sequence generators that supply surrogate keys at insert time.
- Batch header tables — FUN_TRX_BATCHES and FUN_TRX_BATCHES_S provide the batch grouping used to associate multiple transactions.
- Interface staging tables — FUN_INTERFACE_BATCHDISTS, FUN_INTERFACE_DIST_LINES, FUN_INTERFACE_HEADERS, and FUN_INTERFACE_REJECTIONS are used when data is loaded from external sources; the rejection table captures records that fail validation so they can be corrected and resubmitted.
- Legal entity and ledger views — XLE_ENTITY_PROFILES, XLE_FIRSTPARTY_INFORMATION_V, and GL_LEDGER_LE_BSV_SPECIFIC_V supply the legal entity, first-party, and ledger balancing segment context needed to derive the correct accounting entity for each batch.
The user search term fun_dist_lines_s corresponds to the distribution line sequence referenced above; it is the sequence that FUN_TRX_PUB relies on when new distribution rows are inserted during batch creation.
Usage Notes
FUN_TRX_PUB is typically invoked from the Funds Capture concurrent programs, from the Receivables and Payments setup forms, and from custom integrations that need to programmatically create a funds capture batch. Because it is a PUB-classified API, custom code may call CREATE_BATCH directly; callers should supply FND_GLOBAL context (application, responsibility, user, and org) before invocation and should inspect the FND_MSG_PUB message stack after the call to detect validation errors. The package is referenced by two other packages in the APPS schema but does not itself reference any object outside the APPS and SYS owners, with the exception of the DUAL and PLITBLM utility objects. When processing interface data, callers should expect rejected rows to be logged in FUN_INTERFACE_REJECTIONS rather than raised as exceptions, allowing batch processing to continue for valid records.
-
SEQUENCE: FUN.FUN_DIST_LINES_S
12.2.2
owner:FUN, object_type:SEQUENCE, object_name:FUN_DIST_LINES_S, status:VALID,
-
SEQUENCE: FUN.FUN_DIST_LINES_S
12.1.1
owner:FUN, object_type:SEQUENCE, object_name:FUN_DIST_LINES_S, status:VALID,
-
SYNONYM: APPS.FUN_DIST_LINES_S
12.1.1
owner:APPS, object_type:SYNONYM, object_name:FUN_DIST_LINES_S, status:VALID,
-
SYNONYM: APPS.FUN_DIST_LINES_S
12.2.2
owner:APPS, object_type:SYNONYM, object_name:FUN_DIST_LINES_S, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.FUN_TRX_PUB
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_TRX_PUB, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.FUN_WEBADI_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_WEBADI_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_WEBADI_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_WEBADI_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_PERIOD_STATUS_PKG
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_PERIOD_STATUS_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_PERIOD_STATUS_PKG
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_PERIOD_STATUS_PKG, status:VALID,
-
PACKAGE BODY: APPS.FUN_TRX_PUB
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_TRX_PUB, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.FUN_TRX_PVT
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_TRX_PVT, status:VALID,
-
12.2.2 DBA Data
12.2.2
-
PACKAGE BODY: APPS.FUN_RECIPIENT_WF
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_RECIPIENT_WF, status:VALID,
-
PACKAGE BODY: APPS.FUN_TRX_PVT
12.1.1
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_TRX_PVT, status:VALID,
-
PACKAGE BODY: APPS.FUN_RECIPIENT_WF
12.2.2
owner:APPS, object_type:PACKAGE BODY, object_name:FUN_RECIPIENT_WF, status:VALID,
-
APPS.FUN_TRX_PVT dependencies on FUN_DIST_LINES_S
12.2.2
-
APPS.FUN_TRX_PVT dependencies on FUN_DIST_LINES_S
12.1.1
-
APPS.FUN_TRX_PUB dependencies on FUN_DIST_LINES_S
12.1.1
-
APPS.FUN_WEBADI_PKG dependencies on FUN_DIST_LINES_S
12.2.2
-
APPS.FUN_TRX_PUB dependencies on FUN_DIST_LINES_S
12.2.2
-
APPS.FUN_PERIOD_STATUS_PKG dependencies on FUN_DIST_LINES_S
12.1.1
-
APPS.FUN_RECIPIENT_WF dependencies on FUN_DIST_LINES_S
12.2.2
-
APPS.FUN_WEBADI_PKG dependencies on FUN_DIST_LINES_S
12.1.1
-
APPS.FUN_RECIPIENT_WF dependencies on FUN_DIST_LINES_S
12.1.1
-
APPS.FUN_PERIOD_STATUS_PKG dependencies on FUN_DIST_LINES_S
12.2.2
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1