Search Results new_je
Overview
The APPS.CN_LEDGER_JOURNAL_ENTRIES_API package is a public PL/SQL API within the Oracle E-Business Suite Channel Revenue Management (CN) module, historically delivered as part of the Oracle Sales Compensation (CN) schema. The package encapsulates the business logic required to create and interrogate journal entries held in the channel ledger, providing a controlled programmatic interface between application code and the underlying CN_LEDGER_JOURNAL_ENTRIES base tables. It is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling session rather than the package owner, which is significant for direct custom invocations against APPS-owned synonyms.
The package supports the accrual and settlement lifecycle that drives channel revenue accounting, where journal entries record the debit and credit movements associated with sales representatives, periods, batches, and ledger accounts. Its most frequently referenced entry point is the overloaded NEW_JE function, which corresponds directly to the common search term "new_je". The package header carries a creation date of 29-DEC-94 and a header revision of 115.3, reflecting the long-standing stability of the interface across releases.
Key Procedures and Functions
ETRM documents four callable program units, comprising four overloads of NEW_JE together with the NAMES_FROM_IDS procedure.
NEW_JE(three overloaded functions) — Each overload is an API function that creates a new journal entry and returns its journal entry identifier. The overloads differ in the business attributes they accept: the base variant captures batch, sales representative, period, account, credit, debit, and date context; a second variant additionally captures a reason; and a third variant accepts role and credit type identifiers in place of the reason. Parameters are never enumerated here beyond what the header documents; callers should consult the package specification for the authoritative signature.NAMES_FROM_IDS(procedure) — Resolves surrogate identifiers into their human-readable counterparts, returning in/out values for the who-name, reason, posted indicator, sales representative name and identifier, account name, and period name and identifier, based on the supplied batch, sales representative period, and balance identifiers.
Tables Accessed
Through APPS synonyms, the package reads and writes the following objects:
CN_LEDGER_JOURNAL_ENTRIESandCN_LEDGER_JOURNAL_ENTRIES_S— the primary and shadow (sequence/audit) tables holding the journal entry records created byNEW_JE.CN_LEDGER_JE_BATCHES— the batch header to which each new journal entry is assigned via the batch identifier parameter.CN_LEDGER_BAL_TYPES— supplies ledger balance type semantics referenced when mapping credit type and role information.CN_SRP_PERIODS— the sales representative period definitions used to validate the period and sales representative period identifiers.DUAL— the standard single-row source used for function-style scalar evaluation.
Usage Notes
This package is a server-side API intended for programmatic use rather than direct end-user invocation. Typical integration patterns include Oracle Forms-based channel ledger maintenance screens, concurrent programs that generate or settle accrual journal entries in batch, and custom PL/SQL extensions that must post entries while respecting the same validation and sequencing rules applied by Oracle's own code. Because the package is overloaded, custom callers must supply argument lists that match exactly one documented signature to avoid PLS-00307 ambiguity errors. Given that ETRM records no packages referencing this API, it should be treated as a top-level integration surface; developers should wrap calls in their own transaction control and error handling, since the API does not manage commit scope. Release compatibility for 12.1.1 and 12.2.2 is preserved through the APPS synonym layer, but the underlying core tables should never be updated directly.
-
PACKAGE: APPS.CN_LEDGER_JOURNAL_ENTRIES_API
12.1.1
-
PACKAGE: APPS.CN_LEDGER_JOURNAL_ENTRIES_API
12.2.2
-
PACKAGE BODY: APPS.CN_LEDGER_JOURNAL_ENTRIES_API
12.1.1
-
PACKAGE BODY: APPS.CN_LEDGER_JOURNAL_ENTRIES_API
12.2.2
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API SQL Statements
12.1.1
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API SQL Statements
12.2.2
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on DUAL
12.1.1
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on CN_LEDGER_JOURNAL_ENTRIES_S
12.2.2
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on DUAL
12.2.2
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on CN_LEDGER_JOURNAL_ENTRIES_S
12.1.1
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on CN_LEDGER_JOURNAL_ENTRIES
12.1.1
-
APPS.CN_LEDGER_JOURNAL_ENTRIES_API dependencies on CN_LEDGER_JOURNAL_ENTRIES
12.2.2