Hello Ankita,
There are three alternatives:
• ALE: attributes, class and value of objects is transmitted via ALE
• LMSW: there must be a loading / unloading of the classification to perform the copy
• SXDA: Data Transfer Workbench
Usually the ALE method is simpler and faster to implement. Changes in the classification are done in a reference system (usually the configuration system/client) and then sent via the ALE standard tools.
BD54 -> Declaration of logical systems
Prerequisite: logical systems must be declared on each client to define the distribution model, etc ...
BD64 -> distribution model
Define a distribution model for each target system/client
Image may be NSFW.
Clik here to view.
SM59 -> RFC destination
Define RFC destinations with the target systems for the distribution of the configuration.(make sure that the user assigned to the RFC has the correct authorizations).
Image may be NSFW.
Clik here to view.
WE21-> Create RFC port
Prerequisites: Configuring RFC connection (SM59) - Ports identify the SAP systems for data exchange (Idocs, etc ...). The port configuration is a prerequisite for configuring the exchange agreements.
Image may be NSFW.
Clik here to view.
BD82 -> Generate partner profile.
When the partner profile is set via BD82, it is not necessary to execute WE20 to define the outbound parameters.
Make sure to execute this step from the source system and enter in partner system the ID of the target system (where the release strategy has to be "transported").
Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.
Inbound parameters in the "target" system :
Define in the target system (here ECQCLNT200), the inbound parameters for the processing of the messages (Idocs) sent by the source system (here ECDCLNT100).
Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.
Perform this configuration for all the message types :
CHRMAS Characteristics :
Enter the number of partner ECDCLNT100
Enter the type of partner: LS
Enter the type of message: CHRMAS
Enter code processing message: CHRM
CLFMAS Classification:
Enter the number of partner ECDCLNT100
Enter the type of partner: LS
Enter the type of message: CLFMAS
Enter code processing message: CLFM
CLSMAS Characteristics values :
Enter the number of partner ECDCLNT100
Enter the type of partner: LS
Enter the type of message: CLSMAS
Enter code processing message: CLSM
Note : the inbound parameters have to be defined in each target system/client where the release strategy has to be "transported".
After everything has been set up, it is time to transport the classification :
The distribution will copy the settings from the source system to the target systems
BD91 => sending (CHRMAS)
BD92 => sending (CLSMAS)
BD93 => sending (CLFMAS)
Note : the transactions have to be performed in this order, and repeated for each target system/client.
If necessary execute BD87 to process the idocs (log into the target system).
