Hierarchy

⤷

⤷

IMG Activity
ID | ACPY_VC_TFPM042F | Create Payment Medium Formats |
Transaction Code | S_P00_07000227 | (empty) |
Created on | 20000124 | |
Customizing Attributes | ACC_APPY_K_U_A | Attribute (Supplement): Payment Program |
Customizing Activity | ACPY_VC_TFPM042F_OB | Create Payment Medium Formats |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | ACPY_VC_TFPM042F_DC |
In this activity you can create payment medium formats yourself.
Example
Requirements
You will need to create new payment medium formats if the credit institute (house bank) cannot process one of the supplied formats and there is no alternative method of transferring the payment orders (such as IDoc).
Example: The bank expects a data medium exchange format that is only valid for that bank.
Implementation is only possible after the format specification has been thoroughly analyzed to establish the required characteristics of the format. Example:
- What is the name of the format, and where can it be used?
- Who is the recipient of the payment medium, and how are different files to be generated accordingly? If the bank number field is contained in the format header, for example, a file must be generated for each bank.
- In which fields of the format are entries made, and what are the relevant fields in the SAP System called (structures FPAYH, FPAYHX, FPAYP)?
Standard settings
Like the formats provided by SAP, the formats defined in this activity are generated by the generic payment medium program.
Recommendation
Activities
A payment medium format has the following characteristics, which must be assigned in individual activities.
- Format output
Using the Payment Medium Workbench, non-document-based payment media are usually generated as a file. If a particular name of the format appears as a selection option on the selection screen of the generic payment medium program, you must enter this name. If, in addition to the payment medium, an accompanying sheet or a list are generated, you must select it.
- Information about the format
It is possible to create documentation for the payment medium format. You can use the text module FPM_DOCU_SAMPLE as a reference.
- Level of detail
The payments in one payment run are grouped in payment media. The criteria used to group the payments are described by the level of detail.
- Format supplement
The format supplements translate the internal SAP term for the payment method into the language of the format. Example: Entries are to be made in a field in the file according to the direction of payment (bank transfer/debit memo). Two payment methods are created for this in the SAP System, and the relevant format supplements for bank transfer or debit memo are assigned to these payment methods.
- Length and number of reference fields
The file generally contains fields that inform the recipient of the purpose of the payment on the account statement. You have to define the length and number of these reference fields.
- Implementing the formats
If function modules are used to implement the format, entries must be made on the following interfaces:
- Event 00 - Enter sort field
- Event 05 - Enter additional reference fields
- Event 10 - Check format parameters
- Event 20 - Start/file header
- Event 25 - Open/close file
- Event 30 - Order/transaction record
- Event 40 - End/file trailer
If the DME Engine is used, you must select the relevant field in the program control. The above events 05 and 10 can also be used in this case.
- Format-specific parameters
If the format requires fields that are not available in the SAP System, (such as special bank-specific codes for the disk), you have to create a structure in the Data Dictionary that contains the fields. The fields in this structure can be defined as required entry fields and provided with default values. A button is then provided on the selection screen of the generic payment medium program, which can be used to make entries in these format-specific parameters. The parameters in event 20 are then available.
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
VC_TFPM042F | C - View cluster | SM34 |
History
Last changed by/on | SAP | 20000324 |
SAP Release Created in | 46C |