How To Fix O0006 - & Please consider the OIL naming convention -> Longtext (&/&)

SAP Error Message - Details

• Message type: E = Error

• Message class: O0 - IS-OIL area independent messages

• Message number: 006

• Message text: & Please consider the OIL naming convention -> Longtext (&/&)

News in format: YYYYMM
200402: For CATTs please using prefix "system id" e.g. SO7MIGO_POST,..
History:
for all objects not in the list below, <ZH>use prefix OIx</> where x
named the area (A=OIA* Exchanges, B=OIB* HPM/QCI, C=OIC* MAP, D=OID*
MCOE,F=OIF* MRN,G=OIG* TD,H=OIH* TDP,I=OII* BDRP ,J=OIJ* TSW, K=OIK*
TAS/TPI, M=OIM* Mining;O=OIO* RLM(OLM), R=OIR* SSR, U=OIU* PRA and
0=OI0* <zero> for Oil cross application)
use member OIZ_TEMPLATE to get info,notes and templates about various
areas inclusive a short naming convention (which should match with this
document).
&reference& performance
<DS:TX.BATCH-REPORT>Backround processing information</>
<DS:TX.MK-MATCHCODE_INDEX_AKTARTI>Index for supporting MC selection</>
<DS:TX.MK-MC_INDEX_ANLEGEN>Create index to support MC selection</>
<DS:TX.MK-WANN_PUFFERN>Which tables should be buffered?</>

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

What causes this issue?

<ZH>Please do not ignore this message, and read the following lines,
containing information about OIL (up+down) naming conventions</>
Object &v2& does not match the assigned development class &v3&
Object outside the IS-Oil naming conventions ?!
Special handling for transactions, reserved for development class OI0
(Trans. O3*,O4*,O5*), but should be assigned to dev. class OIA-OII.

System Response

Warning, because some objects within oil development classes can be
outside the oil application naming convention (some object types can't
be checked and will be ignored, that means no warning like MCID,SCAT
,VKO*, DSYS,COMM,DOCV,TOBJ,SUST,UDMO,UEMO).

How to fix this error?

