Create transaction with variant not working

Hello!
Here's my issue -- I have a program that, right now, is more of a shell than anything else. It is to access the HR Logical Database PNPCE, and to help filter the data I pull back, I created a Selection View with a couple of additional fields. I put the necessary values in these fields and saved it as a Variant.
All I want to do is create a transaction to run my program and start it using my Variant to fill in these additional fields. Using SE93, I can create a plain transaction with no problem. However, if I click the "Start with variant" drop-down field, I get a response that says screen 1000 (my default Selection Screen) has no variants.
At first we thought there was some client-side things needing configuration, but if I go create a quick-and-dirty program with a single Selection Screen value (no Selection View) and a Variant, SE93 sees the variant with no problems. So I'm wondering if maybe it has something to do with the fact that I'm using a Selection View. Unfortunately, I'm so new to ABAP, I'm completely stuck on how to proceed.
Any suggestions? Thank you so much!

Saquib, thank you SO much! You're right -- that worked.
As a relative newbie to SAP R/3 and ABAP, I'm new to little quirks like this. In other examples, the list (F4) does show the variants. For some reason, this one didn't. I entered it anyway, saved, and ran the transaction, and it popped up with the fields populated from the variant.
Again, kudos and thank you so much. Points duly awarded.

Similar Messages

Create transaction with variants

Hello All
How to create a transaction with variants ? I m aware of the Tcodes SE93 and ShD0. but how to go about it?
when I entered the details in se93, I got an error message as " variant does not exist"
when I entered the details in ShdO, I got an error message as transaction does not exist.
I Dont have access to SHDS transaction.
Kindly advise.
Thanks.

SE93>(name of the cutom TCODE)Select the Parameter TCODE>You will get a screen with lot of inputs
In Default values select the Transactio option > enter SM30>Check skip initial screen(if u dont want to see the initial screen in SM30).
In GUI support (Check all the Check boxex).
(Last option in the screen ie.defaults)
Name of the scrren field       Values
VIEWNAME                     <View name>
UPDATE                             x

'Create' Push button is not working in BDC and LSMW while uploading G/L master data

Hello Experts:
I am facing the following problem:
While uploading G/L master data with the BDC program, 'create' push button is not working even after executing following lines.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
Create G/L account screen is not coming in BDC. Please suggest me what to do.
Thanks !!

Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Re: 'Create' Push button is not working in BDC and LSMW while uploading G/L master data
Hi Glen Anthony
Thank you for the reply Glen Anthony please take a look at the following code.
REPORT ZFI_BDC_FS00
        NO STANDARD PAGE HEADING LINE-SIZE 255.
*INCLUDE BDCRECX1.
TYPES : BEGIN OF STR,
   BUKRS TYPE GLACCOUNT_SCREEN_KEY-BUKRS,        "Company Code
   SAKNR TYPE GLACCOUNT_SCREEN_KEY-SAKNR,        "G/L Account Number
   KTOKS TYPE GLACCOUNT_SCREEN_COA-KTOKS,        "G/L Account Group
   XPLACCT TYPE GLACCOUNT_SCREEN_COA-XPLACCT,    "P&L statement account
   XBILK TYPE GLACCOUNT_SCREEN_COA-XBILK,        "Indicator: Account is a balance sheet account?
   TXT20_ML TYPE GLACCOUNT_SCREEN_COA-TXT20_ML, "G/L account short text
   TXT50_ML TYPE GLACCOUNT_SCREEN_COA-TXT50_ML, "G/L account short text
   WAERS TYPE GLACCOUNT_SCREEN_CCODE-WAERS,      "Account currency
   XSALH TYPE GLACCOUNT_SCREEN_CCODE-XSALH,      "Indicator: Only Manage Balances in Local Currency
   MWSKZ TYPE GLACCOUNT_SCREEN_CCODE-MWSKZ,      "Tax Category in Account Master Record
   XMWNO TYPE GLACCOUNT_SCREEN_CCODE-XMWNO,      "Indicator: Tax code is not a required field
   MITKZ TYPE GLACCOUNT_SCREEN_CCODE-MITKZ,      "Account is reconciliation account
   XOPVW TYPE GLACCOUNT_SCREEN_CCODE-XOPVW,      "Indicator: Open item management?
   XKRES TYPE GLACCOUNT_SCREEN_CCODE-XKRES,      "Indicator: Can Line Items Be Displayed by Account?
   ZUAWA TYPE GLACCOUNT_SCREEN_CCODE-ZUAWA,      "Key for sorting according to assignment numbers
   FSTAG TYPE GLACCOUNT_SCREEN_CCODE-FSTAG,      "Field status group
   XINTB TYPE GLACCOUNT_SCREEN_CCODE-XINTB,      "Indicator: Is account only posted to automatically?
   END OF STR.
