Skip to Content
0
Dec 05, 2011 at 12:25 PM

In the Extended Classic scenario, what creates the PO on the SRM side?

26 Views

Hi Experts,

This sounds like a simple question, however, I've been unable to find the answer.

What I am looking for is the process (report, workflow or function module etc etc) that actually creates the PO on the SRM side once the shopping cart has been approved (before it is replicated to ECC).

The reason for this is, after a support stack upgrade, the creation of the PO seems to have slowed down once the shopping cart has been created. I'm trying to track down where the PO gets created and what triggers that to happen, in order to work out why it isn't as quick as it was prior to the upgrade, but can't piece together the full end to end process.

I can see the "Workflow Without Approval Shopping Cart" workflow that obviously Releases the shopping cart and sets the status to Approved... I can then see the equivalent workflow for the PO (Workflow Without Approval for PurchOrder), but I can't work out the bit inbetween -

- How does the PO actually gets created in SRM and what triggers that to happen?

Any help will be gratefully received - thanks in advance.