Receiver determination ErrorH

[Former Member]

hello everyone:

I have created an scenario n XI for a File to File exchange, under SAP XI 7.0 SP10.

Windows 2003 / SQL Server 2000

Using the Test utility under Integration Builder, I manage to do successful tests for my File_output ( inbound interface) but when doing the File_input (outbound_interface) I get an error in the last step:

 
 Sender Agreement
<Not found>
 
 
<Trace level="1" type="B">SENDER AGREEMENT SIMULATION</Trace> <Trace level="1" type="T">Simulating Adapter Engine...</Trace> <Trace level="1" type="T">Simply trying to loolup for the most specific Sender Agreement object</Trace> <Trace level="1" type="T">no objects found</Trace> <Trace level="1" type="T">Note that real results may differ</Trace>
 
 Receiver Determination
<Not found>
 
 
<Trace level="1" type="B">CL_RD_PLSRV-ENTER_PLSRV</Trace> <Trace level="1" type="T">R E C E I V E R - D E T E R M I N A T I O N </Trace> <Trace level="1" type="T"> Cache Content is up to date </Trace> <Trace level="1" type="T">No Relation found - accept given Receivers. </Trace> <Trace level="1" type="E">CL_RD_PLSRV-ENTER_PLSRV</Trace>
 
 Interface Determination
<Not found>
 
 
<Trace level="1" type="B">CL_ID_PLSRV-ENTER_PLSRV</Trace> <Trace level="1" type="T">I N T E R F A C E - D E T E R M I N A T I O N </Trace> <Trace level="1" type="T"> Cache Content is up to date </Trace> <Trace level="1" type="T">...There is no Interface Determination configured for receiver party and receiver service FTP1ALMA </Trace> <Trace level="1" type="E">CL_ID_PLSRV-ENTER_PLSRV</Trace>
 
 Interface Mapping
<Not found>
 
 
<Trace level="1" type="B">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace> <Trace level="1" type="T">No mapping configured </Trace> <Trace level="1" type="E">CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV</Trace>
 
 Receiver Agreement
<Not found>
 
Runtime error
No receiver agreement found for sender -FTP1ALMA to receiver -FTP1ALMA,urn://alex.com/ftp001.FILE_INTPUT_OB
 
 
<Trace level="1" type="B">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace> <Trace level="1" type="T">no outbound binding found. </Trace> <Trace level="1" type="T">No standard agreement found for , FTP1ALMA, , FTP1ALMA, urn://alex.com/ftp001, FILE_INTPUT_OB </Trace> <Trace level="1" type="E">CL_XMS_PLSRV_OUTBINDING-ENTER_PLSRV</Trace>

also under the monitoring on abap side, I get this error:

 <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Receiver Identification 
  --> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIServer</SAP:Category> 
  <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code> 
  <SAP:P1></SAP:P1> 
  <SAP:P2></SAP:P2> 
  <SAP:P3></SAP:P3> 
  <SAP:P4></SAP:P4> 
  <SAP:AdditionalText></SAP:AdditionalText> 
  <SAP:ApplicationFaultMessage namespace=""></SAP:ApplicationFaultMessage> 
  <SAP:Stack>No receiver could be determined</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

I see there's something to do with the receiver determination, even tough that on my Receiver determination branch I did put the Configured receivers and I have the right parameters on the onfiguration overview for receiver determination.

Any ideas what could go wrong?

Thanks

Alejandro

[Former Member · Accepted solution]

Check the Sender Interface and Reciver Interface in the SXMB_MONI (esp URNs). Is this is the same you have configured ? Also you can check this info from SOAP Header in the SXMB_MONI

Also copy the source message structure from SXMB_MONI and use it to test in your IR .Do you see any error.That may explain .

Regards

Bipin Joshi

[Former Member · Accepted solution]

Hello:

Thanks a lot for your answers, there was a mistake but on one of the agreements, however I can't get it to work just yet, I get this Error now:

 <?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="">
  <SAP:Category>Application</SAP:Category> 
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
  <SAP:P1>com/sap/xi/tf/_FILE_TO_FILE_001_</SAP:P1> 
  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2> 
  <SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>com.sap.aii.utilxi.misc.api.BaseRuntimeException thrown during application mapping com/sap/xi/tf/_FILE_TO_FILE_001_: RuntimeException in Message-Mapping transformatio~</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>

Something to do with mapping I guess....

Thanks!

Alejandro

[Former Member · Accepted solution]

In order to debug what is wrong in the message mapping, use the Test Function in the Message Mapping Tool, using the same payload you use in the realtime scenario (you can take the payload from SXMB_MONI)

Regards,

Sandro

[Former Member · Accepted solution]

Go to your payload in the abap monitor, right click and View source. Copy and past this into the test area (Test tab) of your mapping in the Int. Repository.

Jin

[Former Member · Accepted solution]

Alejandro,

Please check the mapping using the test and debugging mode.

It could be due to mapping functions.

regards,

JE

[Former Member · Accepted solution]

I actually had an error on my Message Mappings under Integration Repository. I corrected it but I see an small red thing on one of the nodes. I have this as the datatype:

DATA TYPE

Record

Row

Name

LastName

Age

on both datatypes, and the red thing is placed on the ROW node. When I do the testing using the real payload, I get the same error about mapping

[Former Member · Accepted solution]

Assuming 'Row' is a required target node and it's not getting mapped - thus the red status. To eliminate the error you should map the appropriate source field/node to the Row node depending on how many target Row instances you're looking for.

Jin

[Former Member · Accepted solution]

hello:

It's mapped

[Former Member · Accepted solution]

Do you get any more info on the error during the test mapping when you put the trace level of the test mapping tool at the Debug level?

Jin

[Former Member · Accepted solution]

I get this

19:52:47 Start of test
Document start
Start tag [ns0:FILE_INPUT]
Add raw attribute [ xmlns:ns0="urn://alex.com/ftp001"]
Start tag [Record]
Start tag [Row]
Start tag [FirstName]
Put value [ads]
Close tag [FirstName]
Start tag [LastName]
Put value [sd]
Close tag [LastName]
Start tag [Age]
Put value [asdasd]
Close tag [Age]
Close tag [Row]
Close tag [Record]
Close tag [ns0:FILE_INPUT]
Document end
Executed successfully
19:52:47 End of test

However if I try to upload an XML file with the contesnts of the Payload, it says that the XML file is not wellformed

Thanks

[Former Member · Accepted solution]

Can you paste the content of you actual payload and the content of the test payload you used in this thread?

Thanks.

Jin

[Former Member · Accepted solution]

Hello:

I used my data for a test payload:

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

<ns0:FILE_INPUT xmlns:ns0="urn://alex.com/ftp001">
   <Record>
      <Row>
         <FirstName>Alejandro</FirstName>
         <LastName>De Leon</LastName>
         <Age>24</Age>
      </Row>
   </Record>
</ns0:FILE_INPUT>

The result is:

22:09:58 Start of test
Document start
Start tag [ns0:FILE_INPUT]
Add raw attribute [ xmlns:ns0="urn://alex.com/ftp001"]
Start tag [Record]
Start tag [Row]
Start tag [FirstName]
Put value [Alejandro]
Close tag [FirstName]
Start tag [LastName]
Put value [De Leon]
Close tag [LastName]
Start tag [Age]
Put value [24]
Close tag [Age]
Close tag [Row]
Close tag [Record]
Close tag [ns0:FILE_INPUT]
Document end
Executed successfully
22:09:58 End of test

The actual payload, as seen on the Abap monitoring, that I copy and pasted to use as feed for the mapping test is:

- <ns:FILEINPUT xmlns:ns="urn://alex.com/ftp001">
- <Recordset>
- <Row>
  <FirstName>Alejandro</FirstName> 
  <LastName>De Leon</LastName> 
  <Age>24</Age> 
  </Row>
- <Row>
  <FirstName>Evelin</FirstName> 
  <LastName>Varela</LastName> 
  <Age>21</Age> 
  </Row>
- <Row>
  <FirstName>Hans</FirstName> 
  <LastName>Hahn</LastName> 
  <Age>29</Age> 
  </Row>
- <Row>
  <FirstName>Gerardo</FirstName> 
  <LastName>Borbolla</LastName> 
  <Age>37</Age> 
  </Row>
  </Recordset>
  </ns:FILEINPUT>

The ROW node is set to 1....unbounded. all others are to 1...1

Thanks

Alejandro

[moorthy · Accepted solution]

Hi,

Refer this blog to test the mapping-

/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

Rgds,

Moorthy

[Former Member · Accepted solution]

Hello

I also did that test and I get the same error about mapping issues

Thanks!

alejandro

[Former Member · Accepted solution]

Hi -

There are a few differences here:

- the root node in your test <b><ns0:FILE_INPUT</b>... has an underscore but your actual doesn't

- <b>Record</b> in your test vs <b>Recordset</b> in your actual

You either have to change your mapping and source Message Type that matches your actual payload being sent or change how sender file adapter conversion to match your mapping and source Message type.

Jin

[Former Member · Accepted solution]

I changed the file adapter conversion, I finally have something like this:

Document Name: FILE_INPUT

RecordSet Structure: Row,*

-Parameters-

Row.fieldNames -> FirsName,LastName,Age

Row.fieldSeparator -> ,

Row.processConfiguration -> FromConfiguration

Row.endSeparator -> 'nl'

BTW, I don't know where to change the RecordSet into Record tag.... all my data types are defined with RECORD, not RECORDSET.

I still have the same issue

Thanks!

alejandro

[Former Member · Accepted solution]

One way to resolve the issue what Jin has identified is to delete namespace from Source Message type displayed in text box called 'XML Namespace'

Regards

Bipin Joshi

[Former Member · Accepted solution]

Hi -

In the "Recordset Name" parameter, put the value <b>Record</b> so that it doesn't default to <b>Recordset</b>.

Jin

[Former Member · Accepted solution]

That was the error mapping, messages are passing now.

Thanks a lot!

Alejandro

[Former Member]

Hi -

In your ABAP monitoring, check your message in the first pipeline step (e.g. Inbound Message) and check the SOAP Header under Main. Make sure the Sender and Interface elements match your intended Sender data in your configured Receiver Determination.

Jin

[udo_martens]

Hi Alejandro,

i assume the error is because of missing sender agreement. For your scenario you need a sender agreement, as well a receiver determination, interface determination and a receiver agreement. Compare entries of SXMB_MONI (bus system, interface, namespace) with entries of IB Directory. They are case sensitive.

Regards,

Udo

[Former Member]

Verify that the receiver determination is active in the SXI_CACHE transaction.

Regards,

Sandro