Ansicht
Dokumentation
Release 4.02: New Developments for Variable Transactions ( RELNBANK_402_EGK_VARTRAN )
RFUMSV00 - Advance Return for Tax on Sales/Purchases RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Short text
Release 4.02: New Developments for Variable Transactions
Description
The variable transaction was redeveloped for release 4.02. This transaction includes services, non-interest bearing positions, and accounts together in one transaction. The indicator 'type of value maintenance' (possible values: with daily balances, with turnovers, with flows from FI G/L accounts, without own flows) controls whether the variable transaction is a service, a non-interest bearing positions, or an account. Value maintenance is exact-time-dependent. It can be changed with the beginning of a new period.
You can now also assign standard conditions to a variable transaction using a condition list (see also the release information regarding standard conditions). Standard conditions are used when the system can not find any valid individual conditions. As regards individual conditions, you can only maintain transaction conditions. Opportunity conditions are costing-specific, and have to be stored in the STC part of a finance object. Note that the conditions list does not contain any opportunity conditions. These conditions are all usually quite unique, and can not currently be stored as standard conditions. In the future, it will be possible to create a conditions list for opportunity conditions in the STC part of a finance object.
Services, non-interest bearing positions, and accounts are supposed to be replaced by the variable transaction. The conversion report is not contained in banking release F4.02. It will be delivered in a subsequent patch, or with the next release. This means that customers who currently use services, non-interest bearing positions, or accounts can not convert them yet. When you create new transactions, you can still use the new variable transaction for Single Transaction Costing and for Risk Management. The Credit Limit component will be included in banking release 4.03. Creating an RM part in the finance object for variable transactions without its own flow data does not make sense.
The variable transaction was developed using the new SAP Business Data Toolset (BDT). This tool offers easy modification-free enhancement of the variable transaction. For example, you can create your own fields or graphics. Before you can use the variable transaction, you need to use the transaction BUSP to generate the carrier screen for the application object 'JBVT' of the variable transaction.
Damage caused to data by errors
Software/hardware requirements
Installation information
Effects on System Administration
Effects on Customizing
Example Customizing for variable transactions is found in client 000. It can either be transported to
another client together with the other example Customizing using a client copy, or on its own using the item list ISB1_VTU.
In addition to the example Customizing and your own Customizing settings, you also have to maintin the number ranges for the number and the internal key of the transactions, as well as the turnovers.
Effect on batch input
Changes to the Interface
Changes in procedure
Procedure for removing dataset errors
Dependent functions
Planning
Further notes
BAL_S_LOG - Application Log: Log header data rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 3612 Date: 20240328 Time: 174528 sap01-206 ( 97 ms )