Issue with field value update for ZAEHL in table PLMZ

[former_member220469]

Dear experts,

I am developing a program to perform the component allocation in routing using the function module CPCC_S_TASK_LIST_MAINTAIN. Execution is fine but after the allocation in table PLMZ the field ZAEHL counter has the default value as 1 for all the component assigned in an operation in a routing. We checked the logic for this behavior, in the standard fm CM_CL_COM_KEY_PROVIDE there is a hard coded value given for the field ZAEHL as 1. Now I have a concern on this behavior, all the components in a group number has same value as 1. Will it have any impact if with this behavior or Do we have any OSS notes for correcting this behavior? Please provide your inputs for this issue

Regards

J.Balakrishnan

[former_member220469]

Can anyone suggest me here?

[former_member220469]

Can anyone suggest me here?

[ninad_narad · Accepted solution]

Hi Balakrishnan,

ZAEHL is an internal counter, while creating a routing/task list it will always be 1. After you have created a routing if you change the component allocation in the routing, you will see another entry in the table with ZAEHL incremented by 1. As you keep on changing the component allocation the entry in the tables will be added and be incremented by 1.

Regards,

Ninad Narad