Transports Consolidation

Hi,
I have created 180 transports to make changes to a SAP Script form and a print program. This is done because we have trouble with copy to clients utility in our system. Now I do not want to send all these transoprts to testing system or production. Because to move each transport, it takes time, and we don't have that much time now. My plan is to create a new transport and include all objects from all of these 180 tranports and send this one. I want to know the impact of it, in terms of time wise. Will it be good decision ? Please let me know the pros and cons. Dos and Don'ts. Your help is greatly appriciated. If you are not clear of the solution plz let me know.
Thank you,
Surya

yes u have follow this procedure,
Change the owner as same and combine all the request(Hopefully)
You can add as a Dependent,
Goto SE01, in the request list, Place the curson on the Request and press Goto --> Dependency Information, here press the add button, you can add the Request no over here under one request, you can 8 requests even it is owned by another user.
First change the owner of the Request to the other person, such that both the requests are under single owner.
Then release them and merge using SE09 SE10 T codes:
select the request and right click-> Merge requests.
reward helpfull answers,
Message was edited by:
sunil kumar

Similar Messages

Page cannot be displayed - No Web Dispatcher - Only ICM running

Hi,
Our training system is a SAP ERP Central Component 5.0, on a WAS 6.40 platform. There is only the Central instance running with all processes available, including ICM. The Dispatcher is NOT configured.
When entering following url, results in 'Page Cannot Displayed'error message:
===============================
http://<virtual-FQDN>:<port>/sap/bc/bsp/sap/hrrcf_start_int?sap-
client=230&BspClient=230&sap-
language=EN&BspLanguage=EN&rcfSpId=9001&rcfContext=MCC
The 'Page cannot be displayed'error occurs FOR ALL SERVICES. The above url was working before and as far as everyone here knows, there have been no changes.
The following url ping tests were SUCCESSFUL. These were typed directly into the Internet Explorer Address:
==================================================
http://<virtual-FQDN>:<port>//sap/bc/ping?sap-client=200
and
http://<virtual-FQDN>:<port>//sap/bc/ping?sap-client=230
and
http://<virtual-FQDN>:<port>//sap/bc/ping
However, performing the ping test from Tx SICF, results in an error. For some reason, the url resolves to Physical-FQDN for teh hostname. However, when changing hostname to the Virtual-FQDN, then Ping works. (Not sure why the Physical-FQDN is not working)
Also testing the service hrrcf_start_int from Tx SICF, results in the same Page cannot be displayed error. (Same for all services)
From Tx SE80, INTERNAL has been selected for Publishing.
Service has been activated.
Have run program SIAC_PUBLISH_ALL_INTERNAL from Tx SE38. Services has also been deactivated and activated from Tx SICF. None of this has helped resolve the error.
Some ICM parameters as follows:
icm/server_port_0 = PROT=HTTP,PORT=8012
icm/host_name_full = <virtual-FQDN>
As mentioned before, the url was working some 2 weeks back, but for some reason is no longer working.
Regards,
Sanjay

