SETTLEMENT procedures - change values statuses (SET_CUSTOMER_VALUE_STATUS?)

Question

Hi, Experts,
at customer, we have implemented a solution, in which during processing of settlement step (e.g. standard 'SUMINTSU' step), we redefined the PROCESS method (in this case of class CL_ISU_EDM_SETTLSTEP_0003).
In that redefinition, we use standard method ADD_SUBTRACT_VALUES to compute the output value for the corresponding profile. Now, this solution is OK and works fine.
Cusomer's next need is to evaluate the output profile values statuses (that means the status of each profile value at each timestamp). Those statuses are located in the interface IF_ISU_EDM_PROFILE_DATA, attributes VALUE_STAT_TAB, VALUE_STAT_TAB_UTC. In the database, statuses are located in table EPROFVALSTAT.
We have already made one working solution in 4.6C system, but we managed that only by changing many standard objects (under time pressure). Now we have to do the same on a 6.0 system with a minimum of changes to standard objects. I already made some analysis in the CL_ISU_EDM* classes framework and found out methods SET_CUSTOMER_VALUE_STATUS and LCL_PERFORM_VALUES_ACTION in class CL_ISU_EDM_PROFILE that should do the job (as I made some sort of debugging).
Now my problem is to find out, how to call those methods and how to manage to compute the values and statuses of values either at once (in 1 processing step) or even in 2 steps. Again, with a minimum of changes to standard objects. I was not able to find any docu on this topic (I only have Guidelines for the Development of Settlement Procedures" - year 2001 and did not find any newer.
Any help will be appreciated
Thanks in advance

Answer 1

Hi, Igor,
thanks a lot for your answer. I already know about the method PERFORM_VALUES_ACTION, it's implementation is placed in the class CL_ISU_EDM_SETTLSTEP (not in CL_ISU_EDM_SETTLSTEP_0010 - as the method is flagged as final, you can't redefine this one). Yes, you are right, that the attributes (tables VALUE_TAB, VALUE_TAB_UTC) are placed in the corresponding interface, but this does not help me solving the problem, how to change the statuses during settlement step.
1. In the call of LCL_PERFORM_VALUES_ACTION (class CL_ISU_EDM_PROFILE), there is a parameter - CUST_VAL_STAT_TAB, but this only works in the process of importing profile values - not in the process of settlement step (I can't fill the parameter, as there are other calls precending this one).
2. Even if I could fill the parameter, mentioned above (1.), I still have to use only one of the parameters ACTION_TAB / CUST_VAL_STAT_TAB. As ACTION_TAB will keep the computed profile values and CUST_VAL_STAT_TAB can set the statuses of profile values, but I can't combine them (leads to an error). This I tried only in debugging.
3. If i set the settlement steps in the order - first the step to compute the values, second the step to set the value statuses, then the statuses will be set, but values will be initial (as the second step initializes the values). If I reverse the order of those two steps, then the values will be computed ok, but the statuses will remain system-managed (no custom statuses are set).
So really helpful would be any real implementation of this process - if anybody did exactly this - setting customer statuses for calculated profile values.