ASYN/SYNC/ASYN Like FIle - webservice- Idoc

Hi Guys,
Is there blog can you sugges or give me solution.
I am tryting to sending a File -XI-Webserivce-IDOC.
please suggest me is it possible these senario.
Regd's
Vardesh.

Could tell us the business process? means the link between file, web service and Idoc and the way u want them to activate?
VJ

Similar Messages

In XI ,file on application sever how to do the scenario like file to idoc?

hi experts,
In XI ,file on application sever how to do the scenario like file to idoc?
thanks in advance
gupt

Hi gupta ,
The following are excellent websites giving step-by-step solution to solve u'r problem:
How to convert an IDoc-XML structure to a flat file and vice-versa in XI 3.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
IDoc Packaging and Mapping Techniques
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
check this blog
Idoc File -> SAP R/3 packaging
How ToConfigure IDoc Adapters
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098
Troubleshooting File-to-IDOC Scenario in XI.
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
cheers!
gyanaraj
****Pls reward points if u find this helpful

File--Webservice--Idoc

A File that is being dropped in XI server. XI's file adapter will pick this file and then we have a BPM that will call the webservice, get the values and then post this as an Idoc.
The above is my requirement.Please anyone help me out.

Hi,
Check this weblogs for some problems and their resolutions:
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
/people/shabarish.vijayakumar/blog/2008/01/08/troubleshooting--rfc-and-soap-scenarios-updated-on-20042009
/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi
/people/stefan.grube/blog/2007/03/29/troubleshooting-soap-http-and-mail-adapter-scenarios-with-tcpgateway
also take a look at this blog
/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit
Please reward points if it helps
Thanks
Vikranth

FILE to IDOC SCENARIO NEED MANDATORY FIELDS IN MATMAS IDOC

Hi
I'm learning a scenario like File to Idoc which is i need some what are the mandatory fields for creting the message mapping.. between source file and MATMAS IDOC... because it was showing several fields.
is there any way to find out the fields we need to map compulsory... for sending IDOC successfully.
Thanks
Babu

Hi Babu !
Log into the R/3 system, transaction WE60, enter the idoc type MATMAS01 or 02, 03, 04, then press F8 or go to Documentation menu, HTML Format.
It will display a document, telling you which fields are optional and which mandatory.
Regards,
Matias
PS: please award points if helpful.

File to Idoc with error in trfc

Hello,
I have a scenario like
File -> XI -> (idoc) R3
The scenario works fine but yesterday I had a problem with the user in the rfc destination(pwd wrong) which is used for the idoc-adapter. In the sxmb_Moni and the RWB the msg. got an success flag/info but it was not delivered to the r3 because the rfc-destintion could not work.
I know that the idoc-adapter is not part of the adapter-engine and my understanding was that the adapter send his status back to the integration engine. But in this cause I got no feedback from the adapter. I think this is not Ok or I am wrong ?
Regards Jami

Hi Jami,
The reason is simple.....the message is sent from the integration server to the adapter engine which was susessful.but what went wrong is the rfc destination being wrong in the receiver adapter which is not known to the integration server. So in simple words, if things work fine in your integration server then it will not throw an error in your sxmb_moni. So had there been a problem between the message transfer from the integration engine to the adapter engine then it would have surely given you an error in your sxmb_moni(for example you specify some wrong parameters while configuring your receiver IDOC adapter).
But in this case since we dont have an IDOC adapter in the component monitoring (it has adapters which are in the JAVA stack only but IDOC adapter is in the ABAP stack)we can see the error in SM58 only.
I hope this answers your question fully. If any other doubts regarding the same pls do ask me.
Regards,
Abhy
Message was edited by: Abhy Thomas

File-Bapi-Idoc scenario

