Connecting a second SAP client

We have one SAP client connected already. Now we want to connect the second one, the same process (O2C). In this other client we have a separate business division, which we want to analyze separately. Current already existing analyses shouldn’t be influenced by this new data load. We will probably also want to have some analyses to compare the business divisions, but we will definitely need to be able to easily create analyses separately.

Will appreciate any guidance a lot.

I will outline below my understanding and will appreciate comments to it.

I understand that first of all we need to create the new connection. And from this instruction we only need to perform steps 1 and 6, because the server part is already there and it is not SAP client specific.

Then, for the moment, since we have a data load running every night, I will add a filter on the case table (VBAP) to only take data from the first client (MANDT = ‘CLIENTNUMBER’). Because, if I understand correctly, otherwise with the next data load the data will be right away pulled from the new client and will mess up my current analyses.

And then the rest I will need to configure in the data jobs. For those cases where the tables and process steps are exactly the same I can re-use already existing ones. But if there will be some specialties that should be different for this new business division, I guess I will need to modify current data jobs with conditions depending on the client. Or even create some new data jobs. For example, if they have some process steps that are not relevant for the first business division.

Does this sound right? Or am I missing something important?

Thank you very much in advance for any input.

Regards
Masha

Hi Masha,

Your plans are very solid and well-thought-out, there is not much to add to that.

Just as a tip, when filtering on the case table (VBAP), make sure to add this filter also for the already existing model. Besides that, please let us know if something does not work as intended or if you encounter any problems.

Best regards,
Your Data Science Team

Hi Masha,

if I may add: The client is set on a connection basis.
Thus, your existing data jobs and extractions will not be affected by adding a new connection. The filtering for the client is always automatically done on the SAP-side. That also means, your data will not end up in the same data job if you’re pulling from two clients.

Furthermore, you will end up with two data jobs in the event collection, because one data job is always tied to exactly one connection (which represents one client). There’s two options:

  1. You can simply duplicate your existing data job, change the source connection and adapt the transformations that differ in the systems.

  2. You could also convert common queries into “templates” and use the same template for both data jobs. Thus, when you change the SQL-Code in the template, it gets applied for all data jobs that use it.

Finally you need to pull everything together into one data model:
You will need to either
a) combine the data in one table or
b) create a View that UNIONs the tables from client 1 and client 2 and then load this table into the datamodel instead of the sourcetables itself.

Hope that helps
Best Max