To provide "variant creation facility" in a Molule pool program

Hi
I have develope a molude pool screen with some input fields.
now I want to provide " variant creation facility" as in standard reports.
I will enable "SAVE" button on the status bar. but I have no idea how to provide
variant creation facility same as in standard reports.
please help me .
Regards
Kakoli

Hi,
I doubt if it can be achieved by standard solution or FMs. But i have an idea. Check the feasibility of implementing it.
Provide 2 buttons. One for saving the variant, other for selecting the variant.
Create a Ztable with variant name as the key field and rest of the screen fields as non key fields. Now, on clicking the save button, update this Ztable with all screen field values. On clicking the get variant button, query this Ztable and provide a popup with available variants. If a variant is selected, populate the values from Z-table to screen.
But can we handle table control with this approach!!!!??? I hope no.
Thanks,
Vinod.

Similar Messages

Variant Creation for the Back Ground Jobs

Hi experts
1) What are the settings we need to consider in the Variant Creation for generating CVC's, Planning Area Initialization, Calculate Proportional Factors and Loading planning area.
2)I believe Process flow to create process chain:
Generate CVC's-->Planning Area Intialization>Load Planning Area Vesrion--
>Calculate Proportional Factors
Please correct if the process flow is not right.
3) Is it require to check the adjust time series for generating CVC's for every time?
4) How to generate the proportional factors for all the products in the single job?I assume that need to create a single selection ID which has all Characteristic values and assign this while creating the Proportional factors.Please correct me if i am wrong.
Please give your valuable opinions on the above queries
Thanks in advance
Edited by: Mani4690 on Mar 4, 2009 9:37 PM

Hi,
Below are the answers to your queries.
1) What are the settings we need to consider in the Variant Creation for generating CVC's, Planning Area Initialization, Calculate Proportional Factors and Loading planning area.
While creating CVC's (t-code /n/sapapo/mc62)select your MPOS, goto create characteristic combinations, then enter Target mpos, say generate in background, tick against all fields in action selection, and then save as variant. During planning area initialisation(/n/sapapo/msdp_admin), select your planning area, right click and say create time series objects and then enter planning version, start and end dates and execute job in background. While calculating proportional factors (/n/sapapo/mc8v), enter ur planning area & infocube and then save as a variant. For loading data from infocube to planning area (tcode /n/sapapo/tscube), select the infocube, planning version, planning area, planning versin, periods, tick mark in results log, key figure assignments, if you have any selection criteria enter, and then save as variant.
2) 2)I believe Process flow to create process chain:
Generate CVC's-->Planning Area Intialization>Load Planning Area Vesrion--
>Calculate Proportional Factors
Please correct if the process flow is not right.
Correct
3) ) Is it require to check the adjust time series for generating CVC's for every time?
Yes, it is required.
4) How to generate the proportional factors for all the products in the single job?I assume that need to create a single selection ID which has all Characteristic values and assign this while creating the Proportional factors.Please correct me if i am wrong.
if you use mc8v t-code and provide planning area & infocube, it will ask for version name and dates, once u enter this info, proportional factors will get created.
Regards
R. Senthil Mareeswaran.

Variant Creation in SAP BI To be used information broadcasting

Dear Friends,
I want to create a VARIANT in SAP BI 7.0 Which is to be used in information broadcasting. I found One Document Named as "Variant Creation In SAP BI to be used in Information Broadcasting.pdf",in SDN Forums. I Couldn't able to Understand the Given Steps in it.
Could any one of You Please send me the Procedure how to create a Variant.I should also see the "Determine from Variants" button in Work book precalculation Tab,which i am not able to see it currently under "Workbook Precalculation".
Waiting for ur reply.
Thanks in advance
Regards
Singam Bhaskar Reddy

Hi,
Even I have gone through the SDN document. It is clearly explained step by step. If you follow the same document thoroughly you will be able to see Determine From Variants radio button properly.
Try to understand the document.....you will get the solution.
Regards,
Suman

Variant creation

Hi,
We have a variant for a SE38 program, which is being used by a batch job to execute the program in the background.
We would like to change the variant directly in production, but find in the attributes that the variant is protected.
My questions are:
1) How can I change the variant
2) If I cannot change the variant then I would like to delete it and create a new variant with the same name. In that case how can I enter values in the attributes? Because on the selection screen of the program, there is a field called Idoc Run Date. This field should be populated dynamically. In the current variant (which we would like to change) find that there is a parameter for idoc run date RS_VARI_V_TODAY_X.
3) If I delete the existing variant will it also delete the parameter RS_VARI_V_TODAY_X.
4) How do I create the parameter RS_VARI_V_TODAY_X (or any other parameter). and attach it to the new variant.
Any help would be appreciated.
Thanks in advance.
MIck

