The Low Account Month (LAM) value is used to prevent an application from accepting a transaction with a date (contained in the built-in attribute ActMth) that is older than the date when the application was deployed. The default value is the year and month in which the application was initiated.
An error message specifying the Account Month is not open appears if you play back tests that were recorded before the current system was deployed. It is advised that you set the LAM to a value that is less than the LAM of such tests.
To set the LAM for the Windows Runtime, perform the following:
Open the Administration Tool.
Right-click the deployed system, click All Tasks > Configure…
On the Customize page, enter a value in the Low field in the High and Low Account Months pane.
Click OK.
To set the Low Account Month (LAM) for the MCP Runtime:
Ensure that you are logged on to the system from the MCP host with the Controller security access level.
From the home position of page 2 of the session where you are logged onto your system,
Enter :LAM [mmyy]
For example, :LAM 9806 sets the Low Account Month to June 1998. If no value is entered, the current value of LAM is displayed.
Refer to the Administration Commands in the Agile Business Suite Runtime for ClearPath MCP Administration Guide for more information on setting the Controller security level.