topic Re: implement snote in production system in Application Development and Automation Discussions

implement snote in production system

former_member547765 — Mon, 18 May 2020 07:48:15 GMT

Hi,

I want to implement snote in sap hana production system.

and it show pop-up "Changes to repository or cross-client customizing are not permitted".

the snote is already implement manually in DEV and QAS system.

can i just transport from dev or qa to production system for the snote?

is it ok if i perform the snote from production system?

Regards

Re: implement snote in production system

sumitjais — Mon, 18 May 2020 07:51:43 GMT

You shouldn't implement any note in Production directly . Transport the implemented change you did in DEV and tested in QAS.

Re: implement snote in production system

former_member644293 — Mon, 18 May 2020 09:02:42 GMT

Please follow the practice of moving the changes from development system to keep all systems in the landscape in sync.

Regards,

Re: implement snote in production system

former_member547765 — Mon, 18 May 2020 09:10:02 GMT

Hi sumitjais

the last time I had implemented successful for snote 2836302 manually for DEV and QAS system.

here is my capture from QAS system

how can i transport to production system ?

Re: implement snote in production system

sumitjais — Mon, 18 May 2020 09:50:46 GMT

Irfan, If the transport is created in DEV and imported in QAS , it will be there in Production transport queue already ( you just have to import in PRD the way you did in QAS) . Please share the transport route snapshot. ( tcode STMS --> Overview --> Transport routes)

Re: implement snote in production system

former_member547765 — Mon, 18 May 2020 14:36:42 GMT

Hi sumitjais

here is the transport routes

i login to my dev and running stms, there is no request number like i mention in capture screen before, how can i able to transport from QAS to PRD system?

Regards

Re: implement snote in production system

former_member547765 — Mon, 18 May 2020 14:38:14 GMT

Hi,

thank you for the advice,

this is the first time i make transport

Regards

Re: implement snote in production system

sumitjais — Mon, 18 May 2020 16:55:31 GMT

Hi Irfan,

You cannot import a transport created in QAS to Production directly.

Let me explain you.

In your landscape , you have consolidation route ( DEV to QAS) and Delivery route ( QAS to PRD).

Any transport (to be imported) to next system must have been created with "consolidation route" and have a transport layer. After this, it can be imported to multiple delivery route . If you create a transport in QAS, it's delivery route directly and has no package to associate with. So, it will be a local transport ( i.e. if you release this transport, it won't create datafile/cofiles which get imported to next system). For the same reason, your transport has "Target" blank.

So, to import the changes you made, you find the transport that was created in DEV for the sapnotes and ensure it has "target" before it is released. Finding the transport request is not difficult. Open the note in SNOTE browser (DEV) and click on it to see Note log, Click on NOte log and you will see the transport number in which the objects were recorded.

Implementing notes directly into Production is the last and least preferred option.

Re: implement snote in production system

former_member547765 — Tue, 19 May 2020 02:45:58 GMT

Hi sumitjais

Thanks for the explanation.

i have found the transport number in DEV system,

since i already implement manually for the snote in QAS system, should i transport again to QAS system after that transport to PRD system?

Regards

Re: implement snote in production system

sumitjais — Tue, 19 May 2020 03:51:40 GMT

Ensure the transport in DEV should not be local while releasing.

If you can de-implement the sapnote in QAS, it's better do that and import the transport from the DEV . If not transport possible to de-implement, import the transport in QAS with "overwrite original" option and then to Production.

Re: implement snote in production system

former_member547765 — Tue, 19 May 2020 04:58:50 GMT

Hi sumitjais

i choose to transport in QAS with "overwrite original" option.

so i have to look for request number from QAS system right?

here is the request number:

so i have to release that request and start transport?

Regards

Re: implement snote in production system

sumitjais — Tue, 19 May 2020 05:39:59 GMT

Let your transport in DEV is DEVK9XXXXX and the one you created in QAS is QASK9XXXXX.

In DEV - You login to DEV , check DEVK9XXXXX which should show target as QAS. Release DEVK9XXXXX

Now login to QAS, the transport DEVK9XXXXX should be in transport queue already in STMS. ( if not add it). Import DEVK9XXXXX ( and not QASK9XXXXX) with option" Overwrite Originals"

Then import DEVK9XXXXX in Production .

Re: implement snote in production system

former_member547765 — Tue, 19 May 2020 07:37:03 GMT

Hi sumitjais

"Now login to QAS, the transport DEVK9XXXXX should be in transport queue already in STMS" this mean i have running stms from QAS system?

i have released the request from DEV system.

regards

Re: implement snote in production system

sumitjais — Tue, 19 May 2020 08:00:55 GMT

Yes , now go to STMS of QAS to import the same . While3 importing Select "Overwrite Originals"

Re: implement snote in production system

former_member547765 — Wed, 20 May 2020 03:01:49 GMT

Hi sumitjais

thanks for the response

the transport running with error occured (RC=8)

R3TRCINS002075125841 was repaired in this system

Message no. TW104

Diagnosis

Object R3TRCINS002075125841 is in repair status. Therefore, it cannot be 
imported.

System Response

The object is not imported.

Procedure

If you still want to import the object, release the relevant repair and 
repeat the import.

maybe something went wrong when I did the release 😄

btw what the mean of "Ensure the transport in DEV should not be local while releasing"?

Regards

Re: implement snote in production system

sumitjais — Wed, 20 May 2020 05:46:33 GMT

Irfan,

Reason : The objects still have repair flag and are locked in other transport.

Release the older transport QAS9XXXX that you created in QAS ( this will be local transport as it has no consolidation route).

Once released , try again importing DEV9XXXX in QAS STMS with overwrite originals.

"Ensure the transport in DEV should not be local while releasing"?

A local transport is the one that does not have consolidation system (QAS in your case) as target and this if released won't create datafile and cofiles . As no files created on release, it cannot be imported in another system.

Re: implement snote in production system

former_member547765 — Wed, 20 May 2020 07:23:45 GMT

sumitjais

the transport request success

i also see it is ready to transport for production system, so i just continue transport to prod system right?

Regards

Re: implement snote in production system

sumitjais — Wed, 20 May 2020 07:57:42 GMT

yes. go ahead

Re: implement snote in production system

former_member547765 — Wed, 20 May 2020 08:14:53 GMT

sorry i think i have to update my st-pi and st-a/pi first on production system, since i have running update in DEV and QAS system

so it will match component version.

by the way, after I success transport to the PRD system the status of the snote in the transport request will become implemented status in PRD system, correct?

Regards

Re: implement snote in production system

sumitjais — Wed, 20 May 2020 08:48:24 GMT

you are right