C_JITInbCallActionLogTP

DDL: C_JITINBCALLACTIONLOGTP Type: view_entity CONSUMPTION Package: NJIT_APP_MANAGE_JIT_CALLS

JIT Call Action Log

C_JITInbCallActionLogTP is a Consumption CDS View that provides data about "JIT Call Action Log" in SAP S/4HANA. It reads from 1 data source (R_JITInbCallActionLogTP) and exposes 26 fields with key field JITCallActionLogUUID. It is exposed through 1 OData service (NJIT_UI_JITINBOUNDCALLTP). It is used in 1 Fiori application: Manage Customer JIT Calls - Create, Manage. Part of development package NJIT_APP_MANAGE_JIT_CALLS.

Data Sources (1)

SourceAliasJoin Type
R_JITInbCallActionLogTP R_JITInbCallActionLogTP projection

Annotations (8)

NameValueLevelField
AccessControl.authorizationCheck #CHECK view
EndUserText.label JIT Call Action Log view
ObjectModel.usageType.dataClass #MIXED view
ObjectModel.usageType.serviceQuality #C view
ObjectModel.usageType.sizeCategory #XXL view
UI.headerInfo.typeName Action Log view
UI.headerInfo.typeNamePlural Action Logs view
VDM.viewType #CONSUMPTION view

OData Services (1)

ServiceBindingVersionContractRelease
NJIT_UI_JITINBOUNDCALLTP NJIT_UI_JITINBOUNDCALLTP V2 C1 NOT_RELEASED

Fiori Apps (1)

App IDApp NameTypeDescription
F6078 Manage Customer JIT Calls - Create, Manage Transactional An application to manage and monitor Customer JIT calls

Manage Customer JIT Calls - Create, Manage

Business Role: Material Planner - Just-In-Time Supply

With this app you can create, modify, and view JIT calls received in the system. Customers request components from suppliers by triggering JIT calls with all relevant component information. They do this by transmitting IDocs that get routed via SAP Cloud Platform Integration and get mapped to the JIT Call SOAP service, which then sends it to your system. The architecture guidelines of SAP S/4HANA Cloud recommend SOAP messages for Electronic Data Interchange (EDI) communication; for more information, refer to the integration documentation for Just-In-Time (JIT) Supply to Customer from Stock. Therefore, a SOAP message is defined for processing incoming customer JIT calls. A customer message can contain many individual JIT calls, among which there could be new ones or existing ones to be changed.

Fields (26)

KeyFieldSource TableSource FieldDescription
KEY JITCallActionLogUUID JITCallActionLogUUID
JITHeaderUUID JITHeaderUUID NodeID
JITCallCompGrpUUID JITCallCompGrpUUID NodeID
ApplicationLogObject ApplicationLogObject
ApplicationLogSubobject ApplicationLogSubobject
JITCallProcessingLogID JITCallProcessingLogID
JITCallActionStatus JITCallActionStatus Status Type
int1
JITAction JITAction Action
JITActionDescription
JITCallActionStatusDesc
JITCallActionSourceDesc
TriggeredByUser TriggeredByUser User Name
FullName _ProcessedByUser FullName Name
CreationDateTime CreationDateTime Executed On
JITCallActionSource JITCallActionSource Action source
JITFioriID JITFioriID Action Source ID
JITFioriApplicationName
JITActionLogAdditionalNote JITActionLogAdditionalNote
JITPreIntProcessingStatus JITPreIntProcessingStatus Intl Proc. Status
JITPostIntProcessingStatus JITPostIntProcessingStatus Intl Proc. Status
JITFrameAction JITFrameAction Action
JITPreIntProcessingStatusText
JITPostIntProcessingStatusText
_JITActionText _JITActionText
_ProcessedByUser _ProcessedByUser

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 C_JITInbCallActionLogTP.
-- 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 C_JITInbCallActionLogTP AS
SELECT
  JITCallActionLogUUID,
  JITHeaderUUID,
  JITCallCompGrpUUID,
  ApplicationLogObject,
  ApplicationLogSubobject,
  JITCallProcessingLogID,
  JITCallActionStatus,
  virtual JITActionLogStatusCriticality : abap.int1 AS int1,
  JITAction,
  _JITActionText[1: Language = $session.system_language].JITActionDescription AS JITActionDescription,
  _JITCallActionStatus._Text[1: Language = $session.system_language].JITCallActionStatusDesc AS JITCallActionStatusDesc,
  _JITCallActionSource._Text[1: Language = $session.system_language].JITCallActionSourceDesc AS JITCallActionSourceDesc,
  TriggeredByUser,
  _ProcessedByUser.FullName AS FullName,
  CreationDateTime,
  JITCallActionSource,
  JITFioriID,
  _JITApplicationID._Text[1: Language = $session.system_language].JITFioriApplicationName AS JITFioriApplicationName,
  JITActionLogAdditionalNote,
  JITPreIntProcessingStatus,
  JITPostIntProcessingStatus,
  JITFrameAction,
  _JITPreInternalStatus._Text[1: Language=$session.system_language].JITInternalStatusText AS JITPreIntProcessingStatusText,
  _JITPostInternalStatus._Text[1: Language=$session.system_language].JITInternalStatusText AS JITPostIntProcessingStatusText
FROM R_JITInbCallActionLogTP
;