Transaction R3AC1 to manage Business Adapter Objects

• Initial Flow Contexts TAB you find the supported Source and Target site types and the Flow Context
• In Tables/Structures within Object TAB you find the names of the R/3 tables used by the extractor

Filtering Settings TAB – setting filtering in the CRM system and applying it in R/3, CRM or Both systems

• Purpose:
  • Reduce data volumes
  • Keep R/3 specific data in the backend
• Filtering is part of the customizing of the system

Mapping Modules: R/3 to CRM TAB: Function Module that converts the BAPIMTCS data into a messaging BDoc

Inbound & Outbound Queues for Business Adapter Objects

• Data transport between R/3 and CRM is based on qRFC technology
• Naming convention for qRFC queues:
  • R3AI_<Business Adapter Object> where: R3A = R/3 Adapter, I = Initial Load
• The Specific Extractor selects the data from the DB tables associated with the Business Adapter Object and triggers the data transfer per qRFC
• Name of the Specific Extractor in table CRMSUBTAB in R/3

R/3 Inbound Adapter