on 09-04-2009 8:10 AM
Hi,
in our integration scenario, we send an IDoc to BPM and after some transformations to the BW.
The problem is that we need to transpose the IDoc (before or in the BPM). Each (used) field should create a new row in a target file.
Example.
IDoc Segment
-
ZZ_X1
-
Table
-
Field1
-
Field2
-
Field3
-
ZZ_X2
-
Table
-
Field4
-
Field5
Target DT
Field1 | content_xx | xxxx
Field2 | content_xx | xxxx
Field3 | content_xx | xxxx
Field4 | content_xx | xxxx
Field5 | content_xx | xxxx
Any suggestions on how to solve this?
The problem is that it does not really end up looking the way we want - because we would each (unique) field to generate a new row in the target DT. That would mean a table result with, say, 8 columns and a number of rows.
Doing the way you suggest would a successful 'transpose' of the IDoc, but a result that would consist of ~60 columns in the target DT... And a need to handle this in the BW instead.
It might be the only solution though (if we want to avoid adding customized abap/java code). At this point this is the design we will implement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
One small rectification in the response that I have provided..
I have give Field2 occurrence as 2 ...actually the occurrence should be 1 here..
Thanks
Ayan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Charlotte
I feel you don't need to do it in BPM.You can do it in mapping..
Create a target data type as follows
Records--0 to unbound occurrence
below it , create the no. of fields that you require for your data structure.
Records-
-- Field1 --occurrence 1
--Field2 -- occurrence 2
etc. etc.
simply map it to with the respective segments of Idoc..
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.