Results for “exclude_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JE_GR_TRNOVR_RULE_LINES table is a component of the Oracle E-Business Suite European Localizations (JE) module, which provides country-specific statutory and regulatory functionality, most notably for Greece. This table stores the individual exclusion rule lines that make up a turnover data exclusion rule. Turnover data in this context refers to revenue-related information that feeds statutory reporting and tax computations; exclusion rules allow an implementation to filter out specific turnover transactions or components so that they are not included in the reported turnover figures.

Each row in JE_GR_TRNOVR_RULE_LINES represents a single line belonging to a parent rule header. The parent header is held in JE_GR_TRNOVR_RULES, and the child lines are linked through the TRNOVR_RULE_ID column. The line-level grain means that a single rule may consist of multiple exclusion criteria evaluated together to determine which turnover data should be excluded.

From a data modeling perspective, the heuristic Data Vault classification derived from the foreign key structure is satellite-leaning. This suggests the table is best understood as a descriptive satellite attached to the JE_GR_TRNOVR_RULES hub, capturing the detail attributes of the exclusion rule at a point in time rather than acting as an independent hub or an associative link.

Key Information Stored

The physical schema in ETRM 12.2.2 documents 27 columns. The most significant are:

• TRNOVR_RULE_LINE_ID — Surrogate primary key of the table. It is enforced by JE_GR_TRNOVR_RULE_LINES_PK and is also the single column of the unique index JE_GR_TRNOVR_RULE_LINES_U1, making it the sole documented business-key candidate.
• TRNOVR_RULE_ID — Foreign key to JE_GR_TRNOVR_RULES. This is the join column that ties each exclusion line back to its rule header and defines the parent-child relationship.
• APPLICATION_ID — Identifies the owning application context, consistent with the multi-application architecture of the EBS data model.
• LOOKUP_TYPE and LOOKUP_CODE — Together they reference an Oracle EBS lookup value, defining the classification or category of the exclusion line, such as the type of turnover segment being excluded.
• EXCLUDE_FLAG — Indicates whether the referenced lookup value is to be excluded when the rule is applied. This flag drives the actual evaluation logic of the rule.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each row and when.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield (DFF) columns, allowing the localization to extend the structure without schema changes.

Common Use Cases and Queries

Typical access patterns revolve around retrieving and validating the lines belonging to a given exclusion rule. A common query joins the child lines to the parent rule:

• SELECT l.trnovr_rule_line_id, l.trnovr_rule_id, l.lookup_type, l.lookup_code, l.exclude_flag FROM je.je_gr_trnovr_rule_lines l WHERE l.trnovr_rule_id = :rule_id
• Reporting and reconciliation queries filter on EXCLUDE_FLAG to list only actively excluded turnover components for a statutory report.
• Lookup validation queries join LOOKUP_TYPE and LOOKUP_CODE to the FND lookup tables to resolve descriptive meanings for reporting.
• DFF queries filter on ATTRIBUTE_CATEGORY and the ATTRIBUTE1–15 columns for locale-specific extensions.

Because the table is transactional reference data rather than high-volume transactional data, queries are typically small and rule-oriented, used during setup, audit, and statutory reporting cycles.

Related Objects

• JE_GR_TRNOVR_RULES — The parent rule header table. Joined via JE_GR_TRNOVR_RULE_LINES.TRNOVR_RULE_ID = JE_GR_TRNOVR_RULES.TRNOVR_RULE_ID. This is the primary and only documented foreign key relationship.
• JE_GR_TRNOVR_RULE_LINES_PK — The primary key constraint enforcing TRNOVR_RULE_LINE_ID uniqueness.
• JE_GR_TRNOVR_RULE_LINES_U1 — The unique index on TRNOVR_RULE_LINE_ID, documenting the business-key candidate.
• FND_LOOKUP_VALUES — Referenced indirectly via LOOKUP_TYPE and LOOKUP_CODE to resolve exclusion line classifications.
• FND_APPLICATION — Resolves the APPLICATION_ID context of each line.

Collectively these objects support the Greek turnover exclusion rule framework within the JE European Localizations product.