Hi, I'm Ask INFA!
What would you like to know?
ASK INFAPreview
Please to access Ask INFA.

Table of Contents

Search

  1. Preface
  2. Introduction to SAP Table Connector
  3. Connections for SAP Table Connector
  4. Mappings and mapping tasks with SAP Table
  5. Synchronization tasks with SAP Table
  6. Data type reference
  7. FAQ for SAP Table Connector

SAP Table Connector

SAP Table Connector

Naming conventions of SAP ADSO objects

Naming conventions of SAP ADSO objects

When you import an ADSO object as a source in Data Integration mappings, it follows
/BIC/A<technical_name of ADSO>*
naming convention, 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!