Activation of Field name showing partially activated

[Former Member]

Dear All,

Activation of Field name showing partially activated.

please help me to activate fully field name -standard.

Regards

Sanjeet

[former_member191761]

Hi Sanjeet,

Can you please elaborate and provide screenshots.

Regards

Sri

[Former Member]

pls find the attached file.

[Former Member]

Hello Sanjeet Kumar,

As per my experiences,Most of time this kind of Partly active issues occurs once when u change the length of the standard domain.

Because this field may be exists in most SAP table suddenly if you change length of domain then this kind of issue will happen.

Better revert back the changes of the domain and activate it, it will work.

Don't ever try change the domains used in the standard table instead you can create Custom domain and add to the custom field as

ZAFNAM.

[Former Member]

Hi,

Exactly correct, i have changed the length, it was working fine but for test only, while i reverting back, its activating partially. Length changed from 12 to 40 char. now reverting back, kindly suggest me how to correct it.

[Former Member]

Hello Sanjeet,

Go to Utilities and Version Management and Retrieve the old version.

[raymond_giuseppi]

Could you display and analyze the activation log of the domain (SE11, Menu : Utilities, Activation Log) to find why the activation was not fully executed. (e.g. some database table with values too long requiring adjustement thru transaction SE14)

Regards,

Raymond

[Former Member]

Dear Madhu,

Please reply me in detail. not getting still.

[Former Member]

Dear Sanjeet,

Whether u have saved the changes in the Transport request then go to Utilies  and Version-> version Management,

it will take to this screen then retrieve to old version.

[Former Member]

Dear Madhu,

I did as you explain, and select the retrieved version then make tick mark,go back then click on activate icon, still not activated.

[Former Member]

Dear Sanjeet ,

Once you tick on old version and click on the retreive push button, then it will get similar kind of pop 

up message then overwrite it . then once save and activate.

[Former Member]

Hi,

You really need to explain your problem properly, rather than just making a vague statement and hoping someone can guess at your issue.

What have you changed/created?  What have you done?  What have you tried that hasn't worked? etc...

This isn't a forum for psychics I'm afraid.

Cheers,

G.

[raymond_giuseppi]

Lost your crystal ball ?

Regards,

Raymond

[former_member196601]

Hi Sanjeet,

Seems like you are editing a standard domain which is never advisable.

This domain could be used in many dependent tables and you will have to adjust data in all the dependent tables using Database utility and this can probably fix your issue but it is better revert this back to what it was and use a custom one if you require.

Thanks,

Naveen

[Former Member]

Dear All,

Thanks a lot, with the help of below thread, i have noted error table name in log and activate 1 by 1

through  transaction code SE14.

Regards

Sanjeet K

[Former Member]

I had done this same requirement in my previous company. Was able to activate also .

But as a consequence whole MM cycle resulted to DUMP

[Former Member]

Are you saying that by modifying a standard SAP domain, you broke the whole of your MM functionality?

(There could be a very valuable lesson for others here...)

Cheers,

G.

[Former Member]

Yeah ,

Coz if you change this field you can see that this is dependent with many structures in SAP MM cycle.

I did changes on Saturday and on Sunday when Material dispatch and Transfer is carried out in my earlier company MIGO transaction was giving dump.

At last SE14 was the saviour.

And everyone knows MIGO is the SOUL of SAP MM

I didn't see this thread at the right time else 10 points was for me for sure

[Former Member]

Thanks for the honest account of what happened.

Sadly, not enough people will read this thread and see you comments and will carry on, editing standard SAP objects without understanding what the consequences could be.

It still amazes me that more and more people new to the world of SAP and ABAP aren't being told about the risks of modifying standard objects, whether through changing data dictionary objects or by performing direct updates or similar.

It strikes me there is a problem with the current education/training approach.

[Former Member]

No Gareth I would like to highlight something on this note.

Am a developer , Though I haven't got any External Training on ABAP Coding Practices at that time , but I was somewhat aware of what are the Do's and Don'ts while playing with ABAP Objects and the whole Credit goes to SDN -> SCN ( am a member of SDN from the very beginning of my career ).

Now the main point , as am a Developer I can express my views only regarding a Development , it was my IT Head who told me to do this , though I repeatedly tried to make him and the MM Consultant aware of the consequences.

I had proposed a very safe alternative for the requirement , for which also I consulted SAP Gurus using SCN.

So in the nutshell , Experienced leads should also use their experience wisely and suggest the best alternative , as I have seen many Vague kind of Development requirement here in SCN

In the end they had to stick with F4 help which I had suggested at that time with my 2.5 years of exp with ABAP .

And I guess SAP also mentions this thing in its License agreement that no change to SAP Standard Objects should be made , if made you need to bear the consequences.

[Former Member]

Another great comment.

I've seen far too many ABAP developers being forced down a route that they know is wrong, simply because someone deemed "superior" to them has told them to do it.  So many posts here on SCN have a justification of "I have to do xyz because my team-lead says I should."

This approach does not always create a quality solution and if the person actually tasked with pushing the buttons doesn't want to push them in a certain way, the lead should listen.  I suspect a big problem is that juniors aren't allowed to speak up or aren't listened to if they do, as seniors just assume they know better.  (Sometimes they do, sometimes they don't!)

[former_member182421]

Sometimes they can't be considered seniors...

[roberto_vacca2]

Sometimes we want only just be payed for what we do.. We work to live, not the opposite.  Life must not be registered as a badge ..