Reason Code Functionality

Dear All,
Experts.
I want to know about Reason Code. What is practical functionality of reason code ?
Here is my understanding as follows :-
Suppose I am posting one bill of Rs. 12,000/- against that I am receiving Rs. 14,000/-.
So if I use reason code,  will my entry & effect like this ?
Bank A/c Dr 14,000
customer A/c Cr 12,000
Exchange Gain A/c Cr 2,000
( Being exchange gain of Rs 2,000/- )
For this functionality Reason code is used ?
1 ) In addition to this will Rs 2,000 generate one more residual line item in customer account ? 2 ) or account will be clear?
3 ) Where I can link the reason codes ? 4 ) It is at customer master level or document level  5 ) Reason code is Manual assignment or Automatic assignment ?
Experts your help on this will be great.
Regards,
Sharvari Joshi.

Dear,
Chintan.
Thank you again for focusing on my questions. Can I link the reason code to customer while taking the payment from F-28 ? 
Or at any other T.code I need to use for using Reason Code ?
1) Define reasons Codes
2) Define accounts for payment differences
3) Define std reason code for clearing w/payment advice notes.
4) Define Reason code for conversion version
5) Define conversion of payment differences reason code.
are the only steps to configure reason codes ?
Your help on this will be great.
Regards,
Sharvari Joshi.

