Some BRM questions from Tech Mahindra, Bangalore interview
In account hierarchy, what are paying (non-subordinate) and non-paying (subordinate) account?
32). How will you identify if the account type is paying or non-paying from the /billinfo object?
33). If there are 3 accounts namely A1,A2 and A3 where :
a). A1 is the parent account of A2 and A3
b). A2 is non-paying child
c). A3 is paying child
During the bill generation, what behaviour is expected in BRM for these account. Will the bill be generated for all the 3 accounts?
34). What is custom event analysis in realtime GPRS? For what it is used for?
35). What is RUM and how is it used?36). If suppose we need to calculate RUM with a complex calclulation like sine,cos or by using some other formula, will it be supported by BRM?
Answer: There is not out of box configuration to change the way RUMs are calculated but it can be customized by changing the policy opcode PCM_OP_ACT_POL_SPEC_CANDIDATE_RUMS.
37). How do you implement the following scenario :
“If the rated amount for an event is less than or equal to 0.001,then reject the event else store the events.”
What all opcodes will be modified to implement this and what are the modifications need to be done?
Answer : For implementing the above scenario in a realtime scenario, we have to customize the PCM_OP_RATE_POL_POST_RATING opcode to implement the above functionality. For implementing the above scenatio for delayed events, an iScript should be written which will rate and discard the above CDR or discard without rating as per requirement.
38). What are pre-rated events?
Answer : GLIDs can be assigned to prerated or partially rated events using the PCM_OP_ACT_POL_SPEC_GLID policy opcode. By default, this policy opcode retrieves an event’s G/L ID from the /config/map_glid storable object, but you can customize it to perform searches on other objects and look at other fields.
For example, you can categorize adjustments by customizing the policy opcode to assign G/L IDs based on the adjustment type.
40). How will you assign GLID to non-rated events?
32). How will you identify if the account type is paying or non-paying from the /billinfo object?
33). If there are 3 accounts namely A1,A2 and A3 where :
a). A1 is the parent account of A2 and A3
b). A2 is non-paying child
c). A3 is paying child
During the bill generation, what behaviour is expected in BRM for these account. Will the bill be generated for all the 3 accounts?
34). What is custom event analysis in realtime GPRS? For what it is used for?
35). What is RUM and how is it used?36). If suppose we need to calculate RUM with a complex calclulation like sine,cos or by using some other formula, will it be supported by BRM?
Answer: There is not out of box configuration to change the way RUMs are calculated but it can be customized by changing the policy opcode PCM_OP_ACT_POL_SPEC_CANDIDATE_RUMS.
37). How do you implement the following scenario :
“If the rated amount for an event is less than or equal to 0.001,then reject the event else store the events.”
What all opcodes will be modified to implement this and what are the modifications need to be done?
Answer : For implementing the above scenario in a realtime scenario, we have to customize the PCM_OP_RATE_POL_POST_RATING opcode to implement the above functionality. For implementing the above scenatio for delayed events, an iScript should be written which will rate and discard the above CDR or discard without rating as per requirement.
38). What are pre-rated events?
Answer : Prerated events are events for which charges are assigned by a policy opcode or through the reason codes file. These prerated events are not processed by the rates defined in your price list.
39). How will you assign GLID to pre-rated events?Answer : GLIDs can be assigned to prerated or partially rated events using the PCM_OP_ACT_POL_SPEC_GLID policy opcode. By default, this policy opcode retrieves an event’s G/L ID from the /config/map_glid storable object, but you can customize it to perform searches on other objects and look at other fields.
For example, you can categorize adjustments by customizing the policy opcode to assign G/L IDs based on the adjustment type.
40). How will you assign GLID to non-rated events?
0 Comments
Post a Comment