Very slow STMS import...

[joo_migueldimas]

Hello,

We´re facing some problems when we import any transport order in our QAS (quality system)... It takes a very long time to finish the import process in this system! (We see the truck icon for a long time). We don´t understand yet what is the reason for this delay in importing process! Why this happens?

Can you help me?... How can I solve this problem?

Kind regards,

João Dimas - Portugal

[Former Member]

There could be different reasons.Starting point might be checking the logs of the transport that you are running.

Thanks,

Naveed

[joo_migueldimas]

Hello Navved, thanks for your answer...

I checked the last ULOG:

APServiceDEV 20101011160429 RFC: tp EXPCHK DEVK905592 pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL -Dtransdir=\beja015sapmnt	rans  (pid=4920)
APServiceDEV 20101011160434 RFC: tp WRITELOG DEVK905592 pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL e 0000 DEV -Dtransdir=\beja015sapmnt	rans  (pid=4920)
APServiceDEV 20101011160434 RFC: tp EXPWBO DEVK905592 client020 pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL FEEDBACK ASYNCEXP -Dtransdir=\beja015sapmnt	rans  (pid=4920)
APServiceQAS 20101011160514 RFC: tp IMPORT DEVK905592 QAS client020 pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL FEEDBACK ASYNCIMP -Dimpmon_mode=DETAILED -Dtransdir=\beja015sapmnt	rans  (pid=2972)
APServiceDEV 20101011161658 RFC: tp COUNT DEV pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL -Dtransdir=\beja015sapmnt	rans  (pid=4844)
APServiceQAS 20101011161658 RFC: tp COUNT QAS pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL -Dtransdir=\beja015sapmnt	rans  (pid=12420)
APServicePRD 20101011161658 RFC: tp COUNT PRD pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL -Dtransdir=\beja015sapmnt	rans 
APServiceDEV 20101011162917 RFC: tp COUNT DEV pf=\beja015sapmnt	rans inTP_DOMAIN_DEV.PFL -Dtransdir=\beja015sapmnt	rans  (pid=4344)
...

I checked another thing that I guess (because I read in other places that it is important for importing process)... I´m talking about Job RDDIMPDP (In our landscape we have three systems (DEV; QAS and PRD) and I checked if this job is released or not...):

- In DEV system:

Client 000 - Is not in released status, but instead it has a trigger SAP_TRIGGER_RDDIMPDP and I guess the job only runs after I certainly event event with job frequency (Event periodic).

Client 020 - It have the same definition as client 000.

- In QAS system:

Client 000 - Status: Released, with Job Frequency 5 Minute(s).

Client 020 - Released, with Job Frequency 5 Minute(s).

- In PRD system:

Client 000 - Is not in released status, but instead it has a trigger SAP_TRIGGER_RDDIMPDP and I guess the job only runs after I certainly event with job frequency (Event periodic).

Client 020 - It have the same definition as client 000... it doesn´t run since Setember 30.

Any problem here?!

Best regards,

João Dimas - Portugal

[Former Member]

Hi,

Also you can look at file SLOG, RDDIMPDP is the job that should be running for transports to work.

This job usually runs Job classification C, try changing it to A, if it is permitted.

Regards,

Vishnu

[joo_migueldimas]

Hello vishnuarigela,

The problem was solved. I run the program RDDNEWPP in client 000 with DDIC and in other clients logged with administration user. The problem was in the Job RDDIMPDP that was in released state and it running every 5 minutes, this Job should be released after the event SAP_TRIGGER_RDDIMPDP

Kind regards,

João Dimas - Portugal