Skip to main content

Hi,

 

We have situation where single CAMT file is loaded to External Payment as multiple records. Multiple Load IDs in External Payment are created for Single External File Transaction Load File ID.

Do you know any specific reason for this? can this be related to Payment Dates?

 

Thanks

Found that when Payment Date is different from Header Date this can happen.

Also found a bug related to this.

135781

153884

 

I’m having the same issue when loading in External Payments.

 

On my ExtCustPayment type external template, I’ve used the COLUMN_REF detail function to ensure 0_START, 1_HEAD, and 2_DETAIL are all the same dates. I’ve tried leaving all date fields out completely and letting IFS use the sysdate/load date and the Load File ID are still splitting out to separate External Payment Load IDs.

 

The Load IDs are being split out at the 1_HEAD grouping level, is there any other possible causes? Or is there a way to have them grouped into a single Load ID? Whether that’s a setting or missing field information?

 

This would be on  IFS 10 Upd 14

 

Thanks

Reply


Terms & ConditionsCookie settings