Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
FIN-FSCM-CLM-CM-CM (Application Component) Basic Functions⤷
FTCM (Package) Treasury: Cash Management (SWIFT, BAI, Fed Wire)
IMG Activity
| ID | FI_BL_PY_VC_T028R | repetitive wires |
| Transaction Code | S_P99_41000060 | (empty) |
| Created on | 19990427 | |
| Customizing Attributes | ACC_BLPY_O_N_A | Attribute: repetitive wires |
| Customizing Activity | FIBLPY_VC_T028R_OB | repetitive wires |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | FIBLPY_VC_T028R_DC |
Repetitive payment transaction codes are defined with the banking partner to associate the repetitive transaction code with a funds movement between two specific bank accounts. The transaction code can then be utilized to efficiently move funds as the transaction code and the amount of the transaction fully specify the payment order.
The transaction code might then be utilized on a daily basis with a varying payment amount to quickly move funds between well defined accounts. The transaction code represents a specific funds movement direction between the related bank accounts. A funding source account and transaction currency are maintained with the code in addition to the target account for the funds movement.
Example
Requirements
Transaction codes are entered for four payment areas within the system. Each of the processing areas requires the customization and entry of related data values. Each of the payment code areas might rely on existing house bank account, company code, and payment method configuration related to the ultimate posting and transaction of a payment order.
- Bank to bank transfers - Cash Management transfers between house bank accounts
Cash Management account names existing within the system are utilized tospecify the bank accounts. A related payment advice type is selected for advice generated using the transaction code.
- Vendor payments - Payments to vendors from house bank accounts
Banking details of the targeted Vendor account must be fully realized prior to entry.
- Treasury partners - Payments to treasury business partners
Treasury business partner and payment details for the partner must first entered.
- Customer repetitive - Payments to customer accounts from house bank accounts
Banking details of the targeted Customer account must be fully realized prior to entry.
Hints
Configured repetitive transaction codes are utilized in specific processing areas within the system associated with the generation of payment orders for external transactions. See some common entry and usage transactions listed below within the further description topic.
Although useful in that respect of generation and transaction of an external payment order, the entry of a repetitive transaction can be utilized to quickly enter banking transactions important to be reflected on the cash position of the organization. They can then be entered or transacted with the external banking partner in the commonly used non integrated communciation method.
Activities
Overview entry screen
A freely user defined grouping code is entered to collect logical groups of transaction codes. The grouping is a user defined field which might be used to segregate the transaction codes by bank, operational unit, or transaction entry personnel.
The grouping code is mandatory for entry prior to entry of transaction codes.
Further reference information can be entered for the grouping, such as related company code or bank. However, these fields are used only for user reference as the banking parties of the transaction are maintained in the transaction code details.
The text field grouping name allows the entry of a longer description for the entered group.
To enter transaction codes, please select a single grouping line and then choose one of the payment areas within the navigation window to enter transaction codes related to that group and payment area.
Transaction detail screen
Transaction codes are freely definable by the user. Typically, the code has special meaning to a bank transaction partner and should typically be recognized by that partner. The code selected by the user must be uniquely defined within the repetitive grouping code.
Each payment area maintains different fields related to the generation of payments within that logical area. Please refer to the above preconditions and utilize selection help to fill entries.
The command to Save must be made by the user to retain the customization entries prior to transaction exit.
Further notes
Repetitive transaction codes are utilized within the following transactions within the system. Please refer to each of the specified program documentations for further information on the topic.
Repetitive transaction fast entry (FRFT)
Online freeform and vendor payment requests (RVND)
Cash concentration (FF73)
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_T028R | C - View cluster | SM34 |
History
| Last changed by/on | SAP | 19990427 |
| SAP Release Created in |
