CN102663614B - Customer relation management is to the collocation method of service release and system - Google Patents

Abstract

The present invention relates to a kind of customer relation management to the collocation method of service release and system.Customer relation management comprises to the collocation method of service release: the class reading excel, obtains deploy content relevant to business in excel; DataBase combining string is obtained by reading configuration file; Connection data storehouse, inquires about the data needed; Splicing structure query language SQL statement, is sorted to output by C++ container.Customer relation management of the present invention, to the collocation method of service release and system, decreases CRM to the workload in the configuration of service release, has saved setup time, improve allocative efficiency.Further, customer relation management of the present invention, to the collocation method of service release and system, is of value to quick opening, can not causes the conflict of database.

Description

Customer relation management is to the collocation method of service release and system

Technical field

The present invention relates to computer realm, particularly relate to a kind of customer relation management to the collocation method of service release and system.

Background technology

The interface of CRM (Customer Relationship Management, customer relation management) and service release belongs to a part for whole Complex interface, is CRM service handling, to an intermediate link of service release after business processing.Each functional module of CRM is responsible for generating business transaction and is changed data, and interface, according to the demand of service release end, is extracted by configuration and needs to the synchronous data of the other side's platform, and receive the return message of the other side's platform from business transaction data.

The data layout that service release end requires is XML (Extensible Markup Language, extend markup language) message, wherein comprises order relevant information; Agent Service and action and correlation parameter; Additional Services and action and correlation parameter.

At present, CRM is undertaken to the configuration effort of service release by manual, and this configuration mode workload is large, and the serious waste time, allocative efficiency is very low.

Summary of the invention

Technical matters to be solved by this invention is to provide a kind of customer relation management to the collocation method of service release and system, saves setup time, improves allocative efficiency.

For solving the problems of the technologies described above, the present invention proposes the collocation method of a kind of customer relation management to service release, comprising:

Read the class of excel, obtain deploy content relevant to business in excel;

DataBase combining string is obtained by reading configuration file;

Connection data storehouse, inquires about the data needed;

Splicing structure query language SQL statement, is sorted to output by C++ container.

Further, said method also can have following characteristics, also comprises:

Calling interface function is triggered according to order;

In the transmission service release process of form ordering system, the capable trigger table of order is monitored in scanning, obtaining the capable state of order is that to serve order to be opened capable, calls service release and sends function to carry out message assembled, and assembled good message data is charged to service release interface table;

Complex interface application integration platform obtains message data from described service release interface table and sends to service release;

Result is also fed back to manageming contacts CRM by service release process message data, and detached process scans the other side's interface table, data is passed to order relevant interface table;

The data of order relevant interface table described in form ordering system process, continue circulation order.

Further, said method also can have following characteristics, and described order relevant interface table comprises successfully feedback form and failed feedback form.

Further, said method also can have following characteristics, also comprises: the service action needed for configure base allocation list, attribute and attribute value mode information are filled in GetSql.xls file.

Further, said method also can have following characteristics, also comprises:

Form ordering system calls the external interface function of CRM to service release;

The interface table of Complex interface from CRM to service release copies data to service release, and makes CRM enter history to the interface data of service release;

Service release data and CRM are to the common Property ID of the data sharing of service release, and the Property ID of definition business is supplied to service release;

Service release obtains corresponding service attribute value according to described Property ID, by this service attribute value transmit to Complex interface.

For solving the problems of the technologies described above, the present invention proposes the configuration-system of a kind of customer relation management to service release, comprising the read module, acquisition module, enquiry module and the assembling module that are connected successively, wherein:

Described read module, for reading the class of excel, obtains deploy content relevant to business in excel;

Described acquisition module, for obtaining DataBase combining string by reading configuration file;

Described enquiry module, for connection data storehouse, inquires about the data needed;

Described assembling module, for splicing structure query language SQL statement, is sorted to output by C++ container.

Further, said system also can have following characteristics, also comprises:

Calling module, for triggering calling interface function according to order;

Monitor module, for in the transmission service release process of form ordering system, order capable trigger table is monitored in scanning, and obtaining the capable state of order is that to serve order to be opened capable, call service release to send function to carry out message assembled, and assembled good message data is charged to service release interface table;

Complex interface application integration platform, for obtaining message data from described service release interface table and sending to service release;

Service release, for the treatment of message data, result is fed back to manageming contacts CRM, detached process scans the other side's interface table, data are passed to order relevant interface table;

Form ordering system, for the treatment of the data of described order relevant interface table, continues circulation order.

