Issue in Importing request from Quality to Production

Hi Experts,
I have a request which is successfully imported to ECC Quality system. I have collected the 'Customer Exits, Functional Module, Function Groups' in this request. I am getting the following error when I try to open the Function module in se37 in the Production system after the Import Process.
Function group ZRSAX contains errors
So, Kindly help me resolve this issue.
Thanks in advance !!!!
Regards,
Gokulkumar RD

Hi Gokulkumar,
This message is FL(023).
Please try to open the include report "zrsaxuxx" in tr-code SE38.
After translated by Google:
* Not for external call, for example, by rsfufill ...
* Not even when you delete, because the bodies have gone
* There is intercepted outside
* Error in UXX how shall he completed while generating
For German
*   Nicht beim externen Aufruf z.B. durch rsfufill...
*   Auch nicht beim Löschen, da müssen die Leichen weg
*   Dort wird außerhalb abgefangen
*   Fehler im UXX wie soll er beim Generieren abge
Hope it is helpful to you.
Regards

Similar Messages

Error while transporting the request from quality to production of BI

Dear all,
When transporting a request (which contains elements of correction - in Bex designer) from quality to production of BI the following error is displayed and the request transport fails. Can the experts throw some light on this.
           Execution of programs after import (XPRA)
           Transport request   : RBDK904992
           System              : RBP
           tp path             : tp
           Version and release: 372.04.04 700
           Post-import methods for change/transport request: RBDK904992
           Post-import method RS_AFTER_IMPORT started for ELEM L, date and time: 20080406140407
           Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Activation Mode)
           Error when activating element EY2CXLKXP5X5AY0RQ2XKN9EX8
           Element 5E4II2344I3JG4R6ACMYQ441Z is missing in version M
           Start of the after-import method RS_ELEM_AFTER_IMPORT for object type(s) ELEM (Delete Mode)
           Errors occurred during post-handling RS_AFTER_IMPORT for ELEM L
           The errors affect the following components:
             BW-WHM (Warehouse Management)
           Post-import methods of change/transport request RBDK904992 completed
               Start of subsequent processing ... 20080406140407
               End of subsequent processing... 20080406140408
           Execute reports for change/transport request: RBDK904992
           Reports for change/transport request RBDK904992 have been executed
               Start of................ 20080406140408
               End of.................. 20080406140408
           Execution of programs after import (XPRA)
           End date and time : 20080406140408
           Ended with return code: ===> 8 <===
Thanks in advance.
Regards,
M.M

Hi,
First try to figure out the object type from the text obtained by following steps above.
Goto Development server ,create fresh request (using transport connection) , transport to QA and then in to production.
After successful transfer of the request for this object ,try to reimport the request which caused error and it should go smoothly without any error.
Hope it helps.
Regards
Mr Kapadia

Process of moving TR from Quality to Production

Dear Experts,
we are in a process of moving TR from Quality to Production. While moving we faced transport incositencies like some old requests have been overwritten into the new one and dependant objects were failed during import in PRD. Now production rehearsal client is kind of messed up. what is the right procedure to transport the requests from Quality to Production. (actually we transferred the TR individually based on the list send by the respectivr module owners). Please help me to findout the solution for this issue.
regards,
Yasin.

Hi,
This situation comes every now & then when you don't have any client strategy define in your landscape I'm not blaming you but for your Project Manager and then rest of the team adopt SAP standard practice if you really want things to go well act NOW..!! here is the basic to start:
Ex,
DEV ::
100 => Golden Client
200 => Customizing Client
300 => Test Client
Things to check before importing request in QAS :
1) Always get the request in sequence format ask the owner of the request for the sequence to avoid dependency issues
2) Technical Specification doc - this doc will be prepare by Functional / Developer on what changes are included in TR
QAS::
400 => Quality Client
Things to check before importing request in PRD :
1) User acceptance doc i.e UAT - client / customer will check the functionality if it's on then move this to PRD
2) Get the request in sequence format
3) Approval for production transport
PRD::
500 => Production Client
Thanks,
Saleem

How i can transport request created in R3AR2 from Quality to Production ?

Hi, Gurus !
I'm new in CRM 7.0, and need your help. Well, we made our implementation in 7.0 version, and the things will be fine, until the start of work.....
Well, the initial download of CUSTOMER_MAIN (in transaction R3AR2) do'n't run OK, because a lot of customers in selection have a bad data.... and this time, anybody change this data,
Today, i know how to re-made this task.....
But my question is : how can transport this request, created in R3AR2, from Quality to Production ?
If the transport is not possible, the answer for the question is remake the request in Production ?
Thank you very much.....
Loduca

