Hierarchy

⤷

⤷

IMG Activity
ID | REAJ_ADJUSTMENT | Implement Enhancements (BAdI) |
Transaction Code | S_EE6_85000037 | (empty) |
Created on | 20100714 | |
Customizing Attributes | REAJ_ADJUSTMENT | General Interventions in Rent Adjustment |
Customizing Activity | REAJ_ADJUSTMENT | General Interventions in Rent Adjustment |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | REAJ_ADJUSTMENT |
Use
The Business Add-In (BAdI) supports enhancements to the standard functions of adjustments of conditions without your writing program code.
For information about possible enhancement scenarios, see the Overview of Enhancement Methods for Master Data Objects and the Real Estate Contract.
Requirements
Standard settings
Activities
Create a BAdI implementation and implement the methods you require for your enhancement. Then activate the BAdI implementation.
For information on using BAdIs, see this documentation.
The following methods exist:
- GET_ADJUSTMENT_VALUE
Gets the value of a variable in the control table - CAPPING
Performs capping - ADJUSTMENT
Performs the adjustment - MODIFY_ADJUSTMENT
Modifies the adjustment - MODIFY_ADJUSTMENT_CEA
Modifies an adjustment of a cost efficiency analysis (Germany) - AFTER_STORE
Performs additional actions after saving - GET_ADJMRULE_FOR_INSERT
Gets the possible adjustment methods to be added - GET_FIELDCATALOG
Gets the field catalog for the adjustment transactions - GET_FIELDCATALOG_VALUE
Gets the value for a field catalog entry - HIDE_FIELDCATALOG
Hides certain field catalog columns (for improved performance) - MODIFY_TCODE
During an indirect call of the adjustment, serves to put the transaction code into effect
- GET_BEHAVIOR_SUBSEQ_COND
Serves to control the adjustment frequency for adjustments of subsequent conditions. Using this method, you can specify using the CF_NO_RHYTHM parameter, if the system should redetermine the adjustment date (standard behavior) or not (CF_NO_RHYTHM = abap_true) when the subsequent condition becomes the condition to be adjusted.
- AFTER_ACTIVATION
Makes it possible to execute follow-up actions on an object after activation of an adjustment
- AFTER_REVERSAL
Makes it possible to execute follow-up actions on an object after reversal of an adjustment
These methods are called automatically during standard processing of the adjustment of conditions. If an implementation exists, the methods are always called in addition to standard system behavior. The standard behavior of the basic actions is not replaced.
Warning
The implementation of the methods has to be independent of the interface. It must not contain any COMMIT WORK or ROLLBACK WORK statements. For example, direct output of messages using the MESSAGE statement is not allowed.
Method description
- GET_ADJUSTMENT_VALUE
This method gets the value of a variable in the control table. The following parameters are used with this method: - IO_CONTRACT and IO_RENTAL_OBJECT
These parameters specify whether or not the condition to be adjusted is a contract condition. If the condition is a contract condition, then the parameter IO_CONTRACT is filled. Otherwise the IO_RENTAL_OBJECT parameter has a value. - IS_CONDITION
This parameter contains the values of the condition to be adjusted. - IF_FIRST_CALL
This parameter indicates whether the method is being called for the first time. If the parameter has a value, then this is the first call of the method. - ID_VALIDFROM_NEW
The parameter contains the newly calculated Valid-From date of the condition. - ID_VARIABLE and CD_ADJUSTMENT_VALUE
The ID_VARIABLE parameter contains the names of the variables from which the CD_ADJUSTMENT_VALUE parameter requested the value. - IT_ADJUSTMENT_VALUE
This parameter transfers all variables of the method as well as their current values.
Then the returned messages (CT_MESSAGE parameter) are displayed in the same list with the messages from standard processing. - CAPPING
This method performs standard rent capping. The following parameters are used with this method: - IO_CONTRACT
This parameter contains the contract object to be adjusted. - IS_CONDITION
This parameter contains the values of the condition to be adjusted. - IF_BEFORE_STANDARD
The parameter has a value before standard capping is performed. - IF_AFTER_STANDARD
This parameter has a value after standard capping was performed. - CS_RECORD
The parameter modifies the adjustment. - CF_EXIT_PROCESSED
This parameter contains the information that the capping was executed by the method. Then the returned messages (CT_MESSAGE parameter) are displayed in the same list with the messages from standard processing. - ID_ADJMRULE and ID_ADJMSUBRULE
The ID_ADJMRULE (combined adjustment rule) and ID_ADJMSUBRULE (adjustment rule) parameters contain the adjustment rules that the implementation is dependent on. - ADJUSTMENT
This method performs the standard adjustment. The following parameters are used with this method: - IO_CONTRACT and IO_RENTAL_OBJECT
These parameters specify whether or not the condition to be adjusted is a contract condition. If the condition is a contract condition, then the parameter IO_CONTRACT is filled. Otherwise the IO_RENTAL_OBJECT parameter has a value. - IS_CONDITION
This parameter contains the values of the condition to be adjusted. - IS_RHYTHM
This parameter contains the frequency data of the condition being adjusted. - ID_VALIDFROM_NEW
The parameter contains the newly calculated Valid-From date of the condition. - CD_UNITPRICE_NEW
This parameter influences the new unit price. - CD_METHREFGUID, CF_ERROR and CF_NO_ADJUSTMENT
This parameter is used to store a link from the adjustment to specific data (see AFTER_STORE).
Then the returned messages (CT_MESSAGE parameter) are displayed in the same list with the messages from standard processing.
If the CF_ERROR parameter is set, then there were errors during execution of the adjustment.
If the CF_NO_ADJUSTMENT parameter is set, then the system could not find an adjustment. - CF_EXIT_PROCESSED
This parameter contains the information that the adjustment was executed by the method. - ID_ADJMRULE and ID_ADJMSUBRULE
The ID_ADJMRULE (combined adjustment rule) and ID_ADJMSUBRULE (adjustment rule) parameters contain the adjustment rules that the implementation is dependent on. - MODIFY_ADJUSTMENT
This method modifies the standard adjustment. The following parameters are used with this method:
- CS_RECORD_MODIFY
This parameter modifies the values of the standard adjustment. - IS_RECORD
This parameter returns the adjustment record calculated by the standard adjustment. - MODIFY_ADJUSTMENT_CEA
This method modifies the values of the standard adjustment that were determined using a cost efficiency analysis. The following parameters are used with this method:
- IO_RENTAL_OBJECT
This parameter contains the rental object to be adjusted. - IS_CONDITION
This parameter contains the values of the condition to be adjusted. - IT_RECORD_METH_ALL, IT_RECORD_TASK, IT_RECORD_TASK_OBJECT
These parameters return the method-specific adjustment values. - CS_RECORD_METH
This parameter influences the adjustment results.
Then the returned messages (CT_MESSAGE parameter) are displayed in the same list with the messages from standard processing. - GET_ADJMRULE_FOR_INSERT
This method influences the number of adjustment rules for assignment within a contract object or rental object.
- IO_CONTRACT and IO_RENTAL_OBJECT
These parameters specify whether or not the condition to be adjusted is a contract condition. If the condition is a contract condition, then the parameter IO_CONTRACT is filled. Otherwise the IO_RENTAL_OBJECT parameter has a value. - CT_ADJMRULE
This parameter influences the number of adjustment rules. - GET_FIELDCATALOG
This method specifies additional output columns for the adjustment transactions, thereby determining the field catalog.
The parameters IF_REVERSAL, IF_SIMULATION, IF_CONTINUATION, IF_DISPLAY tell you which transaction you are in.Using the CT_FIELDCATALOG parameter, you can specify the following additional output columns:
- GRIDROLL: Data element in customer namespace that contains the documentation
- GRIDTEXT: Column header
- GRIDJUST: Setting of column values (R = right aligned, L = left aligned, C= centered)
- GRIDCHECK: Specification of whether the column values are displayed as checkboxes
- GRIDPOS: Position of the column
- GRIDSUM: Specification of whether a column total is output for the given column
- GRIDTYPE: Data type of the column value (A = amount, D = date field, <blank> = Other)
- GRIDCOLOR: Color of the column
- GET_FIELDCATALOG_VALUE
This method returns values for the field catalog mentioned above.
- IO_CONTRACT and IO_RENTAL_OBJECT
These parameters specify whether or not the condition to be adjusted is a contract condition. If the condition is a contract condition, then the parameter IO_CONTRACT is filled. Otherwise the
Business Attributes
ASAP Roadmap ID | 153 | Design enhancements |
Mandatory / Optional | 3 | Nonrequired activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | REAJ_ADJUSTMENT | 0 | ALN0000032 | Rent Adjustment |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20100714 |
SAP Release Created in | 606 |