Professional Documents
Culture Documents
Business Content for SAP BW∕4HANA combines enterprise data warehouse capabilities of SAP BW∕4HANA with
explorative and interactive real-time analytics using the SAP HANA in-memory database. It is delivered as Add-
Ons to SAP BW/4HANA:
Business Content enables quick and cost-effective implementation as it provides a model that can be used as a
guideline during implementation. It can:
The delivered data models follow the recommendations for the layered scalable architecture LSA++, which is
optimized for SAP BW∕4HANA.
For more information about the layered scalable architecture optimized for BW on HANA, see section Layer
Architecture of a Data Warehouse with SAP HANA Database (LSA++) in the SAP BW/4HANA application help on
http://help.sap.com
Business Content uses the SAP HANA-optimized modeling objects like DataStore object (advanced) and
CompositeProvider and other new features of SAP BW∕4HANA. Business Content is a preconfigured set of
application specific information models based on consistent Metadata in SAP BW∕4HANA.
It includes
● InfoObjects, necessary for the Business Content, which is delivered with SAP BW/4HANA Content Add-On 1.0
● Infoareas
● Variables (Variables, SAP Exit Variable, Text Variables), a newly defined set of variables adhering to naming
conventions.
● Master data read classes and conversion exits
For more information about the delivered InfoObjects and variables please see SAP Note 2395613 and SAP
Note 2395579
This Add-On requires: SAP BW∕4HANA and SAP BW∕4HANA Content Basis Add-On 1.0.
It includes a preconfigured set of application specific data models for selected business areas and industries. The
data models contain queries, CompositeProviders, DataStore objects (advanced), InfoSources, key figures,
characteristics, and transformations for SAP applications. Business Content for SAP BW∕4HANA also includes
data flows for master data provisioning of InfoObjects, which are used in these data models.
Source System ID
Before you load data into the BW DataStore objects for SAP HANA-optimized content, you need to maintain the
source system ID.
In the DataStore objects of the Content the two-digit source system ID (0GN_R3_SSY) is filled during the
transformation from the Infosources to the DataStore objects. It is used to fill source system-dependent objects,
such as consolidated InfoObjects (for example, 0GN_CUSTOM), and allows you to determine the system from
which the data was loaded.
Procedure
Open the Data Warehousing Workbench (transaction code RSA1) and choose Administration Source Systems
Source System Assignment
You can also use transaction SE16 to check that the two-digit source system ID has been defined in table
RSSOURSYSTEM for your system and landscape.
Note
Other prerequisites are mentioned in the respective content areas.
The SAP HANA-optimized Business Content follows the LSA++ recommendations. The data model currently
provides the following features:
Note
SAP HANA-optimized Business Content DSOs are provided for this layer if the data is loaded further
into multiple EDW Core Layer DSOs. The structure of the staging layer DSOs reflects the structure of
the connected DataSources.
○ The data is then harmonized and transformed to the EDW core layer. The DataSource and the DSOs in
the EDW core layer are connected by an InfoSource. Only source system dependent transformation logic
may be applied between the open operational data store layer and the InfoSource. Harmonization and
business transformation logic is generally applied between the InfoSource(s) and the EDW core DSO(s).
Note
You can connect multiple sources of the open operational data store layer with the SAP HANA-
optimized Business Content data flow without losing the predefined EDW transformations. This can be
helpful if you need to connect multiple source systems.
○ A corporate memory layer is provided to contain the complete history of the loaded data. It is used as a
source for reconstructions without the need to access the sources again. The corporate memory is filled
independently of the EDW core layer’s update.
Note
The long description of
the InfoSource contains
the technical name of the
corresponding Data
Source. For example: MM-
PUR: Purchase Data Item
(2LIS_02_ITM)
Consolidated InfoObjects
The SAP HANA-optimized Business Content provides consolidated InfoObjects in its data model, where
applicable.
SAP BW uses consolidated InfoObjects to integrate and harmonize information from different SAP components in
a standardized (consolidated) data model (for example, 0MATERIAL from SAP ERP, and 0CRM_PROD from SAP
CRM).
The consolidated InfoObjects can store information about duplicates in the master data, and therefore enable
consolidated reporting using a group ID.
For more information about consolidated InfoObjects, go to the SAP Help Portal at http://help.sap.com and
search for Consolidated InfoObjects for BP, Product and Product Category.
Variables
A set of new variables is delivered adhering to a consistent naming convention (also see 2395579 ).
InfoObject 0MATERIAL
All InfoObjects using the conversion exit MATN1 (e.g.0MATERIAL, 0MAT_PLANT, 0RF_SKU) have been modeled
with length 40. This allows SAP S/4HANA customers to load the extended material number to SAP BW/4HANA
with 40 CHAR. Customers not using SAP S/4HANA can still load their 18 CHAR long material numbers also in
0MATERIAL and the other InfoObjects
Time granularity
In all delivered DataStore objects (advanced) (except in the area of MM-IM) only the finest time Granularity
(0CALDAY or 0CALMONTH) has been included. All other 0CAL* time characteristics (e.g. 0CALQUARTER,
0CALYEAR, ...) are exposed as navigation attributes of 0CALDAY or 0CALMONTH in the CompositeProviders.
More Information
For documentation updates relating to SAP HANA-optimized Business Content, see SAP Note 2400585 :
Collective Note: SAP HANA-Optimized Business Content.
This documentation describes the SAP HANA-optimized Business Content objects for the following components
of SAP ERP Financial Accounting & Controlling:
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Financial Accounting – Accounts Receivable.
The data model follows the recommendations for the layered scalable architecture LSA++, which is optimized for
BW running on SAP HANA.
For more information about general modeling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Financial Accounting: Accounts Receivable, you need
to make the following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
The FI Accounts Receivable data is extracted from the ERP system to the SAP BW/4HANA and made available
there for further evaluation. It allows you to perform analysis on your customers, with the possibility to drill down
to line item level.
SAP delivers sample analytic queries on top of CompositeProvider Accounts Receivable (/IMO/V_FIAR03):
Data Flow
/IMO/D_FIAR30
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the data load.
Generic Customer 0GN_CUSTOM Concatenation of the System ID, Object Type, and
Customer Number.
Fiscal Year of Clearing 0CLR_FYEAR Filled for cleared items. The value is derived from
the clearing date and fiscal year variant.
Indicator for Overdue Item 0OVERDUEIND Filled with “X” for cleared invoice items if the
Clearing date is after the Due date for net
payment.
Overdue Days (Cleared Items) 0OVERDAYS Filled for cleared invoice items. The value is the
difference in days between the Due date for net
payment and the Clearing date.
Amount Weighted Overdue Days 0DBTTWGHT Calculated as for Overdue Days (OVERDAYS), then
(LC) multiplied by the amount in local currency.
No. of Invoices 0INVOICES Filled with “1” if the customer line item is a
cleared invoice item.
Delta Update
Data Modeling
Requires
/IMO/CMFIAR04
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Customer Line Items
(0FI_AR_4).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIAR30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Customer Line Items
(0FI_AR_30).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.1.2 InfoSources
/IMO/FIAR_IS30
This InfoSource contains the structure for providing customer line item data to the core EDW layer. You can
transfer the data by using either DataSource 0FI_AR_4 or 0FI_AR_30.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
2.1.3 CompositeProvider
CompositeProvider: /IMO/V_FIAR03
This CompositeProvider contains customer line item data. It can be used to query the following:
It contains data from DataStore object FI-AR: Customer Line Items (/IMO/D_FIAR30).
Data Modeling
Requires
2.1.4 Queries
/IMO/V_FIAR03_Q0001
● Number of invoices
● Payments without cash discount
● Average invoice amount overdue
● Cash discount amount
● Unauthorized cash discount
The query also shows the weighted and unweighted average number of days that a customer took in the past to
pay bills (Days Beyond Terms Taken).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Required
Optional
Selection option
Optional
Selection option
Optional
Selection option
Required
Selection option
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0OVERDUEIND = X
0OVERDUEIND = X
# of Overdue Invoices
0AC_DOC_TYP = DZ
Exception aggregation:
Counter for All Detailed Values
That are not Zero, Null, or
Error
Reference characteristic:
Clearing Document Number
(0CLR_DOC_NO)
Reference characteristic:
Clearing Document Number
(0CLR_DOC_NO)
Reference characteristic:
Clearing Document Number
(0CLR_DOC_NO)
0AC_DOC_TYP = DR
0POST_KEY = 01
Divided by
Invoice Amount
Divided by
# of Invoices (0INVOICES)
/IMO/V_FIAR03_Q0002
For any fiscal year period (variable Period/Fiscal Year) and comparison fiscal year period (variable Comparison
Period), you can compare the following metrics:
Days Sales Outstanding is the average number of days that the company takes to collect revenue after a sale has
been made.
Days Beyond Terms Taken is the weighted or unweighted average number of days that a customer took to pay bills
in the past.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Required
Optional
Selection option
Optional
Selection option
Optional
Selection option
Required
Period/Fiscal Year
Selection option
Required
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
FISCPER: Variable
0CIIN_FISCPER
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency).
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
Interval:
[(0CXSM_LASTCLDTV – 90) –
0CXSM_LASTCLDTV ]
Multiplied by 90
0DBTTWGHT (Amount
Weighted Over)
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
InfoProvider: /IMO/
D_FIAR30
Cleared in Period
Key figure:
No. of Invoices
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
Interval:
[(0CXSM_LASTCLDTV_CMP –
90) –
0CXSM_LASTCLDTV_CMP ]
Divided by
Multiplied by 90
InfoProvider: /IMO/
D_FIAR30
Divided by
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
Key figure:
0DEB_CRED_LC (Debit/Credit
Amount in Local Currency)
/IMO/V_FIAR03_Q0003
Accounts receivable managers can use this query to display outstanding and overdue customer accounts.
Whether a customer line item is shown as “open” or “cleared” depends on a freely selectable key date (variable
Open on Key Date).
You can split the Overdue Amount into aging groups, with a freely selectable grid width (for example, 10 days).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Required
Optional
Selection option
Optional
Selection option
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Restriction: 0NETDUEDATE
(Net Due Date) is less than
variable 0CEPM_DATE_OPEN
(Open on Key Date)
Restriction:
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Financial Accounting – Accounts Payable.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Financial Accounting: Accounts Payable, you need to
make the following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The FI Accounts Payable data is extracted from the ERP system to the SAP BW/4HANA and made available there
for further evaluation. It allows you to perform analysis on your vendors, with the possibility to drill down to line
item level.
Data Flow
/IMO/D_FIAP30
This DSO (advanced) contains the vendor line items of sub-ledger accounting.
Sources
This DSO is updated by the InfoSource FI-AP: Vendor Line Items (0FI_AP_4/0FI_AP_30) (/IMO/FIAP_IS30).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/CMFIAP30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Vendor Line Items
(0FI_AP_30).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIAP04
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Vendor Line Items
(0FI_AP_4).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.2.2 CompositeProvider
CompositeProvider: /IMO/V_FIAP01
This CompositeProvider contains all vendor line item data from sub-ledger accounting. It contains data from
DataStore object FI-AP: Vendor Line Items (/IMO/D_FIAP30).
Data Modeling
2.2.3 InfoSource
/IMO/FIAP_IS30
This DSO (advanced) contains the vendor line items of sub-ledger accounting.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
2.2.4 Queries
/IMO/V_FIAP01_Q0001
This query displays open items for vendor overdue analysis, separated into different time buckets. This query is
based on CompositeProvider FI Accounts Payable (/IMO/V_FIAP01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure &0TXPO_FIBUCKET5 & - Net due Date = Due Date Grid
5
/IMO/V_FIAP01_Q0002
This query displays due and not due amounts per vendor for a given date. This query is based on
CompositeProvider FI Accounts Payable (/IMO/V_FIAP01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from the application Contract Accounts Receivable and Payable.
The data model fulfills the requirements of the LSA++ (Layered Scalable Architecture) optimized for the execution
of BW under SAP HANA
For more information about the general modeling option for SAP HANA Optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Contract Accounts Receivable, you need to make the
following configuration settings:
General Settings
For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Features
Here you can find the requirements of the customized themes and contents of Contract Accounts Receivable and
Payable - among these are a variety of key figures and characteristics - for specific reporting
/IMO/D_FICA17
This DataStore object (DSO) contains the business partner-specific attributes of the contract account and can be
used for master data reporting.
Sources
This DSO is filled by the InfoSource FICA: Contract account - partnerabh. Attr. (0FC_ACCNTBP_ATTR_2) () are
filled. /IMO/FICA_IS17
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA16
This DataStore object (DSO) contains the business partner independent attributes of the contract account and
can be used for master data reporting.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA15
Sources
This DSO (advanced) is filled by the InfoSource FICA: Disconnect/Reconnect (0FC_WLIA) /IMO/FICA_IS15 is
filled.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
FI-CA: Lock/Unlock
Requires
/IMO/D_FICA14
This DataStore object (DSO) contains the due amounts for promise to pay and due date.
Sources
This DSO is filled by the InfoSource FICA: Amount Due per Payment Date (0FC_PPD) (/IMO/FICA_IS14)
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA13
This DataStore Object contains promise to pay header data from FICA.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA12
Sources
This DSO is filled by the InfoSource FICA: Work items (0FD_WLI) (/IMO/FICA_IS12) are filled.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
All key figures are updated with the aggregation behavior "Overwrite" updated.
Delta Update
Data Modeling
Requires
/IMO/D_FICA11
This DataStore object contains the returns data from FI-CA. This DataStore object contains the payment data
from FI-CA.
Sources
This DSO is filled by the InfoSource FICA: Payments (0FC_PAY) (/IMO/FICA_IS11) are filled.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
FI-CA: Payments
Requires
/IMO/D_FICA09
Sources
This DSO is filled by the InfoSource FICA: Returns (0FC_RET) are filled (/IMO/FICA_IS09)
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
FI-CA: Returns
Requires
/IMO/D_FICA10
This DataStore object contains the data of enhanced revenue distribution dependent on the selected distribution
group.
Sources
This DSO is filled by the InfoSource FICA: Revenue distribution (0FC_RDI) are filled (/IMO/FICA_IS10).
Transformation
Field Routines
Posted Distribution Amount in Transac 0FC_BETRWP IF( FC_OPBELD <> '', FC_BETRWDI, 0 )
tion Currency +/- Sign
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA08
This DataStoreObject contains the data of dunning activities that were executed in the OLTP system.
Sources
This DSO is filled by the InfoSource FICA: Dunning activities (0FC_DUN_ACTIVITIES) are filled. (/IMO/FICA_IS08)
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA07
This DataStoreObject contains the data of dunning history Items that were executed in the OLTP system.
Sources
This DSO is filled by the InfoSource FICA: Dunning history items (0FC_DUN_ITEMS) (/IMO/FICA_IS07) are filled.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA06
This DataStoreObject contains the data of dunning history header that were executed in the OLTP system.
Sources
This DSO is filled by the InfoSource FICA: Header Data of Dunning History (0FC_DUN_HEADER) are filled (/IMO/
FICA_IS06).
Transformation
Field Routines
Concatenation of:
Time Part of Item Group 0FC_ITEMGRT Reading of time part from item group
(0FC_ITEMGRP)
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA05
This object contains all business partner items. By using the characteristic item status (0FI_DOCSTAT), you can
differentiate between open and closed items.
With large data volumes, SAP recommends for the data to be partitioned semantically.
Sources
This DSO is filled by the InfoSource FICA: Business partner items (0FC_BP_ITEMS) are filled. (/IMO/FICA_IS05)
Transformation
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA04
In the standard delivery of the dataSource FI-CA Extraction of Invoicing Document Data (0FC_INVDOC_00) the
various fields are initially hidden for the extraction, for example the invoicing document number (field INVDOCNO).
The data flow delivered already contains the InfoObjects required for this. These fields can be connected to the
relevant InfoObjects after they are mapped into the DataSource. In this case, the key of the DataStore object can
be adjusted to suite your requirements.
Sources
This DSO is filled by the InfoSource FICA: Invoicing document data (0FC_INVDOC_00) are filled. (/IMO/
FICA_IS04)
Transformation
Field Routines
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA03
This DataStore object contains the header data for installment plans.
Sources
This DSO is filled by the InfoSource FICA: Installment plan header data (0FC_IPL_HEAD_01) (/IMO/FICA_IS03)
are filled.
Transformation
Field Routines
Update Date 0UPD_DATE Is filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA02
This DataStore object contains the item data for installment plans.
Sources
This DSO is filled by the InfoSource FICA: Installment plan items (0FC_IPL_ITEM_01) (/IMO/FICA_IS02) are filled.
Transformation
Field Routines
Due date for net payment 0FCNETDUEMO Date conversion from net due date
(0NETDUEDATE)
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/D_FICA01
This composite provider contains the data of the current clarification cases of the application Enhanced Message
Management (EMMA) in FI-CA.
Sources
This DSO is filled by the InfoSource FICA: Case Management (OFCEMMA_CASE) are filled. (/IMO/FICA_IS01)
Transformation
Field Routines
Residence time of case (in days) 0CSM_DURAT Date of the last change(0CH_ON)
Formula:
Residence time in clarification work list 0CSM_PRCT Date of the last change(0CH_ON)
(in days)
Date on which the record was created
(0CREATEDON)
Formula:
Delay of case processing (in days) 0CSM_DELAY Date of the last change(0CH_ON)
Formula:
Update Date 0UPD_DATE Filled with the system date during the
data load.
Delta Update
Data Modeling
Requires
/IMO/CMFICA05
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA business
partner items (0FC_BP_ITEMS).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA17
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA partner
dependent data for contract account(0FC_ACCNTBP_ATTR_2).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA16
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA partner
independent data for contract account(0CACONT_ACC_ATTR_2).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA15
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource notification
disconnection/reconnection (0FC_WLIA).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA15
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource notification
disconnection/reconnection (0FC_WLIA).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA14
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource payment date of
due amount (0FC_PPD).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA13
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource promise to pay
header (0FC_PP).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA15
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource notification
disconnection/reconnection (0FC_WLIA).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA14
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource payment date of
due amount (0FC_PPD).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA13
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource promise to pay
header (0FC_PP).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA12
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource work items
(0FC_WLI).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA11
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource payments
(0FC_PAY).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA09
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA10
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA revenue
distribution (0FC_RDI).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA08
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA dunning
activities(0FC_DUN_ACTIVITIES).
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA07
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA dunning
history (0FC_DUN_ITEMS).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA06
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA dunning
history (0FC_DUN_HEADER).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA04
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource FICA extraction
invoicing document data (0FC_INVDOC_00).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA03
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource installment header
data for Business Warehouse (0FC_IPL_HEAD_01).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA02
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource installment header
items for Business Warehouse (0FC_IPL_ITEM_01).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFICA01
This DataStore object (advanced) is used as a corporate memory DSO for the BW DataSource process statistics
for clarification cases (0FCEMMA_CASE).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.3.2 InfoSources
/IMO/FICA_IS17
This InfoSource contains the structure for the provisioning of the partner dependent attributes for the contract
accounts in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS16
This InfoSource contains the structure for the provisioning of the partner dependent attributes for the contract
accounts in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS15
This InfoSource contains the structure for the provisioning of the notification dates for disconnecting and
reconnecting in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS14
This InfoSource contains the structure for the provisioning of data for the amounts due per payment data in the
EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS13
This InfoSource contains the structure for the provisioning of the header data for the promise to pay in the EDW
core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS12
This InfoSource contains the structure for the provisioning of the work item data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS11
This InfoSource contains the structure for the provisioning of the payment data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS09
This InfoSource contains the structure for the provisioning of the returns lot data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS10
This InfoSource contains the structure for the provisioning of the revenue distribution data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS08
This InfoSource contains the structure for the provisioning of the dunning activities in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS07
This InfoSource contains the structure for the provisioning of the dunning item data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS06
This InfoSource contains the structure for the provisioning of the dunning items in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS05
This InfoSource contains the structure for the provisioning of the business partner items in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
/IMO/FICA_IS04
This InfoSource contains the structure for the provisioning of the invoicing document data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS03
This InfoSource contains the structure for the provisioning of the installment header data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS02
This InfoSource contains the structure for the provisioning of the installment item data in the EDW core layer.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
/IMO/FICA_IS01
This InfoSource forms the interface for the data in Enhanced Message Management (EMMA) of the FI-CA
application. The identically named DataSource 0FCEMMA_CASE provides data for both the new changed and
deleted clarification cases.
Transformation
Source system for R/3 entry 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
For more information about source system IDs, see SAP HANA-Optimized BI Content [page 7].
Data Modeling
Requires
2.3.3 CompositeProvider
CompositeProvider: /IMO/V_FICA09
Contains all items in initial distribution or posted distribution extracted with delta procedures in the BI-system. The
data corresponds with the current status in the ERP system. With the CompositeProvider, you can analyze the
current status of how much distributed amount has been posted, the amount of initial distribution and the amount
of posted distribution.
Data Modeling
CompositeProvider: /IMO/V_FICA07
This CompositeProvider contains all payments data extracted using delta procedures in the BI system.
The data corresponds with the current status in the ERP system.
With the CompositeProvider you can analyze the current status of payment amounts.
Structure
Data Modeling
CompositeProvider: /IMO/V_FICA06
This CompositeProvider contains all returns data extracted using delta procedures in the BI system.
The data corresponds with the current status in the ERP system. Using this CompositeProvider, you can analyze
the current status of the return amount, return charge and the number of returns.
Structure
Data Modeling
CompositeProvider: /IMO/V_FICA05
Structure
Data Modeling
CompositeProvider: /IMO/V_FICA04
Structure
Data Modeling
CompositeProvider: /IMO/V_FICA01
This composite provider contains the data of the current clarification cases of the application Enhanced Message
Management (EMMA) in FI-CA.
Structure
Data Modeling
2.3.4 Queries
/IMO/V_FICA05_Q0001
This query gives you an overview of the open items overdue in a company code and business area on a key date.
The predefined sort provides values for the period smaller than 1, 1-30, 31-60, 61-90 and bigger than 90 days. You
can also use the division and segment in the analysis.
You must specify the key date by which the open items were determined for the selection.
The open items displayed are divided into two categories. The first category enters the normal items for which
neither an installment plan or promise to pay exists. The original items of an installment plan or promise to pay fall
into the second category.
The items of installment plans and collective invoices are not included in the analysis.
Data Modeling
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
<> S, <> R
<> S, <> R
<> S, <> R
<> S, <> R
<> S, <> R
<> S, <> R
/IMO/V_FICA07_Q0001
This query provides an overview of payments for a particular company code, type of data source and payment
type.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_FICA06_Q0001
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
0CESO_ERDAT
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_FICA04_Q0001
This query can be used to analyze sales volume according to invoicing data. The standard view displays the data
relative to the months, company code, and division specified.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Financial Accounting: General Ledger (FI-GL).
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For detailed information about general modeling patterns for SAP HANA-optimized Business Content, see SAP
BW/4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Financial Accounting: General Ledger, you need to
make the following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The general ledger data is extracted from the ERP system to the Business Warehouse for evaluation. You can
analyze accounting data on both an aggregated (balance) level and detailed (accounting document item) level.
SAP delivers sample analytic queries on top of CompositeProviders for the following areas:
/IMO/D_FIGL04
This DSO (advanced) contains the general ledger line items extracted with DataSource General Ledger: Line Items
with Delta Extraction (0FI_GL_4). The DSO enables flow reporting for defined periods.
Prerequisites
The following master data must be loaded before loading the transactional data into this DSO because the master
data is read during the transformation: 0CO_AREA.
This DSO is updated by the InfoSource FI-GL: Line Items (0FI_GL_4) (/IMO/FIGL_IS04).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Data Modeling
Requires
/IMO/D_FIGL06
This DSO (advanced) contains the general ledger balances extracted with DataSource General Ledger Sales
Figures via Delta Extraction (0FI_GL_6) from table GLT0. The DSO enables balance and flow reporting for defined
periods. Reports can be based on any value type that is recorded in the source system.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
FI-GL: Balances
Requires
/IMO/D_FIGL12
This DSO (advanced) contains the new general ledger balances extracted with DataSource General Ledger:
Balances of Leading Ledger via Delta Queue (0FI_GL_12). The DSO enables balance and flow reporting for defined
periods. Reports can be based on any value type that is recorded in the source system.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/D_FIGL14
This DSO (advanced) contains the new general ledger line items extracted with DataSource General Ledger (New):
Line Items Leading Ledger (0FI_GL_14). The DSO enables line item reporting on actual data.
Sources
This DSO is updated by the InfoSource FI-GL: Line Items (0FI_GL_14) (/IMO/FIGL_IS14).
To reduce the number of overlapping delta records, the safety intervals for the extractor can be adapted. For more
information, see SAP Note 1523670 . For performance improvements for extraction, see SAP Note 1731175 .
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/CMFIGL04
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource General Ledger: Line
Items with Delta Extraction (0FI_GL_4).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIGL06
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource General Ledger Sales
Figures via Delta Extraction (0FI_GL_6).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIGL12
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource General Ledger:
Balances of Leading Ledger via Delta Queue (0FI_GL_12).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIGL14
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource General Ledger (New):
Line Items Leading Ledger (0FI_GL_14).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/FIGL_IS04
This InfoSource contains the structure to provide general ledger line items data to the EDW Core Layer. This
InfoSource is based on DataSource 0FI_GL_4.
To reduce the number of overlapping delta records, the safety intervals for the extractor can be adapted. For more
information, see SAP Note 1523670 . For performance improvements for extraction, see SAP Note 1731175 .
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Delta Update
Data Modeling
Requires
/IMO/FIGL_IS06
This InfoSource contains the structure to provide general ledger balance data to the EDW Core Layer. This
InfoSource is based on DataSource 0FI_GL_6.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Requires
/IMO/FIGL_IS12
This InfoSource contains the structure to provide new general ledger balance data to the EDW Core Layer. This
InfoSource is based on DataSource 0FI_GL_12.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/FIGL_IS14
Performance enhancements might be available for data extraction. For more information, see SAP Notes 1476708
and 1531175 .
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This BAdI Provider can be used for balance sheet and profit and loss reporting. The definition of the Provider is
based on ABAP class BAdi Provider for BSPL Reporting (CL_BW4C_FIGL_BSPL_IMPL). The processed data is read
from the replicated balances in DataStoreObject (advanced) FI-GL: New GL – Balances (/IMO/D_FIGL12) via
function group B/S and Profit/Loss (BW4C_FIGL).
DSO FI-GL: New GL – Balances (/IMO/D_FIGL12) determines the list of available InfoObjects in the BAdI Provider.
For custom implementations for the balance sheet and profit and loss reporting you will need to :
A.) Create an Enhancement Spot and BAdI Implementation based on Enhancement Spot RSO_BADI_PROVIDER
For simplification purposes your class needed for step B) can inherit from class Template BAdi Provider for BSPL
Reporting (CL_BW4C_FIGL_BSPL). You will only need to implement method GET_CUSTOMIZING.
Note
Note: The filter value for your BAdI implementation needs to be identical to the name for your BAdI Provider
specified in method GET_CUSTOMIZING.
Data Modeling
2.4.4 CompositeProvider
CompositeProvider: /IMO/V_FIGL01
This CompositeProvider contains all the transaction data (transactions figures) from the leading ledger in general
ledger, as well as the line item data. The Line Items DSO enables reporting on actual data, whereas the Balances
DSO enables reporting on both actual data and plan data (balance and flow reporting for defined periods).
Sources
When creating your own queries on this CompositeProvider, consider the following:
● DataStore object FI-GL: Balances (/IMO/D_FIGL06) contains period totals for general ledger accounts with
different value types, for example, plan data and actual data. When implementing a query that includes data
0INFOPROV: /IMO/D_FIGL06
0FISCPER3: < 1
Data Modeling
Requires
CompositeProvider: /IMO/V_FIGL02
This CompositeProvider contains all the transaction data (transactions figures) from the leading ledger in new
general ledger, as well as the line item data.
Sources
When creating your own queries on this CompositeProvider, consider the following:
● DataStore Object FI-GL: New GL - Balances (/IMO/D_FIGL12) contains period totals for general ledger
accounts with different value types, for example, plan data and actual data. When implementing a query that
0INFOPROV: /IMO/D_FIGL12
0FISCPER3: < 1
Data Modeling
Requires
Definition
This CompositeProvider can be used for balance sheet and profit and loss reporting. It consumes data from BadI
Infoprovider Balance Sheet Reporting (3BVBFIGL01). The displayed data is read from the replicated balance of
DataStoreObject (advanced) FI-GL: New GL – Balances (/IMO/D_FIGL12).
You can use the delivered sample query FI-GL: Financial Statement (/IMO/V_FIGL03_Q0001), or build you own.
Sources
Data Modeling
2.4.5 Queries
/IMO/V_FIGL01_Q0001
This query provides a comparison of general ledger flow and balance between two defined periods. You can also
drill down to the document line item.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Debit &0T_F3VEF & - - Debit for chosen period based
&0T_F3VET &.&0T_FYVK &
on line item data
Key Figure Actuals Comp. &0T_FP3CF& - - Flow for chosen period based
&0T_FP3CT&.&0T_FY2&
on line item data
Key Figure Carry Forward Comp. Per. - Carry Forward for chosen
comparison year (from period
001 in InfoProvider /IMO/
D_FIGL06)
/IMO/V_FIGL01_Q0002
This query provides a comparison of general ledger flow and balance between two defined periods and a
comparison between actual data and plan data on a balance level.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure &0T_VT_VN & &0T_VS_VK & - Flow value for chosen period
&0T_F3VEF & - &0T_F3VET
&.&0T_FYVK &
/IMO/V_FIGL02_Q0001
This query provides a comparison of general ledger flow and balance between two defined periods. You can also
drill down to the document line item.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Debit &0T_F3VEF & - - Debit for chosen period based
&0T_F3VET &.&0T_FYVK &
on line item data
Key Figure Debit Comp. &0T_F3VEFC & - - Debit for chosen comparison
&0T_F3VETC &.&0T_FYVKC
period based on line item data
&
Key Figure Credit Comp. &0T_F3VEFC & - Credit for chosen comparison
- &0T_F3VETC &.&0T_FYVKC
period based on line item data
&
Key Figure Carry Forward Comp. Per. - Carry Forward for chosen
comparison year (from period
000 in InfoProvider /IMO/
D_FIGL06)
/IMO/V_FIGL02_Q0002
This query provides a comparison of general ledger flow and balance between two defined periods and a
comparison between actual data and plan data on a balance level.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure &0T_VT_VN & &0T_VS_VK & - Flow value for chosen period
&0T_F3VEF & - &0T_F3VET
&.&0T_FYVK &
Key Figure &0T_VT_VNC & &0T_VS_VKC - Flow value for chosen com
& &0T_F3VEFC & -
parison period
&0T_F3VETC &.&0T_FYVKC
&
Key Figure Debit Comp. &0T_F3VEFC & - - Debit for chosen comparison
&0T_F3VETC &.&0T_FYVKC
period
&
Key Figure Credit Comp. &0T_F3VEFC & - Credit for chosen comparison
- &0T_F3VETC &.&0T_FYVKC
period
&
Key Figure Carry Forward Comp. Per. - Carry Forward for chosen
comparison year
You can use this query to display a Balance Sheet and Profit/Loss statement.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Single Value
Single Value
Single Value
Single Value
Single Value
Single Value
SAP Exit
Single Value
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name
Posting Period
(0FISCPER3 ) - Variable
0CIIM_FISCPER3
Fiscal Year
(0FISCYEAR ) - Variable
0CIPM_FISCYEAR
(0FISCVARNT) - Variable
0CXPN_FISCVARNT
Posting Period
(0FISCPER3) - Variable
0CIIM_FISCPER3_CMP
(0FISCVARNT) - Variable
0CXPN_FISCVARNT
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Financial Accounting – Asset Accounting.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Before using the SAP HANA-optimized Business Content for Asset Accounting, you need to make the following
configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
To enable determination of the delta datasets, SAP Note 535016 must be installed in all OLTP systems, or the
corresponding Support Package must be imported.
Caution
The BAdI implementations for FIAA_BW_DELTA_UPDATE contained in the note are delivered inactive. These
must be activated in the SAP ERP source system. See point 6 in the note.
The extraction procedure used here is based on the procedure used for the General Ledger: .
Caution
Pay particular attention to the section on global settings.
To maintain a consistent dataset in Financial Accounting during data extraction, new and changed datasets are
loaded for the same time interval for which line items in the General Ledger (0FI_GL_4) were last loaded. If no
data exists for 0FI_GL_4, extraction is not linked to the General Ledger.
1. 0FI_GL_4
General Ledger: line items (if required)
2. 0ASSET_ATTR_TEXT
Asset subnumber
3. 0ASSET_AFAB
Depreciation area real or derived
Then the transaction data FI-AA: Transactions 0FI_AA_11 and FI-AA: Posted Depreciations – Period Values
0FI_AA_12
Features
The FI Asset Accounting data is extracted from the ERP system to the Business Warehouse and made available
there for further evaluation.
SAP delivers sample queries on top of the CompositeProvider Asset Accounting (/IMO/V_FIAA01):
Data Flow
/IMO/D_FIAA11
This DataStore Object (advanced) contains all transactions and annual value information for an asset.
● Transactional data
For flexible filtering in analytic queries, an additional InfoObject Transaction Indicator 0TRANSIND can be added to
this DataStore object. It can be used to differentiate between
Key figures are grouped by the following hierarchy nodes in the DSO:
Sources
This DSO is filled by the InfoSource FI-AA:Transactions (0FI_AA_11) (technical name: /IMO/FIAA_IS11).
Transformation
Field Routines
Transaction Indicator 0TRANSIND Filled with “T” for transactions, “C” for
cumulated and “P” for planned records
based on Transaction Type
Cumulative Acquisition Value at FY Start 0CACQ_VL Filled by Acquisition value for transac
tions 0ACQ_VAL_TR if Asset Transaction
Type = “CUM”
Cumulative Revaluation of Ordinary De 0CREV_OD Filled by Appreciation of the ordinary de
preciation preciation on transaction if Asset Trans
action Type = “CUM”
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_FIAA12
This DataStore Object (advanced) contains the period values for an asset. It is similar in structure to the DataStore
objects FI-AA: Transactions and Annual Values /IMO/D_FIAA11. However, the values refer to individual periods
Cumulative values and certain transactions, such as acquisition values and value adjustments, are calculated
precisely by period from the transactions and annual values from DataSource 0FI_AA_11, while posted and
simulated depreciation values are updated from DataSource 0FI_AA_12.
Key figures are grouped by the following hierarchy nodes in the DSO:
Sources
This DSO is filled by the InfoSource FI-AA: Transactions (0FI_AA_11) (technical name: /IMO/FIAA_IS11).
This DSO is filled by the InfoSource FI-AA: Posted Depreciations – Periodic Values (0FI_AA_12) (technical
name: /IMO/FIAA_IS12).
Transformation
● Start Routine
A start routine is used to add missing periods such as special periods.
Hint: You can find more detailed documentation in the ABAP coding of the start routine.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
● Start Routine
A start routine is used to add missing periods such as special periods.
Hint: You can find more detailed documentation in the ABAP coding of the start routine.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Delta Update
- DataSource: 0FI_AA_12
Data Modeling
Requires
Key figure Values for the period: Posted special de 0PST_SDP_PE
preciation
/IMO/CMFIAA11
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMFIAA12
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource FI-AA: Transactions
(0FI_AA_12).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.5.2 InfoSources
/IMO/FIAA_IS11
This InfoSource contains the structure to provide all transactions for asset postings, as well as annual values
(cumulated and planned) for assets which are transferred to the EDW Core Layer. This InfoSource is based on
DataSource 0FI_AA_11. You can find detailed information on this data source (including source tables/fields,
delta handling and extractor features) by searching for datasource 0FI_AA_11 in the SAP Online Help.
Note
The following InfoObjects are part of the InfoSource but are not updated by the inbound transformation. They
are only used in the start routine of the transformation between InfoSource FI-AA: Transactions /IMO/
FIAA_IS11 and DataStore Object FI-AA: Period Values /IMO/FIAA_DS12:
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/FIAA_IS12
This InfoSource contains the structure to provide values for depreciation postings by period, which are transferred
to the EDW Core Layer. For open periods that have not yet been posted in the SAP ERP source system, the
depreciation values are simulated. This InfoSource is based on DataSource 0FI_AA_12. You can find detailed
information on this DataSource (including source tables/fields, delta handling and extractor features) by
searching for DataSource 0FI_AA_12 in the SAP Online Help.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Key figure Values for the period: Posted special de 0PST_SDP_PE
preciation
2.5.3 CompositeProvider
CompositeProvider: /IMO/V_FIAA01
This CompositeProvider contains asset accounting data including transactions, annual values and period values. It
can be used to query the following for example:
When creating your own queries on this CompositeProvider consider the following:
● Both underlying PartProviders contain data for the same assets recorded for different depreciation areas. A
filter/selection should therefore be added either in the query filter or in the selection option for your key
figures based on InfoObject Depreciation Area 0ASSET_AFAB.
● The following characteristics are only available in source InfoProvider FI-AA: Transactions and Annual
Values /IMO/D_FIAA11:
○ Asset transaction type 0TRANSTYPE
○ Sequence number of asset line items in fiscal year 0SEQ_NUMBER
○ Transaction indicator 0TRANSIND
● The following characteristics are only available in source InfoProvider FI-AA: Period Values /IMO/D_FIAA12:
○ Cost center 0COSTCENTER
○ Order number 0COORDER
○ Controlling area 0CO_AREA
○ Profit center 0PROFIT_CTR
○ Segment for segmental reporting 0SEGMENT
○ Posted / simulated value 0FIAA_SIM
When creating your own queries on this CompositeProvider consider the following:
● Key Figures are grouped by the following key figure hierarchy nodes in the CompositeProvider:
○ Transactional key figures
○ Value adjustments
○ Annual cumulated (start of fiscal year)
○ Period: key figures & posted values
○ Period: Period cumulated (start of period)
○ Period: Annual cumulated (start of FYear)
○ Period: Value adjustments
Value Description
T Transactions
C Cumulative (annual)
P Planned (annual)
○ InfoObject Asset Transaction Type 0TRANSTYPE for key figures based on PartProvider FI-AA: Transactions
and Annual Values /IMO/D_FIAA11 with example values as shown below
Value Description
400 Post-capitalization
○ Navigation attribute Summariz. of trans. types for asset history sheet 0TRANSTYPE__0SHEET_GRP for key
figures based on PartProvider FI-AA: Transactions and Annual Values /IMO/D_FIAA11 with some example
values as shown below
Value Description
10 Acquisition
15 Down payment
20 Retirement
The following restricted key figures are used to provide planned annual values
The following restricted key figures are used to provide annual value adjustments
Value Adjustm. and Appreciation on Or /IMO/V_FIAA01_RK_CP_VAW_ODP 0VAW_ODP_TR with Transaction Indicator
din. Deprec. (PLN/CUM) “P” or “C”
Value Adjustm. and Appreciation on Un /IMO/V_FIAA01_RK_CP_VAW_UDP 0VAW_UDP_TR with Transaction Indicator
planned Depr. (PLN/CUM) “P” or “C”
Value Adjustm. and Apprec. on transfer /IMO/V_FIAA01_RK_CP_VAW_AVR 0VAW_AVR_TR with Transaction Indicator
of reserves (PLN/CUM) “P” or “C”
The following restricted key figures are used to provide transaction based acquisition and depreciation values
restricted by certain Sheet Groups
The following calculated key figures provide acquisition and depreciation values including value adjustments and
can be used for transaction based reports. A filter on Transaction Indicator = “T” should be added to the query
definition.
The following calculated key figures are used for annual value reports such as Annual Asset History Sheet and
calculate various acquisition and depreciation values including value adjustments.
The following calculated key figures are also used for annual value reports such as Annual Asset History Sheet and
calculate cumulative values at the start and at the end of a fiscal year, for example the Net Book Value.
The following calculated key figures are used for period value reports such as Asset History Sheet per period and
calculate various posting values including value adjustments per period.
The following calculated key figures are used for period value reports such as Asset History Sheet per period and
calculate various cumulative values at the start and at the end of a fiscal year, for example the Net Book Value.
Data Modeling
Requires
2.5.4 Queries
/IMO/V_FIAA01_Q0001
This query is used to create an asset history sheet that displays net book value, acquisition and production costs,
and depreciations at the start and the end of a preselected period interval. It is similar to SAP ERP Asset Explorer
transaction AW01n.
This query is based on the CompositeProvider FI-AA: Transactions, Annual and Period Values (/IMO/V_FIAA01).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_FIAA01_Q0002
This query shows various acquisition and depreciation values based on captured asset transactions. The values
are grouped by asset class or asset and transaction type.
This query is based on the CompositeProvider FI-AA: Transactions, Annual and Period Values (/IMO/V_FIAA01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_FIAA01_Q0003
This query is based on the CompositeProvider FI-AA: Transactions, Annual and Period Values (/IMO/V_FIAA01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_FIAA01_Q0004
This query provides a comparison of two depreciation areas. It selects and compares the value adjustments
(depreciation) and net book values of the depreciation areas you select.
This query is based on the CompositeProvider FI-AA: Transactions, Annual and Period Values (/IMO/V_FIAA01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/
V_FIAA01_CK_APC_FYE (An
nual: Accumul. APC at Fiscal
Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPM_ASSET_AFAB (Depre
ciation area for the asset)
/IMO/
V_FIAA01_CK_APC_FYE (An
nual: Accumul. APC at Fiscal
Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPO_ASSET_AFAB_CMP
(Comparison evaluation area)
/IMO/
V_FIAA01_CK_DEPR_FYE
(Annual: Accumul. Deprecia
tion at Fiscal Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPM_ASSET_AFAB (Depre
ciation area for the asset)
/IMO/
V_FIAA01_CK_DEPR_FYE
(Annual: Accumul. Deprecia
tion at Fiscal Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPO_ASSET_AFAB_CMP
(Comparison evaluation area)
/IMO/
V_FIAA01_CK_NBV_FYE (An
nual: Net Book Value at Fiscal
Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPM_ASSET_AFAB (Depre
ciation area for the asset)
/IMO/
V_FIAA01_CK_NBV_FYE (An
nual: Net Book Value at Fiscal
Year End)
0ASSET_AFAB (Depreciation
Area): Variable
0CIPO_ASSET_AFAB_CMP
(Comparison evaluation area)
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Enterprise Controlling: Profit Center Accounting.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Profit Center Accounting, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The Profit Center Accounting data is extracted from the ERP system to the Business Warehouse for evaluation.
It also includes statistical key figure data with fixed and total quantities.
SAP delivers sample analytic queries on top of CompositeProvider Profit Center Accounting (/IMO/V_PCA01) for
the following areas:
Data Flow
/IMO/D_PCA01
This DSO (advanced) contains all of the period totals for profit and loss accounts and balance sheet accounts from
Profit Center Accounting (PCA) that were loaded from the affiliated source systems.
The DSO stores the data in an account-based model based on value type (for example, actual data or plan data),
version (for example, plan version 1 or plan version 2), and currency type (for example, local currency or group
currency).
Carry forward balances are loaded into fiscal year period 000 of the corresponding new fiscal year and must be
included for reporting of balance sheet account balances.
For SAP HANA-optimized content, we recommend calculating the accumulated balance in the query by
accumulating the transaction values of period 0 to n in the query definition, rather than storing the accumulated
balances in the DSO, as defined in SAP Note 328197 .
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
The delta method can only be used for actual data records (value type 0VTYPE = 010) and excludes periodic
transfer balance sheet accounts. Records for other value types can be transferred using full upload.
For more information about prerequisites and restrictions for this delta update, see the documentation for
DataSource Profit Center Accounting Transaction Data (0EC_PCA_1) and SAP Note 328197 .
Data Modeling
EC-PCA: Totals
Requires
/IMO/D_PCA02
This DSO (advanced) contains the period totals for all statistical key figures from Profit Center Accounting (PCA)
that were loaded from the affiliated source systems.
The DSO stores the data in an account-based model based on value type (for example, actual data or plan data)
and version (for example, plan version 1 or plan version 2).
Sources
This DSO is updated by the InfoSource EC-PCA: Statistical Key Figures (0EC_PCA_2) (/IMO/PCA_IS02).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/D_PCA03
This DSO (advanced) contains all actual line items from Profit Center Accounting (PCA) that were loaded from the
affiliated source systems.
Sources
This DSO is updated by the InfoSource EC-PCA: Line Item - Actuals (0EC_PCA_3) (/IMO/PCA_IS03).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Constraints
● Data that is created by periodic transfer balance sheet accounts (ACTIV = PRC4) is not transferred by
DataSource 0EC_PCA_3. This data can be transferred using DataSource 0EC_PCA_4 to DataStore
object /IMO/D_PCA04 with an extra full upload.
● No line items are posted for balance carry forward. For this reason, DataSource 0EC_PCA_3 does not provide
the values for the balance carry forward.
● Balance carry forward is loaded and stored in DataStore object EC-PCA: Totals /IMO/D_PCA01 against fiscal
year period 000.
Delta Update
Data Modeling
Requires
/IMO/D_PCA04
This DSO (advanced) contains the actual line items that are created as a result of periodic transfer programs for
balance sheet items within Profit Center Accounting (PCA).
The DSO stores the data in an account-based model based on currency type (for example, local currency or group
currency).
This DSO is updated by the InfoSource EC-PCA: Line Items Periodic Transfer - Acutals (0EC_PCA_4) (/IMO/
PCA_IS04).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/CMPCA01
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Profit Center:
Transaction Data on Accounts (0EC_PCA_1).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
/IMO/CMPCA03
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Profit Center: Actual
Line Items (0EC_PCA_3).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.6.2 InfoSources
/IMO/PCA_IS01
This InfoSource contains the structure to provide periodic summary records for all profit and loss accounts (cost
elements) and balance sheet accounts that are transferred to Profit Center Accounting from table GLPCT to the
EDW Core Layer. This InfoSource is based on DataSource 0EC_PCA_1.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PCA_IS02
This InfoSource contains the structure to provide summary records for statistical key figures in Profit Center
Accounting that are stored in table GLPCT to the EDW Core Layer. This InfoSource is based on DataSource
0EC_PCA_2.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PCA_IS03
This InfoSource contains the structure to provide actual line items in Profit Center Accounting stored in table
GLPCA to the EDW Core Layer. This InfoSource is based on DataSource 0EC_PCA_3.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PCA_IS04
This InfoSource contains the structure to provide the line items from table GLPCA that are created as a result of
periodic transfer programs for balance sheet items to the EDW Core Layer. This InfoSource is based on
DataSource 0EC_PCA_4.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
2.6.3 CompositeProvider
CompositeProvider: /IMO/V_PCA01
This CompositeProvider contains Profit Center Accounting information for profit and loss accounts, balance sheet
accounts, and statistical key figures.
When creating your own queries on this CompositeProvider, consider the following:
● EC-PCA: Totals /IMO/D_PCA01 contains period totals for profit and loss accounts and balance sheet accounts
for different value types (for example, plan data and actual data). When implementing a query that includes
data for this DataStore object, you must include a filter or selection for your key figures based on the following
characteristics:
○ Value Type: 0VTYPE
○ Version: 0VERSION
○ Currency Type: 0CURRTYPE
● EC-PCA: Totals /IMO/D_PCA01 also includes carry forward balances that are stored against fiscal year period
000. Therefore, to calculate the accumulated balance in the query definition, accumulate the transaction
values of fiscal year period 0 to n.
● EC-PCA: Statistical Key Figures /IMO/D_PCA02 contains consumption quantity and stock quantity for
statistical key figures for all value types (for example, plan data and actual data). Quantities for a statistical key
figure are either recorded with a value against consumption quantity 0QUANTITY or stock quantity
0QUANT_AVRG, depending on the statistical key figure type.
When implementing a query that includes data for this DataStore object, you must include a filter or selection
for your key figures based on the following characteristics:
○ Value Type: 0VTYPE
○ Version: 0VERSION
● EC-PCA: Actual Line Items /IMO/D_PCA03 only contains actual line items. When implementing a query that
includes data for this DataStore object, you must include a filter or selection for your key figures based on the
following characteristics:
○ Currency Type: 0CURRTYPE
● If you want to show actual values for balance sheet accounts mainly based on actual line items, you need to
include the following:
○ Carry forward balance that is stored in DataStore object EC-PCA: Totals /IMO/D_PCA01 against period
000
○ Actual line items created as a result of periodic transfer programs for balance sheet items that are stored
separately in DataStore object EC-PCA: Line Items Periodic Transfer - Actuals /IMO/D_PCA04
● Some characteristics and key figures are not available for all DataStore objects. InfoObjects that are only
available for line item DataStore objects are assigned to their own dimensions in the CompositeProvider,
named […] (Line Item).
Data Modeling
Requires
2.6.4 Queries
/IMO/V_PCA01_Q0001
This query provides a comparison of Profit Center Accounting actual flows and balances between two defined
periods. You can drill down to document line items.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Actuals Comp. &0T_F3VEFC& - Flow for chosen period based
-
on line item data
&0T_F3VETC&.&0T_FYVKC&
Key Figure Carry Forward Comp. Per. - Carry Forward for chosen
comparison year
/IMO/V_PCA01_Q0002
This query provides a comparison of Profit Center Accounting flow and balance between two defined periods and a
comparison between actual, plan, and budget data on a balance level.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_PCA01_Q0003
This query provides a comparison of plan and actual values for all statistical key figures (both Fixed and Total
statistical key figure types). Key figure Consumption Quantity reflects statistical key figures of type Total, whereas
key figure Inventory Quantity reflects statistical key figures of type Fixed.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Overhead Costs Controlling component.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content Content for Profit Center Accounting, you need to make
the following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The controlling data is extracted from the ERP system to the Business Warehouse and made available there for
further analysis.
Possible analysis scenarios are monitoring current actuals, plan costs and commitments as well as related
statistical figures.
Additional Information
In addition to this documentation, please have a look at the following important SAP Notes for the CO-OM
extraction:
● Source tables
● Naming-prefixes for data records per application area
● Value type derivation between SAP ECC and SAP BW/4HANA
For usage of the CO totals extraction in delta mode please check the following SAP notes:
For performance improvements of the CO extractors, please have a look at SAP Notes 549552 and 1424403 .
Skipping the preselection of requested object numbers can improve extraction performance. Please check SAP
Note 2159875 for further details.
For delta loads for changed/deleted commitment line items, please have a look at SAP Note 1375245 .
2.7.1 CompositeProvider
CompositeProvider: /IMO/V_COOM1
For defining meaningful key figures such as restricted key figures or selections in analytic queries the following
characteristics are needed:
0VERSION Version
Data Modeling
Requires
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data for Cost center accounting. The data model follows the requirements for the layered scalable architecture
LSA++, which is optimized for BW running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Profit Center Accounting, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The controlling data for Cost center accounting is extracted from the ERP system to the Business Warehouse and
made available there for further analysis.
Possible analysis scenarios are monitoring current actuals, plan costs, commitments as well as related statistical
key figures.
SAP delivers sample analytic queries on top of the following CompositeProviders for CO-OM CCA:
Data Flow
/IMO/D_CCA10
This DSO (advanced) contains the actual line items for cost centers. The data is extracted by DataSource Actual
Line Items (0CO_OM_CCA_40).
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Activity Type of Partner Cost Center 0PART_ACTTY Depending on the Partner object type,
this field is derived from the partner ob
ject value
Delta Update
● Delta update: ADD Additive Extraction Via Extractor (e.g. LIS Info Structures)
● DataSource: 0CO_OM_CCA_40
Data Modeling
Requires
/IMO/D_CCA20
This DSO (advanced) contains the plan totals for cost centers. The data is extracted by DataSource Cost Centers:
Costs and Allocations (0CO_OM_CCA_1_D). There is a DTP Filter routine for field VTYPE (Value Type) to ensure that
only plan data (VTYPE = 020) is loaded.
Sources
This DSO (advanced) is filled by InfoSource CO-OM CCA: Plan Totals (0CO_OM_CCA_1_D) (/IMO/CCA_IS20).
Transformation
Startroutine
The startroutine is used to load only plan values (VTYPE = '020') into the DataStore object.
In case the DTP filter for VTYPE = '020' is used, this start routine can be removed.
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
/IMO/D_CCA30
This DSO (advanced) contains the commitment line items for cost centers. The data is extracted by DataSource
Cost Centers: Commitment Line Items (0CO_OM_CCA_10).
Sources
This DSO (advanced) is filled by InfoSource CO-OM CCA: Commitment Line Items (0CO_OM_CCA_10) (/IMO/
CCA_IS30).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
● Delta update: ADD Additive Extraction Via Extractor (e.g. LIS Info Structures)
● DataSource: 0CO_OM_CCA_10
Requires
/IMO/D_CCA50
This DSO (advanced) contains the statistical key figures for cost centers. The data is extracted by DataSource
Cost Centers: Statistical Key Figures (0CO_OM_CCA_30).
Sources
This DSO (advanced) is filled by InfoSource CO-OM CCA: Statistical Key Figures (0CO_OM_CCA_30) (/IMO/
CCA_IS50).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/CMCCA10
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Cost Centers: Actual
Costs-Line Items (0CO_OM_CCA_40).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMCCA20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Cost Centers: Costs
and Allocations (Delta Totals)(0CO_OM_CCA_1_D).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMCCA30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Cost Centers:
Commitment Line Items (0CO_OM_CCA_10).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.7.2.2 InfoSources
/IMO/CCA_IS10
This InfoSource contains the structure to provide actual line items for cost centers to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/CCA_IS20
This InfoSource contains the structure to provide plan totals for cost centers to the EDW Core Layer.
Transformation
Data Source: Cost Centers: Costs and Allocations (Delta Totals) (0CO_OM_CCA_1_D)
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/CCA_IS30
This InfoSource contains the structure to provide commitment line items for cost centers to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/CCA_IS50
This InfoSource contains the structure to provide statistical key figures for cost centers to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
2.7.2.3 CompositeProvider
CompositeProvider: /IMO/V_CCA01
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: Variable
0CIPM_VERSION_PLAN
0VTYPE: “20”
0VSTAT: #
0INFOPROV: /IMO/D_CCA20
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTSTAT: #
0VTYPE: “10”
0INFOPROV: /IMO/D_CCA10
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTSTAT: #
0VTYPE: “10”
0INFOPROV: /IMO/D_CCA10
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VTSTAT: #
0VTYPE: “50”
0DB_CR_IND: “H”
0METYPE: “1000”,“1001”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “10”
0INFOPROV: /IMO/D_CCA10
Structures
Data Modeling
/IMO/D_CCA20
DataStore Object (Advanced) CO-OM CCA: Plan
Definition
CompositeProvider: /IMO/V_CCA02
Use
This CompositeProvider contains the statistical key figures data from cost center perspective.
For defining meaningful key figures such as restricted key figures or selections in analytic queries the following
characteristics are needed:
0VERSION Version
0VTYPE: “20”
0VERSION: “0”
0VTYPE: “10”
0VTYPE: “20”
0VERSION: “0”
0VTYPE: “10”
Structures
Selected period and YTD values /IMO/V_CCA02_S002 Selected Period and corresponding YTD
values using 0FISCPER
Data Modeling
Requires
2.7.2.4 Queries
/IMO/V_CCA01_Q0001
This query displays costs for a selected period and previous as well as YTD values by cost center. This query is
based on CompositeProvider CO-OM CCA: Costs and Allocations (/IMO/V_CCA01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Actual &00T_FPIE_YEAR& /IMO/V_CCA01_RK002 Previous Fiscal Year YTD value
YTD
up to selected Period.
Key Figure Actual &0T_FPIE_YEAR& YTD /IMO/V_CCA01_RK002 Current Fiscal Year YTD value
up to selected Period.
/IMO/V_CCA01_Q0002
This query displays costs for all periods of the selected and previous fiscal year. This query is based on
CompositeProvider CO-OM CCA: Costs and Allocations (/IMO/V_CCA01).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_CCA01_Q0003
This query displays actual and plan costs for all periods of the selected and previous fiscal year. This query is
based on CompositeProvider CO-OM CCA: Costs and Allocations (/IMO/V_CCA01).
Data Modeling
Filters
Free Characteristics
Free Characteristics
/IMO/V_CCA01_Q0004
This query is based on CompositeProvider CO-OM CCA: Costs and Allocations (/IMO/V_CCA01).
Structure
Filters
Free Characteristics
Columns
/IMO/V_CCA02_Q0001
This query displays statistical key figure values for a selected period, YTD values according to the selected period,
and YTD values for the previous fiscal year. This query is based on CompositeProvider CO-OM CCA: Statistical Key
Figures (/IMO/V_CCA02).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Rows
Use
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data for internal orders. The data model follows the requirements for the layered scalable architecture LSA++,
which is optimized for BW running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7]
Before using the SAP HANA-optimized Business Content for Profit Center Accounting, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The controlling data for internal orders is extracted from the ERP system to the Business Warehouse and made
available there for further analysis.
Possible analysis scenarios are monitoring current actuals, plan costs, commitments, as well as related statistical
key figures.
SAP delivers sample analytic queries on top of the following CompositeProviders for CO-OM OPA:
Data Flow
/IMO/D_OPA10
This DSO (advanced) contains the actual line items for internal orders. The data is extracted by DataSource
Orders: Actual Line Items Using Delta Extraction (0CO_OM_OPA_40).
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Activity Type of Partner Cost Center 0PART_ACTTY Depending on the Partner object type,
this field is derived from the partner ob
ject value
Delta Update
● Delta update: ADD Additive Extraction Via Extractor (e.g. LIS Info Structures)
● DataSource: 0CO_OM_OPA_40
Data Modeling
Requires
/IMO/D_OPA20
This DSO (advanced) contains plan data for internal orders. The data is extracted by DataSource Orders: Costs
and Allocations (Delta Totals) (0CO_OM_OPA_1_D). There is a DTP Filter routine for field VTYPE (Value Type) to
ensure that only plan data (VTYPE = 020) is loaded.
Sources
This DSO (advanced) is filled by the InfoSource CO-OM OPA: Plan Totals (0CO_OM_OPA_1_D) (/IMO/OPA_IS20).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Activity Type of Partner Cost Center 0PART_ACTTY Depending on the Partner object type,
this field is derived from the partner ob
ject value
Delta Update
Data Modeling
Requires
/IMO/D_OPA30
This DSO (advanced) contains commitment line items for internal orders. The data is extracted by DataSource
Orders: Commitment Line Items (0CO_OM_CCA_7).
This DSO (advanced) is filled by the InfoSource Orders: CO-OM OPA: Commitment Line Items (0CO_OM_OPA_7)
(/IMO/OPA_IS30).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
● Delta update: ADD Additive Extraction Via Extractor (e.g. LIS Info Structures)
● DataSource: 0CO_OM_OPA_7
Data Modeling
Requires
/IMO/D_OPA50
This DSO (advanced) contains statistical key figures for internal orders. The data is extracted by DataSource
Orders: Statistical key figures(0CO_OM_OPA_30).
Sources
This DSO (advanced) is filled by InfoSource CO-OM OPA: Statistical Key Figures (0CO_OM_OPA_30) (/IMO/
OPA_IS50).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
/IMO/CMOPA10
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Orders: Actual Line
Items Using Delta Extraction (0CO_OM_OPA_40).
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMOPA20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Orders: Costs and
Allocations (Delta Totals) (0CO_OM_OPA_1_D).
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMOPA30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Orders: Commitment
Line Items (0CO_OM_OPA_7).
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.7.3.2 CompositeProvider
CompositeProvider: /IMO/V_OPA01
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
0DB_CR_IND: “H”
0METYPE: “1001”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “10”
0INFOPROV: /IMO/D_OPA10
0DB_CR_IND: “H”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION“0”
0VTYPE: “10”
0INFOPROV: /IMO/D_OPA10
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “40”
0INFOPROV: /IMO/D_OPA30
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “10”
0INFOPROV: /IMO/D_OPA10
0DB_CR_IND: “S”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “10”
0INFOPROV: /IMO/D_OPA10
KeyFigure: KeyFigure:
0DB_CR_IND : “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: Variable
0CIPM_VERSION_PLAN
0TYPE: “20”
0INFOPROV: /IMO/D_OPA20
Structures
Data Modeling
CompositeProvider: /IMO/V_OPA02
This CompositeProvider contains the statistical key figures data from orders perspective.
The following characteristics are needed for a meaningful definition of key figures such as restricted key figures or
selections in analytic queries:
0VERSION Version
0VERSION: “0”
0VTYPE: “10”
0VERSION: “0”
0VTYPE: “10”
0VERSION: Variable
0CIPM_VERSION_PLAN
0VTYPE : “20”
0VERSION: Variable
0CIPM_VERSION_PLAN
0VTYPE: “20”
Data Modeling
Requires
2.7.3.3 InfoSources
/IMO/OPA_IS10
This InfoSource contains the structure to provide actual line items for internal orders to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/OPA_IS20
This InfoSource contains the structure to provide plan data for internal orders to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/OPA_IS30
This InfoSource contains the structure to provide commitment line items for internal orders to the EDW Core
Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/OPA_IS50
This InfoSource contains the structure to provide statistical key figures for internal orders to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
2.7.3.4 Queries
/IMO/V_OPA01_Q0001
This query displays costs of internal orders for the selected fiscal year. This query is based on CompositeProvider
CO-OM OPA: Cost and Allocations (/IMO/V_OPA01).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
FM area 0FM_AREA
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_OPA01_Q0002
This query displays costs of internal orders for the selected fiscal year. This query is based on CompositeProvider
CO-OM OPA: Cost and Allocations (/IMO/V_OPA01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
FM area 0FM_AREA
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Characteristic structure
/IMO/V_OPA02_Q0001
This query displays statistical key figure values per order for a selected period and YTD values according to the
selected period. This query is based on CompositeProvider CO-OM OPA: Statistical Key Figures (/IMO/V_OPA02).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Use
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
overhead cost controlling data for projects. The data model follows the requirements for the layered scalable
architecture LSA++, which is optimized for BW running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Overhead Cost Controlling for Projects, you need to
make the following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
The controlling data for projects is extracted from the ERP system to the Business Warehouse and made available
there for further analysis.
Possible analysis scenarios are monitoring current actuals, and plan costs, commitments as well as related
statistical key figures.
SAP delivers sample analytic queries on top of the following CompositeProviders for CO-OM WBS:
Data Flow
Data Flow
This DataStore Object contains the Actual Line items data for network activity elements.
Sources
This DSO is filled by the InfoSource CO-OM NAE: Actual Line Items (0CO_OM_NAE_2) (technical name: /IMO/
NAE_IS10).
Transformation
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DataStore Object contains the Actual Line items data for network activity elements. There is a DTP Filter
routine for field VTYPE (Value Type) to ensure that only plan data (VTYPE = 020) is loaded.
Sources
This DSO is filled by the InfoSource CO-OM NAE: Plan Totals (0CO_OM_NAE_1_D) (technical name: /IMO/
NAE_IS20).
Transformation
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DataStore Object contains the Actual Line items data for network activity elements.
Sources
This DSO is filled by the InfoSource CO-OM NAE: Commitment Line Items (0CO_OM_NAE_3) (technical
name: /IMO/NAE_IS30).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
This DataStore Object contains the statistical key figures data for network activity elements.
Sources
This DSO is filled by the InfoSource CO-OM NAE: Statistical Key Figures (technical name: 0CO_OM_NAE_4)
(technical name: /IMO/NAE_IS50).
Transformation
Field Routines
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
This DataStore Object contains the Actual Line items data for networks.
Sources
This DSO is filled by the InfoSource CO-OM NTW: Actual Line Items (0CO_OM_NTW_2) (technical name: /IMO/
NTW_IS10).
Transformation
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Data Modeling
Requires
This DataStore Object contains the plan totals data for networks. There is a DTP Filter routine for field VTYPE
(Value Type) to ensure that only plan data (VTYPE = 020) is loaded.
Sources
This DSO is filled by the InfoSource CO-OM NTW: Plan Totals (0CO_OM_NTW_1_D) (technical name: /IMO/
NTW_IS20).
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DataStore Object contains the commitment line item data for networks.
Sources
Transformation
Field Routines
Delta Update
Data Modeling
Requires
This DataStore Object contains the statistical key figures data for networks.
Sources
This DSO is filled by the InfoSource CO-OM NTW: Statistical Key Figures (0CO_OM_NTW_4) (technical
name: /IMO/NTW_IS50).
Transformation
Field Routines
Delta Update
Data Modeling
This DataStore Object contains the Actual Line items data for network activities.
Sources
This DSO is filled by the InfoSource CO-OM NWA: Actual Line Items (0CO_OM_NWA_2) (technical name: /IMO/
NWA_IS10).
Transformation
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
This DataStore Object contains the plan totals data for network activities. There is a DTP Filter routine for field
VTYPE (Value Type) to ensure that only plan data (VTYPE = 020) is loaded.
Sources
This DSO is filled by the InfoSource CO-OM NWA: Plan Totals (0CO_OM_NWA_1_D) (technical name: /IMO/
NWA_IS20) .
Transformation
Field Routines
Activity Type of Partner Cost Center 0PART_ACTTY Derive from Partner Object type
(0PIOBJSV) and Partner Object
(0PIOVALUE)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DataStore Object contains the commitment line item data for network activities.
Sources
Transformation
Field Routines
Delta Update
Data Modeling
Requires
This DataStore Object contains the statistical key figures data for network activities.
Sources
This DSO is filled by the InfoSource CO-OM NWA: Statistical Key Figures (0CO_OM_NWA_4) (technical
name: /IMO/NWA_IS50) .
Transformation
Field Routines
Delta Update
Data Modeling
/IMO/D_WBS10
This DSO (advanced) contains the actual line items for WBS elements. The data is extracted by DataSource WBS
Elements: Actual Costs Using Delta Extraction (0CO_OM_WBS_6).
Sources
This DSO (advanced) is filled by the Sources CO-OM WBS: Actual Line Items (0CO_OM_WBS_6) (/IMO/
WBS_IS10).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Activity Type of Partner Cost Center 0PART_ACTTY Depending on the Partner object type,
this field is derived from the partner ob
ject value
Delta Update
● Delta update: ADD Additive Extraction Via Extractor (e.g. LIS Info Structures)
● DataSource: 0CO_OM_WBS_6
Data Modeling
/IMO/D_WBS20
This DSO (advanced) contains the plan data for WBS elements. The data is extracted by DataSource WBS
Elements: Costs (Delta Totals) (0CO_OM_WBS_1_D). There is a DTP Filter routine for field VTYPE (Value Type) to
ensure that only plan data (VTYPE = 020) is loaded.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Activity Type of Partner Cost Center 0PART_ACTTY Depending on the Partner object type,
this field is derived from the partner ob
ject value
Delta Update
Data Modeling
Requires
/IMO/D_WBS30
This DSO (advanced) contains commitment line items for WBS elements. The data is extracted by DataSource
WBS Elements: Commitment Line Items (0CO_OM_WBS_7).
Sources
This DSO (advanced) is filled by the Sources CO-OM WBS: Commitment Line Items (0CO_OM_WBS_7) (/IMO/
WBS_IS30).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
● Delta update: ADD Additive extraction using extractor like LIS Infostructures.
● DataSource: 0CO_OM_WBS_7
Data Modeling
Requires
/IMO/D_WBS50
This DSO (advanced) contains statistical key figures for WBS elements. The data is extracted by DataSource WBS
elements: Statistical key figures (0CO_OM_WBS_4).
Sources
This DSO (advanced) is filled by the Sources CO-OM WBS: Statistical Key Figures (0CO_OM_WBS_4) (/IMO/
WBS_IS50).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
Data Modeling
Requires
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delta extraction:
Activity Elements Actual costs (0CO_OM_NAE_2).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delta Extraction:
Networks Actual Costs (0CO_OM_NTW_2).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Network Header:
Commitment Line Items (0CO_OM_NTW_3).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Network Activity:
Costs (Delta Totals) (0CO_OM_NWA_1_D).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMWBS20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource WBS Elements: Costs
(Delta Totals) (0CO_OM_WBS_1_D).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMWBS30
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMWBS10
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource WBS Elements: Actual
Costs Using Delta Extraction (0CO_OM_WBS_6).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.7.4.2 CompositeProvider
This CompositeProvider enables you to analyze accounting data for project network activity elements and is
composed of
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
Data Modeling
This CompositeProvider enables you to analyze accounting data for project networks and is composed of
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
Data Modeling
This CompositeProvider enables you to analyze accounting data for project network activity and is composed of
0VERSION Version
Data Modeling
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
0CURTYPE = 20
0METYPE = 1000
0VERSION = 0CIPM_VERSION_PLAN
0VTYPE = 20
0VTDETAIL = [1-4]
0FISCPER3 = [1 – 16]
0CURTYPE = 20
0METYPE = 1000
0VERSION = 0
0VTYPE = 10
0VTDETAIL = [1-4]
0FISCPER3 = [1 – 16]
0CURTYPE = 20
0METYPE = 1000
0VERSION = 0
0VTYPE = 40
0CURTYPE = 20
0METYPE = 1001
0VERSION = 0
0VTYPE = 10
0VTDETAIL = [1-4]
0FISCPER3 = [1 – 16]
0CURTYPE = 20
0METYPE = 1001
0VERSION = 0CIPM_VERSION_PLAN
0VTYPE = 20
0VTDETAIL = [1-4]
0FISCPER3 = [1 – 16]
Data Modeling
CompositeProvider: /IMO/V_WBS01
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: 0CIPM_VERSION_PLAN
0VTYPE: “20”
0INFOPROV: /IMO/D_WBS20
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “10”
0INFOPROV: /IMO/D_WBS10
0DB_CR_IND: “S”
0METYPE: “1000”
0VALUATION: Variable
0CIPM_VALUATION
0VERSION: “0”
0VTYPE: “40”
0INFOPROV: /IMO/D_WBS30
Structures
Data Modeling
0FI_RACTIV
InfoObject Business Transaction
CompositeProvider: /IMO/V_WBS02
This CompositeProvider contains statistical key figures data from projects perspective.
For defining meaningful key figures, such as restricted key figures or selections in analytic queries, the following
characteristics are needed:
0VERSION Version
0VERSION: Variable
0CIPM_VERSION_PLAN
0VTYPE: “20”
0VERSION: “0”
0VTYPE: “10”
0VERSION: Variable
0CIPM_VERSION_PLAN
0VTYPE: “20”
0VERSION: “0”
0VTYPE: “10”
Data Modeling
Requires
(Advanced)
2.7.4.3 InfoSources
/IMO/WBS_IS10
This InfoSource contains the structure to provide actual line items for WBS elements to the EDW Core Layer.
Data Source: WBS Elements: Actual Costs Using Delta Extraction (0CO_OM_WBS_6)
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/WBS_IS20
This InfoSource contains the structure to provide plan data for WBS elements to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/WBS_IS30
This InfoSource contains the structure to provide commitment line items for WBS elements to the EDW Core
Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/WBS_IS50
This InfoSource contains the structure to provide statistical key figures for WBS elements to the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide actuals line item data for network activity elements into the EDW
Core Layer. This InfoSource is based on DataSource 0CO_OM_NAE_2.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Requires
This InfoSource contains the structure to provide plan totals data for network activity elements into the EDW Core
Layer. This InfoSource is based on DataSource 0CO_OM_NAE_1_D.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide commitment line item data for network activity elements into the
EDW Core Layer. This InfoSource is based on DataSource 0CO_OM_NAE_3.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide statistical key figures data for network activity elements into the
EDW Core Layer. This InfoSource is based on DataSource 0CO_OM_NAE_4.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
This InfoSource contains the structure to provide actuals line item data for networks into the EDW Core Layer. This
InfoSource is based on DataSource 0CO_OM_NTW_2.
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide plan totals data for networks into the EDW Core Layer. This
InfoSource is based on DataSource 0CO_OM_NTW_1_D.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide commitment line item data for networks into the EDW Core
Layer. This InfoSource is based on DataSource 0CO_OM_NTW_3.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide statistical key figures data for networks into the EDW Core Layer.
This InfoSource is based on DataSource 0CO_OM_NTW_4.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
This InfoSource contains the structure to provide actuals line item data for network activity into the EDW Core
Layer. This InfoSource is based on DataSource 0CO_OM_NWA_2.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide plan totals data for network activity into the EDW Core Layer.
This InfoSource is based on DataSource 0CO_OM_NWA_1_D.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide commitment line item data for network activity into the EDW
Core Layer. This InfoSource is based on DataSource 0CO_OM_NWA_3.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system..
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide statistical key figures data for network activity into the EDW Core
Layer. This InfoSource is based on DataSource 0CO_OM_NWA_4.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Requires
2.7.4.4 Queries
/IMO/V_WBS01_Q0002
This query displays YTD costs for projects up to the selected period. This query is based on CompositeProvider
CO-OM WBS: Cost and Allocations (/IMO/V_WBS01).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Characteristic structure
/IMO/V_WBS02_Q0001
This query displays statistical key figure values per WBS element for a selected fiscal year and the total value. This
query is based on CompositeProvider CO-OM WBS: Statistical Key Figures (/IMO/V_WBS02).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_WBS01_Q0001
This query displays YTD costs for projects up to the selected period. This query is based on CompositeProvider
CO-OM WBS: Cost and Allocations (/IMO/V_WBS01).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
You can use this query to get a cost and revenue overview of selected projects.
Structure
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0PS_GUID__0PROJECT
Characteristic Project Definition —
Columns
Object Type Name Technical Name
/IMO/V_PRO01_RK0002
Key Figure Actual Costs
/IMO/V_PRO01_RK0001
Key Figure Plan Costs
/IMO/V_PRO01_RK0003
Key Figure Commitments
/IMO/V_PRO01_RK0004
Key Figure Actual Revenues
/IMO/V_PRO01_RK0005
Key Figure Planned Revenues
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP or SAP S/4HANA Product Cost Controlling.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modeling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Product Cost Controlling, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
This content provides you with an entry layer to extract and transform product cost controlling data into SAP BW/
4HANA in the area of product cost analysis, cost component split, and itemization.
CO-PC DataFlow
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Production Cost
Analysis (0CO_PC_10).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Product Cost Analysis:
Cost Component Split (0CO_PC_PCP_20).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Product Costing
Analysis: Itemization (0CO_PC_PCP_30).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
2.8.2 InfoSource
This InfoSource contains the structure to provide product cost analysis data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide product cost component split into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide material cost itemization data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Sales and Distribution.
You can use the SAP HANA-optimized Business Content for Sales and Distribution to analyze sales order data,
delivery data, billing data, condition data, and delivery service data.
InfoArea Delivery Service – SAP HANA-optimized (/IMO/SDDLV) contains the CompositeProvider SD-DLV: Service
Level (/IMO/V_SD50), which enables you to analyze delivery service quality.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modeling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
You can track changes to amounts and quantities for sales documents over a specified time period for the
following DataStore objects:
These changes are tracked using InfoObject Statistics Date as Calendar Day (0ST_UP_DTE). All key figures are
updated using aggregation type “Summation”.
Note
If you also want to track changes based on characteristics, such as the material group or route, you must add
the corresponding characteristics to the key part of the DSOs.
Note
If you want to report on the basis of the creation date, rather than tracking the changes to sales documents, you
need to make the following changes to adapt the content:
● Move characteristic 0CALDAY from the key part of DSO to the data part
● Update all time characteristics using characteristic 0CREATEDON (instead of 0ST_UP_DTE) in BW
transformations
● Change the aggregation type for all key figures to “Overwrite”
Integration
Generic InfoObjects
InfoObject Logic
The delivered data flows for sales order, delivery and invoice data contain a key figure reversal for credit postings.
Therefore all records with credit postings are written into the DSOs (advanced) with positive sign. Using formulas
and restricting key figures with values of characteristics 0DEB_CRED and 0DOC_CLASS in the analytic query
enables you to address the values for each document category (e.g. returns) individually.
Overview
3.1 Prerequisites
Before using the SAP HANA-optimized Business Content for Sales and Distribution, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Settings for SD
● If you want to use DataSource 2LIS_11_V_ITM or 2LIS_11_V_SCL, you first need to implement SAP Note
1541366 in your SAP ERP source system.
● Activating Data Extraction in Logistics Customizing Cockpit (SAP ERP) [page 498]
● Transfering Global Settings and Exchange Rates [page 499]
● Performing Setup: SD (SAP ERP) [page 499]
Context
If you set the update for the logistics extract structure to active, data is written to the extract structures, both
online and during completion of setup tables.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node Logistics application 11: SD Sales BW Extract structures .
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures you want to
use:
○ MC11VA0HDR: Extraction SD Sales BW: Document Header for DataSource 2LIS_11_VAHDR
○ MC11VA0ITM: Extraction SD Sales BW: Document Item for DataSource 2LIS_11_VAITM
○ MC11VA0KON: Extraction SD Sales BW: Document Condition for DataSource 2LIS_11_VAKON
○ MC11VA0SCL: Extraction SD Sales BW: Document Schedule Line for DataSource 2LIS_11_VASCL
○ MC11VA0STH: Extraction MD Order Header Status for DataSource 2LIS_11_VASTH
○ MC11VA0STI: Extraction MD Order Item Status for DataSource 2LIS_11_VASTI
○ MC11V_0ITM: Extraction SD Sales BW: Document Item Allocation for DataSource 2LIS_11_V_ITM
○ MC11V_0SCL: Extraction SD Sales BW: Allocation Schedule Line for DataSource 2LIS_11_V_SCL
○ MC11V_0SSL: Extraction MD Sales: Order Delivery for DataSource 2LIS_11_V_SSL
4. Expand in hierarchy structure node Logistics application – 12: LE Shipping BW – Extract structures
5. In the Update column for extract structure BW, click on the Inactive link to activate the following extract
structures – dependent on the extract structures you want to use:
1. MC12VC0HDR: Extraction LE Shipping BW: Document Header for DataSource 2LIS_12_VCHDR
2. MC12VC0ITM: Extraction LE Shipping BW: Document Item for DataSource 2LIS_11_VCITM
3. MC12VC0SCL: Extraction LE Shipping BW: Schedule Line Delivery for DataSource 2LIS_11_VCSCL
6. Expand in hierarchy structure node Logistics application – 13: SD Billing BW – Extract structures
7. In the Update column for extract structure BW, click on the Inactive link to activate the following extract
structures, depending on the extract structures you want to use:
○ MC13VD0HDR: Extraction SD Billing Document BW: Document Header for DataSource 2LIS_13_VDHDR
○ MC13VD0ITM: Extraction SD Billing Document BW: Document Item for DataSource 2LIS_13_VDITM
○ MC13VD0KON: Extraction SD Billing Document BW: Document Condition for DataSource 2LIS_13_VDKON
8. Select the required Update Mode.
Context
Before loading data from Sales and Distribution records into SAP BW/4HANA, you have to transfer currency
codes, units of measure, fiscal year variants, and exchange rates from your SAP source system to your SAP BW/
4HANA system.
Procedure
Next Steps
Before performing an initial upload of Sales and Distribution records into SAP BW/4HANA, you have to run a
reconstruction. The reconstruction writes the documents to be initially extracted to a setup table.
Procedure
1. In your SAP ERP system, call transaction OLI7BW (Perform setup – SD Sales BW: Statistical setup from Old
Documents: Orders).
2. After changing the parameters in Document data restriction (optional) and Control Selection (mandatory), run
the reconstruction.
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application SD Sales BW “11”,
LE Shippping BW “12”, SD Billing BW “13”.
Recommendation
Before performing a new setup, run this transaction.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) SAP Customer Implementation Guide
Integration with Other SAP Components Data Transfer to Business Warehouse Settings for Application-
Specific Data Sources (PI) Logistics Managing Extract Structures Initialization .
/IMO/D_SD10
This DSO (advanced) contains sales document header data for orders and quotations (but not for requests).
Sources
This DSO is filled by the InfoSource Sales Document Header Data (2LIS_11_VAHDR) (technical name: /IMO/
SD_IS10).
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for sales order docu
ments) or “C” (Credit, for returns)
Update Date 0UPD_DATE Fill with the system date during the data
load
BW Delta Process: Update Mode 0RECORDMODE Change of Reverse Images to After Im
ages
*For more information about document classification in SD, see the overview page Sales and Distribution (SAP
HANA-Optimized) [page 493].
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_VAHDR
Data Modeling
Requires
/IMO/D_SD11
This DSO (advanced) contains sales document item data for orders and quotations (but not requests).
This DSO is filled by InfoSource Sales Document Item Data (2LIS_11_VAITM) (technical name: /IMO/SD_IS11).
Prerequisites
You need to load the following master data before loading the transactional data into this DSO:
● 0MATERIAL
● 0ORG_UNIT
● 0BP_GRP
● 0PROD_CATEG
● 0CRM_SALORG
● 0SALESORG
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for sales order docu
ments) or “C” (Credit, for returns)
Update Date 0UPD_DATE Fill with the system date during the data
load
BP: Business Partner Group (from Hier 0BP_GRP Read BP Group and assign to business
archy) partner
Net value in statistic currency 0NET_VAL_S Convert to statistics currency and re
verse sign for returns
Quantity in base unit of measure 0QUANT_B Convert units of measure and reverse
sign for returns
Subtotal* from pricing procedure 0SUBTOT_*S Convert to statistics currency and re
verse sign for returns
No. of orders resulting from quotations 0ORD_QUOT Counted number of orders received from
quotations and reversed +/- sign for
negative sales documents.
Net value order item, resulting from quo 0NETVALQUOT Converted to statistic currency and re
tations versed sign for negative sales docu
ments.
No. of rejected quotation items 0NOQUOT_REJ Counts all quotations where a rejection
reason is given.
Net value of rejected quotation items 0NETVAL_REJ Calculation of net value of rejected quo
tations, conversion to statistic currency
and reversed +/- sign for negative sales
documents.
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_VAITM
Data Modeling
Key figure Net value order item, resulting from quo 0NETVALQUOT
tations
/IMO/D_SD14
This DataStore Object (advanced) contains condition information at an order’s item level. The condition value and
condition amount for each condition type are displayed for each order position.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during data load.
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_VAKON
Data Modeling
Requires
/IMO/D_SD16
This DSO (advanced) contains open order values and quantities in Sales and Shipping. You can use this DSO for
delivery-relevant sales orders or deliveries that refer to sales orders.
Sources
This DSO is filled by the InfoSource Sales-Shipping Allocation Item Data (2LIS_11_V_ITM) (technical name: /IMO/
SD_IS16)
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for sales order docu
ments) or “C” (Credit, for returns)
Update Date 0UPD_DATE Fill with the system date during the data
load
Open orders quantity in base unit of 0OPORDQTYBM Convert unit of measure with factor, and
measure reverse sign for returns
Net value of open orders in statistics cur 0OPORDVALSC Convert to statistics currency and re
rency verse sign for returns
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_V_ITM
Data Modeling
Requires
/IMO/D_SD20
Sources
This DSO is filled by the InfoSource Delivery Header Data (2LIS_12_VCHDR) (technical name: /IMO/SD_IS20).
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for delivery docu
ments) or “C” (Credit, for return deliver
ies)
Update Date 0UPD_DATE Fill with the system date during the data
load
BW Delta Process: Update Mode 0RECORDMODE Change of Reverse Images to After Im
ages
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_12_VCHDR
Data Modeling
Requires
/IMO/D_SD21
Sources
This DSO is filled by InfoSource Delivery Item Data (2LIS_12_VCITM) (technical name: /IMO/SD_IS21).
Prerequisites
You need to load the following master data before loading the transactional data into this DSO:
● 0MATERIAL
● 0ORG_UNIT
● 0BP_GRP
● 0PROD_CATEG
● 0CRM_SALORG
● 0SALESORG
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for delivery docu
ments) or “C” (Credit, for return deliver
ies)
Update Date 0UPD_DATE Fill with the system date during the data
load
BP: Business Partner Group (from Hier 0BP_GRP Read BP Group to business partner
archy)
Quantity in base unit of measure 0QUANT_B Convert units of measure and reverse
sign for return deliveries
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_12_VCITM
Requires
/IMO/D_SD30
Sources
This DSO is filled by the InfoSource Billing Document Header Data (2LIS_13_VDHDR) (technical name: /IMO/
SD_IS30).
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for invoice docu
ments) or “C” (Credit, for credit memos).
Update Date 0UPD_DATE Fill with the system date during the data
load
BW Delta Process: Update Mode 0RECORDMODE Change of Reverse Images to After Im
ages
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_13_VDHDR
Data Modeling
/IMO/D_SD31
Sources
This DSO is filled by the InfoSource Billing Document Item Data (2LIS_13_VDITM) (technical name: /IMO/
SD_IS31).
Prerequisites
You need to load the following master data before loading the transactional data into this DSO:
● 0MATERIAL
● 0ORG_UNIT
● 0BP_GRP
● 0PROD_CATEG
● 0CRM_SALORG
● 0SALESORG
Transformation
Field Routines
Credit/Debit posting* 0DEB_CRED Fill with “D” (Debit, for invoice docu
ments) or “C” (Credit, for credit memos)
Update Date 0UPD_DATE Fill with the system date during the data
load
BP: Business Partner Group (from Hier 0BP_GRP Read BP Group to business partner
archy)
Net value in statistic currency 0NET_VAL_S Convert to statistics currency and re
verse sign for credit memos
Quantity in base unit of measure 0QUANT_B Convert units of measure and reverse
sign for credit memos
Subtotal* from pricing procedure 0SUBTOT_*S Convert to statistics currency and re
verse sign for credit memos
*For more information about how documents are classified in SD, see the overview page Sales and Distribution
(SAP HANA-Optimized) [page 493].
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_13_VDITM
Data Modeling
Requires
/IMO/D_SD34
This DataStore object (advanced) contains condition information at billing item level. The condition value and
condition amount for each condition type are displayed for each order position.
Sources
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during data load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_13_VDKON
Data Modeling
Requires
/IMO/D_SD50
The DataStore object (advanced) integrates data on orders and free-of-charge orders on the basis of the order
items (DataSource 2LIS_11_VAITM) and aggregated information on order delivery schedule lines (DataSource
2LIS_11_V_SSL).
Reversed records are not being deleted in this DataStore object. Instead, a flag (0ITEM_DEL = “X”) is set for such
records.
Sources
Transformation
● Start Routine
The start routine for the updates ensures that only orders (0IMODOCCAT = “C”) and free-of-charge orders
(0IMODOCCAT = “I”) are updated in the DataStore object.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image
(“ ”).
● Start Routine
The start routine for the updates ensures that only orders (0IMODOCCAT = “C”) and free-of-charge orders
(0IMODOCCAT = “I”) are updated in the DataStore object.
● Field Routines
Quantity delivered early acc. req. 0DLVQEYCR Calculation of quantity delivered before re
delivery date quested delivery date
Quantity Delivered Late According 0DLVQLECR Calculation of quantity delivered after re
to Requested Delivery Date quested delivery date.
Quantity Delivered Early According 0DLVQEYSC Calculation of quantity delivered before con
to Schedule Line Date firmed delivery date of schedule line.
Quantity Delivered Late According 0DLVQLESC Calculation of quantity delivered after con
to Schedule Line Date firmed delivery date of schedule line.
Amount with Set GI Status 0GIS_QTY If the delivery status is complete (“C”), the de
livery quantity corresponds to the amount with
set GI status.
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image
(“ ”) and filled with before image (“X”) for de
leted schedule lines.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_VAITM
Delta Update
- Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
Data Modeling
Requires
/IMO/D_SD51
This DataStore object (advanced) contains data from orders and orders free of charge on the basis of order
headers with status information, as well as aggregate information for order and return items.
Reversed records are not being deleted in this DataStore object . Instead, a flag (0HEADER_DEL = “X”) is set for
such records.
Sources
Transformation
● Field Routines
Delivered Early According 0DLVIEYCR Calculation of items which were delivered early according to
to Requested Delivery requested delivery date considering deleted items.
Date
Delivered Late According 0DLVILECR Calculation of items which were delivered late according to re
to Requested Delivery quested delivery date considering deleted items.
Date
Delivered Early/Late Ac 0DLVIELCR Calculation of items which were either delivered early or late
cording to Requested De according to requested delivery date considering deleted
livery Date items.
Confirmed as Requested 0ICOASREQ Calculation of items which were delivered as requested consid
ering deleted items.
Actual Delivered Value 0DLV_VAL Calculation of actual delivered value; multiplication of delivery
quantity and net price considering deleted items.
Net value of the order in 0NET_VAL_HD Calculation of confirmed order value; multiplication of con
document currency firmed quantity and net price considering deleted items.
Less Delivered than Re 0DLVIUNDR Calculation of items for which less was delivered than re
quested quested. In case the unlimited tolerance indicator is not set for
the sales order item, the configured underdelivery tolerance is
taken into account.
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image (“ ”).
● Start Routine
The start routine for the updates ensures that only orders (0IMODOCCAT = “C”) and free-of-charge orders
(0IMODOCCAT = “I”) are updated in the DataStore object.
● Field Routines
Customer 0GN_CUSTOM Concatenation of the Source System ID, Object Type and
Customer.
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image (“ ”).
● Start Routine
The start routine for the updates ensures that only orders (0IMODOCCAT = “C”) and free-of-charge orders
(0IMODOCCAT = “I”) are updated in the DataStore object.
● Field Routines
● Field Routines
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image (“ ”).
Delta Update
The following delta update is supported for this DataStore object:
Delta Update
- Delta Update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
Delta Update
- Delta Update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
Delta Update
- Delta Update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
Data Modeling
Requires
/IMO/D_SD52
This DataStore object (advanced) enables you to perform evaluations with respect to the service level at the order
header and order items level. As a result, analyses such as order quantities delivered too late as a proportion of the
total number of orders/order items are possible.
Sources
Transformation
● Start Routine
The start routine creates internal tables which are used in field routines to derive the Product Category
0PROD_CATEG from the corresponding Product Hierarchy 0PROD_HIER and the BP: Business Partner Group
0BP_GRP.
● Field Routines
Cumulated Order Processing Time for 0CUML_TME Calculates difference between the creation date of the
All Document Items item and the last goods issue date.
Delivered early/late according to req. 0DLVIELCR Calculation of items which were delivered early/late ac
delivery date cording to requested delivery date.
Delivered early/late according to 0DLVIELSC Calculation of items which were delivered early/late ac
schedule line date cording to schedule line date.
Delivered early acc. req. delivery date 0DLVIEYCR Calculation of items which were delivered early according
to requested delivery date.
Delivered early acc. schedule line date 0DLVIEYSC Calculation of items which were delivered early according
to schedule line date.
Delivered late acc. req. delivery date 0DLVILECR Calculation of items which were delivered late according
to requested delivery date.
Delivered late acc. schedule line date 0DLVILESC Calculation of items which were delivered late according
to schedule line date.
More Delivered than Requested 0DLVIOVER Calculation of items for which more was delivered than re
quested. In case the unlimited tolerance indicator is not
set for the sales order item, the configured overdelivery
tolerance is taken into account.
Less Delivered than Requested 0DLVIUNDR Calculation of items for which less was delivered than re
quested. In case the unlimited tolerance indicator is not
set for the sales order item, the configured underdelivery
tolerance is taken into account.
Value delivered early/ late acc. req. de 0DLVVELCR Calculation of value for items which were delivered early/
livery date late according to requested delivery date.
Value of early/late deliveries acc. 0DLVVELSC Calculation of value for items which were delivered early/
schedule line date late according to schedule line date.
Value delivered early acc. req. delivery 0DLVVEYCR Calculation of value for items which were delivered early
date according to requested delivery date.
Value of early deliveries acc. schedule 0DLVVEYSC Calculation of value for items which were delivered early
line date according to schedule line date.
Value of late deliveries acc. req. deliv 0DLVVLECR Calculation of value for items which were delivered late
ery date according to requested delivery date.
Value of late deliveries acc. schedule 0DLVVLESC Calculation of value for items which were delivered late
line date according to schedule line date.
Value Delivered more Than Requested 0DLVVOVER Calculation of value for items for which more was deliv
ered than requested. In case the unlimited tolerance indi
cator is not set for the sales order item, the configured
overdelivery tolerance is taken into account.
Less than Requested Delivery Value 0DLVVUNDR Calculation of value for items for which less was delivered
than requested. In case the unlimited tolerance indicator
is not set for the sales order item, the configured underde
livery tolerance is taken into account.
Confirmed as Requested 0ICOASREQ Calculation of items for which the requested quantity cor
responds to the confirmed quantity.
Value Confirmed as Requested 0VCOASREQ Calculation of value for items for which the requested
quantity corresponds to the confirmed quantity.
Delivery from Warehouse 0ISHP_STCK Calculation of items which are delivered from warehouse
Value with Delivery from Warehouse 0VSHP_STCK Calculation of value for items which are delivered from
warehouse
Value with Delivery Within 24 Hours 0VAL_24 Calculation of value for items which were delivered within
the correct quantity within 24 hours. In case the unlimited
tolerance indicator is not set for the sales order item, the
configured tolerances are taken into account.
Delivery Within 24 Hours 0DLV_24 Calculation of items which were delivered within the cor
rect quantity within 24 hours. In case the unlimited toler
ance indicator is not set for the sales order item, the con
figured tolerances are taken into account.
Net value of the order item in docu 0NET_VALUE Calculation of Net Value for the confirmed quantity.
ment currency
Completely Delivered Quantity 0QTYDLVCMPL Calculation of completely delivered quantity. In case the
unlimited tolerance indicator is not set for the sales order
item, the configured tolerances are taken into account.
Value of Completely Delivered Quanti 0VALDLVCMPL Calculation of value for completely delivered quantity. In
ties case the unlimited tolerance indicator is not set for the
sales order item, the configured tolerances are taken into
account.
BP: Business Partner Group (from Hi 0BP_GRP Filled via Lookup Routine for 0BP_GRP Master Data.
erarchy)
Product Category 0PROD_CATEG Filled via Lookup Routine for 0PROD_CATEG Master Data.
● Field Routines
Delivered Complete 0STS_DLV_C Check whether sales document has been delivered as re
quested.
Perfect Order Fulfillment (Num 0DLVIPOF Counter for perfect orders, i. e. orders without early or late
ber) deliveries, confirmed items correspond to number of
document items and without returns.
Perfect Order Fulfillment (Value) 0DLVVPOF Calculations of values for perfect orders, i. e. orders with
out early or late deliveries, without returns, with items
that were confirmed as requested.
● Field Routines
Value of Returns 0VAL_RET Calculation of returns value based on return quantity and
net price per sales unit.
BW Delta Process 0RECORDMODE Convert reverse image (“R”) into after image (“ ”).
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_VAITM
Delta Update
Delta Update
Data Modeling
Requires
Key figure Value delivered early/ late acc. req. deliv 0DLVVELCR
ery date
/IMO/D_SD53
The lowest goods issue status (0LW_GISTS) is C, or the schedule line (0SCHED_DEL) is marked as deleted.
Sources
Transformation
● Start Routine
The start routine for the updates ensures that only orders (0IMODOCCAT = “C”) and free-of-charge orders
(0IMODOCCAT = “I”) are updated in the DataStore object.
● Field Routines
Amount with Set GI Status 0GIS_QTY Calculation of quantity with posted goods issue.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_11_V_SSL
Data Modeling
Requires
/IMO/CMSD10
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Sales Document
Header Data (2LIS_11_VAHDR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD11
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Sales Document Item
Data (2LIS_11_VAITM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD14
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Order Condition Data
(2LIS_11_VAKON).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD16
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Sales-Shipping
Allocation Item Data (2LIS_11_V_ITM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD17
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Sales Document Order
Delivery (2LIS_11_V_SSL).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD18
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Sales Document
Header Status (2LIS_11_VASTH).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Header Data
(2LIS_12_VCHDR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD21
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Delivery Item Data
(2LIS_12_VCITM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Billing Document
Header Data (2LIS_13_VDHDR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD31
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Billing Document Item
Data (2LIS_13_VDITM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMSD34
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Billing Condition Data
(2LIS_13_VDKON).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
3.3 InfoSources
/IMO/SD_IS10
This InfoSource contains the structure for sales document header data.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS11
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
/IMO/SD_IS14
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS16
This InfoSource contains the shipping-sales allocation data. It is used to report on open order values and
quantities in SAP Business Warehouse for Sales and Shipping.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS17
This InfoSource provides information about the sales documents of an order schedule line. It is based on
DataSource 2LIS_11_V_SSL.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS18
This InfoSource provides information about the header status of a sales document. It is based on DataSource
2LIS_11_VASTH.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS20
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS21
This InfoSource contains information that relates to the delivery item, such as the delivery quantity in sales units,
or the delivery quantity in the base unit of measure.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS30
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS31
This InfoSource contains billing document item data, such as the billing quantity in delivery units, and the net value
of billing items.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS34
This InfoSource provides detailed condition information at billing item level. The condition value and condition
amount for each condition type are displayed for each order position.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/SD_IS111
This InfoSource provides information about returns and credit memos, with the number of returns at sales
document level for example. It is based on InfoSource Sales Document Item Data2LIS_11_VAITM.
Transformation
The characteristics Sales Document (0DOC_NUMBER) and Item (0S_ORD_ITEM) are filled with the reference objects
from InfoSource 2LIS_11_VAITM, which contain the original Sales Document and Item Number that the return/
credit memo document belongs to.
Start Routine
All records that are not returns (0DOC_CATEG = “H”) or credit memos (0DOC_CATEG = “O”) are deleted from the
source package.
Data Modeling
3.4 CompositeProvider
CompositeProvider: /IMO/V_SD10
This CompositeProvider contains transaction data from sales orders, deliveries, and billing documents/invoices.
For queries built on top of this CompositeProvider, the key figures need to be restricted to the correct document
classification (O = Order, D = Delivery, I = Invoice). Beside some sample queries, the CompositeProvider offers a
rich set of restricted and calculated key figures that you can use to implement your own customer queries.
For reporting on deleted header documents, you can use the KeyFigure No. of deleted Documents (0DLT_H_CNT).
For reporting on deleted items, you can use the respective item count KeyFigures (0*_I_CNT) in combination
with Characteristic Item Deleted(0ITEM_DEL).
Data Modeling
Requires
CompositeProvider: /IMO/V_SD20
This CompositeProvider contains transaction data from deliveries. For queries built on top of this
CompositeProvider, the key figures do not need to be restricted to document classification D (Delivery), since only
delivery data is connected to the CompositeProvider. Beside some sample queries, the CompositeProvider offers a
rich set of restricted and calculated key figures that you can use to implement your own customer queries.
For reporting on deleted header documents, you can use the KeyFigure No. of deleted Documents(0DLT_H_CNT).
For reporting on deleted items, you can use the respective item count KeyFigures(0*_1_CNT) in combination with
Characteristic Item deleted(0ITEM_DEL).
Data Modeling
Requires
CompositeProvider: /IMO/V_SD30
This CompositeProvider contains transaction data from billing documents/invoices. For queries built on top of this
CompositeProvider, the key figures do not need to be restricted to the document classification I (Invoice), since
only billing data is connected to the CompositeProvider. Beside some sample queries, the CompositeProvider
offers a rich set of restricted and calculated key figures that you can use to implement your own customer queries.
For reporting on deleted header documents, you can use the KeyFigure No. of deleted Documents(0DLT_H_CNT).
For reporting on deleted items, you can use the respective item count KeyFigures (0*_I_CNT) in combination
with Characteristic Item Deleted(0ITEM_DEL).
Data Modeling
Requires
CompositeProvider: /IMO/V_SD40
This CompositeProvider contains transaction data from order and billing document conditions. For queries built on
top of this CompositeProvider, the key figures need to be restricted to orders or billing documents. To achieve
better reporting performance, restrict the key figures in the query to a specific InfoProvider.
Data Modeling
CompositeProvider: /IMO/V_SD50
This CompositeProvider enables you to perform evaluations with respect to the service level. Different key figures
are available at sales order and item level. It contains data from DataStore object (advanced) SD-DLV: Service
Level Overview (/IMO/D_SD52) and facilitates the analysis of numbers, amounts and item quantities of early or
late deliveries.
Value of items delivered late / req. deliv /IMO/V_SD50_RK001 Key Figure: 0DLVVLECR
ery date
0DLV_STS = “C”
0DLV_STS = “C”
Item Delivered Late but Complete / Req. /IMO/V_SD50_RK004 Key Figure: /IMO/V_SD50_RK008
Delivery Date
0STS_DLV_C = “X”
Number of items delivered late / req. de /IMO/V_SD50_RK008 Key Figure: 0DLVILECR
livery date
0DLV_STS = “C”
0DLV_STS = “C”
0DLV_STS = “C”
0STS_DLV_C = “X”
0DLV_STS = “C”
0STS_DLV_C = “X”
/IMO/V_SD50_RK004)
%A
/IMO/V_SD50_RK003
/IMO/V_SD50_RK006)
%A
Average Processing Time for a Docu /IMO/V_SD50_CK003 Cumulated Processing Time of Delivered
ment Item Items
/IMO/V_SD50_RK002
/IMO/V_SD50_RK003
/IMO/V_SD50_RK005)
%A
/IMO/V_SD50_RK003
Requires
0SO_H_CNT
Technical Data
Aggregation Summation
Calculation No
0SO_I_CNT
Aggregation Summation
Calculation No
0DEL_H_CNT
Technical Data
Aggregation Summation
Calculation No
0DEL_I_CNT
Technical Data
Aggregation Summation
0BIL_H_CNT
Technical Data
Aggregation Summation
Calculation No
0BIL_I_CNT
Technical Data
Aggregation Summation
Calculation No
/IMO/V_SD10_Q0001
This query displays incoming order data per month. The query is based on the CompositeProvider Sales Overview
(/IMO/V_SD10).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DOC_CLASS = O
0DOC_CLASS = O
0DOC_CLASS = O
0DOC_CLASS = O
Formula Average value per Order Item — Incoming Orders Value / No.
of Order Items
/IMO/V_SD10_Q0002
This query displays open order data per month. The query is based on the CompositeProvider Sales Overview
(/IMO/V_SD10).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0DOC_CLASS = O
/IMO/V_SD10_Q0003
This query displays the values for sales revenue and sales orders for the last 12 months. The query is based on the
CompositeProvider Sales Overview (/IMO/V_SD10).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DOC_CLASS = O
0DOC_CLASS = O
0DOC_CLASS = I
0DOC_CLASS = I
/IMO/V_SD10_Q0004
This query compares order, delivery and billing quantities per month.The query is based on the CompositeProvider
Sales Overview (/IMO/V_SD10).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DOC_CLASS = O
0DEB_CRED = C
0DOC_CLASS = O
0DEB_CRED = D
0DOC_CLASS = D
0DOC_CLASS = D
0DEB_CRED = D
0DOC_CLASS = I
0DEB_CRED = C
0DOC_CLASS = I
/IMO/V_SD10_Q0005
This query displays the expected incoming orders per month, based on key figures like Open Quotation Net Value
and Sales Probability. The query is based on the CompositeProvider Sales Overview (/IMO/V_SD10).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Calculation
SAP Exit
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Open Quotation Net Value /IMO/ Subtract the Rejected Quota
V_SD10_CK_OQ_NETVAL
tion Net Value and the Ap
proved Quotation Net Value
from The total Quotation Net
Value.
Key Figure Expected Incoming Order (in /IMO/ Multiplication of Open Quota
%) V_SD10_CK_EXP_INORDER
tion Net Value with Sales
Probability and division by
100.
/IMO/V_SD20_Q0001
This query displays delivery data, such as the number of items delivered and the quantity delivered. The query is
based on the CompositeProvider Delivery (/IMO/V_SD20).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DEB_CRED = D
/IMO/V_SD30_Q0001
This query displays billing data per month. The query is based on the CompositeProvider Billing (/IMO/V_SD30).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DEB_CRED = D
0DEB_CRED = D
/IMO/V_SD30_Q0002
This query displays the ratio of credit memo data. The query is based on the CompositeProvider Billing (/IMO/
V_SD30).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure No. of Credit Memo Items /IMO/ Key figure: 0BIL_I_CNT
V_SD30_RK_CM_ITEMS
0DEB_CRED = C
0DEB_CRED = D
0DEB_CRED = C
0DEB_CRED = C
/IMO/V_SD40_Q0001
This query displays the condition value for each customer. The query is based on CompositeProvider Conditions
(/IMO/V_SD40).
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_SD50_Q0001
This query provides an overview based on delivery performance with respect to requested delivery dates and
confirmed schedule line dates. This query is based on CompositeProvider SD-DLV: Service Level (/IMO/V_SD50).
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Single value
Mandatory
Calcualtion
SAP Exit
Selection option
Optional
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_SD50_Q0002
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Single Value
Mandatory
Interval
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_SD50_Q0003
Use this query to analyze perfectly executed orders. Orders have been perfectly executed, if
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Calculation
SAP Exit
Calculation
SAP Exit
Selection option
Optional
Selection option
Optional
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
This documentation describes the SAP HANA-optimized Business Content objects for the following components
of SAP ERP Supply Chain Management:
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Material Management – Invoice Verification.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
The invoice verification data is extracted from the ERP system to the Business Warehouse and made available
there for further evaluation of the invoice verification process.
Possible analyzing scenarios are general comparisons of different invoice amounts and variances and of reasons
that have caused invoice items to be blocked for payment. You can analyze your invoice verification data at
aggregated or at detailed level, for example by displaying individual invoice document line items.
SAP delivers sample analytic queries on top of a CompositeProvider for the following areas:
4.1.1 Prerequisites
Before using the SAP HANA-optimized Business Content for MM Invoice Verification, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
● Activate Data Extraction in Logistics Customizing Cockpit (SAP ERP) [page 635]
● Perform Setup: Invoice Verification (SAP ERP) [page 636]
● Transfer Global Settings and Exchange Rates [page 637]
Context
By setting the update for the logistics extract structure to active, data is written to the extract structures both
online and during completion of setup tables.
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand in hierarchy structure node Logistics application 06: Invoice Verification Extract structures .
3. In column Update for extract structure MC06M_0ITM Extraction Structure BW, choose Inactive.
4. Select the required Update Mode.
Before performing an initial upload of MM Invoice Verification records into SAP BW/4HANA, you have to run a
reconstruction. The reconstruction writes the documents to be initially extracted in a setup table.
Procedure
1. In your SAP ERP system, call transaction OLI6BW (Invoice Verification – Execute Reconstruction).
2. Run the reconstruction after changing the parameters in Document Selection (optional) and Control Selection
(mandatory).
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them again by running transaction LBWG Delete the Contents of the Setup Tables for Application 06.
Recommendation
Always run this transaction before performing a new setup.
Note
Completing setup tables is a critical action that should be carried out with caution. It might be necessary to lock
the system for example. For large data amounts, the setup can take longer than one night and might have to be
done at the weekend.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) SAP Customer Implementation Guide
Integration with Other SAP Components Data Transfer to Business Warehouse Settings for Application-
Specific Data Sources (PI) Logistics Managing Extract Structures Initialization .
Context
Before loading data from MM purchasing records into SAP BW/4HANA, you have to transfer currency codes, units
of measure, fiscal year variants and exchange rates from your SAP source system to your SAP BW/4HANA system.
Currency translation type 0PSTNG_DAT also has to be installed from SAP HANA-optimized Business Content.
Procedure
Next Steps
/IMO/D_MMIV01
This DSO (advanced) contains replicated invoice verification data at a granular level.
Sources
The following master data must be loaded before loading the transactional data into this DSO, as this master data
is read during transformation:
0COMP_CODE
Exchange rates must be transferred from the source system before loading the transactional data.
Currency conversion type 0PSTNG_DAT is used in the transformation and must be installed from Business Content
before loading data.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Number of Invoice Items 0BBP_BILLITM Filled with constant “1” if invoice item.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_06_INV
Requires
/IMO/CMMMIV01
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Extraction of Invoice
Verification Data into BW (2LIS_06_INV).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
4.1.3 InfoSources
/IMO/MMIV_IS01
This InfoSource contains the structure to provide invoice verification data for the EDW Core Layer.
Transformation
Source System for R/3 Entity 0GN_R3_SSY Filled with the 2-digit logical back-end
system (based on LOGSY)
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
4.1.4 CompositeProvider
Definition
CompositeProvider: /IMO/V_MMIV01
Use
You can use the following characteristics to define specific key figures in analytic queries:
Data Modeling
Requires
4.1.5 Queries
/IMO/V_MMIV01_Q0001
This query provides an overview of invoice related values per vendor / invoice party, such as purchase order and
goods receipt value, freight costs, automatic invoice reduction, net invoiced amount, and gross invoice amount.
This query is based on the MM-IV: Invoice Verification (/IMO/V_MMIV01) CompositeProvider.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
0CISO_INV_PTY
Selection option:
Optional
0CISO_MATL_GROUP
Selection option:
Optional
0CISO_MATERIAL
Selection option:
Optional
0CISO_PURCH_ORG
Selection option:
Optional
0CISO_PUR_GROUP
Selection option:
Optional
0CISO_CO_AREA
Selection option:
Optional
0CISO_COSTCENTER
Selection option:
Optional
0CIIO_CALMONTH
Selection option:
Optional
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_MMIV01_Q0002
This query provides an overview of the reasons that have caused invoice items to be blocked for payment. The
number of affected invoices (if the block is set at header level) or affected items (if the block is set at item level) is
shown for each blocking reason. Multiple listings are possible.This query is based on the MM-IV: Invoice Verification
(/IMO/V_MMIV01) CompositeProvider.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
0CISO_INV_PTY
Selection option:
Optional
0CISO_MATL_GROUP
Selection option:
Optional
0CISO_MATERIAL
Selection option:
Optional
0CIIO_CALMONTH
Selection option:
Optional
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key figure:
Number of Invoices
(0BBP_BILLCT)
Restricted by Blocking
Reason: Manual (Header)
(0BLCKRSN_HM) with values
“A”, “B”, “Z”
Key figure:
Number of Invoices
(0BBP_BILLCT)
Restricted by Blocking
Reason: Statistical
(BLCKRSN_HS) with values
“S”
Restricted by Blocking
Reason: Quality
(BLCKRSN_QL) with values
“X”
Restricted by Blocking
Reason: Quantity
(BLCKRSN_QN) with values
“X”
Restricted by Blocking
Reason: POP Qty
(BLCKRSN_PQ) with values
“X”
Restricted by Blocking
Reason: Price (BLCKRSN_PR)
with values “X”
Restricted by Blocking
Reason: Manual (Item)
(BLCKRSN_MN) with values
“X”
Restricted by Blocking
Reason: Amount
(BLCKRSN_AM) with values
“X”
Key figure:
Restricted by Blocking
Reason: Date (BLCKRSN_DT)
with values “X”
Restricted by Blocking
Reason: Project
(BLCKRSN_PJ) with values
“X”
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Material Management – Procurement.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
The purchasing data is extracted from the ERP system to the Business Warehouse and made available there for
further evaluation of the procurement process.
It allows you to perform analysis of procurement data with regard to purchase orders, goods receipts, and
incoming invoices, at aggregated level as well as at detail level. You can use it to execute general strategic reports
like global spend analyses and to evaluate variations between invoice, goods receipt and purchase order values,
quantities and dates, or for in-depth analysis of your purchasing data at purchase order item and scheduling level.
You can also analyze contract usage and account assignments of your purchase orders, for cost center purchase
overviews for example.
Data Flow
Before using SAP HANA-optimized Business Content for MM Purchasing, you need to make the following
configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
To determine the correct process key during initialization and delta extraction, you need to define that logistical
business transactions are transferred to SAP BW/4HANA.
Procedure
1. In your SAP ERP system, call transaction MCB_ (Define Industry Sector / Derivation Maintenance for Transfer
into SAP BW).
2. Choose the appropriate SAP BW Usage for your industry sector:
○ For R/3 standard customers, choose Standard or Consumer products.
○ For customers with R/3 Retail only, choose Retail.
3. Save your entries.
For more information about the use of the process key in material management and dependency on extraction
process for SAP BW/4HANA, see SAP Note 353042 .
Context
If you set the update for the logistics extract structure to active, data is written to the extract structures, both
online and during completion of setup tables.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node Logistics application 02: Purchasing Extract structures .
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures that you want
to use:
○ MC02M_0ACC: Extraction Purchasing (Account) for DataSource 2LIS_02_ACC
○ MC02M_0CGR: Produced Activity: Delivery of Confirmations Maintenance for Data Source 2LIS_02_CGR
○ MC02M_0HDR: Extraction Purchasing (Header) for DataSource 2LIS_02_HDR
○ MC02M_0ITM: Extraction Purchasing (Item) for DataSource 2LIS_02_ITM
○ MC02M_0SCL: Extraction Purchasing (Schedule Line) for DataSource 2LIS_02_SCL
○ MC02M_0SCN: Produced Activity: Confirmation of Schedule Line Maintenance for Data
Source2LIS_02_SCN
○ MC02M_0SGR: Produced Activity: Delivery of Schedule Lines Maintenance for Data Source 2LIS_02_SGR
4. Select the required Update Mode.
Before performing an initial upload of MM Purchasing records into , you have to perform a reconstruction. The
reconstruction writes the documents to be initially extracted to a setup table.
Procedure
1. In your SAP ERP system, call transaction OLI3BW (Perform setup – Purchasing: Statistical setup of info
structures from purchasing documents).
2. After changing the parameters in Document data restriction (optional) and Control Selection (mandatory), run
the reconstruction .
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application 02.
Note
Completing setup tables is a critical action that should be carried out with caution. It might, for example, be
necessary to lock the system. For large volumes of data, the setup can take longer than one night and may have
to be done at the weekend.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) SAP Customer Implementation Guide
Integration with Other SAP Components Data Transfer to Business Warehouse Settings for Application-
Specific Data Sources (PI) Logistics Managing Extract Structures Initialization .
Context
Before you load data of MM purchasing records into SAP BW/4HANA, you have to transfer currency codes, units of
measure, fiscal year variants, and exchange rates from your SAP source system to your SAP BW/4HANA system.
Procedure
Next Steps
/IMO/D_PUR10
This DSO (advanced) contains purchasing document header data: purchase orders, contracts, schedule
agreements, and quotations (but no requests).
Sources
This DSO is filled by the InfoSource MM-PUR: Purchase Data Header (2LIS_02_HDR) (technical name: /IMO/
PUR_IS10).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_HDR
Some key figures are updated in an additive process. For more information, see the data source documentation.
Data Modeling
Requires
/IMO/D_PUR11
This DSO (advanced) contains purchasing document item data: purchase orders, contracts, schedule agreements,
and quotations (but no requests).
Sources
This DSO is filled by the InfoSource MM-PUR: Purchase Data Header (2LIS_02_ITM) (technical name: /IMO/
PUR_IS11).
Transformation
Start Routine
Only update records that are MM purchase documents (contracts excepted) based on BW: Transaction Key* and
Application Component.
For reversed documents (Record Mode (0RECORDMODE) = “R”), the indicator Item Deleted (0ITEM_DEL) is filled
with “X” and the record is updated into the DataStore object as an after image.
Field Routines
Flag for Contracts 0CT_FLAG Filled with “X” for items with assigned
principal agreement.
Update Date 0UPD_DATE Filled with system date during the data
load.
*For a list of process keys, see SAP Note 684465 BWVORG for purchasing data sources.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_ITM
All key figures used in the DataStore object are filled with aggregation behavior “Overwrite”. If you want to update a
further key figure from the InfoSource check, the key figure needs to be updated in overwrite or additive mode.
Data Modeling
Requires
/IMO/D_PUR12
This DSO (advanced) contains replicated purchasing document schedule line data including purchase history
(goods receipt and invoice receipt values and quantities).
Sources
This DSO is filled by the InfoSource MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) (technical
name: /IMO/PUR_IS12).
Transformation
Start Routine
Only update records that are MM purchase documents (contracts excepted) based on Application Component.
For reversed documents (Record Mode (0RECORDMODE) = “R”), the indicator Item Deleted (0ITEM_DEL) is filled
with “X” and the record is updated into the DataStore object as an after image.
Field Routines
Flag for Contracts 0CT_FLAG Filled with “X” for items with assigned
principal agreement.
Update Date 0UPD_DATE Filled with system date during the data
load.
Net Order Value in Local Currency 0SR_POVLC Filled with BW: Purchase Value in Local
Currency (0CPPVLC) if BW: Transaction
Key represents a purchase order or
schedule agreement record.
Net Order Value in Order Currency 0SR_POVOC Filled with BW: Purchase Value in Order
Currency (0CPPVOC) if BW: Transaction
Key represents a purchase order or
schedule agreement record.
Order Quantity in Base Unit 0SR_POQBU Filled with BW: Amount as OUn
(0CPQUAOU) if BW: Transaction Key rep
resents a purchase order or schedule
agreement record.
Net Goods Receipt Value in Local Cur 0SR_GRVLC Filled with BW: Purchase Value in Local
rency Currency (0CPPVLC) if BW: Transaction
Key represents a goods receipt record.
Net Goods Receipt Value in Order Cur 0SR_GRVOC Filled with BW: Purchase Value in Order
rency Currency (0CPPVOC) if BW: Transaction
Key represents a goods receipt record.
Goods Receipt Quantity in Base Unit 0SR_GRQBU Filled with BW: Amount as OUn
(0CPQUAOU) if BW: Transaction Key rep
resents a goods receipt record.
Net Invoiced Value in Local Currency 0SR_IVVLC Filled with BW: Purchase Value in Local
Currency (0CPPVLC) if BW: Transaction
Key represents an invoice receipt record.
Net Invoiced Value in Order Currency 0SR_IVVOC Filled with BW: Purchase Value in Order
Currency (0CPPVOC) if BW: Transaction
Key represents an invoice receipt record.
Invoiced Quantity in Base Unit 0SR_IVQBU Filled with BW: Amount as OUn
(0CPQUAOU) if BW: Transaction Key rep
resents an invoice receipt record.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_SCL
Some key figures in the data source need to be updated in an additive process. If you want to update a further key
figure from the InfoSource check, the key figure needs to be updated in overwrite or additive mode.
Data Modeling
Requires
/IMO/D_PUR13
This DSO (advanced) contains replicated accounting data on purchase document item level.
Sources
This DSO is filled by the InfoSource Data Account Level (2LIS_02_ACC) (technical name: /IMO/PUR_IS13).
Prerequisites
The following master data must be loaded before loading the transactional data into this DSO because the master
data is read during the transformation:
0COMP_CODE
Transformation
Start Routine
Only update records that are MM purchase orders, schedule agreements, or requests for quotations based on BW:
Transaction Key* and Application Component.
For reversed documents (Record Mode (0RECORDMODE) = “R”), the indicator Item Deleted (0ITEM_DEL) is filled
with “X” and the record is updated into the DataStore object as an after image.
Field Routines
Flag for Contracts 0CT_FLAG Filled with “X” for items with assigned
principal agreement.
Update Date 0UPD_DATE Filled with system date during the data
load.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_ACC
Data Modeling
Requires
/IMO/D_PUR14
This DSO (advanced) contains replicated principal agreement (contracts and scheduling agreements) data on
purchase document item level.
Sources
This DSO is filled by the InfoSource MM-PUR: Purchase Data Item Level (2LIS_02_ITM) (/IMO/PUR_IS11) to
provide general information on the principal agreement.
This DSO is filled by InfoSource MM-PUR: Purchase Data Schedule Line Level (2LIS_02_SCL) (/IMO/PUR_IS12) to
provide contract and scheduling agreement call-offs for the contract item.
Transformation
Update Date 0UPD_DATE Filled with system date during the data
load.
Target Value in Local Currency 0TARG_VLC Filled with Target Value in Document
Currency converted into local currency
by Exchange Rate (0EXCH_RATE).
Target Quantity in Base Unit of Meas 0TARG_QBU Filled with Target Quantity converted
ure into base unit by numerator and denom
inator provided by extracted data re
cord.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
All key figures are updated with aggregation behavior “Overwrite”.
Update Date 0UPD_DATE Filled with system date during the data
load.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
All key figures updated from 2LIS_02_SCL are filled with aggregation behavior “Summation”.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_ITM
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_SCL
Data Modeling
/IMO/D_PUR21
The DSO provides insight into the delivery service of vendors by exploring deviations across the entire delivery
process, between purchase orders, confirmations and goods receipts for example. It can therefore be used to
compare delivery KPIs, such as delivery scores (time, quantity and quality reliability) and quantity and delivery
date deviations.
Note
This DSO contains no information about returns items, service items, and limit items.
Sources
● DataStore object MM-PUR: Purchasing Document Item /IMO/D_PUR11 to provide all attributes of the
purchase order item (such as material, vendor, plant, document category, and status).
● InfoSource MM-PUR: Purchase Data Item (2LIS_02_ITM) /IMO/PUR_IS11 to provide further delivery KPIs
based on goods receipts, such as delivery scores, total delivery time in days, and date and quantity variances.
It also provides the delivery complete indicator.
● InfoSource MM-PUR: Alloc - Schedule Line with GR (2LIS_02_SGR) /IMO/PUR_IS20 to provide delivery KPIs
based on the allocation of schedule line quantities and dates with goods receipt quantities and dates.
● InfoSource MM-PUR: Alloc - Sched Line with Confirmation (2LIS_02_SCN) /IMO/PUR_IS21 to provide delivery
KPIs based on the allocation of schedule line quantities and dates with confirmation quantities and dates.
● InfoSource MM-PUR: Alloc - Confirmation with GR (2LIS_02_CGR) /IMO/PUR_IS22 to provide delivery KPIs
based on the allocation of confirmation quantities and dates with goods receipt quantities and dates.
Transformation
● Start Routine
Purchase order return items are not updated.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
● Start Routine
Only update records that are goods receipts for MM purchase documents based on BW: Transaction Key* and
Application Component.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
Delivery Date Variance 1 0DEL_DT_VR1 The Delivery Date Variance 1-5 key figures are
updated at the time of goods receipt as per the
Delivery Date Variance 2 0DEL_DT_VR2 entry date.
Delivery Date Variance 3 0DEL_DT_VR3 The delivery date variance is evaluated with the
help of a grid whose windows you can define in
Delivery Date Variance 4 0DEL_DT_VR4 Customizing for the Logistics Information
System (LIS). You can define a total of four win
Delivery Date Variance 5 0DEL_DT_VR5 dow limits, so that five windows in total are
available for evaluation purposes. The grid is
defined in accordance with the purchasing or
ganization.
Delivery quantity variance 1 0QTY_DEV_1 The Delivery Quantity Variances 1-5 key figures
are updated as per the date on which the goods
Delivery quantity variance 2 0QTY_DEV_2 receipt or PO change is recorded if a PO item is
closed. The delivery quantity variance is evalu
Delivery quantity variance 3 0QTY_DEV_3 ated with the help of a grid whose windows you
define in Customizing for the Logistics
Delivery quantity variance 4 0QTY_DEV_4
Information System (LIS). You can define a total
of four window limits, so that five windows are
Delivery quantity variance 5 0QTY_DEV_5
available in total for evaluation purposes. The
grid is defined in accordance with the purchas
ing organization.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
The following key figures are filled with aggregation behavior “Overwrite”:
○ Price Unit (0PRICE_UNIT)
○ Net Price (0NET_PRICE)
○ Numerator (0NUMERATOR)
○ Denominator (0DENOMINTR)
○ Total delivery time in days (0TOTDELTIME)
○ Points score for quantity reliability (0QTY_REL)
○ Points score for on-time delivery performance (0ONT_DEL)
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
Quantity Delivered Early Acc. Re 0PDQEYCRPU Filled with Goods Movement Quantity
quested Delivery Date (POUn) (0GMVQTY) if delivery was early by comparing
Requested Delivery Date (0DSDEL_DATE) with
Goods Receipt Date (0GR_DATE).
Quantity Delivered Late Acc. Re 0PDQLECRPU Filled with Goods Movement Quantity
quested Delivery Date (POUn) (0GMVQTY) if delivery was late by comparing
Requested Delivery Date (0DSDEL_DATE) with
Goods Receipt Date (0GR_DATE).
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
● Field Routines
Update Date 0UPD_DATE Filled with system date during the data load.
Quantity Delivered Early Acc. to 0PDQEYSCPU Filled with Goods Movement Quantity
Schedule Line Date (POUn) (0GMVQTY) if delivery was early by comparing
Confirmed Delivery Date (0CONF_DATE) with
Goods Receipt Date (0GR_DATE).
Quantity Delivered Late Acc. Re 0PDQLESCPU Filled with Goods Movement Quantity
quested Delivery Date (POUn) (0GMVQTY) if delivery was late by comparing
Confirmed Delivery Date (0CONF_DATE) with
Goods Receipt Date (0GR_DATE).
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_ITM, 2LIS_02_SGR, 2LIS_02_SCN, 2LIS_02_CGR
Data Modeling
Requires
/IMO/D_PUR22
This DSO (advanced) contains replicated goods receipt information for purchasing document schedule line data.
In comparison with DataStore object MM-PUR: Purchase Document Schedule Line (/IMO/D_PUR12), the purchase
order delivery DSO provides the goods receipt value and quantity based on the posted goods receipt date.
Sources
This DSO is filled by the InfoSource MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL) (/IMO/PUR_IS12).
Transformation
Start Routine
Only update records that are goods receipts for MM purchase documents based on BW: Transaction Key* and
Application Component.
For reversed documents (Record Mode (0RECORDMODE) = “R”), the indicator Item Deleted (0ITEM_DEL) is filled
with “X” and the record is updated into the DataStore object as an after image.
Field Routines
Flag for Contracts 0CT_FLAG Filled with “X” for items with assigned
principal agreement.
Update Date 0UPD_DATE Filled with system date during the data
load.
*For a list of BW transaction keys, see SAP Note 684465 BWVORG for purchasing data sources.
Delta Update
● Delta update: ABR: Complete Delta with deletion flag Via Delta Queue (Cube-Comp)
● DataSource: 2LIS_02_SCL
Some key figures in the data source need to be updated in an additive process. For more information, see the data
source documentation.
Data Modeling
Requires
/IMO/O_PUR11
This DataStore object (advanced) serves as the data acquisition DSO for BW Data Source MM-PUR: Purchase Data
Item (2LIS_02_ITM) and distributes the data into the following target DSOs in the EDW Core Layer:
Use
The data acquisition DSO takes the data from the source and distributes it in the SAP BW/4HANA system. It is part
of the Staging Layer and allows you to fill all targets independently of each other, and even at different times. It is
recommended to delete the data from the data acquisition DSOs after the data was loaded in all data targets.
This data acquisition DSO is mainly field-based and contains all available BW DataSource fields based on BW
DataSource MM-PUR: Purchase Data Item (2LIS_02_ITM).
/IMO/O_PUR12
This DataStore object (advanced) serves as the data acquisition DSO for BW Data Source MM-PUR: Purchase Data
Schedule Lines (2LIS_02_SCL) and distributes the data into the following target DSOs in the EDW Core Layer:
Use
The data acquisition DSO takes the data from the source and distributes it in the SAP BW/4HANA system. It is part
of the Staging Layer and allows you to fill all targets independently of each other, and even at different times. It is
recommended to delete the data from the data acquisition DSOs after the data was loaded in all data targets.
This data acquisition DSO is mainly field-based and contains all available BW DataSource fields based on BW
DataSource MM-PUR: Purchase Data Schedule Lines (2LIS_02_SCL).
/IMO/CMPUR10
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Purchasing Data
(Header Level) (2LIS_02_HDR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR11
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Purchasing Data (Item
Level) (2LIS_02_ITM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR12
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Purchasing Data
(Schedule Line Level) (2LIS_02_SCL).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR13
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Purchasing Data
(Account Level) (2LIS_02_ACC).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Produced Activity:
Delivery of Schedule Lines (2LIS_02_SGR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR20
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Produced Activity:
Delivery of Schedule Lines (2LIS_02_SGR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMPUR22
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Produced Activity:
Delivery of Confirmations (2LIS_02_CGR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
4.2.3 InfoSources
/IMO/PUR_IS10
This InfoSource contains the structure to provide purchase data on header level into the EDW Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit logical backend
system (based on LOGSY)
Logical System Backend 0LOG_SYS_BE Filled with the 2-digit logical original
backend system (based on ORGLOGSY).
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PUR_IS11
This InfoSource contains the structure to provide purchase data on item level into the EDW Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit logical backend
system (based on LOGSY)
Logical System Backend 0LOG_SYS_BE Filled with 2-digit logical original backend
system (based on ORGLOGSY).
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PUR_IS12
This InfoSource contains the structure to provide purchase data on schedule line level into the EDW Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit logical backend
system (based on LOGSY).
Logical System Backend 0LOG_SYS_BE Filled with 2-digit logical original backend
system (based on ORGLOGSY).
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Key figure BW: Sales Value with Taxes in Local Cur 0CPSTLC
rency
/IMO/PUR_IS13
This InfoSource contains the structure to provide purchase accounting data on item level into the EDW Core Layer.
Transformation
Fiscal Year Variant 0FISCVARNT Filled with fiscal year variant of company
code.
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit logical backend
system (based on LOGSY).
Logical System Backend 0LOG_SYS_BE Filled with 2-digit logical original backend
system (based on ORGLOGSY).
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
/IMO/PUR_IS20
This InfoSource contains the structure to consistently provide the schedule line quantities allocated with goods
receipt quantities into the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PUR_IS21
This InfoSource contains the structure to consistently provide the schedule line quantities allocated with
confirmation quantities into the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/PUR_IS21
This InfoSource contains the structure to consistently provide the schedule line quantities allocated with
confirmation quantities into the EDW Core Layer.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
4.2.4 CompositeProvider
Definition
CompositeProvider: /IMO/V_PUR01
This CompositeProvider contains purchase document information including purchasing history at header, item,
and schedule line level.
You can use the following characteristics to define specific key figures in analytic query:
F Purchase Order
K Contract
L Scheduling Agreement
When creating your own queries on this CompositeProvider, keep in mind that the following purchase document
item characteristics are not available for the header key figures Number of Purchase Documents 0NO_HDR,
Number of Deliveries 0DELIVERIES, and Number of Invoices 0INVOICES:
● Material Group
● Purchase Category
● Material
● Product Description
● Product
● Plant
● Location
● Storage Location
● Item Category in Purchasing Document
● Item Deleted
● Returns Item
● Purchasing Reason
● Delivery Completed (indicator)
● Final Invoice (indicator)
● Evaluated Receipt Settlement (ERS)
● GR-Based Invoice Verification
● Goods Receipt (indicator)
If you want to report on purchase order line items that are flagged for deletion, you can use the following key
figures:
Data Modeling
Requires
Definition
CompositeProvider: /IMO/V_PUR02
Use
This CompositeProvider contains information about purchasing contracts and scheduling agreements. It can be
used for tracking contract utilization by comparing released versus target values and quantities, and listing expiry
dates.
You can use the following characteristics to define specific key figures in analytic query:
K Contract
L Scheduling Agreement
Data Modeling
Requires
Definition
CompositeProvider: /IMO/V_PUR03
Use
This CompositeProvider contains an aggregated view of the account assignment elements, for example, cost
centers, the CO order, assets, networks/network activities, and the work breakdown structure elements. Additional
information about accumulated values and quantities can be determined using the G/L account.
You can use the following characteristics to define specific key figures in analytic queryqueries:
F Purchase Order
K Contract
L Scheduling Agreement
Data Modeling
Requires
Definition
CompositeProvider: /IMO/V_PUR04
This CompositeProvider contains indicators and key figures for purchase order item deliveries based on the
associated confirmation and goods receipt documents.
You can use this CompositeProvider to gain insight into the quality of the delivery service of vendors by exploring
deviations across the entire delivery process, between purchase orders, confirmations, and goods receipts for
example. The CompositeProvider provides delivery KPIs, such as delivery scores (time, quantity and quality) and
quantity and delivery date deviations.
You can use the following characteristics to define specific key figures in analytic query queries:
F Purchase Order
L Scheduling Agreement
Data Modeling
Requires
4.2.5 Queries
/IMO/V_PUR01_Q0001
This query displays the trend of procurement values per vendor. You can start further analyses, according to
material group, material, purchasing group, or purchasing organization, or according to time per contract, for
example. The query is intended for rough analysis of procurement behavior.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Optional
Interval
F = Purchase Order
and
L = Scheduling agreement
# Not assigned
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Net Order Value in Local Cur 0SR_POVLC Returns Item (0RET_ITM) = #
rency
Key Figure Net Return Value in Local Cur 0SR_POVLC Returns Item (0RET_ITM) = X
rency
/IMO/V_PUR01_Q0002
This query compares purchasing key figures per vendor such as ordered, delivered, invoiced value / quantity, and
number of purchase documents, deliveries, and invoices.
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Optional
Interval
# Not assigned
# Not assigned
Free Characteristics
Object Type Name Technical Name
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_PUR02_Q0001
This query lists current contracts with actual released values and quantities set against the target values and
quantities, sorted by expiry date.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
# Not assigned
Free Characteristics
Object Type Name Technical Name
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_PUR03_Q0001
This query affords managers an overview of the current and previous order volumes for their cost center(s). They
can display these values for certain requesters or product categories, and can drill down to the corresponding
purchase order item.
This query is based on the MM-PUR: Purchase Accounting (technical name /IMO/V_PUR03) CompositeProvider.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Mandatory
F = Purchase Order
and
L = Scheduling agreement
# Not assigned
# Not assigned
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Purchase Order Value (Se 0PUR_EFFHW Restricted by period SAP Exit
lected Period)
variable Current Fiscal Year/
Period (SAP Exit)
Key Figure Purchase Order Value – Quar 0PUR_EFFHW Restricted by period SAP Exit
ter
variable Current Quarter of
Fiscal Year (SAP Exit)
Key Figure Purchase Order Value – Previ 0PUR_EFFHW Restricted by period SAP Exit
ous Year
variable All Periods of Previous
Fiscal Year (SAP Exit)
/IMO/V_PUR04_Q0001
This query lists different delivery KPIs for each vendor; such as quality, on-time reliability, and quantity reliability
score. The query compares the share of too early or too late delivered quantity.
In the standard setting, the calculations restricted to purchase order items that meet the following conditions:
This query is based on the MM-PUR: Purchase Order Service Level (/IMO/V_PUR04) CompositeProvider.
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
# Not assigned
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
%A
0PDV_QPU
%A
0PDV_QPU
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Material Management component inventory management.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
The inventory management data is extracted from the ERP system to the Business Warehouse and made available
there for further evaluation of different stock values, quantities and movements.
SAP delivers sample analytic queries on top of a CompositeProvider for the following areas:
● Stock Overview
● Material Range of Coverage
● Obsolescence and Variance
Data Flow
More Information
Composite SAP Note 586163 contains information about the following topics:
● Release Strategy
● Information Sources
● Extraction of Stock Data From ERP
● Technical Information About Non-cumulative InfoCubes in SAP BW/4HANA
● Stock Analyses in SAP BW/4HANA
● Performance
The SAP Note also references helpful SAP online documentation such as “Non-Cumulatives” and “Modeling Non-
Cumulatives with Non-Cumulative Key Figures” and the following How To Papers:
Consulting SAP Note regarding Non-cumulative Data in SAP BW: Verifying and Correcting Data
SAP Note 745788 contains information about how to verify and correct data extracted from ERP Material
Management component inventory management.
The inventory scenarios delivered in Business Content are based on inventory key figures with associated
movement key figures. A snapshot scenario can be advantageous, if there is a very high density of movements.
Business Content does not contain such a scenario.
For more information, search for “How to…” document “How-to... Handle Inventory Management Scenarios in SAP
BW/4HANA” mentioned above.
The shipped stock reporting in SAP BW/4HANA does not offer the possibility to report on stock in transit that is
created via purchase order / sales orders. To overcome this functional gap a separate extractor can be
implemented to extract the intercompany stock in transit information.
For more information, search for “How to…” document “How-to... Report on Cross Company Stock in Transit”.
Depending on your specific requirements, the following SAP Notes might be useful to enhance the provided
business content to suit your specific needs:
● SAP Note 571669 - Incorrect stock val. in IC 0IC_C03 due to consumption values
● SAP Note 589024 - Reports in SAP BW/4HANA with storage location and stock type chars.
● SAP Note 637927 - 0IC_C03 InfoCube: Value key figures
● SAP Note 804781 - 0IC_C03: Consumption key figures from LIS INVCO (0IC_C01)
Before using SAP HANA-optimized Business Content for MM Inventory Management, you need to make the
following configuration settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Context
To determine the correct process key during initialization and delta extraction, you need to define that logistical
business transactions are transferred to SAP BW.
Procedure
1. In your SAP ERP system, call transaction MCB_ (Define Industry Sector / Derivation Maintenance
for Transfer into SAP BW).
2. Choose the appropriate SAP BW Usage for your industry sector:
○ For R/3 standard customers, choose Standard or Consumer products.
3. Save your entries.
For more information about the use of the process key in material management and dependency on extraction
process for SAP BW/4HANA, see SAP Note 353042 .
Context
If you set the update for the logistics extract structure to active, data is written to the extract structures, both
online and during completion of setup tables.
Procedure
1. In your SAP ERP system activate the DataSources 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM in transaction
RSA5.
2. Call transaction LBWE (Activate/Edit Extraction Structures).
3. Expand the hierarchy structure node Logistics application 03: Inventory Controlling Extract structures .
4. In the Update column for extract structure SAP BW, click on Inactive to activate the extract structures that you
want to use:
○ MC03BF0: Extraction MM-BW: Goods Movements 2LIS_03_BF
○ MC03UM0: Extraction MM-BW: Stock Revaluations 2LIS_03_UM
5. Select the required Update Mode.
Before performing an initial upload of MM Inventory Management records into SAP BW/4HANA, you have to
perform a reconstruction. The reconstruction writes the documents to be initially extracted to a setup table.
Recommendation
We recommend that you specify the plant as the restriction criterion and to run the program individually per
plant, in order to avoid a long runtime. Use the option Transfer Zero Stock only in exceptional cases, since
this otherwise drastically increases the runtime. (Refer to SAP Note 655798.)
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG. Delete the contents of the setup tables for Application 03.
Note
Completing setup tables is a critical action that should be carried out with caution. It might, for example, be
necessary to lock the system. For large volumes of data, the setup can take longer than one night and may have
to be done at the weekend.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) SAP Customer Implementation Guide
Integration with Other SAP Components Data Transfer to Business Warehouse Settings for Application-
Specific Data Sources (PI) Logistics Managing Extract Structures Initialization
Context
Before you load data of MM inventory management records into SAP BW/4HANA, you have to transfer currency
codes, units of measure, and fiscal year variants from your SAP source system to your SAP BW/4HANA system.
Procedure
Next Steps
/IMO/D_MMIM01
This DataStore object (advanced) allows you to evaluate various material stock quantities from SAP ERP.
● 0CALDAY is used as Reference Time Characteristic (see SAP Online Help for “Time Reference Characteristic”
for more information).
Note
To fill the DataStore Object /IMO/D_MMIM01 with non-cumulative data from ERP please follow the procedures
described here .
Quick summary:
● Stock initialization data extracted by DataSource 2LIS_03_BX must be loaded with DTP extraction mode
Initial Non-Cumulative for Non-Cumulative Values.
● Historical material movements collected in setup table for 2LIS_03_BF must be loaded with active DTP
setting Historical Transactions.
● All later delta requests for 2LIS_03_BF must be loaded without DTP setting Historical Transactions.
There are different non-cumulative key figures with corresponding flow key figures provided for your analysis:
● Total Stock Quantity 0TOTALSTCK based on Quantity Received into Total Stock 0RECTOTSTCK and Quantity
Issued from Total Stock 0ISSTOTSTCK
● Quantity of Valuated Stock 0VALSTCKQTY based on Quantity Received into Valuated Stock 0RECVALSTCK and
Quantity Issued from Valuated Stock 0ISSVALSTCK
● Consignment Stock 0CNSSTCKQTY based on Quantity Received from Consignment Stock 0RECCNSSTCK and
Quantity Issued from Consignment Stock 0ISSCNSSTCK
The key figures can be further restricted in the query definitions to Stock Categories (0STOCKCAT), such as Project
Stock or Sales Order Stock, and to Stock Types (0STOCKTYPE), such as Quality Inspection Stock or Blocked Stock.
In this way, for example, you can evaluate the quantity of valuated project stock based on key figure Quantity of
Valuated Stock (0VALSTCKQTY) and Stock Category “Q”.
Various restricted and calculated key figures are provided by SAP HANA-optimized Business Content for inventory
management reporting. You can find a full list of the restricted and calculated key figures that are delivered by
default in the online documentation of the CompositeProvider Material Stocks & Movements - /IMO/V_MMIM01
[page 780].
This CompositeProvider supports combined reporting for inventory management based on stock quantities, stock
values and consumption quantities / values.
To define various stock key figures, the DataSource fills some additional fields such as Stock Category and Stock
Type that are filled on the extractor side in the LMCB1F20 include (routine STA_VERAENDERUNG). The InfoObject
0INDSPECSTK (field KZBWS) is used to control whether the sales order stock / project stock is valuated or non-
valuated.
The system valuates the transaction key to decide whether the issue movement key figure or receipt movement
key figure is updated. For more information, see SAP Note 492828 : Determining the transaction key for
2LIS_03_BF + 2LIS_03_UM.
The general key figures (for example, Total Stock or Issue Quantity Total Stock), can be restricted in the analytic
query Designer by Stock Category and Stock Type to define more specific stock key figures such as Quantity of
Valuated Project Stock - Blocked.
Keep in mind that only the flow key figures (e.g. Receipt Quantity Total Stock 0RECTOTSTCK and Issue Quantity
Total Stock 0ISSTOTSTCK) are updated in the transformations and not the non-cumulative key figures (e.g.
Quantity Total Stock 0TOTALSTCK) as these key figures are calculated by OLAP during query execution.
Update Logic
When updating the DataSources 2LIS_03_BX and 2LIS_03_BF, the system applies the following logic:
Sources
● InfoSource Stock Initialization (2LIS_03_BX) to provide the stock initialization quantities from SAP ERP
● InfoSource Material Movements (2LIS_03_BF) to provide the material movements mainly sourced from SAP
ERP table MSEG
Transformation
Receipt Quantity Total Stock 0RECTOTSTCK Filled with initial stock quantity in
base unit of measure.
Quantity Received into Valuated 0RECVALSTCK Filled with initial quantity of valuated
Stock stock in base unit of measure based
on stock category and valuation spe
cial stock indicator.
Quantity Received into Consignment 0RECCNSSTCK Filled with initial stock quantity of
Stock consignment stocks in base unit of
measure.
Receipt Quantity Total Stock 0RECTOTSTCK Filled with received stock quantity in
base unit of measure.
Issue Quantity Total Stock 0ISSTOTSTCK Filled with issued stock quantity in
base unit of measure..
Quantity Received into Valuated 0RECVALSTCK Filled with received quantity of valu
Stock ated stock in base unit of measure
based on stock category and valua
tion special stock indicator.
Quantity Issued into Valuated Stock 0ISSVALSTCK Filled with issued quantity of valuated
stock in base unit of measure based
on stock category and valuation spe
cial stock indicator
Quantity Received into Consignment 0RECCNSSTCK Filled with received stock quantity of
Stock consignment stocks in base unit of
measure.
Quantity Issued into Consignment 0ISSCNSSTCK Filled with issues stock quantity of
Stock consignment stocks in base unit of
measure.
Data Modeling
Requires
/IMO/D_MMIM02
● 0CALDAY is used as Reference Time Characteristic (see SAP Online Help for “Time Reference Characteristic”
for more information).
● 0PLANT is set by default as Validity Characteristics (see SAP Note 1501907 for more information).
Note
To fill the DataStore Object /IMO/D_MMIM02 with non-cumulative data from ERP please follow the procedures
described here Prerequisites [page 750].
Quick summary:
● Stock initialization data extracted by data source 2LIS_03_BX must be loaded with DTP extraction mode
Initial Non-Cumulative for Non-Cumulative Values.
● Historical material movements and revaluations collected in setup table for 2LIS_03_BF / 2LIS_03_UM
must be loaded with active DTP setting Historical Transactions.
● All later delta requests for 2LIS_03_BF / 2LIS_03_UM must be loaded without DTP setting Historical
Transactions.
The following non-cumulative key figure with corresponding flow key figures is provided for your analysis:
● Value of Valuated Stock 0VALSTCKVAL based on Value Received from Valuated Stock 0RECVS_VAL and Value
Issued from Valuated Stock 0ISSVS_VAL
The key figures can be further restricted in the query definitions to Stock Categories (0STOCKCAT) and to Stock
Types (0STOCKTYPE), such as Quality Inspection Stock or Blocked Stock.
Various restricted and calculated key figures are provided by SAP HANA-optimized Business Content for inventory
management reporting. You can find a full list of the restricted and calculated key figures that are delivered by
default in the online documentation of the CompositeProvider Material Stocks & Movements - /IMO/V_MMIM01
[page 780].
This CompositeProvider supports combined reporting for inventory management based on stock quantities, stock
values and consumption quantities / values.
To define various stock key figures the data source fills some additional fields such as Stock Category and Stock
Type that are filled on the extractor side in the LMCB1F20 include (routine STA_VERAENDERUNG). The InfoObject
0INDSPECSTK (field KZBWS) is used to control whether the sales order stock / project stock is valuated or non-
valuated.
The system valuates the transaction key to decide whether the issue movement key figure or receipt movement
key figure is updated. For more information, see SAP Note 492828 : Determining the transaction key for
2LIS_03_BF + 2LIS_03_UM.
The general key figures (for example, Value of Valuated Stock), can be restricted in the analytic query Designer by
Stock Category to define more specific stock key figures such as Value of Valuated Project Stock.
However it is also possible to pre-calculate and persist additional key figures already in the transformation based
on Stock Category and Stock Type; that will deliver the same result (key word: key figure model vs account model,
advantages and disadvantages as discussed in SAP Note 586163 ).
Update Logic
When updating the DataSources 2LIS_03_BX, 2LIS_03_BF, and 2LIS_03_UM, the system applies the following
logic:
Sources
● InfoSource Stock Initialization (2LIS_03_BX) to provide the stock initialization quantities and values from SAP
ERP
● InfoSource Material Movements (2LIS_03_BF) to provide the material movements mainly sourced from SAP
ERP table MSEG
● InfoSource Revaluations (2LIS_03_UM) mainly based on SAP ERP table BSEG.
Transformation
Update Date 0UPD_DATE Filled with system date during the data
load.
Value Received into Valuated Stock 0RECVS_VAL Filled with initial value of valuated stock
in local currency based on stock cate
gory and valuation special stock indica
tor.
Update Date 0UPD_DATE Filled with system date during the data
load.
Value Received into Valuated Stock 0RECVS_VAL Filled with initial value of valuated stock
in local currency based on stock cate
gory and valuation special stock indica
tor.
Value Issued from Valuated Stock 0ISSVS_VAL Filled with issued value of valuated
stock in local currency based on stock
category and valuation special stock in
dicator.
Update Date 0UPD_DATE Filled with system date during the data
load.
Value Received into Valuated Stock 0RECVS_VAL Filled in case of increase of revaluated
stock value in local currency based on
stock category
Value Issued from Valuated Stock 0ISSVS_VAL Filled in case of decrease of revaluated
stock value in local currency based on
stock category.
Data Modeling
Requires
/IMO/D_MMIM10
This DataStore object (advanced) allows you to report on Material Movements on document level.
Note
Contrary to the non-cumulative DataStore objects (advanced) MM-IM: Material Stock - Quantities /IMO/
D_MMIM01 and MM-IM: Material Stock - Values /IMO/D_MMIM02, all requests for 2LIS_03_BF must be loaded
without DTP setting Historical Transactions.
Update Logic
When updating the DataSource 2LIS_03_BF, the system applies the following logic:
Sources
This DSO is filled by the InfoSource Material Movements (2LIS_03_BF) to provide the material movements mainly
sourced from SAP ERP table MSEG.
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Data Modeling
Key figure BW: Sales Value with Taxes in Local Cur 0CPSTLC
rency
/IMO/CMMMIM01
This DataStore object (advanced) serves as the corporate memory for all deltas - excluding the historical postings
- that are extracted by DataSource Goods Movement from Inventory Management (2LIS_03_BF).
The historical postings collected during the statistical setup by transaction OLI1BW in SAP ERP should be loaded
into the separate corporate memory /IMO/CMMMIMH1. The reason for the additional corporate memory for
historical postings is the following: the reconstruction of the historical postings into a non-cumulative DataStore
object (advanced) requires to be run by a Data Transfer Process with active indicator Historical Transactions.
Use
The corporate memory is filled independently of the EDW core layer's update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate Memory Without Compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound Table as Extended Table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMMMIM02
This DataStore object (advanced) serves as the corporate memory for all deltas - excluding the historical postings
- that are extracted by DataSource Revaluations (2LIS_03_UM).
The historical postings collected during the statistical setup by transaction OLIZBW in SAP ERP should be loaded
into the separate corporate memory /IMO/CMMMIMH2. The reason for the additional corporate memory for
historical postings is the following: the reconstruction of the historical postings into a non-cumulative DataStore
object (advanced) requires to be run by a Data Transfer Process with active indicator Historical Transactions.
Use
The corporate memory is filled independently of the EDW core layer's update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate Memory Without Compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMMMIMH1
This DataStore object (advanced) serves as the corporate memory only for the historical data (statistical setup
data for material movements collected by transaction OLI1BW in SAP ERP) that is extracted by DataSource Goods
Movement from Inventory Management (2LIS_03_BF).
Use
The corporate memory is filled independently of the EDW core layer's update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate Memory Without Compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound Table as Extended Table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Note
When a reconstruction is necessary, please make sure to load data from this corporate memory into the non-
cumulative DataStore objects (advanced) mentioned below only with the active indicator Historical
Transactions in the Data Transfer Process:
/IMO/CMMMIMH2
Use
The corporate memory is filled independently of the EDW core layer's update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate Memory Without Compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound Table as Extended Table has been turned on. This means the persistence of data
for this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Note
When a reconstruction is necessary, please make sure to load data from this corporate memory into the non-
cumulative DataStore object (advanced) mentioned below only with the active indicator Historical Transactions
in the Data Transfer Process:
4.3.3 InfoSources
/IMO/MMIM_IS01
This InfoSource delivers the data for material movements from MM Inventory Management (MM-IM) DataSource
2LIS_03_BF.
The DataSource 2LIS_03_BF is set up with the report New Setup for Info Structures from Material Movements
(RMCBNEUA) or transaction code OLI1BW.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Key figure BW: Sales Value with Taxes in Local Cur 0CPSTLC
rency
/IMO/MMIM_IS02
This InfoSource delivers the data for revaluations from MM Inventory Management (MM-IM) DataSource
2LIS_03_UM.
The DataSource 2LIS_03_UM is set up with the report Statistical Setup of Info Strucs from Invoice Verification/
Revaluation (RMCBNERP) or transaction code OLIZBW.
Transformation
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Key figure BW: Sales Value with Taxes in Local Cur 0CPSTLC
rency
/IMO/MMIM_IS00
With this InfoSource, you can transfer material stocks from an SAP ERP system to SAP BW/4HANA. The
InfoSource allows you to set up stocks for the inventory DataStore objects (advanced). To do this, use extraction
mode Initial Non-Cumulative for Non-Cumulative Values in the Data Transfer Process (do not use the extraction
mode Full or Delta).
Note
If you want to implement instead a snap shot scenario for your inventory stock, use the Full Update mode to
transfer the current material stocks to a custom DataStore object (advanced) that contains only cumulative
values. Here, you transfer the complete current material stock for a calendar day (snap shots). In this case, note
the aggregation behavior with regard to the selected time characteristic.
The DataSource 2LIS_03_BX is set up with the report BW: Initialization of Opening Stocks in Transfer Structure
(RMCBINIT_BW) or transaction MCNB.
Source System for R/3 Entry* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Key figure BW: Sales Value with Taxes in Local Cur 0CPSTLC
rency
4.3.4 CompositeProvider
CompositeProvider: /IMO/V_MMIM01
This CompositeProvider enables you to evaluate stock quantities, stock values and material movements from SAP
ERP Central Component (SAP ECC).
Beside some sample queries, the CompositeProvider offers a rich set of restricted and calculated key figures that
you can use to implement your own customer queries.
● The following characteristics are NOT available in source InfoProvider MM-IM: Material Stock - Values /IMO/
D_MMIM02 and can therefore not be used for value-based stock reporting:
○ Stock Type 0STOCKTYPE
○ Storage Location 0STOR_LOC
○ Batch number 0BATCH
● The following characteristics are only available in source InfoProvider MM-IM: Material Movements
(Documents) /IMO/D_MMIM10 and should only be used to restrict movement / consumption key figures:
○ Movement Type (Inventory Management) 0MOVETYPE
○ Application Component 0BWAPPLNM
○ BW: Transaction Key 0PROCESSKEY
○ BW: Relevance to Stock 0STOCKRELEV
● The following stock quantity key figures are provided in the CompositeProvider by source InfoProvider MM-IM:
Material Stock - Quantities /IMO/D_MMIM01:
○ Quantity Total Stock 0TOTALSTCK
○ Receipt Quantity Stock 0RECTOTSTCK
○ Issue Quantity Stock 0ISSTOTSTCK
○ Quantity of Valuated Stock 0VALSTCKQTY
○ Quantity Received into Valuated Stock 0RECVALSTCK
○ Quantity Issued from Valuated Stock 0ISSVALSTCK
○ Quantity of consignment stock 0CNSSTCKQTY
○ Quantity Received into Valuated Stock 0RECCNSSTCK
○ Quantity Issued from Valuated Stock 0ISSCNSSTCK
● The following stock value key figures are provided in the CompositeProvider by source InfoProvider MM-IM:
Material Stock - Values /IMO/D_MMIM02:
○ Value of Valuated Stock 0VALSTCKVAL
○ Value Received into Valuated Stock 0RECVS_VAL
○ Value Issued from Valuated Stock 0ISSVS_VAL
● The following movement / consumption key figures are provided in the CompositeProvider by source
InfoProvider MM-IM: Material Movements (Documents) /IMO/D_MMIM10:
○ Value in Local Currency (Movements) 0CPPVLC
○ Quantity in base unit of measure (Movements) 0CPQUABU
○ Number of Activities (Movements) 0CPNOITEMS
● The following characteristics might be helpful when defining specific key figures such as restricted key figures
or selections in analytic queries:
○ InfoObject Stock Category 0STOCKCAT for stock quantity, stock values and material movement key figures
with possible values as shown below:
Value Description
# Valuated Stock
K Vendor Consignment
Q Project Stock
V Consumptions
U Non-Valuated Stock
T Stock in Transit
○ InfoObject Stock Type 0STOCKTYPE for stock quantity and material movement key figures with possible
values as shown below:
Value Description
# Not defined
A Unrestricted Use
B Quality Inspection
D Blocked Stock
E Restricted-Use
F Stock Transfer
H Transit
T Tied Empties
V Consumption
○ InfoObjects Application Component 0BWAPPLNM, BW: Transaction Key 0PROCESSKEY, Movement Type
(Inventory Management) 0MOVETYPE, BW: Relevance to Stock 0STOCKRELEV for material movement key
figures based on PartProvider MM-IM: Material Movements (Documents) /IMO/D_MMIM10.
Received Quantity: Blocked Stock /IMO/V_MMIM01_BLOCKEDSTOCK_REC Key figure: 0RECTOTSTCK with relevant
restriction for blocked stock
Issued Quantity: Blocked Stock /IMO/V_MMIM01_BLOCKEDSTOCK_ISS Key figure: 0ISSTOTSTCK with relevant
restriction for blocked stock
Stock in Quality Inspection /IMO/V_MMIM01_QMSTOCK Key figure: 0TOTALSTCK with relevant re
striction for stock in quality inspection
(0STOCKCAT “#”, “E”, “M”, “Q”, “U” and
0STOCKTYPE “B”, “L”, “O”, “R”)
Received Quantity: Stock in Quality In /IMO/V_MMIM01_QMSTOCK_REC Key figure: 0RECTOTSTCK with relevant
spection restriction for stock in quality inspection
Issued Quantity: Stock in Quality Inspec /IMO/V_MMIM01_QMSTOCK_ISS Key figure: 0ISSTOTSTCK with relevant
tion restriction for stock in quality inspection
Received Quantity: Stock in Transit /IMO/V_MMIM01_TRANSSTOCK_REC Key figure: 0RECTOTSTCK with relevant
restriction for stock in transit
Issued Quantity: Stock in Transit /IMO/V_MMIM01_TRANSSTOCK_ISS Key figure: 0ISSTOTSTCK with relevant
restriction for stock in transit
Vendor Consignment Stock Quantity Re /IMO/V_MMIM01_RK0031 Key figure: 0RECCNSSTCK with
ceipt 0STOCKCAT “K Vendor Consignment”
Vendor Consignment Stock Quantity Is /IMO/V_MMIM01_RK0032 Key figure: 0ISSCNSSTCK with
sued 0STOCKCAT “K Vendor Consignment”
Quantity of Valuated Project Stock (To /IMO/V_MMIM01_RK0053 Key figure: 0VALSTCKQTY with
tal) 0STOCKCAT “Q Project Stock”
Quantity of Valuated Project Stock, Unre /IMO/V_MMIM01_RK0055 Key figure: 0VALSTCKQTY with
stricted 0STOCKCAT “Q Project Stock” and
0STOCKTYPE “A Unrestricted Use”
Quantity of Valuated Sales Order Stock /IMO/V_MMIM01_RK0063 Key figure: 0VALSTCKQTY with
(Total) 0STOCKCAT “E Sales Order Stock”
Quantity of Valuated Sales Order Stock /IMO/V_MMIM01_RK0064 Key figure: 0VALSTCKQTY with
in Q 0STOCKCAT “E Sales Order Stock” and
0STOCKTYPE “B Quality Inspection”
Quantity of Valuated Sales Order Stock, /IMO/V_MMIM01_RK0065 Key figure: 0VALSTCKQTY with
Unrestricted 0STOCKCAT “E Sales Order Stock” and
0STOCKTYPE “A Unrestricted Use”
Quantity of Valuated Sales Order Stock /IMO/V_MMIM01_RK0067 Key figure: 0VALSTCKQTY with
Blocked 0STOCKCAT “E Sales Order Stock” and
0STOCKTYPE “D Blocked Stock”
Quantity of Valuated Sales Order Stock /IMO/V_MMIM01_RK0068 Key figure: 0VALSTCKQTY with
in Transit 0STOCKCAT “E Sales Order Stock” and
0STOCKTYPE “F Stock Transfer”, “H
Transit”
Scrap Proportion of Total Stock Value /IMO/V_MMIM01_CK0001 Scrap Value %A (Value of Valuated Stock
+ Scrap Value)
Scrap Proportion of Total Stock Quantity /IMO/V_MMIM01_CK0002 Scrap Quantity %A (Quantity Total Stock
+ Scrap Quantity)
Data Modeling
Requires
4.3.5 Queries
/IMO/V_MMIM01_Q0001
You can use this query to display stock key figures for total stock, valuated stock, special stock and consignment
stock.
This query is based on the Material Stocks & Movements (/IMO/V_MMIM01) CompositeProvider.
Structure
Free Characteristics
Object Type Name Technical Name
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_MMIM01_Q0002
This query is based on the Material Stocks & Movements (/IMO/V_MMIM01) CompositeProvider.
You can use this query to show the number of days during which the current stock will cover future stock issues on
the basis of the stock and issue values.
Assumption:
When calculating the material range of coverage, it is assumed that the average future stock issues will be the
same as those in the past (constant model).
By changing the calculated key figure /IMO/V_MMIM01_CK0003, other time intervals can be used to calculate the
average stock issues. The time interval must also be adjusted to the calendar day. Note that movement data is
loaded for the complete interval to ensure that you get useful results when calculating the average stock issue.
If you do not select any materials in the variable query, the query runtime is longer.
If the key figure cannot be calculated in the query (for example, if the stock issue value in the relevant period = 0),
the system enters No calc possible in the relevant cell. For more information, see SAP Note 591063 .
If you create queries that have the characteristics Storage Location (0STOR_LOC) and Stock Type (0STOCKTYPE) in
the drilldown, see SAP Note 589024 .
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_MMIM01_Q0003
You can use this query to display information about whether your warehouse contains obsolete stock. This allows
you to, for example, view the percentage and value of obsolete stock per plant and material.
This query is based on the Material Stocks & Movements (/IMO/V_MMIM01) CompositeProvider.
Structure
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP or SAP S/4HANA Production Planning and Controlling.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modeling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
This content provides you with an entry layer to extract and transform production planning and controlling data
into SAP BW/4HANA in the area of production order analysis including material view, work center view,
components and capacity requirements and usage.
PP DataFlow
The areas of PP (Production Planning) and PP-PI (Production Planning - Process Industries) both use the same
Content objects. Therefore take the following into consideration:
● When manufacturing orders are analyzed, data is extracted from production orders (PP) and process orders
(PP-PI) and cumulated independently of the order category.
● Operation data from process orders is not analyzed
However, order category (0COORD_TYPE) is available as a navigation attribute for the manufacturing order
(0PRODORDER). You can use this as an additional selection criterion in your queries (for example, as a filter value
or selection variable), as required. The production order has the order category 10 and the manufacturing order
has the order category 40.
0ACT_FIN_OK
0ACT_FIN_OP
0WRKCT_CATG
In these cases, the Standard System uses the descriptions from PP. If you only use PP-PI, replace the info object
description with the corresponding PP-PI term.
4.4.1 Prerequisites
Before using the SAP HANA-optimized BI Content for Production Planning and Controlling, you need to configure
the following settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Settings for PP
● Activate Data Extraction in Logistics Customizing Cockpit (SAP ERP) [page 797]
● Transfer Global Settings and Exchange Rates [page 797]
● Perform Setup: PP (SAP ERP) [page 798]
Context
If you set the update for the logistics extract structure to active, data is written to the extract structures, both
online and during completion of setup tables.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node → Logistics applications → 04: Shop Floor Control → Extract structures.
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures you want to
use:
○ MC04P_0ARB: Extraction PP-BW: Work Center View from PP/PP-PI for DataSource 2LIS_04_P_ARBPL
○ MC04P_0COM: Extraction PP-BW: Component View from PP/PP-PI for DataSource 2LIS_04_P_COMP
○ MC04P_0MAT: Extraction PP-BW: Material View from PP/PP-PI for DataSource 2LIS_04_P_MATNR
4. Select the required Update Mode.
Context
Before loading data from Production Planning and Controlling into SAP BW/4HANA, you have to transfer currency
codes, units of measure, fiscal year variants, factory calendar, and exchange rates from your SAP source system to
your SAP BW/4HANA system.
Procedure
Before performing an initial upload of Production Planning and Controlling records into SAP BW/4HANA, you have
to run a reconstruction. The reconstruction writes the documents to be initially extracted to a setup table.
Procedure
1. In your SAP ERP system, call transaction OLI4BW (Perform setup – PP BW: Shop Floor Information System).
2. After changing the parameters in Restriction for Production Orders (optional) and Control of the Setup run
(mandatory), run the reconstruction.
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application Shop Floor
Control “04”.
Recommendation
Before performing a new setup, run this transaction.
Note
Completing setup tables is a critical action that should be carried out with caution. It might be necessary to lock
the system. For large volumes of data, the setup can take longer than one night and might have to be done at
the weekend.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) SAP Customer Implementation Guide
Integration with Other SAP Components Data Transfer to Business Warehouse Settings for Application-
Specific Data Sources (PI) Logistics Managing Extract Structures Initialization .
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Material View from
PP/PP-PI (2LIS_04_P_MATNR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Work Center View
from PP/PP-PI (2LIS_04_P_ARBPL_20).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Component View from
PP/PP-PI (2LIS_04_P_COMP).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource PP(PI)Work Center
Capacity (0PP_WCCP_20).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
4.4.3 InfoSources
This InfoSource contains the structure to provide production order header data consistently into the EDW Core
Layer. This provides the transaction data from the production process, with reference to the order header and
item, and returns information about the production order header.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide transaction data from the manufacturing process, with regards
to order operations, as well as work center/operation information consistently into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide material consumptions for the production process, and
information about the material components, consistently into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide standard available capacities for each individual work center
consistently into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from Extended Warehouse Management (EWM).
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for EWM, you need to make the following configuration
settings:
General Settings
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
The warehouse management data is extracted from the EWM or ERP system to the Business Warehouse and
made available there for further evaluation of the warehouse management processes.
EWM allows you to analyze and compare warehouse data. A series of key figures are available, which you can use
as a basis for defining and evaluating your own key figures.
The data basis is provided by the delivered content. It contains the following data flows:
● Inbound Deliveries
● Outbound Deliveries
● Ratio of Outbound Items Delivered on Time
● Ratio of Outbound Delivery Errors
● Warehouse Capacity Level - Occupied Bins
EWM DataFlow
/IMO/D_EWM01
This DataStore Object (advanced) is used for data related to inbound delivery items.
Sources
This DSO is filled by the InfoSource EWM: Inbound Delivery Items (0WM_DLVI_IN) (/IMO/EWM_IS01).
Transformation
Field Rules
Delta Update
Data Modeling
Requires
/IMO/D_EWM02
This DataStore Object (advanced) is used to store data for outbound delivery items.
Sources
This DSO is filled by the InfoSource EWM: Outbound Delivery Items (0WM_DLVI_OUT) (/IMO/EWM_IS02).
Transformation
Field Rules
Delta Update
Data Modeling
Requires
/IMO/D_EWM03
This DataStore Object (advanced) is used for data related to proof of delivery.
Sources
This DSO is filled by the InfoSource EWM: Proof Of Delivery (0WM_POD) (/IMO/EWM_IS03).
Transformation
Field Rules
Delta Update
Data Modeling
Requires
/IMO/D_EWM04
This DataStore object contains value-added service orders extracted from EWM. This DataStore object comprises
multiple rows due to the data model it is based on. A value-added service order can contain 1 to n activities. An
activity can have 1 to n items and 0 to n auxiliary products. The following information is extracted, for example:
Sources
This DSO is filled by the InfoSource EWM: Value-Added Services (0WM_VAS) (/IMO/EWM_IS04).
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: AIMD: After-Images with Deletion Flag Via Delta Queue
● DataSource: 0WM_VAS
Data Modeling
/IMO/D_EWM10
Sources
This DSO is filled by the InfoSource EWM: Warehouse Orders (0WM_WO) (/IMO/EWM_IS10).
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_EWM11
Sources
This DSO is filled by the InfoSource EWM: Warehouse Tasks (0WM_WT_WO) (/IMO/EWM_IS11).
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_EWM12
This DataStore object contains exceptions extracted from the EWM system. The following information is extracted:
● Warehouse number
● Exception code
● Time stamp of the exception
● Processor
● Business context
● Process step
Sources
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
EWM: Exceptions
/IMO/D_EWM20
This DataStore Object (DSO) collects data for a snapshot report about stock.
Sources
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
EWM: Stocks
Requires
/IMO/D_EWM21
This DataStore Object (advanced) contains data for the storage bins that were extracted from Extended
Warehouse Management (EWM).
Sources
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_EWM30
This DataStore Object (advanced) is used to store records related to transportation units.
Sources
This DSO is filled by the InfoSource EWM: Transportation Units (0WM_TU) (/IMO/EWM_IS30).
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_EWM40
This DataSource Object (advanced) contains the extracted results of the measurement service.
Sources
This DSO is filled by the InfoSource EWM: Measurement Service Results (0WM_MS_RESULT) (/IMO/EWM_IS40).
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/D_EWM50
Sources
Transformation
Field Rules
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
Data Modeling
Requires
/IMO/CMEWM01
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Inbound Delivery
Items (0WM_DLVI_IN).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM02
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Outbound Delivery
Items (0WM_DLVI_OUT).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM03
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Proof Of Delivery
(0WM_POD).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM04
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Value-Added Services
(0WM_VAS).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM10
This DataStore Object (Advanced) serves as the corporate memory DSO for the DataSource Warehouse Orders
(0WM_WO).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM11
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Warehouse Tasks
(0WM_WT_WO).
Use
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM12
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Exceptions
(0WM_EXCODE).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM30
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Transportation Units
(0WM_TU).
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM40
This DataStore Object (advanced) serves as the corporate memory DSO for the DataSource Measurement Service
Results (0WM_MS_RESULT).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
/IMO/CMEWM50
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
4.5.2 InfoSources
/IMO/EWM_IS01
This InfoSource contains the structure for providing inbound delivery items data to the EDW Core Layer. This
InfoSource is based on the DataSource Inbound Delivery Items (0WM_DLVI_IN)
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
/IMO/EWM_IS02
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS03
This InfoSource contains the structure for providing proof of delivery data to the EDW Core Layer. This InfoSource
is based on the DataSource Proof of Delivery (0WM_POD).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
/IMO/EWM_IS04
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS10
This InfoSource contains the structure for providing data for warehouse orders to the EDW Core Layer. This
InfoSource is based on the DataSource Warehouse Orders (0WM_WO).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS11
This InfoSource contains the structure for providing data for warehouse tasks to the EDW Core Layer. This
InfoSource is based on the DataSource Warehouse Tasks (0WM_WT_WO).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS12
This InfoSource contains the structure for providing data for exceptions to the EDW Core Layer. This InfoSource is
based on the DataSource Exceptions (0WM_EXCCODE).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS20
This InfoSource contains the structure for providing stock data to the EDW Core Layer. This InfoSource is based on
the DataSource Stocks (0WM_STOCK).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS21
This InfoSource contains the structure for providing storage bin data to the EDW Core Layer. This InfoSource is
based on the DataSource Storage Bins Full Upload (0WM_BIN_FULL).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
/IMO/EWM_IS30
This InfoSource contains the structure for providing data for transportation units to the EDW Core Layer. This
InfoSource is based on the DataSource Transportation Units (0WM_TU).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
/IMO/EWM_IS40
This InfoSource contains the structure for providing results of measurement services to the EDW Core Layer. This
InfoSource is based on the DataSource Measurement Service Results (0WM_MS_RESULT).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Requires
/IMO/EWM_IS50
This InfoSource contains the structure for providing executed workload data to the EDW Core Layer. This
InfoSource is based on the DataSource Executed Workload (0WM_EWL).
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
4.5.3 CompositeProvider
Definition
CompositeProvider: /IMO/V_EWM01
Use
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
Use
This CompositeProvider provides data on outbound deliveries extracted from the EWM system for analysis.
Data Modeling
0WM_REFID
CHA Reference Document Number
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM03
Use
Data Modeling
Definition
CompositeProvider: /IMO/V_EWM04
Use
This CompositeProvider provides data for value added services extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM10
Use
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM11
This CompositeProvider provides warehouse task data extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Use
This CompositeProvider provides exceptions data extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM20
Use
This CompositeProvider provides stocks data extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM21
Use
This CompositeProvider provides data on storage bins extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM30
Use
This CompositeProvider provides data on transportation units extracted from the EWM system for analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM40
Use
This CompositeProvider provides data from the measurement service extracted from the EWM system for
analysis.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
Definition
CompositeProvider: /IMO/V_EWM50
Use
This CompositeProvider provides data on executed workloads extracted from the EWM system for analysis. You
can use the characteristic Status (0WM_STATUS) to differentiate between valid, invalid, and deleted executed
workloads.
Data Modeling
* Exposes corresponding Calendar Week, Calendar Month, and Calendar Year as Navigation Attributes.
4.5.4 Queries
/IMO/V_EWM01_Q0001
You can use this query to display and analyze the number, weight, volume, and value of completed inbound
delivery items. You can also see the total and percentage of delivery items that were quality checked. This allows
you to perform a comparison of trends for a specific day across an extended time period.
Structure
Free Characteristics
Rows
/IMO/V_EWM02_Q0001
You can use this query to display and analyze the number, weight, volume, and value of completed outbound
delivery items grouped by day, week, or month. This information can reveal trends to help you make decisions
such as the following:
Structure
Free Characteristics
Rows
Columns
/IMO/V_EWM02_Q0002
You can use this query to display and analyze service levels achieved by a warehouse. This is measured as a ratio of
the number of outbound items delivered on time against the total number of outbound items delivered. On-time
delivery is achieved when the actual delivery time of an outbound item occurs before or at the delivery time
planned in the system. The actual time is defined as the time stamp at completion of the delivery task. For the
You can choose to see information displayed in a daily, weekly, or monthly format. Drilling down to individual items
allows you to discover why the warehouse could not meet a promised delivery date, or identify issues that call for
additional staff or equipment.
Structure
Free Characteristics
Columns
/IMO/V_EWM02_Q0003
You can use this query to see information about picking task errors or delivery item errors in the warehouse on a
daily, weekly, or monthly basis. This allows you to see developing trends, or know when the number of errors is
improving or getting worse. The query provides drill-down criteria, such as means of transport, route, document
type, and business partner, to allow you to see if the errors originate beyond the warehouse. Additional criteria
related to the warehouse activity area, time of day, or particular employee can help you identify internal sources of
error, and allow you to take actions to improve them.
This query provides the number of incorrect outbound delivery items reported in a confirmed proof of delivery
(PoD), the total number of outbound delivery items flagged by the PoD indicator, and the ratio of the incorrect
outbound delivery items over the total number of outbound delivery items. Time intervals are determined by the
goods issue end date and time.
Free Characteristics
Rows
Columns
/IMO/V_EWM21_Q0001
You can use this query to display and analyze the ratio of occupied bins over the total number of bins in a
warehouse on a given day. You can also use it to build weekly or monthly averages.
Structure
Free Characteristics
Rows
Columns
Use
This documentation describes the SAP HANA-optimized Business Content objects that you can use to take
advantage of the master data key mapping provided by SAP Master Data Governance.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Before using the SAP HANA-optimized Business Content for Master Data Governance, you need to configure
Master Data Governance.
General Settings
● Define the source system ID
For more information, see SAP BW/4HANA Content Add-On [page 7].
Features
In system landscapes with several systems, SAP Master Data Governance provides an understanding of enterprise
master data that is owned and maintained de-centrally. SAP MDG delivers capabilities to load master data from
different sources, to standardize the master data and to detect duplicates. For each of the resulting match groups,
SAP MDG - Consolidation creates unique key mappings (in SAP BW/4HANA context: ‘group IDs’) and calculates a
best record out of the duplicates in that group, using survivorship rules on the master data attributes. These best
records can then be used together with the key mapping information in dedicated analytical or business scenarios,
such as SAP BW/4HANA.
The HANA-optimized Business Content for Master Data Governance takes advantage of the MDG key mapping
groups and the best records for the object types business partner, vendor, customer and material to update the
● SAP MDG key mappings are provided by data source 0MDG_KEY_MAPPING from the SAP MDG client into SAP
BW/4HANA and used to update the local object IDs in the consolidated InfoObjects 0GN_VENDOR,
0GN_CUSTOM, and 0PRODUCT by an additional attribute ‘Group ID’. This allows you to consolidate e.g. purchase
or sales volume by vendor or customer group ID (0CI_GRP_PAR) or material group ID (0CI_GRP_PRO) across
all connected source systems for analysis.
Compounded key of Source System 0VENDOR key in ERP 0BPARTNER key in Group ID (MDG key
0GN_VENDOR system SRM mapping)
● As the key mapping groups are technically a GUID, the best record calculated by SAP MDG - Consolidation is
used in SAP BW/4HANA to provide presentable texts for the key mapping ‘Group IDs’ for reporting. This
information is loaded via data source 0BPARTNER_TEXT into 0CI_GRP_PAR and via data source
0MATERIAL_TEXT into 0CI_GRP_PRO.
With this information you can now consolidate transactional data in SAP BW/4HANA by vendor, customer and
material by MDG key mapping groups and display these groups by the text of the best record.
1 Load 0GN_VENDOR and SAP ERP, SAP SRM, SAP Updates attributes and texts
0GN_CUSTOM by the attribute CRM for 0GN_VENDOR and
and text data sources (e.g. 0GN_CUSTOM
0VENDOR_ATTR,
0VENDOR_TEXT,
0CUSTOMER_ATTR,
0BPARTNER_ATTR, …) from
the local source systems
2 Load advanced DataStore ob SAP MDG client Loads only MDG OTC object
ject /IMO/D_MDG01 by data types ‘business partner’, ‘ven
source 0MDG_KEY_MAPPING dor’ or ‘customer’ and calcu
lates a compounded key in In
foObject 0MD_BPKEY
1 Load 0PRODUCT by the at SAP ERP Updates attributes and texts
tribute and text data sources for 0PRODUCT
(e.g. 0MATERIAL_ATTR,
0MATERIAL_TEXT, …) from
the local source systems
2 Load advanced DataStore ob SAP MDG client Loads only MDG OTC object
ject /IMO/D_MDG02 by data type ‘material’ and calculates
source 0MDG_KEY_MAPPING a compounded key in InfoOb
ject 0MD_PRODKEY
/IMO/D_MDG01
This DSO (advanced) contains MDG key mapping information for the business object types business partner,
vendor and customer. It is enriched by a compounded generic key (0MD_BPKEY) that is used to further update
the BW InfoObjects consolidated vendor (0GN_VENDOR) and consolidated customer (0GN_CUSTOMER).
Sources
This DSO is filled by the InfoSource MDG: Key Mapping (0MDG_KEY_MAPPING) (technical name: /IMO/
MDG_IS01).
Transformation
Field Routines
MDG System Flag MDGSYSFLAG Filled with “X” if origin system is MDG
System. Used to identify master record.
MDG Generic Key for BP/Vendor/Customer 0MD_BPKEY Concatenation of Source System ID, Ob
ject Type, and Business Partner, Vendor
or Customer.
Update Date 0UPD_DATE Filled with system date during the data
load.
DTP Filter
There is a DTP Filter routine for field OTC (Business Object Type) to ensure that only business partner (OTC = 147),
vendor (OTC = 159), and customer (OTC = 266) key mappings are loaded.
Delta Update
Data Modeling
Requires
/IMO/D_MDG02
Sources
This DSO is filled by the InfoSource MDG: Key Mapping (0MDG_KEY_MAPPING)(technical name:/IMO/
MDG_IS01).
Transformation
Field Routines
Name of Target Field/ InfoObject Technical Name of Target Field/ Transformation Rule
InfoObject
MDG System Flag MDGSYSFLAG Filled with “X” if origin system is MDG
System. Used to identify master record.
MDG Generic Key for Product/Material 0MD_BPKEY Concatenation of Source System ID, Ob
ject Type, and Material.
Update Date 0UPD_DATE Filled with system date during the data
load.
DTP Filter
There is a DTP Filter routine for field OTC (Business Object Type) to ensure that material (OTC = 194) key
mappings are loaded.
Delta Update
Data Modeling
Requires
IMO/MDG_IS01
This InfoSource contains the structure to provide key mapping information from SAP Master Data Governance
system into the EDW Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit logical backend
system (based on LOGSY)
*For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7]
Data Modeling
Requires
This documentation describes the SAP HANA-optimized business content for the following SAP for Utilities
components:
The content has been tailored to the requirements of utilities companies. The content contains a large number of
key figures and characteristics for utilities-specific reporting. You can combine this information with data from
other applications such as Controlling, Financial Accounting and Human Resources.
Use
You can use this SAP-HANA-optimized business content to analyze data from SAP S/4HANA Utilities. You can
evaluate various master data, which has been entered using the flexible update.
The data model meets the requirements of the LSA++ (Layered Scalable Architecture), which has been optimized
for the execution of SAP BW/4HANA.
For more information about general modeling for SAP HANA-optimized Business Content, see SAP BW/4HANA
Content Add-On [page 7]
Note
You should only use the objects displayed in the data flow.
Prerequisites
Before you can use the SAP-HANA-optimized business content, you must define the source system ID.
Rate Data, Point of Delivery/Installation Allocation, Business Partner Data, Contract Account Fields, Tme-Independent Data
/IMO/D_UCIO01
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Rate Data for Installation - Devices (EASTL
0UC_DEVINST_ATTR) ( /IMO/UCIO_IS01).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCIO02
This DataStore object (advanced) contains multiple attributes for the rate data in a register. Rate data is required
to bill rental and lease prices for example. Rate data always refers to one utility installation. The DataStore object is
used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Rate Data for Installation - Register
(0UC_REGINST_STR_ATTR) ( /IMO/UCIO_IS02).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCIO03
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Allocation Installation - Point of Delivery
(0UC_PODINST_ATTR) ( /IMO/UCIO_IS03).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCIO04
The DataStore object (advanced) contains the time-independent attributes for the utilities contract and can be
used for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Contract - Time-Independent Attributes
(0UCCONTRACT_ATTR_2) (. /IMO/UCIO_IS04).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCIO06
The DataStore object (advanced) contains the time-independent attributes for the utilities installation and can be
used for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Installation- Time-Independent Attributes
(0UCINSTALLA_ATTR_2) ( /IMO/UCIO_IS06).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCIO07
The DataStore object (advanced) contains the time-dependent attributes for the utilities installation and can be
used for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Installation- Time-Dep. Attributes (UCINSTALLAH_ATTR_2)
(/IMO/UCIO_IS07).
Transformation
Field Routines
Delta Update
Requires
/IMO/D_UCIO08
The DataStore object (advanced) contains utilities industry-specific attributes for the business partner and can be
used for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Business Partner Data (0UCBU_PART_ATTR_3) ( /IMO/
UCIO_IS08).
Transformation
Field Routines
Delta Update
Data Modeling
/IMO/D_UCIO09
The DataStore object (advanced) contains the time-dependent attributes for the utilities contract and can be used
for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Contract Account - Partner-Dependent Attr.
(0UC_ACCNTBP_ATTR_2) ( /IMO/UCIO_IS09).
Transformation
Delta Update
Data Modeling
Requires
/IMO/D_UCIO10
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Premise (0UCPREMISE_ATTR_2) ( /IMO/UCIO_IS10).
Transformation
Field Routines
Delta Update
Data Modeling
UCIO: Premise
Requires
/IMO/D_UCIO11
The DataStore object (advanced) contains the attributes for the connection object and can be used for master
data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Connection Object (with Service Addr.)
(0UC_CONNOBJ_ATTR) (/IMO/UCIO_IS11).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCIO12
The DataStore object (advanced) contains the attributes for the device location and can be used for master data
reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Device Location (0UC_DEVLOC_ATTR) ( /IMO/
UCIO_IS12).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCIO13
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Point of Delivery - Time-Dependent Attributes
(0UC_POD_EXT_ATTR) (/IMO/UCIO_IS13).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCIO14
The DataStore object (advanced) contains the time-independent attributes for the point of delivery and can be
used for master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Point of Delivery - Time-Dependent Attributes
(0UC_POD_EXT_ATTR) (/IMO/UCIO_IS14).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCIO15
The DataStore object (advanced) contains the time-independent attributes for devices and can be used for master
data reporting. The DataStore object is used for the following purposes:
Sources
This DataStore object is filled by the InfoSource UCIO: Device - Time-Independent Attributes (EGERS
0UC_DEVICE_ATTR) ( /IMO/UCIO_IS15).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCIO16
The DataStore object (advanced) contains the time-dependent attributes for devices and can be used for master
data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO Devices - Time-Dep. Attributes (EGERH
0UC_DEVICEH_ATTR) (/IMO/UCIO_IS16).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCIO17
The DataStore object (advanced) contains the attributes for the device information record and can be used for
master data reporting. The DataStore object is used for the following purposes:
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
Sources
This DataStore object is filled by the InfoSource UCIO: Device Data: Info Record for PoD, Historical ( /IMO/
UCIO_IS17).
Transformation
Field Routines
Delta Update
Data Modeling
/IMO/D_UCIO18
Note
Note that prior to the update, you must activate the data in the data targets.manually or by using a process
chain.
The following key figures that were previously used in SAP BI Content have the data type DEC (3 decimal places):
Key figures are provided with 5 decimal places in the table EZUZ in SAP for Utilities. To ensure that the update in
SAP BW on HANA is exact, the following new key figures have been included in the ADSO:
The characteristic 0UC_REGIST was not changed with this content, meaning that the existing key figures are used
to update the attributes in this characteristic.
Sources
This DataStore object is filled by the InfoSource UCIO: Register Attributes (ETDZ 0UC_REGIST_ATTR) ( /IMO/
UCIO_IS18).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/CMUCIO06
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U: Time-
Dependent Data for Utilities Installation (0UCINSTALLA_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO04
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U: Time-
Independent Data in Contract (0UCCONTRACT_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO03
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Contract
Account Fields (0UC_PODINST_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO02
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Rate Data for
Installation Structure at Register Level (<sap-technical-name>EZUZ</sap-technical-name>).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO01
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Rate Data for
Installation Structure at Device Level (EASTL) (0UC_DEVINST_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO07
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U: Time-
Dependent Data in Time-Dependent Data in Utilities Installation(0UCINSTALLAH_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO08
This DataStore object (advanced) is used as the corporate memory DSO for the DataSource IS-U: Business
Partner Data(0UCBU_PART_ATTR_3).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO09
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Contract
Account Fields (0UC_ACCNTBP_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO10
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U: Premise Data
(0UCPREMISE_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO11
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U: Connection
Object (with Service Address) (0UC_CONNOBJ_ATTR_2).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO12
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device Location
(0UC_DEVLOC_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO13
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of Delivery
External ID (0UC_POD_EXT_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO14
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of Delivery
Header Data (0UC_POD_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO15
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device Master
Data: EGERS (0UC_DEVICE_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO16
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device Master
Data: Historical Master Record (EGERH) (0UC_DEVICEH_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO17
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device Master
Data: Shortened Record for PoD (Historical) (0UC_DEVICER_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCIO18
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Technical Data
from Installed Register (ETDZ) (0UC_REGIST_ATTR).
Use
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/UCIO_IS01
This InfoSource extracts the billing-relevant data for a device for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS02
This InfoSource extracts the billing-relevant data for the registers in a meter for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS03
This InfoSource supplies the allocation of points of delivery to the respective utilities installations for the EDW core
layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS04
This InfoSource supplies the time-independent attributes for the utilities contract for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS06
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS07
This InfoSource supplies the time-dependent attributes for the utilities installation for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS08
This InfoSource supplies the utilities-specific attributes for the business partner for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS09
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS10
This InfoSource supplies the attributes for the premise for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS11
This InfoSource supplies the attributes for the connection object for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS12
This InfoSource supplies the attributes for the device location for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS13
This InfoSource supplies the external PoD description for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS14
This InfoSource supplies the header data for the IS-U point of delivery for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS15
This InfoSource supplies the time-independent attributes for devices for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS16
This InfoSource supplies the time-dependent attributes for devices for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS17
This InfoSource supplies the attributes for the device info record for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCIO_IS18
This InfoSource supplies the attributes for the register for a device for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
6.1.3 CompositeProvider
Definition
CompositeProvider: /IMO/V_UCIO01
This Composite Provider provides all contract account relationships for a contract. The Composite Provider
contains the following master data:
The master data is linked by an Inner Join so that all activated characteristics can be used for the restriction.
Data Modeling
InfoProvider
InfoObjects
Definition
CompositeProvider: /IMO/V_UCIO02
Use
This Composite Provider provides all contract account relationships for a business partner. The Composite
Provider contains the following master data:
● Business Partner
● Contract Account (Partner-Independent)
● Contract Account (Partner-Dependent)
● Relationship of Business Partner to Contract Account
● Deletion Indicator
The master data is linked by an Inner Join so that all activated characteristics can be used for the restriction.
Data Modeling
InfoProvider
InfoObjects
Use
This documentation describes the SAP-HANA-optimized business content, that you can use to analyze data from
SAP S/4HANA Utilities.
The data model meets the requirements of the LSA++ (Layered Scalable Architecture), which has been optimized
for the execution of SAP BW/4HANA.
For more information about general modeling for SAP HANA-optimized Business Content, see SAP BW/4HANA
Content Add-On [page 7]
Note
You should only use the objects displayed in the data flow.
Prerequisites
Before you can use the SAP-HANA-optimized business content, you must define the source system ID.
Features
You use this content to evaluate EDM-relevant transaction data (such as profile values) using SAP BW/4HANA.
Data Flow
Meter Reading Document, Meter Reading Order, Meter Reading Reasons and Point of Delivery Allocation
BW Extractor Profiles for Settlement Document, Allocate Usage Factor and Load Profiles, Load Shapes, Usage Factors, Synthetic
Profiles and Profile Header Data
/IMO/D_UCDM01
The meter reading document saves all meter reading data for the register of a device (equipment). This includes
the meter reading status, the plausibility data, and the meter reading result. The meter reading document does not
include the consumption. This is because this can only be determined after considering various factors (many
factors must be considered for the gas division). The DataStore object (advanced) is used for reporting without
updates in other DataStore objects (advanced). The DataStore object (advanced) is used specifically in the
Composite Providers /IMO/V_UCDM01, /IMO/V_UCDM02 and /IMO/V_UCDM03 with the meter reading reason
and the billing order to analyze the following data:
You can for example use the combination of meter reading data and other utilities-specific master data in SAP
BW/4HANA to identify the consumption of vacant installations and disconnected devices.
Caution
Note that the DataStore object (advanced) can be very large. You can use the update definition to define
whether deleting a meter reading document in SAP Utilities (as provided in the Business Content) also results in
the deletion of the meter reading document in this DataStore object (advanced), or just results in a deletion
flag.
The key figure Difference Between Scheduled and Billed Meter Reading Date (Days) (0UC_MR_P_A) is calculated
using the following transformation rule:
Delta Update
Requires
/IMO/D_UCDM02
The meter reading reason is defined for all meter reading documents for an installation. In addition to the
installation and meter reading reason, further information is available to you. For example, the meter reading unit,
the planned meter reading date, and the billing portion. The DataStore object (advanced) is used for the following
evaluations:
The DataStore object (advanced) is used specifically in the Composite Providers /IMO/V_UCDM01 and /IMO/
V_UCDM02 with the meter reading document and the billing order to analyze the following:
You can use the combination of meter reading data and other utilities-specific master data in SAP BW/4HANA for
example to identify the consumption of vacant installations and disconnected devices.
Caution
Note that the DataStore object (advanced) can be very large. You can use the update definition to define
whether deleting a meter reading reason in SAP Utilities (as provided in the Business Content) also results in
the deletion of the meter reading document in this DataStore object (advanced), or just results in a deletion
flag.
This DataStore object is filled by the InfoSource UCDM: Meter Reading Reason for Meter Reading Document
(EABLG) (0UC_MTR_DOCR) ( /IMO/UCDM_IS02).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCDM03
In SAP Utilities, devices are usually allocated for billing reasons. The allocation can be between primary and
secondary meters, transformers and measuring devices, or ripple control receivers and double-rate meters. The
allocations are usually time-dependent, whereby it is seldom the case that multiple time slices exist for the same
device. These relationships are also required in SAP BW/4HANA to map deregulation analyses.
Recommendation
Note that device relationships do not exist in every division. Therefore, we recommend that you only integrate
this DataStore object in Composite Providers as required.
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
Sources
This DataStore object is filled by the InfoSource UCDM: Device-Device Allocation (EZUG) (0UC_DEVALLC_ATTR)
( /IMO/UCDM_IS03).
Transformation
Field Routines
Data Modeling
Requires
/IMO/D_UCDM04
In SAP Utilities a billing order is created if an installation is to billed. It is not necessary to also create a meter
reading document and meter reading reason for this purpose. The billing order is deleted following successful
billing, and is then no longer available in SAP BW/4HANA. In addition to the installation, additional information is
available to you. For example, the meter reading unit, the planned billing date and the billing portion.
Sources
This DataStore object is filled by the InfoSource UCDM: Billing Order (ETRG) (0UC_BILLORD) ( /IMO/UCDM_IS04).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCDM05
The allocation of a logical register to a logical device is particularly necessary in SAP Utilities for billing reasons.
The allocation is time-dependent, whereby it is seldom the case that multiple time slices exist for the same
register. These relationships are also required in SAP BW/4HANA to map device and register analyses.
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
Sources
This DataStore object is filled by the InfoSource UCDM: Register to Device Allocation (EZUZ)
(0UC_REGALLOC_ATTR) ( /IMO/UCDM_IS05).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Data Modeling
Requires
/IMO/D_UCDM06
The allocation of a logical device to a point of delivery is only necessary in SAP Utilities for technical reasons. The
allocation is time-dependent, whereby it is seldom the case that multiple time slices exist for the same device. In
most cases, this object is only defined for commercial and industrial customers.
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
Sources
This DataStore object is filled by the InfoSource UCDM: Device to PoD Allocation (EUILNR) (0UC_PODLNR_ATTR)
( /IMO/UCDM_IS06).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM07
The allocation of a logical register to a point of delivery is only necessary in SAP Utilities for technical reasons. The
allocation is time-dependent, whereby it is seldom the case that multiple time slices exist for the same logical
register. In most cases, this object is only defined for commercial and industrial customers.
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
Sources
This DataStore object is filled by the InfoSource UCDM: Register to PoD Allocation (EUILZW)
(0UC_PODLREG_ATTR) ( /IMO/UCDM_IS07).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM08
In SAP Utilities, the allocation of a point of delivery to a point of delivery group is necessary for deregulation. The
allocation is time-dependent, whereby it is seldom the case that multiple time slices exist for the same point of
delivery.
You can use the DataStore object for the following analyses:
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
The key fields correspond to the table EUIPODGROUP in SAP ECC Utilities.
Sources
This DataStore object is filled by the InfoSource UCDM: Point of Delivery -Point of Delivery Group Assgmt
(0UC_PODPGRP_ATTR) ( /IMO/UCDM_IS08).
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM09
The allocation of a point of delivery to a settlement unit describes the points of delivery that are to be regarded as
one unit for settlement purposes. In SAP Utilities this is particularly relevant for deregulation. The allocation is
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
The key fields correspond to the table EEDMUISETTILUNIT in SAP ECC Utilities.
Sources
This DataStore object is filled by the InfoSource UCDM: PoD Sett. Unit Assignment (0UC_PODSTTL_ATTR) ( /IMO/
UCDM_IS09).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM10
In SAP Utilities, the allocation of a point of delivery to a grid is necessary for deregulation. The allocation is time-
dependent, whereby it is seldom the case that multiple time slices exist for the same point of delivery. In SAP
Utilities, the grid is an object that represents the service territory or part of this territory for a distribution
company.
Caution
If you want to use other fields as the key fields for making selections in reporting, or as links in Composite
Providers, you must define them as a secondary index following the initial creation of the fields.
The key fields correspond to the table EUIGRID in SAP ECC Utilities.
Sources
This DataStore object is filled by the InfoSource UCDM: Point of Delivery-Grid Allocation (0UC_PODGRID_ATTR)
( /IMO/UCDM_IS10).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM11
The settlement document groups information about a settlement task. The contents of the document define
which settlement procedure is to be used for a settlement, and for which period the settlement is to be executed.
The actual settlement is performed by the settlement run.
Sources
This DataStore object is filled by the InfoSource UCDM: Header Data for Settlement Document (0UC_SETTLDOC)
( /IMO/UCDM_IS11).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCDM12
This DataStore object (advanced) describes the settlement units for which settlement is performed collectively in
a single settlement run. The consumption accrued at, or forecast for the points of delivery for a settlement unit is
aggregated in the settlement run, and is provided as a result. The DataStore object (advanced) is used as a linking
element in Composite Providers in SAP BW/4HANA.
Sources
This DataStore object is filled by the InfoSource UCDM: Settlement Document Settlement Unit
(0UC_SETTLDOCUNIT) ( /IMO/UCDM_IS12).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM13
This DataStore object (advanced) describes profiles that were updated as results or interim results during a
settlement run. The DataStore object (advanced) is used as a linking element in Composite Providers in SAP BW/
4HANA.
Sources
This DataStore object is filled by the InfoSource UCDM: Profiles for Settlement Document (0SETTLDOCUPDP)
( /IMO/UCDM_IS13).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
/IMO/D_UCDM14
This DataStore object (advanced) describes the allocation of usage factors to utilities installations. The usage
factor for an installation is related to a synthetic profile, and is generally used for residential customers. Allocation
to installations is controlled by the object type INSTLN. A filter, which makes the restriction to this object type
should be recorded in the data transfer process (DTP).
Note
Once a month or once a year, the consumption value is determined periodically as a cumulative consumption
value. The consumption value must be distributed for time intervals that are relevant for settlement. Synthetic
Example
A standard synthetic profile is 1000kWh. The consumption for an installation in the standard period is 800 kWh.
For this reason, the usage factor is 0.8.
Caution
Use in Composite Providers
A profile allocation changes, it takes the logical profile allocation number of the changed profile.
This DataStore object (advanced) is part of reporting during the creation of allocation lists and stock lists.
Caution
Allocation to installations is controlled by the object type INSTLN. A filter that makes the restriction to this
object type should be recorded in the transformation (routine) or data transfer process (DTP).
Sources
This DataStore object is filled by the InfoSource UCDM: Usage Factor BOR Object Allocation (0UC_UFASS) ( /IMO/
UCDM_IS14).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Requires
/IMO/D_UCDM15
This DataStore object (advanced) describes the allocation of load profiles to utilities installations. This allocation
generally affects commercial and industrial customers. Residential customers are evaluated using the usage
factor. Allocation to installations is controlled by the object type INSTLN. A filter, which makes the restriction to
this object type should be recorded in the data transfer process (DTP).
Note
Consumption is read using an interval meter in the time intervals relevant for settlement. The summation of
consumption values can also be performed by adding up the consumption values of each time interval. A load
profile is a "measured profile", as opposed to a "synthetic profile".
Note
Use in Composite Providers
This DataStore object is part of reporting within the creation of allocation lists and stock lists.
Sources
This DataStore object is filled by the InfoSource UCDM: Load Profile to BOR Object Allocation (0UC_LPASS_ATTR)
( /IMO/UCDM_IS15).
Transformation
Field Routines
Delta Update
Data Modeling
Requires
/IMO/D_UCDM16
This DataStore object (advanced) describes the interval points of delivery, including settlement-relevant profiles,
installations, and settlement units that have been selected during the settlement run. Within a settlement run, the
aggregation of accrued or forecast consumption values is based on this data.
Sources
This DataStore object is filled by the InfoSource UCDM: Load Shapes for Each Settlement Run (0UC_SETTLIN)
( /IMO/UCDM_IS16).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCDM17
This data store object (advanced) describes the points of delivery, installations, and their usage factors, which
were selected during a settlement run. The "usage factor" describes the consumption for a utilities installation
Sources
This DataStore object is filled by the InfoSource UCDM: Usage Factors Settlement Run (0UC_SETTLUF) ( /IMO/
UCDM_IS17).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/D_UCDM18
This DataStore object (advanced) describes the load profiles and synthetic load profiles in the Energy Data
Management (EDM) component. The DataStore object (advanced) is used for the following evaluations:
Sources
This DataStore object is filled by the InfoSource UCDM: Profile Header Data (0UC_PROFILE_ATTR) ( /IMO/
UCDM_IS18) and the InfoSource UCDM: Synthetic Profiles (0UC_SYNPROF_ATTR) (/IMO/UCDM_IS19).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Field Routines
All key figures are updated using the aggregation behavior "Overwrite”.
Delta Update
Data Modeling
Requires
/IMO/CMUCDM01
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM02
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Meter Reading
Reasons for Meter Reading Document (EABLG) (0UC_MTR_DOC).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM03
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device
Allocations at Device Level (EZUG).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
/IMO/CMUCDM04
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Billing Order
(ETRG) (0UC_BILLORD).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM05
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Device
Allocations at Register Level (EZUZ).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM06
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of Delivery
Allocation to Logical Device (0UC_PODLNR_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM07
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of Delivery
Allocation to Logical Register (0UC_PODLREG_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM08
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM09
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of Delivery
Allocation to Settlement Unit (0UC_PODSTTL_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM10
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Point of
Delivery-Grid Allocation (0UC_PODGRID_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
/IMO/CMUCDM11
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Settlement
Document Header Data (0UC_SETTLDOC).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM12
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Settlement
Document Settlement Units:
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM13
This DataStore object (advanced) is used as the corporate memory aDSO for the DataaSource Profiles for
Settlement Document (0UC_SETTLDOCUPDP).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM14
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Allocation of Usage
Factor to Any BOR Objects (0UC_UFASS).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
Caution
Allocation to installations is controlled by the object type INSTLN. A filter that makes the restriction to this
object type should be recorded in the transformation (routine) or data transfer process (DTP).
/IMO/CMUCDM15
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Allocation of Usage
Factor to Any BOR Objects (0UC_LPASS_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
Caution
Allocation to installations is controlled by the object type INSTLN. A filter that makes the restriction to this
object type should be recorded in the transformation (routine) or data transfer process (DTP).
/IMO/CMUCDM16
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Load Shapes for
Each Settlement Run (0UC_SETTLIN).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM17
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Usage Factors for
Each Settlement Run (0UC_SETTLUF).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM18
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Profile Header Data
(0UC_PROFILE_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
/IMO/CMUCDM19
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource Synthetic Profiles:
Additional Data (0UC_SYNPROF_ATTR).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
6.2.2 InfoSources
/IMO/UCDM_IS01
This InfoSource extracts all of the meter reading data for a device for the EDW core layer. The meter reading
document saves all meter reading data for the register of a device (equipment). This includes the meter reading
status, the plausibility data, and the meter reading result. The meter reading document does not include the
consumption. This is because this can only be determined after considering various factors (for example, the Gas
division).
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
/IMO/UCDM_IS02
This InfoSource supplies the meter reading reasons for meter reading documents for the EDW core layer. You
define a meter reading reason for all of an installation's meter reading documents. In addition to the installation
and meter reading reason, further information is available to you. For example, the meter reading unit, the planned
meter reading date, and the billing portion.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS03
This InfoSource supplies the device-device allocation for the EDW core layer. In IS-U/CCS devices are mostly
allocated for billing reasons. The allocation can be between primary and secondary meters, transformers and
measuring devices, or ripple control receivers and double-rate meters. The allocations are usually time-
dependent, whereby it is seldom the case that multiple time slices exist for the same device.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS04
This InfoSource supplies the billing orders for the EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS05
This InfoSource supplies the register-device allocation for the EDW core layer. The allocation of a logical register to
a logical device is particularly necessary in IS-U/CCS for billing reasons. The allocation is time-dependent,
whereby it is seldom the case that multiple time slices exist for the same register.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
/IMO/UCDM_IS06
This InfoSource supplies the device-point of delivery allocation for the EDW core layer. The allocation of a logical
device to a point of delivery in IS-U/CCS is necessary for technical reasons and is time-dependent, whereby it is
seldom the case that multiple time slices exist for the same device. In most cases, this object is only defined for
commercial and industrial customers.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Requires
/IMO/UCDM_IS07
This InfoSource supplies the register-point of delivery allocation for the EDW core layer. The allocation of a logical
register to a point of delivery in IS-U/CCS is necessary for technical reasons and is time-dependent, whereby it is
seldom the case that multiple time slices exist for the same register. In most cases, this object is only defined for
commercial and industrial customers.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Requires
/IMO/UCDM_IS08
This InfoSource supplies the point of delivery-point of delivery group allocation for the EDW core layer. The
allocation of a point of delivery to a point of delivery group in IS-U/CCS is necessary for deregulation processes
and is time-dependent, whereby it is seldom the case that multiple time slices exist for the same point of delivery.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Requires
/IMO/UCDM_IS09
This InfoSource supplies the point of delivery-settlement unit allocation for the EDW core layer. The allocation of a
point of delivery to a settlement unit describes the points of delivery that are to be regarded as one unit for
settlement purposes. In SAP Utilities this is particularly relevant for deregulation. The allocation is time-
dependent, whereby it is seldom the case that multiple time slices exist for the same point of delivery.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS10
This InfoSource supplies the point of delivery-grid allocation for the EDW core layer. The allocation of a point of
delivery to a grid in IS-U/CCS is necessary for deregulation and is time-dependent, whereby it is seldom the case
that multiple time slices exist for the same point of delivery. The grid is an object in the IS-U system that
corresponds to the service area or part of the service area of a distributor.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS11
This InfoSource supplies the data for the settlement dolcument for the EDW core layer. The settlement document
groups information about a settlement task. In the document, you can define which settlement procedure is to be
used for settlement, and for which period the settlement is to be executed. The actual settlement is performed by
the settlement run.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS12
This InfoSource supplies the settlement units that are settled collectively in a single settlement run for the EDW
core layer. During the settlement run, the system aggregates the actual or forecasted consumption values for the
points of delivery of a settlement unit and makes the consumption values available as a result.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS13
This InfoSource supplies profiles that were updated as results or interim results within a settlement run for the
EDW core layer.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS14
This InfoSource supplies the allocation of usage factors to the utilities installation for the EDW core layer. The
usage factor for an installation is related to a synthetic profile, and is generally used for residential customers.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Requires
/IMO/UCDM_IS15
This InfoSource supplies the allocation of load profiles to the utilities installation for the EDW core layer. This
allocation generally affects commercial and industrial customers. The usage factor is used to valuate residential
customers.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS16
This InfoSource supplies the interval points of delivery, including settlement-relevant profiles, installations, and
settlement units that have been selected within the settlement run for the EDW core layer. Within a settlement run,
the aggregation of accrued or forecast consumption is based on this data.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS17
This InfoSource supplies the points of delivery, installations, and their usage factors, which were selected during a
settlement run for the EDW core layer. The usage factor describes the consumption for a utilities installation with
reference to an assigned, synthetic profile. Within a settlement run, the aggregation of accrued or forecast
consumption values is based on this data.
Transformation
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS18
This InfoSource supplies the attributes for the load profile in Energy Data Management for the EDW core layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
/IMO/UCDM_IS19
This InfoSource supplies the attributes for the synthetic profile in Energy Data Management for the EDW core
layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
Requires
6.2.3 CompositeProvider
You use this Composite Provider to perform an aggregated evaluation of meter reading documents. You use these
evaluations to determine how efficient a meter reading is, and not to to list specific meter reading documents. Use
the associated DataStore object (advanced) (/IMO/D_UCDM01) to list the meter reading documents.
Note that the system only posts meter reading documents, which have already been billed. This allows you to
determine indicators such as Number of Days Between Planned and Actual Meter Reading, and refer them to a
meter reader.
The analysis allows you, for example, to quickly and easily determine:
Data Modeling
InfoProvider
InfoObjects
Locked Meter Readings /IMO/V_UCDM01_RK003 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT) [2] –
Locked automatically and [3] – Locked
by user
Correct Meter Readings /IMO/V_UCDM01_RK004 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT)
[1] – Billable
[7] – Billed
Scheduled Meter Readings /IMO/V_UCDM01_RK005 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT) [0] – Me
ter reading order created
This Composite Provider analyzes current meter reading data. It contains the DataStore objects (Advanced)
UCDM: Meter Reading Reason for Meter Reading Document (/IMO/D_UCDM02) and UCDM: Meter Reading
Document (/IMO/D_UCDM01).
The meter reading reason is defined for all meter reading documents for an installation. In addition to the
installation and meter reading reason, other information is also available to you. For example, the meter reading
unit, the scheduled meter reading date, and the billing portion.
The meter reading document saves all meter reading data for the register of a device (equipment). This includes
the meter reading status, the plausibility data, and the meter reading result. Use the Composite Provider to
analyze the following:
The combination of meter reading data and other utilities-specific master data in SAP Business Warehouse (SAP
BW) allows you to identify the consumption of empty installations and locked devices.
Data Modeling
InfoProvider
DataStore Object (Advanced) UCDM: Meter Reading Reason for Meter /IMO/D_UCDM02
Reading Document
InfoObjects
This Composite Provider is used to analyze the current meter reading status, including the billing preparation. It
contains the DataStore objects (Advanced) UCDM: Meter Reading Reason for Meter Reading Document (/IMO/
D_UCDM02), UCDM: Meter Reading Document (/IMO/D_UCDM01) and UCDM: Billing Order (/IMO/D_UCDM04). The
meter reading reason is defined for all meter reading documents for an installation. In addition to the installation
and meter reading reason, other information is also available to you. For example, the meter reading unit, the
scheduled meter reading date, and the billing portion.
The meter reading document saves all meter reading data for the register of a device (equipment). This includes
the meter reading status, the plausibility data, and the meter reading result. The billing order is created if an
installation is to be billed. It is not necessary to also create a meter reading document and meter reading reason
for this purpose. The billing order is deleted after a successful billing, and is then no longer available in SAP BW/
4HANA. In addition to the installation, other information is also available to you. For example, the meter reading
unit, the scheduled billing date and the billing portion.
● The number of installations prepared for billing, by meter reading unit and portion
● The number of, and reason for open billings, by meter reading unit
Data Modeling
InfoProvider
DataStore Object (Advanced) UCDM: Meter Reading Reason for Meter /IMO/D_UCDM02
Reading Document
InfoObjects
Meter Reading Prepared /IMO/V_UCDM03_RK001 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT) [0] – Me
ter reading order created
Plausible Meter Readings /IMO/V_UCDM03_RK002 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT
[1] – Billable
[7] – Billed
Implausible Meter Readings /IMO/V_UCDM03_RK003 The key figure Meter Reading Document
Counter (0UC_MD_CNT) with the meter
reading status (0UC_MRSTAT) [2] –
Locked automatically and [3] – Locked
by user
6.2.4 Queries
/IMO/V_UCDM01_Q0001
This query shows you the successful meter readings for each meter reader for a selected month. The aggregated
view allows you to analyze the meter reading quality of the different meter readers (meter reading companies) and
shows the differences that can be used for improvement measures. This query is called regularly by the
Note
Note that in conjunction with the formulas listed below, you can add the indicator Difference Between Planned
and Actual Meter Reading to the analysis if required in the Query Builder. You can then analyze the quality of the
individual meter readers (meter reading companies) in greater detail.
Data Modeling
Free Characteristics
Object Type Name Technical Name
Variables
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
● Locked by Agent
● Automatically Locked
● Billable
● Released by Agent
● Checked Independently
● Billed
● Partially Billed
IMOV_UCDM01_Q0001
/IMO/V_UCDM01_Q0002
This query shows you the released meter readings for the last 12 months. The selection is made using the variable
Last 12 Months Excluding the Current Month (0CXIO_CML12PMCY) for the time characteristic Calendar Year/Month
(0CALMONTH).
Note
Note that in conjunction with the variables used below, the calendar year/month is derived from the actual date
of the meter reading.
Data Modeling
Free Characteristics
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
● Checkpoint (Greater
than, Not assigned)
● Independent Checkpoint
(Greater than; Not as
signed)
IMOV_UCDM01_Q0002
/IMO/V_UCDM02_Q0001
This query shows the number of meter readings for each meter reading reason and scheduled meter reading date.
You can also drilldown by meter reading unit. This query is normally called on a daily basis by the responsible
manager in the back-office ‘meter reading’, together with other meter reading reports, to determine the workload
for the employee in the back office and the meter reader. For this reason, the report portfolio for the meter reading
manager should also contain other meter reading reports, including the overview of the meter reading status.
Note
Note the following information in conjunction with the following table entries:
● Free Characteristics: The meter reading unit is often also used to drilldown further in the meter readings.
● Variables Used: The variables are compared with other meter reading reports. The selection of the meter
reading date is important here.
The scheduled meter reading date is predetermined by the schedule records, and is only valid as a guide
value.
Data Modeling
Free Characteristics
Object Type Name Technical Name
Variables
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Counter for Meter Reading 0UC_MR_CNT Counter for Meter Reading
Reason
Reason
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
IMOV_UCDM02_Q0001
/IMO/V_UCDM03_Q0001
This query shows the number of meter readings by status, portion and scheduled meter reading date. You can also
drill down according to other characteristics in the meter reading. This allows you to more accurately verify the
data. This query is normally called on a daily basis by the responsible manager in the back-office ‘meter reading’,
together with other meter reading reports, to check the quality of the meter readings and determine the workload
for the employee in the back office.
● Free Characteristics: The meter reading unit is often also used to drill down further in the meter readings.
To improve performance, the meter reading unit is provided with an index in the corresponding ODS object.
● Variables Used: The variables are compared with other meter reading reports. The selection of the meter
reading date is important here.
The scheduled meter reading date is predetermined by the schedule records, and is only valid as a guide
value. The billing portion is the reference unit for all meter readings to be billed at a certain time.
Data Modeling
Free Characteristics
Object Type Name Technical Name
Variables
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Meter Readings Prepared /IMO/V_UCDM03_RK001 Meter Readings with Status
'Meter Reading Order
Created'
Key Figure Plausible Meter Readings /IMO/V_UCDM03_RK002 Meter Readings with Status
● Billed
● Released by Agent
● Billable
● Partially Billed
Key Figure Implausible Meter Readings /IMO/V_UCDM03_RK003 Meter Readings with Status
● Locked by Agent
● Automatically Locked
IMOV_UCDM03_Q0001
Use
You can use this SAP-HANA-optimized business content to analyze data from SAP S/4HANA Utilities.
The data model meets the requirements of the LSA++ (Layered Scalable Architecture), which has been optimized
for the execution of SAP BW/4HANA.
For more information about general modeling for SAP HANA-optimized Business Content, see SAP BW/4HANA
Content Add-On [page 7]
Note
You should only use the objects displayed in the data flow.
Prerequisites
Before you can use the SAP-HANA-optimized business content, you must define the source system ID.
Features
Billed and extrapolated documents from consumption billing are extracted from SAP S/4HANA Utilities to SAP
BW/4HANA and made available for subsequent evaluation. The InfoArea Sales Statistics contains SAP HANA-
optimized business content for evaluating these documents. You can also use revenues, consumption values, the
Data Flow
/IMO/D_UCSA01
This DataStore object (advanced) allows you to evaluate quantities and amounts, which originate from billing
utilities contracts. It only contains basic key figures, such as Quantity, Amount, Tax Amount. Other characteristics
such as Statistic Groups and Subtransaction can be used to create restricted key figures, such as discount,
Sources
This DataStore object is filled by the InfoSource UCSA: Sales Statistics (0UC_SALES_STATS_02) ( /IMO/
UCSA_IS01).
Transformation
Field Routines
All key figures are updated using the aggregation behavior "Summation”.
Delta Update
Data Modeling
Requires
/IMO/D_UCSA02
This DataStore object (advanced) allows you to evaluate extrapolated quantities and amounts, which originate
from the mass extrapolation of utilities contracts in SAP Utilities. It only contains basic key figures, such as
Quantity, Amount, Tax Amount. Other characteristics such as Statistic Groups and Subtransaction can be used to
create restricted key figures, such as discount, consumption, demand. This DataStore object (advanced) is used
as the basis for using Composite Providers to convert unbilled revenue reporting. The unbilled revenue reporting
can only be viewed as a possible evaluation form of extrapolated data.
Sources
This DataStore object is filled by the InfoSource UCSA: Mass Simulation for Billing (0UC_SALES_IMU_01) ( /IMO/
UCSA_IS02).
Note
The ADSO is updated using the InfoSource /IMO/UCSA_IS02. The InfoObjects Business Partner, Contract
Number and Key Date for Simulation Run are not allocated to a transformation rule here. This is because the
associated fields in the DataSource in the source system have been hidden for performance reasons. If you
need to update these objects, you must display these fields in the DataSource.
Transformation
Field Routines
All key figures are updated using the aggregation behavior “Summation”.
Data Modeling
Requires
/IMO/CMUCSA02
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Mass
Simulation for Billing (0UC_SALES_SIMU_01).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
/IMO/CMUCSA01
This DataStore object (advanced) is used as the corporate memory aDSO for the DataSource IS-U Sales Statistics
(delta created by mass activity) (0UC_SALES_STATS_02).
Das Corporate Memory is filled independently of the EDW Core Layer update. The Corporate Memory contains the
entire history for the data loaded and is used to perform a restructure without having to access the sources again.
All Corporate Memory DSOs provided from SAP HANA-optimized Business Content are created using the
template Corporate Memory Without Compression for DataStore objects (advanced) as a default setting. They are
field-based and contain all available BW DataSource fields. The modeling property Inbound table as extended table
has been activated. If you are using SAP IQ as extended storage for your SAP BW system, this means that the
data persistence for this Corporate Memory DSO is hard drive-based and not main memory-base. You should only
use the transformations that connect the Corporate Memory and the SAP HANA-optimized Business Content
InfoSources for the restructure.
6.3.2 InfoSources
/IMO/UCSA_IS01
This InfoSource supplies the data that originates from billing utilities contracts (sales statistics) for the EDW core
layer.
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
/IMO/UCSA_IS01
Requires
/IMO/UCSA_IS02
This InfoSource supplies the data that originates from mass extrapolation of utilities contracts (sales statistics) for
the EDW core layer.
Transformation
The InfoObjects Business Partner, Contract Number and Key Date for Simulation Run are not allocated to a
transformation rule here. This is because the associated fields in the DataSource in the source system have been
All fields (with the exception of the following transformation) are allocated directly to InfoObjects:
Source system for R/3 entity OGN_R3_SSY A two-digit logical backend system
(based on LOGSYS) is entered here.
Data Modeling
/IMO/UCSA_IS02
Requires
6.3.3 CompositeProvider
You can use this Composite Provider to evaluate actual amounts with extrapolated quantities and amounts, which
originate from the mass extrapolation of utilities contracts in SAP Utilities. The characteristics and key figures are
almost exactly the same and originate from the DataStore objects (advanced) Simulated Billings and Sales
Statistics (Basic Key Figures). You can differentiate between extrapolated data and actual data using the
characteristics Simulation ID and Invoice Date, since these are only available in one of the two DataStore objects
(advanced).
Data Modeling
InfoProvider
DataStore Object (Advanced) UCSA: Sales Statistics (Basic Key Fig /IMO/D_UCSA01
ures)
InfoObjects
InfoObject BAS: City district code for city and street 0CITYP_CODE
file
InfoObject BAS: City code for city and street file 0CITYP_CODE
InfoObject BAS: Street code for city and street file 0STREET_COD
6.3.4 Queries
/IMO/V_UCSA01_Q0001
You can use this query to determine the unbilled revenue reporting for a specific year. In the mass simulation for
SAP Utilities, you must first extrapolate the contracts that have not yet been billed and load the values to the
Caution
Note that the analysis period must lie within the simulation period.
You can make the corresponding posting in the general ledger on the basis of the results provided by this query.
You can restrict the selection using the company code. To determine the postings, you compare the revenues from
the selected consumption period from this query with the revenues for the same period from a different query for
the sales statistics.
Note
When you call the query, you should only select posting-relevant data from the data basis as some data is
statistically-relevant but not relevant to posting. However, these statistical data records are not required for
unbilled revenue reporting and may distort the results.
For more Information about unbilled revenue reporting, see SAP Help Portal at https://help.sap.com .
Data Modeling
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Variables
Object Type Name Technical Name
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
IMOV_UCSA01_Q0001
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Plant Maintenance.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
The plant maintenance data is extracted from the ERP system to the Business Warehouse and made available
there for further evaluation of the plant maintenance process.
It allows you to perform analysis of plant maintenance data with regards to plant maintenance orders, notifications
including causes, activities and tasks, maintenance costs, measurement readings, vehicle consumption data,
equipment dismantling at functional locations, work center capacity, maintenance schedules.
SAP delivers sample analytic queries on top of CompositeProviders for the following areas:
● Measurement Results
● Work Center Capacity and Availability
● Equipment Dismantling
● Vehicle Fuel Consumption
● Maintenance Orders: Costs with Asset Utilization
● Scheduling Overview and Planned Order
● Status of Plant Maintenance Orders
● Object Status in Plant Maintenance
● Notifications (including Items, Causes, Tasks and Activities)
● Maintenance Orders and Operations
7.1.1 Prerequisites
Before using SAP HANA-optimized Business Content for Plant Maintenance, you need to make the following
configuration settings:
For more information, see SAP BW/4HANA Content Add-On [page 7].
Context
Before you load data of Plant Maintenance records into SAP BW/4HANA, you have to transfer currency codes,
units of measure, and fiscal year variants from your SAP source system to your SAP BW/4HANA system.
Procedure
Next Steps
Context
Before you can use data flows on top of BW DataSources 0PM_MCOST_ASSET_UTIL and 0PM_SCH_PLND_ORDER,
you need to turn on the Business Function “EAM: Continuous Improvements” (LOG_EAM_CI_3) in the SAP source
system.
For detailed information about the Business Function “EAM: Continuous Improvements” (LOG_EAM_CI_3), go to
the SAP ERP documentation on the SAP Help Portal at https://help.sap.com/viewer/p/SAP_ERP and search for
EAM: Continuous Improvements.
For more information about activating Business Functions, go to the SAP NetWeaver 7.5 documentation on the
SAP Help Portal at https://help.sap.com/viewer/p/SAP_NETWEAVER_750 and search for Switching On Business
Functions.
Procedure
Context
You will need to activate the data extraction in the Logistics Customizing Cockpit if you want to use one of the data
sources in the LIS application component ’17: Plant Maintenance BW’.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node Logistics applications→ 17: Plant Maintenance→ BW Extract structures .
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures that you want
to use:
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246.
Before performing an initial upload of Plant Maintenance records into SAP BW, you have to perform a
reconstruction. The reconstruction writes the documents to be initially extracted to setup tables.
Procedure
1. In your SAP ERP system, call transaction OLI3BW (Reconstruct BW Structures in Plant Maintenance).
2. You can run the setup for Notifications (Event I0) or Orders (Event I3) separately or together. After changing
the document number selection (optional) and Control Reconstruction Run (mandatory), run the
reconstruction.
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application 17.
Recommendation
Before performing a new setup, run this transaction LBWG for application ‘17’.
Note
Completing setup tables is a critical action that should be carried out with caution. It might, for example, be
necessary to lock the system. For large volumes of data, the setup can take longer than one night and may have
to be done at the weekend.
More Information
For more information, see SAP Customizing Implementation Guide (IMG) → SAP Customer Implementation Guide →
Integration with Other SAP Components → Data Transfer to Business Warehouse → Settings for Application-Specific
Data Sources (PI) → Logistics → Managing Extract Structures → Initialization.
This DSO (advanced) contains the replicated measurement reading data for measuring points on measurement
document level.
Sources
This DSO is filled by the InfoSource PM: Measuring Points & Measurement Docs (0PM_MEASUREMENT) (technical
name: /IMO/PM_IS01).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Target Value for Measuring Point in 0DESIREU Target value quantity in SI unit is con
Document Entry Unit verted into document entry unit.
Lower Meas. Limit or Min. Total Counter 0MRMINEU Lower limit or minimum total counter
Reading Document UoM reading in SI unit is converted into docu
ment entry unit.
Upper Meas. Limit or Max. Total Counter 0MRMAXEU Upper limit or maximum total counter
Reading Document UoM reading in SI unit is converted into docu
ment entry unit.
Counter Reading in Document Entry Unit 0CNTRREU Counter reading in SI unit is converted
into document entry unit.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DSO (advanced) contains the replicated status history for plant maintenance orders.
Sources
This DSO is filled by the InfoSource PM: Order Status (0PM_ORDER_STATUS) (technical name: /IMO/PM_IS02).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
● Delta update: NEWE: Only New Records (Inserts) Via Extractor (Cube-Compatible)
● DataSource: 0PM_ORDER_STATUS
Data Modeling
Requires
Sources
This DSO is filled by the InfoSource PM: Object Status (0PM_OBJ_STATUS) (technical name: /IMO/PM_IS03).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: NEWE: Only New Records (Inserts) Via Extractor (Cube-Compatible)
● DataSource: 0PM_OBJ_STATUS
Data Modeling
Requires
This DSO (advanced) contains the replicated data about capacity and availability of work centers.
Sources
This DSO is filled by the InfoSource PM: Work Center Capacity (0PM_WCCP) (technical name: /IMO/PM_IS04).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
This DSO (advanced) contains the replicated data about the number of dismantled pieces of equipment for a
functional locations and installation duration.
Sources
This DSO is filled by the InfoSource PM: Equipment Dismantling (0PM_DSMNTL) (technical name: /IMO/
PM_IS05).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
This DSO (advanced) contains the replicated fleet data with vehicle usage and fuel consumption.
Note
The DSO (advanced) is designed for a monthly extract of fleet data (standard). If your fleet data is provided on a
different granularity (daily, weekly), you will need to adjust this DSO (advanced) accordingly.
Sources
This DSO is filled by the InfoSource PM: Fleet (0PM_FLEET) (technical name: /IMO/PM_IS06).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
PM: Fleet
Requires
This DSO (advanced) contains the replicated data about order costs and asset utilization. The asset utilization is
captured based on measurement readings for up to two preselected measuring points.
Note
NOTE! The data source only returns values when you have entered a single value selection for field POINT1
(Measuring Point 1). Hence a DTP filter needs to be defined for field POINT1 when loading data into SAP BW/
4HANA.
Sources
This DSO is filled by the InfoSource PM: Order Costs and Asset Utilization (0PM_MCOST_ASSET_UTIL) (technical
name: /IMO/PM_IS07).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
● Amount (0AMOUNT)
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
This DSO (advanced) contains the replicated data about scheduled preventive maintenance tasks and planned
maintenance orders.
Sources
This DSO is filled by the InfoSource Schedule Overview and Planned Order (0PM_SCH_PLND_ORDER) (technical
name: /IMO/PM_IS08).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
Data Modeling
Requires
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource PM: Maintenance Notifications (2LIS_17_I0NOTIF) (technical name: /IMO/
PM_IS11).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Lead time of the notification 0NOTIF_PROC Inverted value for reversed or deleted
data records.
Number of tasks with status 'outstan 0TASK_OUTST Inverted value for reversed or deleted
ding' or 'released' data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
No. of notifications with status outstand 0NOTIFOUTST Inverted value for reversed or deleted
ing data records.
Update Date 0UPD_DATE Filled with system date during the data
load
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I0NOTIF
Data Modeling
Requires
This DSO (advanced) contains replicated data of defect or damaged items in maintenance notifications.
Note
If you require to report on notification items with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource PM: Maintenance Notification - Items (2LIS_17_I0ITEM) (technical
name: /IMO/PM_IS12).
Transformation
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I0ITEM
Data Modeling
Requires
This DSO (advanced) contains replicated data of causes of defect or damaged items in maintenance notifications.
Note
If you require to report on notification causes with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource Maintenance Notification - Causes (2LIS_17_I0CAUSE) (technical name: /IMO/
PM_IS13).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I0CAUSE
Data Modeling
Requires
This DSO (advanced) contains replicated data for activities in maintenance notifications. This is independent of
whether the activities affect the whole notification or one notification item.
Note
If you require to report on notification activities with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource PM: Maintenance Notification - Activities (2LIS_17_I0ACTY) (technical
name: /IMO/PM_IS14).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I0ACTY
Data Modeling
Requires
This DSO (advanced) contains replicated data for tasks in maintenance notifications. This is independent of
whether the tasks affect the whole notification or one notification item.
Note
If you require to report on notification items with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource PM: Maintenance Notification - Tasks (2LIS_17_I0TASK) (technical
name: /IMO/PM_IS15).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records
Number of tasks with status 'outstan 0TASK_OUTST Inverted value for reversed or deleted
ding' or 'released' data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I0TASK
Data Modeling
Requires
Note
For information about the key figures provided by DataSource 2LIS_17_I3HDR, please see SAP Note 523450.
This DSO is filled by the InfoSource PM: Maintenance Orders (2LIS_17_I3HDR) (technical name: /IMO/PM_IS16).
Transformation
Field Routines
Number of Orders with Status "Com 0ORD_CLOSED Inverted value for reversed or deleted
pleted" data records.
Number of Orders with Status "Not Exe 0ORD_NOT Inverted value for reversed or deleted
cuted" data records.
Number of Orders with Status "Out 0ORD_OPEN Inverted value for reversed or deleted
standing" data records.
Number of Orders to Be Executed Imme 0ORD_IMMED Inverted value for reversed or deleted
diately data records.
Number of Orders Completed on Sched 0ORD_INTIME Inverted value for reversed or deleted
ule data records.
Lead Time for Order in Calendar Days 0ORD_PROCCD Inverted value for reversed or deleted
data records.
Lead Time for Order in Workdays 0ORD_PROCWD Inverted value for reversed or deleted
data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I3HDR
Data Modeling
This DSO (advanced) contains replicated operations data for maintenance orders including information about the
planned and the actual work.
Sources
This DSO is filled by the InfoSource PM: Maintenance Order - Operations (2LIS_17_I3OPER) (technical
name: /IMO/PM_IS17).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_17_I3OPER
Data Modeling
Requires
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource PM Order Status
(0PM_ORDER_STATUS).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Maintenance
Notifications (2LIS_17_I0NOTIF).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Maintenance
Notifications - Causes (2LIS_17_I0CAUSE).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Maintenance
Notifications - Tasks (2LIS_17_I0TASK).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Plant Maintenance
Order Process (2LIS_17_I3OPER).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property SAP HANA Dynamic Tiering has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
7.1.3 InfoSources
This InfoSource contains the structure to provide measurement reading data for measuring points on
measurement document level into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide maintenance order status into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about plant maintenance object status into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about work center capacity and availability in Plant
Maintenance and Production Planning into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about equipment dismantling at functional locations into
the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about order costs and asset utilization into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about scheduling overview and planned orders into the
EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide maintenance notification data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide item data of maintenance notifications into the EDW Core Layer
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about causes for maintenance notifications into the EDW
Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about activities for maintenance notifications into the EDW
Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about tasks for maintenance notifications into the EDW
Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provides maintenance order data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide movement data for maintenance order operations into the EDW
Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
7.1.4 CompositeProvider
Definition
This CompositeProvider contains transaction data from measuring point respectively counter readings on
measurement document level. You can use this CompositeProvider e.g. to gain insight into the utilization of an
equipment or functional location by analyzing total counter readings and comparing it with the target values or to
monitor discontinuous readings of measuring points e.g. temperature against the tolerance values (maximum/
minimum).
Beside a sample query, the CompositeProvider offers a rich set of characteristics and key figures that you can use
to implement your own customer queries.
Query Design Considerations
When creating your own queries on this CompositeProvider, you will need to decide if measurement documents
with a deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted
from Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains status history information for plant maintenance orders.
Data Modeling
Definition
This CompositeProvider contains status history information for plant maintenance objects.
Data Modeling
Definition
This CompositeProvider contains data about capacity and availability of work centers.
Data Modeling
Definition
This CompositeProvider contains data about the dismantled pieces of equipment for a functional location and
installation duration.
Data Modeling
Definition
This CompositeProvider contains fleet data and can be used to track distance traveled, total and average fuel
consumption and fuel costs.
When creating your own queries on this Composite Provider, keep in mind that the result set should be uniquely
defined based on the following characteristics either by adding them into the rows or columns of the analytical
query or by providing selections or filters:
Data Modeling
Definition
This CompositeProvider contains data about maintenance order costs in comparison to asset utilization. The
asset utilization is captured based on measuring reading or counter readings for up to two measuring points that
are preselected during the data upload.
Actual External Procurement /IMO/V_PM06_CK0001 Amount with Value Type “4” (Actuals)
and PM Costs Value Category “415”
Actual Internal Activities /IMO/V_PM07_RK0002 Amount with Value Type “4” (Actuals)
and PM Costs Value Category “600”
Actual Warehouse Issue /IMO/V_PM07_RK0003 Amount with Value Type “4” (Actuals)
and PM Costs Value Category “400”
Total Actual Cost /IMO/V_PM07_RK0004 Amount with Value Type “4” (Actuals)
Plan External Procurement /IMO/V_PM07_RK0005 Amount with Value Type “1” (Plan) and
PM Costs Value Category “415”
Plan Internal Activities /IMO/V_PM07_RK0006 Amount with Value Type “1” (Plan) and
PM Costs Value Category “600”
Plan Warehouse Issue /IMO/V_PM07_RK0007 Amount with Value Type “1” (Plan) and
PM Costs Value Category “400”
Total Plan Cost /IMO/V_PM07_RK0008 Amount with Value Type “1” (Plan)
Data Modeling
Definition
This CompositeProvider contains data about scheduled preventive maintenance tasks and planned maintenance
orders.
Data Modeling
Definition
If you want to provide combined reporting across plant maintenance and customer service notifications, you may
consider to implement a composite provider as an union of the two Composite Provider PM: Maintenance
Notifications /IMO/V_PM11 and CS: Service Notifications /IMO/V_CS11.
Data Modeling
Definition
This CompositeProvider contains data for defect or damaged items captured by maintenance notifications.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for the causes of defect or damaged items in maintenance notifications.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
If you want to provide combined reporting across plant maintenance and customer service notification causes, you
may consider to implement a composite provider as an union of the two Composite Provider PM: Maintenance
Notifications - Causes /IMO/V_PM13 and CS: Service Notifications - Causes /IMO/V_CS13.
Data Modeling
Definition
This CompositeProvider contains data for activities in maintenance notifications. This is independent of whether
the activities affect the whole notification or one notification item.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
If you want to provide combined reporting across plant maintenance and customer service notification activities,
you may consider to implement a composite provider as an union of the two Composite Provider PM: Maintenance
Notifications - Activities /IMO/V_PM14 and CS: Service Notifications - Activities /IMO/V_CS14.
Data Modeling
Definition
This CompositeProvider contains data for tasks in maintenance notifications. This is independent of whether the
tasks affect the whole notification or one notification item.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for maintenance orders including key metrics such as lead time of the order
in workdays determined by the factory calendar in OLTP system, and number of orders by different status, e.g.
“completed” / “not performed” / “outstanding” / “planned” / “to be executed immediately” / “completed on
time”.
Note
For information about the key figures, please see SAP Note 523450 and SAP Note 2159342.
If you want to provide combined reporting across plant maintenance and customer service orders, you may
consider to implement a composite provider as an union of the two Composite Provider PM: Maintenance
Orders /IMO/V_PM16 and CS: Service Orders /IMO/V_CS16.
Data Modeling
Definition
This CompositeProvider contains operations data for maintenance orders and can be used to report on planned
and actual work based on several maintenance order characteristics.
If you want to provide combined reporting across plant maintenance and customer service order operations, you
may consider to implement a composite provider as an union of the two Composite Provider PM: Maintenance
Order - Operations /IMO/V_PM17 and CS: Service Order - Operations /IMO/V_CS17.
If you want to report on a comprehensive maintenance schedule including preventive maintenance tasks and
planned maintenance order operations, consider to use the Composite Provider PM: Scheduling Overview &
Planned Orders /IMO/V_PM08.
Data Modeling
7.1.5 Queries
You can use this query to display measurement results for the past 14 days at the equipment or functional location
level. It shows both, readings for measuring counters (e.g. odometer) and discontinuous readings for measuring
points (e.g. temperature).
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CNTIND = ‚#‘
0CNTIND = ‚X‘
0CNTIND = ‚X‘
Key Figure Target Value for Measuring 0DESIREU Measuring point is a counter
Point
0CNTIND = ‚X‘
You can use this query to display current status and historical status changes for plant maintenance orders.
This query is based on the PM: Order Status History (/IMO/V_PM02) CompositeProvider
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Variable 0CEIO_CDL14CDCY
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
You can use this query to display current status and historical status changes for plant maintenance objects.
This query is based on the PM: Object Status History (/IMO/V_PM03) CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
You can use this query to track work center capacity and availability. Grouped by the work center category and
work center it shows number of capacities, operating time and compares the available capacity with the
operational capacity.
This query is based on the PM: Work Center Capacity and Availability (/IMO/V_PM04) CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Optional
Selection option
Optional
Selection option
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Key Figure Capacity Lost 0PM_CAPLOST Key Figure Hidden, can be dis
played
You can use this query to report on the number of dismantled pieces of equipment for a functional location and
average installation of equipment.
This query is based on the PM: Equipment Dismantling at Functional Locations (/IMO/V_PM05)
CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Optional
Selection option
Optional
Selection option
Optional
Interval
Optional
Interval
Optional
Interval
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
You can use this query to report on the distance covered, fuel consumption and fuel costs of your fleet. You can
aggregate the results based on a rich set of characteristics such as manufacturer, model, construction year, fuel
type and / or calendar month.
This query is based on the PM: Fleet – Vehicle Consumption (/IMO/V_PM06) CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
You can use this query to compare maintenance order costs with the asset utilization. This allows maintenance
planner to understand how the utilization is linked to maintenance cost of a maintenance object.
This query is based on the PM: Order Costs and Asset Utilization (/IMO/V_PM07) CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0FUNCT_LOC
Characteristic Functional Location —
0EQUIPMENT
Characteristic Equipment Number —
0COORD_TYPE
Characteristic Order Type —
0PM_MEASP1
Characteristic Measurement Point ID1 —
0PM_MEASP2
Characteristic Measurement Point ID2 —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/IMO/V_PM07_RK0008
Key Figure Total Planned Cost —
/IMO/V_PM07_RK0007
Key Figure Plan Warehouse Issue —
/IMO/V_PM07_RK0005
Key Figure Plan External Procurement —
/IMO/V_PM07_RK0006
Key Figure Plan Internal Activities —
/IMO/V_PM07_RK0004
Key Figure Total Actual Cost —
/IMO/V_PM07_RK0003
Key Figure Actual Warehouse Issue —
/IMO/V_PM07_RK0001
Key Figure Actual External Procurement —
/IMO/V_PM07_RK0002
Key Figure Actual Internal Activities —
0READSI1
Key Figure Utilization MPoint 1 —
/IMO/V_PM07_CK0001
Key Figure Cost/Util MPoint 1 —
0READSI2
Key Figure Utilization MPoint 2 —
/IMO/V_PM07_CK0002
Key Figure Cost/Util MPoint 2 —
● All scheduled preventive maintenance tasks that may be required in term of calls.
● All breakdowns and planned maintenance orders.
Viewing them together is essential for maintenance planner. This will enable them to decide if some of the
preventive maintenance calls that are not required can be skipped without any impact of compliance.
This query is based on the PM: Scheduling Overview & Planned Orders (/IMO/V_PM08) CompositeProvider.
Structure
Filters
Object Type Name Technical Name Value Restriction / Calcula
tion
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0PLANPLANT
Characteristic Maintenance Planning Plant —
0PMPLANGRP
Characteristic Maintenance planner group —
0WORKCENTER
Characteristic Work Center/Resource —
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0ORDERSTAT
Characteristic Order Status —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
/I0OPR_PLDWRK
Key Figure Planned Work for Operation —
You can use this query to obtain information about the number of notifications, breakdowns and tasks for
technical objects.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0EQUIPMENT
Characteristic Equipment —
Columns
Object Type Name Technical Name
0CALDAY__0CALMONTH
Key Figure Calendar Year/Month
0OPR_PLDWRK
Key Figure Planned Work for Operation
0NOTIF_TOT
Key Figure Number of notifications
0NTF_INTIME
Key Figure Number of notifications completed on
schedule
0NOTIFOUTST
Key Figure No. of notifications with status outstand
ing
/IMO/V_PM11_RK0001
Key Figure Number of Breakdowns
0TASK_TOT
Key Figure Number of Tasks
0TASK_SUCC
Key Figure No. of tasks with status successful
0TASK_OUTST
Key Figure Number of tasks with status 'outstan
ding' or 'released'
You can use this query to display the damage codes used and how often they occur for maintenance notifications.
This query is based on the PM: Maintenance Notification Items (/IMO/V_PM12) CompositeProvider.
Structure
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_FE
Characteristic Catalog type – Problems —
0CATGRP_FE
Characteristic Code group – Problems —
0CATCODE_FE
Characteristic Code – Problems —
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
You can use this query to get information about problem causes for maintenance notifications and how often they
occur.
This query is based on the PM: Maintenance Notification - Causes (/IMO/V_PM13) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_CSE
Characteristic Catalog type – Cause —
0CATGRP_CSE
Characteristic Code group – Cause —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
You can use this query to get information about activities for maintenance notifications and how often they occur.
This query is based on the PM: Maintenance Notification - Activities (/IMO/V_PM14) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_ACT
Characteristic Catalog type – Activity —
0CATGRP_ACT
Characteristic Code group – Activity —
0CATCODE_ACT
Characteristic Code – Activity —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0ACTVTY_CNT
Key Figure Number of activities —
You can use this query to get information about number and status of tasks for maintenance notifications.
This query is based on the PM: Maintenance Notification - Tasks (/IMO/V_PM15) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
0CALDAY__0CALWEEK
Characteristic Calendar Year/Week
0CALDAY
Characteristic Notification Date
0NOTIFICATN
Characteristic Message Number
0FLGDELETED
Characteristic Indicator: Object Deleted from Source
System
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_TSK
Characteristic Catalog type – Task —
0CATGRP_TSK
Characteristic Code group – Task —
0CATCODE_TSK
Characteristic Code – Task —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
You can use this query to display the number of maintenance orders and their average lead time. You can break
down this information e.g. by technical object and maintenance activity type.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0PLANPLANT
Characteristic Maintenance Planning Plant —
0PMPLANGRP
Characteristic Maintenance Planner Group —
0PM_ORDER__0WORKCENTER
Characteristic Work Center/Resource —
0PM_ORDER__0PMACTTYPE
Characteristic Maintenance Activity Type —
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0ORDER_TOT
Key Figure Number of Orders —
0ORD_IMMED
Key Figure Number of Orders to Be Exe —
cuted Immediately
0ORD_OPEN
Key Figure Number of Orders with Status —
"Outstanding"
0ORD_NOT
Key Figure Number of Orders with Status —
"Not Executed"
0ORD_INTIME
Key Figure Number of Orders Completed —
on Schedule
0ORD_CLOSED
Key Figure Number of Orders with Status —
"Completed"
0ORD_PLND
Key Figure Number of Planned Orders —
Formula Net Average Lead Time Lead Time for Order in Work
days 0ORD_PROCWD
divided by
Number of Orders
0ORDER_TOT
Key Figure Lead Time for Order in Work 0ORD_PROCWD Hidden (can be shown)
days
This query provides an overview of the planned and actual labor for maintenance orders. You can break down this
information e.g. by individual work center and maintenance activity type.
This query is based on the PM: Maintenance Order Operations (/IMO/V_PM17) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0PLANT
Characteristic Plant —
0WORKCENTER
Characteristic Work Center/Recource —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALMONTH
Characteristic Calendar Year/Month —
0OPR_ACTWRK
Key Figure Actual Work for Operation —
0OPR_PLDWRK
Key Figure Planned Work for Operation —
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Customer Service.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modelling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
It allows you to perform analysis of customer service data with regards to service orders and notifications
including causes, activities and tasks. .
SAP delivers sample analytic queries on top of CompositeProviders for the following areas:
7.2.1 Prerequisites
Before using SAP HANA-optimized Business Content for Customer Service, you need to make the following
configuration settings:
For more information, see SAP BW/4HANA Content Add-On [page 7].
Context
Before you load data of Customer Services records into SAP BW/4HANA, you have to transfer currency codes,
units of measure, and fiscal year variants from your SAP source system to your SAP BW/4HANA system.
Procedure
Next Steps
Context
You will need to activate the data extraction in the Logistics Customizing Cockpit if you want to use one of the data
sources in the LIS application component ’18: Customer Service BW’.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node → Logistics applications → 18: Customer Service BW → Extract structures.
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures that you want
to use:
○ MC18I00NTF: CS-BW Extraction: Notification Activity for DataSource 2LIS_18_I0NOTIF
○ MC18I00ITM: CS-BW Extraction: Notification Item for DataSource 2LIS_18_I0ITEM
○ MC18I00CSE: CS-BW Extraction: Notification Cause for DataSource 2LIS_18_I0CAUSE
○ MC18I00ACT: CS-BW Extraction: Notification Activity for DataSource 2LIS_18_I0ACTY
○ MC18I00TSK: CS-BW Extraction: Notification Task for DataSource 2LIS_18_I0TASK
○ MC18I30HDR: CS-BW Extraction: Order for DataSource 2LIS_18_I3HDR
○ MC18I30OPR: Extraction CS-BW: Order Process for DataSource 2LIS_18_I3OPER
4. Select the required Update Mode.
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246.
Context
Before performing an initial upload of Customer Service records into SAP BW, you have to perform a
reconstruction. The reconstruction writes the documents to be initially extracted to setup tables.
1. In your SAP ERP system, call transaction OLISBW (Reconstruction of BW Structures in Customer Service).
2. You can run the setup for Notifications (Event I0) or Orders (Event I3) separately or together. After changing
the document number selection (optional) and Control Reconstruction Run (mandatory), run the
reconstruction.
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application 18.
Recommendation
Before performing a new setup, run this transaction LBWG for application ‘18’.
Completing setup tables is a critical action that should be carried out with caution. It might, for example, be
necessary to lock the system. For large volumes of data, the setup can take longer than one night and may
have to be done at the weekend.
For more information, see SAP Customizing Implementation Guide (IMG) → SAP Customer Implementation
Guide → Integration with Other SAP Components → Data Transfer to Business Warehouse → Settings for
Application-Specific Data Sources (PI) → Logistics → Managing Extract Structures → Initialization .
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource CS: Service Notifications (2LIS_18_I0NOTIF) (technical name:
2LIS_18_I0NOTIF).
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Lead time of the notification 0NOTIF_PROC Inverted value for reversed or deleted
data records.
Number of tasks with status 'outstan 0TASK_OUTST Inverted value for reversed or deleted
ding' or 'released' data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
No. of notifications with status outstand 0NOTIFOUTST Inverted value for reversed or deleted
ing data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I0NOTIF
Data Modeling
This DSO (advanced) contains replicated data of defect or damaged items in service notifications.
Note
If you require to report on notification items with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource CS: Service Notification - Items (2LIS_18_I0ITEM) (technical name: /IMO/
CS_IS12).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I0ITEM
Data Modeling
Requires
This DSO (advanced) contains replicated data of causes of defect or damaged items in service notifications.
Note
If you require to report on notification causes with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource CS: Service Notification - Causes (2LIS_18_I0CAUSE) (technical name: /IMO/
CS_IS13).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I0CAUSE
Data Modeling
Requires
This DSO (advanced) contains replicated data for activities in service notifications. This is independent of whether
the activities affect the whole notification or one notification item.
Sources
This DSO is filled by the InfoSource CS: Service Notification - Activities (2LIS_18_I0ACTY (technical name: /IMO/
CS_IS14).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I0ACTY
Data Modeling
Requires
This DSO (advanced) contains replicated data for tasks in service notifications. This is independent of whether the
tasks affect the whole notification or one notification item.
Note
If you require to report on notification items with “Deletion Flag” status, please see SAP Note 866246.
Sources
This DSO is filled by the InfoSource CS: Service Notification - Tasks (2LIS_18_I0TASK) (technical name: /IMO/
CS_IS15).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Number of tasks with status 'outstan 0TASK_OUTST Inverted value for reversed or deleted
ding' or 'released' data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I0TASK
Data Modeling
Note
For information about the key figures provided by DataSource 2LIS_18_I3HDR, please see SAP Note 523450.
Sources
This DSO is filled by the InfoSource CS: Service Orders (2LIS_18_I3HDR) (technical name: /IMO/CS_IS16).
Transformation
Field Routines
Lead Time for Order in Calendar Days 0ORD_PROCCD Inverted value for reversed or deleted
data records.
Lead Time for Order in Workdays 0ORD_PROCWD Inverted value for reversed or deleted
data records.
Number of Orders with Status "Com 0ORD_CLOSED Inverted value for reversed or deleted
pleted" data records.
Number of Orders with Status "Not Exe 0ORD_NOT Inverted value for reversed or deleted
cuted" data records.
Number of Orders with Status "Out 0ORD_OPEN Inverted value for reversed or deleted
standing" data records.
Number of Orders to Be Executed Imme 0ORD_IMMED Inverted value for reversed or deleted
diately data records.
Number of Orders Completed on Sched 0ORD_INTIME Inverted value for reversed or deleted
ule data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I3HDR
Data Modeling
Requires
This DSO (advanced) contains replicated operations data for service orders including information about the
planned and the actual work.
Sources
This DSO is filled by the InfoSource CS: Service Order - Operations (2LIS_18_I3OPER) (technical name: /IMO/
CS_IS17).
Transformation
Field Routines
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_18_I3OPER
Data Modeling
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Notifications
(2LIS_18_I0NOTIF).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Notifications -
Items (2LIS_18_I0ITEM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Notifications -
Causes (2LIS_18_I0CAUSE).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Notifications -
Activities (2LIS_18_I0ACTY).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Notifications -
Tasks (2LIS_18_I0TASK).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Orders
(2LIS_18_I3HDR).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Service Order
operation (2LIS_18_I3OPER).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
7.2.3 InfoSources
This InfoSource contains the structure to provide service notification data into the EDW Core Layer.
Transformation
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide item data of service notifications into the EDW Core Layer
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about activities for service notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about tasks for service notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provides service order data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
This InfoSource contains the structure to provide movement data for service order operations into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
7.2.4 CompositeProvider
Definition
This CompositeProvider contains header data about service notifications including key metrics such as
notification lead time, downtime of a piece of equipment, number of notifications and number of tasks.
If you want to provide combined reporting across customer service notifications and plant maintenance, you may
consider to implement a composite provider as an union of the two Composite Provider CS: Service
Notifications /IMO/V_CS11 and PM: Maintenance Notifications /IMO/V_PM11.
Data Modeling
Definition
This CompositeProvider contains data for defect or damaged items captured by service notifications.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for the causes of defect or damaged items in service notifications.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
If you want to provide combined reporting across customer service notification causes and plant maintenance, you
may consider to implement a composite provider as an union of the two Composite Provider CS: Service
Notifications - Causes /IMO/V_CS13 and PM: Maintenance Notifications - Causes /IMO/V_PM13.
Data Modeling
Definition
This CompositeProvider contains data for activities in service notifications. This is independent of whether the
activities affect the whole notification or one notification item.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
If you want to provide combined reporting across customer service and plant maintenance notification activities,
you may consider to implement a composite provider as an union of the two Composite Provider CS: Service
Notifications - Activities /IMO/V_CS14 and PM: Maintenance Notifications - Activities /IMO/V_PM14.
Data Modeling
Definition
This CompositeProvider contains data for tasks in service notifications. This is independent of whether the tasks
affect the whole notification or one notification item.
If you want to provide combined reporting across customer service and plant maintenance notification tasks, you
may consider to implement a CompositeProvider as an union of the two CompositeProvider CS: Service
Notifications - Tasks /IMO/V_CS15 and PM: Maintenance Notifications - Tasks /IMO/V_PM15.
Data Modeling
Definition
This CompositeProvider contains data for service orders including key metrics such as lead time of the order in
workdays determined by the factory calendar in OLTP system, and number of orders by different status, e.g.
“completed” / “not performed” / “outstanding” / “planned” / “to be executed immediately” / “completed on
time”.
Note
For information about the key figures, please see SAP Note 523450 and SAP Note 2159342.
If you want to provide combined reporting across customer service orders and plant maintenance, you may
consider to implement a CompositeProvider as an union of the two CompositeProvider CS: Service Orders /IMO/
V_CS16 and PM: Maintenance Orders /IMO/V_PM16.
Data Modeling
Definition
This CompositeProvider contains operations data for service orders and can be used to report on planned and
actual work based on several service order characteristics.
If you want to provide combined reporting across customer service and plant maintenance order operations, you
may consider to implement a CompositeProvider as an union of the two CompositeProvider CS: Service Order -
Operations /IMO/V_CS17 and PM: Maintenance Order - Operations /IMO/V_PM17.
Data Modeling
7.2.5 Queries
You can use this query to obtain information about the number of notifications, breakdowns and tasks for
technical objects.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0EQUIPMENT
Characteristic Equipment —
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0NOTIF_TOT
Key Figure Number of notifications —
0TASK_TOT
Key Figure Number of Tasks —
You can use this query to display the damage codes used and how often they occur for service notifications.
This query is based on the CS: Service Notification Items (/IMO/V_CS12) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CUSTOMER
Characteristic Cust. No. —
0NOTIFICATN__0PLANT
Characteristic Plant —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_FE
Characteristic Catalog type – Problems —
0CATGRP_FE
Characteristic Code group – Problems —
0CATCODE_FE
Characteristic Code – Problems —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0PROBL_FREQ
Key Figure Problem frequency —
You can use this query to get information about problem causes for service notifications and how often they occur.
This query is based on the CS: Service Notification - Causes (/IMO/V_CS13) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
0CUSTOMER
Characteristic Cust. No. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_CSE
Characteristic Catalog type – Cause —
0CATGRP_CSE
Characteristic Code group – Cause —
0CATCODE_CSE
Characteristic Code – Cause —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0CAUSE_CNT
Key Figure Number of causes —
You can use this query to get information about activities for service notifications and how often they occur.
This query is based on the CS: Service Notification - Activities (/IMO/V_PM14) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
0CUSTOMER
Characteristic Cust. No. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_ACT
Characteristic Catalog type – Activity —
0CATGRP_ACT
Characteristic Code group – Activity —
0CATCODE_ACT
Characteristic Code – Activity —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0ACTVTY_CNT
Key Figure Number of activities —
You can use this query to get information about number and status of tasks for service notifications.
This query is based on the CS: Service Notification - Tasks (/IMO/V_CS15) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Characteristic
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CUSTOMER
Characteristic Cust. No. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_TSK
Characteristic Catalog type – Task —
0CATGRP_TSK
Characteristic Code group – Task —
0CATCODE_TSK
Characteristic Code – Task —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month —
0TASK_OUTST
Key Figure Number of tasks with status —
'outstanding' or 'released'
0TASK_TOT
Key Figure Number of Tasks —
0TASK_SUCC
Key Figure No. of tasks with status suc —
cessful
You can use this query to display the number of service orders and their average lead time. You can break down
this information e.g. by technical object and service activity type.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
0CALDAY
Characteristic Order Creation Date
0CS_ORDER
Characteristic Service Order
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CUSTOMER
Characteristic Cust. No. —
0PLANTPLANT
Characteristic Maintenance Planning Plant —
0PMPLANGRP
Characteristic Maintenance planner group —
0CS_ORDER_0WORKCENTER
Characteristic Work Center/Resource —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0ORDER_TOT
Key Figure Number of Orders —
0ORD_PLND
Key Figure Number of Planned Orders —
0ORD_UNPLND
Key Figure Number of Unplanned Orders —
0ORD_INTIME
Key Figure Number of Orders Completed —
on Schedule
0ORD_PROCCD
Key Figure Lead Time for Order in Calen —
dar Days
Key Figure Net Average Lead Time Lead Time for Order in Work
days 0ORD_PROCWD
divided by
Number of Orders
0ORDER_TOT
0ORD_PROCWD
Key Figure Lead Time for Order in Work Hidden (can be shown)
days
This query provides an overview of the planned and actual labor for service orders. You can break down this
information e.g. by individual work center and service activity type
This query is based on the CS: Service Order Operations (/IMO/V_CS17) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CUSTOMER
Characteristic Cust. No. —
0PLANT
Characteristic Plant —
0WORKCENTER
Characteristic Work Center/Recource —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALMONTH
Characteristic Calendar Year/Month —
0OPR_ACTWRK
Key Figure Actual Work for Operation —
0OPR_PLDWRK
Key Figure Planned Work for Operation —
This documentation describes the SAP HANA-optimized Business Content objects that you can use to analyze
data from SAP ERP Quality Management.
The data model follows the requirements for the layered scalable architecture LSA++, which is optimized for BW
running on SAP HANA.
For more information about general modeling patterns for SAP HANA-optimized Business Content, see SAP BW/
4HANA Content Add-On [page 7].
Prerequisites
Features
It allows you to perform analysis of Quality Management data with regard to notifications and inspections including
causes, activities, tasks, lots, and samples.
SAP delivers sample analytic queries on top of CompositeProviders for the following areas:
8.1 Prerequisites
Context
You will need to activate the data extraction in the Logistics Customizing Cockpit if you want to use one of the data
sources in the LIS application component ’05: Quality Management’.
Procedure
1. In your SAP ERP system, call transaction LBWE (Activate/Edit Extraction Structures).
2. Expand the hierarchy structure node → Logistics applications → 05: Quality Management → Extract structures.
3. In the Update column for extract structure BW, choose Inactive to activate the extract structures that you want
to use:
○ MC05Q00NTF: QM-BW Extraction: Notification for DataSource 2LIS_05_Q0NOTIF
○ MC05Q00ITM: QM-BW Extraction: Notification Item for DataSource 2LIS_05_Q0ITEM
○ MC05Q00CSE: Extraction QM-BW: Notification Cause for DataSource 2LIS_05_Q0CAUSE
○ MC05Q00ACT: Extraction QM-BW: Notification Activity for DataSource 2LIS_05_Q0ACTY
○ MC05Q00TSK: QM-BW Extraction: Notification Task for DataSource 2LIS_05_Q0TASK
4. Select the required Update Mode.
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Context
Before performing an initial upload of Quality Management records into SAP BW, you have to perform a
reconstruction. The reconstruction writes the documents to be initially extracted to setup tables.
Procedure
1. In your SAP ERP system, call transaction OLIQBW (Reconstruct of BW Structures for Quality Management).
As the setup tables are no longer needed after initialization and initial extraction into SAP BW/4HANA, you can
delete them by running transaction LBWG Delete the Contents of the Setup Tables for Application 05.
Recommendation
Before performing a new setup, run this transaction LBWG for application ‘05’.
Completing setup tables is a critical action that should be carried out with caution. It might, for example, be
necessary to lock the system. For large volumes of data, the setup can take longer than one night and may
have to be done at the weekend.
For more information, see SAP Customizing Implementation Guide (IMG) → SAP Customer Implementation
Guide → Integration with Other SAP Components → Data Transfer to Business Warehouse → Settings for
Application-Specific Data Sources (PI) → Logistics → Managing Extract Structures → Initialization .
Note
If you require to report on inspection results with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Inspection Results: General Data (2LIS_05_QE1) (technical name: /IMO/
QM_IS01).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Number of inspected and closed sam 0SAMPS_TOTL 0SAMPS_TOTL (Invert value if STORNO
ples is deletion)
Sample size (no. of valid values in sam 0SAMPS_SIZE 0SAMPS_SIZE (Invert value if STORNO
ple) is deletion)
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_QE1
Data Modeling
This DSO (advanced) contains replicated data of quantitative data in quality management.
Sources
This DSO is filled by the InfoSource QM: Inspection Results - Quantitative Data (2LIS_05_QE2) (technical
name: /IMO/QM_IS02).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Number of inspected and closed sam 0SAMPS_TOTL 0SAMPS_TOTL (Invert value if STORNO
ples is deletion)
Sample size (no. of valid values in sam 0SAMPS_SIZE 0SAMPS_SIZE (Invert value if STORNO
ple) is deletion)
Sum of squares if valid single values 0SUM_OF_SQ 0SUM_OF_SQ (Invert value if STORNO is
deletion)
Number of measured values above the 0NO_TOO_HGH 0NO_TOO_HGH (Invert value if STORNO
tolerance range is deletion)
Number of measured values below the 0NO_TOO_LOW 0NO_TOO_LOW (Invert value if STORNO
tolerance range is deletion)
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_QE2
Data Modeling
This DSO (advanced) contains replicated data of inspection lots in quality management.
Note
If you require to report on inspection lots with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Inspection Lots (2LIS_05_QVUDN) (technical name: /IMO/QM_IS03).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Quantity that was actually inspected 0INSP_QTY 0INSP_QTY (Invert value if STORNO is
deletion)
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_QVUDN
Data Modeling
Unit of measurement Base unit of measure for the sample unit 0SAMPLE_UOM
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Quality Notification (2LIS_05_Q0NOTIF) (technical name: /IMO/
QM_IS11).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Defective Quantity UoM (internal) 0DEFQTYINTU Inverted value for reversed or deleted
data records.
Defective Quantity UoM (external) 0DEFQTYEXTU Inverted value for reversed or deleted
data records.
Return Delivery Quantity UoM 0RETURNQTYU Inverted value for reversed or deleted
data records.
Lead time of the notification 0NOTIF_PROC Inverted value for reversed or deleted
data records.
Number of tasks with status ‘outstan 0TASK_OUTST Inverted value for reversed or deleted
ding’ or ‘released’ data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
No. of notifications with status outstand 0NOTIFOUTST Inverted value for reversed or deleted
ing data records.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_Q0NOTIF
Data Modeling
Requires
This DSO (advanced) contains replicated data of defect or damaged items in quality notifications.
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Quality Notification - Items (2LIS_05_Q0ITEM) (technical name: /IMO/
QM_IS12).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Defective Quantity UoM (internal) 0DEFQTYINTU Inverted value for reversed or deleted
data records.
Defective Quantity UoM (external) 0DEFQTYEXTU Inverted value for reversed or deleted
data records.
Delta Update
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_Q0ITEM
Data Modeling
Requires
This DSO (advanced) contains replicated data of causes of defect or damaged items in quality notifications.
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Quality Notification - Causes (2LIS_05_Q0CAUSE) (technical name: /IMO/
QM_IS13).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_Q0CAUSE
Data Modeling
Requires
This DSO (advanced) contains replicated data for activities in quality notifications. This is independent of whether
the activities affect the whole notification or one notification item.
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Quality Notification - Activities (2LIS_05_Q0ACTY (technical name: /IMO/
QM_IS14).
Transformation
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_Q0ACTY
Data Modeling
Requires
This DSO (advanced) contains replicated data for tasks in quality notifications. This is independent of whether the
tasks affect the whole notification or one notification item.
Note
If you require to report on notifications with “Deletion Flag” status, please see SAP Note 866246 .
Sources
This DSO is filled by the InfoSource QM: Quality Notification - Tasks (2LIS_05_Q0TASK) (technical name: /IMO/
QM_IS15).
Transformation
Field Routines
Indicator: Object Deleted from Source 0FLGDELETED Filled with “X” for reversed or deleted
System data records.
Update Date 0UPD_DATE Filled with system date during the data
load.
Number of tasks with status 'outstan 0TASK_OUTST Inverted value for reversed or deleted
ding' or 'released' data records.
No. of tasks with status successful 0TASK_SUCC Inverted value for reversed or deleted
data records.
Delta Update
The following delta update is supported for this DataStore object:
● Delta update: ABR: Complete Delta with Deletion Flag Via Delta Queue
● DataSource: 2LIS_05_Q0TASK
Data Modeling
Requires
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Inspection Result:
General Data (2LIS_05_QE1).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Inspection Results:
Quantitative Data (2LIS_05_QE2).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Inspection Lot/Usage
Decision (2LIS_05_QVUDN).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as an extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Quality Notifications
(2LIS_05_Q0NOTIF).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Quality Notifications -
Items (2LIS_05_Q0ITEM).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Quality Notifications -
Causes (2LIS_05_Q0CAUSE).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Quality Notifications -
Activities (2LIS_05_Q0ACTY).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system. .
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This DataStore object (advanced) serves as the corporate memory DSO for the DataSource Quality Notification -
Tasks (2LIS_05_Q0TASK).
Use
The corporate memory is filled independently of the EDW core layer’s update. It contains the complete history of
the loaded data. It is used as a source for reconstructions without the need to access the sources again.
By default, all corporate memory DSOs provided by the SAP HANA-optimized Business Content have been created
according to the DataStore object (advanced) template Corporate memory without compression. They are field-
based and contain all available BW DataSource fields.
The modeling property Inbound table as extended table has been turned on. This means the persistence of data for
this corporate memory DSO is hard-disk based and not main memory-based if you use SAP IQ as extended
storage for your SAP BW/4HANA system.
The delivered transformations connecting the corporate memory and the SAP HANA-optimized Business Content
InfoSources should only be used for reconstruction purposes.
This InfoSource contains the structure to provide general data of inspection results into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide quantitative data of inspection results into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide inspection data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
Unit of measurement Base unit of measure for the sample unit 0SAMPLE_UOM
This InfoSource contains the structure to provide quality notification data into the EDW Core Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data item information of quality notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about causes for quality notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about activities for quality notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
This InfoSource contains the structure to provide data about tasks for quality notifications into the EDW Core
Layer.
Transformation
Field Rules
Source System for R/3 Entity* 0GN_R3_SSY Filled with the 2-digit system ID of the
connected source system.
* For more information about source system IDs, see SAP BW/4HANA Content Add-On [page 7].
Data Modeling
Requires
8.4 CompositeProvider
Definition
Use
This CompositeProvider contains header data about inspection results including key metrics such as Number of
inspected and closed Samples, Number of defects found and number of Nonconforming Samples.
When creating your own queries on this CompositeProvider, you will need to decide if notifications with a deletion
indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from Source
System 0FLGDELETED).
Data Modeling
Definition
Use
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
Use
This CompositeProvider contains data of inspection lots and usage decisions for quality management.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains header data about service notifications including key metrics such as
notification lead time, downtime of a piece of equipment, number of notifications and number of tasks.
When creating your own queries on this CompositeProvider, you will need to decide if notifications with a deletion
indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from Source
System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for defect or damaged items captured by service notifications.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for the causes of defect or damaged items in service notifications.
Data Modeling
Definition
This CompositeProvider contains data for activities in quality notifications. This is independent of whether the
activities affect the whole notification or one notification item.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
Definition
This CompositeProvider contains data for tasks in quality notifications. This is independent of whether the tasks
affect the whole notification or one notification item.
When creating your own queries on this CompositeProvider, you will need to decide if notification items with a
deletion indicator should be included or excluded from the result set (InfoObject Indicator: Object Deleted from
Source System 0FLGDELETED).
Data Modeling
8.5 Queries
You can use this query to evaluate completed inspection results for stability studies for different batches,
materials, primary packaging, storage conditions and characteristics, across various studies and for a certain
period of time.
This query is based on the QM: Inspection Results - General Data (/IMO/V_QM01) CompositeProvider.
Structure
Default Values
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MASTERCHAR
Characteristic Unique Identifier for a Master
Inspection Characteristic
0INSP_LOT__0FFZT_MON
Characteristic Start Offset [Mon]
0CAT_CODE
Characteristic Code
Columns
Object Type Name Technical Name
0FRAC_NONCF
Key Figure Proportion of Faulty Units
0NONCNFRMTY
Key Figure Number of defects found
0NONCONFMNG
Key Figure Number of Nonconforming Sample Units
You can use this query to display an overview of adherence to tolerance for inspection results.
This query is based on the QM: Inspection Results - Quantitative Data (/IMO/V_QM02) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MASTERCHAR
Characteristic Unique Identifier for a Master
Inspection Characteristic
0TOLERANCE
Characteristic Tolerance area
/IMO/V_QM02_CK0001
Key Figure Mean value
/IMO/V_QM02_CK0002
Key Figure < Tolerance (ppm)
/IMO/V_QM02_CK0003
Key Figure >Tolerance (ppm)
This query provides an overview of the number of inspections and lot quantities, as well as the confirmed quality.
This query is based on the QM: Inspection Lot / Usage Decision (/IMO/V_QM03) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0CALDAY__0CALMONTH
Characteristic Calendar Year/Month
0MATERIAL
Characteristic Material
/IMO/V_QM03_CK0001
Key Figure Share Not OK
0ACCPT_QTY
Key Figure Accepted quantity
0FRAC_NONCF
Key Figure Proportion of Faulty Units
0ILOTS
Key Figure Number of lots
0ILOTS_ACC
Key Figure Number of lots accepted
0ILOTS_SKIP
Key Figure Number of lots skipped
You can use this query to obtain information about the number of notifications, breakdowns and tasks for
technical objects.
This query is based on the QM: Notifications (/IMO/V_QM11) (technical name: /IMO/QM_IS11)
CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MATERIAL
Characteristic Material —
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name
0COMPLQTYU
Key Figure Complaint Quantity UoM
0COMPL_QTY
Key Figure Complaint Quantity
0DEFQTYINTU
Key Figure Defective Quantity UoM (in
ternal)
0DEFQTYEXTU
Key Figure Defective Quantity UoM (ex
ternal)
0DEFQTY_EXT
Key Figure Defective quantity (external)
0DEFQTY_INT
Key Figure Defective quantity (internal)
0NOTIFOUTST
Key Figure No. of notifications with sta
tus outstanding
0NOTIF_PROC
Key Figure Lead time of the notification
0NOTIF_TOT
Key Figure Number of notifications
0NTF_INTIME
Key Figure Number of notifications com
pleted on schedule
0RETURNQTYU
Key Figure Return Delivery Quantity UoM
0RETURN_QTY
Key Figure Return Delivery Quantity
0STASK_OUTST
Key Figure Number of tasks with status
‘outstanding’ or ‘released’
0TASK_SUCC
Key Figure No. of tasks with status suc
cessful
0TASK_TOT
Key Figure Number of Tasks
You can use this query to display the damage codes used and how often they occur for quality notifications.
This query is based on the QM: Notification Items (/IMO/V_QM12) (technical name: /IMO/QM_IS12)
CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MATERIAL
Characteristic Material —
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATCODE_FE
Characteristic Code – problem —
0CATGRP_FE
Characteristic Code group – Problems —
0CATTYP_FE
Characteristic Code type – Problems —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0DEFECT_VAL
Key Figure Total of defect valuations —
0DEFQTYINTU
Key Figure Defective Quantity UoM (in —
ternal)
0DEFQTYEXTU
Key Figure Defective Quantity UoM (ex —
ternal)
0DEFQTY_EXT
Key Figure Defective quantity (external) —
0DEFQTY_INT
Key Figure Defective quantity (internal) —
0PROBL_FREQ
Key Figure Problem frequency —
You can use this query to get information about problem causes for quality notifications and how often they occur.
This query is based on the QM: Notification - Causes (/IMO/V_QM13) (technical name: /IMO/QM_IS13)
CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Free Characteristics
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MATERIAL
Characteristic Material —
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_CSE
Characteristic Catalog type – Cause —
0CATGRP_CSE
Characteristic Code group – Cause —
0CATCODE_CSE
Characteristic Code – Cause —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
0CAUSE_CNT
Key Figure Number of causes —
This query is based on the QM: Notification - Activities (/IMO/V_QM14) (technical name: /IMO/QM_IS14)
CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Free Characteristics
0MATERIAL
Characteristic Material —
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_ACT
Characteristic Catalog type – Activity —
0CATGRP_ ACT
Characteristic Code group – Activity —
0CATCODE_ ACT
Characteristic Code – Activity —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0ACTVTY_CNT
Key Figure Number of activities —
You can use this query to get information about number and status of tasks for quality notifications.
This query is based on the QM: Notification - Tasks (/IMO/V_QM15) (/IMO/QM_IS15) CompositeProvider.
Structure
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Selection option
Optional
Input ready
Optional
Default Values
Rows
Object Type Name Technical Name Value Restriction / Calcula
tion
0MATERIAL
Characteristic Material —
0CUSTOMER
Characteristic Cust. no. —
0NOTIFICATN__0PRIORITY
Characteristic Priority —
0CATTYPE_TSK
Characteristic Catalog type – Task —
0CATGRP_TSK
Characteristic Code group – Task —
0CATCODE_TSK
Characteristic Code – Task —
0CALDAY_0CALMONTH
Characteristic Calendar Year/Month —
Columns
Object Type Name Technical Name Value Restriction / Calcula
tion
0TASK_OUTST
Key Figure Number of tasks with status —
'outstanding' or 'released'
0TASK_SUCC
Key Figure No. of tasks with status suc —
cessful
0TASK_TOT
Key Figure Number of Tasks —
Coding Samples
Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system
environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and
completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP
intentionally or by SAP's gross negligence.
Gender-Neutral Language
As far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales
person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not
exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet Hyperlinks
The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not
warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages
caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see:
https://help.sap.com/viewer/disclaimer).