Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Re - Handing of event custom code , Containers in Table maintenace

Former Member
0 Kudos
95

Hi ,

I have a table with 10 fields in it. Requirement is to add a new field and handle the maintenance screen of it.

Existing process.

Now the table is having overview screen say 34 and SIngle screen 35.

On the display of entry in overview screen 34 ->double click on entry it leads me to a two container(s) split logic in screen 35 which is nothing butthe entry being split and converted into a rule code.Bit tricky.

There is event code (02) to handle this and perform form routines for the logic .

My assumption is when i add the new field to this table i will adjust the table and go for a regeneration of screen 34.

But since it is a regeneration , new code is triggered.This new code can change screen logic.it is OK for me if it limits to screen 34.

//When regeneration it pops with two screens to choose with checkbox option . i will opt for only screen 34.

Q1 ->What are all the necesary checks in such scenario's i should take so that the single screen 35 does not have any effect whatsoever for screen 34.

I'm not sure if particular screen 35 holds or not viz event code , container blocks and includes supporting the same.

I want to know if this can be handled clean with no major risks.

//ALternate solution i'm thinking is to handle this with a field addtion without table maintenance generation

i.e add new field adjust table , activate. Drop this new field into screen 34 activate and support the code for new entry field.

Please let me know your comments.

Br,

Vijay

1 ACCEPTED SOLUTION

nabheetscn
Active Contributor
0 Kudos
59

I think it will be a good iead to save your existing code whether it is event or screen logic changes. As soon as you regenrate it both the screen custom changes will be gone. Then you have to manually go and copy paste the code which you have saved earlier plus modify the screen.

Nabheet

4 REPLIES 4

nabheetscn
Active Contributor
0 Kudos
60

I think it will be a good iead to save your existing code whether it is event or screen logic changes. As soon as you regenrate it both the screen custom changes will be gone. Then you have to manually go and copy paste the code which you have saved earlier plus modify the screen.

Nabheet

Former Member
0 Kudos
59

Hi,

When you create a table maintenance, you will create Function Module.

goto the Function module, go to the Layout and with out regenarating you can add the custom field where you want to

display both in the 1st screen and the 2nd screen.

then coming for custom code to fill data check in chain and endchain you need to specify that new field if you are doing some validation.

and add a module inside chain and endchain, to do validation in the PAI of the Corresponding screen.

if you regenerate the Table maintenace, the previous codes will be get lost before regenerating the maintenance you need to take a back up of code and paste the same in the newely generated table maintenance.

Thanks,

Vinayaka

0 Kudos
59

Hi ,

Yes, i have a temp func group to handle the back up of the code .

As i said that will be my second alternate solution.This is a workaround solution!

Im trying to implement the first solution and in here im looking at options to maintain the screen(s) with no major hurdles.

Br,

Vijay.

Edited by: sniper on Oct 19, 2010 11:00 AM

Former Member
0 Kudos
59

implemented second logic where in i did not generate single screen ,but adjusted the code in table maintenance explicitly.that solved the problem.

in cases such as the above better to handle the new field additions explicitly .