Payables & Cash Management

Get Involved. Join the Conversation.

Topic

    Maullin Shah
    AP Invoice Header >> Identifying PO field related -...
    Topic posted May 19, 2018 by Maullin ShahBlue Ribbon: 750+ Points, last edited January 30, 2019, tagged Financials, Payables 
    628 Views, 4 Comments
    Title:
    AP Invoice Header >> Identifying PO field related - backend update
    Summary:
    AP Invoice Header >> Identifying PO field related - backend update
    Content:

    Hello All,

    We are on R13 (Update 18A).

    One of our business process, requires PO # to be updated on AP invoice header >> Identifying PO.  This PO # is just a place holder and we will NOT do PO matching at line level.  In nutshell, PO# on header only not at line level.  Believe me, this is requirement :).

    Challenges --> 1.) During conversion process, we are not able to find "Identifying PO" in FDBI template for AP invoice header.  We are also not able to find "Identifying PO", in ADF-DI template as well (webadi).

    2.) Once AP invoice is converted, Identifying PO field is grayed out.  So, user cannot even update from front end.

    Help --> Once conversion is done as manual AP invoice, is there a way to updated "Identifying PO" coloumn in AP Invoice headers table from backend?  Does Oracle support can run datafix to update this field?  Or is there any other option to handle it?

    Thanks in advance.

    with regards, Maullin Shah

    Comment

     

    • Becky Alvarez

      Our invoice import performs the match as part of the import process so you have to put the PO number in at the line level in order to bring in the PO number.  I don't know of any way around it and there is no way to fix this after the fact.  We don't provide data fixes for this.  Customer is either matching to the PO or they are not.  If they are then the PO goes in on the line and if they are not then no PO number is entered. 

      Surprisingly the system  will let you validate the Invoice if you manually enter a PO number on the header in the UI and then don't match the lines.  But this is the first I have ever heard of this requirement as it violates the whole purpose of the purchasing system and the checks and balances of validating the invoice against the agreement.  I am not sure how auditors will feel about this not to mention the potential fraud and over payment the customer is opening up.

      I understand your challenges here but out AP system was not setup to easily bypass the procurement system for the reasons I mention above.

       

    • Alexey Shtrakhov

      Hi Maullin,

      Why dont you just open 1 DFF field for this purpose?
      You can then freely update it and also bring it via FBDI template.

      You can also, if needed, allow some persons to update this field and other not.
      Also invoice header level DFF will be available in OTBI.

      Alexey

    • John Gunja

      Hi Maullin,

      What did you end up doing for this requirement ?

      Thanks,

      --John.

      • Maullin Shah

        Hello John,

        We ended up creating DFF on AP invoice header and populated the PO number using FBDI. I know it is clunky, but that's the only workaround available.

         

        with regards, Maullin