Oracle,BRM,and,Custom,Fields,P computer Oracle BRM and Custom Fields - Part 1
----------------------------------------------------------Permission is granted for the below article to forward,reprint, distribute, use for ezine, newsletter, website,offer as free bonus or part of a product for sale as longas no changes a Gone are those times when the companies and the organisations didn't need a hi-tech system to handle them. Owing to the considerable increase in the business sector and thus, an enormous increase in the complexity of the organisational struc
OracleCommunications Billing and Revenue Management (Oracle BRM \ formally known asPortal Infranet) provides two ways for creating, editing, and deleting customfields and storable classes. One way is by using Storable Class Editor, part ofthe Developer Center application, or the alternative approach, by using SDKopcodes. Personally, I prefer the latter choice and in this post I will covermanipulating custom fields with SDK opcodes. Before webegin, there is one change we need to apply first. It is necessary to make thedata dictionary writable. Here's how it's done: 1. Open theOracle DM or Microsoft SQL Server DM configuration file (BRM_HOME/sys/dm_oracle/pin.conf or BRM_HOME/sys/dm_odbc/pin.conf) in a texteditor.2. Enable fieldmanipulation in the data dictionary by setting the following entry to 1: - dmdd_write_enable_fields 1 Our objectivesare as follows: 1. Create a custom field 2. Edit the custom field description 3. Delete the custom field from the database 4. Make the custom fields available to BRM Create a NewCustom Field Creating a newcustom field and committing it to the database can be done with SDK opcodes orwith a pin_deploy utility. As developers, SDK opcodes provide a more flexibleway to create, edit, delete custom fields at the development stage. Thepin_deployutility, on theother hand, uses PODL (Portal Object Definition Language) to export and importfield and storable class definitions, which is more useful at theadministrative level because we can streamline the process by putting fielddefinitions into source code management and therevy reduce the possibility ofdamaging the Oracle BRM production database data dictionary. We can use thefollowing SDK opcodes to manage field specifications:1.PCM_OP_SDK_SET_FLD_SPECS - create or modify a field,2.PCM_OP_SDK_GET_FLD_SPECS - retrieve a field specs,3.PCM_OP_SDK_DEL_FLD_SPECS - delete a field. To create afield, I need to write an input flist for PCM_OP_SDK_SET_FLD_SPECS opcode:0PIN_FLD_POID POID [0] 0.0.0.1 /dd/fields 0 00PIN_FLD_FIELD ARRAY [0]1 PIN_FLD_DESCR STR [0] "custom field forholding a VAT number"1 PIN_FLD_FIELD_NAME STR [0] "C_FLD_VAT_NUMBER"1 PIN_FLD_FIELD_NUM ENUM [0] 100001 PIN_FLD_FIELD_TYPE INT [0] 5 Let's verifythe field we created exists in the database data dictionary by feeding thefollowing input flist to PCM_OP_SDK_GET_FLD_SPECS opcode:0PIN_FLD_POID POID [0] 0.0.0.1 /dd/objects 0 00PIN_FLD_FIELD ARRAY [0]1 PIN_FLD_FIELD_NAME STR [0] "C_FLD_VAT_NUMBER" Editing theCustom Field Description Now that wehave confirmed that the new custom field exists, we can change thedescription,by calling PCM_OP_SDK_SET_FLD_SPECS opcode with the following inputflist:0PIN_FLD_POID POID [0] 0.0.0.1 /dd/fields 0 00PIN_FLD_FIELD ARRAY [0]1 PIN_FLD_DESCR STR [0] "custom field -VAT number"1 PIN_FLD_FIELD_NAME STR [0] "C_FLD_VAT_NUMBER"1 PIN_FLD_FIELD_NUM ENUM [0] 100001 PIN_FLD_FIELD_TYPE INT [0] 5 Again, we canretrieve the field's specifications to verify the change has been made. To get know howto delete and make the custom fields, please read part 2: Oracle BRM andCustom Fields- Part 2".
Oracle,BRM,and,Custom,Fields,P