Hi experts
We have a new characteristic ZCONTRACT.
A few master data datasources delivers this new object with attributes.
ZCONTRACT consists of time dependent attributes and additionaly this field ZOBJ_NO (object number).
ZOBJ_NO is compounded to ZCONTRACT, reason:
| ZCONTRACT | ZOBJ_NO | DATETO | DATEFROM | ZOBJ_TY | ZDISCONT |
|---|---|---|---|---|---|
| 80245202 | 7000000458 | 31.12.9999 | 01.01.1000 | 1 | |
| 80245202 | 7000000460 | 31.12.9999 | 01.01.1000 | 6 | |
| 80245202 | 31.12.9999 | 01.01.2014 | 2 |
Characteristic ZDISCONT is time-dependent and has no relation to compounded field ZOBJ_NO.
ZOBJ_TY (object type) is delivered with ZCONTRACT and ZOBJ_NO from one datasource; at this place the valid dates are set constant.
ZOBJ_NO and ZOBJ_TY are non-transactional data relevant, meaning that there is no split or logic in the transactional data including these fields.
The business requirement is to report over ZOBJ_TY.
The idea was to use ZOBJ_TY as active navigational attribute in the infocube.
While assigning ZCONTRACT to the infocube, the compounded field ZOBJ_NO automatically is assigned to the cube.
Now, as there is no logic for this field ZOBJ_NO (and also ZOBJ_TY) in the transactional data, I recognized that it is not possible to solve it through this way.
Do you agree? Are there any other ways to realize this requirement?
Thanks