Prblem with Synchronous Scenario

hello,
I am facing some problem in sync scenario where i am using a FILE adapter at Sender Side and JDBC Adapter at receiver side,
So, here i used the option of taskTimeout option at the sender side in order to close the job with in that time if there was no response from the receiver side.
I had given upto 1800 secs in the advanced mode table.
But still i am facing some problem with that..
Can anyone help me out...
Thanks,
Soorya

Hi,
File adapter could be used for synchronous processing. Have a look at this:
File - RFC - File without a BPM - Possible from SP 19.
Check the message trace for the interface. You could do this by going to RWB -> Message Monitoring. Please check if you find any useful information about error tracing there.
Thanks,
Bhavish
Reward points if comments helpful

Similar Messages

Problem with Synchronous Scenario

Hello Experts,
Right now i am working on a synchronous scenario RFC <-> 3rd party.
RFC, with other data, passing one table to XI and 3rd party, but in response RFC will require the same table back.
Now here in XI we are not storing synchronous messages in success case. So can anyone tell me that if i want that table in reply also, what should i do?
I was thinking of option that while i communicate with 3rd party, we will create file also in which i will store that table data with the message Id, and while i will get reply back from 3rd party i will read this data from the file and then will pass it back to RFC.
But m not sure that in response how i will read that file? and will i be able to delete that file or not?
Please reply me as soon as possible as i have to give this option to my client.
Hope the question is clear.
Thanks and Regards,
Hetal

Hey,
you can do this in a couple of ways.
Fisrt, you can create a file as already mentioned and access the file from your server.
second, you can create an internal table and access it via hash map.
for both the solutions you need to create a udf.
regards,
Milan.

Message flow in SAP PI 7.31 JAVA only for ABAP Proxy synchronous scenario with Oracle DB

Dear Experts,
I am working on a synchronous scenario Sender ABAP Proxy <===> SAP PI 7.31 JAVA only <===> Oracle Database.I have successfully
configured all the proxy configurations as well both Sender SOAP and JDBC receiver channels are showing no error when pinged from
Cc monitoring in NWA.
1.During testing at Tx SPROXY , I am triggering a message and after 5 minutes I receive an PARSING error message with 2 messages in ECC
local IE i.e. Tx SXMB_MONI.
Note : In NWA , I can see only 1 message that too in cancelled status.
2.Seeing the trace of the messages I assume that the messages have not moved from sender ECC system. I am still confused with flow of message
from the Message Audit log. Audit log of error messages.Could any one share the full Audit log of a successful message generated in SAP PI 7.31 JAVA only.
3.I observed that the QIN Scheduler status in ECC is in INACTIVE status. There is no queue id for 2 messages generated in ECC. Does
it should in ACTIVE status in Tx SMQR..
Regards
Rebecca

Hi Thomas,
Valuable inputs..
1. Since I don't have any audit log for successful message, would you be able to share referring to the
below screenshot whether the message was put into receiver JDBC adapter and JDBC adapter tried to retrieve the Select response from Oracle Database.
2.I have done some setting in Advance mode of the receiver JDBC to increase the time out and other parameters as per SAP note but still the issue is same. If you perhaps have some experience in such scenarios, please share some input so that I can ask the Oracle Database administrator exactly what is required from our side.
3.Regarding the slow response from Oracle , there was some suggestion that the datatype of the request and response should match the column name of the Oracle database. I did that.. Do you have any more suggestion that may be hampering the generation of the response message from the Oracle like SAP note or document.
Regards
Rebecca

IDoc to soap synchronous scenario with BPM

Hi,
I am working on IDoc to soap synchronous scenario using BPM. Here i am facing lot of soap exceptions in my production system. I handled the exceptions. The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second time. Please let me know why the exceptions are getting, and different type of exceptions and solutions for the same.(Blog also is fine)
Thanks & Regards,
Pragathi.

The data getting excuted for the first time, the same data(just changed the description)is giving exceptions for the second
time.
Ideally you should not get an exception for the same data....can you tell is the description and where are you getting the exception...is it a part of the SOAP message or some object?
An exception might have occured because the description would be something unacceptable by the target application.
and different type of exceptions and solutions for the same
there would be many blogs....your thread would be spammed...better make a search on SDN with exception text that you are getting.
Regards,
Abhishek.

Is synchronous scenario possible with JDBC & JMS adapter?

Suppose,JDBC adapter is updating a table or deleting some entry from a table.Can we have an acknowledgement back that the work has been done successfully??
same qstn for JMS adapter also..
Suppose JMS adptr is communicating with any messaging system,can we have acknowledgement back?

