on 07-24-2006 4:03 PM
Dear XI experts,
<u>This is my szenario ;</u>
The input parameter for the RFC is send through a file and the response from the RFC comes into XI which is then written into a File (dummy). Finally Transformation(Message Mapping to IDoc) and send to Target system.
<u>Data Types:</u>
DT_SFING2
<u>Message Types:</u>
MT_SFING2
<u>
Message Interfaces:</u>
external
MI_GETDETAIL
MI_GETDETAIL_RESPONSE
MI_SFING2_AB
MI_SFING_OUT
MI_MODIFY
SYNC
<u>Message mappings:</u>
MM_SFING2 (FILE -RFC)
MM_GETMODIFY (RFC.response File )
MM_GETMODIFY3(File IDoc)
<u>interface mappings:</u>
IM_FING1
IM_FING2
<b><a href="http://www.bilder-hochladen.net/files/u2b-1.jpg">Integration Process (BPM):</a></b>
<b>In the integration Builder:</b>
<u>Business Systems:</u>
BA4_007
->CC_BA4_007_RFC
->CC_BA4_007_IDoc
<u>Business Service:</u>
DELTA
->CC_DELTA_FILE_SEND
<u>Integration Process</u>
IP_DELTAUPDATE2
<u>Sender Agreement</u>
Sender:DELTA
-- MI_SFING2_OUT
->CC_DELTA_FILE_SEND
<b><b>How must be the receiver determinations, interface determination and the receiver agreements?</b>
Can someone help me?
Thanks,
Fatih</b>
Guess Your scenario is File->RFC->File->Idoc.
Is there any specific need for you to map the RFC response to a file and then to Idoc?
Why Cannot you directly trigger use file->rfc->resp->idoc?
You can also use abap proxie which can pick up the file and then get the RFC response inside a proxy using the option call function destination 'RFC destination' get the response and mop to Idoc..
In that case you do not require an bpm and scenario is abap proxie to idoc which is straight & simple.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Just a quick note.. You can achieve an RFC lookup from your mapping itself and do not need BPM for this scenario.
All you will need is a file to IDOC mapping . In the mapping, you can perfrom RFC look up wherein, you can pass the RFC request message and get the RFC response message.
Just take a look at this blog for doing the RFC look up,
If you need inputs on this approach , let me know,
Regards,
Bhavesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Integration configuration steps....
1)Create new scenario in ID.
2)Import your intigration procee into ID.
3)Do the following steps using config wizard....(easy to create)
a) File to BPM (OB to ABS of your source file)....No Interface Mapping
b) BPM to RFC (synch abstarct of your source to RFC)...with IM..
c)If you want you can send the response from RFC...
BPM to File (abstract of dummy to rec IB)
this may help you out......
Sekhar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Receiver Determination-
1) Sender to BPM
2) BPM to RFC
3) BPM to File System
4) BPM to R/3 (idoc)
For those Receiver Determinations, you need to have Interface determinations.
You need to have 3 ( 4-1) Reciever Agreements. Because for BPM it is not required,
Regards,
Moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
<b>3) BPM to File System</b>
Step 3 is not possible, because i have not got a inbound asynchronous message interface for File System ( Delta)
<u>Integration process :</u>
<b>Receive</b> (FileRequest) -> <b>Send_sync</b>( FileRequest,FileResponse(dummy))-><b>Transform</b> (<u>source:</u> FileRequest,FileResponse <u>target:</u> IDoc) -> <b>Send</b> IDoc
Kind Regards,
Fatih
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
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.