Package transport

[Former Member]

As an ABAPer, We normally store project related files in a package and then we transport that package from DEV (client 100) to QA (client 200) system using SE09.

1. By mistake if we send that package to different system instead of QA..How to retrieve it back to DEV system?

2. If we have custom table which is client specific (MANDT) related to that project, will this table works in different client?

[Former Member]

As an ABAPer, We normally store project related files in a package and then we transport that package from DEV (client 100) to QA (client 200) system using SE09.

1. By mistake if we send that package to different system instead of QA..How to retrieve it back to DEV system?

2. If we have custom table which is client specific (MANDT) related to that project, will this table works in different client?

[Former Member]

As of my knowledge i dont think retrieve it back.Just ask them transport to ur system.

[former_member16553]

Hi

    Transport system is one way in SAP.  Transport again to desired client

[Former Member]

Thanks Girdhari....so do I need to create a package once again in my Dev sys or will be available in Dev sys for transport.

[Former Member]

The package should exist in the Development system. I don't think you need to create it all over again.

Check for it once....

Aastha

[Former Member]

Ya sure thanks I'll check this..............

[Former Member]

Hi,

There is no way that you can retrieve it back from the system you have transported it to.

Hence, make a fresh transport to the desired system.

Also, a client-dependent table has the field MANDT of data type CLNT, which indicates Client id and

a client-independent table does not have this field. So, the table must not work in the other client.

Please let me know in case you have any further queries.

Regards,

Aastha

[Former Member]

Thanks Aastha.....so do we normally create this MANDT field? when we already know that we have send this to QA sys.

[Former Member]

Yes, we certainly create the Mandt field to ensure that the table is client specific.

[Former Member]

Hi,

>> 1. By mistake if we send that package to different system instead of QA..How to retrieve it back to DEV system?

In the answer to your first question, I can say in any landscape the DEV system is always connected to QAS system and the QAS is connected to Pre-PRD or PRD system. So, if you release any transport from development, it'll always go to quality.

>> 2. If we have custom table which is client specific (MANDT) related to that project, will this table works in different client?

I'm not sure about your second question. Can you please explain in details.

Regards,

Samir

[Former Member]

Hi ,

its your Basis people job,

just ask them to revert it.

and coming to your second question :the table you released will not show any data as it is client dependent.

regards,

Raj..

[Former Member]

@gachollo.......so how to send the data then?

[former_member213851]

Hi ,

>> 1. By mistake if we send that package to different system instead of QA..How to retrieve it back to DEV system?

Regarding your first question, the package sfter release from Dev system will remain in DEV system too after release . So no need to retieve back it again. If you have send the package to some different system, then ask the Basis team to re-import the earlier version of the objects in the package on the target system.

>> 2. If we have custom table which is client specific (MANDT) related to that project, will this table works in different client?

If MANDT field is present in Table then it implies that Table is client specific or client dependatnt  i.e. values and data in that table will be available on that client only.

So in order to have that values in the other clients, you need to maintain the values on taget client using SM30. you can only maintain values for table if it's table maintenance is generated.

Now if their are too many value in the table that you need to maintain, you need to create BDC program so tah tthe values maintained in the excel file can be uploaded on your target client.

Best Regards,

Sachin

[Former Member]

hello,

if we try to transport the request  to a new system by mistake using se09,we cannot retrieve it back.

if it got affected in that system due to our released TR ,we have to create a new TR(transport request) that will rectify the change in the affected system.

regards,

Namitha