Page tree
Skip to end of metadata
Go to start of metadata
Image/data in this Article is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Analysis of BI Extraction Order for the IS-U Sales Statistic

1. Starting Transaction EBW_SS_MON

Transaction EBW_SS_MON will show this Selection screen with the following Selection Criteria:

2. Group Extraction

Using the Group Extraction, you will get all the Trigger (Reconciliation Keys) created during invoicing, which are waiting for the next Delta Extraction. With Note 1966568 and 1964400 we provide a new Trigger- Table to manage the Delta Extraction. This Table is DBWESTA_BWTRIG. If you have Entries in the old Trigger Table DBESTA_BWPROT left, they will be copied by running this report, doesn’t matter which Source you selected. 
With this Source Selection you will get an overview how many and which Reconciliation Keys are ready to be transferred to BI.

2.1. Fields which are shown in the monitor

  After running the Group Extraction the following monitor is shown:

Now we will go thru every Column

  1. Which Data Source was used to extract the data. If you are only using one Data Source it doesn’t matter, but if you are extracting data with 0UC_SALES_STATS_02 and 0UC_SALES_STATS_03 it is needful which data are belonging to which Data Source.
  2. The Reconciliation Key which should extracted.
  3. Status of the Reconciliation Key, showing if the Key is closed or not.
  4. Posting Date which is used.
  5. Date when the Document belonging to this Reconciliation Key was created.
  6. FMode means the Update Mode, so you see a D for Delta Extraction.
  7. BW Status tells you if the transfer just begun or if the Transfer did not start yet.
  8. If the Transfer started and did not end, this field shows the last transferred document.
  9. InitStatus, shows that the initialization matches the dates of the Reconciliation Key, which means is the Key and the documents are in the time range of the init send from the BI system.
  10. If you click on this symbol, you will see all documents belonging to the Reconciliation Key.
  11. With this Button you can start a simulation of the transfer.
  12. After the simulation runs you will see a log for the simulation and you can show it by clicking on the symbol of the log.

3. Individual Extraction

The individual Extraction is to check if there are any Reconciliation Keys not transferred because of a failure during the extraction. From technical point of view, this shows all entries from table DBESTA_BWTRIGE. If there are entries in table DBESTA_BWPROTE left, which was used before, they will copied with this transaction.

3.1. Fields which are shown in the monitor

Now we will go thru every Column

  1. Data Source which is used for the extraction.
  2. Which Reconciliation Key is used.
  3. Status of the Reconciliation Key (is the Key closed or still opend).
  4. Posting Date of the created Documents
  5. Print Document Number, which fails.
  6. Which Business Partner was used in the Print Document.
  7. Used Contract Account.
  8. The program checks whether the Document is within the initialized Period of the used Data Source. If yes, you will see a green light, if no a red one.
  9. Button to start a simulation of the transfer, to see what the problem is or if the problem still exist.
  10. After the simulation runs, you will find a log in this column.
  11. Total Amount from the Print Document.
  12. With which Currency was the Print Document posted.
  13. If we have a real document, this field is checked otherwise
  14. The field “Document simulated” is checked.
  15. This field is only filled if we have a reversal document. Then you will see the document number from the original Print Document in this field.

4. Extraction History

Last but not least you have the possibility to show the extraction history, means which Reconciliation Keys were extracted before. Let’s check which fields are shown with this option.

  1. Data Source which is used for the extraction.
  2. Which Reconciliation Key is used.
  3. Posting Date of the created Documents.
  4. Date when the Documents were created.
  5. If you hit the expand icon you get more information about the extracted document, like Business Partner and Contract Account.
  6. Possibility to run a Simulation.
  7. After the Simulation run the Application log is filled and shown within this field.
  8. Request which transferred the data to BI.
  9. Status information about the extraction and the Trigger.
  10. Extraction Date.
  11. Extraction Time.
  12. How long does it took to extract.
  13. Print Document from.
  14. Print Document to.
  15. How many Billing Documents are included.
  16. How many Error were thrown.

