Cannot set up a specific payment term

Hello
I have a special requirement for a payment term and do not know how to set it up. I am not sure if it possible to set it up correctly in SAP.
I am using release ECC6.

The term should be based on invoice date.
The due date should be calculated as follows:
You take the invoice date and add 45 calendar days to arrive at a date. The due date should then be the last calendar date of the month of the calculated date.

Popular White Paper On This Topic

For this payment terms cannot be defined in SAP
However, ABAP code can be written to arrive due date...
When user will put Invoice Date, ABAP code (may be substitution.. not sure)
has start working to fill in baseline date / due date...

Thanks for your post but I do not think your suggestions will work.
Probably I have explained badly.

Let me give you a couple of examples:

If invoice date plus 45 days falls on the 28th February then the due date should also be the 28th February.
If invoice date plus 45 days falls on the 1st March then the due date should be the 31st March.

Make the baseline date as no default and enter them on the last calendar date of the month during document posting. Make the credit terms as 61 days in your payment term. It is likely to have success rate of 83%.

Now as regards the exceptional 17 % ( only 4 such cases will happen).

Base line date During January and December (Non leap year)

The no default base line can be entered as 29 Jan and 29 Dec during document posting instead of the last calendar date.

Base line date During January and December ( Leap year)

The no default base line can be entered as 30 Jan and 29 Dec during document posting instead of the last calendar date.

May be you could try the possibility of writing a substitution for tweaking the baseline date during document posting which could make data entry user independent.

Make the baseline date as no default and enter them on the last calendar
date of the month during document posting. Make the credit terms as 61 days
in your payment term. It is likely to have success rate of 83%.

Now as regards the exceptional 17 % (only 4 such cases will happen).

Base line date During January and December (Non leap year)

The no default base line can be entered as 29 Jan and 29 Dec during document
posting instead of the last calendar date.

Base line date During January and December ( Leap year)

The no default base line can be entered as 30 Jan and 29 Dec during
document posting instead of the last calendar date.

May be you could try the possibility of writing a substitution for tweaking
the baseline date during document posting which could make data entry user
independent.

Try it out please.

Regards

Check out the table below and I have used credit term of 61 days in all
cases and have tweaked baseline date in four exceptional cases marked with
asterix.

Make the baseline date as no default and enter them on the last calendar
date of the month during document posting. Make the credit terms as 61 days
in your payment term. It is likely to have success rate of 75%.

Now as regards the exceptional 25 % ( only 6 such cases will happen).

Base line date During November,December and January ( Non leap year)
All November dated bills can use 01 Dec as baseline date.

The no default base line can be entered as 29 Jan and 29 Dec during document
posting instead of the last calendar date.

Base line date During November, December and January ( Leap year)

The no default base line can be entered as 30 Jan and 29 Dec during
document posting instead of the last calendar date.
All November dated bills can use 01 Dec as baseline date.

May be you could try the possibility of writing a substitution for tweaking
the baseline date during document posting which could make data entry user
independent.

Try it out please.

Regards

Check out the table below and I have used credit term of 61 days in all
cases and have tweaked baseline date in four exceptional cases marked with
asterix.

Did you get this working? I believe that you should be able to accomplish this with standard payment terms.

Select Document date as the default for baseline date.
Term 1 - Percentage is 0%, No. of days is 45, Fixed date is 31

This should accomplish what you are asking for. Baseline date will be equal to doc date, but due date will be the last day of the month that is 45 days out from document date. Enter some invoices in FB60 (header information only) when you commit the data, the system will calculate the due date. Look at the payment tab and see if it is working the way you would like.

For the fixed date field, 31 functions as an end of month and not the actual day of the month like you would expect.

I guess requirement of payment term such as this has been requested by many
folks. Am not sure there is a comprehensive and foolproof standard solution
to this in Standard SAP by using features such as fixed date and day limit.
This is so on account of the fact that February has lesser number of days
than other months and February has one day more during leap years. Therefore
, I guess it would be a better idea to customize a procedure with the help
of your ABAP folk.

One possible work around could be peg the due date as the last date with
additional month as 1. This is apart from choosing No Default option for
Base line date and manipulating it manually during invoice posting (
choosing a baseline date by manually computing as due date less 45 days ).
However, in my opinion, this is a cheap work around and prone to clerical
error. Therefore, it would be better to develop a customized solution with
the help of an ABAPER.

A customized programming is foolproof. I tried writing a program in Fox pro
( as I am not an ABAPer) to ascertain 45 days from the date of the document
and push it to the end of the month in which the invoice falls due. It works
pretty well.

The program logic first adds 45 days to the baseline date ( which is the
document date) and the result is stored to a date variable. This variable is
then parsed and chunked into three variables for *Date, Month and Year*.

If the *Month* is 1, 3 , 5 , 7 ,8 10 or 12 then the *Date* is set to 31

If the *Month* is 2

and if the *Year* is divisible by 4 then *Date* is set to 29 else to
28 (*)

(*) You may have to perform the additional check of divisibility *
Year* by 1000 and the result again by 4 for leap centuries

Otherwise

*Date* is set to 30

Now convert the Date,Month and Year Variables into string counter parts (
using pre-defined functions) and concatenate them in DD MM YYYY format and
convert the result into a date related data type and store the same as a
resultant variable called due date.

The difference between the Due date computed and the Document Date is
substituted as the payment terms. This would give the desired due date for
the invoice item.

The generic logic can be used in ABAP (using the appropriate methodology and
syntax) to compute due dates as desired and this, I think , would be
foolproof.

There was a small typo in my earlier mail. With regard to leap centuries the
check for number of days in February is performed by ascertaining the
remainder obtained by dividing the year by *100* ( *not 1000 as mentioned
earlier*...Typo is regretted ) and the result is checked for divisibility by
4. Kindly excuse me for the typo.

Exactly ! The due date is primarily computed as document date + 45
Days....If the 46th day (due date) falls on the last day of the calendar
month by default , then you process as it is. On the other hand the 46th day
( due date falls on any other day of the calendar month, then the customized
procedure pushes the due date a little further so that it coincides with the
last day of the calendar month. Thus you always plan, schedule and make
payments on the nearest last calendar date past the 45 days credit terms
availed.

The same month mentioned by you has been understood by me as the last
calendar date of the month in which the 45th day occurs.

Please correct me if I am wrong. I was always under the impression that you
can use a credit period in number of days OR a fixed date for payment across
a row. Does the payment term allow you to define a due date which is 45 days
and further peg it to a fixed date of 31?

As I am currently not on an SAP system, I am unable to check it. Would you
mind confirming if a payment term can accommodate both a fixed date and a
credit period of 45 days defined across the same row?

You can create payment terms with 45 days AND then a fixed date of 31 (the system will take this to mean End of Month) in the same row, that is correct. If you set this up in a test environment, you can test the calculated due date in FB60. You need only enter the header data and look at the payment tab. It will tell you the calculated due date.

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.