I_JITInbCallActionLog
JIT Inbound Call Action Log
I_JITInbCallActionLog is a Basic CDS View (Dimension) that provides data about "JIT Inbound Call Action Log" in SAP S/4HANA. It reads from 1 data source (njit_call_d_alog) and exposes 28 fields with key field JITCallActionLogUUID. It has 8 associations to related views.
SAP Help Documentation
| Category | CDS Views for Just-in-Time Inbound Call |
|---|---|
| Data Category | Dimension |
| Status | After Internal Processing Status |
Purpose
This CDS view helps retrieve application log data of a particular JIT call. This CDS view provides the data to answer the following business questions: Which action has been performed on the JIT call along with the Fiori ID and Fiori application name? Against what application object and subobject has the action has been performed? This CDS view is enabled for both key user app extensibility and developer extensibility. To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .
Prerequisites
Authorizations Users who want to use this CDS view can have a role with the following restriction types set to read access: Restriction Type ID Restriction Type Comments SALES_AREA Sales Area User must have this restriction type to access JIT call data BEGRU_KNA1 Authorization Group for Customers This depends on the user profile You can use the Display Restriction Types app to find out in which business catalogs these restriction types are included. Users who want to use this CDS view can have the following authorization objects assigned: Authorization Object ID Authorization Object Comments JIT_INB_CO JIT Supply to Customer: Process inbound calls This authorization object must be assigned to the user to access JIT call data F_KNA1_BED Customer: Account Authorization Needed only if the user wants to see JIT calls for a blocked customer
Structure
Important Fields Important fields in this view include the following: Field Name Description JITCallActionLogUUID JIT Call Action Log UUID JITHeaderUUID JIT Call Header UUID JITCallCompGrpUUID JIT Call Component Group UUID ApplicationLogObject Application Log: Object ApplicationLogSubobject Application Log: Sub object JITCallProcessingLogID Application Log: External Identification JITFioriApplicationName JIT Fiori application name JITCallActionSource Action log: Action source JITAction JIT Action JITCallActionStatus Status Type TriggeredByUser Application log: user name CreationDateTime UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) JITFioriID Fiori ID for Just-in-Time Application JITApplicationLogHandle Application Log: Log Handle JITApplicationLogSeverity Indicates severity of the application logs JITActionLogAdditionalNote Additional note for JIT action logs JITPreIntProcessingStatus Previous Internal Processing Status JITPostIntProcessingStatus After Internal Processing Status JITFrameAction JIT Action
This CDS view helps retrieve application log data of a particular JIT call. This CDS view provides the data to answer the following business questions: Which action has been performed on the JIT call along with the Fiori ID and Fiori application name? Against what application object and subobject has the action has been performed? This CDS view is enabled for both key user app extensibility and developer extensibility. To help you decide which CDS view to use for your purposes, SAP has introduced the annotation ObjectModel.supportedCapabilities that indicates the most appropriate use cases for each CDS view. To find out what use cases are best supported by this CDS view, access the entry of the CDS view in the View Browser app and find the values for this annotation under the Annotation tab. For more information, see Supported Capabilities for CDS Views .
Prerequisites
Authorizations Users who want to use this CDS view can have a role with the following restriction types set to read access: Restriction Type ID Restriction Type Comments SALES_AREA Sales Area User must have this restriction type to access JIT call data BEGRU_KNA1 Authorization Group for Customers This depends on the user profile You can use the Display Restriction Types app to find out in which business catalogs these restriction types are included. Users who want to use this CDS view can have the following authorization objects assigned: Authorization Object ID Authorization Object Comments JIT_INB_CO JIT Supply to Customer: Process inbound calls This authorization object must be assigned to the user to access JIT call data F_KNA1_BED Customer: Account Authorization Needed only if the user wants to see JIT calls for a blocked customer
Structure
Important Fields Important fields in this view include the following: Field Name Description JITCallActionLogUUID JIT Call Action Log UUID JITHeaderUUID JIT Call Header UUID JITCallCompGrpUUID JIT Call Component Group UUID ApplicationLogObject Application Log: Object ApplicationLogSubobject Application Log: Sub object JITCallProcessingLogID Application Log: External Identification JITFioriApplicationName JIT Fiori application name JITCallActionSource Action log: Action source JITAction JIT Action JITCallActionStatus Status Type TriggeredByUser Application log: user name CreationDateTime UTC Time Stamp in Long Form (YYYYMMDDhhmmssmmmuuun) JITFioriID Fiori ID for Just-in-Time Application JITApplicationLogHandle Application Log: Log Handle JITApplicationLogSeverity Indicates severity of the application logs JITActionLogAdditionalNote Additional note for JIT action logs JITPreIntProcessingStatus Previous Internal Processing Status JITPostIntProcessingStatus After Internal Processing Status JITFrameAction JIT Action
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| njit_call_d_alog | njit_call_d_alog | from |
Associations (8)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..1] | I_JITInboundCall | _JITInboundCall | $projection.JITHeaderUUID = _JITInboundCall.JITHeaderUUID |
| [0..1] | I_UserContactCard | _ProcessedByUser | $projection.TriggeredByUser = _ProcessedByUser.ContactCardID |
| [0..1] | I_JITAction | _JITAction | $projection.JITAction = _JITAction.JITAction |
| [0..1] | I_JITCallActionSource | _JITCallActionSource | $projection.JITCallActionSource = _JITCallActionSource.JITCallActionSource |
| [0..1] | I_JITCallActionStatus | _JITCallActionStatus | $projection.JITCallActionStatus = _JITCallActionStatus.JITCallActionStatus |
| [0..1] | I_JITApplicationID | _JITApplicationID | $projection.JITFioriID = _JITApplicationID.JITFioriID |
| [0..1] | I_JITInternalStatus | _JITPreInternalStatus | $projection.JITPreIntProcessingStatus = _JITPreInternalStatus.JITIntProcessingStatus |
| [0..1] | I_JITInternalStatus | _JITPostInternalStatus | $projection.JITPostIntProcessingStatus = _JITPostInternalStatus.JITIntProcessingStatus |
Annotations (12)
| Name | Value | Level | Field |
|---|---|---|---|
| AccessControl.authorizationCheck | #MANDATORY | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| Analytics.internalName | #LOCAL | view | |
| EndUserText.label | JIT Inbound Call Action Log | view | |
| Metadata.allowExtensions | true | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_DIMENSION | view | |
| ObjectModel.representativeKey | JITCallActionLogUUID | view | |
| ObjectModel.sapObjectNodeType.name | JITInbCallActionLog | view | |
| ObjectModel.usageType.dataClass | #TRANSACTIONAL | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #XXL | view | |
| VDM.viewType | #BASIC | view |
Fields (28)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | JITCallActionLogUUID | db_key | UUID | |
| JITHeaderUUID | root_key | UUID | ||
| JITCallCompGrpUUID | parent_key | UUID | ||
| ApplicationLogObject | object | TRFM Object | ||
| ApplicationLogSubobject | subobject | Triggering obj. | ||
| JITCallProcessingLogID | ||||
| JITFioriApplicationName | fiori_application_name | Short text | ||
| JITCallActionSource | action_source | Action source | ||
| JITAction | action_code | Single-Character Flag | ||
| JITCallActionStatus | action_status | Upload Status | ||
| TriggeredByUser | aluser | User | ||
| CreationDateTime | crea_date_time | Time Stamp | ||
| JITFioriID | jitfioriid | Fiori ID | ||
| JITApplicationLogHandle | jitapplicationloghandle | Handle | ||
| JITApplicationLogSeverity | jitapplicationlogseverity | Appl Log Severity | ||
| JITActionLogAdditionalNote | jitactionlogadditionalnote | |||
| JITPreIntProcessingStatus | jitpreintprocessingstatus | Intl Proc. Status | ||
| JITPostIntProcessingStatus | jitpostintprocessingstatus | Intl Proc. Status | ||
| JITFrameAction | jitframeaction | Action | ||
| _JITInbCallComponentGroup | _JITInbCallComponentGroup | |||
| _JITInboundCall | _JITInboundCall | |||
| _ProcessedByUser | _ProcessedByUser | |||
| _JITAction | _JITAction | |||
| _JITCallActionSource | _JITCallActionSource | |||
| _JITCallActionStatus | _JITCallActionStatus | |||
| _JITApplicationID | _JITApplicationID | |||
| _JITPreInternalStatus | _JITPreInternalStatus | |||
| _JITPostInternalStatus | _JITPostInternalStatus |
Derived SQL interpretation, reconstructed from the parsed view metadata (data sources, associations, and field mappings). SAP annotations are omitted and the structure is reformulated as SQL — this is a functional approximation, not the verbatim SAP source.
-- Derived SQL interpretation of CDS view I_JITInbCallActionLog.
-- Reconstructed from parsed metadata (data sources, associations, fields).
-- SAP annotations are omitted and the structure is reformulated as SQL;
-- this is a functional approximation, not the verbatim SAP source. Some join
-- conditions may be unavailable and a few CDS constructs are kept as-is.
CREATE VIEW I_JITInbCallActionLog AS
SELECT
db_key AS JITCallActionLogUUID,
root_key AS JITHeaderUUID,
parent_key AS JITCallCompGrpUUID,
object AS ApplicationLogObject,
subobject AS ApplicationLogSubobject,
ltrim( lognumber , '0') AS JITCallProcessingLogID,
fiori_application_name AS JITFioriApplicationName,
action_source AS JITCallActionSource,
action_code AS JITAction,
action_status AS JITCallActionStatus,
aluser AS TriggeredByUser,
crea_date_time AS CreationDateTime,
JITFioriID,
JITApplicationLogHandle,
JITApplicationLogSeverity,
JITActionLogAdditionalNote,
JITPreIntProcessingStatus,
JITPostIntProcessingStatus,
JITFrameAction
FROM njit_call_d_alog
LEFT OUTER JOIN I_JITInboundCall AS _JITInboundCall ON JITHeaderUUID = _JITInboundCall.JITHeaderUUID -- association [1..1]
LEFT OUTER JOIN I_UserContactCard AS _ProcessedByUser ON TriggeredByUser = _ProcessedByUser.ContactCardID -- association [0..1]
LEFT OUTER JOIN I_JITAction AS _JITAction ON JITAction = _JITAction.JITAction -- association [0..1]
LEFT OUTER JOIN I_JITCallActionSource AS _JITCallActionSource ON JITCallActionSource = _JITCallActionSource.JITCallActionSource -- association [0..1]
LEFT OUTER JOIN I_JITCallActionStatus AS _JITCallActionStatus ON JITCallActionStatus = _JITCallActionStatus.JITCallActionStatus -- association [0..1]
LEFT OUTER JOIN I_JITApplicationID AS _JITApplicationID ON JITFioriID = _JITApplicationID.JITFioriID -- association [0..1]
LEFT OUTER JOIN I_JITInternalStatus AS _JITPreInternalStatus ON JITPreIntProcessingStatus = _JITPreInternalStatus.JITIntProcessingStatus -- association [0..1]
LEFT OUTER JOIN I_JITInternalStatus AS _JITPostInternalStatus ON JITPostIntProcessingStatus = _JITPostInternalStatus.JITIntProcessingStatus -- association [0..1]
;
Learn More
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- CDS View Annotations — A Complete Guide
- What Is a CDS View in SAP S/4HANA?
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- CDS View Field Mapping and Associations
- Understanding the SAP S/4HANA Data Model
- CDS View Extensions and Custom Fields in SAP S/4HANA
- Released APIs and Stability Contracts in SAP S/4HANA
- 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
- BW Extractor to CDS View Migration Guide
- S/4HANA CDS View Deprecation: What You Need to Know
- ABAP CDS View Tutorial — From Basics to Real-World Examples
- RAP and CDS Views — Building Transactional Apps in SAP S/4HANA
- Sales Document Status Migration: VBUP/VBUK Removal in S/4HANA
- CO Tables in S/4HANA: COEP, COBK, COSS, COSP to ACDOCA