 (2).jpg)
7 months ago
27
Many contingent workers person aggregate Purchasing Rates (e.g. Specific complaint connected Internal Projects and higher complaint connected Customer Project). With that anticipation we request much than 1 PO enactment for the contingent worker.
We acquisition connected Cost Center for contingent workers moving connected an inter-company project. We make the PO connected Cost Center, delegate a outgo complaint and an ICO complaint to the unit fig successful the app “Manage Cost Rates – Services” and the strategy generates the inter-company invoicing. The contingent idiosyncratic volition past invoice the institution wherever the PO and declaration sit.
In that case, lone 1 PO enactment needs to beryllium valid for the contingent worker, different it volition multiply the fig of tasks successful timesheet app by the fig of PO enactment active. It besides multiplies the enactment if a PO connected task besides exist, but the strategy does not forestall clip posting. It’s precise not convenient for the contingent idiosyncratic and make a batch of attraction and enactment connected the backmost extremity with creating issues successful replication of clip coming from the outer timesheet system.
Due to the strategy behaviour of duplicating clip entries, it creates incorrect postings successful GRIR accounts, creates reconciliation efforts, creates disorder for the contingent workers that request to nonstop his timesheet, truthful much enactment connected the backmost end, and we request to forestall this.
The adoption of this power petition would let america to astatine slightest person a workaround for this issue, due to the fact that Purchasing connected Cost Center is besides required.
https://influence.sap.com/sap/ino/#/idea/299853
already referred the beneath blog
------------------------------------------------------------------------------------------------------------------------------------------------
Learn much astir the SAP Support idiosyncratic and programme here.
