SAP Note 27876 - Planning time fence (man.firming/display/segments)

Symptom:

a) Materials planning for a material with planning time fence and fixing type category '3' or '4' (manual fixing type):

The end of the planning time fence does not only refer to the value defined in the material master. For existing predefined inputs whose date is after the end of the planning time fence, the planning time fence is set to the most distant date of input.
This is not described in the documentation for Release 2.2.

b) The following error occurred up to and including Release 2.2G or 3.0A:

In the MRP list (MD05), with firming type '3' or '4', the end of the planning time fence is always set to the date of the last firmed receipt. This is then incorrect if the last firmed receipt lies before the end of the PTF from the material master record. If no firmed receipt is available, the end of the PTF was not displayed at all.

c) The planning time fence always refers to the net or gross segment. Nevertheless, up until, and including Release 2.2G, the end of the planning time fence was often displayed in another segment.

d) The planning time fence always refers to the net or the gross segment. Therefore, when reading the MRP elements, the system ignores the planning time fence in all other segments of the MRP list irrespective of the MRP procedure.
However, when creating new order proposals, the firming logic was used incorrectly in all segments.

Other terms

MD01, MD02, MD03, MD04, MD05, MD43, Planning time fence, Firming type

Reason and Prerequisites

a) This is intentional.

This allows the MRP controller, who dispatches the inputs during this process (manual planning), to protect planning as well outside of the planning time fence from the material master against automatic changes.
If, for example, a production order is dispatched outside of the planning time fence or firms planned orders, the automatic materials planning should 'accept' his planning up to this date.

b) This is caused by a program error.

c) This is caused by a program error.

d) This is caused by a program error.

Solution

a) The documentation is completed for Releases 2.2G and 3.0.

If you do not want this function behaviour, you can switch it off using a modification (test and maintenance by customer). A modification proposal for Releases 3.0A - 3.0I is contained in the attachment.

b) Correction.

c) Correction.

d) Correction. This is implemented in the standard system as of Releases 2.2J and 3.0F.