Assign object to development class OIZ, if it is used as a help tool, or
scheduled for a later release than the current one.
Assign the object to "local private object" if possible (no transport
toconsolidation).
Read the following lines to get an overview for the different object
types and the naming assignment.
Please have a look at naming convention of oil objects within your oil
area and adjust the objects name or assign a different dev.-class. In
the following section, you will find the naming convention for different
objects.
<ZH>Program objects</>
Oil Programs Downstream (Includes +OIxyinn, nn with step 10)
ROIxyyyy Report (not XPRAs/conversion pgms.)
ROIxXyyy Report (XPRAs must have "X" at 5.Byte)
SAPFOIxy Formpool
SAPLOIxy Function group, don't create manually
SAPLXOIxy Old SMOD(use BADI !) funct.groups->see below f.further info
SAPMOIxy Module pool
y=free;x=oil applic.(A=EXG,B=HPM...);+=F/M/L;
i: Contents T like TOP (data def.), F = Forms, O=PBO, I=PAI
(SMOD/CMOD user-exits starting with 001 for oil owned programs;
for core programs, start with exit number 400)
Oil obj.within core programs (assign dev. class OIx*, except FUGR)
Oil main includes e.G. MM08R+OI MM08RTOI=data;
MM08RFOI=Forms;MM08ROOI=PBO; MM08RXOI=Enhanced modif. concept /
Modification assistant containing sub-includes TOI,OOI,FOI,IOI
;MM08RIOI=PAI <-main incl.
Sub-includes for MM08R+OI (pls. use step 10 beginning with 10)
MM08R410=data; MM08R310=Forms;MM08R110=PBO,MM08R210=PAI (= old names
please do no longer use this for subincludes); MM08R+OI_EXG, MM08R+OI_EP
(examples for NEW names used as subincludes for MM08R+OI)
Oil includes for core function groups, please use prefix "OI_" and
subincludes e.g. OI_Lxxxx+OI_EP for e.g. PRA subinclude). Please do not
use include names within function group name, e.g. do not use LV61AFOI,
you should use OI_LV61AFOI_xxxxx. Please do no longer use numeric
subincludes like 310, 410, 220 (this was an old naming convention until
40B-release).
Oil main includes in core reports called RxxxxFOI=Forms,RxxxxOOI=PBO
,RxxxxIOI=PAI <-main incl.
CUA functions downstr.: OIyy y=free
CUA statuses downstr. : OIxyyy x=applic.area y=free
Text elements down.: OIy if possible or Oyy (y = free)
Screens : Use name range 08nn or 8nnn, please type in
descriptive text "IS-Oil" in short text
SMOD/CMOD user exits: as 400,to avoid conflicts in core programs/FM
VOFM-routines in core: as 400 (in some cases 300 Brazil or 500 are
allowed).
<ZH>Dictionary objects</> Create appends in display mode of core obj.
Tables / Structures / APPENDS(use always append techniques if possible)
ATAB tables: TOIxy.. x = application area y = free
(e.G. Technical customizing like domain values / no application data)
Transparent applic. data: OIxy... x = application area y = free
Structures: OIx_yyyyyy or ROIxyyyy (screen fields)
Oil appends f.core tables:OILxxxxx xxxxx = name of core table
(can be assigned to each oil development class)
Oil appends f.core DB views: OILVAP_xxxx xxx = name of core view
Views:
Help views H_TOIxy / H_OIxyy -> ! use search help !
Customizing + DB views V_TOIxy / V_OIxyy
Data elements: OIx_yyyyyy
Oil appends f.core DB views: OILVAP_xxxx xxx = name of core view
Supplement of core data elements: numeric value as 400 (entry in THLPF)
Domains: OIx_yyyyyy
Lock Objects: E_TOIxy / E_OIxyy
Matchcode objects: OIxy y=free, x=area
Search help: OIxyyyyy y=free, x=area
Append search help: OIL_xxxx xxx = name of core search help
Other objects: please use prefix OIx_ if possible or OIx
Field names in tables:
table field data element
EXGNUM OIA_EXGNUM <-oil down table e.G. TOI*/OI*
OIEXGNUM OIA_EXGNUM <-oil fld./core table-> use append OILttttt (can
be assigned to each oil development class)
<ZH>Other objects</>
Technical table entries: Use OI at the beginning of the key if possible
, otherwise try to use OI at one key field if possible.
Function groups and module:
Group manually: OIxy
Function modules within core groups: OIx_yyyyyyyyyyyyy_yyyyyyyy
Module downstr.: OIx_yy yy = free within core function groups
Module downstr.: yyyyyyy yy = free outside of core function groups
Dialog module: OIx_yyy yyy = free
Message-ID: Oy y = numeric
Release notes: IS*
Downstream: ISOIL* / IS-OIL*
Authorization(s)
Profiles: J_* (downst. J_OI* )
Auth. objects downst.: O_OIx_yyyyyy (x = oil area, y = free)
Auth. groups e.G. f. SM30: OI*
.... to be continued, other objects pls. use OIx if possible
Transaction codes f. downstream (Application = O3xy / O4xy <MRN/TD/TDP>
- Customizing codes = O5xy -> detail information, see below).
Downstream application trans. (3rd Byte not currently used: K-Z, 7-9;
pls. avoid overlapping between different oil areas)
Application codes OI0: O3xy x = 0 to 6 y=free
Application codes OIA: O3xy x = A or B y=free
Application codes OIB: O3xy x = C or D y=free
Application codes OIC: O3xy x = I or J y=free
Application codes OID: O3xy x = G or H y=free
Application codes OIE: O3xy x = E or F y=free
Application codes OIF: O4xy x = 0 to 6 y=free
Application codes OIG: O4xy x = A/B/C/D/F/G/H/I/M/O/R/V y=free
Application codes OIH: O4xy x = J or K or L y=free
Application codes OII: O4xy x = N y=free
Application codes OIJ: O4xy x = T y=free
Application codes OIK: O4xy x = P y=free
Application codes OIM: O3xy x = M y=free
Application codes OIO: O3xy x = O y=free
Application codes OIU*: O3xy x = U y=free
Downstream customizing transactions
Customizing OI0 codes: O5xy x = 0 - 3/y=0-9,A-Z
Customizing OIA codes: O5xy x = 4 - 7 y=0-9/A-Z
Customizing OIB codes: O5xy x = 8 - 9, A - B y=0-9/A-Z
Customizing OIC codes: O5xy x = C - F,M y=0-9/A-Z
Customizing OID codes: O5xy x = G - J y=0-9/A-Z
Customizing OIE codes: O5xy x = K - L y=0-9/A-Z
Customizing O
Customizing OIG codes: O5xy x = S - V y=0-9/A-Z
Customizing OIH codes: O5xy x = W - Z y=0-9/A-Z
Customizing OII codes: O5xy x = N y=0-9/A-Z
Customizing OIJ codes: O5xy x = T y=0-9/A-Z
Customizing OIK codes: O5xy x = P y=0-9/A-Z
Customizing OIM codes: O5xy x = M y=0-9/A-Z
Customizing OIO codes: O5xy x = O y=0-9/A-Z
Customizing OIU codes: O5xy x = U y=0-9/A-Z

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message O0006 - & Please consider the OIL naming convention -> Longtext (&/&) ?

  The SAP error message O0006 typically relates to issues with the naming convention for objects in the SAP system, particularly in the context of the Object Information Layer (OIL) or similar naming conventions. The message suggests that there is a violation of the expected naming standards, which can lead to problems in processing or accessing certain objects.
  Cause:
  
  
  Naming Convention Violation: The error indicates that the naming convention for the object does not comply with the required format. This could be due to:
  
  Incorrect characters in the name (e.g., special characters, spaces).
  Names that are too long or too short.
  Names that do not follow the specific prefix or suffix rules defined by your organization or SAP standards.
  
  
  
  Configuration Issues: There may be configuration settings in the SAP system that enforce specific naming conventions, and if these are not adhered to, the error will be triggered.
  
  
  Data Entry Errors: Manual entry of object names may lead to typos or incorrect formats.
  
  
  Solution:
  
  
  Review Naming Conventions: Check the specific naming conventions required for the objects you are working with. This may involve:
  
  Ensuring that the names are within the allowed character limits.
  Using only permitted characters (e.g., alphanumeric characters).
  Following any specific prefixes or suffixes that are required.
  
  
  
  Correct Object Names: If you identify any objects that do not comply with the naming conventions, rename them according to the guidelines. This may involve:
  
  Modifying the names directly in the relevant transaction or configuration settings.
  Using transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), or others depending on the object type.
  
  
  
  Consult Documentation: Refer to SAP documentation or internal guidelines that outline the naming conventions for your specific environment. This can provide clarity on what is acceptable.
  
  
  Testing: After making changes, test the functionality to ensure that the error does not reoccur.
  
  
  Seek Help: If you are unable to resolve the issue, consider reaching out to your SAP Basis team or a consultant who specializes in SAP configuration for further assistance.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any specific notes related to error O0006. SAP frequently updates its knowledge base with solutions for common issues.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in managing object names and configurations.
  User Roles and Permissions: Ensure that you have the necessary permissions to make changes to object names, as restrictions may prevent you from renaming objects.
  
  By following these steps, you should be able to address the O0006 error and ensure compliance with the OIL naming convention.