Hi Dezso,
Thanks for your suggestion.
The issue is now being resolved. The problem was as follows:
Previously the on-site Consultancy had configured one of the Transport Consolidation routes from DEV to TRN. (This has now been reconfigured so that TRN as well as PRD are the TARGET routes from QA system.
However, previously ABAP Support Packages were applied to DEV & QA. (& not to TRN). Then a Developer transported the SPAU transport through the landscape and it obviously went to the TRN server. (Transport was not imported into Production).
So TRN had no SPs applied, but the transport had been imported into TRN due to landscape setup.
Now the problem is due to an object that concerns authentication which was overwritten by the transport in TRN. (Preventing user authentication). We have a work around in that we can send the users directly through the ITS via a url, they can then authenticate and then they copy and paste the url they are using in the IE Address space. After logging on, the IE session is still holding the session cookie, so no need to authenticate again after copying the url the user wants to use. (I hope this makes sense? No sure how better to describe this).
The longer term solution will be apply the SPs also to TRN and then apply the SPAU transport to TRN and it should then be fine.
Regards,
Sanjay

Transport to Consolidation system doesn't work

First of all, sorry if this is a silly question but I have to admin I am a little missed with NWDI. Every step we did we have a new error
In this case, we have trying to move a iView using NWDI and process to transport from
Development Environment to Consolidation doesn't work.
We have done all steps to deploy changes in Development and iview
has been updated correctly. But then, when we release the DC in NWDS
and go to Transport View - Consolidation tab and we do the import
althougth we have a successfully message with "Import Finished", the
iview has not been updated in Consolidation system .
We have doublechecked server, port and SDM password in Runtine System
tab for this server and everything is OK.
I have analyzed all logs generated during Import process in Transport
Studio and no error is showed.
I have find in CBS Consolidation builspace and we don't have any activities pending, and additionally the DC doesn't appear in this buildspace. However in Development buildspace it is.
Could somebody help us putting some ligth on it? Where can I to try to obtain log information about why this change is not moved to Consolidation?
Thanks in advance.

Hi Javier,
I have sometimes a similar problem: we are developing WebDynpro applications. The activities are checked in and transported correctly, but on the destination system only the old release shows up.
My solution of this situation is not elegant, but effective (steamroller tactics or in german "Holzhammermethode"):
- Log on to the console of the machine where your destination system for your deployment is running. Start up the (really slow) standalone SDM application and select the components, which are not updated correctly, for undeployment and undeploy them manually.
- After successful undeployment reimport the component/activity in the JDI transport studio again.
As mentioned before, not elegant, but effective. It worked for all the situations now, when the deployment did not work, but there was no obvious reason available.
Regards
Karsten

Transport to consolidation system

Hi ,
A scenario, where multiple developers have worked on multiple DCs. If, we want to release only 3 Dcs (1 Dc + 2 used Dcs) into a consolidation system, we are faced with a very peculiar problem.
The developers have worked with no naming conventions on large number of Dcs. And, now we want to transport only 3 Dcs from them to the Consolidation system.
The approach we are taking is: Synch the latest copy of these 3 DCs from active space, using NWDS open all possible files for edit, associate them with new activity name. (No modifications are done on these files). Check it in again, activate , release this activity from the Transport View of the NWDS.
If in the CMS - Transport Studio, we import only this activity in the Import queue to the Consolidation system, will these 3 DCs get imported Consolidation system?
Or, should we go into all the developer's NWDS, open all checked in activity from the Transport Studio of NWDS, identify all activities related to these 3 Dcs , release them individually and then go to CMS - Transport Studio and import all these activities into the consolidation system to get these 3 Dcs into the consolidation system.
Which approach will work?

1. Will the 3 dcs get imported only if all activities (1st to last) related to them are released from NWDS Transport studio and then Imported from CMS - Transport Studio ?
2. Will single activity in the end which has opened all files for edit, work???
Regards,
Sandeep

Hi Pascal,
I do know that for ACTIVATION (after checkin), if the current activity has predecessor activities, then they will tagged along with this last activity, for the Activation process.
Is this the same case for Activities Transport Release as well (In NWDS-Transport View)?
So, In NWDS, Transport View under Waiting section, when my last checked out for Edit Activity, which has been activated already, and is awaiting release, is Released, all predecessor activities (which has been activated & awaiting release as well) will get associated automatically???
Therefore,
1. I do not have to ask all developers to go open their NWDS-Transport View and hunt for activities pertaining to the DCs to be released.And, then ask them to release it? RIGHT?
2. All I need to do is to release the last activity under Waiting and the rest of all activities by other developers will get automatically attached??? RIGHT?
Thanks,
Sandeep

Transport to consolidation system doesnot reflect in components

Hi There,
We have configured a separate Consolidation system for our WebDynpro developments. and we are using TCS for deployment. After import to consolidation system and TCS deployment , changes are not reflecting in Consolidation system.
We defined new track and its components and after initial imports we got development configuration in Development studio and made changes.
Thereafter we have followed these steps
1) We released and transported all our changes from Webdynpro Studio.
2) started Import on Consolidation tab and all components were successfully imported.
3) started TCS deployer for selected track_c and that also completed, without any error messages
4) test in consolidation system shows webdynpro changes have not been moved.
This is first round of imports on this track, if there is anything we might have missed out.
Please suggest.
Thanks a lot for your time.
Rgds

