SAP ABAP IMG Activity BWISUISST_SALES_0010 (Define Performance Settings for Sales Statistics Extractor)
Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication
   IS-U (Application Component) SAP Utilities
     EE80 (Package) IS-U: Customizing
IMG Activity
ID BWISUISST_SALES_0010 Define Performance Settings for Sales Statistics Extractor  
Transaction Code S_KK4_82000949   IMG activity: BWISUISST_SALES_0010 
Created on 20020125    
Customizing Attributes BWISUISST_SALES_0010   Define Performance Settings for Sales Statistics Extractor 
Customizing Activity BWISUISST_SALES_0010   Define Performance Settings for Sales Statistics Extractor 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name BWISUISST_SALES_0010    

The sales statistics extractor formats the information from the billing documents in detail. Based on their weighting procedures, the billing lines items are are divided into months. This is done in order to statistically evaluate expected monthly values, despite cross-month billing (such as annual billing). Due to this level of detail, a large number of statistically relevant records are transferred to BW. In the case of large utilities companies, this may result in impaired system performance during the load process.

The following information describes how to speed up document formatting and how to keep the number of transferred lines to a minimum.

Activities

1. Reduced extractor processing

The billing line items are formatted in the extractor. The lines are read, corresponding master data is determined and any other information read. In addition, the documents are divided into monthly values based on the weighting procedure that was configured in the operand of each billing line.

For this reason, the extractor functions more quickly if:

  • Certain tables do not have to be read because the information in BW is not relevant to the evaluation.
  • You do not want to divide the billing lines into months. This only applies to old documents since the divided bill values are statistically important.

For this reason, this IMG activity contains 3 settings that can be changed at any time. These are as follows:

  1. Division by consumption month as of posting date

    In some IS-U projects, all of the existing bill documents are migrated from the legacy system. This entails the extraction of a large number of entries during the initial download. It is often the case that these legacy document do not have to be divided by consumption month. You can use this setting to define the posting date as of which you want to documents to be divided. This avoids dividing up unnecessary documents and reduces the number of records for transfer.

Only make this setting if you do not want to divide up documents that were migrated from the legacy system.

  1. Posting period

    The standard settings determine that only the posting date is contained in the document. The system has to read additional function modules in order to determine the posting period. The posting period is required in order to compare the billing information with the general ledger. Only deactivate it in exceptional circumstances. Note that the posting date in the document can differ from the posting date of the transfer to FI. For this reason, a comparison of the extracted posting period with the posting period can lead to differences. Therefore, we recommend that you also extract a reconcilliation key into BW, and use it in the InfoCubes.

Only set the posting period indicator if you absolutely do not require the posting period in the InfoCubes

  1. Tax information

    Contains information on the tax base amount, tax amount and tax code. This information is not contained in the billing document but in the print document. The tax informationis divided into monthly values, according to the net amounts. For this reason, the extractor reads the tax amounts from the invoice document.

    If you do not require the tax amounts (only necessary in certain countries), set the tax information indicator. If you do this, the print documents are not read.

If you do not require the tay information then set the tax information indicator

2. Reduce the number of records to be extracted

During the implementation project it is difficult to define what information does not need to be evaluated in BW and what information is required in detailed form. Certain information is only extracted for update rules in to BW. If these fields are already derived, or are not transferred then it is possible to compress the data in the extractor (and not in the InfoCube) without losing information.

However, several implementation projects have shown that the trend is toward a higher degree of detail in BW. This means that the lines that are relevant for statistics should also be available 1:1 in BW. For this reason, efforts to reduce and compromise extracted records can no longer take priority.

The aggregation to a calendar year, for extrapolated documents (such as for settlement prorations) should considered. This considerably reduces the data volume for annual customers.

3. Hide corresponding fields in DataSource maintenance

In DataSource maintenance, hide any fields that you do not want to transfer. This ensures that the initialized fields are not transferred (compare step 2).

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG BWISUISST_SALES_0010 0 I110004876 Information System 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
TE778 S - Table (with text table) SM30 Define Performance Settings for Sales Statistics Extractor 
History
Last changed by/on SAP  20020208 
SAP Release Created in 464