Troubleshooting Guide ccBPM in PI 7.1

Service Interfaces
Problem
                    You are sending a message to an integration process component. The message is set to error status with the error code BPE_ADAPTER UNKNOWN_MESSAGE.


                    A transformation step or synchronous send step fails with the error message "No definition exists for <Interface Namespace> <Interface Name>" (SWF_XMP 021)."


Analysis
                    Service interfaces have been introduced in SAP NetWeaver PI 7.1 which support multiple operations. The message interfaces known from prior releases are still supported by creating service interfaces of category "XI 3.0 compatible" which restricts them to only provide a single operation, the so-called default operation.

                    Operations are distinguishable by the underlying message type, which in turn has to be defined by a unique root tag and its namespace. Integration processes accessing service interfaces having multiple operations enforce using the correct operation by checking the name and namespace of the payload's root element (root tag). When new messages enter the Business Process Engine (BPE), that is, if a message is received (using a receive step or synchronous send step) or created (using a transformation step), its root tag has to match the operation's message type - otherwise the respective step fails.

                    If messages are not accepted by the BPE with the aforementioned error messages, check whether the actual payload matches the definition of the message type of the operation. With respect to the namespace, the subtle differences between the default namespace (<root xmlns="urn:example:com">), an explicit namespace (<ns1:root xmlns:ns1="urn:example:com">), an empty namespace (<ns1:root xmlns:ns1="">), or a tag without an associated namespace (<root>) are a typical source of error.

                    The requirement of the root tag matching the definition in the Enterprise Service Repository is not enforced for of category "XI 3.0 compatible" service interfaces. This includes scenarios upgraded from SAP NetWeaver '04 or SAP NetWeaver 7.0. On the other hand, in scenarios using service interfaces with multiple operations, the root tag of the payload must adhere to the definition in the ES Repository.


Generic User Decisions - Work Item Title
Problem
                    In the work item list in the Business Workplace, some, or all, of the user decision work items have "generic decision task" as the title instead of the title configured in the process definition.

                    The title of a user decision work item is displayed in a language different from the user's logon language.


Analysis
                    The user's logon language differs from the language with which the work item was created or the title has not been translated into the user's logon language. Due to performance reasons, the work item titles are not translated into the user's logon language by default when viewing the list of work items. Instead, the title is displayed in the language the work item was created with or, if it has not been translated to this language, the default title for user decisions is displayed.

                    Make sure that all necessary translations of the title were provided in the process definition and have been activated. In the Business Workplace, use the menu path Settings ' Workflow Settings ' Personal Settings and select the setting Display Work Item Texts in Logon Language. To change the default for all users, use the SAP reference IMG in transaction SPRO, path Application Server ' Business Management ' SAP Business Workflow ' Basic Settings (Workflow System) ' Change Defaults for Personal Workflow Settings.

Generic User Decisions - Options of the User Decision
Problem
                    In the user decision work item in the inbox, the options are all labeled with the same text so that users do not know which one to choose.

Analysis
                    The user decision texts have not been translated into the language the user is logged on in. Translate the texts of the relevant integration process in the Enterprise Services Builder and activate the changes.


Message Packaging - Reconfiguration
Problem
                    The reconfiguration of one of the integration processes has been started using transaction SWF_INB_CONF. However, the reconfiguration does not finish although no hanging queues are to be found in transaction SMQ2. ccBPM Message Packaging is in use in the system.

Analysis
                    There are still messages to be delivered with the previous configuration. Use transaction SWF_INB_ADM to check for messages in error, suspended messages, or messages with scheduled status. If these messages are no longer deliverable, for example, due to the errors not being recoverable, or because no more delivery attempts are to be made, logically delete them using the relevant administration function. As soon as all pending messages for the previous configuration have reached a final status (either delivered or cancelled), the reconfiguration is processed.


Principal Propagation - Enabling Principal Propagation for a Process
Problem
                    Principal propagation shall be enabled for one of the integration processes. However, in transaction SWF_INB_CONF, the checkbox is missing for this integration process but it is shown for others.

Analysis
                    Integration processes can only propagate the principal of the message starting the process instance. To avoid ambiguity at runtime, principal propagation can only be enabled for processes that do not use correlations (that is, there are no inbound messages besides the starting message). If your process requires using correlations, principal propagation cannot be enabled for this process.

                    If your process has only a single inbound message, but you are still not able to activate principal propagation, check that no correlations are defined or used in the process definition. Remove any correlation definition, usage, or activation and activate the changes made to the process definition. You should now be able to configure principal propagation for this process in transaction SWF_INB_CONF.