Integration Center - OData API upsert - PaymentInformationV3 and PaymentInformationDetailV3

[jcaceres]

Hi Community

I need your help to solve the following problem, when we import changes to bank information through the integration center.

If the new change is with a different date than the date of the initial record, the system generates the new record with sequence number 1 and assigns a new external code, but keeps the previous record with sequence number 0 within this new record.

According to SAP recommendations (KBA 2543260), the integration for Payment information only accepts Full Purge and the date of the modification must be the same as the initial registration of the employee.

If we run the integration with full purge, it clears the history of the records and when the data is replicated to payroll, it sends error.

To solve this error we must manually change the new date with the old date. Only that for our client this is not possible since the integrations run with automatic programming and the modifications in Bank data will always come with a different date.

Someone has had this same problem and been able to fix this other than with Full Purge.

thanks for your help

[EmiliaMihaelaA]

Hello Janeth,
Did you found any solution to this problem? We are trying to create an api call to upsert new effective dated record in Payment Information. We understood api is working only with full purge but we can't recreate existing old effective dated records, since effective end date is not api updatable and we have no clue how to create the message,

Thanks