Search Results ben_ext_rslt




Overview
Explore in AI Chat

Overview

BEN_EXT_RSLT is the extract result table within the BEN (Advanced Benefits) product schema of Oracle E-Business Suite. It records the outcome of each benefits extract process executed against a defined extract definition, capturing run-level statistics, status, output file information, and the effective and processing date ranges that governed the run. In EBS 12.1.1 and 12.2.2 the table is owned by the BEN schema and is documented as VALID with 26 columns in the ETRM 12.2.2 physical schema. Its role is operational and diagnostic: it is the parent record for the detailed rows produced by an extract and for any errors encountered during that extract.

From a data modeling perspective, the metadata's heuristic Data Vault classification for this object is satellite-leaning. This should be treated as a modeling suggestion rather than a documented definition: BEN_EXT_RSLT behaves as a descriptive satellite attached to the extract definition (BEN_EXT_DFN), carrying run-specific attributes and audit columns rather than acting as a pure hub or a link between two business entities.

Key Information Stored

The primary key is BEN_EXT_RSLT_PK, defined on the surrogate column EXT_RSLT_ID. No additional unique business-key index is documented beyond this primary key, so EXT_RSLT_ID is the sole documented unique identifier for a row.

Common Use Cases and Queries

The table is most often queried to diagnose failed or partial extract runs, to reconcile counts of extracted records and errors, and to locate generated output files. A typical diagnostic query retrieves the latest runs for a definition:

  • Filter by EXT_DFN_ID and order by RUN_STRT_DT descending to review run history.
  • Filter on EXT_STAT_CD to isolate failures, then inspect TOT_ERR_NUM and join to BEN_EXT_RSLT_ERR.
  • Report on DRCTRY_NAME, OUTPUT_NAME, and OUTPUT_TYPE to locate and audit extract files.
  • Join on REQUEST_ID to the concurrent request tables to correlate with the submitted program.
  • Use RUN_STRT_DT/RUN_END_DT with TOT_REC_NUM to monitor throughput and SLA compliance.

A representative pattern is: select the result row by EXT_DFN_ID and run date, then join BEN_EXT_RSLT_DTL on EXT_RSLT_ID for row-level detail and BEN_EXT_RSLT_ERR on EXT_RSLT_ID for error records.

Related Objects

  • BEN_EXT_DFN — referenced via BEN_EXT_RSLT.EXT_DFN_ID; defines the extract criteria executed for this result.
  • BEN_EXT_RSLT_ERR — references BEN_EXT_RSLT.EXT_RSLT_ID; holds errors generated during the extract run.
  • BEN_EXT_RSLT_DTL — references BEN_EXT_RSLT.EXT_RSLT_ID; holds the detailed extracted rows for the run.
  • BEN_EXT_RSLT_PK — the primary key constraint and unique index on EXT_RSLT_ID.
  • FND_CONCURRENT_REQUESTS — joinable on REQUEST_ID to identify the concurrent program execution.
  • XDO_TEMPLATES — related through XDO_TEMPLATE_ID for XML Publisher output definition.