Results for “simulation_flag”

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

Overview

QP_DEBUG_REQ_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Advanced Pricing (QP) product family and is documented in the ETRM reference with a status of VALID. The view is defined over the base table QP_DEBUG_REQ and exposes the diagnostic and control context associated with pricing debug requests — the records that Advanced Pricing creates when a user or process requests detailed trace output for pricing engine execution.

The view is functionally identical to its base table in column terms. It selects every business column from QP_DEBUG_REQ and adds a synthetic ROW_ID column derived from the table's ROWID. Its role is primarily read-only reporting and integration: it gives developers, DBAs, and support analysts a stable, named object through which to query debug request configuration without touching the base table directly. Because the view contains no joins, filters, or computed business logic, it can be queried with the same semantics and performance characteristics as the underlying table, while preserving the convention of exposing APPS-owned entities through views.

Underlying Base Objects

The ETRM metadata documents a single referenced base object for this view: the synonym QP_DEBUG_REQ. In a standard EBS installation, QP_DEBUG_REQ is an APPS synonym pointing to the actual Advanced Pricing debug request table owned by the QP schema. The view definition is a straightforward projection:

• QP_DEBUG_REQ — the sole source object, providing all 20 business columns. The view adds ROW_ID as ROWID ROW_ID and otherwise performs no transformation.

Because the view does not join to QP_DEBUG_REQ_LINES, QP_DEBUG_LOG, or any FND lookup table, it carries only the header-level attributes of a debug request. Detail-level debug output must be obtained from the corresponding debug log or line tables, keyed by REQUEST_ID.

Key Columns

The view exposes the following columns, all sourced from QP_DEBUG_REQ:

• ROW_ID — the physical ROWID of the base row, useful as a pseudo-primary key in ad hoc queries.
• REQUEST_ID — the identifier of the debug request; the primary correlation key to concurrent request and debug log data.
• REQUEST_NAME — the descriptive name assigned to the debug request. This is the column most commonly searched by users attempting to locate a specific pricing trace.
• CREATED_BY / CREATION_DATE — standard EBS audit columns identifying who created the request and when.
• PRICING_EVENT — the pricing event or phase against which debugging is targeted.
• CALCULATE_FLAG, SIMULATION_FLAG, ROUNDING_FLAG — flags controlling calculation, simulation, and rounding behaviour during the debug run.
• GSA_CHECK_FLAG, GSA_DUP_CHECK_FLAG — controls for GSA pricing validation and duplicate checking.
• TEMP_TABLE_INSERT_FLAG, MANUAL_DISCOUNT_FLAG, DEBUG_FLAG — operational toggles for temporary table population, manual discount handling, and debug trace output.
• SOURCE_ORDER_AMOUNT_FLAG, PUBLIC_API_CALL_FLAG, MANUAL_ADJUSTMENTS_CALL_FLAG, CHECK_CUST_VIEW_FLAG — flags indicating the invocation context, such as public API calls, manual adjustments, and customer view checks.
• REQUEST_TYPE_CODE, VIEW_CODE, CURRENCY_CODE — the request category, pricing view identifier, and currency context of the debug request.

Common Use Cases and Queries

The most frequent use is locating a debug request by its name or ID before extracting the associated trace. Support analysts also use the view to audit which debug flags were enabled for a given run, particularly when diagnosing pricing discrepancies.

• Find a request by name:

SELECT request_id, request_name, created_by, creation_date
FROM   apps.qp_debug_req_v
WHERE  request_name LIKE '%ORDER%';

• List recent debug requests with their flags:

SELECT request_id, request_name, pricing_event, debug_flag,
       calculate_flag, simulation_flag, currency_code
FROM   apps.qp_debug_req_v
WHERE  creation_date >= SYSDATE - 7
ORDER  BY creation_date DESC;

• Identify debug requests invoked through public APIs:

SELECT request_id, request_name, public_api_call_flag,
       manual_adjustments_call_flag
FROM   apps.qp_debug_req_v
WHERE  public_api_call_flag = 'Y';

These queries return debug request configuration only; the actual trace output resides in the debug log objects referenced by REQUEST_ID.