Ansicht
Dokumentation
CRM_CHECK_POST_PERIO - Check Closed Posting Periods/Fiscal Years
ROGBILLS - Synchronize billing plans PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Use
You can use this Business Add-In (BAdI) to define the scope of the fiscal year check and period check. The desired check is passed on in parameter CHECK_KIND:
CHECK_KIND = 0: No check
CHECK_KIND = 1: Check performed only if the contract change affects dates in the past.
CHECK_KIND = 2: Check performed only if the contract change affects dates in the future.
CHECK_KIND = 3: Check performed for both past and future periods.
Requirements
If you create your own implementation, you will find the global variables of the individual CHECK_KIND in include CRM_LEAS_CON_MISC under gc_no through gc_all. This include is a sub-definition of global CRM definition CRM_DIRECT.
Default Settings
The Business Add-In is active in the standard delivery. The default coding is performed automatically.
The Business Add-In supports multiple use. All active implementations are called and executed.
The Business Add-In is not filter-dependent.
Activities
After you have called the IMG activity, proceed as follows:
- In the following dialog box, enter in the field "Implementation" a name for the BAdI implementation and choose Copy.
- If implementations have already been created for the BAdI, a dialog box with the existing implementations will be displayed. In this dialog box, choose Create.
- In the corresponding field, enter a short text for implementation .
- In the tab Propertiesenter filter properties - if this is a filter-dependent BAdI.
- Choose the tab Interface.
- The name of the implementing class is generated by the system based on the name of your impmlementation. You can change the name.
- If the BAdI is a menu exit, the tab FCodes also appears.Enter a function here and, if necessary, additional data.
- Save your entries and assign a package.
- Position the cursor on a method. Call up the Class Builder by double-clicking it.
- Between the statements method <Interface-Name>~<Name of Method>. and endmethod, enter the coding you request for the implementation.
- Save and activate your coding, and navigate back to the screen Change Implementation.
- Save on the screen Change Implementation.
- Note: You can first create an implementation for the BAdI and then activate this later on. In this case, close the processing function at this time.
- Choose Activate.
- When the application program is executed, the coding you have created will be run.
Example
CL_GUI_FRONTEND_SERVICES - Frontend Services PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 3249 Date: 20240523 Time: 174743 sap01-206 ( 44 ms )