https://oraclebrmonlinetraining.blogspot.com/2015/06/oracle-brm-interview-questions-answers.html
Q. What are the supported ways of
Payment processing in BRM?
Answer:
There two types of payment methods in BRM:
i). BRM Initiated Payments –
BRM-initiated payment processing is triggered by BRM and requires no action
from customers. Payments processed in this way are those for which a customer
is automatically charged, such as credit card and direct debit payments.
The
following BRM-initiated payment methods are supported:
- Credit
card
- Debit
card (that don’t need pin)
- Direct
debit
ii). Externally Initiated Payments –
Payment Tool or a third-party payment application method is used to collect
externally initiated payments and post them in BRM.
The
following externally initiated payment methods are supported in BRM:
- Cash
- Check
- Inter-bank
transfer
- Postal
order
- Wire
transfer
- Voucher
Q. What is UEL? Where is it used?
Answer:
UEL or Universal Event Loader is used to rate and load the events of any
format. Using UE Mapper we can create the mapping template to call the rating
opcode and with the UE loader the events can be rated and loaded to the BRM
database.
Q. What is REL?
Answer:
REL or Rated Event Loader loaded the events rated by the batch rating engine in
BRM. It used SQLLDR to load the events to different BRM tables.
Q. What are the differences in UEL and
REL?
Answer:
i). UEL can rate the events while REL
cannot
ii). UEL calls the BRM opcodes to rate and
load the events, while REL uses sql utility to just load the rated events to
BRM DB
iii). UEL can rate and load CDRs of any
format while REL can load the rated CDRs in SOL42 format.
Q). How to retrieve an optional field
from an input flist to make sure the code won’t break if the field is not
present in the input flist?
Answer:
To set or not set the error condition while retrieving a field from an input
flist if the field is not present in the input flist is controlled by the
“optional” flag.
If
the “optional” flag is set to a non-zero value while retrieving the field from
the input flist, the error condition is not set if the field is not present in
the flist meaning that the value would be considered optional.
If
the flag is not set, the error condition would be set if field is not present
in the input flist meaning that the value would be considered to be mandatory.
Q). What are the main fields of the item
table or /item storable class?
Answer
:
Item objects represent A/R in Infranet. Any impact to an account’s A/R is
stored and tracked in an /item object. This includes not only fees and usage
charges, but also payments, adjustments, disputes and refunds. Events always
belong to one or more /item objects. The impact from any event can be traced to
the /item tracking that A/R. Some /item objects belong to a /bill object (cycle
fees, usage, etc), while others are direct A/R and do not belong to any bill
(payments, refunds, etc). The main/important fields of /item objects
arePIN_FLD_ACCOUNT_OBJ, PIN_FLD_BAL_GRP_OBJ, PIN_FLD_BILLINFO_OBJ and
PIN_FLD_STATUS. (PIN_FLD_STATUS – Status of this item. Values are PENDING
(unbilled), OPEN (billed) and CLOSED (zero due)).
Some
most important field to be notices in the /item objects are:
DUE,
RECEIVED, ADJUSTED, TRANSFERRED,WRITE OFF,DISPUTED, TOTAL