Thus, service parameters are very useful in normalizing a product catalogue, like in the above example, instead of having 3 products , “Missed Call Alert on No Response”, “Missed Call Alert on Switched off’ etc. , product catalogue can have just one product. 2 Types of Service Parameters Service Parameters can be of 2 types, Free Flow text where the value of the parameter can be anything. An example of this kind of parameters is surname, password etc. Listed Value, where the value of the parameter has to be one from a predefined list.
An example may be the Quota of a Data service having values like KGB, KGB,1 GOB etc Both Siebel CRM and BPCS support these two types. However, in BPCS, one more type is supported which is called the Default parameters, I. E. Parameters which have default values and can not be changed from outside. 3 CRM Products Definition CRM creates products with parameters. For the ‘Listed parameters, it also creates the list with proper values as per the product definition. After they products are configured properly they are released for sale. CARS can selects these products and attach in an order.
For the products with parameters, CARS either enters a value (Free Flow) or selects one value from the drop-down list (Listed Value) for each of the parameters. 4 BPCS Products Definition BPCS, too, creates the products but creates the parameters separately and then attach any number of parameters with any number of products. For the Default Parameters, the values created and specified. For the Listed Value Parameters, the lists are created, one list for one parameter like CRM. Here they can also create mapping between BPCS values and the values reek to be passed to the Provisioning system.
For the “Free Flow” parameters, it does not create or attach any value. 5 Integration To integrate Siebel and BPCS, so that ordering such products from Siebel CRM is seamlessly provisioned in BPCS, following steps are required, l. Both the systems, Siebel CRM and BPCS, should configure the products similarly I. E. Having the same number of parameters. Only exception is that Siebel should not configure the default parameters II. It is then, required to create the following mapping data, a. Mapping of CRM product id and BPCS shorted of the products b.
Indicators for the products having default parameters – this an be maintained in the above Mapping table c. Mapping of the parameter names of CRM and BPCS parameter see. This mapping can be maintained along with CRM product id so that CRM can also have the flexibility of having same names of the parameters across products. Otherwise, CRM should pose a restriction in naming different parameters with the same string value. This mapping data should also include an indicator for the type, I. E. If “Free Flow” or “Listed Value” d. For the Listed Value parameters, another mapping is needed between the CRM value and BPCS value.
Here also, we should have he mapping for CRM parameter name-parameter value vs. BPCS see for the corresponding values. So, we would need the above mappings….. Phew! Tears quite a lot for a small thing like this well, not sure why BPCS API works with BPCS sequences only, some changes in the BPCS API inputs can drastically improve the integration mechanism(not only in this use case but for other use cases too). These mappings can be maintained in CRM or in the middleware depending on the design followed in the corresponding project. Ill. Orchestration When an order payload comes from CRM, it is to be checked for Order Line