DATA : ITAB TYPE TABLE OF STR WITH HEADER LINE,
        IT_BDCDATA TYPE TABLE OF BDCDATA WITH HEADER LINE,
        TXT(4096) TYPE C OCCURS 0,
        MSG TYPE STRING,
        COUNT(5) TYPE N.
SELECTION-SCREEN : BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
   PARAMETERS : MY_FILE TYPE RLGRAP-FILENAME.
SELECTION-SCREEN : END OF BLOCK B1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR MY_FILE.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
    PROGRAM_NAME        = SYST-CPROG
    DYNPRO_NUMBER       = SYST-DYNNR
*   FIELD_NAME          = ' '
IMPORTING
    FILE_NAME           = MY_FILE
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
   EXPORTING
*   I_FIELD_SEPERATOR          =
*   I_LINE_HEADER              =
     I_TAB_RAW_DATA             = TXT
     I_FILENAME                 = MY_FILE
   TABLES
     I_TAB_CONVERTED_DATA       = ITAB[]
EXCEPTIONS
    CONVERSION_FAILED          = 1
    OTHERS                     = 2
IF SY-SUBRC <> 0.
* IMPLEMENT SUITABLE ERROR HANDLING HERE
ENDIF.
START-OF-SELECTION.
COUNT = 0.
LOOP AT ITAB.
*PERFORM OPEN_GROUP.
REFRESH IT_BDCDATA.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=ACC_CRE'.
*PERFORM BDC_FIELD       USING 'BDC_CURSOR'
*                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-SAKNR'
                               ITAB-SAKNR. "'5'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_KEY-BUKRS'
                               ITAB-BUKRS. "'TATA'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_GROUP'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-KTOKS'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=2102_BS_PL'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-XBILK'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               ITAB-XPLACCT. "''.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB02'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-KTOKS'
                               ITAB-KTOKS. "'GL'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-XBILK'
                               ITAB-XBILK. "'X'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_COA-TXT50_ML'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                               ITAB-TXT20_ML. "'G/L ACCOUNT'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                               ITAB-TXT50_ML. "'G/L ACCOUNT'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=TAB03'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-WAERS'
                               ITAB-WAERS. "'INR'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XSALH'
                               ITAB-XSALH. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                               ITAB-MWSKZ. "'*'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                               ITAB-XMWNO. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                               ITAB-MITKZ. "''.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                               ITAB-XOPVW. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XKRES'
                               ITAB-XKRES. "'X'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                               ITAB-ZUAWA. "'1'.
PERFORM BDC_DYNPRO      USING 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
PERFORM BDC_FIELD       USING 'BDC_OKCODE'
                               '=SAVE'.
PERFORM BDC_FIELD       USING 'BDC_CURSOR'
                               'GLACCOUNT_SCREEN_CCODE-XINTB'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                               ITAB-FSTAG. "'G019'.
PERFORM BDC_FIELD       USING 'GLACCOUNT_SCREEN_CCODE-XINTB'
                               ITAB-XINTB. "'X'.
*PERFORM BDC_TRANSACTION USING 'FS00'.
CALL TRANSACTION 'FS00' USING IT_BDCDATA MODE 'E' UPDATE 'S'.
COUNT = COUNT + 1.
*PERFORM CLOSE_GROUP.
ENDLOOP.
CONCATENATE COUNT ' RECORDS UPDATED SUCCESSFULLY' INTO MSG.
MESSAGE MSG TYPE 'I'.
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
   CLEAR IT_BDCDATA.
   IT_BDCDATA-PROGRAM = PROGRAM.
   IT_BDCDATA-DYNPRO   = DYNPRO.
   IT_BDCDATA-DYNBEGIN = 'X'.
   APPEND IT_BDCDATA.
ENDFORM.
*        INSERT FIELD                                                  *
FORM BDC_FIELD USING FNAM FVAL.
* IF FVAL <> NODATA.
     CLEAR IT_BDCDATA.
     IT_BDCDATA-FNAM = FNAM.
     IT_BDCDATA-FVAL = FVAL.
     APPEND IT_BDCDATA.
* ENDIF.
ENDFORM.

Axis bank net secure with webpin not working on ipad2

Hi,
Axis bank net secure with webpin not working on ipad2
Lt me know how to proceed

Try using their App:
https://itunes.apple.com/in/app/axis-bank-mobile-application/id517266358?mt=8

Since installing Yosemite, Airplay with Freebox not working