Similar Messages

  • Reason Code Functionality in document level

    Dear Sir,
    How to bring Reason codes functionality at document level while posting Debit Note or Credit Note in MIRO. 
    Syam

    Hello Syam,
    What Reason code are you referring to  ? Due you mean to say blocking reason ?
    regards
    pbb

  • Nowhere can input reason code in function BAPI_ACC_DOCUMENT_POST

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

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

  • Function Db6pmcf which cannot be accessed.Reason code:5 error in DB6COCKPIT

    Hi,
    We have 4.6C systems running on AIX 5.3 and DB2. recently I updated the kernel from patch level 2225 to 2307. (Both OS and DB are 64 bit) The DEV and QAS systems were running successfully but I got a problem in PRd systems. I am having error in DB6COCKPIT. I am pasting the exact error here.
    -f 14 -p  0 -c U
    External program terminated with errors
    CLI error
    ERRORMESSAGE: Error -444 in dmdb6rd5.c(752):
    DB6CliFetch(): [IBM][CLI Driver][DB2/AIX64] SQL0444N  Routine
    "DB6PMCF" (specific name "SQL070920161003900") is implemented with
    code in library or path "/usr/sap/PRD/SYS/exe/run/db6pmudf", function
    "Db6pmcf" which cannot be accessed.  Reason code: "5".
    SQLSTATE=42724
    External program terminated with exit code 31
    -f 17 -p  0 -c U -o env
    External program terminated with errors
    CLI error
    ERRORMESSAGE: Error -444 in dmdb6rd5.c(438):
    DB6CliFetch(): [IBM][CLI Driver][DB2/AIX64] SQL0444N  Routine
    "DB6PM_LST" (specific name "SQL070920161002400") is implemented with
    code in library or path "...p/PRD/SYS/exe/run/db6pmudf", function
    "Db6pm_lst" which cannot be accessed.  Reason code: "5".
    SQLSTATE=42724
    External program terminated with exit code 31
    Please reply me back ASAP. This is very urgent.

    This issue was solved.

  • 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

  • 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

  • Problem: Not able to change Signature field reason code Dynamically using signatureSetSeedValue

    Problem: Not able to change Signature Settings Dynamically.  
    What I want: Need to change the Signature Field Reason code Dynamically upon selecting Radio Button.
    Here is My Code:  
    var mydoc = xfa.resolveNode("FormData.P3_443.signature[2].ePadSignatureField3");
    mydoc.signatureSetSeedValue(
    reasons: ["Advisor"],
    flags: 8
    Error Message:
    TypeError: mydoc.signatureSetSeedValue is not a function
    9:XFA:FormData[0]:P3_443[0]:signature[2]:ePadSignatureField3[0]:validate'
       Source Code: Acrobat Code for Signature.
       // Obtain the signature field object:
    var f = this.getField("mySigFieldName");
    f.signatureSetSeedValue(
    { reasons: ["This is a reason", "This is a better reason"],
    flags: 8

    Problem: Not able to change Signature Settings Dynamically.  
    What I want: Need to change the Signature Field Reason code Dynamically upon selecting Radio Button.
    Here is My Code:  
    var mydoc = xfa.resolveNode("FormData.P3_443.signature[2].ePadSignatureField3");
    mydoc.signatureSetSeedValue(
    reasons: ["Advisor"],
    flags: 8
    Error Message:
    TypeError: mydoc.signatureSetSeedValue is not a function
    9:XFA:FormData[0]:P3_443[0]:signature[2]:ePadSignatureField3[0]:validate'
       Source Code: Acrobat Code for Signature.
       // Obtain the signature field object:
    var f = this.getField("mySigFieldName");
    f.signatureSetSeedValue(
    { reasons: ["This is a reason", "This is a better reason"],
    flags: 8

  • Reason code in automatic payment

    Hi
    Please advice how to add the reason code in change line item while editing the proposal in automatic payment run.
    Thank you

    Hi,
    the reason code is normally used for payments with differences to the invoice amount. In the payment run the invoice would normally be paid fully except you have made some further reduction postings to that invoice so you would pay a reduced amount by selecting the invoice and the credit memos relating to it.
    But there is no option to choose this in F110.
    If you want to pay a reduced amount and have a reason code consider using the manual payment functions (F-53 / F-58).
    Hope this helps
    Hein

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

  • BAPI_ACC_DOCUMENT_POST Update reason code on BSEG

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

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

  • Extending resource status and reason code category

    Hi Experts,
    I have a couple of questions regarding the extensibility of status and reason codes in ME15.0 in the context of machine integration:
    1. Is it save to add new status fields (records) in WIP.STATUS for STATUS_GROUP="RESOURCE"? Is there any impact, if a resource doesn't match one of the predefined status values?
    2. The "logResourceStatusChanged" service creates entries in WIP.RESOURCE_TIME_LOG but not in WIP.RESRCE. That way, it is possible to get different status values in both tables at a given time. Do you see any negative impact resulting from this data inconsistency?
    The service "ChangeResourceStatusRequest" is not suitable in our case, since it doesn't provide a timestamp as input parameter for the status change. And even if it would, the prevention of a "sfc complete" when the status is "unscheduled down" is inconvenient for our customer. The scenario is, that the customer wants to complete the quantity produced until the machine broke down (assume lot production).
    3. Is it possible to add new "categories" in addition to the predefined values in WIP.REASON _CODE? What is the impact?
    regards,
    Georg

    Hi Georg,
    I cannot give you a precise yes/no answer - so this is just to share some info.
    - I've heard about some customer who implemented custom statuses. When a new status simply was added in the database, it did not affect a core functionality. But I do not know what happens if this status is assigned to a resource and then a core fucntionality is triggered. There might be some validation which could fail. But it is easier to test specific cases as how you are going to use SAP ME, and I doubt any developer will be happy to run a full analysis of code to answer your question.
    - The new statuses need to be considered for loading via IDAT and adding into LocaleSpecificText properties file.
    - As to custom categories of reason codes, I guess there are only few places where system behavior is tightly connected to specific predefined reason codes. So, I'm inclined to believe that adding reason codes and categories will not harm.
    Regards,
    Sergiy

  • Reason Codes not displaying when performing emergency access management(SPM

    Hello guru,
    I am experiencing a little problem when using superuser privilege management (emergency access) functionality in AC 10.0.
    My problem is that the reason codes created in the AC system via the reason code link in the workcenter does not appear as drop down for me when I click on the logon button in the initial screen displayed in transaction SPM_GRAC.
    Suffice to say that i do not have any reason code to pick from in the drop down for superuser privilege management in the AC system when i logon with the firefighter user to perform SPM.
    Please help me out with your suggestions.
    Thanks

    Hello guru,
    I am experiencing a little problem when using superuser privilege management (emergency access) functionality in AC 10.0.
    My problem is that the reason codes created in the AC system via the reason code link in the workcenter does not appear as drop down for me when I click on the logon button in the initial screen displayed in transaction GRAC_SPM.
    Suffice to say that i do not have any reason code to pick from in the drop down for superuser privilege management in the AC system when i logon with the firefighter user to perform SPM.
    Please help me out with your suggestions.
    Thanks

  • Write-off By Reason Code Split according to Profit Centers

    Hi All,
    I want to know is it possible to Write-off (Reason Code Used)  amount to be distributed by Profit Centers.
    We have a scenario where in revenue from One customer has to be assigned to more than 1 Profit Centers.
    Now if some write-off happens against this customer invoice, wie want this write off amout to be distributed among Profit Centers inProportion.
    e.g. USD 100 split into 2 PC .i.e. USD 50 in PC1, and USD 50 in PC2.
    Now if we receive a revenue of USD 90 and want to write-off USD 10 by reason code. We want the Write off amount to be split by Profit Centers, i.e. USD 5 should be assigned to PC1 and USD 5 should be assigned to PC2.
    I believe it is Posssible By Document splitting Functionality. Is it correct? If correct what are the configuration that might need to be done or is there any other way to achieve the same.
    Thanks in advance
    Regards
    Nitin

    any replies/suggestions

  • Using MBGMCR03 Inbound for reason code

    I'm in the Functional Speccing stage of a project. the process I need to document is this: Requirement to post goods movements interfaced into SAP from an external system. I have scoured the forums throughout the web and found only 1 thing similar (on this site) - solution is to use WMMBXY/WMMBID02.
    The problem with this is that there is no specific field for reason code (which I need to use) in WMMBID02 as there is in MBGMCR03.
    How can I use MBGMCR03 inbound when it has no associated inbound process code bearing in mind that the SAP system is to have no custom developments/modifications? If I have to do some mods what is the minimum that needs to be done either for WMMBID02 to have additional reason code field or for MBGMCR03 to become inbound-friendly?
    Thanks in advance for any help!
    Jay

    More info? In WMMBID02 the field E1MBXYI-GRUND for reason code (as in table MSEG) is there but its text refers to Asset master records. It has only 3 characters allowed and refers to table T098.
    The MBGMCR03 field E1BP2017_GM_ITEM_CREATE-MOVE_REAS (data element MB_GRBEW (same as in MSEG-GRUND)) refers to table T157D and has 4 characters and so seems to have no correlation with WMMBID02.
    Anyone have any ideas? Can I still use the GRUND field from E1MBXYI?
    Jay

Maybe you are looking for