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.

Similar Messages

  • Multiple reason code in payment advice

    We have requirement to put multiple reason code at the time of cash application which we can do manually via f-28 and via payment advice
    F-28 is working fine but payment advice is not
    Steps
    Booked AR invoice of $1000
    Create payment advice of $1000 with below line item and reason code.
    AR Cr 200$ with reason code p1
    AR Cr 300$ with reason code p2
    AR Cr 400$ with reason code p3
    AR Cr 100$ with reason code p4
    Apply cash using payment advice.
    Issue
    The first line of payment advice is booked as on account AR Cr 200$ without reason code p1 and residual is created for  other 3 lines
    I am expecting the result should be that it should create residual for all the 4 lines with correct reason code.
    Expected result
    AR Cr 200$ with reason code p1
    AR Cr 300$ with reason code p2
    AR Cr 400$ with reason code p3
    AR Cr 100$ with
    Is it something i am missing at the time of creating payment advice or applying cash.
    I tested and had issue with the first item of payment advice. There should be something I missed in the payment advice creation .
    Thanks in advance for help.
    AB

    Hi,
    What you could possibly do if the reasons for rejection are similar for each lot is to create these combinations as UD codes and assign them to your selected set. Else you could record the reasons for the rejection in the long text and display this long text on your reporting.
    Regards,
    Roderick

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

  • Multiple Reason Code in UD

    During UD, is it possible to select more than one reason code for rejection.
    I wanted to reject inspection lot for more than 1 reason.
    How to do this?
    Rkumar

    Hi,
    What you could possibly do if the reasons for rejection are similar for each lot is to create these combinations as UD codes and assign them to your selected set. Else you could record the reasons for the rejection in the long text and display this long text on your reporting.
    Regards,
    Roderick

  • Write-off reason code limited to Amounts

    Hi All,
    We are on ecc 6.0. I want to know that is it possible to Link Write-off Reason code to amount and Roles.
    The scenario is like this. We have Multiple reason code configured in SAP
    Bank Charges A write-off reason code:
    Cash application specialist can write-off maximum amount of USD 500 for this reason code.
    If the amount is more than USD 500 it has to be written off by Role 2 which has the limit of more than USD 500.
    Similarly there is other write-off reason code B for which Cash application specialist has a Limit of USD 450000 while Role 2 has a Limit gretaer than USD 450000
    Assigning tolerance group to the user would not help as we have different limits for different reason codes.
    How can we configure such a scenario.Will we be able to achieve the same by validations/substitutions or we can define an user exit at f-28 level. Any other way to achieve the same.
    Thanks in advance
    Regard
    Nitin

    Thank you for your response.  I haven't been able to find a way to turn it off yet, but thought someone else might have found a way.

  • Return Reason Codes Generating Multiple Invoices

    When creating a credit memo in order entry, we often have product returned on an order for several reasons (i.e. one item is returned due to damage, another returned due to code date). When this occurs and the order is autoinvoiced, it creates a separate invoice for each reason code on the order.
    Is anyone aware of a set-up parameter that would eliminate an invoice being generated for each reason code, and allow the entire credit memo to only be one document?

    Hi priyeshosi ,
           If you use function modules start with GUI_* or  WS_* in your report , then you can't generate the spool.
    reason for this, Please check this link,
    http://www.sap-img.com/ab004.htm
    Regards,
    Selva M

  • 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

  • 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

  • CTI Not ready reason code 50010

    Hi ,
      We have a UCCE set up 8.0 . Agents automatically going to not ready state. When checked in report it shows Missed Tasks eroor code (50010). It is a default cisco reason code.Can anyone explain the exact reason for this issue .
    Thanks,
    Rahul

    Hi,
    the schema handbook says about this error code:
    The agent did not receive multiple consecutive calls routed to him/her. The system makes the agent Not Ready automatically so that additional calls are not routed to the agent. By default, the number of consecutive calls missed before the agent is made Not Ready is 2.
    This means the system was able to see these agents as available, it tried to send calls there, but for some reason the calls never reached the agent.
    A common mistake causing this issue is Device Target misconfiguration. Can you please check whether you have set up device target for agents, including labels for CUCM and IVR/VRU's?
    G.

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

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

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

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

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

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

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

  • Can Local Mode Cisco Mesh APs (1522/1552) be supported in a Multiple country code 5508 WLC?

    I've read previous discussions (i.e., "wlc 5508 multiple country codes + mesh ap") on this forum that stated Mesh APs can't be supported on a WLC set-up with more than one country code configured. If you have Outdoor APs which are set-up for local mode only, and not used in a Mesh wireless architecture (using Mesh Beacons), will this apply as well? I don't know if there are any caveats to this. Or if Cisco 1522/1552 APs can't be supported on a WLC using more than one country code period, regardless for how they are used, since they are considered Mesh APs. Another question, can a WLC support two regions (Region E and Region A), in a two country code assignment? I've read on the forum the downfalls for using more than one country code on a WLC, so understand that it will use the lowest common denominator settings (i.e., power, channels) for operation, so this isn't ideal.
    I want to stick to one controller using one country code only. This isn't something I want to do, but we had an issue with an order being processed for APs, which resulted in the wrong region APs being delivered by a vendor, and leadership is exploring alternative options. So, the above is worst case scenario planning if we can't swap the APs back for some legal reason, or if it takes too long to accomplish. We could always purchase a smaller WLC with a license size to support only the different region APs purchased if it comes to it.

    Hi,
    As per my experience, Normal APs(Local Mode) can work with multiple Country Code .
    WLC can support multiple country code but it's a bad idea to have it. Only common channel, power will allowed.
    Best is to buy a 2504WLC and use it.
    Regards
    Dont forget to rate helpful posts

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

Maybe you are looking for