Show TOC

Object documentationF&R Exception

 

Exception in SAP Forecasting and Replenishment (SAP F&R) that the system triggers based on exceptional business situations in the logistics chain or exceptional technical situations.

 

The system uses F&R exceptions to display exceptional situations in different business areas and to inform users about both business and technical causes and consequences in the program flow.

Based on this information, you can analyze the exceptional situations and eliminate errors. You can decide that an error is negligible enough for you to set the status to Processed. You can also use criteria and rules to control the number of exceptions that are created in certain situations. For more information, see Suppressing Exceptions in SAP F&R.

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.

Structure

In SAP F&R, exceptions are divided into the following three categories:

  • Exception with business cause

    This category of exception is caused by an exceptional situation in the logistics chain and not by a program error. Business causes for this exception category can differ depending on the business area. There are also business causes for exceptions that can occur in several business areas.

    Example Example

    Excessively high level of stock based on the proposed order quantity

    If very high order quantities far exceed the usual stock of a product, the system automatically issues a warning. A combination of the following can lead to an excessively high order quantity:

    • Positive trend

    • Sales promotions

    • Price markdowns

    • Special events in the yearly calendar

    • Optimization over a large number of demand periods

    • High minimum stock level

    End of the example.

  • Business exception with technical cause

    In this exception category, a technical reason creates a business problem, causing the system to trigger a business exception.

    Example Example

    Incorrect referencing of a logistical unit when optimizing the order quantity on the basis of a vendor's discount scales.

    End of the example.

  • Technical exception

    Example Example

    Inconsistency error message

    If you set parameter X globally in the parameter specification, in other words for all products in the product master, and in the configuration file you only assign the parameter to those products with entry 005 in field Y, the system contravenes the default defined in the parameter specification. The import module therefore terminates the program and creates an exception.

    End of the example.

You must differentiate F&R exceptions further, according to the process level:

  • Low-level exceptions

    In the Exception Workbench, low-level exceptions describe the reason for a problem. The consequences of the problem are unknown at this level and can only be described by a linked high-level exception.

    Low-level exceptions must always be connected to high-level exceptions so that the system leaves the low-level exceptions in the exception memory. If a low-level exception is not linked to an exception on a higher level, the higher-level process that is currently running discards the low-level exception.

    Low-level exceptions can, for example, be created by a function module following failed access to a database. This function module writes the low-level exceptions to an exception memory.

  • High-level exceptions

    High-level exceptions primarily describe the consequences of an exceptional situation rather than the reason for the problem. High-level exceptions can be linked with low-level exceptions:

    • With one low-level exception

    • With several low-level exceptions

    • With no low-level exceptions

    High-level exceptions form the end of the exception chain. If low-level exceptions are not assigned to a high-level exception, the system automatically deletes these low-level exceptions.

Example

In the Exception Workbench, the system displays the following high-level exception that is linked to three low-level exceptions:

High-level exception: Problems occurred during supply source determination for product FRE_PROD_ZZZ in location XXX.

If you select the icon for the exception in the VA column in the Exception Workbench, the system displays the connected low-level exceptions:

  • Several transportation lanes with same priority and procurement type found

    (Long text: several transportation lanes found with the same priority and procurement type for location XX1, target location YY1, and product ZZ1 for date 9999 99 99.)

  • Several transportation lanes with same priority and procurement type found

    (Long text: several transportation lanes found with the same priority and procurement type for location XX2, target location YY2, and product ZZ2 for date 9999 99 99.)

  • Several transportation lanes with same priority and procurement type found

    (Long text: several transportation lanes found with the same priority and procurement type for location XX3, target location YY3, and product ZZ3 for date 9999 99 99.)

More Information

Alert Monitor