Self Service Procurement

Get Involved. Join the Conversation.

Topic

    Ashok
    Project Billing Details on a Requisition Date: Defaulting...
    Topic posted October 26, 2018 by AshokBlack Diamond: 60,000+ Points, tagged How-To, Setup, Tip 
    120 Views, 12 Comments
    Title:
    Project Billing Details on a Requisition Date: Defaulting Logic for Expenditure Item Date
    Summary:
    Project Billing Details: How does the Expenditure Item Date value default on a requisition
    Content:

    A few customers asked about the defaulting logic of the attribute 'Expenditure Item Date' on a requisition. As you know this is one of several Projects Descriptive Flexfields defined for the purposes of project billing and accounting. 

    Concept:

    The Expenditure Item Date uses need by date (requested delivery date), sysdate or blank as default values. Given below are the steps to find this setup and configure it based on your requirement.

    Steps:

    1. Go to FSM task Manage Project Costing Descriptive Flexfields. Perform a blind search.
    2. Find and select Project Costing Details DFF to edit
    3. Change context in Context Sensitive Segments to POR: Requisition
    4. Select EXPENDITURE_ITEM_DATE and edit

    5. From Initial Default region:
    a) Choose default type parameter and default value EIDate - to have need-by date as default "or"
    b) Choose SQL and default value: "select sysdate from dual" - to have sysdate as default
    6. Save and close and deploy the descriptive flexfield.

    Comment

     

    • Ramesh Radhakrishnan

      Thanks for the Note Ashok!!

    • Ramesh Bomma

      Thank you Ashok

    • ASHOK ROUT

      Hi Ashok,

      Can we make the expenditure item date defaulting condition based. We are using the query -select sysdate from dual- to default the expenditure item date to sysdate. But Its defaulting the expenditure item date to sysdate for both and non project requisitions. We want the expenditure item date to default to sysdate for project based requisitions only. For Non project requisitions, this date should be null.

      Regards,

      Ashok Rout

    • Mara Prieto

      Hi Ashok Rout,

      The default of the date happens when you add the item to the cart or when you open the Enter Requisition Line page. With current design we cannot make the date default happen only when the user enters a project.

      But you can still submit the requisition with the default date and without any project details.

      Thanks
      Mara

      • ASHOK ROUT

        Hi Mara,

        We are able to submit the Requisition with this Default Expenditure Item Date populated for  non project based requisition. The challenge is coming when we are trying to generate the ERS invoice for such PO/Receipt lines; the payable invoice import program fails for such lines with a message Insufficient Project Information. The error does not appear if a non project PR/PO line is created with expenditure item date as null. 

        Regards,

        Ashok

    • Mara Prieto

      Hi Ashok Rout

      Could you please clarify what ERS invoice is and where you are generating your payables invoice. We don't hear this issue from other Cloud customers.

      Thanks
      Mara

      • ASHOK ROUT

        Hi Mara,

        ERS invoice refers to the Pay on Receipt functionality available in Procurement. When the Pay on receipt functionality is enabled at the Supplier Site level, upon receipt of the goods/service, the program Send Pay on Receipt will create an invoice for the receipt qty/ amount in Payables.

        Now in our case, the Send Pay on Receipt program is failing for all the receipts for which Pay on Receipt functionality is enabled at the Supplier Site level.The error message is Insufficient Projects information. There is an SR also logged for this issue.

        Upon investigation, we found that, the invoice is not getting created as the expenditure item date is populated for non project based POs. This is happening because we are using the SQL- select sysdate from dual to default the expenditure item date at the Requisition billing details level. This is defaulting the expenditure item date for non project requisitions as well.

        So our requirement is that the expenditure item date should default to the sys date for project based requisitions; for non project requisitions, it should default as NULL.

        Hope the issue is clear now. Please advise on how to handle this.

        Regards,

        Ashok

         

         

    • Mara Prieto

      Hi Ashok Rout,

      I've discussed this with the projects team as well. It is UI default behavior that the Expenditure Item Date is defaulted on all Requisitions, PO's, and Invoices.It should not cause any problems as it should only be evaluated when it's determined that the document/line/distribution is related to a Project. 
      So, the ERS Invoice program should not need this validation as far as I can tell. Could you please log a bug against Oracle Fusion Payables. Please add reference to this customer connect thread so the team can contact our team for any further clarifications.

      Thanks
      Mara

    • Ashok

      Ashok

      Do provide the bug number once logged and mark this post as answered. I suspect other customers may also be interested in the results.

    • ASHOK ROUT

      Hi Mara,

      Please find the bug details:

      SR No: SR 3-20639230093 : [IMPL SR]"Insufficient projects information" error in AP open interface for ERS invoice.

      Bug No: Bug30228385

      It will be great if you can help in quicker resolution to this issue.

      Regards,

      Ashok

    • Mara Prieto

      Thanks Ashok. I added some comments to the bug, and contact details.
      Our support team should be able to keep you posted.

      thanks
      mara