Using Default Data for UCTYP Problem

[dean_hinson2]

Hello All,

Those in the US know about the New Legal Regulation regarding Ultimate Consignee Type (UCT). We have applied most the OSS note from SAP on the GTS-side.  In order to handle issue when the UCT is not replicated to GTS from the ERP-side, we decided to use the Default Data mechanism to determine the UCT by Business Unit.

The Field List fro Default Data is set-up like this..

And the Default Procedure, Defaults Rules and Accesses are configured accordingly.

However, when maintaining the Default Data, the prompt (or drop down) works fine..

but after maintaining the entry, we get this error..

Any ideas why this is happening?

Please let me know your thoughts.

Regards, Dean.

[mouaz_benredjeb · Accepted solution]

Hello,

Quite sure you did it but just to make sure: did you install following OSS note ?

1945148 - US AES: Legal changes in April 2014 - default data, incompleteness check and outbound processing

Regards.

Mouaz

[dean_hinson2 · Accepted solution]

Yes, we did...

[mouaz_benredjeb · Accepted solution]

Could you please try to remove the foreign key from proposal field H_UCTYP and then retry ?

[dean_hinson2 · Accepted solution]

That worked... Thank you....

Any idea why SAP adds that Foreign Key?

[mouaz_benredjeb · Accepted solution]

The foreign key is used to "control" the values that you can put in the field. Basically, the foreign key points to the table where allowed values are maintained.

In some cases, it can be replaced by the data element as in the data element you can as well specify allowed values.

Could you please:

First: Without changing anything (i.e. leaving the foreign key blank), check that the match code is displaying the 4 values you had before (D, G, O and R)

Second: try to add data element /SAPSLL/UCTYP in field data element and recheck that you still have the 4 values in the match code.

[dean_hinson2 · Accepted solution]

The drop-down work fine.. Is that what you are asking?

[former_member215181]

Hi Dean,

I tried the same thing in a "sandbox" system, and it worked ok for me.  My suggestions would be (in the Data Dictionary):

1. In Structure /SAPSLL/CUHD_LOAD_0115_S, make sure that the Check Table and Domain for field UCTYP are both /SAPSLL/CUIND, and that the Foreign Key is set up with:

• MANDT = SYST-MANDT
• CUSCS = (generic)
• CUINC = '011'
• CUIND = /SAPSLL/CUHD_LOAD_0115_S-UCTYP

Use Foreign Key field type "Key fields/candidates", with cardinality 1:CN.

2. In Table /SAPSLL/LEGTPR, make sure that the Check Table and Domain for field UCTYP are both /SAPSLL/CUIND.

The only thing I can see different between your screen-shot and mine, is that in the Search Help, your system has pre-set the Code List Procedure (CUSUS, in your case), whereas mine does not (shows available entries as a separate column).  I wonder if that's significant?

Let us know how you get on.

Regards,

Dave

[dean_hinson2]

Hello Dave,

This is the Foreign Key Definition in /SAPSLL/LEGTPR for UCTYP..