3790675 - i_businesspartnertp_3 loop: second commit fails with 'iv_x_save is blank' and address check errors; workaround with bapi_transaction_commit

• When running i_businesspartnertp_3 inside a loop, the first COMMIT ENTITIES succeeds, but the second fails.
• Error: "BUPA_CREATE_FROM_DATA のパラメータ IV_X_SAVE が空白" (parameter IV_X_SAVE of FM BUPA_CREATE_FROM_DATA is '' and must be 'A').
• Error: "Parameter IV_X_SAVE of FM BUPA_CENTRAL_CHANGE is '': must be 'A'".
• Error via API_BUSINESS_PARTNER: code R11/243 "Internal error when calling operation module BUA_CHECK_ADDRESS_VALIDITY_ALL; a check table is missing".
• Error detail: code R1/000 "Error_Time Dependency_Addresses CHECK_TABLE_MISSING".

SAP S/4HANA Cloud Public Edition

1. Implement BP create/update using RAP BO i_businesspartnertp_3 (EML).
2. Process multiple Business Partners in a LOOP.
3. Call MODIFY ENTITIES and COMMIT ENTITIES per iteration (or perform MODIFY ENTITIES per record and a single COMMIT ENTITIES after the loop).
4. Observe: first record commits successfully; on the second commit the errors occur as listed in Symptom.

• A global memory variable in the Business Partner framework (for example, the save/control flag) is not cleared between iterations when multiple create/update operations run in the same session. The RAP save path commits the database unit but does not trigger the BP framework’s global-memory cleanup, leading to IV_X_SAVE not being set and follow-up address buffer/check-table errors.

1. After each COMMIT ENTITIES for i_businesspartnertp_3 (or between two BP processing iterations in the same session), call BAPI_TRANSACTION_COMMIT explicitly to trigger the BP framework’s global-memory cleanup.
2. If feasible for the use case, avoid calling the RAP BO in a tight loop; instead, collect all changes and execute a single MODIFY ENTITIES followed by COMMIT ENTITIES. If a loop is necessary, retain step 1.
3. Apply the same approach for both create (BUPA_CREATE_FROM_DATA) and update (BUPA_CENTRAL_CHANGE) flows.
4. Note: The explicit BAPI_TRANSACTION_COMMIT is a safe, idempotent workaround and can remain in place without side effects until a standard correction is delivered.

• Refer to: SAP Note 1797736 - Error analysis for SAP Gateway

i_businesspartnertp_3, business partner, RAP, EML, MODIFY ENTITIES, COMMIT ENTITIES, BAPI_TRANSACTION_COMMIT, BUPA_CREATE_FROM_DATA, IV_X_SAVE, BUPA_CENTRAL_CHANGE, BUA_CHECK_ADDRESS_VALIDITY_ALL, CHECK_TABLE_MISSING, R11/243, R1/000, api_business_partner , KBA , LO-MD-BP-2CL , Business Partners for Public Cloud , Problem