I dont think, you can have such customization in std settings. If you are open for enhancement then it would be better to populate payment terms field based on logic.
Remember in which transaction you would like to write the logic, ist in sales order , if yes at what level - Header / Item?
Choose the proper location to input this coding, Your ABAPer would be in better position to assist you in this regard.
Eg: Assume its document value you are referring about.
Create necessary payment terms to suit the below conditions,
1.upto 10000 - full payment - ( Immediate payment)
2.more than 10000 to 2.5 - 10% of total value
3.more than 2.5 - pay in 10 days
4.more than 5 lacs - pay in 20 days
Regards,
Reazuddin MD
Hi Kanna Palle,
The solution for your requirement can be found in note 119907 which explains:
"With pricing you can determine data for terms of payment by means of
condition records and transfer them to the document.
If you use this option for condition records with stored scales, then
the system also determines the terms of payment if the first scale level
was not reached and the condition rate is therefore equal to zero. "
However, notice that you can have only one payment term per condition
record, not one payment term per scale level. That means you can't use
different payment terms for different scale levels.
I hope this document can help you to solve quickly your requirement.
Regards
Ruy Castro
Add comment