cancel
Showing results for 
Search instead for 
Did you mean: 

ESS Customization.

Former Member
0 Kudos

Hi,

I'm trying to customize the component ess/us/addr from the standard ESS package. I'm adding extra telephone fields into the existing screen. I'm adding the following elements on my UI layer.

Label : Com01 Area1 Teln1 Extn1

The names mentioned above(except label) are context variables mapped to the model. Model Name : HRXSS_PER_P0006_US. Com01 is a drop down field the other three are input fields. These UI elements are on the Edit screen.

Scenario : I'm successfully launching the WD application. Updating the fields with valid data in the edit screen and successfully saving. None of the fields mentioned above are mandatory. After saving, when i go back to the screen again and try to change the existing data, I'm successful again.<b> " But during this data modification, I get an error after deleting the entries and leaving the fields blank."</b> I then checked the backend, i realized that, when i try to delete the entries and proceed, the backend entries are not getting deleted. On further enquiry i saw that, the com01 field is being emptied in the backend and the other three fields are not getting updated. <b>In the backend, Area1, Teln1, Extn1 are together getting saved as Num01. My problem is this field Num01 is not getting updated when i leave the fields blank on the UI.</b>

Please help solving the issue. Can anyone also elaborate if this is a WD java problem or a problem from the backend?

Regards,

Chaitanya

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Hi Chaitanya,

Can you please explain how d you resolve this issue.

I am facing somewhat similar problem.

Sharing the solution wil be of gr8 help.

Regards

Deb

Former Member
0 Kudos

What is the process that you have adopted to make these changes.

which structure have you modified to accomodate the new fields

have you used hcmt_bsp_pa_us_r0006

as the problem is in edit check model HRXSS_PER_EDIT_0006_US also please

Former Member
0 Kudos

Yes i did. The existing standard fields are behaving well, in the sense that, if i delete any values for a non-mandatory field they get deleted in the backend as well and i'm able to proceed further.

Former Member
0 Kudos

Did you compare with existing standard fields in the Infotype having similar data structure?