Results for “extract_version”
30 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBY_EXTRACTS_B is the base (non-translated) definition table for data extracts used during payment file creation in Oracle Payments (IBY). In Oracle EBS 12.1.1 and 12.2.2, payment formats do not write their output directly from transactional tables; instead, each format references a named extract that declares which PL/SQL generation package, entry point, and data source are invoked to assemble the payment instruction payload. IBY_EXTRACTS_B holds that extract definition, and its translated counterparts in IBY_EXTRACTS_TL provide the user-facing name and description.
The object is owned by the IBY schema and is classified as VALID in ETRM metadata, with 14 documented columns in the 12.2.2 physical schema. Under a heuristic Data Vault classification mined from the foreign-key structure, the table is assessed as hub-leaning: the business concept being modeled is the extract itself, keyed by EXTRACT_ID, with two child (satellite-like) consumers — the translation table IBY_EXTRACTS_TL and the payment format table IBY_FORMATS_B — depending on it. This classification is a modeling suggestion derived from the FK graph rather than a certified Data Vault design.
Key Information Stored
The table is anchored by a surrogate primary key, EXTRACT_ID, identified by the unique index IBY_EXTRACTS_B.EXTRACTID_U1 (EXTRACT_ID, ZD_EDITION_NAME). The edition column supports Oracle's edition-based redefinition strategy in 12.2.2, allowing multiple editions of the same row to coexist.
The business-key candidate is captured by the unique constraint IBY_EXTRACTS_B_CODE_VERSION_UK, composed of EXTRACT_CODE and EXTRACT_VERSION. This pairing allows multiple versions of the same logical extract to be defined and upgraded without losing prior definitions, which is essential when a payment format must be regenerated under a revised extraction rule.
- EXTRACT_ID — surrogate primary key, referenced by all dependent tables.
- EXTRACT_CODE — the human-readable business identifier for the extract.
- EXTRACT_VERSION — version indicator forming the second half of the business key.
- GEN_CODE_PACKAGE — PL/SQL package invoked to generate the extract output.
- GEN_CODE_ENTRY_POINT — the procedure or function inside that package that performs the generation.
- GEN_CODE_LANGUAGE — language setting applied to the generation logic.
- DATASOURCE_CODE — identifies the source from which extract data is retrieved.
- OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J layer.
- ZD_EDITION_NAME — edition-based redefinition discriminator in 12.2.2.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS WHO-column audit trail.
Common Use Cases and Queries
The most frequent operational query is locating the generation package behind a failing or custom payment format. A join between IBY_FORMATS_B and IBY_EXTRACTS_B by EXTRACT_ID reveals the responsible package and entry point, which is the first diagnostic step when a payment instruction file produces incorrect or empty output.
A representative query pattern:
SELECT f.format_code, e.extract_code, e.gen_code_package, e.gen_code_entry_point FROM iby_formats_b f, iby_extracts_b e WHERE f.extract_id = e.extract_id;- Audit queries select EXTRACT_CODE, EXTRACT_VERSION, LAST_UPDATED_BY, and LAST_UPDATE_DATE to detect extract definitions modified outside change control.
- Translation reporting joins IBY_EXTRACTS_TL on EXTRACT_ID to retrieve the display name in the session language.
Typical reporting uses include documenting which extracts exist per version, tracing custom extract registrations created during format extension, and validating that the referenced generation package still exists after database upgrades.
Related Objects
The following objects depend on IBY_EXTRACTS_B through documented foreign-key relationships or participate directly in extract resolution:
- IBY_EXTRACTS_TL — translation table; joins on IBY_EXTRACTS_TL.EXTRACT_ID = IBY_EXTRACTS_B.EXTRACT_ID, supplying name and description.
- IBY_FORMATS_B — payment format definitions; joins on IBY_FORMATS_B.EXTRACT_ID = IBY_EXTRACTS_B.EXTRACT_ID, linking each format to its extract.
- IBY_FORMATS_TL — translated format names, retrievable alongside the extract for user-facing reports.
- IBY_PAY_INSTRUCTIONS_ALL / IBY_PAYMENTS_ALL — downstream payment instruction records produced by the extract logic.
- IBY_DOCS_PAYABLE_ALL — documents delivered into the payment process, providing the source data consumed by the extract.
These objects together form the payment file generation chain: format definition, extract definition, generation code, and resulting instruction output.
-
Defines data extracts for payment file creation
-
Defines data extracts for payment file creation
-
View: IBY_EXTRACTS_VL 12.1.1
APPS.IBY_EXTRACTS_VL·↳ IBY_EXTRACTS_B·↳ IBY_EXTRACTS_TL·Explore IBY module →
-
View: IBY_EXTRACTS_VL 12.2.2
APPS.IBY_EXTRACTS_VL·↳ IBY_EXTRACTS_B·↳ IBY_EXTRACTS_TL·Explore IBY module →
-
VIEW: IBY.IBY_EXTRACTS_B# 12.2.2
-
VIEW: APPS.IBY_EXTRACTS_VL 12.2.2
-
VIEW: IBY.IBY_EXTRACTS_B# 12.2.2
-
VIEW: APPS.IBY_EXTRACTS_VL 12.1.1
-
TABLE: IBY.IBY_EXTRACTS_B 12.2.2
-
TABLE: IBY.IBY_EXTRACTS_B 12.1.1
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.1.1
Stores the user privilege settings for viewing sensitive data in iPayment operations UI
-
eTRM - IBY Tables and Views 12.2.2
Stores the user privilege settings for viewing sensitive data in iPayment operations UI