Further, said system also can have following characteristics, and described order relevant interface table comprises successfully feedback form and failed feedback form.

Further, said system also can have following characteristics, also comprises: packing module, for the service action needed for configure base allocation list, attribute and attribute value mode information being filled in GetSql.xls file.

Further, said system also can have following characteristics, also comprises:

Described form ordering system is also for calling the external interface function of CRM to service release;

Complex interface, copies data to service release for the interface table from CRM to service release, and makes CRM enter history to the interface data of service release;

Definition module, the data of described service release and CRM are to the common Property ID of the data sharing of service release, and described definition module is supplied to service release for the Property ID defining business;

Described service release, also for obtaining corresponding service attribute value according to described Property ID, gives described Complex interface by this service attribute value transmit.

Customer relation management of the present invention, to the collocation method of service release and system, decreases CRM to the workload in the configuration of service release, has saved setup time, improve allocative efficiency.Further, customer relation management of the present invention, to the collocation method of service release and system, is of value to quick opening, can not causes the conflict of database.

Accompanying drawing explanation

Fig. 1 be in the embodiment of the present invention customer relation management to the process flow diagram of the collocation method of service release;

Fig. 2 be in the embodiment of the present invention customer relation management to the structural drawing of the configuration-system of service release.

Embodiment

Be described principle of the present invention and feature below in conjunction with accompanying drawing, example, only for explaining the present invention, is not intended to limit scope of the present invention.

The simplification that the present invention is configured by codes implement, some fixing statements by Program Generating, uncertain part is realized by configuration excel.

Fig. 1 be in the embodiment of the present invention customer relation management to the process flow diagram of the collocation method of service release.As shown in Figure 1, in the present embodiment, customer relation management comprises the steps: to the flow process of the collocation method of service release

Step 101, reads the class of excel, obtains deploy content relevant to business in excel;

Step 102, obtains DataBase combining string by reading configuration file Config.cfg;

Step 103, connection data storehouse, inquires about the data needed;

Step 104, assembled SQL (Structured Query Language, Structured Query Language (SQL)) statement, is sorted to output by C++ container.

In the embodiment of the present invention, customer relation management can also comprise the steps: to trigger calling interface function according to order to the collocation method of service release; In the transmission service release process of form ordering system, the capable trigger table of order is monitored in scanning, obtaining the capable state of order is that to serve order to be opened capable, calls service release and sends function to carry out message assembled, and assembled good message data is charged to service release interface table; Complex interface application integration platform obtains message data from described service release interface table and sends to service release; Result is also fed back to manageming contacts CRM by service release process message data, and detached process scans the other side's interface table, data is passed to order relevant interface table; The data of form ordering system process order relevant interface table, continue circulation order.

Wherein, order relevant interface table can comprise successfully feedback form and failed feedback form.

In the embodiment of the present invention, customer relation management can also comprise the steps: the service action needed for configure base allocation list, attribute and attribute value mode information to be filled in GetSql.xls file to the collocation method of service release.

Wherein, configurations table comprises service, the relation table or_svcgrouprel_dict of action and set of properties, set of properties, relation table or_groupprorel_dict, the data source obtaining value method table or_DataSource_dict of data source of Property ID and property value obtaining value method and data source definitions table or_DataDef_dict.The corresponding relation of these four tables is as follows:

or_svcgrouprel_dict.group_id＝or_groupprorel_dict.group_id，

or_groupprorel_dict.property_new_value＝or_DataDef_dict.data_id，

or_groupprorel_dict.property_old_value＝or_DataDef_dict.data_id，

or_DataSource_dict.datasource.id＝or_DataDef_dict.data_id。

Wherein, the data_exp (obtaining value method) shown in the field SVC_ID (service ID) in or_svcgrouprel_dict and property_name (attribute-name), the or_DataDef_dict table in ACTIOM_ID (action ID), or_groupprorel_dict table can obtain.The value of property_new_value with property_old_value is in most of the cases the same, will define twice table or_DataDef_dict respectively if different.The configuration of configurations table will illustrate in content below.

In the embodiment of the present invention, to the collocation method of service release, customer relation management can also comprise the steps: that form ordering system calls the external interface function of CRM to service release; The interface table of Complex interface from CRM to service release copies data to service release, and makes CRM enter history to the interface data of service release; Service release data and CRM are to the common Property ID of the data sharing of service release, and the Property ID of definition business is supplied to service release; Service release obtains corresponding service attribute value according to described Property ID, by this service attribute value transmit to Complex interface.

