on 08-21-2013 10:06 AM
Hi
I am not tha good with masterdata infoobjects etc, så I hope someone can give me some good documentation/articals about it.
In mye case I have a time dependent masterdata object called MO1 that has
- MOID
- from date
- to date
- desciption defined
I have been given some work to add some attributes to this masterdata. The attributes data is coming from another extractor than the main masterdata. The question is: in the attributes extractor, must the field MOID be defined to be able to map this to the masterdata information? if the mastedata is time dep, must we then also have from date and to date in the attributes? If the from date and to date are different then what is defined for the masterdata, what happens then?
Hi
The question is: in the attributes extractor, must the field MOID be defined to be able to map this to the masterdata information?
Yes it must be present otherwise you can't map it. Any object that is possibly compounded must also be present.
if the mastedata is time dep, must we then also have from date and to date in the attributes? If the from date and to date are different then what is defined for the masterdata, what happens then?
Yes that is required. You'll see when you check your infoobject the validto is also part of the key.
The timedependent masterdata tables begin with /BI0/Q*
hope it clarifies
Martin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Helge,
in the attributes extractor, must the field MOID be defined to be able to map this to the masterdata information?
No, but you want the same length and type. right values need to come form that extrcator.
Most of the time we always loading respective master data from respective standard extractors only.
if the master data is time dep, must we then also have from date and to date in the attributes?
Yes, we need date to and date from for time dependence objects
If the from date and to date are different then what is defined for the master data, what happens then?
Whole data will mismatch, you need to check how it look like at ecc side and bw side. need right mapping from right source.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Thanks for the good answers!
Just one clarification related to the answer you gave when it comes to if MOID need to be a part of the attribute extractor;
So you are saying that MOID does not has to be a part of the extractor, but an ID that has the same length and type to be able to map the attributes to the correct MOID?
Hi Helge,
If its compounded then its mandatory to have that object. when its compounded that object automatically part of your attributes.
if standard attribute data source then its need to be part. if its customizing one its not mandatory. in that case source and target need to be the same length and type.
can you please name the data source.
Thanks
User | Count |
---|---|
83 | |
24 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.