I_ProfitCenterText
Profit Center - Text
I_ProfitCenterText is a Basic CDS View that provides data about "Profit Center - Text" in SAP S/4HANA. It reads from 1 data source (cepct) and exposes 10 fields with key fields Language, ControllingArea, ProfitCenter, 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. Part of development package FINS_PROFIT_CENTER_VDM.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| cepct | cepct | from |
Associations (3)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..1] | I_ControllingArea | _ControllingAreaText | $projection.ControllingArea = _ControllingAreaText.ControllingArea |
| [0..1] | I_Language | _Language | $projection.Language = _Language.Language |
| [0..1] | I_ControllingArea | _ControllingArea | $projection.ControllingArea = _ControllingArea.ControllingArea |
Annotations (17)
| Name | Value | Level | Field |
|---|---|---|---|
| EndUserText.label | Profit Center - Text | view | |
| Analytics.dataExtraction.enabled | true | view | |
| Analytics.dataExtraction.delta.changeDataCapture.automatic | true | view | |
| VDM.viewType | #BASIC | view | |
| AbapCatalog.sqlViewName | IFIPROFITCENTERT | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| ObjectModel.dataCategory | #TEXT | view | |
| ObjectModel.representativeKey | ProfitCenter | 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 | |
| Metadata.ignorePropagatedAnnotations | true | 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 | Language | cepct | spras | |
| KEY | ControllingArea | cepct | kokrs | |
| KEY | ProfitCenter | cepct | prctr | |
| KEY | ValidityEndDate | cepct | datbi | |
| ValidityStartDate | datab | |||
| ProfitCenterName | ||||
| ProfitCenterLongName | ||||
| _ControllingArea | _ControllingArea | |||
| _Language | _Language | |||
| _ControllingAreaText | _ControllingAreaText |
@EndUserText.label: 'Profit Center - Text'
@Analytics:{
dataExtraction: {
enabled: true,
delta.changeDataCapture: {
automatic: true
}
}
}
@VDM.viewType: #BASIC
@AbapCatalog.sqlViewName: 'IFIPROFITCENTERT'
@AbapCatalog.preserveKey: true
@AccessControl.authorizationCheck: #CHECK //NOT_REQUIRED
@ObjectModel.dataCategory: #TEXT
@ObjectModel.representativeKey: 'ProfitCenter'
@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
}
@Metadata.ignorePropagatedAnnotations: true
@Search.searchable: true
//--[ GENERATED:012:29JlHNUf7jY4ipE4XHfNBG
@AccessControl.privilegedAssociations: ['_ControllingAreaText']
// ]--GENERATED
@Consumption.filter.businessDate.at: true
define view I_ProfitCenterText
as select from cepct
left outer to one join cepc as _md on cepct.prctr = _md.prctr
and cepct.kokrs = _md.kokrs
and cepct.datbi = _md.datbi
//--[ GENERATED:012:29JlHNUf7jY4ipE4XHfNBG
association [0..1] to I_ControllingArea as _ControllingAreaText on $projection.ControllingArea = _ControllingAreaText.ControllingArea
// ]--GENERATED
association [0..1] to I_Language as _Language on $projection.Language = _Language.Language
association [0..1] to I_ControllingArea as _ControllingArea on $projection.ControllingArea = _ControllingArea.ControllingArea
{
@Semantics.language: true
@ObjectModel.foreignKey.association: '_Language'
key cepct.spras as Language,
//--[ GENERATED:012:29JlHNUf7jY4ipE4XHfNBG
@Consumption.valueHelpDefinition: [
{ entity: { name: 'I_ControllingArea',
element: 'ControllingArea' }
}]
@ObjectModel.text.association: '_ControllingAreaText'
// ]--GENERATED
@ObjectModel.foreignKey.association: '_ControllingArea'
key cepct.kokrs as ControllingArea,
@ObjectModel.text.element: ['ProfitCenterLongName', 'ProfitCenterName']
key cepct.prctr as ProfitCenter,
@Semantics.businessDate.to: true
key cepct.datbi as ValidityEndDate,
@Semantics.businessDate.from: true
datab as ValidityStartDate,
@Semantics.text: true
@Search.defaultSearchElement: true
@Search.fuzzinessThreshold: 0.8
@Search.ranking: #LOW
cast (ktext as fis_prctr_shorttext preserving type) as ProfitCenterName,
@Semantics.text: true
cast (ltext as fac_prctr_ltext preserving type ) as ProfitCenterLongName,
_ControllingArea,
_Language,
//--[ GENERATED:012:29JlHNUf7jY4ipE4XHfNBG
@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