Associate new type of purchase requsition to Replenishment Planning

Hi
I have created a type of purchase requisition (ZNBB) and I can't associate it to the Replenishment Planning.
I have tried to associate it in the SRS parameters and also using the MRP Groups, but WRP1 keeps calling the standard type of requisition (NB). This is a problem for us since we have a different logic for our retail operations than for the rest of our operations.
Best Regards

Hi Patricio,
Did you found any solution to your problem.
I am searching for the same.
Regards,
Ashu

Similar Messages

  • Associate new type of purchase requisition to WRP1

    I have created a type of purchase requisition (ZNBB) and I can't associate it to the Replenishment Planning.
    I have tried to associate it in the SRS parameters and also using the MRP Groups, but WRP1 keeps calling the standard type of requisition (NB). This is a problem for us since we have a different logic for our retail operations than for the rest of our operations. Is there anyway of making WRP1 call the new purchase requisition type?
    Best Regards,
    Patrício Silva

    Hi
    Does anyone has the solution to this issue? I am also having the same issue..
    Best Regards
    Junwen

  • Validate Materials according type of Purchase Requisition

    Good morning.
    At present the system we have several types of Purchase Requsitions (document created by the ME51N) that users can use (PR for Material, PR for contracts, PR for services, etc)
    When creating the PR, the user chooses the PR type and write materials codes. The system is not Restrict the user to do things like, for a PR with type pshicical Materials,  request a service material, which is obviously wrong and generate rework.
    What we require is to know how to parameterize the system to validate that type of PR, only to order the materials associated with each type and do not let things like the example above.
    We have the material well classified by Material Group and Purchase Group. I just need to know how to assign materials to each type of PR.
    Research on this topic, I found the SPRO something I think I could serve.
    SPRO -> Materials Management -> Purchasing -> PR -> Documents types
    See here for example for PR ZS01 - PR Materials (used to order everything that is NOT services, ie physical materials), if I go to see the types of position allowed me see the following:
    Code:
    Tp.Pos | Text Pos Type
    Normal
    C Appropriation
    L Outsourcing
    I Wanted to third
    Transfer V
    F Service
    I also see that all other types of PR of which there are established, have enabled the same kind of position.
    Anyone know if this is why users can request a service for a material type PR Materials. o A physical material in a service PR?
    Could Restrict through this that for example if the user creates a type PR SERVICE, only to enter service type material (a material through the group I guess)?
    At last if i cant by parameterization, which I think is to create a Ztable with the association "MATERIAL - TYPE Purchase Requisition" and a field-exit to the fields where the materials are entered in PR to validate that the user typed material associated with this type of PR chosen and if that does not leave PR record. What I like about this solution is that the material planner will add a function over having to keep this updated Z table.
    I would appreciate opinions.

    Hi,
    By using following BADI you can put a check while saving PR
    You can put a check with reference to item category and document type , and material group of the entered material and PR document type , if required you can maintain Z table with allowed relationship or you can update the same in BADI
    (BAdI) ME_REQ_POSTED, you can trigger a variety of follow-on processing operations for purchase requisitions at the time of posting
    Thanks
    Diwakar

  • New Output type for purchase return excise invoice..?

    Hi all
      For purchase return process with exisable material.
    Here I m using the transaction
    1.J1IS to create purchase return excise invoice and
    2.J1IV for posting to accounts & print purchase return excise invoice
    .In standard SAP the output for purchase return excise invoice is JEXC.
    here my query is started,
    ABAPer created the new program for purchase return output with all new layouts,
    And from functional side i have defined new output type for the same as YEXC copying from JEXC.
    While doing the transaction J1IV, i getting the output type YEXC, i m not able to print preview.
    To proceed further i need some body guidence. Like where to assign the output type.
    some body can give some inputs .
    Thanks
    sap-mm

    Hi AP thanks for ur immediate response.
    But i have done all the configuratuion in NACE only.
    There in nace i m not able find out the mistake or missing configuration.
    Can u expalin me step by step process end to end .
    Thanks
    sap-mm

  • Define new document type for purchase order

    Hello
    I want to create a new document type for purchase ordre with also new number range.
    And within my conditions, the shopping card will be generate either document type ECPO with number range 44 or document type ZOS with number range 33.
    The document type is still a purchase order.
    Is it possible to do that? To assign new document type for purcharse order?
    If yes, is there any Badi to put my conditions of generation of my document type?
    Thank you for your help.
    Regards,
    Peggy

    Hi Markus
    Thank you four your response. Unfortuntly, i do not want to create a new transaction type.
    It is still a purchase order which could be visibled in standard transaction. The behaviour is still like standard PO, and could be visible in standard transaction PO.
    I just want to create 2 types of purchases orders to identify them, so create a new number range and so a new document type for purchase order..
    I have a condition to do "the shopping card will be created in this document type, and this schopping card will be created in this document type".
    But standard document type is ECPO, and I don't really know if it is possible to create new document type for purchase order...
    Peggy.

  • Purchase requsition and Purchase order Price Changes

    Hi All,
    When purchase requsition(XXXXXXXX) is converted in to a purchase order through ME 59N(YYYYYYYYYY),after converting in to a purchase order i will change the purchase order price to a new value.
    How can i track the price changes for a purchase order that is converted from a purchase requsition.(i know i can see the changes to a PO,under item changes for PO)
    Is this data is stored in any table?
    with regards,
    Amogh

    Hi,
    this change is not captured, because the price is being changed at the point of the PO creation and so there will be no record in the header or item changes option (the system does not see anything as being changed because this is a creation of a new PO).
    The price from the requisition is merely a suggestion and it is not meant to be a purchase price anyway (it is designed to be used to value the requisition for the  release strategy).
    I know that you can configure the system to pass this req "price" to the PO, but it is not the same price and so you will not find the type of controls that you would expect.
    In many cases a simple ABAP is written that reads POs that have a reference requisition and the ABAP compares the prices and reports on those that exceed a tolerance (either hard coded in the program or held on a new table in SAP).
    None of this is standard SAP but it is something that many people create to handle the situation where the user enters the requisition at a deliberately low value to get it through the release strategy.
    Steve B

  • Auto trigger of Purchase requsitions in Sales Order in case of Third party

    Hi,
    In a third party sales scenario, where do we set the automatic creation of Purchase requsitions when we create a third party sales order. I checked the Item category configuartion but couldn't figure it out anywhere.

    Hi Ronaldo,
    In Scheldule Line Category, for the Purchase Order Type,Please select the Options Related to Purchase Requestion.So that we you create the Order automatically the Purchase Requisation Number will get generated.
    Please Reward If Really Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Purchase requsition to purchase order

    hi all,
      I want to make a compulsory purchase requsition field in po for a particular document type only ,not the other document type for the same user?
        How we can do this? Any help
    Regards
    sri

    Hi,
    In my understanding you can not restrict the PR to PO at document level. Even if you make settings in define screen layout at document level by controlling field reference also system will allow you to  make a PO without PR.
    You can control by only user authorization, means a particular user can not make PO without PR. This is user level, but this is applicable for all document types. You can not control a particular document type by using user authorization.
    regards,
    abi

  • URGETNT: REGARDING Purchase Requsition Approval tables

    hi,
    I am making a report on purchase requsition and i have to display the details of which person has approved it and its date of approval. can anybody tell me which are the tables used in it to display it,example :-
    1st Approval - Name of d person      Date of Approval
    2nd Approval - Name of d person     Date of Approval
    3rd  Approval - Name of d person     Date of Approval
    Final Approval - Name of d person    Date of Approval
    this type of details i want to display in my report. if anybody gives me tables and details about it to make d <b><b>report ,he or she will be definately REWARDED...
    Currently i am using table <b>EBAN,EBKN</b> ..
    Regards,
    Ric.s

    Use these table to see who released and description
    T16FC  -  Release code for particular release group
    T16FD  -  Description for Release code
    T16FG  -  Release Groups
    T16FH  -  Descriptions of Release Groups
    T16FK  -  Release Statuses
    use BAPI to get release information for PR .
    BAPI_REQUISITION_GETRELINFO.
    reward points if useful.
    Regards,
    Vimal
    Message was edited by:
            Vimal Kumar

  • Urgent:regarding purchase requsitions

    HI,
    i am making purchase requsition report in which i have to display that these are the person who released the purchase requsition at dese dates.
    plzzzz help me out as i am able to display only release requsitions but not the person who had released it. i am using table eban.
    IF ANYBODY HELP ME OUT HE OR SHE WILL BE DEFINATELY REWARDED.
    Regards,
    ric.s

    Hi,
    Go through this program, you have answer
    It is possible to generate a complete list of purchase document releases with the purchase document number (requisitions and orders), releaser, release date and release time. * First, create an Infoset using transaction SQ02 directly reading from table CDPOS and create an additional table: CDHDR. If you are releasing purchase requsitions at the item level, it is convenient to create an additional field (PURPS LIKE EBAN-BNFPO) to capture the item number.
    GO THROUGH THIS CODE
    Mass Display of Purchase Orders
    Submitted by webmaster at www.sap-img.com
    Mass display or print Purchase Order History
    You can request report by :
    1. Change date
    2. User Name
    3. Purchase Order Number
    4. Vendor Code
    Written by : SAP Basis, ABAP Programming and Other IMG Stuff
    www.sap-img.com
    REPORT ZPOCHANGE LINE-SIZE 132 NO STANDARD PAGE HEADING
    LINE-COUNT 065(001)
    MESSAGE-ID VR.
    TABLES: DD04T,
    CDHDR,
    CDPOS,
    DD03L,
    DD41V,
    T685T,
    VBPA,
    TPART,
    KONVC,
    EKKO.
    SELECT-OPTIONS: XUDATE FOR CDHDR-UDATE,
    XNAME FOR CDHDR-USERNAME,
    XEBELN FOR EKKO-EBELN,
    XLIFNR FOR EKKO-LIFNR.
    SELECTION-SCREEN SKIP.
    TEXT-001 - Sorting Sequence
    SELECTION-SCREEN BEGIN OF BLOCK BLK1 WITH FRAME TITLE TEXT-001.
    PARAMETERS: SUDATE RADIOBUTTON GROUP R1,
    SNAME RADIOBUTTON GROUP R1,
    SOBID RADIOBUTTON GROUP R1.
    SELECTION-SCREEN END OF BLOCK BLK1.
    DATA: WFLAG,
    WCHANGENR LIKE CDHDR-CHANGENR.
    DATA: INDTEXT(60) TYPE C.
    DATA: BEGIN OF ICDHDR OCCURS 50.
    INCLUDE STRUCTURE CDHDR.
    DATA: END OF ICDHDR.
    DATA: BEGIN OF ICDSHW OCCURS 50.
    INCLUDE STRUCTURE CDSHW.
    DATA: END OF ICDSHW.
    DATA: BEGIN OF EKKEY,
    EBELN LIKE EKET-EBELN,
    EBELP LIKE EKET-EBELP,
    ETENR LIKE EKET-ETENR,
    END OF EKKEY.
    DATA: BEGIN OF ITAB OCCURS 50,
    BEGIN OF EKKEY,
    EBELN LIKE EKET-EBELN,
    EBELP LIKE EKET-EBELP,
    ETENR LIKE EKET-ETENR,
    END OF EKKEY,
    CHANGENR LIKE CDHDR-CHANGENR,
    UDATE LIKE CDHDR-UDATE,
    UTIME LIKE CDHDR-UTIME,
    USERNAME LIKE CDHDR-USERNAME,
    CHNGIND LIKE CDSHW-CHNGIND,
    FTEXT LIKE CDSHW-FTEXT,
    OUTLEN LIKE CDSHW-OUTLEN,
    F_OLD LIKE CDSHW-F_OLD,
    F_NEW LIKE CDSHW-F_NEW,
    END OF ITAB.
    DATA: OLD_OBJECTID LIKE CDHDR-OBJECTID.
    FIELD-SYMBOLS: <F_OLD>, <F_NEW>.
    SELECT * FROM EKKO WHERE EBELN IN XEBELN AND
    LIFNR IN XLIFNR.
    CLEAR CDHDR.
    CLEAR CDPOS.
    CDHDR-OBJECTCLAS = 'EINKBELEG'.
    CDHDR-OBJECTID = EKKO-EBELN.
    PERFORM GETCHGDOCS.
    ENDSELECT.
    IF SUDATE = 'X'.
    SORT ITAB BY UDATE EKKEY-EBELN CHANGENR EKKEY-EBELP
    EKKEY-ETENR.
    ELSEIF SNAME = 'X'.
    SORT ITAB BY USERNAME EKKEY-EBELN CHANGENR EKKEY-EBELP
    EKKEY-ETENR.
    ELSE.
    SORT ITAB BY EKKEY-EBELN CHANGENR EKKEY-EBELP EKKEY-ETENR.
    ENDIF.
    LOOP AT ITAB.
    CLEAR: INDTEXT, EKKEY.
    CASE ITAB-CHNGIND.
    WHEN 'U'.
    INDTEXT(50) = ITAB-FTEXT.
    INDTEXT+51 = TEXT-020.
    CONDENSE INDTEXT.
    WHEN 'D'.
    INDTEXT = TEXT-021.
    WHEN 'E'.
    INDTEXT(5) = ITAB-FTEXT.
    INDTEXT+51 = TEXT-021.
    CONDENSE INDTEXT.
    WHEN 'I'.
    INDTEXT = TEXT-022.
    ENDCASE.
    RESERVE 4 LINES.
    IF WCHANGENR NE ITAB-CHANGENR.
    WCHANGENR = ITAB-CHANGENR.
    EKKEY = ITAB-EKKEY.
    WRITE:/ ITAB-UDATE UNDER 'Change Date',
    ITAB-UTIME UNDER 'Time',
    ITAB-USERNAME UNDER 'User Name',
    ITAB-EKKEY-EBELN UNDER 'PO No',
    ITAB-EKKEY-EBELP UNDER 'Item',
    ITAB-EKKEY-ETENR UNDER 'Sch No',
    INDTEXT UNDER 'Changes'.
    ELSEIF ITAB-EKKEY NE EKKEY.
    WRITE:/ ITAB-EKKEY-EBELP UNDER 'Item',
    ITAB-EKKEY-ETENR UNDER 'Sch No',
    INDTEXT UNDER 'Changes'.
    ENDIF.
    CASE ITAB-CHNGIND.
    WHEN 'U'.
    ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
    ASSIGN ITAB-F_NEW(ITAB-OUTLEN) TO <F_NEW>.
    WRITE: / TEXT-023 UNDER 'Changes',
    <F_OLD>.
    WRITE: / TEXT-024 UNDER 'Changes',
    <F_NEW>.
    WHEN 'E'.
    ASSIGN ITAB-F_OLD(ITAB-OUTLEN) TO <F_OLD>.
    WRITE: TEXT-023 UNDER 'Changes',
    <F_OLD>.
    ENDCASE.
    SKIP.
    ENDLOOP.
    TOP-OF-PAGE.
    WRITE:/ SY-DATUM,SY-UZEIT,
    50 'P U R C H A S E O R D E R H I S T O R Y',
    120 'Page', SY-PAGNO.
    WRITE: / SY-REPID,
    60 'Purchase Orders Changes'.
    SKIP.
    ULINE.
    IF SUDATE = 'X'.
    WRITE:/001 'Change Date',
    014 'Time',
    024 'User Name',
    038 'PO No',
    050 'Item',
    057 'Sch No',
    065 'Changes'.
    ELSEIF SOBID = 'X'.
    WRITE:/001 'PO No',
    013 'Item',
    020 'Sch No',
    028 'Change Date',
    041 'Time',
    051 'User Name',
    065 'Changes'.
    ELSE.
    WRITE:/001 'User Name',
    015 'Change Date',
    028 'Time',
    038 'PO No',
    050 'Item',
    057 'Sch No',
    065 'Changes'.
    ENDIF.
    ULINE.
    FORM GETCHGDOCS.
    CALL FUNCTION 'CHANGEDOCUMENT_READ_HEADERS'
    EXPORTING
    DATE_OF_CHANGE = CDHDR-UDATE
    OBJECTCLASS = CDHDR-OBJECTCLAS
    OBJECTID = CDHDR-OBJECTID
    TIME_OF_CHANGE = CDHDR-UTIME
    USERNAME = CDHDR-USERNAME
    TABLES
    I_CDHDR = ICDHDR
    EXCEPTIONS
    NO_POSITION_FOUND = 1
    OTHERS = 2.
    CHECK SY-SUBRC EQ 0.
    DELETE ICDHDR WHERE CHANGE_IND EQ 'I'.
    CHECK NOT ICDHDR[] IS INITIAL.
    LOOP AT ICDHDR.
    CHECK ICDHDR-UDATE IN XUDATE.
    CHECK ICDHDR-USERNAME IN XNAME.
    CALL FUNCTION 'CHANGEDOCUMENT_READ_POSITIONS'
    EXPORTING CHANGENUMBER = ICDHDR-CHANGENR
    IMPORTING HEADER = CDHDR
    TABLES EDITPOS = ICDSHW
    EXCEPTIONS NO_POSITION_FOUND = 1
    OTHERS = 2.
    CHECK SY-SUBRC EQ 0.
    LOOP AT ICDSHW.
    CHECK ICDSHW-TEXT_CASE EQ SPACE.
    MOVE-CORRESPONDING ICDSHW TO ITAB.
    MOVE-CORRESPONDING ICDHDR TO ITAB.
    MOVE ICDSHW-TABKEY+3 TO ITAB-EKKEY.
    APPEND ITAB.
    ENDLOOP.
    ENDLOOP.
    ENDFORM.
    END OF PROGRAM
    Regards,
    Satish

  • Changing a Message type on Purchase Order

    Hi guys,
    How can I change a standard message type on Purchase Order ?
    For example :
    On Purchase Order, when a insert a new Contract item number, occurs the Error message below :
    'Contract vendor 610065 differs from vendor 610195'
    But, I neet to change this message type from 'Error' to 'Warning' in some cases.
    How can I do this, please ? I'm learning OO now and I have some difficulty yet..
    tks
    Flavio

    I found a Method  'PROCESS_ITEM' in a Badi 'ME_PROCESS_PO_CUST' that the piece of code bellow.  I tried to insert the code :
    message e047(06) with '12345'.
    but... the message 47 didn't change, and this message only was added to messages.
      define mmpur_message.
        gl_tabix = sy-tabix.
        gl_subrc = sy-subrc.
        message id &2 type &1 number &3 with &4 &5 &6 &7 into gl_dummy.
        call method cl_message_mm=>create
          exporting
            im_msgid = &2
            im_msgty = &1
            im_msgno = &3
            im_msgv1 = sy-msgv1
            im_msgv2 = sy-msgv2
            im_msgv3 = sy-msgv3
            im_msgv4 = sy-msgv4
          exceptions
            failure  = 01
            dialog   = 02.
        if sy-subrc = 1 or sy-subrc = 2.
          message id sy-msgid type sy-msgty number sy-msgno
                  with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        endif.
        sy-subrc = gl_subrc.
        sy-tabix = gl_tabix.
      end-of-definition.

  • Reg.Output type for purchase order

    Dear Sir
    I followed your steps but not come to "List of allowed output"
    when I select the message for Purchase order(ME21N). There are listing NEU,SPO,MAHN  and AUFB.
    I just copy the NEU and all,I did not change anything.
    Maintain Output of Purchase Order
    1. Condition Table
    SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
    Select:
    Purchasing Doc. Type,
    Purch. Organization,
    Vendor
    2. Access Sequences
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
    3. Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
    Ex:
    EF---> TES
    Select “TES” and double click on “Mail title and texts” and go to
    EN- New Purchase Order Print Out,
    Select “TES” again and double click on “Processing routines,
    Select “TES” again and double click on “Partner Roles
    4. Message Determination Schemas
    4.1. Message Determination Schemas
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
    4.2. Assign Schema to Purchase Order
    SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
    5. Partner Roles per Message Type
    SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
    6. Condition Record
    Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
    Now you create PO(ME21N) and save it. Go to ME22N and print the PO by giving output type TES.
    Please help me sir
    Rajj

    Hi
    Go to NACE
    Select application as EF Purchase Order
    Define TES as out put type there
    Vishal...

  • Several purchase requsitions from one sales order

    Hi,
    I am using item category TAB to create a purchase requsition from a sales order, this works fine.
    What I really want to do is to create one purchase requsition for each condition type of a special kind from the TAB position in the sales order.
    Another possibility is to create several purchase orders from one purchase requsition, split on the earlier mentioned condition types. In any case, the end result should be several POs from one SO, split on condition types.
    Can this be done in config or do you have a suitable user-exit for me?
    Thanks in advance!
    Best Regards
    Viktor

    HI,
    The Cost Center Determination settings is in OVF3, the standard works only at the header level though, so it would not work if cost center is needed on the line item.
    For this case I suggest to try from CO view:
    A material is linked to a profit center. From this profit center you can determine a cost center using txn OKB9
    In combination with the material's account assignment field and account determination customizing, an alternate revenue account can be determined for this material. ("Normal" revenue accounts are to be used in combination with CO-PA).
    If this account is a cost element with category type "1" you need the entries in OKB9.
    Hope this help!
    Regards!

  • Line item in purchase requsition

    Dear Sir ,
    Presently i am working in 4.7 environment  , in purchase requsition screen no. of line item is upto 10 , My client want 100 line item to be punched in one PR , whether this is possible or not , please specify that how can it be done .
    thanks & regards
    shailendra

    Hi
    Just enter the first ten items and then press enter u ll get another ten new lines. this ll happen everytime u press enter after entering data in the last line. i do not know what is the limit. but 100 records can be done. u will not need any settings for this. it just straight forward
    cheers
    maniraj

  • Disable info record by type of purchase order

    Dear All,
    Can I disable the field "InfoUpdate" in the purchase order by type of purchase order?
    We need, when we create a new purchase order we don´t want to bring SAP info record information by type of purchase order.
    Regards,

    Hi Josiane,
    Do you want the field not to be checked by default? This can be done by means of "default values for buyers", trs OMFI. Select a code that you normally use (or create a new one) and on the first tab you have "Info record update - Purchase order". Make this field be empty. Then assign the "default values" code to each user by means of the user parameter EVO.
    If you need different defaults by PO types rather than by the user, this will be BAdI ME_PROCESS_PO_CUST, method PROCESS_ITEM. Here you can check which document type was assigned to the PO by calling IM_ITEM->GET_HEADER.
    BR
    Raf

Maybe you are looking for

  • My computer doesn't recognize my ipod nano 2nd gen

    My computer running Windows 7 doesn't recognize my ipod nano 2nd gen.  Also my ipod not seen in my itunes.  I did all the reset stuff and nothing works.  Do you think it is just shot???

  • Excel 2010 Status Bar Sum

    I recently switched from Excel 2007 to 2010. In 2007 when I highlighted a range of cells that included hidden cells, the SUM in the status bar only displayed the sum of the visible cells - which was very helpful in determining a) whether the range co

  • Resource Management

    Dear all I need to implement Resource Management KIndly share the documentation .... CHeers

  • Games into ipod trouble

    hello, i have a 5th gen ipod video, and i have games ready to be put into my ipod. when i plug it in and try to sync it, i get this error, "some of the games...blah blah blah... because you are not authorized for them on this computer. so i try to go

  • The Strange Case of the Missing Network Icon

    Can anyone help my buddy Tom - who is running a G4 iBook with OS X Panther? He is unable to get onto his wireless network and here is the problem in his own words: "Had a moment to muck about in the iBook drive, following data crumbs from the all-per