Replicating Customer-Specific Condition Objects to Mobile Client 

Use

Certain condition tables that are used in standard condition types (for example, A304 in PR00) and customer-specific R/3 condition tables, in general, are not loaded from the CRM server to the CDB automatically.

In the following section, the steps that have to be performed to load A-tables are described. Condition table A040 serves as an example and can be replaced by any other A-table.

·        Checking Entries in the Mobile Bridge

·        Generating Objects for Data Transfer

·        Creating SAP R/3 Adapter Objects

·        Generating Table Script

·        Generating the Metadata on the Mobile Client

·        Creating the Replication Object

·        Creating a Publication

·        Updating the Mobile Client

·        Creating Subscriptions to Customer-Specific Condition Objects