How to recall Transport request

[sumanth_naidu]

Hi All,

Recently we have moved an transport request of an validation to production which has changed all the sets contents in that particular comapnay code in the production. Please help us to retrive the data as it is in the production befor the transport request is moved.

Please help me out in solving this issue.

Thanks,

Nandu

[former_member1245113]

Hi

In Development Client go to UTILITIES --> VERSIONS --> VERSION MANAGEMENT then all the versions are displayed

select the older versions and Click on the Retrieve button.

then make a fresh Request and Transport it back to Production

This is the only method to restore the previous code to the best of my knowledge

Cheerz

Ram

[sumanth_naidu]

Hi Ram,

As i explained earlier we have moved an transport request to production which changed (overwrited) all the sets in GS02 which we dont wanted to happen in production system. Now we want the data which is present before moving that Transport request to prodcution.

Thanks,

nandu

[Former Member]

Hi

Do one thing.

In Dev/QA retrieve the previous request and again transport it to production.

Hope it helps.

Rgs,

Priya

[sumanth_naidu]

Hi Ram,

where can i find teh version option.

Thanks,

Nandu

[Former Member]

ABAP Objects have version management in Development...look under Ultilities>Versions>Version Mgmt. Here you can retrieve the prior (to your transport) version, make that the current, and transport that (as a new request) through your landscape. Note that this will NOT, however, fix any database table destruction which may have occurred in the current Production version.

[arul_murugan]

Hi,

go to utilities->verison->version managenent .

Check the check box with the version that u want and click on the retrieve and activate the program and move it across servers'

Thanks

Arul

[Former Member]

I believe you're asking about retrieving the actual data content of the tables prior to the erroneous transport? It sounds like the objects transported to production destroyed vital data? If so, your title is quite misleading.

If it happened yesterday, perhaps Basis could help by restoring tables, but that is rarely ever a solution; the system is so integrated that that could result in "widowed" or "orphaned" entries in other tables. And, restore would certainly result in more lost data from logistics/FI/other modules.

Perhaps there's change management turned on so that you can see the data values in the tables before the transport? Probably not, though, if your program wrote directly to the tables. If not, one must, via SAP transaction, put back the data values that were destroyed manually, which will no doubt be a very tedious and painful process.

This situation demonstrates why we should avoid writing programs that directly update database tables. Best practice is to utilize BAPIs, or Call Transaction technology, etc., to utilize SAP's programming to update tables, and then only after complete testing and data validation in a Quality/User Test instance.

[adrian_dorn]

>

 sets

What exactly do you mean by the term "SETS"?

I think everyone in the topic is assuming that by "SETS" you mean ABAP-programs. In that case the solution is to go into the Version Managment of the ABAPs as described by Ram and Break-Point.

However: if you mean something different when you use the term "SETS", then obviously the Version Managment approach will not work.

[sumanth_naidu]

useful thoughts