I_ServiceDocumentType
Service Transaction Type
I_ServiceDocumentType is a Basic CDS View (Dimension) that provides data about "Service Transaction Type" in SAP S/4HANA. It reads from 1 data source (crmc_proc_type) and exposes 10 fields with key field ServiceDocumentType. It has 2 associations to related views. It is exposed through 3 OData services (UI_BILLINGDOCUMENTFS, UI_HCMMYTIMESHEET, UI_HCMMYTIMESHEET). It is used in 2 Fiori applications: Billing Document, My Timesheet (S/4HANA / Version 4).
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| crmc_proc_type | crmc_proc_type | from |
Associations (2)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [1..*] | I_ServiceDocumentTypeText | _ServiceDocumentTypeText | $projection.ServiceDocumentType = _ServiceDocumentTypeText.ServiceDocumentType |
| [1..*] | I_BusinessObjTypeText | _ServiceObjectTypeText | $projection.ServiceObjectType = _ServiceObjectTypeText.BusinessObjectType |
Annotations (16)
| Name | Value | Level | Field |
|---|---|---|---|
| AbapCatalog.sqlViewName | ISERVDOCTYPE | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| AccessControl.authorizationCheck | #CHECK | view | |
| EndUserText.label | Service Transaction Type | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| VDM.viewType | #BASIC | view | |
| VDM.lifecycle.contract.type | #PUBLIC_LOCAL_API | view | |
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| ObjectModel.representativeKey | ServiceDocumentType | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| Metadata.allowExtensions | true | view | |
| ObjectModel.sapObjectNodeType.name | ServiceDocumentType | view |
OData Services (3)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_BILLINGDOCUMENTFS | UI_BILLINGDOCUMENTFS | V2 | C1 | NOT_RELEASED |
| UI_HCMMYTIMESHEET | API_HCMMYTIMESHEET | V2 | C2 | NOT_RELEASED |
| UI_HCMMYTIMESHEET | UI_HCMMYTIMESHEET | V2 | C1 | NOT_RELEASED |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F1901 | Billing Document | Fact sheet | The billing document object page displays contextual information about the billing document business object, bringing together all of the object's relevant attributes to provide you with an overview of the selected billing document. |
| F3074A | My Timesheet (S/4HANA / Version 4) | Transactional | You, as an employee, can use this app to manage your time entries quickly and efficiently using a desktop or a mobile device. |
Billing Document
Business Role: Billing Clerk
You can access this object page from the Enterprise Search for billing documents search results. It displays contextual information about the billing document business object, bringing together all of the object"s relevant attributes to provide you with an overview of the selected billing document. At the bottom of the page, you can choose the name of involved business partners to display their contact details.
My Timesheet (S/4HANA / Version 4)
Business Role: Employee - HR Info
You, as an employee, can use this app to manage your time entries quickly and efficiently using a desktop or a mobile device. You can use this app to do the following: enter time records for the chosen personnel assignment using form entry or assignments. create or import assignments and manage them. create and manage assignment groups. use horizontal or grid view for time entries. view the calendar for a chosen month on a desktop device, and for a given week on a mobile device. copy and paste time records. access the to-do list. switch between the allowed data entry profiles for a given time entry.
Fields (10)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | ServiceDocumentType | process_type | ||
| ServiceObjectType | object_type | |||
| CustMgmtServiceTeamProfile | service_team_profile | |||
| SrvcProcessStepOverviewProfile | proc_stp_ovw_prfl | |||
| ServiceDocumentTemplateType | template_type | |||
| SrvcDocTypeBlockingStatus | process_blocked | |||
| StatusProfile | user_stat_proc | |||
| SrvcRejectionReasonProfile | rejprofile | |||
| _ServiceDocumentTypeText | _ServiceDocumentTypeText | |||
| _ServiceObjectTypeText | _ServiceObjectTypeText |
@AbapCatalog:{
sqlViewName: 'ISERVDOCTYPE',
compiler.compareFilter: true,
preserveKey:true
}
@AccessControl.authorizationCheck: #CHECK
@EndUserText.label: 'Service Transaction Type'
@Analytics: { dataCategory: #DIMENSION }
@VDM: {
viewType: #BASIC,
lifecycle.contract.type: #PUBLIC_LOCAL_API
}
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.usageType.dataClass: #CUSTOMIZING
@ObjectModel.usageType.serviceQuality: #A
@ObjectModel.usageType.sizeCategory: #S
@ObjectModel.representativeKey: 'ServiceDocumentType'
@ObjectModel.supportedCapabilities: [ #ANALYTICAL_DIMENSION, #CDS_MODELING_ASSOCIATION_TARGET, #SQL_DATA_SOURCE, #CDS_MODELING_DATA_SOURCE ]
@Metadata.ignorePropagatedAnnotations: true
@Search.searchable
@Metadata.allowExtensions:true
//! Code list for the Service Transaction Type
@ObjectModel.sapObjectNodeType.name: 'ServiceDocumentType'
define view I_ServiceDocumentType
as select from crmc_proc_type
association [1..*] to I_ServiceDocumentTypeText as _ServiceDocumentTypeText on $projection.ServiceDocumentType = _ServiceDocumentTypeText.ServiceDocumentType
association [1..*] to I_BusinessObjTypeText as _ServiceObjectTypeText on $projection.ServiceObjectType = _ServiceObjectTypeText.BusinessObjectType
{
@Search: {
defaultSearchElement: true,
fuzzinessThreshold: 0.8,
ranking: #HIGH
}
@ObjectModel.text.association: '_ServiceDocumentTypeText'
key process_type as ServiceDocumentType,
@ObjectModel.text.association: '_ServiceObjectTypeText'
object_type as ServiceObjectType,
service_team_profile as CustMgmtServiceTeamProfile,
proc_stp_ovw_prfl as SrvcProcessStepOverviewProfile,
template_type as ServiceDocumentTemplateType,
process_blocked as SrvcDocTypeBlockingStatus,
user_stat_proc as StatusProfile,
rejprofile as SrvcRejectionReasonProfile,
_ServiceDocumentTypeText,
_ServiceObjectTypeText
}
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