Skip to Content
author's profile photo Former Member
Former Member

Extended Classic Scenario - how does the integration work ?

Hi,

Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?

Many thanks,

fiona

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2005 at 01:07 PM

    Hi Fiona,

    In the extended classic scenario, you can transfer Purch. Requisitions from R/3 to your SRM via qRFCs, do the sourcing in SRM, create a local SRM PO and transfer this purchase order to your R/3 with an RFC - BAPI call. (for example the BAPI_PO_CREATE1) Technically there is a so called Plug-in in your backend where the mapping from the SRM-PO to the BAPI structures is done. After this, the BAPI is called in the R/3.

    In the extended classic scenario, the SRM is the leading system. So in the R/3 you will only have a copy of the PO which can not be changed.

    Best regards,

    Olaf

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Fiona,

      Concerning GR & Invoices, the updates are sent to R/3 through ALE/IDOC.

      Concerning Materials, you can incorporate MAterial numbers in the catalog, without replication locally the materials (If you use CCM 2.0, a product catalog can be directly from MM Material master, to enrich Supplier data).

      To avoid local material check, in the catalog link customizing point put the corresponding flag, and fill in a logical system (do not put the local system, or the SRM will continue to check local Material master).

      Best regards.

      Vadim

  • author's profile photo Former Member
    Former Member
    Posted on Nov 22, 2005 at 12:18 PM

    Hi,

    The process in the extended classic scenario is:

    1-SC created locally

    2-SC Workflow approval

    3-Local PO creation (if the PO is incomplete, it has to be completed manually by a purchaser user)

    4-PO edition (print, mail, XML and/or fax)

    5-PO transfer in R/3 (BAPI RFC Call) (the created PO cannot be modified in R/3)

    For GR and invoices, they may be created in SRM, then they are transfered through ALE in R/3.

    You've got BADIs in the system for all these documents creations, check,...

    Regards.

    Vadim

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.