I_CostCenterText
Cost Center - Text
I_CostCenterText is a Basic CDS View that provides data about "Cost Center - Text" in SAP S/4HANA. It reads from 1 data source (cskt) and exposes 10 fields with key fields CostCenter, ControllingArea, Language, ValidityEndDate. It has 3 associations to related views. It is exposed through 1 OData service (UI_SSACPERDCAMOUNTS_REVIEW). It is used in 1 Fiori application: Review Service Entry Sheet Accruals.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| cskt | cskt | from |
Associations (3)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_ControllingArea | _ControllingAreaText | $projection.ControllingArea = _ControllingAreaText.ControllingArea |
| [0..1] | I_ControllingArea | _ControllingArea | $projection.ControllingArea = _ControllingArea.ControllingArea |
| [0..1] | I_Language | _Language | $projection.Language = _Language.Language |
Annotations (17)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Cost Center - Text | view | |
| Analytics.dataExtraction.enabled | true | view | |
| Analytics.dataExtraction.delta.changeDataCapture.automatic | true | view | |
| VDM.viewType | #BASIC | view | |
| AbapCatalog.sqlViewName | IFICOSTCENTERT | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| ObjectModel.dataCategory | #TEXT | view | |
| ObjectModel.representativeKey | CostCenter | view | |
| AbapCatalog.preserveKey | true | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.modelingPattern | #LANGUAGE_DEPENDENT_TEXT | view | |
| ObjectModel.usageType.dataClass | #MASTER | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #M | view | |
| Search.searchable | true | view | |
| Consumption.filter.businessDate.at | true | view |
OData Services (1)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_SSACPERDCAMOUNTS_REVIEW | UI_SSACPERDCAMOUNTS_REVIEW | V2 | C1 | NOT_RELEASED |
Fiori Apps (1)
| App ID | App Name | Type | Description |
|---|---|---|---|
| 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 (10)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | CostCenter | cskt | kostl | |
| KEY | ControllingArea | cskt | kokrs | |
| KEY | Language | cskt | spras | |
| KEY | ValidityEndDate | cskt | datbi | |
| ValidityStartDate | _md | datab | ||
| CostCenterName | ||||
| CostCenterDescription | ||||
| _ControllingArea | _ControllingArea | |||
| _Language | _Language | |||
| _ControllingAreaText | _ControllingAreaText |
@EndUserText.label: 'Cost Center - Text'
@Analytics:{
dataExtraction: {
enabled: true,
delta.changeDataCapture: {
automatic: true
}
}
}
@VDM.viewType: #BASIC
@AbapCatalog.sqlViewName: 'IFICOSTCENTERT'
@AccessControl.authorizationCheck: #CHECK //NOT_REQUIRED
@ObjectModel.dataCategory: #TEXT
@ObjectModel.representativeKey: 'CostCenter'
@AbapCatalog.preserveKey:true
@Metadata.ignorePropagatedAnnotations: true
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.modelingPattern: #LANGUAGE_DEPENDENT_TEXT
@ObjectModel.supportedCapabilities: [ #CDS_MODELING_DATA_SOURCE, #CDS_MODELING_ASSOCIATION_TARGET, #LANGUAGE_DEPENDENT_TEXT, #EXTRACTION_DATA_SOURCE ]
@ObjectModel.usageType: {
dataClass: #MASTER,
serviceQuality: #A,
sizeCategory: #M
}
@Search.searchable: true
//--[ GENERATED:012:29JlHNUf7jY4ioM8lnJMdG
@AccessControl.privilegedAssociations: ['_ControllingAreaText']
// ]--GENERATED
@Consumption.filter.businessDate.at: true
define view I_CostCenterText
as select from cskt
left outer to one join csks as _md on cskt.kostl = _md.kostl
and cskt.kokrs = _md.kokrs
and cskt.datbi = _md.datbi
//--[ GENERATED:012:29JlHNUf7jY4ioM8lnJMdG
association [0..1] to I_ControllingArea as _ControllingAreaText on $projection.ControllingArea = _ControllingAreaText.ControllingArea
// ]--GENERATED
association [0..1] to I_ControllingArea as _ControllingArea on $projection.ControllingArea = _ControllingArea.ControllingArea
association [0..1] to I_Language as _Language on $projection.Language = _Language.Language
{
@ObjectModel.text.element: 'CostCenterDescription'
key cskt.kostl as CostCenter,
//--[ GENERATED:012:29JlHNUf7jY4ioM8lnJMdG
@Consumption.valueHelpDefinition: [
{ entity: { name: 'I_ControllingAreaStdVH',
element: 'ControllingArea' }
}]
@ObjectModel.text.association: '_ControllingAreaText'
// ]--GENERATED
@ObjectModel.foreignKey.association: '_ControllingArea'
key cskt.kokrs as ControllingArea,
@Semantics.language: true
@ObjectModel.foreignKey.association: '_Language'
key cskt.spras as Language,
@Semantics.businessDate.to: true
key cskt.datbi as ValidityEndDate,
@Semantics.businessDate.from: true
_md.datab as ValidityStartDate,
@Semantics.text: true
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #HIGH
cast(cskt.ktext as fis_kostl_name preserving type) as CostCenterName,
@Semantics.text: true
cast(cskt.ltext as fis_kostl_ltext preserving type) as CostCenterDescription,
_ControllingArea,
_Language,
//--[ GENERATED:012:29JlHNUf7jY4ioM8lnJMdG
@Consumption.hidden: true
_ControllingAreaText
// ]--GENERATED
}
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