One More Try: Cost Center Master

[mike_mcinerney]

I originally posted this at the end of October. I received zero replies, but I wanted to give the forum one more crack it. Thanks... ...Mike

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We have a need to enhance the Cost Center Master, and have used enhancement COOMKS01 to add additional fields and maintain them via the CI_CSKS structure (on the "Additional Fields" tab of KS01,2,3).

In particular, we added a "Responsible PERNR" field which accepts an employee number. We would like to integrate that back to CSKS-VERAK (responsible person) , such that a change in PERNR will update the VERAK field with the first 20 characters of the employee's eName (from pa0002). Any idea how I can change the value of the CSKS-VERAK field at the same time.

Hope the question made sense. Thanks... ...Mike

[Former Member]

There could be way where you can do this but its not the standard way of implementing an exit.

You can use Enhancement COOMKS02.

Now this has an exit which gets triggerred when a 'SAVE' is done in KS01/KS02.

Again this Exit does not have facility to change CSKS data, but it has CSKS has importing parameter.

Here you use the expert method of acessing attributes using field symobls. You have to find out which is the final internal table storing this CSKS data in the transaction.

Then declare a field symbol:

field-symobs : <FS> type any,

<FS1> type any, <FS2> type any.

assign '(SAPLKMA1)ITAB' to <FS>.

if sy-subrc eq 0.

assign component 'VERAK' of <FS> to <FS1>.

assign component 'ZFIELD' of <FS> to <FS2>.

<FS1> = <FS2>.

endif.

[mike_mcinerney]

Hello Sharath,

Thank you for the reply.

COOMKS01 also has a save of CSKS. The problem seems to be, that

there is a CSKS and CSKS_CI section, and I can only get fields to "stick" in the database on the CSKS_CI.

I will, explore COOMKS02.

Thanks for the input.

Reward points to follow...

...Mike

I

[former_member186143]

you have to add you're fields to CI_CLSA

futher on you have to start the fieldname iwt ZZ

so VERAK is not possible (or not recommended by sap as you can check the errors it will produce) but ZZVERAK is allowed

if you have included the field in ci_clsa it makes no difference for you're convenience since it can be used if it is a normal field of clsa. (in se16n you will see you're field when you search on table clsa)

So now I have to go on searching for an example how to handle the screen exits

kind regards

arthur de smidt

[mike_mcinerney]

closed