Error on sender FCC: InterfaceDetermination did not yield any actual intfc

[Former Member]

Hi Experts,

I am developing a File to Proxy scenario. Sender File adapter with FCC has been configured as required with the Fixedfiled lenghths and filed names. On trying to execute the i/f by placing the source file at the desired location; Sender Communication channel throws the following exception: Error: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface. I am using the iNtegrated configuration object on PI 7.3 and Ic has been configured correctly too.

the adapter logs look as follows:

18.10.2011 08:20:46 Information Channel CC_BOURQUE_AccrualTransactions_FILE_Sender1: Converted complete file content to XML format

18.10.2011 08:20:46 Information Channel CC_BOURQUE_AccrualTransactions_FILE_Sender1: Send binary file "D:\Interfaces\ITF\07\Out\freight_export.dat", size 46538 with QoS EO

18.10.2011 08:20:46 Information MP: processing local module localejbs/CallSapAdapter

18.10.2011 08:20:46 Information Application attempting to send an XI message asynchronously using connection File_http://sap.com/xi/XI/System

18.10.2011 08:20:46 Error Returning to application. Exception: com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface

18.10.2011 08:20:46 Error MP: exception caught with cause com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface

18.10.2011 08:20:46 Error Attempt to process file failed with com.sap.aii.adapter.xi.routing.RoutingException: InterfaceDetermination did not yield any actual interface

Please guide me if I am missing on anything.

Regards,

Elizabeth

[Former Member]

hello Jacob,

Could you able to resolve this issue.

what was the solution , this error was occurring when we remove the XML name space from Message type

Ram

[markangelo_dihiansan]

Hello,

Before you do an ICO, make sure that the file is correctly converted using FCC. You just need a file sender comm channel and a sender agreement. See in sxi_monitor if the text file is converted correctly and then proceed to using ICO.

Hope this helps,

Mark

[Former Member]

Hi Mark,

On trying to post the file to Proxy using the RD, ID SA and RA the adapter does not thrwo an error now and the messge has been passed through. However the payload genertaed using the FCC does not geenerate the source XML messgae with the correct start tags. PI expects the start tag to be:

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

<ns0:MT_AccrualTransactions xmlns:ns0="http://cf.com/sap/pi/RTR/I09/InboundAccrualTransactions">

whereas the FCC generates a start tag as

<?xml version="1.0" encoding="utf-8" ?>

- <MT_AccrualsTransactions>

and hence the message fails with Mapping Error: MAPPING:EXCEPTION_DURING_EXECUTE in the Integration Engine.

How can this be resolved?

Regards,

Elizabeth

[markangelo_dihiansan]

Hello,

<?xml version="1.0" encoding="utf-8" ?> 
 <MT_AccrualsTransactions>

What you can do is:

1. Go to the MT_AccrualsTransactions message type

2. Edit

3. Remove the entry under XML namespace

4. Save and activate

Hope this helps,

Mark

[Former Member]

Hi Mark,

Have removed the namespace from the message type. Still the same issue occurs for mapping.

On trying to copy and use the source payload on the Message mapping test tab, the source structure is reflected with all the elements and nodes in red.

Following is how my source payload looks like:

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

<MT_AccrualsTransactions>

<Accruals>

<Row>

<BillOfLadingNumber>21776</BillOfLadingNumber>

<CarrierCode>VB</CarrierCode>

<ChargeTypeInterface>FO</ChargeTypeInterface>

<CreateDate>07-01-201107:45:22:303</CreateDate>

<Amount>28830.51</Amount>

<Currency>U</Currency>

<ExportDate>07-01-201107:45:24:070</ExportDate>

<VendorCode>105106</VendorCode>

<CustomData1>5140200-1000000</CustomData1>

<CustomData2>6635</CustomData2>

<CustomData3>88846</CustomData3>

<CustomData4>5 2011/</CustomData4>

<CustomData5>01/31</CustomData5>

