I_SalesDocumentType
Sales Document Type
I_SalesDocumentType is a Basic CDS View (Dimension) that provides data about "Sales Document Type" in SAP S/4HANA. It reads from 1 data source (tvak) and exposes 21 fields with key field SalesDocumentType. It has 6 associations to related views. It is exposed through 2 OData services (UI_RFM_PRVSNLSLSCONTR, UI_RFM_SLSORD_PRGS_MONITOR). It is used in 2 Fiori applications: Monitor Sales Order Progress - Fashion, Manage Provisional Sales Contracts - Fashion.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| tvak | tvak | from |
Associations (6)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_SalesDocumentTypeText | _Text | $projection.SalesDocumentType = _Text.SalesDocumentType |
| [1..1] | I_SalesDocumentType | _OrderTypeForBillingRequest | $projection.OrderTypeForBillingRequest = _OrderTypeForBillingRequest.SalesDocumentType |
| [1..1] | I_DeliveryBlockReason | _DeliveryBlockReason | $projection.DeliveryBlockReason = _DeliveryBlockReason.DeliveryBlockReason |
| [0..1] | I_SDDocumentTextDetnProcedure | _TextDeterminationProcedure | $projection.TextDeterminationProcedure = _TextDeterminationProcedure.TextDeterminationProcedure |
| [0..1] | I_PartDeterminationProcedure | _PartDeterminationProcedure | $projection.PartnerDeterminationProcedure = _PartDeterminationProcedure.PartnerDeterminationProcedure |
| [0..*] | I_SalesDocumentTypeLangDepdnt | _SalesDocumentTypeLangDepdnt | $projection.SalesDocumentType = _SalesDocumentTypeLangDepdnt.SalesDocumentType |
Annotations (17)
| Name | Value | Level | Field |
|---|---|---|---|
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.representativeKey | SalesDocumentType | view | |
| ObjectModel.sapObjectNodeType.name | SalesDocumentType | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| EndUserText.label | Sales Document Type | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| VDM.viewType | #BASIC | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AbapCatalog.sqlViewName | ISDSALESDOCTYPE | view | |
| AbapCatalog.preserveKey | true | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.buffering.status | #ACTIVE | view | |
| AbapCatalog.buffering.type | #FULL | view | |
| Metadata.allowExtensions | true | view | |
| Metadata.ignorePropagatedAnnotations | true | view |
OData Services (2)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| UI_RFM_PRVSNLSLSCONTR | UI_RFM_PRVSNLSLSCONTR | V2 | C1 | NOT_RELEASED |
| UI_RFM_SLSORD_PRGS_MONITOR | UI_RFM_SLSORD_PRGS_MONITOR | V2 | C1 | NOT_RELEASED |
Fiori Apps (2)
| App ID | App Name | Type | Description |
|---|---|---|---|
| F5392 | Monitor Sales Order Progress - Fashion | Transactional | Monitor Sales Order Progress - Fashion : This app is used to track and further monitor for the different status of the Sales Orders and thereby further actions can be taken accordingly by the business, |
| F5398 | Manage Provisional Sales Contracts - Fashion | Transactional | Manage Provisional Sales Contracts - Fashion. This is used to create the special types of contracts and the call off |
Monitor Sales Order Progress - Fashion
Business Role: Order Fulfillment Specialist (Retail)
With this app, you can monitor the status, that is, the overall progress of account assigned sales orders. This application allows you to identify the conditions based on quantity and status. It checks for exceptions and helps you take informed decisions and necessary actions.
Manage Provisional Sales Contracts - Fashion
Business Role: Order Fulfillment Specialist (Retail)
With this app, you can display the provisional sales contract details at header and generic product levels, so you can get a complete view of different items in these contracts. You can also use this app to create provisional sales contracts as well as create subsequent orders (call-offs) for these contracts.
Fields (21)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | SalesDocumentType | auart | ||
| SDDocumentCategory | vbtyp | |||
| MandatoryReferenceSDDocCat | bezob | |||
| SalesDocumentProcessingType | vbklt | |||
| ScreenSequenceGroup | kopgr | |||
| OrderTypeForBillingRequest | aufak | |||
| DeliveryBlockReason | lifsk | |||
| IsLocked | sperr | |||
| RetsMgmtIsActive | msr_active | |||
| TradeComplianceIsActive | itmac | |||
| TextDeterminationProcedure | ||||
| PartnerDeterminationProcedure | ||||
| SlsDocProdProposalProcedure | pvbsm | |||
| NumberRangeForIntIDAssignment | numki | |||
| NumberRangeForExtIDAssignment | numke | |||
| _Text | _Text | |||
| _OrderTypeForBillingRequest | _OrderTypeForBillingRequest | |||
| _SalesDocumentTypeLangDepdnt | _SalesDocumentTypeLangDepdnt | |||
| _DeliveryBlockReason | _DeliveryBlockReason | |||
| _TextDeterminationProcedure | _TextDeterminationProcedure | |||
| _PartDeterminationProcedure | _PartDeterminationProcedure |
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.representativeKey: 'SalesDocumentType'
@ObjectModel.sapObjectNodeType.name: 'SalesDocumentType'
@ObjectModel.usageType.dataClass: #CUSTOMIZING
@ObjectModel.usageType.serviceQuality: #A
@ObjectModel.usageType.sizeCategory: #S
@ObjectModel.supportedCapabilities: [ #ANALYTICAL_DIMENSION, #CDS_MODELING_ASSOCIATION_TARGET, #SQL_DATA_SOURCE, #CDS_MODELING_DATA_SOURCE ]
@ObjectModel.modelingPattern: [ #ANALYTICAL_DIMENSION ]
@EndUserText.label: 'Sales Document Type'
@Analytics: { dataCategory: #DIMENSION}
@VDM.viewType: #BASIC
@AccessControl.authorizationCheck:#NOT_REQUIRED
@AbapCatalog.sqlViewName: 'ISDSALESDOCTYPE'
@AbapCatalog.preserveKey: true
@AbapCatalog.compiler.compareFilter:true
@AbapCatalog.buffering.status: #ACTIVE
@AbapCatalog.buffering.type: #FULL
@Metadata.allowExtensions: true
@Metadata.ignorePropagatedAnnotations:true
define view I_SalesDocumentType
as select from tvak
association [0..*] to I_SalesDocumentTypeText as _Text on $projection.SalesDocumentType = _Text.SalesDocumentType
association [1..1] to I_SalesDocumentType as _OrderTypeForBillingRequest on $projection.OrderTypeForBillingRequest = _OrderTypeForBillingRequest.SalesDocumentType
association [1..1] to I_DeliveryBlockReason as _DeliveryBlockReason on $projection.DeliveryBlockReason = _DeliveryBlockReason.DeliveryBlockReason
association [0..1] to I_SDDocumentTextDetnProcedure as _TextDeterminationProcedure on $projection.TextDeterminationProcedure = _TextDeterminationProcedure.TextDeterminationProcedure
association [0..1] to I_PartDeterminationProcedure as _PartDeterminationProcedure on $projection.PartnerDeterminationProcedure = _PartDeterminationProcedure.PartnerDeterminationProcedure
association [0..*] to I_SalesDocumentTypeLangDepdnt as _SalesDocumentTypeLangDepdnt on $projection.SalesDocumentType = _SalesDocumentTypeLangDepdnt.SalesDocumentType
{
@ObjectModel.text.association: '_Text'
key auart as SalesDocumentType,
vbtyp as SDDocumentCategory,
bezob as MandatoryReferenceSDDocCat,
vbklt as SalesDocumentProcessingType,
kopgr as ScreenSequenceGroup,
@ObjectModel.foreignKey.association: '_OrderTypeForBillingRequest'
aufak as OrderTypeForBillingRequest,
@Analytics.internalName: #LOCAL
@ObjectModel.foreignKey.association: '_DeliveryBlockReason'
lifsk as DeliveryBlockReason,
sperr as IsLocked,
msr_active as RetsMgmtIsActive,
itmac as TradeComplianceIsActive,
@Analytics.internalName: #LOCAL
@ObjectModel.foreignKey.association: '_TextDeterminationProcedure'
cast(txtgr as sls_doc_text_detn_head preserving type ) as TextDeterminationProcedure,
@Analytics.internalName: #LOCAL
@ObjectModel.foreignKey.association: '_PartDeterminationProcedure'
cast(pargr as sls_doc_partner_detn_head preserving type ) as PartnerDeterminationProcedure,
pvbsm as SlsDocProdProposalProcedure,
numki as NumberRangeForIntIDAssignment,
numke as NumberRangeForExtIDAssignment,
//Association
_Text,
_OrderTypeForBillingRequest,
_SalesDocumentTypeLangDepdnt,
_DeliveryBlockReason,
_TextDeterminationProcedure,
_PartDeterminationProcedure
};
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