Important Enhancements in SRM classic Scenario implementation.

Hi Experts,
We are going to plan SAP-SRM imlementation with Classic Scenario.
Please provide important enhancements that are need in general and their requirement and usage.
Also please suggest, how to start and follow in implementation step by step.
thanks
withregards
Reshma

Hi,
Please check configuration guides in SAP Solution Manager or offline documents in SAP Service Marketplace. http://service.sap.com/srm-inst
Regards,
Masa

Similar Messages

  • SRM classic scenario with shopping cart

    In a SRM classic scenario it's possible to create a shoping cart for material stock or it's only possible to create for indirect material (center cost, order, etc).

    Hi Carla
    yes. Indeed you need enhancement
    http://wiki.sdn.sap.com/wiki/display/SRM/BBP_CREATE_BE_PO_NEW-CreatePOin+backend
    you need to clear the account assignment while creating a PO in the backend.
    so PO will be created in the backend rather than in SRM .
    but see impacts - how inventory gl accounts are posted while doing good receipt. Is it taking GL account from valuation class .
    Hide the Order as direct too in SRM .
    create one custome field in shopping cart to determine to order a PO in the backend (for stock materials) so when you check this field, this sc item PO will be created without account assignment.
    Muthu

  • PO Confirmation in SRM Classic Scenario

    Hi,
    I'd like to know if there's a functionality in SRM Classic Scenario wherein suppliers/vendors can tag POs that have been received by them?

    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 Classic Scenario & Invoicing Service Purchase Orders through SUS

    Hi everyone,
    I hope I am able to provide enough information to ask this question.  We are running SRM Classic Scenario in addition to SUS.  We would like to be able to have our Vendors login to SUS and Invoice us.  However, we are being told that in order to do this we will need to install EHP4.  We are currently running ECC 6.  Could someone help me understand what it is exactly that we are not able to do this as is?   I understand that we are able to configure our current system setup to process Material related Invoices but not Services related invoices.
    Thanks for your help.

    Hi Jellis,
    Your vendors can send invoice from SUS but only for material POs (As you are not running ECC 6 with Ehp 4)
    If you want the vendors to send you invoice for service POs also, then you need to go with Ehp 4 as service POs are not supported in SUS using IDOC technology. They need to be in XML format only.
    Regards,
    Nikhil

  • SRM Classic Scenario Reporting

    Hi Experts,
    We have implemented SRM 5.0 classic scenario and BI 7.0. i would like to know various reporting possibilites for shopping carts with backend PO.
    One of the business requirement is to report on Shopping carts, respective PO information in the backend (ECC6.0), and PO history information like GR and IR posting etc.
    I was able to identify the tables in SRM which has been updated with this information from the backend system ECC 6.0. My BI consultant is saying this cant be uploaded into BI system, since there is no change document is created, the delta process wont see the update. He is asking for change document creation, but I am not sure whether this is the right approach or best practise.
    I am sure there should be standard practise and what are limitations of doing a full load every day for uploading the information into BI no matter what. I need your help to recommend a best solution
    Vijay

    Hi Carla
    yes. Indeed you need enhancement
    http://wiki.sdn.sap.com/wiki/display/SRM/BBP_CREATE_BE_PO_NEW-CreatePOin+backend
    you need to clear the account assignment while creating a PO in the backend.
    so PO will be created in the backend rather than in SRM .
    but see impacts - how inventory gl accounts are posted while doing good receipt. Is it taking GL account from valuation class .
    Hide the Order as direct too in SRM .
    create one custome field in shopping cart to determine to order a PO in the backend (for stock materials) so when you check this field, this sc item PO will be created without account assignment.
    Muthu

  • Unable to create confirmation/invoice in SRM,Classic Scenario

    Hi Guru's,
    I am unable to create Confirmation/Invoice in the Portal, attached the screen shot of the error
    its is the problem with the ADRC table, there is no entry in the table for the BP.
    I tried to access the table via SM30 to add the entry in ADRC manually, I get a message table maintenance not defined
    Regards,
    Kiran

    Hi Kiran,
    Could you please also advise whether all the users are not able to create the confirmation in portal. Or if there is any specific user who is not able to do that?
    And I also request you to advise whether you going to do the invoice in SRM portal in classic scenario?
    Best Regards,
    Bharathi

  • SRM Classic Scenario - What decides if shopping cart creates a PO or PR

    Hi,
    In the classic implementation of self-service, how is it decided if the document created in ECC (after shopping cart approval) is a Purchase Order or a Purchase Requisition?
    Is this through a technical solution ie., the PR or PO decision is based on the call to the BAPI that creates a PR or a PO?
    If not then where in config is this aspect decided?

    hi
    if you have assigned FIXED source of supply - PO will be created
    if you dont assign any vendor / prefered vendor - PR will be created ( if no specific sourcing configured)
    as masa said you can control the follow on documents in the define backend Objects.....

  • Enable multiple PO numberranges to support SRM Classic implementation.

    Hi Experts,
    We have implemented SRM 7.0 Classic Implimentation.
    We currently have one PO number range which is assigned to one PO document type to support North America and Canada region.
    We are planning to go for roll-out for Latin America, Europe and Asia pacific.
    Here the client requirement is that they need to have one PO numberrange per Company.
    Can any one suggest what ios the BADI that can be used to achieve this. Backend ECC we can have as many PO document type but how can this be managed in SRM.
    Thanks in advance please help me with BADI or any other means this can be achieved.
    Regards,
    B.N.Karthikeyan

    Hi,
    We are in Classic scenario implementation and hence the standard SRM does not have capability to manage multiple number ranges for PO.
    My question can this be possible to have multiple PO number ranges in Classic scenario based on the company code of the user given in the user attribute.
    SAP MM side I dont have any problem. Only thing is during transfer process how do we achieve selecting different number ranges if I maintain multiple numer ranges in SRM in the maintain intervals.
    Do we have any BADI to achive this expectation. As the customising does not allow us to maintain differnt Number ranges for same logical backend ECC system.
    Regards,
    B.N.Karthikeyan
    Edited by: B.N. Karthikeyan on May 17, 2011 9:25 AM

  • SRM 7.0  Unable to create PO - Classic Scenario.

    Hello,
    We are able to successfully create the below scenario.
    PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
    We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
    Able to create RFx --> Rfx Response.
    Now once the RFx Response is Accepted --> We go for creating PO.
    Classic Scenario.
    The error is due to pricing - debugged and checked as mentioned in my earlier message.
    IPC pricing is switched off and the BADI for simple pricing is activated.
    Error :   " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
    But this is due to pricing is what i guess.
    Error is raised in FM "BBP_PDPRC_UPDATE".
    Kindly Suggest.
    Unable to Create PO
    Regards.
    Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

    Hi,
    Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
    Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
    Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
    SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
    Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
    Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
    Kind regards,
    Tim

  • PI setting for transferring Contract from SRM to ECC - Classic scenario

    Dear Experts
    SRM 702
    ECC 6.0 EHP6
    SRM - Classic scenario
    Need to understand PI setting for transferring Contract from SRM to ECC, as currently document Central Contract document getting created in SRM, but it is not getting transfer to ECC
    No XML message getting triggered in ECC systm as well
    can you help me in this
    if any additional information needed, pls revert
    Regards
    Prashant K

    Fully approve and release the contract. It will trigger the XML Message.
    Go to https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=01100035870000000122&_HIER_… and download the configuration guide & check the PI setting and required Software Components in PI.

  • How differentiate POs classic scenario and POs extended classic scenario?

    Hi Gurus,
    Is possible determine that some POs are generated in SRM system and send to R3 (Extended classic scenario) and other POs only to send from SRM to R3 system (classic scenario) in the same system?
    How we can differentiate which POs should be sent to R3 (classic scenario) and which not? Is possible use type of document for example? Could you explain me if exists standard process?
    The objective is determining the following: Is necessary differentiating POs created in SRM of importation and  should be sent to R3 system (classic scenario), and in case of local POs (not importation) is necessary extended classic scenario.
    I have understood that there is a scenario that includes the Classic and Extended Classic, I think is called Decoupled scenario.
    Thanks for your help!!

    Hello,
    Yes this is possible.
    You can do it automatically based on the product category. You must define the back-end system you wish to use for each product category by making the relevant settings in Customizing for SAP SRM under SRM Server --> Technical Basic Settings --> Define Backend System for Product Category
    Check the online documentation here: http://help.sap.com/saphelp_srm701/helpdata/en/f3/6f505050404ce99151722a79a2c089/frameset.htm
    You can also use Business Add-In BBP_EXTLOCALPO_BADI to overwrite settings made in Activate Extended Classic Scenario and implement more rues for the scenario determination, e.g. based on the purchasing organization for manually created PO's.
    First you set you system to Activate Extended Classic Scenario : SPRO --> SAP Supplier Relationship Management --> SRM Server --> Cross-Application Basic Settings --> Activate Extended Classic Scenario.
    Then you set exceptions in the BAdI.
    Regards
    Franck

  • Classic scenario Configuration document

    Hi  Rama krishna C Teja ,
    I'm Pawan,Presently we are implementing SRM -Classic scenario to our client .at present we are starting defining the Organizational structure? but there are many confusions.......................
    can you please send the config. document for classic scenario ?
                    my email id :          [email protected]
    Warm Regards,
    Pawan

    Hi Atul,
    I'm working using  with this, but let me know what are the changes take place in EBP3.0 and SRM 5.0 ....beacuse we are implementing in SRM 5.0 ...if possiable plese send the COOK book SRM 5.0 to mail id :
             [email protected]
    Pawan

  • Classic Scenario Possibility

    Hi Friends,
    I am a first times for Classic Scenario implementation.
    Can the below scenario is a Possibility in SRM
    1. SC creation
    2. SOCO
    3. RFX and Vendor Response
    4. Central contract in SRM and distributed to MM
    5. Release orders (PO) in MM with ref to Central COntract
    I have few Questions:
    1. What is the BSA attribute will be there in Classic
    2. Can we create initiate sourcing from SC in CLassic or every time we create SC, it will create PR in ECC.
    3. Can central contract be created locally in SRM and distributed in ECC (similar to Extended Classic)
    Appreciate any help in this regard
    IS

    I am not sure as I have to test this in system but i found this some where which needs to be checked.
    Section 3: Default Transaction Types
    If there are multiple transaction types determined, then the default entry in the transaction type dropdown box is set to 'space'. If there is only one entry found for the user then this will be displayed as the default entry in the dropdown box. Here is the code section where it happens: /SAPSRM/CL_CH_WD_DOM_SOCO_GAF3, /SAPSRM/IF_CLL_MAPPER~REFRESH:

  • Info record mandatory for shopping cart creation in SRM classic scneario

    Hi Gurus,
    We are creating shopping cart in our SRM 7.01 system in classic mode. We have not created any info record for the product category and vendor in the backend ECC system.
    Do we need create an info record for the particular combination of material group/material and supplier in the ECC backend system so that the shopping cart in SRM classic scenario creates a PO directly in the system?
    Thanks and regards,
    Ranjan

    Hi Sam,
    Thanks for your update. So, what you mean that the SRM shopping cart  with a direct vendor or contract can create a PO directly in the backend  system even if the backend system does not have nay info record for the particular combination of the material and vendor.
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

  • Classic Scenario Config

    Hi,
    We are new to SRM. We thought of going for SRM Classic Scenario. ( procurement process in SRM for back end system Product categories).
    What are all the necessary configuration setting in SRM 5.0, we need to make to go for classic scenario.
    What is the role of XI server in clasical scenario?
    Helpfull answers will be rewarded.
    Thanks
    Giri

    Hi
    Adding to Pierre,to know more on classic click the following link.
    But if you want to do GR /IV . you must create model vie in SRM add messages  MBGMCR and BBPIV and distribute to back end.
    http://help.sap.com/saphelp_srm30/helpdata/en/0a/baf73a93ad9179e10000000a114084/frameset.htm
    For classic scenario , PO will be created in SAP R/3 system.
    R/3  is a leading system.
    Regards
    Muthu
    Edited by: Muthuraman Govindasamy on Sep 8, 2008 3:14 PM

Maybe you are looking for