Table of Contents

Search

  1. Preface
  2. Part 1: Getting Started with PowerExchange for SAP NetWeaver
  3. Part 2: Data Integration Using PowerExchange for SAP Dynamic ABAP Table Extractor
  4. Part 3: Data Integration Using ABAP
  5. Part 4: IDoc Integration Using ALE
  6. Part 5: Data Integration Using BAPI/RFC Functions
  7. Part 6: Data Migration
  8. Part 7: Business Content Integration
  9. Part 8: SAP BW Data Extraction
  10. Part 9: Loading Data to SAP BI
  11. Appendix A: Data Type Reference
  12. Appendix B: Code Pages and Unicode Support
  13. Appendix C: Glossary

PowerExchange for SAP NetWeaver User Guide for PowerCenter

PowerExchange for SAP NetWeaver User Guide for PowerCenter

Mappings for Business Content Integration

Mappings for Business Content Integration

You need to import several PowerCenter mappings from BCI_Mappings.xml. Use these mappings and the processing mappings that you create to integrate with SAP business content.
Use the following mappings to integrate with SAP business content:
  1. Listener mapping.
    Receives DataSource data from SAP, loads it to staging targets, and requests that the PowerCenter Integration Service start the appropriate processing and send request sessions for the DataSource. You configure and use the imported listener mapping.
  2. Send request mapping.
    Sends requests for DataSource data to SAP. The PowerCenter Integration Service uses request files generated when you create the processing mapping to request data from SAP. When SAP receives the request, it sends data to the listener mapping. You configure and use the imported send request mapping.
  3. Processing mapping.
    Processes DataSource data staged by the listener mapping and loads it to the target data warehouse. When you create processing mappings, you can specify data selection parameters and determine whether to consume all the DataSource data or only the data that changed since the last time it was processed. You use the Generate Mapping for BCI Wizard in the Mapping Designer to create processing mappings. You create one processing mapping for each non-hierarchy DataSource you want to process. You create one processing mapping for all hierarchy DataSources.
  4. Cleanup mapping.
    Cleans up data in the staging targets. You configure and use the imported cleanup mapping.
You cannot customize the listener mapping or the send request mapping that you import from BCI_Mappings.xml. You also cannot customize the processing mapping that you generate from PowerCenter.
The following table shows the relationship of the business content integration mappings:
Mapping
Source(s)
Target(s)
Notes
Listener
SAP/ALEIDoc source
  • BCI_Scheduling_Target LMAPI target
  • RSINFOStaging relational target
  • Indicator relational target
  • Source_For_BCI relational target
BCI_Scheduling_Target LMAPI target determines which processing and send request mappings are run for each DataSource. Source_For_BCI relational target is the source of the processing mapping.
Send Request
Flat file source
SAP/ALEIDoc target
Source is the request file created when you create the processing mapping.
Processing
Source_For_BCI relational source
Relational target data warehouse
Source_For_BCI relational source is the target of the listener mapping.
Cleanup
  • Source_For_BCI relational source
  • DocumentNumber relational source
Source_For_BCI relational target
Removes processed data from Source_For_BCI relational source.

0 COMMENTS

We’d like to hear from you!