Run 2 CCO Monitors with 2 CustomerCheckout schemas/tenants on the same database

[StelianD]

Dear Community,

we are running a partner hosted SAP Business One Cloud with SAP Business One 9.3 version for SAP HANA on a HANA database 1.0

Here we have customers that are using the CCO and as a result also the CCO Monitor and so on. We are now facing issues regarding the update/movement of the customers to a new infrastructure because we need to move all at once because of the CustomerCheckout schema/tenant and it is not optimal in this case.

In order to optimize the movement on a new infrastructure we thought that maybe we can split the customers so that every one of them gets his own CustomerCheckout schema/tenant and CCO Monitor and so on.

So for example:

• customer 1 - integration framework 1 - CustomerCheckout schema 1
• customer 2 - integration framework 2 - CustomerCheckout schema 2
• etc...

But I then saw that during the integration framework scenario activation I cannot choose a schema to connect to and that the scenario is connecting to the standard CustomerCheckout schema.

My question is, is it possible to create this kind of setup? Is there any way to direct the integration framework scenario to another database other than the standard? For example to CustomerCheckout1?

Thank you and best Regards

Stelian

[JoergAldinger]

Hello Stelian,

I don't think you can, since it's retrieving the DB name from the SLD and that SLD entry ID is pretty sure to be hard-coded in the scenarios.

We do have the same issue, and for that reason when upgrading we always need to make sure that no invoices are pending in the monitor (or if there are, they are resent after upgrade), which makes it everything more complicated because you need to be extra careful.

Another issue is that the Company ID in B1i SLD is likely to change with the upgrade, which means you also need to reconfigure all CCO terminals with the new B1 system ID.

One potential solution might be to create a SQL script that goes through all the tables in the old CustomerCheckoutDB database and copies over all records from one system ID to the new database and then removes them from the old database, but that would have to be well-written to run reliably.

Let me know your thoughts, I agree this process should be easier. I really hope that integration with B1 can be moved away from CCO to CCOM and from B1IF to ServiceLayer in the future.

Best regards,

Joerg.

[StelianD]

Hello Joerg,

thank you for the fast reply.

I am dissapointed. I hopped that there is a way to overwrite the standard settings and this way enable the possibilty of using more CustomerCheckout schemas on the same system...

I completly forgott about invoices pending in the monitor, I was to concentrated on finding a workaround, but you are right.

I was aware of the changed that will happen regarding the Company ID, but I was not aware of it being so complicated. I know that on normal system (1 customer runs his own system) you need to change the Company ID on the CCO in the settings but that is it...

The update is getting a lot more fun now...

Are you also running a SAP Business One partner hosted cloud? If yes, is it on HANA or MSSQL?

Best Regards

Stelian

[JoergAldinger]

Hello Stelian,

Yes, we are also running Partner hosted Cloud for B1. We have service units in both SQL and HANA, but currently only have CCO in HANA-based service units.

Best regards,

Joerg.