I_PurchasingGroup

DDL: I_PURCHASINGGROUP SQL: IMMPURCHGROUP Type: view BASIC

Purchasing Group

I_PurchasingGroup is a Basic CDS View (Dimension) that provides data about "Purchasing Group" in SAP S/4HANA. It reads from 1 data source (t024) and exposes 7 fields with key field PurchasingGroup. It is exposed through 3 OData services (UI_RFM_PO_MNG, UI_SOURCING_PROJECT_COMPARE, UI_SSACPERDCAMOUNTS_REVIEW). It is used in 2 Fiori applications: Manage Purchase Orders - Fashion, Review Service Entry Sheet Accruals.

1 data source(s) Exposed by 3 service(s) Used in 2 Fiori app(s) 7 fields

Data Sources (1)

SourceAliasJoin Type
t024 t024 from

Annotations (17)

NameValueLevelField
ClientHandling.algorithm #SESSION_VARIABLE view
ObjectModel.representativeKey PurchasingGroup view
ObjectModel.usageType.dataClass #CUSTOMIZING view
ObjectModel.usageType.serviceQuality #A view
ObjectModel.usageType.sizeCategory #S view
ObjectModel.sapObjectNodeType.name PurchasingGroup view
AbapCatalog.sqlViewName IMMPURCHGROUP view
AbapCatalog.preserveKey true view
EndUserText.label Purchasing Group view
Analytics.dataCategory #DIMENSION view
VDM.viewType #BASIC view
VDM.lifecycle.contract.type #PUBLIC_LOCAL_API view
Analytics.dataExtraction.enabled true view
Search.searchable true view
Metadata.allowExtensions true view
Metadata.ignorePropagatedAnnotations true view
AccessControl.authorizationCheck #NOT_REQUIRED view

OData Services (3)

ServiceBindingVersionContractRelease
UI_RFM_PO_MNG UI_RFM_PO_MNG V2 C1 NOT_RELEASED
UI_SOURCING_PROJECT_COMPARE UI_SRCGPROJ_COMPARE V2 C1 NOT_RELEASED
UI_SSACPERDCAMOUNTS_REVIEW UI_SSACPERDCAMOUNTS_REVIEW V2 C1 NOT_RELEASED

Fiori Apps (2)

App IDApp NameTypeDescription
F5391 Manage Purchase Orders - Fashion Transactional
F6108 Review Service Entry Sheet Accruals Transactional Review service entry sheet accrual amount for each period.

Manage Purchase Orders - Fashion

Business Role: Purchaser (Retail)

With this app, you can now consolidate purchase order items into an existing purchase order based on the settings in the rule maintained using the Configure Purchase Order Consolidation Rule app.

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 (7)

KeyFieldSource TableSource FieldDescription
KEY PurchasingGroup t024 ekgrp
PurchasingGroupName
PurchasingGroupPhoneNumber t024 ektel
FaxNumber t024 telfx
PhoneNumber t024 tel_number
PhoneNumberExtension t024 tel_extens
EmailAddress t024 smtp_addr 
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.representativeKey: 'PurchasingGroup'
@ObjectModel.usageType.dataClass: #CUSTOMIZING
@ObjectModel.usageType.serviceQuality: #A 
@ObjectModel.usageType.sizeCategory: #S
@ObjectModel.sapObjectNodeType.name:'PurchasingGroup'
@AbapCatalog.sqlViewName: 'IMMPURCHGROUP'
@AbapCatalog.preserveKey:true 
@EndUserText.label: 'Purchasing Group'
@Analytics.dataCategory: #DIMENSION
@VDM.viewType: #BASIC
@VDM.lifecycle.contract.type: #PUBLIC_LOCAL_API
@ObjectModel.supportedCapabilities:[#SQL_DATA_SOURCE,
                                    #CDS_MODELING_DATA_SOURCE, 
                                    #CDS_MODELING_ASSOCIATION_TARGET, 
                                    #ANALYTICAL_DIMENSION,
                                    #EXTRACTION_DATA_SOURCE]
@Analytics.dataExtraction.enabled: true
@Search.searchable: true        
@Metadata.allowExtensions:true
@Metadata.ignorePropagatedAnnotations: true
@AccessControl.authorizationCheck:#NOT_REQUIRED
define view I_PurchasingGroup 

as select from t024 
{
    @ObjectModel.text.element : 'PurchasingGroupName'
    
    @Consumption.labelElement: 'PurchasingGroupName'  
    @Search.defaultSearchElement: true
    @Search.fuzzinessThreshold: 0.75  
    key t024.ekgrp as PurchasingGroup,
    
    @Semantics.text: true
    @Search.defaultSearchElement: true
    @Search.fuzzinessThreshold: 0.75
    cast(t024.eknam as mm_a_purg_grp_name preserving type ) as PurchasingGroupName,
   
    t024.ektel as PurchasingGroupPhoneNumber,
    
    t024.telfx as FaxNumber,
    
    t024.tel_number as PhoneNumber,
    
    t024.tel_extens as PhoneNumberExtension,
    
    t024.smtp_addr as EmailAddress


}

Learn More