cancel
Showing results for 
Search instead for 
Did you mean: 

no matching PO in entry sheet- New user

coolio_7
Participant
0 Kudos

Gents,

our new business user using ML81N for the 1st time and getting below error. have you seen this before ? any advise what might me wrong ?

Accepted Solutions (0)

Answers (4)

Answers (4)

coolio_7
Participant
0 Kudos

We recently did SP03 system upgrade and that too care of this issue in our production system. This issue was isolated to 1 user for whom a new user profils was created. I'll close this discussion.

Thanks all for your prompt responses.

JL23
Active Contributor
0 Kudos

This means that your issue is solved, please close this discussion, and review your other countless open questions too. It is a rule (No. 😎 as you can read in 

If you don't know how a question is to be closed then see

JL23
Active Contributor
0 Kudos

A SAP error would be visible to any user, so you better check the authorization. This KBA explains which authorization objects are checked: 2217833 - Error SE559 in ML81N

coolio_7
Participant
0 Kudos

I have already reviewed the above note you mentioned.

This user has the same roles, accesses, defaults,,,,,,,,,,in test system and no issue in test/ QA system- It is only in Production system that we're seeing this weird error- Only this new user.

our security folks even removed roles and reinstated and it still don't work.....

Please advise.

JL23
Active Contributor
0 Kudos

Maybe there is a weird value in table ESDUS, compare the settings between production and quality system, between this user and another colleague of him.

William_Laverde
Product and Topic Expert
Product and Topic Expert
0 Kudos

HI Coolio,

Since this issue is only on your production system, you might have to debug the problem working backward. Please put a breakpoint at the error and execute. When you arrive at the breakpoint look at the code and see if any exits, bapi, bad, or non SAP code is called. That could be the problem since it does not happend with QA or Dev systems.

coolio_7
Participant
0 Kudos

I checked and ESDUS is the culprit. this user has action for 'ML81N' in test but missing in in PDF.

how can i get/ maintain the same action 'ML81N' in production (is it security thing or screen variant?) ?

JL23
Active Contributor
0 Kudos

no entry is usually not an issue, this is creating itself with a first successful execution.

I see here much to much discussion where people want the settings equal for everybody and then write programs to do so, which could have been then a source for the issue.

Take Williams advice and debug to see which values are being processed when it comes to the problem, an exit or BADI should actually bring the same results in QA and Prod except it is already worked on and not yet transported, but I think there is still a wrong value that causes this issue.

Have you already tried with a different PO, just to make sure it is not PO related?

Btw, there was a similar discussion where the user posted his solution last week

jagdeepsingh83
Active Contributor
0 Kudos

Have you checked the users have all roles that others user have in the same area ? when you get this error .. also ask user to share SU53 screen shot to rule out any authorizations errors

coolio_7
Participant
0 Kudos

yep. did that.

nothing comes up on su53 and security trace- This happens only in production system.

Former Member
0 Kudos

This error is due to program error and you need to update the correction as mentioned in below OSS Note...

2112582 - ML81N: Incorrect items in tree view & incorrect error message SE559

coolio_7
Participant
0 Kudos

this is isolated only to 1 newly joined user. Issue is that she is getting these weird line and not even taking it to correct screen.

i got her test profile and it works fine. i think this is something else ?

Former Member
0 Kudos

Are you sure cos in test it might be implemented.

coolio_7
Participant
0 Kudos

it is not implemented in my test system.

Former Member
0 Kudos

Ok then you need to take this to SAP asking if we implement this the error might go for other users.