on 03-03-2010 10:16 PM
The transaction FSE2 must be released in the production environment. For now the same blocked and is presenting the following message Client 500 has status 'not modifiable'
Someone know how to tell the trandação be free in a production environment?
sorry for my English
Antonio Xavier
Edited by: axp333 on Mar 4, 2010 1:49 AM
Hi ,
Go to the transaction code SCC4 . you can change the production client from non modifiabe to modifiable.
You can change the customizing setting with out generating any request.
But IT IS VERY RISKY IN LIVE SYSTEM
with regards,
Sudipto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear.......,
If you modify FSV in PRD client & also if you want to assign new GL's in FSV ,you must go through mentioned procedure only.
OBA5.........APPLICATION AREA : FE
ENTER
GIVE MESSAGE NUMBER : 146
GIVE USER NAME
ONLINE : I
BATCH : I
STANDARD : E
Please check 398292 SAP Note ,if you are in R/3 4.6 Version
Rgds
ManiSuma
Hi,
First, you will need to open the client that your are working on via Transaction code SCC4. Select the option available from the tab Changes and Transports for Client Specific objects. Proposed to select :changes without automatic recording.
Once this is done, you may perform the changes in that client directly.
Please check whether you have the authorization to do so.
I hope the above information helps.
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Xavier,
in general Client 500 has status 'not modifiable' always in any company for the purpose of security.
Landscape of testing server and production servers will be different in general.
If this is going to be the case you need to make your changes in Development client, create a request and test the same in testing client (through t.code SCC1 without releasing the same - if Dev client and testing client are in the same land scape)
If you are satisfied then release the request and transport it to production with the help of your basis team.
Aravind Boddupalli
Hi
Please check the following link for making FSE2 a user transaction.
http://sapfin.blogspot.com/2009/08/information-convert-tcode-fse2.html
even after completing these settings, you may still get a msg that the transaction is not open for change.
still the changes will be made and saved
Regards
Sach!n
Hi Xavier,
Through FSE2 you can change the Financial Statement Version. At the first instance why you want to bring T.Code FSE2 to operate in production. If FSE2 is operated only by one person you can exercise control else if the same t.code authorisation is given to each and every body how you can exercise control over the structure of your financial statements?
Aravind Boddupalli
Hi Aravind
fse2 the transaction will be used only by a user in our company. but we are failing to release it into the production environment as the customer for this transaction is closed and we are failing to release the fse2 so you know how to free the production?
sorry for my English
Antonio Xavier
I am not clear about your query, do you want the FSV to be created and moved to the production client? Or you want a particular user to be assigned with the T.code-FSE2?
To move the FSV to production, you should create and save it in the transport request from the T.code-OB58. FSE2 is for changing the financial statement version after creation.
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.