CUIC Reason code reports

I am trying to create a report that shows reason codes as words, eg 1 =meeting etc
I have made what I believe to be the relavant changes, however whilst the Parameters check out ok, when i go to creat the fields, I get a syntax error.
if anyone can take a look at this and let me know here I am goiing wrong, I would be grateful.
please be advised, I haven't had any training on SQL, I am learning as i go!

Thanks for getting back to me, unfortunately I don't have the ability to check this through an SQL application.
Hence the question.:-)
I will go through the query again
Cheers Sarah

Similar Messages

  • Global reason code report generation

    Dear All,
    I am running uccx8.0 standard Edition. I want to take global reason codes report, How can i do that. I think in the CCX historical report i can see the reports for preserved. But i want to see for custom reason codes.

    Sorry i got the solution,

  • CUIC Not Ready Reason Code Reporting Issue

    We have a single node UCCX 9.0.2 environment with co-resident CUIC used for historical reporting.
    When we run the Agent Not Ready Reason Code Summary Report it will only give statistics for the system generated reason codes (the 32XXX ones), even if we choose other reason codes in the filter parameters.
    In the attached screenshots you can see where I chose a bunch of other reason codes as filter options, but none of them show on the report.  It does the same thing regardless of who runs the report, including the admin super user that's created during installation.
    Anyone have any ideas?

    We do not run the same version that you are on, however, I would also take a look at the Agent State Detail report and filter by the reason code field.
    The report includes a lot of additional data but at least you can get to the actual customized reason code values along with the duration the agent spent in that code per occurrence.
    Hope this helps.

  • Reason codes

    Hi ,
    We have a contact center UCCE 8x, in which few of the Agents are migrated to Siebel CRM CTI Application from CAD. We are using Cisco CRM adapters for the CTI communications between CRM and ICM. So the call is maturing to the agent properly, but the (AUX code)reason codes reports are not getting appeared on the CUIC.
    Please let us know where are we need to look up to fix this reports issue.
    Also let me know where we need to configure reason code for Siebel desktop users.

    Hi,
    Can you let me know what is the solution for this issue?
    Regards
    Arun

  • CUIC Agent Real-time reporting reason code

    Hi,
    In CUIC agent real time report reason code for not ready it shows 50002 or integer we have configured in ICM.
    How we can display reason code as name which we have configured in icm like tea, coffee , meeting.
    CUIC version we are using 8.5.
    Regards,
    Dinesh Joshi

    The way I got round this was creating thresholds - eg 1 = Lunch 2 = meeting etc.
    this does work, however you can't then Threshold the time on those particular texts, but at least you can see what 'state' they are in.
    let me know if it works..
    Thanks Sarah

  • Packaged CCE 9.03 - Display Reason Code Text in CUIC report

    The (Stock) Agent Team Real Time report includes a Reason Code field, but not the descriptive Reason Code Text (or Name).  Is there any way to present the descriptive text  or name in the report?
    Please note that we have CUIC standard.
    Thanks!
    Jackie

    Comparing Handled on an Agent report to Answered on a Call Type report is tricky, since depending on your call flows the two values can be vastly different. If you're looking at Answered and Handled on the same report (Call Type Historical All Fields should have both), there are opportunities for either value to be higher than the other within any given interval or across multiple intervals.
    Generally, if Answered is higher than Handled in one interval, then Handled is going to be higher than Answered in one of the intervals after that (though not necessarily the one right after - depends on call length). In the database, Answered is incremented in the interval when the call is answered, Handled is incremented in the interval when the wrap-up completes. So a very basic example would be with a single call - Say the Agent picks up an inbound call at 8:56am, and hangs up and completes wrap-up at 9:07am... The 8:30am interval would show 1 call Answered and 0 Handled, while the 9:00am interval would show 0 calls Answered and 1 Handled.
    -Jameson

  • Reason Code dispaly in FBL3N report

    Hi!
    We have used reason codes for specific purpose i.e when ever cash and bank postings are happened, reason code must be assigned in order to know the nature of payment.
    But while taking the FBL3N report, reason code is not dispalying any data,available in BSEG table.
    how to do it?
    I have configured for choose additional fields under GL Accounting - GL accounts-Display line items-choose additional fields.
    regs,
    Ramesh

    Hi,
    Go to FBL5N and execute.you will see the list of open and cleared items.Change the layout by selecting the Reason Code in the list available and click the left arror button and save it.you can see the reason code.
    Thanks
    Prasada

  • Documents not coming in the report taken for reversal reason code

    Hi,
    We have defined the various reason codes for document reversal.
    When we try to take the report based on the reason code in FB03 or FAGLL03, the reversal doucment is not coming up.
    Is there any setting for it? or how to get that report? We need that report to authorize the reversals.
    Thanks,
    Pratap

    Hi,
    Please note that In standard SAP, the reversal reason code gets stored in the original document which is reversed. It does not get stored in the reversal document.
    You can get the report based on the field STBLG (Reverse Document Number) and STJAH (Reverse document fiscal year).
    This will be filled up for both original document and reversal document. And the clearing document number will be same for both the documents, so you can easily link the two documents in FAGLL03 output layout using sorting based on clearing document and filtering based on the two fields given.
    Regards,
    Gaurav

  • Agents showing in NOT READY Reason Code Summary Report

    I have a large install, with over 100 skills and CSQs.  Three agents always show up in everybody's Not Reason Code Summary Report, even though they are not assigned to those skills.  At this point none of these three agents has ever been active.  My assumption is there is a bug that until an agent actually goes Active at least once this happens.  I am looking for confirmation, documentation of such.
    Thanks.

    Hi,
    What is the version of IPCC you are running?
    What do you mean when you say agent goes active?
    Please refer to this guide below for UCCX 5.0. Refer to pg 65 for Agent Summary report.
    http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/crs/express_6_0/user/guide/crs601hr.pdf
    See if it has the information you are looking for.
    So you mean to say you filter this report based on Skill name and still see those 3 agents evene when you chose a skill which is nto assigned to three of them?
    Thanks
    Ankita

  • Historical report issue with CCX Custom Reason codes

    Hi Evryone,
    I have CCX version 8.5,
    In Cisco Desktop Administrator ,I have configured custom Reason codes for agent logout & Agent not ready,
    These code are working ok when agent is loging out or Not ready,
    But in Historical reports I am not able to see these custom Reason code base reports
    I can only see the reports for agent not ready/login logout with only global reason codes, but report didnt show the cutom reason code base report
    Please help me to troubleshoot this issue.
    Regards
    Deepak

    hi Deepak, 
    Did you do something else while creating new global reason codes? 
    I have global reason codes, but in the the Historical Reports "detail" tab don't show up any of them. Report only shows system-genereted reason codes.
    BEst regards

  • The system shall allow for reporting by rejection reason code

    Allow the reporting of a reason code when an order is rejected for the purpose of tracking lost sales
    The system shall allow for reporting by rejection reason code to allow for tracking lost sales.

    A custom ABAP will have to be developed looking at table VBAK and VBAP to determine the reason for rejection, then group it by order number.

  • Getting Reason Code, Condition Type, and Condition Value in one report

    Hello there,
    I have got a Question for you all BW Gurus. I need the answer for this as soon as possible. I will assign points to all helpful answers.
    I am having a Sales cube, Delivery Cube, and a Conditions Cube which I built. Each cube is populated from different ODS. Means there are 3 ODS for 3 cubes. I am joining these 3 cubes under a Multiprovider.
    My Question is:
    We are using Reason Codes at Delivery level. We have identified an empty field in the delivery tables and populating this field with the reason codes. We have condition type and condition value only in the Condition cube. One of the reporting requirements is that we need to see Reason code, Condition Type, and Condition value in one report. I am planning to report on the Multiprovider. Since Reason code, Condition Type, and Condition value are not present in all the 3 cubes (means they are not common characteristics in the Multiprovider), I don’t think I can get those values in one report if I report on the Multiprovider. Please correct me if I am wrong. If what I say is correct, please tell me how to solve my problem. Once again, helpful answers will be greatly appreciated and rewarded with points.
    Thank you in advance.
    Kind Regards,
    Swathi

    Hello Swathi,
    Please do not post the same question on multiple forums.
    Thanks,

  • Siebel CRM Reason Code Commands

    We are needing to enable some commands on the Cisco CTIOS Siebel connector and just not sure where they are enabled or edited at.
    We are using connecter provided by  CISCO for CTI between Siebel and CISCO. Connector provides the enabled command to Siebel that siebel can send as device command like "DeviceCommand = "ChangeNotReadyState"" using communication configuration DEF file.
    Currently we have business requirement:
    CTI agents can set their state to NOT READY on a click of button with reason code selected by the agents irrespective of there current state.
    We configured the button, but the button is enabled only when the device command "ChangeNotReadyState" is enabled. Can it be possible to enable this button always and we can are able to change agents state at CTIOS level(CISCO)? Can we send "ChangeNotReadyState" command to CISCO irrespective of agents current state
    Here is what we have done so far:
    We configured DEF according to ORACLE support recommendation  (ID 543337.1 listed below in this mail)
    RELEVANT PARTIAL DEF FILE:
    [Command:DSC_NOTREADY_POP_EXE]
       SubCommand_1 = "DSC_NOTREADY_NOPOPUP"
       SubCommand_2 = "DSC_NOTREADY_POPUP"
       SubCommand_3 = "CleanDashBoard"
       Comment      = "YQ8279: Add for Direct not ready Button Aug2012"
       Description  = "Not Ready"
       ExecuteAll   = "TRUE"
       Hidden       = "TRUE"
    [Command:DSC_NOTREADY_NOPOPUP]
       Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
       Description   = "Not Ready"
       DeviceCommand = "ChangeNotReadyState"
       FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
       Hidden        = "TRUE"
    [Command:DSC_NOTREADY_POPUP]
       Comment       = "YQ8279: Add for Direct not ready Button Aug2012"
       Description   = "Not Ready"
       DeviceCommand = "ChangeNotReadyState"
       FilterSpec    = "[$GetCommandStatus(ChangeNotReadyState)]= 'Enabled'"
       Hidden        = "TRUE"
       CmdData       = "PopupforReason"
       [CmdData:PopupforReason]
          Comment          = "YQ8279: Add for Direct not ready Button Aug2012"
          Param.ReasonCode = "[Name]"
          SelectApplet     = "Transfer Multiple LOV Popup Applet"
          SelectBusComp    = "List Of Values"
          SelectBusObj     = "List Of Values"
          SelectParam      = "TRUE"
          SelectQuerySpec  = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
          SelectTitle      = "Please select the reason for changing status to Not-Ready"
    So with above configuration suggested by oracle support we are sending "ChangeNotReadyState" device command twice in a manner so that it will be processed one after the other. But it is not happing, second command is not going through as its not enabled after Siebel issued it once. Please see below logs and highlights.
    SCOMM LOG: <In Time Context >
    ChangeNotReadyState Command is enabled  (status = 16)
    see image 1 on attached doc
    Now user applied the command once :
    See Image 2 on attached doc
    Now "ChangeNotReadyState" device command is disabled .
    Can we make it "ChangeNotReadyState" enabled via connecter always by making some registry setting or some setup.
    See image 3 on attached doc
    Oracle Support Suggestion:
    Not able to select Not Ready Reason Code [ID 543337.1]
    https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147
    Symptoms
    In the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
    Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
    Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
    Cause
    Users were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
    During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
    The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls. 
    Solution
    Suggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
    Then we can call another communications command that starts the popup for the LOV of aux codes.
    Here the agent will have enough time to pick the code with no more inbound calls.
    The device commands for the command group are as follow:
    [Command:NotReadyForGVoiceGroup]
       SubCommand_1 = "NotReadyForGVoiceStd"
       SubCommand_2 = "NotReadyForGVoiceAuxCode"
       SubCommand_99 = "NotReadyForGVoiceEnabler"
       Description   = "Set not redy for voice"
       Hidden        = "TRUE"
       ExecuteAll = "TRUE"
    [Command:NotReadyForGVoiceStd]
       Description   = "Set not ready for voice"
       DeviceCommand = "NotReady"
       Hidden        = "True"
       Title        = "Voice not Ready"
       CmdData       = "NotReadyAuxCode"
    [CmdData:NotReadyAuxCode]
       Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
    [Command:NotReadyForGVoiceAuxCode]
       Description   = "Seçect Reason Code for Voice"
       DeviceCommand = "NotReady"
      FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
       Hidden        = "True"
       HotKey        = "Alt+A"
       Title        = "Aux Mode"
       Profile       = "Gplus Voice1"
       CmdData       = "ReasonCodePopup"
       [CmdData:ReasonCodePopup]
          Param.ReasonCode               = "[Name]"
          Param.ReasonValue               = "[Value]"
          Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
          SelectApplet                    = "Value Type Pick Applet"
          SelectBusComp                   = "List Of Values"
          SelectBusObj                    = "List Of Values"
          SelectParam                     = "TRUE"
          SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
          SelectTitle                     = "Please select the reason for changing status to Not-Ready"

    Thanks for your response Cherilynn,
    You are correct for a vanilla agetn desktop.  However, if the agent has to become available to move from one aux reason to another, the agent may get a call in that process.  With customiization, we can allow changing from one aux code to another without having to make the agent ready.  Oracle suggested a solution but to do this, we need to enable and modify certain parameters within Cisco.  What we are trying to find out is where are these parameters set, ex:  AgentWorkMode and AgentWorkMode2, ChangeNotReadyState...
    ORACLE SUPPORT SR
    Not able to select Not Ready Reason Code [ID 543337.1]
    SymptomsIn the current production we are having some CTI agents facing problem with picking the AUX Codes (Reason Codes) when trying to change status for Not Ready.
    Some of the agents reported that they can NOT pick the reason codes ( probably the icon is disabled for some reason at some point of time). I tried to reproduce the problem, but not happened.
    Our objective is to not receive the call and make the agent click the AUX Code (Not Ready Reason Code).
    CauseUsers were not able to pick the auxiliary code (reason code) at Siebel web client under using Genesys Gplus 7.0.000.1. Agent objective was to not receive the call and be able to click the AUX Code.
    During the operation of selecting an auxiliary code (aux code dialog open or not ready reason code applet) an incoming call reaches the agent before he decide which aux code to user not allowing selecting the reason code.
    The GPlus driver at this point did not receive the not ready command and is in ready state for this agent allowing new calls.
    SolutionSuggestion was to define first the not ready state for the GPlus with the default reason code = -1. Now agent is on a not ready state allowing enough time for agent to perform the selection.
    Then we can call another communications command that starts the popup for the LOV of aux codes.
    Here the agent will have enough time to pick the code with no more inbound calls.
    The device commands for the command group are as follow:
    [Command:NotReadyForGVoiceGroup]
       SubCommand_1 = "NotReadyForGVoiceStd"
       SubCommand_2 = "NotReadyForGVoiceAuxCode"
       SubCommand_99 = "NotReadyForGVoiceEnabler"
       Description   = "Set not redy for voice"
       Hidden        = "TRUE"
       ExecuteAll = "TRUE"
    [Command:NotReadyForGVoiceStd]
       Description   = "Set not ready for voice"
       DeviceCommand = "NotReady"
       Hidden        = "True"
       Title        = "Voice not Ready"
       CmdData       = "NotReadyAuxCode"
    [CmdData:NotReadyAuxCode]
       Param.ReasonCode               = "-1"   ; Check manual Gplus Adapter for Siebel 7—Deployment Guide page 241 for the value.
    [Command:NotReadyForGVoiceAuxCode]
       Description   = "Seçect Reason Code for Voice"
       DeviceCommand = "NotReady"
      FilterSpec    = "[$GetCommandStatus(NotReady)] = 'Enabled'"
       Hidden        = "True"
       HotKey        = "Alt+A"
       Title        = "Aux Mode"
       Profile       = "Gplus Voice1"
       CmdData       = "ReasonCodePopup"
       [CmdData:ReasonCodePopup]
          Param.ReasonCode               = "[Name]"
          Param.ReasonValue               = "[Value]"
          Param.StringAttributeExtensions = "ReasonCode,ReasonValue"
          SelectApplet                    = "Value Type Pick Applet"
          SelectBusComp                   = "List Of Values"
          SelectBusObj                    = "List Of Values"
          SelectParam                     = "TRUE"
          SelectQuerySpec                 = "[Type] = 'REASON_CODE' AND [Active] = 'Y'"
          SelectTitle                     = "Please select the reason for changing status to Not-Ready"
    Regards,
    https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_afrLoop=485718774714219&type=DOCUMENT&id=881215.1&displayIndex=4&_afrWindowMode=0&_adf.ctrl-state=dhq5nrae7_147

  • Reason code with post with different GL account

    Dear All,
    Help me to understand the following
    1.Reason code wise standard report
    2.customer/vendor payment difference want to post separate gl with Reason code wise
    3.Partal /Residual payment with different gl with reason code.
    4.Invoice is posted customer refuses to Pay.
    How to simulate the scenario without using dispute Management/Credit Management.
    Guide me is there any way to simulate the above issues with reason code.
    5.Suggest me is there any configuration other that OBBE/OBEX
    Reason code and post with diffent GL
    Regards,
    CS

    Hi CS,
    1.Reason code wise standard report.
    A. We can get the Reason code wise Report Customer line item Report FBL5N @ select screen and out put screen with change layout.
    2.customer/vendor payment difference want to post separate gl with Reason code wise
      A.Configuration OBBE we can configure, with the tick "C", and OBXL we can assign GL a/c and rules activate Reason code.
    3.Partial /Residual payment with different gl with reason code.
       A. while posting F-28 , or F-53 difference amount post in the field we have to field Reason code and Differences amount and  simulate,
    Note:If we select Reason code xxx with "C" in this scenario system will through error, we have to use other reason code except "C".
      Each reason code we can configure according to our requirements.
    4.Invoice is posted customer refuses to Pay.
       No idea in sap.
    Rds,
    @nil

  • Reversal Reason Code not displayed in document -FB08

    Hello,
    I have reversed the FI document using the transaction code FB08. While reversing I have given the SAP standard reversal reason code as 1. A new document was created on reversal of document.
    But Reversal reason code '1' is not getting displayed in FB03 or GL line item report FAGLL03. I have checked the Field staus of the Posting key as well as of the GL accounts, at both the places "Reason code" is optional entry field.
    Can you please suggest where/How to see the reversal reason in the document reversed through FB08.

    Hi Prasanna,
    First of all go to Table BKPF & check for the field STGRD value for the concerned document.If it has value then you will get the value for Reversal Reason in FB03.
    I think you have mistook selecting the Reversal Reason in the layout because there are 2 different Reversal Reason fields with the same name. So select the correct field (BKPF-STGRD) from the layout.
    Hope it solves.
    Regards
    Andrew

Maybe you are looking for