Initial Download : Overview/Customizing : Downloading Filter/Business Object in CRM Online/Initial Load/Monitoring Initial Load

Initial Download : Overview

 

Customizing : Downloading Filter

 

•  The transactions to specify the filter criteria for the various business objects is found under: Middleware -> R/3 Adapter -> Initial Download -> Object Management (2.0B) or Middleware -> R/3 Data Exchange -> Initial Download -> Object Management (2.0C)
•   General filter settings concern all download objects.
•   Business object specific filter criteria have higher priority than general filters. It is possible to define an object specific filter even if a general one already exists.
•   Filter settings are stored in table SMOFFILTAB and refer to table fields.
•   Filters for the initial download are also used for the delta download.
• In  order to prevent inconsistencies between OLTP R/3 data and the CDB, predefined filters are only available for data fields that are unlikely to change on the OLTP R/3 system.
•   When changing filter conditions for customizing data, a synchronization download is required.

Business Object in CRM Online

 

Initial Load

 

The  transaction to start the Initial Download can be found at: Middleware -> R/3 Adapter -> Initial Download -> Start (2.0B) or Middleware -> R/3 Data Exchange -> Initial Download -> Start (2.0C).

  The Mobile Sales/Service business objects are stored in the table SMOFOBJECT in the CDB.

  Tables associated to each object are found in the table SMOFTABLES.

  The dependencies of download objects are stored in the table SMOFOBJPAR (some business objects must be downloaded before other business objects can, e.g. conditions for materials can only be downloaded if the materials are already downloaded).

Monitoring Initial Load

 

•  The location of the transaction to monitor the Initial Download is: Middleware -> R/3 Adapter -> Initial Download -> Monitor Download (2.0B). or Middleware -> R/3 Data Exchange -> Initial Download -> Monitor Download (2.0C).
•   Object dependencies are kept in table SMOFOBJPAR and are used to control the download order of dependent download objects during an initial download.
•   For further information on monitoring, see unit Monitoring & Error Handling.
•   If the initial download finishes unsuccessfully, consult SAP note 309734 for an general error analysis.