Personal Profile service for Brazil - Type Conflict for infotype 0002

[Former Member]

Hello All,

We are enabling personal profile service for Brazil. And we did all the required configuration for that.

When I access the personal info service I can see the overview page with personal data. But when I click on display link, I get the error message saying -

• Type conflict with ASSIGN in program CL_HRPA_UI_CONVERT_0002_BR

Is there any configuration missing?

Thanks,

Bhushan

[Former Member · Accepted solution]

Looks like you might have to debug some more, you need to see if pnnnn2 is having value or not, if value is there, we need to see if its in appropriate format to get converted into <p0625>

Defiantly some thing wrong with pnnnn2, so u need to find the source where its going wrong. But if you start debugging it, you will understand whats is causing to go wrong with pnnn2.

[Former Member · Accepted solution]

Hello,

We implemented a feature IVWID for brazil. And it worked well.

Thanks all for your input.

Bhushan

[Former Member]

There should be dump in the backend, pls check it using st22 and provide us those details.

[Former Member]

Short text

    Type conflict with ASSIGN in program "CL_HRPA_UI_CONVERT_0002_BR====CP".

What happened?

    Error in the ABAP Application Program

    The current ABAP program "CL_HRPA_UI_CONVERT_0002_BR====CP" had to be

     terminated because it has

    come across a statement that unfortunately cannot be executed.

What can you do?

    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system

    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look

    at and manage termination messages, and you can also

    keep them for a long time.

Error analysis

    You attempted to assign a field to a typed field symbol,

    but the field does not have the required type.

How to correct the error

    Adapt the type of the field symbol to the type of the field or use an

    untyped field symbol or use the "CASTING" addition.

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

    "ASSIGN_TYPE_CONFLICT" " "

    "CL_HRPA_UI_CONVERT_0002_BR====CP" or "CL_HRPA_UI_CONVERT_0002_BR====CM003"

    "IF_HRPA_UI_CONVERT_STANDARD~OUTPUT_CONVERSION"

    If you cannot solve the problem yourself and want to send an error

    notification to SAP, include the following information:

    1. The description of the current problem (short dump)

       To save the description, choose "System->List->Save->Local File

    (Unconverted)".

    2. Corresponding system log

       Display the system log by calling transaction SM21.

       Restrict the time interval to 10 minutes before and five minutes

    after the short dump. Then choose "System->List->Save->Local File

    (Unconverted)".

    3. If the problem occurs in a problem of your own or a modified SAP

    program: The source code of the program

       In the editor, choose "Utilities->More

    Utilities->Upload/Download->Download".

Line  SourceCde

    6   DATA: attributes           TYPE hrpad_field_attribute_tab.

    7   DATA: l_object_key         TYPE hcm_object_key.

    8   DATA: l_subrc              TYPE sysubrc.

    9

   10   FIELD-SYMBOLS <r0002_br>   TYPE hcmt_bsp_pa_br_r0002.

   11   FIELD-SYMBOLS <p0002_br>   TYPE p0002.

   12   FIELD-SYMBOLS <p0625>      TYPE p0625.

   13

   14   is_ok = if_hrpa_ui_convert_standard~true.

   15   ASSIGN screen_structure    TO <r0002_br>.

   16   l_object_key = <r0002_br>-object_key.

   17   MOVE-CORRESPONDING pnnnn TO super_screen_ref.

   18

   19   CALL METHOD super->if_hrpa_ui_convert_standard~output_conversion

   20     EXPORTING

   21       screen_structure_name = a_super_screen_structure_main

   22       pnnnn                 = pnnnn

   23       message_handler       = message_handler

   24       field_metadatas       = field_metadatas

   25     IMPORTING

   26       screen_structure      = super_screen_ref

   27       is_ok                 = is_ok

   28       field_attributes      = field_attributes.

   29

   30   MOVE-CORRESPONDING super_screen_ref TO screen_structure.

   31

   32   CASE a_super_screen_structure_main.

   33     WHEN 'HCMT_BSP_PA_XX_R0002'.

   34       ASSIGN pnnnn                  TO <p0002_br>.

   35       ASSIGN screen_structure       TO <r0002_br>.

>>>>>       ASSIGN pnnnn2                 TO <p0625>.

   37       MOVE-CORRESPONDING <p0002_br> TO <r0002_br>.

   38       MOVE-CORRESPONDING <p0625>    TO <r0002_br>.

[Former Member]

Looks like BR 0002 is looking for dependent infotype 0625.

Create the 0625 infotype and see.

[Former Member]

It's already there 0625 ....