Reason code and payment terms

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

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

Similar Messages

Invoice and payment terms ...I don't understand . please suggest me

I have given problem below. In FI, we normally configure in fbzp tocode...what is the outpur type here ? for the below which program I need to check ? Invoice and payment terms ...given
Pls take a look at this invoice and let me know why it is changing the payment term.
User has below problem :
SAP FI Output type SAP19
Payment Terms print "Payment Due Immediately" rather than actual terms.
i.e. invoice 208615 - payment terms US02 - should print "Net 60" however prints "Payment Due Immediately".
Is this hard coded and if so, can it be corrected and when?
Please advise.
Thanks,

Using fb12, I am selecting customer invoice
then in new popup I am giving invoice number and fiscal year. then it is giving message on status bar as 'customer invoice requested'.
Then i am going to F.61 and executing by giving in pop up -->correpspondence, company code, document number and fiscal year.
Then a spool is getting created and I am able to see the form output in /nsp01 where the error is occuring .
Could you please suggest me hwo to find out the form name and driver program name.
THANKS IN ADVANCE.
Edited by: Sam Kumar on Sep 3, 2008 7:30 PM

Where to configure the reason code for payment differene

Dear Experts,
I did the settings in obxl with reason code option and changed the screen layout for the postings keys for payment difference as mandatory. while doing the account assignment in obxl system asking the reason code for payment difference. Where to configure the reason code any t.code is there, please guide me.
J.francis

Just Go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment > Define Reason Codes (Manual Outgoing Payments)
There you have to create Reason Code
Now go SPRO>IMG>Financial Accounting (New) >Accounts Receivable and Accounts Payable > Business Transactions > Outgoing Payments > Manual Outgoing Payments > Overpayment/Underpayment >Define Accounts for Payment Differences (Manual Outgoing Payment)
Here assign GL
Best Of Luck
Tanmoy

Auto update of Valid to and Payment Terms field

Hi,
I have a scenario, where based on the Net value of the document, Valid To date of the Quotation and Payment Terms should auto populate.
Ex: If Net value is above 5lks, then payment terms should be 100% with in 20 days from current day and valid to date is also 20 days from now. Like wise, if Net value is below 5lks, then payment terms and valid to date should be 10 days.
Thanks for response in advance.
Vam

Hi,
Please check if the following user exits help.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document" .
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
Regards,
P Gomatheeswaran

Authorization for Credit, Commitment Limit and Payment Terms

It's very required to have authorization for Credit Limit, Commitment Limit and Payment Terms change. Currently it's very hard to control limits as every user can change these values and omit approval procedure or authorization for Confirm Credit Line Deviation and Confirm Debt Line Deviation.

Thanks, You were right. It runs well for the sales order with out delivery. After I create delivery in reference to this sales order and change payment terms in sales order there is no new credit control check.
Is there a possibility to run credit control check after a delivery is created?

Case created without business partner, reason code and result code

In our CRM system, some cases was created without business partner, reason code and result code.
We created some customer functions to make these fields as mandatory, it always work for our technique people and process expert, but it didn't work for some users occasionally. We cannot debug it.
Can anyone tell me why and how to solve it?
Please help me !
Regards,
Shirley

Hello Shirley,
Well, then I would check the code, which calls your custom function modules.
It may be possible, that you have an IF in the 'Main' program, which makes it possible to skip the custom FM for these users.
The reason I am assuming this, is that normally you need just to change attributes for a field to make it mandatory, or customizing like SHD0 makes this possible. If you use custom FM, you have to call them somewhere and this is the point I would be looking for.
Check the traces for the users and you should find, that the custom FM are not called for them.
My opinion, of course
Award points if this helps.
Regards,
Martin Kuma

Vlidations for reason code and note type

Hi
i have a scenario file to ECC. From file i am getting Reason code and note type fields. I need to validate whether the correct reasons code and note type exists or not..
seven possible reason codes may exists in file and 10 15 valid note types exists..
how i achieve that..
venkat

Ok,
You can use multimapping and split the messages in the target structure. But the condition of the root node of each splitted message has to be validated against your <b>note</b> and <b>reason code</b>
Please refer the URL for more clarfication.
http://www.flickr.com/photo_zoom.gne?id=1131422258&size=o
Best regards,
raj.

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

