C_ManageJournalEntryLedger

DDL: C_MANAGEJOURNALENTRYLEDGER Type: view_entity CONSUMPTION

Journal Entry Ledger

C_ManageJournalEntryLedger is a Consumption CDS View that provides data about "Journal Entry Ledger" in SAP S/4HANA. It reads from 1 data source (R_ManageJournalEntryLedger) and exposes 8 fields with key fields IsStatisticalDocument, SourceLedger, CompanyCode, FiscalYear, AccountingDocument. It has 1 association to related views. It is exposed through 1 OData service (UI_JOURNALENTRY_MANAGE). It is used in 1 Fiori application: Manage Journal Entries - New Version.

Data Sources (1)

SourceAliasJoin Type
R_ManageJournalEntryLedger _Item from

Associations (1)

CardinalityTargetAliasCondition
[1..1] I_Ledger _Ledger $projection.SourceLedger = _Ledger.Ledger

Annotations (7)

NameValueLevelField
AccessControl.authorizationCheck #MANDATORY view
EndUserText.label Journal Entry Ledger view
Metadata.ignorePropagatedAnnotations true view
ObjectModel.usageType.serviceQuality #C view
ObjectModel.usageType.sizeCategory #XXL view
ObjectModel.usageType.dataClass #MIXED view
VDM.viewType #CONSUMPTION view

OData Services (1)

ServiceBindingVersionContractRelease
UI_JOURNALENTRY_MANAGE UI_JOURNALENTRY_MANAGE V2 C1 NOT_RELEASED

Fiori Apps (1)

App IDApp NameTypeDescription
F0717A Manage Journal Entries - New Version Transactional With this app you can analyze journal entries, create reversals or make adjustments.

Manage Journal Entries - New Version

Business Role: General Ledger Accountant

With this app, you can manage and analyze journal entries. You can find, filter, sort, and group journal entries according to the requirements of your business. The app is your entry point for many important journal entry management functions, allowing you to create, copy, verify, edit, and reverse entries. Additionally, you can initiate correspondence, analyze change and reversal logs, and display entries in t-account views or document flows. You navigate to the details of individual journal entries to display more information, such as transaction data, line items, associated journal entries, and other related documents.

Fields (8)

KeyFieldSource TableSource FieldDescription
KEY IsStatisticalDocument R_ManageJournalEntryLedger IsStatisticalDocument
KEY SourceLedger R_ManageJournalEntryLedger SourceLedger
KEY CompanyCode R_ManageJournalEntryLedger CompanyCode
KEY FiscalYear R_ManageJournalEntryLedger FiscalYear
KEY AccountingDocument R_ManageJournalEntryLedger AccountingDocument
LedgerName
IsLeadingLedger _Ledger IsLeadingLedger
IsDefaultValue
@AbapCatalog.viewEnhancementCategory: [#NONE]
@AccessControl.authorizationCheck: #MANDATORY
@EndUserText.label: 'Journal Entry Ledger'
@Metadata.ignorePropagatedAnnotations: true
@ObjectModel.usageType:{
  serviceQuality: #C,
  sizeCategory: #XXL,
  dataClass: #MIXED
}

@VDM.viewType: #CONSUMPTION

define view entity C_ManageJournalEntryLedger
  as select from R_ManageJournalEntryLedger as _Item
  
  association [1..1] to I_Ledger              as _Ledger                        on $projection.SourceLedger = _Ledger.Ledger
{ 
  @Environment.sql.passValue: true
  @Semantics.booleanIndicator
  key _Item.IsStatisticalDocument,
  @ObjectModel.text.element:  [ 'LedgerName' ]
  @UI.textArrangement: #TEXT_LAST
  key _Item.SourceLedger,
  key _Item.CompanyCode,
  key _Item.FiscalYear,
  key _Item.AccountingDocument,
  
  @Semantics.text: true
  @UI.hidden: true
  _Ledger._Text[1:Language = $session.system_language].LedgerName,
  
  _Ledger.IsLeadingLedger,
  
  @ObjectModel.virtualElement: true
  @ObjectModel.virtualElementCalculatedBy: 'ABAP:CL_MJE_DEFAULT_LEDGER_CALC'
  @Semantics.booleanIndicator
  //@UI.hidden: true  

  cast('' as abap.char(1)) as IsDefaultValue
      
}