Exeception Handling

[Former Member]

Hi all,

I am using a BAPI "CCAP_ECN_CREATE" to create a change number, this BAPI has two response messages like one for the Successful creation of the change number and other to throw any execeptions while executing this BAPI. Now while executing this BAPI thro' SAP XI, I have created the normal flow using this blog "https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file%28without+bpm%29" but I am not able to get the required output and it throws an exeception in MONI

like (In Request message mapping)

<SAP:Category>Application</SAP:Category>

<SAP:Code area="RFC_ADAPTER">APPLICATION_ERROR</SAP:Code>

and also

" <SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>

<SAP:P1>Object ID F4802E69C70B3A27B9DFFEF504252607 Software Component D84621B148DD11DDB501D48DAA290035</SAP:P1> "

I am not aware of how to handle the execeptions(Fault messages) while using BAPI's.

Please provide inputs.

Regards,

Nithiyanandam

[Former Member]

hi,

chk ur mapping program using the test tab.

Regards.

Siddhesh

[Former Member]

Hey,

you can use a BPM and use the fault message in the applicaiton error field of the send step.

based on the application error you can trigger an exception.

regards,

Milan

[Former Member]

Hi,

I think I dont need a BPM process to trigger exeception, because the BAPI itself can through the exeception, I just need to capture that in my response, If successful I need to capture the success message else the exeception message.

please check with the BAPI name which I provided, it handles the execption on its own.

Regards,

Nithiyanandam

[Former Member]

Hi All,

Please provide some inputs...

Regards,

Nithiyanandam

[Former Member]

Hi Nithya,

Check this help link....

http://help.sap.com/saphelp_nw04/helpdata/en/5d/a45c3cff8ca92be10000000a114084/frameset.htm

you can fill you fault maessage class using the BAp return.

CALL METHOD cl_proxy_fault=>raise

EXPORTING

bapireturn_tab = < Table with BAPI Return Information>.

Reagrds,

Sunil.

[Former Member]

Hi

To kick off , try doing an SXI_cache refresh

regards

krishna