Did you put your development in a transport when you first saved it? If yes, and if your transport system is properly configured you can release the transport using SE09 and import it into the production using transaction STMS.
Markus

Reg: Error while transporting from Quality to Production

Hi ,
I am facing a problem while transporting ODS from quality to production.. The same works perfectly when i transport from Dev to quality.
The Error Displayed while transporting is
Start of the after-import method RS_ODSO_AFTER_IMPORT for object type
The creation of the export DataSource failed
Password logon no longer possible - too many failed attempts
Error when creating the export DataSource and dependent Objects
Error when activating DataStore Object
The creation of the export DataSource failed
Password logon no longer possible - too many failed attempts
Error when creating the export DataSource and dependent Objects
Error when resetting DataStore Object to the active version
Kindly give me some suggestion ..
Thanks in advance
Regards
Guru

go to the source system RFC connection in SM59 and do a remote login - if you get the login page there then there is an issue with the RFC connection. also check if any other system is using the same RFC.. we had a situation where th R/3 connection was being used by 3 BI instances and everytime we reset the password , another system would lock the sme , ultimately we identified the systems and did a password reset in all the systems and then the issue got resolved.
but then we also faced the same issue you faced and it was related to login issues - check the remote login and that will tell you.

Transport of object from Quality to Production.

Hi,
I am a technical designer and have a limited understanding on the transport management system and basis.
I had recently created an object on the development system and provided my user with the transport request number. She had moved it to Quality and tested it. The object is working fine and she wants to move it to the production system.
I was under the impression that the request would show up on the production system and could be imported from quality but it is not.
Could some one explain as to what I am missing here? Is there anything I could do from my side to get the object moved from Quality to Production?
Regards,
Prem.

Hi Prem
Plz check whether your request is relased and transported
correctly.
for this log into quality system and type the tcode STMS_IMPORT.
search for your request,
if available ,check if there is a green tick mark against that, if yes then it can be imported to production system ( that has to be done by your BASIS personell).
if not,
check any filter criteria is set in the fields displayed and remove / change if required that as per requirement.
or , use the menu path GOTO -> IMPORT HISTORY (Ctrl+F7) and search ther (here also check for the filter criteria).
it should be available, if it is transported correctly.
do the same in your production system also, u can find your request (but unless transported to production there will not be the green tick mark against that)
reward if useful.
Regards
Prabumanoharan

Transport of activity from Quality to production for webDynpro Java applica

Hi,
can anybody tell me how do i go for transporting activity in webdynpro java applications from quality to production server.
i have done some changes in webdynpro code and deployed in quality system. i have created activity and now want to transport that to production so that the changed functionality should reflect in production system.
Its urgent so your quick suggestion will be appreciated.

Hi,
can anybody tell me how do i go for transporting activity in webdynpro java applications from quality to production server.
i have done some changes in webdynpro code and deployed in quality system. i have created activity and now want to transport that to production so that the changed functionality should reflect in production system.
Its urgent so your quick suggestion will be appreciated.
Hi Vijayalaxmi,
Following are the steps for transporting the content from DEV to QA
1. Check in the activity into DTR and activate it. Once it is activated successfully it will show green
2. Now go to transport view and release the activity by drilling down in waiting... node.
3. Once the activity is released it becomes available in the Consolidation tab of CMS.
4. Import the activity in consolidation tab
5. Assemble the components in the Assembly tab.
Once you assemble an .SCA file is created in \usr\<SID>\trans\CMS
6. Copy this file manually and deploy it using SDM in QA.
Hope it clears your doubts
Best Regards,
Ravi

Transport of Employees from Quality to Production

Hello,
This is regarding Employee assignment in CRM Sales Organizations (using T code PPOMA_CRM). We have around 1200 employees to be assigned in CRM Sales Organizations & we have to assign USER ID's for each of these employees.Since we do not have all 1200 employee master data in Development Server we will have to do this excercise in Quality Server. We want to save all these assignments in a Transport request directly from Quality server, so later same can be transported to Production Server .
Kindly let me know standard procedure for transporting all the assignments of employees & user ids from Quality to Production.
Regards,
Rajendra

Hi Rajendra,
Salesorganisation assignment to employee is masterdata and it willl not involve any tranport .
You need to create the assignment in production client. Sales organisation Id will change from client to
Client.
Regards
Pavan.A

Error while uploading roles from quality to production

Dear friends,
I have to upload roles from quality to production.
I have downloaded it from qualtiy but while uploading to production it is giving me an error "File does not contain valid data".
Can anybody tell me what could be the problem and how to resolve it.
Thanks in advance
regards
Nirgun

