SAP ABAP IMG Activity REAJ_ADJUSTMENT_EDIT (Customer Fields (Editable))

Hierarchy

☛ EA-FIN (Software Component) EA-FIN
   ⤷ RE-FX-AJ (Application Component) Rent Adjustment
     ⤷ RE_AJ_CA (Package) RE: Cross Application Adjustment (Comprehensive Functions)

IMG Activity

ID	REAJ_ADJUSTMENT_EDIT	Customer Fields (Editable)
Transaction Code	S_EE6_85000180	(empty)
Created on	20110802
Customizing Attributes	REAJ_ADJUSTMENT_EDIT	Rent Adjustment: Add Customer Fields (Editable)
Customizing Activity	REAJ_ADJUSTMENT_EDIT	Rent Adjustment: Add Customer Fields (Editable)

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	BADI_REAJ_ADJUSTMENT_EDIT

Use

The Business Add-In (BAdI) makes it possible to add customer-specific input fields and output fields to the processing of adjustments. These fields can be displayed for input or output on a detail dialog box for the adjustment record on a customer-specific subscreen (maximum size 81 x 10).

Requirements

• You must add the customer fields to table VIAJRECORD and structure REAJ_RECORD_MODIFY using append.
• For you to be able to display the customer-specific fields in the adjustment list, you also have to implement the BAdI BADI_REAJ_ADJUSTMENT. Direct output of the append fields in the adjustment list is not supported, since the system is not able to determine which fields belong to which adjustment method.

Description of Methods

• Method GET_EDIT_CONTEXT
It returns the context for editability.

• Import IF_CREATE
This parameter is set, if the adjustment is in create mode (within transactions that can generate an adjustment run, such as REAJPR or REAJPRCEA).
• Import IF_CONTINUE
This parameter is set, if the adjustment is in continuation mode (within transactions that can continue an adjustment run, such as REAJCH or REAJCHCEA).
• Import IF_REVERSAL
This parameter is set, if the adjustment is in reversal mode (within transactions that can reverse an adjustment run, such as REAJRV or REAJRVCEA).
• Import IF_DISPLAY
This parameter is set, if the adjustment is in display mode (within transactions that can display an adjustment run, such as REAJSH or REAJSHCEA).
• Import IF_SIMULATION
This parameter is set if the adjustment was not yet converted to an update run.
• Import IS_RECORD
It contains the relevant process parameters.
• Changing CD_GUI_PBO and CD_GUI_PAI
These parameters are used to communicate the PBO/PAI function modules to the adjustment. These modules are called either before or after the customer-specific screen is output. They supply the relevant data to the adjustment. You can use function group REAJ_GUI_ADJM_EDT_TEMPLATE as a template and adjust your copy to suit your needs.

• Method MODIFY_RECORD
This method is used to modify the adjustment data at various events. In contrast to the method MODIFY_ADJUSTMENT of the BAdI definition BADI_REAJ_ADJUSTMENT, you can use MODIFY_RECORD to also modify data during the continuation of adjustments.

• Import IF_CREATE and IF_CONTINUE
They indicate if the adjustment run is in create mode or in continuation mode.
• Import IF_AFTER_PREASSIGNMENT
This parameter is set, if the call takes place after preassignment is made (immediately before the output of the adjustment list).
• Import IF_BEFORE_STORE
This parameter is set, if the call takes place before saving.
• Import IS_RECORD
It contains the data of the relevant adjustment record.
• Changing CS_RECORD_MODIFY
It is used to return the changed data.

• Method AFTER_STORE
It is called after saving to perform additional actions. Using this method, you can update your own additional data, which was possibly created during processing and needs to be saved (in addition to the append fields mentioned above).

Parameters of Method:

• Import ID_PROCESSGUID
It contains the GUID under which the adjustment run is stored in the tables VICAPROCESSID and VIAJRECORD.
• Import IF_CREATE and IF_CONTINUE
They indicate if the adjustment run is in create mode or in continuation mode.
At this point, make sure all checks were already performed without any errors occurring. No more changes can be made to the data. Only internal errors are now possible here (such as, data inconsistency, errors in the technical infrastructure, or programming errors). For these exceptional situations, you can output termination messages. This is implicitly linked to a resetting of the last database changes (ROLLBACK WORK). You are not allowed under any circumstances to use a COMMIT WORK or ROLLBACK WORK statement within this method, since this can cause internal errors.

• Method IS_ACTIVATE_DISABLED
It is used to deactivate the activation function.

• Import IS_RECORD
It contains the data of the relevant adjustment record.
• Changing CF_DISABLED
The function is deactivated if ABAP_TRUE or 'X' is returned.

• Method IS_ANNOUNCE_DISABLED
It is used to deactivate the notification function. The parameter is analogous to IS_ACTIVATE_DISABLED.
• Method IS_APPROVAL_DISABLED
It is used to deactivate the approval function.

Note that the methods MODIFY_RECORD, IS_ACTIVATE_DISABLED, IS_ANNOUNCE_DISABLED, IS_APPROVAL_DISABLED and IS_DECLINE_DISABLED can only be called for adjustment records with the status 'No Errors in Calculation' or 'Warnings Exist for Calculation'. They are not called for records that are already complete, reversed, or have errors.

The methods IS_ACTIVATE_DISABLED, IS_ANNOUNCE_DISABLED, IS_APPROVAL_DISABLED and IS_DECLINE_DISABLED are only called if the corresponding function would be active in the standard system. For example, the activation function is deactivated, if there was no approval yet for adjustments requiring approval. In that case, the method IS_ACTIVATE_DISABLED is not called.

Notes for Developers

Business Attributes

ASAP Roadmap ID	257	Create User Exits
Mandatory / Optional	3	Nonrequired 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	20110802
SAP Release Created in	606