Is it possible to switch a production SRM 5.0/ECC system from an "extended classic" scenario to a "classic" scenario? If so, what are the issues? The client believes this will eliminate the rework caused by PO replication errors and that SAP's "extended classic" scenario is not mature.
Requires Free Membership to View
When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.
Hannah Smalltree, Editorial Director
I'm not sure if I understand your business reasoning for the cancellation of the R/3 Invoice. As you are aware in either classic or extended classic, an Invoice can be created in SRM, and as a standard solution design, an IDoc is generated in SRM for the Invoice and transferred to R/3 for posting. Please remember, until the backend invoice is posted no financial postings are done. In SRM an invoice is merely an entry point, only once this invoice IDoc is successfully posted in R/3 the corresponding vendor debit/credits etc are posted in SAP Financials.
Therefore I'm still not sure what the business reasoning is to cancel the R/3 invoice. If anything you would want to cancel the Invoice in SAP SRM and that would transfer the change to the R/3 Invoice for cancellation.
This was first published in May 2008