Jms Adapter supports Asynchronous scenarios only but If u want to use Synchronous then possible with Standard module beans :
For ex: JMS to Rfc synchronous scenario:
In id:
Sender jms adapter supports Asynchronous scenarios so we have to use standard module beans in Module tab.
Like :
AF_Modules/RequestResponseBean -> 0
CallSapAdapter
AF_Modules/ResponseOnewayBean -> 1
And Provide values in configuration:
0 -> passThrough -> true
1 -> receiverChannel ->provide RECEIVER JMS adapter name ( have to create one more JMS receiver communication channel for responce )
1 -> receiverService ->provide receiver adapter service name (that is provide sender business component because need response for sender )
jdbc adapter :
http://www.****************/Tutorials/XI/SOAP2JDBC/Page1.htm

ERROR During call of SOAP with a SOAP- RFC- SOAP Synchronous scenario

Hello Experts,
I've recently created a SOAP->RFC->SOAP synchronous scenario but every time I'm invoking the SOAP via XMLSpy then i will hang and send a timeout error. Also a log in XI was generated as shown below.
I hope you could help me on this one.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          28.09.2010 09:31:23
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
      in
     procedure "DELETE_LUW_PACKET" "(FORM)", nor was it propagated by a RAISING
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
Regards,
Alfred

Normally such an error comes when the DB of SAP PI is full.
Contact your BASIS or ADMIN team and ask them to free the DB space.
Regards,
Abhishek.

IDOC Serialization & Synchronous Scenarios with AAE

Hi Folks,
I have queries reg Advanced Adapter Engine (AAE):
1) Can we do the Synchronous scenarios through AAE.
2) How can i do the IDOC serialization. How AAE helps in that.
Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
Thank you!!
Regards,
Sekhar

MDM Learn wrote:
Hi Folks,
>
> I have queries reg Advanced Adapter Engine (AAE):
>
> 1) Can we do the Synchronous scenarios through AAE.
Already supported as part of 7.1 / 7.11 so dont see any problem here
>
> 2) How can i do the IDOC serialization. How AAE helps in that.
>
> Am using PI 7.3 ...Can you please mention the possibilites for the above queries.
>
> Thank you!!
>
> Regards,
> Sekhar
the above should be very much supported if you are using the Java IDoc adapter. For serialization use qRFC in SAP partner profile

FILE to SOAP synchronous scenario - config of SOAP channel

Hi All,
I have a scenario where I want PI to pull some files from 3rd party application.
Adapters to be used: SOAP receiver, FILE adapters.
I am aware of the use of Request/Response beans in File sender channel and the File receiver channel to dump the received files in a particular location.
I need help with the configuration of the SOAP channel.
The files to be pulled will be Encrypted.
Summary:
File sender(RequestResponse & ResponseOneWay Beans) , File receiver( to receive the files), SOAP receiver.
Need help with the config of SOAP.
Kindly let me know your views.
Thanks,
Pratibha.

Hi,
Let me put it in detail steps:
In forward flow we will be sending an IDoc. It will be processed and later an Acknowledgement file will be generated.
Now, we want to PULL this Ack file. If the other party had to push the Ack file, the scenario would have been simple.
But, we want to poll for this file and then pull it.
So, we would have something like this:
1. FILE SENDER sends a sample file.
2. We will be applying the beans in file sender to make it a synchronous scenario. So, the Ack file will be received at the location mentioned in the corresponding FILE RECEIVER adapter.
3. We have a SOAP RECEIVER which should send the ACK file in response.
I have configured the same scenario where the RECEIVER was HTTP adapter. The 3rd party had provided us the URL and ENT-APRF value. When I used to send the sample file via FILE SENDER to this HTTP receiver, I was able to retrieve the ACK file via the FILE RECEIVER.
Now, I wish to configure the same using RECEIVER SOAP adapter.
I need to know about the config at SOAP end i.e. how and where the ACK file will be available at the SOAP end for the FILE sender to pull the file.
Ack files will be encrypted..
Any views/suggestions will be of great help.
Thanks,
Pratibha.

Respone message in an synchronous scenario

Hi,
I want to create a scenario:
third party system (via WebService) <-> SAP PI <-> SAP (ABAP Proxy)
I have a SOAP to Proxy synchronous scenario.
Its an synchronous outbound and an synchronous inbound interface.
It is possible to transfer the response message from the inbound interface to the outbound interface?
The response message is a very elemetary mesage (only a key).
With the message from the third party system I will insert data in the SAP system. The new key I will return to the third party system via the response messages.
Any help please?

