on 01-05-2009 2:09 PM
Hi All,
i have an file to RFC scenario..if there are any exceptions while posting the data into SAP,want to catch all error/successful messages in XI and send the messages back to the sender...
Can any1 tell me how do i handel this.?do i need to do any alert config?
Thanks.
Rohan Patil.
Hi Rohan,
my suggestion would be to use a File to Sync ABAP Server Proxy scenario and the Fault Message Type. Take a look at the following blog:
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Within the server proxy, you can call the RFC and evaluate the return code.
Regards,
Chen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Chen,
My RFC is already capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan P
Hi Chen,
My RFC is capturing all messages , what i want to know is:
1.when my RFC gives an error/successful message..where/how can see that message in XI.(these messages are captured in the repsonse).
2.after this i want send these messages by mail to the user.
Above two are the reqs..How do i go about this.
Thanks.
Rohan Patil.
Hi Rohan,
seems the SDN is not quite stable today...
1) In an ABAP RFC, the success/error information are defined by the return code and exceptions. If you are using a standard receiver RFC scenario, what you are able to see on XI is only the information returned by export and table parameters in the RFC, meaning that if your RFC call is somehow failed, what you see on XI is only the empty results.
However, BAPI is a special RFC technology. Under the table parameters there is additionally a RETURN parameter, this is exactly where you can find the error or success info of your BAPI call. Use a sychronous RFC interface to get the response message.
In this case my recommandation would be: BAPI or ABAP Proxy+Fault Message Type.
2) If you want to send the response using Mail Adapter to a particular recepient, a BPM is required. Basically you receive the file, carry out the mapping and send it to the SAP calling your RFC/BAPI/Proxy, then receive the synchronous reponse, map it to an email structure and send it to your mail receiver.
Regards,
Chen
Hi Rohan,
seems the SDN is not quite stable today...
1) In an ABAP RFC, the success/error information are defined by the return code and exceptions. If you are using a standard receiver RFC scenario, what you are able to see on XI is only the information returned by export and table parameters in the RFC, meaning that if your RFC call is somehow failed, what you see on XI is only the empty results.
However, BAPI is a special RFC technology. Under the table parameters there is additionally a RETURN parameter, this is exactly where you can find the error or success info of your BAPI call. Use a sychronous RFC interface to get the response message.
In this case my recommandation would be: BAPI or ABAP Proxy+Fault Message Type.
2) If you want to send the response using Mail Adapter to a particular recepient, a BPM is required. Basically you receive the file, carry out the mapping and send it to the SAP calling your RFC/BAPI/Proxy, then receive the synchronous reponse, map it to an email structure and send it to your mail receiver.
Regards,
Chen
Hi Rohan,
seems the SDN is not quite stable today...
1) In an ABAP RFC, the success/error information are defined by the return code and exceptions. If you are using a standard receiver RFC scenario, what you are able to see on XI is only the information returned by export and table parameters in the RFC, meaning that if your RFC call is somehow failed, what you see on XI is only the empty results.
However, BAPI is a special RFC technology. Under the table parameters there is additionally a RETURN parameter, this is exactly where you can find the error or success info of your BAPI call. Use a sychronous RFC interface to get the response message.
In this case my recommandation would be: BAPI or ABAP Proxy+Fault Message Type.
2) If you want to send the response using Mail Adapter to a particular recepient, a BPM is required. Basically you receive the file, carry out the mapping and send it to the SAP calling your RFC/BAPI/Proxy, then receive the synchronous reponse, map it to an email structure and send it to your mail receiver.
Regards,
Chen
Hi Rohan,
seems the SDN is not quite stable today...
1) In an ABAP RFC, the success/error information are defined by the return code and exceptions. If you are using a standard receiver RFC scenario, what you are able to see on XI is only the information returned by export and table parameters in the RFC, meaning that if your RFC call is somehow failed, what you see on XI is only the empty results.
However, BAPI is a special RFC technology. Under the table parameters there is additionally a RETURN parameter, this is exactly where you can find the error or success info of your BAPI call. Use a sychronous RFC interface to get the response message. In the RETURN element you'll see the success/error information.
In this case my recommandation would be: BAPI or ABAP Proxy+Fault Message Type.
2) If you want to send the response using Mail Adapter to a particular recepient, a BPM is required. Basically you receive the file, carry out the mapping and send it to SAP R3 to call your RFC/BAPI/ABAP Proxy, then receive the synchronous reponse, map it to an email structure and send it to your mail receiver.
Regards,
Chen
Hi ,
The scenario you are trying to execute is an communication between an Async System and Sync System. As the File Adapter only supports only Async mode of communication, in a normal scenario, it is not possible for it to capture the response from the RFC.
In such cases BPM looks a valid option.
File will send data to an Integration Process. The Integration Process(BPM) then synchronously send the request message(It received from the Sender System) to the RFC. The response sent back by the RFC is captured by the Integration Process(As it sent the request Synchronously). Once the response is with the BPM, you can use another Inbound FileCC to receive the response.
The response may be the data or the Fault MEssage( Message regarding the Exception ).If you want a mail to be sent, you can use an Inbound Mail CC insted of Inbound File CC.
regards,
Subhendu
Hi
in Your Graphical mapping, USE UDF to handle Exception.
throw new CustomException(message);
will report the qualified exception and will raise an alert when the condition fails
/people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
/people/bhavesh.kantilal/blog/2006/07/25/triggering-xi-alerts-from-a-user-defined-function
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
The scenario you are trying to execute is an communication between an Async System and Sync System. As the File Adapter only supports only Async mode of communication, in a normal scenario, it is not possible for it to capture the response from the RFC.
In such cases BPM looks a valid option.
File will send data to an Integration Process. The Integration Process(BPM) then synchronously send the request message(It received from the Sender System) to the RFC. The response sent back by the RFC is captured by the Integration Process(As it sent the request Synchronously). Once the response is with the BPM, you can use another Inbound FileCC to receive the response.
The response may be the data or the Fault MEssage( Message regarding the Exception ).If you want a mail to be sent, you can use an Inbound Mail CC insted of Inbound File CC.
regards,
Subhendu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You may also configure a BPM scenario with the following step:
1. Receive to receive file
2. Inside a Block -> Send step to send message to RFC
3. In another branch of same block you may use exception handler for any type of error and you may send data from here to file system again using send step.
The advantage here would be any modification in requirement (like changing the location to which errors are sent) would be easily accomodated.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
7 | |
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.