Sourcing Cockpit in Classic Scenario

Hi,
We are implementation SRM 7.0 Classic Scenario.
The client requirement is this. They want a requester to create a incomplete shopping cart, as they are not aware of the price and the vendor at times. Now they want the incomplete shopping cart to be picked up by the buyer in the sourcing cockpit, add the price and vendor details, and then this cart to go ahead with the approval hierarchy.
Now I understand that the PO gets created directly from the sourcing cockpit, but is it possible for the buyer to complete the SHC first(we are ok with buyer approvals), and then for the SHC to go through the approval hierarchy. Else is there any other Solution for this.
Please suggest.
Ron

Hi
after approval only the SC goes to cockpit or follow on document created.
BUYER can determine the price
you can do the configuration Sourcing carried out without source of supply.
though REQUESTER eneter any price , BUYER can override the price.
If requester assigned prefered vendor or without any vendor - it will go the cockpit.
if REQUESTER enter any price if requester assign any fixed vendor, PO will be created since - Free text sc - Product category contract,
if it is material , the price can be picked from contract like any fixed siurce of supply.
Muthu

Similar Messages

  • Influence PO document type in ECC from Sourcing Cockpit in Classic Scenario

    Hello experts: we are running SRM 7.0 with ECC 6 EhP 4 in a classic scenario.
    Our business requirements are: all SC item created with reference to a catalogue item must result in a PO not subject to release strategy in ECC6 MM. For this purpose, document type ZEC has been entered under parameter BSA in tcode PPOMA_BBP.
    Due to Sourcing customizing, some Shopping carts items without source of supply are sent to Sourcing Cockpit.
    In sourcing cockpit application, buyer completes the open items by including the vendor, price, etc and create draft POs that are finally converted into backend purchase orders in ECC6. These Purchase orders, created without reference to a catalogue item should be subject to release strategy and approved by the corresponding approval body in ECC6.
    Due to that, we must change the document type in backend and enter another one which is subject to release strategy. We tried it thru badi BBP_TARGET_OBJTYPE but we could not get it. we change BE_DOC_TYPE to NB when the catalog id is blank in the SC item and follow-doc is PO. However, system always creates PO with document type ZEC
    We would like to know how to influence the PO document type when we are trying to create POs from SOCO.
    Any clue about it?
    Many thanks in advance
    Best Regards
    Valentí

    Solved

  • Sourcing in extended classic scenario

    Hello, all
    We are using the extended classic scenario in SRM 5.0.
    In sourcing cockpit I have the following problem. In spro Supplier Relationship Management/SRM/Server/Sourcing/Define Sourcing for Product Categories I set  Sourcing Always Carried Out. From a shopping cart the purchase order is created automatically as the data complete, but  I'd like to sent shopping cart to the sourcing, where from  a shopping cart create bid invitation or purchase order. How  do it?
    Please help,
    Best regards,
    Guzal

    Hi Guzal,
    As informed by Claudia, Incomplete mainly means no vendor assignment, no price etc.
    If the vendor is assigned at the shopping cart level by means of a contract the shopping cart (details)  is complete. Even in this case the SC should go to Sourcing cockpit in case of "Sourcing Always carried out" is chosen in the sourcing column.
    In the above case the P.O gets directly created from SC only when the options
    " Sourcing never carried out" & " Sourcing carried out for items w/o assigned source of supply" were chosen.
    Hope you will be more clear on this issue. Any clarifications always welcome.
    Rgds,
    Teja

  • SRM Bidding Engine and Sourcing Cockpit

    Hi All,
    can the SRM Bidding Engine be linked to the sourcing cockpit when using the classic scenario?
    What I want to be able to do is to create an RFX from a shopping cart in the sourcing cockpit. We use the classic sceanrio currently on SRM 4.
    Cheers
    Chris

    Hi Chris,
    yes, the bidding and auction functionality is directly connected to the Sourcing Cockpit in Classic Scenario. That is standard. In order to be able to create a classic PO from Bidding / Auction, all you need is a shopping cart, you describe you have.
    Cheers,
    Claudia

  • Sourcing of GOA in Extended Classic Scenario

    Hello all,
    We are using the <u>extended classic scenario</u> with both Purchase Contracts and Global Outline agreements.
    Is it possible to use the GOA in the back-end as a source of supply in the sourcing transaction in SRM? What setting do I have to use exactly?
    Kind regards,
    sander

    Hi
    Which SRM and R/3 versions are you using ?
    I guess, the following threads will help.
    <b>Source determination in backend (R/3) for distributed contract i.e. GOA
    Transaction For Creating GOA
    Distribution of GOA in R/3
    FM or BADI s' used to create a GOA
    GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
    Hope this will help.
    Please reward full points, incase it suits your requirements.
    Regards
    - Atul

  • GOA as SOS (Source Of Supply) in extended classic scenario

    Hi,
    I understand that when I create a SC in EBP, GOA can't be a SOS in "Extended Classic Scenario (SRM 5.0)". If I want to make GOA as SOS, how do I do it ?
    I have searched the forums and found that the below BADIs can be used.
    BBP_CTR_BE_CREATE
    BBP_CTR_INIT_UP
    BBP_CTR_MAIL_BADI
    BBP_CTR_MASS_BADI
    Now I am looking for someone who has done this scenario and please explain how did you do it ?
    With regards,
    Pranav

    Hi,
    I had a former project where I modified SRM standard source so that I can use GOA as source of supply in extended classic scenario. In Standard, as you know, SAP doesn't allow to use GOA as SOS in extended classic. In extended classic, we have to use local SRM contract as SOS. In my case, it was SRM 3.0.
    Cheers.

  • Classic scenario - Sourcing

    Hi,
    I read that in a classical scenario, purchasers do not have to added to the purchase group in the org structure.
    The purchase group mereley exists to transfer the P Ggp value to the backend system.
    In this case if courcing is activated in the classical scenario, there would be no purchaser responsible for the backend PGrp.
    To who will the request be forwarded?
    Thanks,
    Vignesh

    Hi
    one purchaser might be repsonsible for one product category .
    you might entered responsiblity TAb for purchase group
    under this you have responsible product category
    whenever no source of supply is there , it goes to purchaser of responsible product category.- if you do soucing configuration.
    simply when you see purchase group in the basic data click one binocular , you get purchaser name of pg .
    br
    muthu

  • SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

    Good day,
    I would really appreciate some assistance on the following matter:
    We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
    Our process is as follows: Purchase
    Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
    converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
    create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
    When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data".  We do not have PI/XI and I would really
    appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
    I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
    ordered in system SRDxxxx (which is the SRM system).
    Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
    Thank you in advance,
    Marinda

    I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

  • Purchase Order error message when on Sourcing Cockpit.

    Hi All,
    I have encountered a series of error messages when I try to convert my Shopping Cart into a Purchase Order in SRM 5 within the Sourcing Cockpit. I am using Extended Classic Scenario and have defined the number range in SRM and ECC5. The error messages are below, the moment i try to concert the cart to a Po;
    - Internal number range is missing for transaction type. Inform syst. admin    
    - Transaction type * does not exist. Check entries    
    - Some backend documents could not be generated, or they contain errors  Further Information 
    - No status object is available for 
    I have checked the transaaction type, number ranges assignments, attributes in PPOMA_BBP but fail to find the cause.
    Any pointers would be welcome!
    Thnx,
    Mike

    Hi Muthu,
    The number ranges are consistent as I have checked the number range for local purchase order and this is set as an internal between the range 3000000000 - 3999999999. On the transaction type for BUS2201 Purchase Order, 30 has been set as the Int Number Range, with all other fields left blank.
    The strange thing is that the documents that failed to convert into a PO had been reprocessed in the Application Monitor for Purchase Orders, but when I go back into Sourcing to create the PO, I now get the message:
    "You have either failed to select an item, or you cannot create a follow-on document due to an error that has occurred"
    Regards
    Mike,

  • Doubts in creation of PO for service PR in classic scenario

    Hi everyone,
    I'm working with SRM 5.5 in a classic scenario.
    I have the following process:
    1. A PR for services is created in ECC (Item Category "D")
    2. The PR is transferred to SRM as SC
    3. A bid invitation is created in sourcing cockpit
    4. A bid is accepted
    5. A PO is created.
    In the 5th step the PO is created locally in SRM. Is this the standard behavior?? Why is not created in R/3?
    Thanks,
    Ivá

    Hi Ivan,
    For scenario details pls refer below links:
    http://help.sap.com/saphelp_srm50/helpdata/en/d9/cbd33b8dca2c43e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/frameset.htm
    What message do you get when you create a PO from Bid?
    Are you able to execute the scenario for materials?
    Regards,
    Prashant

  • 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

  • :):(Creation of RFX or LAC in a Classic Scenario:):(

    Hi Guys,
    I was wondering if you guys could come up with some nice suggestions on how i should go ahead and process my requirements.
    We are implementing a SRM 4.0 (classic scenario) system. I am aware that all shopping carts in SRM are created and transferred to the backend as a PO/PR according to our customization and nothing goes to the sourcing cockpit when a vendor is not assigned in a classic scenario.
    <b>Implementation of a classic scenario restricts one to create a Bid or a Live Auction from the sourcing cockpit. Can all the SRM GURUS suggest me in what way one could push the requirements to the bidding engine or to the Live Auction Cockpit in a CLASSIC SCENARIO</b>.
    I hope i would get great responses.
    Thanks
    Sunny

    Hello Sunny,
    there has never been such limitations.
    Classic scenario is supported by Sourcing Cockpit & Bidding Engine in SRM 4.0, at the condition that a classic SC is created in SRM.
    In sourcing customizing, you can decide to send all SC without source of supply to the Sourcing Cockpit.
    You can even decide to initiate directly an RFX, without using the Sourcing Cockpit.
    At the end of the negociation (RFX --> Bids --> Auctions --> Bids), the awarded bid can be transformed into a backend PO or a backend Contrat.
    Rgds
    Christophe

  • The Shopping cart not appearing in the sourcing cockpit of the buyer

    Hi
    We are using Extended Classic Scenario. The SC was created in SRM and then after approval was send to a central buyer for sourcing. The central buyer redistributes the same to the respective Buyer based on the purchasing group. However the SC doesnt appear in the sourcing cockpit of the actual buyer and when I see the details of the SC item in BBP_PD, I see that the Sourcing Relevant Indicator is marked 'Y' which means Sourcing is already completed. But nowhere a supplier has been added to the SC by anyone and it also doesnt reflect in the BBP_PD.
    Any idea how and why the indicator has the status 'Y' and how can I make the SC appear in the sourcing cockpit of the buyer.

    Hi Manoj,
    If the SC is directly converted into a P.O (either ordered / held status) please check the Sourcing settings in SPRO.
    SPRO > IMG > SRM > SRM Server > Sourcing > Define sourcing for product categories
    Check whether sourcing always carried out was maintained for the required product category. The P.O will get directly created in case the setting is " Sourcing never carried out".
    Please check this and let me know if this is the case.
    Rgds,
    Teja

  • Direct Procurement in Classic Scenario

    Hi Experts,
    We are on SRM 7 Ehp1, ECC 6 Ehp4.
    Classic Scenario.
    1. I have read in the forums , that in Classic Scenario, direct procurement is possible but the system behaves like Extended Classic and creates a Local PO. Just want to confirm this and if yes , does this happen as a standard or do we need to implement any BADI or anything to achieve this.
    2. Also , in Classic Scenario, PDP scenario , can we transfer stock items(Direct Materials) PR's into SRM system or are there any limitations.
    Thanks
    Aditya

    Hi Aditya,
    You are right. Classic system behaves as extended classic for Direct procurement scenario. Your PO will be created in SRM itself and a copy of this will be sent to ECC. This happens as a standard and no BADIs need to be implemented for this.
    Also in your classic system, you can transfer stock PRs into SRM. These will be available as shopping carts in the sourcing cockpit.
    Regards,
    Nikhil

  • Classic Scenanio and Extended Classic Scenario

    Hi all,
    I would implement on the same system 2 different scenario:
    1. Classic Scenario for self service procurement
    2. Extended Classic Scenario for the following business scenario:
        a. PR from ECC is transfered into Sourcing Cockpit with Plan Driven Scenario
        b. buyer convert the SC created in Sourcing Cockpit into a GOA or a PO that are transfered to ECC.
    Can coexist this different scenario?
    Can I address this different scenario only with organizational differences?
    Thanks
    Bye
    Marco

    Hi Marco,
    I see 2 quick ways to realise your requirement.
    The first is to create an attribute in t77omattr for a position and maintain that attribute in the organisational model. This attribute could just be filled with an X for example.
    Then you have to implement BADI BBP_EXTLOCALPO_BADI and retrieve the attribute you created with FM BBP_READ_ATTRIBUTES (use sy-uname to retrieve the attribute for the current user).
    The 2nd is to create a Z-table with the user-ids that you want to use the local (or ECS) scenario. Then again in BADI BBP_EXTLOCALPO_BADI  you have to write the logic to retrieve and compare this.
    Keep in mind that these are user-based distinctions and not based on scenario.

Maybe you are looking for

  • Error while running a Dynpro Application

    Hi, I am using an RFC that use GUI_DOWNLOAD FM to push the file data to an internal table, but when it comes to Dynpro application it through an error u2018Access via Null Reference is not possible u2019 (Exception 1 of GUI_DOWNLOAD) while assigning

  • McAffee installation should not be in default, do you agree?

    My suggestionn is not having it checked by default, since many users could accept it without knowing (by not observing the checked box, while trying a fast installation). And as many have another antivirus installed already, having both will be a mes

  • Host preferred credentials suddenly not working

    Windows 11GR2 on Windows 2008 64 bit For some reason I am getting failures in dbconsole, I double check all my host credentials etc., part of dba groups, part of log on as a batch job etc. are all ok. Everything was working fine. Now I try to clone t

  • Monitoring using Openview

    Does anyone monitor their appliances using openview? If so, how?

  • Missing variable

    Hi Guys, I'm using an infoobject in both an infoset and a multiprovider. I've created a variable in one of the queries, and want to add that same variable to another query. It is however not showing this variable in the query designer! Any ideas why