Automatic Integration of Financial Objects
With the automatic financial object integration (FO Integration) function, you can enter financial object data manually when you create the master data, or you can let the system derive the financial object data. You can use this function when you create the data for the transactions given below. The following rules apply:
Group 1
BCA account
Variable transactions (applies for the SAP Banking application component only)
Generic transactions
Facilities in SAP Banking
You can generate the relevant parts of the financial object (analysis parameters, profitability analysis, default risk and limit, external key figures) as tab pages. You can fill these in when you create transactions. You cannot create the Profitability Analysis
tab page for facilities.
Group 2
Loan transactions
Money market transactions
Foreign exchange transactions
OTC derivatives
Securities and listed derivatives
Securities account class position
Futures account class position
Lot-based position in futures account
Security transactions
Subledger positions and subpositions
Exposure positions
Raw Exposures
Trade Finance
The tab pages Analysis Parameters
, Default Risk Limit
(not for futures account class position), and Profitability Analysis
(not for securities account class position, futures account class position and trade finance) are created for each company code.
Group 1:
To be able to use financial object integration, you need to have set the FO Integration Active / Component Active
indicator for each transaction type (BCA account, variable transaction, generic transaction, facility) in Customizing under Activate/Deactivate Automatic Financial Object Integration
. In Customizing, choose:
, or
, or
, or
, or
.
and then
The relevant parts of the financial object (analysis parameters, Profitability Analysis, default risk limit, and external key figures) are created as tab pages for the activated components. If at least one component is activated, the general part of the financial object and the tab page for the external key figures are activated automatically.
Note
For BCA accounts, you can activate the automatic integration of financial objects on the basis of the bank area and product.
Group 2:
To be able to use the automatic integration of financial objects, you need to have set the Component Active
indicator in Customizing for the individual transactions and the selected component. In Customizing, choose:
, or
, or
, or
Under , or
.
And then
or Activate/Deactivate Financial Object Integration for Security Transaction
(not for profitability analysis)
Note
For the following transactions, you can activate the automatic integration of financial objects on the basis of the company code and product type:
Loan Transactions
Money Market Transaction
Foreign Exchange Transaction
OTC Derivatives
Securities Account Class Position
Class Position in Futures Account
Lot-Based Position in Futures Account
Subledger Positions and Subpositions
(Here, you also need to specify for which valuation area you want to activate the automatic integration of financial objects.)
Group 1 and 2:
If you want the system to derive the financial object data instead of the user entering the data manually, you have to define derivation strategies. Derivation strategies describe what information needs to be derived from the transaction master data.
If you have activated automatic financial object integration for a particular component, when you maintain the transaction data for that component, the system provides online entry screens in which the financial object data can be entered or derived using the relevant derivation steps from Customizing.
Note
The following information applies to the transaction forms ‘option spread’ and ‘currency option.’ You need to generate two financial objects for these transactions. There is therefore no interface for these transactions, and the system does not check the data before it is saved.
When you save the transaction, the system checks the information in the various parts of the financial object. If one of the financial object parts contains errors, the system reacts in one of the following ways, depending on the Customizing setting:
The master data cannot be saved, so neither the transaction itself nor the financial object with the components activated for automatic FO integration are saved on the database. This is the case if the function for the automatic integration of financial objects is fully active.
The master data can be saved, but the financial object part that contains errors is not saved. If all the components activated for automatic FO integration contain invalid data, the general part of the financial object is not saved on the database either. This is the case if the function for the automatic integration of financial objects is partially active.
The following table reflects system behavior using the example of the transaction category "Generic Transaction":
Case 1: Automatic FO integration is active only for component X
Customizing Settings | Is the data saved on the database? | ||||
Automatic FO integration is activated | System reaction when there are errors | Status of data | Generic transaction | General part of FO | Part for component X in FO |
Component X | Data cannot be saved (completely active) | X data is correct | Yes | Yes | Yes |
Component X | Data can be saved without the data of the part for component X (partially active) | X data is correct | Yes | Yes | Yes |
Component X | Data cannot be saved (completely active) | X data contains errors | No | No | No |
Component X | Data can be saved without the data of the part for component X (partially active) | X data contains errors | Yes | No | No |
Case 2: Automatic FO integration is active for component Y as well
Customizing Settings | Is the data saved on the database? | |||||
Automatic FO integration is activated | System reaction when there are errors | Status of data | Generic transactions | General part of FO | Part for component X in FO | Part for component Y in FO |
Component Y | Data cannot be saved (completely active) | Y data contains errors | No | No | No | No |
Component Y | Data can be saved without the data of the part for component Y (partially active) | Y data contains errors | Yes | Yes | Yes | No |
Component X | Data cannot be saved (completely active) | X data contains errors | No | No | No | No |
Component X | Data can be saved without the data of the part for component X (partially active) | X data contains errors | Yes | Yes | No | Yes |
If financial object integration is active for a transaction category, this changes the way in which the system derives characteristics for the Market Risk Analysis and Default Risk and Limit System components. See Editing Characteristic Derivations.