MRP run in background - ONhold

[Former Member]

hi

Off late, the MRP background job scheduled weekly is taking a very long time. more than 4 hours and when i check the status in SM50, it shows the job shows status ON HOLD and reason as ARFC.

In SM66 , i can see the job is STOPPED.

But after a long interval it gets running and the job gets completed after several hours.

Can anyone please help me on this.

Thanks and Regards

Joe

[Private_Member_19084]

Hello joe,

we are facing exactly the same problem since a few days.

Do you remember the reason?

thx

[Former Member]

hello Christian,

what is the planning mode being used ?

If you have performance problems which cannot be corrected by other

measures (note: planning mode 3 is absolutely unnecessary, unreasonable and

can cause damage in productive operation), the above situation can be

avoided by a performance tuning modification.     

“ On-Hold – ARFC “.

That is due to Parallel processing  - one application server is waiting for the other server

Before planning of a new low-level code can be started in MRP, the previous  low-level code must have been planned completely.

Therefore, it may happen that only one server is working whereas the other

ones are waiting in order to then start planning of the next low-level

1. code.

The described behavior may be extreme if some few materials make up the

main load of the performance.

The situation becomes more probable if these materials succeed each other

in the planning file because they have very similar material numbers.

Example: 5 complex finished products whose material numbers are almost

identical make up 80% of the runtime of material requirements planning.

The performance statistics of the planning run shows that the tasks (or

application servers) were not utilized uniformly.

[alexander_teslyuk]

Hi Joe,

I believe you should have addressed this question to another forum as the current one is for ME application.

Regards,

Alex.