Skip to Content
avatar image
Former Member

Extraction from Datasource 0UC_SALES_STATS_02

Hi All,

We are currently working on developments of sales statistics 0UCSA_C05 cube for a large utility company. As part of building this cube, we are using data source 0UC_SALES_STATS_02 .

When we run info package to extract data from R/3 to BI - PSA, we are not able to get any records into delta queue in source system and as a result the info package is returning "0" records.

We checked the same data source in extract checker (RSA3) & there a pop up comes & ask for print document no .If I provide print document no then it extract 5 records for that particular print document no otherwise it is giving 0 records.

I feel I need to give print document as my selection criteria in the Infopackage so that it will extract that 5 records. But problem is that print document no (OPBEL) is not available in data source 0UC_SALES_STATS_02 so how can I give it as a selection criteria in infopackage.

Please let me know if anyone has worked on data source 0UC_SALES_STATS_02 extraction & what is the exact extraction procedure for this data source.

If anyone has any clue on why the delta is not getting built in source system, pls let us know and appreciate your attention to this message.



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Mar 30, 2009 at 12:50 PM


    If you are doing the extraction for the first time:

    1. Run full load, without any selection.

    2. Do init load, with / without selection depending on your scenario.

    3. Close reconciliation keys in source system (FPG4). The extractor only picks up the records for closed recon keys.

    4. Run transaction EBW_DQ_SS to fill the delta queue.

    5. Run the delta info-package.

    Then you should be able to see some data in your PSA / DSO.

    Once initialized, needless to add, you need to run only steps 3 through to 5 on an ongoing basis.

    Please let me know if this helps or if you have any other Qs.

    The other response to your query is a link to the help for the datasource. I'm sure you have already read through this.



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Saad Asad Khatri


      Actually the IS-U Billing extractor works different from other standard extractors. The Mass Activity program executed in ECC is triggered based on the last info-package executed. If the infio-package is excuted as a delta mode, then mass activity process the delta data. But if the info-package process based on any date or other criteria, then the next mass activity program works only for the parameteres mentioned in the info-package. In any case you will not loose the delta data becuase the next mass activity picks correct data.

      So, there should not be any chance of duplicate data unless you execute some info-package manually. Hope this helps! Please reply if you have more questions.



  • avatar image
    Former Member
    Mar 16, 2009 at 11:39 AM

    Hi Sonal

    Did'nt worked on this.

    But could able to find some documentation,which might be helpful

    go thru the uploading process


    For optimal use of the DataSource, we recommend you check the IMG for BW from Plug-in PI2001.1 and mySAP Utilities 4.63 upwards. Under the application-specific settings, you can find notes on the utilities industry and on the sales statistics. You can find further information releases prior to IS-U 4.63 and Plug-in P12001.1 in SAPNet under the alias Utilities.

    Due to the large amounts of data involved, it is important that OLTP Customizing for the sales statistics is completed before the first productive loading process takes place and that the changes are directly implemented.

    In addition, the DataSource 0UC_SALES_STATS_02 is available from mySAP Utilities IS-U 4.62 upwards. You can only use one of the two DataSources in productive operation. Please see the documentation for the DataSource 0UC_SALES_STATS_02. As a rule, the other DataSource should only be implemented if you experience problems with the load time. It is not as user friendly but produces the same results.


    You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource.

    This DataSource transfers information to the InfoSource 0UC_ISU_01 (sales statistics). This applies to regional information (for example, country, city), contract data (for example, division, business partner) and invoicing data entered in the document line items (for example, rate).

    Address data in the extractor can only be transferred when it has been entered in the IS-U system together with the regional structure.

    In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require.

    If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the installation, the installation contract and the billing documents. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field.

    Additionally, you are able to access the Exit BWESTA01 that enables you to carry out modifications whilst data records are being formatted. This is a higher-performance enhancement than the standard function module for DataSources.

    Delta Update

    After the initial run and initialization of the delta method, you can use this DataSource for the delta upload.

    The full update is supported. However, you must only use the full update to extract documents that contain one or more of the following characteristics:

    u2022 The documents were created prior to IS-U 4.61

    u2022 The documents were created prior to connection to a BW system.

    The documents have already been unloaded into BW. The user is responsible for any inconsistencies

    When you extract the documents for the first time, select the complete posting period.

    We recommend that you carry out initialization and full upload in a number of steps in order to create smaller packages. To improve the performance, select an update via the PSA. The data is extracted in accordance with the selection criteria. In this case, the posting date of the documents is used as the selection criteria.

    Initialize all future posting dates, even if the enhanced selection area does not yet contain any documents. The new documents are automatically entered by delta processing.

    Carry out delta processing at regular intervals. We recommend that large utility companies carry out delta processing on a daily basis. Only documents with closed reconciliation keys can be processed.

    Uploading Processes in Detail

    Full Upload:

    All documents with a closed a reconciliation key are extracted in accordance with the selection. Use the full upload to extract all existing documents after connection of the DataSource.

    Documents with an open reconciliation key are saved in index table DBESTA_BWPROT for later processing.

    Initial Upload:

    All closed reconciliation keys in index table DBESTA_BWPROT are processed according to the initial selection and the associated documents are extracted. You should perform the initialization after the full upload, using the same selection. The initial run only extracts data if in the mean time associated reconciliation keys were closed between the full and initial upload, or if there are new documents.

    Delta Upload:

    All closed reconciliation keys are processed in accordance with the initial selections and the corresponding documents are extracted. This normally concerns new documents in productive operation.

    Features of the Extractor

    As of release IS-U/CCS 4.71, the DataSource can also be used for the ODS. However, because of the large volume of data, you should only create one ODS with definition INSERT (no update of existing records).



    Add comment
    10|10000 characters needed characters exceeded