CORE_DATEFUNCTION
Get Details of all Date Functions
CORE_DATEFUNCTION is a CDS View that provides data about "Get Details of all Date Functions" in SAP S/4HANA. It reads from 1 data source (datefunction) and exposes 11 fields with key field id. It has 2 associations to related views.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| datefunction | datefunction | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..*] | CORE_DATEFUNCTION_TEXT | _Text | datefunction.id = _Text.id |
| [1] | DATEFUNCTION_SIMULATE_QUERY | _SimulatedTimePeriod | datefunction.id = _SimulatedTimePeriod.id |
Annotations (5)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | COREDATEFUNC | view | |
| EndUserText.label | Get Details of all Date Functions | view | |
| ObjectModel.usageType.serviceQuality | #P | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view |
Fields (11)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | id | id | ||
| type | type | |||
| granularity | granularity | |||
| calendartype | calendartype | |||
| startoffset | startoffset | |||
| startpoint | startpoint | |||
| endfixeddate | endfixeddate | |||
| endoffset | endoffset | |||
| endpoint | endpoint | |||
| _Text | _Text | |||
| _SimulatedTimePeriod | _SimulatedTimePeriod |
@AbapCatalog.sqlViewName: 'COREDATEFUNC'
@EndUserText.label: 'Get Details of all Date Functions'
@ObjectModel.usageType.serviceQuality: #P
@ClientHandling.algorithm: #SESSION_VARIABLE
@AccessControl.authorizationCheck: #NOT_REQUIRED
// CDS Test Double - GTD_CORE_DATEFUNCTION
define view CORE_DATEFUNCTION
as select from datefunction
association [1..*] to CORE_DATEFUNCTION_TEXT as _Text on datefunction.id = _Text.id
association [1] to DATEFUNCTION_SIMULATE_QUERY as _SimulatedTimePeriod on datefunction.id = _SimulatedTimePeriod.id
{
key id,
/*
* Object namespace - 1 (SAP content), 2 (Customer content).
* 1) ABAP Language Version values '2' (ABAP for Key Users) and '5' (ABAP for Cloud Development) are for customer content.
* 2) Use older logic as fallback and check the ID prefixes if objects are custom ones (YY*, YZ* and Z*).
* 3) For Standard ABAP Language Version (' ') and for null cases, mark as predefined.
*/
case when abap_language_version = '2' or abap_language_version = '5' then 2
when id like 'YY%' or id like 'YZ%' or id like 'Z%' then 2
else 1
end as datefunctiontype,
type,
granularity,
calendartype,
startfixeddate,
startoffset,
startoffsetunit,
startrelativeoffsetunit,
startpoint,
startrelativeoffset,
startyearoffset,
endfixeddate,
endoffset,
endoffsetunit,
endrelativeoffsetunit,
endpoint,
endrelativeoffset,
endyearoffset,
/* Associations */
_Text,
_SimulatedTimePeriod
}
/*+[internal] {
"BASEINFO":
{
"FROM":
[
"DATEFUNCTION"
],
"ASSOCIATED":
[
"CORE_DATEFUNCTION_TEXT",
"DATEFUNCTION_SIMULATE_QUERY"
],
"BASE":
[],
"ANNO_REF":
[],
"SCALAR_FUNCTION":
[],
"VERSION":0,
"ANNOREF_EVALUATION_ERROR":""
}
}*/
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