3
SAP Note Header Data Symptom This note describes how to include user-defined or additional fields in Asset Accounting reports. Other Terms ALV Solution In Release 4.6C, you have to implement the attached advance corrections. Procedure in the example of the RABEST_ALV01 program: 1. Call the ABAP Dictionary (transaction SE11) and enter 'Data type' FIAA_SALVTAB_RABEST. 2. Select the CI_REPRABEST include (double-click). 3. In the table, enter the fields that you want the system to include in the report. You can find examples for this at the end of this note. 4. Activate the change. 5. When you next start the program, change the layout. Copy the new field from the column set to the column selection. Result: The system displays the field in the output list. However, the inclusion of user-defined fields in the report is restricted by the fact that you can always only include fields that are transferred to this report by the logical database. Alternatively, you can also create a sort version (in Customizing for Asset Accounting under 'Information System'). Include the additional field in the sort version and start the program with this sort version. Restriction: When you include the field using a sort version, the system cannot process the formats of the date, quantity and currency fields. Note that you cannot apply this method to transfer fields from the ANLCV structure to reporting. To show additional amount fields from this structure, you also need to modify the report. Note that this method is not available for the RASIMU02 report. See Note 427827 for an enhancement of RASIMU02. Furthermore, you should only transfer the fields actually required, as every additional field impairs the performance. Restriction: The RABIKA_ALV01 report (depreciation comparison) The inclusion of additional ALNB fields is not anticipated. Restriction: Fields from the table ANLV (Insurance data) The fields from the table ANLV are used in the executing report RAVERS_ALV01 only. Non-integrated fields from the table ANLV (structure FIAA_SALVTAB_RAVERS) can be added to the structure CI_REPRAVERS for the report RAVERS_ALV01. In all other standard asset reports, the import of the table ANLV is not taken into account. Examples of selected asset standard fields: ================================================ The fields that are included are supplied with values in the program by a MOVE-CORRESPONDING statement. That is why it is necessary to designate the added fields to the fields that correspond exactly to the original tables or original structures. The component type also has to agree to ensure a correct format. Therefore, always check what the fields in the original structures (ANLAV, ANLB, ANLV) are called and which category they are. Then copy the entries to the CI_REPRA... structure identically. For fields that contain either currency amounts or quantity specifications, you have to specify 335065 - Include user-defined fields in reports Version 16 Validity: 14.05.2014 - active Language English Released On 14.05.2014 10:46:59 Release Status Released for Customer Component FI-AA-IS Information System Priority Correction with low priority Category Program error

335065 Include User-Defined Fields in Reports

Embed Size (px)

DESCRIPTION

335065 Include user-defined fields in reports

