SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Showing results for 
Search instead for 
Did you mean: 

Obligatory meter reading in UCES moveout

0 Kudos
198

Hello experts,

how to set within UCES (JSP/Java or ABAP-Customizing) the fields for meter reading as obligatory. This is needed for moveout-process over UCES. In movein-process the request parameters are checked against "empty", also in meter reading-process.

Thanks in advance

Stefan

1 ACCEPTED SOLUTION

Former Member
0 Kudos
152

Stefan,

As long as your stepping through the moveout_meter page in your UCES Move-Out process, you should be able to set the desired field to mandatory by updating the appropriate resource file with an "*" after the last character in the message key text corresponding to the field you're wanting to change.

We are not using the moveout_meter page in our UCES Move-Out process, but I've made this adjustment to fields on other pages in our webbase-config path, as well as other processes with Biller Direct/UCES.

Regards,

Gavin

View solution in original post

2 REPLIES 2

Former Member
0 Kudos
153

Stefan,

As long as your stepping through the moveout_meter page in your UCES Move-Out process, you should be able to set the desired field to mandatory by updating the appropriate resource file with an "*" after the last character in the message key text corresponding to the field you're wanting to change.

We are not using the moveout_meter page in our UCES Move-Out process, but I've made this adjustment to fields on other pages in our webbase-config path, as well as other processes with Biller Direct/UCES.

Regards,

Gavin

0 Kudos
152

Hello Gavin,

we also don't use moveout_meter page in our scenario. We use the meterreading process pages instead.

We solved the problem by creating an own action class for verifying the relevant request parameters. This action is called after standard action comes with success. In success case of our action class, we forward to next page. In error case we forward to meterreading edit page.

In our scenario this solution could be created faster than configuring (understanding) the movout meterreading scenario, u described.

Thanks a lot!

Stefan