Project Management

Get Involved. Join the Conversation.

Topic

    ARUNKUMAR JAYARAMAN
    UNABLE TO DERIVE THE PROJECT SEGMENT IN COA FOR RECEIVABLE...
    Topic posted November 7, 2017 by ARUNKUMAR JAYARAMAN, tagged Other, Project Management 
    291 Views, 6 Comments
    Title:
    UNABLE TO DERIVE THE PROJECT SEGMENT IN COA FOR RECEIVABLE TRANSACTION JOURNAL BATCH
    Summary:
    We are unable to derive the project segment (3rd segment in COA) for the receivable transaction journal batch.
    Content:

    When we account the Project AR invoice, we are unable to derive the project segment (3rd segment in COA) for the receivable transaction journal batch.

    As of now the accounting entries are showing the Project Segment value as "00000"

    The requirement is that the Project Segment (3rd segment in COA) should display the respective project number.

    For example, for a given project number 12345, a Project Invoice is created & transferred to AR. When we account the AR invoice, the respective GL account code should be as follows.

    108-400792-12345-000000-000-000-000-0000-0000-0000
    108-520000-12345-000000-000-000-000-0000-0000-0000

    But, as of now the 3rd segment is displayed as 00000 as shown below.

    108-400792-00000-000000-000-000-000-0000-0000-0000
    108-520000-00000-000000-000-000-000-0000-0000-0000

    Please let us know how to achieve this.

    Image:

    Comment

     

    • Perry Unrau

      Project number is not an attribute that is currently transferred to Fusion Receivables or made available in the SLA Source views for invoice accounting in Fusion Receivables.  This is because invoice lines can easily contain transactions from multiple projects, depending on the invoice format definition.  One solution used by other Fusion users is to populate either a contract header DFF or a contract line DFF with the project number, should the relationship between contract and project be a simple one, where either a contract or a contract line only has a single project associated.  Contract header and contract line DFFs are available in the SLA Source views for invoice accounting in Fusion Receivables and can be referenced in SLA's setup, like in Account Rules or Journal Entry Rules, to override the initial default accounting derived by Fusion Receivables' AutoAccounting.

      • ARUNKUMAR JAYARAMAN

        Hi Perry,

        Thanks for the update. We have some peculiar cases where a single contract line is associated to multiple projects.

        In this scenario, how to achieve the requirement by populating the Contract line DFF?

        As per our understanding, the contract line DFF can capture only one project number.

        Please help.

        Regards,

        Arun J

    • Perry Unrau

      That is going to be difficult.  The intent for the Receivables accounting entries was to use the contract-related attributes to drive the various segment values, not the project, since invoice lines can span multiple projects, whereas an invoice can only be for a single contract.  In a future release, we are planning to enhance the integration between Project Billing and Receivables to capture project and task on the project contract invoice line and pass them to Receivables, when the invoice format involved groups transactions by project and/or task.

      In the meantime and if the credit entry in Receivables must have the project number segment populated, assuming your invoice formats do group transactions by project and you concatenate the project number into the invoice line description, I am wondering if there would be a way to automate the isolation of the project number in the invoice line description and the copying of that value to an already defined SLA source for Receivables invoices.  A Project Billing user could manually do this in the Edit Invoice UI, by visually identifying the project number in the invoice line description and copying it to an invoice line DFF.  A Receivables user could manually do this when Managing AutoInvoice Lines in Excel.  I am guessing the manual approach would be cost prohibitive to implement.

      Perry

       

      • ARUNKUMAR JAYARAMAN

        Hi Perry,

        Thanks for the update.

        We have created the contract line DFF as per your earlier suggestion by using "Contract Line Descriptive Flexfield Attribute 2"

        We used the above DFF attribute reference in AR Account Rule setup & associated the same to Subledger Journal Entry Rule Sets.

        We were able to populate the third segment with the project number in AR invoice.

        But, it is working fine for Expenditure Item based invoices alone.

        Whereas, it is NOT working for Event based invoices.

        Please help us how to fix this issue.

        Regards,

        Arun J

        • Perry Unrau

          Hi Arun,

          I would suggest you double check to ensure you are grouping events by contract line (grouping name starts with 'Contract line, ' or Contract Line Number is in the details region of the invoice format), such that contract line number is being stamped on the invoice line and can be used to get to the contract line DFF.

          Perry

           

    • Prasanna Reka

      Not sure if it works but give a try, create DFF on Invoice Line with Table Based value set- so you can write query to link multiple tables and filter the values based on condition, we can make sure correct project# is the only value available in list, sometimes if the query returns only one value it can default (note default may not work with all fields).

      Just give a try i am also struggling to make this kind of requirement work for user enabled PCC flexfield in Project Costing.