I recently created my own BDC upload template that enables user to choose the processing mode, the update mode and options for Default Size, Continue After Commit, and Not a Batch Input Session easily.
Another good thing with this program is a functionality to generate an excel file template. The image below shows the actual screenshot.
I modified the SAP standard program BDCRECX1 and saved it as ZBDCRECX1. I used this for my BDC upload program instead of the standard BDCRECX1 include. You may download the source code of ZBDCRECX1 on the link below. I also included a sample upload program utilizing the ZBDCRECX1 include.
zbdc_template.zip
Enjoy coding! 
Below are the steps on how to activate webgui on SAP ECC 6.0:
1. Go to your Instance Profile parameter using tcode RZ10 and set the icm/server_port_0 parameter to PROT=HTTP,PORT=8000
2. Now go to transaction SICF and activate the following:
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
3. Run transaction SIAC_PUBLISH_ALL_INTERNAL to publish internet services.
4. Now browse to http://<servername>:<icmport>/sap/bc/gui/sap/its/webgui/
As simple as that, you can now use SAP webgui.
This tutorial will teach you how to export an ALV report to Microsoft Excel file. This is intended for abap programmers who already have a knowledge in ALV reporting as I will not show here how to create an ALV.
Assuming you already have an ABAP program with ALV report, what you need to do is add a button or menu that will trigger the function that will export the ALV data to Excel file. but before that let’s start first with the declaration of types and variables that we’re going to use.
TYPE-POOLS ole2. " we will use OLE objects
DATA: v_excel TYPE ole2_object, " Excel object
v_wrkbkl TYPE ole2_object, " list of workbooks
v_wrkbk TYPE ole2_object, " workbook
v_cell TYPE ole2_object, " cell
v_font TYPE ole2_object, " font
v_row TYPE i. " rowNow we’re done with the variable declaration, let’s proceed to the main program. We will create 3 forms: One is for the preparation of the Excel file, second is for the data export from alv cells to excel cells, and third is for error handling.
The code below is for the preparation of excel application object.
* it_main and wa_main is the tables used in your ALV
FORM export_to_excel TABLES p_it_main STRUCTURE wa_main.
* Create Excel object
CREATE OBJECT v_excel 'EXCEL.APPLICATION'.
* Call Error_handler form
PERFORM Error_Handler.
* Show excel window
SET PROPERTY OF v_excel 'Visible' = 1.
* get list of workbooks, initially empty
CALL METHOD OF v_excel 'Workbooks' = v_wrkbkl.
PERFORM Error_Handler.
* add a new workbook to workbook list
CALL METHOD OF v_wrkbkl 'Add' = v_wrkbk.
PERFORM Error_Handler.
* export ALV column header to Excel
* PERFORM export_data USING rows columns boldfont value
PERFORM export_data USING 1 1 1 'header_1'.
PERFORM export_data USING 1 2 1 'header_2'.
PERFORM export_data USING 1 3 1 'header_3'.
PERFORM export_data USING 1 4 1 'header_4'.
PERFORM export_data USING 1 5 1 'header_5'.
* Loop through ALV rows and fields and transfer data to Excel
LOOP AT p_it_main INTO wa_main.
v_row = sy-tabix + 1.
PERFORM export_data USING v_row 1 0 wa_bill-field1.
PERFORM export_data USING v_row 2 0 wa_bill-field2.
PERFORM export_data USING v_row 3 0 wa_bill-field3.
PERFORM export_data USING v_row 4 0 wa_bill-field4.
PERFORM export_data USING v_row 5 0 wa_bill-field5.
ENDLOOP.
FREE OBJECT v_excel.
PERFORM error_handler.
ENDFORM.The next code is for the export_data form.
FORM export_data USING x y z val.
CALL METHOD OF v_excel 'Cells' = v_cell
exporting
#1 = x
#2 = y.
PERFORM error_handler.
SET PROPERTY OF v_cell 'Value' = val.
PERFORM error_handler.
GET PROPERTY OF v_cell 'Font' = v_font.
PERFORM error_handler.
SET PROPERTY OF v_font 'Bold' = z .
PERFORM error_handler.
ENDFORM.And for the code of error_handler form.
FORM error_handler.
IF sy-subrc 0.
CALL METHOD OF v_excel 'QUIT'.
FREE OBJECT v_excel.
v_excel-handle = -1.
MESSAGE: 'Failed to export to Excel.' TYPE 'E'.
ENDIF.
ENDFORM.Now that we’ve completed all the 3 forms, all you have to do now is call the export_to_excel form to initiate the export. In the example below, I call the export_to_excel form on user command ‘M_EXP’.
FORM f_user_command USING p_ucomm LIKE sy-ucomm.
CASE p_ucomm.
WHEN 'M_EXP'.
PERFORM export_to_excel TABLES it_main.
WHEN 'CANCEL' OR 'BACK' OR 'EXIT'.
LEAVE TO SCREEN 0.
ENDCASE.
ENDFORM.
JEST table contains object status that is either system status or a user status. Field STAT corresponds to the Object Status. Field INACT identifies whether the status is currently active or inactive and field CHGNR is the change number that identifies the change documents for an object and is incremented serially.
TJ02 table contains the list of system status and description. All statuses in this table are internal. This means they are consistent across objects and clients. A single object can have multiple active system statuses and user statuses & inactive ones.
TJ30 table contains the list of user status and TJ30T contains their description.
You could use function module STATUS_READ read active object status and STATUS_OBJECT_READ to retrieve the status profile of an object number.
Instead of going to transaction code SM30 to maintain your table, why not create your own t-code for that specific table maintenance screen. To do this, here’s the step by step procedure I stumbled upon on some SAP technical forums:
1. Go to t-code SE93.
2. Type in your customized t-code on the transaction code field.
3. Click on Create button.
4. Give it a short description and tick on the “Transaction with Parameters” radio button.
2. On the next screen, type “SM30″ in the transaction field.
3. Check mark the skip initial screen.
4. type “0″ on screen field
5. Under the Classification area, check mark on Inherit GUI attributes
6. Tick all GUI support checkboxes.
7. On the default value section, give this:
Name of Screen Field: VIEWNAME
Value: Your table name
Name of Screen Field: UPDATE
Value: X X
sdn blogger
sap blogger
Recent Comments