CRM and CX Blogs by SAP
Stay up-to-date on the latest developments and product news about intelligent customer experience and CRM technologies through blog posts from SAP experts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member


I have summarized some useful tables which is used often for SAP CRM middleware, including middleware general parameter related tables, adapter object related tables, filter related tables, queue name related tables, Bdoc flow and Bdoc message related tables, load status tables and RFC related tables etc.

 

Useful tables for CRM Middleware


 

Middleware general parameter related tables:


 



































Table name System Description
SMOFPARSFA CRM General middleware parameters
SMOF_ERPSH CRM ERP-Site Header table
CRMPAROLTP ERP CRM OLTP Parameters
CRMCONSUM ERP CRM consumer
CRMRFCPAR ERP Definitions for RFC Connections

 

Adapter Object related tables:


 























































Table name System Description
SMOFTABLES CRM Finding the Adapter Object Involved
SMOFOBJECT CRM Download Objects
SMOFINICON CRM Flow Contexts in Initial Download depending on Site Types
CRMOBJECT ERP Download Objects
CRMSUBTAB ERP Generic Extractor for Objects
CRMATAB ERP Tables Permitted for Customizing Download
CRMOBJTAB ERP Tables Belonging to One Object
CRMMAPTAB ERP Relationship Between Table Names in CRMOBJTAB and BAPIMTCS
CRMINTBAP ERP Assignment of Internal and External Table Fields

 

 

Filter related tables:


 

























Table name System Description
SMOFFILFLD CRM The predefined fields for filter
SMOFFILTAB CRM Filter settings
CRMFILTAB ERP Filter settings

 

 

Queue Name tables:


 




















Table name System Description
SMOFQFIND CRM Queue Name setting
CRMQNAMES ERP Queue Name setting

 

 

Bdoc Type Flow related tables:


 






























Table name System Description
SMW3BDOCIF CRM BDoc Type Specific Flow Attributes (Validation service)
SMW3FDSTD CRM Flow: Standard Configuration
SMW3FDBDOC CRM BDoc Type Specific Flow
SMW3FDCUST CRM Customer-Specific Flow

 

 

Bdoc message related tables:


 























































Table name System Description
SMW3_BDOC CRM BDoc Message Store: Header
SMW3_BDOC1 CRM BDoc Message Store: Message Body (classic  part)
SMW3_BDOC2 CRM BDoc Message Store: Message Body (extension part)
SMW3_BDOC4 CRM BDoc: Validation Errors
SMW3_BDOC5 CRM BDoc: Receivers with state
SMW3_BDOC6 CRM BDoc: Receiver specific error segments
SMW3_BDOC7 CRM BDoc: Receiver Root IDs
SMW3_BDOCQ CRM qRFC Queues in use by BDoc Message
TSMW3_STAT CRM Attributes of Bdoc Processing States

 

Load status related tables:


 

























Table name System Description
SMOFDSTAT CRM Initial load monitoring - Current Download Status of Objects
SMOFRSTAT CRM Request load monitoring - Current Download Status of Objects
SDIMASTAT CRM Dima load monitoring - Current Download Status of Objects

 

 

RFC related tables:


 








































Table name System Description
ARFCSSTATE CRM,ERP Description of ARFC Call Status (Send)
ARFCSDATA CRM,ERP ARFC Call Data (Callers)
TRFCQSTATE CRM,ERP Description of qRFC Call Conditions (Inbound Queue)
TRFCQDATA CRM,ERP qRFC Call Data (Inbound Queue)
TRFCQOUT CRM,ERP tRFC Queue Description (Outbound Queue)
TRFCQIN CRM,ERP tRFC Queue Description (Inbound Queue)


DIMA related tables:


 








































Table name System Description
SDIMABASIC CRM Basic Information for DIMA
SDIMAHEAD CRM Header Data of Dima
SDIMASTAT CRM Dima load monitoring - Current Download Status of Objects
SDIMAMESS CRM Messages for DIMA
SDIMADET CRM DIMA Filter conditions
SDIMAFILT CRM Allowed Filters for DIMA

 


Logical system during exchange:


 

 

























Table name System Description
CRMPRLS ERP ERP Logical System for Download
CRMMLSGUID CRM ERP Logical System (should has same value as ERP CRMPRLS)
TBDLS(T) ERP, CRM Logical system defination

 

I will try to add more in the future.

Hope this helps.

3 Comments