Reason Code in FBL3N

HI,
I have done a posting through F-02 and mentioned Reason Code at the time of entry.
When I check FBL3N, Reason code is not getting populated, what could be reason?
Regards,
Meenakshi

Hi,
In FBL3N, go to change lay out (Ctrl + F8), from the "Hidden Fields" section select "Reason Code" and move to left hand side > Click on Copy button. You will see Reason Code appearing in the screen.
Regards,
Ravi Kumar
Edited by: Ravi Kumar on Nov 7, 2008 1:28 PM

Similar Messages

  • 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

  • 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

  • FBL3N: reason code display

    Hi guys
    I'd like to add reason code to the selection screen of FBL3N.
    But it isn't displayed in the list available. While it is in the list available of FBL1N.
    How can I make it selectable on screen FBL3N?
    Should I config something in O7F8? how to do it?
    Thanks

    For some reason I can't display the link.
    I follow the steps in another thread:Add username field to dynamic selection in FBL1N
    1. Executed Transaction SE36
    2. Selected logical database KDF (for FBL1N)
    3. Then Menu -> Extras -> selection views
    4. Selected origins of the view SAP.
    5. Then i selected Table of BKPF, Table fields of USNAM and functional group as 03.
    6. Then saved the changes.
    and make the same changes as you gave me. But still doesn't work.
    In that thread, they finally mentioned notes 310886,1171560 which I don't have ID to logon......
    Please help me.

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

  • FBL1N not showing reversal reason codes

    Hi,
    We have made some reversals for AP invoices.  In BKPF table, I can see the reversal reason code in field STGRD.  I can also see the reversal reason code in FB03 document header.
    However, in FBL1N, I do not see anything under reason code column.  Is this the correct field?
    Are there any reports which show the list of reversed documents and the reversal reason codes?
    Thanks.

    Hi,
    Reason code, may be you are checking in FBL3N is(BSEG-RSTGR)
    Reason Code for Payments
        Key which represents a reason for payment differences. The keys can be
        freely defined in the system.
    Reversal reason code field is not available in the hidden fields list.
    In case if you want to add this field, please go to settings--special fields
    There you can add table and field name, this can be done in customizing client and can be transported to PRD client.
    Rgds
    Murali. N

  • Incoming payment by F-28: Reason code error while posting

    Hello everyone,
    I want to post Incoing Payment using F-28 net of TDS. I want the separate GL account to be picked up automatically for the difference when I enter the Reason Code 003.
    I did the following customization for the same.
    1. Financial Accounting> Accounts Receivable and Accounts Payable> Business Transactions>Incoimng Payments> Incoming Payments Global Settings>Overpayment/Underpayment> Define Reason Codes:- Here I selected the Indicator 'C' for reason code 003 which is for "Indicator: Charge off difference via separate account". The reason code 003 is for TDS Netted
    2. Below the Define Reason Code node, I selected the node 'Define Accounts for Payment Differences' . Selected the key ' Rules' and selected the checkbox 'Reason Code'. Then clicked on 'Accounts' and enetered the desired GL account against the reason code '003'.
    After doing the above customization I posted the Incoming payment using T code F-28. I entered the difference in the field 'Difference Posting'. Then entered reason code '003' which is for 'TDS netted' in the field 'Reason Code'. Now, I am getting the follwoing error.
    Reason codes with automatic charge-off are not permitted here
    Message no. F5605
    Diagnosis
    The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose.  Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
    System Response
    The reason code entered is not accepted.
    Procedure
    You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.
    How can I proceed ahead?
    Thanks and Regards,
    Pradnya

    Hi Saulo,
    Thanks for ur reply.
    I had alreay done the config in OBXL and OBBE. Only thing I wanted to know is while posting Incoming Payment by F-28, how to use this reason code.
    Ur reply was a gr8 help for me.
    Regards,
    Pradnya

  • Clearing Payment to a G/L account set up in Reason Code

    I am having a problem posting an overpayment/underpayment to a G/L account using a reason code. What I am attempting to do is, using F-28, have the remainder of an underpayment post to a G/L account attached to the reason codes. What I need to have work is that in F-28 I do not want to have to enter any data on what the residual amount is, it should just take whatever is not paid and apply it to the G/L account tied to the reason code.  I have set 3 new reason codes in OBBE to test different possibilities with the checkboxes in that transaction, and have attached each of the reason codes to accounts using OBXL. What is happening now is that when I enter a short pay amount for an invoice and I enter a reason code in the RCd field in the residual tab - I hit save and it seems to try to attach the remaining amount to an account that is currently tied to a blank reason code in our setup in OBXL. I would think that since I am placing a code in the RCD field, that it would use the account tied to that. I have also tried to use the reason code field below, but encounter the same results or, with one of my codes that has the "charge off difference via separate account" checkbox checked, it will not allow that code in that field below.
    There must be a way to take the shortpay amoun,t and without entering the residual amount anywhere, use the G/L account tied to the reason code to post the remainder to. Can anybody help on what I may need to do to get this to work?
    Thanks -
    PS. This is not a tolerance issue as I have set the tolerances for both the customer and the user high enough to allow under/overpayments.

    No... this is SAP standard.... if you are treating them as residual payment and the GL is seperate than the small diff GL we have to enter the amount there..... as system cannot understand whats the differnece when we dont put the amount there......
    we can always see the field NOT ASSIGNED in the bootom.. it is just the matter of copy paste for the user.... it has to come thro user discipline.... i dont see a standard sap way of doing it,....

  • Two deductions for invoice with same reason code posted as one line item

    Hi
    We have a scenario wherein we are taking two or more deductions on the same invoice and are using the same reason code which have a setting of charge off.
    SAP system displays the FI posting with same reason codes with charge off setting as one line item.
    However we want the FI Posting to display separate line items per deduction and not combine amounts of deductions based on same reason code with charge off setting.
    Any comments are appreciated.
    Edited by: Kirti Bhardwaj on Jul 24, 2011 9:46 AM

    Hi,
    you can use different reason codes in distribute differences screen once you have fist selected one reason code for one invoice.

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

  • Is there a way to hide some reason codes in dispute management without deleting?

    Within SAP Dispute management (UDM_DISPUTE) we would like to remove some of the available reason codes in the drop down on the search screen and available to assign drop down, but not physically delete them.  Is there a way to do this? 
    I know if I physically delete them out of the Reason code list (SPRO -> FSCM -> dispute management -> Dispute Case Processing -> Case types -> Create Values for Attribute "Reason") then if an old dispute case that used that reason code is displayed, the four digit number code will be displayed rather than the description.  So we would prefer to not physically delete the code / description from the reason codes but somehow make them non-display, or inactive. 
    Any thoughts on this?

    Hello Stephen,
    you may consider the functionality "personal list", putting all valid reason codes in and leaving out those you do not want to show. Maybe your Authorisation / Security Team can also help you performing this exercise for all affected users at once.
    Regards,
    Christoph

  • Error: Reason codes with automatic charge-off are not permitted here(F-28)

    Hi All
    I creted a reason code in obxl t-code and assigned a gl code in OBXL transaction code, But when I am trying to clear a payment with reason code in F-28, System is throwing the following error..Can some one tell me why i am getting this error?
    Reason codes with automatic charge-off are not permitted here
    Message no. F5605
    Diagnosis
    The reason code entered is designed to ensure that the payment difference amount is posted to an account specially set up for this purpose.  Postings of this nature usually require additional specifications (e.g. tax code, business area). If the difference stems from a single open item, the necessary specifications can be taken from that item. In the case that led to this error message, however, the difference does not stem soley from one item, which means that this method cannot be used.
    System Response
    The reason code entered is not accepted.
    Procedure
    You can either select a different reason code, which would create a new open item for the customer or vendor OR write off the difference using the function Charge off diff.. This function either takes you into a pre-configured account assignment model or into the document overview. From here you can enter the required difference postings.

    Hi Venkata,
    It seems while entering the payment (partial payment / residual items) ... you are clearing multiple items with differences. (e.g. if the difference amount is $30, then may the difference consists of two invoices underpaid by $15 each). In this scenario, F-28 doesn't know which additional account assignment fields should be picked up ... hence the error.
    First of all, to validate that this indeed is the case, try clearing a payment with the same reason code where difference can be attributed to a single invoice. If you still get an error, then there is some other problem.
    Then, to take care of a the business scenario where the difference can indeed be due to multiple documents, select "charge off difference" option and create an entry to post the difference as necessary.
    HTH,
    Manish Patel
    Sr. SAP Solutions Consultant

  • Incoming Payment with Underpayment/Overpayment in F-28 with reason code

    Hi All,
    While making a incoming payment with overpayment / underpayment in F-28, I am getting an error u2018Reason codes with automatic charge-off are not permitted here u2018. The reason code is defined with charge off checked and the account for differences is defined for the same.
    Please advice
    Thanks

    Please check "Indicator: Charge off difference via separate account" in reason code settings (TCode OBBE). If this indicator is set against the reason code that you are using, you will getting the error.
    What you can do is either use different reason code or in residual items tab you can specify the reason code with residual items.
    Thanks,
    Sukhbold
    Edited by: Sukhbold Altanbat on Oct 13, 2011 7:47 AM

  • Reason code SE is not defined

    I have created credit memo request in VA01.
    i have generate biling documnet (credit memo) VF01 but accounting document not generate.
    it is giving error message when i am trying to release manuvally.
    "Reason code SE is not defined"
    Message no. F5596.
    please help what can i do for posting accounting document.
    Thx
    k.Satish

    HI,
    In credit memo request VA02 mode please enter reason code for that document and then try to recreate credit memo..
    Because in your case reason code is mandatory and it is not maintained in credit memo request thats why it is not copied into creidt memo. So please maintain that and then check once agian...
    Regards
    sankar

  • 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

