Which tables does I_PurchasingOrganization use?

I_PurchasingOrganization reads from 1 data source(s): t024e.

How many fields does I_PurchasingOrganization have?

I_PurchasingOrganization has 5 fields. Key fields: PurchasingOrganization.

I_PurchasingOrganization

DDL: I_PURCHASINGORGANIZATION SQL: IMMPURGORG Type: view BASIC

Purchasing Organization

I_PurchasingOrganization is a Basic CDS View (Dimension) that provides data about "Purchasing Organization" in SAP S/4HANA. It reads from 1 data source (t024e) and exposes 5 fields with key field PurchasingOrganization. It has 1 association to related views. It is exposed through 5 OData services (MM_PUR_PROCESS_PR_V4, UI_KANBANCONTAINER_MONITOR, UI_RFM_PO_MNG, ...). It is used in 2 Fiori applications: Manage Purchase Orders - Fashion, Review Service Entry Sheet Accruals.

Data Sources (1)

Source	Alias	Join Type
t024e	t024e	from

Associations (1)

Cardinality	Target	Alias	Condition
[0..*]	I_PlantPurchasingOrganization	_Plant	`$projection.PurchasingOrganization = _Plant.PurchasingOrganization`

Annotations (17)

Name	Value	Level
AbapCatalog.preserveKey	true	view
AbapCatalog.compiler.compareFilter	true	view
ClientHandling.algorithm	#SESSION_VARIABLE	view
ObjectModel.representativeKey	PurchasingOrganization	view
ObjectModel.usageType.dataClass	#ORGANIZATIONAL	view
ObjectModel.usageType.serviceQuality	#A	view
ObjectModel.usageType.sizeCategory	#S	view
ObjectModel.sapObjectNodeType.name	PurchasingOrganization	view
AbapCatalog.sqlViewName	IMMPURGORG	view
EndUserText.label	Purchasing Organization	view
Analytics.dataCategory	#DIMENSION	view
Analytics.dataExtraction.enabled	true	view
VDM.viewType	#BASIC	view
VDM.lifecycle.contract.type	#PUBLIC_LOCAL_API	view
AccessControl.authorizationCheck	#NOT_REQUIRED	view
Search.searchable	true	view
Metadata.ignorePropagatedAnnotations	true	view

OData Services (5)

Service	Binding	Version	Contract	Release
MM_PUR_PROCESS_PR_V4	MM_PUR_PR_PROCESS_V4	V4	C1	NOT_RELEASED
UI_KANBANCONTAINER_MONITOR	UI_KANBANCONTAINER_MONITOR	V4	C1	NOT_RELEASED
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 ID	App Name	Type	Description
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 (5)

Key	Field	Source Table	Source Field
KEY	PurchasingOrganization
	PurchasingOrganizationName
	CompanyCode	t024e	bukrs
	ConfigDeprecationCode	t024e	configdeprecationcode
	_Plant		_Plant

@AbapCatalog.preserveKey: true
@AbapCatalog.compiler.compareFilter: true
@ClientHandling.algorithm: #SESSION_VARIABLE
@ObjectModel.representativeKey: 'PurchasingOrganization'
@ObjectModel.usageType.dataClass:#ORGANIZATIONAL
@ObjectModel.usageType.serviceQuality:#A
@ObjectModel.usageType.sizeCategory: #S
@ObjectModel.sapObjectNodeType.name:'PurchasingOrganization'
@ObjectModel.supportedCapabilities: [ #SEARCHABLE_ENTITY,
                                      #ANALYTICAL_DIMENSION,
                                      #EXTRACTION_DATA_SOURCE,
                                      #SQL_DATA_SOURCE, 
                                      #CDS_MODELING_DATA_SOURCE, 
                                      #CDS_MODELING_ASSOCIATION_TARGET ]
@AbapCatalog.sqlViewName: 'IMMPURGORG'
@EndUserText.label: 'Purchasing Organization'
@Analytics.dataCategory: #DIMENSION
@Analytics.dataExtraction.enabled: true
@VDM.viewType: #BASIC
@VDM.lifecycle.contract.type: #PUBLIC_LOCAL_API
@AccessControl.authorizationCheck: #NOT_REQUIRED
@Search.searchable: true
@Metadata.ignorePropagatedAnnotations: true
define view I_PurchasingOrganization
  as select from t024e

  association [0..*] to I_PlantPurchasingOrganization as _Plant on $projection.PurchasingOrganization = _Plant.PurchasingOrganization

{
      @Search.defaultSearchElement: true
      @Search.fuzzinessThreshold: 0.75
      @ObjectModel.text.element : 'PurchasingOrganizationName'
  key cast( ekorg as ekorg_ll preserving type )           as PurchasingOrganization,

      @Search.defaultSearchElement: true
      @Search.fuzzinessThreshold: 0.75
      @Semantics.text: true
      cast( ekotx as mm_a_purg_org_name preserving type ) as PurchasingOrganizationName,

      t024e.bukrs                                         as CompanyCode,
      
      t024e.configdeprecationcode                         as ConfigDeprecationCode,

      _Plant
};

Depth:

I_PurchasingOrganization view

t024e