Hi Experts,
I am working on the scenario like File-Bapi-Idoc
1) Getting the file from external system, in the file
If the Sonumber is populated then need trigger an Bapi_change
and after getting the response flag as 1 from Bapi then have to send all those file fields through IDOC-.
Else
2)If the Sonumber is not populated from the file then need to trigger a Bapi_Createfromdat to create the sales order and receive the salesorder number as response from Bapi then
have to send all those file fields and Bapi response sales ordernumber through the same IDOC which is mentioned in the point 1.
Please provide the solution for this.
Is BPM required for this,if so provide the steps.
Thanks in advance,
Praveen

Hey,
     you will require a BPM for this.
     Steps.
1)    recieve step(abstract async) for the file
2) Switch case: condition based on the Sonumber i.e . whether it is populated or not.
Branch 1(of switch if Sonumber is populated): send step(abstract synchronous) recieves flag as 1.
Branch 1 will also have a transformation step that will consist of the mapping between bapi_change and Idoc
Branch 2(of switch if Sonumber is not populated):send step (abstract synchronous) recieves sales order number. the creation logic will be written in the BAPI.
Branch 2 will also have a transformation step that will consists of mapping between Bapi_create and the Idoc.
3) After the switch there will be an abstract asynchronous send step for the Idoc.
In Inegration directory:
Channel: File, RFC and Idoc.
receiver determination
File-> BPM
BPM->RFC
BPM-> IDOC
Now for Idoc you require ALE settings both on XI as well as R3
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
WE42 process code
WE47 status info.
reward points if useful
regards,
      Milan

How to realize a Sync-Asyn Bridge

Hey Folks,
I was trying to 'decode' whatever is written in the How to guide (Realize a sync - async and async - sync bridge in the adapter framework). Thanks to Bhavesh he posted the thread on the Async - Sync part and so i thought i would figure out the Sync - Async part.
Ok so here is what i have done till now (with no success);
its a HTTP <-> XI <-> File
So;
2 DT/MT for HTTP, 2 DT/MT for file
1 MI outbound sync -> http
1 MI inbound sync -> File
the 2 mappings and the 1 IM
In configuration;
1 rec. file adapter and 1 sender file adapter
the configuration is as usual for a sync scenario; except for the sender agreement for the sender file adapter, i configure a dummy sender agreement with dummy interface and dummy namespace but the original CC created.
In the Recv. file channel module part;
1     AF_Modules/RequestOnewayBean     Local Enterprise Bean     2
2     CallSapAdapter     Local Enterprise Bean     0
3     AF_Modules/WaitResponseBean     Local Enterprise Bean     1
2     passThrough     true
in the sender file channel;
1     AF_Modules/NotifyResponseBean     Local Enterprise Bean     1
So any of you guys who did something on that document, i hope can throw some light
Cos i am sure i am missing something here !!!
~~ShaBZ

HI,
Are you using BPM or not??
Can you plz tell me the SP number/version.
I hope Sync - Asyn without BPM is possible with latest SP.
Please see the below links
/people/community.user/blog/2006/12/12/http-to-rfc--a-starter-kit
Searching for a BPM scenario
With BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Regards
Chilla..

I just got an iTouch and whenever I try to sync it to iTunes it keeps poping up with a message that says something like "cannot sync or read file". What should I do?

I just got an iTouch and whenever I try to sync it to iTunes it keeps poping up with a message that says something like "cannot sync or read file". What should I do?

Is the error message:
"Attempting to copy to the disk <iPod name> failed. The disk could not be read from or written to."
if it is try:
http://support.apple.com/kb/HT1207
If not, what is the wording?

BPM correlation and Sync-Asyn Bridge....

Regarding Sync-Asyn ,I have gone thru these blogs...
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
I am not able to do a end to end scenario...using this ....So could any one give me a step by step guide for the syn-asyn Bridge.
And also step by step for correlation...
Please help me in this regard....

