ALE customizing transport "cannot add to buffer" |
 |
EXPERT RESPONSE FROM: Axel Angeli
|
|
|
| > |
QUESTION POSED ON: 13 May 2003
I need to distribute customizing data with ALE between 2 different systems (2 different landscapes.) I've customized the ALE interface and I generated the ALE request from the sender (centralized) system but I can't import the change request into the receiver system. The problem is in the Transport management system because by using transaction BDXD. I have the error: "cannot add to buffer the request from the sender system". Which kind of CTS customizing do I need to see the "trans" directory of sender system? Where is the ALE request when I create it?
|
|
| > |
EXPERT RESPONSE
My first recommendation is to use the distribution of ALE scenario in transaction SALE instead of creating a transport request. This will send the scenario via RFC to the target and everything will be fine.
If for whatever reason you have to use the transport requests, you will have to analyze your transport layers. Given the TR number you may find it in SE09 by pressing F5 on the entry screen. If you do not know the number, the easiest way to find it, is browsing tables E070 and E071.
Distributing the scenario with a transport request should only be necessary if you define a scenario on a system that is absolutely not involved in the scenario itself, e.g. if you define a template for a roll-out or a replica of your system. If the distribution master is part of the scenario or can reach all participating systems via RFC, you should distribute it via RFC. If someone expresses security concerns, I cannot accept it. Distribution of the scenario does not activate anything until the partner profiles are set up in the participating systems.
|
|
|
|
|
|
|
|
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
|
|
|
|
|
|
|
|
|
|
|
