Search Results ar_credit_memo_api_pub_w




Overview
Explore in AI Chat

Overview

APPS.AR_CREDIT_MEMO_API_PUB_W is a public wrapper package in the Oracle E-Business Suite Receivables (AR) module. It provides an interface layer through which external and internal callers can invoke credit memo creation and maintenance logic that is otherwise encapsulated in the underlying API package, AR_CREDIT_MEMO_API_PUB. As its name indicates, the "_W" suffix denotes a wrapper, and the "_PUB" element signifies that the package is intended for public consumption rather than private, internal use.

The package is classified as OTHER in the ETRM metadata and holds a VALID status in the APPS schema. It is a documented component of ETRM 12.2.2 and remains a valid object across the 12.1.1 and 12.2.2 releases. The principal business function it serves is to support programmatic creation and processing of credit memos in Oracle Receivables, allowing credit transactions to be generated without direct user interaction through the Receivables forms.

The wrapper design follows the standard Oracle EBS pattern of separating the publishing interface from the implementation body. This permits Oracle to revise the internal API while preserving a stable public signature for external integrations.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P6 — A Rosetta-style table copy procedure that transfers inbound tabular data into the package's PL/SQL structures. The "P6" designation identifies the specific parameter profile or version of the copy operation. It is typically used to stage input values prior to processing.
  • ROSETTA_TABLE_COPY_OUT_P6 — Performs the outbound counterpart to the P6 copy-in routine, copying data from PL/SQL structures back to the caller's table-based parameters. Used to return results or processed collections to the invoking program.
  • ROSETTA_TABLE_COPY_IN_P9 — An inbound table copy procedure parallel to the P6 variant but using the alternate "P9" parameter profile, offering a different shape or set of input collections.
  • ROSETTA_TABLE_COPY_OUT_P9 — The outbound counterpart for the P9 profile, returning processed data collections to the caller.
  • CREATE_REQUEST — The primary functional entry point exposed by this wrapper. It initiates a credit memo request, channeling the caller's input through validation and into the underlying AR_CREDIT_MEMO_API_PUB logic. This procedure is the conventional invocation point for creating credit memos programmatically.

Tables Accessed

According to the documented metadata, the package references the APPS synonym PLITBLM. PLITBLM is one of the standard Oracle EBS PL/SQL index-by tables used to carry multi-row parameter data between caller and callee; it is consistent with the Rosetta table-copy procedures identified above. The dependency listing additionally references AR_CREDIT_MEMO_API_PUB, along with the JTF collection types JTF_DATE_TABLE, JTF_NUMBER_TABLE, JTF_VARCHAR2_TABLE_100, JTF_VARCHAR2_TABLE_200, JTF_VARCHAR2_TABLE_400, and JTF_VARCHAR2_TABLE_2000. These JTF types supply the typed PL/SQL collections used to hold dates, numbers, and strings across the API boundary.

Usage Notes

APPS.AR_CREDIT_MEMO_API_PUB_W is normally invoked as a programmatic interface rather than from a standard Oracle Receivables form or seeded concurrent program. Custom PL/SQL code, external integrations, and interface programs call its CREATE_REQUEST procedure when credit memos must be generated as part of an automated business process, such as refund processing or invoice adjustment. The Rosetta copy-in and copy-out procedures are used to marshal bulk collection parameters into and out of the package when large volumes of records are processed.

Because the package is documented as referenced by zero other packages, it functions as a leaf-level public interface, sitting between external callers and the internal AR_CREDIT_MEMO_API_PUB implementation. Callers should supply correctly typed JTF collections and expect that validation, defaults, and transactional logic are handled downstream by the underlying API.