MIGO should not create after PO Delivery Date

Hi,
We have a PO with multiple line items and diff. Delivery Dates...
We want that during MIGO Process, Posting Date should not exceed to PO Delivery Date.
Means, if PO Delivery Date is 05.07.2014, then MIGO should not created after this date...
Please suggest.

If you want to achieve the scenario with standard settings, then you can use the field "Latest GR date".
Just put the same date as delivery date in this field. Then  system will not allow to do GR if the Posting date is exceed with compare this date in MIGO.
You can find the latest GR date in Delivery tab in PO. Also you can maintain the field as mandatory in PO to avoid the field value blank as per your requirement.
Also if you want to change Latest GR date along with delivery date, just take the steps which is explained in this document Mass changes from one field to another field.
**Edited by: Dëv Päträ

Similar Messages

  • Material availability date can not be after the delivery date

    Dear Experts,
    we are using the following scnario,
    1. Once the user creates the sales order, automatically system creates PO in the background.
    we have created Bapi program for creation of Background PO in SD User Exit.
    The following issue occurs in Prd, DS1, QS1 server, We have done Technical upgradation project, Now when we creates sales order automatically po created with error message of Material availablity date can not be after the delivery date. even sales order no also not updated in the PO.
    QAS server (without technical upgrade) i refered the same input parameter and used the same and create the sales order system generates PO automatically without error message.
    Does any one can through lights on this issue,
    Thanks and Best Regards,
    Muralidharan S

    Hi
    The dates are determined due to shipping and transportation scheduling settings. So check whether the shipping and transportation scheduling is being performed as per the cofiguration settings after Technical upgrade. Since the MAD date should not be after Delivery date but it seems that the dates are not determined properly.
    Also check the Transit  time, Loading time, Pick/Pack time and Lead time are retained as same as before the technical upgrade. Use the QAS server settings to validate the settings in other servers.
    Regards
    Rajkumar K

  • AR Invoice date should not be less than delivery date

    How can i make an alert for user when they will prepare AR Invoice?
    Example:
    If Delivery date is 01-10-2010 and Invoice date should be later or same but not less than delivery date(01-10-2010).
    if Invoice date is less than delivery date then This data should not be added into the database.
    So there is any way to stop this error.
    Thanks
    Mizan

    Dear Bala,
    Here is the SP:
    set ANSI_NULLS ON
    set QUOTED_IDENTIFIER ON
    go
    ALTER proc [dbo].[SBO_SP_PostTransactionNotice]
    @object_type nvarchar(20),                     -- SBO Object Type
    @transaction_type nchar(1),               -- [A]dd, <u>pdate, [D]elete, [C]ancel, C[L]ose
    @num_of_cols_in_key int,
    @list_of_key_cols_tab_del nvarchar(255),
    @list_of_cols_val_tab_del nvarchar(255)
    AS
    begin
    -- Return values
    declare @error  int                    -- Result (0 for no error)
    declare @error_message nvarchar (200)           -- Error string to be displayed
    select @error = 0
    select @error_message = N'Ok'
    --     ADD     YOUR     CODE     HERE
    If @object_type='13' and @transaction_type='A'
    BEGIN
    If Exists (Select distinct 'error' from [dbo].[OINV] T0 Inner Join INV1 T1
    On T0.DocEntry=T1.DocEntry Inner Join DLN1 T2 On T1.BaseEntry=T2.DocEntry
    Where T0.DocDate<T2.DocDate
    And T0.DocEntry = @list_of_cols_val_tab_del)
    BEGIN
    Select @error = -1,
    @error_message = 'DocDate for Invoice Should not be Less than Del. Date. So You can not Add this Doc'
    End
    End
    -- Select the return values
    select  @error,@error_message
    end
    Regards,
    Mizan

  • E-Rec Reference Code in the Publication tab should not appear after enddate

    hi,
    There is a requirement from the client after the end date of the publication ,the reference code should not be displayed to the candidate in the Candidate page ,presently the same is manually done in the system by changing the status to withdrawn.
    Is there any way by which we can automate the process by change in customising by which the reference code does not appear after the end date
    Please provide a solution if something can be done in the standard setting or do we require any Zworkflow to be developed for the same.
    Regards
    RK

    Hi RK,
    this is nothing the standard supports.
    But I would not use a workflow here. As this is a mass handling workflow is no good idea. This is a task for a customer periodical service. Just build a class implementing the periodical service interface which gets all released publications which have a publication end in the past and status released and change their status using the cl_hrrcf_posting_inst_bl. This should be done in a couple of hours. Add the customizing and the issue is solved.
    A requirement in this context where a customer workflow is quite handy in my opinion is a customer workflow which closes all postings and withdraws released publications when you close the requisition. This reduces the steps a recruiter has to do and ensures that no candidate applies although you are already done with the requisition.
    Kind Regards
    Roman

  • Sales order cannot be created  for the delivery date before 20.10.2008

    when i create a sales order today (18102008) sales order cannot be created  for the delivery date before 20.10.2008
    how the system is checking the 2 days duration for delivery date - which table is having this duration days.
    is it dependent on sales order type.....
    actually i checkeup in V0V8 - even then i couldn't  solve this error when i am creating the sales order.
    Pls suggest

    Dear Selvamuthu
    In normal circumstances, you can create as many as sale orders as you can irrespective of delivery date, and system will not  prevent to create unless you apply some user exit for some reason.
    Check any user exit is applied for that sale document type where some logic would have been written in such a way that if stock is available, sale order can be created.
    thanks
    G. Lakshmipathi

  • PO Qty should not Amended after GR

    Hi friends
    i have to do PO Qty should not Amended after GR finished . IS there any BADI Enhancements points please let me know i guess
    this is BADI ME_PO_PRICING_CUST  i have tried it but it is not working for me or i missing some thing .please give suggestions what i need to do .And  the same time  there is also  required for particular user it should be allow to change
    REgards
    Rk

    Hi when GR is done and it is allowing to change it comes under PO amendment
    ask functional if amendment can be stopped
    regards
    m.a

  • Could not create a valid GL date rejection for PA transactions to GL

    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    Praveen

    Praveen Bharadwaj wrote:
    Hi All,
    PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
    I have verified all Periods are Opened. Still there is a a rejection.
    Thanks,
    PraveenPlease see these docs.
    PAGGLT, PASGLT gives 'Could Not Create A Valid GLDate', even when GL data is re-open. [ID 330874.1]
    PRC: Interface Labor Costs to GL (PALDLC) Will Not Interface, CDL.Batch_Name Is Null [ID 437301.1]
    PALDLC and PASDUC Error - Could Not Create A Valid GL Date For Provider [ID 338330.1]
    Distribute Labor Cost Exception-Could Not Create A Valid GL Date [ID 418675.1]
    PAXACCPB - PRC: Create Accounting Gets Error 95325 Gl Date Not An Open Or Future Enterable Period [ID 951452.1]
    Thanks,
    Hussein

  • Po should not editable after grn

    Dear All
    My clint wants po should not editable after grn.
    pls help

    Hi,
    you can use user exit : EXIT_SAPMM06E_016
    Following Logic can be use:
    1. Validate the company code (BUKRS ) & Purchasing document type (BSART = F) from EKKO table for the Purchase order number (EBELN).
    2. Check the entries for the Purchase order and the item number in the Purchase order history table ( EKBE) and also Validate if there is no reversal document for goods receipt ..
    3. If we find GR doc in EKBE table with out reversal documents then display the warning or error message as POP - UP by using functional module POPUP_TO_CONFIRM.
    Step 1: Validate Company code and Purchasing Document type from EKKO table
    Step 2: Check the Purchasing document history from EKBE table
    Step 3: Check whether any reversal made for goods receipt.
    Step 4: Display popup message to user:
    Use the function module u201CPOPUP_TO_CONFIRMu201D to display the below message u201CThe PO has been already Receipted. Before changing PO please take care about GR document reversalu201D.
    Regards,
    Vikas

  • System should not creates new version when value of PO increased..

    Hi Experts,
    Need your help to solve this problem. When i increase value of PO it should retrigger Release strategy but it creates version first, then i have to tick completion indicator and check then only release strategy retriggers..
    It should not create new version when change po
    Please check below screenshot
    Please help

    Hi
    Please reveiw the following points in note
       - 493900 FAQ: Release Strategy
          4.  Why is the release strategy not determined?
         "If you use version management, the determination of the release
          strategy starts when the version is completed.
          You complete a version by setting the "version completed"
          indicator in the version tab."
       - 662993 Resetting an already occurred release
         You edit a purchasing document with release strategy.
         You change the quantity or the price. In spite of that, the
         already set release is not reset.
    The release strategy works the same with or without version management
    active - the only difference in case - version management is active -
    is that if release is to be reset, it will be reset only on version
    I hope this helsp to clarify this issue
    Kind regards,
    Lorraine

  • My i phone is not activating after i up date my i phone 3gs can you help me

    my i phone is not activating after i up date my i phone 3gs can you help me

    See your Other post on this Topic...
    https://discussions.apple.com/message/23620536#23620536

  • Delivery should not create with out company code data

    Hi all,
              We have created a customer master without company code data with T code VD01 and subsequently created sales order and delivery with PGI and invoice also saved but no accounting document is getting generated. But we want to stop at delivery only; system should not allow creating delivery. Please do the needful
    Thanks in advance
    Regards,
    Nagesh

    hi nagesh,.
    from standard SAP it might not be possible.
    but check this work around:
    after creating the COMPANY CODE DATA by the marketing people only you please go ahead and create a delivery till that time the sales order will be in open status.
    if you want to stop it through the SAP system:
    then you need to contact TECHNICAL PERSON on the same:
    MV45AFZZ : USEREXIT_SAVE_DOCUMENT_PREPARE for checking while creating a delivery if not created then to throw an ERROR message - this is the only probability to check
    but he may not be having solution for your query.
    except the work around.
    please check and confirm
    balajia

  • TR was not created after MIGO

    Hi, experts
    Sometimes after I did goods receipt with MIGO for purchsing order, the TR was not created by system. Normally after MIGO system create material document and TR at same time, then I use LT06 with reference the document no. place it to the storage bin.
    But for this case, no TR generaged. I can only use LT10 /mvt999 to move them to the storage bin.
    Can you please tell me the possible reason for this problem( TR not created)?

    Can you please check what is the movement type being used ? If you were able to use LT06 in some cases means that most probably 101 is correctly defined in LE--> Interfaces --> Movement types to trigger the TR's.
    1) however, if you are using / different movement type is being triggered and is not set up to create the TR.
    2) If you see that the movement type is still 101, you could still be creating the TR's in the background, however, if you have a background job or some other transaction that is confirming the open TR's , this could be one of the reasons why you are not able to use LT06.
    For this you can go to MIGO ( go to display tab for material document) , go to WM tab and find out the TR # there.
    You can then go to LB03 and if you scroll to the right , you will find the TO # created.
    Please go to LT21 and check who and how the TO is being created / confirmed, if thats something out of the process for you.
    Thanks

  • Plannned Delivery time not considered while calculating delivery date

    Hi PP Gurus,
    We have a situation is that after MRP run system is not taking into account planned delivery time while calculating delivery dates in schedule lines
    It is taking into account GR processing time.We have GR processing time of 3 days.requirment date is 13.10.2011 & delivery date created by the system is 10.10.2011.
    We have maintained correct master data i.e.Materail Master , Info record & Scheduling agreement.
    Please advice why it is happening & what is the significance of planned delivery time in externaly procured materail with scheduling agrement schedule lines?
    Thanks & Regards,
    Sandesh

    Hi Sandesh,
    Is this happening for particular materials or for all materials
    Couple of checks -
    1) Check with material master changes, might be after MRP run PDT is updated in material master etc ..
    2) Check in OPPQ, for option external procurement , whether scheduling info records/agree is marked or not
    Best Regards
    K.Madhu Kumar

  • Purchase Requisition Date is not updated with Scheduleline Delivery Date

    Hi,
      This is a third part Sales Scenario. The Delivery date on the schedule line is passed on to purchase requisition as the delivery date of that item. Due to some business requirement, the delivery date of the schedule line is changed just before saving the sales order in the BADI called through the userexit userexit_save_document_prepare. Now on saving the sales order, the purchase requsition is also created.The delivery date of the schedule line is changed but has not reflected on the Purchase Requision.
    If the Sales Order is opened in VA02 and the schedule line delivery date is modified, the Purchase Requisition delivery date is also getting modified.
    Why did it not happen at the time of saving the Sales Order.
    What is the structure into which the purchase requsition information is stored, so that on processing the sales order, this information is utilized to create the purchase requsition.
    Please help.

    Hi,
    Check the following table for the mentioned fields EBAN-BADAT and EBAT-FRGDT
    Thanksk and Regards,
    Hari Challa.

  • Billing date in sales order should not be modifiable to backwards dates

    hi gurus
    I have a requirement where in few users while creating a sales order , they should not be able to modify the billing dates to previous dates . So that particular field shd not be modifiable . Could use some help here .
    Regards
    JNM

    Dear JaganNM,
    While creating the billing document in VF01 the billing date will be changed manually by the user.
    This change will not applicable in sales order.
    Once you save the billing document you can't change the billing date in sales order ,it will be graded out.
    Before saving the billing document only the date can be changed in sales order.
    Let me know if you have any further clarifications.
    Thnaks&Regards
    Raghu.K

Maybe you are looking for