CRM is exactly the service of needs and attribute are added in the message template that had to the fundamental purpose of service release.By showing the relation of or_svcgrouprel_dict, or_groupprorel_dict, or_DataSource_dict, or_DataDef_dict, finding corresponding obtaining value method, then carrying out value and be filled in template.

Here is the template blank before configuration:

Suppose to require now that configuration service (svc_id) is S00001, action (action_id) is open an account (1000), attribute is KI (supposing to require that the value of KI is 123), and so through configuration, program will obtain template blank below after performing:

Below, the configuration of configurations table is described one by one.

1, the configuration of or_svcgrouprel_dict is shown

Table or_svcgrouprel_dict comprises field SVC_TYPE, SVC_ID, ACTION_ID, GROUP_ID, OP_TIME.

Wherein, field SVC_TYPE marks COS, is divided into O (Additional Services) and M (main service), herein by select*from pd_svc_dict where svc_id=' service ID ' go to inquire COS;

Wherein, field SVC_ID marks service ID, and this field obtains in parameterized template, such as will obtain now the SVC_ID of returning short message, can check that obtaining SVC_ID is BS1209 in parameterized template;

Wherein, field ACTION_ID marks action, herein if main service is inquired about by select*from pd_action_dict; If Additional Services are inquired about by select*from or_subsvcact_dict, in Query Result herein, field sub_svc_id is 0,1,2,3,4,8, corresponding relation be 1 order, 0 quit the subscription of, 2 suspend, 3 suspend recover, 4 change, 8 other, (in Additional Services, only have two action_id, be respectively 99999 and 99998), then remove the ACTION_ID in corresponding look-up table according to the ACTION in parameterized template, such as the corresponding ACTION_ID that opens an account is 1000;

Wherein, field GROUP_ID mark group and the set together of several attribute, need oneself to define herein, its value can be arbitrary, unique requirement is at table or_svcgrouprel_dict not, first can go inquiry by or_svcgrouprel_dict, then look for one not used, this value to GROUP_ID.

Wherein, field OP_TIME is system time.

Such as, suppose to want configuration service school to believe logical, action is opened an account, and can obtain INSERT statement below by illustrating above:

2, the configuration of or_groupprorel_dict is shown

Table or_groupprorel_dict comprises field GROUP_ID, PROPERTY_ID, PROPERTY_NAME, PROPERTY_NEW_VALUE, PROPERTY_OLD_VALUE, SERIAL_NO, PROPERTY_NUM, OP_TIME.

Wherein, field GROUP_ID marks service group, and this field configures in table or_svcgrouprel_dict;

Wherein, field PROPERTY_ID marks Property ID, this field needs configuration, first to determine which value table or_groupprorel_dict has been present in, this field value of configuration can not repeat with already present value, it is noted that, if this attribute exists, that just needs multiplexing original PROPERTY_ID in addition.Such as: by SQL:select*from or_groupprorel_dict where property_name=PHONE_NO ', can inquire this attribute of PHONE_NO and exist, be 8400517, so just can with originally configuring; Equally, if this attribute does not exist, a Property ID can be found out by inquiry, then determine whether this value exists by query statement.Such as: in table or_groupprorel_dict, determine property_id=123, then whether can be used by the value of following statement select*from or_groupprorel_dict where property_id=123 property_id=123.

Wherein, field PROPERTY_NAME is used for marking attribute-name, and this is in parameter configuration document and exists, and namely arrange the PHONE_NO in " INSTCON ", BIZCODE is called attribute;

Wherein, field PROPERTY_NEW_VALUE, PROPERTY_OLD_VALUE attribute is new, old value, need definition herein, their value can be arbitrary, unique requirement is at table or_groupprorel_dict not, first can go inquiry by or_groupprorel_dict, then look for respectively one not used, this value is assigned to PROPERTY_NEW_VALUE, PROPERTY_OLD_VALUE respectively.

Wherein, field SERIAL_NO is used for marking attribute number, is exactly to number in order to all attributes in group herein;

Wherein, field PROPERTY_NUM marks attribute number, and value represents the number of all properties herein;

Wherein, field OP_TIME is system time.

Data_id in the corresponding or_datadef_dict table of PROPERTY_NEW_VALUE, PROPERTY_OLD_VALUE in table or_groupprorel_dict.

Such as, supposing to want configuration service school to believe logical, INSERT statement below can be obtained by illustrating above:

