cancel
Showing results for 
Search instead for 
Did you mean: 

Work Order Long Text greyed out after EHP 7 upgrade

Former Member
0 Kudos

Hello,

Work order long text is locked after EHP upgrade, when i am creating an order from notification, Long text in WO is greyed out/ not editable, Interestingly when i am creating a work order from IW31, long text is available for edit. I tried some notes, but didnt had luck..Could any one please help me.Thanks

King

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

If you already implemented SAP note 2204730, you should below thing as well.

One important manual setting needs to be performed before testing: In the SU3 screen, under the tab parameters, please add the parameter ( EAM_ORDER_OCX_LTXT_1 ) with value ( X ) as shown below.

This setting is must / required for the note to work. you can ask security team to add for all user who access IW31 and IW32.

Thank you

Prashanth

Former Member
0 Kudos

Hello,

Did you check this below note and its referenced notes?

2174541 - Header Long Text Box is not Editable in IW32

Former Member
0 Kudos

Thanks Saurabh, we implemented notes 2176194 and 2204730, and that solved the problem.

jogeswararao_kavala
Active Contributor
0 Kudos

Hello,

Please see this discussion. Perhaps the solution is here.

Regards

KJogeswaraRao

Former Member
0 Kudos

Thanks Mr Kavala, I applied those notes, but didnt worked. I noticed one thing. when i am creating a notification which has very long description(say200 characters), from this notification if i am creating a work orders, the work order text is greyed out/ Not editable.

If i create a notification with short text(say 50 characters), from this notification if we create a work order, Long text is not greyed out/ its editable.

If notification text limit exceeds certain characters, Work orders are getting locked. i am not sure where we keep control for this.

Thanks

jogeswararao_kavala
Active Contributor
0 Kudos

There is no configuration control for Work Order longtext. It is one of the inconsistencies we face during upgrading as posted by several. Relevant notes also available to rectify the same. In case these are not helpful, then I feel you should raise a service message at OSS. Also. we have few members among ourselves who had a direct exposure to this situation. Let's expect their responses too to your issue.

Goodluck

KJogeswaraRao

Former Member
0 Kudos

Hey King, we are experiencing the same issue after applying update, did you raise a service message?  Would be interested to know what the outcome was.  Thank you.