cancel
Showing results for 
Search instead for 
Did you mean: 

STMS - <transport> is missing in table E070.

Private_Member_19084
Active Contributor
0 Kudos

Hi experts,

after we have done a system copy with SWPM, we get sometimes an error in executing transports via STMS.

The error is "Internal error <tranport order> is missing in table E070".


Does anybody know what it means?

Thank you

Accepted Solutions (1)

Accepted Solutions (1)

divyanshu_srivastava3
Active Contributor
0 Kudos

E070 is the table which includs - Change & Transport System: Header of Requests/Tasks

Use Se06 and STMS to reconfigure TMS.

Also, if required, goto see SE11 and activate it.

Regards,

Private_Member_19084
Active Contributor
0 Kudos

I already did se06... I did now activate se11.

Maybe it helps.

Private_Member_19084
Active Contributor
0 Kudos

One other question.

We have a 3 system landscape

And the error appears on transport to productive system.

In E070 I can see the transport, however with targetsystem "Quality".

In Table E070 in Productive and quality system.

May it be, that this is the problem and the transport-landscape is not correct, because in E070 of prod sysetm it should be target system producitve-system I guess.

divyanshu_srivastava3
Active Contributor
0 Kudos

I didn't get this completely. You can try to reconfigure TMS and hope that helps.

Sriram2009
Active Contributor
0 Kudos

Hi Christian

After completed the system copy, have you reconfigure the TMS? & post system copy tasks?

BR

SS

Former Member
0 Kudos

hi Christian,

The issue is with your STMS configuration so request you to re-run the SE06 & STMS configuraiton as suggested earlier.

And normaly the E070 entry depends on the Next system in the Transport layer which you have created.

So try to reconfigured it and see if the STMS configuration is Consistent to. If its shows error try to remove the system from Domain controller and add it back again in Domain controller.

Let us know the outcome.

Regards,

Ram

Private_Member_19084
Active Contributor
0 Kudos

yes I did.

And transporting works, but I get that error.

Private_Member_19084
Active Contributor
0 Kudos

maybe I did something wrong. And I executed Se06 in new taget system of the copy.

How do I have to execute se06?

- take over originals?  - I did "no"

- tms configuration delete - I did no

- delete transport-ways - I did no

divyanshu_srivastava3
Active Contributor
0 Kudos

Delete everything, and start  TMS setup again

Refer -

SE06 - Processing after Installation of CTO - Basis Corner - SCN Wiki

divyanshu_srivastava3
Active Contributor
0 Kudos

How do I have to execute se06?

- take over originals?  - Do yes

- tms configuration delete - Do yes

- delete transport-ways - Do yes

Former Member
0 Kudos

Hi Christian,

This Selection should be fine for the SE06 post processing.

Do you have the screenshot for the old entry or the export taken.

Normally at my end we take the E070 and other TMS* tables export and keep it handy.

Also the Re-configuration might solve your issue and do sync up with the Domain Controller.

Regards,

Ram

Sriram2009
Active Contributor
0 Kudos

Hi Christian

1. Could you check the status of system copied system on TMS domain controller?

2. Could you refer the document for reconfiurations

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=0CCsQFjAB&url=htt...

BR

SS

manumohandas82
Active Contributor
0 Kudos

Hi Christian ,

Perform as sugggsted by Divyanshu  above  ( in the target system )and then  go to transaction STMS , add the system to the transport controller  ( it will pop up by default if it is sharing the  /usr/sap/trans as that of the domain controller )

Click on transport routes  ( Menu STMS )  ,  in the menu options  Configuration - > Adjust with domain controller

Thanks ,

Manu

Answers (1)

Answers (1)

Private_Member_19084
Active Contributor
0 Kudos

Hello together,

I've now done the remove via SE06 and also did setup again via STMS:

however, I still get the same error message.

Any other ideas?

Kind regards

divyanshu_srivastava3
Active Contributor
0 Kudos

HI Christian,

Lets be precise - "we get sometimes an error in executing transports via STMS."

Is that the same system copy that you did from Production to Development ?

When do you get the error message - what is the exact actions that you perform ?

Regards,

Private_Member_19084
Active Contributor
0 Kudos

Hello Divyanshu,

today I made 3 test-transports and I got it for each.

We did a DB-Refresh with SWPM.

After that I did SE06 and delete the configuration.

Next, I did go to domain controller, delete the system. In the target system I did go to stms and create it again. Next i did go to domain controller again and did accept the system.


And thatn I tried a test-transport.

Kind regards

manumohandas82
Active Contributor
0 Kudos

Hi Christian ,

Did you add the transports manually to the queue  of the target system ?

What do you mean by a test transport  [ Ie , Are you using the solution manager to create test transports [Charm] or Are you using a transport of copies method ] ?

Thanks ,

Manu

Private_Member_19084
Active Contributor
0 Kudos

No, I did not add it manually.
I did just create a change and did tranpsport it till productive system.

manumohandas82
Active Contributor
0 Kudos

Got you , The test transport is just a tr created by you for test purpose  [ Dont know why you imported this in prod anayways ]

But you are facing the issue in Quality Only right ? [ ie the  restored system ]  ?

Can you execute the following in Quality ,[ Check both options while you run  ] and send back the screenshot

RDDIT049 [ Run in SE38 ]

Also need a screenshot for TXN STMS -> Monitor -> TMS alert -> TMS ALert Viewer

Also check whether the Time is in sync between DEV , QA . [ Run RSDBTIME in se38 in DEV and Quality  and compare ]

Thanks ,

Manu

divyanshu_srivastava3
Active Contributor
0 Kudos

IN which system are you getting this error ? Dev Qa or Prod ?

Private_Member_19084
Active Contributor
0 Kudos

If i transport to Q-system (this is the updated (target of copy)) I get that error in tms.

Private_Member_19084
Active Contributor
0 Kudos

Hello Manu,

not exactly.

Since yesterday we also did refresh our dev-system and we get the error on transporting from dev into qual and also from qual into prod.

I did steps written above (se06 and stms) in both systems.

Here are the output I did in qual system (sysetm which was refreshed 1st time).

manumohandas82
Active Contributor
0 Kudos

When you refreshed your development system did you increase the development system  transport number  in table E070L


Can you post the contents of the table E070L from the development box .   ?


And the last TR released from DEV before the refresh


Thanks ,

Manu

Private_Member_19084
Active Contributor
0 Kudos

What do you mean with "increase"?
The transport number is still unique and a rolling number, which was not resetted to another value if you mean that.

Kind regards

Private_Member_19084
Active Contributor
0 Kudos

So you want the number, or should I compare the number already with another value?


In quality system it is <SID>K900635 and in dev system it is <SID>K971892.

Kind regards

manumohandas82
Active Contributor
0 Kudos

Hi Christian ,

This is just a doubt

The E070L Stores the last TR sequence number  ( last number of Change request created ) ,  So when you refresh from PROD to DEV  the  value of the field TRKORR needs to be updated .

As any new TR's generated from DEV will again start from this value . Check the following link .

So check whether the value of this entry is correct  [ Compare with the number which is last exported from DEV before refresh ] . If the new TR's created has a number greater than the above number [ the number before refresh ] then  you are fine .

Thanks ,

Manu