Surely you will have two mappings in place.One mapping will correspond to the request message, while the other one will correspond to the response.When you are doing the mapping for response, then however do it in reverse manner. For example suppose in your case System A is the sender and System B is receiver. Then you make two message types for each system,one for request and one for response.In the mapping for request, the message type of System A will be source and that of system B will be target because request is going from A to B. However in the response mapping, as the response is coming from B to A, in the mapping you will have the message type for system B as source structure and that of System A in target..And you will add both of these mappings in the Operation mapping in the message mapping tab.

No response message in Proxy to JDBC synchronous scenario

Dear Team,
I am working on synchronous scenario Sender ABAP proxy <===> SAP PI 7.31 <===> Oracle Database.All the necessary proxy configuration has been successfully tested.
Business Scenario:
ABAP proxy will send a single Vendor Id to Oracle DB as request and in return , it has to retrieve all the columns related to Vendor as response.Oracle Database stores all the Vendor information.There are 11 columns including the vendor Id in the view for the Vendor records.
Design :
For Request structure:
a-->Created MT for Sender ABAP Proxy with only 1 field for Vendor Id.
b-->Created MT for Receiver JDBC with Action as SELECT , Table with "View Name" , Access with Constant Blank for all 11 column and Key as Vendor Id.
I have been following the link and Bhavesh Kantilal document.
http://help.sap.com/saphelp_nw73/helpdata/en/44/7b7171fde93673e10000000a114a6b/content.htm?frameset=/en/44/7b7855fde93673e10000000a114a6b/f
rameset.htm&current_toc=/en/ca/b977f1c7814201954f20bb87ad7aab/plain.htm&node_id=71
For Response structure:
Created MT for Receiver JDBC with All the column names.
Created MT for target ABAP ECC with the same 11 column name of JDBC response.
Note :
1.Database team shared a excel file as a sample payload which has all the column names of a vendor and I created my DT with the same naming conventions as they are maintaining in their database i.e. Column names are in CAPs, in the same order and even the special characters in the column name.
2. The PING test connection for Cc works fine to database.
Please read out my queries as the I am not receiving any response from Oracle DB and gives error as timeout exception:
1.Since I am trying to retrieve all the column of the view , am I doing the correct procedure of putting all the column name in the JDBC request structure and making a Select statement. Can I add < * > to fetch all the column name and if so where can I add it.
2. Whats the difference between SELECT and SQL_QUERY and on what circumstances I can add it?
3. How can I test ICO in ID?
4. Can I use any SOAP tool to test the messages? Is there any functionality in NWA to test the messages directly to JDBC .
Hope all your inputs can improve my design part.
Regards
Rebecca

Hi Rebecca,
Did you go through all of these links below?
PROXY to JDBC- SYNC
Proxy to JDBC Sync, with Idoc Receiver
JDBC to PROXY Sync Scenario | SCN
JBDC Receiver Insert Statement Response
Re: Synchronous JDBC select
receiver JDBC structure
Regards,
Jannus Botha

SAP PI conceptual best practice for synchronous scenarios

Hi,
 Apologies for the length of this post but I'm sure this is an area most of you have thought about in your journey with SAP PI.
 We have recently upgraded our SAP PI system from 7.0 to 7.1 and I'd like to document best practice guidelines for our internal development team to follow.
I'd be grateful for any feedback related to my thoughts below which may help to consolidate my knowledge to date.
 Prior to the upgrade we have implemented a number of synchronous and asynchronous scenarios using SAP PI as the hub at runtime using the Integration Directory configuration.
