Professional Documents
Culture Documents
Submitted to
By
ORACLE COMMUNICATIONS 1
OAP User Manual February 18, 2017
Table of Contents
1. About this Document .......................................................................................................................... 10
2. Revision History .................................................................................................................................. 10
3. Access considerations to use OAP ...................................................................................................... 10
4. Application Login Process ................................................................................................................... 12
5. Master Data Setup .............................................................................................................................. 13
5.1. BRM Master Setup .......................................................................................................................... 13
5.1.1. Channel List ................................................................................................................................. 13
5.1.2. Channel Map ............................................................................................................................... 14
5.1.3. CATV Provisioning ....................................................................................................................... 15
5.1.4. Refund Rule ................................................................................................................................. 18
5.2. OAP Master Setup ........................................................................................................................... 22
5.2.1. Role Definitions ........................................................................................................................... 22
5.2.2. Role and Permission Settings ...................................................................................................... 25
5.2.3. User and Role Settings ................................................................................................................ 27
5.2.4. Plans and Pricing ......................................................................................................................... 30
5.2.4.1. Create a new Plan List ............................................................................................................. 31
5.2.4.2. Load an existing Plan List Details ............................................................................................ 33
5.2.4.3. Edit an existing Plan List .......................................................................................................... 34
5.2.4.4. Manage Geo Access for an existing Plan List. ......................................................................... 36
5.2.5. User and Plan Settings ................................................................................................................ 37
5.2.6. Country Geo Setup ...................................................................................................................... 39
5.2.7. State Geo Setup .......................................................................................................................... 41
5.2.8. District Geo Setup ....................................................................................................................... 44
5.2.9. City Geo Setup............................................................................................................................. 46
5.2.10. Area Geo Setup ........................................................................................................................... 48
5.2.11. Street Geo Setup ......................................................................................................................... 51
5.2.12. Location Geo Setup ..................................................................................................................... 54
5.2.13. Building Geo Setup ...................................................................................................................... 57
5.3. Ticket Mgmt. Master Setup ............................................................................................................ 60
5.3.1. Group Setup ................................................................................................................................ 60
5.3.2. Team Setup ................................................................................................................................. 61
5.3.3. Queue Setup ............................................................................................................................... 65
ORACLE COMMUNICATIONS 2
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 3
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 4
OAP User Manual February 18, 2017
6.3.3.4. Changing a package in Main Conn. for Res. Account ............................................................ 177
6.3.3.5. STB swap when its identified as faulty .................................................................................. 178
6.3.3.6. VC swap when its identified as faulty ................................................................................... 179
6.3.3.7. Corporate Parent customer registration .............................................................................. 180
6.3.3.8. Corporate Child customer registration ................................................................................. 181
6.3.3.9. Change LCO of customer....................................................................................................... 182
6.3.3.10. Verification of Self-care account profile ............................................................................... 184
6.3.3.11. CATV Service Termination for Additional TV. ....................................................................... 188
6.3.3.12. CATV Service Termination for Main TV. ................................................................................ 189
6.3.3.13. CATV Temporary Service Suspension ................................................................................... 191
6.3.3.14. CATV service reactivation as per customer request ............................................................. 191
6.3.3.15. View Invoices of customer as a CSR ...................................................................................... 193
6.3.3.16. View KYC/CAF PDF of customer as a CSR .............................................................................. 195
6.3.3.17. Post Cash Payment for Single customer as a CSR ................................................................. 196
6.3.3.18. Post Cheque Payment for Single customer as CSR ............................................................... 197
6.3.3.19. Payment receipt verification as a CSR .................................................................................. 198
6.3.3.20. Payment reversal because of wrong posting ........................................................................ 199
6.3.3.21. Payment reversal because of cheque bounce ...................................................................... 200
6.3.3.22. Single customer account level credit adjustment................................................................. 202
6.3.3.23. Single customer account level debit adjustment.................................................................. 203
6.3.3.24. Single customer bill level credit adjustment ......................................................................... 204
6.3.3.25. Single customer bill level debit adjustment .......................................................................... 205
6.3.3.26. Single customer Item level credit adjustment ...................................................................... 205
6.3.3.27. Single customer Item level debit adjustment ....................................................................... 206
6.3.3.28. Apply tax exemption for a specific customer Acc. ................................................................ 206
6.3.4. Manage tickets for individual customers and VHD cases ......................................................... 207
6.3.4.1. Individual Customer Ticket Management ............................................................................. 207
6.3.4.1.1. Create a Call Log / FTR as a CSR ............................................................................................ 207
6.3.4.1.2. Create a Call Log / Work Order as a CSR ............................................................................... 208
6.3.4.1.3. View Open Work Order History as a CSR .............................................................................. 209
6.3.4.1.4. Update Remarks in Open Work Order as a CSR .................................................................... 210
6.3.4.1.5. Auto Assignment of Work Order to a Service Team ............................................................. 211
6.3.4.1.6. View Assigned Work Order by Service Coordinator ............................................................. 212
ORACLE COMMUNICATIONS 5
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 6
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 7
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 8
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 9
OAP User Manual February 18, 2017
The document provides the user manual to allow handling critical OAP Activities by operations
team of Fastway Transmissions Pvt. Ltd and is under constant improvement for betterment.
The document illustrate steps involved in performing various activities as listed in the Table
of Contents section. Included material covers screenshots, field level descriptions, possible
error /confirmations messages that are applied as per concerned use case / business scenario.
This document has been written purely for the use of operations team so it is not technical in
nature and assumes very little knowledge in the readers of this document about the system.
Document is filled with lot of visual material to quickly understand how system UI looks like
when accessing it for different use cases and during respective workflows execution.
A separate operation manual has been provided and should be referred to know about
catalogue / product configuration and hence this guide does not fit for that purpose, although
some use cases on price plan management are covered as they are in OAP access purview.
This document does not cover the application monitoring guidelines for OAP. A separate
document (Standard Operational Procedure) will need to be created by operations team.
This document will continue to evolve as more functionalities are added to the OAP in future.
2. Revision History
1. OAP (Oracle Access Portal) is meant for direct login only by business users.
2. The types of business users that can login to OAP are as following
a. Customer Service Representative (CSR)
ORACLE COMMUNICATIONS 10
OAP User Manual February 18, 2017
3. Every business user who wants to login to OAP should have Active account status and
respective roles assigned by an admin user.
4. A user need the login account user-name and password recognized by OAP to login.
5. It is recommended to keep the browser cache clear for optimal performance and
cookies & browser pop ups enabled to allow using application without any issues.
6. The browser type and its version used for accessing OAP should be equal or above
than the specified versions as mentioned in the below table
7. The application requires integration with SMS gateway so network connectivity should
be highly ensured to avoid any issue with using functionalities where SMS is sent.
8. Connectivity to Database and BRM application server is absolutely essential and should
be 100 % available else the use of application will be affected leaving poor experience.
9. OAP is different from Self-Care Portal which is mainly for the end customer login.
ORACLE COMMUNICATIONS 11
OAP User Manual February 18, 2017
Profile being displayed below for a business user of account type: CSR_ADMIN
ORACLE COMMUNICATIONS 12
OAP User Manual February 18, 2017
Master data setup plays a crucial role in the functioning of OAP hence such privileges should
be given only to very few roles (like CSR_ADMIN) as a recommended standard practice. The
integrity of master data should be protected in the system in all circumstances.
Objective: This screen allows to configure CATV Channel List data in BRM via OAP UI
Steps:
1. Login to OAP as a CSR Admin who will have permissions to configure master data.
2. Navigate to the menu path OAP >> Set up >> BRM Master Setup >> Channel List
3. Provide free text Inputs as required for Channel Name, Channel Id, Channel Type,
Channel Genre, Channel Rate, & Type on the screen loaded in front of you.
4. You will get a confirmation message on the screen when request is complete.
ORACLE COMMUNICATIONS 13
OAP User Manual February 18, 2017
Objective: This screen allows to configure Channel Map master data in BRM via OAP UI.
Steps:
1. Login to OAP as a CSR Admin who will have permissions to configure master data.
2. Navigate to the menu path OAP >> Set up >> BRM Master Setup >> Channel Map
3. Provide free text Inputs as required for Provisioning Tag, Package Type, Channel
Name, and Channel Id on the screen loaded in front of you.
4. You will get a confirmation message on the screen when request is complete.
ORACLE COMMUNICATIONS 14
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 15
OAP User Manual February 18, 2017
1. Login to OAP as a CSR Admin who will have permissions to configure master data.
2. Navigate to the menu OAP >> Set up >> BRM Master Setup >> CATV Provisioning
3. Provide free text Inputs (as required) for Package Type, Package Type, and
Conditional Access Id for following network elements
a. CISCO Power Key
b. GOSPEL
c. CONEX.
4. You will get a confirmation message on the screen when request is complete.
5. After creation, the submitted data will be visible in the grid on lower part of page.
ORACLE COMMUNICATIONS 16
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 17
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 18
OAP User Manual February 18, 2017
Objective: This screen allows to configure CATV Refund Rules in BRM via OAP UI.
Steps:
1. Login to OAP as a CSR Admin who will have permissions to configure master data.
2. Navigate to the menu OAP >> Set up >> BRM Master Setup >> Refund Rule
3. Provide free text Inputs (as required) for Rule Name, Plan Name, Rule Type, Step
Unit, Start Step, End Step, Step Amount, Step Value, & Flag.
4. You will get a confirmation message on the screen when request is complete.
5. After creation, the submitted data will be visible in the grid on lower part of page.
ORACLE COMMUNICATIONS 19
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 20
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 21
OAP User Manual February 18, 2017
Objective: This screen allows to create & edit user roles in OAP and they would be mapped
with permissions in subsequent sections of master setup via OAP UI. Having such roles in the
system provide an easy way to manage permissions assignment to the actual business users.
Steps:
1. Login to OAP as a CSR Admin who will have permissions to configure master data.
2. Navigate to the menu OAP >> Set up >> OAP Master Setup >> Role Definitions
3. Provide Inputs as following on the screen to create a new Role
a. Role Name Name of the role that you want to see in application
b. Role Description A friendly and clear description of the role
c. Privilege Description What kind of privileges this role should have
d. Active: Mark the slider to reflect the role as Active
4. You will get a confirmation message on the screen when role is created.
5. After creation, the role definition will be visible in the grid on lower part of page.
ORACLE COMMUNICATIONS 22
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 23
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 24
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 25
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 26
OAP User Manual February 18, 2017
Objective: Here we map a business user account with one or more roles as per operational
requirements. The permissions mapped to the associated roles will be automatically given to
the user account and hence upon login, that user would be able to access all relevant
functional links through OAP. This mapping can be edited also later on to associate more
roles or to remove existing associated roles if needed. This operation should be given to very
few privileged admin user accounts to prevent any un-intentional access to functionalities.
Steps:
1. Login to OAP as a CSR Admin who has permissions to map user accounts with roles.
2. Navigate to OAP >> Set up >> OAP Master Setup >> User and Role Settings
3. Perform below steps as suggested to map a role with permissions
a. Search and select a role using either account number / registered mobile no.
b. Already assigned and available roles for assignment would be auto populated.
c. Select the roles that need to be now to be mapped with the user account and
move them to the Assigned Roles section by using the > labelled button.
4. Click on the update button to map the roles in the Assigned Roles section with user.
ORACLE COMMUNICATIONS 27
OAP User Manual February 18, 2017
5. You will get a confirmation message on the screen when mapping is saved.
6. Similar steps to be followed for the existing mapping of a user and roles.
ORACLE COMMUNICATIONS 28
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 29
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 30
OAP User Manual February 18, 2017
constraints applied to the plan-list so that based on geo scope, they may or may not be visible
to the CSR accounts while managing the end customers in BAU operations.
ORACLE COMMUNICATIONS 31
OAP User Manual February 18, 2017
While creating a plan-list, displayed plans are searched and retrieved from Billing System.
Plan-list definition is stored and managed within OAP only and not sent to Billing System.
ORACLE COMMUNICATIONS 32
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 33
OAP User Manual February 18, 2017
2. Navigate to OAP >> Set up >> OAP Master Setup >> Plans and Pricing.
3. Perform below steps as suggested to load an existing plan list
4. Select a plan list from the plan-list names displayed in the drop down.
ORACLE COMMUNICATIONS 34
OAP User Manual February 18, 2017
While editing a plan-list, new plans can be added to the plan-list and existing associated plans
can be moved out of the plan-list definition.
ORACLE COMMUNICATIONS 35
OAP User Manual February 18, 2017
1. A Plan list geo access restrictions is manageable through the OAP interface.
2. The widest scope it can be applied is at PAN India level (All states).
3. If needed plan-list geo constraints can be narrowed to a restricted scope too example,
a particular state or few cities under a particular state etc.
4. For a specific plan-list, the geo-constraints can be modified at a later stage.
5. It is essential that for every plan list created in the system, the geo access is defined.
6. Key inputs while assigning geo access constraints for a plan list are as following
a. Select the plan list name which you want to configure geo access control.
b. Select the target state. If nothing specific then select ALL.
c. Select the target district. If nothing specific then select ALL.
d. Select the target city. If nothing specific then select ALL.
e. Select the target region. If nothing specific then select ALL.
ORACLE COMMUNICATIONS 36
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 37
OAP User Manual February 18, 2017
3. Follow below steps to associate a user (CSR) account with one or more plan lists
a. Navigate to OAP >> Set up >> OAP Master Setup >> User and Plans Settings.
b. Search and select a user account using either the account number or RMN.
c. When the searched user account is selected then the already assigned and
available (to be assigned) plan-lists get visible in the screen accordingly.
d. To narrow down the search scope of plan-lists, select the appropriate
combination of State, District, City and Region and accordingly it will filter the
shown plan-lists in the available plan-lists section.
e. Choose any more plan-lists that you want to assign to the user account and
move those plan-lists from the Available to Assigned plan-lists section.
f. Click on Update button and you will get a confirmation message on the screen.
ORACLE COMMUNICATIONS 38
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 39
OAP User Manual February 18, 2017
1. This functionality allows to setup the master data for a Country as geo entity in the system.
2. Navigate to OAP >> Set up >> OAP Master Setup >> Country.
3. Provide inputs as following on the screen loaded in front of you.
a. Country Code Enter value 91 for India (Country).
b. Name of the Country.
c. Short name of the country (IND)
d. Currency Code 356 (For Indian Rupees.)
e. Currency INR (For Indian Rupees.)
4. Click on the submit button.
ORACLE COMMUNICATIONS 40
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 41
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 42
OAP User Manual February 18, 2017
To edit an existing State, choose the target state from the display grid and click edit icon.
ORACLE COMMUNICATIONS 43
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 44
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 45
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 46
OAP User Manual February 18, 2017
Editing an existing City Details. Select target city record from the grid and click on edit icon.
ORACLE COMMUNICATIONS 47
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 48
OAP User Manual February 18, 2017
1. This section allows to setup the master data for an Area as geo entity in the system.
2. Area is the topmost entity in the geo data hierarchy that maps to a pin-code.
3. An area is defined under a city and must have a unique area code mapped to it.
4. It is recommended to not configure duplicate area names under a specific city.
5. Navigate to OAP >> Set up >> OAP Master Setup >> Area.
6. Provide inputs as following on the screen loaded in front of you.
a. Select type of service applicable (CATV only for Fastway)
b. Select State from the drop down.
c. Select District from the drop down.
d. Select City Detail from the drop down.
e. Select a specific Region from the drop down.
f. Enter the zip code (Pincode) applicable for the Area being defined.
g. Input Area Code A unique code for each Area to be given.
h. Name of the Area (Unique for each Area).
i. Select Service Type under Home Pass drop down.
j. Enter Home Pass capacity (Integer value > 0)
ORACLE COMMUNICATIONS 49
OAP User Manual February 18, 2017
Editing an existing Area Detail is allowed and can be done if needed. Must not edit area
code once defined and created the area.
ORACLE COMMUNICATIONS 50
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 51
OAP User Manual February 18, 2017
Description: A Street is reported under an area in the geo structure of data. A Street
shares the same pin-code that has been applied at the area level.
1. Navigate to OAP >> Set up >> OAP Master Setup >> Street.
2. Provide inputs as following on the screen loaded in front of you.
a. Select type of service applicable (CATV only for Fastway)
b. Enter the zip code (Pincode) applicable for the Street being defined.
c. Select Area Name based on the Pincode entered in the previous step.
d. Input name of the Street (Unique for each Street).
e. Select Service Type under Home Pass drop down.
f. Enter Home Pass capacity (Integer value > 0)
3. Click on the submit button.
4. On-screen confirmation would be provided.
ORACLE COMMUNICATIONS 52
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 53
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 54
OAP User Manual February 18, 2017
Description: A Location is reported under an area in the geo structure of data. A Location
shares the same pin-code that has been applied at the area level.
1. Navigate to OAP >> Set up >> OAP Master Setup >> Location.
2. Provide inputs as following on the screen loaded in front of you.
a. Select type of service applicable (CATV only for Fastway)
b. Enter the zip code (Pincode) applicable for the Location being defined.
c. Select Area Name based on the Pincode entered in the previous step.
d. Input name of the Location (Unique for each Location).
e. Select Service Type under Home Pass drop down.
f. Enter Home Pass capacity (Integer value > 0)
3. Click on the submit button.
4. On-screen confirmation would be provided.
ORACLE COMMUNICATIONS 55
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 56
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 57
OAP User Manual February 18, 2017
Description: A Building is reported under a Street in the geo structure of data. A Building
shares the same pin-code that has been applied at the respective Street level.
1. Navigate to OAP >> Set up >> OAP Master Setup >> Building.
2. Provide inputs as following on the screen loaded in front of you.
a. Select type of service applicable (CATV only for Fastway)
b. Enter the zip code (Pincode) applicable for the Location being defined.
c. Select Area Name based on the Pincode entered in the previous step.
d. Select the Street populated based on the selected Area.
e. Input name of the Building (Unique for each Building).
f. Select Service Type under Home Pass drop down.
g. Enter Home Pass capacity (Integer value > 0)
3. Click on the submit button.
4. On-screen confirmation would be provided.
ORACLE COMMUNICATIONS 58
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 59
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 60
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 61
OAP User Manual February 18, 2017
In the context of customer ticket management, defining a team is essential and it represents
a service team which has the responsibilities to manage the customer tickets / work orders
when a call is logged by the CSR agents as per customer calls / feedback / other channels.
A team ultimately gets placed in a group under a particular state. A team is generally mapped
with an LCO to serve the work orders of respective customers however a team can be shared
across multiple LCOs under a particular state. An LCO can also have multiple teams if required
per unique combination of disposition parameters (Call Type, Call Area and Call Category).
ORACLE COMMUNICATIONS 62
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 63
OAP User Manual February 18, 2017
Below is the team setup being created for handling the VHD work orders? Generally it is
recommended to have separate service teams to deal with VHD specific and normal customer
complaints specific work orders. In case of defining a VHD team you must map all cities under
the chosen state while creating a VHD team definition.
ORACLE COMMUNICATIONS 64
OAP User Manual February 18, 2017
It is highly recommended to define separate queues for VHD and non-VHD types of work
orders SLAs and is a good idea to define a separate queue for each service team. Mapping of
a queue to a call type is an important consideration and plays a vital role in automatic
assignment of work order to the associated service team when a ticket is raised by CSR.
ORACLE COMMUNICATIONS 65
OAP User Manual February 18, 2017
4. Note: Once a team has been put in operational use then you should not change the
service (ex: CATV) & call types for which queue was originally associated with.
ORACLE COMMUNICATIONS 66
OAP User Manual February 18, 2017
Below is the queue being setup to handle the VHD type of work orders
ORACLE COMMUNICATIONS 67
OAP User Manual February 18, 2017
1. Navigate to OAP >> Set up >> CT Master Setup >> Assign Team and Queue.
2. Provide inputs as following on the screen loaded in front of you.
a. Select the group from which you want to pick the team for mapping.
b. Select a team from the list populated based on the selected group.
c. Select a specific queue that you want to map to the selected team.
ORACLE COMMUNICATIONS 68
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 69
OAP User Manual February 18, 2017
Below is mapping of VHD queue to state level VHD team to handle VHD WO
ORACLE COMMUNICATIONS 70
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 71
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 72
OAP User Manual February 18, 2017
This screen is used to assign a business user (always a CSR) as the coordinator of a service
team. This assignment is essential and has high importance as it plays a role in the automatic
assignments of work orders to intended service team when the ticket is logged by the CSR.
It is a valid scenario to make the same business user as a coordinator for more than one
service teams. If done so then the assigned work orders to all those teams will be visible in
that service coordinator dashboard upon his login, but for the simplicity sake, a separate
coordinator account mapping with each service teams also does work.
1. Navigate to OAP >> Set up >> CT Master Setup >> Team Admin Mapping.
2. Perform steps as below and provide required inputs as specified.
a. Search for service coordinator (CSR) using Account Number or Name input.
b. Upon selecting the searched user account record, the already assigned and
available teams (can be assigned) are listed on the screen bottom section.
c. Associate a specific team to the target CSR by moving that team from Available
teams section to the Assigned teams section.
d. Associate only those teams which are under one of the states already mapped
in target CSR geo access else this mapping wont serve any purpose.
ORACLE COMMUNICATIONS 73
OAP User Manual February 18, 2017
e. Disassociate a specific team from the target user by moving that team from
Assigned teams section to the Available teams section.
ORACLE COMMUNICATIONS 74
OAP User Manual February 18, 2017
This screen supports the assignment of a service engineer (generally a technical person from
LCO side), who works at the ground level to resolve the created work order.
It is understood that in case of Fastway, LCO organization user do not use the online system
and communication with them from Fastway service management team is managed offline
therefore to stick with designed service model of the system, a member of the Fastway service
team itself (someone other than the coordinator) can be mapped as a service engineer to the
team via this screen so that his name then can be reflected in the engineers list while the
team coordinator schedules the assignment of that work order.
If the Service executive to team assignment is not done then the teams service coordinator
will have to assign the work order to himself and track for closure.
Steps to map a service engineer with a team are same as what were followed for coordinator.
ORACLE COMMUNICATIONS 75
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 76
OAP User Manual February 18, 2017
This configuration represents the call type and it plays an important role in the disposition
parameters set used during the ticket creation by the helpdesk CSR. This is the topmost entity
in the disposition parameters hierarchy used by the ticket management system.
The Call Type also plays a vital role while defining a queue for ticket mgmt. and it is used as
one of the parameter to identify concerned service team while the ticket is raised by CSR.
1. Navigate to OAP >> Set up >> CT Master Setup >> Call Type.
2. Perform steps as below and provide required inputs as specified.
a. Select the relevant Service Type (CATV only).
b. Input a meaningful name of the call type (provide one word or if multiple words
given then concatenate them by an underscore).
c. Select the Status as Active.
d. Carefully select True or False from the field drop down (IS_VHD).
e. The field (IS_VHD) will determine whether the call type (being created) and
underneath disposition will be used for individual tickets or for VHD type tickets.
ORACLE COMMUNICATIONS 77
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 78
OAP User Manual February 18, 2017
This configuration represents the call area and it plays an important role in the disposition
parameters set used during the ticket creation by the helpdesk CSR. This is the level-2 entity
in the disposition parameters hierarchy used by the ticket management system.
The Call Area is defined under a specific Call Type in the disposition parameters hierarchy.
1. Navigate to OAP >> Set up >> CT Master Setup >> Call Area.
2. Perform steps as below and provide required inputs as specified.
a. Select the relevant Service Type (CATV only).
b. Select the top level entity in the disposition hierarchy (i.e. Call type).
c. Input a meaningful name of the call area (provide one word or if multiple words
given then concatenate them by an underscore).
d. Select the Status as Active.
ORACLE COMMUNICATIONS 79
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 80
OAP User Manual February 18, 2017
This configuration represents the call category and it plays an important role in the disposition
parameters set used during the ticket creation by the helpdesk CSR. This is the level-3 entity
in the disposition parameters hierarchy used by the ticket management system.
The Call Category is defined under a specific Call Area in disposition parameters hierarchy.
ORACLE COMMUNICATIONS 81
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 82
OAP User Manual February 18, 2017
This configuration represents the call sub-category and it plays an important role in the
disposition parameters set used during the ticket creation by the helpdesk CSR. This is the
level-4 entity in the disposition parameters hierarchy used by the ticket management system.
The Call Sub-Category is defined under a specific Call Category in disposition hierarchy.
1. Navigate to OAP >> Set up >> CT Master Setup >> Sub Category.
2. Perform steps as below and provide required inputs as specified.
a. Select the relevant Service Type (CATV only).
b. Select the top level entity in the disposition hierarchy (i.e. Call type).
c. Select the next entity in the disposition hierarchy (i.e. Call Area).
d. Select the next entity in the disposition hierarchy (i.e. Call Category).
e. Input a meaningful name of the call sub category (provide one word or if
multiple words given then concatenate them by an underscore).
f. Choose (type of action workflow) from the list First Time Resolution, or Work
Order and this will be of potential use in self-care portal in future development.
g. Select the Status as Active.
ORACLE COMMUNICATIONS 83
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 84
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 85
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 86
OAP User Manual February 18, 2017
This configuration represents the type of action (FTR/Work Order) to be taken by the system
when the other disposition parameters are chosen in the hierarchy and so it plays an
important role in the disposition set used during the ticket creation by the CSR. This is the
level-6 entity in the disposition parameters hierarchy used by the ticket management system.
1. Navigate to OAP >> Set up >> CT Master Setup >> Action.
2. Perform steps as below and provide required inputs as specified.
a. Select the relevant Service Type (CATV only).
b. Select the top level entity in the disposition hierarchy (i.e. Call type).
c. Select the next entity in the disposition hierarchy (i.e. Call Area).
d. Select the next entity in the disposition hierarchy (i.e. Call Category).
e. Select the next entity in the disposition hierarchy (i.e. Call Sub Category).
f. Select the next entity in the disposition hierarchy (i.e. Resolution Name).
g. Input a meaningful name of the call Action Type (provide one word or if multiple
words given then concatenate them by an underscore).
h. Select Action Status (Completed or FWD To WO) for the Action being created.
i. Select the Status as Active.
3. Click on the submit button & on-screen confirmation would be provided.
ORACLE COMMUNICATIONS 87
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 88
OAP User Manual February 18, 2017
1. Navigate to OAP >> Set up >> CT Master Setup >> Team and LCO Mapping.
2. Perform steps as below and provide required inputs as specified.
a. Select the relevant Service Type (CATV only).
b. Select the Access State under which the target LCO is registered.
c. Select a Group Name (list populated as per already selected State).
d. Select a team Name (list populated as per already selected Group).
e. Select a city (list populated as per already team name).
f. Select an LCO (list populated as per already city name).
3. When all above inputs are chosen then screen fetches and displays already associated
and not associated mapping of disposition parameters.
4. Chose the required disposition set with the input combinations as needed.
5. Click on the submit button & on-screen confirmation would be provided.
ORACLE COMMUNICATIONS 89
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 90
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 91
OAP User Manual February 18, 2017
1. Navigate to OAP >> Set up >> Prospect Master Setup >> SC Pincode Mapping.
2. Perform steps as below and provide required inputs as specified.
ORACLE COMMUNICATIONS 92
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 93
OAP User Manual February 18, 2017
This screen allows to map a business user (always a CSR) as a sales executive based on a
specific pin-code. It is possible to map the same sales executive with multiple pin-codes.
Sales executive is the person supposed to do ground level follow ups on the created lead /
prospect and ultimately reports back the feedback to the sales coordinator.
It is essential to have a sales executive mapping to create a lead against a given pin-code.
The steps here would be similar to followed for Pincode to Sales Coordinator mapping
ORACLE COMMUNICATIONS 94
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 95
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 96
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 97
OAP User Manual February 18, 2017
1. Navigate to OAP >> Set up >> Prospect Master Setup >> Channel.
2. Perform steps as below and provide required inputs as specified.
a. Input a meaningful name of the prospect channel (provide one word or if
multiple words given then concatenate them by an underscore).
b. Input a meaningful description of the prospect channel being created.
ORACLE COMMUNICATIONS 98
OAP User Manual February 18, 2017
ORACLE COMMUNICATIONS 99
OAP User Manual February 18, 2017
1. Navigate to OAP >> Set up >> Prospect Master Setup >> Source.
2. Perform steps as below and provide required inputs as specified.
a. Input a meaningful name of the prospect source (provide one word or if multiple
words given then concatenate them by an underscore).
b. Input a meaningful description of the prospect source being created.
6. Account Management
Creating a Service Provider account in the below screens where Service Provider is one of
the top most entities in the organizational hierarchy. This is a onetime setup activity.
Creating a Joint Venture account in the below screens where Joint Venture is one of the
top most entities in the organizational hierarchy. This is a onetime setup activity.
Creating a Super Distributor account in the below screens where a Super Distributor is
placed either under a Service Provider / Joint Venture in the organizational hierarchy. This
is a usually a onetime setup activity for each super-distributor that needs to be supported.
Creating a Distributor account in the below screens where a Distributor is placed always
under a Super Distributor account in the organizational hierarchy. This is a usually a onetime
setup activity for each distributor (sub-distributor) that needs to be supported.
Creating an LCO account below where an LCO can be placed at different levels in the
organizational hierarchy, depending upon whether it is a primary point or a secondary point
LCO. Without an LCO existence, end customer cannot be registered in the system. This is a
usually a onetime setup activity for each LCO and is for primary point LCO in this section.
Creating an LCO account below where an LCO can be placed at different levels in the
organizational hierarchy, depending upon whether it is a primary point or a secondary point
LCO. Without an LCO existence, end customer cannot be registered in the system. This is a
usually a onetime setup activity for each LCO and is for secondary point LCO in this section.
Creating a Central Warehouse account below where it is be placed at the top level in the
organizational hierarchy (Similarly to a Service Provider / Joint Venture). This is a usually
a onetime setup activity for each Central Warehouse that is required in the system.
Creating a City Warehouse account below where it is be placed under a Regional Warehouse
account in the organizational hierarchy. This is a usually a onetime setup activity for each
City Warehouse that is required in the system.
Follow steps as were in case of a normal CSR user creation but make sure to
assign the roles specific to call center user. Example screenshot below:-
Follow steps as were in case of a normal CSR user creation but make sure to
assign the roles specific to field service engineer. Example screenshot below:-
Follow steps as were in case of a normal CSR user creation but make sure to
assign the roles specific to collection agent engineer. Example screenshot below:-
In this process, the CSR agent has to go through a series of steps to establish the authenticity
of his login profile and so he will have to reset his password, re-validate email address /
mobile numbers, validate a OTP M-Pass code and setup some security answers, so it is
essential to have his mobile no. correctly set while creating his profile in the first place.
After completing all security steps and profile validation, now CSR is able to login as below
This operations allows to extend / reduce the CSRs reachability in terms of his service access
at the geographical and organizational level. A CSR can also be allowed to work under multiple
LCOs under different states, if his ORG/GEO access are setup properly.
Below here, a CSR performs the on-screen registration of an end customer. After the
registration is complete, the system offers to proceed with activation inputs screen (covered
in a separate section of the document) and based on the situation, a CSR user can chose to
do it either immediately or at a later time, as required.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Open a registered customer profile and follow steps as shown in the screenshots below.
Below screenshots guide on the process where a CSR has to activate an end customer account
which has been registered previously but was not moved forward in activation process.
Below screenshot displays the profile of already such customer with 2 active connections.
Clicking on the new activation button proceeds to a screen to create additional connection.
Open existing end customer account and perform the below steps.
Open existing end customer account and perform the below steps.
The process is same as mentioned in the section STB swap when its identified as
faulty above. Follow same steps but against VC Device this time. For CISCO network
element based account activations, this functionality will not be applied.
1. The account has to be created through preactivation and shipped to LCO as per the
normal process.
2. Open the end customer account from OAP
3. Select the
Model from the dropdown as Corporate
choose the appropriate subscriber type
Account type as Parent.
Click on Save changes
Now to add a child to this hierarchy, add a child account which has been created through
preactivation. Open the end customer account from OAP
Select the
Model from the dropdown as Corporate
Choose the appropriate subscriber type
Account type as Child.
In Parent Account Number, enter the account number created in 4.3.3.14
Verify:
Go to Hierarchy Tab in Account Info. Screen and see if parent account can be seen or not.
Open existing end customer account and perform the below steps.
Open self-care portal main page as below and click on Login button under CATV.
Enter the login credentials as the end customer and click on Submit button.
Open end customer account from OAP for which Service Termination for Additional
TV is to be done.
Click on Termination
A pop up appears on screen asking if you want to Disassociate the device. Click Yes.
The Service Termination for Additional TV will be done successfully.
1. Open end customer account in OAP for which Main TV Service Termination to be done.
3. Click on Termination
4. A pop up appears on the screen asking if you want to Disassociate the device. Click Yes.
The Service Termination for Main TV will be done successfully.
Objective: The CSR should be able to view invoices of the end customer from OAP.
Pre-requisite: The billing and invoicing should be run for the end customer.
Go to Bills tab
In the count, enter the number of bills for which Invoices has to be seen.
Click on Search.
Open existing end customer account and perform the below steps.
Open existing end customer account and perform the below steps.
Open existing end customer account and input disposition parameters to create a WO.
Open existing end customer account and perform the below steps.
Below screenshot shows mapped VHD work order at the Super-Distributor level in his profile
Login as the service coordinator of the service team responsible to handle VHD work orders.
Login as the service coordinator of the service team responsible to handle VHD work orders.
Login as the service coordinator of the service team responsible to handle VHD work orders.
Login as the CSR ADMIN / with a role that has relevant permissions to extract this report.
6.3.5.1. Retrack
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do retrack
There are 2 ways of doing retrack
Enter the STB Device ID for which retrack has to be done and click Submit.
Click Retrack.
1. Order ID
2. Error Code
3. Error Description
4. Provisioning Action
5. Order Creation Date
6. Status
In above that the status is Inprogress. It is because the simulator has not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as RETRACK_PK
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do retrack
There are 2 ways of doing retrack
From CATV Provisioning Menu
Go to CATV Provisioning -> RETRACK -> CONAX
Enter the VC Device ID for which retrack has to be done and click Submit.
Click Retrack.
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as RETRACK_CONAX
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do retrack
Enter the VC Device ID for which retrack has to be done and click Submit.
Click Retrack.
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as RETRACK_PK
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Navigation Path
Go to CATV Provisioning -> SEND OSD -> CISCO
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do OSD
There are 1 way of doing OSD
From CATV Provisioning Menu
Enter the STB Device ID for which OSD, Title and Message has to be done and click Submit.
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Clear OSD
Click on Clear button on the display screen.
Navigation Path
Go to CATV Provisioning -> SEND OSD -> CONAX
Permissions
The end user must have the following Permissions to execute the functionality:
1. 40100000
2. 40200000
3. 40300000
4. 40400000
5. 4050000
6. 4060000
7. 40700000
8. 40800000
Execution Steps
How to do OSD
There are 1 way of doing OSD
From CATV Provisioning Menu
Go to CATV Provisioning -> SEND OSD -> CONAX
Enter the VC Device ID for which OSD, Duration in seconds and Message has to be done and
click Submit.
1. Order ID
2. Error Code
3. Error Description
4. Provisioning Action
5. Order Creation Date
6. Status
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Clear OSD
Click on Clear button on the display screen.
Navigation Path
Go to CATV Provisioning -> SEND OSD -> GOSPELL
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do OSD
There is 1 ways of doing OSD
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as SEND_OSD_GOSPELL
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Clear OSD
Click on Clear button on the display screen.
Navigation Path
Go to CATV Provisioning -> SEND EMAIL -> CISCO
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do Email
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Search the end customer account for which you wish to verify Email.
Go to Provision Tab
Select the search key as Provisioning Action and value as EMAIL_PK
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Clear Email
Click on Clear button on the display screen.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do Email
There is 1 way of doing Email
4. Provisioning Action
5. Order Creation Date
6. Status
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as EMAIL_CONAX
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Clear Email
Click on Clear button on the display screen.
Navigation Path
Go to CATV Provisioning -> SEND EMAIL -> GOSPELL
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do Email
There is 1 way of doing Email
From CATV Provisioning Menu
Go to CATV Provisioning -> SEND Email -> GOSPELL
In below we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab
Select the search key as Provisioning Action and value as EMAIL_CONAX
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Clear Email
Click on Clear button on the display screen.
6.3.5.4. FingerPrinting
Navigation Path
Go to CATV Provisioning -> Finger Printing -> CISCO
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Execution Steps
How to do one channel One STB FP
Enter the STB Device ID, Add package CAID and Delete Package CAID
Add package CAID : The channel ID to be added if any.
Delete package CAID : The channel ID to be deleted if any.
Note : One among add package or delete package caid should be selected.
In below we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_SINGLE_CHANNEL_PK
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Go to CATV Provisioning -> Finger Printing -> CISCO -> All Channel One STB
Enter the STB Device ID, Add package CAID and Delete Package CAID
Add package CAID : The channel ID to be added if any.
Delete package CAID : The channel ID to be deleted if any.
Note : One among add package or delete package caid should be selected.
(a)Order ID
(b)Error Code
(c)Error Description
(d)Provisioning Action
(e)Order Creation Date
(f)Status
In below we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_ALL_CHANNELS_SINGLE_STB_PK
You can see all provisioning actions for the account here.
Click Display.
The provisioning order display comes on the screen.
Go to CATV Provisioning -> Finger Printing -> CISCO -> One Channel All STB
Enter the STB Device ID, Add package CAID and Delete Package CAID
Add package CAID : The channel ID to be added if any.
In above we see the status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_SINGLE_CHANNEL_ALL_STBS_PK
You can see all provisioning actions for the account here.
Click Display.
Go to CATV Provisioning -> Finger Printing -> CISCO -> All Channel All STB
Enter the Segment Name and click Submit
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_ALL_CHANNEL_ALL_STBS_PK
You can see all provisioning actions for the account here.
Click Display.
Execution Steps
How to do FP CONAX
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Search the end customer account for which you wish to verify FP.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_CONAX
You can see all provisioning actions for the account here.
Click Display.
How to do FP GOSPELL
There is 1 way of doing Fingerprinting
From CATV Provisioning Menu
Go to CATV Provisioning -> Finger Printing -> GOSPELL
Enter the following details and click Submit.
o VC_ID : VC device id
o Foreground Color
o Background Color
o XCoordinate : in pixels
o YCoordinate : in pixels
o Font Size : Size of Font to be displayed on screen.
o Duration : Time interval between each display in seconds
o Frequency : Time interval between each display in seconds
o Show Time : Frequency in seconds to display
o NumTime : Number of times to display
o CAID Select the CA ID.
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
FINGERPRINTING_GOSPELL
You can see all provisioning actions for the account here.
Click Display.
6.3.5.5. Blacklisting
6.3.5.5.1.1. STB
Navigation Path
Go to CATV Provisioning ->Blacklisting -> CISCO -> STB
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Objective
This functionality can be used by the users to blacklist STB devices.
Execution Steps
Click STB.
Enter the STB device id which has to be blacklisted.
Note: To blacklist device, please make sure that the device is not in allocated state. If it is
in allocated state then please SWAP the device first.
Click on Submit.
A new action Blacklist will be there with Description as State Changed from 1 to 7
which means that Blacklisting of device was successful.
6.3.5.5.2.1. STB
Navigation Path
Go to CATV Provisioning ->Blacklisting -> CISCO -> STB
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Objective
This functionality can be used by the users to blacklist STB devices.
Execution Steps
Click STB.
Enter the STB device id which has to be blacklisted.
Note: To blacklist device, please make sure that the device is not in allocated state. If it is
in allocated state then please SWAP the device first.
Click on Submit.
A new action Blacklist will be there with Description as State Changed from 1 to 7
which means that Blacklisting of device was successful.
6.3.5.5.2.2. VC
Navigation Path
Go to Inventory Mgmt. ->Device Blacklisting -> VC
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 40100000
(b) 40200000
(c) 40300000
(d) 40400000
(e) 4050000
(f) 4060000
(g) 40700000
(h) 40800000
Objective
This functionality can be used by the users to blacklist VC devices.
Execution Steps
Click VC.
Enter the VC device id which has to be blacklisted.
Note: To blacklist device, please make sure that the device is not in allocated state. If it is
in allocated state then please SWAP the device first.
Click on Submit.
A new action Blacklist will be there with Description as State Changed from 1 to 7
which mean that Blacklisting of device was successful.
Execution Steps
How to do RESET PIN CISCO
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
RESET_PIN_PK
You can see all provisioning actions for the account here.
Click Display.
Execution Steps
How to do RESET PIN GOSPELL
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
RESET_PIN_GOSPELL
You can see all provisioning actions for the account here.
Click Display.
6.3.5.5.4.1. CONEX
Execution Steps
How to do SET PIN CONAX
(d)Provisioning Action
(e)Order Creation Date
(f)Status
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Display
The below screen is comes up when you select the Action as Display.
Go to Provision Tab Select the search key as Provisioning Action and value as
RESET_PIN_CONAX
You can see all provisioning actions for the account here.
Click Display.
(a)Order ID
(b)Error Code
(c)Error Description
(d)Provisioning Action
(e)Order Creation Date
(f)Status
In above we see that status is Inprogress. It is because the simulator is not run on BRM.
Search the provisioning status by Provisioning Action
Select the key as PROVISIONING ACTION
Display
The below screen comes up when you select the Action as Display.
7. Bulk Management
Navigation Path
Permission
The end user must have the following Permissions to execute the functionality:
(a) 60000000
(b) 60100000
Objective
This functionality can be used by the end user to search for an inventory and locate details
about the inventory.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60000000
(b) 60700000
Objective:
This functionality can be used by the end user to search for an inventory and locate lifecycle
details about the inventory.
The inventory device lifecycle search can be done by providing the following options:
STB Serial No
VC Serial No
Account No
Action
Creation Date
MAC ID
IP Address
Remote Serial No
Adapter Serial No
If you want to search the lifecycle for an STB device, select the search type as STB Serial No
and in Search value provide the STB Serial No and click on Search
Navigation Path
Go to Inventory Mgmt. ->Loading -> STB Loading
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60200000
(b) 60201000
Objective
This functionality can be used by the users to load devices.
Execution Steps
Click STB Loading.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
Supplier code The code of supplier for which loading is done.
Invoice no the invoice number against which loading is done
purchase order The order number of the purchase
order date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSES
Part 2:
Device Code Can be Harcoded as STB,VC,Remote or Adapter
Serial No Device Serial Number for loading
Warranty Period This can be given in months
Device Id Device ID for loading
NetworkNode - Manufacturer
Model Model no of the box
Type This is colon separated. First field is type of device like HD, SD, followed by
Plan name.
Category Can be NEW, REPAIRED, FAULTY, SCRAP.
CardRequired This can be either 0 or 1
Recordable - This can be either 0 or 1
Description Brief description can be given
Note: Part 2 can have multiple rows depending upon the number of devices to be loaded.
STB_DEVICE (2).csv
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
In the Task List, Select All.
Description and Status shows weather the job was executed succesfully or failed.
Purchase Order is Empty When purchase order number is not provided for loading
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60200000
(b) 60202000
Objective
This functionality can be used by the users to load VC devices.
Execution Steps
Click VC Loading.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
purchase_order The order number of the purchase
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSES
Part 2:
Device Code Can be Harcoded as STB,VC,Remote or Adapter
Serial No Device Serial Number for loading
Warranty Period This can be given in months
Device Id Device ID for loading
NetworkNode - Manufacturer
Model Model no of the box
Type This is colon separated. First field is type of device like HD, SD, followed
by Plan name.
Category Can be NEW, REPAIRED, FAULTY, SCRAP.
CardRequired This can be either 0 or 1
Recordable - This can be either 0 or 1
Description Brief description can be given
Note: Part 2 can have multiple rows depending upon the number of devices to be loaded.
VC_DEVICE.csv
Description and Status shows weather the job was executed succesfully or failed.
Navigation Path
Go to Inventory Mgmt. ->State Change -> STB Device State Change
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60400000
(b) 60401000
Objective
This functionality can be used by the users to change state of devices.
Execution Steps
Click Download Template. Please fill the details of the csv file as below:
All the fields in CSV are mandatory.
Device_id: The STB device id for which state change has to be done.
State_id: The state id to which the STB Device has to be changed.
STB_DEVICE_STATE
_CHANGE (2).csv
Navigate to Inventory Mgmt. ->State Change -> STB Device State Change
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
In the Task List, Select All.
Description and Status shows weather the job was executed succesfully or failed.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Device_id not found When user entered a wrong device ID.
Navigation Path
Go to Inventory Mgmt. ->State Change -> VC Device State Change
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60400000
(b) 60402000
Objective
This functionality can be used by the users to change state of devices.
Execution Steps
Click Download Template. Please fill the details of the csv file as below:
All the fields in CSV are mandatory.
Device_id: The VC device id for which state change has to be done.
State_id: The state id to which the VC Device has to be changed.
VC_DEVICE_STATE_
CHANGE.csv
Navigate to Inventory Mgmt. ->State Change -> STB Device State Change
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
Description and Status shows weather the job was executed succesfully or failed.
1. The CSV File format should not be changed - This error comes on screen when the CSV
file is tampered and fields in CSV are missing.
2. The CSV file is empty When no data is entered in CSV file.
3. Device_id not found When user entered a wrong device ID.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700001
(b) 40500001
Objective
This functionality can be used by the users to blacklist STB devices.
Execution Steps
Click STB.
Note: To blacklist device, please make sure that the device is not in allocated state. If it is
in allocated state then please SWAP the device first.
Click on Submit.
A new action Blacklist will be there with Description as State Changed from 1 to 7
which means that Blacklisting of device was successful.
7.1.5.2. VC Device
Navigation Path
Go to Inventory Mgmt. ->Device Blacklisting -> VC
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700001
(b) 40500000
Objective
Execution Steps
Click VC.
Enter the VC device id which has to be blacklisted.
Note: To blacklist device, please make sure that the device is not in allocated state. If it is
in allocated state then please SWAP the device first.
Click on Submit.
A new action Blacklist will be there with Description as State Changed from 1 to 7
which mean that Blacklisting of device was successful.
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700002
(b) 60700003
Objective
This functionality is used to transfer stock from one warehouse to another.
Execution Steps
Click STB Device.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
purchase_order The order number of the purchase
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSES
Part 2:
Serial No STB Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
To warehouse who received the box
Category - Can be NEW/REPAIRED only
Transfer Flag This can be between 100 to 108.
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows depending upon the no. of devices to be transferred.
STB_DEVICE_STOCK
_TRANSFER_CWRW.csv
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
In the Task List, Select All.
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
7.1.6.2. VC Device
Navigation Path
Go to Inventory Mgmt. ->Stock Transfer -> VC Device
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700002
(b) 60700004
Objective
This functionality is used to transfer stock from one warehouse to another.
Execution Steps
Click VC Device.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
purchase_order The order number of the purchase
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSES
Part 2:
Serial No VC Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows based on the number of devices to be transferred.
VC_DEVICE_STOCK_
TRANSFER_CWRW.csv
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
In the Task List, Select All.
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Warehouse/LCO Account mismatch in SHIP_FROM When the FROM in CSV file is
not in sync with the transfer flag in the CSV.
SHIP_TO account not found When the TO account in CSV file not found in BRM.
Category can be NEW or REPAIRED only When the category in CSV is entered
something other than NEW or REPAIRED.
Navigation Path
Go to Inventory Mgmt. ->New Stock Issue to LCO-> STB Device
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700005
(b) 60700006
Objective
This functionality is used to transfer stock new stock issue to LCO.
Execution Steps
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no .
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSESE
Part 2:
Serial No STB Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
To warehouse who received the box
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows based on the number of devices to be transferred.
STB_DEVICE_STOCK
_ISSUE.csv
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Warehouse/LCO Account mismatch in SHIP_FROM When the FROM in CSV file is
not in sync with the transfer flag in the CSV.
SHIP_TO account not found When the TO account in CSV file not found in BRM.
Category can be NEW or REPAIRED only When the category in CSV is entered
something other than NEW or REPAIRED.
7.1.7.2. VC Device
Navigation Path
Go to Inventory Mgmt. ->New Stock Issue to LCO-> VC Device
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700002
(b) 60700007
Objective
This functionality is used to transfer stock new stock issue to LCO.
Execution Steps
Click VC Device.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSESE
Part 2:
Serial No STB Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
To warehouse who received the box
Category - Can be NEW/REPAIRED only
Transfer Flag This can be between 200 to 202.
Transfer Flag 200 : RGH to LCO
201 : CWH to LCO
202 : CIH to LCO
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows based on number of devices to be transferred.
In the search box give the date range when the job was run in BRM.
In the Order List, select the Order Number
In the Task List, Select All.
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Warehouse/LCO Account mismatch in SHIP_FROM When the FROM in CSV file is
not in sync with the transfer flag in the CSV.
SHIP_TO account not found When the TO account in CSV file not found in BRM.
Category can be NEW or REPAIRED only When the category in CSV is entered
something other than NEW or REPAIRED.
Navigation Path
Go to Inventory Mgmt. ->GRN FROM LCO-> STB Device
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700008
(b) 60700009
Objective
Execution Steps
Click STB Device.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSESE
Part 2:
Serial No STB Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
To warehouse who received the box
Category - Can be NEW/REPAIRED only
Transfer Flag This can be between 300 to 302.
Transfer Flag 300 : LCO to RGH
301 : LCO to CNW
302 : LCO to CIW
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows based on the number of devices to be transferred.
STB_DEVICE_GRN.cs
v
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Warehouse/LCO Account mismatch in SHIP_FROM When the FROM in CSV file is
not in sync with the transfer flag in the CSV.
SHIP_TO account not found When the TO account in CSV file not found in BRM.
Category can be NEW or REPAIRED only When the category in CSV is entered
something other than NEW or REPAIRED.
7.1.8.2. VC Device
Navigation Path
Go to Inventory Mgmt. ->GRN FROM LCO-> VC Device
Permissions
The end user must have the following Permissions to execute the functionality:
(a) 60700008
(b) 60700010
Objective
This functionality is used to return goods from LCO.
Execution Steps
Click VC Device.
Part 1:
Header - Short Description of the type of device for which loading is to be done.
Stock point code The WAREHOUSE account no.
supplier_code The code of supplier for which loading is done.
Invoice_no the invoice number against which loading is done
order_date date of loading
Note: OAP is validating the account type of stock point code. Necessary changes to be
done to support new WAREHOUSESE
Part 2:
Serial No STB Device Serial Number for stock transfer
From The warehouse account number from where stock transfer is initiated
To warehouse who received the box
Category - Can be NEW/REPAIRED only
Transfer Flag This can be between 300 to 302.
Where
RGH - Regional Warehouse
CNW - Central Warehouse
CIW - City warehouse
Note: Part 2 can have multiple rows based on the number of devices to be transferred.
VC_DEVICE_GRN.csv
Description and Status shows weather the job was executed succesfully or failed.
51049: Error in searching Stock point code This error comes on screen when the
warehouse account number is not correct.
The CSV File format should not be changed - This error comes on screen when the
CSV file is tampered and fields in CSV are missing.
The CSV file is empty When no data is entered in CSV file.
Warehouse/LCO Account mismatch in SHIP_FROM When the FROM in CSV file is not
in sync with the transfer flag in the CSV.
SHIP_TO account not found When the TO account in CSV file not found in BRM.
Category can be NEW or REPAIRED only When the category in CSV is entered
something other than NEW or REPAIRED.
This is one of the most important functionalities offered by the system and it allows the CSR
or CSR-ADMIN account type of users to register and activate end subscribers through a
lightweight and simple process where as a minimum very few inputs are to be passed in a
CSV file and a bulk number of end customer accounts can be registered and activated in one
go. Please follow steps as provided below in the screenshots provided. A sample CSV file
contents are being shown to give a fair idea of inputs required to execute this use case.
With below format, browse to the CSV file that needs to be uploaded to process inputs.
1. STB_NUMBER STB Device Identifier that will be associated with registered account.
2. VC_NUMBER VC Device Identifier that will be associated with registered account.
3. ENTITY_CODE Account No (User Id) of concerned LCO business unit for customer.
4. SUBSRIBER_TYPE Account type (constant value = 99 for end customer)
5. PAY_TYPE Prepaid / Postpaid type of the customer account being created.
6. SUBSCRIPTION_PACK - Subscription pack to be associated for activation.
7. FIRST_NAME First name of the customer.
8. LAST_NAME Last name of the customer.
9. RMN Valid mobile number of the end customer being registered.
10. RMAIL Valid email address of the end customer being registered.
11. DOOR_NO Door number of the customer billing address that will be registered.
12. AREA_CODE Area code as per customers Billing address (Pre-configured value).
13. BUILDING_ID Building Id as per customers Billing address (Pre-configured value).
Search using search options in the below part of the screen to confirm order is submitted
Below are the parameters used in the CSV template to use various modes of bulk payments
1. Account No Account number of the end customer.
2. Service Type A numeric constant represents CATV service.
3. Mode of payment Cash / Cheque / Online payment (numeric constants).
4. Amount Amount posted on behalf of individual customer (must be valid amount).
5. Receipt No/Wired Transfer ID To be supplied as per the payment mode.
6. From Date(MM/DD/YYYY) Start date covered by the payment made
7. To Date(MM/DD/YYYY) End date covered by the payment made
8. MICR Code MICR code
9. Bank Account No Bank account number for cheque/online payments
10. Bank Name Bank name for cheque/online payments
11. Branch Name Bank Branch name for cheque/online payments
12. Cheque No Cheque number for cheque payments
13. Cheque Date/Effective Date(MM/DD/YYYY) Effective date for cheque payments.
14. Gateway Payment Gateway used for online payment mode
15. DESCR A bit description of the payment transaction being posted.
Easiest way is to search using bulk functionality type & applicable date-range.
8. Others
After clicking on Assigned button, below screen appear for the highlighted row.
Login as a CSR (Responsible for customer registration) and perform steps as below.
9. Reports
http://103.41.23.141:9001/console/
Username: weblogic
Password: weblogic1
3. Click on myrealm
5. Click on new and it will open the user creation part. Provide the user details which
you want to create. And click OK
6. After creating the user all users will appear as shown below.
acle_ias_farm%26_afrWindowMode%3D0%26_afrLoop%3D1891462731095980%26_adf.ctr
l-state%3Dt2628g51l_4
Username: weblogic
Password : weblogic1
And click on bifoundation_domain
Right click on bifoundation_domain and click on security and select application roles as
shown below.
Please find the attached file for BRM user creation process
5. Open report catalog and then open permission to assign roles to get report access.
Step 2: go to Fastway_Reports
Provide the filter values as shown below and click on apply to view the
report
Filter Clarification:
1. MSO: This filter shows the list of mso accounts.
2. DT: This filter shows the list of distributor account
3. LCO: This filter shows the list of LCO accounts.
4. Network Node: This filter shows the list of network nodes
5. Phase: This filter shows the list of Phase types.
6. Package: This filter show the list of packages.
If you want to see report data for other reports, click on catalog
Filter Clarification:
MSO: This filter shows the list of MSO accounts.
Phase: This list shows the different phases.
Expire Date: select the date (this date is for LCO agreement date which is getting expired
before the selected date)
Click on apply.
Click on open
Filter clarification:
Click on open
Filter clarification:
Click on Open
Filter Clarification:
Click Open
Filter Clarification:
Click on Open
Filter Clarification:
Click Open
Filter Clarification:
Click on open
Filter Clarification:
WAREHOUSE: This shows the list of warehouses
Entity: This filter shows the list of LCO accounts.
Start_Date and END_DATE: select the date range to know the transaction happened
between these dates.
Click open
Filter Clarification:
WAREHOUSE: This shows the list of warehouses
Entity: This filter shows the list of LCO accounts.
Start_Date and END_DATE: select the date range to know the transaction happened
between these dates.
Provide the filter data and click apply.
Click open
Filter Clarification:
WAREHOUSE: This shows the list of warehouses
Start_Date and END_DATE: select the date range to know what the transactions are
happened between these dates.
Filter Clarification:
WAREHOUSE: This shows the list of warehouses
Start_Date and END_DATE: select the date range to know what are the transactions
happened between these dates.
Click open
Here we can download reports in HTML, PDF, RTF, Excel, PowerPoint formats.
For example click on PDF it will open the report as shown below. There you will get
download option to download the report.