IDOC HRMD_A Client Has Status 'Not Modifiable'

Hi all,
I'm working with the HRMD_A07 Idoc.
The status is green, but the data are not loaded in the system.
It is possible that this situation is related to the status of the system that is 'Not Modifiable' ?
If I create a record in the PA30 I'm getting an error message about the status 'Not Modifiable' of the system, but at the end I manage to save the data.
thx

Hi Gabriel
For this u have 2 solution
1. Temporary
Every time you need to open client using SCC4 & SE06. After that u have to close the client.
2. Permanent
You have to talk to your ABAPer to have a customized Tcode for the REAJINDX.
Regards
Abhishek Tiwari

Similar Messages

Tables can be maintained even though Client has status 'not modifiable" ?

I am looking, list of tables which i can maintain directly even though "Client has status 'not modifiable'" status
example : T000
Rgds

No ..No...Siddesh,
You are understanding my requirement in reverse.
We are now not in execution of giving the access.
i regret, if i am failing to explain my requirement
A Auditor wants
a). He wanted to know the users having S_TABU_DIS auth object with 02 value and assigned authroization groups.
b). He wanted list of tables including Z tables that can be maintained directly thru maintenance view
Auditor will do some excerse Directly Maintained Tables (vs) Authroized users
He will come back with a list of tables for which we have to give the logs.
I tried my best to explain my requirement.
To summarise - I repeat i am looking "List of Tables that can be maintained directly - When Client has status 'not modifiable" ?
Thanks in advance for your time for this query.
Rgds

Client 000 has status not modifiable

Dear all,
after installing ABAP and JAVA stacks I can normally
work in both system (NSP, J2E). I created a RFC function module via se37 to use it as a basis for a web service.
But when I try to release my web service for SOAP runtime using TA WSCONFIG I always get an error message: <b>Client 000 has status not modifiable</b>...
Are there any restrictions or did I make a mistake?
Thank you

hi Harald,
Did you make a client copy after your ABAP installation? SAP doesn't allow you to work on 000 client. so you need to make a copy of 000 (say 111 or any other number)and continue to install your JAVA Stack on this CLIENT. i guess you had put your JAVA stack on 000 itself. that's the problem.
Just make a new client or "Client Copy". and Put a java stack on that client. Remove the old java stack. This should solve your problem.
Regards
Arun

CLIENT 600 HAS STATUS NOT MODIFIABLE

Hi SDN,
I gotone problem related to SM30.While user trying to upload the table he will get the message like <b>CLIENT 600 HAS STATUS NOT MODIFIABLE</b>. Could you please provide me the solution and reason for this message? I will be very great ful and thank ful for the answers..
Appreciation for the answers..
Regards,
Kumar

Hi,
This thread has answer to your question...check it out...
How do SM30 Update when client is "not modifiable" ?
assign points if helpful...

OBB8 - Client clientnum has status "not midifiable".

Dear All,
I have given atuhorization of OBB8. But when user try to run OBB8, it gives Client <clientnum> has status "not midifiable".
Our requirement is to Maintain Terms of Payment directly into production.
Please advice below steps will work and is it advisable or not ?
1. In SPRO -> Financial Accounting->Accounts Receivable and Accounts Payables-
->Business Transactions->Incomming Invoices/Credit Memo -> Maintain Terms of Payment.
In Mainain Object if I check the "Current Setting" - will it work.
If try to check the "Current Setting" it will ask for Access key as object is going to modified ?
Whether this object "V_T052" is advisable to modify ?
Thanks in advance
Nirav
Thanks in advance
Nirav

Vinaya Reddy wrote:Hi
>
> Yes i agree....to maintain SAP standard tables, you need to ask the basis guys to open the client and then modify the table.
Yes this will do the trick to, but I would advise against it.
Customizing tables should always be maintained in your development system an transported to production, don't open production for customizing, if you do so you can't ensure that the OBB8 table is the only customizing table that's changed in production - and overtime you will probably find your self in a situation where you have forgotten to close the productive client again, and that other types of customizing has been changed directly in you productive system as well. This can potentially endanger the stability and security of your system landscape.
If you want to maintain it directly in production - change the recording routine on this table only in SE54. It's a change to SAP Standard, (and of course you should avoid changing the standard if it is practically possible) but you will keep the control of your landscape.
And in my book it a bigger Sin to open your productive system for customizing, than it is to change this kind of SAP Standard settings - but that's just my opinion.
Regards
Morten Nielsen

