2
SAP Note Header Data Symptom You want to extend the Data/InfoSource 0FI_AP_3 or 0FI_AR_3 by additional fields or InfoObjects (e.g. the business area). Other Terms Data/InfoSources 0FI_AP_3 and 0FI_AR_3, ODS objects 0FIAP_O03 and 0FIAR_O03, InfoCubes 0FIAP_C03 and 0FIAR_C03 Reason and Prerequisites Missing documentation on the enhancement of FI-AP/AR line item reporting. Solution We recommend the following procedure: 1. Check in the OLTP system whether the required information already exists in the database tables BSIK or BSAK (for 0FI_AP_3) or BSID or BSAD (for 0FI_AR_3). You can do this by calling either Transaction SE11 or Transaction SE80. ¡ If this is the case (like for example for the business area, field name: GSBER), it is sufficient to enhance the extract structure DTFIAP_3 (for 0FI_AP_3) or DTFIAP_3 (for 0FI_AR_3). The extractor will then fill this field automatically (via move-corresponding). Please note that it is considered a technical modification to add fields that lie in the SAP namespace to the extract structure. ¡ If the desired information is not directly in tables BSIK or BSAK or BSID or BSAD, or if you want to avoid a modification , you first need to enhance the extract structure DTFIAP_3 or DTFIAR_3 by the wanted field as well. The following applies as well if this alternative is used: If the names of the fields to be added to the extract structure lie in the SAP namespace, such an enhancement is a system modification. If the names of the fields are in the customer namespace, it is a modification-free change. Create a function module (any name and development class) which will read the desired information (e.g. from a table which does not exist in the SAP standard) and fill or change the additional field in the extract structure. Use function module SAMPLE_PROCESS_00005020 as a reference (concerning the input and output parameters). After that, enter the function module you just created in table TPS31. This way, the function module will be called for each extracted record. Note that in this case, the performance might deteriorate considerably during the extraction depending on the table which is being read and the complexity of the programmed logic. 2. If no suitable InfoObject exists, it must be created in the BW System. 3. Ensure that the communication structures, the transfer rules, the ODS objects and the InfoCubes are enhanced by the new field or by the InfoObject. Additionally, all changed objects must be activated. Alternatively to the described procedure, you can also use the generic DataSource enhancement which was developed for BW Release 2.0B. The generic DataSource enhancement is described in the BW documentation or in the BW PlugIn documentation. The user exits EXIT_SAPLRSAP_001 for transaction data and EXIT_SAPLRSAP_002 for master data are used here. For reasons of efficiency, we recommend using this method if extensive databse tables (e,g, BSEG, BSIS, KNA1, etc.)are used. With the generic method, processing is conducted by package rather than by every extracted record. The duration of the extraction may be substantially shorter than by record-by-record processing. Validity 321411 - Enhancement of FI-AP/AR line item reporting Version 7 Validity: 08-02-2001 - active Language English Released On 08-01-2001 18:00:00 Release Status Released for Customer Component BW-BCT-FI BW only - Financial Accounting Priority Recommendations / Additional Info Category Documentation error

test

Embed Size (px)

DESCRIPTION

test

Citation preview

  • SAP Note

    Header Data

    Symptom

    You want to extend the Data/InfoSource 0FI_AP_3 or 0FI_AR_3 by additional fields or InfoObjects (e.g. the business area).

    Other Terms

    Data/InfoSources 0FI_AP_3 and 0FI_AR_3, ODS objects 0FIAP_O03 and 0FIAR_O03, InfoCubes 0FIAP_C03 and 0FIAR_C03

    Reason and Prerequisites

    Missing documentation on the enhancement of FI-AP/AR line item reporting.

    Solution

    We recommend the following procedure:

    1. Check in the OLTP system whether the required information already exists in the database tables BSIK or BSAK (for 0FI_AP_3) or BSID or BSAD (for 0FI_AR_3). You can do this by calling either Transaction SE11 or Transaction SE80.

    If this is the case (like for example for the business area, field name: GSBER), it is sufficient to enhance the extract structure DTFIAP_3 (for 0FI_AP_3) or DTFIAP_3 (for 0FI_AR_3). The extractor will then fill this field automatically (via move-corresponding). Please note that it is considered a technical modification to add fields that lie in the SAP namespace to the extract structure.

    If the desired information is not directly in tables BSIK or BSAK or BSID or BSAD, or if you want to avoid a modification , you first need to enhance the extract structure DTFIAP_3 or DTFIAR_3 by the wanted field as well. The following applies as well if this alternative is used: If the names of the fields to be added to the extract structure lie in the SAP namespace, such an enhancement is a system modification. If the names of the fields are in the customer namespace, it is a modification-free change. Create a function module (any name and development class) which will read the desired information (e.g. from a table which does not exist in the SAP standard) and fill or change the additional field in the extract structure. Use function module SAMPLE_PROCESS_00005020 as a reference (concerning the input and output parameters). After that, enter the function module you just created in table TPS31. This way, the function module will be called for each extracted record. Note that in this case, the performance might deteriorate considerably during the extraction depending on the table which is being read and the complexity of the programmed logic.

    2. If no suitable InfoObject exists, it must be created in the BW System.

    3. Ensure that the communication structures, the transfer rules, the ODS objects and the InfoCubes are enhanced by the new field or by the InfoObject. Additionally, all changed objects must be activated.

    Alternatively to the described procedure, you can also use the generic DataSource enhancement which was developed for BW Release 2.0B. The generic DataSource enhancement is described in the BW documentation or in the BW PlugIn documentation. The user exits EXIT_SAPLRSAP_001 for transaction data and EXIT_SAPLRSAP_002 for master data are used here. For reasons of efficiency, we recommend using this method if extensive databse tables (e,g, BSEG, BSIS, KNA1, etc.)are used. With the generic method, processing is conducted by package rather than by every extracted record. The duration of the extraction may be substantially shorter than by record-by-record processing.

    Validity

    321411 - Enhancement of FI-AP/AR line item reporting

    Version 7 Validity: 08-02-2001 - active Language English

    Released On 08-01-2001 18:00:00 Release Status Released for Customer Component BW-BCT-FI BW only - Financial Accounting Priority Recommendations / Additional Info Category Documentation error

  • References

    This document refers to:

    SAP Notes

    This document is referenced by:

    SAP Notes (1)

    Software Component From Rel. To Rel. And Subsequent

    SAP_APPL 40B 40B

    45B 45B

    46B 46B

    46C 46C

    PI 1999_1_46B 1999_1_46B

    PI-A 1999_1_40B 1999_1_45B

    319686 BW objects FI-AP/AR line item reporting BW 2.0B

    319686 BW objects FI-AP/AR line item reporting BW 2.0B