<CustomData6>034</CustomData6>

<CustomData7></CustomData7>

<CustomData8></CustomData8>

<CustomData9></CustomData9>

<CustomData10></CustomData10>

<ReferenceNo></ReferenceNo>

<EquipmentInitials></EquipmentInitials>

<EquipmentNumber>B MTC723</EquipmentNumber>

<ShipDateTime>01</ShipDateTime>

<OrderNumber>-29-201107:00:00:000U88714</OrderNumber>

<ShippedQty></ShippedQty>

<ShippedUOM></ShippedUOM>

<OrganizationCode/>

<AccrualDate/>

<EOF/>

</Row>

</Accruals>

</MT_AccrualsTransactions>

What could be wrong?

Regards,

Elizabeth

[Former Member]

Hi mark,

It was an issue with the message type name that was set incorrectly in FCC.

FCC was configured with MT_AccrualsTransactions instead of MT_AccrualTransactions.

Hence the error .

[markangelo_dihiansan]

Hello,

As a general rule, always check your FCC first Can this thread be closed now?

Regards,

Mark

[Former Member]

Hi Mark,

Unfortunately, the Runtime Mapping error still persists..

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

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

<SAP:P1>com/sap/xi/tf/_MM_BOURQUE_TO_SAP_AccrualTransacti~</SAP:P1>

<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>

<SAP:P3>on: Cannot create target element /ns0:MT_AccrualTr</SAP:P3>

<SAP:P4>ansactions_Proxy. Values missing in queue context~</SAP:P4>

<SAP:AdditionalText />

<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_BOURQUE_TO_SAP_AccrualTransacti_{; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_AccrualTransactions_Proxy. Values missing in queue context}</SAP:Stack>

~Elizabeth

[markangelo_dihiansan]

Hello,

<SAP:P3>on: Cannot create target element /ns0:MT_AccrualTr</SAP:P3> 
<SAP:P4>ansactions_Proxy. Values missing in queue context~</SAP:P4> 

This should be a mapping error. Check your message mapping by loading the output of the fcc in message mapping.

Hope this helps,

Mark

[Former Member]

Hi,

The FCC parameters that I have configured are as follows:

Document name: MT_AccrualTransactions

Recordset name: Accruals

Recordset Structure: Row, *

Recordset Sequrnce: Acending

parameters:

Row.fieldFixedLengths = 30,4,15,22,13,1,22,10,25,25,5,25,25,25,25,25,25,25,30,10,30,22,30,10,3,15,22,1

Row.fieldNames = BillOfLadingNumber,CarrierCode,ChargeTypeInterface,CreateDate,Amount,Currency,ExportDate,VendorCode,CustomData1,CustomData2,CustomData3,CustomData4,CustomData5,CustomData6,CustomData7,CustomData8,CustomData9,CustomData10,ReferenceNo,EquipmentInitials,EquipmentNumber,ShipDateTime,OrderNumber,ShippedQty,ShippedUOM,OrganizationCode,AccrualDate,EOF

Row.processFieldNames = fromConfiguration

Row.lastFieldsOptional= YES

Do i need to configure any other parameter?

Regards,

Elizabeth

[Former Member]

you can remove

Row.processFieldNames = fromConfiguration

as you already have mentioned field names.

Regards

Raj

[Former Member]

Hi Raj,

Eevn on Removal of the paramter the earlier message mapping exception still exists

Regards,

Elizabeth

[Former Member]

Elizabeth

InterfaceDetermination did not yield any actual interface

It seems to be error in interface determination. Please check the conditions mentioned in Interface determination.

check the interface to process the message in ID.

Also check the message before the error step. You can see the payload in sxmb_moni. expand the tree in left pane above the error node and check the payload.

Regards

RajCheck

[Former Member]

Hi Experts,

Was facing similar issue with FCC. This post has helped me as I have mentioned wrong MT in configuration.

Thank you

Hardik