Ansicht
Dokumentation

/FRE/FRP_BADI_003 - BAdI: Creation of F&R Exceptions

/FRE/FRP_BADI_003 - BAdI: Creation of F&R Exceptions

CL_GUI_FRONTEND_SERVICES - Frontend Services   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

You use this BAdI to create user-specific exceptions in FRP outbound. The data made available in the methods cannot be changed. F&R exceptions can be created during the implementation of the BAdIs, but the exceptions have to be defined and configured appropriately.

Because the FRP outbound only processes data that is required for automatic replenishment, only this data is available on the planning date. Which data is processed in the FRP outbound for a location depends on whether or not the forecast and/or requirements calculation for that location is to take place on the relevant planning date (see description of the methods).

The data made available does not always correspond to the master data that has been maintained, but is adapted to the requirements for FRP. For example, if a rounding profile is maintained for a lane but the rounding has been turned off for the entire location, no rounding profile will be assigned to the lane imported to the BAdI.

If the master data is time-dependent, the valid value for the current planning date will be provided. For location product master data, all time-dependent values are provided as well. A table with non-listing periods for a location product is also provided.

The following methods are provided by the BAdI:

  • Transfer of master data and open receipts and issues (MD_AND_OOP_DATA)
This method is called in the package processing step for determining the master data and open order proposals in the FRP outbound (non-critical time frame). If the open order proposals are processed in a separate process step, the method is called twice in the package processing: in the first step without the open goods receipts or open issues, and second step with both the open goods receipts and open issues.
The following information is made available:
  • IS_LOC
    Location number, GUID, type, time zone data is always available

  • I_PLANTP
    Planning time stamp data is always available

  • IS_LOC_MD
    Location master data is always available in the first step, not available in the second step

  • IT_FRP_TEMP_MATKEY
    For FRP run adapted product master data, data is always available in the first step, not available in the second step

  • IT_FRP_TEMP_MATLOC
    For FRP run adapted location product master data (with time-dependent data), data is always available in the first step, not available in the second step

  • IT_FRP_TEMP_SCHEDULE
    For FRP run adapted source of supply and scheduling data, that includes a grouping key with which the order proposals are grouped, data is available in the first step only if the requirements calculation is done, it is not available in the second step

  • IT_FRP_HORIZONS
    For data involving location products that fall within the determined start of the consumption horizon and the end of the forecast horizon, data is always available in the first step, not available in the second step

  • IT_LOCPROD_FC
    For the list of location products to be forecasted on the relevant planning day, data is always available in the first step, not available in the second step

  • IT_LOCPROD_RP
    For the list of location products with requirements calculation on the relevant planning day, data is always available in the first step, not available in the second step

  • IT_ITEMDEACT
    For the list of non listing information, data is always available in the first step, not available in the second step

  • IT_OPENGR
    For open goods receipts for location products, data is always available in the second step only if requirements calculation is done, not available in the first step

  • IT_OPENGI
    For open goods issues for location products, data is always available in the second step only if requirements calculation is done, not available in the first step

  • Transfer of DIF occurrences
This method is called in the package processing step for determining DIF data in the FRP outbound (non-critical time frame). If the open order proposals are processed in a separate process step, the method is called in the package processing only in the first step, not in the second step in which only the open issues and receipts are determined.
The following information is made available:
  • IS_LOC
    Location number, GUID, type, time zone

  • I_PLANTP
    Planning time stamp

  • IS_LOC_MD
    Location master data

  • IT_FRP_HORIZONS
    Data for location products that fall within the determined start of the consumption horizon and the end of the forecast horizon

  • IT_LOCPROD_FC
    For the list of location products to be forecasted on the relevant planning day, data is always available in the first step, not available in the second step

  • IT_CALEVENT
    Calendar events for the location

  • IT_PREDICTORS
    Predictors for the location products (depending on delta handling or initialization, not all predictors are provided; depending on the start of a week, only the predictors for the location products to be forecasted are provided)

  • IT_CORFACTOR
    Correction factors for the location products

  • IT_WP_DEF
    Weighting profile definitions

  • IT_WP_ASSIGN
    Weighting profile assignments for the location products

  • Transfer of the consumption and current stocks
This method is called in the package processing step for the determination of the consumption and the stock data in the FRP outbound (critical time frame).
The following information is made available:
  • IS_LOC
    Location number, GUID, type, time zone data is always available

  • I_PLANTP
    Planning time stamp data is always available

  • IT_CONSUMPTION
    Consumption data for the location products is always available

  • IT_STOCK
    Stock data for the location products is available if the requirements calculation is done






PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 8238 Date: 20240329 Time: 110752     sap01-206 ( 79 ms )