Printing of PO in Extended classic scenario

Hello,
Normally the PO print spool gets deleted after 14 days.how do I reprint a PO if reqd after 14 days.PO is not editable in extended classic scenario. so not able to do any change in messages of PO.

Hello,
Any soln for this??
Edited by: JJJ J on May 9, 2009 8:59 AM

Similar Messages

  • Extended classic scenario - PO print output

    Hi all,
    Please help me. We have SRM 5.5 (SAPKIBT11) the extended classic scenario.
    Could you please tell me Can I print the PO from Web GUI?
    If in the Web GUI Output area in PO I set indicator Printer, and to set in Output Pushbutton, in Log I have status - Successfully processed. In trx SP01 the spool status - Compl. But the PO smartforms don't print.
    PS: from Output Preview button I can to print the PO smartforms, but I need to print from  Output area through the Output Pushbutton. (in the trx BBP_POC or BBP_PPF).
    Best regards
    Guzal.

    Hi, Masa,
    Thank you for your advice,
    I set the method U:Print Using Berkeley Protocol, after that
    in  trx. SP01 I have the Error Status on Composite Document -
    Status Incorrect (Reason Unknown).
    Best regards,
    Guzal.

  • Extended classic scenario and printout in ERP

    Hi,
    we want to use extended classic scenario but the printout of the PO should happen in the backend system. PO is already created in the ERP system but I can't change it (as designed). How is it possible to create the printout from the backend?
    Thanks
    Hubert

    Hi Hubert
    This consulting note is for triggering Output of PO from ECC instead of SRM. Printing can happen from ECC if you can switch off PO Output form SRM and start triggering the same from ECC as per consulting note.
    Try working with this FM In SRM BBP_OUTPUT_PO_PRINT_REMOTE for printing the PO, if PO Output is still required to be triggered from SRM.
    Regards
    Virender Singh

  • Extended Classic Scenario - PO Update issue

    Hello experts.
    We are working with SRM 5 in the extended classic scenario and we have a serious problem in a productive environment for the following case.
    (01) We create a purchase requisition (PR) in R/3 with several items;
    (02) We send PR to the SRM generating a shopping cart;
    (03) The buyer creates a PO for all items from the shopping cart;
    (04) The PO is transmitted to R/3;
    (05) For some cases buyer changes the PO wich is sent back (updated) to R/3;
    So far so good. The problem happens when some item in the request already has GR or Invoice. In those cases when the PO is updated on SRM, its transmission to R/3 does not occur, generating an error log that can be seen in transaction RZ20 of SRM.
    I understand that if any GR or Invoice exists for the item it can no longer be modified, but is it expected that no other item can also be modified from SRM? What is the expected behavior for this case?
    Moreover, even if the GR and Invoice have been canceled, we are still unable to update the PO in R/3 from SRM. Is this a expected behavior? It was our understanding that the PO should be updated if all incoming documents (GR, Invoice, SES ..) were completely canceled.
    We appreciate any help on this matter.
    Thanks and Regards,
    Evandro Miasato

    Hi, Masa,
    Thank you for your advice,
    I set the method U:Print Using Berkeley Protocol, after that
    in  trx. SP01 I have the Error Status on Composite Document -
    Status Incorrect (Reason Unknown).
    Best regards,
    Guzal.

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

  • Error while creating Manual Service PO in Extended Classic Scenario

    Hi Experts,
    Extended Classic scenario (SRM 7.0 with ECC 6.0)  While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
    Error Msgs:
    1. Backend Error:In case of account assignment, please enter acc. assignment data for item
    2. Backend Error:Purchase order still contains faulty items
    Regards,
    Mohan

    Hi,
    Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
    Pl do the needful
    Regards,
    Mohan

  • 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 text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

    Dear experts,
    My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
    Is it normal?
    Do I need to customize something?
    Can it be achieved by BADi? How then?
    OR is it only possible from SRM 5.0?
    Thanks in advance
    RD

    Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT,  and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
    Note: if this BADI is not present, use BBP_CREATE_PO_BACK
    Regards, IA

  • No GR on Confirmation Approval in Extended Classic Scenario

    Hi all gurus out there,
    We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
    We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
    Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
    Cheers!
    Siow Fong

    Hi Guys,
    I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
    Regards
    Siow Fong

  • Problem in Extended Classic Scenario related to PO

    hi,
    we are using Extended classic scenario in our client. User has created a SC .when we are going to create a PO system is showing an error Purchase Group B01 does not exist.
    This Purchase group is not created in R3 or neither replicated to SRM.and it is not assigned in the Org structure.
    Kindly Let me know from where the purchase Group might be Picked apart from the org Structure.
    regards
    subhash

    Hi
    Can you check your SC how this Purchase group picked form your basic data ?
    since this purchase group is existing in srm thats why it picked while create sc right?
    regards
    Muthu

  • 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

  • Freight is not updated in R/3 in the Extended Classic scenario

    Friends,
    Freight is not updated in R/3 in the Extended Classic scenario.
    Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
    We have created a condition for Freight (Value and Percentage)in Create
    Payment Conditions using the following menu path:
    spro
    --> Supplier Relationship Management
    --> SRM Server
    --> Cross-Application Basic Settings
    --> Pricing
    --> Process Payment Conditions
    When creating a Purchase Order in SRM in the "Item Data" tab, there is
    a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
    from the drop down menu. Here Freight is available. Add Freight and
    the PO record in SRM is updated with the Freight Condition. However,
    upon ordering, the Freight condition does not transfer to the PO
    recordin R/3.
    We've heard this can be achieved by enhancement: only ie by implementing
    set of BADIs..  But does anyone know WHICH BADIs we need?  Or how we could find out?  Thanks.

    Hi
    <b> You can either of these BADIs to handlwe the scenario.</b>
    BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
    BBP_CREATE_PO_BACK   OLD Exit while creating a PO in the backend system     
    BBP_ECS_PO_OUT_BADI  ECS: PO Transfer to Logistics Backend                  
    BBP_EXTLOCALPO_BADI  Control Extended Classic Scenario  
    Hope this will help.
    Please reward suitable points.
    Regards
    - Atul

  • 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

  • Extended Classic Scenario - Free Items?

    Does SAP support PO's in Extended Classic Scenario with a zero price (free items)? 
    My client is switching from classic to extended classic scenario and they require to be able to creaet PO's that have a zero price like they have in the classic scenario.
    We are currently getting an error that we need a price with the IR flag, but I would expect the system to automatically unflag the IR flag for a free item?

    Hi Jay,
    Thanks for your response.  There are two problems with your soluiton.  First the shopping cart doesn't have the IR flag on it and can't be changed by the user and we have PO's created directly from SC's and go out to the vendor.
    Second, In extended classic scenario it apprears that the system doesn't allow you to change the ir flag on the PO and make the cooresponding change in the ERP PO.

  • Switch from classic to Extended Classic Scenario- Impact

    Hello,
    We are proposing to switch from Classic to Extended Classic Scenario.
    We are on SRM_SERVER 550,Sp7 and SAP 4.7 backend.
    We want to know if this is technically feasible to switch and have less/no impact on existing transactional data and master data.
    Main concerns are: Existing open Shopping carts and PO's.
    We are also modifying the WF by including buyer completion WF.
    Will the carts created in classic scenario and 'awaiting approval' work similarly in ECS?
    Can we copy old carts (created in classic scenario) into new ones in ECS?
    Are there any other issues like the ones above which people have come across?
    Is there any standard SAP material/Consulting note available
    which gives some guidelines for switching scenarios?
    Regards,
    Srivatsan

    Hello,
    You can switch from the classic to the extended classic scenario by making the global settings in the IMG.
    But it would be better if you can decide if only a particular set of categories need ECS.
    If you wish to have both the scenarios,the deciding factor is the product category.
    You can also activate a  BADI for the control of ECS despite the above Global settings.
    Reward if answer is helpful,
    Thanks & Regards,
    Nagarajan

Maybe you are looking for