cancel
Showing results for 
Search instead for 
Did you mean: 

Error whilst creating an entry sheet in the backend system

Former Member
0 Kudos

We've created a limit order with confirmation and we can successfully create the first confirmation without any problem.

When we try to enter a subsequent confirmation, we get the error "Error whilst creating an entry sheet in the backend system 5000000237 022 PU Ordered quantity exceeded by 1 AU : 1000".

Has anyone any ideas why this is happening?

Is it tolerances ? If so which keys should I maintain in both SRM and R/3.

Regards

Keith

Accepted Solutions (1)

Accepted Solutions (1)

yann_bouillut
Active Contributor
0 Kudos

Hi Keith,

This is a backend error due to the lack of the unlimited flaf on item level.

Please read OSS note 338032.

Kind regards,

Yann

Former Member
0 Kudos

Yann

How do I set this via SRM ?

Keith

yann_bouillut
Active Contributor
0 Kudos

Hi,

You can use bbp_doc_change badi to set the unlimited flag in the PO (BUS2201)

Kind regards,

Yann

Former Member
0 Kudos

Can this not be done any other way ?

Former Member
0 Kudos

I've checked the unlimited box when creating a limit order but this doesn't appear to make any difference.

yann_bouillut
Active Contributor
0 Kudos

Hi,

Did you check the backend PO as well ? ))

Kind regards,

Yann

Former Member
0 Kudos

I can't as we're using ECS...

yann_bouillut
Active Contributor
0 Kudos

Hi,

I mean in display mode : do you see the unlimited flag ?

Kind regards,

Yann

yann_bouillut
Active Contributor
0 Kudos

Also please check that the final entry flag is not set.

kind regards,

Yann

Former Member
0 Kudos

The unlimited flag can be set and can be seen.

It's the flag on the delivery tab in the backend PO that needs to be checked.

I'm getting one of our developers to implement the BADI as we speak.

Thanks for your help.

Keith

Former Member
0 Kudos

Hi

Check whether OSS notes 935538 has been implemented in R3 (or on R3 plug in SAPKIPZI5D). If yes, there is a corrective note 990264 to be implemented in SRM. We faced similar problems and these notes solved our problem.

Rgds

Reddy

Former Member
0 Kudos

Reddy

Thanks for your reply. Note 990264 did indeed provide the fix.

Keith

Answers (1)

Answers (1)

Former Member
0 Kudos

Added points