Budget compromise by date delivery purchase order (ME21N)

Hello Experts, please a consultant
It is possible configure in FM or MM for the The budget may be committed by the delivery date of the purchase order and not the date of the document?
Greetings and thanks for the suggestions
Hello experts.

Hi,
Why not? You can have these settings in OF39. Just be aware, that you cannot use PBET profile if you want to set FM data on the basis of delivery date.
Regards,
Eli

Similar Messages

  • Budget compromise by releasing requisition purchase order (ME54N)

    hello Experts, please a consultant
    It is possible to configure in FM for the budget compromise at the time of the release of the requisition (ME54N) and not when creating the purchase requisition (ME51N)?
    greetings and thanks for the suggestions
    Augusto

    Hi,
    Do you mean consume the budget at the time of release and not on the creation? It won't be possible, due to prudence policy in PSM-FM. Imagine, creating a lot of PRs, which won't have effect at the budget and the lack or resources will be discovered only at their release.
    Of course, by modifying standard code, in theory, you can force this kind of logic, but I won't recommend it both from technical and functional reasons.
    Regards,
    Eli

  • How to execute availability check against delivery date in purchase order

    Hi all
    In MD04, I know that "available date = delivery date in purchase order + GR processing time" & "GR date = delivery date in purchase order". When I execute availability check in production order, I will get material's committed date = available date. But I hope to get material's committed date = GR date in purchase order.
    For example. delivery date in purchase order is 2012/02/06 and GR processing time is 2 days. After ATP in production order, I will get committed date 2012/02/08. But I hope it show 2012/02/06. How to customize it.
    (The GR processing time must be set 2 days for MRP calculation. it can be changed to 0.) Thanks!!

    Hi Rita,
    One Doubt, If you say that material commited has to be the GR date and you do not wish to wait for GR processing time, then why do you have the GR processing time in first place.
    For ex. My client, we get the stock as per GR in Quality inspection and so we have GR processing time considered for available time in MD04. But since the business considers the Inspection stock as avialble, The stock gets reflected in avialibility check the moment GR is done.
    So please explain your requirement in detail. There could some way to do so. If not the raise an issue with SAP.

  • Delivery date in Purchase Order Header

    Hi all,
    In which table is Delivery date in Purchase Order Header stored.
    the screen field name is eeind.
    Thanks

    Table EKET, Field EINDT or LPEIN try to look from se11 or se16n
    reward point if correct

  • Delivery date in Purchase Order in the item overview

    Hi all,
    In which table is Delivery date in Purchase Order in the item overview stored.
    the screen field name is eeind.
    Thanks

    In table EKET in field EINDT the delivery date is stored, based on the Schedule lines in the PO Item

  • Source inspection before 365 days of delivery date of purchase order

    Hi Experts,
    Business wants to create source inspection lot well in advance before 365 days of delivery date of purchase order. this lot is required to record results.
    In SAP, transaction code QA51 allows only two digit characters for 'number of days for opening period' so system is not creating inspection lot for more than 99 days delivery date from current date.
    Please advise.

    Hi Patel, I really got interested on this particular issue because we have been using source inspection in our company for a while. After some investigation on ABAP code of report I will share with you my fact findings:
    1) System calculates the start date of source inspection (delivery date from PO - Leadtime from q-info record). For example, in my test case it was 14.08.2015 - 0 days. So field g_datum below will be 14.08.2015:
    2) System then checks if you are running the report in background (highlighted in yellow above). If so then it will check if the start date of inspection (g_datum) falls on opening horizon (g_datum_eroff). The opening horizon is calculated as per formula below (system login date + opening period). As an example: 14.08.2014 + 30 days = 13.09.2014.
    Default opening period (p_eroff) is 30 days:
    3) So all-in-all, when you are running QI07 online you´ll get a yellow traffic light on the long leadtime PO but you will be able to process it (on-line). However if you run the report in background (job scheduling) system will only create inspection lot to the relevant POs if the PO's delivery date falls on the 30 days window based upon the current date.

  • Fixed Day in a week as Delivery date in Purchase Order.

    Dear All
    I have the below requirement
    For a material/ vendor combination users would like see  always a fixed day as delivery date in Purchase Order.
    For  example for a Material X and Vendor Y always Wednesday of the week should be delivery date.
    Whether this can be achieved ?
    Can you please let me know your thoughts on this
    Regards
    Shyam

    Dear Jurgen
    Thanks for referring to the post.
    But actually my requirement is bit more specific. For material-vendor combination the deleivery date should be a particular day in a week
    Ex : Material X and Vendor X1 = Monday
    Material Y and Vendor Y1=Tuesday
    This requirement I believe is quite difficult in achieving  for a PR from MRP. That's why I put the question as whether we can achieve this when we convert the MPR PRs to PO s ?
    Please let me know your thoughts on this
    Regards
    Shyam

  • Selection of a price list based on the delivery date of purchase orders

    Description of requirement:
    One of our customers would like to have the price list selected on the basis of the delivery date of purchase orders rather than on the posting date.
    The customer wants to have this feature available by the date scheduled for their go-live, that is January 2nd 2008.
    Best regards,
    Emmanuel Ruellan

    Dear development team,
    Is it possible to have the above functionality in a future version?
    Best regards,
    Emmanuel Ruellan

  • How to update need by date in Purchase order using an API?

    Hi All,
    Is there any API available in 11i which can be used to update the need by date in purchase order?
    There is a API PO_CHANGE_API1_S.UPDATE_PO, but it updates only the promise date and not the need by date.
    Please help !!
    Thanks & Regards
    Anuj

    Your error comes from Sybase, so I suggest you post your question to a Sybase forum.  And be aware that Sybase does not use the same tsql dialect as sql server, so you must use their dialect (if, indeed, there is any difference in this particular situation). 
    One note - there should be no space between "N" and the Unicode string literal to which it applies in tsql.  E.g.,
    = N'Executive Chair эюя'
    not
    = N 'Executive Chair эюя'

  • Calculate due on date in incoming invoice based on p.date of purchase order

    We would like to calculate due on date in incoming invoice based on posting date of purchase order position. We want to be able to see the posting date of the purchase order lines from miro transaccion. Then we would add 85 days to calculate the due on date. I have tried to create an "item list variant" from OLMRLIST transaccion (Customizing - Logistics invoice verification) and add the posting date but it is not possible to access this value.
    Thanks in advance.

    Hi,
    have a look at badi MRM_PAYMENT_TERMS.
    Check as well OSS Note 1156325 - BAdIs in the Logistics Invoice Verification environment
    Best regards.

  • Message alert when Invoice date preceds Purchase order date

    Hi all,
    I want to define message alert, when Invoice date precedes Purchase order date. Is there any standard message type is there, If yes please let me know. Otherwise how can i define this, please.
    Thanks
    CS..

    Hi,
    You can take help of your abbaper and enter the validation in the user exit of MIRO thru which Invoices are booked.
    Hope this helps, if yes, please assign points.
    Regards,
    Harish

  • User exit to change item level data in purchase order

    Hi,
    Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirment is
    For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked).   now i cant use ME_PROCESS_PO_CUST  because process_item wont get triggered if there is no change in itemlevel data.
    Regards,
    Rahul

    Hi Rahul,
    Probably EXIT_SAPLMEKO_002.
    hope it helps,
    Edgar

  • Help - User exit to change item level data in Purchase Order

    Hi,
    Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirement is For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked).   now i cant use ME_PROCESS_PO_CUST  because process_item wont get triggered if there is no change in item level data.
    Thanks,
    Rahul

    Hi Rahul,
    Probably EXIT_SAPLMEKO_002.
    hope it helps,
    Edgar

  • INFO UPDATE in the purchase order ( ME21N)

    Why the field INFO UPDATE in the purchase order ( ME21N) is not flaged when I create a purchase order?
    I create a PO, and I flag it in ME21N, but it cancel it? WHY
    I have already tried it in spro Default values for purchasing, and all seem good!!
    Anybody could tell how can I tick this field?
    Thanks a lot
    Kari

    Hi
    Info update indictor can be set by defualt if you maintain the same in the Purchase inforecord,
    If no inforecord exists then this would not be flagged and if you flag it then the Purchase inforecord gets created with the update of with or wothout plant based on the default value assigned to the buyers.
    Thanks & Regards
    Kishore

  • Updating Scheduling data for Purchase Order

    Hi,
    I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
    Thanks
    Somnath paul

    try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes  are there  leave it with space )...
    this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
    Example of population of BAPI interface in the Function
    Parameter: POHEADER
    COMP_CODE            =                    1000
    DOC_TYPE             =                    NB
    ITEM_INTVL           =                    00001
    VENDOR               =                    0000001000
    PMNTTRMS             =                     0001
    PURCH_ORG            =                     1000
    PUR_GROUP            =                     001
    CURRENCY             =                     EUR
    Parameter: POHEADERX
    COMP_CODE            =                     X
    DOC_TYPE             =                     X
    ITEM_INTVL           =                     X
    VENDOR               =                     X
    PMNTTRMS             =                     X
    PURCH_ORG            =                     X
    PUR_GROUP            =                     X
    Parameter: POITEM
    PO_ITEM              =                     00001
    MATERIAL             =                    100-100
    PLANT                =                    1000
    STGE_LOC             =                    0001
    QUANTITY             =                    15.000
    TAX_CODE             =                    V0
    ITEM_CAT             =                     0
    ACCTASSCAT           =                    K
      Parameter: POITEMX
      PO_ITEM              =                    00001
      MATERIAL             =                    X
      PLANT                =                    X
      STGE_LOC             =                    X
      QUANTITY             =                    X
      TAX_CODE             =                    X
      ITEM_CAT             =                    X
      ACCTASSCAT           =                    X
      Parameter: POSCHEDULE
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      DELIVERY_DATE        =                    02.12.2002
      QUANTITY             =                    6.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
      DELIVERY_DATE        =                    03.12.2002
      QUANTITY             =                    5.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0003
      DELIVERY_DATE        =                    04.12.2002
      QUANTITY             =                    4.000
      Parameter: POSCHEDULEX
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      PO_ITEMX             =                    X
      SCHED_LINEX          =                    X
      DELIVERY_DATE        =                    X
      QUANTITY             =                    X
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
    Parameter: POACCOUNT
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    15.000
    GL_ACCOUNT           =                    0000400000
    COSTCENTER           =                    0000001000
    CO_AREA              =                    1000
    Parameter: POACCOUNTX
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    X
    GL_ACCOUNT           =                    X
    COSTCENTER           =                    X
    CO_AREA              =                    X
    Parameter: POCOND
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    001
    COND_TYPE            =                    PB00
    COND_VALUE           =                    79.900000000
    CURRENCY             =                    EUR
    CURRENCY_ISO         =                    EUR
    COND_UNIT            =                    KG
    COND_P_UNT           =                    1
    CHANGE_ID            =                    U
    Parameter: POCONDX
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    000
    ITM_NUMBERX          =                    X
    COND_TYPE            =                    X
    COND_VALUE           =                    X
    CURRENCY             =                    X
    CHANGE_ID            =                    X
    Parameter: POPARTNER
    PARTNERDESC          =                    OA
    LANGU                =                    EN
    BUSPARTNO            =                    0000001100
    PARTNERDESC          =                    GS
    LANGU                =                    EN
    BUSPARTNO            =                    0000001200
    PARTNERDESC          =                    PI
    LANGU                =                    EN
    BUSPARTNO            =                    0000001000
    reward points if helpful....

Maybe you are looking for