PLI/RPLI System Clarifications on Sales Force ID Creation, PAN Updation & DEAO Mapping Issues
Clarifications Issued on Sales Force ID Creation, PAN Updation Issues and DEAO ID Mapping in PLI/RPLI System
Important clarifications have been issued regarding issues faced by Circles and Divisions in connection with Sales Force/Monitoring Staff ID creation, PAN updation problems, and DEAO ID creation/mapping in the PLI/RPLI system. The clarifications address multiple operational concerns raised from the field units.
Query No. 1: Product and Distribution Channel Fields Not Visible During Sales Force ID Creation
Field units reported that while creating Sales Force/Monitoring Staff IDs in the Production environment, the Product and Distribution Channel fields were not appearing, although the same fields were visible in the UAT environment.
Clarification Issued
During creation of a new Advisor profile, the Distribution Channel and Product Class are automatically derived from the Advisor Coordinator (DH) profile.
If these values were selected during setup of the Advisor Coordinator (DH), the same values will automatically populate for all new Advisor profiles created under that Coordinator.
If no values were selected at the Advisor Coordinator (DH) level, these fields will not appear during Advisor profile creation.
It has also been clarified that this configuration does not affect commission calculation in any manner.
Query No. 2 & 3: PAN Updation Issues for IDs Converted from Divisional Superintendent to Divisional Head
Several units reported difficulty in updating PAN details for accounts converted from Divisional Superintendent to Divisional Head (DH) due to incorrect default PAN category settings and non-editable fields.
Additionally, for changed AC to DH IDs, the “Person” field is appearing as “N”.
Clarification Issued
The concerned offices have been requested to provide 1 or 2 sample cases for detailed analysis in the following format:
Circle Name
Name of Division
DH ID
This information will help the technical team examine the issue and provide a resolution.
Query No. 4: Creation of Separate DEAO IDs and Mapping Issues
Queries were also raised regarding creation of separate DEAO IDs for existing DEEMP users working in Administrative Offices and problems encountered while tagging DEEMP IDs with ASP(HQ).
Clarification Issued
The following instructions have been communicated:
Existing DEEMP profiles may be changed to Pending status.
New IDs may then be created under the role of DEAO.
The newly created DEAO IDs should subsequently be mapped with ASP(HQ)/OS/Dy. OS.
Circles have also been advised to share details of policies currently tagged with DEEMP profiles in the prescribed template to the CEPT team.
The CEPT team will thereafter map/tag those policies with the newly created DEAO IDs.
These clarifications are expected to help Circles and Divisions resolve operational issues related to Sales Force profile creation, PAN updation, and DEAO mapping activities in the PLI/RPLI application environment.