Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: TK - Transport Organizer
Message number: 598
Message text: Application variants may not begin with "SAP&&" or "CUS&&"
The variant &V2& of the report &V1& could not be included as an
application variant in an object list of the Transport Organizer, since
variant &V2& is a system variant.
Names of application variants can begin with "SAP&" or "CUS&".
The variant is not included in the object list.
You can include the variant &V2& of the report &V1& as a system variant
in the object list. The correct syntax is as follows:
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
LIMU VARI <8 or 40 character report name><variant name>Error message extract from SAP system. Copyright SAP SE.
TK598
- Application variants may not begin with "SAP&&" or "CUS&&" ?The SAP error message TK598 indicates that there is an issue with the naming convention of application variants in the SAP system. Specifically, it states that application variants cannot begin with the prefixes "SAP&&" or "CUS&&". This restriction is in place to avoid conflicts with standard SAP objects and customer-specific objects.
Cause:
The error occurs when a user attempts to create or modify an application variant (such as a report variant) with a name that starts with either "SAP&&" or "CUS&&". These prefixes are reserved for standard SAP applications and customer-specific applications, respectively. The system enforces this rule to maintain the integrity of the naming conventions and to prevent potential conflicts or confusion.
Solution:
To resolve this error, you should rename the application variant to ensure that it does not start with "SAP&&" or "CUS&&". Here are the steps to do this:
- Identify the Variant: Determine which application variant is causing the error.
- Rename the Variant:
- Go to the transaction where you manage the application variants (e.g., SE38 for report variants).
- Locate the variant that is causing the issue.
- Change the name of the variant to something that does not start with "SAP&&" or "CUS&&". For example, you could use a prefix that is unique to your organization or simply start with a different character.
- Save Changes: After renaming the variant, save your changes and try to execute the transaction again.
Related Information:
By following these steps, you should be able to resolve the TK598 error and successfully manage your application variants in SAP.
Get instant SAP help. Sign up for our Free Essentials Plan.
TK597
System variants have to start with "SAP&&" or "CUS&&"
What causes this issue? Variant &V2& for report &V1& could not be included as system variant in an object list of the Transport Organ...
TK596
Object is locked for repair &1 (&2)
What causes this issue? Object &V3& is already locked for repair &V1& by user &V2&. Repaired objects cannot be exchanged betw...
TK599
No task for editing objects can be determined
What causes this issue? One or more objects could not be checked for editing because no suitable task was found. "&V1&" was defined...
TK600
*** Authorizations in Change and Transport System ***********************
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.