AnsweredAssumed Answered

Account review Coverage view not populated.

Question asked by Muzammil Kaleemulla on Jan 15, 2018
Latest reply on Jan 16, 2018 by Boris Lekumovich

Like • Show 0 Likes0
Comment • 6

Hi,

I need to use a coverage file to determine the reviewers for an account review, and I know that the filter is applied on V_REVIEW_ACCOUNT_DETAIL_DATA. Upon using a coverage file, I don't see the desired user_id as review and nothing has been assigned to him.

After querying the View V_REVIEW_ACCOUNT_DETAIL_DATA, the result is an empty view.
Is this normal? Shouldn't this view be filled when I run a review , and the accounts should be mapped against that review_id?

Coverage file sample data:

user_id='tommyh'|supervisor_id='anandb'|review.

Kindly assist.

Thanks.

No one else has this question

Outcomes

6 Replies

Boris Lekumovich Jan 15, 2018 2:15 AM
Mark Correct
Correct Answer
The sample data might be incorrect.
I suggest you check the help section on how to construct a correct coverage file for an account review.

Look for "Information about Account Review Entries in a Coverage File" and "Examples of Reviewer/Monitor Coverage File Entries" in the help
Like • Show 0 Likes0
Actions
- Muzammil Kaleemulla @ Boris Lekumovich on Jan 15, 2018 2:42 AM
  Mark Correct
  Correct Answer
  Thank you for responding Boris.
  Now I've changed the column name to only those that be used to filter from V_REVIEW_ACCOUNT_DETAIL_DATA. I missed this information when I initially read, and I assumed any column can be used to filter.
  
  However, V_REVIEW_ACCOUNT_DETAIL_DATA is still empty and all accounts are unassigned.
  
  Sample Coverage text:
  user_id='E12345'| UPPER(MAPPED_USER_NAME) like '%YAS%'
  Like • Show 0 Likes0
  Actions
- Muzammil Kaleemulla @ Boris Lekumovich on Jan 16, 2018 2:01 AM
  Mark Correct
  Correct Answer
  Hi,
  Since we are limited with few columns that can be used to filter, is it possible to set reviewer based on supervisor_id?
  For example, if account's user supervisor is "A1234", then "S6789" should be the reviewer and so on.
  
  Also, shouldn't the view V_REVIEW_ACCOUNT_DETAIL_DATA have few rows in it?
  Like • Show 0 Likes0
  Actions
  - Boris Lekumovich @ Muzammil Kaleemulla on Jan 16, 2018 5:05 AM
    Mark Correct
    Correct Answer
    You have out of the box configuration for supervisors to review the accounts of their subordinates (screenshot below)
    
    An example to a coverage file for account review:
    user_id='11'|ACCT_CAS3='Medium'
    
    user_id is the value taken from user_id column in pv_users
    Like • Show 0 Likes0
    Actions
    - Muzammil Kaleemulla @ Boris Lekumovich on Jan 16, 2018 5:17 AM
      Mark Correct
      Correct Answer
      Well, I guess I didn't explain the requirement correctly. My bad.
      The requirement is not supervisors review the accounts of their subordinates. I'm aware that this is OOTB.
      
      The customer wants to assign 1 reviewer (may be the head of that dept.) for accounts that are subordinate of supervisors say Boris, Muzammil and Tim, and another reviewer for accounts that are subordinates of Supervisors Garret, David and Manoj and so.
      
      So the goal is to assign
      user_id='A1234', for all accounts' whose supervisor is 'Boris' or 'Muzammil' or 'Tim'
      User_id ='S6730' for all accounts' whose supervisor is 'Garret' or 'David' or 'Manoj' ... and so on
      in words.
      
      I hope this has made the requirement clear.
      
      Also, I don't understand why V_REVIEW_ACCOUNT_DETAIL_DATA doesn't have any rows.
      Because my understanding is that this view then gets filtered and the accounts are assigned to respective reviewer based on the coverage file. So if this view is empty, nothing would get assigned correct?
      Like • Show 0 Likes0
      Actions
      - Boris Lekumovich @ Muzammil Kaleemulla on Jan 16, 2018 5:55 AM
        Mark Correct
        Correct Answer
        Have you considered to use the user review instead of account review?
        I believe it might be easier to achieve.
        
        If account review is the only way to go, then consider the following (wasn't tested)
        Create a managed account attribute (integer type, not to waste a precious account attribute)
        Using sql update query (with your business logic) populate the attribute with a specific value
        Let's say, for all accounts' whose supervisor is 'Boris' or 'Muzammil' or 'Tim' the value will be 111
        For all accounts' whose supervisor is 'Garret' or 'David' or 'Manoj' the value will be 222
        Note: you will need to run the SQL update query before the review execution.
        
        The coverage file will look like this:
        user_id='A1234'|ACCT_CAI1=111 user_id='S6730'|ACCT_CAI3=222
        The approach above is not ideal, but it's a start. You might be able to come up with something more flexible and suitable for you requirements.
        
        I don't think you should worry about V_REVIEW_ACCOUNT_DETAIL_DATA
        I have a coverage file configured and the view is still empty (I don't know whether it's expected or a bug).
        Like • Show 0 Likes0
        Actions

Account review Coverage view not populated.

Outcomes

Related Content

Recommended Content