Search Results update_sll_amount

Overview

OKS_BILL_SCH is the service contracts billing schedule engine within Oracle E-Business Suite. It belongs to the OKS (Service Contracts) application and is owned by APPS, with an API classification of OTHER in the ETRM 12.2.2 repository. The package encapsulates the business logic that creates, maintains, cascades, and terminates billing schedules for service contracts and subscriptions, including the line-level and subline-level revenue and price allocation records that drive invoicing. It operates against the service contracts data model (OKS_K_HEADERS_B, OKS_K_LINES_B, OKS_BILL_SUB_LINES) and the contracting core tables (OKC_K_HEADERS_B, OKC_K_LINES_B). Because billing schedule generation must remain consistent with order management data, the package also touches OE_ORDER_LINES_ALL through a documented synonym. The package exposes 25 documented procedures and functions and is referenced by 18 other packages, which places it centrally in the service contracts billing call graph. Standard logging and message-handling constants are inherited from OKC_API, and runtime diagnostics use the FND_LOG hierarchy through the module identifier oks.plsql.oks_bill_sch.

Key Procedures and Functions

The documented entry points group into schedule creation, schedule maintenance, amount recalculation, date cascading, and deletion.

• CREATE_HDR_SCHEDULE, CREATE_HEADER_BILL_SCH, CREATE_BILL_SCH_RULES, CREATE_BILL_SCH_CP, and CREATE_SUBCRIPTION_BS build header-level schedules, schedule rules, and subscription billing schedules.
• COPY_BILL_SCH and ADJUST_REPLACE_PRODUCT_BS replicate or adjust schedules when contracts are copied or products are replaced.
• UPDATE_SLL_AMOUNT, CAL_HDR_SLL_AMOUNT, and CAL_SLLID_AMOUNT recalculate subline-level amounts at the schedule, header, and line identifier levels.
• CASCADE_DATES_SLL and CASCADE_DT_LINES_SLL propagate changed dates down to subline records; UPDATE_OM_SLL_DATE and UPDATE_BS_ENDDATE and UPDATE_BS_INTERFACE_DATE synchronize dates back to order management and the billing interface.
• DEL_RUL_ELEMENTS, DEL_SUBLINE_LVL_RULE, and DELETE_CONTRACT_BS_SLL remove rule elements, subline-level rules, and contract billing schedule sublines. The user search term del_subline_lvl_rule resolves to the documented procedure DEL_SUBLINE_LVL_RULE, which deletes subline-level billing schedule rules.
• TERMINATE_BILL_SCH and PREVIEW_SUBSCRIPTION_BS support termination processing and schedule preview.

Tables Accessed

The package reads and writes the service contracts base tables OKS_K_HEADERS_B, OKS_K_LINES_B, OKS_SUBSCR_HEADER_B, and OKS_SUBSCR_ELEMENTS, and the billing detail tables OKS_BILL_CONT_LINES and OKS_BILL_SUB_LINES, which hold contract and subline billing records. Schedule structure is stored in OKS_STREAM_LEVELS_B and OKS_LEVEL_ELEMENTS, and attribute-level rule data in OKS_LEVEL_ELEMENTS and OKS_SUBSCR_ELEMENTS. Contracting core data is read from OKC_K_HEADERS_ALL_B, OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, and OKC_K_REL_OBJS, which provide contract header, line, item, and relationship context. OE_ORDER_LINES_ALL supplies sales order line dates and identifiers used when synchronizing billing dates back to order management. DUAL is used for single-row computations.

Usage Notes

OKS_BILL_SCH is primarily invoked indirectly rather than from end-user forms directly. Service Contracts forms and concurrent programs that generate or regenerate billing schedules call into this package, and the 18 dependent packages confirm it is a shared internal API layer. Custom extensions should call the documented procedures rather than updating OKS_BILL_SUB_LINES or OKS_BILL_CONT_LINES directly, because date cascading, amount recalculation, and order management synchronization are coordinated inside these routines. Date-sensitive operations such as UPDATE_OM_SLL_DATE and UPDATE_BS_INTERFACE_DATE should be executed in the same transaction as the corresponding order management change to preserve consistency. Because message constants are inherited from OKC_API, callers should interpret return statuses using the OKC_API success, error, and unexpected-error flags, and review FND_LOG output under the oks.plsql.oks_bill_sch module when diagnosing failures.