Service Entry Sheet Error msg

[Former Member]

Hi Friends,

I am running service cycle while raising service entry sheet in reference with that PO i am getting system message Customizing Incorrectly Maintained .

Service cycle is running well and this system message is also not causing any problem but each time it appears while creation of service entry sheets.

As per Guidance Mr. Pankaj i also maintained settings in Source determination and default values but problem is still there.

Need your kind guidance.

Regards

Vivek

[former_member193326 · Accepted solution]

Hi,

Please first check the information in the following notes

943778 > Runtime error "TABLEVIEW_DUP_COLUMN_INDEX"

1067124 > SE729 in ML82

Please also check the following information from our expert, which could

be useful for clarifying the issue:

We have noticed that SE729 generally occurs during an upgrade.

The variants maintained before and after upgrade could be different.

Since different customers maintain different number of entries for

each variant, it would not be possible to release a standard note to

all customers to fix this. Moreover this cannot be fixed using a notes

assistant, the changes have to be done manually.

The entries in the Table 'T162V'(for each of the 6 variants)

should always be the same as that of the columns in the table

control(TC_View).

Table Control(Screen) Screen 400 SAPLMSP(TC for services ).

Below is the standard logic to verify if the customising is correct.

**********************************************************

• Determine number of lines in customizing tables

describe table t162v_tab lines lv_t162vlines.

• Determine number of columns in table control

describe table tc_view-cols lines lv_tclines.

lv_tclines = 6 * lv_tclines.

Here 6 signifies the 6 variants for the TC.

if lv_t162vlines ne lv_tclines.

message s729.

endif.

**********************************************************

Please make sure that the entries maintained in T162V are the same

as the columns maintained in the TC.

For this case, you can use SM31 transaction to maintain the same

number of entries in the T162V as in Table Control.

Below is the standard logic to verify if the customising is correct.

**********************************************************

• Determine number of lines in customizing tables

describe table t162v_tab lines lv_t162vlines.

• Determine number of columns in table control

describe table tc_view-cols lines lv_tclines.

lv_tclines = 6 * lv_tclines.

Here 6 signifies the 6 variants for the TC.

if lv_t162vlines ne lv_tclines.

message s729.

endif.

**********************************************************

So please make sure that the entries maintained in T162V are the same

as the columns maintained in the TC.

For this case, you can use SM31 transaction to maintain same

number of entries in the T162V as in Table Control.

I hope this helps, if no, I would recommend to open a SAP tickdet in the SAP Marketplace.

Best Regards,

Arminda Jack

[Former Member · Accepted solution]

Hi Arminda

Thanks for your valuable suggestions But i am sorry to say problem is still there

IF any body faced same problem in past please help

Regards

Vivek

[Former Member · Accepted solution]

HI Arminda Jack

Thanks your are absolutely right.There was some problem with table T162V

Thanking you once again.

Regards

Vivek

[former_member193326]

Hi Vivek,

I am glad that I could help you.

Best Regards,

Arminda Jack

[former_member193326]

Hi Vivek,

Sorry!, I did not answer before, because I am waiting for the developers to give me an explanation about why this functionality is working like this. I can only confirm that the developers answered to another customer that the system is wokring as designed, but I wanted to know why is it working like this.

If I get an explanation I will inform you.

There´s no solution for this. You could always try with a user exit, but I have not tried this.

Please refer the attached note 459516 " FAQ: Vendor evaluation"

and documnentation of enhancement MM06L001.

The function modules for enhancement MM06L001 are as follows:

o EXIT_SAPLMEL0_001

for the general criteria

o EXIT_RM06LBAT_001

for the quality criteria if the vendor evaluation is carried out

in the background

o EXIT_SAPMM06L_001

for the quality criteria if the vendor evaluation is carried out

online

o EXIT_RM06LBEW_001

for the quality criteria when the scores for the semi-automatic

and automatic subcriteria are determined

Please see if any of the exits can be helpful.

Best Regards,

Arminda