Blocking PO creation without a Purch. Req

Hello Team,
We need to make sure that PO can be created only if there is a Purchase Requisition already created. How do I stop the system from Blocking PO creation without reference to a requisition?
I will appreciate your feedback.
Joel.

Hi,
There are two alternative solutions you can think of -
1)   Set up the related authorization key in OMET and assign this key to your buyer with parameter EFB; or
20  Define the ''error'' release strategy if PO is created without reference to PR.  In this particular case, the user exit shall be activated to append the CEKKO communication structure to include MRP Controller as part of the release strategy structure.
Cheers,
HT

Similar Messages

  • Automated vendor block on creation without user inputs

    Hi All,
    I want to block the vendor in creation without user inputs:
    Not in T-code mk01<extras<blocked data, and definiately not after creating the vendor and using t-code MK05.
    How i can change a field in table LFA1 while creating the vendor.
    the field that i want to set is LFA1-SPERM (for all purchasing Org).
    Please suggest if you have any ideas how this can be done.
    Thanks,
    Mamta

    Hi,
    Not sure your issue was solved already.
    However, if not resolved already try this
    create an explicit enhancement in include MF02KFV0
    ENHANCEMENT 3  ZFI_VENDOR_CREATE.  
    IF SY-TCODE = 'MK01''.
    LFA1-SPERM = `X`.
    ENDIF.
    ENDENHANCEMENT.
    Enhancement Spot :ES_MF02KFV0   
    Program: MF02KFV0  
    Enhancement Implementation type: Dynamic Enhancement Point
    Enhancement Implementation POint:  \IC:MF02KFV0\EX:VERBUCHUNGSAUFRUF_02\EI
    Regards
    Raja

  • BPM Alert - P.O created without purch req

    Hi all,
    I have an issue where my BPM alert "purchase order lines created without reference to a purch req" sometimes gives me a P.O that was creatd with ref to a P.O. I have raised an OSS note for SAP but I was wondering if anyone else had a similiar issueor if they have the same alert but it functions correctly?
    Thanks,
    Kev

    Hi Kevin,
    as already explained via another communication channel I think the collector is working perfectly fine. Be aware that, like most other Procurement collectors, we are checking on line item level and not only on document level. As your example shows ONLY line item 20 is created without PR reference. But your screenshot of the document itself shows line item 10 which is created with a PR reference and hence was not in our output list. Also a look in table EKPO shows that one item was created with reference and the other wasnu2019t.
    Best Regards
    Volker

  • How to block the creation of a Sales Orders without a linked Purchase Order

    Hi. I'm trying to block the creation of a Sales Order that doesn't have a linked Purchase Order. The first thing I did is using the SBO Transaction Notification as follows:
    IF  @transaction_type = 'A' AND @object_type='17'
    BEGIN
         IF (SELECT PoPrss FROM ORDR WHERE DocEntry = @list_of_cols_val_tab_del) = 'N'
         BEGIN
              SET @error = 1
              SET @error_message = 'Purchase Order Missing...'
         END
    END
    This works good. I create the Sales Order, I tick the purchase order field on the logistics tab, I click Add, and then the purchase order window appears...
    Then, the problem begins... If I click the Cancel button, the purchase order is obviously not created, but the Sales Order is created.
    Can someone tell me how to block the creation of the sales order If the user press the cancel button on the purchase order window (and the purchase order is not created)
    As far as I can see, after clicking the add button in the sales order document, the Sales Order is created on the DB. If there's no way of blocking the creation of the Sales Order, can I avoid closing the purchase order window by the SBO_TransactionNotification? (if the purchase order has not been created)
    Thanks...

    Hi Yail,
    I think you can't close the purchase order with the stored procedure.
    Try to catch the Event when the user click on Cancel button.
    So you can list the vents with event logger : https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ede3be37-0e01-0010-1883-cd1b5293473e
    You can block the cancel button and force the user to create the purchase order.
    Hope i help you
    Best regards
    Michael

  • Blocking the Creation of PO in Service Order

    Hello SAP folks,
    I have got an issue where I have to block the Creation of Purchase Requisation Number(BANFN) which is generated  in the background after the creation of the Service order(IW31)  I have tried the user exit EXIT_SAPLCOIH_009 but while coding i could'nt trace the field which is holding the value of PR number.Please let me know is it possible to stop the creation of PR if Yes, Please guide me in this issue in terms of coding.
    Thanxs in advance.
    Regards,
    Indira

    Hi Indira,
    Try these User Exits.
    CNEX0013  Order: Cust. enhancement: Default item category comp. a
    CNEX0026  Customer enhancement for general inspection of material
    CNEX0027  Customer enhancement: Plant, storage loc. finding for c
    IWO10004  Maintenance order: Customer check for order completion
    IWO10005  Maintenance order: Cust.-specif. determination of profi
    IWO10006  Maint. order: Fcode exclusion through cust. enhancement
    IWO10007  Maint.order: Customer enhancement - permits in the orde
    IWO10008  Cust. enhancement: Determination of tax jurisdiction co
    IWO10009  PM Order: Customer Check for 'Save' Event
    IWO10010  Maint. order: Cust. enhancement for determining WBS ele
    IWO10011  Maint. order: Customer enhancement for component select
    IWO10015  Maintenance order: F4 Help for user fields on operation
    IWO10016  PM Order: Cust. enhancement to check operation user fie
    IWO10017  Determine external order number by customer logic
    IWO10018  Maintenance order: User fields on order header
    IWO10020  Maintenance order: Automatically include task list
    IWO10021  Automatic task list transfer when creating order from n
    IWO10022  Determine calendar from user exit
    IWO10023  Service order: Change header data for advance shipment
    IWO10024  Service order: Changes to items for advance shipment
    IWO10025  PM/SM order: Finding responsible cost center
    IWO10029  Inclusion of bill of material in PM/SM order
    IWO10030  Preset Fields for Event Object
    IWO10031  Hide personnel number in PM/SM order
    IWO10033  Customer-Specific Authorization Check Maint./Service Or
    IWO10034  Operation status based on the status of capacity reqs
    Regards,
    Vijay

  • Not running MRP but has Purch Req with Sales Order as pegged reqmnt in AFS

    Hello Gurus!
    MRP run is activated in the Plant but we do not run MRP (no MRP batch job nor manual MRP). However, there are materials that have Purch Reqs with creation indicator as MRP showing pegged reqmnt from Sales Order even if Item category is the same.
    My initial check shows that those materials with issue has MRP Indicator as BLANK(Multi-level, transaction dependent MRP) and those that do not generate Purch Req from SOs has N(No transaction-dependent MRP). However, transaction dependent MRP is not activated.
    Can you provide areas where I should check/other probable cause of this?
    Your valuable insights is deeply appreciated. Thanks!

    Hello?
    I just want to update how this was resolved.
    I found out that MRP Indicator field in AFS MRP view for the materials with MRP generated Purch Reqs is maintained as BLANK(Multi-level, transaction dependent MRP) in AFS MRP view instead of N(No transaction-dependent MRP) but there is no transaction group maintained. So MRP run is triggered whenevert there is MRP relevant transactions performed.

  • BPM Alert Issue - P.O Created withour ref to Purch Req

    Hi,
    Has anyone else had any issues with the BPM alert "P.o's created without ref to a P.O";? It seems to be reporting incorrectly - it gives us sometimes P.O that were in fact created with ref to a purch req.
    I've raised an OSS for this with Sap - although I'm still awaiting a response...Has anyone had the same issue described above?
    Thanks,
    K
    Edited by: Kevin Devaney on Nov 11, 2010 11:39 AM

    Hi Kevin,
    as already explained via another communication channel I think the collector is working perfectly fine. Be aware that, like most other Procurement collectors, we are checking on line item level and not only on document level. As your example shows ONLY line item 20 is created without PR reference. But your screenshot of the document itself shows line item 10 which is created with a PR reference and hence was not in our output list. Also a look in table EKPO shows that one item was created with reference and the other wasnu2019t.
    Best Regards
    Volker

  • Status of Purch Req

    Hi,
    On SAP release 46C the processing status of a purchase requisition is not updated during the creation of a contract.
    When I create a contract WK from a PR NB, the staus of Purch Req display only "Contract Created" but not displays the details of the Contract.
    Thanks and regards
    Michela

    Hello,
    The similar issue is reported in the SDN threads earlier:
    Status Update Issue with PR doc type NB
    Check if the contract is created correctly with the right assignment.also once you have created a contract with the particular account assignment, u cannot change it. You would have to create a new contract with the desired account assignment category and then try creating a PR. Hope this helps!
    Regards

  • Block cash sales with credit limit blocking from creation of outbound

    Hello everyone,
    Can you please teach me how to block cash sales with credit limit blocking from creation of outbound delivery?  Currently, outbound delivery can not be created only for charge sales with credit limit block.  Problem is, we can not confirm the cash sales.  We have to delete first the outbound then unblock the S.O. before creating a new Outbound.
    Thanks in advance.
    Ridgy

    Cash sale transaction will not have credit limit block, as the transaction is based on receipt of immediate payment. But if you still want to try the same, configure a 'Z' transaction Type for cash sale (Copy of Cash Sale - Sales Order Type) and maintain Credit check field as 'D' and try the scenario.
    Ideally there should not be a Credir Check foe a Cash Sale Scenario.
    Regards,
    Rajesh Banka

  • Converting SNP Planned Order /Purch Req to Prod.Order/Purch.Order

    Guys
    What is the standard process to Convert the SNP Planned Order /Purch Req. into a Prod.Order/Purch.Order ?
    Can the conversion indicator be set in APO for SNP Planned Order /Purch Req.and then transferred to R3 as Prod.Order/Purch.Order  or can the convesrion of Planned Order /Purch Req to Prod.Order/Purch.Order  can be done in R3 itself ?
    I am not clear on how exactly this works. Would appreicate if you could provide me with the standard process and any config involved in the same such as Number Ranges and how to set the conversion indicator automatically through SNP planning runs ?
    Thanks

    When you set this indicator for a planned order or a purchase
    requisition, the system automatically converts the order into a
    Production order or purchase order after the transfer to the
    connected SAP R/3 system.
    The converted orders are then retransferred to the SAP APO system with a
    different category; a purchase requisition with category BS-ANF becomes
    a purchase order delivery schedule line with category BS-EIN.
    Please check configuration setting in SPro for transfer setting to R/3.
    1. Configure Transfer to OLTP Systems(SNP)
    2.Maintain Global Parameters and Defaults(PPDS)
    Also on R/3 side you can see it in MD04/MD07 collectively for a product . or individually on
    MD13 : planned order
    MB51n: PR
    Manish

  • Block the creation of planned order

    Dear experts
    How can I control the creation of planned order? I want to block the creation of planned order if the BOM or routing is not exist.
    BRs

    Hi,
    I think this can be done using 'Material status' try the following and let me know if it works.
    Create a new material status in transaction OMS4 (like R1 - "Created but BOM and Routing not maintained" )and in the details screen select Option "B" for MRP messages.
    You designate a material as a "R1 -Created but BOM and Routing not maintained" In the master record.
        MRP                          "B" = warning
    Please try this and let me know the result.   
    Regards,
    Prakash

  • Block cancellation/creation of billing document on CLOSED posting period

    Hi Experts,
    Currently, user is allowed to cancel/create backdated billing document where period already closed, but it does not release to accounting automatically, due to the period has been closed.
    When account user found out that the accounting document is missing for the billing document, they have to re-open the period and manual release it to accounting, in order to generate the accounting document.
    Therefore, we need the billing document to be blocked for cancellation/creation on CLOSED posting period.
      Is there any settings in stardard SAP to block cancellation/creation of billing document on CLOSED posting period?
    would appreciate your inputs.
    Thanks and Regards,
    N.C.Reddy

    Hi ,
    We have blocked cancellation/ creation of billing document through below  user exit. Below is the progran code also.
    ***INCLUDE RV60AFZC.
    FORM USEREXIT_NUMBER_RANGE_INV_DATE USING US_RANGE_INTERN.
    Example: Number range from TVFK like in standard
    US_RANGE_INTERN = TVFK-NUMKI.
    *{   INSERT         KPDK904773                                        1
    *Block creation or cancellation of billing doc in closed period
    DATA : gv_gjahr TYPE bkpf-gjahr,
           gv_monat TYPE bkpf-monat,
           gv_poper TYPE t009b-poper,
           gv_bukrs TYPE t001-bukrs,
           lv_gjahr TYPE t001b-frye1,
           lv_monat TYPE t001b-frpe1,
           gv_oper  TYPE t001b-frpe1.
      CLEAR : gv_gjahr, gv_monat, gv_poper, gv_bukrs.
      gv_bukrs = vbrk-bukrs.
    IF NOT likp-wadat_ist IS INITIAL.
    *- First determine the Period of the Actual GI date.
      CALL FUNCTION 'FI_PERIOD_DETERMINE'
        EXPORTING
          i_budat              = likp-wadat_ist
          i_bukrs              = gv_bukrs
       IMPORTING
         E_GJAHR              = gv_gjahr
         E_MONAT              = gv_monat
         E_POPER              = gv_poper
       EXCEPTIONS
         FISCAL_YEAR          = 1
         PERIOD               = 2
         PERIOD_VERSION       = 3
         POSTING_PERIOD       = 4
         SPECIAL_PERIOD       = 5
         VERSION              = 6
         POSTING_DATE         = 7
         OTHERS               = 8.
          IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                   WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ELSE.
            CLEAR : lv_gjahr, lv_monat.
            lv_gjahr = gv_gjahr.
            lv_monat = gv_monat.
    *- Once period is determine check whether Period is open or not for 'D' - Customer Account
            CALL FUNCTION 'FI_PERIOD_CHECK'
              EXPORTING
                I_BUKRS                = gv_bukrs
                i_gjahr                = lv_gjahr
                i_koart                = 'D'
                i_monat                = lv_monat
             IMPORTING
               E_OPER                 = gv_oper
             EXCEPTIONS
               ERROR_PERIOD           = 1
               ERROR_PERIOD_ACC       = 2
               INVALID_INPUT          = 3
               OTHERS                 = 4.
              IF sy-subrc <> 0.
               MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ELSE.
    *- Once period is determine check whether Period is open or not for 'S' - All G/L Accounts
                CALL FUNCTION 'FI_PERIOD_CHECK'
                EXPORTING
                  I_BUKRS                = gv_bukrs
                  i_gjahr                = lv_gjahr
                  i_koart                = 'S'
                  i_monat                = lv_monat
               IMPORTING
                 E_OPER                 = gv_oper
               EXCEPTIONS
                 ERROR_PERIOD           = 1
                 ERROR_PERIOD_ACC       = 2
                 INVALID_INPUT          = 3
                 OTHERS                 = 4.
                IF sy-subrc <> 0.
                  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
               ENDIF.
             ENDIF.
         ENDIF.
    ENDIF.
    *- Check Billing Date period is closed or not
    IF kom-fkdat is not initial.
      clear : gv_gjahr, gv_monat, gv_poper.
    *- First determine the Period of the Actual GI date.
      CALL FUNCTION 'FI_PERIOD_DETERMINE'
        EXPORTING
          i_budat              = kom-fkdat
          i_bukrs              = gv_bukrs
       IMPORTING
         E_GJAHR              = gv_gjahr
         E_MONAT              = gv_monat
         E_POPER              = gv_poper
       EXCEPTIONS
         FISCAL_YEAR          = 1
         PERIOD               = 2
         PERIOD_VERSION       = 3
         POSTING_PERIOD       = 4
         SPECIAL_PERIOD       = 5
         VERSION              = 6
         POSTING_DATE         = 7
         OTHERS               = 8.
          IF sy-subrc <> 0.
           MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                   WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ELSE.
            CLEAR : lv_gjahr, lv_monat.
            lv_gjahr = gv_gjahr.
            lv_monat = gv_monat.
    *- Once period is determine check whether Period is open or not for 'D' - Customer Account
            CALL FUNCTION 'FI_PERIOD_CHECK'
              EXPORTING
                I_BUKRS                = gv_bukrs
                i_gjahr                = lv_gjahr
                i_koart                = 'D'
                i_monat                = lv_monat
             IMPORTING
               E_OPER                 = gv_oper
             EXCEPTIONS
               ERROR_PERIOD           = 1
               ERROR_PERIOD_ACC       = 2
               INVALID_INPUT          = 3
               OTHERS                 = 4.
              IF sy-subrc <> 0.
               MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                       WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
              ELSE.
    *- Once period is determine check whether Period is open or not for 'S' - All G/L Accounts
                CALL FUNCTION 'FI_PERIOD_CHECK'
                EXPORTING
                  I_BUKRS                = gv_bukrs
                  i_gjahr                = lv_gjahr
                  i_koart                = 'S'
                  i_monat                = lv_monat
               IMPORTING
                 E_OPER                 = gv_oper
               EXCEPTIONS
                 ERROR_PERIOD           = 1
                 ERROR_PERIOD_ACC       = 2
                 INVALID_INPUT          = 3
                 OTHERS                 = 4.
                IF sy-subrc <> 0.
                  MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                     WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
               ELSE.
                IF kom-fkdat4(2) <> likp-wadat_ist4(2).
                ENDIF.
               ENDIF.
             ENDIF.
         ENDIF.
    ENDIF.
    *}   INSERT
    ENDFORM.
          FORM USEREXIT_FILL_VBRK_VBRP                                  *
          This userexit can be used to fill fields in VBRK and VBRP     *
          Be aware, that at this time the work areas KUAGV KURGV        *
          KUWEV and KUREV are not filled.                               *
          This form is called from FORM VBRK_VBRP_FUELLEN.              *
    FORM USEREXIT_FILL_VBRK_VBRP.
    Example: change Tax country
    VBRK-LANDTX = T001-LAND1.
    ENDFORM.
    *eject

  • Restriction of RFQ creation without PR reference

    Dear all,
    I want to restrict the RFQ creation without PR reference for certain document type in RFQ say AN.How to do that???
    Regards,
    Atanu

    Hi,
    Creation of RFQ without any reference is standard functionality. So restricting it without reference of PR is quite tricky.
    I can suggest you to use field selection key.
    For example, as standard for document type AN, SAP uses field selection key ANA. You copy this key and create your own new key. In this key you can find field 'PR' under field selection group 'Reference data. item'. Mark this field as required entry. Assign your new key to document type.
    Please try this out and let me know how it worked.
    Regards,
    Sameer

  • Purch.Req for STO

    Dear Experts...
    1. Can we have a Purchase Requisition for the STO? Our client based in Kochin has branches in other states like Delhi, Kolkata,  
        Andhra etc..the sales requirement data collected from branches will be sent to Kochi head office, and Kochi will create Stock
       Transfer Order to transfer the Finished Goods to the requesting branch for sales..Here I want to know what document in SAP  
       can be entered to proceed to STO ? (Like the case of conveting Purch Req to PO)
    2. Our Client has 8 categories of finished products for eg. Spices, Soup mixtures, Seafood varieties etc, and in each of this 
        catrgory  they have many classifications, for eg. in Spices category they have cardamom mix, pepper-ginger mix etc, same is
        the case for other categories. For reporting, they want to capture the COSTING reports for each category. My question is, 
        can these CATEGORIES be defined in the MATERIAL GROUP, so that can we generate reports based on the Material Group? 
        What data is pulled from MM module for costing? when costing which price is taken? material master Avg Price or PO price of
       that GRN which is issued to the Production?
    Please suggest some solutions
    Suraj

    Thanks for the reply...
    Please give me some info on what data will be pulled from MM for Product Costing. I believe it is the price of the raw materials issued to production, depending on its value in PO. We are maintaining batches to manage the raw materials. Since we maintain the Moving Avg Price for valuation, there will be an average value in the material maste. In order to take the exact value for costing we use FIFO method, wherein the values will be pulled from the PO. Please correct me if Iam wrong and suggest the correct procedure.
    regards
    Suraj

  • Sales order is blocked for Delivery-ZH Cost estimate Req

    Hi experts,
    When I am saving the sales order I am getting the informative message standard cost estimate for material xxxx is missing. when i am creating delivery with reference to sales order  it is not allowing me to do delivery it is showing that Sales order is blocked for Delivery-ZH Cost estimate Req( in  a log). Can you pls let me know what configuration I have to check.
    Regards,
    Sunina Agarwal

    hello, friend.
    it looks like product costing has been activated in your environment.  if such is the case, you would have to coordinate with your FICO consultant, and they have to make the necessary standard cost estimates.
    please also check if the cost estimates are part of the incompletion procedures.  if it is, you would not be able to bill the transaction even if this is taken out of the incompleteness procedure.
    regards.

Maybe you are looking for