Fault message type using in File to IDoc Scenario

Hi,
I have successfully configured File to IDoc scenario. Now I am thinking to add some flavour to it by using Fault message type.
Can I use fault message type without using any proxies?
Can some body help in giving an answer to my question and provide some weblogs to achieve the configuration?
Thanks in advance.
Suraj Kumar

Hi Suraj,
With IDOCs, you cannot set up fault messages as it is async mode communication. There is not control which waits for the processing of the message/application errors as you have it in case of synch mode.
But, you can set up acknowledgement using ALEAUD. Check this for more /people/saravanakumar.kuppusamy2/blog/2005/01/20/configuration-tips-for-a-business-serviceintegration-process-to-send-back-ale-audit-idoc
praveen

Similar Messages

How is the Fault Message Type used?

Hi,
I have a HTTP-SOAP scenario.I want to post a request to a HTTP Server using the SOAP receiver adapter and get the ackowledgement message from the receiver, if it was successful or not. Is this possible using the Fault Message type?
If not how else can i capture the response in the EO mode?

Hi Sivasakthi
Yes you can capture soap response using SOAP fault message
Check this link for embedded soap response
http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
With this you can refer to this blog as well
Handling Web Service SOAP Fault Responses in SAP NetWeaver XI
Thanks
Gaurav

Fault Messages/Response handling in File-XI-SOAP scenario

Hi
I have a File-XI-Webservice scenario.
Suppose I am sending a call "Request" to the webservice with 4 fields a,b,c and d. If the call is succesful we get an epmty "Response" back. Suppose any of the fields a,b,c or d are missing then the webservice throws an "AccountUtilsException" with a message "Required data 'c' missing". I want to be able to capture this message in a file.
I tried using asynchronous scenario first but that didnt work. I didnt get an empty response back for successful messages, neither did i get an error in sxmb_moni for missing data. Only the SOAP adapter would be red and the error "UNKNOWN ERROR" would appear. So I created a BPM with a receive, send-sync, send steps. With the AccountUtilsException set up as the response. Now, when all the data is good everything is successful and a file is created with the empty "Response" xml. When any of the fields is missing I see errors in sxmb_moni with Message class "Application error". But when I go into the payload I cannot see the xml. Instead it says "Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later." When I click view source I see the xml with the message "Required field c is missing". A file is also not written. Can anyone help me figure out what I am doing wrong?
Thanks,
Jahnavi

Hi Jahnavi,
yes, the asynchronous scenario cant work because there is no answer.
I think you should have exception types in your interfaces and map the fields of the exception. I m not shure if the answer of the webService in case of exception (AccountUtilsException) is a xml msg, you shoud be able to find out that at RTW message monitoring. You should be able to put that into a the exception type of the interface. Another possiblility to pick the exception up would be an alert.
Regards,
Udo

Without using ID file to idoc scenario

Hi People
I am trying one scenario(file to IDoc) that is without using configuration only using IR only is it possible to create? and how
Thanks & regards
shekar

Hi,
some scenarios could be done without IR:
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
But I guess it's not possible to realize a scenario without ID.
For example where do you want to configure you File Adapter?
Regards
Patrick
Edited by: Patrick Koehnen on May 21, 2008 1:31 PM

Status of message in case of file-xi-idoc scenario

In file2idoc scenario, i have 500 records, how to check the records reached or not (except SXMB_MONI & IDX5)?

palnati,
RWB run time workbench.
or
http://<yourserver>:<port>/MessagingSystem
Regards
Sreeram.G.Reddy

Suggestions for File to IDOC Scenario

Experts,
Here is the requirement A Legacy System will Produce the Customer data file and we have to transform certain data and post it to DEBMAS.
As Part of the information in the file there is a field Which could have a value Update,Amend or Delete.
My Question is How do it handle this.
Please give me your valuable thoughts.
Is it Possible to go for File2IDOC here?
Thanks
Vasu.

