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

Similar Messages

Transformation transport problems when containing routine

Hi Gurus,
I'm facing a transport problem.
When i want to transport a transformation that contains routines, the transport says syntax error in routine. The routine in DEV is tested and correct. I realised, that the transport does not bring the routines. After transport, i open the transformation, and the routines contain the default routine: RESULT = .
I found some answers in some posts, but no exact answer how can i get rid of this transport problem. I don't like copy - paste into prod system with manually editing....
If you have any idea, please let me know.
Thanks
Laszlo

Thanks for your help, it worked now, but i think it should work without owerwrite originals. Sometimes it seems that the routines is not included in the transport request, when i modify a routine in a transformation.
But thanks anyway, problem solved now

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

Open Hub transporting problems

Hi everybody, we have Open Hub transporting problems, it just gives us return code 12 or 8, basically, it doen't want to transport neither Open Hub Destination, nor Transformations, nor DTPs, and bear in mind that we're on the 15th Patch Level. We've looked at all the SAP Notes, but they reffer to the earlier patch levels...
And other problem, is that it's OK in DEV system but in QUALITY system, when you launch a DTP it gives us a dumb with ASSIGN_TYPE_ERROR
Any ideas??

My destination path on the DEV box is simply the following (identified by BID in the following path):
D:\usr\sap\BID\DVEBMGS00\work
And when I locate the un-activated open hub on the QA box, the BID is already changed to BIQ, but the server name box/field is empty....
I am going to try with the object changebility option, btw, is there any documentation on how to change these objects that are marked with object changebility on the QA box (provided that we can not manually change anything on the QA box)...
Anyways, I think my problem is with the server name conversion from "abc-bi-dev" to "abc-bi-qa"....!!!
Also, please note the RSBFILE entry for this object in the QA box has the "btcsrvname" as blank...
Do you think there is any additional setting that needs to be done on the QA box to do this translation (from "abc-bi-dev" to "abc-bi-qa")?
The only two setup we have done as far as the BI is concerned is at the "Tools-> Conversion of logical system name"....where you only put the conversion for client name mapping from dev to qa and local file system mapping from dev to qa.
So, is there anything else to map the host name (from "abc-bi-dev" to "abc-bi-qa") either at BI perspective or Basis/NetWeaver perspective?
Thanks a lot...
~Sabuj.
Edited by: Sabuj Haque on Feb 1, 2009 1:11 PM
Edited by: Sabuj Haque on Feb 1, 2009 5:34 PM

The Object cannot not be processed due to a transport problem

We are trying to delete a standard web template 0ADHOC_TABLE (modified by our coworker before and transported) and reinstall a new one or totally standard one, but when clicking the "X" icon to delete this web template, get the following error:
"The Object cannot not be processed due to a transport problem"
What could be the reason?
Thanks

Hi Kevin,
This message coms up because as you mention, the template has been transported. Since it is in the target system, if you delete form the dev system, the system needs to ensure that it is also removed from the system it has been transported too.
You can check the dev package assigned to the template, assign a new request against this dev class (RSA1 > Transport Connection > Bex Truck icon). Log out and log back into WAD and try to delete it, and then send this transport. Or you can simply reinstall it as Roberto suggests.
Hope this helps...

Multiprovider transport problem

Hello Friends ,
While transporting the multiprovider from BW Development to BW Testing system I am getting following error in the Log display of BW Testing System,
R3TRMPRO***(Multiprovider name) was repaired in this system.
The log display for the Delevelopment system shows messages 'Feedback after export or import'--'Successfully Completed'
But the problem occurs in BW Testing system ,
and we are getting the above error message ,
Import--(8) Ended with errors
please suggest solution .
Thanks in advance.

Hello A.H.P ,
Thanks for valuable suggestion.
I think someone has directly repair this multiprovider in Testing system.
I will do the required steps as suggested by you.
Agains thanks very much .
Message was edited by: Amol Kulkarni

Source System Does Not Exist - Transport Problem