Because this attribute of PHONE_NO exists, and by confirming that the obtaining value method existed can be multiplexing, so to the assignment of PROPERTY_NEW_VALUE, PROPERTY_OLD_VALUE with original the same.

3, the configuration of or_DataDef_dict is shown

Table or_svcgrouprel_dict comprises field DATA_ID, DATA_NAME, DATASOURCE_ID, DATA_TYPE, DAFAULT_VALUE, DATA_LENGTH.

Wherein, field DATA_ID, value is with perperty_new_value or perperty_old_value in table OR_GROUPPROREL_DICT herein, if perperty_new_value with perperty_old_value is identical, only needs configuration once just passable herein;

Wherein, field DATA_NAME, value is the perperty_name in table OR_GROUPPROREL_DICT herein;

Wherein, field DATASOURCE_ID, herein oneself definition, require that the datasource_id in or_datasource_dict does not have and repeating of newly defining, generally all the value of datasource_id be configured to identical with DATA_ID;

Wherein, field DATA_TYPE, comprises int, long, date, string, func, and the type namely marking the value of taking out in OR_DATASOURCE_DICT table is identical;

Wherein, these two fields of field DAFAULT_VALUE, DATA_LENGTH are not temporarily used, and fill out NULL.

Such as, suppose to want configuration service school to believe logical, action is opened an account, and can obtain INSERT statement below by illustrating above:

4, the configuration of or_DataSource_dict is shown

Table or_DataSource_dict comprises field DATASOURCE_ID, SRC_TYPE, DATA_EXP, RSLT_ID, RLST_TYPE, PARAM_ID, PARAM_TYPE.

Wherein, field DATASOURCE_ID, field is with the DATASOURCE_ID in or_DataDef_dict herein;

Wherein, field SRC_TYPE, value is 1-4 herein, and concrete meaning is as follows:

1 expression directly obtains from uType according to message;

2 represent acquired value from sql statement;

3 represent that one is obtained by pointer with * beginning, and one is definite value, such as 03;

4 representative functions;

Wherein, field DATA_EXP, definition value mostly is sql and definite value herein, and SRC_TYPE corresponding relation concrete and above is as follows:

1 expression directly obtains from uType according to message---want the field of value in corresponding message;

2 represent acquired value from sql statement----need product to provide obtaining value method herein;

3 represent that one is obtained by pointer with * beginning, and one is definite value, such as 03;

4 representative functions---respective function name;

Illustrate:

Example 1:datasource_id=' 100 ' data_exp=' ID_NO ' src_type=' 1 ' represents that 100 by uType ID_NO acquired value

Example 2:datasource=' 112 ', data_exp=' * $ (122) $ ' src_type=' 3 ' represents that the value of 112 obtains be worth and be assigned to 112 by data source 122

Example 3:

By expression formula acquired value, the change in expression formula needs by this mode acquired value of $ () $.

Wherein, field DATA_TYPE, comprises int, long, date, string, func;

Wherein, these two fields of field DAFAULT_VALUE, DATA_LENGTH are not temporarily used, and fill out NULL.

Such as, suppose to want configuration service school to believe logical, action is opened an account, by illustrate above can obtain below INSERT statement (herein need not defined attribute PHONE_NO again because its obtaining value method has existed and we determine it is can be multiplexing):

By the above configuration instruction to four configurations tables, following SQL statement can be obtained:

In the process of actual disposition CRM to service release data, often only can not configure an action, generally need to configure multiple action, such as order, quit the subscription of, open an account, sell in advance, sell in advance and recover etc.Collocation method is with the same above, but their obtaining value method is different in time being multiple action, the obtaining value method of the attribute ENDTIME_TEST such as ordering and sell correspondence is in advance different, it is value can be deposited into history lists that difference is to order and quit the subscription of, if will get less than value with the same of order time the obtaining value method of the attribute of correspondence is sold in definition in advance, because pre-pin value is got at main schedule, this situation is just needed according to method above, a corresponding relation is write to these four configurations tables more, so just can there be two kinds of corresponding relations, a kind ofly to fetch data at history lists, another fetches data at main schedule, so no matter which kind of action corresponding can get value.

Such as, suppose to want configuration service school to believe logical, action be open an account, in advance sell, sell recovery in advance, can determine that ACTION_ID corresponding to these actions is 99999 and 99998 according to aforesaid collocation method, said above, because these actions will in history lists and main schedule value, therefore two kinds of obtaining value methods will be defined, in order to define two kinds of different obtaining value methods, and these two kinds of obtaining value methods are same services, so correspond to two kinds of action definitions, two groups, the insert statement inserting table OR_SVCGROUPREL_DICT is as follows:

