Skip to Content
0
Former Member
Nov 28, 2011 at 10:12 AM

file2file scenario - NO_MAPPINGPROGRAM_FOUND

47 Views

Hi,

I got file to file scenario with message mapping. (i am changing

structure of input file using message mapping).

I got configured file adapter with content conversion to generate

input XML message on outbound interface and similar way inbound

interface to generate csv file from output xml message.

I got set Operation Mapping on Interface Determination screen.

There is also assigned Message Mapping to Operation Mapping which

makes conversion of input message to output one.

Everything works fine. Output file is generated with remapped

content. So work is done as should be.

But PI still generates following error message:

http://sap.com/xi/XI/Message/30" xmlns:SOAP=" http://schemas.xmlsoap.org/soap/envelope/">

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

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

<SAP:P1>Object ID 11E1D7B1A49E3A1EA7D73CEE6766F224 Software Component 1B5DC810B90911E0B144F495C2A02DE4</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Mapping program is not available in runtime cache: Object ID 11E1D7B1A49E3A1EA7D73CEE6766F224 Software Component 1B5DC810B90911E0B144F495C2A02DE4</SAP:Stack>

</SAP:Error>

I dont know how to get rid of this error. I tried to delete mappings

and create them again. Also with different names. It's still the same.

I have found out, the same error is generated, when i delete

Operation Mapping from repository, but dont delete it from Interface

Determination screen. (so PI is referring to nonexistent object)

Difference is only that output file is not generated in that

case. It is logical, because mapping really dont exist.

But why the same error is triggered when mapping exist and output file

is correctly created?

Is there any way how to find out, which mapping program PI is looking for?

I also tried to create FaultMessage and assign it to inbound

interface, but it didnt helped.

Is necessary to create any mapping for that FaultMessage? If so, then

how?

Or is problem somewhere else?