Hi Vasu,
If Customer data file is of type xml then file to IDOC scenario is preferable.
Else you have to convert Customer data file to xml first and then proceed for that you can use content converson feature of File Adapter.
The information for Update,Amend or Delete will be provided by customer or you have to decide it based of data in table?
if it is provided by customer then you can go for ABAP Proxy for that take help of ABAPers.
If you have to decide the Update,Amend or Delete logic.
Then fetch the data from table compare it with incoming data decide the Action and then perform the action this can also be handled in ABAP Proxy.
Reward Points if HElpful
Thanks
Sunil Singh

Error handling using fault message type in outbound synchronous ABAP proxy

Hi,
We've a scenario, outbound synchronous ABAP proxy to synchronous SOAP receiver. The requirement is to send multiple records in a single rquest and get response for all the records sent (in the same response message).
Say if I send 10 records from ECC, I should get 10 records as response from SOAP to ECC. But the problem here is, there could be some invalid requests, for which an invalid error status code should be sent as part of response.
Source Structure
Req_Proxy
    req (0..unbounded, string)
Response Structure
Resp_SOAP
Resp (0..Unbounded)
       respString (0..1, String) (carries the actaul response message)
      status code (0..1, String) (carries the status of the response, for ex, 001 (successful), 002 (error))
And now we are planning to make use of Fault Message Type, to track the errors from SOAP (status code 002). But, we are not sure on how to track this for all the requested records. Is it possible to track the errors for all the requested records in a singe call using fault message type? For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8 for valid and 2 for invalid accordingly.
Please calrify.
Thanks.
Rohit

For eg if 8 records are successful and 2 are invalid, then we should get 10 records in response 8
for valid and 2 for invalid accordingly.
Check if you can modify the WSDL structure to include an error node that would get populated incase of invalid entries....this would mean that you get the success and failure details in the single message....also at the proxy-end make the necessary change in your DT.....may be then you do not need to use the fault message...
Regards,
Abhishek.

Using Fault Message Type in BPM

Hi,
In my BPM Scenario, I am using a synchronous send step in which I am using a fault message type.For giving the container for the fault message in the Properties area of the send step, I want to define a container corresponding to the Fault message Type I have already defined.How can I achieve this since it is not possible by defining an Abstract Interface? Can someone please explain how to do this?
Thanks and Regards,
Soumya.

Hi Soumya,
Here are the links for two threads. one has discussed fault mssage type in bpm and the other the general application of a fault message type.
thread1:- Alert monitoring and fault message types
thread2:- fault message in BPM process
Regards,
Sushumna

Is it mandatory to use a Fault Message Type.

Hi all
I am currently doing a Soap-Proxy synchronous scenario,where by sending an employee id through webservice to SAP ECC ,employee details will be retreived from ECC as a response.
In this scenario, is it necessary to specify the Fault Message Type in the outbound and inbound synchronous Message interfaces and do the corresponding message mapping for Fault message types.
Asvance Thanks,
Ram.

Hi ram,
It is not at all mendetary to use Fault message in ur case.Usually it depends upon requirement.If client want's to implement ...u have to use.
generally fault messages are used wen u want to catch some exception viz. ECC server is down,Employee ID does not exist.,No record found for the given EmpID etc....ect.......
See these to know more abt fault message type and its implementation........
Fault message implementation.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
How to Guide
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40574601-ec97-2910-3cba-a0fdc10f4dce
With Integration Scenario
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/52398597-0601-0010-868a-fd95f8061d85
How to Guide - Using Web Service
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f027dde5-e16e-2910-97a4-f231046429f2
Presentation
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9f2ad490-0201-0010-a1bd-81d072f3c5ca
Regards
Biplab
***Reward with points if it helps you!!

What is the message type and basic type used for catsdb in idoc help me

what is the message type and basic type used for catsdb in idoc help me
ANY IDOC FOR CATSDB PLEASE TELL,
Regards,
Jagrut BharatKumar Shukla
points will be awarded

