Category Archives for "SAP Erros"

Error message Special character “_” in generic key

I got this error when entering a value into a key field of a custom SAP table. I am still not really sure why this error occurred as the solution I found was not really related to the error text as I just reduced the key size of the table.

The overall key length of my table was greater than 120 characters. I therefore got it done to 115 and re-built the SAP table maintenance. After I had done this everything worked fine and was able to add entries with the “_” character via transaction .

FL389 – Only tables with flat line structure are allowed in RFC – SAP error message

The SAP message FL 389 can also appear if you are assigning a structure which contains a string field to a function module tables parameter. Within an RFC enabled function module it shows this message as a success message but will not let you save.

You get a slightly different message  with none RFC enabled functions modules but has the same effect “<TABLE> must be a flat structure. You cannot use internal tables, strings, references, or structures as components.


Solution
Using the function module tables parameter is obsolete so the simple solution would be to create a table type of your structure and then create a EXPORTING or CHANGING parameter based on this.

Create table type via transaction SE11

table_type

 

 

 

 

 

 

Create EXPORTING/CHANGING parameter

exporting

 

 

 

 

 

 

Table Maintenance dump – Negative value

table_maint_errorIf you get the following error when you access your table maintenance via transaction SM30 it is probably due to negative values within your table fields.

Category: Error at Screen
Runtime Runtime Errors: DYNPRO_FIELD_CONVERSION

These may be stored in currency fields and be perfectly valid but SAP does not seem to be able to deal with them if you create your table maintenance directly on the database table, see OSS Note 329857.

The solution is basically to create a Maintenance View for your table via tcode SE11 and then create your table maintenance based on this. You don’t have to do anything clever in the View just add the single table and all its fields. Then create the tab maint from within the view. Then simply enter the view name via SM30 instead of the table name…simples!!!