Hi
We have the next Landscape in BW 7.0 (Netweaver 2004's)
LRDCLNT300     is R3 DEV
LRQCLNT700     is R3 QA
LBDCLNT100     is BW DEV
LBQCLNT700     is BW QA
The connections are
LBDCLNT100 (BW Dev) use as source system        LRDCLNT300 (R3 Dev)
LBQCLNT700 (BW QA) use as source system        LRQCLNT700 (R3 QA)
In RSA1->TOOLS -> Conversion of Logical System Names
In Conversion of source system after the transport we have these entries
Source System                    Target System
LBDCLNT100 (BW Dev)         LBQCLNT700 (BW QA)
LRDCLNT300 (R3   Dev)         LRQCLNT700 (BW QA)
But when we transport an order from BW DEV to BW QA show the error "source system LRDCLNT300 does not exist"
Never made the conversion of source system after the transport.
Can you help us please.

Thanks Edwin
     I create a RFC for LRDCLNT300 (R3 Dev) in my BW QA system (Target System).
I try an order again but it didn't work, also I try to check 7.0 checkbox but I got the message "No entry exists for original source system LBDCLNT100 for 3.x object"
and I have to uncheck again.
I still have the same problem the objects are associated to R3 Dev, never make the conversion to R3 QA.

Query Transportation Problem?

Hi Guru's,
We are working in Bw 3.5 Version
Query: We have observed that there was a problem with Query in Dev & Quality Server?
as per the regular activities we have modeled the entire process in Dev
from data Source to Data target
then we have developed a report on this data target.
all this was saved under one Request and transported to Quality.
then there was some modifications in update rules & and also in Bex report
for this also we have sent under one request to Quality
there we have observed that the modifications in update rules have been applied
& in report this modifications did nnot apply in Quality server
Can any one help in this ............
advance thanks ,very very urgent..
Points will be rewarded >
Hari

Hi,
I have the same problem. I have a query in production and I need to change it. I changed it in dev, transported the query with no error, but I don't see the changes in prod.
There is any configuration error? Normal transports work fine.
Thanks

Transportation problem in Dev system

Hello All,
I am getting the problem in Transportation. While i am transporting the request from Dev to Quality, the problem is comming in Export. please see the bellow error messages.
Exports with Errors       No Further Transport
    TBD TB Development
            TBD        TB Development
                       Pre-Export Methods                       29.12.2008 13:00:01    (0) Successfully Completed
                       Export                                   30.12.2008 08:47:19 In process: Requires update
                Import steps not specific to transport request
in the log bellow messages are displaying.
   [dev trc     ,00000] Mon Dec 29 13:00:07 2008                          760684 0.760684
   [dev trc     ,00000] Disconnecting from ALL connections:                   10 0.760694
   [dev trc     ,00000] Disconnecting from connection 0 ...                   26 0.760720
   [dev trc     ,00000] Now I'm disconnected from SAP DB                    2370 0.763090
   [dev trc     ,00000] Disconnected from connection 0                        14 0.763104
   [dev trc     ,00000] statistics db_con_commit (com_total=2, com_tx=2)
                                                                                13 0.763117
   [dev trc     ,00000] statistics db_con_rollback (roll_total=0, roll_tx=0)
                                                                                13 0.763130
Disconnected from database.
End of Transport (0000).
date&time: 29.12.2008 - 13:00:07
Please let me know the solution for the above issue, i will assign full points.
Regards
KK

Hi,
Your Error statement COMMIT shows that the sytem has submittted the request to make connection with the system.
But it immediately gives CON_ROLLBACK (statement) error, which generally happens, there is not enough space in your quality system. therefore the Rollback of the submitted request happens.
Check the DB space in ur Qual system and speak to your BASIS team, so that it can increase the DB size and also, u can urself clean the system.

Workflow rule transporting problem

Hi,
When i am trying to transport rule to from dev system to client system it is not getting copied can any body tell how to copy the rule data from dev to c system

Hi!!!
Thanks for ur prompt helps. Actually instead of OBJECTID I was passing the Obj-key and not the OBJECTID. This was creating problem. But still dont know why it was creating the prob.
Anyways THANKS A LOT.
Regards,
Sudipto.

Transport problem - newest versions overwrite by olders during transport

Hello everybody!
I am writing my master thesis, which mainly focuses on problems with transport in SAP, precisely with data inconsistence.
Let's consider the following situation:
In DEV:
1) Create change request R1 containing object O(1),
2) Release R1
3) Create change request R2 containing the newer version of object - O(2)
4) Release R2
In PRD:
1) Import R2 (using Single Import)
2) Import R1
... thus then an older version O(1) is in PRD instead of O(2).
The presented situation is very trivial, however the transport could consist of plenty requests, which contain plenty objects under different requests. If in this case because of some reasons the Single Import is necessary (like some organization prevents from performing an immediate full transport), the transport administrator has to examine all other requests from an import queue, in order to check, if this Single Import do not cause any inconstistencies.
Is there already any tool, which can fully or partly automize this process?
Or maybe anybody has an idea to ensure that the transport is relevant?
On of the solutions is checking every object under all of requests and comparing their versions. Is this effective? Does it totally solve the problem? Does any tool supporting this solution exist?
Do you maybe have any other ideas to solve this problem?
I would be very thankful for your help!
Best regards,
MZ

