Results for “fte_chrg_prc_attributes”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FTE_CHRG_PRC_ATTRIBUTES is a Transportation Execution (FTE) module table within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as an audit and traceability table that stores the qualifying conditions and pricing attributes responsible for granting a particular price or charge to a load or load detail record. When Oracle Transportation Management (OTM) or the EBS transportation pricing engine evaluates a rate or charge against a shipment, it records the specific qualifiers — such as service level, equipment type, lane, commodity, or accessorial conditions — that either matched or failed to match during that evaluation. FTE_CHRG_PRC_ATTRIBUTES persists those individual evaluation outcomes, allowing the system to explain why a given charge was assigned.
The table's role in EBS is primarily diagnostic and supporting. It does not drive pricing calculations directly; instead, it enables users to drill from a finalized charge back to the individual qualifier attributes that triggered it. Based on the mined foreign key structure — the single FK to FTE_LOAD_CHARGES — this object is best described as satellite-leaning in a heuristic Data Vault classification. It is a dependent, descriptive table hanging off the load-charge hub, and it should be treated as a satellite when modeling for analytics rather than as an independent hub or link.
Key Information Stored
The documented metadata confirms a focused, narrow structure. The most important data elements are:
- LOAD_CHARGE_ID — the foreign key to FTE_LOAD_CHARGES. This is the dominant relational anchor and links each attribute row to the specific charge it explains.
- Qualifier and Pricing Attribute definitions — columns holding the identity and values of each qualifier and/or pricing attribute that qualified the load or load detail for the price or charge in question.
- Attribute category / type indicators — distinguishing whether the stored row represents a Qualifier versus a Pricing Attribute.
- Attribute name and value pairs — the descriptive content capturing the specific condition (for example, service level code, region, or equipment class) used during evaluation.
The table's own surrogate primary key (typically a sequence-generated identifier) is the technical row identifier, while LOAD_CHARGE_ID is the principal business-key candidate and the column validated by the documented foreign key to FTE_LOAD_CHARGES. No other unique indexes are documented in the supplied metadata. The excerpt also notes "Not implemented in this database," meaning the proprietary column list is not fully exposed for this environment; analysts should verify the exact column inventory against the seeded ETRM data model before writing production SQL.
Common Use Cases and Queries
The most frequent use case is charge explanation and dispute resolution. A transportation analyst who questions why a load incurred a specific freight charge can join FTE_CHRG_PRC_ATTRIBUTES to FTE_LOAD_CHARGES to retrieve all qualifiers that contributed to that decision:
- Charge justification reports — list every qualifier and pricing attribute attached to each charge on a shipment.
- Rate auditing — identify loads where multiple qualifiers matched, indicating potential ambiguity or over-qualification.
- Pricing troubleshooting — compare expected qualifiers against actual recorded attributes when charges appear erroneous.
- Historical traceability — retain the evaluation context for compliance and audit trails.
A representative query pattern joins on the documented key:
- SELECT lc.load_id, lc.charge_amount, cpa.* FROM fte_load_charges lc, fte_chrg_prc_attributes cpa WHERE lc.load_charge_id = cpa.load_charge_id AND lc.load_id = :load_id;
Related Objects
The documented foreign key makes FTE_LOAD_CHARGES the primary parent object. Other significant related tables in the FTE transportation model include those holding loads, load details, and rate/charge definitions, which are joined indirectly through FTE_LOAD_CHARGES. The most significant dependents and references are:
- FTE_LOAD_CHARGES — parent object; join on LOAD_CHARGE_ID. This is the only documented foreign key relationship.
- FTE_LOADS — the shipment header providing the load context, reached through FTE_LOAD_CHARGES.
- FTE_LOAD_DETAILS — line-level load records that may carry charge-level attribute detail.
- FTE_RATE_* / charge definition tables — the pricing engine objects whose qualifiers are materialized into this table.
- OTM integration interfaces — inbound pricing and rating messages that populate charge and attribute data.
Because the object is satellite-leaning, downstream reporting views and FTE charge inquiry screens typically consume it as a detail child of FTE_LOAD_CHARGES rather than querying it standalone.
-
This table holds the details of any Qualifiers and/or Pricing Attributes that qualified the Load or Load Detail to receive a particular price or charge.
Not implemented in this database·Explore FTE module →
-
This table holds the details of any Qualifiers and/or Pricing Attributes that qualified the Load or Load Detail to receive a particular price or charge.
Not implemented in this database·Explore FTE module →
-
Table: FTE_LOAD_CHARGES 12.1.1
Holds the price related to the details of a tendered shipment
Not implemented in this database·Explore FTE module →
-
12.1.1 FND Design Data 12.1.1
-
Table: FTE_LOAD_CHARGES 12.2.2
Holds the price related to the details of a tendered shipment
Not implemented in this database·Explore FTE module →
-
12.2.2 FND Design Data 12.2.2