Results for “aso_apr_rules_b”

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

Overview

ASO_APR_RULES_B is a base table belonging to the ASO – Order Capture module (Order Capture / Oracle Advanced Pricing–related rule definitions) in Oracle E-Business Suite. According to the ETRM metadata, the object is documented as obsolete and not used in 11i, and is flagged in the implementation notes as not implemented in this database. Consequently, in Oracle EBS 12.1.1 and 12.2.2 environments, this table should generally be regarded as a legacy or reserved object rather than an actively populated transactional table. It retains a defined structure, a primary key, and a set of referential constraints, but normal order-capture processing does not write to or read from it.

Heuristically, the FK/PK topology classifies this object as hub-leaning within a Data Vault modeling convention: it carries a single surrogate identifier (ASO_APR_RULE_ID) that is referenced by several dependent tables, which is characteristic of a hub entity surrounded by satellite and link structures. This classification is a suggestion only, derived from the mined relationship data, and should be validated against the actual physical model before being relied upon.

Key Information Stored

Because the object is obsolete, the metadata documents only a minimal set of columns. The columns that matter structurally are:

• ASO_APR_RULE_ID – the surrogate primary key column, defined by the constraint ASO_APR_RULES_B_PK. It uniquely identifies each rule row and is the column propagated into all dependent child tables.
• AK_OBJECT – a foreign key referencing AK_OBJECTS, linking the rule to an AK (Application Kit) object definition. This identifies the object context against which the rule was defined.

The remaining descriptive and translatable attributes of the rule are not held on this base table. Textual/descriptive content is delegated to ASO_APR_RULES_TL, and the rule's constituent steps and group memberships are held in separate child tables, as reflected in the FK relationships. No additional business-key unique indexes are documented in the provided metadata beyond the primary key, so ASO_APR_RULE_ID is the only documented identifier for this object.

Common Use Cases and Queries

In practice, direct querying of ASO_APR_RULES_B occurs principally during data-model archaeology, impact analysis, and upgrade assessment rather than in day-to-day reporting. Typical patterns include verifying whether the object is populated at all, and tracing rule identifiers into the dependent tables:

• Existence/population check: SELECT COUNT(*) FROM ASO_APR_RULES_B; — a zero or near-zero count confirms the obsolete status documented in the ETRM metadata.
• Rule-to-translation join: SELECT b.aso_apr_rule_id, t.* FROM aso_apr_rules_b b, aso_apr_rules_tl t WHERE b.aso_apr_rule_id = t.aso_apr_rule_id;
• Rule-to-step join: SELECT b.aso_apr_rule_id, s.* FROM aso_apr_rules_b b, aso_apr_rule_steps_b s WHERE b.aso_apr_rule_id = s.aso_apr_rule_id;
• Object linkage: SELECT b.aso_apr_rule_id, b.ak_object FROM aso_apr_rules_b b, ak_objects a WHERE b.ak_object = a.object_id; (join column names should be confirmed against the AK_OBJECTS definition).

These queries are useful for confirming referential integrity before archiving, for assessing customizations that may reference the table, and for supporting pre-upgrade or decommissioning decisions.

Related Objects

The following objects are documented as participating in the referential structure of ASO_APR_RULES_B and represent the most significant dependencies:

• ASO_APR_RULES_TL – translatable/descriptive rows; join on ASO_APR_RULES_TL.ASO_APR_RULE_ID → ASO_APR_RULES_B.ASO_APR_RULE_ID.
• ASO_APR_RULE_GRP_MEMBER – group membership entries; join on ASO_APR_RULE_GRP_MEMBER.ASO_APR_RULE_ID → ASO_APR_RULES_B.ASO_APR_RULE_ID.
• ASO_APR_RULE_STEPS_B – the steps defining each rule; join on ASO_APR_RULE_STEPS_B.ASO_APR_RULE_ID → ASO_APR_RULES_B.ASO_APR_RULE_ID.
• AK_OBJECTS – referenced by the AK_OBJECT foreign key on ASO_APR_RULES_B, linking rules to AK object metadata.

Collectively, these define the hub-and-dependent structure around the ASO_APR_RULE_ID surrogate key. Because the parent object is documented as obsolete, these child tables should likewise be treated as legacy and validated for population before any analysis or reporting is attempted.