Search Results calculate_new_line_amount

Overview

The APPS.POS_SCO_TOLERANCE_PVT package is a private (PVT API classification) PL/SQL package that supports Supplier Change Order (SCO) processing and Requester Change Order (RCO) processing within Oracle Purchasing. Its principal business purpose is to evaluate whether proposed changes to a purchase order — such as promise date, unit price, ship quantity, line amount, or document amount — fall within predefined tolerance thresholds. When a change is determined to be within tolerance, the package determines whether the change can be applied automatically according to business rules; when a change falls outside tolerance, the package drives routing of the change request to the requester for review and approval. The package therefore sits at the decision point between automated application of supplier-driven changes and workflow-based requester notification and authorization.

Key Procedures and Functions

The package exposes 26 documented procedures and functions grouped around tolerance evaluation, recalculation, routing, and workflow initiation.

• Tolerance initialization and evaluation: INITIALIZE_TOL_VALUES establishes the tolerance values used during evaluation. PROMISE_DATE_WITHIN_TOL, UNIT_PRICE_WITHIN_TOL, SHIP_QUANTITY_WITHIN_TOL, DOC_AMOUNT_WITHIN_TOL, LINE_AMOUNT_WITHIN_TOL, and SHIP_AMOUNT_WITHIN_TOL each test a specific attribute against its configured tolerance.
• Recalculation: CALCULATE_NEW_DOC_AMOUNT, CALCULATE_NEW_LINE_AMOUNT, and CALCULATE_NEW_SHIP_AMOUNT compute the resulting amounts after a proposed change, supporting downstream comparison against tolerance limits.
• Routing and business rules: ROUTE_TO_REQUESTER and MARK_SCO_FOR_REQ direct change requests to the requester. ROUTE_SCO_BIZ_RULES and AUTO_APP_BIZ_RULES apply the configured business rules that determine whether a change is routed for review or automatically applied.
• Promise date handling: PROMISE_DATE_CHANGE processes changes to the promised delivery date.
• RCO workflow initiation: INITIATE_RCO_FLOW and START_RCO_WORKFLOW (with alternate spellings INITIATERCOFLOW and STARTRCOWORKFLOW) launch the Requester Change Order workflow.
• Diagnostics: LOG_MESSAGE writes messages used for debugging and audit purposes.

Tables Accessed

The package references purchasing and requisitioning tables through APPS synonyms. PO_HEADERS_ALL, PO_LINES_ALL, and PO_LINE_LOCATIONS_ALL (together with their archive counterparts PO_LINES_ARCHIVE_ALL and PO_LINE_LOCATIONS_ARCHIVE_ALL) supply the document, line, and shipment data being evaluated. PO_DISTRIBUTIONS_ALL, PO_RELEASES_ALL, PO_DOCUMENT_TYPES, and PO_ACCEPTANCES support amount calculations, release handling, document typing, and acceptance processing. PO_REQUISITION_HEADERS_ALL, PO_REQUISITION_LINES_ALL, and PO_REQ_DISTRIBUTIONS_ALL link requisition data to the originating requester. PO_CHANGE_REQUESTS stores the change request records that the routing procedures manage, and FND_USER resolves the requester identity for workflow routing. PLITBLM is an Oracle-supplied line table used in bulk operations.

Usage Notes

As a private API, this package is not intended for direct invocation by customer code. It is referenced by the POS_SCO_TOLERANCE_GRP package and by itself, indicating that a public group package wraps its entry points. In Oracle EBS 12.1.1 and 12.2.2, tolerance evaluation and SCO/RCO routing are triggered from the Purchasing application's supplier change order processing — typically through concurrent programs and workflow background processes rather than interactive forms. Customizations should call the corresponding group or public APIs instead of the private package, because private signatures can change between releases. Implementers extending SCO behavior should note that tolerance decisions here govern whether changes bypass requester review, so misconfiguration of tolerance values or business rules can materially alter approval routing.