ALE + Transport

hi friends,
I have developed an ALE for transfer of material across two clients.Now i want to move this to QA/PROD..For this to get happen,only request has to transfer or something more has to be done..
Thanks,
Gaurav

Hi Gaurav,
As per my knoledge the
following things cannot be transported
1). Port definition
2). Partner profile definition
3).RFC Destinations
4) Distribution model definition.
These things have to be created in each and every system for ALE settings.
Regards,
Ranjith.

Similar Messages

ALE Transports overwritting local settings in SD account determination

When sending over ALE transports for SD account determination changes, it is deleting existing entries in the local system. For example we maintain entries for sales orgs that are maintained on the local system, but when we ALE entries for the other sales org, the local entries are deleted. Why?
This is also happening with international addresses that are maintained on the local box. When we ALE over the English address the international address that was created on the local box is deleted. Any help would be greatly appreciated.
Jocelyn

Dear,
Like MM-FI Integration is done solely by the Finance people, they will ask MM counter part only in some cases....FI-SD integration is done by SD people....you (finance) just need to supply the GL account information.....
Use VKOA to maintain FI-SD integration..
Regards,
Chintan Joshi

ALE Transports

Hi,
Can anyone tell me what all are ALE settings can be transported into another system and what all are the ALE Settings has to created in each system.
Thanks & Regards,
Raja T

Hi Raja,
ALE settings can be transported into another system:
- Clients
- Logical Systems
ALE Settings have to created in each system:
- Distribution Model
- Partner Profile
- RFC Destination
Regards,
Ferry Lianto

ALE transport problem

Hi,
We define our distribution in our development system and want to transport it in our quality assurance system. We tried to create just a transport but without success as the logical system is not changed so we still have the logical system of our DEV system. We try to use the transaction BDXE but without success as we did not understand how to use this transaction.
Any help will be appreciate.
Thanks,
Jean-Christophe

Hi Jean,
Why don't you use transaction BD64 to distribute model view from DEV to QA system? Please ensure the logical system setup has been transported to QA.
Once you created the distribution model in DEV then you can distribute to QA.
Path: BD64 -> Change mode -> Select the model view -> Edit -> Model view -> Distribute.
Hope this will help.
Regards,
Ferry Lianto

Using ALE to synchronize Variant Configuration data from Production to Dev

SAP Gurus,
We are trying to move away from opening our production environment every time with need to add new Variant configuration for products.
In order to do so, we need to ensure that our development and staging systems are in line with production LO-VC data. We have been looking at a possible ALE solution but I would like to get other suggestions.
Any thoughts you may have with regards to either pros and cons of ALE, or another solution we may have overlooked. If your clients are transporting Variant Configuration to production, what method are they currently using to ensure data consistency between environments.
Our landscape currently has two production environments for two separate business lines but both use LO-VC therefore we would like to standardize the process.
Thanks and Regards,
Kevin Webb
SAP SD Senior Consultant

Hi Webb,
General its a complex process to transport VC but for system consistency you can:
1. do the changes Manually in each system
2. Use ALE idoc process to transport.
But ALE transport generally used for fresh VC transport, if the VC already present in transporting system, it may cause inconsistency. Hence if you want to transport some changes then I can suggest you to do MANUALLY.
But if you are transporting VC freshly in each system, go for ALE.
try and revert

PR Release Strategy- transport of charact/class/ values using ALE

Does anyone have the information relative to ALE set up for release strategy-
I am using transactions BD91 for characteristics; BD 92 for Class and BD 93 for the actual values into release strategy.
I need the information as to what needs to be set up in Development client and receiving clients ( Q and Prod) for these transactions i.e., RFC destinations, define ports, Identify Message types & setup partner profile configurations etc
This will be a great help.
Thanks
Raj

Hi Raj,
Please check the below notes for more inrofmation:
86900 - Transport of Release strategies (OMGQ,OMGS)
799345    Transport of release strategy disabled
10745     Copying classification data to another client
45951     Transporting class data: system / client. - has details of what you are looking for.
Hope this helps.
Regards,
Ashwini.

How is partner profile for ALE/IDOC transported?

Hi experts,
How is a request created for transporting configurations in ALE/idoc.
Valuable answers will be generously rewarded.
regards,
Shrita.

Hi,
some configurations are client dependent and some are client independent.
so client dependent configurations are transported to different clients using SCC1 transaction.
and client independent configurations they refelect automatically.
Regards
vijay

Transport abt ALE Config

Hi,
We have done all IDOC to File scenarios
We have configured the ALE settings on SAP R/3's DEv server.
Can i transport these Config to SAP R/3's QTY Server or Should i create them as it is appear in the SAP R/3's DEV server???
Regards
Suman

Hi Suman..
This was the ALE settings...
Steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.\
idoc to idoc
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
regards,
Kishore

ALE/IDOC TRANSPORT ERROR FOR Z TABLE