No interfaces to date are exposes directly from our backend systems using transaction SOAMANAGER.
 Our asynchronous scenarios operate through the SAP PI hub at runtime which builds in resilience and harnesses the benefits of the queue-based approach.
 My queries relate to the implementation of synchronous scenarios where there is no mapping or routing requirement. Perhaps it's best that I outline my experience/thoughts on the 3 options and summarise my queries/concerns that people may be able to advise upon afterwards.
 1) Use SAP PI Integration Directory. I appreciate going through SAP PI at runtime is not necessary and adds latency to the process but the monitoring capability in transaction SXMB_MONI provide full access for audit purposes and we have implemented alerting running hourly so all process errors are raised and we handle accordingly. In our SAP PI Production system we have a full record of sync messages recorded while these don't show in the backend system as we don't have propogation turned on. When we first looked at this, the reduction in speed seemed to be outweighed by the quality of the monitoring/alerting given none of the processes are particularly intensive and don't require instant responses. We have some inbound interfaces called by two sender systems so we have the overhead of maintaing the Integration Repository/Directory design/configuration twice for these systems but the nice thing is SXMB_MONI shows which system sent the message. Extra work but seemingly for improved visibility of the process. I'm not suggesting this is the correct long term approach but states where we are currently.
 2) Use the Advanced Adapter Engine. I've heard mixed reviews about this functionaslity, there areh obvious improvements in speed by avoiding the ABAP stack on the SAP PI server at runtime, but some people have complained about the lack of SXMB_MONI support. I don't know if this is still the case as we're at SAP PI 7.1 EHP1 but I plan to test and evaluate once Basis have set up the pre-requisite RFC etc.
 3) Use the backend system's SOAP runtime and SOAMANAGER. Using this option I can still model inbound interfaces in SAP PI but expose these using transaction SOAMANAGER in the backend ABAP system. [I would have tested out the direct P2P connection option but our backend systems are still at Netweaver 7.0 and this option is not supported until 7.1 so that's out for now.] The clear benefits of exposing the service directly from the backend system is obviously performance which in some of our planned processes would be desirable. My understanding is that the logging/tracing options in SOAMANAGER have to be switched on while you investigate so there is no automatic recording of interface detail for retrospective review.
 Queries:
 I have the feeling that there is no clear cut answer to which of the options you select from above but the decision should be based upon the requirements.
 I'm curious to understand SAPs intention with these options -
 - For synchronous scenarios is it assumed that the client should always handle errors therefore the lack of monitoring should be less of a concern and option 3 desirable when no mapping/routing is required?
 - Not only does option 3 offer the best performance, but the generated WSDL is ready once built for any further system to implement thereby offering the maximum benefit of SOA, therefore should we always use option 3 whenever possible?
 - Is it intended that the AAE runtime should be used when available but only for asynchronous scenarios or those requiring SAP PI functionality like mapping/routing otherwise customers should use option 3? I accept there are some areas of functionality not yet supported with the AAE so that would be another factor.
 Thanks for any advice, it is much appreciated.
 Alan
Edited by: Alan Cecchini on Aug 19, 2010 11:48 AM
Edited by: Alan Cecchini on Aug 19, 2010 11:50 AM
Edited by: Alan Cecchini on Aug 20, 2010 12:11 PM

Hi Aaron,
I was hoping for a better more concrete answer to my questions.
I've had discussion with a number of experienced SAP developers and read many articles.
There is no definitive paper that sets out the best approach here but I have gleaned the following key points:
- Make interfaces asynchronous whenever possible to reduce system dependencies and improve the user experience (e.g. by eliminating wait times when they are not essential, such as by sending them an email with confirmation details rather than waiting for the server to respond)
- It is the responsibility of the client to handle errors in synchronous scenarios hence monitoring lost through P-P services compared to the details information in transaction SXMB_MONI for PI services is not such a big issue. You can always turn on monitoring in SOAMANAGER to trace errors if need be.
- Choice of integration technique varies considerably by release level (for PI and Netweaver) so system landscape will be a significant factor. For example, we have some systems on Netweaver 7.0 and other on 7.1. As you need 7.1 for direction connection PI services we'd rather wait until all systems are at the higher level than have mixed usage in our landscape - it is already complex enough.
- We've not tried the AAE option in a Production scenarios yet but this is only really important for high volume interfaces, something that is not a concern at the moment. Obviously cumulative performance may be an issue in time so we plan to start looking at AAE soon.
Hope these comments may be useful.
Alan

Treatement of Fault Messages in Synchronous Scenarios?!

Hi all,
I got a question concerning the use of fault messages in
synchronous scenarios...
1. When I define a fault message for my synchronous
   receiver interface, a fault message, coming back
   would not be handled by my sync. Interface- and
   Messagemapping, right?
   So how can I give the fault messageinformation back to
   the sender?
2. Will I have to define a second scenario for handling
   the fault message?
   (Meaning new Communication Channel, MI, IM, MM and so
   on)
   Thanks for help, anwers are quickly rewarded...
   Daniel

> 1. When I define a fault message for my synchronous
>
>    receiver interface, a fault message, coming back
>    would not be handled by my sync. Interface- and
>    Messagemapping, right?
> So how can I give the fault messageinformation
> ion back to
>    the sender?
The fault message has to be handled in your BPM using an exception branch. You can create an exception branch in a block and assign it to be the handler for a particular exception(fault message).
How can we handle Exception Branch in BPM effectively
> 2. Will I have to define a second scenario for
> handling
>    the fault message?
> (Meaning new Communication Channel, MI, IM, MM and
> and so
>    on)
It depends on what you want to do with your fault message. If you want to throw an alert, that could trigger emails, you can do it by configuring alerts and using a control step in your exception branch to throw alerts. Only if you want to do something else like log a message into a database, you will need separate jdbc communication channel, MI etc.
Regards,
Suresh

