on 08-01-2015 11:42 AM
Hi
I am working on a scenario where one file is ftpserver1 which contains header data and second file is in ftpserver2 this two files should merge into single idoc INVOIC.INVOIC02
I thought of using Integration process and used the BPM Pattern of collect files
1) But how IP understands idoc as it understands only abstract interface. Is it necessary to create abstract service interface for idoc??? i tried that to still it throwing the error.
I followed this link as well BPM Abstract Interface for IDOC? | SCN but it couldn't helps me
i tried of creating message mapping to inbound service interface to abstract interface thought it is not working
it is throwing error while trying to activate integration process ..
please share if you have links or docs for this kind of secenario i.e two files merging into one idoc..i searched SDN but i couldn't found any docs related to abstract interface for receiver idoc
or else tell me exact steps for this in 1) ESR 2) ID
How can i resolve this ??..your early answers appreciated with points
Please help me out as it is hitting heads....
Looking into the error it look like there is some problem i your receiver abstract interface definition or in the definition of container you are using in send step.
Thanks,
Apu das
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pavan,
Are you using ccBPM or NW BPM? Going for BPM is not suggested unless it is un-avoidable situation. In NW BPM we have
For your scenario, we can try using Multi-mapping, by having two source messages mapped to the single Invoice IDoc in the Message mapping?
One source message will have the MT of first file and second source message will have MT of 2nd file.
If you still want to go for the BPM approach, for the error you are facing you need to create Abstract interface consisting of Invoice IDoc structure and then use a transformation step to map the Abstract interface of IDoc with the Invoice IDoc and the use the send step to post the IDoc to the ECC system.
Regards,
Nitin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nitin,
Thank you for your response
facing error here
I have created abstract interface for idoc and mapped abstract idoc interface with standard idoc
but not able to see this one in transformation step as this step only picks up only OM Of abstract interfaces
so i have given here consolidate mapping of 2files in one sender which are abstract to receiver idoc abstract interface is that right???
if so what i have to mention in receiver determination to idoc...? is standard idoc??
in sxmb_moni it is throwing error
can you please clarify regarding this..
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.