ESS time sheet problem

[Former Member]

It turns out the reason we can't display our Z custom fields in CATS is because they have the word 'field' in the name and the Class CL_XSS_CAT_PROFILE has a piece of code that bypasses any CATS field with the name 'field' in it. (This seems to be a contradiction in SAP's policy not to mess with custom fields starting with the letter Z.) We have tried renaming the fields using transaction SE11 but we loose the history of CATS data. We also used transaction CMOD and also lost the data. We have also tried changing the code in the Class CL_XSS_CAT_PROFILE but that seems to cause other problems.

I have attached several screen shots. The first one CI_CATSDB.jpg shows the 9 fields in question. The second one, catsdb, shows the ci_catsdb include at the end of catsdb. The third one, PREPARE_FS_TS, shows the SAP code where it is skipping the custom fields for the new time sheet. The fourth one set_fs_wl shows whre the custom fields are being exluded in the new time sheet work list.

We have tried two different options on renaming the fields in ci_catsdb. Both options were successful as far as displaying the time sheet. However, both options also deleted the data. I do not know what either option does to the archived data.

One option was to run SE11 on ci_catsdb and rename the fields. The second option The second way was to have two sessions opened. One running transaction code spro and the other running transaction code cmod.

Under spro

cross-application components -> Time Sheet -> settings for all user interfaces -> Customer-Specific Modifications -> create custom Fields -> make field assignment I would delete the field save it. Then go to the second session (running transaction cmod) rename field, save it activate it. Then go to the first session insert the new field,

Your prompt attention to this issue would be greatly appreciated.

Edited by: babu rao on Jun 5, 2008 4:37 PM

[Former Member]

Hi,

Check the transaction 'CAC2' for your data entry profile.

Follow the below steps: -

1. Go to the transaction 'cac2',

2. under the modifiable fields see if the customer fields are hidden with the radio button

3. if you want the fields to be available for all the data entry profiles then make them visible with the radio button options (select the required one)

4. if you want it to enable the fields for only one profile then select the influencing button, enter the data entry profile and pree enter. Now change the field settings.

Let me know if you still face any issue.

Thanks & Regards, Swapnil Mishra

[former_member443899]

Hey,

Thanks for the quick response, but yes we know how to add a field to different data entry profiles. That is not the issue.

Our issue is that Enterprise Portal does not recognize any field that contain the word "field". Thus, a solution that uses customer field called FIELD1 will work fine in ECC, but will not even show in Enterprise Portal's record working time even. The problem appears to be a bug within the Java Webdynpro application itself.

We have tested 2nd customer field called "Job", but this could lead to additional complications. So I was hoping that through OSS or creativity that someone has come up with a solution to this problem that would not involve a new customer field.

Again thanks for the response.

Doug

[Former Member]

Hi,

Yes, as far as I remember there is already a SAP Note for this. Search for the note and apply the same.

Thanks & Regards, Swapnil Mishra

[SKM1]

174b6e5733d1118b3f0060b03ca329/content.htm

Refer to the sap help link pasted above. If your custom fields are

Input fields then you need to ensure that these fields in the field selection

are not set to required entry options as this option is only available

For technical reasons and if chosen for those custom fields

would not make these fields visible in the time sheet.

Srinivas Mandgi

[former_member443899]

Do you have the OSS note number? I am currently working with OSS myself, but it is taking a while.

Thanks,

Doug

[former_member443899]

Srinivas Mandgi.

Your URL did not paste properly. Could you try sending it again? The field is labled as input only, but there does seem to be a bug with portal that it will not recognize fields that contain "FIELD".

Thanks for your help and if you have any other suggestions I would love to hear them.

Doug

[SKM1]

Hi Doug,

Sorry , here it is once more.

Happy Thanksgiving.

http://help.sap.com/saphelp_46c/helpdata/fr/a8/174b6e5733d1118b3f0060b03ca329/content.htm

Regards

Srinivas Mandgi

[former_member443899]

Thanks again. We were able to add the fields in ECC and its been working since 2005. This is strictly a problem with how portal works. We can add any customer field using CAC2, Influencing, etc.. The problem is that fields that contain the text "FIELD" are not recognized by the enterprise portal's record working time application. This results in the field working in ECC, but not in EP.

I'll let you all know how the OSS note goes.

Happy US Thanksgiving (In Canada ours was in OCT)

Doug

Edited by: Doug Robbins on Nov 23, 2011 3:04 PM

[former_member443899]

Here is the solution we were given.

CL_XSS_CAT_PROFILE

PREPARE_FS_TS

in line 98 to 102.

-

---

LOOP AT field_selection_time_sheet

ASSIGNING <fs_line>

WHERE mfeld CS 'FIELD' AND

NOT mfeld CS 'CATSFIELDS'.

CLEAR l_position.

-

---

For this issue, you may do your own modification on the coding like:

LOOP AT field_selection_time_sheet

ASSIGNING <fs_line>

WHERE mfeld CS 'FIELD' AND

NOT ( mfeld CS 'CATSFIELDS' OR mfeld EQ 'FIELD1' ).

CLEAR l_position.

[SKM1]

Hi Doug,

Thanks for that piece of information. Could you elaborate in more detail on the abap code you have added to resolve your problem . Thanks.

Srinivas Mandgi

[former_member443899]

The code was provided by SAP. It appears to say that they will continue to ignore fields that contain "field", but we can hard code an exception for our field called "field1". Its not ideal because you have to update the code any time you upgrade.

Doug

[SKM1]

Hi Doug,

Thanks for sharing this information with us.

Just for the benefit of the others the SAP Note No that provides the solution to resolve this issue is "Note 1232258 - CATS WD: Additional fields are not displayed"

What the note is doing is it is removing the constraint of deleting the any field on the XSS screen with the string "FIELD"

The issue here is that in the standard scenario SAP is not permitting any customer field in the CATSDB structure to be named wholly or partially with the string "FIELD" ( note CS is contains string so in the earlier code which included mfeld CS "FIELD" simply means the in the Customer Include ( or simply CI include) of CATSDB structure containing any field named with a text containing the string field ( which means part of whole of the name) would not be permitted.

SAP has released a this note 1232258 to correct this problem and what they have done is by making changes using their correction instructions in this note, they are permitting customer fields to contain string "FIELD" or "-FIELD"( e.g. NEW1-FIELD)

Srinivas Mandgi

Edited by: Srinivas Mandgi on Dec 1, 2011 1:09 AM

[former_member443899]

Hi Srinivas,

I was just reviewing the OSS note you provided. That appears to be very close to what I need, but there is still a small problem that I will address with OSS directly.

At first renames the standard "CATS_ADDFI-FIELD1" to "CATSDB-FIELD1" then SAP removes any field that contains "CATS_ADDFI-FIELD2" to "CATS_ADDFI-FIELD10".

The SAP delete any field contains the string 'FIELD' which will delete our field "CATSDB-FIELD1", and the fix in OSS Note 1232258 will delete any field that contains the string "-FIELD" which also will delete our field.

If our field was names ZFIELD1 the OSS note fix would work perfectly.

Thanks,

Doug

[former_member443899]

See note 1665054 - CATS WD: Additional fields are not displayed. We are currently testing and I wanted to share. The only change is that we asked sap to update the string of the types of fields they delete so it is more accurate.

Doug

[former_member443899]

Hey There,

It looks like I'm having the same problem as you. In ECC we created a customer field called "FIELD1" with the description of Jobs to pull in IT0554 information. Unfortunately as you've notice the portal does not like this name. Did you ever find a solution?

Thanks,

Doug