go to the top

How to use transaction EBW_DQ_SS to transfer data into the delta queue

After starting the EBW_DQ_SS you will see the following screen:

In field (1) you have to insert a date ID and a identification, like it is needed in every mass activity. In field (2) you get information about the status of that run.

Now lets go through the fields on each tab.

1.) This field needs only be filled if you want to extract the data twice! That means if you want to extract you sales statistic data into a second system by using the data source
     0UC_SALES_STATS_03, you need to start the EBW_DQ_SS ones without in additional data source and a second time with the additional data source 0UC_SALES_STATS_03
     inserted in this field.

2.) Just use this selection if you want to extract only special posting dates.

3.) Possible selection for Reconciliation Keys.

4.) Mark this if you want to run only a simulation without any update in the delta queue.

On the tab of Technical Settings you can do the following

1.) Select a existing Variant or create a new one for the parallel processing object BW_DQ_SS

2.) and 3.) Decide if you want to use the automatic load distribution or if you want to distribute manual number of jobs to special hosts.

Last but not least check the log tab

On this tab you will get detailed information about the status of the job and you are able to jump into the job log or into the application log.

go to the top

Handling of quantity sign during extraction 

This article will show you how the sign of any extracted quantity is determined. We differentiate 3 way how a sign is determined.

The billing document shows a positive amount

If we have a positive amount, the sign of the quantity will be also positive.

The billing document shows a negative amount

If we have a negative amount, the sign of the quantity will be also negative, even if it is shown positive in the billing document.

The billing document shows an amount of zero

If the amount is zero, the sign of the quantity is determined from the sub transaction.

Is it possible to change the sign at its own imagination?

Yes it is. We offer a user exit, EBIA001 --> Function Modul EXIT_SAPLEA16HELP_002. This customer extension is called twice, once before the logic described above is called and once after. So you can store or check the sign when the customer extension is called first (time = start) and compare it with the sign you have at the second call (time = end). If the sign is not as you expect, you will be able to change it at that time.

Customer extension is called first with time 'START'.

Second call of customer extension with time 'END'.

Manual Billing Document was not transfered

You have a manual Billing Document, where the Net amount is zero and you expecting that it gets transfered to your statistic system, because the billed quantity is not zero. Since a manual Billing Document gives you a lot of options how to creeate the document, you need to specify the type of quantity (see next picture)

Only if this was set the statistic can assign the given quantity and add it to the right sum. If you do not set it, the documents will be missed in your statistic. To correct this issue, you can create a new document without having inconsitencies, because the wrong document was not transfered. If you are realy sure you can also change the field "ARTMENGE" of table DEBERCHZ1 for the affected documents.

Days of the current Contract


A extracted print document has a change of the rate category within the billed period. This change is also shown in the extracted data in your BW system. In the field "Number of billed Contract Days"  you only see one entrie in the first extracted line item. But you expecting a proration and a value for each rate category.


The field "Number of billed Contract Days" only counts the whole days which are billed for this contract, it does not show the number of days billed for each rate category.

Incorrect distribution of quantities and amounts

By clicking on this link, you will find information how the distribution of quantities and amounts is working.

go to the top

Specifications for Sales Statistics Extractor

After starting transaction SBIW, you go to the customizing point "Define Specifications for Sales Statistics Extractor":

the following options are shown:

Why there are these options for additional source documents? What does this mean?

Sales statistic with the sales statistic data sources is based on the billing documents comming from IS-U billing. But the main documets which are transfered to BW are the print documents created in IS-U invoicing. Additional it is possible to tranfere also documents which are invoiced with the convergent invoicing or from the SD. The problem here is, that the base of this documets is not the IS-U billing. Thats why in case of extracting CI (convergent invoicing) documents or SD- documents, you need to check this settings. When this is done the sales statistic also looks for sorce documents coming from the marked sources.

go to the top

  • No labels

1 Comment

  1. Great Info. All in one spot - thanks !