SAP Knowledge Base Article - Public

3442546 - Lockbox is not automatically processed when imported via API after 2402 release.

Symptom

  • The lockbox file is not automatically processed when importing via API API_LOCKBOXPOST_IN after 2402 release.

Environment

SAP S/4HANA Cloud

Cause

Authorization function area is missing in communication role SAP_COM_CSR_0759 which belongs to communication scenario SAP_COM_0759.

Resolution

  1. Identify communication user for scenario ID SAP_COM_0759 (Scenario: Finance - Accounts Receivable Lockbox Integration) in app Communication Arrangements (App ID F1763).
  2. Create new communication arrangement for Communication Scenario ID SAP_COM_0002 and assign the same communication user in SAP_COM_0759. This will merge the authorization of communication which contains authorization for functional area.
  3. With release 2408, you can go ahead and remove the SAP_COM_0002 user authorization from the SAP_COM_0759.

See Also

Lockbox - Post

Guidelines for configuring Communication Scenario Finance – Posting Integration (SAP_COM_0002)

Keywords

Lockbox, SAP_COM_0759, SFTP server, API, Reprocess Lockbox Items, Functional area, FINS_FKBER_AUTH, Manage Incoming Payment Files, Manage Bank Message, the difference is too large for clearing, SOAP, inbound API, Regression, empty line, Error, Manage Lockbox Batches, API , KBA , FI-BL-PT-US-2CL , US-bank statement/lockbox (Public Cloud) , Problem

Product

SAP S/4HANA Cloud 2402