Hi,
Check these message types.
ATT_ABS_WITH_COST and WORKSCHED_WITH_COST.

ABAP provider proxy error using Fault Message Type

Hello experts,
I'm using a provider ABAP proxy with a fault message type in the inbound service interface.
In the ABAP code on the backend system, I need to fill a database table.
in case the record exist --> fault + message back to SAP PI to be alerted.
I do this with a RAISE EXCEPTION TYPE.
I generated all necessary proxies.
The error I got on the backend system (SXMB_MONI) is this:
Application Error - Call Inbound Proxy
SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="xxxxx">FMT_xxxxxx</SAP:ApplicationFaultMessage>
<SAP:Stack>The application triggered an exception</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
Can it be that I need to use something else instead of the RAISE EXCEPTION TYPE. to get something back to SAP PI?
Now the error is logged in SXMB_MONI on the backend system.
Please advice.
Thanks a lot
Dimitri

Hi Dimitri,
Check out these links -
1. /people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
2. http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Sunil Chandra

Hi all!How to use the fault message types

Hi all, i am new beginner on XI.
I have read the introduction in SAP Library about
fault message types
but the steps of how to use fault message are clear
could you help me?
could you give me some guide or docs or links?

Hi,
These might help you:
http://help.sap.com/saphelp_nw04/helpdata/en/f3/c26c3cbfac384fe10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm
Regards,
Chandra

Message has error status at outbound side File To Idoc Scenario

hi ,
In my File to Idoc scenario , when i go to sxmb_moni , i found that its showing red flag at Outbound Status Tab and showing message "Message has error status at outbound side".
When i go to IDX5 and and select my idoc and click on Transaction Id it shows "Password logon no longer possible - too many faile" .
Please suggest what may be the problem ?
Regards,
Rohit

1. First check the RFC destination name used in receiver Idoc adapter communication channel.
2. As i said earlier, in sm59 transaction in XI gui, u can check same rfc destination under type 3. There check the logon credentials and the username.
3. Now goto the R3 system GUI and check in su01 that same user is locked or not. If locked unlock it.
4. And if u change the password of that user, then do the similar change in XI -> sm59 -> rfc destination logon credential
Regards,
Prateek

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

Doubt on technical systems and fault message types

Hi,
 I had still doubt & i'm not clear to answers i got yesterday , plz clarify my doubts
 1.what are fault message types and how do we catch any exceptions in file to proxy scenario , can any one give simple example ?
 2.How do we register a non-sap system(FTP SERVER) in SLD ? what steps should we follow? Does any one have blogs regarding this?
 Plz answer to this questions, good answers will be rewarded.

Hi Smitha,
1. what are fault message types and how do we catch any exceptions in file to proxy scenario , can any one give simple example
Fault Message are Msg type that provided whenever u create a namespace..they are usually used to get the exception or error mapped which has occured while execution of Application at the sender/receiver end....
One scenario where i had used it from Soap to RFC where i defined the exception in rfc source code at r/3 end...I mapped that exception to Fault msg type that i created of my own type(didnt used the default)..
Refer this for Fault msg usage in Asynch scenarios.
/people/shabarish.vijayakumar/blog/2006/11/02/fault-message-types--a-demo-part-1
Refer this for Fault msg usage in Synch scenarios.
/people/sap.user72/blog/2006/01/16/xi-propagation-of-meaningful-error-information-to-soap-client
Refer this for Handling Exceptions
http://help.sap.com/saphelp_nw04/helpdata/en/33/4a773f12f14a18e10000000a114084/content.htm
2.How do we register a non-sap system(FTP SERVER) in SLD ? what steps should we follow? Does any one have blogs regarding this?
For this you have to define the 3rd Party TS & BS in sld.
Have a look at the following links...
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/0aad3efa11b300e10000000a114084/frameset.htm
Cheers...
Vasu
** REward POints if found useful **

Fault message type using in File to IDoc Scenario

Similar Messages

Maybe you are looking for