I_LedgerText

DDL: I_LEDGERTEXT SQL: IFILEDGERT Type: view BASIC Package: FINS_LEDGER_VDM

Ledger - Text

I_LedgerText (Basic)

Package: Explore, extend and adapt the SAP S/4HANA Public Edition with built-in and side-by-side extension capabilities.

Accounting and Financial Close

I_LedgerText is a Basic CDS View that provides data about "Ledger - Text" in SAP S/4HANA. It reads from 1 data source (finsc_ledger_t) and exposes 4 fields with key fields Ledger, Language. It has 1 association to related views. It is exposed through 12 OData services (ASQL_F2129, ASQL_F2599, ASQL_F3548, ...). It is used in 1 Fiori application: Review Service Entry Sheet Accruals. Part of development package FINS_LEDGER_VDM.

SAP API Hub

CategoryBasic
StateC1
Line of BusinessAccounting and Financial Close
Application ComponentFI-GL-GL-A-2CL
CapabilitiesData Source for Data Extraction,Data Source for Defining CDS Entities,Language-Dependent Text,Association Target for Defining CDS Entities
Extensible (Key User)No
Extensible (Developer)No
Release State (Key User)Released
Release State (Developer)Released
PackageAccounting and Financial Close for SAP S/4HANA Cloud Public Edition
Description <p>This CDS view provides access to ledger names in different languages. This CDS view provides the prerequisites for answering the following business questions:</p> <ul> <li> <p>What is the ledger name in a specific language?</p> </li> </ul>

Documentation

Data Sources (1)

SourceAliasJoin Type
finsc_ledger_t finsc_ledger_t from

Associations (1)

CardinalityTargetAliasCondition
[0..1] I_Language _Language $projection.Language = _Language.Language

Annotations (14)

NameValueLevelField
EndUserText.label Ledger - Text view
ObjectModel.dataCategory #TEXT view
ObjectModel.representativeKey Ledger view
AccessControl.authorizationCheck #CHECK view
VDM.viewType #BASIC view
AbapCatalog.sqlViewName IFILEDGERT view
ClientHandling.algorithm #SESSION_VARIABLE view
Metadata.ignorePropagatedAnnotations true view
ObjectModel.usageType.serviceQuality #A view
ObjectModel.usageType.sizeCategory #M view
ObjectModel.usageType.dataClass #CUSTOMIZING view
AbapCatalog.preserveKey true view
Analytics.dataExtraction.enabled true view
ObjectModel.modelingPattern #LANGUAGE_DEPENDENT_TEXT view

OData Services (12)

ServiceBindingVersionContractRelease
ASQL_F2129 ASQL_F2129 C2 NOT_RELEASED
ASQL_F2599 ASQL_F2599 C2 NOT_RELEASED
ASQL_F3548 ASQL_F3548 C2 NOT_RELEASED
ASQL_F3756 ASQL_F3756 C2 NOT_RELEASED
ASQL_F4095 ASQL_F4095 C2 NOT_RELEASED
ASQL_F4185 ASQL_F4185 C2 NOT_RELEASED
ASQL_F4186 ASQL_F4186 C2 NOT_RELEASED
ASQL_F4363 ASQL_F4363 C2 NOT_RELEASED
ASQL_F5406 ASQL_F5406 C2 NOT_RELEASED
ASQL_F5407 ASQL_F5407 C2 NOT_RELEASED
ASQL_F6108 ASQL_F6108 C2 NOT_RELEASED
UI_SSACPERDCAMOUNTS_REVIEW UI_SSACPERDCAMOUNTS_REVIEW V2 C1 NOT_RELEASED

Fiori Apps (1)

App IDApp NameTypeDescription
F6108 Review Service Entry Sheet Accruals Transactional Review service entry sheet accrual amount for each period.

Review Service Entry Sheet Accruals

Business Role: Cost Accountant - Overhead

For service purchasing, you need to post accruals for costs that come from unapproved service entry sheets. A purchase order item could have multiple service entry sheets with different account assignments. The Service Entry Sheet Accruals application enables you to calculate and post accruals in General Ledger Accounting automatically. The relevant data can be transferred from Service Purchasing and Recording of the Materials Management component to the Accrual Engine and automatically converted from purchase order items into accrual subobjects. The system calculates the accruals for each account assignment specified in the items of service entry sheets. In each period, you can start an accrual run, which posts all accruals for the service transactions.

Fields (4)

KeyFieldSource TableSource FieldDescription
KEY Ledger rldnr Ledger in General Ledger Accounting
KEY Language langu Primary lang.
LedgerName name Ledger Name
_Language _Language

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_LedgerText.
-- 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.
-- SQL view name: IFILEDGERT

CREATE VIEW I_LedgerText AS
SELECT
  rldnr AS Ledger,
  langu AS Language,
  name AS LedgerName
FROM finsc_ledger_t
LEFT OUTER JOIN I_Language AS _Language ON Language = _Language.Language  -- association [0..1]
;