Search Results delete_fee_type

Overview

OKL_MAINTAIN_FEE_PVT is a private (PVT) PL/SQL package in the APPS schema within Oracle E-Business Suite's Enterprise Contract and Transaction Management (ETRM / Oracle Lease and Finance Management) module. Its business function is to centralize the creation, validation, maintenance, and rollover of fee-related and stream-related data on lease and contract instruments. The package acts as an internal engine used by public contract APIs to establish fee types, payment headers and details, stream type rules, party records, and passthrough/RVI stream processing. Because it is classified as a private API, it is not intended to be called directly by external integrations; instead, it is invoked by the public wrapper package OKL_MAINTAIN_FEE_PVT_W and by numerous other ETRM packages.

Key Procedures and Functions

The documented interface exposes eighteen procedures and functions grouped by functional area:

• Payment header and detail maintenance: CREATE_PAYMENT_HDRS, CREATE_PAYMENT_DTLS, and DELETE_PAYMENT_HDRS manage the payment records associated with fees on a contract.
• Fee type maintenance: CREATE_FEE_TYPE, VALIDATE_FEE_TYPE, UPDATE_FEE_TYPE, and DELETE_FEE_TYPE provide the lifecycle operations for defining and maintaining fee types used across lease transactions.
• Stream type rule processing: CREATE_STRMTP_RUL, UPDATE_STRMTP_RUL, and PROCESS_STRMTP_RUL manage stream type rules that drive how fee amounts translate into payment streams.
• Rollover processing: VALIDATE_ROLLOVER_FEELINE and ROLLOVER_FEE validate and execute the rollover of fee lines when a contract is rebooked or extended.
• Amount allocation and stream processing: ALLOCATE_AMOUNT and PROCESS_RVI_STREAM handle the distribution of fee amounts and the processing of RVI (residual value insurance) streams.
• Party maintenance: CREATE_PARTY, UPDATE_PARTY, and DELETE_PASSTHRU_PARTY manage party roles tied to fees, including passthrough party records.

Tables Accessed

The package operates against core contract and party tables through APPS synonyms. Contract header and line data are read and written through OKC_K_HEADERS_B, OKC_K_HEADERS_ALL_B, OKC_K_LINES_B, OKC_K_ITEMS, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, OKC_RULES_B, and OKC_STATUSES_B. Lease-specific fee and stream data are managed through OKL_K_LINES, OKL_K_PARTY_ROLES, and OKL_TRX_QUOTES_B. Payment information is sourced from OKL_PARTY_PAYMENT_HDR_V and OKL_PARTY_PAYMENT_DTLS_V, and stream type source data from OKL_STRMTYP_SOURCE_V. Party and customer data are resolved via HZ_PARTIES, HZ_CUST_ACCOUNTS, OKX_PARTIES_V, and OKL_K_PARTY_ROLES. Application setup and region metadata are read from AK_REGIONS and AK_REGION_ITEMS. Collectively these reads/writes support fee definition, validation, payment generation, rollover logic, and party assignment.

Usage Notes

OKL_MAINTAIN_FEE_PVT is referenced by twelve other packages, including OKL_CONTRACT_BOOK_PVT, OKL_CONTRACT_REBOOK_PVT, OKL_CREATE_STREAMS_PVT, OKL_DEAL_CHARGES_PVT, OKL_DEAL_TERMS_PVT, OKL_LA_SALES_TAX_PVT, OKL_LA_STREAM_PVT, OKL_OPEN_INTERFACE_PVT, OKL_QA_DATA_INTEGRITY, OKL_QUOTE_TO_CONTRACT_PVT, and OKL_SEC_INVESTOR_PVT, as well as its public wrapper OKL_MAINTAIN_FEE_PVT_W. It is therefore typically invoked indirectly during contract booking, rebooking, quote-to-contract conversion, stream creation, and deal charge/term processing. Custom code should call the public wrapper rather than this private package. Because fee and stream processing follows ETRM's standard API conventions (FND_API and OKL_API/OKC_API error handling), callers should expect the standard API return status pattern and should not bypass validation routines such as VALIDATE_FEE_TYPE or VALIDATE_ROLLOVER_FEELINE.