I_LogicalSystem
Logical System
I_LogicalSystem is a Basic CDS View (Dimension) that provides data about "Logical System" in SAP S/4HANA. It reads from 1 data source (tbdls) and exposes 2 fields with key field LogicalSystem. It has 1 association to related views. It is exposed through 9 OData services (FARR_BUSINESS_RECNCLN, UI_ACCRUALS_MANAGE, UI_ACCRUALS_PERDCAMT_MANAGE, ...). It is used in 3 Fiori applications: Business Reconciliation, Timesheet Analytics - Activities (S/4HANA), Timesheet Analytics - My Activities (S/4HANA).
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| tbdls | tbdls | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_LogicalSystemText | _Text | $projection.LogicalSystem = _Text.LogicalSystem |
Annotations (11)
| Name | Value | Level | Field |
|---|---|---|---|
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.representativeKey | LogicalSystem | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #C | view | |
| ObjectModel.usageType.sizeCategory | #L | view | |
| AbapCatalog.sqlViewName | ILOGICALSYSTEM | view | |
| EndUserText.label | Logical System | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| Analytics.dataExtraction.enabled | true | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| VDM.viewType | #BASIC | view |
OData Services (9)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| FARR_BUSINESS_RECNCLN | FARR_BUSINESS_RECNCLN | V2 | C1 | NOT_RELEASED |
| UI_ACCRUALS_MANAGE | UI_ACCRUALS_MANAGE | V2 | C1 | NOT_RELEASED |
| UI_ACCRUALS_PERDCAMT_MANAGE | UI_ACCRS_PERDCAMT_MANAGE | V2 | C1 | NOT_RELEASED |
| UI_HCMACTUALACTIVITIES | UI_HCMACTUALACTIVITIES | V2 | C1 | NOT_RELEASED |
| UI_HCMACTUALACTIVITIES_EMP | UI_HCMACTUALACTIVITIES_EMP | V2 | C1 | NOT_RELEASED |
| UI_HCMCOMPLIANCE | UI_HCMCOMPLIANCE_V2 | V2 | C1 | NOT_RELEASED |
| UI_HCMCOMPLIANCE_EMP | UI_HCMCOMPLIANCE_EMP_V2 | V2 | C1 | NOT_RELEASED |
| UI_INBOUNDDELIVERYMANAGE | UI_INBOUNDDELIVERYMANAGE | V4 | C1 | NOT_RELEASED |
| UI_PURCHASEORDERACCRS_DISPLAY | UI_PURCHASEORDERACCRS_DSP | V2 | C1 | NOT_RELEASED |
Fiori Apps (3)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F4830 | Business Reconciliation | Transactional | Revenue Accountant can use this application to do reconciliation between sender components and revenue accounting engine side. |
| F6687 | Timesheet Analytics - Activities (S/4HANA) | Analytical | Analytical app that allows Manager or Time Administrator to drill down on activities by various dimensions |
| F7189 | Timesheet Analytics - My Activities (S/4HANA) | Analytical | Analytical app that allows Employee to drill down on activities by various dimensions |
Business Reconciliation
Business Role: Revenue Accountant
You can have close integration with the universal journal by posting directly to the universal journal without persistence of the Revenue Accounting (RAR) subledger. The benefits of direct posting are the following:A simplified process for small- and medium-volume business scenarios When direct posting is used, no RAR subledger is used, and this leads to reduced reconciliation effort. A reduction in the number of period-end batch jobs required to execute the Transfer Revenue transaction for time-based revenues and the Calculate Contract Liabilities and Contract Assets transaction
Timesheet Analytics - Activities (S/4HANA)
Business Role: Manager - HR Info
With this feature, you as an authorized user can view all timesheet records within your area of responsibility. You can also analyze the timesheet records based on different attributes such as attendance or absence type, cost center, project, network or controlling area, for example.
Timesheet Analytics - My Activities (S/4HANA)
Business Role: Employee - HR Info
With this feature, you as an employee can view all of your timesheet records. You can also analyze the timesheet records based on different attributes such as attendance or absence type, cost center, project, network or controlling area, for example.
Fields (2)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | LogicalSystem | logsys | ||
| _Text | _Text |
@ClientHandling.algorithm: #SESSION_VARIABLE //Inserted by VDM CDS Suite Plugin
@ObjectModel.representativeKey: 'LogicalSystem'
@ObjectModel.usageType.dataClass: #CUSTOMIZING
@ObjectModel.usageType.serviceQuality: #C
@ObjectModel.usageType.sizeCategory: #L
@AbapCatalog.sqlViewName: 'ILOGICALSYSTEM'
@EndUserText.label: 'Logical System'
@Analytics : {dataCategory: #DIMENSION, dataExtraction.enabled : true}
@AccessControl.authorizationCheck: #NOT_REQUIRED
@VDM.viewType: #BASIC
define view I_LogicalSystem
as select from tbdls
association [0..*] to I_LogicalSystemText as _Text on $projection.LogicalSystem = _Text.LogicalSystem
{
@ObjectModel.text.association: '_Text'
key logsys as LogicalSystem,
_Text
}
Learn More
- What Is a CDS View in SAP S/4HANA?
- Types of CDS Views: Basic, Composite, Consumption, and Transactional
- SAP Tables vs CDS Views — Key Differences
- Understanding Data Lineage in SAP S/4HANA
- VDM (Virtual Data Model) in SAP S/4HANA Explained
- CDS View Annotations — A Complete Guide
- 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