Invalid Transactions Page - Rejection reason 'Invalid Entity Location'

book

Article ID: 197226

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

Product: Clarity PPM
Keywords: Invalid Transactions; Invalid Entity Location; Post Transactions to Financials job

After XOGing transactions and running the Post Transactions to Financials job, these transactions can remain unprocessed in the Invalid Transactions page, with an error message of "Invalid Entity Location". All the preliminary checks that need to be performed is provided in this KB. If all these preconditions checkout, and if the transactions continue to get rejected, perform the following analysis.

Cause

Missing records in one of the financially related tables.

There are several checks that are performed by the Post Transactions to Financials job before it rejects transactions with this error message. The flow leading up to the rejection is as follows.

1. Determine WIP Entity using the following query

SELECT
       NVL(RTRIM(SOURCEFIELDENTITY), 'PE')
 FROM
       NAMEOPTIONS

2. Obtain Entity. If the first query did not return any result, replace <provide_code> with PE.

SELECT
       ENTITY
FROM
       locations
WHERE
       locationid in
       (
              SELECT
                     DECODE('<provide_code>', 'CE', CS.LOCATIONID, 'EE', E.LOCATIONID, P.LOCATIONID)
              FROM
                     IMP_TRANSACTIONIMPORT T
                   , PAC_MNT_PROJECTS      P
                   , CLNTSUPP              CS
                   , PAC_MNT_RESOURCES     E
              WHERE
                     T.TRANSIMPORTKEY in
                     (
                            SELECT
                                   TRANSIMPORTKEY
                            FROM
                                   IMP_TRANSACTIONIMPORT
                            WHERE
                                   IMPORTSTATUS = 'N'
                     )
                     AND P.PROJECT_CODE      = UPPER(T.PROJECT_CODE)
                     AND CS.COMPANY_CODE (+) = P.COMPANY_CODE
                     AND E.RESOURCE_CODE (+) = T.RESOURCE_CODE
       )

3. If no entity is returned above, the transaction gets rejected.

Environment

Version: 15.8.1

Resolution

1. Check for missing records in PAC_MNT_PROJECTS or PAC_MNT_RESOURCES tables. It can be verified by running the following queries.

SELECT
    locationid
FROM
    pac_mnt_projects pmp
WHERE
    pmp.project_code IN (
        SELECT
            project_code
        FROM
            imp_transactionimport
        WHERE
            importstatus = 'N'
    )
ORDER BY last_updated_date DESC
SELECT
    locationid
FROM
    pac_mnt_resources pmr
WHERE
    pmr.resource_code IN (
        SELECT
            resource_code
        FROM
            imp_transactionimport
        WHERE
            importstatus = 'N'
    )
ORDER BY last_updated_date DESC

2. If records are missing or incomplete in PAC_MNT_PROJECTS, then go to the corresponding Project record, make some change, update it and revert the change. Verify the record in the table again

3. The same approach as in Point 2 can be followed for Resources, if records are missing in PAC_MNT_RESOURCES table

4. Note that the change would have to be related to the financials. Such as setting a new location and reverting or changing the financial status etc.