How to Transport SPRO Setting Enable_Fixed_Cubename

[Former Member]

Dear Members,

I need to know transport sequence while transporting TR first time to QA in implementation project.

We have set the parameter Enable_Fixed_Cubename = 'X'. But system is not prompting for Transport request in BID(Development) in SPRO -> IMG ->Planning & Cons -> Config Parameter -> Set Model Level parameter. (Note 1689814)

Based on my understanding, This parameter needs to be transported first so that while transporting technical name of the cube doesn't get change followed by the request collected through RSA1 which has Environment and other stuff.

My questions are below.

1. How we can capture SPRO parameters in Transport Request

2. What should be the transport sequence after capturing the customizing TR. SPRO setting has the reference of Model name so Model needs to be      transported first. If we transport model and environment first then technical name of cube will get changed.

Regards,

Rahul Kumar

[former_member200327 · Accepted solution]

Hi Rahul,

Some SPRO settings can be transported and some not. FIXED CUBENAME can't be transported.

So, first time when you transport the Model name is not going to change - it changes only if you change something in the Model. Hence right after the transport you have to manually set this parameter.

Hope this helps,

Gersh

[Former Member · Accepted solution]

Thanks Gersh for your kind reply.

While going through OSS Note 1689814, It says setting has to be same in source and Target, Otherwise TR will give error. I belive,It means we have to transport this SPRO setting.

l Transport Model:

¡ For release 10:

When the parameter ENABLE_FIXED_CUBENAME has been switched off both on source

and target system, the behavior remains the same before applying the enhancement. When parameter

ENABLE_FIXED_CUBENAME has been switched on both on source and target system, and the model

structure has been changed during transport, the behavior for transport would be that:

- If the InfoCube technical names of the model are identical

1689814 - Stabilize InfoCube's technical name in the modeling process

Version 5 Validity: 26.09.2014 - active Language English

Released On 26.09.2014 14:45:06

Release Status Released for Customer

Component EPM-BPC-NW-ADM Admin

EPM-BPC-NW NetWeaver Version

Priority Correction with medium priority

Category Program error

Other Components

between source and target system, and if there's no transaction data maintained in the model on

target system, the technical name of the InfoCube would keep unchanged after transport. If

there's transaction data maintained in the model on target system, an error message would be

displayed in the transport log and import of the model would be canceled.

- If the InfoCube technical names of the model are different

between source and target system, the technical name of the InfoCube on target system would be

changed to the same as the technical name of the InfoCube on source system.

If the parameter ENABLE_FIXED_CUBENAME has different value between source and

target system, the model import would not be performed and an error message would be raised in

the transport log.

[former_member200327 · Accepted solution]

This Note was written a long time back when most of the users already had Models transported and wanted to keep same Tech name. If you put that setting right after first Model transport it will work fine.

[Former Member · Accepted solution]

Thanks a lot Gersh for your help.

I have additional query here - How we will do setting in QA and PRD? we need to transport it. We are not able to capture this setting in Transport request in SPRO. 

[former_member200327 · Accepted solution]

This is not an additional query, this is same query. And the answer is same - don't transport that setting, enter it directly in QA  and PRD.

[Former Member]

Thanks Gersh,

Transport went successful.

Thanks a lot.

[rbalaji_it]

Please advise of how did you transport it