Search Results bim_src_code_details_pkg




Overview

BIM_SRC_CODE_DETAILS_PKG is a concurrent program registered within the Oracle E-Business Suite under the BIM – Marketing Intelligence product family. The acronym "BIM" denotes the Marketing Intelligence module, historically positioned in the EBS application stack as a supporting component of the Oracle Marketing and Trade Management footprint. The program is classified as a collection program, meaning its primary purpose is to gather source code detail records and populate the corresponding staging structures consumed by downstream marketing intelligence processes. The concurrent program bears the same user-facing name as its underlying PL/SQL package, BIM_SRC_CODE_DETAILS_PKG, and its documented description identifies it simply as the "BIM_SRC_CODE_DETAILS_PKG Concurrent Program." The metadata provided in the ETRM 12.1.1 / 12.2.2 reference records the program as belonging to an obsolete product designation, and the program itself is flagged as Enabled: No, indicating that it is registered in the concurrent program definitions but is not active in the current release.

Execution Details

The documented execution method is PL/SQL Stored Procedure, with a Standard argument method. The executable record carries the user name "BIM_SRC_CODE_DETAILS_PKG executable" and the description "Executable for BIM_SRC_CODE_DETAILS_PKG collection program." The execution filename is specified as BIM_SRC_CODE_DETAILS_PKG.Populate, signifying that the procedure invoked at run time is the Populate routine within the package. The subroutine name field is documented as blank. Together, these attributes confirm that when the program is submitted, the concurrent manager invokes BIM_SRC_CODE_DETAILS_PKG.Populate directly as a stored program unit rather than through a host script or Java executable.

Execution Filename: BIM_SRC_CODE_DETAILS_PKG.Populate
Subroutine Name: (none)
Execution Method: PL/SQL Stored Procedure
Argument Method: Standard

How to Run

Because the argument method is Standard, the program is designed to be submitted through the Oracle EBS Standard Request Submission (SRS) interface, typically navigated as Submit Requests from the application responsibility menu. Three parameters are documented in the request set argument definition, each associated with the token assignment $SRS$.BIM_SRC_CODE_DETAILS_PKG and each marked as displayable, insertable, and updatable, with no default type or default value supplied:

  • ATTRIBUTE1 — mapped to PERIODYEAR, the processing year against which source code details are collected.
  • ATTRIBUTE2 — mapped to STARTPERIOD, the beginning fiscal period for the collection range.
  • ATTRIBUTE3 — mapped to ENDPERIOD, the closing fiscal period for the collection range.

In practice, a user would supply a valid period year along with start and end periods that bound the data window to be extracted. Since the program is documented as disabled, submissions are unlikely to succeed in a standard production instance unless the definition has been re-enabled by a functional administrator. Where the program remains disabled, the same collection logic may be replaced by a successor program or integrated into a broader Marketing Intelligence data load.

Related Objects

The BIM_SRC_CODE_DETAILS_PKG program is one component in a family of BIM-branded collection and load programs that feed the Marketing Intelligence and Trade Management schema. Related objects commonly associated with this pattern include other BIM concurrent programs that invoke similarly named packages with a .Populate entry point, together with the staging and interface tables those packages populate and the concurrent request set definitions that group them for sequential execution. Because the documented metadata does not enumerate specific interface tables, APIs, or reports, administrators should verify the actual dependent objects directly in the target instance by inspecting the package body of BIM_SRC_CODE_DETAILS_PKG and the concurrent program's incompatibilities and request set memberships in the Concurrent Programs form.