on ‎2014 Mar 25 1:00 PM
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.
Request clarification before answering.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
| User | Count |
|---|---|
| 11 | |
| 8 | |
| 5 | |
| 4 | |
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.