Structure of a Generic Transaction

The elementary transactions of a generic transaction are identified by a transaction form. This controls the valuation of the elementary transaction in the Risk Analysis component.

Data Selection

You can enter an external number or an internal number, and a version date. The external number identifies generic transaction uniquely. The system assigns the internal numbers. You can use the version date to save more than one version of a generic transaction. You can use the version date in the case of transactions with variable interest payments for example, in order to examine the transaction before and after interest rate fixing.

The sole purpose of version management for generic transactions is to enable you to record changes to the generic transaction as a result of corporate actions (for example a change to the nominal values). When you save a generic transaction, you can choose whether or not the system creates a version. In general, you do not need to use a version date, as changes are documented in the change documents.

Ensure that the version date is always before the start of the term of the first elementary transaction of the generic transaction If this is not the case, the system does not select the generic transaction when you carry out evaluations with an evaluation date that is before the creation date.

If you leave the Version Date field empty, the system uses today’s date as the version date.

You can create one version per day only.

To edit a generic transaction, proceed as follows:

Create without template

Enter an external number to identify the generic transaction.

You can also enter a version date from which the generic transaction is valid. If you do not enter a version date, the system uses today’s date.

Choose ( ) Create .

Create with template

Select a generic transaction that you want to use as a template.

Enter an internal or an external number and a version date, or use input help.

Choose ( ) Copy Generic Transaction .

The system opens a dialog box.

Enter a new external number for the generic transaction.

You can also enter a version date from which the generic transaction is valid. If you do not enter a version date, the system uses today’s date as the version date.

Choose ( ) Copy Generic Transaction .

( )

You can use category 8 for generic transactions that you want to use as a template only.

Change

Select a generic transaction that you want to change.

Enter an internal or an external number, or use input help.

Choose ( ) Change .

( ) Note that you can change the current version only. You do not therefore need to enter a version date for the generic transaction.

Display

Select a generic transaction that you want to display.

Enter an internal or an external number and a version date, or use input help.

Choose ( ) Display .

The system displays a screen that contains all information relating to the generic transaction, or in which you can enter this information. The dialog structure on the left contains the hierarchy of the elementary transactions of the generic transaction. The tab pages on the right contain the master data and the analysis parameters.

Action

To change or create a generic transaction, proceed as follows:

Enter master data for the generic transaction

Enter the following information:

Short name

Enter an appropriate name for your generic transaction.

Category

Generic transactions can have the following categories:

Real Generic Transaction (Category 0)

Transaction that exists in the SAP system and is to be valuated. You can process this transaction online and offline and it is suitable for external data transfer (EDT).

Fictitious Generic Transaction (category 1)

Transaction that the user can create and that is taken into account in ALM simulations only, and not in NPV analysis. You can process this transaction online only and it is not suitable for external data transfer (EDT).

Simulated Generic Transaction (category 2)

Transaction that is generated automatically by the system for ALM simulation. You can process this transaction online only and it is not suitable for external data transfer (EDT).

Sample Hierarchy for a Generic Transaction (category 8)

Sample that contains the hierarchy of the subtransactions of a generic transaction. You can process this transaction online only and it is not suitable for external data transfer (EDT).

Class Supplement as a Generic Transaction (category 9)

Class for a Treasury transaction that is to be expanded to form a generic transaction.

Note that you can create financial objects for generic transactions of category 0 (real generic transaction) only. Generic transactions of categories 1 and 2 (fictitious and simulated generic transactions) are assigned to positions. You can create financial objects for those positions.

Securities Identification Number

Enter the security ID number of the generic transaction.

You do not need make entries for the transaction environment and the security ID number for all transactions. Cash flow transactions for example do not require a security ID number.

Transaction environment

Enter a company code, securities account, portfolio, trader, currency, and business partner for the generic transaction.

Create hierarchy for the elementary transactions

The dialog structure shows which elementary transactions make up the generic transaction, and how the hierarchy of the elementary transactions is arranged. You can use the following interactions in order to create new elementary transactions or change the hierarchy:

For notes on creating structured transactions, see Examples of Generic Transactions .

Elementary transaction data

Select the elementary transaction in the dialog structure.

The system opens a dialog box.

Select the transaction form of the elementary transaction.

The transaction form controls the valuation in Risk Management, as it tells the price calculator what kind of transaction is involved. If a node has an elementary transaction form, the corresponding sub-tree also has to describe this transaction. If this is not the case, inconsistency errors occur.

For more information, see Transaction Form of an Elementary Transaction .

The system creates the tab pages for the header information and the cash flow of the transaction. The entries that the system requires depends on the transaction form of the elementary transaction.

Choose the Header Information tab page .

You must make the following entries for all transaction forms:

Valuation rule

You can define a valuation rule for each of the elementary transactions that belong to the generic transaction.

Note that the valuation rules defined in the elementary transactions are overridden by any valuation rule that is defined in the financial object of the generic transaction.

Default Risk and Limit System

Set the Selected Transaction indicator as required. The following restrictions apply:

The indicator must be set in exactly one elementary transaction.

You cannot change the indicator in elementary transactions with the transaction form 200 (complex financial transaction).

You cannot change this indicator for generic transactions of category 9 (complex class).

Start of Term

You must make an entry in this field for the top node in the hierarchy of the elementary transactions. For all other nodes, this field is optional.

You must enter additional information on the generated tab page, depending on the transaction form you chose. For more information, see the examples of generic transactions.

Choose the Cash Flow tab page and enter the cash flows for the transaction.

Choose ( ) Back and then ( ) Save .

In the case of generic transactions belonging to the fictitious category, the system asks you whether a position is to be generated in position management for generic transactions. The system then assigns an internal number and the description <User><Date><Time> to this position.

You have the following additional options when editing generic transactions: