Search Results get_supplier_name
Overview
The APPS.JA_CN_AP_VALIDATION_PKG package body is a China localization (JA_CN) module that supports the validation of Oracle Payables transactions against legal entity and balance segment value assignment rules. Its primary business purpose is to identify and validate Payables transactions that fail one of two conditions defined in the package header: transactions in which the operating legal entity differs from the legal entity associated with the Balance Segment Value assigned to that Payables transaction, and transactions that have not been itemized. The package operates in the context of Oracle E-Business Suite 12.1.1 and 12.2.2, where multi-organization and Subledger Accounting (SLA) architectures require that Payables activity be reconciled to the correct ledger and legal entity structure.
The package source header identifies the file as JACNAPVB.pls (version 120.1) and records its creation on 13-Apr-2010 by Chaoqun Wu, with a subsequent update on 26-May-2010 to address bug 9763810. This history indicates the package was introduced to satisfy China statutory reporting and reconciliation requirements around legal entity and balance segment assignment.
Key Procedures and Functions
The documented package exposes one public procedure: Validate_Payables. This procedure is the validation driver for the package, responsible for evaluating Payables transactions against the two validation rules described above — legal entity consistency with the Balance Segment Value, and itemization status. It operates upon the ledger, legal entity, and Subledger Accounting structures that are queried through the tables listed below.
In addition to the documented procedure, the package body contains a private helper function, Get_Supplier_Name, which is relevant to users searching on that term. Per the package comments, its purpose is "to get supplier name, including customer name from AR Refund." It accepts a supplier name and identifiers for the accounting event header and ledger, and returns the resolved supplier name as a VARCHAR2 value. The function initializes a local variable with the passed-in supplier name, sets a procedure name constant for debugging, and references a debug level variable, reflecting the package's internal instrumentation conventions. Because this function is not listed among the documented procedures in ETRM, it should be treated as an internal utility rather than a supported public API entry point.
Tables Accessed
The package reads and/or writes the following tables via APPS synonyms. Payables tables — AP_CHECKS_ALL, AP_INVOICES_ALL, and AP_INVOICE_PAYMENTS_ALL — supply check, invoice, and payment transaction data for validation. AP_SUPPLIERS provides supplier identification, supporting the Get_Supplier_Name logic. General Ledger tables — GL_IMPORT_REFERENCES, GL_JE_HEADERS, GL_JE_LINES, GL_LEDGERS, GL_LEDGER_NORM_SEG_VALS, and GL_PERIODS — provide journal, ledger, period, and normalized segment value context, including the Balance Segment Value used in the legal entity comparison. HZ_CUST_ACCOUNTS and HZ_PARTIES provide customer/party data for AR Refund scenarios referenced by Get_Supplier_Name. The localization table JA_CN_LEDGER_LE_BSV_GT stores China-specific ledger, legal entity, and balance segment value mapping used to enforce rule one. Finally, Subledger Accounting tables XLA_AE_HEADERS and XLA_AE_LINES correlate accounting events with the underlying Payables transactions and their ledger context.
Usage Notes
Given its classification as OTHER and its zero inbound package references, JA_CN_AP_VALIDATION_PKG is not a general-purpose API used by other PL/SQL packages. It is most plausibly invoked by a concurrent program that produces a China Payables validation report, consistent with the package header's statement that the "Validation report includes transaction as below." The report output drives correction of transactions where legal entity and balance segment assignment disagree, or where itemization is incomplete, both of which affect China statutory reporting accuracy. The Get_Supplier_Name function supports report rendering by resolving supplier or AR refund customer names on validated transactions.
- Invoke through its associated concurrent program for reporting; do not call
Validate_Payablesdirectly from custom code without confirming supported signatures. - Treat
Get_Supplier_Nameas an internal function; it is not documented in ETRM and has no guaranteed external interface. - Dependencies include XLA and GL tables, so results depend on Subledger Accounting and ledger setup being current.
- Applicable to Chinese localization ledgers only; the
JA_CN_LEDGER_LE_BSV_GTmapping table is required for rule one evaluation.
-
PACKAGE BODY: APPS.JA_CN_AP_VALIDATION_PKG
12.2.2
-
PACKAGE BODY: APPS.AHL_DI_DOC_INDEX_PVT
12.1.1
-
PACKAGE BODY: APPS.AHL_DI_DOC_INDEX_PVT
12.2.2
-
PACKAGE: APPS.MSC_ATP_FUNC
12.2.2
-
PACKAGE: APPS.MSC_ATP_FUNC
12.1.1
-
PACKAGE: APPS.POR_VIEW_REQS_PKG
12.1.1
-
PACKAGE BODY: APPS.POS_SPM_WF_PKG1
12.1.1
-
PACKAGE: APPS.POR_VIEW_REQS_PKG
12.2.2
-
PACKAGE BODY: APPS.POS_SPM_WF_PKG1
12.2.2
-
PACKAGE BODY: APPS.POR_VIEW_REQS_PKG
12.1.1
-
PACKAGE: APPS.PA_PLANNING_RESOURCE_UTILS
12.1.1
-
PACKAGE: APPS.PA_PLANNING_RESOURCE_UTILS
12.2.2
-
PACKAGE BODY: APPS.POR_VIEW_REQS_PKG
12.2.2
-
PACKAGE BODY: APPS.MSC_ATP_FUNC
12.1.1
-
PACKAGE: APPS.PA_PLANNING_ELEMENT_UTILS
12.1.1
-
PACKAGE BODY: APPS.MSC_ATP_FUNC
12.2.2
-
PACKAGE: APPS.PA_PLANNING_ELEMENT_UTILS
12.2.2
-
PACKAGE BODY: APPS.WSH_VENDOR_PARTY_MERGE_PKG
12.1.1
-
APPS.JMF_SHIKYU_AUTO_RCV_PROC dependencies on PO_VENDORS
12.1.1
-
APPS.POS_SPM_WF_PKG1 dependencies on WF_PROCESS_ACTIVITIES
12.1.1
-
APPS.JMF_SHIKYU_AUTO_RCV_PROC dependencies on PO_VENDORS
12.2.2
-
APPS.JMF_SHIKYU_AUTO_RCV_PROC dependencies on PO_VENDOR_SITES_ALL
12.2.2
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PO_VENDORS
12.2.2
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ASSIGNMENTS
12.2.2
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PO_VENDORS
12.1.1
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ROLE_TYPES_B
12.1.1
-
APPS.POS_SPM_WF_PKG1 dependencies on WF_PROCESS_ACTIVITIES
12.2.2
-
APPS.JMF_SHIKYU_AUTO_RCV_PROC dependencies on PO_VENDOR_SITES_ALL
12.1.1
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ASSIGNMENTS
12.1.1
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ROLE_TYPES_B
12.2.2
-
APPS.POS_SPM_WF_PKG1 dependencies on FND_LOOKUP_VALUES
12.2.2
-
APPS.POS_SPM_WF_PKG1 dependencies on POS_VENDOR_UTIL_PKG
12.1.1
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ASSIGNMENTS
12.1.1
-
APPS.POS_SPM_WF_PKG1 dependencies on POS_VENDOR_UTIL_PKG
12.2.2
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PA_PROJECT_ASSIGNMENTS
12.2.2
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PO_VENDORS
12.1.1
-
APPS.WSH_VENDOR_PARTY_MERGE_PKG dependencies on FND_MESSAGE
12.1.1
-
APPS.PA_PLANNING_ELEMENT_UTILS dependencies on PO_VENDORS
12.2.2
-
APPS.POS_SPM_WF_PKG1 dependencies on FND_LOOKUP_VALUES
12.1.1
-
APPS.JA_CN_AP_VALIDATION_PKG dependencies on FND_LOG
12.2.2
-
PACKAGE: APPS.QA_PLAN_ELEMENT_API
12.1.1
-
APPS.WSH_VENDOR_PARTY_MERGE_PKG dependencies on PO_VENDORS
12.1.1
-
APPS.WSH_VENDOR_PARTY_MERGE_PKG dependencies on FND_MESSAGE
12.2.2
-
APPS.WSH_VENDOR_PARTY_MERGE_PKG dependencies on PO_VENDORS
12.2.2
-
PACKAGE BODY: APPS.WSH_VENDOR_PARTY_MERGE_PKG
12.2.2
-
PACKAGE: APPS.QA_PLAN_ELEMENT_API
12.2.2
-
APPS.PA_PLANNING_RESOURCE_UTILS dependencies on FND_MSG_PUB
12.2.2
-
APPS.PA_PLANNING_RESOURCE_UTILS dependencies on FND_MSG_PUB
12.1.1
-
APPS.JA_CN_AP_VALIDATION_PKG dependencies on DUAL
12.2.2
-
APPS.POR_VIEW_REQS_PKG dependencies on PO_REQUISITION_LINES_ALL
12.2.2