Program names L... are reserved for function group includes

[Former Member]

Hello

We create a function group 'YX24 ", then one include is generated called 'LYX24TOP'. now we want to include one program 'LYX24T00' in this include , but system shows us the error message (see below).

<u>(Program names L... are reserved for function group includes

Message no. DS024

Diagnosis

You attempted to create a program name beginning with L, but such names are reserved for function group includes.

You cannot assign program names identical to those generated by the function library. Reserved name ranges are:

L<function group name>U

L<function group name>$

L<function group name>T

L<function group name>C

L<function group name>V

System Response

You should observe the following for all other program names beginning with L):</u>

I also attached our incldue for you refernce . i know that one ABAP programer made it successuflly in one system (i saw it before), but we do not know how he can realize it. It is appreciated that someone can give us some hints .

<u><b>LYX24TOP

----

---

• generated viewmaintenance function pool top

• generation date: 05.07.2006 at 12:45:27 by user KOUDOUNIS_X

----

---

FUNCTION-POOL YX24 MESSAGE-ID SV.

----

---

• T A B L E S *

----

---

TABLES:

YXLFAVMDET, " Material determination @SIM20030406

YXLFAVIS, " Controll YMXLAVIS/YXWE.. @SIM20030516

YXAVIS_K, " Headerinfo splitted file @SIM20030516

USR01, " User record @SIM20030317

VBAK, " Sales Document: Header @SIM20021203

VBAP, " Sales Document: Item Data

VBEP, " Sales Document: Schedule Line Data

STXH. " Text-Header

----

---

• T Y P E S *

----

---

TYPE-POOLS YXRG1. " "@SIM20030516

TYPES:

• .. relevant data of Sales Document: Header @SIM20021203

BEGIN OF TY_VBAK, " @SIM20021203

VBELN LIKE VBAK-VBELN, " @SIM20021203

VDATU LIKE VBAK-VDATU, " @SIM20021203

AUART LIKE VBAK-AUART, " @SIM20030406

END OF TY_VBAK, " @SIM20021203

" @SIM20021203

• .. relevant data of Sales Document: Item Data

BEGIN OF TY_VBAP,

VBELN LIKE VBAP-VBELN,

POSNR LIKE VBAP-POSNR,

MATNR LIKE VBAP-MATNR,

ABGRU LIKE VBAP-ABGRU, " @SIM20021210

SPRAS LIKE STXH-TDSPRAS,

NOTE LIKE TLINE-TDLINE,

END OF TY_VBAP,

• .. relevant data of Sales Document: Schedule Line Data

BEGIN OF TY_VBEP,

VBELN LIKE VBEP-VBELN,

POSNR LIKE VBEP-POSNR,

ETENR LIKE VBEP-ETENR,

BANFN LIKE VBEP-BANFN,

BNFPO LIKE VBEP-BNFPO,

END OF TY_VBEP,

• .. Message data

BEGIN OF TY_MESSG,

MSGID LIKE SY-MSGID,

MSGTY LIKE SY-MSGTY,

MSGNO LIKE SY-MSGNO,

MSGV1 LIKE SY-MSGV1,

MSGV2 LIKE SY-MSGV2,

MSGV3 LIKE SY-MSGV3,

MSGV4 LIKE SY-MSGV4,

END OF TY_MESSG,

• .. already done flag

BEGIN OF TY_FLAG,

ID(04) TYPE C,

HIGHPOS LIKE VBAP-POSNR,

END OF TY_FLAG.

DATA:

• .. Tables for CALL TRANSACTION

I_BDCDATA TYPE BDCDATA OCCURS 0 WITH HEADER LINE,

I_MESSTAB TYPE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.

DATA:

• .. Table for Sales Document: Item Data

I_VBAP TYPE TY_VBAP OCCURS 0 WITH HEADER LINE,

• .. Table for Sales Document: Schedule Line Data

I_VBEP TYPE TY_VBEP OCCURS 0 WITH HEADER LINE,

• .. Table for Textlines

I_TLINES LIKE TLINE OCCURS 0 WITH HEADER LINE.

----

---

• S T R U C T U R E S *

----

---

DATA:

• .. Workarea for Sales Document: Header " @SIM20021203

W_VBAK TYPE TY_VBAK, " @SIM20021203

• .. Workarea for Sales Document: Item Data

W_VBAP TYPE TY_VBAP,

• .. already done flag

W_ADFL TYPE TY_FLAG, "

• .. Workarea for preparation of message

W_MESSG TYPE TY_MESSG.

*--- WORK-FIELDS

DATA:

BEGIN OF W,

ETDAT LIKE RV45A-ETDAT, " "@SIM20021203

