on 03-11-2014 12:34 PM
Hi everyone, Hi Sander van Willigen,
referring to the initial thread I started a new discussion on this topic as I need more information.
This is what I have done. Its working now but I do not know the reason.
... two remarks we are on SAP BW 7.3 SP 10 and
after editing the Z Infoobject "External. Chars. in Hier" and select 0Costelemnt I just mapped the fields with Hierarchy Split in the transformation segment Hierarchy Nodes.
So the transformation is as:
NODENAME > 0COSTELMNT
NODENAME > 0CO_AREA
NODENAME > ZCOSTELMNT
NODENAME > ZCO_AREA
It is working now and the hierarchy is shown correct but I do not know the reason.
thanks in advance for any response.
greetings Ömer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roland,
very helpful blogs thanks for this.
I´ve followed the blog creating hierarchy explained
In my scenario I copied infoobject 0costelemnt into Zcostelemnt.
Zcost is compounded to Zco_area (copy of 0CO_AREA).
When loading I received the error that 0costelemnt is not a valid char for this hier.
So I edit Zcostelemnt and entered 0costelemnt as "External Characteristic".
Finaly I assigned NODENAME in the transformation to all infoobjects. Is this correct? I do not know why I have to assign 0costelemnt to Zcostelemnt as this is already a copy.
Hierarchy Node Segment
NODENAME > 0COSTELMNT
NODENAME > 0CO_AREA
NODENAME > ZCOSTELMNT
NODENAME > ZCO_AREA
Interval Segment
LeafTo > ZCOSTELMNT
LeafTo > ZCO_AREA
Thanks for your answer in advance.
Greetings Ömer
Hi Ömer,
In my system I have a similar case. I created Characteristic RCOSTELMN as equivalent of Characteristic 0COSTELMNT. It is compounded to Characteristic RCOAREA. I.e. all custom InfoObjects.
I do not suggest to maintain External Characteristics in Hierarchies. I did not enter anything here.
Please have a look at the following screenshot of the Transformation.
Note the following rules:
Please have a look at my configuration and modify yours accordingly.
Thanks,
Sander
Hi Sander,
thanks for your reply.
My scenario looks a bit different as the transfer method is IDOC - at least it looks like as I do not have the objects (FIELDNAME, KOKRS and KSTAR) in my source.
...Not able to upload images at the moment!
The mapping for Hierarchie Node Segment looks like:
NODEID > 0H_NODEID
IOBJNM > 0H_IOBJNM
NODENAME > 0H_HIERNODE
NODENAME > (Hiearchy Split) 0COSTCENTER
NODENAME > (Hiearchy Split) 0CO_AREA
NODENAME > (Hiearchy Split) ZCOSTELMNT
NODENAME > (Hiearchy Split) ZCO_AREA
TLEVEL > 0H_TLEVEL
LINK > 0H_LINK
PARENTID > 0H_PARENTID
CHILDID > 0H_CHILDID
NEXTID > 0H_NEXTID
DATEFROM >
DATETO >
INTERVL > 0H_INTERVL
OBJECTID > 0OBJECTID
Additionally mapped the Interval Segment like:
NODEID > 0H_NODEID
LEAFFROM >
LEAFTO > (Hiearchy Split) ZCOSTELMNT
LEAFTO > (Hiearchy Split) ZCO_AREA
OBJECTID > 0OBJECTID
Reading the SAP HELP again - more accurately - it is described there.
The field NODENAME has to be assigned to the basis characteristic and external characteristics of the hierarchy.
Transformation für eine Hierarchie anlegen - Modellierung - SAP Library
Thanks again for your help here.
Much appreciated.
Greetings Ömer
Hi Ömer,
I am curious on which source system and plug-in release you are. I am on SAP_APPL 6.06 and PI_BASIS 7.31. In my system the DataSource looks as follows:
The Transfer Method is in my case 3: PSA and IDOC. It might be different in your case.
Please have a look at SAP Note 1313068 - tRFC transfer of pure IDoc hierarchies to PSA and implement it if necessary.
Anyway, I found for your reference another Hierarchy DataSource 0MATERIAL_LPRH_HIER with Transfer Method 1: IDOC Only. This should be more familiar to your case.
Please have a look at the following screenshot:
You can observe that I also used rule type Hierarchy Split in this case. However, the difference is the handling of IOBJNM.
If you have loaded your data in the PSA and you analyze segment Hierarchy Nodes, then you will observe the Business Content Characteristics 0CO_AREA and 0COSTELMNT. You will have to intervene here: replace the Business Content Characteristics by your custom Characteristics.
You have to create a small routine with coding like this:
case source_fields_3-iobjnm.
when '0CO_AREA'.
result = 'ZCO_AREA'.
when '0COSTELMNT'.
result = 'ZCOSTELMNT'.
when others.
result = source_fields_3-iobjnm.
endcase.
I hope that this will be sufficient to let it work in your case. If not, please let me know.
Best regards,
Sander
Hi Sander,
thanks for your reply.
I checked my DS in R3 and it is case 1. Pure IDOC.
But just mentioning again. The hierarchie load is working as desribed in my previous posts.
The only thing is, that I do not understand why I have to set 0COSTELEMNT as external Char to my ZCOSTELEMNT.
Anyway I tried changing the transformation as suggested by you but I am receiving errors that the ZCostlement Object is not available in A version.
Or Blank is not a valid InfoObject name
Thanks for your hints.
Greetings Ömer
Hi Sander,
its been a while but due to a new requierement I investigated again some time and finally got it working.
Solution is that I did not read exactly the error message 🙂 and I followed your proposal additionally.
Sander van Willigen wrote:
Hi Ömer,
My advise is: remove all External Characteristics in the hierarchy and after that, apply my proposal of Mar 18, 2014 1:33 AM.
Best regards,
Sander
Message no. RH603
While debugging the SOURCE_FIELDS_3-IOBJNM I noticed that I have to use 0COSTELMT instead of 0COSTELMNT.
So this is working now.
IF SOURCE_FIELDS_3-IOBJNM = '0COSTELMT'.
RESULT = 'ACOSTELMT'.
ELSE.
RESULT = SOURCE_FIELDS_3-IOBJNM.
ENDIF.
Changing it
Thank you all again for your responses.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
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.