How to automatically firm PRs during MRP run?

[fra88fgback]

Hi Folks,

I already checked several past questions. By the way, no one answered in a clear way.

I'd like to *create* firmed PRs within period time fence during MRP run.

KBA 2351191 seems to suggest to use MRP Type P1/2/3/4 and time fence. However, *NEW* PRs are always out of the time fence, hence *not* firmed.

This strategy firms only PRs already existing when setting time fence. I cannot say users to change time fance, run MRP, then change again time fance to firm PRs created by first MRP run.

I sure miss something. Is there any other way to firm PRs? Do I need any material master field to fulfill?

My material master contains:

MRP Type P1

Time fence: 190/200 days

Minimum lot size or rounding

Info record with delivery time

The MRP runs with:

Processing Key: NETCH

Create PRs: 1

SA Deliv. Sched. Lines: 3

Create MRP List :1

Planning mode: 3

Scheduling: 1

I saw also Jurgen answer but it didn't solved. The thing destroied me.

[Dominik_Tylczynski · Accepted solution]

Hello fra88fgback

I don't think what you are trying to achieve is doable with standard Firming Type SAP provides 4 firming types but none of them creates procurement proposals in the planning time fence and get them fixed. That is precisely the purpose of firming types to protect procurement plan within the planning time fence and make it more stable despite changing requirements. I think you are trying to misuse firming types.

You can use MD_PURREQ_CHANGE BAdI to implement a custom firming logic and update CH_EBAN-FIXKZ

Best regards

Dominik Tylczynski

[fra88fgback · Accepted solution]

Hello 3a9e4ce873a94034b33dc62b0ce600ee

Thanks for your reply!

As I imagined, but it is honestly not that clear in documentation.

Thanks for the BAdI, I'm gonna use it. I'll share my thoughts just if someone will need same implementation in future.

In order to implement my purpouse:

1) I will first check whether PRs are already firmed

2) I will check if the request date is less than time fence end date

3) I will check if rescheduling date is greater or equal to sy-datum and less than time fence end-date

4) I will set the fixed indicator CH_EBAN-FIXKZ (it helps me doing first control since MD04 firm PRs without set it within time fence),

request and delivery date equal to rescheduling date and changed indicator (in BAdI)

5) if check at 3) won't pass, I'll calculate delivery date with BAPI ADD_TIME_TO_DATE and DATE_CONVERT_TO_FACTORYDATE (in order to consider calendar day, but setting a delivery date not on Sunday or Saturday)

6) If new calculated delivery date does not respect check at 3) again I won't set changes, otherwise I will set same effect of point 4).

In this way I should achieve the goal.

We plan independent requiriments by MD61. MRP will create PRs with respect to them. Inside the Time fence we will have firmed PRs according to initial Year Budget/Forecast (MD61), if new requirements will arise late, MRP will create PRs out of the time fence. Within the time fence will be created new firmed PRs only if delivery date is less than time fence, but planned delivery time is more or less the planning time fance, hence it will be difficoult to happen.

Thanks again Dominik,

KR

Francesco

[Dominik_Tylczynski · Accepted solution]

Hi fra88fgback

The proposed BAdI logic seems fine. However please double check the business requirements. Planning time fence is meant to protect supply plans in the nearest future. That's why MRP doesn't create procurement proposals in the planning time fance if firming type is active. What you want to do is to create procurement proposals in the planning time fence and have them firmed so they are not changed anymore by subsequent MRP runs. That will not protect the supply plan in the planning time fence. Why don't you go with standard firming logic? If demand changes within planning time fence and MRP doesn't create relevant procurement proposal there, you will get a MRP exception so MRP controller can evaluate the situation and take a decision if the procurement can still be executed in the planning time fence.

[fra88fgback · Accepted solution]

Hi 3a9e4ce873a94034b33dc62b0ce600ee

First of all, thanks again for your feedback.

I'll give you some context to explain process reasons.

My customer is a very little non-productive branch. They buy and re-sell end product.

My interlocutor works for logistic and procurement.

Actually, they use excel to create year purchase forecast and then manually create PO proposal. Sales monthly updates forecast (VSF) and create real requirements (Sales orders). These requirements would affect monthly budget if MRP run creates automatically not firmed PRs.

Planning delivery time is quite long (at least four months).

Actually they do not use MRP functionality.

The idea is to lock at start PRs created by MRP run using VSF, convert PRs into POs.

Then, future requirements would be:

- Put as non-firmed PRs whether lead time is exceeded

- Put as new firmed PRs whether lead time is still profitable. In this case, new PRs would be taken into account for ne POs proposal

The goal is:

- to protect initial budget proposal from Sales not expected requirement fluctuations;

- to answer initial forecast shared requirements first;

- to start considering new requirements over the time fence;

- to reduce manual activity by users (considering they are few people);

I don't know if it is the best way, but it seems can help.

Francesco