Results for “cn_prepostbatches”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CN_PREPOSTBATCHES is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified under the ETRM metadata as an "OTHER" API type. It forms part of the Oracle Contracts (CN) module's payment posting infrastructure, specifically supporting the pre-posting batch lifecycle for payment worksheets and pay runs. The package functions as a backend controller that prepares and finalizes posting batches, serving as an intermediary stage between the generation of payment transactions and their eventual transfer into the general ledger via the posting batches mechanism. The name of the package—combining "prepost" and "batches"—indicates its role in managing batches that are in a pre-posted state, prior to final accounting distribution. It works closely with the CN_PREPOST_PVT package, which shares the same naming convention and likely handles the private implementation of pre-posting logic. In EBS 12.1.1 and 12.2.2, such packages underpin the concurrent processing architecture that allows large volumes of payment transactions to be grouped, validated, and posted systematically rather than individually.
Key Procedures and Functions
The ETRM documentation identifies three documented program units within CN_PREPOSTBATCHES:
- GET_UID — A function that returns a unique identifier, typically used to obtain a system-generated primary key or session-level sequence value for batch records. This is commonly used in Oracle EBS packages to generate internal IDs before insertion into transactional tables, ensuring referential integrity across related records without relying on sequence lookups in the calling code.
- BEGIN_RECORD — A procedure that initiates or opens a new batch record. It likely performs initialization of the batch structure, sets up default values, and prepares the necessary context for subsequent posting operations. This is a typical "start of transaction" routine that must be called before other batch processing procedures.
- POSTING_CONC — A concurrent-program-oriented procedure, as indicated by the "CONC" suffix typical of Oracle EBS concurrent manager entry points. This procedure serves as the executable logic invoked by a concurrent program to perform batch posting. It would handle the bulk processing of batched payment data, commit the posting results, and likely write output or log information for the concurrent request.
The metadata does not expose parameter signatures, so parameter descriptions are deliberately omitted to avoid speculation. The package contains both a specification and a body, consistent with standard PL/SQL packaging practice.
Tables Accessed
According to the documented metadata, CN_PREPOSTBATCHES references the following tables via APPS synonyms:
- CN_POSTING_BATCHES — The primary table holding posting batch headers and control information. The package reads and writes this table to create, update, and manage the lifecycle of posting batches.
- CN_POSTING_BATCHES_S — A shadow or sequence table associated with CN_POSTING_BATCHES, typically used to derive primary key values for new batch records, consistent with the GET_UID function's role.
- DUAL — The standard Oracle single-row table, used for simple value retrieval such as sequence number generation or sysdate checks.
The package also references the STANDARD package under the SYS schema. The dependency listing confirms it is referenced by several other packages, including CN_PAYMENT_WORKSHEET_PVT, CN_PAYRUN_PVT, CN_PMT_TRANS_PVT, CN_PREPOST_PVT, and itself, indicating it is a foundational utility within the payment posting family.
Usage Notes
CN_PREPOSTBATCHES is typically invoked indirectly through the Oracle Contracts payment processing flow. The POSTING_CONC procedure is the likely entry point for concurrent program execution, where a batch ID or parameter set is passed to the concurrent manager and the package processes batches en masse. The BEGIN_RECORD and GET_UID routines would be called programmatically by other PL/SQL packages—particularly CN_PREPOST_PVT and CN_PAYMENT_WORKSHEET_PVT—when constructing or extending posting batches from the payment worksheet or pay run processes. Custom code should not bypass these packages when manipulating posting batch data, as direct DML could violate batching assumptions and leave the pre-posting state inconsistent. Because the package is referenced by four other packages in the documented dependency chain, any modifications to its specification require recompilation of dependent objects. In 12.2.2 environments, the same logic is preserved, and the package remains VALID in the ETRM registry. Developers searching for "cn_prepost_pvt" should note that CN_PREPOST_PVT is a separate but tightly coupled package that builds upon CN_PREPOSTBATCHES for its posting operations.
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: PUBLIC.DUAL 12.1.1
-
SYNONYM: PUBLIC.DUAL 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1