Search Results aso_apr_rule_steps_b




Overview
Explore in AI Chat

Overview

The table ASO_APR_RULE_STEPS_B is a core data structure within the Oracle E-Business Suite (EBS) Order Capture (ASO) module. It was designed to store the individual steps or conditions that comprise an approval rule, forming part of a legacy approval rules engine. However, based on the provided ETRM documentation, this table is explicitly marked as obsolete and was not used in the 11i release. In the context of Oracle EBS 12.1.1 and 12.2.2, this object is considered a historical artifact. Its presence in the database schema is typically for backward compatibility or data migration purposes, and it is not part of the active application logic in these later versions. Its primary role was to define rule logic by linking attributes and functions for comparison.

Key Information Stored

The table's structure indicates it was intended to store the components of a rule's conditional logic. The primary key is ASO_APR_RULE_STEP_ID, which uniquely identifies each step. A critical foreign key, ASO_APR_RULE_ID, links the step to its parent rule in the ASO_APR_RULES_B table. The table design supports complex rule conditions through columns referencing left-hand side (LHS) and right-hand side (RHS) elements. Key columns include LHS_AK_OBJECT, LHS_AK_ATTRIBUTE_CODE, and LHS_AK_ATTR_APPLIC_ID, which together would reference a specific attribute from the AK_OBJECT_ATTRIBUTES table to form one side of a condition. Corresponding RHS columns (RHS_AK_OBJECT, etc.) define the other side. Furthermore, LHS_FUNCTION_ID and RHS_FUNCTION_ID columns allow for the application of transformation functions (from ASO_APR_FUNCTION) to the attribute values before comparison.

Common Use Cases and Queries

As the table is obsolete in releases 12.1.1 and 12.2.2, there are no active use cases for application development or integration. Its primary relevance is for technical consultants and DBAs performing schema analysis, data cleanup, or understanding legacy data migration paths. Sample queries would be diagnostic in nature. For instance, identifying if any residual data exists in the table: SELECT COUNT(*) FROM ASO_APR_RULE_STEPS_B;. Another query might examine the historical structure by joining to related tables, though these related tables are likely also obsolete: SELECT step.aso_apr_rule_step_id, rule.rule_name FROM ASO_APR_RULE_STEPS_B step LEFT JOIN ASO_APR_RULES_B rule ON step.aso_apr_rule_id = rule.aso_apr_rule_id WHERE ROWNUM < 10;.

Related Objects

The ETRM metadata clearly defines the following relationships for the ASO_APR_RULE_STEPS_B table:

  • Parent/Referenced Tables (Foreign Keys FROM this table):
    • ASO_APR_RULES_B: Linked via ASO_APR_RULE_STEPS_B.ASO_APR_RULE_ID.
    • AK_OBJECT_ATTRIBUTES (for LHS): Linked via the composite foreign key on columns LHS_AK_OBJECT, LHS_AK_ATTRIBUTE_CODE, and LHS_AK_ATTR_APPLIC_ID.
    • AK_OBJECT_ATTRIBUTES (for RHS): Linked via the composite foreign key on columns RHS_AK_OBJECT, RHS_AK_ATTRIBUTE_CODE, and RHS_AK_ATTR_APPLIC_ID.
    • ASO_APR_FUNCTION (for LHS): Linked via ASO_APR_RULE_STEPS_B.LHS_FUNCTION_ID.
      • ASO_APR_FUNCTION (for RHS): Linked via ASO_APR_RULE_STEPS_B.RHS_FUNCTION_ID.
  • Child/Referencing Table (Foreign Key TO this table):
    • ASO_APR_RULE_STEPS_TL: Likely a translation table, linked via ASO_APR_RULE_STEPS_TL.ASO_APR_RULE_STEP_ID.