on 02-03-2010 12:42 PM
Hi,
The scenario is EDI xml should be read from FTP and map to request of BAPI and again response of BAPI should be mapped to EDI structure and EDI xml should be droped in FTP.
need to do this scenario using BPM
In BPM I have used the following steps:
1. Receive
2. Transformation
3. Sync Send
4. Transformation
5. Async Send.
so for the configuration part .. what is required.. how many communication channels is it 3.
1. First sender cc for sender edi file Pick up
2. second Receiver RFC for connectint to R/3
3. Third File Receiver CC for again droping the RFC response as edi xml ..
correct me if i am wrong.
regards
sai
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
we are using PI 7.1 here i have declared all the services interfaces as abstract.. may i know how it differs. will give my objects list .. correct me if i am wrong any where..
1. Imported XSD of request and response in External Definition.
2. Imported RFC from R/3 to Imported Objects.
3. Services Interfaces ..
XSDRequest_AbstractAsynchronous
XSDResponse_AbstractAsynchronous
RFC_Abstract_Synchronous
RFC_Request_Abstract_Asynchronous
RFC_Response_Abstract_Asynchronous.
as i have shown about the steps used in BPM..
regards,
sai.
Apart from Abstract service interfaces whihc you mentioned, you also need to maintain Outbound and Inbound SI for the FTP.
RFC can be directly used as a SI in the corresponding objects (OM, Receiver Agreement etc)
If possible try implementing a exception handling for the SyncSend step.....would be a good (not required) design approach.
Regards,
Abhishek.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.