Run your program in online mode in production.
On the selection screen, put all the values you want to store as variant.
Now press the Save button.
You will be directed to Variant creation screen.
Give your variant name.
Save it.. it will ask for "overwritten".. say yes.
Regards,
Naimesh Patel

AFAB dynamic variant creation for Posting period.

HI,
Business Requirement :
Business want to run AFAB transaction code every month automatically with schedule job.
system should pick present month period in posting period field.
i checked in variant creation against posting period there is no dynamic " D " in selection variable column.
how can i fix this.

Hi Jani,
Check with abaper if TVARV table can Help you in this case, or create a z program from AFAB. And add date field to it, and schedule job based on that,
I think TVARV table will be a better approach.
Another point to consider here would be that dep should be run once business is ready to do so, and has its own hick ups in business if corrections are required to be made after executing AFAB by job
Regards
Pankaj B.

T.code for Variant creation

Hello Gurus,
What is the T.code for variant creation
regards
sapmm

Dear sapmm99,
In my understanding the default values that should be automatically reflected for the input parameters for executing any report is
referred as a variant.
Say for Eg,executing report MB52,in case if I execute the report several times with the same input,i can save the input parameters
and create that as a variant and in future i can call this variant to reduce the work load and execute the report.
For eg: enter the plant 1000,material type as FERT,some material group and click on the save icon and the system asks to enter
the variant name and the meaning and then select the check boxes for protect variant and click on copy screen assignment.
If i want to protect the entered input parameters i can select the check boxes for the same and save and come out.
Next time when i execute the same report MB52 and if I need some default values to get copied,i can get the variant by clicking on
get variant or else Shift+F5 and select the saved variant.
Check the same for the reports like ME5A.
Check and revert.
Regards
Mangalraj.S

SDHO - question on variant creation

"Hi team
I need you HELP!!
I have generate a transaction variant for tcodes: CO11N and CO15 then I have assigned some users to both transactions.
in SHD0
First I set the users to CO11N variant --> assign variant and set proposal.
with the same group of user i set the variant for tcode CO15.
when testing I realized the the field quantity in Good movements was non editable in CO15 (the last configuration for the list of users).
but in CO11N it was editable
I know there is an option to active the variant at the begginig of the transaction but this is not a solution since it makes for ALL non editable and not only the listed users. Also it affected all not considering the user assignenment.
How can I make it non editable in CO11N and CO15 at the same time for the list of users??
TCode CO11
Transaction variant: ZCO11NNCO11N
Variant Group: ZCO11NN
and
TCode CO15
Transaction variant: ZCO15NNCO15
Variant Group: ZCO15NN
question 2: Can the program SAPLCOWB has 2 transaction variant assigned at the same time?
thks in advance!!
PLS help!!!

any ideas?
can the program SAPLCOWB has to variant ?
1- co11n
2 -co15
thks!

How to create transaction or screen variant for custom tcode in module pool

Hi,
I have one module pool program with custome tcode ,i want to create transaction or screen variant for this tcode.Next time when we run this tcode we need a variant for this tcode.
I tried by using of SHD0 but it is working only for standred tcodes.Is there any possibilty please help me.
thanks,
Lavanya.

Hi,
you created a Custom Tcode for ur module pool Pgm..if u execute the Tcode in the output screen give the input details and press Save Option then variant will be created. Then you can use that variant.
otherwise.. while creating a Tcode..
select an option for Tcode type Tranasction With variant ..there u will provide the variant for ur Tcode ( which is already created ).
Regards,
PraVeen.

There is any Performance problem with Creation of many Y or Z Programs.

HI,
There is any Performance problem with Creation of many Y or Z Programs. plz give clarity regarding this to me......
regards
ganesh

Ganesh,
Can you please mention the context and the purpose of creating these custom program. And application are you referring to?
Regards,
Rohit

Save/create a variant in user defined screen in dialog program

is there a way to save/create a variant in user defined screen in dialog program?
thanks...

Few important tables for Variants:
VARI - ABAP/4: Variant storage (similar to INDX)
VARID - Variant directory
VARINUM - Internal number assignment for variants
VARIT - Variant texts
TVARV - Table of variables in selection criteria
TVARC - Variant conditions
TVARUVN - Individual Variant Variable: Assignment TVARV
TVARCT - Text for Variants Conditions
TVARH - Header entries for screen variants
TVARIND - Save screen variants
Regards,
Vishal

