Search Results oks_arfeeder_pub




Overview
Explore in AI Chat

Overview

AR_INTERFACESALESCREDITS_GRP is a public PL/SQL package in the APPS schema that supports the Receivables (AR) AutoInvoice sales credit interface. It provides the programmatic entry point for loading sales-credit line records into the Oracle Receivables interface tables, from where the AutoInvoice process subsequently validates and transfers them into the production receivable tables. The object is classified as a Group (GRP) package, indicating that its procedures encapsulate a related set of operations on the AR interface sales-credit entity rather than exposing a fully granular, single-purpose API.

In the broader Order-to-Cash integration flow, sales credits represent the revenue allocation among salespersons or other credit recipients associated with an invoice line. External systems producing invoice data — order capture, order fulfillment, or third-party applications — must place these allocations in the interface layer before AutoInvoice can consume them. AR_INTERFACESALESCREDITS_GRP serves this role by isolating the insert logic and the associated Receivable Applications relationship in one callable unit.

Key Procedures and Functions

The documented interface exposes a single procedure:

  • INSERT_SALESCREDIT — Inserts sales-credit records for the Receivables AutoInvoice interface. This procedure encapsulates the write operation that moves sales-credit data into the AR interface tables, and it is the routine invoked by external feeder programs when they require a supported, packaged method of loading sales credits rather than a direct, unsupported insert.

No additional documented procedures or functions are recorded for this package. Parameter lists are not published in the ETRM metadata and are deliberately not reproduced here; callers should obtain the exact signature from the installed package specification in the target environment, as the specification is the authoritative source for argument order, defaults, and data types.

Tables Accessed

The package operates against the following tables through APPS synonyms:

  • RA_INTERFACE_SALESCREDITS_ALL — The AutoInvoice interface table that holds sales-credit allocations awaiting validation and import. INSERT_SALESCREDIT writes rows into this table, forming the staging data that AutoInvoice later processes.
  • AR_RECEIVABLE_APPLICATIONS — The Receivables applications table. The package's dependency on this table reflects the linkage between sales credits and the receivable application records against which they are associated, ensuring the inserted interface data remains consistent with the receivable side of the transaction.

Reads and writes against these objects occur in the context of the caller's transaction; the package does not itself commit, so transaction control remains with the calling program.

Usage Notes

AR_INTERFACESALESCREDITS_GRP is not a standalone concurrent program. It is invoked programmatically by other packages that build the AutoInvoice interface. The documented reference chain confirms this: the package is referenced by OE_INVOICE_PUB, the Order Management invoicing public API, and by OKS_ARFEEDER_PUB, the Service Contracts (OKS) AR feeder that pushes contract-related invoice and sales-credit data into Receivables. This makes the package relevant whenever teleservice or service contract billing requires sales-credit distributions to accompany generated invoices.

The user query term "oks_arfeeder_pub" reflects this exact caller relationship: OKS_ARFEEDER_PUB is the module most commonly associated with invocations of this sales-credit insert routine in a service-contracts implementation. The package is also self-referencing, indicating internal procedure calls within the package body.

Typical invocation contexts include:

  • Order Management invoice generation through OE_INVOICE_PUB when sales credits must be passed to Receivables.
  • Service Contracts AR feeder processing via OKS_ARFEEDER_PUB for contract and subscription billing.
  • Custom feeder programs that follow the supported path for loading sales credits instead of inserting directly into RA_INTERFACE_SALESCREDITS_ALL.

Because the object status is VALID and owned by APPS, it should be invoked with the standard APPS initialization (FND_GLOBAL.APPS_INITIALIZE) to establish a valid application and user context. Callers remain responsible for committing or rolling back, and for ensuring that a corresponding AutoInvoice run is executed to import the staged sales credits.