HI matore,
the best way is to transport the roles from DEV to QA and then to production as julius suggested
are you trying for mass down load are single role
Mass download
go to PFCG >> utilities>> Mass download>> select all the roles which you want to move it to production
and execute save it on desktop
now go to production system>> go to PFCG>>in menu click on roles>>click on upload>>select the file which is saved in desktop and click ok
mass generation of roles
in the menu click on utilities>>mass generation>>give the role names with you have uploaded and click on execute select all click on genetate button
download a single role
go to PFCG>>in the menu click on role>>click on down load and save it on desktop
now go to production system>> go to PFCG>>in menu click on roles>>click on upload>>select the file and click ok
now you needs to manully generate the role
do the user comparison
hope this helps
thanks
kishore

Problem while loading data from quality to production

Hai,
We are using standard extractor 2LIS_11_VASCL, and in test case in QTY 300, we were able to make some changes and see the changes and see the results of the changes in T-CODE RSA3. When we try the same changes in PRD300, No Changes are triggered and T-CODE RSA3 shows no changes.
Can any one suggest me regarding this prolem...

Hi bandi,
Instead of trying for the same changes in production, why cant you do the transport the object from Quality to Production & then check for the changes in RSA3.
You are transporting the object only from Quality to production.
As no data is present in PRD, u may not be finding any changes in RSA3.
Hope it helps.

Objects moving from quality to production

Hi All,
I need a step by steb documentation for objects moving from quality to production.please do the needful.
Thanks in advance
Ram

Hi Ram,
What is the transport system u r using?
Check the below links for different transport systems.
CMS
http://help.sap.com/saphelp_nwpi71/helpdata/en/49/630650f75d4df6a3dc2f93d51eb864/content.htm
CTS
http://help.sap.com/saphelp_nwpi71/helpdata/en/9a/775de286874bc78dcb1470bc80f0f9/content.htm
FIle Transport system
http://help.sap.com/saphelp_nw04/helpdata/en/a8/5e56006c17e748a68bb3843ed5aab8/content.htm
Thanks,

Program to Auto Import transports to quality and production systems

Hi Experts
Do anyone have a program that imports transport requests automatically into quality and production systems from development? I know there is a procedure to import all into QA that can be set in TMS.
But I am looking for a program instead that could auto import into quality and subsequently to production.
Thanks,
Ravali

You need to set the autoimport job in Q whichh will bring all the transport from Dev when they are released. For autoimport go to STMS --> import queue of your Q system -->Start import with the small truck sign and it will ask you to select the time (run it every 15 mins or so) --> start the job
Production you never setup an autoimport, there might be some transports which you may not want to send to prod, only the approved transport will go to prod. Hope this helps

How to transport requests from development to production server

hi gurus
i am new to SDN
can u pls give me detailed information how to transport requests from development server to production server?if possible give me screen shot documents
regards
surya

Hi
Transporting
There are help pages that discuss creation of transports.
In simple terms, you: create a transport package
add objects to the package export the package, plus optionally any related objects to a predefined folder/directory on the portal server into a file with an extension of .EPA copy the .EPA file to the import folder of your QA system and import it test the contents on the QA system copy the .EPA file to the import folder of your production system and import it Create a transport package file
Here is the step by step procedure to create a transport package:
For Export
1. Go to system administration, and click on transport?export.
2. In the middle pane, select the folder you want to export and right click on the Transport Package. 3. Fill in the General Properties i.e the name of the package, id and description. 4. And say finish and open the object for editing.
5. When the object has been opened then right click on the object you want to transport, and say "Add object to the Transport Package".
6. Check the checkbox of the item u have added and see the properties if it has been added properly. 7. Now click on the save button.
8. After the object is saved, click on the export button. 9. U will have an option to select where to store the .epa file which will be generated. U can overwrite an existing one by selecting the browse button, or store it with the generated name in the location it automatically generates. 10. Now Click on the Start Export button.
11. once the export is completed, it shows a report on how much time is taken to generate the .epa file. 12. Here there is an option for downloading the .epa file. Click on the link and download the file. This file is ready to be uploaded into any other EP Server.
For Import:
Pre-requisites: You have to copy the .epa file created while export into the local drive. Optionally, you have to manually copy the .epa file generated in the export function into the Import directory of the server ie. chooseFollow the steps below for importing a certain file. 1. Go to System Administration in the portal, and click on Transport?Import. 2. For the source of the package, Click on the radio button Server for the .epa file you have copied lately. Else, click on the radio button on client if you are operating in the client and select the .epa file you have stored on the local drive. 3. Now select the file from the browse option and click on Upload.
4. Now click on the import button. 5. Once the import process is finished, the report is shown. In the whole process, the par files are not included in the .epa files. For the par files to be included into the .epa files then we have to change the pcdStartup.properties file in the server. The property to be changed is Pcd.TransportApplication.Export.ExcludeObjectTypesAfterRuleProcessing: Keep this property's value as empty for enabling the par files to be uploaded into the .epa. You can check for this property in the portal in the following -System Administration-Support-Portal Content Directory-PCD Configuration.

