Product categories Central contracts as SOS in SC

Hello,
We are implementing SRM 7 Level 9 with extended classic scenario.
We have created central contracts with items with Products categories only.
Those central contracts do not appear when the requester has selected the same product category in the shopping cart item.
We see no IMG activities for this. What can we do?
Thanks in advance.

Hi
I have set up several central contracts, each time with one contract item with one product category. It means we have only ONE criteria.
Contracts never appear in SC SOS tab.
It works well with classic scenario (I can grab all contracts I have in ECC against the product category).
Does ECS require more than one criteria to automatically assign the contract to SC item? Because we want to run ECS here.

Similar Messages

  • Benefits of implementing Central Contracts in SRM 7.

    Dear Experts,
    Picture the following:
    - Classic Scenario.
    - One ECC 6 EHP 4 Back end.
    I'm currently exploring the benefits of implementing Central Contracts against using only Purchasing Contracts in ECC and replicating them to SRM for use in the Shopping Carts.
    So my question is why would you implement central contracts in SRM instead of just replicating these contracts from ECC? What benefits would you get out of having central contracts in place against having only Purchasing Contracts in ECC?
    Thanks for your input.

    adding to Manju one point .
    - Procurement department(PURCHASER) can use web interface to create / manage contracts rather GUI interface and quick contract creation / maintenance
    - Approval mechanism simplified with less efforts.
    - Different ways to create a contract from SRM
       Copy an existing contract
    Use an existing template
    Upload an external file
    Upload a contract from the catalog
    Muthuraman
    1.You can use this business process to access SAP SRM contract features, such as contract hierarchies, discount across contract hierarchies, and grouping logic, when determining source of supply in SAP ERP.
    2.You can create a central contract in SAP SRM, and it can then be used as source of supply in both SAP SRM and SAP ERP. Relevant data is sent to SAP ERP for a source of supply determination, and a specific type of contract or scheduling agreement can be created there.
    3.While determining a source of supply, you can access central contracts directly.
    4.The price is determined in SAP SRM before the SAP ERP purchase order (PO) is sent to the supplier.
    5.You can create and change central contracts and renegotiate existing contracts directly with a supplier, or through the creation of an RFx. You can automatically assign a contract as a source of supply, or it can be listed as one of numerous potential source of supply contracts. A strategic purchaser can create a contract whenever they anticipate a long-term relationship with a supplier.
    6.Contract management enables purchasers from various parts of the company at different locations to take advantage of the terms of globally-negotiated contracts for specific product categories. You can provide users with specific levels of authorization to contracts, and you can categorize documents as confidential.
    6.You can distribute central contracts to release-authorized purchasing organizations, and these organizations can then use them as source of supply in the appropriate SAP ERP system. Hierarchies can be used to organize, structure, display, and search for contracts.
    7.If you use SAP NetWeaver Business Intelligence (SAP BI), you can view various consolidated reports of contract management. For example, you can view aggregated value released against all contracts in a contract hierarchy.

  • Central Contract Management in case of Classic Scenario

    Hi,
    At our current implementation, requirement is to implement both Service procurement(with hierarchy) and Central Conract Management. I was exploring the possibility of utilizing Central Contract Management with Classic scenario.
    Will the Central Contracts created in this fashion be available in Sourcing Cockpit for the buyer to select against Purchase Requisitions? Will the Central Contract be visible at all in SRM in this case ?
    Please respond only with reference to Classic scenario.
    Thanks,
    Abhilash

    Yes the Central Contract will be available in the Sourcing Cockpit, both local and classic scenario's. Yes the Central Contracts will be available for the creation of Purchase Requisitions in R/3 and to assign SOS in R/3.
    Do know that for SRM 7.0 PI is required for setting up Central Contracts. This is promised to change with the release of EHP1 for SRM (due june 2010).
    Kind regards,
    Tim

  • Registration of Suppliers to New Product Categories

    Hi,
    As we have seen, during registration of new suppliers, system offers a list of product categories to select. System sends questionnaires related to the selected product categories, to prospective supplier's email ID. The supplier submits answers to these question. The buyer will scrutinize the details, registers him as supplier and also maintains supplier list for the product categories which he has requested.
    Now the supplier is interested in some more product categories. So he has to select some more product categories. The system should send him a questionnaires for those product category. The buyer will scrutinize the answers submitted by the supplier and maintains supplier list for those product categories.
    How to map this scenario in standard SAP?
    Ganapathi

    Hi Ganapathi
    Nikhil is correct.
    i assume that supplier want to register some more product category which is not in the system . sorry if i understood wrong.
    or it is just understanding between buyer and supplier.
    There is no fixed rule that whatever supplier register the product category and he will receive the PO or contract.
    It is understanding between Buyer and Supplier what type of product category supplier expert to do service for the purchase organisation.
    Whatever product category is existed in the ROS system the same only can be registered by the Supplier.
    Because purchase organisation uses only some product category which they wants for their organisation.
    For ex
    step 1:-BREAKS product category - TVS registerd in the ROS system and become supplier
    step 2:- again TVS supplier want to add WHEELS product category ? and expects a questionaire for WHEELS from the Purchase organisation?
    Muthu

  • Hierarchy - Product Categories

    Hello everyone!
    I´m starting to prepare the environment to  start working with CRM standalone (no integration with R/3).
    I need some help/tips/materials/etc on how to created Products, Hierarchies with product categories, etc.
    I am reading the ConfigGuide C09 (Central Master Data Standalone). I believe there is a gap between items 3.2.1 and 3.2.2 because I have no products created yet. Do I have to create a base hierarchy first? How?!
    I appreciate any kind of help.
    Thanks,
    Luis.

    1. Create Hierarchy First, you can do so by transaction comm_hierarchy.
    2. Create Categories under the hierarchy in step 1.
    3. Under the categories created under step 2 add the settypes you want to use in your Product.
    4. Start creating product under the categories created in step 2 from transaction commpr01.
    Without creating Heirarchies & Categories one will never be able to create a Product.
    Regards,
    Harshit

  • Central Contract in Classic Scenario

    Hi Friends,
    I have done the central contract scenario in Ex classic  where Local contract will be distributed to ECC .
    Can we use the central contract concept in Classic Scenario and is there any limitation based on scenario.
    As in classic the documents are created in ECC , so for central contract also there will be no local contract ???
    Can anyone please help me to understand the same.
    Thanks
    IS

    Hello,
    Yes, this concept can be used in classic scenario as well.
    You can use them as source of supply, since in classic scenario ECC contracts are considered as soruce of supply. Therefore, replicated contracts will be proposed as SOS for shopping carts.
    Regards,
    Ricardo

  • Central Contract, MDM Catalog, and classic scenario

    Dear SAP experts,
    We are in SRM 7.01 with backend ECC 6.05 deploying classic scenario. We are using Central Contract Management in which we negotiate contract in SRM and later distribute it to ECC. We also plan to use SRM-MDM Catalog.
    We notice that if we are using classic scenaro, the contract that is used as reference is the contract number in ECC (the one distributed from SRM). So at first we assume that if we want to push the contract data to MDM, we should have pushed the ECC Contract number. However we find out that actually SAP block the ECC Contract coming as distribution from SRM to go to MDM.
    Our second option is to use distribution of contract from SRM to catalog. It does using SRM contract number. We create SC and then we pull the catalog item from the catalog (which contain SRM contract number) and then we order. However we end up with 'error in process' in which the system try to create a PR instead in the ECC (meaning that the contract number cannot be read).
    We're puzzled with this. How can we use the combination of central contract, MDM catalog and classic scenario? Can we use the combination?
    Best regards,
    John

    Maria
    If you want the contracts to be in SRM and do not want them to send to Backend, then check this out.
    Create a Vendor list for those items in SRM by assigning the local contracts to the vendors.Activate Vendor list for sourcing.
    Then local contract data should pick as SOS from the vendor list.
    If you can create contracts in Backend for stock material then SC would pick the backend contract as SOS in classic scenario.
    Let me know if the above works or not.
    PS : Reward points if helpful.
    Regards
    Jagadish

  • SRM 7.0 Central Contract-For Centralized Purchasing Scenario

    Hello Experts
    Is it possible to set up a corporate (read Centralized) Purchasing strategy, where in One Central purchasing organization creates and manages Central contracts for various Plants assigned to different company codes using SRM 7.0 with ECC Backend?
    Tried to set this scenario up by assigning Purchase organization directly to Plants (in ECC) but the Contracts were failing during replication in ECC.
    Any inputs on this are appreciated.
    Thanks
    Raman.
    Note: Contracts went through successfully in ECC after assigning the Purchasing organization to Company code.

    Hi,
    Please check this.
    SPRO -> Enterprise structure -> Assignment ->
    Logistics - General -> Assign Plant to company code.
    Assign plant to company code
    In the IMG activity "Assignment Plant - Company Code" you assign each plant to a company code.
    A plant can only belong to one company code.
    Note
    Complete functionality of the system can only be ensured if the plants assigned to a company code are only those situated in the same country as the company code.
    It is therefore recommended that you also create a company code for each country in which a plant is situated.
    Examples
    Only then are tax postings created when transferring stock between plants in different countries.
    The taxation procedure and Intrastat declaration are supported only for the country of the company code.
    Requirements
    Before you can assign plants to company codes, you must define the valuation control.
    You may change the valuation control in the production system only after contacting your SAP consultant. Changes may cause inconsistencies in documents.
    Actions
    Assign your plants to company codes.
    Regards,
    Masa

  • Central Contract Management

    Dear SAP Experts,
    I have a few questions regarding our implementation of SRM and ECC.
    FYI, we are planning to use SRM 7.01 and ECC 6.05 as backend.
    We’re planning to utilize Central Contract Management functionality in SRM, where we negotiate the price in SRM then we distribute the contract to ECC. In ECC we create PR, which have reference to this contract (contract number in SRM is different with ECC). So this PR will have assigned source of supply, is it possible for us then to create PO automatically from tcode ME59? The reason we ask this because we see in documentation that every PO in ECC created with reference to contact in SRM, ECC will need to check first the current price in the SRM contract, so we would like to confirm whether it is working if we use ME59 (we plan to use ME59 as background job and unfortunately we don’t have the testing system yet to verify this).
    We’re planning to have PR created in ECC. However we would like to utilize MDM catalog as well. Is it possible that during PR creation we can select items from the catalog?
    We’re planning to have implement SRM 7.01 in 2 waves. In first wave we will only use Self Service Procurement and Strategic Sourcing (using classic deployment where the leading PO is in ECC). However in the second wave, we’re planning to implement SUS (Supplier Collaboration). In SUS, we would like to activate the business function, so the vendor will response RFx and participate in auction from SUS itself. The question is…is it possible for us to have it planned like this? For example, in first wave, the RFx and auction will use SRM server itself, however in the second wave, we will switch it to SUS. Our concern is that the switch will happen to the productive server already. Is this okay?
    Thanks
    Varian

    Hi,
    When you distribute the central contract to ECC system, it creates a new contract in ECC system.
    When you create PR, you can assign this contract as source of supply.
    Then automatic PO creation if your settings for automatic PO is maintained.
    In ECC 6.04 also catalog integration is possible. So for your version 6.05 there is absolutely no problem. The same OCI interface parameters have to be maintained in MM system for catalog.
    Your two stage implementation is absolutely possible.
    With Regards,
    Malay

  • Central contract Workflow attributes

    Hello,
    As per my understanding we can activate the workflow on any contract attributes/ fields(for central contract) like prices, product category etc.
    We can activate u201C1-stepu2019 standard bc set u201C/SAPSRM/C_CT_600_001_SP04u201D and can determined workflow agent based on any attributes like u201CProduct categoriesu201D ,price etc
    Or we can use BADI Implementation u201CBADI /SAPSRM/BD_WF_RESP_RESOLVERu201D for Agent determined based on attribute store in customized table
    Please correct me if my understanding is wrong
    However we need your valuable inputs on below
    1)     List of central contract ( CCTR ) attributes/fields on which we can activate the workflow.
    2)     List of central contract ( CCTR ) attributes/fields on which we can activate the workflow without any badi implementation ( without any coding ). As a part of standard configuration.
    Best Regards
    EPR_SRM_MDM

    HI,
    I suppose you plan to use process controlled workflow.
    If yes then you can check the tcode BRF and try to create a expression of type formula interpreter.
    In the this expression navigate to formula editor and here you can find all the attritutes you can trigger for any business object.
    For agent dertermination SAP has already delivered many agent determination method.. If a process level and click on the F4 feature available for field Resolver Name to find all the predelivered methods.
    You can check the service market place http://service.sap.com for Workflow Guide SAP SRM 7.0
    Path:
    service markerplace -> Release & Upgrade info -> Installation & Upgrade Guides-> select SRM 7.0
    Regards
    Sam

  • Updation of central contract

    Hi all,
    We have a SRM 7.0 system with ERP 6.0 as the backend. I have created a central contract for an item - A with vendor - B  in SRM and distributed it to a purchasing organisation (3002) through assign distribution functionality.
    Now when i create a shopping cart for item A , the central contract appears as a source of supply and i can proceed with ordering of this item. But the problem i am facing is that the central contract is not getting updated in the backend ie the quantity does not decrease after buying the item - A.
    Pl let me know if any message types need to be defined for updation to be posssible.
    Thanks.

    Hi Nikhil,
    How did you fix this issue? I've created a central contract in SRM 7.01 and distributed successfully to ERP. When i created the PO in SRM, SRM contract release values is not updated in SRM.Or when i created PO in ERP using SRM contract as SOS, that PO is not updating SRM release values.
    Regards,
    Gigies

  • Badis for PO and Central Contract in SRM 7.0 in classic

    Hi everyone,
    I need you help. We are working in a implementation of SRM7.0 with ECC 6.0 Ehp 4 in a classic scenario. We want to know which badis we can use in order to change the purchasing group of the PO an Central Contract when their are transfered to ECC.
    BR,
    Ivá

    Hi Muthu,
    We are wondering if it is posible the following:
    - An user wants to create PO form SRM. This PO in SRM has the Purchasing group XXX, but (for any reason) we need when this PO is send to ECC, the system changes the purchasing group to YYY.
    BR
    Ivá

  • Central Contract SRM

    I have an issue, when I create central contract in SRM. The Select System is empty. No values is there on the screen.
    Even though I try to create contract I have the error message "No customizing entry for SRDCLNT600 in table BBP_BACKEND_DEST"
    We have SRM 7.0 , ECC 6.0 EHP4.
    Regards,
    Lya

    Hi,
    Are you just setting up the system or has it been working already ?
    Pl check your "Define Backend Systems" set-up in IMG. There might be some problem here.
    Best regards,
    Ramki

  • SRM, MDM, ECC integration for central contract management.

    Hi there,
    I am questioned by a client with respect to the possibility of the following scenario -
    1. There are several SAP back end systems in place.
    2. SRM 7.0 will be implemented as single sourcing system.
    3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
    4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
    5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
    Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
    Thanks and Regards,
    Shantanu Joshi

    Hello Shantanu Joshi
    Your business scenario is standart MDM functionality
    More about how it works you can read from:
    MDM overview
    and standart help links (see scenarios part):
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
    Regards
    Kanstantsin

  • SRM -- MDM -- ECC integration for central contract management for SRM 7.0

    Hi there,
    I am questioned by a client with respect to the possibility of the following scenario -
    1. There are several SAP back end systems in place.
    2. SRM 7.0 will be implemented as single sourcing system.
    3. The SAP back end systems carry different material master codes for the same material and this will remain the same and no cleaning effort to have a unique code across all systems is going to be done.
    4. If we use MDM in the mix - will it be possible for the SRM system to act as a central contracting solution and create a central contract with the unique material code in MDM.
    5. On distribution of this contract across to individual SAP back end system the back end should map the MDM code to correct material code in that respective system.
    Any insights with respect to if this is possible with some enhancements or not at all possible will be highly appreciated.
    Thanks and Regards,
    Shantanu Joshi

    Hello Shantanu Joshi
    Your business scenario is standart MDM functionality
    More about how it works you can read from:
    MDM overview
    and standart help links (see scenarios part):
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
    http://help.sap.com/saphelp_nwmdm71/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm
    Regards
    Kanstantsin

Maybe you are looking for