I_Division
Division
I_Division is a Basic CDS View (Dimension) that provides data about "Division" in SAP S/4HANA. It reads from 1 data source (tspa) and exposes 2 fields with key field Division. It has 1 association to related views. It is exposed through 11 OData services (C_BILLGDOCREDACTED_SD, C_SALESORDERMANAGE_SD, UI_CADOCUMENT_MNG, ...). It is used in 2 Fiori applications: Monitor Sales Order Progress - Fashion, Manage Provisional Sales Contracts - Fashion.
Data Sources (1)
| Source | Alias | Join Type |
|---|---|---|
| tspa | tspa | from |
Associations (1)
| Cardinality | Target | Alias | Condition |
|---|---|---|---|
| [0..*] | I_DivisionText | _Text | $projection.Division = _Text.Division |
Annotations (20)
| Name | Value | Level | Field |
|---|---|---|---|
| ClientHandling.algorithm | #SESSION_VARIABLE | view | |
| ObjectModel.representativeKey | Division | view | |
| ObjectModel.usageType.dataClass | #CUSTOMIZING | view | |
| ObjectModel.usageType.serviceQuality | #A | view | |
| ObjectModel.usageType.sizeCategory | #S | view | |
| EndUserText.label | Division | view | |
| Analytics.dataCategory | #DIMENSION | view | |
| VDM.viewType | #BASIC | view | |
| AccessControl.authorizationCheck | #NOT_REQUIRED | view | |
| AbapCatalog.sqlViewName | ISDDIVISION | view | |
| Search.searchable | true | view | |
| AbapCatalog.buffering.status | #ACTIVE | view | |
| AbapCatalog.buffering.type | #FULL | view | |
| AbapCatalog.compiler.compareFilter | true | view | |
| AbapCatalog.preserveKey | true | view | |
| Metadata.ignorePropagatedAnnotations | true | view | |
| Analytics.dataExtraction.enabled | true | view | |
| ObjectModel.modelingPattern | #ANALYTICAL_DIMENSION | view | |
| ObjectModel.sapObjectNodeType.name | Division | view | |
| ObjectModel.objectIdentifier.oidElement | DivisionOID | view |
OData Services (11)
| Service | Binding | Version | Contract | Release |
|---|---|---|---|---|
| C_BILLGDOCREDACTED_SD | C_BILLGDOCREDACTED | V2 | C1 | NOT_RELEASED |
| C_SALESORDERMANAGE_SD | C_SALESORDERMANAGE_SRV | V4 | C1 | NOT_RELEASED |
| UI_CADOCUMENT_MNG | UI_CADOCUMENT_MNG | V4 | C1 | NOT_RELEASED |
| UI_CREDITMEMOREQUESTMANAGE | UI_CREDITMEMOREQUESTMANAGE | V4 | C1 | NOT_RELEASED |
| UI_CUSTOMERRETURNMANAGE | UI_CUSTOMERRETURNMANAGE | V4 | C1 | NOT_RELEASED |
| UI_INBOUNDDELIVERYMANAGE | UI_INBOUNDDELIVERYMANAGE | V4 | C1 | NOT_RELEASED |
| UI_PRELIMBILLINGDOCUMENT_F6990 | UI_PRELIMBILLINGDOCUMENT_F6990 | V4 | C1 | NOT_RELEASED |
| UI_RFM_PRVSNLSLSCONTR | UI_RFM_PRVSNLSLSCONTR | V2 | C1 | NOT_RELEASED |
| UI_RFM_SLSORD_PRGS_MONITOR | UI_RFM_SLSORD_PRGS_MONITOR | V2 | C1 | NOT_RELEASED |
| UI_SALESCONTRACTMANAGE | UI_SALESCONTRACTMANAGE | V4 | C1 | NOT_RELEASED |
| UI_SALESQUOTATIONMANAGE | UI_SALESQUOTATIONMANAGE | V4 | 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 (2)
| Key | Field | Source Table | Source Field | Description |
|---|---|---|---|---|
| KEY | Division | spart | ||
| _Text | _Text |
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.representativeKey: 'Division'
@ObjectModel.usageType.dataClass: #CUSTOMIZING
@ObjectModel.usageType.serviceQuality: #A
@ObjectModel.usageType.sizeCategory: #S
@EndUserText.label: 'Division'
@Analytics.dataCategory: #DIMENSION
@VDM.viewType: #BASIC
@AccessControl.authorizationCheck: #NOT_REQUIRED
@AbapCatalog.sqlViewName: 'ISDDIVISION'
@Search.searchable: true
@AbapCatalog.buffering.status: #ACTIVE
@AbapCatalog.buffering.type: #FULL
@AbapCatalog.compiler.compareFilter: true
@AbapCatalog.preserveKey: true
@Metadata.ignorePropagatedAnnotations: true
@Analytics.dataExtraction.enabled: true
@ObjectModel.modelingPattern: #ANALYTICAL_DIMENSION
@ObjectModel.supportedCapabilities: [ #SQL_DATA_SOURCE,
#CDS_MODELING_DATA_SOURCE,
#CDS_MODELING_ASSOCIATION_TARGET,
#ANALYTICAL_DIMENSION,
#SEARCHABLE_ENTITY,
#EXTRACTION_DATA_SOURCE ]
@ObjectModel.alternativeKey: [{ id: 'OID', uniqueness: #UNIQUE, element: ['DivisionOID'] }]
@ObjectModel.sapObjectNodeType.name: 'Division'
@ObjectModel.objectIdentifier.oidElement:'DivisionOID'
define view I_Division
as select from tspa
left outer to one join mdi_oid_config
on mdi_oid_config.object_type_code = 'DRF_0050'
association [0..*] to I_DivisionText as _Text on $projection.Division = _Text.Division
{
@Search.defaultSearchElement: true
@Search.ranking: #HIGH
@Search.fuzzinessThreshold: 0.8
@ObjectModel.text.association: '_Text'
key spart as Division,
@ObjectModel.filter.enabled: false
@ObjectModel.sort.enabled: false
case
when mdi_oid_config.context is initial or mdi_oid_config.compose_oid is initial
then cast( spart as division_oid )
when mdi_oid_config.context is not initial and mdi_oid_config.compose_oid is not initial
then cast( concat( concat( mdi_oid_config.context, ':' ), spart ) as division_oid )
end as DivisionOID,
_Text
};
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