Creating a parameter transaction
Hi All,
Can any one tell me how to create a parameter transaction of ztable?
Tnx,
Joe
Hi,
Parameter transactions allow you to preassign values to fields on the initial screen of a transaction.
To create a parameter transaction, use the Transaction Maintenance transaction (SE93). Once you have entered a transaction code and short description, choose transaction type Transaction with parameters (Parameter transaction).
You can hide the initial screen of a parameter transaction if you have specified values for all of its fields.
Have a look to dis link[link|http://www.sapdev.co.uk/tips/tips_tabmaint_tcode.htm]
regards,
Archana
Edited by: Archana Kumari on Aug 28, 2009 1:37 PM
Similar Messages
-
How to create a variant used in SM30,View variant in Parameter transaction?
Dear Team,
I have a view V_TCURR. For which I would be creating a parameter transaction for transaction SM30 by filling the default Values section (VIMDYNFLDS-LTD_DTA_VR, VIEWNAME,TVIMV-VARIANT). The values for first two fields are obvious.
The question is on TVIMV-VARIANT How can we create a variant which can be used in tcode SM30.
Delving a little deeper show that these variants Obsolete since R/3 Release 3.1I: Selection variant for a table or maintenance view.
Since R/3 Release 4.0, there are view variants instead of selection variants.
The field only exists for reasons of backwards compatibility.
If thats is so, How do I use the same in parameter transaction..?
I have tried creating a view variant and use it parameter transaction but in vain..
Please help resolve my problem. I hope I am very clear. If still need any clarification, please get back to me.
Thanks a lot in advance,
Reagards,
Sai.
P.S. Though there are multiple quuestions on simlar subjects none of them has been either answered or is completely relevant to mine.Dear Suman,
Thanks a lot for the answer. Actually the Tcode is getting created if I do what you have said me.
But when I run the tcode which was created by view variant created, I am not getting the desired details .
To be more clear..
Previously there was a variant (TMIMV-VARIANT) created with follwing criteria..
Table TMIMV.
TABNAME VARIANT AS4POS VIEWFIELD NEGATION OPERATOR VALUE AND_OR TABIX
V_TCURR ZTHB 1 KURST NOT EQ M AND 2
V_TCURR ZTHB 2 KURST NOT EQ DWBP AND 2
V_TCURR ZTHB 3 TCURR EQ THB OR 4
V_TCURR ZTHB 4 TCURR EQ USD OR 4
V_TCURR ZTHB 5 TCURR EQ US$ 4
When we run tcode created by paramaeter transaction.. viewname as V_TCURR, TMIMV-VARIANT. I am getting the desired records for updation.
But if I do the same using View variant with the same selection criteria
Table Field name Operator Comaparison AND/OR
Value
TCURR KURST NE 'M' AND
TCURR KURST NE 'DWBP' AND
TCURR TCURR EQ THB OR
TCURR TCURR EQ USD OR
TCURR TCURR EQ US$
And the run the tcode created by using the view variant .. I am getting No entries found that match selection criteria...
Could you please help and let me know if I am missing any step.. Kindly also check from your side how this can be achieved.
Thanks a lot in advance,
Sai. -
Hi,
need some help, I am creating an Parameter Transaction to create display only view for an Table. But I need to restrict only certain fields for selection, but by default system is prompting to select Selection fields.
thanks
LakhbirExecute Tcode SE93
In the transaction code mention SM30 and check skip initial screen.
In the Default values.
Name of the screen field = VIEWNAME
value = <Your table name>
In the next line
Name of the screen field = UPDATE
value = 'X'
Hope this will help you.
Regards
Aman -
Hi All,
I have created a Parameter transaction for SM30 by which I am able to maintain entries in my user-defined table. But, I would like to restrict the entries displayed (not using the conditions in SM30) by creating the selection screen where only the few fields of the user-defined table are presented for selection and based on that I get output. I want the full functionality of the parameter transaction(creation , deletion of the entries) though.
if some one has any ideas kindly let me know.
Thanks,
ManishHi Manish,
I don't know if a two-step maintenance is good for you as suggested in one reply here, but if your requirement is to give user a SM30 feature but have a selection screen of your own, then here is an example of how you can achieve that with a custom program. I don't think you can achieve that with just parametric transaction and without using conditions and without modifying the maintenance screens.
Let me know if you have any questions regarding this code. This program is for a Z table mainetnance which has two fields, a code and a description. Users are given a choice of entering their criteria for either the code or the description or both. This criteria is internally converted to a format that the table maintenance function module understands. The result is that users get to see and maintain only the records that they wanted.
REPORT test.
* DB TABLES AND STRUCTURES *
TABLES: sscrfields,
z_group.
* INTERNAL TABLES *
*-- Internal table for seltab
DATA : i_seltab LIKE vimsellist OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF i_excl_tab OCCURS 0,
pfkey LIKE sy-pfkey.
DATA: END OF i_excl_tab.
* VARIABLES *
* CONSTANTS *
*------------------------ Selection Screen ---------------------------*
*-- Maintain EOQ Tables: Initial Screen
SELECTION-SCREEN BEGIN OF BLOCK selscr WITH FRAME TITLE text-000.
SELECTION-SCREEN SKIP 1.
*-- Select the table you want to maintain
SELECTION-SCREEN BEGIN OF BLOCK program WITH FRAME TITLE text-001.
PARAMETERS : p_table LIKE dd02l-tabname DEFAULT 'Z_GROUP'.
SELECTION-SCREEN END OF BLOCK program.
SELECTION-SCREEN BEGIN OF BLOCK fursel WITH FRAME TITLE text-002.
*-- Selections for EOQ groups
SELECT-OPTIONS: s_group FOR z_group-group,
s_descr FOR z_group-descr NO-EXTENSION
NO INTERVALS.
SELECTION-SCREEN END OF BLOCK fursel.
*-- display or maintain options
SELECTION-SCREEN PUSHBUTTON: /10(20) update USER-COMMAND upda
MODIF ID ind,
35(20) display USER-COMMAND disp
MODIF ID ind.
SELECTION-SCREEN END OF BLOCK selscr.
INITIALIZATION.
PERFORM initialize_variables.
AT SELECTION-SCREEN OUTPUT.
*-- set the PF Status for the selection screen
PERFORM set_sel_screen_pf_status.
LOOP AT SCREEN.
CHECK screen-name = 'P_TABLE'.
screen-input = 0.
MODIFY SCREEN.
ENDLOOP.
AT SELECTION-SCREEN.
CHECK NOT p_table IS INITIAL.
PERFORM call_maintenance USING sscrfields-ucomm.
START-OF-SELECTION.
END-OF-SELECTION.
*--------------------- Routines used in the program -------------------*
* FORM initialize_variables *
FORM initialize_variables.
MOVE: 'Update'(006) TO update,
'Display'(007) TO display.
ENDFORM. " initialize_variables
* FORM SET_SEL_SCREEN_PF_STATUS *
FORM set_sel_screen_pf_status.
MOVE 'ONLI' TO i_excl_tab-pfkey.
APPEND i_excl_tab.
CLEAR i_excl_tab.
MOVE 'SJOB' TO i_excl_tab-pfkey.
APPEND i_excl_tab.
CLEAR i_excl_tab.
MOVE 'PRIN' TO i_excl_tab-pfkey.
APPEND i_excl_tab.
CLEAR i_excl_tab.
MOVE 'DYNS' TO i_excl_tab-pfkey.
APPEND i_excl_tab.
CLEAR i_excl_tab.
CALL FUNCTION 'RS_SET_SELSCREEN_STATUS'
EXPORTING
p_status = '%_00'
p_program = 'RSSYSTDB'
TABLES
p_exclude = i_excl_tab.
ENDFORM. " SET_SEL_SCREEN_PF_STATUS
*& Form call_maintenance
* To display the maintenance of the table entered.
FORM call_maintenance USING action LIKE sy-ucomm.
DATA: l_view_action.
IF action = 'UPDA'.
l_view_action = 'U'.
ELSEIF action = 'DISP'.
l_view_action = 'S'.
ELSE.
EXIT.
ENDIF.
*-- prepare the select statement for the call
PERFORM prepare_sel_statement.
CALL FUNCTION 'VIEW_MAINTENANCE_CALL'
EXPORTING
action = l_view_action
* CORR_NUMBER = ' '
* GENERATE_MAINT_TOOL_IF_MISSING = ' '
* SHOW_SELECTION_POPUP = ' '
view_name = p_table
* NO_WARNING_FOR_CLIENTINDEP = ' '
* RFC_DESTINATION_FOR_UPGRADE = ' '
* CLIENT_FOR_UPGRADE = ' '
* VARIANT_FOR_SELECTION = ' '
* COMPLEX_SELCONDS_USED = ' '
TABLES
dba_sellist = i_seltab
* EXCL_CUA_FUNCT =
EXCEPTIONS
client_reference = 1
foreign_lock = 2
invalid_action = 3
no_clientindependent_auth = 4
no_database_function = 5
no_editor_function = 6
no_show_auth = 7
no_tvdir_entry = 8
no_upd_auth = 9
only_show_allowed = 10
system_failure = 11
unknown_field_in_dba_sellist = 12
view_not_found = 13
OTHERS = 14
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " call_maintenance
* FORM prepare_sel_statement *
FORM prepare_sel_statement.
CLEAR: i_seltab, i_seltab[].
PERFORM prepare_seltab_for_grp.
ENDFORM. " PREPARE_SEL_STATEMENT
* FORM PREPARE_SELTAB_FOR_GRP *
FORM prepare_seltab_for_grp.
IF NOT s_group[] IS INITIAL.
*-- if any criteria is entered for the GROUP field
CALL FUNCTION 'VIEW_RANGETAB_TO_SELLIST'
EXPORTING
fieldname = 'GROUP'
* APPEND_CONJUNCTION = ' '
TABLES
sellist = i_seltab
rangetab = s_group.
ENDIF.
IF NOT s_descr[] IS INITIAL.
*-- if any criteria is entered for the GROUP DESCRIPTION field
CALL FUNCTION 'VIEW_RANGETAB_TO_SELLIST'
EXPORTING
fieldname = 'DESCR'
append_conjunction = 'AND'
TABLES
sellist = i_seltab
rangetab = s_descr.
ENDIF.
ENDFORM. " PREPARE_SELTAB_FOR_GRP
Hope this helps.
Srinivas -
Parameter transaction for table maintenance - multiple tables?
Hello,
I am very familiar with creating a parameter transaction to call SM30 for a specific Z-table of ours.
However, I have 14 tables that a group of users will need to maintain. Rather than create 14 different transactions in SE93, what are my options?
When creating a parameter transaction in SE93, I get the error that the field 'VIEWNAME' is used more than once. There has to be a way to achieve this with only one transaction.
Thank you very much,
MichaelI dont think you can create a single transaction with multiple VIEWNAME's.Options I would suggest you is create a simple report with radio buttons for each table and call the FM "VIEW_MAINTENANCE_CALL" with the viewname based on user selection and create a single transaction to the report or create transaction for each and create a Area menu with all the 14 transaction.
-
SE93: Parameter Transaction for SE38
Hello
I want to create a parameter transaction to display my program in edit mode.
i.e. Instead of going to SE38 and change my program.
There are lots of websites describing how to call SM30 in edit mode for a particular View. I just wanted to know if it possible with SE38 also..
I have entered the following screen-field values in SE93 but the new transaction stays on the initial screen of SE38, even though skip initial screen option is checked.
Field: RS38M-PROGRAMM
Value: ZTEST
Field: RS38M-FUNC_EDIT
Value: X
I must somehow pass some additional value which would account for clicking the "Change" button.. but how?
I know about Call Transaction, BDCs etc.. but really wanted to know if its possible via parameter transaction...Hi, Shrikaant
Follow the Steps Bellow then you will understand with is Difference Between SE38 and SM30
1. Run T-Code SM30
2. Go to Menu Path System => Status
3. From the System Status Box Double Click Screen 100
4. It will bring you in Screen Painter Select Layout button
5. On the you will see some Fields under buttons Display, Maintain and Transport
6. These buttons are hidden for Screen SM30
7. So you are setting this value in Parameter Transaction UPDATE = 'X'
This option is not available in SE38 so you can't do the same for this Transaction.
Hope you understand, Please reply if any confusion
Thanks and Regards,
Faisal -
Parameter transaction for view maintenance
Hi there, please help
I've created a parameter transaction(ZTRN) for a view maintenance(ZVIEW) with the ff
Skip initial screen = X
VIEWNAME = 'ZVIEW'
UPDATE = X.
How can i change this transaction/view so that only 1 record can be maintained, i.e how/what
parameters to provide before calling the transaction so that only one record can be maintained. With the above settings all records are displayed.
I've tried using UPDATE_LTD = X but its not helping either.
Thanks in advanceI don't think this is possible in the way you want it to. What you could do is use the standard events provided by the maintenance view. In these event create a check that only one record can be changed or even displayed.
I don't have a SAP system to give you an example but I can refer you to this:
[Maintenance events|http://help.sap.com/saphelp_nw70/helpdata/EN/91/ca9f0ea9d111d1a5690000e82deaaa/content.htm]
Edited by: Micky Oestreich on Aug 6, 2008 2:41 PM -
Providing authorization for parameter transaction
hello all,
I have created a parameter transaction for a table maintainance generator(table a z-table). the requirement is, we want to provide authorization only for few users so how can we go forward...
with regards,
sandeep akella.When you are parametrizing any TCoe then there is no changes happen in the Authorization checks from the original. So you need to take care this in the following way:
1. Go to table TDDAT and find out the Authorization Group of that z-table. If nothing found, please create a Custom Auth group and assign the table to that grp in SE54.
2. Now go to the role through which you want to provide access to that table to the users or create a new role and add the Parametrized Tcode in the menu of the Tcode.
3. In authorization data, please assign the Authorization group for that particular table in S_TABU_DIS and provide the activity as per your requirement.
4. Assign the role to the users.
Regards,
Dipanjan -
i AM TO CREAT A PARAMETER FROM THE ANALYSIS DATABASE BUT APPARENTLY THERE ARE NO VALUES IN THE DIMENSIONN MEMBER
BELOW IS THE LOGIC THAT WAS USED WHEN LOADING THE DATA INTO THE DATAWAREHOUSE.
1)
Each transaction in the audit trail is matched with a record in the EA dimension table using the EA, SUBJOB, and AGENCY
2)
Each transaction in the audit trail is matched with a record in the Trans Code dimension table using trans_code
3)
If the EA_STAT value is E4, U4, P5, 02, 03, or 04 AND the TRANS_GROUP value is 3500 or 9100, then the record is marked as a PROJECT
4)
If the EA_STAT value is NOT in E4, U4, P5, 02, 03, or 04 AND the TRANS_GROUP value is 3500, then the record is marked as NON-PROJECT
5)
Anything else outside of those ranges is marked as UNKNOWN.
"SELECT
ACTIVITY = coalesce(activity,''),
AGENCY = coalesce(agency,''),
AGENCY_SOURCE = coalesce(agency_source,''),
AGREEMENT_NO = coalesce(f.agreement_no,''),
AGREEMENT_SFX = coalesce(agreement_sfx,''),
APPN_SYMBOL = coalesce(appn_symbol,''),
AT_VENDOR_NO = coalesce(at_vendor_no,''),
AT_VENDOR_SFX = coalesce(at_vendor_sfx, ''),
CHECK_NO,
CHRGE_UNIT = coalesce(chrge_unit,''),
COMPONENT = coalesce(component,''),
CUR_DOC_NO,
CUR_DOC_SFX,
EA = coalesce(f.EA,''),
EFFECTIVE_DATE,
ELEMENT = coalesce(element,''),
FISCAL_YEAR = coalesce(f.fiscal_year, ''),
FUND_DETAIL = coalesce(fund_detail,''),
FUND_NUMBER = coalesce(fund_number,''),
INVOICE_NO = coalesce(invoice_no, ''),
OBJ_DETL = coalesce(obj_detl,''),
OPERATOR = coalesce(operator,''),
PROCESS_DATE,
PROGRAM = coalesce(program,''),
REMIT_ADVICE_DESC = coalesce(REMIT_ADVICE_DESC,''),
RESPONSIBLE_UNIT = coalesce(RESPONSIBLE_UNIT,''),
REVENUE_SOURCE = COALESCE(revenue_source,''),
SUBJOB = COALESCE(f.SUBJOB,''),
TASK = COALESCE(TASK,''),
TRANS_CODE = COALESCE(TRANS_CODE,''),
TRANSACTION_AMOUNT,
TRANSACTION_QTY,
VENDOR_NO = CASE WHEN LEN(VENDOR_NO) = 0 THEN AT_VENDOR_NO ELSE VENDOR_NO END,
VENDOR_SFX = CASE WHEN LEN(VENDOR_SFX) = 0 THEN AT_VENDOR_SFX ELSE VENDOR_SFX END,
b.BIEN_SK,
DOCUMENT_DATE,
LET_DATE = '1900-01-01',
COMPLETION_DATE = '1900-01-01', t.TRANS_SK,
case when t.trans_grp_desc = 'EXPENDITURES' AND f.CATEGORY != '9' then f.transaction_amount else 0.00 end AS TRAN_AMT_EXPENDITURE,
case when t.trans_grp_desc = 'REVENUE' then f.transaction_amount else 0.00 end AS TRAN_AMT_REVENUE,
case when t.trans_grp_desc = 'AGREEMENT AMT BILLED' then f.transaction_amount else 0.00 end AS TRAN_AMT_AGREEMENT,
case when t.trans_grp_desc = 'ENCUMBRANCES' then f.transaction_amount else 0.00 end AS TRAN_AMT_ENCUMBRANCE,
case when t.trans_grp_desc = 'LEG EXP BUDGET' then f.transaction_amount else 0.00 end AS TRAN_AMT_LEGISLATIVE_BDGT,
case when t.trans_grp_desc = 'OPERATING BUDGET' then f.transaction_amount else 0.00 end AS TRAN_AMT_OPERATING_BDGT,
case when t.trans_grp_desc = 'PROJECT BUDGET' then f.transaction_amount else 0.00 end AS TRAN_AMT_PROJECT_BDGT,
EA_FINAL_STAT = coalesce(f.ea_final_stat,''),
CASE
WHEN
e.ea_stat IN ('E4', 'U4', 'P5', '02', '03', '04')
and t.trans_grp IN ('3500', '9100')
THEN 1 -- PROJECT
WHEN
e.ea_stat NOT IN ('E4', 'U4', 'P5', '02', '03', '04')
and t.trans_grp IN ('3500')
THEN 2 -- NON PROJECT
ELSE 0 -- UNKNOWN
END AS EXPENDITURE_GROUP_SK,
BATCH_AGENCY,
BATCH_DATE,
BATCH_TYPE,
BATCH_NO,
DOC_INDEX,
LINE_NO,
FUND_SPLT_SEQ_NO,
DUP_REC_IND,
RECORD_NO,
STATE_FORCE_ORDER,
REFERENCE_CODE,
FLEET_CODE,
FUEL_TYPE,
f.CONTRACT_NO,
f.CONTRACT_SFX
FROM
" + @[Package::SQL_Source_Table] + " as f
JOIN " + @[Package::SQL_Dest_DB] + ".dbo.DIM_BIENNIUM as b
ON b.fiscal_year = f.fiscal_year
AND CAST(f.fiscal_month as tinyint) = b.fiscal_month_no
JOIN " + @[Package::SQL_Dest_DB] + ".dbo.dim_trans as t
on t.trans_cd = f.trans_code
JOIN (SELECT MAX(EA_SK) AS EA_SK, EA, SUBJOB, EA_AGY, EA_STAT FROM " + @[Package::SQL_Dest_DB] + ".dbo.dim_EA GROUP BY EA, SUBJOB, EA_AGY, EA_STAT) e
on f.EA = e.EA
AND f.SUBJOB = e.SUBJOB
AND f.AGENCY = e.EA_AGY
HOW DO YOU SUGGEST i GO ABOUT IT?=Code.fFormatColumnName(Parameters!pSummary1.Value) &
" " & trim(fields(Parameters!pSummary1.Value).Value) &
iif(
Parameters!pSummary1.Value="OBJECT",
"-" & Lookup(
iif(isnothing(Fields!CAT_OBJ_KEY.Value), "-111", Fields!CAT_OBJ_KEY.Value),
Fields!CAT_OBJ_KEY.Value, Fields!OBJECT_DESC.Value,
"sqlOBJLookup"),
iif(
Parameters!pSummary1.Value="CATEGORY",
"-" & Lookup(
iif(isnothing(Fields!CATEGORY.Value), "-1", Fields!CATEGORY.Value),
Fields!CATEGORY.Value, Fields!CATEGORY_DESC.Value,
"sqlCategoryLookup"),
iif(
Parameters!pSummary1.Value="OBJ_DETL",
"-" & Lookup(
iif(isnothing(Fields!OBJ_DETL.Value), "-111", Fields!OBJ_DETL.Value),
Fields!OBJ_DETL.Value, Fields!OBJ_DETL_DESC.Value,
"sqlOBJDetLookup"),
) & " TOTALS:" -
Parameter Transaction Code for Function Group based Tcodes
Hi,
I have created a function group for a single screen 1000 having only 2 screen fields with input/output enabled, one of them being a flag field. Have also created a Transaction code to point to the screen 1000.
My requirement is to create another Tcode(Parameter Transaction Code) with the previous created Tcode and pass default values to the screens flag element. I have entered the below :
Name of the screen field
Value
FLAG
X
Still i am not able to get the value of FLAG as X when i debug the program. I am confused what mistake have i done. It will be helpful if someone can guide on this. I know its simple and i believe me i have tried all possible ways to check my mistake. Couldn't find any.
Thanks and Regards,
Vadid ValiullaYes, Basically i am calling TCODE1 from TCODE2.
I am using the same Function Group and yes a global variable is defined for the screen fields.
I actually do not want to go by the Parameter ID method. But still i can use it if that is easier. Currently there is no Parameter ID for the screen field as i wanted the Tcode2 also to be called independently.
Thanks for your time Prakash
Regards,
Vadid -
How to create a parameter id on screen element
How to create a parameter id on screen element
reply urgentHi Madan,
Check this info.
Parametere Id is the one which holds the memory for the particular field. when we need to pass the the field from one screen to another use the parameter Id.
The SAP Memory is a user-specific memory area of the application server, which is accessed by all main sessions of a user session at once. ABAP programs have access to SPA/GPA parameters stored in the SAP Memory (also called SET/GET parameters).
Eg. Of how to use Set parameter
you can give value of variable (dobj) to parameter ID 'pid'. This will store value in SAP memory
SET PARAMETER ID pid FIELD dobj.
When you want to use that value stored in SAP memory
you can use GET parameter.
GET PARAMETER ID pid FIELD dobj.
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.
To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.
The relevant fields must each be linked to an SPA/GPA parameter.
On a selection screen, you link fields to parameters using the MEMORY ID addition in the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID when you declare a parameter or selection option, the corresponding input field is linked to that input field.
Check this link.
http://help.sap.com/saphelp_47x200/helpdata/en/f5/6a853c61c5140ee10000000a11405a/frameset.htm
Hope this resolves your query.
Reward all the helpful answers.
Regards -
Authorization object for parameter transactions
Hi all,
I'm trying to restrict transaction VL10h for shipping point,this transaction is a parameter transaction and is not controlled by an authorization object directly.when I run a trace , transaction Vl10x shows up. The authorization object that is being checked is V_LIKP_VST.
Note : The requirement is when the user executes transaction VL10h he/she should be able to display only those shipping points they are authorized to.
Please advice.
Thanks,
Mohan.Hi Mohan,
For transaction VL10H you can specify values for the following fields in authorization object V_LIKP_VST:
-Activity:
01 Create or generate
02 Change
03 Display
04 Print, edit messages
18 Deliveries from coll. proc.
24 Archive
25 Reload
85 Reverse
-Shipping point: Here you must set the restriction for each group of users that are allowed for the maintenance of the shipping points that are used for delivery processing.
You can restrict the access through these fields.
Regards,
Leandro -
MOPZ - "create new maintenance transaction" pops up web browser
Hi Guru,
I'm configuring MOPZ on SolMan EHP1 SPS22. I've configured SMSY RFC (all green), Logical Component, Create Solution and set to created Logical Component.
But when I go to DSWP --> Operations --> Change Management --> Maintenance Optimizer --> create new maintenance transaction. It is showing a blank page and is popping up a web browser:
http://SOLMAN:8001/sap/public/myssocntl?sap-client=001
Kindly need your expertise.
Thanks and Regards,
YanDear Yohanes,
I see you are using this link
http://SOLMAN:8001/sap/public/myssocntl?sap-client=001
I would think you should be providing a fully qualified host name such as
http://SOLMAN.yourcompany. your domain:8001/sap/public/myssocntl?sap-client=001
Also ensure you have defined parameter icm/host_name_full to the value of the fully qualified host name.
This may be the solution to your problem.
Regards,
Paul -
Creating a variant transaction
Hi,
Im trying to create the above in SE93. Im calling it Z_SWWL and its calling transaction SWWL, which contains variants. But its not finding any 'transaction variant' to choose from!?
Any ideas?
Thanks,
DaveHi
goto SHD0 tcode and create a Transaction variant with screen variants for a dialog Transaction
then assign that Transaction variant in SE93 by creating a variant transaction code
see the doc
we can create Transaction Variants Using SHD0 Transaction.
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).
see the links
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html
Re: shd0 transaction
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/132f9803d76f40e10000000a422035/content.htm
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1213076,00.html
Re: shd0 transaction
Regards
Anji -
Parameter ~TRANSACTION in webgui service
Hi all,
we plan to publish transaction PPMDT on our intranet using the SAP GUI for HTML.
I copied the service "webgui" and tried to add the parameter ~TRANSACTION = PPMDT in "GUI Configuration", but it has no effect. When I call the service in a browser and log on, the usual start menu is displayed, not transaction PPMDT. I also set parameter ~WEBGUI_SIMPLE_TOOLBAR = 32 in the same place and it works fine.
Can I only specify the ~TRANSACTION parameter in the URL? Or is there a possibility to specify the parameter somewhere in SICF?
As I am not an ITS expert at all, I appreciate any help.
Thank you, MichaelHello Michael,
What you have done should work. Just to be clear:
1. create a new service that is the exact copy of WEBGUI
2. in the GUI configuration area add ~transaction PPMDT
3. save and test.
Besides the "~transaction PPMDT" what else is in the GUI Configuration area for the new service that you created?
Edgar
Maybe you are looking for
-
Please help! iMovie keeps crashing on launch
Please help! Every time I try to open iMovie, it opens for about 10 seconds, during which time it won't allow you to click anything and then 'quits unexpectedly'. Here are the problem details.....I don't understand why it is doing it because it has w
-
I am facing a issue in Flash container. I am having a project which has main container which call different SWFs into it. Now I call this main container file into another container, and their problem starts. Many option doesn't work properly which ge
-
Hi, I am getting the vlaue like this(59.00-). Now i want to convert like this (-59.0). please let me know how i can convert this. thanks in advance. vij.
-
Stuck on "setting date and time" why is it doing this and I cant move to any other screne?
My question is the subject line.
-
This just started mid-day, working fine one moment, and know i can't open pages. IE seems to be working fine. == URL of affected sites == http:// == User Agent == Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SV1; GTB0.0; SLCC1; .NE