MPE_TT_CLAIM_OA
Tool Tracking: OAs
MPE_TT_CLAIM_OA is an SAP database table in S/4HANA. Tool Tracking: OAs. It contains 5 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| I_TrackToolUsageHistOpActy | view | from | BASIC | Track Tool Usage: History for equipment by claim type OA |
Fields (5)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | MANDT | Client | |||
| KEY | docnmbr | MPE_DOC_NMBR | Document Number | |||
| KEY | oan_instance_id | MPE_OAN_INSTANCE_ID | Instance ID | |||
| KEY | oan_element_number | MPE_OAN_ELEMENT_NUMBER | Element Number | |||
| sfi_id | MPE_SFI_ID | Serial.Mat. ID |
Derived SQL schema, reconstructed from the indexed DDIC field metadata (field names, types, lengths and key flags) — a functional representation, not the verbatim SAP source.
-- Tool Tracking: OAs
-- Category TRANSPARENT · Delivery class A
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE MPE_TT_CLAIM_OA (
MANDT, -- Client [MANDT]
DOCNMBR, -- Document Number [MPE_DOC_NMBR]
OAN_INSTANCE_ID, -- Instance ID [MPE_OAN_INSTANCE_ID]
OAN_ELEMENT_NUMBER, -- Element Number [MPE_OAN_ELEMENT_NUMBER]
SFI_ID, -- Serial.Mat. ID [MPE_SFI_ID]
PRIMARY KEY (MANDT, DOCNMBR, OAN_INSTANCE_ID, OAN_ELEMENT_NUMBER)
);
Learn More
- Understanding Data Lineage in SAP S/4HANA
- SAP Tables vs CDS Views — Key Differences
- Understanding the SAP S/4HANA Data Model
- BSEG to ACDOCA: The Universal Journal Migration
- Business Partner Migration: KNA1/LFA1 to BUT000
- Material Document Migration: MSEG/MKPF to MATDOC
- How to Find the Right CDS View for an SAP Table
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA