cancel
Showing results for 
Search instead for 
Did you mean: 

Error on Dynamic configuration

manikandan_shanmugam3
Active Participant
0 Kudos

Dear All,

Scenario:File to File

I have tested two files. the first files has processed successfully end - end but second one getting error on receiver channel.

Error: Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: The Adapter Message Property 'FileName' was configured as mandatory element, but there is no 'DynamicConfiguration' element in the XI Message header: com.sap.aii.adapter.file.configuration.DynamicConfigurationException: The Adapter Message Property 'FileName' was configured as mandatory element, but there is no 'DynamicConfiguration' element in the XI Message header

Note:ASMA properties are same for the both sender and receiver channel.i have checked only FileName.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dynamic Configuration happen for one file only.

if you are having multile mapping in your interface and applied dynamic configuration on both mappings .dynamic configuration gonna execute for only one file.for other file it will gonna throw an error.

Please clarify the interface if its using multi-mapping or not.

Answers (2)

Answers (2)

former_member181985
Active Contributor
0 Kudos

check the dynamic configuration header in SXMB_MONI for the message (under SOAPHeader)

former_member200962
Active Contributor
0 Kudos

do you have a mapping inbetween? If yes confirm if the FileName for the second file was generated by the mapping program.

manikandan_shanmugam3
Active Participant
0 Kudos

Hi abhishek,

We are not mapping file name.

Former Member
0 Kudos

Hi,

Error says that the file name is expected but it hasn't received the same from the source...

go to moni and double click the message and check in DynamicConfiguration tab of SOAPHeader of Inbound Payload and check the file name is getting passed or not for both the messages...

if you have kept the same file name on both sides then this error should not occur...

check configuration one more time..

HTH

Rajesh