CREATION OF SET FOR PURCHASE ORDER NUMBER

Dear Sirs,
I want to create a basic set containing all purchase order number, even though i am using table MSEG and field EBELN, i am not getting and values in it. how to create a basic set containing all the available PO numbers, which can be used in FI validation.
Give me the full setting to create a above mentioned set.
Thanks and Regards

i didn't get what u are saying please elobrate. let me put forth my issue clearly.
my client want to check where there is any PO available are not, for payments exceeding 1,00,000/-
So i am cofiguring a validation, for which i want to keep the  "set of PO numbers" in "CHECK" part of the validation. which i am unable to do. when ever i try to select the set it is saying no valid object found.
SO please help me with ur expert knowledge in this regards
Thanks & Regards

Similar Messages

  • No goods receipt possible for purchase order Number and Item number.

    Hello experts,
    When I create a Goods Reciept with reference to Purchase Order using BAPI_GOODSMVT_CREATE, the following error message appears.
    No goods receipt possible for purchase order <PO number> <line item number>.
    But the GR is getting created manually using Transaction MIGO for the same PO number.
    I found some blogs to check for deletion indicator and Movement type and quantity, when I searched SDN for the same Issue.
    In my case 
    1.deletion indicator is not set for the Purchase order line items
    2.And Movement type is 101
    3.And gm_code is 01.
    Could anyone please suggest me, what else could be the reason for this error?

    Here is the code what i have written.
      f_gmvt_header-pstng_date = sy-datum.
      f_gmvt_header-doc_date   = sy-datum.
      f_gmvt_header-pr_uname   = sy-uname.
      f_gmvt_header-ref_doc_no = p_ebeln.
      f_goodsmvt_code_tmp        = '01'.
    * Looping the PO details.
      CLEAR: gf_item,f_gmvt_item.
      LOOP AT gt_item INTO gf_item.
    * fill the bapi item structure details
        f_gmvt_item-material   = gf_item-material.
        f_gmvt_item-plant      = gf_sbms-werks.
        f_gmvt_item-stge_loc   = '0001'.
        f_gmvt_item-move_type  = '101'.
        f_gmvt_item-po_number  = p_ebeln.
        f_gmvt_item-po_item    = gf_item-po_item.
        f_gmvt_item-entry_qnt  = gf_item-quantity.
        f_gmvt_item-entry_uom  = 'PC'.
        f_gmvt_item-entry_uom_iso = 'PCE'.
        f_gmvt_item-po_pr_qnt = gf_item-quantity.
        f_gmvt_item-orderpr_un = 'PC'.
        f_gmvt_item-orderpr_un_iso = 'PCE'.
        f_gmvt_item-no_more_gr = 'X'.
        f_gmvt_item-ref_doc    = p_ebeln.
        f_gmvt_item-prod_date  = sy-datum.
        f_gmvt_item-mvt_ind    = 'B'.
        f_gmvt_item-move_reas  = '101'.
        f_gmvt_item-vendor      = gf_lfm1-lifnr.
        APPEND f_gmvt_item TO t_gmvt_item.
        CLEAR f_gmvt_item.
      ENDLOOP.
    * cALL THE bapi fm FOR gr POSTING
      CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
        EXPORTING
          goodsmvt_header               = f_gmvt_header
          goodsmvt_code                 = f_goodsmvt_code_tmp
    *     TESTRUN                       = ' '
    *     GOODSMVT_REF_EWM              =
       IMPORTING
         goodsmvt_headret              = f_gmvt_headret
    *     MATERIALDOCUMENT              =
    *     MATDOCUMENTYEAR               =
        TABLES
          goodsmvt_item                 = t_gmvt_item
    *     GOODSMVT_SERIALNUMBER         =
          return                        = t_return
    *     GOODSMVT_SERV_PART_DATA       =
    *     EXTENSIONIN                   =
      IF sy-subrc = 0.
    * For commit the changes use BAPI_TRANSACTION_COMMIT FM.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
          EXPORTING
            wait = 'X'.
    *      MOVE: f_GMVT_HEADRET-MAT_DOC   TO WA_DET-MBLNR,
    *            f_GMVT_HEADRET-DOC_YEAR  TO WA_DET-MJAHR,
    *            f_GMVT_HEADER-REF_DOC_NO TO WA_DET-EBELN.
    *      APPEND WA_DET TO IT_DET.
    *      CLEAR WA_DET.
      ENDIF.

  • Negative values for Purchase Order Number

    Hi,
    We are facing a strange issue in our R12.1.3 Ebiz instance (DB 11.2.0.1) - Solaris Sparc 64 bit - 2 node (1 node Apps, 1 node DB).
    Some of the purchase orders are having a negative purchase order number.
    SQL> select segment1 from PO_HEADERS_ALL where segment1 < '0';
    SEGMENT1
    -7951814
    -8960847
    How it could happen. Any suggestions please !

    hi muneer
    >
    We are facing a strange issue in our R12.1.3 Ebiz instance (DB 11.2.0.1) - Solaris Sparc 64 bit - 2 node (1 node Apps, 1 node DB).
    Some of the purchase orders are having a negative purchase order number.
    SQL> select segment1 from PO_HEADERS_ALL where segment1 < '0';
    SEGMENT1
    -7951814
    -8960847please see
    Error: Purchase Order Creation Could Not Be Initiated, But PO Was Created With Negative PO Number And No Distributions [ID 789464.1]     To Bottom     
    PO Creation Process Failed In Sourcing And Creates Document With Negative Numbers [ID 1479616.1]
    Purchase Order Receipt FAQ (P4312) [ID 1306869.1]
    How it could happen. Any suggestions please !looks like a bug
    Can a Purchase Order (PO) Be Created With Negative Quantity or Price? [ID 241389.1]
    AppsMasti
    Sharing is caring

  • Creating  workflow for purchase order release.

    Hi friends
    I want step by step detail about creation of workflow for purchase order release..
    After release purchase order it will goes to the two level of approval..
    after that the workflow should be completed...
    how can i develope the workflow for that scenario..
    Thanks
    Gowrishankar

    Hi Gowrishankar,
    You can get step by step workflow for PO using standard workflow
    <b>Release of Purchase Order :WS20000075</b>
    And for two levels of approvals you have to configure in SPRO the path is
    Purchase Order:
    SPRO> Material Management->Purchasing->/Purchase order-->Release procedure ---> Procedure with classification ---> set up procedure with classification ---> double click on Release strategies and Workflow.
    If you don't know about this configuration, you have to confirm with your MM consultant.
    Thanks and Regards,
    Prabhakar Dharmala

  • Demerger  Purchase order number range.

    Hi Friends,
    We have demerger of 1 of hte business of the company & new entity will be using same client which we are using.
    We will be Creating new Purcharse orders with open amounts for new legal entities.
    Here requirement for purchase order number range is as belows. How can we achieve this.
    Our advice for number range is to use a prefix + old PO number, to ensure the incoming invoices can be easily assigned.
    Thanks,
    Kiran

    HI,
       You may define external number range as shown below, for example:
       Assign the same as external number range for the PO Doc type:
       While creating the PO, maintain the number range externally with the required prefix + old PO number.
    Test the same and revert back.
    Regards,
    AKPT

  • User Exit for Purchase Requisition Number Range

    Dear Experts,
    I searched on sdn, i got M06B0003 &M06B0004 this 2 user exit for PR Number range.
    I have activated both User exits but while creating PR is not getting effect of that user exit.
    I have checked by putting Break-point in respective user exit but while saving the PR it should go to that break-point but it not going there aslo.
    And also i have checked user exit MM06E003 but it is for Purchase Order number range.And for PO it is working.
    Please help me to solve this issue.Solution will be appreciated.
    Regards,
    Sanket.

    Hi,
    Sorry that badi will not help try this one ...EXIT_SAPLMEREQ_009 in MEREQ001 where the export parameters is purchase requisition number....
    Thanks,
    Shailaja Ainala.

  • External number range for purchase order response?

    Hi all,
    is it possible to use an external number range when creating purchase order responses (BUS2209, PCO, POR) manually?
    If I transfer the POR from an external system like SUS via XML, can I use an external number range?
    I'm using SRM 4.0 (EBP 5.0) in standalone scenario with Business Connector 4.7 as XML interface.
    Any help is appreciated,
    Karsten

    Hi
    No need to maintian Internal number range.. Yes you need to use an external number range
    Only the PO, RQ & RS are sync and therefore must correspond with the R/3 number ranges.
    The rest, Shop Cart (SC), Local PO (EBP), Confirmation, Invoice, Bid Inv and Bid, aren't synced and can be assigned to any number range. (FYI- using ECS)
    Re: Extended Classic - Purchase Order Number Ranges
    http://help.sap.com/saphelp_srm50/helpdata/en/87/7cc73cee4fb55be10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/6d/0f343e47fd6b2ee10000000a114084/frameset.htm
    Re: Number range config
    Re: config for Number Ranges ? :-(
    Re: PO Creation with external PO number
    Purchase Order Response BUS2232
    PO number range Issue
    Re: Defining the number range
    Regards
    - Atul

  • Basket icon is not displaying for purchase order creation transaction iview

    Hi SDNs,
    I have created a set of purchase related transaction iviews like for example purchase order display.
    there i couldn't find the basket icon to drop the other purchase order number, which we generally choose by using docuement overview on to change the number.
    in WebGUI how do we drop the exisiting documnet into the screen.
    I have activated all icon services in sicf, is there any specific services to be activated to have such kind of icons in webgui.
    Please suggest me to resolve this.
    Your inputs are appreciated.
    Thanks,
    Sireesha.B

    Hi SDN's,
    Can anyone suggest me for the above problem.
    Your inputs will be highly appreciated.
    Regards,
    Sireesha.B

  • Debugging EDI output (IDOC creation) for purchase order...

    Hi,
    We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
    Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
    Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
    Regards,
    Rajesh

    Hi
    Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
    Save.
    Set the break point in your user exit.
    Go to se 38 -> Run RSNAST00,
    Give the object id (Your PO #)
    Give the output type  and execute, the control will stop at break point.
    Regards,
    Baburaj

  • Inspection Type 05 require input purchase order number for rejection

    Hi Experts,
    I have inspection and needed to reject in QA12.
    When inputting the stock posting quantity to return, it prompts the reason for rejection, and required to input purchase order number also.
    Since that is material return from production(inspection type 05) with no purchase order number, where in SPRO I can check the setting of this and disable this?
    Please kindly advise, thanks!
    Regards,
    Daniel

    Hi SujitSND,
    I have some materials in inspection lot which is created from material return in production.
    This lot is rejected by QA and needed to return to production line.
    When inputting the qualtity field RETURN DELIVERY, system forced me to input Purchase Order number which is not available.
    My target is to not needing to input purchase order.
    Regards,
    Daniel

  • Purchase order number for each postings with FBL3N

    Hello
    With tcode FBL3N, I need to get all the postings on expenses accounts. Additionally it is possible to get more information on the postings from the orginal paper invoice. It shall be also more convenient to get the purchase order number walk trhough SAP with it. Then is it possible to get the purchase order number for each postings with FBL3N?
    thanks for inputs
    sb

    Hello,
    Could you please add field BSEG-EBELN as a special field in FBL3N (from
    menu path Settings -> Special fields).
    Then, select the Purchase order field again from "Change Layout"
    (Ctrl+F8). Now this field is available for display variants, it has the
    technical name 1-U_EBELN and the description 'Purchase Document'.
    The other field has the same description but as technical name
    '1-EBELN'. When you create a display variant be aware that you select
    1-U_EBELN and not 1-EBELN.
    *******Please also refer to attached notes 215798 and 984305.
    Best regards, Hana

  • Error:-document is in transfer for purchase order..creation is not possible

    Hello,
    While doing confirmation of PO I am getting this error, saying "document is in transfer for purchase order..creation is not possible".
    can anyone please suggest me solution on this type of error?

    Hi,
    Is the PO in ORDERED status? Is there any confirmation posted for this PO which might be stuck (idoc failed to reach back end)?
    If it is a case of idoc failure, then reprocess the idoc and then do the next confirmation.
    regards,
    MRao

  • Getting errors when iam using  BAPI_PO_CREATE1 for Purchase Order creation

    Hi sap Gurus,
      I am getting Errors when iam using  BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
    I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
    pls let me know .
    thanks in advance.

    Hi,
    Check the sample code..
    report  zpo_test             .
    *DATA DECLARATION
    constants : c_x value 'X'.
    *Structures to hold PO header data
    data : header like bapimepoheader ,
    headerx like bapimepoheaderx .
    *Structures to hold PO account data
    data : account like bapimepoaccount occurs 0 with header line ,
    accountx like bapimepoaccountx occurs 0 with header line .
    *Internal Tables to hold PO ITEM DATA
    data : item like bapimepoitem occurs 0 with header line,
    itemx like bapimepoitemx occurs 0 with header line,
    *Internal table to hold messages from BAPI call
    return like bapiret2 occurs 0 with header line,
    *Internal table to hold messages from BAPI call
    pocontractlimits like bapiesucc occurs 0 with header line.
    data : w_header(40) value 'PO Header',
    purchaseorder like bapimepoheader-po_number,
    delivery_date like bapimeposchedule-delivery_date.
    data : ws_langu like sy-langu.
    *text-001 = 'PO Header' - define as text element
    selection-screen begin of block b1 with frame title text-001.
    parameters : company like header-comp_code default '122' ,
    doctyp like header-doc_type default 'NB' ,
    cdate like header-creat_date default sy-datum ,
    vendor like header-vendor default '2000000012' ,
    pur_org like header-purch_org default 'PU01' ,
    pur_grp like header-pur_group default '005' .
    *sociedad like HEADER-COMP_CODE default '122' ,
    *vendedor like HEADER-SALES_PERS default 'sale person'.
    selection-screen end of block b1.
    selection-screen begin of block b2 with frame title text-002.
    parameters : item_num like item-po_item default '00010',
    material like item-material default '12000000' ,
    tipo_imp like item-acctasscat default 'K' ,
    *pos_doc like ITEM-ITEM_CAT default 'F' ,
    shorttxt like item-short_text default 'PRUEBA BAPI' ,
    grup_art like item-matl_group default '817230000' ,
    plant like item-plant default '3001' ,
    mpe like item-trackingno default '9999' ,
    *contrato like ITEM-AGREEMENT default '4904000003' ,
    *quantity like ITEM-QUANTITY default 1 .
    po_unit like item-po_unit default 'EA'.
    selection-screen end of block b2.
    Par?mnetros de imputaci?n
    selection-screen begin of block b3 with frame title text-004.
    parameters : centro like account-costcenter default '1220813150',
    cuenta like account-gl_account default '6631400' ,
    num_pos like account-po_item default '10' ,
    serial like account-serial_no default '01' ,
    ind_imp like account-tax_code default 'I2' .
    selection-screen end of block b3.
    start-of-selection.
    *DATA POPULATION
      ws_langu = sy-langu. "Language variable
    *POPULATE HEADER DATA FOR PO
    *HEADER-COMP_CODE = sociedad .
      header-doc_type = doctyp .
      header-vendor = vendor .
      header-creat_date = cdate .
      header-created_by = 'TD17191' .
      header-purch_org = pur_org .
      header-pur_group = pur_grp .
      header-comp_code = company .
      header-langu = ws_langu .
    *HEADER-SALES_PERS = vendedor .
    *HEADER-CURRENCY = 'DOP' .
    *HEADER-ITEM_INTVL = 10 .
    *HEADER-PMNTTRMS = 'N30' .
    *HEADER-EXCH_RATE = 1 .
    *POPULATE HEADER FLAG.
      headerx-comp_code = c_x.
      headerx-doc_type = c_x.
      headerx-vendor = c_x.
      headerx-creat_date = c_x.
      headerx-created_by = c_x.
      headerx-purch_org = c_x.
      headerx-pur_group = c_x.
      headerx-langu = c_x.
    *HEADERX-sales_pers = c_x.
    *HEADERX-CURRENCY = c_x.
    *HEADER-ITEM_INTVL = c_x.
    *HEADER-PMNTTRMS = c_x.
    *HEADER-EXCH_RATE = c_x.
    *HEADER-EXCH_RATE = c_x.
    *POPULATE ITEM DATA.
      item-po_item = item_num.
      item-quantity = '1'.
    *ITEM-MATERIAL = material .
      item-short_text = 'prueba bapi_po_create1'.
    *ITEM-TAX_CODE = ''.
      item-acctasscat = 'K' .
    *ITEM-ITEM_CAT = 'D' .
      item-matl_group = '817230000' .
      item-plant = '3001' .
      item-trackingno = '99999'.
      item-preq_name = 'test'.
    *ITEM-AGREEMENT = '' .
    *ITEM-AGMT_ITEM = ''.
      item-quantity = '1' .
      item-po_unit = 'EA'.
    *ITEM-ORDERPR_UN = 'EA'.
      item-conv_num1 = '1'.
      item-conv_den1 = '1'.
      item-net_price = '1000000' .
      item-price_unit = '1'.
      item-gr_pr_time = '0'.
      item-prnt_price = 'X'.
      item-unlimited_dlv = 'X'.
      item-gr_ind = 'X' .
      item-ir_ind = 'X' .
      item-gr_basediv = 'X'.
    *ITEM-PCKG_NO = '' .
      append item. clear item.
    *POPULATE ITEM FLAG TABLE
      itemx-po_item = item_num.
      itemx-po_itemx = c_x.
    *ITEMX-MATERIAL = C_X.
      itemx-short_text = c_x.
      itemx-quantity = c_x.
    *ITEMX-TAX_CODE = C_X.
      itemx-acctasscat = c_x.
    *ITEMX-ITEM_CAT = c_x.
      itemx-matl_group = c_x.
      itemx-plant = c_x.
      itemx-trackingno = c_x.
      itemx-preq_name = c_x.
    *ITEMX-AGREEMENT = C_X.
    *ITEMX-AGMT_ITEM = c_x.
      itemx-stge_loc = c_x.
      itemx-quantity = c_x.
      itemx-po_unit = c_x.
    *ITEMX-ORDERPR_UN = C_X.
      itemx-conv_num1 = c_x.
      itemx-conv_den1 = c_x.
      itemx-net_price = c_x.
      itemx-price_unit = c_x.
      itemx-gr_pr_time = c_x.
      itemx-prnt_price = c_x.
      itemx-unlimited_dlv = c_x.
      itemx-gr_ind = c_x .
      itemx-ir_ind = c_x .
      itemx-gr_basediv = c_x .
      append itemx. clear itemx.
    *POPULATE ACCOUNT DATA.
      account-po_item = item_num.
      account-serial_no = serial .
      account-creat_date = sy-datum .
      account-costcenter = centro .
      account-gl_account = cuenta .
      account-gr_rcpt = 'tester'.
      append account. clear account.
    *POPULATE ACCOUNT FLAG TABLE.
      accountx-po_item = item_num .
      accountx-po_itemx = c_x .
      accountx-serial_no = serial .
      accountx-serial_nox = c_x .
      accountx-creat_date = c_x .
      accountx-costcenter = c_x .
      accountx-gl_account = c_x .
      account-gr_rcpt = c_x.
      append accountx. clear accountx.
    *BAPI CALL
      call function 'DIALOG_SET_NO_DIALOG'.
      call function 'BAPI_PO_CREATE1'
        exporting
          poheader         = header
          poheaderx        = headerx
        importing
          exppurchaseorder = purchaseorder
        tables
          return           = return
          poitem           = item
          poitemx          = itemx
          poaccount        = account
          poaccountx       = accountx.
    *Confirm the document creation by calling database COMMIT
      call function 'BAPI_TRANSACTION_COMMIT'
      exporting
      wait = 'X'
    IMPORTING
    RETURN =
    end-of-selection.
    *Output the messages returned from BAPI call
      loop at return.
        write / return-message.
      endloop.
    Regards
    Sudheer

  • Document is in transfer for purchase order.Creation not possible

    Dear All,
    We did partial confirmation in EBP and later when trying to do confiramtion for the remaining quantiy getting the message"document is in transfer for purchase order.Creation not possible"
    We are taking this problem in production as well as in quality systems also.
    What are possible reason and how to solve it.
    kindly share your views.
    Thank you.

    Hi yshu,
    use tcode bd87 in SRM to check for failed confirmation IDOC (type MBGMCR).
    The double click the status record to see the exact cause of the failure.
    Rectify the error. Then try to execute the IDOC from BD87 tcode.
    For a few errors you may not be able to execute the IDOC but to create a new confirmation in SRM. In such cases, follow the below procedure..
    There should be an entry for the confirmation in the transfer table BBP_DOCUMENT_TAB in SRM. Display the details.
    Then run FM "BBP_DELETE_FROM_DOCUMENT_TAB" to delete the entry from the doc tab table.
    Then post a new confirmation in SRM.
    There is also a FM in SRM using which you can change the status of thefailed IDOC from 51 to 68 or 31.
    Rgds,
    MJ

  • How to Assigning the number ranges for Purchase Order using EXIT_SAPMM06E_0

    How to Assigning the number ranges for Purchase Order using EXIT_SAPMM06E_001 using Functional Module NUMBER_GET_NEXT explain me ?

    Hi,
    First go thourh the FM import export parameters list.
    Try to create an internal table of type INRI-NRRANGENR for number ranges.
    We can provide the lower and higher values for this table so that what ever PO is created will be with that range.
    Try to create the ncessary ones using this FM.
    In the Exit, EXIT_SAPMM06E_001,
    the Export parameters are-
    EKKO-EBELN- the PO ios created with in that specified range
    Range as INRI-NRRANGENR - Here try to assign the Internal table that was populated in the FM.
    Try to code this in the Include provded and keep Breakpint and check the PO number generated.
    Reply if u need more help on this.
    Reward if helpful.
    Best Wishes,
    Chandralekha

Maybe you are looking for