Communicating System Tables

For Aurea CRM to work correctly on all stations, info areas containing configuration settings need to be communicated.

Apply the following settings to your communication formats:

• Key: Enable the Output and Input cells to ensure that serial numbers are assigned correctly, see Key Info Area.
• Language: Output the Language info area to all branch offices to ensure that all languages are available on all stations, see Multi-Language Catalogs in the CRM.core Administrator Guide. Deny access to the Language info area on branch offices in the Rights module, see Defining Rights at the Info Area Level in the CRM.core Administrator Guide.
• Text: Enable the Output and Input cells. Texts can be added and translated on branch offices, see Text in the CRM.core Administrator Guide.
• Tenant and Additional Tenant: Enable the Output and Input cells if you are working with tenants, see Tenants in the CRM.core Administrator Guide.
• Configuration: Always communicate the Configuration info area to branch offices, see Configuration Info Area in the CRM.core Administrator Guide.
• Exchange Rate Table: Enable the Output and Input cells if you work with multiple currencies, see Working with Several Currencies in the vertical-specific manuals.
• Station and dependent info areas/Station Configuration: Enable the Output and Input cells for the Station info area and child info areas, as well as for the Station Configuration info area. If your communication setup includes multiple tiers, communicate the main office's Station and Station Configuration to all branch offices, otherwise you are prompted to register your license, see Aurea CRM License in the CRM.core Administrator Guide.
• Rep and dependent info areas: Enable the Output and Input cells for the Rep info area and its child info areas. Use the Central Login Configuration info area to define logins for users at branch offices, see Central Login Configuration in the CRM.core Administrator Guide.

  To communicate logins, include the corresponding records in both the Central Login Configuration (ES) and Rep (ID) info areas in your communication format. The data in the Central Login Configuration (ES) info area is transferred to the Login (US) info area on the target station, and the corresponding users' directories are added.

  The Login (US) info area itself is not communicated.

• User Tracking: Input the User Tracking info area from all branch offices, see User Tracking in the CRM.core Administrator Guide.
• Country and City: Enable the Output and Input cells. These info areas are also updated when adding new companies on branch offices, see Country Info Area and City Info Area in the CRM.core Administrator Guide.
• Relationship Level: Enable the Send and Receive cells if reciprocal relationships should be added automatically, see Relationships in the User Manual.
• Format: The Format info area contains a significant portion of Aurea CRM's configuration options (access rights, masks, triggers etc.), see Formats in the User Manual. Always output the Format info area to all branch offices.
  Note: Save conditions and transfer formats as global formats so that users at branch offices can also use them, see Global Formats in the User Manual. The data model is always communicated to branch offices if it is changed (irrespective of your communication settings), see Communicating Data Model Changes in the CRM.core Administrator Guide.

  If you want to communicate specific formats to specific branch offices, use the Distrib . code fields in the Format info area to further restrict the communication of certain format types (e.g. conditions).

• History: Input the History info area on all branch offices, see History in the CRM.core Administrator Guide.
  Note: The Catalog Maintenance and Catalog info areas are always communicated. They are not available in the C.Format info area, see Communicating Catalogs.
• CRM Process: Enable the Input and Output cells for the CRM Process info area to ensure the system-wide CRM process configuration functions correctly on all stations, see CRM Process Configuration in the CRM.core Administrator Guide.
• Stock, Stock Control etc.: If you are using the stock-related info areas, you need to communicate all info areas containing stock-relevant data, see Inventory Management in the Business Logic Manuals.

  The Stock History (BTB only) info area is not communicated; it is used to record changes to local stocks.

• WWW Interest (II), WWW Interest Configuration (I9): Enable the Input and Output cells for these info areas to ensure that user-specific settings of <offline> users are correctly synchronized between online and offline mode, see web <offline> Installation & Technical Guide.