NLS Lookup Cockpit: Maintenance

You can view the results of the Lookup Analyzer in the NLS Lookup Cockpit, including additional information about the translation status and developments found in the translation process. After switching to edit mode, you can also delete rows in which some lookup code was adjusted already or if you need to re-execute the analysis for a specific InfoProvider. You can also mark certain objects asRemove from scope, for example if these code objects are in the $TMP package and therefore not relevant for the productive translation. It is also possible to change the status of certain developments in order to re-execute the syntax check.

Transaction: /DVD/NLS_LOOKUP

One of the two most important columns in the Lookup Browser is the Translation status column, which gives you the following information:

The translation was successful.

The translation was not executed due to an unsupported SELECT form in the Lookup Translator. Manual correction of SELECTs with this statement is required before translation. After manual correction, delete the row with the adjusted lookup in the Lookup Browser, run the Lookup Analyzer again for the specific InfoProvider to find the adjusted lookup, and execute the Lookup Translator. Only the following SELECT types are supported:

SELECT */list of fields FROM active DSO table INTO/APPENDING (CORRESPONDING FIELDS) OF TABLE
Table FOR ALL ENTRIES IN internal table WHERE condition only with AND operators without brackets
Value assignment without variables

NOTE If FOR ALL ENTRIES is referenced to an internal table and is defined using an include, the translation will be marked successful, but during the execution, the load will fail. You can fix this by defining the required table, for example by listing all the required fields in the referenced structure. A similar issue occurs when INTO TABLE is defined as the TYPE TABLE of the data element.

	The translation was unsuccessful. A problem occurred during the translation – check the translation logs.
	The syntax check was successful. The SELECT can be translated correctly using the translation process. The list of supported SELECTs is available in the Lookup Translator description.
Empty	No development was found for translation. No further information is available.
	The code object was marked as not relevant for translation and was excluded from the translation scope. Examples are code objects in $TMP and/or code objects that are not in productive usage. This status is given to the code objects based on user decisions and is not assigned automatically.
	The previously found lookup cannot be found in the same row in the code object.
	The code object is no longer active.

_{NLS Lookup Cockpit – results}

The second most important column is the Token value column. It contains information about why the syntax checks marked the code object as not automatically translatable. In order to execute the translation, you must adjust the SELECT condition so that the syntax check marks the object with a green tick to show that the syntax check was successful. The NLS Cockpit displays a table with multiple columns that are described below:

Code ID	Technical name of the program or routine
Line no.	Line number of the SELECT statement in the code (when displayed directly)
Inv rout	Indicates whether it is an inversion routine or not
InfoProvider	Technical name of the analyzed InfoProvider
Object ID	Technical name of the transformation, update rule, transfer rule, report, class method ID, etc.
Src type/Trg type	Type of source object/target object
Source name/Trg name	Technical name of the source object/target object of the transformation or rule
Field name	Affected field of a field routine
Stat	Translation status
Token	Value that caused the syntax check to mark the code object as not automatically translatable
Hash used for code	Unique hash assigned to translated code. The code is also visible in transaction SE38
Username	Name of the user who executed the translation
Date/Time tran.	Date/time of the translation