Note to SAP Community members: SAP recognizes the importance of the integrity of the SAP Community. In an effort to continue to support the community and at the same time adapt to this time of uncertainty, we are creating a temporary space for partne...
The SAP Customer Influence program, I believe, is a wonderful platform and an excellent way for SAP to understand what customers need and want in their product road maps. Customer Influence is used for various products within SAP, split down to a mod...
Hi there,
We only use an external number range for employee numbers in ERP. I have set up replication which works for updating employees in EC which already exist in ERP. However, when hiring a new employee, I get the error "Personnel number 000000...
Hi there,
I am setting up data replication from SF EC to SAP ERP. I now have basic replication working (or at least in principle).
After making a change to employee 1234's name in EC, I trigger the replication query from ERP with transaction ...
Hi there,
I am trying to set up replication between EC and SAP HCM. When testing the replication with the query tool for a single employee, I am getting the following error:
055(ECPAO_IN_PROCESSING) An exception with the type CX_HRPA_INVA...
Check out this article that explains how to do it: https://blogs.sap.com/2019/07/03/birthday-and-anniversary-alerts-to-the-employees-in-successfactors/I know the answer is very late, but I'm answering in case there is anyone else looking for a soluti...
Hi Ilyas,Here is the documentation I recorded at the time about the problem...ErrorAn exception with the type CX_HRPA_INVALID_FEATURE was
raised, but was not handled locally or declared in a RAISING clause.CauseValue mappings may be incorrect, a pick...
I suggest you start a new question with more details of the problem you are experiencing - include some context and info so that we have a better idea of how to answer you
It turns out that the error was caused by the fact that I had omitted to map the event reason/action reason for info-type 0000. The BAdi implementation was not the reason for the error.
