Overdelivery tolerance - extended classic

Hi all,
We have extended classic scenario, and would like to have overdelivery tolerance.  I've created a tolerance group in SRM, and assigned tol keys CF, DA and DQ. 
I've also maintained a Purchasing Value Key in ECC via OMQW (SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
When I post the confirmation in SRM I get the appropriate error message (so if I try to post 106 for a PO with 100 qty, I get the error message, 105 is OK).
However, the IDoc goes into error in the backend, as the qty is exceeded.  Error message: "PU Ordered quantity exceeded by 5 EA : <PLANTCODE>"
When I look at the PO inside SRM, in the item detail the overdelivery tolerance is 0%, and the ECC copy also has 0%.  I would have expected them both to show 5% (and for this to copy-into the PO)?
If I create a new 'spot PO' directly in ECC (ME21N) with all the same detail, the 5% tolerance is coming through automatically from the OMQW setup.
Do you have any ideas how to get the overdelivery tolerance into the SRM PO, so that the copy in the backend would also show it (so IDOC will post successfully)?
Thanks in advance,
J

Hi,
I have a similar problem.
I have assigne a tolerance group in ppoma_bbp, but the purchasing group is not defaulted into the PO,
Therefore the % on the PO is 0, which leads to an error message when i hit check on the confirmations in SRM, even if I am within the tolerance limit.
Also when i try to search for the tolerance group on the PO it won't display.
If I update the tolerances the manually ont he PO the i am able to create an overdelivery.
We are on the same release ECC 6 EhP 4 and SRM 7.0 SP 9, extended classic.
Could you please update how you solved the issue?
Cheers
Ulrike

Similar Messages

  • Tolerance key DQ in extended Classic scenario give Backen error message

    Dear all,
    I am using SRM 7.0, SP 9 
    Extended Classic Scenario.
    I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
    I also set up the ECC tolerances:
    - Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
    And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
    - And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
    And even with this set up I still get the error message
    u201CBackend Purchase Order quantity exceeded by 1 EAu201D
    when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
    What Configuration am I missing?
    Cheers
    Ulrike

    Dear Rahul,
    Thanks for you input
    Let me give you an example of the behaviour:
    in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
    User orders a PO  with quantity=1000, price $100;
    No additional tolerances assigned in the PO itself
    User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
    In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
    So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
    But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
    Cheers
    Ulrike

  • Tolerances in SRM extended classic scenario

    Hi all,
    I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
    We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
    We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
    However, whenever we try to confirm more than PO quantity, we get an error message. “PO Ordered quantity exceeded by 1 EA“
    It seems so that SRM has a ‘double’ tolerance check
    • one in SRM against defined tolerance (via attribute TOG)
    • one in R/3 against the PO tolerance
    Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have PO’s without a material master. Are there any possibilities to skip the PO tolerance check?
    Thanks for your help,
    Martina
    Edited by: Martina A. on Jan 15, 2008 1:13 PM

    Hi
    Depending on the SRM version you are using, Please go through the links, which will definitely help ->
    Condition Type SRM - ECC
    Tolerance in SRM and ECC (BE R/3)
    Tolerance
    Re: SC Budget check without SAP Fund Mgmt
    TOG parameter and tolerance checks better understanding
    Setting EKPO-UNTTO with BAPI_PO_Create
    Re: SRM: many confirmation for PO
    Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
    Do let me know.
    Regards
    - Atul

  • Purchase order replication – extended classic scenario using XML proxy via PI

    Hi Experts
    Question:
    In case of extended classic deployment is it possible to use XML proxy to
    transfer SRM purchase orders to ECC? As we know as of SRM 7.01 its via RFC
    whether SRM 7.02 onwards does SAP support XML for ECS too?
    Has
    anyone read about this in any of the SAP forums?
    Background: In our project, client have invested
    heavily on XI and XI monitoring and troubleshooting, integrated to SAP SOLMAN.
    And would like to opt for XML mode of transfer and reuse existing solution.
    This is the main reason we would like to be very clear in our understanding
    before we go back to client.
    We appreciate your time and support.
    Regards
    Prashanth

    Dear Rahul,
    Thanks for you input
    Let me give you an example of the behaviour:
    in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
    User orders a PO  with quantity=1000, price $100;
    No additional tolerances assigned in the PO itself
    User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
    In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
    So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
    But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
    Cheers
    Ulrike

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

  • How to close extended classic PO in ECC...

    Hi Friends...
    We are in SRM 7.02 and ECC 6.05 in Extended Classic Scenario. One PO had been created for 1 Quantity 3 years ago. There was no GR/IR document posted against that PO. Now that PO had been archieved from SRM. But still PO is available in ECC with open quantity and also its appearing in the open PO report. Now requester wanted, the PO to be closed in ECC and shouldnot appear in the open PO list.
    How to handle this situation.. How to close the extended classic PO in ECC at this scenario. As PO not available in SRM, we can not do anything from SRM side.
    Your inputs are appreciated....
    Regards
    Sivakumar Kandasamy

    Hi Sivakumar,
    If you mean how to archive PO in MM side, please refer to the following info:
    ====
    In ECC system, if you want to archive a MM PO, please use transaction
    SARA->archive object MM_EKKO.
    456129 FAQ: Archiving in purchasing
    401318 Archiving: Additional information
    ====
    If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
    refer to the following test data:
    Parameters:    PURCHASEORDER      =  XXXXXXXXX
    Parameters:    POITEM
    PO_ITEM                        = 00010
    DELETE_IND                     = X
    Parameters:    POITEMX
    PO_ITEM                        = 00010
    PO_ITEMX                       = X
    DELETE_IND                     = X
    You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
    Regards,
    Ivy

  • 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

  • Error while changing PO in SRM extended classic Version 5.0

    Hi Guys,
    we are facing issue while changing PO in SRM , this is extended classic with version 5.0.
    The system status is active() is error message and PO remains unchanged. Kindly help to resolve this issue. we have an approval for even PO if a user changes the qty in the PO then it calls the approval WF logic.
    Thanks
    Srujank

    Hello Srujan,
    Go through the following thread:
    Re: PO status change
    Hope it helps.
    Thanks,
    Neelima

  • 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

  • IR_IND indicator in purchase order - Extended Classic

    Hi All,
    We have a scenario where we purchase free item from vendors. We reset IR_IND in SRM PO then replicate into backend where IR receipt is reset and Free item is set. We have implemented badi BBP_DOC_CHANGE_BADI and BBP_ESC_PO_OUT to do so but POs always in held status and fail to replicate into backend. Our abaper found the changes in BADI has been overwritten by standard code - system will overwrite it with vendor data. Also we found relevant note 1260486 that stated this is truth - our badi changes will not be kept.
    For this case, can anyone help/advice how can we purchase free item in extended classic scenario? thank you.
    regards,
    glen

    Hello,
       Not sure if I follow exactly the comments about being overwritten from the partner data, but we do this successfully in an implementation of BADI BBP_ECS_PO_OUT_BADI.  In particular in our case we set the GR/IR flags based on a couple of criteria like the document type and amount; I don't recall all the technical details of the structure elements in the subsequent BAPI calls to create or change the PO (BAPI_PO_CREATE1 and BAPI_PO_CHANGE) regarding the free goods flag (UMSON) in the ECC PO, but FYI it is mutually exclusive to try and set the IR flag on a free goods item, the BAPI ignores it if IR is set as I remember.
    Hope this helps a little
    Cheers
    MC

  • 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

Maybe you are looking for