How to transfer request from Development to Production

Hi,
Can anybody tell me Step by Step procedure to transfer request form Dev. to Prod.

Hi
It depends how many enviroments you have and the transport routes is defined: anyway I can suppose there are development, quality and production system.
So:
- A) U have to release the request in dev system (trx SE09 or SE10): after releasing the request the system will move it to the queue of quality system.
After the step A u need to use only the trx STMS in all next enviroments in order to transfer the request to the production.
- B) It needs to import the request to the quality system:
- run trx STMS,
- press the first icon (with a truck);
- double click on the quality queue
- refresh the list;
- place the cursor on the request;
- Go to Request->Import
After importing the requet to the quality, the system will place it in the production queue, so now it needs to repeat the step B, but u have to choose the production queue:
- C) It needs to import the request to the production system:
- run trx STMS,
- press the first icon (with a truck);
- double click on the production queue
- refresh the list;
- place the cursor on the request;
- Go to Request->Import
Sometimes the system is setted not to transfer the request to the next queue after importing it, in this case u need to transfer it by yourself (trx STMS):
After choosing the right queue go to: Request->Forward->System
Anyway yuo should consider the steps above should be done by your basis, so perhaps u have no authoriations to run trx STMS.
Max

Can not import requests in Quality Server

Dear Gurus,
Please find below logs and let me know where error is coming.
We configure some changes and released it to quality server but I am not able to transfer requests in Quality Server and tp system log is as per below.
When I transfer requests it goes in continuously loop mode endlessly. I delete those requests from import monitor queue then restarted it but same results.
Please guide me what to do......
System Log Entries
START imp single DIQ 20140303102340 INSERV01 sapdnl10 20140303102339554
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303102339554
START MOVE NAMETABS DIQ 6 20140303102342 INSERV01 sapdnl10 20140303102339554
START tp_getprots DIQ P 20140303102345 INSERV01 sapdnl10 20140303102339554
START imp single DIQ 20140303102713 INSERV01 sapdnl10 20140303102712936
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303102712936
START tp_getprots DIQ P 20140303102713 INSERV01 sapdnl10 20140303102712936
STOP tp_getprots DIQ P 20140303102849 INSERV01 sapdnl10 20140303102712936
START MOVE NAMETABS DIQ 6 20140303102849 INSERV01 sapdnl10 20140303102712936
START tp_getprots DIQ P 20140303102849 INSERV01 sapdnl10 20140303102712936
STOP tp_getprots DIQ P 20140303103000 INSERV01 sapdnl10 20140303102339554
STOP MOVE NAMETABS DIQ 6 20140303103000 INSERV01 sapdnl10 20140303102339554
START MAIN IMPORT DIQ I 20140303103000 INSERV01 sapdnl10 20140303102339554
STOP tp_getprots DIQ P 20140303103004 INSERV01 sapdnl10 20140303102712936
STOP MOVE NAMETABS DIQ 6 20140303103004 INSERV01 sapdnl10 20140303102712936
START MAIN IMPORT DIQ I 20140303103004 INSERV01 sapdnl10 20140303102712936
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (10), I'm waiting 4 sec (20140303103028). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (10), I'm waiting 4 sec (20140303103032). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (20), I'm waiting 1 sec (20140303103052). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (20), I'm waiting 1 sec (20140303103056). My name: pid 13240
START imp single DIQ 20140303103059 INSERV01 sapdnl10 20140303103059141
INFO TBATG CONVERSION OF DIQ N not needed INSERV01 sapdnl10 20140303103059141
START MOVE NAMETABS DIQ 6 20140303103059 INSERV01 sapdnl10 20140303103059141
START tp_getprots DIQ P 20140303103059 INSERV01 sapdnl10 20140303103059141
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (30), I'm waiting 4 sec (20140303103116). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (30), I'm waiting 4 sec (20140303103120). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (40), I'm waiting 2 sec (20140303103147). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (40), I'm waiting 2 sec (20140303103151). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (50), I'm waiting 2 sec (20140303103222). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (50), I'm waiting 2 sec (20140303103226). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (60), I'm waiting 1 sec (20140303103258). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (60), I'm waiting 1 sec (20140303103302). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (70), I'm waiting 4 sec (20140303103320). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (70), I'm waiting 4 sec (20140303103324). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (80), I'm waiting 1 sec (20140303103357). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (80), I'm waiting 1 sec (20140303103401). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (90), I'm waiting 5 sec (20140303103422). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (90), I'm waiting 5 sec (20140303103426). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (100), I'm waiting 3 sec (20140303103454). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (100), I'm waiting 3 sec (20140303103458). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (110), I'm waiting 4 sec (20140303103524). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (110), I'm waiting 4 sec (20140303103529). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (120), I'm waiting 3 sec (20140303103553). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (120), I'm waiting 3 sec (20140303103558). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (130), I'm waiting 2 sec (20140303103624). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (130), I'm waiting 2 sec (20140303103629). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (140), I'm waiting 2 sec (20140303103656). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (140), I'm waiting 2 sec (20140303103701). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (150), I'm waiting 3 sec (20140303103726). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (150), I'm waiting 3 sec (20140303103731). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (160), I'm waiting 1 sec (20140303103758). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (160), I'm waiting 1 sec (20140303103803). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (170), I'm waiting 4 sec (20140303103824). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (170), I'm waiting 4 sec (20140303103829). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (180), I'm waiting 4 sec (20140303103857). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (180), I'm waiting 4 sec (20140303103902). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (190), I'm waiting 1 sec (20140303103922). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (190), I'm waiting 1 sec (20140303103927). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (200), I'm waiting 2 sec (20140303103948). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (200), I'm waiting 2 sec (20140303103953). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (210), I'm waiting 5 sec (20140303104018). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (210), I'm waiting 5 sec (20140303104023). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (220), I'm waiting 3 sec (20140303104046). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (220), I'm waiting 3 sec (20140303104051). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (230), I'm waiting 4 sec (20140303104118). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (230), I'm waiting 4 sec (20140303104122). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (240), I'm waiting 2 sec (20140303104156). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (240), I'm waiting 2 sec (20140303104200). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (250), I'm waiting 2 sec (20140303104225). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (250), I'm waiting 2 sec (20140303104229). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (260), I'm waiting 5 sec (20140303104256). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (260), I'm waiting 5 sec (20140303104300). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (270), I'm waiting 1 sec (20140303104331). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (270), I'm waiting 1 sec (20140303104335). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (280), I'm waiting 5 sec (20140303104356). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (280), I'm waiting 5 sec (20140303104400). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (290), I'm waiting 2 sec (20140303104425). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (290), I'm waiting 2 sec (20140303104429). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (300), I'm waiting 3 sec (20140303104459). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (300), I'm waiting 3 sec (20140303104503). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (310), I'm waiting 2 sec (20140303104529). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (310), I'm waiting 2 sec (20140303104533). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (320), I'm waiting 2 sec (20140303104559). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (320), I'm waiting 2 sec (20140303104603). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (330), I'm waiting 3 sec (20140303104629). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (330), I'm waiting 3 sec (20140303104633). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (340), I'm waiting 2 sec (20140303104700). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (340), I'm waiting 2 sec (20140303104704). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (350), I'm waiting 5 sec (20140303104725). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (350), I'm waiting 5 sec (20140303104729). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (360), I'm waiting 1 sec (20140303104759). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (360), I'm waiting 1 sec (20140303104803). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (370), I'm waiting 4 sec (20140303104828). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (370), I'm waiting 4 sec (20140303104832). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (380), I'm waiting 3 sec (20140303104858). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (380), I'm waiting 3 sec (20140303104902). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (390), I'm waiting 4 sec (20140303104922). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (390), I'm waiting 4 sec (20140303104926). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (400), I'm waiting 2 sec (20140303104959). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (400), I'm waiting 2 sec (20140303105003). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (410), I'm waiting 2 sec (20140303105025). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (410), I'm waiting 2 sec (20140303105029). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (420), I'm waiting 3 sec (20140303105046). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (420), I'm waiting 3 sec (20140303105050). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (430), I'm waiting 5 sec (20140303105119). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (430), I'm waiting 5 sec (20140303105124). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (440), I'm waiting 5 sec (20140303105151). My name: pid 12312
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (440), I'm waiting 5 sec (20140303105156). My name: pid 13240
WARNING: \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ is already in use (450), I'm waiting 4 sec (20140303105217).

Hi Irin,
Just rename this file \\sapdnl10\sapmnt\trans\tmp\DIDKK902769.DIQ
and start the import again.
Hope this helps.
Regards,
Deepak Kori

Issue in Importing request from Quality to Production

Similar Messages

Maybe you are looking for