Ansicht
Dokumentation
Report Writer: Extended data set entries ( RELNFI_GLX_RW_ERWDS )
BAL_S_LOG - Application Log: Log header data BAL Application Log DocumentationDiese Dokumentation steht unter dem Copyright der SAP AG.
!!!!!!!!!!!!NICHT ÜBERSETZEN - RELEASE-2.1-RELEVANT!!!!!!!!!!!!!!!
Kurztext
Report Writer: Extended data set entries
Beschreibung
Function
Multi-dimensional additional conditions can now be linked to data fields.
Explanation
Up to now, an additional field could be defined with a fixed value for a data field. This combination defined a data set entry. Example (data base tables GLT0/GLT1/GLT2): The data set entry HSL-0 (local currency/Ist) consists of the link of the data fields 'Local currency' HSL++' with the field 'record type' RRCTY ='0'. (record type '0'/'1' defines actual/planned values. The definition was carried out via table T804B.
It is now possible to define several additional fields to a data field. This is achieved by linking a data field with an additional set. This additional set can be a basic, single or multi-dimension set and can contain any values and value ranges per dimension. The additional set is treated analog to the existing additional field, that is, for calculating the report values corresponding to the data set entry only data base records which meet the additional set are taken into consideration.
Example
A report should have following 3 columns (local currency)
Column 1: Record type 1 (plan) / fiscal year 1991 / version variable
Column 2: Record type 0 (actual) / fiscal year 1992 / version 001
Column 3: Variance
It would not have been possible up to now to create this report since the first two columns would have had to be defined as logical columns. As a result it would not have been possible any more to calculate the variance.
However, the report in which data set entries are defined for the first two columns can be implemented now. They refer to data fields HSL++ with the additional sets
:-----------:
|0Z-PLAN-91 | Plan 1991
M-----------:
| :RRCTY-------: Record type
>-----------|0ZRRCTY_1 | Additional set for T804F
| :B-----------: 1
| :RYEAR-------: Fiscal year
>-----------|0Z-RYEAR-91 | Fiscal year 1991
| :B-----------: 1991
| RVERS:-------: G/L version
>-----------|0Z-PVERS | Plan version
:B-----------: &PVERS
for column 1 (data set entry ZHSL-1-91) and
:-----------:
|0Z-IST-92 | Actual 1992
M-----------:
| RRCTY-------: Record type
>-----------|0ZRRCTY_0 | Additional set for T804F
| :B----------: 0
| RVERS-------: Fiscal year
>-----------|0Z-RYEAR-92 | fiscal year 1992
| :B-----------: 1992
| RVERS--------: G/L version
>-----------|TZ-SEL-PVERS| version
:B-----------: 001
for column 2 (data set entry ZHSL-0-92). A simple data set is enough to create the desired 3 columns as a column set:
:*D----------: Data set
|TZ-I92P91 | Planned 91 / actual 92
:D-----------: ZHSL-1-91
ZHSL-0-92
<002> - <001>
All data set entries are defined in the new ATAB table T804F now. Table T804B which had this function up to now defines data fields as before but without an additional field (ADFLD) and additional value (ADVAL). The definition of a data set entry in table T804F consists of the data field definition from T804B and an additional set. Line and column texts are stored in the new text table T804G. (see 'Änderungen in der Vorgehensweise'.)
Note
In checking field usage, the fields of an additional set are taken into account where the corresponding data set is, thus in the report line, report column or as a selection set. If a field has already been addressed in a report via a set, it may no longer be addressed in an additional set (and vice versa).
Soft-/Hardwarevoraussetzungen
none
Besonderheiten bei der Installation
With release 1.2A, the new definitions of the already existing data set entries are included in the standard version for the SAP standard data bases of FI-GLX (GLT0, GLT1, GLT2). The delivery is carried out in client 000. After installing release 1.2A, these definitions must then b transported to all other clients with the help of program RGRT804F. For this purpose, the program must first be started in client 000, after this in the other clients.
In addition to transporting the standard definitions, the program RGRT804F also converts definitions of data set entries of data base tables defined by the user.
After successful conversion, all report groups must be generated in all clients again. The program RGRJBG00 (mass generator) can be used to do this.
Both programs can be started in batch. Depending on the number of report groups, generation can take a little longer so that a batch run (per client) is preferable. If a program is cancelled online because of timeout, it must be carried out in batch in any case.
It is very important that the program RGRT804F runs on the same application server for all clients. The reason for this is that definitions for a file are exported on the current application server (client 000) or imported from the file (client unequal to 000). In particular, bear in mind that the batch server can be different to the current application server.
Auswirkungen auf die Systemverwaltung
none
Auswirkungen auf das Customizing
none
Änderungen in der Vorgehensweise
The definition of data set entries is carried out via the maintenance of table T804F with the help of transaction SM31. Data set entries defined by the user must start with the letter 'Y' or 'Z'.
The additional sets can contain value and set variables.
The following entries would be made in the above example on the entry screen:
| Table | Name in the | line text | |
| Data set | Column text | ||
| Data field | additional set | ||
| Definition | |||
| ________________________________________________________________________ |
none
GLT1,,ZHSL-0-92,,Localc. Actual 92
,,,,Localc. Actual 92
,,,,HSL,,0Z-IST-92
GLT1,,ZHSL-1-91,,Localc. Planned 91
,,,,Localc. Planned 91
,,,,HSL,,0Z-PLAN-91
After a new data set entry has been defined, it must be activated in the relevant libraries of the Report Writer. (transaction 'change library', screen 'data set entries'.)
Abhängige Funktionen
none
Planungen
For release 1.2A, it is not yet possible to use period fields as an additional dimension. This functionality is under preparation.
Weitere Hinweise
If no conversion has been made and a report group is generated, typically the following error messages are issued in the area FI-GLX (the field 'record type' was an additional field up to now):
Field record type does not exist
HSL-0 does not exist in data set Z-DATA-00 (column 001)
If the error still occurs after the conversion during the generation
Field record type does not exist
the libraries must still be converted. Therefore, it is enough to access it with the maintenance transaction (GR22) and then save it.
With the CO reports (table CCSS), there is the problem, that the field 'version' (VERSN) was used at the same time as an additional field and as a 'transparent' field (to which sets are created). Since all fields are now transparent, the CO reports cannot all be started even after the tables were successfully converted and must be changed. However, this only concerns reports defined by the user since the standard reports will be delivered again.
CPI1466 during Backup rdisp/max_wprun_time - Maximum work process run time
Diese Dokumentation steht unter dem Copyright der SAP AG.
Length: 9723 Date: 20240523 Time: 160044 sap01-206 ( 144 ms )
