cancel
Showing results for 
Search instead for 
Did you mean: 

Recommended Block size settings

Former Member
0 Kudos

Hi ,

What is the recommended block size settings for for different kinds of orders ? How do you ensure optimum performance for the different kinds of orders and different data volumes ?

Regards,

Ranjini.

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

The order size is determined by various factors, like:

- The runtimes of u201Corder selectionu201D and u201Cwriting to liveCacheu201D vary according to the chosen package sizes. The relevant parameters are maintained in /SAPAPO/CTMCUST for CTM settings. However the package size parameter for asynchronous liveCache updates can also be maintained via the variable planning parameter u201CPackageSizeu201D for each CTM profile.

1. The setting for Order Selection is based on location-products rather than on number orders. If, for example, the parameter is set to 5000, CTM reads the orders for the first 5000 locationproducts in one package from liveCache. If the average amount of orders per location-product combination is

a. 0.2 (each fifth loc-prod. has an order), the result is 1000 orders per package

b. 10 (each loc-prod. has on average 10 orders), the result is 50000 orders per package

As you can see, this setting strongly depends on the orders (including fixed orders, PP/DS orders) existing per location-product. Therefore it is important to try different settings to clarify performance issues. As a guideline SAP expects values of 10000-50000 orders per package for optimal performance

2. The setting for the package size for asynchronous liveCache Update considers the existing requirements and creates orders for them. The PackageSize parameter determines here the

number of requirements considered before sending the resulting orders to liveCache. The possibility exists that several orders have been created per requirement or just one. Therefore

the parameter does not imply that the package includes 500 orders, if this is the current setting, it only means that 500 requirements are considered and the respective orders sent in

one package.

It is only necessary to change this parameter if the CTM engine is waiting for the liveCache (the queue for packages to be transferred to liveCache increases as liveCache is not dealing with the necessary updates fast enough). One can then look into the CTM Application log and find the number of orders transferred per package depending on the most relevant categories:

a. planned orders / production orders

b. purchase requisitions

c. transport orders

d. substitution orders

The amount of orders per package coming from these categories together should result in at least 5000 orders per package to have optimal performance.

Former Member
0 Kudos

Hi Vinod ,

Thanks for this detailed explanation . Can you recommend a few notes that will also be useful ?

Regards,

Ranjini.

Former Member
0 Kudos

Hi - try 420669, else the best practices document available online would be very useful.

Regards

Vinod