ISU – Sales Statistics Extractor (0UC_SALES_STATS_02)

Introduction

Few years back when I started with my SAP IS-U/BW support project, I had to go through the process of learning on how the extraction takes place from SAP source system for special extractors such as Sales Statistics and how the delta queue is updated.

I had to go through many posts and reach my seniors on how to perform the data extraction.I have tried to share the points gathered and lessons learnt from my experience below.

IS-U Sales Statistics (Delta created by Mass Activity) – 0UC_SALES_STATS_02:

Sales Statistics is the standard industry specific solution for an Utility company.

• It helps in evaluating consumption and revenue.
• Statistics is generated for all invoiced billing documents with consumption and revenue data.
• The posting or consumption period serves as a time basis.
• It acts as a basis for optimizing rate structure and pricing.
• It provides standardized and process related analytical information and acts as a reliable source.
• 0UC_SALES_STATS_02 data source is available from the ISU release 4.62
• BIW_ISU_ESTA is the extract structure.
• ISU_BW_SALES_STATISTICS is the function module
• Delta mechanism – Only New Records via Delta Queue (NEWD)
• BWESTA01 is the standard exit for 0UC_SALES_STATISTICS_02
• Function Group: XE71ESTA01
• Function Module: EXIT_SAPLE71ESTA01_001.

Steps to extract Sales Statistics data to BW:

• • Trigger Full load in BW to establish connection between ECC and BW. The no.of records loaded is 0.
  • Trigger Init-without data transfer in BW, this is to initialize the delta queue in RSA7 (ECC).
  • RSA7 – Delta Queue is initialized.
  • Trigger the mass run EBW_DQ_SS with the Date ID and Identification and pass the Posting Date as a selection (huge selection range).                                                           Prior to mass run (EBW_DQ_SS) “Reconciliation Closure” Job needs to be executed and completed.
  • Set the Technical settings (Variant and No.of Jobs), Save the parameters and Schedule Program Run.   

• • On completion of mass run in ECC, the delta queue in RSA7 gets filled. RSA7 – Delta queue for 0UC_SALES_STATS_02 is filled.
  • Trigger the Delta load in BW to extract the records.

• Load data from PSA to further data targets in BW

Additional Information:

• Mass activity pushes data to delta queue only if there are any closed Reconciliation Keys for the day.
• Creation of new Invoice/Print Document leads to an entry in Invoicing tables such as ERDK and other tables and in DBESTA_BWTRIG table. Delta since last request is existing in this table.
• EBW_DQ_SS mass run looks into DBESTA_BWTRIG entries and if Reconciliation Key for the relevant Print Doc is closed, then the same documents are pushed to delta queue.            Tcode – FPF3 shows the status of Reconciliation Key. “Postings can no longer be made” means that the Reconkey is closed.
• To close the Reconciliation Key use Tcode – FPF2.
• Once data is available in delta queue, it can be extracted to BW.
• Once the Print Doc is pushed to Delta queue the entry in DBESTA_BWTRIG is cleared.
• DBESTA_BWPROTH is the history table which records all the extraction history.

Lessons Learnt:

• What happens if a Full load is triggered when the Delta is already set.
  • The full load would not result in any records, instead an entry in DBESTA_BWTRIG is created. “Created by Request” field in DBESTA_BWTRIG is filled with Full IP Request ID.
  • While the next Delta is triggered as per schedule then the above full load selection is also extracted along with delta records (New records).
  • If the selection in Full load was already extracted before then the delta load would result in duplicates.
  • It is better we do not disturb the delta load by triggering Full load in mid of the schedule.
• There is no chance of missing documents because until the relevant Reconciliation Key is closed in ECC, it is not extracted to BW and it is staged in DBESTA_BWTRIG.                      On Reconkey closure it would be available for extraction.
• Tcode –
  • FPF2  – Close Reconcilation Key
  • FPG1 Transfer of FI-CA Totals Records to General Ledger
• Closing Reconciliation Keys –
  • Each reconciliation key for which the values are transferred to the general ledger must be closed first.
    This ensures that no other postings are carried out for this reconciliation key and that the recorded values cannot be changed.

Conclusion

This post will be helpful for BW consultants who are new to SAP ISU and would have to perform Sales Statistics Extraction.