Purchase requisition forward option

I am working on 11 version
created requisition hierarchy, which has lets say 5 level of approval, first 4 level does not have any approval limit assigned, so document should go to the top level(who has approval limit as unlimited) and so can approve the document.
Now at some mid level, lets say 3rd user, want to forward requisition document to someone outside this assigned hierarchy to UserX.
so User3 selects UserX in forward to field and forward it, but no notification goes to UserX here.
there are two cases now, If i set UserX approval limit as less than the document price, then notification comes as "No Approver found"
if I set UserX approval limit as Unlimited, he gets notification and as soon as he approves it, status of requisition becomes Approved.
what i want is
Approval Hierarchy: User1>User2>User3>User4>User5
if user3 sends it to UserX then once approved by UserX it shud come back to User3 and then should follow the hierarchy.

thanks for your reply, it seems AME have to be used.
to answer why i need this, consider this business scenerio
Lets say requestor raises PR and sends it to his manager to verify the details, manager then sends it to budget team to verify budget, they send it to HOD for final approval.
this was default hierarchy.
Now lets say budget team wants to discuss the case with HR for some requisition(Exception) here comes forward option handy, and budget team forwards it to HR team(who is not in default hierarchy) gets the feedback, and then decides whether to approve or reject and then it follows again the same hierarchy i.e. goes to HOD
In case if i use approval limit, it is destined to end at the point i send it to HR,
coz case1: they have approval limit less than the PR amount, it ends with "No approver found"
Case2: They have approval limit more than the PR amount, it ends with Approved status.
So how do i go with AME in this case? just install AME and use "Purchase_req" seeded "Approval transaction type"

