Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FI-LOC (Application Component) Localization⤷
ID-DMEE (Package) International Development: Data Medium Exchange Engine
IMG Activity
| ID | BADI_DMEECONVERT | BAdI: File Conversion |
| Transaction Code | S_PL0_86000066 | (empty) |
| Created on | 20040220 | |
| Customizing Attributes | DMEE_BADIS | Business Add-Ins for DME Engine |
| Customizing Activity | BADI_DMEECONVERT | BAdI: File Conversion |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | BADI_DMEECONVERT |
Use
You can use this Business Add-In in conjunction with the file conversion program DME Engine: Convert Format of Incoming DME File.
The BAdI has two purposes. First, when the file conversion program reads a file sent to you by a bank, it generates two new files in MultiCash format (a header file and a line item file). This BAdI enables you to change either or both of the MultiCash files before the file conversion program saves them.
Second, this BAdI allows the program, once it has generated the MultiCash files, to automatically call the Electronic Bank Statement program (or any other program of your choice) to process the MultiCash files.
Note
This BAdI is only suitable for use with the DMEE format tree type MCSH. For other tree types, use the BAdI BADI_DMEECONVERT_ABA instead.
It uses the DMEE format tree type as the filter value. If you need to use the DMEE format tree as the filter value, use BAdI: File Modification instead.
Requirements
Standard settings
A standard implementation is provided. It:
- Numbers all incoming payment files in consecutive order
- Automatically calls the Electronic Bank Statement program after reading the files
Activities
If it meets your requirements, activate the standard implementation. Then create a variant for the Electronic Bank Statement Program so that it runs automatically.
If the standard implementation does not meet your requirements, create your own implementation, following the instructions. The BAdI uses the DMEE format tree type as the filter value, so create an implementation for each tree type that you want to use it for.
Example
See also
Methods
Business Attributes
| ASAP Roadmap ID | 207 | Establish Reporting |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20040713 |
| SAP Release Created in | 500 |
