Skip to main content

All Outbound Request in Siebel SQL Query

--All Outbound Requests--
SELECT
SCR.REQ_NUM AS 'Request #'
,SCR.STATUS_CD AS 'Status'
--,SCR.CM_SRVR_COMP_NAME AS 'Component Name'
--,SCR.NAME AS 'Description'
,SCR.STATUS_MSG AS 'Status Message'
--,SCR.DFLT_MEDIUM_CD AS 'Default Preference'
--, AS 'Recipient Group'
,SCR.PROC_START_DT AS 'Start Time'
,SCR.PROC_END_DT AS 'End Time'
,SCR.CREATED AS 'Created'
,SCRU.LOGIN AS 'Created By'
--,SCR.COMMENTS AS 'Comments'
--Comm Request Source--
,SCRS.SRC_ROW_ID AS 'Id'
--Comm Package--
,SDCP.NAME AS 'Name'
,SDCP.MEDIA_TYPE_CD AS 'Channel Type'
--Request Recipient Source
--,RCS.ROW_ID
,RCS.SR_NUM AS 'SR No'
--Customer Record
,(ISNULL(CUS.FST_NAME, '') + ' ' + ISNULL(CUS.MID_NAME, '') + ' ' + ' ' + ISNULL(CUS.LAST_NAME, '')) AS 'Name ENU'

FROM S_COMM_REQ SCR --Comm Parent Request
LEFT JOIN S_USER SCRU ON SCRU.PAR_ROW_ID = SCR.CREATED_BY -- Comm Parent Request Created By
LEFT JOIN S_COMM_REQ_SRC SCRS ON SCRS.COMM_REQ_ID = SCR.ROW_ID -- Comm Request Source
LEFT JOIN S_COMM_REQ_PKG SCRPIT ON SCRPIT.COMM_REQ_ID = SCR.ROW_ID -- Comm Request/Comm Package
LEFT JOIN S_DMND_CRTN_PRG SDCP ON SDCP.ROW_ID = SCRPIT.DCP_ID --Comm Package
LEFT JOIN S_COMM_REQ_SRC RCSI ON SCR.ROW_ID = RCSI.COMM_REQ_ID
LEFT JOIN S_SRV_REQ RCS ON RCS.ROW_ID = RCSI.SRC_ROW_ID --Request Recipient Source
LEFT JOIN S_CONTACT CUS ON CUS.ROW_ID = RCS.CST_CON_ID -- Customer Record

WHERE 1=1

ORDER BY SCR.CREATED DESC

Comments

Popular posts from this blog

How to set Profile Attribute in Siebel Workflow

For setting the Profile Attribute in Siebel Workflow, follow below steps: Add Business Service box in workflow. Open Business Service properties. Set  SessionAccessService in Business Service Name. Set  SetProfileAttr in Method Name. Then click on Business Service and set Input Arguments as below: Against Name argument you will add your profile attribute name and against Value argument you will add value for the new profile attribute, it could be from Process Property or Literal.

How to call Popup Applet through Server Script in Siebel

Background: Based on the requirements you need to show data or reports on a popup applet. You can invoke popup applet using workflow (below business service will be used in business service step), applet server script or browser script and using vanilla method and setting field user properties. Procedure: Below is the script for calling popup applet through server script: if (MethodName == "MethodName") { var oServiceAF = TheApplication().GetService("SLM Save List Service"); var inputPropAF = TheApplication().NewPropertySet(); var outputPropAF = TheApplication().NewPropertySet(); inputPropAF.SetProperty("Applet Name","ABC Popup Applet"); inputPropAF.SetProperty("Applet Mode","6"); inputPropAF.SetProperty("Applet Height", "700"); inputPropAF.SetProperty("Applet Width", "700"); oServiceAF.InvokeMethod("LoadPopupApplet", inputPropAF, outputPropAF) return (CancelOperati...

How to create and publish Inbound Web Service in Siebel based on Workflow

Inbound Web Services: The Inbound Web Service allows an external system to call a Siebel published Web Service. You can publish a business service or a business process as a Web Service and generate a Web Service Definition Language (WSDL) file that an external system can import. The Inbound Web Services can only be published from Siebel C using SOAP-RPC binding. Source: Oracle Docs What Is The Difference Between Web Services and APIs? An API is an interface that allows you to build on the data and functionality of another application, while a web service is a network-based resource that fulfills a specific task. Yes, there’s overlap between the two: all web services are APIs, but not all APIs are web services. Both web services and APIs are — at their core — very useful and very much used today. However, it’s the web services associated with SOAP and/or Service Oriented Architecture which are falling out of favor. Source: NordicApis Process: Prepare the workflow which will serve as Si...