Search Results ozf_sd_no_response

Overview

OZF_SD_UTIL_PVT is an Oracle EBS Trade Management (formerly Oracle Channel Revenue Management, and historically Oracle Sales and Distribution/Claims) private utility package belonging to the APPS schema. In EBS 12.1.1 and 12.2.2 it underpins the deduction and supplier claims settlement workflow captured in the OZF_SD_* schema, where "SD" denotes Sales Deduction activity such as claim batches, batch lines, disputes, and postback processing. The package is classified as PVT (private), which means it is not a formally published public API; it is a supporting library of internal routines invoked by other OZF packages, workflows, and concurrent programs rather than by external integrations. Its header identifies the deployed source file as ozfvsdub.pls (version 120.17, dated 2008/05/02), confirming that the same foundational logic has been carried forward from the 11i heritage codebase into the 12.1.1 and 12.2.2 releases with minimal change. The package assembles a broad set of utility operations: currency conversion against utilization and batch records, date and timezone normalization between the R12 (RN) model and legacy database representations, stale request data cleanup, request price updates, batch adjustment and claim creation, penalty batch closure, event raising, and completion flag management.

Key Procedures and Functions

The package exposes sixteen documented procedures and functions that fall into several functional clusters.

• Currency handling: SD_CONVERT_CURRENCY derives the source currency from OZF_SD_BATCH_LINES_ALL and the target currency from the batch header, then calls OZF_UTILITY_PVT.Convert_Currency to translate a batch line amount. GET_CONVERTED_CURRENCY provides a related conversion retrieval helper.
• Amount and settlement processing: SD_AMOUNT_POSTBACK reads utilization, claim, accounted, and universal currency remaining amounts for a batch line, supporting the postback of claim balances. PROCESS_BATCH_ADJUST_CLAIM and CREATE_ADJUSTMENT drive adjustment creation against supplier deduction batches, while PROCESS_SD_PEN_CLOSE_BATCHES closes penalty-related batches.
• Date and timezone utilities: CONVERT_TO_RN_DATE, CONVERT_TO_DB_DATE, CONVERT_TO_RN_TIMEZONE, and CONVERT_TO_RN_DATETIME normalize date and timestamp values between the RN (Release 12 native) representation and legacy database storage conventions.
• Request and response processing: PROCESS_SD_RESPONSE processes deduction response records, UPDATE_SD_REQ_PRICES refreshes request pricing, and UPDATE_SD_REQ_STALE_DATA clears or corrects obsolete request rows.
• Flow control and messaging: SD_RAISE_EVENT publishes a business event for the deduction workflow, while SET_COMPLETE_FLAGS and CHECK_COMPLETE_FLAGS maintain and evaluate completeness indicators on batch or request entities.

Tables Accessed

The package reads and writes the core deduction data model through APPS synonyms.

• OZF_SD_BATCH_HEADERS_ALL, OZF_SD_BATCH_LINES_ALL, OZF_SD_BATCH_LINE_DISPUTES: batch header, line, and dispute records that carry claim amounts, currencies, and batch identifiers.
• OZF_FUNDS_UTILIZED_ALL_B: the utilization source providing currency codes, exchange rate dates, and remaining amount balances.
• OZF_SD_REQUEST_HEADERS_ALL_B and OZF_SD_REQUEST_LINES_ALL: supplier deduction request headers and lines updated by the request maintenance routines.
• OZF_SD_RES_HEADER_INTF, OZF_SD_RES_PROD_INTF, OZF_SD_RES_DIST_PRICES_INTF, OZF_SD_RES_CUST_INTF: the results interface tables used when response or adjustment data is staged for import.
• AMS_USER_STATUSES_B, FND_CURRENCIES, FND_NEW_MESSAGES, FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_REQUESTS: supporting lookups for statuses and currencies, message retrieval for raised events, and concurrent program/request context used during background processing.

Usage Notes

Because OZF_SD_UTIL_PVT is a private package, it should not be called directly from external interfaces; Oracle does not guarantee its signature across patches. It is typically invoked from the OZF Sales Deduction forms, from concurrent programs that process deduction batches and supplier responses, from the deduction workflow through SD_RAISE_EVENT, and from the two other APPS packages documented as referencing it. The "ozf_sd_no_response" search term relates to the deduction response lifecycle that this package supports — specifically the logic around PROCESS_SD_RESPONSE, SD_RAISE_EVENT, and the completeness flag routines, which together determine when a supplier deduction or claim has received no response and trigger follow-up or stale-data handling. Debug behavior is influenced by the CLN_DEBUG_LEVEL profile option referenced in the package header. Any customization should invoke the public deduction APIs instead, leaving this utility package to Oracle-supplied code paths.