CCUX0004 Post-Processing of Configuration with Dependencies

[Former Member]

The enhancement CCUX0004 contains the function EXIT_SAPLCUKO_003 which according to the documentation allows further changes with object dependencies after completing the configuration. However, there isn't any further details on how this might be achieved.

In this exit I have attempted to populate a characteristic value with a caluclated result via CUPR_SET_VAL and CE_C_SET_CBASE.

It appears that the value set in EXIT_SAPLCUKO_003 has been applied to the characteristic when reviewing the results in the value assignment interface within the sales order. However, the information icon for the characteristic can not identify the origin of the characteristic.

I would be interested to know if I am applying this enhancement correctly. I would also like to understand how authoring information is generated. There doesn't appear to be an option within the exist parameters.

Regards

Shane

[Former Member]

I contacted OSS with my issue regarding this exit (EXIT_SAPLCUKO_003) and their response was that it is possible to set a characteristic value but it would NOT be processed further. To me, this is different to what the documentation associated with the enhancement implies;

"This enhancement (CCUX0004) lets you make further changes with dependencies after the configuration is complete. After you call the customer exit, the configurator reads the changed values."

The response from OSS matches what is occurring within the VC configurator;

"The user-exit you have implemented is called after the configuration, The docuemntation says: "This user exit allows further changes with object dependencies after completing the configuration." This means after the user-exits is processed there is no further processing of object dependencies."

When I queried the interpretation of the enhancement documentation I received a further update;

"You are correct with "this exit does allow further changes to be made.",but this does not mean that after setting values in this exit dependencies are processed. When you enter the configuration, for example in a salesorder, all values set by dependencies are deleted, the dependencies are then evaluated and the values are set.

So in your example the values set in the exit are deleted when you enter the configuration and are set again in the exit when you leave the configuration.

So values that should be set by dependencies dependant on the values setin the the exit are never set."

The suggestion to my original issue of authroing a characteristic was to develop a VC function. The results from the function could then be applied by subsequent dependencies.

I am pretty much back to the start or my design journey again, but at least I have eliminated this particular path. I hope my experience is of assistance to anyone else who may attempt to apply this enhancement.

Good luck

Shane