Purchase requisition rejection WS65400027

Hello all,
my customer has found out that after upgrade from 4.6 to 6.0 the purchase requisition rejection isnt announced to the PR creator.
I have activated the WS65400027 workflow for the REJECTION_START event (connected type in SWE2 and set the WS65400027 and TS 65400032 as a general task in OCCU as described in SAP notes for this particular workflow).
However the generated workitem is not coming only to the PR creator but to every single SAP user.
Release strategies and workflow for the PR releasing is properly customized.
Thanx for any tips
Petr

Hello Peter !
                In standard workflow, for the task TS65400032, you have to choose "Workflow initiator(expression)" for initiator to receive the work item.Verify whether initiator is maintained as mentioned above.
                You've stated as follows :
However the generated workitem is not coming only to the PR creator but to every single SAP user.
                This means whether the work item for this task is sent to every SAP user except the initiator ?
Regards,
S.Suresh.

Similar Messages

  • Error While Creating Workflow for Purchase Requisition Rejection

    HI Experts,
    Purchase Requisition No is not Displaying in the Business Workplace Inbox after my Work  flow got triggered.
    In Work flow i am Using the Task  97600004  which i copied from the Standard Task  65400032. This Task i called in the Activity Step having Work Item Display Tab. In this Tab while i am checking at Work Item Text  for Identification  of Work item in work flow inbox level it is Giving Error "Container element '_WI_OBJECT_ID' does not exist and also Insert Expression is in Disable Mode.
    In Business Workplace Inbox i am getting message as "Purchase requisition  00000 rejected".
    Please Suggest where i am Committing Error.
    Thanks in Advance
    Srikanth Kumar

    HI.
    I Have Checked the work flow as suggested Dheepak
    In Start Event of Work flow i declared BUS2105 as BOR Object . The Task which i copied contains BUS2009 as default.
    As Raj Suggested In Task i have Created a New Element BUS2105 at Container Tab and set binding in task and set the Binding between Work flow and Task. Now it is working fine and i am getting the PR No in the Message of SBWP inbox.
    But i Having one more doubt regarding this issue only Why BUS2009 BOR object Type is not working which is the Task as default even though its binding is set between work flow and task?
    Thanks Dheepak and Raj for Your Valuable Suggestions. My gmail id is srikanth537. Can u add me In your Friends list.
    Thanks
    Srikanth Kumar
    09937876902
    Edited by: Srikanth Kumar Talasu on Dec 23, 2008 11:59 AM

  • Rejection of a purchase order or purchase requisition.

    Hello,
    I know this is a question that was asked many times before, but nobody was able to give a clear answer to it.
    The objects purchase order(BUS2012) and purchase requisition(BUS2105) do not have between their methods, the rejection. But they contain the event REJECTED(rejection start). 
    Let's say i create a purchase requisition in me51n. If i want to approve it in an Abap program, I can use the function BAPI_REQUISITION_RELEASE_GEN. But what if i want to reject the requisition?
    PS: I know that i can use workflow, but this is not the case.
    Thank you,
    Efren

    Hello,
    I think you are are right, but i have a question.
    If you create a purchase requisition in me51n, then it will appear in me55( it can be released or rejected in me55). Iif i do not approve the requisition, it is clear that i am rejecting it...but it will remain in me55,no?
    And one more question. I think you know that if you create a workflow where you send a workitem with the release of a purchase requisition/order, the receiver can reject it. Clicking the reject button really does nothing? It is just for design?
    Thanks,
    Efren

  • BAPI to reject purchase requisition

    Dear All,
    Iu2019m looking forward a BAPI to reject purchase requisition. I found below BAPIs for purchase requisition but I couldn't  find any BAPI to reject requisition? I wonder whether a BAPI exists to reject purchase requisition or not. Thanks in advance.
    - BAPI_REQUISITION_RELEASE
    - BAPI_REQUISITION_RELEASE_GEN
    - BAPI_REQUISITION_RESET_RELEASE
    - BAPI_REQUISITION_RESET_REL_GEN
    - BAPI_REQUISITION_CHANGE
    - BAPI_REQUISITION_CREATE
    - BAPI_REQUISITION_DELETE
    - BAPI_REQUISITION_GETDETAIL
    - BAPI_REQUISITION_GETITEMS
    - BAPI_REQUISITION_GETITEMSREL
    - BAPI_REQUISITION_GETRELINFO

    aarioglu,
    I am facing to the same problem.
    Did you solve it?
    Thanks in advance.
    Felipe Fernandes

  • Reject Purchase Requisition

    Warm Greetings !!!!!!!!!!!!!
    With Reference to Release Strategy of Purchase requisition
    After higher level release preceding level can still reject the purchase requisition example:
    Below release for the level 100000/=
    User create PR /                                                                   Use
    1st level of release  Parts manager /                                   Charles
    2nd level of release  service manager                                Zeeyaudeen
    3rd level of release  service Director                                  Mohamed Ali
    If Charles rejects the PR after released by Zeeyaudeen and Mohamed ali system allows to reject with out any error message. Is this an expected system behavior? Appreciate your advice
    Share with me how it can be prevented to reject preceding PR with out their permission
    Thanks & best wishes
    Regards
    Shamulheq

    Hi shamulheq ,
    This can be handled by AG modification/ remove from user .
    Regards,
    Yagnesh Bhatt

  • Collective reject for Purchase Requisition

    Hi all,
    How can I reject Purchase Requisition on ME55 without using workflow?
    Best regards,
    Munur

    Hi,
    ME55 is for collective release for PR. You can reject the PR by giving the desired code and select X button or reject in ME54. You cannot reject collectively in ME55. There is no reject button in ME55. Here we will give release code and release group and execute , the sys displays the list of PRS we can save these PRs as releaswe and select the status to need release by another code. Thanking you.
    Edited by: Padmasri Garapati on Nov 17, 2011 6:53 AM

  • Rejected Purchase Requisitions + shopping cart

    Hi,
    I have this requirement:
    develop a report to extract (every day) all the rejected Purchase Requisitions and their  items (only items that have status rejected).
    how to those rejected Purchase Requisitions ?
    Many thanks

    CLOSED

  • Rejection(release refused) of Purchase requisition?

    Hi all,
    Sorry to post again.
    In ECC 6.0 i have to reject a Purchase Requisition in the transaction ME54N.
    When i am rejecting a PR in ME54N an event in Business object type BUS2105  called 'Rejection_start' is getting triggered. There are two more event in this business object 'Rejected' and 'Rejected_stop'. This is the root cause of my doubt.
    Will PR be rejected by just pressing the Reject button in the transaction ME54N or there is some more to be done.
    Regards,
    Gautham P

    Hi,
    Just click on the reject button and save the PR, then the PR gets rejected.
    As you are asking about the bussiness object BUS2105 and the events in the business object the details are as follows:
    Rejected' : This event is triggered when you are pressing the reject button and save the PR
    'Rejected_stop' : This event is triggered when you are cancelling the rejection ( You are approving the PR by pressing release button) after rejection of PR.
    Regards,
    sampath

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
    When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
    If no other release strategy is determined by the reduction of the
    amount or value, the system will keep already existing releases.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

  • How to Reject Purchase Requisition

    Hi All
    I tried using ME UPDATE REQUISITION but its not working.
    If anyone had tried this function module before to reject the purchase requisition, please guide me how to use it
    Or is there is any other way to Reject Purchase Requisition.

    hiii
    you can use BAPI_REQUISITION_CHANGE
    FM to reject purchase requision.
    regards
    twinkal

  • Purchase Requisition number not changing when sales order item is rejected

    Hi all,
    I have a requirement to change the sales order status to 'TECO' when ever some reason for rejection is selected in the status tab at the item level.The status should change from 'TECO' when i remove the reason for rejection.
    The status change is happening correctly.I have achieved it using user exit.
    CASE 1 : Initially, when a new item is added in the Sales order the purchase requisition number appears in the schedule lines tab of the item level. This is as expected.
    CASE 2 :When the same item is blocked (by entering a reason for rejection in status tab of VA02 ) then the purchase requisition number is not present in the schedule lines tab.This is as expected.
    But i face the following issue.
    CASE3 : Again if the blocked item is unblocked (By removing the reason for rejection in status tab of VA02 ) then the purchase requisition number does not appear again in the schedule lines tab.The purchase requisition number is expected to appear again.
    This happens in case of DROP SHIPMENT scenario. I understand that in case of dropshipment scenario the purchase requisition number is triggered by item category and schedule lines only.
    I tried to make the changes(to change the status ) in user exits 'MV45AFZZ' and also 'MV45AFZB'.But i face the issue in both the exits.Please let me know if there are any means to solve this issue(as mentioned in case 3).
    Regards,
    S.Suba

    Many thanks for your answer. It help me to solve the issue.
    So applying note 738171, with transaction OVB5 (or VOFM, requirements->subsequent functions->Purch.requisitions) we create one new requirement, ie RV07A900, and then we apply the rule that if we have delivery or billing block, that is, VBAK-LIFSK or VBAK-FAKSK not empty, then we set an error with a code similar to this:
                da_sy-msgid = 'Z1'.    (message class)
                da_sy-msgno = '001'.  (message number)
                error_exception = true.
    and then the PR is not created.
    Regards.

  • Rejecting an entire Purchase Requisition

    Hi,
    Is there any way to reject an entire Purchase requisition in SAP? I use Tcode ME54N for this, but I can reject the PR only item by item. If PR has more material items, it takes much time to reject the item one by one.
    Any one please help me on this?
    Thanks
    Rajee

    I don't think there is way to do it in standard SAP. I added the following fields in the table MASSFLDLST to make them appear in TCode MASS, they show up and it even gives a success message saying the PR is changed but the PR never gets changed.
    BUS2105   EBAN                          EBAKZ
    BUS2105   EBAN                          LOEKZ
    I think you need to develop a custom abap program to do this mass job.

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

  • PO creation from One Purchase Requisition

    Dear all;
    In standard SAP We can create multiple PO from A single PReq ,though the full quantity of PReq is taken first time of PO creation .Is there any restriction that After full use PReq quantity no one can use the same PReq for further PO creation.
    Thanking You;
    Regards;
    Joydeep Mukherjee

    Dear Joydeep,
    In contrast to a purchase requisition, it is possible to create more than one PO in reference to a RFQ.
    A RFQ only gives information about the price for which can be ordered from a vendor. The system does therefore not reject you from ordering again from the same vendor with the best conditions.
    Once you create a PO with reference to an RFQ, if the quantity in PR to which the RFQ is refering is exhausted,
    the user is prevented from creating further PO only with reference to the PR. But the user can create Purchase orders refering to a RFQ as long as the validity period of the RFQ is still valid.
    Regards,
    ian, Wong Loke Foong

  • Purchase Requisition with wrong details - Sending back to Originator

    Hi Experts,
    In SAP Purchase Requisition contents found incorrect on the stand of technical specification then buyer do not have provision to send back it through SAP to the originator (Design department) for correction.
    At present buyer are resolving such issues on the basis of Email. Till the time PR get corrected by originator it shows pending for action on buyer’s a/c .
    Hence considering above facts request to suggest us the method for sending the Incorrect PR line items to the originator through SAP.
    Regards,
    Shekhar Gaikwad

    Hi,
       Configure release strategy for PO at item level along with workflow. The release code can be the buyer and once the buyer found any error in the technical specification, he can reject the release, which will notify the creator.
       Refer the help doc: Workflow for Reject Purchase Requisition Item (SAP Library - MM - Materials Management: Workflow Scenarios)
    Regards,
    AKPT

Maybe you are looking for