Put a condition before you process the subsequent select statement.
Check for the lt_process_order holds any data or not.
i.e if lt_process_order[] is not initial.
<your select statement>
endif.
Thanks,
Namrata
Put a condition before you process the subsequent select statement.
Check for the lt_process_order holds any data or not.
i.e if lt_process_order[] is not initial.
<your select statement>
endif.
Thanks,
Namrata
Hi,
For assigning F4 help
You have to define, implement and register the event on F4.
Use method register_f4_for_fields.
And refer to this standard report this will surely help you.
BCALV_TEST_GRID_F4_HELP
Reward if helpful.
Hello Chitturi,
There are two forms of workbench request
1) Local Workbench request : In this case the workbench request has target system as <space>
2) Transportable workbench Request
This determination of Local / Transportable workbench request is based on package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.
So please check the package
Regards
Suresh Nair
hi,
Go to SE21.Enter Your Package Name.Click on Change Button.In the transport attribute assign a proper transport layer.Now Go to se09.click on check box workbench request.If your request number is displaying under local change request then double click on it and on property tab assign a proper target system. that's All.
Regards
Ajit Tiwari
Hi Aradhya,
First download your OLE generated object into Presentation Server(i.e. particular location) , then with the help of this FMs ""SO_DOCUMENT_SEND_API1" or "SO_NEW_DOCUMENT_SEND_API1" you can send Excel Sheet attached to your respective mail id . Search in SCN.SAP.COM lot of Sample code you can find code and discussion on this FMs .
Regard's
Smruti
Hi Santhosh,
While calling the form you got this exception because the parameter in form is different and the parameter that you passing to form is different. So check with the datatype of the attribute that you passing.
Ex for causing error may be like this:
DATA lv_str TYPE string.
PERFORM test USING lv_str.
FORM test im_str TYPE c.
***
ENDFORM.
Here datatype of lv_str and im_str is different. So here you get exception.
Hello Siong Chao
validate selection screen parameters through At Selection Screen on <field_name>events or by At Selection Screen,then use "For all entries" It's better .Join are beneficial for 2 tables only.
Hi Chao,
Instead of using the above complicated INNER JOIN code just divide it into select statements for different tables one by one e.g. AUFK, AFKO, AFPO, CRHD & MARA.
While you select from one table use those retrieved entries to filter data from the next select statement using "FOR ALL ENTRIES in....".
For example:
SELECT AUFNR
AUART
AUTYP
REFNR
ERNAM
ERDAT
AENAM
AEDAT
FROM aufk
into table it_aufk
where ...............(some condition - if any)
If sy-subrc is initial.
SELECT AUFNR
GLTRP
GSTRP
FTRMS
FROM afko
into table it_afko
FOR ALL ENTRIES IN it_aufk
WHERE aufnr = it_aufk-aufnr.
Endif.
This will improve your performance and simplify the code rather than using INNER JOIN.
Hope this helps.
Regards,
Arnab
Hi smruti,
is there any way to send a mail , in body can we attach text boxes.(attachment i know,but i'm asking in body).
Please let me know if you know..
Regards,
Krishna
A common error.
Almost as common as the erroneous belief that many responders to this post seem to have. I've said it before and I'll say it again.
In nearly ever case, INNER JOIN performs better than FOR ALL ENTRIES.
The only exceptions are when one or more of the tables is buffered, or with very specific forms of data. In these cases, you must test to find out which is most efficient, as there are no hard and fast rules.
I don't know where this myth about INNER JOIN arose, but I'm pleased that now, at last, in the ABAP for HANA courses it is being debunked by SAP.
Hi,
In excel file treat the text format cells are treated as text. In your internal table take the field name of type either char or string, then call the fm TEXT_CONVERT_XLS_TO_SAP then it convert the excel file to internal table with exactly what it contains.
Regards,
Chinni
HI
most of the fields do not have PARAMETER ID''s,
do i need to create parameter id's for them...(and some screen fields are structure fields)...
..................
Dear Hemant,
As Deepak Nagar Worte, It is correct solution for this because For All Entries Delete all duplicates from Internal table. So User POSNR with VBELN.
Thanks!.
Ram Shanker
use a dynamic submit statement inside your excel upload program
lets say lv_program_name is the variable where you store the program name after uploading from excel ...
so then use SUBMIT (lv_program_name)
also if it has to be run multiple times , (if there is a column say no. of times )
then use Do lv_n times. and then the above submit...
experiment a little its achievable ...
hope it helps...
Hi Custodio
Thank you for ansering
Now I can find the link of Project definition to Profit Center.
But the the fields AKSTL, FKSTL and KOSTL in table PRPS are empty...
The Only link for Profit Center that I can find is in table csks.
Hi,
Have you checked the data elements for all the fields?
You cannot create parameter ids if its a standard data element.
What do you mean by some fields are structure fields.
If you dont have parameter ids, you can also use import export parameters.
Dear Readyy,
Please put a Break Point and check the action at runtime. May by show the some result.
Thanks.
Ram
Yes I have checked, No problem with authorization...
I am able to edit other WS, but not this particular...
Dear Vinay.
It'd be better to go with BDC for this issue. Just Record and perform the BDC interanll on action of Transfer button of Module Pool Screen.
Thanks.
Ram
Hi Priya,
It is not possible to change standard program without 'access key'. Access key is not for security purpose but it is for licence.
If you are adding new field to standard program, you can go for enhancement by using exit's where you can add you own code.
If you want to try with enhancement you can refer this below link:
http://wiki.sdn.sap.com/wiki/display/ABAP/Enhancements+(User+Exits+and+Customer+exits)