Classic Scenario PO release

Hi guys,
We have clasic scenario where the PO is created only in the ECC, How the PO release is handled?? whether the any customization exist for auto release the PO once it is created in ECC box or we have to do it in some BADI or user-exit???
regards,
Prabhu

Hi
it purely workflow business stratergy
for example
create a shopping cart with fixed souurce of supply like contract so business would have decided no approval is required since no BUYER intervention is required for further PO processing and directly send it to the vendor.
create a describe procurement with valid contract . here Workflow get s trigerred since how much is the value of Purchase order so release startatergy is applicable for approving the Purchase order or BUYER csn evaluate what exactly he require and delivery date updates and some docuemntation for justification of this PO.
Muthu

Similar Messages

  • 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

  • Contract Creation in SRM 7.0 classic scenario

    Hi All,
    We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
    Question is  -
    1)  Can we  create  contracts in SRM 7.0 Classic scenario ?
    2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
    3) How  we can  transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
    What are the mandatory fields required to transfer the CLM contracts contracts to ECC  outline agreement -  I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
    Rgds/Pawan

    Hi Pawan,
    Please find the answered for your questions:
    Question is -
    1) Can we create contracts in SRM 7.0 Classic scenario ?
    Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
    2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
    Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
    3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
    +Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
    +As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
    +This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
    +Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
    Hope this helps.
    Regards,
    Mitesh

  • SRM & SUS in Classic scenario

    Hello SRM Gurus,
    I would be great if you could give your overview for below my quires.
    I have good idea of SRM with SUS for extended classic scenario.  But how would be the communication between SRM and SUS in Classic scenario. Because the PO will be created in backend.
    Now my question is in Classic scenario,
    What is the use of SUS in classic scenario?
    How the PO will be transfer to SUS system? Does the PO data from SRM or ECC?
    What is the communication data between SRM and SUS?
    Kindly provide me above information and also your thoughts.
    Thanks.
    Regards,
    Magesh.

    Hi Mahesh,
    If you are using SRM7.0 & ECC EHP4 version with classic scenario then you can user configuration gudie "Plan-Driven Procurement with Supplier Integration: Configuration Guide" (Release SRM4.0).
    But following keys points are to be noted for SRM7.0:
    1. "PO" and "service entry confirmation" will be handled using XML messages.
    2. To send PO's using XML messages to SUS from ECC activate the workflow in SWETYPV transaction by falging "Linkage activated" for object BUS2012(CHANGED & CREATED) for workflow ws3800008.
    3. take the help of PI consulatant to enalbed the PI messages to send PO and Serivce confiramtion bewtween SUS and ECC.
    ERP     PurchaseOrderERPRequest_out_V1                          PurchaseOrderERPRequest_In_V1                          SRM
    SRM     PurchaseOrderERPConfirmation_Out_V1     PurchaseOrderERPConfirmation_In_V1                         ERP
    SRM     ServiceAcknowledgementERPCreateRequest_Out     ServiceAcknowledgementERPCreateRequest_In     ERP
    ERP     ServiceAcknowledgementERPConfirmation_Out     ServiceAcknowledgementERPConfirmation_In     SRM
    ERP               ServiceAcknowledgementERPCancellationNotification_Out                                                                                    ServiceAcknowledgementERPCancellationNotification_In     SRM
    With Regards
    Manjunath

  • ASN for extended classic scenario

    Hello all,
    we have SRM with extended classic scenario (EBP-MM),
    is it possible to use ASN (shipping notification) functionality in our system ?
    Kind regards,
    Arthur

    Hi
    ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
    Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
    You need to have functional background for this:
    To create an ASN against PO or SA release:
    1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
    2. dispatch vehicle no. (optional)
    3. road challan no. (optional)
    4. one more optional entry ( sorry I forgot)
    Useful related pointers ->
    Re: how does the GR get into SUS---MM-SUS Sceanario
    ASN in Extended Classic Scenario with SUS
    SUS ASN & Invoice
    The specified item was not found.
    Do let me know.
    Regards
    - Atul

  • Extended Classic Scenario

    Referring to note 963000, we are about to install SRM 5.0 as AddOn to
    Ecc ERP 2005. In SRM we would like to implement the "Exteded Classic
    Scenario", meaning the procurement process will take place locally in
    EBP and a copy of data is replicated to the beckend system (ECC).
    Is the "Exteded Classic Scenario" compatible with the "SRM as add-on"
    installation? Note 963000 sais "The following scenarios are released
    within SRM AddOn: ... Self service procurement (classic deplyment)":
    does that mean that only the "Classic scenario" (meaning only Shopping
    cart on EBP, the rest of the purchasing process on backend) is
    available?

    HEllo,
    Only self-service scenario is supported. Means classic, extended classic and standalone.
    HTH
    Gordan
    Message was edited by: Gordan Flego
    Message was edited by: Gordan Flego

  • Questions about SRM PO in Classic scenario

    Hello All
    I have a number of questions about the SRM PO in classic scenario.
    1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
    for the same?
    We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
    Our requirement is not have an approval initially once the PO is created, but only for the changes
    2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
    for this to happen. Should SAP XI be required for this?
    3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit?
    We are using SRM 7.0
    Regards
    Kedar

    Hi,
    1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
    for the same?
    We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
    Our requirement is not have an approval initially once the PO is created, but only for the changes
    Sol: In ECC6.0 if the P.O is changed and release strategy is there in ECC6.0 then it follows the ECC6.0 Approval Route.
    2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
    for this to happen. Should SAP XI be required for this?
    XI is mandatory
    3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit.
    Once P.O is created in ECC 6.0 for the P.R in Sourcing Cockpit, cancelling/reduction will not have a updation in the sourcing cockpit in SRM.
    Eg  100 nos P.R is in SRM sourcing cockpit for which  you have createdaa P.O for 40 nos is ECC6.0
    for the remaining 60 nos PR ,you can create a P.O in ECC6.0
    Regards
    Ganesh

  • 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

  • External requirement handling in SRM using classic scenario

    Hi Experts,
    We have a requirement in Classic scenario:
    PRs for MRO / indirect materials generated in PM / PS of ERP will be transferred to SRM using WF interface for approval process.
    Upon final approval in SRM, Follow-on document PO should be created in the back end.
    The SC in SRM should have the status u201CApprovedu201D & u2018Follow-on Documentu2019 created.
    My question is SRM standard will create a PO as follow-on doc after the SC is approved in SRM. How to control this creation of PO in SRM & only approval message should be transferred to back end ERP.
    Pls provide any suggestions or inputs on technical settings / adjustments to be carried out.
    Note that we cannot use PDP scenario as SRM will be used only for SC approval process.
    Tks.

    Thanks Muthu for the reply.
    The doc flow in the link above shows that after SC is approved, it will be available in sourcing cockpit for further processing (i.e. RFX, PO etc) in SRM. Our requirement should not be allowed to create PO in SRM and it should be allowed only in back end ECC.
    SRM is used to centralize the approval process where multiple back end systems are connected. (How ever, in future follow-on docs are also created in SRM).
    Current Target steps:
    1. Create PR from PM/PS in ECC (PR status will be "In release").
    2. Transfer PR to SRM and SC will be created (SC status will be "In approval").
    3. SC will be Approved / or Rejected in SRM. (PR status will be updated to Approved / or Rejected in ECC).
    4. If approved, follow-on doc PO (manual or automatic) will be created in ECC. (SC status will be updated to EX: "PO cretaed")
    When the SC is in the process of approval, user in ECC may add new items or make changes to PR from PM/PS. After these changes, the current approval WF for SC in SRM should be cancelled and new SC is created and so on...
    Sophisticated message synchronization is required between ECC & SRM.
    Is it possible to acheave the above solution (create PO only in back end system) using the steps mentioned in doc "5082a622-7310-2c10-1a9b-ef31dd69a770.pdf" with some modifications.
    Forgot to mention the following system details:
    ERP - ECC with EhP4 
    SRM - SRM 7.0
    Thanks,

  • Activate extended classic scenario

    Hello, when I try to activate extended classic scenario to create contracts in SRM and then transfer them to R/3 I have these options:
    Extended local PO
    BE Purch Grps Resp.
    Back-end check reqd
    Back-end errors, show as error msg
    Which options may I have to select?
    Thanks in advance

    Hi,
    I think Rosa's requirement is to create a manual and local contract in SRM.  Indeed you mentioned an excellent  BADi, but my understanding is this badi gets called from the sourcing application.  I am not sure whether this gets called from the SRM local contract.  This is the help documentation I am pasting here.  It would be wonderful if this works.  See the highlighted "importing parameters" part of the following pasted one.
    Thank you,
    DV
    Determine Target System of Contract
    Use
    With method CONTRACT_LOGSYS_DETERMINE, you can control the target system determination for contracts.
    In the standard, the Sourcing application and SAP Bidding Engine create contracts locally in SAP Enterprise Buyer . With this method, you can create a contract in the backend system instead.
    Requirements
    You are using a backend system with Release 4.6B or higher.
    You have created the logical system in activity Define Logical System
    Parameters
    Importing
    The BAdI takes this data from requirements in SAP Bidding Engine (bid) or from requirements in the Sourcing application.
    IT_HEADER
    Header structures
    IT_ITEMS
    Item structures
    IT_PARTNER
    Business partner data such as vendor or location
    IT_ORG
    Organizational data
    Changing
    In the method you can overwrite the following field:
    CV_LOGSYS
    Name of the system in which a contract is to be created.
    If this field remains empty or contains the name of the local system, then the contract is created locally.
    If this field contains the name of a backend system, then the contract is created there.
    Notes
    When coding the method, use the delivered sample coding as a guide.
    See also
    BAdI Determine Backend System / Company Code

  • Does SRM 7 Extended Classic Scenario support PCards?

    Does SRM 7 Extended Classic Scenario support PCards as standard?  I know SRM 4 does not but wanted to know if that has changed.

    Paul,
    URL https://websmp208.sap-ag.de/support  ( service.sap.com) ...on header
    Go to 'Release& Upgrade Info' ..then sub item  'Release notes'....look for SAP Solutions on left scroll...then select SRM...
    Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
    Let me know if you did not get it..
    Thanks,
    Rahul Mandale

  • Extended Classic Scenario causing a dump "Buffer Table not up to date'

    Hi All,
    I could create a Shopping Cart in the Classic Scenario.
    After activating the Global settings together with the Back end groups responsible for the ECS, I have also a Badi in place for a certain Category id..I expected that for this category id if I create a shopping cart thro' the describe requirement it would create a Local PO and a replica would be generated in the Back end system.
    But  as and when I add the item to the Shopping Cart, I get an ABAP Dump indicating the buffer table not up to date and a program error "Uncaught exception" in the Program SALBBP_PDH.
    I also tried searching SAP Notes,but to vain.Working on SRM 5.0 Release level 12 and ECC 6.0 as back end.
    Any body who has faced this before, Pl give me the clues.
    Thanks & Regards,
    Nagarajan

    Hi
    it is basis consulatant responsiblity. you must take help from Basis .
    Note 26171 - Possible entry values for command field ("OK-code")
    Buffer commands:
    WARNING: Resetting buffers can significantly change the performance of the
    entire system for a long time. It should therefore only be used when there
    is a good reason to do so. As of release 3.0B system administator
    authorization is required (authorization object S_ADMI_FCD). The action is
    noted in the system log.
    /$SYNC- This resets all buffers of the application server
    /$CUA - This resets the CUA buffers of the application server
    /$TAB - This resets the table buffers of the application server
    /$NAM - This resets the nametab buffers of the application server
    /$DYNP - This resets the screen buffers of the application server
    regards
    Muthu

  • Currency issue in Local PO in SRM ( SRM 4.0, Ext. Classic scenario)

    Hello SRM community,
           There is contract exist at a Product category level which is created in currency Euro & can be used by both local as well as well global purchasing org. for subsequent PO releases( Call off).
    We are using extended classic scenario, SRM 4.0. before explaining the scenario, here is what we have maintain for a vendor in BBPMAININT
    Let say..
    Vendor(Business Partner)             Purchasing org.                     Currency
    100168                                         Global Purchasing org.     Euro
    100168               Local Purchasing Org                SEK
    Now there are two scenarios in this
    Scenario No.1
    When Strategic purchaser directly creates any purchase order release for Local purchasing org. with reference to above created contract
    & if he chooses Euro as a currency, system throws a warning message as "Currency Euro in Purchase order is different then the PO currency SEK of vendor.
    but still he manage to order the PO Euro.
    Scenario No.2
    If strategic purchaser creates shopping cart for local purchasing org. where S/C currency is Euro & assign above contract as a source of supply.
    Local PO gets created but the system swaps the currency in PO automatically to SEK which is nothing but the currency available for Vendor/Pur. Org combination
    in BBPMAININT.
    Why there is this difference in behaviour.
    I mean, when you directly creates a PO release wrt contract, system allows you to select currency other then the one maintain in BBPMAININT for Vendor/PUr.Org combination however if you try to create a SC for Local pur. org  with contract as a valid source of supply then system overrides the SC currency with the currency maintain in the BBPMAININT for  Vendor/PUr.Org combination
    We would like to know if there is any way possible by which we can maintain SC currency in PO & should not allow system to
    swap it with what is being maintain in Vendor/Pur.Org combination in BBPMAININT.-
    is there any Badi available where we can change this behaviour..& if poosible a way of approach to do it through Badi....
    Any help is well appreciated with full rewards to valuable suggesation.
    Regards
    Bharat Morajkar

    Hi Bharat,
    You can use the BADI <b>BBP_DOC_CHANGE_BADI</b> to make changes to the document, after user entry and before saving the document to the database.
    BBP_SC_CHANGE method can be used for changing shopping carts.
    Hope this works in your case. Try it and let me know.
    Rgds,
    Teja

  • 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.

  • 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

Maybe you are looking for