Dear Experts,
I am new to ALE/IDOC,I am trying a simple scenario by transporting a ztable data between two clients with in a same server.
steps i have done are :
1, created logical system at both sender and receiver.
2, assigned logical system to clients at both side.
3, created segments for fields at Z table and created new message type.
4, created RFC destination and port at both ends.
5, created distribution model at sender.
6, When i generated partner profile at sender i got the below error
"Port could not be created
RFC destination LOGSTM_210 not specified for system LOGSTM_210
Enter the RFC destination and restart the generation"
can any one please help me to solve this error?
Thanks In Advance,
Sujay.

Hello Sujay,
Have you added the message type SYNCH to the sender Partner Profile(WE20)?
If not, then you have to manually add this message type to the Partner Profile & give the relevant port details. SYNCH is reqd. for RFC (read port) determination. This is reqd. before the generation of partner profile !!
Hope i am clear.
BR,
Suhas

Transporting ALE Distribution Model to a Target System

Hi,
      How do I transport an ALE Distribution Model from a Development System to another target system
      While transporting, how do I ensure that in the target system, the ALE Model points to the correct partner system?
      e.g. a Dev System1 points to a Dev System2. Hence a QA System1 must point to QA System2.
        When I created the ALE Model, the system prompts for a transport request, so there must be a way to transport the same
Regards,
Aditya

Hi Aditya,
In my experiences, we always maintain manually the distribution model and partner profile in our production system due to data integrity and security reasons.
However, we always maintain the distribution model and partner profile for QA system from development system via transaction BD64.
For logical system name, you need to tranport from DEV -> QA -> PROD system.
Hope this will help.
Regards,
Ferry Lianto

Transport ALE Configuration from Development to Production System

Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...

The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation?

Transport Output Condition records with ALE

Hi All.
Does anyone know if its possibel to transport Output condition (mn01, mn04 etc) records via ALE between systems.
It appears to be possible for normal condition records (VK01) but doesn't appear possibel for the output ones.
Any ideas how to set this up so we don't have to manually create these records in all environments?

Hi markjaneasl ,
Check any message type existed for that or not. Better if you post in this ABAP forum.May be you will get proper replies in that forums. Explain the requirement little more.
Regards,
Madhu.

ALE Stock Transport Orders

Hi
We have two instances both on 46c and want to pass stock transport orders between them automatically when they are created.
We was lookin at doing this viw ALE.
Could someone point me in the right direction on how to set this up or possable ways of doing this.
Thanks in advance
Barry

hey,
This can be done through ALE.
The IDoc ORDERS02 is used to create stock transport orders.This IDoc contains only one transport order.
Function module IDOC_INPUT_REC_SHIPMENTS can create a stock transport order, change the dates and quantities in an order, delete an entire order or individual items, and release individual items in an order. But it can not add an item to an existing order. Also, it does not distinguish between deletion and locking of the items. The following will list the important (not mandatory) fields required to build up an order IDoc for the function module to process successfully.
To set up the ALE system you would need to set up Partner profile etc . etc,
let me know if you need any more information.
Cheerio,
Disha

SAP/System did NOT prompt me for a transport request for ALE BD64 CDM View!

Hi Experts,
Am doing ALE setup for sending sales orders IDOC out to a 3rd party system.
I have created the logical system and attached to a transport. Here we dont have necessity of linking a client to this logical system!
Then, I created a Distribution Model (CDM) View in BD64 transaction and added Message types to it, but SAP/System did NOT prompt me for a transport request!! Pls. let me know
1) Is it usual with CDMs creation that NOT prompting for a transport? if so, How my CDM/changes will be moved to QA/Production?
2) If not, Why system did not prompted me for a transport?
3) Then How Can I attach my CDM/changes to a transport?
Thank you

I don't think we get a TR prompt when adding a view in BD64.
You've to individually maintain the CDM view in QAS & PROD. Also there is a functionality to "distribute" the CDM view, are you looking for something similar ?

ALE methodology to transport the release class

How can I use ALE methodology to transport the release class, release characteristics and release characteristic value assignment from one client to another client ?
please explain with clear steps.

Hi
Step 1: Move Characteristics to the target system/client (ALE).
i). In the source system/client, execute transaction BD91
This generates one idoc (logical message type CHRMAS) for each characteristic.
ii). In the source system, check the status of the outbound idocs using transaction WE05, selecting message type CHRMAS.
All outbound idocs should be in status 03 (Data Passed to Port OK).
iii). * Only exception is when target system is D94 client 110. In this case the idocs go to status 30 (IDoc ready for dispatch) and an extra step is required to release the idocs to the target system. In this case, using transaction SE38, run report RSEOUT00 to release the idocs.
iv). Check that the idocs were received and posted in the target system:
Log on to the target system & execute transaction WE05, selecting logical message type CHRMAS.
v). If any idocs are in status 64, run transaction BD87 to re-process these to status 53.
Step 2: Move Classes to the target system/client (ALE).
In the source system/client, execute transaction BD92
This generates one outbound idoc (message type CLSMAS) for each Class.
Step 3: Check Config & classification data in target system/client
Hope it helps
Thanks /Karthik

ALE + Transport

Similar Messages

Maybe you are looking for