BI Technical Meeting

Compounded Characteristics
2011

1
 Compounded Characteristics
► You sometimes need to compound InfoObjects in order to map
the data model. Some InfoObjects cannot be defined uniquely
without compounding.
► For example, if storage location A for plant B is not the same as
storage location A for plant C, you can only evaluate the
characteristic Storage Location in connection with Plant. In this
case, compound characteristic Storage Location to Plant, so that
the characteristic is unique.

2
 Where to setup in BI?
►The compounding is setup on the InfoObject in tab Compounding
►The leading characteristic is not included in the compounding list
(in this sample we do not see the Sold-to Party)

3
 How is the data being stored
►The master data of the compounded
object is being stored with a database
key including the object itself and all
compounded characteristics.
►The InfoProvider is only storing the
leading characteristic itself. The
compounded characteristics are
separate objects.

4
 How is the data being shown in BEX
►WithinBEX the compounded object is being shown with the full key as you see it
on master data.

►Ifyou add all Compounded Characteristics, only the leading characteristic is

shown as key

►If you set them up as Display no, you even do not need to show them

5
 Pros and Cons of Compounded Characteristics

►Pros
Attributes can not only be used on single objects, but on compounded too
Avoids building Infosets on some requirements
No risk to have master data being stored as transactional data

►Cons
Access to compounded objects is not as fast as to uncompounded objects
CPEX had an issue to handle compounded master data objects

6
 Upcomming topics
►BCS

►IP

►Report / report Interface

►Trigger chains from Events in other systems
►BW-A

►Good extractor coding

►Dimension Design on Cubes
►Delta Management
►RSRT