Default Reason code in IT0008 during PA40 Actions

Hi,
My requiremnt is default the reason code in infotype 008 during actions in PA40. Itshould be same as the one the user selected during the initial Action screen.
For Eg: Suppose user is selected the '01' as reson code in the initial action screen during the Hiring action, then when IT0008 appears, reason code should be defaulted as '01'.
Pls share any idea to do it.

Hi,
I have got the user exit for poulating the data. But the problem is how to get values from the screen  for Infotype 0000  to screen for infotype 0008. Since the user may not save the data in 0000.So we can't read it from database.

Similar Messages

  • User exit to default reason code on MI07

    Hi MM Experts,
    Am an ABAPer and need your expert advice on this. For some reason I have been asked to default the reason code on MI07 screen with a certain value  as soon as  the user gets on the screen. I have not been able to find a user exit where I can default the value on MI07 for reason code.
    All MM experts can you please suggest a user exit where we can do this.
    Regards,
    Saket.

    Dear Saket Tiwari & Dëv Päträ
    I think I've given you the not clearing impression. i mean that T-Code OLMB is for "Inventory Management and Physical Inventory" configuration. (I think that you already know about it)
    1) Go to T-Code >> OLMB > Physical Inventory > Default Values for Physical Inventory  &
                                 OLMB > Physical Inventory > Field Selection for Physical Inventory
        Pre-settings for entering physical inventory documents
    Reason for inventory difference
         The default value you specify here is only displayed when you enter an inventory difference
         without reference to the corresponding document. But you can also change the default value.
    2) and You can control "Filed selection for Physical Inventory" such as MIGO filed selection.
    I think that before finding Technical Enhancement Spot, You can consider Configuration Control for your process.
    I hope that my options will be helpful for your project.
    Regards,
    Jeong, Yeong-Chul

  • Physical Inventory - MI07 default reason code

    Hi Friends,
              I config the default for reason code to count inventory ( Movementy Type 701/702) . And I do to create the transactions for physical inventory (MI01+MI04) and then I try to post difference qty by use MI07  but a reason code disappear in reason field. Pls. help me, what should I do to set up default a reason code in that field.  Thanks in advance
    Pland12

    go to OMJJ and maintian reason for movement type.
    It is not possiblle to  configure default reason for movement to a movement type

  • 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 for short payment received from Customers

    Hello
    We are on ECC 6.0 without application of any enhancement package.
    Requirement is to capture reasons of short payment received from customer and generate a report based on such reason codes.
    Reasons of short payment received could be - Adhoc payment; Excess billed; Tax deducted at source (TDS) on freight / service charges and Bank charges etc.
    Let me know relevant configuration required.
    Would reason codes be captured during incoming payment entry or customer account clearing?
    Thanks.
    Vimal, India

    Hi Vimal
    Following is the configuration for Reason code for customer payments. It can be short payment, over payment or discount not allowed.
    First step is to define reason code. You do this in Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Codes
    Define reason code , short text, long text and assign it to correspondence type. (please note correspondence type settings needs to be done first).  There is a column c which is Indicator: Charge off difference via separate account set this if you want to post the difference to seperate account during clearing customer open item.
    The second step is to define accounts for payment difference.
    Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Accounts for Payment Differences
    Assign G/L accounts against reason codes.
    The third step is Define Reason Code Conversion Version
    Financial Accounting (New >Accounts Receivable and Accounts Payable>Incoming Payments>Incoming Payments Global Settings>Overpayment/Underpayment>Define Reason Code Conversion Version
    In this step, you make the default settings you need for the manual incoming payment processing via payment advice notes. If differences between the payment advice item and the total of the allocated open items occur after selecting the open items, you can enter a reason code in the payment advice item. This represents the reason for the reduction of the payment amount specified by the paying person.
    Create version 001 and name for it.
    For correspondence type create or assign relevant form and print program in global settings> correspondence
    Once you have these settings you can insert appropriate reason code while clearing customer open item .
    You can print correspondence via T-ode F.62 on a monthly basis or wekly basis.
    Hope this helps.
    Thanks
    Sanjeev

  • Lockbox -Residual item - Reason code - FLB2

    Hi Gurus,
    I would appreciate if you could help me on the following.
    1. During lockbox processing (FLB2), will SAP create residual item for invoices with partial payments?
    2. If yes, will SAP populate reason code as well?
    3. Is there any configuration that need to be maintained for lockbox to create residual item and populate reason code?
    Thank you,

    Hi,
    1. During lock processing, whether lock box post residual or partial payments is controlled in configuration. In transaction code OBAY, defaul is residual, or you can choose partial payment.
    2. Lockbox will not populate reason code by default. In the BAI2 format, there is a field for reason code. Either you can work with the bank to populate that field. In our company we have a custom pre processing program that populate the field with a default reason code for all residual payments. During post processing, users change that to appropriate different reason codes depending on whether they going to write it off or keep it as a residual open itme on customer.
    3. You can control the population of reason code using substitution rules. For example any payment difference that is less than $50, you can write a substitution rule populate a certain reason code during posting. There is no standard configuration to do this.
    Hope this helps.

  • Whats the purpose of reason codes?

    Hi Experts,
    In many scenarios we add reason codes e.g. all the actions like terminations, new hire, rehire, change in position etc. Now our organization is adding a new reason code for termination action with reason code "termination due to LOA".  And they are calling meetings and stuff. Is it really that important of an issue. I was wondering reason code is there but is that this big of a deal. Please explain.
    Thanks,
    Rashmi

    One are is for reporting purposes.
    Also, based on the purpose code you can change which infogroup is called (feature).
    Then you don't need to maintain so many actions.
    Kirsten

  • Reason Code automatically defaulted in dispute created from FBL5N

    Hi Guys,
    Your help would be greatly appreciated here.
    We have a situation where ONLY for document type RV (Billing transfer), the reason code is defaulted to "AA" awaiting audit. This happens when I select a particular customer invoice from FBL5N and create a dispute from there. While creation of dispute, it does not ask me for any reason code entry and is not even there as an input field, but when I save this dispute and view it in the corresponding FI document, the reason code gets populated as AA in additional information tab of financial document.
    We want to change this reason code from AA to DI but we dont seem to find where to change this.
    I have revisited every possible configuration for dispute management and even checked "Define Default Values" in dispute management and we have not mentioned AA as default value anywhere. But we are not able to find it. Note: This is happening only for document type RV and for other doc types no reason code gets updated.
    Is there any configuration which I might have missed?
    Regards,
    Sweta

    Hi Mark,
    I was hoping you would respond to this considering your experience in this. I have checked for substitutions already but there is no such substitution which exists. Our technical team is trying to find out if it is hardcoded but they have not had any clue so far. Some routine would hardly be a case because the accounting document is already existing and after this the dispute is being created. i.e. the dispute is not getting created on the SD side nor it is getting created at the time of transfer of docs from SD to FI. It is purely during FI-Dispute link up after SD part is over. However, I will still tell my technical team to look into it.
    Regards,
    Sweta

  • NPS SQL missing reason-code in Server 2012 R2

    Hi
    It seems like several SQL fields in the 2012 R2 version of NPS logging has been removed.
    Amongst others the Reason-Code field.
    Most people only refer to log files to see why someone can't connect to the vpn server.
    In previous versions we had a web front end for an sql view that gave you the reason why the server denied access so that we do not need to give helpdesk personnel access to the log files and we also filter which operations vpn sessions they can see (via
    multiple vpn nps policies and then filter the sql view based on their permissions).
    Is there any way to restore the logging of this field to SQL as well as logging the source IP address of the request (our investors requires this and we get audited on it) with the issued IP (non DHCP). We are not allowed to run DHCP on this server since
    it is situated in the 3rd party datacenter.
    Regards
    Johan

    And this is what Server 2008R2 had parsed in the default stored procedure:
    FROM
    OPENXML(@idoc,
    '/Event')
    WITH
        Computer_Name
    nvarchar(255)
    './Computer-Name',
        Packet_Type
    int
    './Packet-Type',
        [User_Name]
    nvarchar(255)
    './User-Name',
        F_Q_User_Name
    nvarchar(255)
    './Fully-Qualifed-User-Name',
        Called_Station_Id
    nvarchar(255)
    './Called-Station-Id',
        Calling_Station_Id
    nvarchar(255)
    './Calling-Station-Id',
        Callback_Number
    nvarchar(255)
    './Callback-Number',
        Framed_IP_Address
    nvarchar(15)
    './Framed-IP-Address',
        NAS_Identifier
    nvarchar(255)
    './NAS-Identifier',
        NAS_IP_Address
    nvarchar(15)
    './NAS-IP-Address',
        NAS_Port
    int
    './NAS-Port',
        Client_Vendor
    int
    './Client-Vendor',
        Client_IP_Address
    nvarchar(15)
    './Client-IP-Address',
        Client_Friendly_Name
    nvarchar(255)
    './Client-Friendly-Name',
        Event_Timestamp
    datetime
    './Event-Timestamp',
        Port_Limit
    int
    './Port-Limit',
        NAS_Port_Type
    int
    './NAS-Port-Type',
        Connect_Info
    nvarchar(255)
    './Connect-Info',
        Framed_Protocol
    int
    './Framed-Protocol',
        Service_Type
    int
    './Service-Type',
        Authentication_Type
    int
    './Authentication-Type',
        NP_Policy_Name
    nvarchar(255)
    './NP-Policy-Name',
        Reason_Code
    int
    './Reason-Code',
        Class
    nvarchar(255)
    './Class',
    Session_Timeout
    int
    './Session-Timeout',
        Idle_Timeout
    int
    './Idle-Timeout',
        Termination_Action
    int
    './Termination-Action',
        EAP_Friendly_Name
    nvarchar(255)
    './EAP-Friendly-Name',
        Acct_Status_Type
    int
    './Acct-Status-Type',
        Acct_Delay_Time
    int
    './Acct-Delay-Time',
        Acct_Input_Octets
    int
    './Acct-Input-Octets',
        Acct_Output_Octets
    int
    './Acct-Output-Octets',
        Acct_Session_Id
    nvarchar(255)
    './Acct-Session-Id',
        Acct_Authentic
    int
    './Acct-Authentic',
        Acct_Session_Time
    int
    './Acct-Session-Time',
        Acct_Input_Packets
    int
    './Acct-Input-Packets',
        Acct_Output_Packets
    int
    './Acct-Output-Packets',
        Acct_Terminate_Cause
    int
    './Acct-Terminate-Cause',
        Acct_Multi_Session_Id
    nvarchar(255)
    './Acct-Multi-Session-Id',
        Acct_Link_Count
    int
    './Acct-Link-Count',
        Acct_Interim_Interval
    int
    './Acct-Interim-Interval',
        Tunnel_Type
    int
    './Tunnel-Type',
        Tunnel_Medium_Type
    int
    './Tunnel-Medium-Type',
        Tunnel_Client_Endpoint
    nvarchar(255)
    './Tunnel-Client-Endpt',
        Tunnel_Server_Endpoint
    nvarchar(255)
    './Tunnel-Server-Endpt',
        Acct_Tunnel_Connection
    nvarchar(255)
    './Acct-Tunnel-Connection',
        Tunnel_Pvt_Group_Id
    nvarchar(255)
    './Tunnel-Pvt-Group-Id',
        Tunnel_Assignment_Id
    nvarchar(255)
    './Tunnel-Assignment-Id',
        Tunnel_Preference
    int
    './Tunnel-Preference',
        MS_Acct_Auth_Type
    int
    './MS-Acct-Auth-Type',
        MS_Acct_EAP_Type
    int
    './MS-Acct-EAP-Type',
        MS_RAS_Version
    nvarchar(255)
    './MS-RAS-Version',
        MS_RAS_Vendor
    int
    './MS-RAS-Vendor',
        MS_CHAP_Error
    nvarchar(255)
    './MS-CHAP-Error',
        MS_CHAP_Domain
    nvarchar(255)
    './MS-CHAP-Domain',
    MS_MPPE_Encryption_Types
    int
    './MS-MPPE-Encryption-Types',
    MS_MPPE_Encryption_Policy
    int
    './MS-MPPE-Encryption-Policy',
        Proxy_Policy_Name
    nvarchar(255)
    './Proxy-Policy-Name',
        Provider_Type
    int
    './Provider-Type',
        Provider_Name
    nvarchar(255)
    './Provider-Name',
        Remote_Server_Address
    nvarchar(15)
    './Remote-Server-Address',
        MS_RAS_Client_Name
    nvarchar(255)
    './MS-RAS-Client-Name',
        MS_RAS_Client_Version
    nvarchar(255)
    './MS-RAS-Client-Version',
        NAP-specific information, available from NPS starting with Windows Server 2008.

  • Where to populate/update Reason code of BSEG in this BADI?

    Hello
    Under 'Dispute Management' our requirement is that when user creates a dispute case document (UDM_DISPUTE), user also inputs the 'Reason code', so this reason code should reflect on its associated accounting doc (BSEG-RSTGR), in this process i found one BADI - FDM_AR_DISP_COMPLETE with COMPLETE_DISPUTE method, this BADI is having code of pure OOPS, i don't know how to update the reason code, which structure i have to use, where should i set or populate the reason code? do i need to set any flags as well? how to declare and there by access the IMPORT structures data?  pls. let me know
    Thank you.

    Hi,
    In the IMG check the documentation for the following node:
    FI->AR & AP->SAP FI SCM->Disput Management Integration-> Customer Enhancemnets->Completion Dispute case.
    Copied the text below:
    Completion of Dispute Case
    Functionality
    You use the method COMPLETE_DISPUTE to include customer-specific BOR objects, attributes, or notes in the dispute case.
    Parameters
    I_ACTION
    The parameter I_ACTION specifies which action is carried out on a dispute case:
    I_ACTION = 1
    The disputed item is included in a new dispute case.
    I_ACTION = 2
    An existing dispute case is changed (by a clearing transaction).
    I_ACTION = 3
    The disputed item is triggered from an existing dispute case and transferred to a new dispute case (splitting a dispute case).
    I_ACTION = 4
    A dispute case is created in Dispute Management. Open items are then selected and added using the relevant functkon keys.
    T_DOCUMENTS
    This table of the line structure FDM_AR_DOCUMENTS contains the keys of the line items that are included in the dispute case or (for clearing transactions) reassigned to the dispute case record. The classification enables you to recognize the target nodes in the record:
    DISP... indicates disputed (open) items
    SOLV... resolved (cleared) items
    The table also specifies the change in value to the item that is carried out in the dispute case.
    T_OBJECTS
    This table of the line structure FDM_AR_OBJECTS contains the BOR keys of the linked objects in the dispute case but without the disputed or resolved line items.
    The business partner that is directly involved in the dispute case is entered under the clasification BUPA, the other objects are informative (INFO...), for example, the underlying FI invoice and SD billing document or the account statement.
    T_ATTRIBUTES
    This table of the line structure FDM_ATTRIBUTE contains the values of the dispute case attributes for the technical names. For a list of the technical names, see the fields of the database tables SCMG_T_CASE_ATTR and UDMCASEATTR00 in the Repository Information System (ABAP Dictionary) of Dispute Management.
    T_NOTES
    This table of the line structure TLINE contains the dispute case notes. Each line of text consists of the usual format column in SAPscript texts and the actual (unformatted) text.
    C_ADDITIONAL_OBJECTS
    The table C_ADDITIONAL_OBJECTS can be filld with the customer- specific additional BOR objects in the BAdI. Make sure that you have set up the derivation of the element type in Customizing for this BOR object type.
    C_ADDITIONAL_ATTRIBUTES
    Table C_ADDITIONAL_ATTRIBUTES can be filled with the customer- specific additional attributes in the BAdI. You can only set standard attributes if they have not already been defined by the system. For customer-specific attributes, you must add these to the attribute profile first.
    C_ADDITIONAL_NOTES
    Table C_ADDITIONAL_NOTES can be filled with customer-specific notes in the BAdI. They are added to the existing notes.
    Notes
    If you want to add BOR objects or attributes when you create a dispute case with user dialog, use the Business Add-In FDM_USER_SCREEN.
    If however, you want to add BOR objects, attributes, or notes derived from the FI data with no dialog when you create a dispute case, use this BAdI.
    When you change a dispute case (by clearing open items, I_ACTION = 2) only additional BOR objects are included in the dispute case. Attributes and notes are only transferred if the parameter E_EXTENDED_CHANGE_MODE has been set.
    When you create a dispute case from Dispute Management (I_ACTION = 4), only additional BOR objects and attributes are included in the dispute case.
    See also
    Kind regards,
    Robert
    PS. I have had no exposure to this BADi before but looking at it I would believe that you need to populate the T_ATTRIBUTES table with your reason code:
    ATTR_ID             'REASON_CODE'  -> type group FDMCO
    ATTR_VALUE    <your reason code value>
    XDELTA             'X'   indicating it is a change.
    PPS.  Re-reading your post maybe alos check the node in the IMG Customer Specific Default Values for Reason (FDM_AR_DEF_REASON) if this one serves your purpose.
    Edited by: RJ. Schamhart on May 31, 2011 4:30 PM

  • How to default "Reason" in a Business Activity transaction

    Hi experts,
    When I create a Business Activity, I am able to default Priority and Goal. When it comes to 'Reason' I am unable to default because there is no direct assignment in Trans type in Customizing header. We can assign only the Subject Profile for the Reason but not the reason code.
    Can anybody give some idea to default the reason code in the Activity document. It's an urgent req. Pl reply ASAP.
    Ranjan

    In customizing in the crm server there is no way of doing it without programming.
    But if you program, you should rather do it with the post processing framework (actions) than with the events: just create an event which is executed automatically (an always-true schedule condition and also an always-true start condition). This is calling then a self-written method which sets the reason via an CRM_ORDER_MAINTAIN. The reason code itself then can be passed as a container parameter.
    The benefit of this approach is that the predefinition can be enabled or disabled via customizing per transaction type.
    Kai

  • Tax Code Determination - default tax code for sales

    Under the tax code determination window i have set the default tax code for sales as VAT@4% and I have save it.  but when I open the sales quotation , order or any other sales document the tax code is not appeared.  what could be the reason?
    thanks
    SV Reddy

    Is ur "Determination Type" is 'Material Type'?
    FYI from Help file,
    When you enter item information in the marketing documents, system will check the item master data. If the item classification for the tax is:
    Material Item
    The tax code determination for material will start.
    Service Item
    The tax code determination for service will start.
    When you enter service information in the marketing documents, the tax code determination for service documents will start
    Regards,
    Dhana

  • NPS return Internal Error with Reason Code 1

    Hi,
    I am having an embedded client which is trying to authenticate using PEAP-MSCHAPv2 using NPS server 2008.
    NPS returns this error 
    Network Policy Server discarded the request for a user.
    Contact the Network Policy Server administrator for more information.
    User:
    Security ID:
    SANDBOX\deeps
    Account Name:
    deeps
    Account Domain:
    SANDBOX
    Fully Qualified Account Name:
    SANDBOX\deeps
    Client Machine:
    Security ID:
    NULL SID
    Account Name:
    Fully Qualified Account Name:
    OS-Version:
    Called Station Identifier:
    Calling Station Identifier:
    NAS:
    NAS IPv4 Address:
    xx.xx.xx.xx
    NAS IPv6 Address:
    NAS Identifier:
    NAS Port-Type:
    Wireless - Other
    NAS Port:
    5
    RADIUS Client:
    Client Friendly Name:
    Deeps_Canopy_AP
    Client IP Address:
    xx.xx.xx.xx
    Authentication Details:
    Connection Request Policy Name:
    deeps-test
    Network Policy Name:
    deeps-test
    Authentication Provider:
    Windows
    Authentication Server:
    USIL01PMPTST01.sandbox.com
    Authentication Type:
    EAP
    EAP Type:
    Account Session Identifier:
    Reason Code:
    1
    Reason:
    An internal error occurred. Check the system event log for additional information.
    This is not very helpful as it doesn't describe what went wrong and where.
    What else logs can I enable to debug further ? Attached are few logs from various components,
    Certificate,CRP and Network Policy are fine as they work fine with other standard client.
    Please help.
    Thanks,
    Netlogon logon and it return 0.
    4/20 05:31:32 [LOGON] [6480] SANDBOX: SamLogon: Network logon of SANDBOX\deeps from  Entered
    04/20 05:31:32 [LOGON] [6480] SANDBOX: SamLogon: Network logon of SANDBOX\deeps from  Returns 0x0
    Logs of NPS IN1504.log
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.407</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name
    data_type="1">deeps</User-Name><NAS-IP-Address data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU
    data_type="0">1020</Framed-MTU><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 25</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.407</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 25</Class><Session-Timeout data_type="0">30</Session-Timeout><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor
    data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name
    data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name
    data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.672</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 26</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.672</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 26</Class><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Session-Timeout
    data_type="0">30</Session-Timeout><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name
    data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.938</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 27</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:16.938</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 27</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:17.878</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 28</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:17.878</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 28</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.141</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 29</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.141</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 29</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.405</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 30</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.405</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 30</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.669</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 31</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:18.669</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 31</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:19.629</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 32</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 04:16:19.629</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 32</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:29.898</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><User-Name
    data_type="1">deeps</User-Name><NAS-IP-Address data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU
    data_type="0">1020</Framed-MTU><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 40</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:29.898</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 40</Class><Session-Timeout data_type="0">30</Session-Timeout><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor
    data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name
    data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name
    data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:30.176</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 41</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:30.176</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 41</Class><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Session-Timeout
    data_type="0">30</Session-Timeout><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name
    data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:30.441</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 42</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:30.441</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 42</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.383</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 43</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.383</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 43</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.655</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 44</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.655</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 44</Class><Session-Timeout data_type="0">30</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.920</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 45</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:31.920</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 45</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:32.184</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 46</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:32.184</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 46</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:32.458</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><NAS-IP-Address
    data_type="3">10.110.61.2</NAS-IP-Address><NAS-Port data_type="0">5</NAS-Port><NAS-Port-Type data_type="0">18</NAS-Port-Type><Framed-MTU data_type="0">1020</Framed-MTU><Client-IP-Address
    data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><User-Name data_type="1">deeps</User-Name><Proxy-Policy-Name
    data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Class
    data_type="1">311 1 10.120.133.1 04/20/2015 08:26:24 47</Class><Authentication-Type data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Quarantine-Update-Non-Compliant
    data_type="0">1</Quarantine-Update-Non-Compliant><Packet-Type data_type="0">1</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>
    <Event><Timestamp data_type="4">04/20/2015 05:31:32.458</Timestamp><Computer-Name data_type="1">USIL01PMPTST01</Computer-Name><Event-Source data_type="1">IAS</Event-Source><Class data_type="1">311
    1 10.120.133.1 04/20/2015 08:26:24 47</Class><Session-Timeout data_type="0">60</Session-Timeout><Client-IP-Address data_type="3">10.110.61.2</Client-IP-Address><Client-Vendor data_type="0">0</Client-Vendor><Client-Friendly-Name
    data_type="1">Deeps_Canopy_AP</Client-Friendly-Name><Quarantine-Update-Non-Compliant data_type="0">1</Quarantine-Update-Non-Compliant><Proxy-Policy-Name data_type="1">deeps-test</Proxy-Policy-Name><Provider-Type
    data_type="0">1</Provider-Type><SAM-Account-Name data_type="1">SANDBOX\deeps</SAM-Account-Name><Fully-Qualifed-User-Name data_type="1">SANDBOX\deeps</Fully-Qualifed-User-Name><Authentication-Type
    data_type="0">5</Authentication-Type><NP-Policy-Name data_type="1">deeps-test</NP-Policy-Name><Packet-Type data_type="0">11</Packet-Type><Reason-Code data_type="0">0</Reason-Code></Event>

    Hi chitsri,
    The log you provided above only contains the successful authentication.
    Because standard clients are working fine with NPS, I assume that this issue is caused by the embedded client.
    >>What else logs can I enable to debug further ?
    We may try to perform a network capture on the NPS server. Then find out what's the difference between the embedded client and standard clients.
    To download the the network monitor, please click the link below:
    http://www.microsoft.com/en-hk/download/details.aspx?id=4865
    If we can't find any hint from the capture data, you may contact Microsoft Customer Service and Support (CSS) via telephone so that a dedicated Support Professional can assist with your request.
    To obtain the phone numbers for specific technology request please take a look at the web site listed below:
    http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone#faq607
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • FBE1 multiple reason codes

    Dear Experts,
    In FBE1, We have two reason codes for deducting amount from bill amount. e.g. Bill correction amt and TDS. However, we have tried to enter it as new item. Along with payment amt we entered TDS and clicking on new item entered the correction amt and save the document. At the time of f-28, both deductible amount clubbed together and shown under TDS GL. That was wrong.
    Thanks in adv
    Ajeesh.s

    HI,
    1 From the list of intercompany transactions, select the transaction or transactions to which to assign a reason code and click Edit.
    Note: You can assign a reason code only to transactions with the MisMatched status.
    2 Take one of these actions:
    To assign a reason code to one transaction, from Reason Code, select a reason code.
    To assign a reason code to multiple transactions, enable the check boxes of all transactions, select Edit, then Set Reason Code, select a reason code and click Set.
    The reason code that you select is assigned to all the selected intercompany transactions.
    3 Click Save to save the changes.

  • Multiple reason codes in ICT HFM

    Dear all,
    We are implementing ICT Module for HFM 11.1.2.1 for one of our client. After the reconciliation by transaction ID and by Account, there have about hundreds of transactions that do not match and they have to enter reasons code.
    It seems that they have to enter reason codes transaction by transaction. Is it possible to select all the non matching transactions once and to assign the same reason code for all in one operation ?
    Thank you
    Best regards,
    Arnaud

    HI,
    1 From the list of intercompany transactions, select the transaction or transactions to which to assign a reason code and click Edit.
    Note: You can assign a reason code only to transactions with the MisMatched status.
    2 Take one of these actions:
    To assign a reason code to one transaction, from Reason Code, select a reason code.
    To assign a reason code to multiple transactions, enable the check boxes of all transactions, select Edit, then Set Reason Code, select a reason code and click Set.
    The reason code that you select is assigned to all the selected intercompany transactions.
    3 Click Save to save the changes.

Maybe you are looking for

  • I cannot put any of my itunes library on my new iPad

    This is a match/icloud issue.  I bought a new ipad mini for personal use as well as to play music in my fitness classes.  I did not buy a cellular capable ipad and I do not have wifi access at every gym I teach at.  So I need my device to actually ho

  • XML data extraction in 8.1.7

    Hi, I am new to xmlparser. I have the following xml file as CLOB in oracle 8.1.7 dB. I need to extract the data, based on the user request. If the user requests "Collateral Assets", then i have to extract the data group, related to that "Collateral A

  • Automatic syndication not working in SP06

    Does anyone have problems with automatic syndication in SP06 (version 5.5.62.58)? I upgraded our development system to SP06 few days ago. The syndication server didn't syndicate any changes. I also noticed that the next syndication time didn't get up

  • To detect if pen drive is connected or not in labview

    i want to detect if pen drive is connected or not using labview Stara Solved! Go to Solution.

  • Update one table based on condition from another table using date ranges

    Hello! I have two tables: DateRange (consists of ranges of dates): StartDate            FinishDate         Condition 2014-01-02       2014-01-03           true 2014-01-03       2014-01-13           false 2014-01-13       2014-01-14           true Cal