topic Re: User interface with oops concept in Application Development and Automation Discussions

User interface with oops concept

virendra_singhsomwanshi — Thu, 24 Oct 2013 12:19:24 GMT

Hello Everybody

Act. I am working in a project in which i have to create a user interface for creating, changing and approval (1st and 2nd level) screen under one transaction. Each screen have different layout and selection parameter. I have divided the screen into three part 1st part is navigation tree, 2nd part is selection and 3rd is main data screen in which creation changing and approval screen will be populated as per the selection screen and navigation tree. I hope this will give you a clear picture :

____________________________

| 1st | 2nd |

| | |

| |_____________________|

| | 3rd |

| | |

|_____ |_____________________|

My query is : what is the best practice(way) to achieve this requirement with the help of oops concept? There are so many classes to achieve this requirement. So I want to know what will be the best way to achieve this goal?, what are the classes should I use and what should be the flow of my program.

Thanks and Regards

Virendra Singh Somwanshi

Re: User interface with oops concept

virendra_singhsomwanshi — Fri, 25 Oct 2013 08:22:10 GMT

Re: User interface with oops concept

virendra_singhsomwanshi — Sat, 26 Oct 2013 06:56:42 GMT

PLEASE HELP

Re: User interface with oops concept

Former Member — Mon, 28 Oct 2013 09:56:13 GMT

Hi,

first of all, check the SAP Examples - Transaction DWDM.

Then without explaining the details of the 3 screens its hard to tell.

But something like the Examples - first screen might be a list tree.

Some buttons and header stuff in the Second Screen and third screen displays whatever you need.

greetings

Re: User interface with oops concept

virendra_singhsomwanshi — Wed, 30 Oct 2013 15:05:49 GMT

Hi Klaus

Thanks for the reply

Detail of 3 screens are :

1st screen is a list tree in which there will be options of create, change and approval (1st level and 2nd level), as soon as user click on any option, according to that selection screen(2nd screen) will open.

In 2nd screen, there will be parameters and select options, where user enter any data for example: transporter information and hit enter or click on execute button then transporter name will be display on the same screen (this is second screen which is selection screen) and according to the selection data third screen will display data.

Third screen is ALV or table control in which user enter the data and save in create and change screen and during approval there will be alv list with the check box and there will be a button on application toolbar of approval. I hope this will give more clarification to my requirement. My motive is to make in best possible way.

Thanks and Regards

Virendra Singh Somwanshi

Re: User interface with oops concept

Former Member — Mon, 04 Nov 2013 08:57:42 GMT

Hi Virendra,

According to my experience i try to tell you how i will do this.

1st screen) NAVIGATION TREE.

To make clear and easy to use code, i will make a navigation tree with recursion algorithm.This is for sure. Code is easy to understand. Couple of lines. When a new requirment appears it will be easy to extend.

2 st) SELECTION SCREEN

This subscreen should be made with factory pattern. When user click on the node in list tree appriopriate parameters and sel-option will apear ( with factory pattern ). When you will have a new requirment ( new creen for example ), it will be easy. This will give you time at weekend and you will be abble go out with friends

3 st) DATA DISPLAY

That could be easy to use one screen with ALV GRID. Please do not use Table Control. Table Control is old thing. Nobody use this. Is so old that only 65 year old people use it. ALV is 100% better. Why... google search, you have to read about it.

Maybe somebody can give feedback to this idea.

If this is helpful. That will be great.

Good Luck Virendra

and kind regards

Marek