B2B troubleshooting

This page collects the B2B symptoms that aren’t resolved by repeating the action that produced them.

1. Transported security configuration can’t be activated

Symptom. After a DevOps transport of a company, subsidiary, trading partner or communication partner, its security entries are listed in the target tenant’s TPM but can’t be activated. Activation fails with:

Cannot read resource with ID : <User Account>. Cause Not Found from Configurations service

Publishing the entry can fail instead with a message about a null value for SAP_AS2_Inbound_Private_Key_Alias. Editing the entry in the SAP UI doesn’t help.

Cause. Figaf Tool before 2609 wrote these entries into the transport archive keyed by their Alias. SAP identifies them by a different field - an AS2 Inbound Decryption Configuration of a company or subsidiary by its User Account, a Signature Verification Configuration of a trading or communication partner by its AS2 Partner ID. After the import SAP can’t find the entry under the key it expects, so the entry exists but can’t be addressed. Entries whose Alias happens to equal that field are unaffected, which is why entries created by Figaf Tool itself kept working.

Fix. Update to 2609 or later, then:

  1. Delete the affected entries in the target tenant’s TPM. A new transport can’t repair them, because the wrong value is their identity in SAP.

  2. Run a forcible synchronization (options Synchronize objects forcibly and Rebuild links for the latest versions forcibly) of the TPM registry for the source CPI agent from the Change Tracking Tool → Tracked Objects page - see Synchronize with an Agent system. Business entities synchronized before the update still hold the old data, so without this step the next transport carries the same wrong key again.

  3. Transport the business entity again, and activate the entry of the target’s purpose in TPM.

The User Account and the Private Key Alias are transported unchanged, and no landscape mapping is needed for them, because each purpose (Dev, Test, Prod) has its own User Account.

2. Agreement with a custom integration flow can’t be activated

Symptom. An agreement created by Figaf Tool whose B2B scenario uses the Custom Integration Flow mapping option can’t be activated in SAP Integration Suite. Activation fails with:

[ERROR] [MISSING_MANDATORY_FIELD]: Mapping is required (field: mapping)

In the SAP UI the scenario looks correct: the Mapping step shows Custom Integration Flow with the right ProcessDirect address.

Cause. An agreement is created from an agreement template, and its B2B scenario is copied from the template’s - including the field that holds the mapping kind. Figaf Tool before 2610 wrote the fields of the mapping it was asked for but left that field at the template’s value, and wrote the custom integration flow address under its legacy name. Since SAP release 2609 the activation reads the mapping kind and requires the fields that belong to it: the field still says Integration Advisor, the MAG fields have been removed, so the activation refuses. The SAP UI converts the legacy address field when it displays the scenario, which is why the scenario looks correct there.

The mirror case passes activation but maps wrongly: an agreement whose scenario uses a MAG, created from an agreement template that itself uses a Custom Integration Flow, keeps the template’s mapping kind and the template’s ProcessDirect address, so it runs the template’s integration flow and ignores the chosen MAG.

2610 sets the mapping kind explicitly for both kinds of mapping - a custom integration flow and a MAG - and removes the fields of the other kind.

Fix. Update to 2610 or later. New agreements activate normally, from the Create agreement dialog and from the PI to CPI B2B migration alike.

Agreements created earlier are not repaired by the update. For each of them, open its B2B scenario in the SAP Integration Suite UI, switch to edit mode, save it without changes - the save writes the new format - then activate it.

An agreement of the mirror case is not repaired by a re-save either, because the scenario is valid as it stands. Open its B2B scenario, set the Mapping step to the intended MAG, save and activate it.