on 01-13-2009 9:23 PM
Classic scenario:
SRM EBP ERP
1) Shopping cart created
2) Shooping cart workflow approved
i) Pur req
3) Sends PO Copy to SRM EBP ii)PO
4) Sends GR Copy to SRM EBP iv) Goods Receipt
5) Sends Invoice Copy to SRM EBP v) Invoice
Extended classic scenario
SRM EBP ERP
1) Shopping cart created
2) Shooping cart workflow approved
3) PO Created I) Sends PO copy to ERP
4) Sends GR Copy to SRM EBP ii) Goods Receipt
5) Sends Invoice Copy to SRM EBP iii) Invoice
Qusetions
1) Is this above flow is correct
2) In classic scenarios
i) What steps to be followed in ECC to SRM, to send PO to SRM
Goods Receipt and Invoice can create in SRM side and send copy to backend
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
The PO creation is an important distinguisher.
In Classic - The PO is directly created in ECC and no PO document is created in SRM. So its not that a copy is created in and system but document will exist only in ECC. There is only document reference in SRM.
In Ext Classic - PO document is first created in SRM and you can process the document before ordering. Here a copy (Non Editable) is created in ECC.
Regards
Hussain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Classic and Extended classic main difference is PO handling. Your understanding almost correct.
GR and Invoice can be created SRM or ERP.
When GR or Invoice is created ERP side, it update status in SRM side. (It is not document copy)
There is no business scenario for PO copy from ERP to SRM.
Regards,
Masa
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.