topic Re: Transport Sapscript form issue in Application Development and Automation Discussions

Transport Sapscript form issue

Former Member — Tue, 18 Aug 2009 16:47:03 GMT

Hi friends, I trying to transport a Sapscript form from DEV100 to QAS400. I changed it and save on a request, so I went to stms and made a import but the form don't update inn QAS. I tried use RSWBO052 too, but without sucess. Whats I doing wrong?

Thanks!

Re: Transport Sapscript form issue

brad_bohn — Tue, 18 Aug 2009 17:08:56 GMT

Lots of things could be wrong - did you look at the import log? Are you importing to client 400 or to another client? What does your transport landscape look like? What does the generation step show in the import log? Is there an open repair for the form in that client? Is the form active or non-active in that client? Is there actually an R3TR FORM object in that transport?

Re: Transport Sapscript form issue

Former Member — Tue, 18 Aug 2009 17:13:14 GMT

Hi,

From the development and staging servers mentioned, it looks like developmet has client 100 and staging has client 400. Usually, the same client is used in SAP Landscape from dev to stag to prod.

Confirm from BASIS that your path for transport is configured from DEV client 100 to QAS client 400. If not, it may be the case that transports are happening on one of the same clients, either 100 or 400.

Since SAPScripts are client dependent, in such a scenario, you will have to get the SAPScript transported to the needed client in dev itself first. You can use transaction SCC1 for this.

Regards,

Shiva

Re: Transport Sapscript form issue

Former Member — Tue, 18 Aug 2009 17:14:12 GMT

Thanks Shivanand Patil, Brad Bohn.

I tried made new request, only with the form and it works...I don't undertood, but works...

Edited by: Fulvio Valente on Aug 18, 2009 7:14 PM

Edited by: Fulvio Valente on Aug 18, 2009 7:16 PM

Re: Transport Sapscript form issue

Former Member — Mon, 27 Aug 2012 07:28:15 GMT

Hi Fulvio,

I have the similar issue now about why some forms are missing although we specified the target client explicitly during the import. Do you have any idea what was the root cause?

Regards,

Yohanes