VPN: Reason Code -5204?

I have installed a VPN Tunnel on my 5230. It works when I am using the browser.
But TIVI (www.tivi.com) does not work. It isn't registering to the sip server. In the VPN protocol are a lot off error massages like this:
"Warning: Dropped data due to VPN policy, source address '169.254.2.1', reason code -5204"
What is going wrong there? Please explain this to me.
Marcus

Hi!
I was able able to solve te problem.
I installed the VPN Client and ignored the error.
Then I created a new destination 'Intranet' in the network destination. To create a new destination you have to open the network destination menu. In the options you should have a menu item administer. With this you can create the new network destination.

Similar Messages

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.

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

MR8M creation of new reason code and editable description

HI,
We want to create new Reason code in MR8M transaction. After creation of reason we want to editable reason description when we select this.
Please suggest me.
Thanks
Shital

Hi Shital,
You can insert the reason code in table T041C, from SPRO -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Adjustment Posting/Reversal -> Define Reasons for Reversal...
but you cannot change everytime the description in MR8M
Thanx & Regards
Mauro

Scrap Movement type + reason code - different GL account ( OBYC)

Hi Experts -
I have an issue in hand which explains as below ...
User wants to post Scrap movement of different reason to post to different GL account with T.Code OBYC. SAP has a movement type 561 for Scrap related account determination. In the standard SAP situation, we can post to ONLY ONE GL account for Scrap using 561 movement type. But my situation is like this - A material can be scrapped due to different reason (reason code) and based on the reason (I use reason code A - E), I want to post it to different GL account.
In standard SAP , we can define the account determination (OBYC) for scrap with ONLY ONE GL account as follows ...
Val. modifier - Plant 1
Val Class - 1111
General/Account Modifier - VNG (mapped to 561)
GL Account - Z123456
But my scenario is like this ....
561 + reason code A should post to Z123456
561 + reason code B should post to Z999999
561 + reason code C should post to Z111111
I was thinking for creating new General modifiers for different codes (A - E). Please suggest me if that solution is feasible else provide me an efficient solution.
Thanks much.
Regards,
Jude

HI
Defining new general modifiers is an option.
Alternatively you can look at defining a new substitution rule. The substitution rule will only hold good if the GL Account for scrap is not used anywhere else. (This should ideally be the case if it a scrap account).
In the substitution rules you can check for the particular scrap account number and then depending on your reason code, you can change the GL account before it is posted to.
Regards

Limiting or control for Residual payment with reason codes

Hi FI Gurus,
When we are received or making payment to customer or vendor, sometimes we need to clear the invoice by receiving or making payments with small differences through residual payment. Is there any control for limiting residual payment.
Lets have an example
invoice posted for 1000
customer dr 1000
sales       cr 1000
Partial payment recd 500
cash/bank dr 500
customer cr   500
final payment received 350 and balanace amount adjusted with residual payment by defining reason code like rounding off difference. So in this case accounting entry will be
customer cr 350
rounding off diff 150
cash/bank 500
being final payment agaisnt invoice
My question:   Is there any way to restrict the residual payment like 10% or 20% of total invoice i.e. 100 or 200 and not more than 20% ? other wise sometime user may adjust any amount may be 100000 through this way by putting the same reason code, which is not fair.
I checked SPRO setting but i did not get anyt setting relating to above case.
If any body know, please let me know? Thanks in advance
Regards,
Prakash

Hi Lawerance,
Thanks for reply.
But I am looking for amount adjusted through residual with reason code. I dont think there is any limitation or control in the SPRO standard setting. Tolerance is preventing user to post document for more than a specific amount. But my question is something different.
I want to control the user for adjusting amount from residual tab with selecting reason code. In other words user should not adjust more than some limit with residual payment by selecting reason codes. Thanks.
Regards,
Prakash

Reason code with post with different GL account

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

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

VPN: Reason Code -5204?

Similar Messages

Maybe you are looking for