new PR not created with backgroup MRP process

[former_member199650]

Hi,

Please guide me for the following query:

We have scheduled the MRP process in the background through transaction

code MDBT.

The parameters which were passed during the scheduling are as follows:

Plant 0002

Processing key NETCH

Create purchase req. 1

Schedule lines 3

Create MRP list 1

Planning mode 1

Scheduling 1

Planning date 05.12.2013.

Variant name:ZMRP_NEW.

For Material Code P1S002, the reorder point was set as 200 and the

Maximum Stock level was set as 500.

The Lot size is set as 'HB'.

MRP Controller is set as '001'.

MRP Type is set as 'VB'.

The stock level was '0' at the time of execution of MRP Process and two

Purchase Requisition were already created with quantity 195 but still

new Purchase Requisition was not created by the backgroup MRP process.

And the same is got created when the MRP process was run as dialog

process. Please guide me about this problem.

Thanks and Best Regards

Subject was edited by: Jürgen L

[RobynCouch]

Hi Mahavir

You mention two existing requisitions.  Were those requisitions created manually or do they have the fixed flag set?  You would see a * next to the requisition number in MD04 if that is the case.

If so MRP cannot modify these documents and the result you described is correct.

Regards

Robyn

[former_member199650]

Hi,

Thanks for your reply please.

But the total quantity of the existing PRs were less than the reorder point in that case system should create new PR based on the MRP execution, but system did not do it.

Please help me in knowing why system is not creating PRs when executing the MRP run in the background (MDBT) whereas when i ran it as a dialog process through transaction code MD03 it created correctly the required Purchase Requisition.

Please guide

Thanks and Regards

[RobynCouch]

Sorry I assumed it was 2 requisitions for 195 each.  People have described the likely problem above.

When you are running MRP you choose a procesing key:

NETCH - Net change for total horizon

NETPL - Net change for planning horizon

NEUPL - Regenerative planning

The NETCH and NETPL options correspond to flags on the planning file.  These flags are set automatically when relevant things are changed in the system and cleared when MRP has been executed.  This means that with these processing modes MRP only runs when something has changed which it needs to consider.  For NEUPL MRP runs for every material which has a planning file entry.

None of this works is the planning file entry doesn't exist which happens sometimes when the materials is created by external programs or LSMW.  Check MD21 to see the planning file entry for that material and MDAB to generate any missing planning file entries.

[Caetano]

Hello

Generally, when a material is planned by the dialog transactions but it is not planned by the background job, it meas that the planning file is missing or it is not checked.

Do you have a planning file created for this material? You can check that on transaction MD21.

MDBT selects the materials to be planned based on the planning file, therefore, you must have an entry on MD21 and the flag "net change" must be checked.

If the planning file entry was not created, you should run MDAB, in order to create it.

If the planning file was created but the flag "net change" was not checked, you can use MD20 to check it.

Check the following note for more details:

205681  - MRP: Planning file entry for material requirements planning

553746 - FAQ: Planning file entries in material requirements planning

BR

Caetano

[former_member199650]

Hi,

But i am using MRP Type as 'VB'.

Please guide me.

Thanks and Regards

[JL23]

Have you checked whether you have an entry in the planning file?