Transaction Variant Error
Hi all,
I am trying to create a transaction variant for one of the SAP std transaction and when I execute tcode shd0 and put the tcode there and hit the create button I get the following error message:
Variants are possible only for dialog transactions.
Message no. MS417
Diagnosis
You cannot create variants for variant or parameter transactions.
So can you please tell me how can I create variant for such case.
Thanks,
Rajeev
This is the place you are getting the error MSHD0F01 , As in my earlier reply i mentioned you cannot write transaction variant wrapper on transaction variant
select single * from tstc where tcode = shdtv-tcode.
if sy-subrc >< 0.
message e416 with shdtv-tcode.
else.
if tstc-cinfo o c_type_menu "menu
or tstc-cinfo o c_type_para. "parameter-/variant transaction
message e417.
endif.
endif.
a®
Similar Messages
-
Error while trying to create Transaction variant for FV60 layout change
Hi Gurus,
I am trying to change the "order/sequence" of FV60 layout (rearranging columns). For which I tried to create Transaction Variant (in sandbox). I keyed in the t-code (FV60) and gave a variant name in the field for Transaction variant. But it gives me a wierd error - "Enter transaction code". Has anybody come across this before? This is enhancement pack 7 so the config button is not available.Thanks Ravi. I went through the note and did exactly the same. But the two check boxes displayed in the note for "Adopt column sequence" and "Adopt column width" is not displayed in my screen!!! Screen shot attached.
-
General Ledger Posting Error (GLT2 051) No accounting transaction variant
Hello SAP Gurus-
When testing lockbox in FLB2, I received the following error message:
General Ledger Posting Error (GLT2 051) No accounting transaction variant assigned to FB01/ /LB
We are on ECC 6.0
I created a new Document Type LB
I created a new G/L account for Lockbox clearing and AR
How do I fix this?
Thank you!Hi,
Assign a transaction variant for the document type you created in Transaction code GSP_VZ3. Also, make sure that the GL accounts affected are assigned with item categories in GSP_LZ2.
Thanks
Aravind -
Error message "no accounting transaction variant assigned for FB60//GL"
Hi Friends,
I created a new document type for GL postings in ECC 6.0. I tried to post a document for this document in FB60.. It displays the error message "no accounting transaction variant assigned for FB60//GL". Can anyone help me solve this problem.
Thanks
RamyaYou need to do the settings as follows:
Go to extended document splitting- define business transaction variant
Here u need to do series of settings.
Pl check your settings here -
Dear All,
I am facing a problem while doing the transaction variant. It is as follows -
With the T.Code SHD0, i started creating a transaction variant and named as ZMM01 for the transaction MM01.
After clicking the create(F5), it went to the MM01 transaction for recording. Here i wanted to give some default inputs in the fields Industry sector and Material type, i gave my default values and pressed enter, then "Confirm screen entries" screen popped up. Here i selected(marked) required check boxes and clicked "Exit and Save". It went to another screen where i gave "Screen variant short description" and when i clicked on save, "Create Object Directory Entry" screen popped up.
What exactly should i do now?
When i tried to save by clicking on save button, system is giving me a message "Specify the package or flag it as a local object"
"Message no is TR742".
BUT.....
When i clicked the "Local Object" tab which is next to "Save" button, system is asking me to Assign a package" and in the package field the system is giving the value "$TMP" by default and when i tried to save it OR click "Local object" again, system is giving me an error message "Test objects cannot be created in foreign namespaces", Message no. TO131.
Pl guide me what exactly i have to do at this stage( How/Procedure to save).
Thanks & Regards,Hi ,
Ensure that all the variants you have created start with Z like screen variant , transaction variant .
The system throws this message when you use other name space which is not allowed .
Regards,
Hari. -
Transaction variant durign creation of sales order.
I have a scenario Sale area is R001/10/10 and is applicable for all the customer in all india.
Now the requirement is to incase of sell order creation to only the customers at UP it will be made mandatory to put cheque number in the sales order otherwise the order will not solved.
The same will be applicable only for up customer not to other customers.
Now the problem is if i want to added some field in incompletion procedure and assign to the order type it will not solve my problem.
Becasue OR is assign to R001/10/10 and sell happens from hyderabad, bangalore as well as up also. and this control only require in case of sell to up customers only. If i will assign the incomplition procedure to order type it will be applicable to all.
So it was suggested by anybody to creat transaction variant during sales order creation. Can anybody tell me the way to creat or any other suggestions.
The right answar will be rewarded.
Thanks.
Laxmikanta Das.
09958119889Hi
If you donot find any other alternative, you can finally go for using the Userexit. When the sales order is created and before saving the document, the system checks for the field -State/Region etc., and if the value is UP then it checks for the Check Number in that corresponding field. You have to mention the systems reaction(warning or error) if there is no value in that field.
Thanks,
Ravi -
Problem in creating transaction variant
Hi all,
I am trying to create transaction variant for F- 41 transaction . it's giving an error message .
Variants are possible only for dialog transactions.
Message no. MS417
Diagnosis
You cannot create variants for variant or parameter transactions.
Procedure
Variant transaction: Adjust the variant
Parameter transaction: Adjust the parameter(s)
i need to disable the filed 'document type' .
Guide me.
Regards,
RaviHi,
You can copied into SAP standard program to Zprogram and then use the Loop at screen....Endloop to disable the Documnet type.
FYI...If you go for F.14 transaction there you find Sytesm----> status .. there you will find SAP standard program. Make a copy to Zprogarm and try to disable it.
Regards
Thiru -
Hi All,
I am able to create transaction variant for transaction code MM01, XD01 and XK01 successfully. But i am unable to create transaction variant for VA01.
And also some times i am getting error message "SAP Object SCV1(short text of variant) cannot be assigned to package ZXXX". Can you pls let me know why i am getting this error and why i am unable to create transaction variant for VA01 successfully.
Thanks,
RajuHi,
There is no difference in creation of the transaction variant for VA01/02. But the way it works is different. It works at order type level instead of t-code level. You have to create the variant in SHD0 and assign the same in order type customization.
Alternatively you can populate the field TVAK-VARIANT with the transaction variant name in MV45AFZZ subroutine USEREXIT_MOVE_FIELDS_TO_VBAK/USEREXIT_FIELD-MODIFY. With out this it wont work. Just try to change the TVAK-VARIANT value in debug mode and see if it works fine. Surpricingly it works fine if you individually execute the variant.
The error you mentioned might be because you might have given one of the screen variant name not starting with Z or Y.
Thanks,
Vinod. -
Please find code below. When I run this report with transaction it gives variant error .How can I fix this problem
REPORT yiwm_uom_stock .
*---Data Include
INCLUDE yiwm_uom_stock_data.
*INITIALIZATION.
PERFORM initialize_variant.
*----ON SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant .
*---START-OF-SELECTION
START-OF-SELECTION.
PERFORM get_data.
PERFORM write_data .
*& Form get_data
FORM get_data.
*--Quants of stock with selection screen.
SELECT werks lgort lgnum gesme
verme einme ausme lgpla
lgtyp matnr lqnum
FROM lqua
INTO CORRESPONDING FIELDS OF TABLE gt_itab
WHERE werks IN s_werks
AND lgnum EQ p_lgnum
AND lgort IN s_lgort
AND lgtyp IN s_lgtyp
AND kober IN s_kober
AND matnr IN s_matnr.
LOOP AT gt_itab.
CLEAR lagp .
SELECT SINGLE lgtyp lgber lptyp plauf skzua skzue skzsa skzse
skzsi spgru anzqu maxqu anzle maxle btanr btaps
kzdyn lgewi gewei mgewi bdatu bzeit ivivo sorlp
rdatu rzeit kzinv idatu ivnum ivpos brand uname
laedt kober reihf verif
FROM lagp
INTO CORRESPONDING FIELDS OF gt_itab
WHERE lgnum = gt_itab-lgnum
AND lgpla = gt_itab-lgpla
AND lgtyp = gt_itab-lgtyp.
CLEAR mara.
SELECT SINGLE matnr meins zzshmat matkl
mtart ean11 zzkshrtyp
FROM mara
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr.
CLEAR marm.
SELECT SINGLE meinh umrez umren breit hoehe
meabm volum voleh brgew gewei
FROM marm
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr
AND meinh EQ p_meinh.
CLEAR mlgn.
SELECT SINGLE ltkza ltkze lgbkz block
bsskz l2skr mkapv
FROM mlgn
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr
AND lgnum EQ gt_itab-lgnum.
CLEAR mlgt.
SELECT SINGLE lgpla lpmax lpmin
mamng nsmng kober rdmng
FROM mlgt
INTO CORRESPONDING FIELDS OF gt_itab
WHERE lgnum EQ gt_itab-lgnum
AND lgpla EQ gt_itab-lgpla
AND matnr EQ gt_itab-matnr
AND lgtyp EQ gt_itab-lgtyp.
CLEAR makt.
SELECT SINGLE maktx
FROM makt
INTO gt_itab-maktx
WHERE matnr EQ gt_itab-matnr.
MODIFY gt_itab.
CLEAR gt_itab.
ENDLOOP.
ENDFORM. "get_data
Form write_data *
FORM write_data.
PERFORM find_list_header.
PERFORM fill_field_cat TABLES gt_fldcat
USING 'GT_ITAB'
'YIWM_UOM_STOCK'.
gv_repid = sy-repid.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_buffer_active = ' '
i_callback_program = gv_repid
i_default = 'X'
i_save = 'A'
is_layout = gs_layout
it_fieldcat = gt_fldcat[]
is_variant = gs_variant
TABLES
t_outtab = gt_itab.
ENDFORM. " write_data
Form find_list_header *
FORM find_list_header.
CLEAR : gt_header, gt_header[].
gt_header-typ = 'H'.
sy-title = 'UOM STOCK REPORT'.
MOVE sy-title TO gt_header-info.
APPEND gt_header.
ENDFORM. " find_list_header
Form fill_field_cat *
FORM fill_field_cat TABLES gt_fldcat
USING p_intname
p_inclname.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
i_program_name = sy-repid
i_inclname = p_inclname
i_internal_tabname = p_intname
CHANGING
ct_fieldcat = gt_fldcat[]
EXCEPTIONS
inconsistent_interface = 1
program_error = 2
OTHERS = 3.
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. " fill_field_cat
*& Form INITIALIZE_VARIANT
text
FORM initialize_variant .
g_save = 'A'.
CLEAR g_variant.
g_variant-report = sy-repid.
gx_variant = g_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant
EXCEPTIONS
not_found = 2.
IF sy-subrc = 0.
p_vari = gx_variant-variant.
ENDIF.
ENDFORM. " INITIALIZE_VARIANT
*& Form F4_FOR_VARIANT
text
FORM f4_for_variant.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
EXPORTING
is_variant = gs_variant
i_save = g_save
IMPORTING
e_exit = g_exit
es_variant = gx_variant
EXCEPTIONS
not_found = 2.
IF sy-subrc = 2.
MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
IF g_exit = space.
p_vari = gx_variant-variant.
ENDIF.
ENDIF.
ENDFORM. " F4_FOR_VARIANT
*& Form PAI_OF_SELECTION_SCREEN
text
FORM pai_of_selection_screen.
IF NOT p_vari IS INITIAL.
MOVE g_variant TO gx_variant.
MOVE p_vari TO gx_variant-variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant.
g_variant = gx_variant.
ELSE.
PERFORM initialize_variant.
ENDIF.
ENDFORM. " PAI_OF_SELECTION_SCREENHi Narendan ..
I changed but it is already leave to the code screen (leave program). I think it will be useful to send complete code again .Please remember , it gives error only call with transaction.
REPORT yiwm_uom_stock .
*---Data Include
INCLUDE yiwm_uom_stock_data.
INITIALIZATION.
PERFORM initialize_variant.
*----ON SELECTION SCREEN
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_vari.
PERFORM f4_for_variant .
*---START-OF-SELECTION
START-OF-SELECTION.
PERFORM get_data.
PERFORM write_data .
*& Form get_data
FORM get_data.
*--Quants of stock with selection screen.
SELECT werks lgort lgnum gesme
verme einme ausme lgpla
lgtyp matnr lqnum
FROM lqua
INTO CORRESPONDING FIELDS OF TABLE gt_itab
WHERE werks IN s_werks
AND lgnum EQ p_lgnum
AND lgort IN s_lgort
AND lgtyp IN s_lgtyp
AND kober IN s_kober
AND matnr IN s_matnr.
LOOP AT gt_itab.
CLEAR lagp .
SELECT SINGLE lgtyp lgber lptyp plauf skzua skzue skzsa skzse
skzsi spgru anzqu maxqu anzle maxle btanr btaps
kzdyn lgewi gewei mgewi bdatu bzeit ivivo sorlp
rdatu rzeit kzinv idatu ivnum ivpos brand uname
laedt kober reihf verif
FROM lagp
INTO CORRESPONDING FIELDS OF gt_itab
WHERE lgnum = gt_itab-lgnum
AND lgpla = gt_itab-lgpla
AND lgtyp = gt_itab-lgtyp.
CLEAR mara.
SELECT SINGLE matnr meins zzshmat matkl
mtart ean11 zzkshrtyp
FROM mara
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr.
CLEAR marm.
SELECT SINGLE meinh umrez umren breit hoehe
meabm volum voleh brgew gewei
FROM marm
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr
AND meinh EQ p_meinh.
CLEAR mlgn.
SELECT SINGLE ltkza ltkze lgbkz block
bsskz l2skr mkapv
FROM mlgn
INTO CORRESPONDING FIELDS OF gt_itab
WHERE matnr EQ gt_itab-matnr
AND lgnum EQ gt_itab-lgnum.
CLEAR mlgt.
SELECT SINGLE lgpla lpmax lpmin
mamng nsmng kober rdmng
FROM mlgt
INTO CORRESPONDING FIELDS OF gt_itab
WHERE lgnum EQ gt_itab-lgnum
AND lgpla EQ gt_itab-lgpla
AND matnr EQ gt_itab-matnr
AND lgtyp EQ gt_itab-lgtyp.
CLEAR makt.
SELECT SINGLE maktx
FROM makt
INTO gt_itab-maktx
WHERE matnr EQ gt_itab-matnr.
MODIFY gt_itab.
CLEAR gt_itab.
ENDLOOP.
ENDFORM. "get_data
Form write_data *
FORM write_data.
PERFORM find_list_header.
PERFORM fill_field_cat TABLES gt_fldcat
USING 'GT_ITAB'
'YIWM_UOM_STOCK'.
gv_repid = sy-repid.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_buffer_active = ' '
i_callback_program = gv_repid
i_default = 'X'
i_save = 'A'
is_layout = gs_layout
it_fieldcat = gt_fldcat[]
is_variant = gs_variant
TABLES
t_outtab = gt_itab.
ENDFORM. " write_data
Form find_list_header *
FORM find_list_header.
CLEAR : gt_header, gt_header[].
gt_header-typ = 'H'.
sy-title = 'UOM STOCK REPORT'.
MOVE sy-title TO gt_header-info.
APPEND gt_header.
ENDFORM. " find_list_header
Form fill_field_cat *
FORM fill_field_cat TABLES gt_fldcat
USING p_intname
p_inclname.
CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
EXPORTING
i_program_name = sy-repid
i_inclname = p_inclname
i_internal_tabname = p_intname
CHANGING
ct_fieldcat = gt_fldcat[]
EXCEPTIONS
inconsistent_interface = 1
program_error = 2
OTHERS = 3.
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. " fill_field_cat
*& Form INITIALIZE_VARIANT
text
FORM initialize_variant .
g_save = 'A'.
CLEAR g_variant.
g_variant-report = sy-repid.
gx_variant = g_variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant
EXCEPTIONS
EXCEPTIONS
wrong_input = 1
not_found = 2
program_error = 3
OTHERS = 4 .
IF sy-subrc = 0.
p_vari = gx_variant-variant.
ENDIF.
ENDFORM. " INITIALIZE_VARIANT
*& Form F4_FOR_VARIANT
text
FORM f4_for_variant.
gs_variant-report = sy-repid.
gs_variant-variant = p_vari.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
EXPORTING
is_variant = gs_variant
i_save = g_save
IMPORTING
e_exit = g_exit
es_variant = gx_variant
EXCEPTIONS
not_found = 2.
IF sy-subrc = 2.
MESSAGE ID sy-msgid TYPE 'S' NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ELSE.
IF g_exit = space.
p_vari = gx_variant-variant.
ENDIF.
ENDIF.
ENDFORM. " F4_FOR_VARIANT
*& Form PAI_OF_SELECTION_SCREEN
text
FORM pai_of_selection_screen.
IF NOT p_vari IS INITIAL.
MOVE g_variant TO gx_variant.
MOVE p_vari TO gx_variant-variant.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
EXPORTING
i_save = g_save
CHANGING
cs_variant = gx_variant.
g_variant = gx_variant.
ELSE.
PERFORM initialize_variant.
ENDIF.
ENDFORM. " PAI_OF_SELECTION_SCREEN -
Hi Experts,
i want to make some fields non-editable while the user navigates to the transaction IR02. This can be acheived using transaction variant because the user will be navigating through a button click from another program. But here i have a problem where i am not able to create transaction variant. It is giving an error whle i try to create it. Has anyone created a variant for IR02. Pls give your suggestions to acheive the same.
Thanks in advance
ShanthiDear PP CON,
No need to create any Transaction variant for this, while creating the role,after assigning the
Authorization for T code MFBF,check the value for this authorization object C_BACKFL REM:
Backflushing and include the tick marks for B alone and remove the tick marks for
K Component backflush
L Activity backlush.
Save the changes --->refresh the menu and if you need to assign to a test user , assign it and check.
Check & revert back.
Regards
Mangalraj.S -
hi all,
i need to know how to create screen variant & transaction variant for transaction code : F-58 ?
When i try to create screen variant for F-58 I get an error:
"screen variants are only possible for dialogue transactions".
Thanks & regards.
Message was edited by: annie siddScreen Variants
http://help.sap.com/saphelp_nw04/helpdata/en/7d/f63a22015111d396480000e82de14a/content.htm
Screen Variants Course
http://www50.sap.com/useducation/curriculum/course.asp?cid=60142840
If you find this answer useful, please reward me for the same.
Good luck -
Transaction variant from TCODE ME51n issue
I am created Transaction variant Against transaction ME51N and ME52n ( two transaction variant ) we donu2019t want to give transaction me51n and me52n to users.
But the problem is that when I revoke the transaction Me51n and me52n from users and give them to transaction variant transactions YME51N and YME52N when the user run that transaction error occur that missing authorization object S_TCODE and value ME51N same in run in transaction YME52n the required transaction is me52n. we donu2019t want to give both transactions to users please help me regarding this issue
thanksCheck whether you are using it right.following extract from SAP help apply.
Transaction type: Variant transaction
In the SAP Reference IMG, under "Basis Components" -> "Application Personalizaion" -> "Tailoring of Application Transactions", you can define transaction variants. These allow you to preassign values to fields within a transaction, define field attributes, or hide entire screens.
To run a transaction variant, you define a variant transaction. On the next screen, enter the name of the transaction and the name of the variant.
If above does not work there is a brute-force alternative- a little abap can be fired whenever someone executes me52n or yme52n to go after sy-uname and thereby call yme52n or me52n as need be! -
Same transaction variant runs differently on different servers
Hi experts,
We have created a transaction variant for MK01.
Our production system consists of 3 servers.
Everything is ok when we use this transaction variant on the main server, but there is a dump when the transaction variant is run on another server...
Any idea from where this problem may come : problem in the transaction variant, problem on server customizing ?
Thanks for your help !
PhilippeSorry, more details about the dump !
Using ST22, I found the following dump message :
SYSTEM_CORE_DUMPED
Process terminated by signal 11
Another information : Using SM21, I found the following messages :
Signal 11 received by operating system
Stop Workproc 2, PID 10753
Start Workproc 2, 3 times since system startup PID2672
Delete session 001 after error 023
Thanks for your help ! -
Hello,
using SHD0, I created a standard transaction variant ZIP01 for transaction IP01.
But how can I transport this variant to other systems?
I tried with program RSTRANSP with following parameters:
- Program Name: SAPLIWP3
- Variant name: ZIP01
But I get the following error message: "Function cannot be used for local/private objects"
Message no. DB275
Diagnosis
Variants cannot be transported if the relevant program has only been defined as a local/private object (development class $TMP).
System Response
No transport request generated.
I thougt I had attached my transaction variant and corresponding screen variants to a development package but the systems seems to tell it is not the case. How can I check it (I am just a functional consultant trying to learn more technical things, not an ABAPer, sorry)
By the way, I am not even sure it is the right way to transport transaction variants. In other threads, program RSTRANSP was mentioned to transport selection and layout variants but can it be used to transport transaction variants/screen variants created with SHD0 too?
Thanks in advance for your help.
Regards.Thank you both for your answers, but unfortunately I am still facing the same issue.
@Arseni: I checked as you mentioned and yes, the variant is well assigned to a package
@sFayaz: In SE38, when entering the program SAPLIWP3, and asking to display variants, I get the message:
"Program SAPLIWP3 has no selection screens
Message no. DB244"
Is a "transaction variant" the same as a "program variant"?
Edited by: Laurent Delhaie on Nov 25, 2011 12:01 PM -
Transaction variant not assigned
Hello Sir,
While I am posting the payment/receipt document in FBCJ (Cash Journal) I have got the error as - No accounting transaction variant assigned to FBCJ/K3. Where K3 is the document type.
BSRhi BSR,
Pls check in OBA7 whether u have created the Document type and it is assigned in Tcode FBCJC1. If it is not assigned pls assign to it......
if it is usefull..assign me the points...
ranjit
Maybe you are looking for
-
Function Module not extracting records when InfoPackaged is executed
Hi, I'm using a Function module for extracting data. The DataSource is working fine in RSA3 with a selection criteria. But when i schedule the infopackage with the same selections in the data selection tab, Its not getting me any records into BW. In
-
Error while creating work order from purchase order
Dear All, We are having a subcontracting scenario where we are creating a Work order from PO but getting the below error. Error - "No master data assigned to partners-locations-product combination." Done all the setting mentioned in the below thread
-
Enter Button no longer works after update
I updated FF to the most recent version this morning. upon completing the update I typed an address into the URL bar and hit enter, nothing happened. I've noticed that I must manually click every single time on the green arrow in order to proceed aft
-
Upcoming Lumira Webinar June 11th on the topic of "Big Data Visualization and Custom Extensions"
The next webinar in the Lumira series is coming up this week on Wednesday, June 11th, 10:00 AM - 11:00 AM Pacific Standard Time. The day is almost here and if you've already registered, thank you! If not, please click here to register. Speaker Profil
-
Hi We have set up a service material DIEN and placed a Sales Order and got it to Billing. The acounting doc is not creating due to "No standard cost for material". The standard material type DIEN does not have costing views. It is a service and there