Why extended Classic is implemented

Hi Everybody,
I was working in SAP SRM for past 3 years and only Support Experience. Yesterday attended an interview and he asked me why your client has implemented Extended Classic why not Classic Scenario?
I know it depends to client-to-client.
Can any one let me know the list of points need to be discussed to support this question. My answer was not impressive.
Sree

Hi Sree,
You are right here it depends on the client whether to configure the system for extended classic and classic scenario.
The extended classic scenario suits customer who wants to
their purchasing department to save time and money by using the streamlined purchasing functionality of SAP SRM
use the full sourcing capabilities offered by SAP SRM, yet who also want to be able to confirm and invoice direct materials
the flexibility of being able to pre-enter confirmations and invoices
Where the classic scenario suits the customer who wants:
wide user group, for example employees not necessarily working in the purchasing department, to be able to enter their requirements quickly and easily. SAP SRM’s functionality and ease of navigation allow this, as it requires only minimal training
their purchasing department to operate solely with the functionality offered by the backend system(s)
For whom a transfer of purchasing activities to SAP SRM is not viable in SAP SRM
You can use both the classic and extended classic capabilities by configuring the product categories
Please let me know if the above answer is helpful.
Best Regards,
Ankit Jain

Similar Messages

  • Why Extended Classic Scenario

    Hello
    I understand the difference between Extended Classic and Classic Scenario with the follow on document creation. But, I need to understand the business benifits of implementing Extended Classic Scenario as opposed to Classic Scenario in SRM. In what business scenario do one suggest Extended Classic.
    Appreciate every answer
    Thanks
    Vijay

    Hi Vijay,
    The most important thing to consider when choosing the implementation scenario is to consider which system will support the different steps of the procurement process.
    In case of the classic scenario, after creation of the request (shopping cart) in SRM, the remaining process steps will be handled / supported  in the back-end system (ECC). Goods receipt can be executed in both systems.  This would be a good choice if the organization has already an operational back-end system and the users from the purchasing department are already familiar (and happy) with all the MM functionality.  SRM will only function as a support tool for administrating the purchasing needs of the end-users in the organization.
    In case of the extended-classic implementation scenario the complete purchasing process will be supported in the SRM system (most organizations prefer to use the back-end system for invoice verification). Thus requesters, purchasers, goods recipients etc. all will use the SRM system to support their respective activities.  This would be the preferred scenario in case both MM (ECC) and SRM are new to the organisation and will be implemented together.
    SRM offers the different users a nicer user interface as opposed to the R/3 screens. Also the (strategic) sourcing capabilities of SRM can only be used  when implementing the extended classic scenario. Same for the Suplier Enablement business scenariou2019s. Most are only supported when extended classic is active.
    So depending on the intentions of the organization a choice can be made. SRM only as a tool for administrating the decentralized request from the end users in the organization: Classic scenario will suffice. SRM as a tool to support the complete purchasing process, from sourcing till  evaluation - Extended classic will be the correct choice.
    Regards,
    Skander

  • Why extends HashMap and implements Map?

    Hi,
    I browsed the source of HashMap in JDK 5.0.
    The declaration of the class puzzled me.
    Declaration of HashMap:public class HashMap<K,V>
        extends AbstractMap<K,V>
        implements Map<K,V>, Cloneable, SerializableDeclaration of AbstractMap:public abstract class AbstractMap<K,V> implements Map<K,V>Puzzle:
    Now that AbstractMap has been declared to implement Map interface, and HashMap extends AbstractMap,
    why HashMap is declared to implement Map interface again?
    I don't think that's necessary.
    a cup of Java, cheers!
    Sha Jiang

    I don't think it makes any difference that this code is part of the standard libraryAbsolutely, I agree on the view.
    I think it was declared as such for clarity only.I just be curious with the little topic.
    "clarity" may be the answer.
    Thanks!

  • Direct procurement always as extended classic -- why ?

    Hi ,
    As per SAP's specification , ' SRM Server is the leading server for direct procurement. This means the system behaves according to extended classic scenario' .
    Is there any specific reason on why the scenario would always be extended classic for direct procurement ?
    And does this also imply that in a classic scenario, if a SC is created for a direct material which refers to backend material , the PO created would be in accord with the extended classic scenario ?
    Reasons/Answers --- Anyone ?
    thanks-
    Harmeet.

    Hi Harmeet
    Yes, even in classic scenario, if a SC is created for a direct material which refers to backend material , the PO created will be in accordance with the extended classic scenario by default i.e. a local SRM PO would be created which will be replicated to ECC. However you can alter this behaviour and force the system to create a PO in ECC (like classic scenario) by implementing BADIs.
    Regards,
    Nikhil

  • Classic and Extended Classic implementation

    Hi all,
    Can Self service procurement scenario be implemented in classic as well as extended mode?What are the differences in configuration in SPRO?

    Hi,
    There is no much differences in terms of configuration in SRM system.
    for extended classic scenarion  SPRO-> SRM server-> cross applications basic setting -> activate extended classic scenario
    This setting determines EBP system generates local purchase orders.
    If you are implementing Ext classic scenario no need to define the step  cross applicatoins -> Define objects in backend system
    Using badi  BBP_EXTLOCALPO_BADI you can override the setting in extended classic scenario, example: for certain product category using BADI we can create PO in back end system also ( classic scenario ).
    Thanks & Regards,
    Prasad.s

  • Implement Limit PO functionality in extended classic

    Hello Geeks,
    I have an issue while trying to implement the Limit PO functionality in SRM 5.0  this extended classic scenarion, initially this functionality was supperessed using BADI, but now it was invoked.
    I could now successfully create Limit SHC and PO is generated in SRM, but while transferring of the PO to backend it gives me an error message.
    I have not done any addtional settings either in SAP R/3 or SRM to implement this new Limit PO funtionality. Just only I have activated thru the BADI which has been suppressed.
    But I get an error message when the PO is created and I can see the RZ20 error message as
    "Combination of GR/IR control not allowed for external services"
    However I have not mainatined the GR/IR in the vendor master record either in R/3 or SRM, but still I get the same message.
    Please suggest me how to avoid this error message and post successfully the PO in R/3
    Thanks
    Regards
    Srujan

    Hello Srujan,
    There can be several causes for this issue, but only analysing and debugging we could provide a solution.
    You have to create a test data for BAPI_PO_CREATE1 and analyse it in your ERP system.
    One recurring issue is the following: the structures POITEM and POITEMX may not be aligned regarding fields GR_NON_VAL and GR_BASEDIV.
    If POITEM contains values in any field then an 'X' should also be present in that corresponding field at POITEMX. If they are not aligned, this error can be raised. To fix it,  use the BADI BP_PO_INBOUND -> Method MAP_BEFORE_BAPI in R/3 side and set the "POITEMX" values to 'X' only when those flags
    are set to 'X'
    Regards,
    Thiago Salvador

  • Has anybody implemented SUS in SRM 5 - Extended classic - pls help

    Hi There,
    I would like to hear from anybody who has implemented SUS in SRM 5 - Extended Classic.
    A client of mine is considering implementing SUS - SRM 5. I cannot find any SAP SUS related docuemntation for the Extended Classic scenario.
    Do you have any helpful imformation i.e setup,config and tips that you can share with me.
    Many thanks for your help in advance.
    Thanks,
    Sheena

    Hi Sheena,
    Please have a look at the link:
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/srm/business+scenarios
    Here you will find usefull information, like:
    https://service.sap.com/~sapidb/011000358700002897382004E/Plan-DrivenwithSInew.pdf
    Regards,
    Peter

  • No GR on Confirmation Approval in Extended Classic Scenario

    Hi all gurus out there,
    We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
    We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
    Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
    Cheers!
    Siow Fong

    Hi Guys,
    I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
    Regards
    Siow Fong

  • PO approval process in ECC for extended classic scenario

    Hi All,
    At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.  
    So our requirement is :
    User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
    Thanks in advance.
    Regards,
    Jennifer
    Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

    Hi Jennifer,
    Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

  • URGENT: CLASSIC & EXTENDED CLASSIC

    hi gurus,
                can anyone tell me the difference between classic and extended classic scenarious in SRM? when will we use them for client requirement?
    what is the difference between R/3 enterprise structure and SRM organizational plan?
    what is meant by SAP SCM?
    if i  implement the extended classic then willl it possible in classic?how and why
    what r the followon documents will support for each scenarious?please be detail.
    what is the transactioncode for VENDORMAPPING?
    CCM,SUS,SOURCING,SSP,PDP,SERVICEPROCUREMENT are depending on which scenarios i.e classic or extended classic for each business scenarious?
    please send solutions immediatly to my id <i>[email protected]</i>
    warm regards
    rakhi

    Let me see if I can satisfy you :
    - The major difference between classic and Ex. classic is the system where the leading PO is created. In classic it's r/3 while in ECS it's SRM.
    The usage depends on the customer requirement and convinience.
    - R/3 ent structure and SRM org are mutually exclusive. But you take ref of r/3 ent structure in SRM org structure at many points.
    - SCM is collabration of many SAP components like APO, ICH. It's basically group of SAP solutions to map the tptal functionality of supply chain.
    - You can control ECS scenario with BADI depending on yr business objects.
    - Follow on documents are same for both PO or contract , GRN/Confirmation, Invoice
    - already tolD BBPGETVD for downloading vendors from R/3 and BBPUPVD for synchronisation
    - CCM is component for catalog can work in both classic or ECS
      SUS is component for suppliers can work in both classic or ECS
      sourcing is functionality for purchasers can work in both classic or ECS
      SSP is business scenario for self service can work in both classic or ECS
      PDP is BS for plan driven procurement can work in both classic or ECS
      service procurement is for service and work in same way
      these components or business scenarios are mapped as per customer requirements and hence the leading PO location has flexibility.
    BR
    Dinesh
    (Reward if helps)

  • SRM 7.0 extended classic - attachments to backend

    Hi,
    We are in SRM 7.0 and have a requirement to store SRM attachments in the backend ERP.
    This is for the extended scenario going through Badi BBP_ECS_PO_OUT.
    Has anyone got a solution for moving the attachments to the backend?
    Kind regards,
    Alexander

    Hi,
    The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
    attachment transfer logic was only implemented in the Classic Scenario.
    One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
    At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
    I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
    BADI does (BBP_CREATE_BE_PO_NEW).
    We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
    1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
    1413792  Attachment deleted after changing purchase order
    Ihope this information help you to understand this issue,
    Kind Regards,
    Rafael Rhoden

  • PO attachment transfer to ECC - Extended classic scenario

    Hi all,
    We are on SRM 5.0 ECS.As standard,can the SRM PO attachments be transferred to  ECC PO?Is this possible in  ECS?If so,what are the steps?

    HI Alexander,
    The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
    attachment transfer logic was only implemented in the Classic Scenario.
    One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
    At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
    I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
    BADI does (BBP_CREATE_BE_PO_NEW).
    We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
    1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
    1413792 Attachment deleted after changing purchase order
    I hope this information help you to understand this issue,
    Kind Regards,
    Rafael Rhoden

  • Extended Classic Sceanario or Classic Scenario

    dear all,
    i'm a bw person and right now trying to figure out why my confirmation extractor in SRM isnt delivery the data i want. I did a search in service market place and found this 1101861.
    anyway, my question is, is there a function or table or anyway i can determine if the srm system i'm extracting from is using extended classing or just the classing scenario?
    thank you!

    Hi
    Please confirm what sceanrio in SRM are you planning for ?
    I have not tried this. In Extended Classic Scenario, using BADI " BBP_TARGET_OBJTYPE"    -> I guess, it's possible, but not sure. Try it out. 
    Purchase Order (PO) will be created in the R/3 system using the BADI -  BBP_TARGET_OBJTYPE. Please read the standard documentation of this BADI, before implementing the same.
    Regards
    - Atul

  • PO error - extended classic scenario

    Hi Guys,
    I'm using SRM 5.0 with extended classic scenario...
    During creation of the purchase order locally (in SRM) I got the "error in process" status.
    My means of T-code RZ20 I got the following info to ithis error:
    context:B2B Procurement
    object name:Purchase Order
    short name: Backend application errors
    status: Active
    Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
    using Transaction BBP_PD I got the following status:
    Status: I1080
    Description: in transfer to execution system
    Do you have any idea what should I do in order to resolve this outstanding issue?
    many thanks in advance for your help.
    regards,
    Piotrek

    Hi
    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>Note 508972 - Error during transfer of extended purchase orders
    Note 881650 - Duplicate transfer/output of the purchase order
    PO status in " error In Process ".
    Error in Transfer Process (Urgent )
    FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
    Hope this will help.
    Regards
    - Atul

  • PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

    Dear experts,
    My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
    Is it normal?
    Do I need to customize something?
    Can it be achieved by BADi? How then?
    OR is it only possible from SRM 5.0?
    Thanks in advance
    RD

    Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT,  and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
    Note: if this BADI is not present, use BBP_CREATE_PO_BACK
    Regards, IA

Maybe you are looking for

  • Can i delete a file on my external disk?

    I have a toshiba external hard disk. When i plug it into my macbook air, i can only see my documents and copy them to the macbook or copy files from macbook to hard disk. But i can't delete any file on my external disk. How can i can do it?

  • Customer-Bapi

    Hello Gurus, Whats the BAPI we can use to update the customer master tax Classification field. Regards

  • Specified url text input type of form in DW CS5

    If I wanted to dilspay a text input type form on the site's last page, Will the url link function during my table data display? I'm assuming it will be hoverable and active as a link if the text input type form used to submit the link to the database

  • Error in exporting project in OSB 11.1.5

    Hi All, I am facing problem while exporting my resource in OSB console. The export failed with exception: org.apache.xmlbeans.SchemaTypeLoaderException: XML-BEANS compiled schema: Could not locate compiled schema resource schemaorg_apache_xmlbeans/sy

  • JDeveloper 10.1.3.4.0: Unable to find "Debugger - Remote" option

    According to the JDeveloper help: The remote debugging protocols are configured in Debugger - Remote page of the Preferences Dialog. I do not see a "Debugger - Remote" option in the preferences dialog. There are a bunch of options under "Debugger" bu