PO in backend classic scenario

Hi experts
I am triing to create Po in backend from a catalog shopping cart but an error occur ERROR CREATING SUBSEQUENT DOCUMENT`
But no log that help me to solve the problem are displayed.
Im PPOMA_BBP the users have BSA atribute ECPO.
IN Define Number Ranges per Backend System for Follow-on Documents For backend (PO) and for SRM (PO)
In Define Objects in Backend System (Purch. Reqs, Reservations, Purch. Orders) Always external and PO or PR
In Define Sourcing for Product Categories NEVER CARRIED AUT
Where can I find a log  to solve it?
Nilson

Hi. Is that all it says in the application monitors or RZ20?
You can try and resubmit using function BBP_REQREQ_TRANSFER and see if that creates a more meaningful error.
If you do not get anything that makes sense in the application monitors or RZ20 then you should raise a message with SAP.
Regards,
Dave.

Similar Messages

  • Urgent ! Purchase Requisition not created in Backend Classic Scenario

    Hello All,
    I am implementing the classic scenario SRM 5.5. We have replicated the material form the backend to SRM system. Also we have made the necessary config such as maintain backend system, Define Backend System for Product Category, Define Number Ranges for Shopping Carts and Follow-on Document, Define Number Ranges per Backend System for Follow-on Document. Now the problem i am facing is that in the dev system SC with line item with desc and the product (material replicated from backend) as line items are created and their PR is created in the backend. However the same is not happening in the QA system. Only those SC with line item as Desc/text only are created in the backend and those having have product id dont transfer to create PR in the backend. There is no message in the RZ20, SM13, ST22, SM21 etc. Alsowhen i try to tranfer it using the FM BBP_PD_SC_TRANSFER it is created successfully and there is entry in BBP_DOCUMENT_TAB which is cleared afetr clean_reqreq_up is run. I am not sure whats is going wrong. Please help me out guys.
    Thanks
    Karthik

    Hi Andy,
    Thanks for the quick responses. I dont see any PR doc no and neither the BUS object type in BBP_PD item details. Please see the o/p below
    BE_LOG_SYSTEM                R3QAS400
    BE_OBJ_ITEM
    BE_OBJECT_TYPE
    BE_OBJECT_ID
    BE_REFOBJ_TYPE
    BE_REFOBJ
    BE_REFOBJ_ITEM
    BE_REFOBJ_SBITM
    BE_REFOBJ_TYPE2
    BE_REFOBJ2
    BE_REFOBJ_ITEM2
    BE_REFOBJ_FYEAR2             0000
    BE_STGE_LOC
    BE_PLANT                     IE01
    BE_BATCH
    BE_VAL_TYPE
    BE_MOVE_REAS                 0000
    BE_EXPERYDATE                000000
    BE_PUR_GROUP                 440
    BE_PUR_ORG                   IE01
    BE_CO_CODE                   IE01
    BE_DOC_TYPE                  EC
    BE_ACCREQUIRED
    BE_SP_STK_IND
    BE_INFO_REC
    BE_MOVE_TYPE                 101, so i am not sure what could be going wrong.
    Is there any way i can debug it and find out what the cause is,
    though the calls to the bapis are asynchronous. Also just for the reference sake my backend is 46C. I have been grazing through the notes but haven't found a substantial one.

  • POR transferred into MM(Backend) system in Extended Classic Scenario

    I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9 
    As we are successfully send PO from EBP to SUS.
    Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
    Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
    As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
    Please tell us, Provided Solution will  be really appreaciated.
    Thanks.
    Regards,
    Pawan Keshwani

    hi,
    Pls see the foll notes:
    Note 576349 - Terms of payment in the ECS
    Note 541934 - Modification note: Copying base date from T052
    Note 953999 - ECS: Terms of Payment values not in PO header
    <b>Note 940453 - Backend payment term data not updated in the extended PO
    Note 945018 - Incoterms data not transferred to the back end</b>
    BR,
    Disha.
    Pls reward points for useful answers.

  • 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

  • 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

  • Number of document created in th backend in the classic scenario?

    Dear Experts,
    Could you please tell me the number of document and its details created in the ECC backend in the below cases?
    1. Case 1:
    Define backend objects:Purchase requistion created if no stock available.
    Is it correct that the system will create two documents here? The first document will be Purchase Requisition
    ( from the classic scenario) and then a purchase order has to be triggered manually from the PR?
    2. Case 2:
    Define backend objects: Purchase Order if data complete, otherwise Purchase requisition.
    Here, if all the data are complete and the system directly creates Purchase Order in the ECC backend system. From the shopping cart in SRM, one can see only ECC backend purchase order, no purchase requistion. If i check the Purchase Order in ECC backend system, I donot see any purchase requistion with reference to the Purchase Order.
    Could you please help here? What are the number of documents created here? It is one or two (both purchase requisition and Purchase Order).
    Is it not a violation of standard classic scenario if only one document is created?
    Thanks and regards,
    Ranjan

    Hi,
    In other words in the shopping cart is approved
    1) If the source is assigned  -It will create a P.O in  the backend  (Classic)
    2) If the source is NOT assigned  -It will create a P.R in the backend (Classic) .. you have to assign a  source
    Regards
    G.Ganesh Kumar

  • PO output for Extended classic Scenario from the R/3 backend

    Hi,
    1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
    Regards,
    DV

    Hi Anil,
    We are working on extended classic scenario with SRM 5.0 & ECC6.0.
    Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ". 
    Please send the related document to [email protected]
    Thanks in advance
    Ashutosh

  • Extended classic scenario - no backend PO created

    I try to activate the extended classic scenario. It's not activated in customizing, tried to do it only with BADI implementation for special material groups. We are able to create POs in SRM but transfer to backend doesn't work.
    I get following error messages in application monitor as backend application errors:
    No instance of object type PurchaseOrder has been created. External reference:  
    PO header data still faulty  
    Document number 100000093 not within defined inter val  
    What's going wrong here?
    Hubert

    Hello,
    Check if you have set up the customizing as below:                                                                               
    Extended classic scenario:                                                                               
    a) at SRM side:                                                                               
    - To assign the transaction type to the extended classic scenario you have to maintain the transaction type name (= the R/3 PO document type) to the attribute DP_PROC_TY (in contradiction to BSA in classic scenario) in PPOMA_BBP of the responsible Purchazing group.                                           
    - Create a number range for a local PO.                                                                
    - Assign the local PO number range as a internal numer range to the transaction type.                                                                               
    b) at R/3 side:                                                                               
    - Enter the Number Range (corresponding to the SRM number range PO) and flag it as an external number range (trx. OMH6 Number Range for Purchasing Documents)                                                                               
    - Maintain the document type corresponding to the SRM transaction type and assign the R/3 number range for POs as "NoRge Ext" (field V_T161-NUMKE) (trx. Document type within Purchase Order Customizing)                                                                               
    - Make sure that the SRM and R/3 number ranges match are exactly the same.
    Kind regards,
    Ricardo

  • SRM table for backend PO & PR no. in Classic scenario

    Hi All,
    We are in classic scenario.
    I need the table/view name which stores the PR and PO no. created in the backend system.
    I could find different view names for PO,PR nos. from BBP_PD but is there any single table/view which stores this data ?
    Any other table names will help.
    regards,
    Sambit

    Muthu,
    Appreciate your speedy response.
    I found your answers helpful. Though the table didnt meet the requirement I have awarded you the points as it was helpful.
    I'm not sure why but the BBP_PDBEI table should fetch the data when Bus. object type BUS2012 as suggested by you. But it only fetches the SRM POs created directly not the R/3 standard POs. I mean the table fetches "EBP PO" document type not the "R/3 PO" created directly in the R/3 backend system.
    Thanks,
    Sambit

  • Output(print out) in SRM for backend PO in Classic scenario

    Hello,
    My requirement is to take print out for the backend PO created thru shopping cart in classic scenario.
    i know for extended classic scenario Actions works as in that case PO is created locally and then replicated.
    But in the classic Scenario where the PO is in backend, can we take print out in SRM becasue the detials of that Po is available in SRM to in Fllow up documents in SRM 5.0.
    is there any standard way available to achieve that.
    Thanks
    Robin

    Hi Sarabjeet,
    It does not make sense to print PO from SRM in classic scenario because there is no PO in SRM at all !
    In classic scenario, PO is created only in the backend.
    Only shopping cart is created in SRM.
    Kind regards,
    Yann

  • SUS / no goods receipt doc to backend  in extended classic scenario?

    Hello
        have you any find  a solution for problem
        in SRM/SUS and goods receipt in extended classic scenario. Gr remains  only in SRM not going to backend...
    Brg Harri
    Message was edited by: Harri Harkonen
    Message was edited by: Harri Harkonen

    Hi Christophe,
    We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
    I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
    The goods receipt is posted in backend this way.
    Unfortunately we are not able to cancel or make a return delivery on this GR.
    I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
    Thanks in advance.
    Rgds,
    Martijn

  • Extended Classic Scenario not creating backend PO

    Hi All
    We are just starting with SRM (Using SRM 5.0 SRM Server 5.5) and trying to decide to use Classic or Extended Classic.
    I can get the Classic working were an approved SC creates a backend PO without any problem. However when I switch on Extended Classic the backend PO is not created from an apporved SC.
    In RZ20 my error is Shopping cart 1000000080 (PReq. ): BBP_BD 002 Buffer table not up to date and Table BBP_DOCUMENT_TAB is empty
    In config I activated the extended classic scenario as well as activating the backend purchasing groups as responsible. Under sourcing I also defined for the relevant product categories as "1 - Sourcing Never Carried out"
    Am I missing something obvious??
    Many thanks for any help.
    Daniel

    Hi Daniel,
    In reference to the info. you have provided, it looks like you have not switched to Extended Classic Scenario properly.
    Once you say you are on ECS, the P.O should get created in SRM and the copy of it should get replicated to R/3.
    As you said you have flagged both the check boxes in SPRO for ECS activation, try activating sourcing also.
    SPRO > IMG > SRM > SRM Server > Sourcing > Choose one Product category for which you want to create shopping cart and set the setting as " Sourcing Always carried out".
    Check whether the approved shopping cart is coming to Sourcing cockpit or not.And from there try to create a P.O by assigning vendor.
    Also ensure that no BADI is activated which converts ECS to Classic scenario for the Product category you have choosen.
    If this cycle woks then definitely what you require will also work.Clarifications are welcome.
    Award points for helpful answers.
    Rgds,
    Teja

  • Classic scenario: Update shopping cart with changes in backend PO?

    The Shopper would like to have visibility in their shopping cart (SRM 5.0, classic scenario) of changes made to the follow-on PO created in ECC6. Is it possible for the cart to be updated with changes made to the backend document, or would the customisation for this type of request be too complex?
    Any advice would be appreciated, thanks!

    Hi,
    Yes this report is reading the PO quantity and value and the history tab for follow-on documents such as GR or invoice.
    Thus the SC history is updated.
    Kind regards,
    Yann
    Message was edited by:
            Yann Bouillut

  • SRM 7 : Vendor record replication in backend with Extended Classic Scenario

    Hello,
    We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
    Can you explain what is to be configured to get the new vendors replicated to the backend?
    Thanks in advance.

    Hi,
    It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
    Check the below link for more details:
    http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
    Regards,
    Sanjeev

  • Direct materials in classic scenario - any restriction in backend?

    Dear SAP gurus,
    I have read that when we use classic scenario, procurement for direct materials actually using extended classic. But as per SRM 7 EHP 2 the true classic PO (leading PO in ECC) now possible.
    I just want to confirm is there any restriction in the backend side? E.g what is the minimum version of ECC that we should use for this scenario?
    One more thing, I assume that in classic scenario we can have SC or external requirement goes to Sourcing Cockpit, and then we can proceed to create RFx or Auction from here rite? From here, I assume we can create PO from the response and it will create directly in ECC. is this correct?
    Best regards,
    John

    Hi Ramki,
    thanks for the confirmation. one more thing, can we setup different po type in classic scenario when we're creating po from rfx response? as i understand we can only setup one number range for po backend in srm config, so what should i do if i want to specify that user can chose the po type that they want to create in backend as a follow on from rfx response?
    best regards,
    john

Maybe you are looking for