Customer data with locations
The customer master 2.0 is based conceptually on the use with locations. If a location is part of a central customer number and has the customer master 2.0, it automatically uses the same customer master of all other locations.
Taking customer data with you
If a location wants to "leave" a central network, a new customer number outside the central network must be created for this customer. He does not take any customer data with him here and starts with an empty customer base. Using the export and import function, the customer can transfer the previous customer data to the new customer number. Of course, this must be done within the framework of data protection and conditions agreed with the customers.
No own customer base in the central network
The use of an "own" customer base 2.0 is not possible within a central association.
Exception: A location can still work "offline", so to speak, with the discontinued customer master 1.0 at the location.
If a single location uses the offline customer base, no reports with customer data can be run for this location in the head office. These reports must then always be created at the location itself.
A conversion of a location from customer master 2.0 to the local customer master 1.0 "Offline" can currently only be carried out as a service via support (with developer support).
Old customer base 1.0 for locations (discontinued)
The customer base 1.0 can be synchronised between the head office and the branch with the web clearing. Accounting can also be used in the head office for the settlement of customer transactions. However, the use is subject to different conditions.
To edit the respective data, you must switch to the corresponding client in the head office.
An increase of the functional scope as well as the lifting of the restrictions is planned for the future.
Permissions...
By setting permissions in the MCP, you also control access in the locations.
Reconciliation of customer data...
- The first time you start MOBILE PEOPLE from a customer base in a store, the program asks for a store number. This should normally be the client number of the store. However, if several stores want to use the same customer master, you can simply use the same store number. It is important that each branch has a unique client number for the Hypersoft Suite.
- The customer number can be entered in a separate number range in each store. However, the client number is used to differentiate between the customers. If the same client numbers were used in different branches, customer data with the same name would be overwritten in the head office.
- Changes to customer data can be made both in the store and in the head office. However, this must be determined with a procedure, since changes cannot be processed on both sides within a comparison cycle. If you were to change the data of a customer both in the store and in the head office, the changes from the store would overwrite those in the head office. The same applies to the creation of new customer data (with the same customer number) within a comparison cycle.
Further documentation:
Location management in practice
Back to the parent page: Location functions of the programs