Diagnosis
Elementary transaction &V1& is a Bermuda option. However, at least oneprevious elementary transaction has a different transaction form.
The hierarchy for Bermuda options is restrictive. It must not contain anelementary transaction with a transaction form other than that forBermuda options above the Bermuda option itself.
Your hierarchy must have the following structure:
Bermuda option
,,|_Bermuda option
,, |_Bermuda option
,,,,,, |_Underlying,,
It must not be structured like this:
Elementary transaction
,, |_Bermuda option
,,,, |_Bermuda option
,,,,,, |_Underlying
An exception is the complex transaction (transaction form 200). If thefirst elementary transaction is a complex transaction, then the Bermudaoption(s) below this level can be depicted as subtransactions. The samerestrictions as for non-complex transactions apply to thesubtransactions themselves in terms of transaction 063 (Bermuda option).
Note: The system determines the number of the elementarytransaction for a generic transaction (transaction RCA00) by assigningnumbers, starting with 1, on each level of the hierarchy tree, startingfrom the top and working downwards. In the external data transfer, thisnumber matches the NGIDNR, the sequential number for a GID in the FGET.
Example
Number,, Tree
1,,,, Elementary transaction (top level)
2,, ,, |_ Elementary transaction (second level)
4,,,, |_Elementary transaction (third level)
5,,,, |_Elementary transaction (third level)
7,,,, |_Elementary transaction (fourth level)
3,,,, |_ Elementary transaction (second level)
6,,,, |_Elementary transaction (third level),,

Procedure
Either choose a different transaction form for the elementarytransaction, or correct your hierarchy for the generic transaction.