Problems transporting SAP Script

[Former Member]

I've made some modifications to a previously existing "Z" sapscript. The changes were made and tested in our development client and they're working as desired. However, I've encountered an issue trying to move the modified sapscript across our system landscape.

When the change was made I was prompted for a transport and I created one at this time. In our dev environment I used SCC1 to copy the transport to another client within the same environment and the changes were successfully moved. When I requested our BASIS folks to move the transport to our QA environment, the transport log show everything successful (0), but my changes aren't in QA. The transport was also moved across all DEV clients and oddly enough the changes I copied with SCC1 are also gone.

If I use SCC1 again and copy the same transport, I see the expected changes in my sapscript.

Does anyone have any idea what could be causing this?

er

[Former Member]

Hi,

Just make sure basis team transported it to the required client in Quality. If you have multiple clients.

[Former Member]

Hi,
Just make sure basis team transported it to the required client in Quality. If you have multiple clients.

Transport logs show that is was successfully copied to all the desired clients in quality.

[Former Member]

Try activating it.

Rob

[Former Member]

Try activating it.
Rob

The "activate" option is greyed out so I'm assuming that the form is already active. In fact I'm able to print the form in quality, it just doesn't have the changes I made.

[Former Member]

You probably aren't authorized to activate - get Basis to try this.

Rob

[Former Member]

On the administrative data area, is the status "active - saved"?

Rob

[Former Member]

On the administrative data area, is the status "active - saved"?
Rob

It is "active - saved" in both QA and DEV. Also, my security is pretty much wide open in both Dev and QA so I don't think it's an authorization issue with activation.

Any other ideas?

[awin_prabhu]

Client in development system corresponding to the client in QA should have the changes.

For example, consider you do all changes in client 010 in Development system, and your QA client is 011.

Then you need to client copy the changes done in 010 to 011 in the development system before releasing to QA.

If the developement client in DA and client in QA are same, then we do not need the client copy.

In your case, i think both clients are different, so you need to do client copy in DA for client in QA everytime before releasing to QA.

Hope you can understand.

[Former Member]

Client in development system corresponding to the client in QA should have the changes.
For example, consider you do all changes in client 010 in Development system, and your QA client is 011.
Then you need to client copy the changes done in 010 to 011 in the development system before releasing to QA.
If the developement client in DA and client in QA are same, then we do not need the client copy.
In your case, i think both clients are different, so you need to do client copy in DA for client in QA everytime before releasing to QA.
Hope you can understand.

The changes were made in Dev Client 300. As part of the basis role the move the transport to the other 3 dev clients (400, 600, 700). Once moved in all Dev environments, the transport is then moved to the QA system and it's clients. This method has worked for thousands of transports and I've never encountered this issue. It seems to be specific to the sapscript but I haven't been able to find any reason why.

[Former Member]

Hello Elder Ribeiro ,

Try the option that "Rob Burbank" mentioned. Did you check with your basis and request them to activate the SAPSCRIPT again in QA or re transport the same SAPSCRIPT again and see.

Thanks,

Greetson

[Former Member]

Hello Elder Ribeiro ,
Try the option that "Rob Burbank" mentioned. Did you check with your basis and request them to activate the SAPSCRIPT again in QA or re transport the same SAPSCRIPT again and see.
Thanks,
Greetson

Hi Greetson, thanx for the reply.

I've had basis try and reactivate and it is already active. Also, had them re transport the sapscript again (with original and new) transport and the issue persists. If I SCC1 the transport within the DEV clients the changes I made are present. If I have basis transport the changes (using stms) to all the Dev and QA clients, my changes are not present and the previously SCC1 client no longer has the changes either.

[Former Member]

Then something worg on your system Transports/ Transports path that is related to the SAPSCRIPTS.

Did you transport any other SAPSCRIPT objects recently?

Did you upgrade recently in your landscape? if this is happening only after the upgrade?

If no other way try to contact SAP .

Thanks,

Greetson

[Former Member]

If it is active and saved, what is the date and userid on that tab?

Rob

[Former Member]

If it is active and saved, what is the date and userid on that tab?
Rob

The Changed on date is today and the user is DDIC. The date/time reflect the last time I had Basis retry moving it for me, although the changes aren't present.

We recently did a system stack upgrade and this is the first sapscript transport we have tried to move since then...perhaps related??

[Former Member]

Issue was resolved...and it was something a previous user suggested.

Once I reactivated the SAP Script everything worked fine....major oversight on my part.

Thanx everyone.

[kiran_k8]

Riberio,

If your problem is solved then fine,else also check in which LANGUAGE of the Script you made the changes as the script can exist in multiple languages.If you have done a change with EN for a script I think those changes will not be available for DE or any other  language.Scripts we need to be careful even from this aspect.

K.Kiran.