Skip to Content

Using S4 Cloud Business Content for SAC with S4 On premise views

Hi,

There some standard content for SAC specific to S4HANA Cloud like

Manufacturing for SAP S/4HANA Cloud. These are live connection based models.

I have a few questions:

1. I wanted to understand if these models can be linked to S4 on premise CDS views as well.

2. If the answer to #1 is No, what are the options for On-premise clients?

3. If the answer to #1 is Yes, how do I figure out the standard CDS view it should link to?

Regards,

Shyam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    May 15 at 10:20 AM

    Hi,

    If you go to the Help pages for the Business Content : https://help.sap.com/doc/00f68c2e08b941f081002fd3691d86a7/release/en-US/078868f57f3346a98c3233207bd211c7.html you'll see a link on that page to a PDF (see the SAP Analytics Cloud Content Documentation )

    in that PDF document, you'll see - as you correctly suspected - that all the samples shipped are based on S/4HANA Cloud.

    I haven't tried "repointing" these Cloud samples to an on-premise S/4 source. I'm not sure it'll be possible, as these models expect Cloud to Cloud connections, not a Path or Proxy connection. Rolf Sieberg may be able to comment.

    so, at best, i suspect you'll be able to use the samples (and associated documentation) to understand the CDS Analytical Queries that are being used in the S/4 scenario, for example Financial Planning.

    Thanks to the documentation, You'll also get an idea of the calculated measures that are done in SAC (modeller) - for example General Ledger, metric: COGS = Material Expenses + Personnel Expenses + Interest & Similar Expenses

    You could then design you Stories/Dashboards to be similarly to the samples, if that's the look you're going for.

    Kind regards,

    H


    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      on the one hand, i imagine it's to do with time and effort , and aligning that with our strategic priorities (i.e. cloud first)

      and I can well imagine that part of the rationale is that cloud customers won't be customising , whereas on-premise most likely will - so the potential for shipping something that won't work 'out of the box' is much higher... hence the decision.

      Just my 2 cents.

      Regards, H