Be configured with two groups above, can respectively according to aforesaid method allocation list or_groupprorel_dict corresponding to these two groups, or_DataDef_dict is as follows:

------21067 groups

-----21068 groups

------21067 groups

-----21068 groups

Configure obtaining value method below, as follows by the expression formula of getting main schedule obtaining data_exp as the determination of product:

And after table name, add HIS and condition and a.update_accept=" $ (103) $ " and a.update_type unequal to " U " exactly in the difference that history lists fetches data, table pd_userprc_info_ $ (100 such as,-1,2) history lists of $ is pd_userprc_info_his_ $ (100,-1,2) $, so it is as follows to obtain expression formula:

Be 99999 owing to ordering respective action, and group corresponding to this action is 21067, can obtain datasource_id is by that analogy 3521 fetch data at history lists, so it is as follows to insert predicative sentence:

To the configuration of above-mentioned four configurations tables, should be noted that following some:

1, general configuration, picks up from source, first allocation list or_svcgrouprel_dict;

2, service release message parameter obtains, and the most basic entrance is: service (svc_id)+action (action_id);

3, svc_id+action_id → group_id (table or_svcgrouprel_dict realizes this configuration, service+action herein can corresponding multiple parameter group);

4, (table or_groupprorel_dict realizes this configuration to group_id → property_id+property_old_value+property_new_value, group can corresponding N number of attribute herein, in conjunction with table above, each service+action can determine the parameter needed for N number of service release);

5, property_new_value/property_old_value=or_datadef_dict.da ta_id (table or_datadef_dict be configured with above table in property_old_value and property_new_value value);

6, data_id → datasource_id (or_datadef_dict is configured with data source id:datasource_id corresponding to data_id);

7, datasource_id → data value (or_datasource_dict is configured with the obtaining value method of data source);

8, for above-mentioned 4 configurations tables, first can establish an excel form, after complete for desired data collection arrangement, produce sql script according to excel form.

Under normal conditions, in or_datasource_dict table, data_exp is sql statement, will introduce by way of example by group value, the collocation method getting definite value below.

Such as, configure main service enterprise all-purpose card, SVC_ID=' BSJ111 ' can order, quits the subscription of, sell in advance, and attribute has SERVICELEVELID, EFFTTIME, ENDTIME, EXT_YKTKQ_ADMINPHONE.EFFTTIME, ENDTIME can with original, and SERVICELEVELID gets definite value 0.

First select*from pd_action_dict can inquire corresponding action ID is 1000,1052,1055, two not used GROUP_ID are found to be 20123 and 20124 through inquiry, introduced aforementioned, and ordered and quit the subscription of and will fetch data in history lists, so corresponding for action 1000 and 1055 group, the corresponding another one group of pre-pin, so can configure as follows:

Insert into OR_SVCGROUPREL_DICT(SVC_TYPE，SVC_ID，ACTION_ID，GROUP_ID，OP_TIME，OP_NOTE)Values(′M′，′BSJ111′，1000，20109，sysdate，NULL)；

Insert into OR_SVCGROUPREL_DICT(SVC_TYPE，SVC_ID，ACTION_ID，GROUP_ID，OP_TIME，OP_NOTE)Values(′M′，′BSJ111′，1055，20109，sysdate，NULL)；

Insert into OR_SVCGROUPREL_DICT(SVC_TYPE，SVC_ID，ACTION_ID，GROUP_ID，OP_TIME，OP_NOTE)Values(′M′，′BSJ111′，1052，20110，sysdate，NULL)；

It should be noted that, a general configuration custom is all that odd number is corresponding to history lists value.

Allocation list OR_GROUPPROREL_DICT below, first attribute EFFTTIME is determined by inquiry OR_GROUPPROREL_DICT table and the people to product, ENDTIME, can with to be originally defined, so can EFFTTIME be determined, property_new_value with property_old_value of ENDTIME is identical and be respectively 249 and 251, then question blank or_datadef_dict, the definition of 249 and 251 is there is in confirmation form, but in table or_datasource_dict, but there is no the obtaining value method of 251, here the concept of group is just caused, by group value in other words when the obtaining value method of two attributes is identical can once take out time, just can be defined in one in an obtaining value method, inquired about by his-and-hers watches select*from or_DataGroup_rel, obtain the corresponding relation that 249-251 also exists group, so can determine that their new old value is 249 and 251, and configure as follows:

