Customer Statement Template Issue

  • 9 October 2020
  • 2 replies

Userlevel 3
Badge +5

When creating customer statements our users either forget to enter a customer or customer range into the statement selection template, or move between templates causing the template to display correctly but not work as designed.  What happens when this occurs is that all customers that have an outstanding balance receive an e-mail statement or one prints on our printers.

We have seen this issue happen regularly, so I am looking to put in place a way of stopping it happening.  I have created a blank statement template and set it as the default template, so now users must select there chosen template and enter the correct values manually.

Previously users would create the statement from the customer analysis screen, and the default customer template would auto populate with the customer number.  So in this scenario it takes longer for the user.  This solution I would only want to be a temporary one.

What I would like is to create an event that gives a warning that the user is about to create statement for all customers with an open balance across all divisions, do you want to proceed?  This would give them a chance to stop it happening.  As the statement template printing happens from a pop-out template screen I am unsure of how to do this.

We are currently on apps 8, but we are in the process of upgrading to apps 10 (due to go live at the start of January).

I am hoping someone in the community has either created a solution for this or a similar issue, or knows how I could do this?




2 replies

Userlevel 3
Badge +5

Has anyone any ideas how we can stop this issue happening please?




Userlevel 7
Badge +11


One way to solve could be to use the LOV properties and store a saved search for the LOV related to the template. 

For example, I created a selection template for statements.  In the process to create customer statements the LOV on the selection template would only show the statement template.  

All LOV’s that I know of have the ability to use a saved search. From a user perspective, the only available selection template would be the customer statement template. 

Down side would be to make this work best, remove the default from STD template or set the statement template as the default. 

The other common use screen for selection templates is the open items report where you can save the current selections on the navigator so the default is no longer important as you would save the report run options with the preferred selection template to the navigator. 

To add a saved search for any LOV, do the LOV, then use properties to create a saved search, then again in the properties set the LOV to use the saved search. This only works in IEE. 

Best regards,