Table of Contents

Search

  1. Preface
  2. Part 1: Introduction to SAP Connector
  3. Part 2: SAP Connector administration
  4. Part 3: Connections
  5. Part 4: Data integration using BAPI/RFC functions
  6. Part 5: Data integration using IDocs
  7. Part 6: SAP BW data extraction
  8. Part 7: Data integration for SAP ADSO
  9. Appendix A: SAP data type reference

SAP Connector

SAP Connector

Importing an SAP ADSO object

Importing an SAP ADSO object

To read from an SAP ADSO, use SAP Table Reader Connector. Import an ADSO object from SAP as a source in Data Integration mappings.
The naming convention of an ADSO is:
/BIC/A<technical_name of ADSO>*
, where * represents the table number associated with an ADSO.
When you import an ADSO into Cloud Data Integration, the Secure Agent imports the following five tables associated with each ADSO:
  • /BIC/A<technical_name of ADSO>1
    . Inbound table for data store <technical_name of ADSO>.
  • /BIC/A<technical_name of ADSO>2
    . Active data table for data store <technical_name of ADSO>.
  • /BIC/A<technical_name of ADSO>3
    . Change log for data store <technical_name of ADSO>.
  • /BIC/A<technical_name of ADSO>6
    . View for extraction from data store <technical_name of ADSO>.
  • /BIC/A<technical_name of ADSO>7
    . View for reporting for datastore <technical_name of ADSO>.
  • /BIC/A<technical_name of ADSO>8
    . View for external access (introduced in BW/4HANA 2.0 <technical_name of ADSO>.
The following image shows the five tables of an ADSO with technical name ZDELTA that you can import from BW/4HANA 1.0 into Cloud Data Integration:
An ADSO is imported with its associated five tables.

0 COMMENTS

We’d like to hear from you!