Search Results g_request_mode




Overview
Explore in AI Chat

Overview

OZF_CLAIM_UTILITY_PVT is a private PL/SQL package in the APPS schema that provides shared utility logic for the Oracle E-Business Suite Trade Management (formerly Oracle Field Sales/Advanced Pricing) claims subsystem. Its unit comment header identifies a significant revision, "Rule Based Settlement Enhancement" (20-May-2009, KPATRO), which introduced the rule-driven claim settlement flow that the package now supports. The package is declared with AUTHID CURRENT_USER and is classified as a private (PVT) API, meaning it is not intended as a published interface for external consumers; it is instead invoked by other packages within the OZF claim module. The package defines two associative array record types, ozf_rule_match_rec_type and ozf_accrual_match_rec_type, together with their table types, which are used to cache matched claim-to-credit-memo and claim-to-accrual relationships during settlement processing. Package-level constants G_AUTO_MODE, G_MANU_MODE, and G_REQUEST_MODE distinguish the settlement invocation paths, and G_DEFAULT_NUM_REC_FETCH (30) sets the default bulk fetch size.

Key Procedures and Functions

The package exposes five documented procedures and functions:

  • CHECK_CLAIM_ACCESS — Validates whether a given user has access to a specific claim object. It accepts API-standard parameters (API version, initialization of the message list, commit flag, and validation level) along with an object identifier, object type, and user identifier, and returns a standard return status, message count, message data, and an x_access indicator showing whether access is permitted. This is the only procedure in the package whose signature is fully visible in the provided source excerpt.
  • NORMALIZE_CUSTOMER_REFERENCE — Standardizes a customer reference value so that claims and credit transactions can be matched consistently, typically resolving free-form or legacy customer identifiers against the trading partner model.
  • NORMALIZE_CREDIT_REFERENCE — Performs the equivalent normalization for credit-side references (such as credit memo numbers), enabling reliable association between a claim and its corresponding receivables transaction.
  • START_RULE_BASED_SETTLEMENT — Initiates the rule-based settlement process introduced by the 2009 enhancement, driving the matching of claims to credits and accruals according to configured settlement rules.
  • CREATE_LOG — Writes entries to the rule-based settlement log, capturing processing outcomes and diagnostics for auditing and troubleshooting settlement activity.

Tables Accessed

The package reads and writes across the claims, offers, receivables, and trading partner schemas via APPS synonyms. Claim data is held in OZF_CLAIMS_ALL, OZF_CLAIM_LINES_ALL, and OZF_CLAIM_LINES_UTIL_ALL, while offer and promotion configuration is read from OZF_OFFERS. Settlement logging is persisted in OZF_RULE_BASED_LOG and its sequence OZF_RULE_BASED_LOG_S, consistent with the CREATE_LOG procedure. System behavior is parameterized through OZF_SYS_PARAMETERS_ALL. Credit-side matching draws on RA_CUSTOMER_TRX_ALL and RA_CUST_TRX_TYPES_ALL, with payment terms information from AR_PAYMENT_SCHEDULES_ALL. Customer and site resolution uses HZ_CUST_ACCT_RELATE_ALL, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL. PLITBLM is referenced as a PL/SQL table-based bulk collection type used internally for set-based processing.

Usage Notes

As a PVT package, OZF_CLAIM_UTILITY_PVT is not called directly from forms or concurrent programs; it is invoked by the public claim APIs and by the fourteen other packages that reference it. In a 12.1.1 or 12.2.2 environment, the settlement logic is typically triggered through the Trade Management claim settlement concurrent program or the claim entry/approval forms, which in turn call the public wrapper that delegates to START_RULE_BASED_SETTLEMENT. The presence of the AUTO, MANU, and REQUEST mode constants indicates the settlement routine behaves differently depending on whether it is driven by an automated concurrent process, a manual user action, or an explicit request. Customizations should not call this package directly, since its signature is not guaranteed across patches; instead, extensions should use the corresponding public OZF APIs. Troubleshooting rule-based settlement issues is normally performed by querying OZF_RULE_BASED_LOG for the entries written by CREATE_LOG.