Results for “review_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The OZF.OZF_SD_BATCH_LINE_DISPUTES table is a Trade Management (OZF) module object within Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores line-level dispute information for Supplier Ship and Debit (SD) batches processed in Oracle Trade Management. Supplier Ship and Debit is the mechanism by which a supplier reimburses a distributor or reseller for promotional allowances, rebates, or price protections tied to specific shipment and debit transactions. When a discrepancy arises between what a supplier acknowledges and what the distributor claims — for example, an insufficient credit, a rejected line, or a disputed rebate amount — the dispute is captured at the batch line level in this table.
The object is documented in ETRM as a standalone table with 17 columns, primary key OZF_SD_BATCH_LINE_DISPUTES_PK on BATCH_LINE_DISPUTE_ID, and a unique index OZF_SD_BATCH_LINE_DISPUTES_U1 on the same column. Under a heuristic Data Vault classification mined from the foreign key structure, this table is modeled as standalone — it does not function as a classic hub, link, or satellite, since its only documented foreign key points to a security construct rather than a business entity. In practice it behaves as a line-level satellite or detail table attached to a ship-and-debit batch hierarchy, carrying descriptive dispute attributes plus standard WHO/audit columns.
Key Information Stored
The most significant columns in this table are:
BATCH_LINE_DISPUTE_ID— the surrogate primary key and business-key candidate (unique index U1), uniquely identifying each dispute record.BATCH_ID— reference to the parent Supplier Ship and Debit batch header.BATCH_LINE_ID— reference to the specific batch line on which the dispute is raised.DISPUTE_CODE— the categorization of the dispute (reason or type).REVIEW_FLAG— indicates whether the dispute is flagged for review.OBJECT_VERSION_NUMBER— optimistic locking column used by the Trade Management framework.SECURITY_GROUP_ID— foreign key toFND_SECURITY_GROUPS, enforcing multi-tenant/multi-org data security.- Standard audit columns:
CREATION_DATE,CREATED_BY,CREATED_FROM,LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN. - Concurrent program columns:
REQUEST_ID,PROGRAM_ID,PROGRAM_APPLICATION_ID,PROGRAM_UPDATE_DATE— identifying the batch process that inserted or updated the record.
The surrogate key is BATCH_LINE_DISPUTE_ID; the unique index U1 is documented as the business-key candidate. The composite of BATCH_ID and BATCH_LINE_ID functions as a logical parent reference even though no FK constraint to the batch tables is documented in the metadata.
Common Use Cases and Queries
Typical reporting scenarios include identifying disputed lines within a batch, measuring dispute rates by reason code, and reviewing flagged disputes pending resolution.
SELECT d.BATCH_LINE_DISPUTE_ID, d.BATCH_ID, d.BATCH_LINE_ID,
d.DISPUTE_CODE, d.REVIEW_FLAG, d.CREATION_DATE
FROM OZF.OZF_SD_BATCH_LINE_DISPUTES d
WHERE d.BATCH_ID = :p_batch_id;
A dispute-reason analysis query groups by DISPUTE_CODE:
SELECT DISPUTE_CODE, COUNT(*) dispute_count FROM OZF.OZF_SD_BATCH_LINE_DISPUTES WHERE SECURITY_GROUP_ID = :p_security_group GROUP BY DISPUTE_CODE ORDER BY dispute_count DESC;
Users may also filter on REVIEW_FLAG to surface disputes requiring manual attention, and join to the concurrent request columns to trace which batch program created the dispute.
Related Objects
FND_SECURITY_GROUPS— joined viaSECURITY_GROUP_ID; the only documented foreign key relationship.- Supplier Ship and Debit batch header table (OZF SD batch) — referenced via
BATCH_ID. - Supplier Ship and Debit batch line table — referenced via
BATCH_LINE_ID. FND_CONCURRENT_REQUESTS— associated throughREQUEST_IDfor audit tracing.- Trade Management SD batch concurrent programs — populate the dispute rows during batch validation and reconciliation.
- OZF Trade Management reporting views and OBIEE/Discoverer extracts that consolidate dispute metrics.
The object is Oracle proprietary and confidential, distributed under legal notices as part of the ETRM documentation set.
-
store the line dispute information of Supplier Ship and Debit Batch in Oracle Trade Management
-
store the line dispute information of Supplier Ship and Debit Batch in Oracle Trade Management
-
View: HR_POSITIONS_X 12.2.2
Date-effective view based on secured positions view.
APPS.HR_POSITIONS_X·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_ALL_POSITIONS 12.2.2
Date-effective view.
APPS.HR_ALL_POSITIONS·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
Every time a learner plays online learning, a row in this table is created for a specific leaner against a learning object.
-
View: HR_POSITIONS_F 12.1.1
Secure view based on the corresponding _ALL_ table.
APPS.HR_POSITIONS_F·↳ FND_PROFILE·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITIONS 12.2.2
Date-effective view based on secured positions view.
APPS.HR_POSITIONS·↳ FND_PROFILE·↳ FND_SESSIONS·↳ HR_GENERAL·Explore PER module →
-
View: HR_ALL_POSITIONS_V1 12.2.2
Date-effective view with reduced pl/sql functions for performance.
APPS.HR_ALL_POSITIONS_V1·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITION_API_V 12.2.2
APPS.HR_POSITION_API_V·↳ HR_ALL_POSITIONS_F·↳ PER_POSITION_DEFINITIONS·Explore PER module →
-
View: HR_ALL_POSITIONS 12.1.1
Date-effective view.
APPS.HR_ALL_POSITIONS·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_POSITIONS 12.1.1
Date-effective view based on secured positions view.
APPS.HR_POSITIONS·↳ FND_PROFILE·↳ FND_SESSIONS·↳ HR_GENERAL·Explore PER module →
-
View: HR_POSITIONS_X 12.1.1
Date-effective view based on secured positions view.
APPS.HR_POSITIONS_X·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
Every time a learner plays online learning, a row in this table is created for a specific leaner against a learning object.
-
View: GHR_POSITIONS_H_V 12.2.2
Mapping of GHR_PA_HISTORY columns to HR_ALL_POSITIONS_F.
APPS.GHR_POSITIONS_H_V·↳ FND_DATE·↳ GHR_GENERAL·↳ GHR_PA_HISTORY·Explore GHR module →
-
View: HR_POSITIONS_F 12.2.2
Secure view based on the corresponding _ALL_ table.
APPS.HR_POSITIONS_F·↳ FND_PROFILE·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
Position Extra information shadow used for refreshing position transaction extra information.
-
POSITION_TRANSACTION is used to maintain and create positions. Each transaction needs to be approved by pre-identified approvers. On approval these transactions are applied to database.Each transaction can have a combination of one or more
-
Position Extra information shadow used for refreshing position transaction extra information.
-
View: GHR_POSITIONS_H_V 12.1.1
Mapping of GHR_PA_HISTORY columns to HR_ALL_POSITIONS_F.
APPS.GHR_POSITIONS_H_V·↳ FND_DATE·↳ GHR_GENERAL·↳ GHR_PA_HISTORY·Explore GHR module →
-
View: HR_POSITIONS_V1 12.1.1
To support User Interface.
APPS.HR_POSITIONS_V1·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_POSITIONS_V1 12.2.2
To support User Interface.
APPS.HR_POSITIONS_V1·↳ FND_PROFILE·↳ HR_GENERAL·↳ HR_POSITIONS_F·Explore PER module →
-
View: HR_ALL_POSITIONS_F_VL 12.2.2
APPS.HR_ALL_POSITIONS_F_VL·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_POSITIONS_V 12.2.2
To support User Interface.
APPS.HR_POSITIONS_V·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_POSITIONS_V 12.1.1
To support User Interface.
APPS.HR_POSITIONS_V·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_GENERAL·Explore PER module →
-
View: HR_ALL_POSITIONS_F_VL 12.1.1
APPS.HR_ALL_POSITIONS_F_VL·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
View: HR_ALL_POSITIONS_V1 12.1.1
Date-effective view with reduced pl/sql functions for performance.
APPS.HR_ALL_POSITIONS_V1·↳ FND_SESSIONS·↳ HR_ALL_POSITIONS_F·↳ HR_ALL_POSITIONS_F_TL·Explore PER module →
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
View: HR_POSITION_API_V 12.1.1
APPS.HR_POSITION_API_V·↳ HR_ALL_POSITIONS_F·↳ PER_POSITION_DEFINITIONS·Explore PER module →
-
POSITION_TRANSACTION is used to maintain and create positions. Each transaction needs to be approved by pre-identified approvers. On approval these transactions are applied to database.Each transaction can have a combination of one or more
-
Position definition information.
-
Position definition information.
-
APPS.PQH_POSITION_TRANSACTIONS_V·↳ HR_GENERAL·↳ PQH_POSITION_TRANSACTIONS·↳ PQH_UTILITY·Explore PQH module →
-
VIEW: OTA.OTA_ATTEMPTS# 12.2.2
-
PACKAGE: APPS.PQH_PTX_INS 12.2.2
-
PACKAGE: APPS.PQH_PTX_UPD 12.1.1
-
PACKAGE: APPS.PQH_PTX_UPD 12.2.2
-
PACKAGE: APPS.PQH_PTX_INS 12.1.1
-
VIEW: HR.PQH_PTX_SHADOW# 12.2.2
-
VIEW: OTA.OTA_ATTEMPTS# 12.2.2