-----20109 groups

-----20110 groups

To above-mentioned statement, it should be noted that, the obtaining value method of group is not in daily use, but arouse attention, and if only occur 251 and do not occur 249, so just with organizing the method for value, can only can not redefine an obtaining value method to 251 or carry out value by other implementation method; In 20110 groups, PROPERTY_NEW_VALUE and PROPERTY_OLD_VALUE of attribute ' SERVICELEVELID ' correspondence is 2559, with in 20109 groups ' the new old value of SERVICELEVELID ' attribute is identical, this is because what know that attribute ' SERVICELEVELID ' gets is definite value, so do not needed to distinguish in history lists value and main schedule value, their obtaining value method and datadef table can be identical.

Carry out allocation list or_datadef_dict below, due to multiplexing being defined originally of attribute EFFTTIME, ENDTIME_TEST, so here just need not to define they two, configure as follows:

-----20109 groups

-----20110 groups

Carry out allocation list or_datasource_dict below, what should be noted that attribute ' SERVICELEVELID ' gets herein is definite value, configures as follows:

----20109 groups, fetch data from dataSource table

----20110 groups, fetch data from dataSource table

Note: obtaining value method:

In above-mentioned statement, condition id_no=" $ (100) $ " and svc_id=" $ (109) $ ", here $ (100) $ is just equivalent to the obtaining value method calling datasource_id=100 in fact, and $ (109) $ is equivalent to the obtaining value method calling datasource_id=109.

Should be noted that following some:

1, the data source value of some conventional variablees is as follows:

User id_no $ (100) $ obtains,

Operation flowing water update_accept obtains with (103),

Agent Service MAIN_SVC_ID $ (109) $ obtains,

Additional Services ID $ (114) $ obtains,

Customer ID cust_id $ (115) $ obtains,

Service area REGION_ID $ (104) $ obtains,

Operator's job number LOGIN_NO obtains with (126),

Service number SERVICE_NO $ (125) $ obtains,

2, variable is replaced symbol $ () $ and can be intercepted result character string according to variable-value, using method: $ (data, loc, len) $, usage is with the substr method of oracle.Such as $ (100 ,-1,2) $ represents that intercepting 2 .100 data source value character strings are id_no of user from last 1 of 100 these data source value result character strings left, is namely intercept last two of id_no herein;

3, skilfully use UE row pattern batch and write SQL configuration statement;

When 4, using result set pattern acquiring data source value, i.e. or_datasource_dict.rslt_type=2, such as 249 and 251 two data sources are got by the data_exp of 249 1 data sources.Then now the value of 251 just depends on 249, if 249 these data sources do not use in service configuration, so 251 also can not get value.Because data source does not have value entrance, say with not these data inside data buffer storage;

When 5, using result set pattern acquiring data source value, if a certain train value taken out is for time empty, can have an impact to whole data set result.To eliminate the effects of the act method: nvl (column_x, chr (0)) can added by empty row.Such as source_id=3990:

6, because data source value uses cache way, if if so the data_exp in or_datasource_dict table has renewal, need flush buffers, method upgrades or_templet_dict.valid row.Valid value can be compared when program enters and whether have renewal, if had, then again can get or_datasource_dict table and put into chained list.

Upgrade statement:

UPDATE or_templet_dict

SET valid＝TO_CHAR(MOD(TO_NUMBER(valid)+1，10))

7, in general, a service can configure two cover group_id, corresponding attribute service data value is respectively from history lists value and master meter value, the such as parameter IMSI value of main service S00001, change of product 1104 value, from user's master meter ur_usersim_info value, cancellation then needs user's history lists ur_usersim_info_his to go value, because after cancellation, the business datum of user all can proceed to history lists.Such as, for two kinds of obtaining value methods of IMSI, to its definition two set of properties: 20014 and 20013.

8, in or_svcgrouprel_dict table about the action_id of Additional Services.; In this table the inside, the value that the action_id of Additional Services does not use input parameter to transmit, but have two 99999/99998, being the set of properties of 99999 configurations from history lists value in or_svcgrouprel_dict, is the set of properties of 99998 configurations from master meter value.Such as: select*from or_svcgrouprel_dict where svc_id=' BS1002 '.

The verification of data can adopt following steps:

1, verify whether have exception according to following statement:

2, the first step: according to order number or order line number inquiry sequence information checking OL_STATUS field:

Select*from or_orderline_info WHERE order_line_id＝′L1210012600000014′；