Similar Messages

  • Purchase Requisition action have submit but not forward(is null)

    Dear all,
    Purchase Requisition action history have "submit" but not "forward"(it is null), and PR header status is "In Process", why? please help me, tks.
    Regards
    Edited by: user3392434 on 2012/2/15 下午 9:51

    user3392434 wrote:
    Dear all,
    Purchase Requisition action history have "submit" but not "forward"(it is null), and PR header status is "In Process", why? please help me, tks.
    Regards
    Edited by: user3392434 on 2012/2/15 下午 9:51which approval process are you using in your system??
    Thanks
    Mahendra

  • Purchase requisition with out material master - options

    Hi experts
    I wish to establish a control in Purchase requisition that, when the user enters item with out material master record (only enters text), system should give  a pop for decision options yes or no.
    Please let me know the userexit useful to map this while saving the document.
    regards
    marias

    Hi
    This userexit is specifically for Customers' Own Data in Purchase Requisition. we need to provide data. My scenario does not involve entry of new data and to verify the PR item data already entered.
    regards
    marias

  • Adding Print option in purchase requisition menu in ME51N

    Hi Guru's,
    I have a requirement to add print option in the menu 'purchase requisition' in the transaction ME51N.
    I couldn't find any menu exits for this
    Please  Help me in this regard.
    Thanks & Regards,
    Sastry

    Hi Kavitha,
    Check this first.
    Regards
    Edy

  • Service purchase requisition/order with Material group optional

    Is it possible to create a purchase requisition/order with item category D (services) without entering any material group?
    We would like to enter only the G/L account but not the material group.

    Hi,
    It is not possible to create PR/PO without material / Service group & Item catagory D.
    Better create service groups like material group which will help you for reports also.
    Regards,
    Manish Jain

  • Purchase requisition - are there any other options instead of SRM

    Hello,
    We would like to work with some purchase requisition in cProjects for external service provider we need for our projects. We are using hierarchical Accounting with PS. The first possibility is using SRM I think. The second way is the use of the network in PS which we would have to build up manually. Unfortunately we don't want to use SRM and therefore I am searching for some other ways to handle the purchase requisition...
    Any Suggestion?
    Thx in advance and have a nice day,
      Max
    icq: 130405000
    msn: joshuax112

    Hello Thomas,
    I was worried about getting an answer like this .. and there are dozen of other questions still waiting for an answer that could look like this. Nevertheless this answers is better than searching in the hope of finding something
    Thanks for your reply an have a nice day,
      Max
    P.S. Is there somewhere an german community I can send my whole business scenario with a lot of questions?

  • Fixed purchase requisitions in MD04

    Hello experts,
    When users launch MRP, the only elements that are changed are planned orders and purchase requisitions. Is there any way to have the same behaviour for fixed planned orders and fixed purchase requisitions??
    Thanks in advance.
    Laura.

    Laura, Let me use 'firmed' instead of 'fixed' in my reply.
    1. Firmed Planned Orders:
      There is an option in the MRP type config called 'Roll forward period'. This option can be set with a -/+ sign to delete firmed planned orders either in past or future respectively.
    Any planned order rendered useless but still lying in the system just because of the fimed indicator can be deleted with this setting.
    A firmed planned order on a maximum can firm the BOM components underneath and there are no follow-up actions/responsibilities/obligations required for planners, if required.
    A planning re-run may sort the issue quickly with out further consultations required with shop floor personnel for instance.
    Hence the deletion option is made available for firmed planned orders in SAP standard.
    2.Firmed Purchase Requisitions:
        Other than manual changes which make the PR firmed, there are other related actions like PurReq release procedure/status which also makes system consider that the PR is firmed and does not allow further changes.  
    During Planning run system does a simple source determination and during the purchasing source determination there is an extended set of activities that come into picture.
    So the message is a lot of follow-up activities are still possible with respect to a PR and hence in standard we do not have some similar option for PR's like the roll-forward period available for planned orders.

  • Purchase requisition (msg error)

    hi
    during the inception of the purchase requisition, and Once I click ENTRE after going to enter the material code. SAP displays the following message :
    ""Conflicts in screen size; for more information, see the note SAP 570861""
    what this means ?
    best regards

    hi,
    release note:
    Summary
    Symptom
    Elements in subscreens are only partly displayed or cannot be scrolled correctly.
    NetWeaver Business Client
    In the NetWeaver Business Client, as a result of the warning dialog, the system displays the following dialog:
    "Server Busy.
    This action cannot be completed because the other program is busy. Choose #Switch To# to activate the busy program..."
    You are unable to avoid the second dialog. Simply choose "Switch To" and close the original warning dialog. Since the warning dialog and the second dialog are not displayed in the customer system, this is not really problematic.
    Other terms
    Resize
    Reason and Prerequisites
    These types of errors may be due to conflicts in size between subscreens and their elements.
    Solution
    This is an ABAP application error that must be corrected by the application programmer responsible for ABAP. The easiest way to find the application component that is responsible is as follows:
    After you reach the screen that contains the error, choose the "System/Status..." menu option. Then double-click the transaction name in the "Transaction" field. On the next screen, choose the "Goto/Object directory entry" menu option. Double-click the package to display the application component that is responsible.
    Background information:
    As of patch 22 (Version 2766 of sapfront.dll) for the 620 GUI and subsequent versions of SAP GUI for Windows, the size of subscreens and their elements is checked at the front end. If conflicts occur, they are logged in an error log file (for example, sapfewdll_XX_XXXX_XX_XXXX.err.trc) in \SapWorkDir (Note 360504). A dialog box referring to the conflicts may appear before the incorrect screen is displayed. The display of this dialog box can be activated or deactivated in the front-end options (Options (Alt+F12) -> Options -> Activate Dialog Window for Screen Size Check##).
    As of patch level 39 of the SAP GUI for Windows 6.20 and subsequent versions of SAP GUI for Windows, customers can only activate or deactivate this check (size checking) by modifying the registry. If the entry "CheckDynproSize" under
    \HKEY_CURRENT_USER\Software\SAP\SAPGUI Front\SAP Frontend Server\ Customize\
    is filled with the value 1 (DWORD), it is activated, and if the value is 0, it is deactivated. You have to create the entry if it does not exist.
    The error log file should be forwarded to the development department of the ABAP program in question so that the error can be eliminated.
    You can use Note 324687 to display the subscreen borders. You can use transaction ST20 to analyze and display the screen trace recording. For example: For information about analyzing the subscreen call hierarchy (subscreen tree), see Note 365940.
    If a checkbox is the last element on the right of a subscreen or step loop, you can ignore this error message.
    hope this may help you,
    Regards,
    Srinivas

  • Error in creation of purchase requisition

    Hello Sap Guru,
    When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?
    If anyone can please explain the reason & solution of this error.
    Thanks In advance
    Deepak Garg

    {code)When we are trying to create a purchase requisition under t.code ME51N, we are getting error message "enter valuation price"?{code)
    Hi,
    it is sap standard process when you create PR and if material master record exist the price is automatically taken from the valuation price field. if record not exist enter lum sum price of requested material price.
    When purchase guy create po with reference to Pr they can change valuation price also.
    In custommization for Purchasing under Purchase Requisition -> Define Screen Layout at Document Level, you can set price and price unit. The Valuation price field can be set as a mandatory or optional input field.

  • Generated a report which gives PR(Purchase Requisition) analysis using ALV.

    hi experts,
    please give me tables and fields for following report, and also exlain me briefly,
    Generated a report which gives PR(Purchase Requisition) analysis using ALV.
    thanks in advance,
    radhakrishna

    Hi
    please find this report which link SO PO PR and Prd Ord and there status.
    >
    REPORT z_so_info.
    TABLES: vbak, vbap, afko, afpo.
    *Field catalog
    TYPE-POOLS: slis.
    DATA: lv_repid TYPE sy-repid VALUE sy-repid,
    xfield TYPE slis_t_fieldcat_alv,
    afield TYPE slis_fieldcat_alv.
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 1(25) text-002.
    SELECT-OPTIONS: so_so FOR vbak-vbeln OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SELECTION-SCREEN END OF BLOCK b1.
    SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-003.
    PARAMETERS:
    p_kunnr LIKE vbak-kunnr, " sold-to
    p_kunwe LIKE vbak-kunnr. " ship-to
    SELECTION-SCREEN END OF BLOCK b2.
    *Constants
    CONSTANTS: c_zor TYPE vbak-auart VALUE 'ZOR',
    c_we TYPE vbpa-parvw VALUE 'WE',
    c_ag TYPE vbpa-parvw VALUE 'AG'.
    c_space TYPE space.
    *Ranges
    RANGES: ra_parvw FOR vbpa-parvw,
    ra_kunnr FOR vbpa-kunnr.
    *Tables
    DATA: BEGIN OF gt_output OCCURS 0,
    vbeln LIKE vbak-vbeln, " sales order number
    posnr LIKE vbap-posnr, " SO item number
    matnr LIKE vbap-matnr, " material number
    sh LIKE vbpa-kunnr, " Ship-to
    sp LIKE vbpa-kunnr, " Sold-to
    lifnr LIKE ekko-lifnr, " Vendor
    bstnk LIKE vbak-bstnk, " PO number
    banfn LIKE vbep-banfn, " Purchase requi
    po_st TYPE char30, " PO status text
    pstyv TYPE vbap-pstyv, " Item catagory
    aufnr LIKE afpo-aufnr, " Production Order
    prd_stat TYPE string, " Prd order status
    END OF gt_output.
    DATA: wa_output LIKE gt_output.
    FIELD-SYMBOLS: <fs_output> LIKE gt_output.
    *Table for sales order and PO
    TYPES : BEGIN OF gs_data,
    vbeln TYPE vbak-vbeln,
    posnr TYPE vbap-posnr,
    pstyv TYPE vbap-pstyv,
    matnr TYPE vbap-matnr,
    END OF gs_data.
    DATA: gt_data TYPE STANDARD TABLE OF gs_data,
    wa_data TYPE gs_data.
    *Table for Production Orders
    TYPES: BEGIN OF gs_prd,
    aufnr TYPE afpo-aufnr,
    posnr TYPE afpo-posnr,
    kdauf TYPE afpo-kdauf,
    kdpos TYPE afpo-kdpos,
    wepos TYPE afpo-wepos, "Goods Receipt Indicator
    elikz TYPE afpo-elikz, "Delivery Completed Indicator
    objnr TYPE aufk-objnr, "Object number
    getri TYPE afko-getri, "Confirmed Order Finish Date
    gltri TYPE afko-gltri, "Actual finish date
    END OF gs_prd.
    DATA: gt_prd TYPE STANDARD TABLE OF gs_prd,
    wa_prd TYPE gs_prd.
    *Table for partner data
    TYPES: BEGIN OF gs_partner,
    vbeln TYPE vbak-vbeln,
    posnr TYPE vbap-posnr,
    parvw TYPE vbpa-parvw,
    kunnr TYPE vbpa-kunnr,
    END OF gs_partner.
    DATA: gt_partner TYPE STANDARD TABLE OF gs_partner,
    wa_partner TYPE gs_partner.
    TYPES: BEGIN OF gs_po,
    ebeln TYPE ekkn-ebeln,
    ebelp TYPE ekkn-ebelp,
    vbeln TYPE ekkn-vbeln,
    vbelp TYPE ekkn-vbelp,
    END OF gs_po.
    DATA: gt_po TYPE STANDARD TABLE OF gs_po,
    wa_po TYPE gs_po.
    TYPES: BEGIN OF gs_preq,
    vbeln TYPE vbep-vbeln,
    posnr TYPE vbep-posnr,
    banfn TYPE vbep-banfn,
    END OF gs_preq.
    DATA: gt_preq TYPE STANDARD TABLE OF gs_preq,
    wa_preq TYPE gs_preq.
    TYPES: BEGIN OF gs_po_stat,
    ebeln TYPE ekko-ebeln,
    procstat TYPE ekko-procstat,
    lifnr TYPE ekko-lifnr,
    END OF gs_po_stat.
    DATA: gt_po_stat TYPE STANDARD TABLE OF gs_po_stat,
    wa_po_stat TYPE gs_po_stat.
    *Field symbols
    FIELD-SYMBOLS: <fs> TYPE tj02t-txt04,
    <fs_temp> TYPE tj02t-txt04,
    <fs_stat> TYPE char30.
    START-OF-SELECTION.
    PERFORM fr_build_range.
    PERFORM fr_get_data.
    PERFORM fr_build_fc.
    PERFORM fr_output.
    *& Form fr_get_data
    text
    --> p1 text
    <-- p2 text
    FORM fr_get_data.
    *Get SO
    SELECT avbeln aposnr apstyv amatnr
    FROM vbap AS a
    JOIN vbak AS b
    ON avbeln = bvbeln
    JOIN vbpa AS c
    ON bvbeln = cvbeln
    INTO TABLE gt_data
    WHERE b~vbeln IN so_so
    AND b~auart EQ c_zor "Only Sales Orders
    AND c~kunnr IN ra_kunnr. "from selection screen
    DELETE ADJACENT DUPLICATES FROM gt_data COMPARING vbeln posnr.
    *get data of the production order
    IF NOT gt_data[] IS INITIAL.
    SELECT aaufnr aposnr akdauf akdpos awepos aelikz
    b~objnr
    FROM afpo AS a
    JOIN aufk AS b
    ON aaufnr = baufnr
    INTO TABLE gt_prd
    FOR ALL ENTRIES IN gt_data
    WHERE a~kdauf EQ gt_data-vbeln
    AND a~kdpos EQ gt_data-posnr.
    ENDIF.
    *Get partner data
    IF NOT gt_data[] IS INITIAL.
    SELECT vbeln posnr parvw kunnr
    FROM vbpa
    INTO TABLE gt_partner
    FOR ALL ENTRIES IN gt_data
    WHERE vbeln EQ gt_data-vbeln.
    ENDIF.
    *Get Purchase Order
    IF NOT gt_data[] IS INITIAL.
    SELECT ebeln ebelp vbeln vbelp
    FROM ekkn
    INTO TABLE gt_po
    FOR ALL ENTRIES IN gt_data
    WHERE vbeln EQ gt_data-vbeln
    AND vbelp EQ gt_data-posnr.
    SELECT vbeln posnr banfn
    FROM vbep
    INTO TABLE gt_preq
    FOR ALL ENTRIES IN gt_data
    WHERE vbeln EQ gt_data-vbeln
    AND posnr EQ gt_data-posnr.
    ENDIF.
    IF NOT gt_po[] IS INITIAL.
    SELECT aebeln aprocstat a~lifnr
    FROM ekko AS a
    JOIN ekpo AS b
    ON aebeln = bebeln
    INTO TABLE gt_po_stat
    FOR ALL ENTRIES IN gt_po
    WHERE b~ebeln EQ gt_po-ebeln
    AND b~ebelp EQ gt_po-ebelp.
    ENDIF.
    *Move data to output table
    LOOP AT gt_data INTO wa_data.
    wa_output-vbeln = wa_data-vbeln.
    wa_output-posnr = wa_data-posnr.
    wa_output-pstyv = wa_data-pstyv.
    wa_output-matnr = wa_data-matnr.
    READ TABLE gt_po INTO wa_po WITH KEY vbeln = wa_data-vbeln
    vbelp = wa_data-posnr.
    IF sy-subrc EQ 0.
    wa_output-bstnk = wa_po-ebeln.
    READ TABLE gt_po_stat INTO wa_po_stat WITH KEY ebeln = wa_po-ebeln.
    IF sy-subrc EQ 0.
    wa_output-lifnr = wa_po_stat-lifnr.
    CASE wa_po_stat-procstat.
    WHEN '01'.
    wa_output-po_st = 'Version in process'.
    WHEN '02'.
    wa_output-po_st = 'Active'.
    WHEN '03'.
    wa_output-po_st = 'In release'.
    WHEN '04'.
    wa_output-po_st = 'Partially released'.
    WHEN '05'.
    wa_output-po_st = 'Released Completely'.
    WHEN '08'.
    wa_output-po_st = 'Rejected'.
    ENDCASE.
    ENDIF. "inner read subrc
    ENDIF. "outer read subrc
    READ TABLE gt_preq INTO wa_preq WITH KEY vbeln = wa_data-vbeln
    posnr = wa_data-posnr.
    IF sy-subrc EQ 0.
    wa_output-banfn = wa_preq-banfn.
    ENDIF.
    READ TABLE gt_prd INTO wa_prd WITH KEY kdauf = wa_data-vbeln
    kdpos = wa_data-posnr.
    IF sy-subrc EQ 0.
    wa_output-aufnr = wa_prd-aufnr.
    *get the purchase requisition for production order as well
    SELECT SINGLE banfn
    FROM ebkn
    INTO wa_output-banfn
    WHERE aufnr EQ wa_prd-aufnr.
    *Get the status of the production order
    PERFORM fr_get_prd_stat USING wa_prd-objnr
    CHANGING wa_output-prd_stat.
    ENDIF. " sy-subrc
    READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
    parvw = c_we.
    IF sy-subrc EQ 0.
    wa_output-sh = wa_partner-kunnr.
    ENDIF.
    READ TABLE gt_partner INTO wa_partner WITH KEY vbeln = wa_data-vbeln
    parvw = c_ag.
    IF sy-subrc EQ 0.
    wa_output-sp = wa_partner-kunnr.
    ENDIF.
    APPEND wa_output TO gt_output.
    CLEAR: wa_data, wa_prd,wa_partner,wa_output.
    ENDLOOP.
    ENDFORM. " fr_get_data
    *& Form fr_build_range
    text
    --> p1 text
    <-- p2 text
    FORM fr_build_range .
    *Range for partner function
    MOVE 'I' TO ra_parvw-sign.
    MOVE 'EQ' TO ra_parvw-option.
    MOVE 'SH' TO ra_parvw-low. " we
    APPEND ra_parvw.
    CLEAR ra_parvw.
    MOVE 'I' TO ra_parvw-sign.
    MOVE 'EQ' TO ra_parvw-option.
    MOVE 'SP' TO ra_parvw-low. " ag
    APPEND ra_parvw.
    CLEAR ra_parvw.
    *Range for ship-to and sold-to
    MOVE 'I' TO ra_kunnr-sign.
    MOVE 'EQ' TO ra_kunnr-option.
    MOVE p_kunnr TO ra_kunnr-low.
    APPEND ra_kunnr.
    CLEAR ra_kunnr.
    MOVE 'I' TO ra_kunnr-sign.
    MOVE 'EQ' TO ra_kunnr-option.
    MOVE p_kunwe TO ra_kunnr-low.
    APPEND ra_kunnr.
    CLEAR ra_kunnr.
    ENDFORM. " fr_build_range
    *& Form fr_build_fc
    text
    --> p1 text
    <-- p2 text
    FORM fr_build_fc .
    sales order number
    afield-fieldname = 'VBELN'.
    afield-seltext_s = 'Sales #'.
    afield-ref_tabname = 'VBAK'.
    APPEND afield TO xfield. CLEAR afield.
    sales ITEM number
    afield-fieldname = 'POSNR'.
    afield-seltext_s = 'Item #'.
    afield-ref_tabname = 'VBAP'.
    APPEND afield TO xfield. CLEAR afield.
    Material Number
    afield-fieldname = 'MATNR'.
    afield-seltext_s = 'Material #'.
    afield-ref_tabname = 'VBAP'.
    afield-outputlen = 10.
    APPEND afield TO xfield. CLEAR afield.
    *Vendor Number
    afield-fieldname = 'LIFNR'.
    afield-seltext_s = 'Vendor Num.'.
    afield-ref_tabname = 'EKKO'.
    APPEND afield TO xfield. CLEAR afield.
    ship-to-party
    afield-fieldname = 'SH'.
    afield-seltext_s = 'Ship-to'.
    afield-ref_tabname = 'VBPA'.
    APPEND afield TO xfield. CLEAR afield.
    sold-to-party
    afield-fieldname = 'SP'.
    afield-seltext_s = 'Sold-to'.
    afield-ref_tabname = 'VBPA'.
    APPEND afield TO xfield. CLEAR afield.
    *PO number
    afield-fieldname = 'BSTNK'.
    afield-seltext_s = 'PO NUM'.
    afield-ref_tabname = 'EKKO'.
    APPEND afield TO xfield. CLEAR afield.
    *PO status
    afield-fieldname = 'PO_STAT'.
    afield-seltext_s = 'Step'.
    afield-ref_tabname = 'zbacklog_v2'.
    APPEND afield TO xfield. CLEAR afield.
    *PO step status
    afield-fieldname = 'PO_ST'.
    afield-seltext_s = 'PO.Status'.
    afield-ref_tabname = 'zbacklog_v2'.
    APPEND afield TO xfield. CLEAR afield.
    *Purchase requisition
    afield-fieldname = 'BANFN'.
    afield-seltext_s = 'Pur. Req.'.
    afield-ref_tabname = 'VBEP'.
    APPEND afield TO xfield. CLEAR afield.
    *Item catagory
    afield-fieldname = 'PSTYV'.
    afield-seltext_s = 'Itm. Catg'.
    afield-ref_tabname = 'VBAP'.
    APPEND afield TO xfield. CLEAR afield.
    *Prodcution Order number
    afield-fieldname = 'AUFNR'.
    afield-seltext_m = 'Prod.Order'.
    afield-ref_tabname = 'AFKO'.
    APPEND afield TO xfield. CLEAR afield.
    *PRODCUTION status
    afield-fieldname = 'PRD_STAT'.
    afield-seltext_s = 'Prd. Step'.
    afield-ref_tabname = 'zbacklog_v2'.
    afield-outputlen = 20.
    APPEND afield TO xfield. CLEAR afield.
    *PRODUCTION step status
    afield-fieldname = 'PRD_ST'.
    afield-seltext_s = 'Prd. Status'.
    afield-ref_tabname = 'zbacklog_v2'.
    APPEND afield TO xfield. CLEAR afield.
    ENDFORM. " fr_build_fc
    *& Form fr_output
    text
    --> p1 text
    <-- p2 text
    FORM fr_output .
    CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
    i_callback_program = sy-repid
    I_CALLBACK_PF_STATUS_SET = ' '
    I_CALLBACK_USER_COMMAND = ' '
    I_STRUCTURE_NAME =
    IS_LAYOUT =
    it_fieldcat = xfield[]
    i_default = 'X'
    i_save = 'A'
    TABLES
    t_outtab = gt_output
    EXCEPTIONS
    program_error = 1
    OTHERS = 2.
    ENDFORM. " fr_output
    *& Form fr_get_prd_stat
    text
    -->P_WA_PRD_OBJNR text
    FORM fr_get_prd_stat USING p_objnr CHANGING p_prd_stat.
    DATA: lt_status TYPE STANDARD TABLE OF jstat,
    wa_status TYPE jstat,
    lv_status TYPE tj02t-txt04,
    lv_temp2 TYPE char5,
    lv_buff TYPE string.
    CALL FUNCTION 'STATUS_READ'
    EXPORTING
    client = sy-mandt
    objnr = p_objnr
    only_active = 'X'
    TABLES
    status = lt_status
    EXCEPTIONS
    object_not_found = 1
    OTHERS = 2.
    LOOP AT lt_status INTO wa_status.
    IF wa_status-stat(1) EQ 'I'.
    SELECT txt04 FROM tj02t
    INTO lv_status
    WHERE istat EQ wa_status-stat
    AND spras EQ 'E'.
    ENDSELECT.
    lv_temp2 = lv_status.
    CONCATENATE lv_temp2 p_prd_stat INTO p_prd_stat
    SEPARATED BY ','.
    ENDIF.
    CLEAR: wa_status, lv_status, lv_temp2.
    ENDLOOP.
    lv_buff = p_prd_stat.
    *Status of Production Order
    IF lv_buff CS 'CRTD'.
    p_prd_stat = 'Not Active'.
    ENDIF.
    IF lv_buff CS 'REL'.
    IF lv_buff CS 'GMPS'.
    p_prd_stat = 'Printed In Prod'.
    ELSE.
    p_prd_stat = 'Printed'.
    ENDIF.
    ENDIF.
    IF lv_buff CS 'TECO'.
    p_prd_stat = 'Technically Compt.'.
    ENDIF.
    ENDFORM. " fr_get_prd_stat
    >

  • Number range purchase requisitions at storage location level

    How can I define a number range for purchase requisitions at storage location level? I have one plant with several storage locations and I want a number range for purchase requisitions per storage location.

    what is the background to this request?
    I guess that the requestor can easily identify their own requisitions among many.
    I dont think that this is necessary with SAP, do not put to much importance in numbers, there are many other options to meet the users requirements.

  • How to change an Existing  Purchase Requisition Document in MM.

    Hi Folks,
    I want to write a program to change a existing  Purchase Requisition in MM.
    I found two BAPI's BAPI_PR_CHANGE and BAPI_REQUISITION_CHANGE , which could be used to change PR document in  ECC.
    I have following question:
    1) why we have two seprate BAPI's for changing PR.
    2) Do we need to use both BAPI's to change PR, depending on what value we are trying to change.
    3) Is it optional to use any of these two BAPI's
    Or do we have any other way to implement this PR change process.( Bcoz of when i tried to debug standard PR change process, none of these two BAPI's has been called)
    Which FM or method is called when, we try to change and save PR document manually.
    I would appriciate, if some one has any sample code to implement this PR change process.
    Regards
    PG
    Edited by: PG on Aug 23, 2010 3:10 PM

    >
    PG wrote:
    > I have following question:
    > 1) why we have two seprate BAPI's for changing PR.
    BAPI_REQUISITION_CHANGE is the older BAPI, the one based on the older ERP transaction (ME5x family), while BAPI_PR_CHANGE is the newest one, referring to the "recent" Enjoy transaction (ME5xN family).
    They both satisfy you task probably, but if you can chose, I'd go for BAPI_PR_CHANGE.
    >
    PG wrote:
    > 2) Do we need to use both BAPI's to change PR, depending on what value we are trying to change.
    > 3) Is it optional to use any of these two BAPI's
    You can use the first or the second one, it's indifferent. The newest one will also trigger user exits from ME5xN family. Which transactions are used by the users on the ERP? Choose with regards to the transactions used during the normal activity.
    >
    PG wrote:
    > Or do we have any other way to implement this PR change process.( Bcoz of when i tried to debug standard PR change process, none of these two BAPI's has been called)
    Normal PR change operativity doesn't use BAPI. BAPIs are used to create/modify docs from "external" systems (it's not properly true, but let assume it), they provide a simple interface to populate with PR data and the process of creation/modification will trigger every check/userexit already defined for the standard transactions on the ERP.
    In example, suppose that in ME51N you defined a custom check in a specific userexit which don't allow an user to create a material item which have odd quantity (odd example, I know ). Then using BAPI_PR_CREATE you will not be able to create a PR with items with odd quantity, because the same check will be executed.

  • How to change line type on EAM Purchase Requisitions

    When an EAM Work Order is released, we get Purchase Requisitions with the Line Type as the Purchasing Options default. This can be changed on the req but there is no option to select the req line type on the EAM Work Order page.
    There's a Line Type field on the EAM Work Order page but it's different from the Requisition Line Type.
    Just wondering what are our options to give users the ability to select req line type from EAM Work Order page. We know personalization is an option but we'd need to add a brand new field and even if we do, we are unsure that ReqImport will actually use this new field.
    Workflow extensions could also be a solution and was hoping that someone out there would have some tips and tricks to share.
    Regards,
    Sanjib

    I think the only way is to:
    1) read the address data from Matrix 178 and keep the data in your Add-On
    2) delete the original address (activate the menu item (ID = 1293) or send Ctrl-K via Application.SendKeys)
    3) "click" on "Define new"
    4) and enter the data you have read in 1) into the cells of Matrix 178 again...
    HTH

  • Payment history in Item head ( status tab) of Purchase requisition

    Dear group members,
    In purchase requisition, in item head, in status tab we can find the history of
    1. Purchase Order
    2 service entry sheet
    3. Goods receipt entry sheet
    4. Invoice entry
    5. Down payment
    6. Credit memo
    Here i need the information of payment made vendor
    My user makes payment from F-53
    How can i get the history of payment made to vendor in purchase requisition (in status tab?)
    Regard
    shamulheq

    Hi !Paul Shrewsbury  
    When vendor payment is made through F-53 is their any option to make payment to vendor by selecting purchase order number? Her we make full payment for the invoice, no open item balance in vendor a/c
    In my company if we make downpaymenf-48 to vendor by selecting the purchase order it reflects in purchase order history/Purchase requisition status tab
    If u can put some more light on this it will be great help for me
    Regards
    shamulheq

  • Purchase Requisition Transfers from SCM 5.0 APO to R/3

    I am working on SCM 5.0 -- transferring Purchase Requisitions from APO to R/3 from SNP heurristic run. I am wondering if there is any documented procedure of available options and the steps involved in setting up.
    Can you transfer only certain Purchase Requisitions instead of ALL?
    Can you setup approval workflow to allow the transfer of only approved PRs ?
    What steps involved to get PRs from the SNP Heuristic?
    I found the IMG Activity (SAP SCM – Implementation Guide &#61614; Advanced Planning and Optimization &#61664; Supply Chain Planning &#61664; Supply Network Planning (SNP) &#61664; Basic Settings &#61664; Configure Transfer to OLTP system).
    I shall greatly apprecaite if some one answers the questions and points me to some 'How to Guide or the steps involved in setting up'.
    Thanks

    Devendra,
    You actually need the SCM-APO-CIF  (Core Interface) Training for this. A Pre-requisite to that is the APO Overview.  Have you undergone it ?
    In Short i will tell you the answers you want ...  I hope you will reward me with Points if you feel it was helpful.
    To Transfer PRs from APO to R3 following setup is needed ..
    - Do Configuration of  STO (Stock Transfer) in R3.  Ensure Stock Transfer PRs and STOs between the 2 Plants can be created Manually in R3.  This will require you to do a Lot of MM & SD Configuration on IntraCompany STOs.
    A Key Part for APO is to set the STO Order Types for the
    Source and Destination Plant,  Assign Vendor to the Shipping Plant,  Customer to the Destination Plant .. etc. A Test of correct setup is your ability to create a PR and STO manually in R3 first before you do APO.
    - Setup of all APO Locations (Plants in SAP-R3), Products (Materials in SAP-R3).  These are done via the Location and Product Integration Models.  Make sure you have defined the Timezone in the Plant and set the Plant in SAP as DC or Production Plant (Refer CIF Training).
    -  Setup of  Transport Lanes in APO (done manually in APO).
    You define Transport Durations here.
    -  You have to have the Purchase Requisition Integration Model Active for those Product Locations.  To do the Integration Model all CIF Configuration including the one IMG you have described in your Question is to be done. Assuming that the Products are set to 'X0' MRP Type in R3 ... so they are set to Planning in APO.
    -  For Setup in "Configure Transfer to OLTP" it is best to select 'Periodic Transfer' so you can actually control the Product-Locations and Date Range of PRs APO has created.  The Planning Runs create 'Change Pointers' to send the PRs to R3.
    - Define in APO that you will be sending Purchase Requisitions at your Destination Location to R3.  You use 'Publish Change Pointers' - /sapapo/cp1 to do this.
    - The Change Pointers are created after APO Planning run which can be sent to R3 using /sapapo/c5.  You should send them periodically after you're satisfied with the planning results or in Night Batch runs after your Planning run.
    -  To Control some type of PRs you will have to use User Exits in APO for CIF that send External Procurement / PRs from APO to R3.  This is not Standard.  But I am not sure why you will  have different types of PRs for Stock Transfer between 2 Plants.  There is no need.  You can control PRs between 2 Locations to not go to R3, via the selection of locations in /sapapo/c5.
    Hope you find this usefull.
    Regards,
    Ambrish Mathur

Maybe you are looking for