3 About Opcode Workflows

Learn about Oracle Communications Billing and Revenue Management opcode workflow concepts. For a list of opcodes with descriptions, see "Opcode Descriptions".

Caution:

• Always use the BRM API to manipulate data. Changing data in the database without using the API can corrupt the data.

• Do not use SQL commands to change data in the database. Always use the API.

An opcode workflow describes the opcodes that perform BRM operations (for example, creating accounts, purchasing bundles, and running billing). Therefore, in this document, workflow descriptions are organized not according to opcodes, but instead, according to types of BRM operations, such as billing and customer management.

An opcode workflow can describe:

• The main opcode that performs the operation. For example, PCM_OP_CUST_COMMIT_CUSTOMER is the main opcode for creating accounts.

• Additional opcodes that are called during the opcode flow. For example, before creating an account, PCM_OP_CUST_COMMIT_CUSTOMER calls PCM_OP_CUST_POL_PRE_COMMIT to enable customization.

• The actions the opcode performs (for example, retrieve data, change data, or delete data).

• When an opcode is called (for example, by another opcode).

• Important fields in input and output flist that can be used.

• Customizations that can be performed by using the opcodes.

• Conditions that cause an opcode to fail.

Use opcode workflows for the following purposes:

• To find out which opcodes to use when customizing BRM.

• To learn how BRM works.

• To troubleshoot BRM by tracking the progress of operations. For example, you can determine which opcode is failing if you know what the sequence of opcode calls is.