Authorization Object: F_RPCODE
Repetitive Code
Category: Payment Transactions
Definition
Repetitive codes are used to simplify processing of recurring payments.
Such usage is agreed between the user and the bank. In this respect,
the following activities are offered:
Create and change to bring the data into the system,
Lock and release, to control usability,
Display, to enable the user to use the function,
Display change documents, to enable you to display the master data
changes.
You should only use the delete function once you have carefully checked
and agreed with the bank that it is clear that a repetitive code is no
longer being used and may be deleted.
A check is made of the authorization object during among other things
repetitive code maintenance (OT81), with their use in vendor payment
requests (RVND) and in the fast entry of repetitive payments (FRFT).
Click on the objects below, to expand data.
Object Fields
The list below includes the object’s fields, ordered by industry-standard importance:
| ACTVT | Activity | Filled in 100% of cases |
| BUKRS | Company Code | Filled in 100% of cases |
| PTYPE | Category Of Business Partner Receiving Payment | Filled in 100% of cases |
Popularity Statistics
Average popularity of F_RPCODE in roles: 0% (What does this mean?)
Average popularity of F_RPCODE by users: 2% (What does this mean?)
Object F_RPCODE is frequently used by users in the following areas:
FI:Financial Accounting
BC:Basis Components
Environmental Analysis
1. Common authorization objects used with F_RPCODE:
| F_REGU_BUK | Automatic Payment: Activity Authorization For Company Codes | Objects appear together in 20% of cases |
| F_BKPF_BUK | Accounting Document: Authorization For Company Codes | Objects appear together in 0% of cases |
| F_BKPF_KOA | Accounting Document: Authorization For Account Types | Objects appear together in 0% of cases |
| F_KNA1_APP | Customer: Application Authorization | Objects appear together in 0% of cases |
| F_KNA1_BED | Customer: Account Authorization | Objects appear together in 0% of cases |
| F_KNA1_GEN | Customer: Central Data | Objects appear together in 0% of cases |
| F_KNA1_GRP | Customer: Account Group Authorization | Objects appear together in 0% of cases |
| F_LFA1_APP | Vendor: Application Authorization | Objects appear together in 0% of cases |
| F_LFA1_BEK | Vendor: Account Authorization | Objects appear together in 0% of cases |
| F_LFA1_GEN | Vendor: Central Data | Objects appear together in 0% of cases |
| F_LFA1_GRP | Vendor: Account Group Authorization | Objects appear together in 0% of cases |
| F_PAYRQ | Authorization Object For Payment Requests | Objects appear together in 0% of cases |
| S_TCODE | Transaction Code Check At Transaction Start | Objects appear together in 0% of cases |
2. Appearance of F_RPCODE in T-Codes:
| FIBLAPOP | Vendors – Payment Request | Used in 100% of cases |
| FIRPGR | Repetitive Code Groups Maintenance | Used in 100% of cases |
| FRFT_B | Repetitive Codes: Payment to Banks | Used in 100% of cases |
| FRFT_TR | Repetitives: Payment Treasury Partnr | Used in 100% of cases |
| OT81 | Process Repetitive Codes | Used in 100% of cases |
| RVND | Create Payment Requests Online | Used in 60% of cases |