Relationship between condition type and payment term

Hi,
I created a purchase order (only 1 item) with with payment term "Within 14 days 2 % cash discount" So a condition type SKTO auto added for the item with discount is 2%.
can anybody show me the relationship between payment term with the condition type and the IMG T.code to make this relationship?
Thanks
Long

If you go to IMG - MM- Purchasing - conditions- Define price determination process - Define Condition types
For SKTO the condition category is E- Cash discount
For this condition type which is defined in the calculation procedure , the system internally derives a percentage from the terms of payment and inserts it in the condition type with the category E

Customer numbers and payment terms

Is there a way of having multiple payment terms for a single customer depending on product?
Our payment terms vary depending on the product. To solve this we have created upto 5 customer codes with different terms for the same physical customer. The products are assigned to the relevant customer code.
This set up works fine financially but is a pain for distribution planning. There is no link in SAP to recognise that some customers are the same and can be combined into single loads.
All thoughts and suggestions welcome!
Thanks

Yes this is a genuine business requirement. The best approach to address this is instead of changing the payment terms each and every time in customer master, the same can be done while creating sale order. Based on some logic only, this will differ and if possible, may be you can apply a suitable exit to overwrite from customer master. Dont encourage to change in customer master at any cost.
thanks
G. Lakshmipathi

Cutomer master co code data payment terms

hi all,
could pls tell me what is the use of payment terms field in co code data of customer master.Only sales area data payment terms get populated in the sales order.Then why should we maintain the payment terms in co code data
thanks & regards

Hi
Master records have separate areas for Financial Accounting, Sales, and Purchasing.
You can specify different terms of payment keys in each of these areas.
When you then enter a business transaction, the application in question will use the key
specified in its area of the master record.
best regards,
Thangesh

Purchase order and Payment terms

Hi,
My client requirement. The delivery date in PO: 25-09-2008. If the vendor pays goods delivery to us after 25-09-2008 he want to deduct 2% on po value as Late Delivery Fees. My client is asking automation of this scenario. Automatically at that time of GR this entry should happend based on above requirement.
Where we can do customization for this?
Please guide me.
Sateesh Kumar

Hi,
Please maintain the payment terms in OBB8 as follow
Account Type will be the vendor. Default for baseline date will be the document date. In Payment Terms Tab, maintain as follow
Percentage will be 2% and number of days will be 15 days (for Example)
You can maintain the number of days according to your client requirement.
Regards,
Jigar

Dunning and Payment Terms

Hello Gurus,
I am working on Dunning procedures. We have a Dunning procedure at 3 levels - 30, 60 and 90 days.
The requirement is to have a 15 days grace period. The dunning letters need to be printed taking into affect grace period and it should be done at 46, 76 and 106 days. So far this to happen, I think the payment terms should be Net 15 days. ( I guess the DUnning procedure grace period will not help for this ).
Can you please suggest if this is correct i.e., the Payment terms should be 'Net 15 days' for the Customers for whom the Dunning is to be run. If the Payment terms is 'Payable immediately' than the Dunning happens at 30, 60 and 90 days. Can you please confirm if this is how the system should behave.
Thanks,
SNK.

If the grace period of 15 days is applicable only to certain customers then yes, create a 15 days net payment term and assign to those customer master.
If the grace period of 15 days is applicable to all the customer, then it is best to change the days in dunning procedure itself.
Regards,
SDNer

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

Draft invoice and payment terms

A customer has 30 day credit terms (for example), but when creating a DRAFT invoice the docuemnt date, posting date and due date defaults to todays date.
When converting the draft invoice to an INVOICE, the due date remains as today - not the payment terms of 30 days from posting date.
How can the payment terms be activated to ensure correct aging of the invoice?
2005A PL23

The 'due date' appears as soon as the Customer is selected in Invoice not while saving as 'Draft'. The due date is based on the 'Payment Terms' set in the 'BP Master Data'.
I request you to check if the 'Due Date' is set properly before saving the document as draft. It should be as per the payment Terms of the BP. If not check the Payment Terms of the BP.
I have checked this feature with SAP B1 2005B PL: 38 and works properly.

Reason code and payment terms

Similar Messages

Maybe you are looking for