Show TOC

Defining Communication ComponentsLocate this document in the navigation structure

Use

In the PCK, the communication component is of type Business Communication Component. It represents an abstract, addressable unit. Business communication components are used in cross-company processes, for example, if the parties involved have only published their interfaces and not their system landscape, or it is only partly known.

Using a business communication component, you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.

Procedure
  1. Create a communication component.

    More information: Creating Objects

    Object keys consisting of partner and communication components are assigned.

Defining Communication Components With and Without Party

  1. You can assign a communication component to a party or define it as a Communication Component Without Party.

    Communication components that are assigned to a party are displayed in the navigation area of the PCK under Party in the subtree of the party.

    Communication components that are not assigned to a party are displayed in the subtree as Communication Components Without Party.

Adapter-Specific Identifiers

  1. In the case of particular message formats, the sender and receiver are addressed by special identifiers at communication component level (and not at party level). These identifiers are part of the message header. The following adapter-specific identifiers exist:
    Adapter Type Identifier

    IDoc-Adapter

    Logical system

    RFC Adapter

    SAP system ID and client
    • To display and edit adapter-specific identifiers for a communication component, in the object editor menu bar, choose Object → Adapter-Specific Identifiers.
    • To edit the identifiers, switch to change mode.
    • Specify the names for your adapter-specific identifiers and choose Apply.

Defining Access Control Using Assigned Users

You can restrict access to the runtime environment to specific users for a particular sender communication component. An authorization check is then carried out at runtime prior to inbound processing of the message. This ensures that messages that have the particular communication component entered as the sender in the message header can only be executed in the Adapter Engine by the specified users.

You can use this function in B2B processes to grant your various business partners different users, and then enter these users in the relevant communication components. In this way, you can ensure that for the configured message senders, the PCK will only accept those messages that are sent by the "right" business partners.

  1. To assign authorized users, in the editor Edit Communication Component, select the Assigned Users tab page.
  2. Insert a new line for the new user (Insert Line After Selection ) and enter the user name manually.

If no users are specified, there are no access restrictions for this communication component.

The function is supported by the following sender adapters:

XI Adapter

RFC Adapter

SOAP Adapter

SAP Business Connector Adapter