| # Table sharing Generally, the functional requirements determine which tables must be shared. For table sharing, performance-related considerations are less relevant. Table sharing can result in larger tables. Larger tables can occur especially if records from a particular table are not used in all companies, or if you share dynamic data. Larger tables can decrease performance. Furthermore, table sharing can lead to more locking problems, because more users update the same data. However, in practice these problems do not regularly occur. If problems occur it will probably concern dynamic data, such as in the Financials package related to integration transactions or central purchase invoice matching. If these performance problems occur, the best solution is to regularly archive and delete data from these tables; generally, this should work. If this is not a sufficient solution, use one of the following methods: Replication. Keep the tables in sync manually. Disable the required functionality. Note For more information, refer to the following documents: User's Guide for Archiving (U9352* US). User's Guide for Multicompany Table Sharing (U9505* US). |