Master meter is record not, represents that order has been brought to completion into history

Select*from or_ordline_info_201001 WHERE order_line_id＝′L2210012700000028′；

< 13 not yet goes to service release, and request helps order group related personnel's problem identificatioin place

=13 services are treated open-minded, and the reason majority running into this situation at present occurs that order is waited for, namely there is still untreated order before this order or exist abnormal, please perform second step

In=14 service releases

> 14 service release terminates, and please directly performs the 3rd step

3, second step: if order status is 13, please look into see if there is and wait for order or exception:

Wait for order:

Abnormal order:

SELECT*

FROM or_ordlineexcp_info

WHERE order_line_id＝′L2210041500000021′

Check the error message of excp_reason and err_msg field description, according to miscue information inspection allocation list data, orientation problem reason.

Common exception has:

Call the failure of service release function:

[if_Exception|30000|30000|fillUtype. extremely-1 is returned]----this mistake does not normally need the service sending service release not configure to cause, can according to the service ID of order, to table 1or_ordlinedisprelse_dict (controlling whether send service release), confirm that business is the need of transmission.

The statement error of data source.

4, the 3rd step: check that whether message data is correct

select*from spmswOrderTaskLog0004where crm_order_id＝′L2210012700000028′

--current table, this shows last position is last position of id_no.

select*from SPMSWORDERTASKLOGHIS201004 where crm_order_id＝′L2210012700000028′

--history lists.Submeter is carried out by days

If data enter history and the field of configuration all in message, the contact service personnel of opening please check whether success, if some field is not in message, forward the 4th step to, if current table data do not enter history please contact Complex interface.

5, the 4th step: check whether obtaining value method can get value

Attribute according to message and oneself configuration is compared, if lack certain attribute, that just goes or_grouprel_dict to go to search the new old value of this attribute, and then goes to inquire about obtaining value method, see that can obtaining value method get value, confirm with regard to the people contacting product if do not get value.

Customer relation management of the present invention, to the collocation method of service release, decreases CRM to the workload in the configuration of service release, has saved setup time, improve allocative efficiency.Further, customer relation management of the present invention, to the collocation method of service release, is of value to quick opening, and can not cause the conflict of database.

The invention allows for the configuration-system of a kind of customer relation management to service release, in order to implement the collocation method of above-mentioned customer relation management to service release.

Fig. 2 be in the embodiment of the present invention customer relation management to the structural drawing of the configuration-system of service release.As shown in Figure 2, in the present embodiment, customer relation management can comprise read module 210, acquisition module 220, enquiry module 230 and assembling module 240 to the inking device 200 of service release.Read module 210, for reading the class of excel, obtains deploy content relevant to business in excel.Acquisition module 220 is for obtaining DataBase combining string by reading configuration file.Enquiry module 230, for connection data storehouse, is inquired about the data needed.Assembling module 240, for splicing structure query language SQL statement, is sorted to output by C++ container.

In the embodiment of the present invention, customer relation management can also comprise calling module to the configuration-system of service release, monitor module, Complex interface application integration platform, service release and form ordering system.Wherein, calling module is used for triggering calling interface function according to order.Monitor module to be used in the transmission service release process of form ordering system, the capable trigger table of order is monitored in scanning, obtaining the capable state of order is that to serve order to be opened capable, calls service release and sends function to carry out message assembled, and assembled good message data is charged to service release interface table.Complex interface application integration platform is used for obtaining message data from service release interface table and sending to service release.Service release is for the treatment of message data and result is fed back to manageming contacts CRM, and detached process scans the other side's interface table, data is passed to order relevant interface table; Form ordering system, for the treatment of the data of order relevant interface table, continues circulation order.

In the embodiment of the present invention, customer relation management can also comprise packing module to the configuration-system of service release.Packing module is used for the service action needed for configure base allocation list, attribute and attribute value mode information to be filled in GetSql.xls file.

In the embodiment of the present invention, customer relation management can also comprise Complex interface and definition module to the configuration-system of service release.Form ordering system is also for calling the external interface function of CRM to service release.The interface table that Complex interface is used for from CRM to service release copies data to service release, and makes CRM enter history to the interface data of service release.The data of service release and CRM are to the common Property ID of the data sharing of service release, and definition module is supplied to service release for the Property ID defining business.Service release also for obtaining corresponding service attribute value according to Property ID, by this service attribute value transmit to Complex interface.

