SAP ABAP IMG Activity REFX_RECA_RESUBM (Implement Enhancements (BAdI))
Hierarchy
☛ EA-FIN (Software Component) EA-FIN
   ⤷ RE-FX (Application Component) Flexible Real Estate Management
     ⤷ RE_CA_CU (Package) RE: Customizing (IMG) and Area Menu
IMG Activity
ID REFX_RECA_RESUBM Implement Enhancements (BAdI)  
Transaction Code S_PLN_06000054   (empty) 
Created on 20030505    
Customizing Attributes REFX_RECA_RESUBM   Implement Enhancements (BAdI) 
Customizing Activity REFX_RECA_RESUBM   Implement Enhancements (BAdI) 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name RECA_RESUBMISSION    

Use

The primary task of this Business Add-In (BAdI) is to determine the list of dates for user-specific reminder rules. Implementing this Business Add-In is mandatory for every reminder rule specified in the Customizing activity Define Reminder Rules. You can process all required user-specific rules within the same Business Add-In implementation. That means that it is not necessary to create a separate implementation of RECA_RESUBMISSION for each reminder rule.

The BAdI method CHANGE_ATTR_OBJ_DATE makes it possible to influence the determination of the person responsible for a reminder date. In the standard system, the system enters the person responsible for the assigned object as the person responsible for the reminder date. The following parameters are available as IMPORTING parameters: IO_PARENT (object with reminder), IS_RULE (reminder rule for object) and IS_RS_OBJ_DATE (reminder date for object). You can influence the person responsible using the CHANGING parameter CD_RESPONSIBLE (person responsible).

The BAdI method CHANGE_OUTPUT_DATA_OBJ_DATE makes it possible to change the output attributes of a reminder date. The following parameters are available as IMPORTING parameters: IO_OBJECT (object with reminder) and IS_OBJ_DATE_X (reminder date and additional fields). You can use the CHANGING parameter CD_RSICONSTATUS to change the icon for the processing status.

The BAdI method GET_BEHAVIOR_CONTEXT makes it possible to allow changing the person responsible using the function key 'Change Further Attributes'. It also allows you to control whether the reminder category should be changed for completed or fixed dates, if the assigned reminder rule was changed.
The following parameters are available as IMPORTING parameters: IO_PARENT (object with reminder), IT_OBJ_DATE_X (reminder dates for object and additional fields), IS_RULE (reminder rule for object) and IS_RS_OBJ_DATE (reminder date for object). You can allow changing the person responsible using the CHANGING parameter CF_CHANGE_RESPONSIBLE. You can control the adjustment of the reminder category using the CHANGING parameter CF_UPDATE_REASON_AT_FIXED_DONE. Note that the IMPORTING parameter IO_PARENT only contains a valid reference during processing of a single object.

You can also define additional fields for overviews of the reminder dates. You can then use these fields in the RE Navigator (left-hand part of the screen) and in the mass-processing transactions for reminder dates (RECARS and RECARSCN). First use the APPEND. technique to insert the additional fields into DDIC structure RECA_RS_OBJ_DATE_MASS_L. Then implement method CHANGE_OUTPUT_DATA and populate the additional fields with the data required. You can use existing data from standard fields to derive your own data.

Requirements

First specify the general attributes and parameters of the reminder rules in the Define Reminder Rules Customizing activity.

Using this parameter definition, the system automatically generates the input screen when the rule is used within RE Navigator. You are not allowed to create your own screens for the input screen. The parameters entered by the user for the reminder rule (such as, number of months, date, and so on) are available in technical form as IMPORTING parameters during the implementation of the BAdI method. The system uses them to calculate the list of dates for the reminder.

Standard settings

Activities

Create a Business Add-In implementation and define the CALCULATE_DATE_LIST method. Then activate the Business Add-In implementation.

Example

The reminder rules provided by SAP (such as A01) are defined by the RECA_RESUBMISSION BAdI implementation of the same name. You can use these standard rules for orientation when defining you own rules.

Note the following:

  • The CALCULATE_DATE_LIST method is called for each of your active BAdI implementations, if the system has to determine the list of dates for a reminder rule. Make sure that you process only the rules you want and do so in only one BAdI implementation. The typical structure of the method is:

               CASE is_rule-rsrule. 
                 WHEN 'Y01'. 
                   "Calculation of the list of dates for rule Y01 
                 WHEN 'Y02'. 
                   "Calculation of the list of dates for rule Y02 
                 ... 
               ENDCASE.

  • Do not directly access databases (SELECT statements) on tables where the data could be being processed. For example, if you tried to retrieve data for the contract term in this way and there are unsaved changes, you do not get the current processing status, and can thereby generate errors in the list of dates.
    Use only the API_RE_xx_GET_DETAIL function module for data retrieval. (Here xx stands for the English abbreviation for the object type, for instance CN for the real estate contract.)
  • Do not use statements that execute actions on the interface, for example, MESSAGE without RAISING, CALL SCREEN and so on. Also, do not use COMMIT WORK or ROLLBACK WORK.

Business Attributes
ASAP Roadmap ID 153   Design enhancements 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20030506 
SAP Release Created in 200