SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is :  G3OSBSR102.
R/3 backend Box is :   RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2)  In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
  >Cross-Application Basic Settings
   >Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

Similar Messages

  • SR_ Extended Classic Scenario : Request your help please

    Hi Guru's,
    We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
    in our project the SRM box is : G3OSBSR102.
    R/3 backend Box is : RCHSBR3142.
    Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
    The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
    1) In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
    If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
    2) In this field: BE_LOG_SYSTEM.
    If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
    Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
    Many Thanks,
    Prasad NN.

    Hi ,
    Go to SPRO
    There is a node - Activate Extended Classic scenario
    Do the config.
    Regards
    G.Ganesh Kumar

  • Tolerances in SRM extended classic scenario

    Hi all,
    I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
    We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
    We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
    However, whenever we try to confirm more than PO quantity, we get an error message. “PO Ordered quantity exceeded by 1 EA“
    It seems so that SRM has a ‘double’ tolerance check
    • one in SRM against defined tolerance (via attribute TOG)
    • one in R/3 against the PO tolerance
    Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have PO’s without a material master. Are there any possibilities to skip the PO tolerance check?
    Thanks for your help,
    Martina
    Edited by: Martina A. on Jan 15, 2008 1:13 PM

    Hi
    Depending on the SRM version you are using, Please go through the links, which will definitely help ->
    Condition Type SRM - ECC
    Tolerance in SRM and ECC (BE R/3)
    Tolerance
    Re: SC Budget check without SAP Fund Mgmt
    TOG parameter and tolerance checks better understanding
    Setting EKPO-UNTTO with BAPI_PO_Create
    Re: SRM: many confirmation for PO
    Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
    Do let me know.
    Regards
    - Atul

  • SAP eSourcing with SRM Extended Classic Scenario

    Hi Team,
    We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
    Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
    eSourcing can be used for Strategic RFx and CLM functionalities.
    SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
    Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
    Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
    Thanks
    Jogy

    Hi
    SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
    MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
    Regards
    Mudit Saini

  • SRM Extended Classic Scenario

    HI,
    Please let me know in the extended classic scenario when the PO is created in SRM does the same PO  number gets created in the backend system.Also is the PO created in the Backend system can be opened in transaction ME21N or it can be viewed only in ME22N transaction.
    Thanks,
    Manu

    While configuring consultant has to maintain the same number range in both systems. This way the PO number created in SRM system remains the same as in backend ECC system.
    This PO is only readable in backend system. Only ME23.. transactions can be used to view this. If user is allowed to modiify this PO in backend system it will lead to inconsistency between the systems.

  • STO in a SRM Extended classic Scenario

    Hi All,
       Although I have implemented STO process in a classic scenario, I have not implemented or not sure if possible in a Extended Classic Scenario. Please advise on how STO could be implemented in SRM 7.0 ECS scenario. Will award appropriately.
    Regards
    Rao.

    Hi,
    STO is not a supported PO type for classic or ECS.
    Since you have managed to do with the classic earlier, the logic would be pretty similar in my opinion. Both will called to the BAPI_PO_CREATE1 eventually and i also believe you have made data adjustment in the SRM/ERP BADI before the classic PO data is used for the document creation.
    Likewise for ECS PO, we have BADI for the ECS PO too.  By adjusting the necessary data before document creation, you should achive the same end result.
    However there is a major difference between classic and ECS PO - the latter cannot be edited in the ERP at all if that is a requirement which you have done in the earlier PO.
    Regards.
    YS

  • On Time Delivery Metric ( SRM Extended Classic Scenario)

    Can anyone provide feedback on how you are measuring suppliers on time delivery performance based on SRM Extended classic POs. We are currently trying to use the Stat-Rel Date (SLFDT) in R3 to measure Original commitment date vs. Actual delivery date to get our OTD Metric However when we create an ECS PO with Reference to an R3 Requistion the SLFDT date is populated with the Requistion delivery date and not the delivery date on the Purchase Order.
    R3 Version ECC 6.0 SP 12
    SRM 5.0 SP 9
    Thanks,
    Erick Sick

    Hi,
    Have you defined your Log systems in both SRM and ECC? Have you assigned a client to the logical system? Are you sure that all RFC connections are working fine?
    Regards,
    Nikhil

  • How is Idoc MBGMCR triggered/Configured in SRM Extended classic scenario

    Hello All,
    In the existing scenario, when confirmation is created in SUS portal, corresponding confirmation gets created in EBP .
    Once the confirmation in EBP gets approved ,we want corresponding confirmation creation in backend system (ECC) .
    I  thought of using the standard idoc of basic type MBGMCR01 and message type MBGMCR for the above requirement.
    But I am unable to find how to configure the triggering of idoc MBGMCR during creation of confirmation in EBP.
    If anybody has an idea of message control method in SRM or how is idoc MBGMCR gets triggered, please let me know.
    Thanks in advance.

    Hi Anuradha,
    You would require to set up distribution model , tcode - BD64
    SAP NetWeaver  ->Application Server ->IDOC Interface / Application Link Enabling (ALE) -> Modeling and Implementing Business Processes ->Master Data Distribution ->Distribution Using Object Classes ->Model Distribution Using Classes.
    Once the distribution model is set up you can assign the message type MBGMCR.
    Hope this helps you.
    Regards,
    Ashish

  • Extended Classic Scenario PPOMA_Purchasing Org and Group

    Hi gurus,
    We are working with SRM 5.5 and we are having problems with the assignments for the Purchasing organization and Purchasing groups in the PPOMA.
    In the documentation it says we should have one box for the R3 Purchasing Organization (flagged and referred to the backend POrg) and one for the Local Purchasing Organization (flagged but NOT referred to the backend POrg). The same for the Purchasing Groups, the one under R3 POrg will be flagged and referred to the PGroup in R3 and the one under the Local POrg will have the flag but it will not be referred to the backend PGroup.
    Afterwards, in the attributes for the Local POrg and Local PGroup, with the attributes PURCH_ORGX and PURCH_GRPX the local and the R3 POrg and PGroup will be assigned each other.
    The purchasers will be located in the Local PGroup. The R3 POrg and PGroup will never have users assigned.
    The problem is that all the workflow is only working if the "Local" POrg and Group have the backend purchasing organization and purch group assigned in the Function Tab. This means that the 2 boxes for R3 are no longer necessary. In the documentation it says that this version of SRM needs both boxes for the POrgs and the 2 boxes for the PGroups. We have flagged the Extended Classic Scenario.
    Any help on this? It's because of the version?
    Many thanks and regards,
    I will give Points!

    Hi Ana
    PURCH_GRP     Purchasing group     Number of an organizational unit that is indicated as local purchasing group in the organizational plan.
    This attribute is simulated. You define an organizational unit as company on the Function tab.
    PURCH_GRPX     R/3 purchasing group     Number of an organizational unit that is indicated as the R/3 purchasing group in the organizational plan. The value contains the ID and the associated backend system of a backend purchasing group.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    PURCH_ORG      Purchasing organization     Number of an organizational unit that is indicated as local purchasing organization in the organizational plan.
    This attribute is simulated. You define an organizational unit as purchasing organization on the Function tab.
    PURCH_ORGX     R/3 purchasing organization     Number of an organizational unit that is indicated as the R/3 purchasing organization in the organizational plan.
    This attribute is simulated. You define the ID and the associated system on the Function tab.
    can you elaborate more?
    in ECS also we can map the backend purchase organisation/ purchase group for purchasing activity.
    there might be a resposibilty tab for the backend purchase group might be mapped the responsible purchaser list (dept).plz check it up
    regards
    Muthu
    regards
    Muthu

  • Invoicing Plan functionality in Extended Classic scenario

    Hi,
    For PO's are created in SRM-Extended Classic scenario, kindly let me know on how to maitain Invoicing plans.
    Thanks,
    KB

    Hi. You could use ERS.
    Let's say you wanted an invoice plan to pay every month for 12 months, you could create a cart on an ERS vendor and order quantity 12, unit months.
    Then every month the user could do a goods receipt for 1 month.
    That would trigger an ERS invoice, just like an invoice plan would.
    The only problem with this is that you are relying on the user to do the goods receipt.
    Regards,
    Dave.

  • Sharing attachment documents (e.g. for P.O.) in extended classic scenario

    Dear SAP SRM gurus
    in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0  as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
    My customer wants to know if there is the possibility of not replicating them.
    Any suggestions will be appreciated.
    Many thanks in advance
    Best regards
    Gianluigi Brenna
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
    Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

    Hello,
    In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
    If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
    Regards,
    Prasanna

  • Extended classic scenario to Classic scenarioc in SRM.??

    someone pls tell me how to change from Extended classic scenario to Classic scenarion while creating in shopping cart...?
    I am using BADI "BBP_EXTLOCALPO_BADI" change to classic scenarion from extending classic..but i got confused about source code..So i request any one can help me for suitable source code..

    Hi
    Do you mean to say that you have set up Extended Classic Scenario but you want to change it to Classic Scenario?... If this is the case, remove the activation in COnfiguration for Extended classic scenario and deactivate BADIs you ve implemented for Extended Classic
    OR
    Do you want to change it to Classic only for the Document user is creating.--> Read the indicator or data from SC and decide whether the document has to be in Classic or Extended classic SCenario.... The BADI will either have Extended classic = X or NOT.... so there is no parameter for classic Scen... Depending on your requirements, implement the ext. classic badi to SET it or NOT set it...
    Regards
    Virender SIngh

  • Use of Purchase info records in SRM SC in Extended Classic scenario

    Hi All,
    We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
    Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
    Thanks,
    Ankur

    HI Ankur
    when you say the price did not get updated did you check the sequence which is used for price determination ?
    1. User entry
    2. Contracts
    3.  Info record
    If still you think it is an issue please check the report  EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
    Regards
    Vinita

  • Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

    We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
    Please provide some help in solving this issue.

    Hello,
    This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC).  And accepting the SES in ML81N will generate GR posting.
    For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
    So basically, for service items you create confirmation and for materials you create ASN.
    Regards,
    Prasanna

  • SRM 7 : Vendor record replication in backend with Extended Classic Scenario

    Hello,
    We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
    Can you explain what is to be configured to get the new vendors replicated to the backend?
    Thanks in advance.

    Hi,
    It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
    Check the below link for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
    Regards,
    Sanjeev

Maybe you are looking for