BAPI_ACC_DOCUMENT_POST Update reason code on BSEG

Is the only way to update the reason code (BSEG-RSTGR) using the above bapi is by using the extension1 .
Tnks

I spent the last two days getting this working. It is really difficult but I got there in the end.
In the function module BAPI_ACC_DOCUMENT_POST in routine INIT_GLOBALS the program searches for an implementation of ACC_DOCUMENT. The filter is the document type which for this BAPI is BKPFF (two letter F's).
Later in routine CALL_BADI the methdo CHANGE is called of the implementation.
I copied the sample code from CL_EXM_IM_ACC+DOCUMENT into my Z BADI which I wittily called ZCL_IM_ACC_DOCUMENT. As I am changing the value of a field already in ACCIT I can leave the code exactly as is.
I then created my own structure (has to be all character fields regardless of the target field type in ACCIT), and filled up the extension table as follows just before calling the BAPI.
DATA: lt_extension2     TYPE STANDARD TABLE OF bapiparex
                                   WITH HEADER LINE,
          ls_extension2     TYPE zzbank_bapi_structure.
CLEAR ls_extension2.
        ls_extension2-posnr = 2.                  "Second Item
        ls_extension2-rebzg = gt_details-vbeln_vf."Invoice
        ls_extension2-rebzt = 'Z'.                "It's an invoice
        ls_extension2-rebzz = 1.                  "Item
        SELECT SINGLE gjahr FROM bkpf
          INTO ls_extension2-rebzj
          WHERE bukrs = gt_header-bukrs
          AND   belnr = gt_details-vbeln_vf.
The BAPI chooses ir's own posting keys, which we do not like
        IF gt_details-shkzg = 'S'."Normal
          ls_extension2-bschl = '15'."Incoming Customer Payment
        ELSE.
          ls_extension2-bschl = '05'."Outgoing Customer Payment
        ENDIF.
        lt_extension2-structure = 'ZZBANK_BAPI_STRUCTURE'.
        lt_extension2-valuepart1 = ls_extension2.
        APPEND lt_extension2.
The trick with BADIS is not just to activate the class but also the implemenation. I forget the second part every time.
Hope this helps.
Cheersy Cheers
Paul

Similar Messages

  • 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

  • Reason code display FBL3N

    Dear Experts,
    We are updating reason codes while posting FI documents, but reason code details are not displaying in FBL3N transaction, we changed the layout but still reason code details are not appearing. Please let me know how get these details in FBL3N transaction code.
    Other wise any alternative transaction is available to display these details for each document?
    Regards
    Babu.

    Hello,
    You should add standard fields to FBL*N report with using customizing step below.
    SPRO -> Financial Accounting (New) -> General Ledger Accounting (New) -> Master Data -> G/L Accounts -> Line Items -> Define Special Fields for Line Item Display
    Otherwise, you can add additional fields with using business transaction event 00001650.
    But if you want to activate addition operation, you must run RFPOSXEXTEND program via SE38 transaction. This program generate structure for FBL*N reports.
    Regards,
    Burak

  • OTL: Timecard Audit Template require reason code for all transaction.

    We are currently using OTL with CLA template with interface time entry from external system.
    When monthly time entry interfaced into OTL each employee have to review and update their time and submit to manager, but when process to audit template they has been forced to update reason code for all transactions.
    We suppose to update the reason code only for the modified transactions. Please help me.
    Nonny.

    nondhasid,
    If you are not modifying those records which are asking for a reason field to be filled, then it should be coming from the Late setup. Check the CLA setup.
    --Shiv                                                                                                                                                                                                                                                                                                                                                                       

  • How to update Tr code FB02   and update the field reference key1 (bseg-xref

    Can any body
    help me how to update   Tr code   fb02
    and  update the field  reference  key1 (bseg-xref1)  with the interest amount
    calculated.
    Below i have  written My  program  flow logic
    The program should read the open items i.e debit items in the customer account,
    Based on the  invoice date and customer payment terms  calculate the due date and then the  interest should be  calculated on that item based on the due date.
    Use the  transaction  fb02  and update the field  reference  key 1 (BSEG-xref1)
    with the interest amount calculated
    Only  consider  customers whose  interest indicator  knb1-vzskz = 'vk'.
    Interest is to be  calculated for every  30  days
    at the rate of  1% .please see example below.
    Document date is 01.01.2007
    for amount  1000SGD   payment  term  7  days
    It becomes  due  on  08.01.2007
    until  06.02.2007 you should not  consider  for calculation of interest
    SGD  on   7.02.2007 run you can consider this  item for interest calculation

    Hi Robert,
    Thanks for answering.
    I am looking at Ref 2 should flow automatically to clearing document from the accounitng document for billing.
    Ex: Billing document is created and accounted. Ref 2 is AB
    Now when receipt is accounted for this biling document this AB should flow automatically to Ref 2 field.
    Thanks
    NNS.

  • Nowhere can input reason code in function BAPI_ACC_DOCUMENT_POST

    Hi.....
    Field Reason code is a required field for a G/L account,But it seems that nowhere can input it in function BAPI_ACC_DOCUMENT_POST's table parameter ACCOUNTGL.Thus I can use this function to create Accounting Document .....How can I solve it ? 
    Thanks

    Why do you put something in the 'extension1' segment ?
    What sort of doc do u post ?
    Message was edited by: Erwan LE BRUN

  • Validation at line item level for F-32 to input Reason code

    Hi Gurus,
    I would like to write a validation / substitution for F-32 transaction code where in the Reason code field need to be mandatory field (With out input in to this field value the user should not come out of the transaction)
    Please guide me how to write validation with out user exit
    Thanks

    Hi Suresh,
    I guess the idea of MEENAKSH is good, perhaps you have an error in the Tcode, because in table BKPF the Tcode stored is FB1D and not F-32  :
    So put the following in GGB0 and check again :
    Prerequisite :
    BKPF-TCODE = FB1D
    Check :
    BSEG-RSTGR <> '  '
    Message :
    Error : Reason code required
    in the other hand, you can active a trace in GGB0 (Menu > Extras > Activate trace) to see what's the exactly the error
    So it's not a question of screen.
    Regards.

  • How to post reason code/movement type from MM to FI document?

    Have had a request from our Finance guy here that when a movement is posted in MM (eg a scrapping), the reason code and movement type are to go onto the FI document when the movement is posted to the GL accounts. These values are to be viewed from FBL3N.
    He thinks it might need to be done with substitutions but I have had no experience in this area and he has no idea how to go about it. I have extended the COBL structure using OKX3 which has put the field into BSEG but have no idea how to go about doing the substitution or which exit to use. Inaddition in SAP standard, MSEG passes the movememnt type tyo COBL field BWART but then this seems to get voided.
    Can anyone help me?
    Regards
    Larissa Maryniuk

    Hi Larissa,
    Please go through with this below link. You can easily understand about Substitutions.
    http://techbays.files.wordpress.com/2008/08/sap-tip-how-to-use-substitutions-lakshman-tandra1.pdf
    Best Regards,
    Mohan.

  • FBL5N t code and BSEG table is showing wrong contract number

    Hi,
    The proces flow is contract number>sales order>DMR-->Invoice
    Now when I am checking the VBFA table it's showing correct contract number against invoices but FBL5N t code and BSEG table are showing wrong contract numbers.
    Why FBL5N and BSEG table is showing wrong contract number?
    Currently we are using one enhancement and user exit is used to incorporate one customized field as identifier for bill type.
    1. During the billing document release to accounting VFX3, The user exit triggering and it is update the customized fields and Net settlement indicator.
    2. Using the Invoice number, get the fields VGBEL(Document number of the reference document) and VGPOS (Item number of the reference item) from VBRP and read table VBAP with VBELN and POSNR, to get DMR number (Sales Document) that created for the Invoice.
    3. Use fields VGBEL and VGPOS on table VBAP to get the sale order number.
    4. By using the Sales order number, get the Distribution channel to update Net indicator field
    In accounting table BSEG-UZAWE = JF must be updated on the customer line.
    5. Retrieve the sale order number and item level to get customized field from table VBAP
    Any pointers.
    Thanks
    Ashu

    Hi Reazuddin,
    Thanks for your reply,
    I am concercerned about BSEG table and using user exit EXIT_SAPLV60B_008 to post the document in FI.
    Now in we have enhanced this user exit  for contracts and included in this way.
      SELECT SINGLE ZZ_CONTRACT FROM VBAK INTO (LC_CONTRACT) WHERE VBELN EQ cvbrp-vgbel.
    Endloop.
    *Moving the values to final accounting table
    loop at xaccit.
    xaccit-vertn = lc_contract.
    xaccit-VBEL2 = xaccit-AUBEL.
    xaccit-xref3 = lc_vbel2.
    MODIFY xaccit .
    ENDLOOP.
    Clear: lc_contract,lc_vgbel,lc_vgpos,lc_vbel2.
    But I am getting correct data when checked other clients( development and quality), this problem I am getting in production.
    Do I need to ask the ABAP'er to debug this enhancement in production?
    Thanks
    Ashutosh

  • 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

  • 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]

  • Reason code and payment terms

    Hi Gurus,
    Is there any link between reason codes and payment terms ?
    When I am posting a document or creating any residual and assign a reason code, it automatically assign a payment term and which i am unable to change.
    any advice, suggestion would be appreciated.
    Thanks.

    Hi,
    There is no direct link between Reason Code and Payment terms.
    Reason code is the key actually specify the reason for payment difference it can be any reason like DISPUTE - TAX, DISPUTE - IN PRICE, DISPUTE EX - QTY and so on and those we can define.
    Where as Payment Term are used to define
    1. Base line date for due date calculation
    2. Cash discount periods
    3. Cash discount percentage rated
    And the Payment Term which is coming by default while posting the document is the same one which has been defined in your master data for that customer. So I would suggest you check the master for that customer and surely you will find the same payment term updated there as well.
    But it not means that you can not changed Payment term while creating or posting document, you change it and it will supersede you master data payment term.
    Hope this will answer your query.
    Regards,
    Abhinav Sharma

  • 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

  • Bapi or function module to update rstgr field in bseg table

    what is the bapi or function module used to update the fields in bseg table particularly "rstgr" field?

    Hi,
    Use Bapi
    BAPI_ACC_DOCUMENT_POST
    Regards,
    Prashant

  • URGENT: Reason code in Material document

    Dear all,
    We processed a thousand 551 movements without reason code.
    The user strongly NEEDs that field populated.
    I tried to modified the document with MB02 but, the field 'reason code'  does not appear.
    I looked in configuration trying to find a way to open it for input when process with MB02 and I did not find it.
    This has BIG implications in our company and the user is thinking in updating directly MSEG with the reason code.
    Does any body know how to open the field in MB02  OR if there is any implication in updating field Reason code (MSEG-GRUND) directly in the database?
    Thank you.
    Monica.

    Monica,
    I don't think it's possible via MB02. In general, changes to a material document are very limited (except a few text fields). I would suggest to cancel the movements and redo them correctly instead of doing a direct table update.
    If the volume is high, you should try to use LSMW or similar methods. Have a look into BAPI_GOODSMVT_CANCEL and BAPI_GOODSMVT_CREATE.
    Hope this helps.
    H Narayan

Maybe you are looking for