Configuration for System Refresh of BW/BW Source Systems. (landscape configuration after system copy). The position of the BDLS task in the middle of the task list is on purpose. The BDLS conversion must run before most BW configuration tasks. However, some cleanup tasks require the old logical system. Screen Shot Of some transaction to compare after Refresh 1. STMS: Transport Domain, System Overview, Transport Configuration, Transport Parameter 2. SCC4: Client status open / close. AL11: Transport directory location othe location. RZ03: Operation Mode, Current work process status, instance and startup profile location from instance.

1. Tms Configuration After System Copy
2. Stms Configuration After System Refresh Dns
3. Stms Configuration After System Refresh Optive
4. Stms Configuration After System Copy

Symptom

• You have a Process Orchestration (PO) system with multiple Integration Flow (Iflow) or Integrated Configuration (ICO) interfaces
• You have also configured at least one 'Wildcard ICO' (see note 2277886) which is also working fine.
• If you execute a Full CPA Cache refresh, then these interfaces may stop working
• In this case, we are documenting the error from an ABAP Proxy -> PO scenario using SOAP Sender channel in XI 3.0 mode
• If you take the XPI Inspector Example 50 (By Channel) trace you will see an error like:
  com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the message's header fields
  com.sap.engine.interfaces.messaging.api.exception.ConfigException: No sender agreement configured that matches the messages header fields
  
• The error visible in transaction SXMB_MONI in the backend proxy sending system is similar to below:
  <SAP:Code area='INTERNAL'>CLIENT_RECEIVE_FAILED</SAP:Code>
  <SAP:P1>Configuration error on Adapter-Framework(AFW)-Server</SAP:P1>
  <SAP:P2>com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=<Sender_Component>;TS=;AN=<your_interface>;ANS=<your_namespace>;</SAP:P2>
  <SAP:P3>Please check configuration for SOAP/XI sender agreement</SAP:P3>
  <SAP:P4/>
  <SAP:AdditionalText/>
  <SAP:Stack>Error while receiving by HTTP (error code: Configuration error on Adapter-Framework(AFW)-Server, error text: com.sap.aii.af.service.cpa.CPAObjectNotFoundException: Couldn't retrieve inbound binding for the given P/S/A values: FP=;TP=;FS=<Sender_Component>;TS=;AN=<your_interface>;ANS=<your_namespace>;) Please check configuration for SOAP/XI sender agreement </SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>

Read more...

Environment

Product

Keywords

Tms Configuration After System Copy

Process Integration, PI, Process Orchestration, PO, NetWeaver, XI, AEX , KBA , BC-XI-CON-AFW-AAE , Advanced Adapter Engine , Problem

Stms Configuration After System Refresh Dns

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Stms Configuration After System Refresh Optive

Search for additional results

Stms Configuration After System Copy

Visit SAP Support Portal's SAP Notes and KBA Search.