Since installing Yosemite, Airplay with Freebox not working
With Maverick Airplay working well

If you haven't done so already, try resetting the printing system.
OS X Mavericks: Reset the printing system also Yosemite
Try deleting the printer and scanner and add them back.
Also try Applications/Image Capture to see if it can find the printer and scanner.

How enter the values in to table when create entries option is not working

hi everyone,
can u please tell me How enter the values in to table when create entries option is not working.
it's urgent.
thanking u all

Hi Shree,
how many entries u want to insert ,,
is it a ztable or custom table ..
just tell me ur clear requirement ..
clarify the same ..
if no options avaliable then if its less entries or some value u can do it through debugging ..
if its bulk entries then u can write a program ..
just let me know ..
regards,
VIjay

Wifi connection with 4s not working after installing new software ios6

wifi connection with 4s not working after installing ios 6.

Go to Settings > WiFi > Select your network and hit the right arrow to "Forget Network"
Then go to Settings > General > Reset Network Settings and try connecting again when the phone restarts.

I'm having constant problems with pages not working. I.E.: I cannot fill in writeable fields, click on buttons... or anything... nothing on the page works. And, this is not exclusive to a particular site. I can, however, work well in Explorer.

For the last few weeks I have had constant problems with pages not working. I.E.: I cannot fill in writeable fields, click on buttons... or anything... nothing on the page works. And, this is not exclusive to a particular site. It does seem to be a browser issue, because I can work well in Explorer.

Both the Yahoo! Toolbar extension and the Babylon extension have been reported to cause an issue like that. Disable or uninstall those add-ons.
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

Applications associated with workstations not working

Hello,
I have onld zen 7.x, on netware.
Applications associated with workstations not working or appearing in one container. Not sure if it every worked. Apps work fine with users.
I am in a bind, since I need to get the app out in the workstation space.
It maybe rights or simple install error with the ZEN from the begining.
thanks for any help or ideas.. Yes I know I need to get to Zen 11.
Phil

PhilJannusch,
> Applications associated with workstations not working or appearing in
> one container. Not sure if it every worked. Apps work fine with users.
>
> I am in a bind, since I need to get the app out in the workstation
> space.
Please tell us more as "not working" can mean a lot of things. So:
Are they user or workstation associated?
Are those for whick they do not work (users or workstations) all in the
same container?
In what way do they not work?
Any errors?
Anders Gustafsson (NKP)
The Aaland Islands (N60 E20)
Have an idea for a product enhancement? Please visit:
http://www.novell.com/rms

I am getting frustrated with Apple not working with Flash player on some of my favorite web sites. Is there any alternative that will work on I-pad instead of flash?

I am getting frustrated with Apple not working with Flash Player on some of my favorite web sites! Is there another alternative to watching these site options on my I-pad?

Flash is not, and probably never will be, supported on the iPad : http://www.apple.com/hotnews/thoughts-on-flash/ . Plus it would be up to Adobe to make a version of their flash player that works on iOS devices - something which they have never managed to do and which they have now given up on trying to do.
Browser apps such as Skyfire, iSwifter and Puffin 'work' on some sites, but judging by their reviews not all sites. Also some websites, especially news sites, have their own apps in the App Store, so your could try checking there for your sites (and there is the built-in YouTube app).

My orignal computer that I sync my iPhone 4 with does not work...can I sync it with a new computer?

My original computer that I set up my iPhone 4 with
Does not work.....can I use a new computer to sync
The phone....how do I do this and is there a risk of
Of losing any apps, music etc

Try this:
Syncing to a "New" Computer or replacing a "crashed" Hard Drive

Transaction variant not working in quality

Hi,
I have created a transaction varient in SHD0 and activated it in develpoment and then
it is working fine in development system.Then variant transported to quality and there also
it is activated but somehow it is not working in qulaity sytem.
I checked in the respctive transaction with following path
SYSTEM>>>>>STATUS>>>>>SAP REPOSITORY DATA and i can find it is transaction variant name
below screen program.
Pl suggest the resolution.
Regards,
Rushikesh

Hi,
Check the variant is transported properly in QA. If present then check the transaction for the same.
If you make this transaction for a table the check the table delivery and maintenance allowed or not. It should be maintenance allowed.
Thanks
Subhankar

Screen variant not working when assigned to transaction variant in SHd0

Dear All,
User requires tax code column for line items in MIRO to be made non-editable. I am using SHD0 transaction for the same. I am able to make the column grey-off by creating screen variant. The program is SAPLMR1M and screen number 6310. When tested individually thru SHD0 the variant is working perfect. But it is not working when assigned to a transaction variant. Any clues on the same would be really helpful.
Thanks in advance
Komal

