Skip to Content
0

MD01N transaction fails with error message "Product XXXXXX in location XXXX cannot be planned"

Jun 25, 2017 at 05:43 PM

87

avatar image

Hi Gurus,

I have been trying to develop some scenarios using MRP live. While doing so I faced an issue of failed MRP live run. With lot sizing procedure WB- Weekly lot size, when MRP live executed whether single level/ multilevel, it fails with the error message "Product XXXXXX in location XXXX cannot be planned". On further investigating, I found that the MRP live run goes through successfully, when the lot sizing procedure is EX - Lot-for-lot size. I am not sure why the inconsistency with the dynamic lot sizing procedure while with static lot sizing procedure it's fine. Please help.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Pradeep Santara Jul 05, 2017 at 07:07 AM
0

Hi Jocelyn,

Thanks for your response.

I am working in 1610 on-premise edition and yes I have checked the Simplification list SIMPL_OP1610_FPS02 thoroughly, don't think have missed anything in this context.

I am not sure if it is a configuration issue, however further deep diving I could pin point this issue related to lot sizing procedure.

Later, I observed that in the Product Master in /SAPAPO/MAT1 , the lot sizing radio button is not getting set in case of periodic lot sizing procedures, while the same is getting selected correctly for lot-for-lot & Fixed lot Size procedures.

In order to resolve this, we applied the SAP Note 2459403 - Field 'Period Lot Size' and 'Reorder Point Method'
gives incorrect value but unfortunately it did not help.

Product master screen shot attached herewith.

Please let me know in case I'm missing out somewhere.

product-master.png

Regards,

Pradeep


product-master.png (32.0 kB)
Share
10 |10000 characters needed characters left characters exceeded
Jocelyn Dart
Jul 04, 2017 at 08:33 AM
0

Hi Pradeep,

Firstly please confirm if you have checked the Simplification List for your S/4HANA release to check if there any changes in this area or particular configuration that may be the cause of your problem.

Secondly please provide some more details - at the very least your S/4HANA version and feature pack level

Rgds,

Jocelyn

Share
10 |10000 characters needed characters left characters exceeded