Thomas:
As far as I understood, you suggest the solution, which would compare timestamp of every object versions. How can I "receive" the information about it? And when should the versions be checked (I mean, before releasing requests, or maybe after releasing, but before import)?
Uwe:
But what if because of some reasons, just one request of this created "request" set is needed? Sometimes Single Imports does not cause any problems and could be even one of the transport strategy. I was thinking more a solution, which would enable a Single Import, but would not allow for data inconsistencies, caused by overwriting the newest version by older versions.
BTW, I was not aware of the fact, that there is no locking in case of customizing requests, thus thank you. To be honest, I do not see any point why in case of Workbench Requests we lock objects, and in case of Customizing Requests we do not. In my opinion it just causes additional problems. Maybe you know, why SAP solved it like that? What kind of advantages does it give? Of course this problem is also interesting.
Sandra:
Yes, DEV+PRD was just to introduce the main idea. The transactions you gave can be of course helpful to find an error, but I was thinking more about comparing versions under two change requests, before the objects are imported to the target system (not between two systems).
Best regards,
Marcin

ABAP Query transport problem

Dear All,
I need to copy queries from Standard Area to Global area. When I use the transport facility (SQ03 --> Environment --> transport), it does pop-up the transport workbench request screen at the first time. I created one transport request number for it. After that, I accidently deleted the transport request without released it first. Now I have problem to add back the queries into the new transport request since the prompt for transport workbench request is not pop-up even I successfully copied the query from standard area to global area.
Is there any suggested solution?. Thank you in advance for any suggestion.
Edited by: shahrir razlan on Apr 16, 2008 6:36 PM
Edited by: shahrir razlan on Apr 16, 2008 6:37 PM

chances are very very slim.. (i think zero) to delete a request, when it has objects .
so your statement - "I accidently deleted the transport request without released it first " doesnt sounds logical...
either you have removed your objects from the list before deleting the request..
but if that was teh case, then it shud pop up for new request..
as it is not asking for new request.... it is almost sure, that it is still in some request..
look hard in se01 - your request shud be there... description shud be something like 'transport for abap query'.

Re: Transport problem of SAP Query in Global Area

Hi All,
I am facing a problem in transporting the query which is created in Global area.
I created a Query in Global Area and saved in a Transport Request. Now i created a Transaction code for this query by taking the Program name generated by this Query.
then i released the TR to Quality sys, which contains User Group, Infoset, Query & Transaction code. I see User Group & Infoset in my Quality sys but i dont see th Query & Transaction code assigned to this Query, and when i try to run the transaction code assigned to this query its giving dump saying 'LOAD_PROGRAM_NOT_FOUND'.
Could anyone please help me in resolving this..am i missing any steps here...kindly do the needful...
Regards,
Pavan

Hi i solved my problem by myself.
I have to set Query as external available and have to use the MDX Query.
Its strange because if i build a new report the query dont have to be set as external available.

Data Source Transport Problem

Hi,
I am trying to transport some BW Objects ( InfoCubes, IO, DTPs, Transformations, Datasources) from my SAP Bw Dev system to some other SAP BW dev system E15 010.
All the Objects have been correctly transported but the DataSources as well as the connected Transformations are not getting transported.
Following error is coming:
Start of the after-import method RS_TRFN_AFTER_IMPORT for object type(s) TRFN (Aktivierungsmodus)
No rule exists
Source RSDS 0TCT_DS02 T15CLNT100 does not exist
No rule exists
Please give me ideas how to solve this problem..
Thanks and regards
Pradeep

Hi Pradeep,
The datasource & transformations are dependent on the source system. Can you please confirm if this target BW system is connected with the source R/3 system where active datasource exist.
If this target BW system is connected with some other R/3 system, can you please confirm that before transporting BI requests from one system to other, did you transport transport requests from source R/3 system to target R/3 system.

ALE IDOC Problem...

HI..
I am facing a problem on the inbound side.
If I check the IDoc in WE02, I am getting a status error as
"No status record was passed to ALE by the a"
Customised IDoc is used.
Please advise if you can Thnx

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND EASILY AND YOURSELF CAN WORKOUT WITH THIS REAL TIME SCENARIO WHICH TRANSFERS THE DATA BETWEEN TWO SYSTEMS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

ALE transport problem

Similar Messages

Maybe you are looking for