Data Extraction Technology

 This post describes the standard methods and architecture for extracting data from source systems and into the first ­level Data Targets.

The preferred extraction method varies depending on the source system technology. The standard extraction methods appear in descending order from most to least desired. Developers must attempt to use the methods at the top of these lists before proceeding down to the less preferred methods.

Seq. Std. Extraction Technology Benefits and Drawbacks
SAP Systems:
1 Delivered extractors  from SAP Benefits:

 

•  Written and maintained by SAP

•  Implements SAP best practices and business knowledge around ERP data.

• Documented at help.sap.com

Guidelines:

•  Read the associated documentation for each specific extractor you intend to use prior to activating it. You should look for extractor specific documents at help.sap.com in the Business Content documentation, and in OSS Notes.
2 Generic extractor using a table or view Benefits:

 

• Extractor code generated automatically (no programming)

• Extractor template code maintained by SAP.

•  Known to work already – limited testing and debugging required

Guidelines:

• Make sure you have checked for an existing, business content extractor prior to choosing this method.

• Where possible, define views on the source SAP system from which to extract data. The view names can begin with ZBW. Views provide an additional layer of abstraction and insulation from table changes on the source system.
3 Custom extractor using

 

ABAP

 Guidelines:

 

•  Make sure you have exhausted the prior to options before embarking on construction of a custom extractor.

•  Follow the SAP guidelines for custom extractors, and model your code after existing extractors.

Courtesy: Project Help Documents

Comments

Post a Comment

Popular posts from this blog

Sample ABAP program for Updating notepad file data to Internal table and Sending it to Application server

 *--Structure type TYPES: BEGIN OF TY_STD, RONO TYPE C LENGTH 4, NAME1 TYPE C LENGTH 20, GEN TYPE C LENGTH 6, FEES TYPE C LENGTH 10. END OF TY_STD. *--Header line and internal table DATA WKA TYPE TY_STD. DATA INT_TAB TYPE TABLE OF TY_STD. *--Application server files are known as "Datasets" *--here "fname" is the Dataset DATA FNAME TYPE C LENGTH 40 VALUE "StudentsInfo.txt". *--Convert notepad file data into internal table CALL FUNCTION 'GUI_UPLOAD' EXPORTING FILENAME = 'C:Documents and SettingsAdministratorDesktopstudents.txt' HAS FIELD_SEPARATOR = 'X' TABLES DATA_TAB = INT_TAB. *--Sending data to Application Server OPEN DATASET FNAME FOR OUTPUT IN TEXT MODE ENCODING DEFAULT. LOOP AT INT_TAB INTO WKA. TRANSFER WKA TO FNAME. ENDLOOP. CLOSE DATASET FNAME.
Read more

OPEN SQL EXAMPLES IN ABAP – PART 2

 ******************************************* **displaying Raw Materials and Finished products **only from MARA table. DATA WA TYPE MARA. * **--WHERE clause is for filtering the records SELECT * FROM MARA INTO WA WHERE MTART = 'ROH' OR MTART = 'FERT'. WRITE: / WA-MATNR, WA-MBRSH, WA-MTART, WA-MEINS. ENDSELECT. * **************************************************
Read more

Domains and Data Elements

  Domains A domain provided Technical attributes (type, length and possible values) for a field. The definition of domain in ABAP is same as that in Mathematics. In the world of Mathematics, a domain is defined as the set of input values that are valid for a given function. The same holds true for domains in ABAP. To understand this, let us first see what is the role of domains in ABAP data dictionary. Domains -> Data Elements -> (Structures, DB tables, program references etc.)
Read more