Hi,
Defining Sync/Async Communication
To enable the communication between a synchronously calling business system (synchronous outbound interface) and an asynchronously called business system (asynchronous inbound and outbound interface), you can define a sync/async bridge in an integration process. You can only define one sync/async bridge for each integration process.
You can also achieve sync/async communication by using the JMS adapter. If you do not have any particular demand for monitoring or for troubleshooting, SAP recommends that you use sync/async communication in the JMS adapter instead. The advantage of using the JMS adapter over synch/async communication using an integration process is a significant increase in system performance.
See: Async/Sync and Sync/Async Bridge in JMS Adapter
Structure of a Sync/Async Bridge
The following table outlines the minimum components of a sync/async bridge:
Step
Use
Receive step to open the sync/async bridge
Receives the message request from the synchronously calling business system and opens the sync/async bridge
Asynchronous send step
Sends the received message asynchronously to the asynchronously called business system
Receive step
Receives the message from the asynchronously called business system
Send step to close the sync/async bridge
Sends, for example, the response from the asynchronously called business system to the synchronously calling business system
Performance Considerations
If you insert additional steps in the sync/async bridge, the synchronous time is increased correspondingly. If the time that elapses before the sync/async bridge is closed is too long, this can lead to problems.
Fault Messages
It is currently not possible to send fault messages back to the synchronously calling business system. If you want to return error statuses to the synchronously calling business system, you can define a field for an error indicator in the message that is sent to the synchronous interface.
Procedure
Define a Receive Step to Open the Sync/Async Bridge
       1.      Insert the receive step to open the sync/async bridge in the integration process.
You can do this at the following points:
○       Directly after the start marker
○       As the first step in a block if the block is the first step of the integration process and if it has the mode Standard
○       As the first step in a fork. If the fork already contains some starting receive steps, the Start Process indicator is automatically reset for these steps.
       2.      In the object area, define the container element that receives the synchronously sent message.
Specify an asynchronous, abstract interface in the container element. The message must correspond to the request message of the synchronous interface used to receive the message.
       3.      Select this container element in the Message field in the properties area of the receive step.
       4.      In the Mode field, select Open S/A Bridge.
       5.      Select the Start Process field.
The receive step to open the sync/async bridge must start the integration process. There must be no other receive steps to start the integration process.
       6.      Specify the synchronous interface for receiving the message from the synchronously calling business system. The message type of the message to be received and the request message from the synchronous interface must be identical.
Define an Asynchronous Send Step
       7.      Insert a send step that sends the received message asynchronously to the asynchronously called business system.
See also: Sending Messages from Integration Processes Asynchronously
Define a Receive Step
       8.      Insert a receive step that receives the message from the asynchronously called business system.
Define a Send Step to Close the Sync/Async Bridge
       9.      Insert the send step at the required position in the process definition.
Do not insert the send step in a loop, block, or fork.
   10.      In the Mode field, select Close S/A Bridge.
The integration process must not contain any further send steps to close a sync/async bridge.
   11.      In the Opened By field, specify the receive step that opened the sync/async bridge.
   12.      In the message field, specify the message that is sent to the synchronous interface.
This message must be of the same type as the response message from the synchronous interface that you specified in the opening receive step.
Example
You can find an example of a sync/async bridge in the Integration Repository under SAP Basis à SAP Basis 6.40, namespace http://sap.com/xi/XI/System/Patterns under BpmPatternSyncAsyncBridge.
For a description of the example, see Example: Sync/Async Communication.
Reg,
suresh

Correlation and Sync Asyn Bridge

Regarding Sync-Asyn ,I have gone thru these blogs...
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
I am not able to do a end to end scenario...using this ....So could any one give me a step by step guide for the syn-asyn Bridge.
And also step by step for correlation...
Please help me in this regard....
<Moderator note: thread locked. I moved your last post to XI, please do not post duplicate questions>
Edited by: Mike Pokraka on Jul 7, 2008 1:00 PM

