Need to reopen PO to change posting date (for jobs ?)

bob_upbob_up Member Posts: 155
Our client is using jobs and has document approval. When they come to invoice a PO they need to enter the actual posting/tax point date. When they do so, the validation on the PO forces them to reopen the order ... but only where there are job lines. This mean they then have to release the order again with the subsequent chain of approvals. This is a major aggrevation.

We are being asked to remove the check so that they can change the date without re-opening the order. Can anyone explain why this control might be there ?

This client does not use warehousing or manufacturing.

Comments

  • David_SingletonDavid_Singleton Member Posts: 5,479
    Definitely do not by pass the checking, that is a disaster waiting to happen. Instead put a wrapper around the release so that the order will be re-opened, date changed and then re-released in the transaction.

    This will probably interfere with your approvals system, so its probably not the quick fix you were hoping for.
    David Singleton
  • David_CoxDavid_Cox Member Posts: 509
    1. Train the user where they need to change the posting date, to use the Post Batch option and set a filter for the Single Order, on the options tab they can choose to set and replace the Posting Date.

    2. The tax point date on the Purchase Invoice is set by the Vendor, you could allow the date to be changed within a codeunit, look at the codeunits that allow specific fields only like the Shipment Tracking No. to be changed on the posted Shipment documents, create a function on the Order menu to change just the posting date based on one of these codeunits, add your date checking code in the codeunit.

    David
    Analyst Developer with over 17 years Navision, Contract Status - Busy
    Mobile: +44(0)7854 842801
    Email: david.cox@adeptris.com
    Twitter: https://twitter.com/Adeptris
    Website: http://www.adeptris.com
  • bob_upbob_up Member Posts: 155
    Thank you David and David for your really helpful suggestions.

    Mr. Cox, your 1st suggestion looks like it may fit the bill :-)
  • David_CoxDavid_Cox Member Posts: 509
    Hi Bob,
    If you are going to use option 1 then add this little code to the Post Batch Reports, to stop the user posting the wrong documents and creating more work.

    All it needs is if the user does not enter a document number filter then error.

    In the Post Batch Reports,
    Create a C/AL Global: 'Text Constant', Text5000 - Please enter a Document No. Filter.

    Then in the report add a little code:
    Purchase Header - OnPreDataItem()
    IF GETFILTER("No.")= '' THEN
       ERROR(Text5000);
    

    David
    Analyst Developer with over 17 years Navision, Contract Status - Busy
    Mobile: +44(0)7854 842801
    Email: david.cox@adeptris.com
    Twitter: https://twitter.com/Adeptris
    Website: http://www.adeptris.com
  • bob_upbob_up Member Posts: 155
    Yes, I will add that check immediately.

    Thanks again

    Bob
Sign In or Register to comment.