SOAP to Proxy synchronous scenario

Hi,
Hope you are all doing well.
I have a SOAP to Proxy synchronous scenario. As part of this scenario, the data structure of the response sent by SAP is different from the response sent back to the SOAP requester. Hence I have used request message mapping between the SOAP request sent by requester and the one passed on to SAP and response message mapping between the response sent by SAP and the one passed on to the requester. Both the message mappings are incorporated in a single Interface mapping.
The problem is that the interface is behaving like a asynchronous one, i.e., request is passing over to SAP but though the proxy is giving a response back, the same is not coming over to XI.
It would be really helpful if you can let me know what might have gone wrong.
regards
Debansu

Hi,
you should have that:
1. Two Message Mapping:
1.1. a Message Mapping for request    (called MM_request)    , from MT_SOAP_request     to   MT_Proxy_request.
1.2. a Message Mapping for response (called MM_response) , from MT_Proxy_response   to   MT_SOAP_response.
2. One Operation Mapping (in PI 7.1) or Interface Mapping (in PI 7.0) from SI_SOAP to SI_ Proxy with:
2.1 in the tab "request", so from MT_SOAP_request     to   MT_Proxy_request    , give your Message Mapping "MM_request".
2.2 in tab "response"   , so from MT_Proxy_response   to   MT_SOAP_response, give your Message Mapping "MM_response".
3. In you Directory, you define a flow like that:
from SI_SOAP to SI_ Proxy by using your Operation Mapping.
If I missed nothing, that's all.
MT = Message Type
MM = Message Mapping
SI =Service Interface in PI 7.1 or Message Interface in PI 7.0.
regards.
Mickael
Edited by: Mickael Huchet on Oct 19, 2011 4:07 PM

IDOC to SOAP synchronous scenario

Hi All,
We have an IDOC to SOAP synchronous scenario in which IDOCs are sent to SOAP by calling a service and then SOAP sends a response back to XI . The response is not sent to SAP- R3. Please suggest on this
Thanks

Hello Rajesh,
Thanks for your good justification.
Here I have also replicated same kind of scenario and having same kind of issue.
One thing just wanted to confirm - Even though SOAP adapter expects HTTP 200 response back from webservice, still SOAP channel is getting into red with following , and as we have Alert configured ...Alert mail also receiving as part of Error only. So How can we avoid that response ? Is there have any parameter to handle or suppress the response back?
Thanks!
Goutam

File to RFC synchronous scenario stopped Picking the files

Hi Experts,
We have a File to RFC synchronous scenario. Till yesterday night it is working fine.
But suddenly it is stooped working.In moni, i can see the failed messages with the Mapping error " Can not create target element, values missing in the queue context "
No Payload in moni / communication channel monitoring / Message monitoring. I've noticed that, wrong files placed in the To-be- processed files and the adapter picked those files and failed in mapping.
I tried by stop and start the communication channel / did some dummy changes in the communication channel and activated. cleared the cache.
But still the communication channel is not working.when i stop and start the communication channel it will try to process the wrong files and failed.
Give me your valuable inputs to resolve this issue.
Regards
Bhargava krishna

Hi Bharghav,
Please go through the below,
Symptom
FTP Adapter is being used in the business scenario for message processing.
During file processing it is noticed, that the FTP sender channel stops
polling. There is no error in the channel monitor or the trace/log files
and the polling jobs are correctly displayed in the AFW scheduler table.
The issue is observed after a network connection issue with the FTP server.
In order to remove the hanging locks from the FTP Adapter, the parameter
'ftp.timeout' setting is required to be set, which releases the lock once
the timeout value is expired. But in the above situation, the value for the
'ftp.timeout' is not taken properly while establishing the data connection
by File Adapter.
Other terms
FTP Adapter, sender, FTP, adapter, timeout, stalled, network, hang, polling
Reason and Prerequisites
Program error
Solution
The hanging situation has now been improved by code changes. Please see
section "SP Patch Level" of this note for a list of updated software
components.
To get this correction available in your Support Package you need to apply
the patch matching to your Support Package version as per the instructions
in the NetWeaver Support Package Stack guide which can be found on the SAP
Service Marketplace as described in SAP Note 952402.
Thanks & Regards
Uday.S

Prblem with Synchronous Scenario

Similar Messages

Maybe you are looking for