Creation of PO in Classic scenario.

Hi
i am using classic scenario.my problem is i have created shopping cart&approved.after approving this PR had been generated.
ok. now i want to create PO,GR &Invoice with PR.but i could not create with PR.
so please suggest me How to create PO, GR, Invoice with PR in Back end?
OR
Are these created automatically without PR in Backend?
could any one suggest the process.
BR
sss

Hi
This control settings available in SRM
SPRO
cross apllication settings..
Define  Objects for Backend System
check this settings for your material group w.r.t external procurement.
is it PO creation or PR generate settings?
Is your Shopping cart has a valid source of supply.
if your cart is incomplete , PR only created, so check it up.
br
muthu

Similar Messages

  • How to know which BAPi is being used for creation of PO in classic scenario

    Hello Experts,
    We are in SRM 7.0 classic scenario.
    How can we know which BAPI is being used in the calssic scenario i.e. How can we know if we are usind BAPI_PO_CREATE or BAPI_PO_CREATE1 for creation of PO?
    Any pointers will be highly appreciated.
    Thank you in advance,
    Thanks & Regards,
    RKS

    Hi RKS
    yesterday BLOG by our SUMMER WANG helps every SRM consultant to debug the PO error
    /people/summer.wang/blog/2010/05/11/trouble-shooting-of-srm-po-transfer-error
    Good work Summer wang !!
    Muthu

  • PO Creation Process in Classic Scenario

    Hi
    I want to understand the exact PO creation process in a classic scenario. Once the buyer clicks on 'Create Purchase Order' in the SOCO, what are the series of steps that are triggered till the PO number gets displayed in the SOCO screen?
    I assume that the shopping cart has all required data and ready for PO creation.
    With Regards
    Sathya

    Hi,
    The shopping cart is created and approved in SAP Enterprise Buyer. The remainder of the procurement process takes place in the backend ERP system(s) and all other follow-on documents, such the purchase order, goods receipt/service entry sheet and invoice, are located there. With SAP Supplier Self-Services, you have partial supplier involvement for the operational procurement business scenarios when buying materials. There is no support for services.
    Shopping Cart
    SAP Enterprise Buyer
    Approval
    SAP Enterprise Buyer
    Purchase Order
    Backend system
    Goods Receipt
    Backend system (can be pre-entered in SAP Enterprise Buyer)
    Invoice
    Backend system (can be pre-entered in SAP Enterprise Buyer)
    Please award the points if it helps.
    BR,
    Vijay Mittal

  • Creation of Inbound delivery mandatory for ASN process in classic scenario?

    Dear Experts,
    We are going for classic scenario for our green field SRM implementation process. Our client is not using  ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
    Is the below the process correct?
    PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
    Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
    Could you please comment on the above process? Could you please suggest the best practices followed here?
    Thanks and regards,
    Ranjan
    Ranjan Sutradhar

    Hey Ranjan!,
    You are on track.
    The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
    Regards,
    Nikhil

  • SRM PO creation classic scenario

    Hi,
    I have some requirements & need direction
    Scenario#1
    Classic scenario: SC created for multiple lines with multiple product categories. This fetches corrosponding P Groups based on the config. When PO is created it creates multiple POs based on P Groups. We need to create single PO out of this SC by passing a dummy P Grp while PO creation
    Scenario 2 #
    Same example but all the product categories are same so there will be one P Grp passed on while PO creation. However, we need to pass a dummy P Grp while PO creation. Ideally in this scenario system would have created single PO but we need to pass this dummy P Grp. In short any PO generated out of SRM will have same P Grp. We dont want to touch current config & need development
    Scenario 3#
    SC -PO scenario. SOurced SCs. Once SC is approved, it will create PO as a standard functionality. However, we want to hold Po creation & subsequently run a batch job which will collect all SC approved during some period say 3 Hrs & group them based on vendor & plant & create POs accordingly.
    Example:
    Sourced SCs
    SC-1 with vendor 123456 created for qty 100
    SC-2 with vendor 999999 created for qty 200
    SC-3 with vendor 123456 created for qty 100
    We need to create 2 POs grouping first & third in one & create another PO for SC-2
    Please advise
    arjman

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • Purchase Order Creation, Extended Classic Scenario

    Can someone please explain the different databse tables affected during the creation of a Purchase Order.
    Also, is there a transaction with which we can create PO in Extended classic scenario?

    hi,
    below are the tables effected while creation of PO:
    CRMD_ORDERADM_H
    CRMD_ORDERADM_I
    BBP_PDIGP
    BBP_PDBEI
    BBP_PDISB
    BBP_PDISS
    BBP_PDSDLN
    BBP_PDACC
    BBP_PDTAX
    BBP_PDATT
    BBP_PDORG
    BBP_PDWGT
    BBP_PDDYN
    BBP_PDEXR
    PRCD_ITEM
    PRCD_COND
    PRCD_COND
    BBP_PDDEP
    CRMD_PARTNER
    as far as your second question is concerned normally we will be creating a PO in SRM/EBP in web browser and it will replicate to the backend ERP.
    regards
    IGA

  • 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

  • :):(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

  • 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

  • PO creation problem with classic scenario

    Hi All,
    We are in SRM 7.0 nad have mapped extended classic scenario. Now we want to map the Classic scenario only for a specific company code. So, my question is can we map the classic scenario on company code specific.
    I tried maintianing the document type & number ranges in R/3. Maintained the number ranges & transaction type in SRM.
    Also implemented BADI BBP_EXTLOCALPO_BADI.
    But after creating the SC the status is "Approved" but no PO getting created in ECC. On observing RZ20 there is an system error for the number ranges.
    Please let me know if I am missing some steps.
    Thanks in advance.
    Regards,
    Abey.

    HI,
    Make sure the PO number range in ERP is same in SRM. Also have the external checkbox checked for PO number range in ERP.
    Also have the same transaction type in SRM and ERP. Where the ERP transaction type should have external number range as the above mentioned profile.
    Regards
    Sam

  • Extended Classic Scenario, BADI for PO creation in R/3

    Hi,
    We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
    1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
    2) After implementing the BADI, do I also have to change the BAPI?
    3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
    Thanks and Regards,
    Peter

    Hi Peter,
    1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
    Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
    2-If you use the tracking number field, no use of R/3 BADI is required.
    3-BAPI_PO_CREATE1
    Please check my answers in this post :
    catalogid field not going in R3 backend
    Kind regards
    Yann
    Message was edited by: Yann Bouillut
    Message was edited by: Yann Bouillut

  • Shopping Cart and PO creation - Classic Scenario

    Hi,
    SRM 5.0 - Classic Scenario
    User U-1 is under the company code C-1
    Shopping Cart SC-1 has been created successfully for the Product Category PC-1
    Product Category PC-1 has been assigned to Purchasing Org. POrg-1
    <b>Question 1)</b>
    But back-end POrg-1 has NOT been assigned to Company Code C-1. What will happen to this SC-1 ? Will the PO be created ?
    <b>Question 2)</b>
    Next....Vendor V-1 has been assigned as Source for the Shopping Cart SC-1.But Vendor V-1 has NOT been extended to the Purchasing Org POrg-1. But it has been extended to the POrg-2.
    Will the above SC-1 will be converted as PO ?
    Please help. Currently I am doing blueprint. I don't have the system to do the above test.
    With regards,
    Pranav

    Hi Pranav,
    Here are answers to your questions;
    Question 1)
    But back-end POrg-1 has NOT been assigned to Company Code C-1. What will happen to this SC-1 ? Will the PO be created ?
    <b>
    Sundeep: No, This PO will be in "Error in Transmission" with a backend application error for a PO. Same as trying to create it directly in ECC, it will error</b>
    Question 2)
    Next....Vendor V-1 has been assigned as Source for the Shopping Cart SC-1.But Vendor V-1 has NOT been extended to the Purchasing Org POrg-1. But it has been extended to the POrg-2.
    Will the above SC-1 will be converted as PO ?
    <b>Sundeep: No, it is same as trying to create a PO in ECC directly, it will not allow you to create it. Also this scenario is not practical, as in reality, when you replicate vendors from a backend, it will replicate all Porgs that the vendor is created with, hence this scenario concern is ruled out !</b>
    Thanks,
    Sundeep

  • Creation PO in classic scenario in backend

    Hi,
    I'm in classic scenario with plan driven. I'm using SRM 5.5
    I'm using bid engine and i'd like to create a PO in backend directly from a bid.
    What do I need to get it?
    thanks in advance
    Best Regards

    Hi
    As per this SAP OSS Note 762223... you can try this out..
    <u>I guess this OSS Note, will be applicable to SRM 550</u>
    Releases
    Software
    Component Release From
    Release To
    Release And
    subsequent
    SRM_SERVER 500 500 500  
    SRM_SERVER 550 550 550  
    BBPCRM 4.0 400 400
    You can try this out.. Hope this will help.
    Regards
    - Atul

  • PO error - extended classic scenario

    Hi Guys,
    I'm using SRM 5.0 with extended classic scenario...
    During creation of the purchase order locally (in SRM) I got the "error in process" status.
    My means of T-code RZ20 I got the following info to ithis error:
    context:B2B Procurement
    object name:Purchase Order
    short name: Backend application errors
    status: Active
    Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
    using Transaction BBP_PD I got the following status:
    Status: I1080
    Description: in transfer to execution system
    Do you have any idea what should I do in order to resolve this outstanding issue?
    many thanks in advance for your help.
    regards,
    Piotrek

    Hi
    Go to transaction - <b>SPAM</b> to get all the required Patch levels and other required system version details.
    <b>Meanwhile, try the following SAP OSS Notes as well -></b>
    <u>Note 508972 - Error during transfer of extended purchase orders
    Note 881650 - Duplicate transfer/output of the purchase order
    PO status in " error In Process ".
    Error in Transfer Process (Urgent )
    FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)</u>
    Hope this will help.
    Regards
    - Atul

  • PO not generated at backend in classic scenario

    Hi,
    I am working with SRM 5.0 in classic scenario.
    1) I have defined No. ranges for SC and follow-on documents in SPRO. No. range PO is defined for backend (classic) POs. (Checkbox -External is not marked)
    PO - From 3005000000  to 3008000000
    2) I have assigned this no. range PO to document type 'EC' (Pur Order) as external no. range
    3) No. range PO is also defined at R/3 backend for Purchase Orders (checkbox 'External' not marked)
    PO - From 3004000000 to 3009999999
    4) This no. range is assigned to doc. type EC as Internal no. range in R/3 backend
    Now, when I am creating a SC in SRM and ordering it, it is causing an error in creation.
    I see the following description in Admin login:
    Shopping cart 6500005899 (PO 3005000532): BAPI 001 No instance of object type PurchaseOrder has been created. External reference: 
    PO no. 3005000532 is picked from no. range PO defined in SRM.
    But, in SC screen, I do not see any follow-on documents.
    When I check BBP_PD, I find following data:
    BE_OBJECT_TYPE    ->  BUS2012         -> Follow on Document Object Type in backend system
    BE_OBJECT_ID      -> 3005000535       -> Follow on Document Object ID in backend
    (However, this no. belongs to no. range PO defined in SRM. At the backend, the PO no. range starts from 3004000000 to 3009999999)
    BE_INFO_REC    -> 5300002566
    Also, I can see two lines highlighted in Red under Stats:
                           Status                            Description                 Inactive
    HEADER          I1015                         Awaiting Approval                X
    0000000001      I1111                    Item in Transfer Process           X
    My doubt is that ,
    a) Why system is picking PO# from SRM no. range (3005000535) and showing it as backend object ID?
    b) When system is able to fetch the Info record information from backend, why the PO is not getting generated at the backend?
    Why there is an error in transmission of PO?
    Please help.
    thanks

    plz see Peter instructions in this thread
    SC: Error in transmission BAPI 001
    regards
    Muthu

Maybe you are looking for