Search Results maintain_batch_status




Overview
Explore in AI Chat

Overview

CN_CALC_SUBMISSION_PVT is a private PL/SQL package in the Oracle EBS Applications (APPS) schema that supports the Oracle Channel Revenue Management (formerly Trade Management) calculation submission engine. Its central responsibility is to manage and process calculation submission batches — logical groupings of transactions (vendor claims, customer claims, or supplier-side accrual items) that must undergo quota, accrual, and interval-based calculations before they can be settled. The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the definer, and it is classified as PVT in the ETRM registry, which signals that it is intended for internal use by other calculation-submission components rather than direct invocation by end users or external custom code. The single line of header comments (cnvsbcss.pls 120.2, dated July 2005) confirms that this code predates the 12.1.1/12.2.2 releases and has remained largely stable, which is common for core calculation infrastructure in the Channel Revenue Management module.

Key Procedures and Functions

The ETRM metadata documents four procedures within the package. Each follows the standard Oracle EBS API signature convention, including the ubiquitous p_api_version, p_init_msg_list, p_commit, p_validation_level, x_return_status, x_msg_count, and x_msg_data parameters, though only their purpose is described here per the source documentation.

  • VALIDATE — Validates a calculation submission batch identified by p_calc_sub_batch_id. This is the entry check that ensures a batch is structurally and referentially sound before any expensive calculation work is attempted.
  • COPYBATCH — Copies a calculation submission batch, enabling users or processes to duplicate an existing batch configuration as the basis for a new submission.
  • CALCULATE — Processes a calculation submission batch. Per the header comments, this procedure "commits automatically," meaning it performs its own transactional commit rather than relying on the caller to commit.
  • MAINTAIN_BATCH_STATUS — The procedure that matched the user's search term. As the name implies, it is responsible for maintaining (setting, updating, or transitioning) the status of a calculation submission batch, ensuring the batch lifecycle state accurately reflects the outcome of validation, calculation, or copying operations.

Tables Accessed

Seven of the fourteen documented tables are transactional batch tables: CN_CALC_SUBMISSION_BATCHES, CN_CALC_SUBMISSION_BATCHES_ALL, CN_CALC_SUBMISSION_BATCHES_S1, CN_CALC_SUBMISSION_ENTRIES, CN_CALC_SUBMISSION_ENTRIES_S1, CN_CALC_SUB_QUOTAS, and CN_CALC_SUB_QUOTAS_S. The batch and entry tables hold the header and line-level records of a submission, while the _S1 and _S suffixed objects are sequence/denormalized support objects used to generate IDs and maintain ordering.

The remaining tables are reference and status sources: CN_QUOTAS, CN_QUOTAS_ALL (the quota definitions against which submissions are calculated), CN_COMP_PLANS_ALL (compensation plans), CN_INTERVAL_TYPES and CN_INTERVAL_TYPES_ALL_TL (interval type definitions and their translated names), CN_PERIOD_STATUSES_ALL (the accounting period status that gates whether a batch may be calculated or settled), and CN_PROCESS_AUDITS / CN_PROCESS_AUDITS_ALL (audit trail records capturing processing history). Together these tables allow the package to validate batch integrity, perform the actual quota and accrual computations, and record outcomes for auditing.

Usage Notes

Because CN_CALC_SUBMISSION_PVT is a private (PVT) package, it is not intended for direct invocation by end users or external integrations. It is referenced by exactly one other packaged object in the ETRM registry, which strongly suggests a thin public or JTF-facing wrapper orchestrates calls to VALIDATE, CALCULATE, COPYBATCH, and MAINTAIN_BATCH_STATUS. In practice, these procedures are driven by the Oracle Channel Revenue Management calculation submission concurrent programs and OAF/Forms-based UIs that let users create, copy, validate, and run calculation submission batches. The MAINTAIN_BATCH_STATUS procedure is typically invoked as a bookkeeping step before and after the heavier CALCULATE routine so that the batch header status remains consistent even if the caller aborts. Custom code should avoid calling this package directly; instead, use the supported public APIs in the CN product family, as the private signature is subject to change and is protected by the AUTHID CURRENT_USER model.