Client side changes required to download CE field value help in Retail Execution 3.1.16 for IOS ??

[former_member200342]

Hi All,

We are using Retail Execution 3.1.16 for IOS.

In SAP CRM system for the business partner contact two Function fields are available one is a text field and the other is F4.

But in REx3.1.6 only Function field with text is available as standard, and we need to download the Function Field with F4 values too in REx.

After referring the REx extensibility guide for REx 3.1 we added the below changes in UIAConfiguration.XML file

Changes added in the UIA XML :

<!-- Contact Details Screen -->

        <screen id="ContactDetails">

        </screen>

        <ceFieldDefinitions>

        <ceFieldDefinition id="ZFUNCTION" labelId="FUNCTION" dataType="1510"/>

        </ceFieldDefinitions>

        <ceSectionDefinitions>

         <ceSection for="CONTACTS">

             <field id="ZFUNCTION"/>

         </ceSection>

        </ceSectionDefinitions>

Are the below changes sufficient to add the new function field in ContactDetails screen ??

OR changes are required in the XIB file and mapping needs to be done ??

How to map it ??

[Former Member · Accepted solution]

Hi Prajit,

You need to implement BAdI /mac/rs_badi_get_ce_value_help in the CRM backend to pass the possible values for the LOV field.

As you are defining this field for Contacts, you should have multiple entries for the key value pairs in the ET_VALUE_HELP exporting table of the BAdi similar to.

OBJECT_TYPE = BusinessPartnerMBO

SUB_OBJECT_TYPE = BusinessPartnerMBO

LANGU = Client language (example EN)

FIELD_NAME = ZFUNCTION

KEY_FIELD = <YOUR ENUM KEY>

VALUE = <YOUR ENUM VALUE>

Regards,

Harsha

[former_member200342 · Accepted solution]

Hi Harsha,

Thanks for your reply.

What changes are required in the UIACOnfiguration_iOS.xml file which we need to upload in the MIME repository as well as include in the client project?

The changes we have made are already in the previous post. Are these changes sufficient?

Since we need to replace the function text field with this new Z field, do we need to define the complete contact detail screen in UIA xml or we just need to define this new Z field.

Could you please also let us know what other UI changes are required.

Regards,

Prajit

[Former Member · Accepted solution]

Hi Prajit,

Its sufficient to modify the UIAConfiguration_iOS.xml file as you have initially described.

You only have to define the new Z field in the xml, however this will not replace the standard field but add this field into the More.. section of the Contact edit screen. Hiding the standard field is not an option in 3.1 client

Regards,

Harsha

[former_member200342 · Accepted solution]

Hi Harsha,

We need the changes in the UIA xml and uploaded in the MIME repository, but once we do this we are unable to get CE fields on the device. Even the existing Customer CE fields are not getting displayed. Which works fine again when we upload the old xml. On analysis we found the new xml in the SUP and even in the device DB. Not sure what exactly went wrong in the new xml.

Is there anything that we are missing from our end?

Regards,

Prajit

[Former Member · Accepted solution]

Probably there is an error in parsing the XML, verify what is the delta with respect to the old xml and you can paste the same here.

[former_member200342 · Accepted solution]

Hi Harsha,

The delta in the XML is pasted below for a new field ZFUNCTION that we want to add to the customer contact person screen.

Changes added in the UIA XML :

<!-- Contact Details Screen -->

        <screen id="ContactDetails">

        </screen>

        <ceFieldDefinitions>

        <ceFieldDefinition id="ZFUNCTION" labelId="FUNCTION" dataType="1510"/>

        </ceFieldDefinitions>

        <ceSectionDefinitions>

         <ceSection for="CONTACTS">

             <field id="ZFUNCTION"/>

         </ceSection>

        </ceSectionDefinitions>

Please verify if this is correct.

Thanks,

Prajit

[Former Member · Accepted solution]

Looks correct, could you please take a look at the Log.  You can use the Settings-General-Send Log feature, look out for an error like

"UI Configuration XML parse error", in case you don't find this then there may be additional logs statements that can indicate the issue.