DYNPRO LIKE BDCDATA-DYNPRO," "@SIM20021203

MATNR LIKE VBAP-MATNR, " "@SIM20021203

C_FIELD(10) TYPE C, " CHAR-Field

MODE_CT(01) TYPE C, " mode call transaction

TDNAME LIKE STXH-TDNAME, " Textkey

NOTE(72) TYPE C, " Item note

RETCO LIKE SY-SUBRC, " Returncode

END OF W.

----

---

• C O N S T A N T S *

----

---

CONSTANTS:

BEGIN OF V,

• .. Id's

AD_FLAG_GR TYPE TY_FLAG-ID VALUE '#GR#'," Goods rec. already done

• .. call transaction modes

MODE_DIS LIKE W-MODE_CT VALUE 'A', " display screen

MODE_ERR LIKE W-MODE_CT VALUE 'E', " display screen on error

MODE_NO LIKE W-MODE_CT VALUE 'N', " no display

• .. program names

PG_ORDER_PROC LIKE BDCDATA-PROGRAM VALUE 'SAPMV45A',

PG_TEXTS LIKE BDCDATA-PROGRAM VALUE 'SAPLSTXX',

• .. text

TDOBJ_POS LIKE STXH-TDOBJECT VALUE 'VBBP', " Item text

TDID_NOTE LIKE STXH-TDID VALUE '0002', " Item note

• .. returncodes

RC_OK LIKE SY-SUBRC VALUE '00',

RC_NOTOK LIKE SY-SUBRC VALUE '04',

• .. misc.

REPID LIKE SY-REPID VALUE 'SAPLYX16', "@SIM20030516

END OF V.

• global constants

DATA: GC_FTP_GET(3) TYPE C VALUE 'GET',

GC_FTP_PUT(3) TYPE C VALUE 'PUT',

GC_FTP_MGET(4) TYPE C VALUE 'MGET',

GC_FTP_MPUT(4) TYPE C VALUE 'MPUT',

GC_EPS_IN LIKE EPSF-EPSSUBDIR VALUE 'in',

GC_EPS_OUT LIKE EPSF-EPSSUBDIR VALUE 'out',

GC_EPS_LOG LIKE EPSF-EPSSUBDIR VALUE 'log',

GC_DEF_RECTRA LIKE EPSF-EPSRECTRA VALUE 10,

GC_DEF_TXTRECTRA LIKE EPSF-EPSRECTRA VALUE 1000,

GC_VERS_200 LIKE EPSFTPSI-VERSION VALUE '2.00',

GC_VERS_202 LIKE EPSFTPSI-VERSION VALUE '2.02',

GC_OVRWRI_S LIKE EPSF-EPSOVRWRI VALUE 'S',

GC_OVRWRI_F LIKE EPSF-EPSOVRWRI VALUE 'F',

GC_OVRWRI_R LIKE EPSF-EPSOVRWRI VALUE 'R',

GC_8000_BYTE LIKE EPSF-EPSFILSIZ VALUE 8000,

GC_1000 TYPE I VALUE 1000,

GC_LAYOUT_1 TYPE C VALUE '1',

GC_LAYOUT_2 TYPE C VALUE '2',

GC_MON_FLAG_M LIKE EPSF-EPSTRAMON VALUE 'M'.

INCLUDE LSVIMDAT . "general data decl.

include lyx24t00 . "view rel. data dcl.</b></b></b></u>

[seshatalpasai_madala]

Hi,

It has to be in the customer name space, if you create an include that will be a repository object and it has to be in customer name space that is Z* or Y*. So make sure that you include starts with either Z or Y.

Regards,

Sesh

[Former Member]

Hi,

Thanks ! is there any way to use name space like 'L'? i would like to say one ABAP expert really do not use 'X' or 'Y' , but use 'L' . maybe by user account SAP*, have you tries it or any testing ? thanks !

zhao sheng

[Former Member]

Hello Zhao,

Only include programs that get generated automatically will have their name starting with LY or LZ. So, if you want to have such a program, you have to create it using forward navigation. You can NOT go to SE38 and create it there.

So, type a dummy variable name that does not exist in your function group. Then, double click that variable. The system will ask you whether you want to create it. You have to click yes. After that, the system will display a list of programs inside of which you can create the variable. The very first one is usually a new include of the form L<your function group name starting with Y/Z>_XXX. You can modify the name of this include, but you should keep the section L<your function group name starting with Y/Z>_ and only modify the XXX part (this part does not have to be 3 characters).

Regards,

Abdullah

[Former Member]

I have tried using the method mentioned by Abdullah but the system gives error "Unable to create include LZFI_AADF_CEXX in function group ZFI_AADF_CE".