Hierarchy
⤷ FS-CML (Application Component) Loans Management
⤷ FVVD_ARCHIVE (Package) Loan Reorganization and Archiving
IMG Activity
ID | FVVD_ARCHIV | BAdI: Reset Key Date |
Transaction Code | S_PLN_16000189 | (empty) |
Created on | 20020418 | |
Customizing Attributes | FVVD_ARCHIV | BAdI: Reset Key Date |
Customizing Activity | FVVD_ARCHIV | BAdI: Reset Key Date |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | FVVD_ARCHIV |
Use
You use this Business Add-In (BAdI) in the Loans Management (CML) component. It is executed within the technical check routine for determining a permitted archiving key date.
Using this BAdI you can reset the archiving key date specified in the application for each loan and in doing so exclude documents from the archiving process. Note: It is only possible to exclude documents from the archiving process by resetting the key date.
When the key date is reset, the new key date must not be after the key date determined by the archiving pre-check (otherwise the proposal is ignored).
Note that subsequent business-related checks as to whether documents can be archived can change the stored key date again.
Using this BAdI you can also move the key date specified in the application, up to which the incoming and outgoing payments are to be included, for each loan. There are no restrictions for this.
Requirements
Standard settings
This BAdI is not activated in the standard system.
Activities
After calling up the IMG activity, a dialog box appears, in which you can enter a name for the implementation.
If you have already made other implementations for this BAdI, another dialog box appears, in which the existing implementations are displayed. In this case, choose Create, and proceed as follows:
- In the dialog box, enter a name for the BAdI implementation in the Implementation field, and choose Create.
The screen for creating BAdI implementations is now displayed.
- Enter a short text for the implementation in the Short text for implementation field.
- From the tab index, choose Interface.
The Name of implemented class field is already filled on the tab page, as a class name was automatically assigned to the implementation when you named it.
- Save your entries, and assign the implementation to a development class.
- Place the cursor on the method, and double-click to enter method processing.
- Enter the code for the implementation between the statements
method <Interface name> ~ <Name of method>
andendmethod
. - Save and implement your code. Return to the Edit Implementation screen.
- Save the entries on the Edit Implementation screen.
Note: You can also create an implementation, and then activate it at a later time. In such a case, end the processing stage at this point.
- Choose Activate
The code you stored in the method will be run when the application program is executed.
Business Attributes
ASAP Roadmap ID | 257 | Create User Exits |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-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 | FVVD_ARCHIV | 0 | HLA0100078 | Portfolio |
Maintenance Objects
Maintenance object type | E | Business Add-In - Definition |
History
Last changed by/on | SAP | 20020419 |
SAP Release Created in | 110 |