Maybe you are looking for

  • Help with 2 simultaneous internal users trying to VPN (Cisco s/w) to extern

    Hello all, We are a small office running Small Business Server 2003 - which means we're running the ISA 2004 firewall. An external company has provided us with Cisco VPN software (ver403a) to access their network/secure web site. A single user has be

  • Oracle 10g Dataguard Error

    Hi, I created a standby database using RMAN backups. I have followed all the steps correctly because the standby database does come up without any errors when I give the command 'alter database mount standby database;' or 'alter database recover mana

  • Leading zeros in SAP ME materials that come from SAP ERP

    Hello! When materials are transfered from the SAP ERP side via MII to SAP ME it can be observed that material numbers have leading zeros. For example a material number is created in SAP ME like 0000000123456 instead of 123456. I think this behaviour

  • Mac to mac networking

    ok, I got my networking working (2 macs). Now I am using the mac mini files as a hard drive from my emac. How do I turn off the mac mini when I am finished. I have no monitor. Can I still just push the power button for 5 sec to turn it off? thanks

  • How do i clear network error 3212 when attempting to connect

    I just downloaded iTunes to my new laptop with windows 7.  when I attempt to connect to iStore or login. i get a newwork error 3212 saying I have a netowork error and need to establish a connection.   I definately have connectivity.