newly added field cause BPM automated activity fail

Hi everyone, I am investigating an issue now:

My environment is NWDS SP14.

I designed a BPM which was working: a message triggered the BPM, the subsequent automated activity have sync call to ECC.

Now I need to additional a field (it was called "filename" then later I renamed to "FileName", the datatype is defined in namespace of http://xxx/data), I modified ESR for data type.

Then I imported the service interface into Composite Designer, from BPM side, I can see the newly added field showing up.

However, the runtime failed at the automated activity:

JPR failed to transfer the request message to the messaging system. Reason: com.sap.aii.utilxi.xmlvalidation.impl.XMLValidationException: XML Validation for payload with root element name CorePay_BPM_Out , target namespace http://xxx/data Failed!Errors Encountered During Parsing
  1.cvc-complex-type.2.4.a: Invalid content was found starting with element 'FileName'. One of '{filename, JournalGroup}' is expected.

It seems like the BPM did not take this schema change.

Any idea ?

Thanks

-Liang