cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Planned order conversion issue

former_member691361
Participant
0 Likes
776

Hello,

While converting planned order to process order from APO by flagging conversion indicator, the planned order is getting stuck in ECC queue with following error

'Standard prod. production w/o batch mgmt reqmt poss. only in indiv. stock".

This is not happening for all orders but happening very frequently.

Could you please suggest the fix for the same.

Thanks,

Prash

Accepted Solutions (0)

Answers (4)

Answers (4)

former_member691361
Participant
0 Likes

Hello Brahmakar,

It is a configurable material and below is the error details.

"Standard prod. production w/o batch mgmt reqmt poss. only in indiv. stock"

Message no. MILL_CONF_IN_PROD010

Thanks,

Prasanth

rupesh_brahmankar
Active Contributor
0 Likes

Hello,

This could be due to configuration is inconsistent.

In that case SAP note 1638400 - Planned order conversion triggered from APO fails is useful, please read all Reason and Prerequisites from the note.

Best Regards,

R.Brahmankar

rupesh_brahmankar
Active Contributor
0 Likes

Hello,

What is error message number? Is it MILL_CONF_IN_PROD 010?

Is order for configurable material with variant configuration (VC)?

Please share product view //RRP3 screen shot

Best Regards,

R.Brahmankar

former_member691361
Participant
0 Likes

Hello Alan,

Earlier I checked that note, but not sure whether it relates to our issue.

As far as I understand from the note , the error occurs when we change the planned order in APO (mostly scheduling) and hence it is not in sync with ECC. So when we implement the BADI, it will ignore this discrepancy and go for conversion.(please correct me if I am wrong).

Also confused on point from note - After that converting of new created planned orders will be ignored in foregoing cases.

But in our case, when the issue order is either recreated or re-explode , still we will get the same error. And also the new order without any manual intervention is also getting the same error.

This is not happening for every orders, but it is happening frequently.

Thanks,

Prash

alan_heathcote
Explorer
0 Likes

Hi Prash, have you checked OSS?

note 1638400 might help