Regarding Sync-Asyn ,I have gone thru these blogs...
Demonstrating Use of Synchronous-Asynchronous Bridge to Integrate Synchronous and Asynchronous systems using ccBPM in SAP Xi - Use of Synch - Asynch bridge in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge in ccBPM
I am not able to do a end to end scenario...using this ....So could any one give me a step by step guide for the syn-asyn Bridge.
And also step by step for correlation...
Please help me in this regard....
<Moderator note: thread locked. I moved your last post to XI, please do not post duplicate questions>
Edited by: Mike Pokraka on Jul 7, 2008 1:00 PM

Doubt about RFC Destination in FILE to IDOC Async scenario

hi
In FILE-XI-IDOC Async Scenario we are creating RFC Destination in R/3 and XI.
For Asyn we don't want response But We are Creating RFC Destination in R/3 also.
Any specific reason.
Thanks in advance.

First you need to have a clear understading of how the idoc adapters works.
In xi we create rfc destination and specify that in the port maintenance on the idoc adapter so that we can establish a connection to the sender / receiver system which contains the IDOC METADATA (IDX2) that is required by the idoc adapter to convert the native idoc into idoc xml format.
In R/3 as sender we create rfc destination so that when the idoc has to be transported to the xi system first it will be sent to trfc port that rfc desination that u define the trfc port contains that the target system address(IP) and logon parameters req.So idoc can be sent to the desired destination.
In R/3 as a receiver to facilitate communication we define rfc dest, partner profile and specify the inbound parameters so that idoc can be posted.
Hope this answers your ques.
cheers
*Raj*
*POINTS IF SATISFIED WITH ANSWER.

Multiple Operations for File to IDoc scenario

Hi all,
I have a file to IDoc scenario where two IdocXML files (one for INSERT and one for CHANGE of Business Object) have to be picked up by file adapter and transfered to SAP System. In respect to the multiple operations PI 7.1 can handle I would like to create one Service Interface for the Business Object and two operations (INSERT and CHANGE).
Unfortunately I am not able to use the operation in the sender agreement, so I can't specify the comm-channel for the operations, only for the interface.
So, can I use multiple operations in a file scenario (respectively in a non Web Service scenario)??
Thanks a bunch,
Manfred

The scenario is pretty easy. I just want two different files to be read by one Comm Channel with one Sender Agreement.
They are both transferred to the same receiver. I just wanted to test one scenario using multiple operations.
In your blog you described that you should not use two operations with the same set of messages (synchronous/asynchronous). In my case both are asynchronous but I already tried it with one being sync and the other one async. Where did you actually get this information, it puzzles me a little since SAP does the same in its preconfigured Enterprise Services as far as I know.
In the Trace for pipeline step Interface determination in SXMB_MONI it says:
<Trace level="1" type="T">...There is no Interface Determination configured for receiver party and receiver service BS_RECEIVER</Trace>
<Trace level="2" type="T">Check conditions for (Inb: Party Srvc If) BS_RECEIVER SI_..._Out</Trace>
<Trace level="2" type="T">...valid InbIf without Condition: SI_..._Out</Trace>
<Trace level="2" type="T">Number of receiving Interfaces:1</Trace>
So it finds the Outbound Interface in Receiver side which is wrong since I specified the Inbound Interface in the Interface determination. Did anyone of you already encounter such a behaviour? I already deleted and recreated all routing objects but without any success.
Thanks,
Manfred

FILE RFC IDoc

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 IDoc . The diagram of the following is shown below;
http://photos1.blogger.com/blogger/3087/1595/1600/RFC.0.jpg
Mapping 1 ) File >> RFC (getDetail)
Mapping 2 ) RFC (getDetail-Response) >> IDoc
Problems : Message Interfaces
Abstract_synchronous
Output : File
Input :IDoc
Activation of the change list canceled
Check result for Message Interface sync | http://xi/DeltaUpdate2:
Message interface Message Interface sync | http://xi/DeltaUpdate2 references an IDoc message and a non-IDoc message
But I need the synchronous step !
It is possible to use correlation with Asynchronous or the only way to get the return message is use Synchronous RFC?
And Can you brief me the steps in bpm?
Regards,
Fatih

