implement snote in production system

[former_member547765]

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

[former_member547765]

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

[sumitjais]

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

[former_member547765]

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

[sumitjais]

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.

[former_member547765]

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

[sumitjais]

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.

[former_member547765]

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

[sumitjais]

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 .

[former_member547765]

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

[sumitjais]

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

[former_member547765]

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

[sumitjais]

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.

[former_member547765]

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

[sumitjais]

yes. go ahead

[former_member547765]

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

[sumitjais]

you are right

[former_member547765]

Hi sumitjais

thanks, i have success transport to production system, but i have another case 😄

here is my the snote when i running RCWB_TCI_DIGITSIGN_AUTOMATION in QAS system :

the snote in step 10 includes this snote:

RCWB_TCI_DIGITSIGN_AUTOMATION in PRD system:

Step 10 download and implement SAP note: 0002721941

How can i transport for snote 2721941 from QAS system to PRD system?

since snote 2721941 is the part in step 10 in QAS system

Regards

[sumitjais]

I am sorry but I could not understand the issue here.

The step 10 in QAS is downloading 2869143 .

Do you mean - the step 10 in PRD is downloading another note 2721941 ( and 2869143) ?

Is the last screen shot " Load the ..." from QAS?

[former_member547765]

Yes ,

the step 10 in QAS downloading note 2869143

and in PRD

step 10 is downloading for note 2721941

here is capture screen from PRD

[sumitjais]

Looks like all other notes ( 2869143, 2589007, etc..) have already been imported in PRD with the transport , so it's waiting for what is not imported ( maybe captured in some another transport) yet i.e. 2721941.

Check in DEV using 2721941 log- In which transport , note 2721941 is captured. Was that transport imported to QAS and PRD?

[former_member547765]

i never transport for that note to QAS or PRD,

i implement manually in DEV and QAS for all that note

Regards

[sumitjais]

Irfan,

You mean you don't have a transport that can be imported from DEV to QAS/PRD .

If so, you can manually download -upload the notes and implement. ( Go to SAP support --> Open the note in browser --> Click "download" a SAR file is downloaded; Go to SNOTE Tcode and upload sapnote --> Upload the SAR file)

[former_member547765]

Hi sumitjais

when i implement the snote 2869143 in QAS (not transported from DEV)

i have transport request in QAS which is contains snote 2721941:

Regards

[former_member547765]

here is the contains from TR above :

Regards

[sumitjais]

A transport from QAS cannot be imported to PRD . ( Reason -I have already explained earlier in this thread)

You have to

Either find out the transport for 2869143 in DEV and release it with target QAS. Import the same in QAS with overwrite option and then in PRD.

OR - Upload the notes in PRD and implement. ( this should be the only case when you are implementing in PRD).

First is preferred one , but you need to find out the transport.

[former_member547765]

Hi sumitjais

ok i found the TR from dev.

how about the manual activities from the snote, do i have to run it in PRD system?

Regards

[sumitjais]

No, your manual activities should also reach to PRD through Transport. ( Perhaps they will be in same transport- if not find that transport too)

[former_member547765]

Hi sumitjais

i try to transport using the above step....last time i was able to transport to QAS and the to PRD

this time i try again with another TR, but there is an error

i have released both TR in dev and QA

Regards

[sumitjais]

Hi Irfan,

All these issue are occurring because of incorrect capturing of objects in the transports. In this case, the objects getting transported have 'repair' flag so they are not allowing it to overwrite .

You must have to remove the repair flags (Ex - maybe R3TRFUGRSCWU is locked in some another transport- you may have to find and release that too.

Follow 1541124 - Importing of a Support Package or transporting a change request errors out: "object was re...

and fix all the issues you see for the objects in repair. Then import the transport again.

[former_member547765]

Hi sumitjais

i have success implement all the snote in PRD system

thank you for the help

Regards

[former_member644293]

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

Regards,

[former_member547765]

Hi,

thank you for the advice,

this is the first time i make transport

Regards

[former_member547765]

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 ?

[sumitjais]

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)