Skip to Content
avatar image
Former Member

Having PA and Payroll in SAP without OM

Dear All,

What could be risk of having Core HR data keyed in from third party in SAP without OM in premise.What will be its impact on Payroll.

What is best way to implement it. Please let me know if any one has experience of doing it

Thanks & Regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jun 13, 2017 at 05:26 PM


    PY only needs PA to run.

    OM comes on top of PA but is not necessary.

    Last year I have taken off OM from an on-premise SAP system leaving it only left with PA and PY as part of a side-by-side cloud deployment.

    Impact was next to none but very few processes were based on OM or relying on OM data.

    The risk you might face should be toward OM based functionalities such as Workflow, ESS, MSS, etc...

    You might have to look further in your own customer development and make modification if necessary.



    Add comment
    10|10000 characters needed characters exceeded

    • By switching off integration between OM and PA (feature PLOGI); that was a good strategy for the client. However every situation are different.

      When switched off, IT0001 behaves in a different way, and integrated fields becomes available for input.

      Cost Center - the data becomes available for input so you can simply maintain it directly from IT0001.

      Org.Unit/Position/Function are also maintained directly in IT0001 from T528B (position) T527X (org.unit) and T513 (function).

      In my case I moved everyone to position 99999999 at the cut-off date as there was no need to maintain position in PA for payroll and shifted to maintain cost center.

      It's not really a side-by-side model but rather a HCM Core Hybrid model.

      For this strategy we could get loose of O-S-C objects and focus of PA data change integration and that has made a success as it was a lot more easier to handle. I really think client should put a lot of "good sense thinking" into the decision making of OM integration.

      There was few processes that would rely on some data from OM (for instance, a manager and the team) but this was resolved with a custom table in SAP and then an adaptation of the processes that resolves who's a manager and who's the team.

      If you have to maintain O-S-C object to make them available in SAP ERP HCM as part of your go-forward strategy, the first thing to understand is that there is only one place where the data can be maintained.

      If your cloud product is responsible for OM then changes to equivalent of O, S and C objects should only happen in said cloud product otherwise it would get just to messy. Imagine the nightmare two way stream :)

      So onces you made clear this, you can think of how to integrate T527x, T528b and T513 table with your cloud system, that would make it available to IT0001 for PA data maintenance (create operation is usually easy, but the other one maybe a little more complicated to integrate considering the link to IT0001).

      If you are part of the lucky one that have a lot of "core" processes based on OM that will remain in SAP ERP HCM it means you absolutely need that data in OM table; so for this you might push those integrated entries to OM with the RHINTE00 (but I am not sure, that would have to be checked - because if PLOGI is off then this one might behave differently... so if it does not work you probably would have too look at a custom report to integrated T527x, T528b and T513 to HRP1000 and HRP1001 and resolve maintenance issue by leveraging proper authority for each of your administrators profiles).

      Now this is where it becomes a little tricky in terms of integrating OM data from an external source; if your cloud software is EC part of the standard offering include an integration tool to replicate OM data in those PA based tables. Any who it will requiere some work :) Success!

      What is your cloud vendor if I may ask?