Skip to Content

Business Requirement:

For our monthly policy customized application, there was a requirement to maintain multiple Pricing records for different Payment Terms but with same Validity period (Payment Term should be at Item level). As per Standard SAP we can’t have multiple records in the same condition under key values Valid on the same date. Condition Valid From and Valid To Dates are part of the primary key in the database table hence date ranges between the records cannot overlap. When we create a new record system will pick the most recent record and overwrite the previous one.

So in order to achieve the same we’ve added ZTERM (Payment Term) so that the system proposed the field in the field catalog.



Included ZTERM as a new entry. Now we can use field ZTERM as a key field when we’ll create new Condition Table.


So what we’ve done is created a Condition Table as:

Sales org./Distr. Chl/Matl Group/Price grp/ T


Issue arises after this point as when we’ve tried to maintain condition record in this Condition Table system does not display the description from the text table i.e; Payment Term Description was missing.



In Standard there are some fields which are not prepared in standard condition maintenance regarding field text determination and that does not handle text determination from the relevant text table. Few standards field are ZTERM, REGIO etc.


During the condition maintenance for Prices/Surcharges/Discounts in VK11 the descriptive text has not been determined for ZTERM (Payment Term) in the Header/Line item of the condition maintenance so we used BTE (Business Transaction Event) in order to determine the text.


Execute FIBF


Give the Product name that will link the event with the function module. Enter the product name description and check box A is required in order activate the product.


Select the appropriate event which gets triggered during the execution and against the event assign the Product name which was created above and assign a function module name. Take appropriate event which will fulfill the requirement and in my case it is 00503306 (Maintain conditions: Text determination)

Against the corresponding BTE check the Sample Function Module in SE37 and copy the same into the Custom Function Module Z*.



The desired logic will be encoded in the Custom Function Module. Save and Activate the FM. Be noted that the Creation of correct Function Module is necessary.


Further link the newly created customized Function Module and the Event using the product created.



Test the BTE. Now Description field is coming up while Condition Record maintenance.


NOTE: This might be considered as a common Knowledge but posting on SCN with this surety that it will also be helpful for many. Any feedback will be highly valued and appreciated. Thanks.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. ' MoazzaM '


    It is not common but very informative document and the way you presented the issue and its solution is appreciatable. If you add one more screen shot where ZTERM text is missing will add more value to this document and it will help to compare the difference of any field with and without description in create condition screen.

    Keep posting and sharing your ideas and knowledge with others.


  2. Former Member

    Dear Ammarah you always been presented your self with significant material on SCN. This is very informative document although this scenario is not very much familiar but very rare and effective for maintaining multiple payment terms against one validity date also you describe its text determination quite well. i hope you will always share your effective and informative material with us on SCN. Thanks!


    Suhaib Bin Aziz

  3. Suman Sardar


    Although I think for a description in VK11 we may not go for the BTE you mentioned but your way of presentation is quite cool.Indeed a nice document.

    Thanks for sharing.Keep it up.



    1. Former Member Post author

      Dear Suman,

      To avoid Modifications in a Standard Program (dependent on Release Version) or creation of special Routine checks, we’ve implemented BTE functionality against Payment Term Text Determination however thank you for appreciating and liking the document. Rgds.


Leave a Reply