In order for BDEx to run correctly, collating work and exceptions from across the SAP landscape, it is necessary to configure the various systems and the connectivity between them.

Define systems and RFC destinations
This configuration option manages the list of systems in the landscape, and how these are to be reached. Every client that will be using BDEx must be entered into this table, so include all development, QA, training, pre-production and production clients where applicable. This can be maintained in SPRO or via configuration table /BTI/MDE_C_SYST.

Field Description
System ID The BDEx system ID
SAP System ID The SAP system ID
Client The client number
System Name A descriptive name for the system
Application The application class ID
Appl class The BDEx application class name
Destination The RFC destination to the source system
Source System Whether this system is the primary BDEx system
Source sys ID The source system ID for this system
Source client The source client number for this system
Icon The icon to display for this system
Active No longer used
WF used Whether inform when resolved should use workflow or email notification

For example, the following configuration would be appropriate for an ISU system EP1 client 100 and a CRM system CP1 client 100:

Field Example value
System ID 0001
SAP System ID EP1
Client 100
System name ECC production client 100
Application IS-Utilities
Source system X
Source sys ID
Source client
WF used
Field Example value
System ID 0002
SAP System ID CP1
Client 100
System name CRM production client 100
Appl class
Destination EP1CLNT100
Source system
Source sys ID EP1
Source client 100
WF used


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment