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|
|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
• 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
• 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|
• 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