Search Results do_store_financial_report

Overview

APPS.HZ_MAP_PARTY_PUB is a public PL/SQL API package within the Oracle E-Business Suite Trading Community Architecture (TCA) and Receivables (AR) module. Its principal business function is to reconcile, map, and store party-related data held in the TCA party interface staging tables into the master TCA registry tables. The package functions as the persistence and mapping engine for bulk party import and enrichment processes, taking records that have been loaded into HZ_PARTY_INTERFACE and transforming them into fully formed parties, organization profiles, party sites, contact points, credit ratings, financial reports, financial numbers, party relationships, business reports, locations, and classifications. The header comment (ARHMAPSS.pls 120.5) confirms its lineage within the Receivables party mapping subsystem.

Key Procedures and Functions

The package exposes twelve documented procedures, each responsible for persisting a discrete TCA entity. Parameter lists are intentionally omitted; the purposes are as follows:

• MAP — The primary driver procedure. It accepts an API version, initialization and commit flags, a group identifier, an inactivation flag, and a validation level, and orchestrates the mapping of a batch of interface records into the TCA registry, returning standard return status, message count, and message data.
• MAP_CONC_WRAPPER — A concurrent-program wrapper around MAP, exposing the standard concurrent manager errbuf/retcode interface plus the group identifier.
• STORE_ORG — Stores organization party data using the HZ_PARTY_V2PUB organization record type and returns an organization profile identifier.
• STORE_PARTY_SITE — Persists party site records using the HZ_PARTY_SITE_V2PUB party site record type.
• STORE_CONTACT_POINT — Stores contact point records (such as phone and email) using the HZ_CONTACT_POINT_V2PUB contact point and phone record types. This is the procedure associated with the search term store_contact_point.
• STORE_CREDIT_RATINGS — Persists credit rating records via the HZ_PARTY_INFO_V2PUB credit rating record type.
• DO_STORE_FINANCIAL_REPORT — Stores financial report records using the HZ_ORGANIZATION_INFO_V2PUB financial report record type and returns the new report identifier.
• DO_STORE_FINANCIAL_NUMBER — Stores financial number records (for example, DUNS numbers) associated with a party.
• STORE_PARTY_REL — Persists party relationship records between TCA parties.
• STORE_BUSINESS_REPORT — Stores business report data associated with organization parties.
• DO_STORE_LOCATION — Persists location records into the TCA location model.
• STORE_CLASSIFICATION — Stores classification (code assignment) records linking parties to TCA classification codes.

Tables Accessed

The package operates against an extensive set of TCA tables referenced through APPS synonyms. HZ_PARTY_INTERFACE is the primary source staging table read during mapping, with HZ_PARTY_INTERFACE_ERRORS (and its _S sequence) used to log validation and processing failures. Master entity tables written include HZ_PARTIES, HZ_ORGANIZATION_PROFILES, HZ_CONTACT_POINTS, HZ_LOCATIONS, HZ_CREDIT_RATINGS, HZ_FINANCIAL_REPORTS, HZ_FINANCIAL_NUMBERS, HZ_CODE_ASSIGNMENTS (classifications), and HZ_ORIG_SYS_REFERENCES (source-system cross references). The DUNS-related tables HZ_DNB_REQUEST_LOG and HZ_DNB_REQUEST_LOG_S support credit and D&B enrichment, while FND_CURRENCIES provides currency validation and conversion context for financial data.

Usage Notes

HZ_MAP_PARTY_PUB is typically invoked in two modes. In batch mode, the MAP_CONC_WRAPPER procedure is registered as a concurrent program, allowing scheduled or on-demand mapping of party batches identified by a group identifier. In programmatic mode, custom PL/SQL and integration code call the individual STORE_* and DO_STORE_* procedures directly to persist specific entities. The package is a public API (classification PUB) owned by APPS, and it is not referenced by any other documented package, meaning it is intended to be called from external processes, concurrent programs, or TCA-related forms rather than from within the TCA package hierarchy itself. Callers should supply the appropriate API version and validation level, and must inspect the returned x_return_status, message count, and message data to handle errors, with interface-level failures captured in HZ_PARTY_INTERFACE_ERRORS.