Solved this..
Created one more request with application files and followed the cycle.. and this time it deployed application. Weird though worked.
Cheers

Error while transport to Consolidation

Hi All,
When I am trying to import the activities in Consolidation I am getting the following error in the SDM log.
'appl/wd_test'/'lonmin.com'/'DEP_APPL_C'/'4410'/'0'
dependency:
name: 'appl/ext_lib_sp14'
vendor: 'lonmin.com'
And when I try to create and edit the dependencies of wd_test project I get error "Cannot sync url The path does not seem to exist on the server" We are not able to find out this component anywhere. IS there any workaround to do the transport without using this component.
Any help is appreciated.
Regards,
Jaydeep

Can you Sync the DC in the DEP_APPL_D development configuration?

Response message became too slow, after transported to Consolidation Sys!

Hi guys,
I have a sync interface with BPM who calls an HTTP service.
In development system things work fine and the interface is really fast. It gets a response from HTTP service in a few seconds (also with big messages, over 2 mega bytes). After transported to the consolidation system, the response message became too slow and after 600sec it gets a timeout.
No parameters on Integration Server and RZ10 were changed
Anyone knows whats happening or have an idea?
Thanks in advance,
Ricardo.
Message was edited by: Ricardo Quintino

Hi Udo,
What do you mean "the channels are not transported 1:1"?
One thing, the difference between Development XI and Consolidation XI is that Consolidation is in Cluster.
I need to do some extra configurations for HTTP in Cluster systems?
Thanks in advance.
Regards,
Ricardo.
Message was edited by: Ricardo Quintino

How to transport Custom Characteristics in consolidation to other system?

Hello,
For consolidation purposes i was creating new characteristic for table ECMCT with T.CODE CX0A1.
I was genereting the changes i have made, but transport was not created.
Can someone tell me how to transport custom characteristic?
Best regards,
Avishai

Hi Eli,
The characteristics can not be transported with this one.
Our problem comes from table MCDX.
The content for object dependency is not the same in Development and quality system and I can't find how to update it.

2 consolidation routes, one transport layer - not possible

Hello everyone,
I have one DEV system and two QAS systems. Some of my development need to go to both of two systems, however some of them need to go to only one of my QAS.
So I have set up two transport groups: one link to both of two QAS and another one link to one of them. Because it is not possible for 2 consolidation routes with one transport layer, so there would be much of trouble when I need to transport my own development into that one QAS------I need to manually change the object directory entry/package for it first.
So I would like to know is there any way easier to set up the landscape so that the developer can easily choose the correct transport target in our situation?
Thank you very much in advance for your help!
Best regards,
Keith

Hi Keith,
please do not mix up transport groups (systems sharing one transport directory) with transport target groups.
If you have one development system DEV and two QA-Systems QA1 / QA2 then there are 3 options: Transport from DEV to QA1 only, transport from DEV to QA2 only and transport from DEV to both QA1 and QA2. To realize this, you need three consolidation routes starting in DEV. One with transport layer (say) ZQA1 pointing to QA1, one with transport layer (say) ZQA2 pointing to QA2 and on with transport layer (say) ZALL pointing to the transport target group which in turn points to QA1 and QA2. Then you need to create 3 packages (formerly: development classes) poining to one of these three transport layers. For example ZPACKZQA1, ZPACKZQA2, ZPACKZALL. Then when you create a programm you need to specify a package. Depending on the package you choose, the program will be transported to either QA1 only, QA2 only or both QA1 and QA2.
Best regards
Thomas

Best practice data source from ECC 6.0 for legal consolidation in BPC NW7.5

