02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Updating Calls<br />

Defining the Structured Query Language Statements<br />

Help Desk Integration<br />

When defining the Structured Query Language (SQL) statements for the HDDRSelectSQL<br />

and HDSRSelectSQL properties, specify the selected fields in the following order:<br />

Call ID (10a)<br />

Customer Number (10a)<br />

Customer Name (30a)<br />

Product (10a)<br />

Allocated to (10a)<br />

Waiting on (10a)<br />

Call Status (1a)<br />

DR or SR number (5,0)<br />

The size of the original field in your help desk software is not important because the field<br />

truncates to the size indicated when updating the SupportCenter call header file.<br />

The following is an example SQL statement:<br />

SELECT SUBSTR(S_SRV_REQ.SR_NUM,1,10),<br />

SUBSTR(S_SRV_REQ.CST_OU_ID,1,10), SUBSTR(S_ORG_EXT.NAME,1,30),<br />

SUBSTR(S_PROD_INT.NAME,1,10), SUBSTR(S_EMPLOYEE.LOGIN,1,10),<br />

SUBSTR(S_SRV_REQ.SR_SUB_STAT_ID,1,10),<br />

SUBSTR(S_SRV_REQ.SR_STAT_ID,1,1), SUBSTR(S_SRV_REQ.SR_CST_NUM,3,5)<br />

FROM SIEBEL.S_EMPLOYEE S_EMPLOYEE, SIEBEL.S_ORG_EXT S_ORG_EXT,<br />

SIEBEL.S_PROD_INT S_PROD_INT, SIEBEL.S_PROD_LN S_PROD_LN,<br />

SIEBEL.S_SRV_REQ S_SRV_REQ WHERE S_SRV_REQ.CST_OU_ID =<br />

S_ORG_EXT.ROW_ID AND S_SRV_REQ.PRDINT_ID = S_PROD_INT.ROW_ID AND<br />

S_PROD_INT.PR_PROD_LN_ID = S_PROD_LN.ROW_ID AND<br />

S_SRV_REQ.OWNER_EMP_ID = S_EMPLOYEE.ROW_ID AND ((S_SRV_REQ.SR_CST_NUM<br />

Like 'DR%') AND (S_PROD_LN.NAME Like '%<strong>MKS</strong>%'))<br />

You run the Associate Calls Update program from the DTBridge Console. A Java class<br />

executes your defined SQL statements, which associates calls with the appropriate DR or SR<br />

and generates a history log of the associated calls. For example, any records containing data<br />

that maps incorrectly (such as alpha data in the numeric DR/SR number field) causes a<br />

warning message in the history log. The invalid records are skipped, and the process<br />

continues with the next record. A total count of all warnings posted (resulting in records not<br />

updated) prints at the end of the log. To view the latest history log, from the DTBridge<br />

Console, click File > View History.<br />

327

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!