Results for “process_cons_bill_tbl”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKL_CONS_BILL is an Oracle EBS Contracts (OKL/OKC) PL/SQL package responsible for consolidated billing of lease and service contracts. Its central role is to gather the components of one or more contracts that are eligible for billing and to combine them into a single consolidated invoice record, thereby reducing the number of separate invoices issued to a customer. The package works primarily against the OKL consolidated receivables and external sell invoice views and tables, along with the contract header and line structures that define what is being billed.
The consolidated billing data model is represented internally by two PL/SQL record types. The cons_bill_rec_type record captures the key attributes required to assemble a consolidated bill, including customer_id, currency, bill_to_site, payment_method, contract_id, contract_number, invoice format, organization, set of books, legal entity, and the amounts drawn from the external and transferable sell invoice views. The companion saved_bill_rec_type record persists the consolidated bill information for subsequent processing. These structures drive the logic performed by the package’s documented procedures and functions, and they reflect the package's function of aggregating billing inputs before a consolidated AR invoice is created.
Key Procedures and Functions
- CREATE_CONS_BILL — Creates a consolidated bill record from the supplied billing attributes. It is the entry point that accepts the consolidated billing data and establishes the header-level consolidated invoice within the OKL consolidated receivables structures.
- PROCESS_CONS_BILL_TBL — Processes the consolidated billing table (the collection typed as
cons_bill_tbl_type). It iterates over the assembled billing records and performs the validation, consolidation, and write operations required to complete the consolidated billing run. - GET_INVOICE_GROUP — Retrieves the invoice group associated with the consolidated billing process. This function supports grouping and identification of the invoices that are to be consolidated or that result from consolidation.
These three documented units operate together: CREATE_CONS_BILL establishes the bill, PROCESS_CONS_BILL_TBL drives the table-level processing, and GET_INVOICE_GROUP supplies the grouping context. The package references the previous consolidated invoice number (consolidated_invoice_number) through the prev_cons_invoice_num field, which ties directly to the user's search term cons_inv_number, referring to the number of the prior consolidated invoice in the OKL consolidated AR header.
Tables Accessed
The package reads and writes contract and billing data across several APPS synonyms:
- OKC_K_HEADERS_B, OKC_K_HEADERS_ALL_B — contract headers, supplying contract identity and number for consolidation.
- OKC_K_LINES_B, OKC_K_ITEMS — contract lines and items that define billable components.
- OKC_LINE_STYLES_B, OKC_RULES_B — line style and rule metadata influencing billing behavior.
- OKL_EXT_SELL_INVS_TL, OKL_XTL_SELL_INVS_TL — external and transferable sell invoice lines that provide the amounts, currency, and customer data.
- OKL_INVOICE_FORMATS_B — invoice format definitions used when generating the consolidated invoice.
- OKL_CNSLD_AR_HDRS_B, OKL_CNSLD_AR_HDRS_TL — consolidated AR invoice headers, including the consolidated invoice number.
- OKL_CNSLD_AR_LINES_B, OKL_CNSLD_AR_LINES_TL — consolidated AR invoice lines.
- OKL_CNSLD_AR_STRMS_B, OKL_CNSLD_AR_STRMS_TL — consolidated AR streams supporting the billing schedules.
Usage Notes
OKL_CONS_BILL is typically invoked from the Contracts consolidated billing flows, including concurrent programs and the consolidated billing forms that drive invoice generation. The commit frequency constant of 1000 indicates that the package is designed for set-based processing of large billing volumes, committing periodically within PROCESS_CONS_BILL_TBL. Because it is referenced by one other package, customizations should account for that dependency. Standard behavior is governed by the OKL_API application constants and the NO_DATA_FOUND, TOO_MANY_ROWS, and OTHERS exception handlers defined in the package, so custom code invoking these procedures should be prepared to handle those standardized error conditions rather than assuming direct table access.
-
PACKAGE: APPS.OKL_CONS_BILL 12.2.2
-
PACKAGE: APPS.OKL_CONS_BILL 12.1.1
-
PACKAGE: APPS.OKL_CONS_BILL 12.2.2
-
PACKAGE: APPS.OKL_CONS_BILL 12.1.1