Hi there,
after scanning every message in this forum for "data source" I wonder if there isn't any standard approach from SAP to extract consolidation data from ECC 6.0. I have to say that my customer is not using New g/l so far and therefore the great guide "how to get balances from ECC 6.0 ..." does not fully work for us.
Coming from the old world of EC-CS there is the first option to go via the GLT3 table. This option requires clever customization and the need to keep both GLT0 and GLT3 in line. Who has experiences regarding maintenance of these tables in a production environment?
We therefore plan to use data source 0FI_GL_4 which contains all line items to the financial documents posted. Does this approach make sense or will it fail because of performance issues?
Any help is appreciated!
Kind regards,
Dierk

Hi Dierk,
Do you have a need for the level of detail provided by the 0FI_GL_4 extractor? Normally I would recommend going for the basic 0FI_GL_6 extractor, which provides a much more manageable data volume since it only gives the periodic activity and balances as well as a much smaller selection of characteristics. Link: [http://help.sap.com/saphelp_nw70/helpdata/en/0a/558cabb2e19a4db3097b81bba4fd0e/frameset.htm]
Despite this initial recommendation, every client I've had has eventually had a need for the level of detail provided by the 0FI_GL_4 extractor (or the New G/L equivalent - 0FI_GL_14). Most BW systems can handle the output of the line-item extractors without much issue, but you should test using production data and make sure your system sizing takes into account the load.
The major problem you can run into with the line-item extractors is that if your delta somehow gets compromised it can take a very long time (days, sometimes weeks) to reinitialize and this can cause a large load in your ECC and BW system. Also, for the first transport to production, it is important to plan time to initialize the delta.
Ethan

Import steps not specific to Transport Request

Hi all,
I need to move 5 Released Transport Request as "Local Change Requests" to another SAP installation.
I followed two guides to do this:
SAP BASIS / ABAP - How to Export and Import an External Change Request - YouTube
How to copy Repository Objects between non-connected SAP systems - ABAP Development - SCN Wiki
However I have problems creating the Change Request that contains all my requests: if I generate it as Local Change Request it is not available on cofiles and data folders.
So I created a new Virtual System called M02 and I created a standard consolidation transport link between my original system M01 and the virtual system M02.
Then I created a new TRANSPORT OF COPIES Transport Request and I selected as target system M02. All objects are correctly added to the new request and the validation is correctly performed.
However when I release the request on the SOURCE server I get the following error:
M01#######            My Request Name
M01        System M01
             Checks at Operating System Level         05.03.2014 16:48:34    (0) Successfully Completed
             Pre-Export Methods                       05.03.2014 16:48:37    (0) Successfully Completed
             Export                                   05.03.2014 16:48:47    (0) Successfully Completed
      Import steps not specific to transport request
M02        Virtual System
             Selection for Import                     05.03.2014 16:48:47    (0) Successfully Completed
      Import steps not specific to transport request
"Import steps not specific to transport request" expanded as:
Feedback after export or import 05.03.2014 16:48:48    (0) Successfully Completed
I get this message even if I generate the new Change Request from a single Change Request (the first one that we released).
The cofiles and data files are correctly generated, however the IMPORT on the TARGET server returns an error (invalid data package)
My question is: is the "Import steps not specific to transport request" message correct, or should I modify something? Why am I getting this message?
Thank you

Hi Chinna,
Its a warning message you can ignore that... if you want to see what exactly the reason for warning in SE09 --> select the released request --> click the Transport Log Ikon --> select the warning message and click the spects Ikon --> go on expanding you can find the warnings of Objects in Yellow...
Hope this helps,
Sudhakar.

Cannot see 'WAITING/RELEASED' in Transport View in NWDS

Hello,
We just installed NWDI (7.0 SP09) and followed the steps to configure it.
I created a New DC, created a WebDynpro application within it and checked-in the activity.
The Activation Request shows a green check mark, and a running-man symbol.
Under the Transport View, I do not see the yellow and green flags for the Waiting and Released tasks.
In CMS, we have configured a single machine for our development server (we have not included any consolidation or test or production machine in the landscape). We have disabled automatic deployment for the development machine.
Can someone please point-out where we are making a mistake ?
Thanks
Jon.

The running man symbol appears because you disabled automatic deployment. The green check mark indicates that activation was successful. The activity should nevertheless appear in the Transport view as a waiting activity, since activation was successful. In order to deploy the DC's touched in the activity you'll have to go to the TCS Deployer now: [http://<nwdiserver>:<port>/TCS/Deployer].

Error while importing to production through CMS Transport Studio

Hi,
I am trying to transport my application from development to Production using CMS tracks. All DC's are getting properly consolidated,Assembled and Approved. But while importing into the Production, it is throwing following error :
*************ERROR LOG********************************
Info:06/07/22 17:07:13 - ERROR: Not deployed. Deploy Service returned ERROR:
Info: java.rmi.RemoteException: Cannot deploy application asianpaints.com/hsspapp..
Info: Reason: Exception during generation of components of application asianpaints.com/hsspapp in container EJBContainer.; nested exception is: Info: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/hsspapp in container EJBContainer.
Info: at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:554)
Info: at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
Info: at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304)
Info: at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193)
Info: at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122)
Info: at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
Info: at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
Info: at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
Info: at java.security.AccessController.doPrivileged(Native Method)
Info: at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
Info: at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info: Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Exception during generation of components of application asianpaints.com/hsspapp in container EJBContainer.
Info: at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:621)
Info: at com.sap.engine.services.deploy.server.application.DeployUtilTransaction.commonBegin(DeployUtilTransaction.java:319)
Info: at com.sap.engine.services.deploy.server.application.DeploymentTransaction.begin(DeploymentTransaction.java:307)
Info: at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:292)
Info: at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:326)
Info: at com.sap.engine.services.deploy.server.DeployServiceImpl.makeGlobalTransaction(DeployServiceImpl.java:3139)
Info: at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:539)
Info: ... 10 more
Info: Caused by: java.lang.NoClassDefFoundError: com/apil/hssp/newhelper/TransactionDTOInfo: at java.lang.Class.getDeclaredMethods0(Native Method)
Info: at java.lang.Class.privateGetDeclaredMethods(Class.java:1655)
Info: at java.lang.Class.getMethod0(Class.java:1901)
Info: at java.lang.Class.getMethod(Class.java:984)
Info: at com.sap.engine.services.ejb.deploy.xml.CMPParser.getFieldClass(CMPParser.java:464)
Info: at com.sap.engine.services.ejb.deploy.xml.CMPParser.fillCmpFieldInfo(CMPParser.java:88)
Info: at com.sap.engine.services.ejb.deploy.xml.CMPParser.parseCMPFields(CMPParser.java:646)
Info: at com.sap.engine.services.ejb.deploy.xml.CMPParser.parseFields(CMPParser.java:121)
Info: at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:174)
Info: at com.sap.engine.services.ejb.deploy.xml.EJBJarParser.parseXml(EJBJarParser.java:97)
Info: at com.sap.engine.services.ejb.deploy.DeployAdmin.parseSingleJar(DeployAdmin.java:297)
Info: at com.sap.engine.services.ejb.deploy.DeployAdmin.generate(DeployAdmin.java:247)
Info: at com.sap.engine.services.ejb.EJBAdmin.deploy(EJBAdmin.java:2144)
Info: at com.sap.engine.services.deploy.server.application.DeploymentTransaction.makeComponents(DeploymentTransaction.java:606
*****************ERROR LOG************************
Both my development and production are on running on the same version.
Kindly help on this issue.
Regards,
Yashodhan Mujumdar

Hi Yashodhan,
I had the same problem and resolved by adding reference of the Used DCs in application-j2ee-engine.xml of EJB project.
The xml looks like:
<reference
 reference-type="hard">
 <reference-target
 provider-name="sap.com"
 target-type="application">xappscprxrpmcommon</reference-target>
 </reference>
 <provider-name>sap.com</provider-name>
 <fail-over-enable
 mode="disable"/>
thanks,
Nancy

Error in Transport

Hi,
While transporting the process chains, I am getting the following error Source system does not exist
Message no. RSAR409
Diagnosis
Source system is not known.
System Response
The imported data for DataSource was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
Procedure
Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
You get to maintenance using Tools -> Conversion of the logical system names.
I have already checked the table in the development system and it contains the source system and so does the table in Consolidation system.
Any ideas on how to solve this error.
Thanks and Regards,
Sahana Narahalli

Hi Sahana,
The BW system landscape needs to be maintained. It looks like the Development Acceptance and Production environments are not maintained in the System Landscape Design, which is evident from the message 'Source system is not known'.
Ask your Basis team to do this. BW team may not have authorizations for such kind of Landscape changes.
Best Regards,
Pratap Sone

Error when transporting BI 7.0 request

Hi Experts,
I´ve been trying to transport the first and simple request to the QAS environment and I´m getting error 12 with the log below. No one knows till now what´s going on, so I would really appreciate any help. I´m a BI Consultant and I can´t understand the whole meaning of the error description. In this request there´s just a an Infoarea object.
Thanks in advance.
Fabio
Log File: /usr/sap/trans/log/CBDI900093.CBQ
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.
Main import
Transport request : CBDK900093
System : CBQ
tp path : tp
Version and release: 372.04.29 700
R3trans version 6.14 (release 700 - 14.05.08 - 17:05:00).
unicode enabled version
===============================================
date&time : 28.08.2008 - 09:12:41
control file: /usr/sap/trans/tmp/CBDKK900093.CBQ
> #pid 1228956 on celcbq ()
> import
> buffersync=yes
> file='/usr/sap/trans/data/R900093.CBD'
> continuation='/usr/sap/trans/data/R900093_#.CBD'
> client=300
> csi=yes
> repeatimport=yes
>
> excluding 'R3TRDDDD','R3TRDOMA','R3TRDTEL','R3TRENQU','R3TRMACO','R3TRMCID','R3TRMCOB','R3TRSHLP','R3TRSQLT','R3TRTABL','R3TRTTYP
R3trans was called as follows: R3trans -u 2 -w /usr/sap/trans/tmp/CBDI900093.CBQ /usr/sap/trans/tmp/CBDKK900093.CBQ
active unconditional modes: 2
Connected to DBMS = ORACLE --- dbs_ora_tnsname = 'CBQ' --- SYSTEM = 'CBQ'.
0 0
trace at level 1 opened for a given file pointer
================== STEP 1 =====================
date&time : 28.08.2008 - 09:12:41
function : IMPORT
data file : /usr/sap/trans/data/R900093.CBD
Continuation : /usr/sap/trans/data/R900093_#.CBD
buffersync : YES
client : 300
repeatimport : YES (corresponds to unconditional mode 1)
repeatclimport : NO
c.s.i. : YES
l.s.m. : VECTOR
charsetadapt : YES
def. charset : WEUROPEAN
commit : 100000
table cache : dynamic
EXCLUDING : 'R3TRVIEW','R3TRUENO','R3TRTTYP','R3TRTABL','R3TRSQLT','R3TRSHLP','R3TRMCOB','R3TRMCID','R3TRMACO','R3TRENQU','R
Data file is compressed with algorithm 'L'.
Export was executed on 28.08.2008 at 09:10:40 by cbdadm
700
with R3trans version: 14.05.08 - 17:05:00
Source System = IBM RS/6000 with AIX on DBMS = ORACLE --- dbs_ora_tnsname = 'CBD' --- SYSTEM = 'CBD'.
language vector during export: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdi(),./:;
language vector during export: ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789abcdi(),./:;& (ISO-ARHECSDEENFRELHUITJADAPLZFNLNOPTSKRUESTRFISVB
lsm during export: VECTOR
trfunction = K (transport to consolidation system)
Used Commandfile CBDK900093 (SAP237827/2)
This is a transport to consolidation system.
1 entry for E070 inserted (CBDK900093).
2 entries for E071 inserted (CBDK900093 *).
1 E071C entry created
1 entry for E070C inserted (CBDK900093).
8 entries for E070A inserted (CBDK900093 *).
1 entry for E07T inserted (CBDK900093 *).
Start import R3TRAREA0HCM ...
2910 2910
1 entry for TADIR inserted (R3TRAREA0HCM ).
1 entry for RSDAREA inserted (0HCM M).
0 entries from RSDAREAT (&0HCM M) deleted.
0 entries from RSDAREAT (;0HCM M) deleted.
0 entries from RSDAREAT (:0HCM M) deleted.
0 entries from RSDAREAT (/0HCM M) deleted.
0 entries from RSDAREAT (.0HCM M) deleted.
0 entries from RSDAREAT (,0HCM M) deleted.
0 entries from RSDAREAT ()0HCM M) deleted.
0 entries from RSDAREAT ((0HCM M) deleted.
0 entries from RSDAREAT (i0HCM M) deleted.
0 entries from RSDAREAT (d0HCM M) deleted.
0 entries from RSDAREAT (c0HCM M) deleted.
0 entries from RSDAREAT (b0HCM M) deleted.
0 entries from RSDAREAT (a0HCM M) deleted.
0 entries from RSDAREAT (90HCM M) deleted.
0 entries from RSDAREAT (80HCM M) deleted.
0 entries from RSDAREAT (70HCM M) deleted.
0 entries from RSDAREAT (60HCM M) deleted.
0 entries from RSDAREAT (50HCM M) deleted.
0 entries from RSDAREAT (40HCM M) deleted.
0 entries from RSDAREAT (30HCM M) deleted.
0 entries from RSDAREAT (20HCM M) deleted.
0 entries from RSDAREAT (10HCM M) deleted.
0 entries from RSDAREAT (00HCM M) deleted.
0 entries from RSDAREAT (Z0HCM M) deleted.
0 entries from RSDAREAT (Y0HCM M) deleted.
0 entries from RSDAREAT (X0HCM M) deleted.
0 entries from RSDAREAT (W0HCM M) deleted.
0 entries from RSDAREAT (V0HCM M) deleted.
0 entries from RSDAREAT (U0HCM M) deleted.
0 entries from RSDAREAT (T0HCM M) deleted.
0 entries from RSDAREAT (S0HCM M) deleted.
0 entries from RSDAREAT (R0HCM M) deleted.
0 entries from RSDAREAT (Q0HCM M) deleted.
1 entry for RSDAREAT inserted (P0HCM M).
0 entries from RSDAREAT (O0HCM M) deleted.
0 entries from RSDAREAT (N0HCM M) deleted.
0 entries from RSDAREAT (M0HCM M) deleted.
0 entries from RSDAREAT (L0HCM M) deleted.
0 entries from RSDAREAT (K0HCM M) deleted.
0 entries from RSDAREAT (J0HCM M) deleted.
0 entries from RSDAREAT (I0HCM M) deleted.
0 entries from RSDAREAT (H0HCM M) deleted.
0 entries from RSDAREAT (G0HCM M) deleted.
0 entries from RSDAREAT (F0HCM M) deleted.
1 entry for RSDAREAT inserted (E0HCM M).
1 entry for RSDAREAT inserted (D0HCM M).
0 entries from RSDAREAT (C0HCM M) deleted.
0 entries from RSDAREAT (B0HCM M) deleted.
0 entries from RSDAREAT (A0HCM M) deleted.
End of import R3TRAREA0HCM
E071-LOCKFLAGs 000002 - 000002 updated ('2', 1 entries).
E071C entries 000002 - 000002 deleted (1 entries).
CBDK900093 touched.
1 tables in P-buffer synchronized.
1 tables in R-buffer synchronized.
2310 5220
***LOG BZY=>unexpected return code 103 calling INS
306203 0.306203
db_syflush (TRUE, FALSE) failed 22 0.306225
db_con_commit received an error return code in before-commit action
32 0.306257
*** ERROR => missing return code handler 25 0.306282
caller does not handle code 1024 from dblink#5[293]
==> calling sap_dext to abort transaction
sap_dext called with msgnr 900:
Main import
End date and time : 20080828091241
Ended with return code: ===> 12 <===
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.

Hi Fabio,
You should contact your System Admin for this error.
Since the transport tp return code is 12, that means this not because of the content of the transport. however, it may be due to some other technical settings.
http://help.sap.com/saphelp_nw2004s/helpdata/en/57/38e26c4eb711d182bf0000e829fbfe/content.htm
Regards,
Zaheer

Transports Consolidation

Similar Messages

Maybe you are looking for