BFC V10 database merge

[Former Member]

Hello,

We have actually 4 databases recently migrated to BFC V10 :

• 2 parametrization databases :
  • 1 Core database with core Group parametrization
  • 1 Specific database with specific business parametrization
• 2 production/reporting databases :
  • 1 Core Group database
  • 1 Specific database with business specific reporting

Following company reorganisation, we are thinking about "merging" the two param databases into a single one (Core would be transfered to specific) and the two production databases into one (Core -> specific), that in order to optimize functional administration and ease reporting on a single database.

I know that a new feature of FC V10 is to allow modifying objects that have not been designed in the current database ; solution that could ease this project.

Do you think it's a complex or risky project ?

Many thanks in advance for your help.

[olivier_gentile]

Hello Patrick,

The new V10 option called "Signatures consumed for identifier range" in the Profile range tab of the "Site Profiles" module really eases this kind of project.

In the previous versions only a single signature could be allocated to a given site. Therefore only objects created on this site were editable on this same site. Indeed objects' identifiers were built on the site signature (signature number * 52488 + incremental counter)  thus allowing the site to recognize that it had full control on them.

Now SAP FC authorizes to allocate several signatures to a given site. This allows the site to gain full control over objects that where not originally created on it. The only requirement is that the signature contained in the objects identifiers must be part of the signatures listed in the "Signatures consumed for identifier range" option.

In your project your objective will be to keep the specific parametrization dababase which contains probably both group and specific customization, and add the group parametrization database signature in the "Signatures consumed for identifier range" option. This will be your new merged parametrization database allowing full control over objects created on both original parametrization databases.

For production databases you will more likely keep you group database as the new merged database, as the group reportings are probably not complete in the specific production database. Then you will have to transfer the specific production database reportings in the new merged database (after receiving the specific parametrization from the new merged parametrization database). Finally, you will have to add the specific production database signature in the "Signatures consumed for identifier range" option to gain full control over production objects created on specific production database.

In my opinion, with this feature, your project is neither complex nor risky.

Regards,

Olivier Gentile