NJIT_CALL_D_ALOG
Just-In-Time Request: Action Logs - #GENERATED#
NJIT_CALL_D_ALOG is an SAP database table in S/4HANA. Just-In-Time Request: Action Logs - #GENERATED#. It contains 20 fields. 3 CDS views read from this table.
CDS Views using this table (3)
| View | Type | Join | VDM | Description |
|---|---|---|---|---|
| I_JITCallActionLog | view_entity | from | BASIC | JIT Call Action Log |
| I_JITInbCallActionLog | view_entity | from | BASIC | JIT Inbound Call Action Log |
| I_JITOutbCallActionLog | view_entity | from | BASIC | Interface for Action Log |
Fields (20)
| Key | Field | Data Element | Description | Domain | Type | Length |
|---|---|---|---|---|---|---|
| KEY | mandt | MANDT | Client | |||
| KEY | db_key | /BOBF/CONF_KEY | NodeID | |||
| root_key | /BOBF/CONF_KEY | NodeID | ||||
| parent_key | /BOBF/CONF_KEY | NodeID | ||||
| lognumber | BALNREXT | External ID | ||||
| object | BALOBJ_D | Object | ||||
| subobject | BALSUBOBJ | Subobject | ||||
| action_code | NJIT_ACTION | Action | ||||
| action_status | NJIT_STATUS_TYPE | Status Type | ||||
| action_source | NJIT_SOURCE | Action source | ||||
| fiori_application_name | DDTEXT | Short text | ||||
| crea_date_time | TIMESTAMPL | Time Stamp | ||||
| aluser | BALUSER | User | ||||
| jitfioriid | NJIT_FIORI_ID | Fiori ID | ||||
| jitapplicationlogseverity | NJIT_APPLICATION_LOG_SEVERITY | Appl Log Severity | ||||
| jitapplicationloghandle | BALLOGHNDL | Handle | ||||
| jitactionlogadditionalnote | abap.char | |||||
| jitpreintprocessingstatus | NJIT_INT_STAT | Intl Proc. Status | ||||
| jitpostintprocessingstatus | NJIT_INT_STAT | Intl Proc. Status | ||||
| jitframeaction | NJIT_ACTION | Action |
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.
-- Just-In-Time Request: Action Logs - #GENERATED#
-- Category TRANSPARENT · Delivery class A
-- Derived schema, generated from indexed DDIC field metadata (not the verbatim SAP source).
CREATE TABLE NJIT_CALL_D_ALOG (
MANDT, -- Client [MANDT]
DB_KEY, -- NodeID [/BOBF/CONF_KEY]
ROOT_KEY, -- NodeID [/BOBF/CONF_KEY]
PARENT_KEY, -- NodeID [/BOBF/CONF_KEY]
LOGNUMBER, -- External ID [BALNREXT]
OBJECT, -- Object [BALOBJ_D]
SUBOBJECT, -- Subobject [BALSUBOBJ]
ACTION_CODE, -- Action [NJIT_ACTION]
ACTION_STATUS, -- Status Type [NJIT_STATUS_TYPE]
ACTION_SOURCE, -- Action source [NJIT_SOURCE]
FIORI_APPLICATION_NAME, -- Short text [DDTEXT]
CREA_DATE_TIME, -- Time Stamp [TIMESTAMPL]
ALUSER, -- User [BALUSER]
JITFIORIID, -- Fiori ID [NJIT_FIORI_ID]
JITAPPLICATIONLOGSEVERITY, -- Appl Log Severity [NJIT_APPLICATION_LOG_SEVERITY]
JITAPPLICATIONLOGHANDLE, -- Handle [BALLOGHNDL]
JITACTIONLOGADDITIONALNOTE, -- abap.char
JITPREINTPROCESSINGSTATUS, -- Intl Proc. Status [NJIT_INT_STAT]
JITPOSTINTPROCESSINGSTATUS, -- Intl Proc. Status [NJIT_INT_STAT]
JITFRAMEACTION, -- Action [NJIT_ACTION]
PRIMARY KEY (MANDT, DB_KEY)
);
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