SCBO_TRC_EXC_DET
CBO Tracing - Exception Details
SCBO_TRC_EXC_DET is an SAP database table in S/4HANA. CBO Tracing - Exception Details. It contains 5 fields. 1 CDS views read from this table.
CDS Views using this table (1)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| I_Scbo_TraceException_TP | view | from | CBO: Trace Exception |
Fields (5)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | trace_run_id | SXCO_TRACE_RUN_ID | Trace Run ID | |||
| KEY | ordinal_number | SXCO_ORDINAL_NUMBER | Ordinal Number | |||
| class_name | SXCO_CLASS_NAME | Class Name | ||||
| class_etag | abap.char | |||||
| exception_text | abap.char |
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.
-- CBO Tracing - Exception Details
-- Category TRANSPARENT · Delivery class W
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE SCBO_TRC_EXC_DET (
TRACE_RUN_ID, -- Trace Run ID [SXCO_TRACE_RUN_ID]
ORDINAL_NUMBER, -- Ordinal Number [SXCO_ORDINAL_NUMBER]
CLASS_NAME, -- Class Name [SXCO_CLASS_NAME]
CLASS_ETAG, -- abap.char
EXCEPTION_TEXT, -- abap.char
PRIMARY KEY (TRACE_RUN_ID, ORDINAL_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