How To Fix SDC_ANALYSIS_KIND103 - Document Has no Master Language

SAP Error Message - Details

• Message type: E = Error

• Message class: SDC_ANALYSIS_KIND - INTERNAL: Document analysis - kind of findings

• Message number: 103

• Message text: Document Has no Master Language

&MEANING&
The document exists in several languages, but the master (original)
language is not defined.

What causes this issue?

The original language of the documentation can be the same as the
original language of its main object. However, it is not a 'must'.
For example, for a function module, which belongs to the function group
with original language German, some parameters, which require docu
should be added. The docu creation is done by non-german speaking
person. He creates it in the transaction SE61 with language English.
Therefore, original language of such document will be English.
The value ?X? in field MASTERLANG in table DOKIL defines the original
language. All SAP Tools work with this field, when the original language
needs to be determined.
When this error occurs in the checked system, some language versions of
the document for the affected object exist. But <ZH>NONE</> of them has
the ?X? in the field MASTERLANG to define the original language.
If the original language cannot be determined, no further checks are
performed for such documents.

How to fix this error?

You have to check / verify, if the affected object, for example data
element, message, function module and so on, requires documentation or
not.
If documentation is not required, trigger the deletion of the document
in all languages.
If the documentation is required, two major cases needs to be
considered:
If a version of the document in planned original language exists, this
one could be reused.
If there is none in the desired language, you would have to create the
docu with status ?Active? from scratch.
<ZH>Possible activities to resolve the missing original language</>:
Actions for deleting the document in all languages:
If error is raised for <ZH>Message</> (docu class 'NA'):
Set explicitly self-explanatory flag for the message in transaction
SE91.
Self-explanatory flag means, that 'Object explained sufficiently by
short text' and therefore does not require documentation.
If error is raised for <ZH>Data Element</> (docu class 'DE'):
Use menu: <LS>GoTo->Documentation->Status</> in transaction SE11 and
select one of the statuses: 'Object is not used in any screen' or
'Object explained sufficiently by short text'.
If error is raised for object from another docu class:
Use transaction of your main object, for example, SE37 for function
modules and its parameters or SE24 for classes / interfaces and their
methods. Create the dummy document from there. This is necessary to
receive the required entry in a transport request. Then delete the
document from the Docu-Editor, to get the deletion transported through
the system landscape.
You also can create & delete the dummy document for parameters,
mentioned in the error message, in transaction SE61.
If a version of the document exists in your development / correction
system, creation of dummy document will be not possible. In this case
select the 'Edit' in transaction SE61, make dummy change, to receive the
required entry in the transport request. Then delete the document.
Actions for restoring of the document
On initial screen of transaction SE61 select a language in which
document exists and which you would like to have as original language of
your document.
Use button 'Change' and make dummy change to create / select a transport
request.
If there is no version in the wished language, it is better first to
transport the deletion in all languages as described before and after
that create the document from scratch with state 'Active'.
Actions for creation of the document
Use either transaction of your main object, for example, SE91 for
messages, SE11 for data elements, and create the docu in the original
language of your main object. Or use the transaction SE61 and select the
language, which you would like to have as original language, as well as
document class from error message and document name.
Save the version of the document with state 'Active' and assign it to a
feasible transport request.
&HINTS&
Do not forget to release the transport request, which contains either
documentation object itself or corresponding dictionary / repository
object.

Error message extract from SAP system. Copyright SAP SE.