Search Results get_conc_req_id

Overview

CN_CALC_SUBMISSION_PVT is the private implementation package body for the Oracle E-Business Suite compensation calculation submission engine, delivered as part of the Incentive Compensation (CN) module. It encapsulates the core PL/SQL logic that manages the lifecycle of compensation calculation submissions: validating submission parameters, initiating and copying submission batches, executing the calculation of earnings for sales representatives and quotas, and maintaining the status of submission batches as processing proceeds. The package operates against the CN_CALC_SUBMISSION_BATCHES table family and associated quota, interval, and audit structures. The name suffix _PVT (private) indicates that the procedural interface is not intended as a public API; the corresponding public wrapper package, typically CN_CALC_SUBMISSION_PUB, is the sanctioned entry point for callers. The package body header, revision 120.5, references the source file cnvsbcsb.pls.

Key Procedures and Functions

The documented package members comprise four procedures whose purpose mirrors the calculation submission workflow:

• VALIDATE — Performs pre-processing validation of a calculation submission request, confirming that the batch definition, interval, organizational context, and related parameters are internally consistent and eligible for submission before any calculation work begins.
• COPYBATCH — Creates a new submission batch by copying the definition of an existing batch (including batch attributes such as calculation type, date range, salesrep option, hierarchy flag, and interval type) so that recurring or phased calculations can reuse a prior configuration.
• CALCULATE — Drives the substantive calculation of compensation for the submission, iterating over the sales representatives and quotas associated with the batch and producing the resulting calculation submission entries.
• MAINTAIN_BATCH_STATUS — Manages transitions of the batch status field on CN_CALC_SUBMISSION_BATCHES, ensuring the batch record and its object version reflect the current state of processing.

The body also declares private record types such as sub_batch_rec_type, rep_entry_rec_type, and quota_entry_rec_type, and an internal helper check_end_of_interval that returns 1 when a specified period closes an interval. Notably, sub_batch_rec_type carries a concurrent_request_id sourced from CN_PROCESS_AUDITS, which is the linkage relevant to the search term get_conc_req_id.

Tables Accessed

The package reads and writes through APPS synonyms, principally:

• CN_CALC_SUBMISSION_BATCHES, CN_CALC_SUBMISSION_BATCHES_ALL, and CN_CALC_SUBMISSION_BATCHES_S1 — batch definitions and their key sequences;
• CN_CALC_SUBMISSION_ENTRIES and CN_CALC_SUBMISSION_ENTRIES_S1 — individual calculation results per sales representative;
• CN_CALC_SUB_QUOTAS and CN_CALC_SUB_QUOTAS_S — quotas participating in a given submission;
• CN_QUOTAS and CN_QUOTAS_ALL — the underlying quota master definitions;
• CN_PROCESS_AUDITS and CN_PROCESS_AUDITS_ALL — audit records holding the concurrent_request_id that associates a batch with its Enterprise Command Center (concurrent) request;
• CN_INTERVAL_TYPES and CN_INTERVAL_TYPES_ALL_TL — interval type definitions and translated names;
• CN_PERIOD_STATUSES_ALL and CN_COMP_PLANS_ALL — period open/close rules and compensation plan context used during validation and calculation.

Usage Notes

CN_CALC_SUBMISSION_PVT is invoked indirectly. Users initiate compensation calculations from the Incentive Compensation calculation submission form or by submitting the associated concurrent program; the public package layer calls into this private body to validate, copy, calculate, and update status. The presence of concurrent_request_id in the private record type—derived from CN_PROCESS_AUDITS—explains why searching for get_conc_req_id surfaces this object: the concurrent request identifier is the link used to track a running calculation and to retrieve its output. Because the package is classified PVT and references the _ALL and _TL variant tables, custom code should not call it directly; instead, use the supported public API or the standard concurrent program, which manages audit creation, request identifiers, and batch status updates consistently with multi-org and multilingual data access.