Skip to main content
Kofax

MarkView Viewer - Particular user is missing from the Comment Request LOV

Summary

12063

Applies To

  • ERP System: Oracle, SAP
  • MarkView Version: 7.1 and higher

Behavior

  • When attempting to place the Comment Request Action you are unable to find a particular user in the Comment Request LOV.

Known Causes

In order for a user to be present in the Comment Request LOV, the user will need to:

  • Belong to a group that has the COMMENTER privilege (this is normally provided via the All Users group which has this privilege on many document types).
  • Be granted the COMMENTER Role.
  • Have a valid Email Address defined in the user account profile in the ERP system.
  • The MarkView user account is active and not end-dated.
  • The ERP user account for the user is active and unlocked.

Resolution

  • Privileges Check:
    Ensure that the user belongs to a group having the Commenter privilege:
    • Navigate to MarkView Home -> Administration -> Document Types
    • Choose Details for the Document Type you are attempting to place the Comment Request Action on.
    • Choose Privilege Group Auths.
    • Ensure the user belongs to a group where the 'Commenter {Y|N}' privilege is set to 'Y'
    • Ensure that the user has been granted the COMMENTER role.
  • Custom Join Point Check:
    Run this query in the MarkView Schema to verify if you have any Custom Join Points for the Commenter LOV: select a.* from mv_lov_join_point a, mv_lov_tab b where a.lov_id=b.lov_id and b.lov_name='COMMENTER';
    If the query output returns any CUSTOM Join Point calls, that typically means that a customization has been implemented and you will need to investigate the custom code to troubleshoot the issue. If you need assistance with your customization, you can contact the System Implementer directly, or log a case in the Kofax support portal, with the understanding that MarkView Technical Support may need to refer this to Kofax Professional Services.
  • Basic Query Check:
    Run this query in the MarkView Schema to check if the system retrieves the UserID you are looking for in the Commenter LOV, you have to enter the following when prompted:
    MARKVIEWUSERID --> User who is placing the Comment Request Markup. DOCUMENTID --> The Document Id on which the user is placing the markup
    ORGID --> The OrgID of the Document (It can be found in the WorkItem History output for the Invoice you are doing the test on).
    select distinct mup.last_name || ', ' || mup.first_name || ' (' || mup.user_id || ')' full_name, mup.last_name, mup.first_name, mup.user_id
    from mv_user_profile mup
    where (mup.enable_timestamp is null or mup.enable_timestamp <= sysdate)
    and (mup.disable_timestamp is null or mup.disable_timestamp >= sysdate) and mup.user_id <> '&MARKVIEWUSERID'
    and mup.user_id in
    (select distinct urg.user_id from sf_user_role_grant urg
    where urg.role_id = 'COMMENTER'
    and urg.enabled_yn = 'Y'
    and (urg.effective_as_of_timestamp is null or
    sysdate > urg.effective_as_of_timestamp) and (urg.effective_until_timestamp is null or
    sysdate < urg.effective_until_timestamp) intersect
    select distinct mugm.user_id from mv_document md,
    mv_privilege_group_auth pga,
    mv_user_group_member mugm where md.document_id = &DOCUMENTID
    and md.document_type_id = pga.document_type_id and pga.privilege_code = 'COMMENTER'
    and pga.auth_type = 'Y'
    and pga.authorized_group_id = mugm.group_id
    intersect
    select distinct mugm.user_id
    from mv_user_group_member mugm where mugm.group_id in
    (select distinct moga.authorized_group_id from mv_org_group_auth moga
    where moga.org_instance_id = (select o.org_instance_id
    from mvt_org o
    where o.org_id = &ORGID))); 
     
    • If the user name is retrieved in the previous query, then proceed with the next troubleshooting steps, otherwise you will need to determine why the user is not being returned from the query. If you are unable to determine why the user is not being returned by the query please log a case with MarkView Technical Support for further troubleshooting.
  • Verify the Info Source:
    Verify whether the preference MVERP_USER_INFO_SOURCE is set to ERP or MARKVIEW.
    If its MarkView, then verify the user has a valid email address in mvt_approval_user table and ensure this query returns the UserID you are looking for in the LOV:
    select up.user_id, au.email_address, up.first_name, up.last_name, up.first_name || ' ' || up.last_name full_name from mv_user_profile up, mvt_approval_user au
    where up.user_id = '&USERID'
    and (up.enable_timestamp is null or up.enable_timestamp <= sysdate) and (up.disable_timestamp is null or up.disable_timestamp > sysdate) and up.user_id = au.user_id(+);
    If it is set to ERP, then verify the below based on the ERP System you have (SAP or Oracle):

Oracle:

  • Ensure that the user has a valid email address in both Oracle tables fnd_user and per_all_people_f.
  • Ensure that the user account is active and can access Oracle without any issue.
    You can use the query below (APPS schema) to verify:
    select fu.user_name, fu.email_address, papf.email_address , papf.effective_start_date, papf.effective_end_date from fnd_user fu,per_all_people_f papf where fu.employee_id = papf.person_id and fu.user_name = upper('&User_Name')

SAP:

  • Ensure that the user has a valid email address defined from SAP side.
  • Ensure that the user account is unlocked and the user can access SAP from SAP GUI without any issue.
    To ensure that MarkView is able to retrieve the user account from SAP and the user has an active account, you can execute the BAPI function below, it should return all active users and this particular user should be one of them:
    • Execute the BAPI '/S170/BAPI_AP_GET_USER_INFO' from SAP GUI using the TCode: se37.
    • Enter the value: /S170/BAPI_AP_GET_USER_INFO.
    • Press F8 and check the retrieved list of users and see If that particular user is in the list, If not or the function has not retrieved any user or shown any error, please contact the MarkView Support Team and update them with these details.

Keywords: LOV, Commenter, "Comment Request"