Fault Message with blank fields

[Former Member]

Hi all,

We're making a WS->RFC syncronous scenario. In the called BAPI our ABAP developer has declared an Exception, and I've imported the RFC .Exception datatype, which includes a stantard structure, with: name, field, message and attributtes. When we try to call the WS (making the exception to be thrown), we got in the response only the name (NO_EXISTS, the exception name) and text fields, and the text is the same that the name...

How can we send a custom message for response? For example Name=NO_EXISTS Text='The country doesn't exist'.

Thanks in advance.

[Former Member · Accepted solution]

HI,

In XI you could do the Message mapping of Fault Message Type to RFC.response.

And the response coming from RFC could be mapped with the Message text with using FixValues.

Here you could mention if RFC response is NO_EXISTS Then message 'The country doesn't exist' should be passed.

See below links

http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm

Thanks

swarup

[Former Member]

Hi

Finally, we'll return the exception message on the export items. its easier for all of us..

Thank you!

[Former Member]

Hi,

Check this option in RFC adapter.

Advanced Mode

For SAP systems (with and without load balancing) and also for external RFC servers, set the Advanced Mode indicator to show additional configuration options.

Parameter

1) Send 'Confirm Transaction'

Only deactivate the indicator if you do not want the transaction confirmation signal (Confirm TID) to be sent after a transactional RFC call.

2)Commit Control for Single BAPI Calls

If you want to use this communication channel to call BAPIs as remote-enabled function modules that change data in the database, set the indicator.

If executed successfully, the transaction is written to the database by calling the function module BAPI_TRANSACTION_COMMIT explicitly. If an error occurs, the transaction is rolled back by BAPI_TRANSACTION_ROLLBACK.

The result is determined by the value of the field TYPE in parameter RETURN. If successful, the tables are empty and the values “”, “S”, “I”, and “W” are displayed. All other values are regarded as errors.

To change this setting, set the indicator BAPI Advanced Mode.

In the Successful RETURN-TYPE Values table, enter the values that should lead to a successful execution.

3) Table

You can also specify additional parameters of the class JCO.Client for the adapter configuration.

Enter the name and values of the parameters in the table displayed

http://help.sap.com/saphelp_nw04/helpdata/en/c8/e80440a832e369e10000000a155106/content.htm

Regards,

Phani

Reward Points if Helpful

[VijayKonam]

Eneko,

This data must come from R3. In the RFC definition, while defining the Exception the developer has to provide the text description. If thats not possible and this is the only exception that the RFC throws, you have to hardcode it in XI mapping.

VJ

[Former Member]

Hi VijayShankar,

Umm, and how the developer can set the text in R3?

Thanks in advance.

[VijayKonam]

That must be the ABAPers task.. he must be aware of that..!! I guess he has to change RFC configuration on R3.

VJ