Error: Message interface is not used by this process Netweaver PI 7.0

Question

Hi All,
I am receiving this error in file to idoc scenario. The file is being picked up by communication channel. Then through an interface mapping IM_MET_ROUTE is being forwarded to a BPM MET_FILE_ROUTE. The MET_FILE_ROUTE forwards it to different BPM depending on file type. whenever I am posting a file it is not reaching IM_MET_ROUTE and giving an error  as shown below.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--
Call Adapter
  -->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIAdapter</SAP:Category>
  <SAP:Code area="BPE_ADAPTER">MESSAGE_NOT_USED</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>Message interface is not used by this process</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
Can you please suggest any solution to remove the error.

Answer 1

Hi All,
Thanks a lot Vikrant for your suggestion. The error is resolved. This was not a configuration problem. This was a design problem. Initially I also looked for configuration changes but that was correct hence I came to conclusion that this might be a design isuue.
   These are the steps that we should follow to resolve the errors
1. First Check your configuration again and again with test tool and payload to find where exactly your configuration is failing.
2. The above step will not be successful since we are already receiving the error.
3. The above test will fail in interface determination step.
4. Please go through the interface determination in Integration repository(PI 7.0).
5. Check whether all interface mapping,source and target message interface are proper or not.
6. if receiver or sender of message is an BPM please look into their receiver and sender element message type.This must match with the one specified in Interface mapping defined within Integration directory( in the interface deterination step).
   In my case the sixth step above was the solution.