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:
-
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.
-
Run a forcible synchronization (options
Synchronize objects forciblyandRebuild links for the latest versions forcibly) of the TPM registry for the source CPI agent from theChange Tracking Tool → Tracked Objectspage - 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. -
Transport the business entity again, and activate the entry of the target’s purpose in TPM.
|
The |