QAS_30584_2014
-
Upload
navin-singh -
Category
Documents
-
view
212 -
download
0
description
Transcript of QAS_30584_2014
-
Transport request not able to be imported in QAS ( 0000030584/2014 )
Back Print
Classification
Message 30584 / 2014
created 13.01.2014 - 15:39:27 INDIA
Reporter Mr Jayesh Lapasia
Customer Anushakti Chemicals & Drugs Ltd (996524)
Last change 13.01.2014 - 16:19:36 INDIA by SAP
Status Customer Action
Automatic closing of message on 27.01.2014
Language English
Component BC-CTS-TMS
Priority Very High
Problem is business-critical, has serious consequences for business operations and requires an immediate solution. To guarantee 24/7
support, create your message in English.
A prerequisite for a Very High priority message is that either the problem occurs in a production system or an imminent go-live/upgrade
is jeopardized. If a go-live/upgrade is jeopardized, enter a Go-live/Upgrade date in the Business Impact section.
Affected System
System ID / Name QAS / SAPDEV01
Installation No. / Name 0020405173 / ERP T
System Type Test system
Product Version SAP ERP 6.0
Operating System NT/INTEL WIN2008
Database MSSQLSRV 2008 R2
Technical Usage Type ERP Central Component (ECC)
Changed on 25.01.2013 by SAP EarlyWatch Alert Service
Connection Status Access Data Provided / Connection Open
Business Impact
Create a new Business Impact (optional)
Business Impact History
-
13.01.2014 - 15:39:33 INDIA - Business Impact by Mr Jayesh Lapasia
A live system is not operational No
Pending GoingLive or Upgrade Is at Risk Yes
GoingLive/Upgrade Date 15.01.2014
Core business processes are affected and are at serious risk No
Estimated Financial Loss during the Next 24 Hours
(Please specify currency) NA
Number of Affected Users 10
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Description of Business Processes w ith Business Impact:
Request are not been able to be imported to QAS system due to w hich
all development w ork is stuck and cannot be moved into PRD system
Connection open
With Semi Automatic Opening you can enable SAP to open service connections to your systems independently - at any time
and w ithout customer interaction.
Access data provided Make sure to maintain your 24 hour contact w ithin the Contact Persons section below !
Problem Details: Transport request not able to be imported in QAS
Short Text
Transport request not able to be imported in QAS
Long Text
We are not able to import any request in QAS system from Development
system due to w hich all developmental w ork w hich has been done in
development system is stuck and cannot be moved into PRD system. for
eg -
TR DEVK912427
Its quite urgent.
USER id - hoailanu
Passw ord - rahul123
Rahul Nathani
9833931354
Steps for Reconstruction
Error Message Number Screen Number Transaction Program Table
-
Communication
13.01.2014 - 16:12:31 INDIA - Reply by SAP Dear Rahul,
Since there are no CTS+ transports involved, We've corrected the
component of this message to BC-CTS-TMS
I logged and checked the issue.
As you can see in SLOG from QAS, it is full of:
WARNING: Background job RDDIMPDP could not be started or terminate Please check that
the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This w arning is harmless if no further w arnings follow .)WARNING: System
QAS. Warning. 20140113160457 :
WARNING: Background job RDDIMPDP could not be started or terminate Please check that
the R/3 system is running.
Please check the system. Use transactions SM21, SM37, SM50.
WARNING: (This w arning is harmless if no further w arnings follow .)
w hich means there are problems to trigger RDDIMPDP. Checking it in
SM37 I see it has a high delay.
Can you please do the follow ing?
1. Please logon to both 000 and other transport involved clients (500)
as a DDIC user and execute the RDDNEWPP report (w ith transaction
SA38 or SE38).
2. Kindly remove the tp hanging entries from the Import Monitor
3. Ensure that clogged entries does not exist in TRBAT & TRJOB table
entries. There is currently one entry in TRBAT, if still exist,
please remove it.
4. Now remove these transport requests from the Import queue.
Now , please re-add these requests w ith the corresponding target clients
and import them.
Please read further on attached note
71353 Transports hang during background steps
Thanks and kind regards,
Javier Hernanz
-
SAP Product Support # NW CORE
=============================================================
DID YOU KNOW? There is a new SAP Support TWITTER Channel
w here you can see the last new s of SAP Support:
http://w w w .tw itter.com/SAP_GSupport
=============================================================
Contacts & Notifications
Name Phone Number Mobile Telephone E-Mail Notif ication
Reporter Mr Jayesh Lapasia +91 67976641 +91 67976641 [email protected] By SMS By e-mail
24h contact * Mr Jayesh Lapasia +91 67976641 +91 67976641 [email protected] By SMS By e-mail
Opening System Other By SMS By e-mail
Other By SMS By e-mail
Other By SMS By e-mail
* 24h contact must be named for messages w ith Very High priority
Back Print