topic Re: Memory ID in Application Development and Automation Discussions

Memory ID

Former Member — Mon, 04 Aug 2008 14:32:12 GMT

Hello All,

I got one problem with my memory id.

I created one selection-screen with 3 TABS.

SELECTION-SCREEN BEGIN OF TABBED BLOCK tabb1 FOR 20 LINES.

SELECTION-SCREEN TAB (40) tab1 USER-COMMAND tab1

DEFAULT SCREEN 1010 .

SELECTION-SCREEN TAB (40) tab2 USER-COMMAND tab2

DEFAULT SCREEN 1020.

SELECTION-SCREEN TAB (40) tab3 USER-COMMAND tab3

DEFAULT SCREEN 1030.

SELECTION-SCREEN END OF BLOCK tabb1.

*I have a radiobutton group in each of my tabs in the selection screen.

SELECTION-SCREEN BEGIN OF SCREEN 1010 AS SUBSCREEN .

SELECTION-SCREEN BEGIN OF BLOCK gui WITH FRAME TITLE TEXT-004.

SELECTION-SCREEN SKIP 1.

SELECT-OPTIONS lfdat FOR likp-lfdat .

SELECTION-SCREEN SKIP 1.

PARAMETERS: r_9801 RADIOBUTTON GROUP gui,

r_sch1 RADIOBUTTON GROUP gui.

SELECTION-SCREEN SKIP 1.

PARAMETERS : spld LIKE user01-spld.

SELECTION-SCREEN SKIP 1.

SELECTION-SCREEN END OF BLOCK gui.

SELECTION-SCREEN END OF SCREEN 1010.

SELECTION-SCREEN BEGIN OF SCREEN 1020 AS SUBSCREEN.

SELECTION-SCREEN BEGIN OF BLOCK rep WITH FRAME TITLE TEXT-005.

SELECTION-SCREEN SKIP 1.

PARAMETERS : p_refno LIKE z40pat-file_refno .

SELECTION-SCREEN SKIP 1.

PARAMETERS: r_view RADIOBUTTON GROUP rep,

r_upd RADIOBUTTON GROUP rep.

SELECTION-SCREEN SKIP 1.

PARAMETERS : p_spld LIKE user01-spld.

SELECTION-SCREEN SKIP 1.

SELECTION-SCREEN END OF BLOCK rep.

SELECTION-SCREEN END OF SCREEN 1020.

SELECTION-SCREEN BEGIN OF SCREEN 1030 AS SUBSCREEN.

SELECTION-SCREEN BEGIN OF BLOCK rep1 WITH FRAME TITLE text-006.

SELECTION-SCREEN SKIP 1.

PARAMETERS : p_ref LIKE z40pat-file_refno .

SELECTION-SCREEN SKIP 1.

PARAMETERS: r_summ RADIOBUTTON GROUP rep1,

r_record RADIOBUTTON GROUP rep1.

SELECTION-SCREEN SKIP 1.

SELECTION-SCREEN END OF BLOCK rep1.

SELECTION-SCREEN END OF SCREEN 1030.

*********************INITALIZATION **************************

INITIALIZATION.

tab1 = text-001.

tab2 = text-002.

tab3 = text-003.

IMPORT g_acttab FROM MEMORY ID 'zssfsdfr3'.

IF sy-subrc = 0.

tabb1-prog = sy-repid.

tabb1-activetab = g_acttab.

CASE g_acttab.

WHEN 'TAB1'.

tabb1-dynnr = 1010.

WHEN 'TAB2'.

tabb1-dynnr = 1020.

WHEN 'TAB3'.

tabb1-dynnr = 1030.

WHEN OTHERS.

ENDCASE.

ENDIF.

DELETE FROM MEMORY ID 'zssfsdfr3'.

********START_OF_SELECTION********************

START-OF-SELECTION.

g_acttab = tabb1-activetab.

EXPORT g_acttab TO MEMORY ID 'zssfsdfr3'.

What's my problem is It's working fine in DEVELOPMENT but it's not working in PRODUCTION.

It's gives the error like

The system attempted to use dynpro 1010 in program "Z40R208".

This dynpro does not exist.

Regards,

Vandu.

Re: Memory ID

Former Member — Mon, 04 Aug 2008 14:55:18 GMT

Hi Vandana,

Here is some clue.

You designed everything properly in developement system, created a transport and moved the program rite.

According to the error message please check everything has moved properly to the production system means program has moved properly but the screen you designed for this not yet moved to production I guess.

Please check the all the transports and transport log related to this program, verify that all the screens moved to production system.

Re: Memory ID

Former Member — Mon, 04 Aug 2008 15:11:56 GMT

Thanks for ur sugesssion.

i Checked every thing , transport went through ZAP successfully.

I think the Memory ID is the Problem .

My progrm name is Z23P&A.

Please help me?

regards,

Vandu.

Re: Memory ID

Former Member — Mon, 04 Aug 2008 15:44:04 GMT

One more clue...

If it is the problem with the memory Id then...

Before you import the memory u should export the memory to the same id in the other program.

Second clue would be:

Try to double click on that screen number in developement system if it is not asking you to create a new screen and if it asking in the production system then the problem with the screen creation.

According to the error message it is related to the screen I think.

Re: Memory ID

Former Member — Mon, 04 Aug 2008 17:37:56 GMT

Hi Vandana,

Have you checked the related transports in the production server,Does that transport contains the relavent screen.

If so,then try to doubl;e clikc on it.

If the screen exits then there should be some problem..

If it does not exit,then there should be a problem in the Transport...

Once check and confirm..

Thanks & Regards,

Sudheer.

Re: Memory ID

Former Member — Thu, 28 Jul 2011 15:24:36 GMT

Solved