Citation preview

  • SAP Note

    Header Data

    Symptom

    This note describes how to include user-defined or additional fields in Asset Accounting reports.

    Other Terms

    ALV

    Solution

    In Release 4.6C, you have to implement the attached advance corrections. Procedure in the example of the RABEST_ALV01 program:

    1. Call the ABAP Dictionary (transaction SE11) and enter 'Data type' FIAA_SALVTAB_RABEST.

    2. Select the CI_REPRABEST include (double-click).

    3. In the table, enter the fields that you want the system to include in the report. You can find examples for this at the end of this note.

    4. Activate the change.

    5. When you next start the program, change the layout. Copy the new field from the column set to the column selection.

    Result: The system displays the field in the output list. However, the inclusion of user-defined fields in the report is restricted by the fact that you can always only include fields that are transferred to this report by the logical database. Alternatively, you can also create a sort version (in Customizing for Asset Accounting under 'Information System'). Include the additional field in the sort version and start the program with this sort version. Restriction: When you include the field using a sort version, the system cannot process the formats of the date, quantity and currency fields. Note that you cannot apply this method to transfer fields from the ANLCV structure to reporting. To show additional amount fields from this structure, you also need to modify the report. Note that this method is not available for the RASIMU02 report. See Note 427827 for an enhancement of RASIMU02. Furthermore, you should only transfer the fields actually required, as every additional field impairs the performance.

    Restriction: The RABIKA_ALV01 report (depreciation comparison)

    The inclusion of additional ALNB fields is not anticipated. Restriction: Fields from the table ANLV (Insurance data) The fields from the table ANLV are used in the executing report RAVERS_ALV01 only. Non-integrated fields from the table ANLV (structure FIAA_SALVTAB_RAVERS) can be added to the structure CI_REPRAVERS for the report RAVERS_ALV01. In all other standard asset reports, the import of the table ANLV is not taken into account.

    Examples of selected asset standard fields: ================================================ The fields that are included are supplied with values in the program by a MOVE-CORRESPONDING statement. That is why it is necessary to designate the added fields to the fields that correspond exactly to the original tables or original structures. The component type also has to agree to ensure a correct format. Therefore, always check what the fields in the original structures (ANLAV, ANLB, ANLV) are called and which category they are. Then copy the entries to the CI_REPRA... structure identically. For fields that contain either currency amounts or quantity specifications, you have to specify

    335065 - Include user-defined fields in reports

    Version 16 Validity: 14.05.2014 - active Language English

    Released On 14.05.2014 10:46:59

    Release Status Released for Customer

    Component FI-AA-IS Information System

    Priority Correction with low priority

    Category Program error

  • reference tables and reference fields. You can assign the reference fields on the Currency/Quantity fields tab page. 1) Date fields: =========== a) Deactivation date (underlying ANLAV structure): Component Component type Short description DEAKT DEAKT Deactivation date

    or b) Acquisition date (underlying ANLAV structure): Component Component type Short description ZUGDT DZUGDAT Asset value date of the first posting

    2) Quantity fields: =========== Quantity and unit of measure (in underlying ANLAV structure): Component Component type Short description MENGE MENGE_D Quantity MEINS MEINS Base Unit of Quantity In addition, you also have to enter 'ANLA' as reference table and 'MEINS' as reference field for the Quantity field on the Currency/quantity fields tab page.

    3) Currency fields: ============ Asset scrap value (in underlying ANLB structure): Component Component type Short description SCHRW SCHRW Asset scrap value

    In addition, you also have to enter 'T093B' as reference table and 'WAERS' as reference field for the Quantity field on the Currency/Quantity fields tab page.

    If the report does not contain the currency, such as report RAANLA_ALV01, you also have to add to the structure CI_REPRA... (for RAANLA_ALV01 in structure CI_REPRAANLA)as a component WAERS with typing TYPE and component type WAERS. 4) Other fields: ============ a) Asset description long text (underlying ANLAV structure): Component Component type Short description TXA50 TXA50_ANLT Asset description

    or b) Depreciation key (underlying ANLB structure): Component Component type Short description AFASL AFASL Depreciation key

    Other Attributes

    Validity

    Correction Instructions

    SE11

    Software Component From Rel. To Rel. And Subsequent

    SAP_APPL 46A 46B

    46C 46C

    470 470

    500 500

    600 600

    602 602

    603 603

    604 604

    605 605

    606 606

    616 616

    617 617

    Correction Instructions

    Software Component Valid from Valid to Number

    SAP_APPL 46B 46C 202321

    Transaction codes

  • Support Packages & Patches

    References

    This document refers to:

    SAP Notes

    This document is referenced by:

    SAP Notes (8)

    Support Packages

    Software Component Release Support Package

    SAP_APPL 46C SAPKH46C13

    1496720 Quantity management and quantity specification in reporting 1158620 Reporting - no summarization of quantity in main numbers

    671702 Validity display time-dependent data 540785 FAQ note:Reporting of Asset Accounting 526282 Reporting: Include error w/ user-defined fields in reports 456965 Display validity time-dependent data 450158 RAGITT_ALV01: No display of ANLA-TXA50 possible 427827 RASIMU02 Displaying and sorting additional fields from asset

    427827 RASIMU02 Displaying and sorting additional fields from asset 450158 RAGITT_ALV01: No display of ANLA-TXA50 possible 456965 Display validity time-dependent data 1158620 Reporting - no summarization of quantity in main numbers 526282 Reporting: Include error w/ user-defined fields in reports 1496720 Quantity management and quantity specification in reporting 671702 Validity display time-dependent data 540785 FAQ note:Reporting of Asset Accounting