Step 1: Deactivate the &* functions and operation

1. Transaction PE04

And select the &* entries

Other than &DECI, please follow the steps as follows. In this document I’ll show the steps for &CURR.

Select &CURR and Enter:

Press Change and acknowledge the information:

In the Country assignment, Scroll down and you will see the entry Non profit Organization Checked.

Uncheck the entries. It should look like

Save and Exit.

After repeating this step for all &* Entries, go to transaction SE38, and check the program HUNCALC0. This program should not have any syntax error. If it has any then the deactivation of one &* feature is not done correctly. Please repeat the steps.

Note: Do not deactivate &DECI

Step II: Regenerate all $TMP objects to make them Unicode compliant.

Transaction SE38 and execute report RPUMKG00 (Based on the note 573044)

That’s all.

If the data transfer Workbench (SXDA) does not have the necessary structure.

To correct this we need to maintain entries in the following two tables: SXDA2 (SAPDXfer: Structure Info for Data Transfer Object) and SXDA3 (SAPDXfer: Field Info for Data Transfer Object). Once you have the entries here these tables, the data transfer programs will start recognizing and parsing the input structures accordingly.

Let’s see the step by step procedure for maintaining the infotype 1080 in the SAP HR module. The corresponding structure is E1P1080. For this purpose, the Key for data transfer object is 0777. How did we find that out? By debugging the upload program and I will check if there is any better way to do this.

Since these structures are not available, all we have to do this is to add this structure in the SXDA2 table and the key fields in the SXDA3 table.

For SXDA2 table, let’s see the available components in the 0777 key. The way to see is transaction SM30 and maintain the list with key 0777.

The last position was 83 and the structure was E1P1063.

To add, press the ‘New Entries’

And Add the new info type like the following:

And press the Active button.

And confirm the following message.

In the same way do the changes to the SXDA3 table, which is going to have the key elements. Use transaction SM30 and maintain SXDA3.

Confirm the following message:

Position on the key 0777 and the item 83 (Which was the one we identified as the last item existed in SXDA2 before our addition. We added item 84)

Create ‘New Entries’ as below:

Remember to check the Active box. Save the entries confirming the following:

Save the changes in a transport.

Repeat the same for the following key fields:

That’s all. The whole process can be repeated for any new structure that needs to be used in the data transfer workbench.