An abnormal termination occurs because a user exit program was not found in FI-SL (for example RGIVUxxx, RGIFUxxx) when you post a document.
Typically, this problem occurs after a release upgrade, an upgrade, a client copy (local or remote) or a system copy.
In the FI-SL Customizing, field movements with user exits were created or exits for validation or substitution were entered, which cause problems with the above-specified actions.
For releases < 3.0:
If program RGIFU000 was not found, you have entered user exits for the fixed field movements but have not programmed any exits. Therefore, check your fixed field movements and create an exit, if necessary.
If program RGIVUxxx (xxx = current client) has not been found, copy RGIVUxxx to your new clients.
As an alternative, you can also use the program RGIVU000 for all clients.
Then start program RGIMOVV0. The program RGIMOVV0 ensures that the respective FI-SL programs are regenerated and the right user exit programs are used.
For releases 3.0A through 3.0B
Please read the release note 'User Exit Programs in the Field Movement' for Release 3.0A first.
You can find the exit programs for the respective application areas in the table T80U (client-independent). These tables you can find in the FI-SL Customizing under Basic Settings -> User Exits.
If a program terminates because a user exit program could not be found (for example, after a client copy), create this exit program by copying an already existing one, include it in this table and then start program RGIMOVV0 to regenerate the FI-SL programs.
As of Release 3.0C
Please read the release note 'Specifying the User Exit Programs in Tables T80I and/or T80D' for Release 3.0C first.
You can find the exit programs for the respective application areas in the tables T80I (client-independent) and T80D (client-specific). These tables you can find in the FI-SL Customizing under Basic Settings -> User Exits.
There shold not be any problems with the client copy.
In the case of a system copy, the user exit programs up to and including Release 3.0F are not also transported automatically.
After the client transport, you have to transport the user exit programs into the target system or maintain them there manually.
In case of an upgrade from a release < 3.0C to a release > 3.0C, the current client is always specified as the last 3 characters of the program name when table T80U is converted to T80D (if the Client-dependent ID was active in T80U), regardless of whether the program exists, or not. This can cause problems with the upgrade. In this case, please make sure to maintain table T80D.
Up to and including Release 3.0E, you have to start program RGIMOVV0 or program RGUGBR00 with the parameters Validation, Substitution, Rules for regenerating the FI-SL programs after each change to table T80D.
General note:
Please ensure that you only use program names that lie in the customer name range (for example, Zxxxxxxx) in the table T80U (up to and including Release 3.0B) or in the tables T80D and T80I (as of Release 3.0C), in which user exit programs are entered.
Please assign a valid customer development class to these programs so that the programs can be transported correctly.
Additional key words
RGICOPY0, T80U, T80D, T80I, RGIVU000, RGIFU000
No comments:
Post a Comment