Question

New Inbound DELSCH Configuration - Receive Failed?

  • 1 June 2020
  • 3 replies
  • 228 views

Badge +2

Hi all,

I am trying to configure a new inbound EDI process to receive customer orders into our IFS 10 UPD 4 setup after being converted from VDA 4905/4915 to EDIFACT DELSCH XML. The  first part of the process works ok (ReceiveCustomerSchedule) but the second part fails (LoadInboxMessage).

The error text is:

XMLPARSE_NAME:View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST at [2:1] 
Caused by: ifs.fnd.record.serialization.FndXmlRecordParser$ViewNameMismatchException: XMLPARSE_NAME:View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST at [2:1]

I have configured:

  • [Our ID at Customer] in Customer
  • Add DELSCH config to Message Setup in Customer
  • Configured Routing Rules - Inbound

Can anyone give any pointers as to what “View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST” might refer to?

Thanks in advance.


3 replies

Userlevel 5
Badge +11

Hi @RoryClark,

This is an exact copy of my question which received no responses? But rewording the heading and question resulted in a longer discussion here.

This issue has been reported to IFS as I believe it is a bug.

Badge +2

Hi all,

I am trying to configure a new inbound EDI process to receive customer orders into our IFS 10 UPD 4 setup after being word to pdf converted from VDA 4905/4915 to EDIFACT DELSCH XML. The  first part of the process works ok (ReceiveCustomerSchedule) but the second part fails (LoadInboxMessage).

The error text is:

XMLPARSE_NAME:View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST at [2:1] 
Caused by: ifs.fnd.record.serialization.FndXmlRecordParser$ViewNameMismatchException: XMLPARSE_NAME:View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST at [2:1]

I have configured:

  • [Our ID at Customer] in Customer
  • Add DELSCH config to Message Setup in Customer
  • Configured Routing Rules - Inbound

Can anyone give any pointers as to what “View name mismatch: SCHEDULES != IN_MESSAGE_REQUEST” might refer to?

Thanks in advance.

thank you my issue has been solved

Userlevel 5
Badge +11

 

thank you my issue has been solved

 

Can you tell us how it was resolved?

Reply