Show TOC

Function documentationSuppressing Exceptions in SAP F&R

 

In SAP F&R, you can create rules and criteria to specify the system behavior regarding the suppression of an F&R exception object in certain situations. That is, if you find that too many exceptions are being created, or if the exceptions that are raised do not sufficiently consider the circumstances leading to their creation (meaning that they are not always relevant), you can define criteria and rules that suppress or control their use in certain situations.

Note Note

You can only use the suppression functionality if you have activated the business function SCM-FRE, Replenishment and Optimization in F&R (SCM_FRE_OPTIM).

End of the note.

Features

  • Criteria are used to link a database field (for example, the field Listingstatus of the location product) with a value via a relational operator. At runtime, during the creation of the F&R exception object, the system checks whether the value contained in the database field fits this value regarding the relational operator.

  • A rule is used to combine different criteria with a Boolean operator. Rules can be assigned to different F&R exception object types, and more than one rule can be attached to an exception object type. This is important since sometimes you may need to attach different suppression behaviors to an exception object type, depending on different situations in the database tables. Within a rule, you define the suppression behavior that should take place if the rule delivers a Boolean 'True'. The following suppression behaviors are available:

    • The extraction of this exception into SAP BW is suppressed.

    • The displaying of this exception in the F&R user interface is suppressed.

    • The relevance of this exception for use in the Replenishment Workbench for Stores is suppressed.

    • The system is prevented from writing any entries for this exception into the database.

    At runtime, during the creation of the F&R exception object, the system checks every assigned rule and executes the suppression behavior accordingly. If more than one rule is assigned to the F&R exception object type in question, the system combines the suppression behavior of the different rules. If one rule indicates that the exception should not be written into the database, the system ignores all other rules and does not write any entries for this exception into the database.

Example

For material planners, an exception stating that there is a zero stock of product XY in location YZ is not important in the following situations:

  • The product is an ultra-slow seller

  • The product is delisted and the ABC indicator has a particular value, for example, ‘C'

To control the use of this exception, material planners can define criteria which are then evaluated by the system during the creation of exceptions. These criteria could be the following, for example:

  • If a product is identified as an ultra-slow seller, then the exception 214 of message class /FRE/EMON shall not be relevant for display.

  • If a product is not listed and the ABC indicator has the value ‘C’, then no entries for the exception 205 of message class /FRE/EMON shall be written to the database.

More Information