RFC exception error..

[former_member238007]

Hi,

My scenario is File to RFC in which i am getting the below exception error

In the receiver side i have configure a file adapter as a sender communication channel and included the module configurations also..

i have configured the scenario based on this link ..

*"https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/file-rfc-file%28without+bpm%29*

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

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

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

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="urn:sap-com:document:sap:rfc:functions">CCAP_ECN_CREATE.Exception</SAP:ApplicationFaultMessage>

<SAP:Stack />

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

in additon to these

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">

<SAP:Category>XIServer</SAP:Category>

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

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

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Interface mapping Object ID F4802E69C70B3A27B9DFFEF504252607 Software Component D84621B148DD11DDB501D48DAA290035 does not exist in runtime cache</SAP:Stack> *

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

we have cleared all the caches

For Material and BOM creation scenarios it is working fine but for this change number scenario we have an another structure to handle CCAP_ECE_CREATE.exception, unable to use this structure, is it required or can it be left..

regards,

Kishore

[Former Member]

Hi,

It seems your mapping is not active or there is a wrong mapping in interface mapping. In Interface mapping check if you have added the right mappings in Request and Response Tab.

Regards,

Sarvesh

Edited by: Sarvesh Singh on Oct 7, 2008 1:51 PM

[former_member238007]

Sarvesh,

i have checked the mapping and interface mapping, everything is fine overther and the next thing i have used mass mapping.. So, every field in the source structure and the target structure is mapped one to one..

regards,

Kishore

[Former Member]

Well it seems the problem in RFC, re-import the RFC "CCAP_ECN_CREATE" and do the mapping again.

Refresh the cache after that and try.

[dharamveer_gaur2]

Refresh full CPA cache refresh, your mapping not exist in cache. might be you changed something and that is not reflecting your cache.so refresh your CPA cache.

Edited by: Dharamveer Gaur on Oct 7, 2008 10:40 AM

[Former Member]

Hi,

Please check the Communication Channel for RFC Receiver in RWB. There you will get the exact error that have raised for this RFC.

It may be the authorization problem while calling the RFC.

thanks

Swarup

[former_member238007]

Sarvesh..

I have done that but sarvesh what is the use of CCAP_ECN_CREATE.exception, what is the use of these, is these to be used in fault message types,

if it is used how to do the mapping..

regards

Kishore

[Former Member]

Hi,

yes, CCAP_ECN_CREATE.exception need to map with fault message type. Create the fault message type. which will have the standard data type. use it or create the custome one and add as additional data type in it.

thanks

Swarup

[Former Member]

Are you using the same RFC for BOM creation too. Can you plz throw some light on your scenario, I have seen the link which you have sent in your ques. So what RFC/RFCs you are using in this scenario.

And yes for CCAP_ECN_CREATE.exception you need to create the Fault messge.

[former_member238007]

Sarvesh /Swarup,

Can u elaborate on fault message type, how to declare it and how to use with CCAP_ECN_CREATE.exceptiion,

actually this BAPI is used for creating changing numbers for the existing BOM's..

My doubt during successfull execution it gives response and if any errors if it throws then this exception should handle those errors.

for other BAPI's such as BAPI_MATERIAL_SAVEDATA does not contain any exception structure, so response structure itself handles those errors but where as for these it defers..

Reimported the BAPI and checked same error..

regards,

Kishore

[Former Member]

Hi,

The Fault Message Type is created seperately.

Please refer below step wise comments

http://help.sap.com/saphelp_nw04/helpdata/en/dd/b7623c6369f454e10000000a114084/frameset.htm

thanks

Swarup

[former_member238007]

Hi,

Can we use fault message types for the Synchronous scenarios..

regards,

Kishore

[Former Member]

This thread will clear few of your doubts..