Hi,
Try to record again for the whole set of screens instead of doing that for the individual tax screen and only for the tax screen make the required field disable.
Once done and saved, you can see all the screens variants in the transaction variant.
Use the Change WITH PROCESSING OPTION.
Hope this solves your problem
Regards
Shiva

Transaction variant not working

Hey,
I am facing with this peculiar problem of transaction variant. I created a transaction variant as desired by my client for VA01 and activated the same. I checked the status in the transaction VA01 and there it showed that the transaction variant has been successfully applied. But when I check for the fields that I wanted to be made non editable or invisible the same was not reflected in the transaction. Now after trying enough like creating new transaction variants, adding new screen variants to the existing transaction variant, somehow it has started working. But now when I change the transaction variant, even after activating it, the changes in the variant are not reflected in the transaction. Old changes are being reflected. Please advise!
The reconstruction steps are as follows:
SHD0 -
Creation of transaction variant - with processing.
Activating it.
Appreciate a quick response. Thanks in advance.
Note: It might be that I am going wrong somewhere, I would really appreciate if someone could send me a file containing screenshots on how to create and use transaction variants. My email ID is
[email protected]
Regards,
Z

hi,
just check out the following pre-requisites if you have followed them or not:
You can assign various transaction variants to individual sales document types.
With the help of transaction variants, you create various variants for the same transaction in order to simplify your transaction flows. You can achieve this by:
Preassigning fields with values
Fading out and changing input availability for fields
Fading out entire screens
In this way, you can provide your users with screens which are defined according to their specific needs per sales document type.
When a transaction variant is created, several screen variants are created for each individual screen for the transaction chosen for the variant. The system accesses this screen variant when a transaction variant is applied.
PrerequisitesIn the standard system, transaction variants for Sales (for example, quotation, sales order, credit memo request, group master contract) are defined for all business objects. Assignment of transaction variants for the sales document type is carried out in Customizing for sales document types.
Activities
You will find the transaction for creating a transaction variant in Customizing, under General Settings - Field Display Characteristics - Configure application transaction fields. You can find further information on this in the implementation guide.
Assignment of transaction variants to sales document types can be found in Customizing for Sales, under Sales - Sales Documents - Sales Document Header - Define Sales Document Types in the Variants field.
In order that a transaction can be called up depending on a sales document type, the system of course needs the information as to which sales document type should be worked with. This choice is however made by the user on the initial screen first.
This means that the initial screen can not be modified or faded out within a transaction variant. If you wish to miss out or modify the initial screen with the choice of sales document types, you need to create a variant transaction, this means a variant is created for a complete transaction. This transaction will then have ist own name, which has been defined by you.
regards,
Siddharth.

Screen Variant Not working

Hi,
I have created one screen variant for screen for SAPLBBP_SC_UI_ITS screen 230.
It's getting called while i checked by debugging .
But its not working in ITS Template & in transaction also .
In SAPgui it's not working .
Is there any more setting for Screen variant apart from just save it & called in screen variant BADI .
Thanks,
SS

Hi
<u>This BADI as you can see by name is for Screen Variants.
BBP_SCREENVARIANT in this case.</u>
<b>Please read the following documentation to get the clear difference</b>
Transaction Variants and Screen Variants
Transaction variants can simplify transaction runs as they allow you to:
Preassign values to fields
Hide and change the 'ready for input' status of fields
Hide and change table control column attributes
Hide menu functions
Hide entire screens
In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.
Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.
There are both client-specific and cross-client transaction variants. All screen variants are cross-client, but may be assigned to a client-specific transaction variant.
A namespace exists for cross-client transaction variants and screen variants and both are automatically attached to the Transport Organizer. Client-specific transaction variants must be transported manually.
In principle, transaction and screen variants can be created for all dialog and reporting transactions. There are, however, certain Restrictions that apply to certain transactions, depending on their internal structure.
No transaction variants are possible with transactions already containing preset parameters (parameter transactions and variant transactions).
Screen variants
Screen variants allow you to simplify screen editing by:
Inserting default values in fields
Hiding and changing the ready for input status of fields
Hiding and changing the attributes of table control columns
A screen variant contains field values and attributes for exactly one screen. A screen variant can, howevever, be assigned to multiple transaction variants. Screen variants are always cross-client; they may, however, be assigned to a client-specific transaction. They can also be called at runtime by a program. The different possibilities for calling screen variants guarantee great flexibility of use.
For more information, see: Calling Screen Variants
A specific namespace has been designated for screen variants and they are automatically attached to the Change and Transport System.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Create transaction with variant not working

Similar Messages

Maybe you are looking for