Search Results import_responses




Overview
Explore in AI Chat

Overview

The APPS.BIM_RESPONSE_IMPORT_PUB package is a public PL/SQL API within the Oracle E-Business Suite Business Intelligence/Advanced Marketing (BIM) module. Its principal business function is to import survey and campaign response data collected in external or staging systems into the EBS interface tables that feed the marketing response processing pipeline. The package acts as the inbound gateway for response records — translating source-coded response header, grade, and invalid-reason information into the validated staging structures that downstream concurrent programs consume to create permanent response records.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking schema rather than the defining schema, and the header comment ($Header: bimpmris.pls 120.1 2005/06/14 ...) indicates the package originated in the early 12.x code line and remained largely stable through 12.1.1 and 12.2.2. Its API classification is PUB, confirming it is intended to be called directly by external components, concurrent programs, or custom code rather than being restricted to internal package use.

Key Procedures and Functions

The ETRM metadata documents a single public procedure:

  • IMPORT_RESPONSES — The sole documented entry point. Although the source excerpt labels the API type as "Private" in the internal comment block, ETRM classifies the package as PUB and exposes this procedure as the supported interface. It accepts a standard EBS API parameter preamble (API version number, initialization message list flag, commit flag, and validation level) together with an interface header identifier and a response header record. Its behaviour is to read staged response data identified by the interface header, validate it against the grading, reason, and source-code reference data, and orchestrate insertion into the response interface tables. Two named record types support the interface: response_hdr_rec_type (carrying source code, response country, create date, source, landing-pad hits, and survey-completed indicators) and the grade/invalid-reason collection types used for aggregate response reporting.

Tables Accessed

The package reads and writes the following tables through APPS synonyms:

  • BIM_R_RESP_INT_HEADER and BIM_R_RESP_INT_HEADER_S — the response interface header and its sequence, holding the parent response record created or updated by the import.
  • BIM_R_RESP_INT_GRADES and BIM_R_RESP_INT_GRADES_S — interface grade lines, populated with per-grade response counts supplied by the caller.
  • BIM_R_RESP_INT_REASON and BIM_R_RESP_INT_REASON_S — interface records capturing invalid responses and their associated reasons.
  • AMS_SOURCE_CODES — source-code reference data used to validate the source_code value on the incoming response header.
  • JTF_LOC_HIERARCHIES_B — territory/location hierarchy base table, consulted for geographic validation of the response country.
  • DUAL and PLITBLM — utility objects; the latter is the standard EBS PL/SQL table-to-message conversion package used by the API message-handling framework.

Usage Notes

BIM_RESPONSE_IMPORT_PUB.IMPORT_RESPONSES is typically invoked from a concurrent program or from custom PL/SQL integration code that has already populated the BIM response interface tables from an external survey tool, call-centre feed, or third-party marketing platform. Callers are expected to follow the standard EBS API conventions: pass p_init_msg_list as FND_API.G_TRUE when a fresh message stack is required, set p_commit according to transaction control requirements, and choose an appropriate p_validation_level — the default full validation enforces reference-data checks against AMS_SOURCE_CODES and the location hierarchy.

The interface header identifier (p_interface_header_id) or the response header record must identify the staged batch to be imported. ETRM records no dependent packages referencing this API, so it is consumed directly rather than nested within another public package. Because the API does not itself submit the downstream response-import concurrent program, integrations that require the validated interface rows to be converted into permanent responses must invoke that program separately after a successful call.