OB58-Client clientnum has status "not midifiable"

Dear All,
I have given atuhorization of OB58. But when user try to run OB58, it gives Client <clientnum> has status "not midifiable".
Is there any possibility without changing cleint status to run this T-Code?
Thanks in advance
Nirav

Hi Nirav ,
OB58 transaction code provides user authorization to maintain T011 and T011T tables which are cross client tables. Except in development system changes to cross - client tables and repository objects is not allowed in QA and Production clients. Production client will be always in not modifiable and no transports allowed and ecatt not allowed state and for security measures.All such changes needs to be done in dev needs to go to QA and production through proper transport.
If the business recommeds to make any such changes directly in production system based on the criticallity client needs to opened using SCC4 transaction code with prior business approvals as recommended and and needs to set back to previous state again once chnages are done.
Note : You should be very carefull when you open and close the production system as it will effect the system security and as a result which effects the business data.
Regards
Kanti

FSE2-client status is not modifiable

Hi Experts,
Everytime i run t-code FSE2(Change Financial Statement version, this message always appeared..
" ClIent ... has status "not modifiable""
Is there any t-code to make this modifiable?
Please advise...
Thanks
rey

Hi Rey,
In which client are you trying to do this change?
Normally this change needs to be done in the development client & transported to production client.
That is why this error appears.
If you want to change this setting, contact you BASIS consultant.
Regards,
Inoka

T.code FBZG: editing of failed payment trans .. Client 400 has state not ..

Hi All,
launching t.code FBZG, and filling in, then, the company code,
I choose the option "enter data and maintain copied data" and select the button "maintain data"
SAP gives the the pop-up with the message:
" Client 400 has status 'not modifiable "
What could it depen on?
Thanks a lot for Your advices.
Gandalf

Hello,
You have two alternatives:
1. Recommended
Call up transaction SOBJ. Click the "Maintain" button
Postion the cursor on the V_TINSO entry.
Select the field "Current Settings" (V_OBJ_H-CURSETTINGS).
Save the Entry.
If the object category of the view in your system is "APPL" change it to "CUST", before you select the "Current Settings" flag.
Please refer SAP Note No.387533.
2. Not recommended.
You can change the Client Role in Test System to "Production", it would then allow you to enter the data. Before that please consult your Basis Administrator.
Hope this will help you.
Regards,
Ravi

When launching a transaction, I am getting error that client XYZ has status

I am in SAP APO , when I try to launch the transaction /SAPAPO/48000009
SAP Menu -> SCM Basis -> Planning Service Manager -> Current Setting -> Define Planning Profile. I get a error saying Client XYZ has status 'not modifiable'.
What setting could be missing?
Please help with your inputs.
Harsha Gatt

You are on the wrong forum. This forum is about SAP Business One SDK.

Maintain the values - Client 'Not Modifiable'

Hi,
I have created a table Y1260. It has three fields namely MANDT, WERKS and FLAG.
I have given Delivery Class = 'C' and Maintainance allowed.
Under technical settings, Data Class = 'APPL2' and Size category as 0.
Buffering is set 'OFF'.
Under Table Maint., Authorization Group is &NC&.
When I go to SM30 for maintaining the values, it is not allowing me stating that .. Client 010 has status 'not modifiable'.
Please help me to solve this issue.
Thanks in advance.

Hi,
You have given deleivery class 'C' which means customizing table, maintenance only by cust., not SAP import..
Try to change it to 'A'.
Regards.
Mudit

RE: Client Not Modifiable for Z Tables

Hi all,
One of our developer created 3 custom Ztables, when he is testing in testing environment, he is able to modify 2 of them using SM30, but for one table it says "Client status not modifiable". i checked his profile and he got access to SM30 and also to S_TABU_CLI--> Allowed (X).
I dont know why it is not allowing this table to change and allows other tables to change ( I dont think this is any thing wrong with his authorization)
I also checked in SE11 and his delivery class is type "A" like the other 2 tables.
what else i need to check?
thanks,
Sun
Edited by: sun on Nov 19, 2008 3:53 PM

There was a little bug in SOBJ a while ago which let you change the owner of the object in a development system without transporting. But that should be fixed - as it is simply not an option anymore, also in a production system.
The better (more transparent) option in my opinion is to use the current settings flag if these tables are going to serve a "customizing" type function of the application and you want the flexibility to change them system specifically within your landscape without having to transport it and not wanting to open the (productive or test) client just to make a change of something non-critical for the application.
But you need to pick and choose them carefully. There are also some other settings which you might want to tighten the control on - for example very application sensitive master data.
Now I don't know what these tables are used for, but you did mention S_TABU_CLI being required so they are even client independent (most likely)... at least as far as their maintenance is to be concerned.
As you are asking this in the security forum (and not the ABAP or Data Dictionary forums), you might want to review the technical design of this solution...
It is not unknown that the developer and customizing roles find their way to production and used there with reliance on the SCC4 client settings either, and as these are client dependent... what are the settings of the other clients and the authority of the users in them?
But that is up to you. Certainly training and experience helps as well (which includes learning the hard way
I prefer the current settings to the client settings where the "use case" is justified.
Cheers,
Julius
ps: The one table which could not be changed, was it being changed from a different client than the other two?

Client not modifiable

Hello,
When i am executing the transaction code OAAQ in production server it is working fine but when i am trying in quality server it says client 100 is not modiable where as both client settings are same in QA and PROD in SCC4.
When i made QA as modiable manual and then it is working fine...
I would like to know is there any config setting becase of that it is not working or is there any problem Basis side
Thanks in advance.
Regards,
Krushna biswal

Hello,
I have found the solution for it.
If the client role is "PRODUCTION" in SCC4 then it work fine, if it is other than "PRODUCTIOn" role then we need to change to modifiable client then only it will work, otherise, "Client XXX is not modifiable" messge will occured.
Regards,
Krushna Biswal

OVR1 and SR10 not modifiable in production system.

Hi all,
We would like tcode OVR1 and SR10 to be executable in our production system.
We want to skip the change request needed to push the new entries from our development all the way to our production system. I want only to activated the possibility to create the OVR1, SR10, SR11 and SR12.
Here is the message we get when we try to create in our production system
Message no. TK430
Diagnosis
The system administrator has set your logon client to the 'not modifiable' status.
Client-specific objects can not be changed in this client.
System Response
The function terminates.
Procedure
Contact the system administrator.
For more information, see the SAP Library under Change and Transport System.
Regards!
Curtis

To All,
The OSS Note 812002 will deactivate the transport requirement.
There's a config in Solution Manager that must be set also.
When I get the full Solution I will post it here.
Regards!
Curtis

BP Status 'Not Released'

Hi,
when creating a business partner, there is a check box 'not released' in Status tab in sap gui. If I check the check box and save without error, will this BP be replicated to ECC?
As I have a business scenario that BP will be created in CRM and replicated to ECC. But it cannot be used for any business transaction until the BP is approved.
Therefore, I need to know if BP flagged with that status, will it be replicated to ECC?
secondly, in ECC, how do i uncheck the check box if the BP is approved and ready to be used. (Once it is uncheck from Not Release, this should replicate to CRM and update the status, so that all business transaction are ready to be used with this BP).
Is this workable?
cheers,
ginnie

Hi Ginnie ,
To answer your First Question ,
Yes, Eventhough you set the Not Released under status tab of general data, Still that BP will flow to ECC. It will give you a popup saying *Business partner has status "Not Released" * and a Yellow Exclamation mark will come next to BP number and it will flow to ECC.
At ECC side , you can use this in transactions too .
Instead of this, I will suggest you to use Central Lock which is just above the Not released check box, to achieve your functionality. If you use this, BP will be transfered to ECC but system will not allow you to use it in any transaction.
So you can achieve your functionality as follows :
1. Create a BP in CRM with Central Lock Tick on.
2. BP will flow to ECC with this tick on.(As a result Central lock, No transactions are allowed for this BP)
3. Once BP is been approved by an approver in CRM, Reset this tick in CRM , which automatically will flow in ECC
4 And now you are able to use this BP in transactions at ECC side
Hope I am able to clear all your doubts. Please revert to me if you need more help in this.
Regards,
Nikhil

HRMD_A Idocs sent to XI has status 39

Hi,
Our HRMD_A idocs used to have status 03, but after we started using XI , most of them have status 39 and they are being processed correctly. But some other programs are checking for status 03.
How does this Idoc status gets changed or effected after using XI?
Any ideas on that?
Thanks in advance.

Hi Anjana
We are trying to integrate HR master data with a legacy system and we are using chnage pointers for that. Did your scenario use change pointers to trigger HRMD Idocs ? if so I would appriciate ur help. I did all steps for setting up change pointers , but can't get the change points trigered when some thing is changed.

IDOC HRMD_A Client Has Status 'Not Modifiable'

Similar Messages

Maybe you are looking for