How to provide select-option in module pool programming

Hi all,
How to provide select-option in module pool programming.
If any body knows let me immediately.
Thanks
sudheer

Hi Sudheer,
Unfortunately there is no standard way of having a select-option in a module pool program.
What you can try is having two fields and creating a range in your program and populating the range at runtime with respective value and trying to simulate some functionality of the select-option.
Hope it helps.
Thanks, Debasish

How to store the variant in Module Pool Programming

Hi,
I have the module pool program which is having 4 screen. depends on the first and second screen, third screen is called. i want to store the data of third screen to the variant. All the screen except first screen is a subscreen.
Regards,
Dhiraj.

Hi Dhiraj,
You can create a variant only for a Report. Module Pool Programs require a dialog with the user & hence creating a varint is not possible. You can possibly create some Parameter IDs & default values in there.
Regards,
Suresh Datti

Plz provide tutorial to learn the Module pool programing?

Hello,
Please provide me with the Tutorials which will be helpful to learn Module Pool Programming.
If any one can provide me with the screen shots then it would be great!
ANy help would be appreciated......
Thank You!
Krishna Chaitanya

Hi,
Screens are the most general type of user dialog that you can use in ABAP programs. You do not define them in ABAP programs, but instead in the Screen Painter. A screen consists of the input/output mask and the flow logic. You can define screens for any program with type 1, M, or F.
The screens in a single ABAP program can be combined to form screen sequences. You can call single screens or screen sequences either using a transaction code from outside the ABAP program, or by using the CALL SCREEN statement in the corresponding ABAP program. When you call a screen or screen sequence, the screen flow logic takes control of the ABAP program execution. You can define screen sequences dynamically by setting the next screen attribute for a screen dynamically in the ABAP program.
A screen consists of the input/output mask and the flow logic. The screen flow logic is divided into the Process Before Output (PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen.
The following diagram shows the place of screens between the GUI status and the ABAP program:
The screen flow logic calls dialog modules in the ABAP program, either to prepare the screen for display (PBO event) or to process the user's entries (PAI event). Screens are dynamic programs, and have their own data objects, called screen fields. These are linked to the input/output fields that appear on the screen itself. When the screen is displayed, and when it finishes processing, the system passes data between the screen fields and data objects in the ABAP program. Data is copied between identically-named fields.
Each screen has a GUI status, containing a menu bar, standard toolbar, and an application toolbar. Like screens, GUI statuses are independent components of the ABAP program. You create them in the ABAP Workbench using the Menu Painter. You assign GUI statuses to screens dynamically in your ABAP programs. Each screen is linked to the current GUI status by a special screen field into which the corresponding function code is placed whenever the user chooses a function. The screen passes the function code to the ABAP program just like any other screen field. You can then read it in the program.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Check the below link:
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Regards
Kiran Sure

Is it possible to save a variant in Module Pool program

Hi,
We have got a requirement to save a Variant for the user selections in Module Pool Program. Is it possible to save a variant in a Module Pool Program?
Please let me know how to do that if it is possible.
Thanks in Advance.

hi Dagny,
You can't have variants for module pool. It is possible only for selection screen.
You have following alternatives :-
1. Create a report with same selection screen as you have now in module pool.
And then make a call screen to your intial module pool.
In this way you can all the advantage of variants as well as module pool.
OR
2. Create a transaction variant using transaction SHDO.
Hope it is helpful.
and do search the form , it is already answered before.
regards
venkat

Reg : Variant saving for Module Pool Programming

Hey Friends,
Plz help me in how to create variant for Module Pool Programming as in normal reports.Thanx in advance.

Hi,
You can create variants for Module pool program using the transaction SHD0. You can create Screen variants for your screens using this Tcode.
Go to SHD0 -> Give the Transaction code(ZTRAN) for which you want to create a variant -> name of some variant (ZVAR) -> create -> takes you to your transaction -> Give the values that you want to be displayed as variants -> Click on Save -> Opens a pop up to confirm the screen entries -> Check the check boxes of those fields that you have entered the data with (the column with check boxes that says W.Content) -> Exit and Save -> Save the variant -> You can see a screen variant created (ZVAR_0100)
Now Goto -> Create variant transaction -> Give your transaction variant name (ZVAR) -> Select Transaction with variant -> Takes you to SE93 transaction -> Give the transaction variant name -> save. Run with the created transaction.
Edited by: Nitwick on Jul 27, 2009 4:49 PM

To provide "variant creation facility" in a Molule pool program

Similar Messages

Maybe you are looking for