Customer relation management of the present invention, to the configuration-system of service release, can perform the collocation method of aforesaid customer relation management to service release, decreases CRM to the workload in the configuration of service release, has saved setup time, improve allocative efficiency.Further, customer relation management of the present invention to service release configuration-system performed by customer relation management to the collocation method of service release, be of value to quick opening, and the conflict of database can not be caused.

The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.

Claims (8)

1. customer relation management is to a collocation method for service release, it is characterized in that, comprising:

Read the class of excel, obtain deploy content relevant to business in excel;

DataBase combining string is obtained by reading configuration file;

Connection data storehouse, inquires about the data needed;

Splicing structure query language SQL statement, is sorted to output by C++ container;

Service action needed for configure base allocation list, attribute and attribute value mode information are filled in GetSql.xls file;

Wherein, configurations table comprises service, the relation table or_svcgrouprel_dict of action and set of properties, set of properties, relation table or_groupprorel_dict, the data source obtaining value method table or_DataSource_dict of data source of Property ID and property value obtaining value method and data source definitions table or_DataDef_dict.

2. customer relation management according to claim 1 is to the collocation method of service release, it is characterized in that, also comprises:

Calling interface function is triggered according to order;

In the transmission service release process of form ordering system, the capable trigger table of order is monitored in scanning, obtaining the capable state of order is that to serve order to be opened capable, calls service release and sends function to carry out message assembled, and assembled good message data is charged to service release interface table;

Complex interface application integration platform obtains message data from described service release interface table and sends to service release;

Result is also fed back to manageming contacts CRM by service release process message data, and detached process scans the other side's interface table, data is passed to order relevant interface table;

The data of order relevant interface table described in form ordering system process, continue circulation order.

3. customer relation management according to claim 2 is to the collocation method of service release, it is characterized in that, described order relevant interface table comprises successfully feedback form and failed feedback form.

4. customer relation management according to claim 2 is to the collocation method of service release, it is characterized in that, also comprises:

Form ordering system calls the external interface function of CRM to service release;

The interface table of Complex interface from CRM to service release copies data to service release, and makes CRM enter history to the interface data of service release;

Service release data and CRM are to the common Property ID of the data sharing of service release, and the Property ID of definition business is supplied to service release;

Service release obtains corresponding service attribute value according to described Property ID, by this service attribute value transmit to Complex interface.

5. customer relation management is to a configuration-system for service release, it is characterized in that, comprises the read module, acquisition module, enquiry module and the assembling module that are connected successively, wherein:

Described read module, for reading the class of excel, obtains deploy content relevant to business in excel;

Described acquisition module, for obtaining DataBase combining string by reading configuration file;

Described enquiry module, for connection data storehouse, inquires about the data needed;

Described assembling module, for splicing structure query language SQL statement, is sorted to output by C++ container;

Packing module, for being filled in GetSql.xls file by the service action needed for configure base allocation list, attribute and attribute value mode information;

Wherein, configurations table comprises service, the relation table or_svcgrouprel_dict of action and set of properties, set of properties, relation table or_groupprorel_dict, the data source obtaining value method table or_DataSource_dict of data source of Property ID and property value obtaining value method and data source definitions table or_DataDef_dict.

6. customer relation management according to claim 5 is to the configuration-system of service release, it is characterized in that, also comprises:

Calling module, for triggering calling interface function according to order;

Monitor module, for in the transmission service release process of form ordering system, order capable trigger table is monitored in scanning, and obtaining the capable state of order is that to serve order to be opened capable, call service release to send function to carry out message assembled, and assembled good message data is charged to service release interface table;

Complex interface application integration platform, for obtaining message data from described service release interface table and sending to service release;

Service release, for the treatment of message data, result is fed back to manageming contacts CRM, detached process scans the other side's interface table, data are passed to order relevant interface table;

Form ordering system, for the treatment of the data of described order relevant interface table, continues circulation order.

7. customer relation management according to claim 6 is to the configuration-system of service release, it is characterized in that, described order relevant interface table comprises successfully feedback form and failed feedback form.

8. customer relation management according to claim 6 is to the configuration-system of service release, it is characterized in that, also comprises:

Described form ordering system is also for calling the external interface function of CRM to service release;

Complex interface, copies data to service release for the interface table from CRM to service release, and makes CRM enter history to the interface data of service release;

Definition module, the data of described service release and CRM are to the common Property ID of the data sharing of service release, and described definition module is supplied to service release for the Property ID defining business;

Described service release, also for obtaining corresponding service attribute value according to described Property ID, gives described Complex interface by this service attribute value transmit.