Hi,
Easier solution for this is create one Abstract Message Interface(like dummy) for the RFC response.
Assumptions- You are doing RFC Req/Resp mapping outside the BPM.
If so, your RFC response will be stored in the Dummy Repsonse structure. Then send this structre async from BPM. Outside the BPM map this structure with Actual Idoc interface.
Hope this will work here
Regards,
Moorthy

Help in creation of XML file for IDOC postings

Hi All,
Need help if anyone has knowledge/experience in creating XML files for IDOC processing.
We need to design an input file (in XML format) for creation of IDOCu2019s for purchase Invoices through Interface.
We have an existing input file, which is working correctly. We are trying to modify this existing input file for a new Tax Code (Non-deductible inverse tax liability). This tax code is working fine for manual postings. But, through IDOC, tax postings are not correctly triggering.
Could you please confirm if any one has experience on this, so that I can share more details for resolving.
Thanks & Regards,
Srini

Hello,
you can use CALL TRANSFORMATION id, which will create a exact "print" of the ABAP data into the XML.
If you need to change the structure of XML, you can alter your ABAP structure to match the requirements.
Of course you can create your own XSLT but that is not that easy to describe and nobody will do that for you around here. If you would like to start with XSLT, you´d better start the search.
Regards Otto

File to IDOC scenario-no messages in SXMB_MONI

Hi all,
   I know this is asked so many times ,I checked some links but couldn;t find out the gap where it happened.
I am doing a File to IDOC scenario through XI mapping.
I am not getting any messages in SXMB_MONI.
When I check Communication Channel monitering in Runtime Workbench, it shows processing successfully, then it should generate messages in SXMB_MONI and intimate whether the scenario created is correct or not right!
Please help.
My scenario goes like this:
Sender : Business service(Some file location)
Used File adapter for sender communication channnel.
Receiver : Business system(SAP R/3)
Used IDOC Adapter for receiver communication channel.
One more thing is,do I need to create logical system for Business service also?If so, where do I maintain it?(In SAP R/3 or in XI system?)
Till now,I maintained my XI system as logical system in WE20 and I didn't create any logical system for business service in any system.Does it create main problem?

Hi , I am able to poll the files from file location now.and I am receiving IDOC into SAP R/3 with status 56.I already created partner for file path as a logical system and assigned inbound parameters with respective message type . Even the status shows :
An inbound partner profile could not be found with the following key:
/LSDEMO/LS//DEBMAS////
This involves the key fields of table EDP21:
-SNDPRN partner number of sender
-SNDPRT partner type of sender
-SNDPFC partner function of sender
-MESTYP logical message type
-MESCOD logical message code
-MESFCT logical message function
-TEST    test flag
I already manitained following data and there is one record in EDP21.
SNDPRN = LSDEMO
SNDPRT = LS
SNDPFC = LS
MESTYP   = DEBMAS
MESCOD = space
MESFCT = space
TEST = space
EVCODE   = DEBM
SYNCHK = X
METHOD = space
USRTYP = space
USRLNG = space
INMOD = space
DCART = space
And please let me know whether I have to maintain outbound parameters also for my partner in XI system.I didn't see any difference even I maintained it.
And my IDOC takes another port rather than I mentioned in my SNDPRN(sender port) of my IDOC control record in message mapping.Let me know whether it's mandatory to maintain port name with SAP<XXX>convension,because IDOC in R/3 is picking the port with that naming convension.
Edited by: Jaya on Feb 26, 2010 10:17 AM
Edited by: Jaya on Feb 26, 2010 10:27 AM

ASYN/SYNC/ASYN Like FIle - webservice- Idoc

Similar Messages

Maybe you are looking for