Scribd
Upload
45 views

BW Extractor Enhancement

This document outlines a methodology for enhancing BW user-exits. It describes implementing exit code in the source systems prior to enhancement to avoid retrofitting. There are four exits - one each for transaction data, master data, texts, and hierarchies. The same exit code needs to be implemented in each exit component, along with include files for each system. Function modules should be created per extractor using a naming convention, organized into function groups by exit type and system.

Uploaded by

P177264
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
45 views

BW Extractor Enhancement

This document outlines a methodology for enhancing BW user-exits. It describes implementing exit code in the source systems prior to enhancement to avoid retrofitting. There are four exits - one each for transaction data, master data, texts, and hierarchies. The same exit code needs to be implemented in each exit component, along with include files for each system. Function modules should be created per extractor using a naming convention, organized into function groups by exit type and system.

Uploaded by

P177264
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

BW User-exit enhancement methodology

Bear in mind that this procedure will need to be implemented in each source system from which data is being extracted, ideally prior to any enhancement being undertaken (in order to avoid the need to retro-fit this process). The SMOD enhancement for the exits is: RSAP0001 Within the enhancement, there are four exits. The last digit of the user exit determines the type of extractor for which it is called, as follows: EXIT_SAPLRSAP_001 (Transaction Data) EXIT_SAPLRSAP_002 (Master Data) EXIT_SAPLRSAP_003 (Texts) EXIT_SAPLRSAP_004 (Hierarchies). The same code (as in the file called "Exit Code.txt") needs to be implemented in each exit component.

Exit code.txt (5 KB)

In addition, the attached top include code and other include need to be implemented as ABAP includes - once only for each system.

ZXRSATOP.txt (5 KB)

ZXRSAUXX.txt (5 KB)

The code in these files relates to a naming convention for BW enhancements of "ZBW_<Extractor Name>_EXIT". In order to use this, one function module per extractor to be enhanced should be created. I would recommend creating one function group for each exit type (Transaction Data, Master Data, Texts, Hierarchy) per system, in order to keep the created functions "tidy".

You might also like