*XDIM_MAXMEMBERS

When the number of records being processed is too big, the performance can deteriorate significantly. Also, processing too much data in the memory will slow down the system for other uses and eventually run out of memory. For example, an TSV_TNEW_PAGE_ALLOC_FAILED ABAP dump can occur even with high Roll memory settings. In this case, you can break the action into multiple packets and execute them sequentially using the following syntax:

*XDIM_MAXMEMBERS {dimension} = {max number of members}

Example Example

*XDIM_MEMBERSET TIME = 2009.JAN

*XDIM_MEMBERSET CATEGORY = FCST_LOAD

*XDIM_MAXMEMBERS P_ACCT = 5

*RUNALLOCATION

*FACTOR=1/12

*DIM TIME WHAT = 2009.JAN; WHERE = BAS(2009.TOTAL);

*DIM CATEGORY WHAT = FCST_LOAD; WHERE = FORECAST;

*ENDALLOCATION

Assuming the whole year’s forecast initially loaded 2009.JAN and FCST_LOAD, the above script allocates the data equally to each period in 2009. The script logic engine reads the data in packages split by P_ACCT members, with each package containing a maximum of five P_ACCT members, until it reaches the end in P_ACCT dimension members.

End of the example.

Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or by its gross negligence.