SAP Study

[Configuration] Create, Change Unit Of Measure

2011-04-12T20:17:00.000-07:00

Conversion to unit of measure in the SAP can be stored with the naming of internally (SAP standard) or external (determined by the user). For naming the unit of measure (UoM) is provided for each - each language.
Unit unit of measure (UoM) is comprised of 3 characters for the keyword (business key), and 30 characters for description.

IMG -> SAP NetWeaver -> General Settings -> Check units of measurement

SAP Router installation

2011-04-04T22:59:00.000-07:00

Create a message to SAP with component XX-SER-NET-NEW Saprouter to register by filling out the form, the hostname and IP Public saprouter
Set 2 environment variables: SECUDIR and SNC_LIB according to the
guide you’ve downloaded. # SECUDIR=/saprouter/; export SECUDIR # SNC_LIB=/saprouter/; export SNC_LIB
Download the latest SapCrypto Saprouter and then extract to a directory C:\saprouter
Go to https: / / service.sap / com / saprouter-sncadd, select Apply, then we will get distinguish< span=""> name>distinguish

5. Generate Certificate Request with command sapgenpse get_pse -v -r C:\saprouter\certreq -p

C:\saprouter\local.pse “”

6. Enter certreq file content to the web, then press the button a Certificate Request

From the Web will be generated certificate, copied its contents into a new file with the name srcert
Import command with Certifcate
sapgenpse import_own_cert-c C: \ SAProuter \ srcert-p C: \ SAProuter \ local.pse

Generate Credentials to the user who used to run saprouter by using the command:
sapgenpse seclogin-p C: \ usr \ sap \ saprouter \ local.pse-O
(this will of create the file "cred_v2?)

Check saprouter configuration with command:
sapgenpse get_my_name -v -n Issuer
(This should always give the answer “CN=SAProuter CA, OU=SAProuter,
O=SAP, C=DE”)

Start Saprouter with command

Saprouter -r -K "p:"

Saprouter certificate has a validity time for 1 year, after more than 1 year be expired, to renew, repeat steps 4-8

CREATE DOWN PAYMENT REQUEST (F-47)

2011-04-04T21:21:00.000-07:00

Header Data
Document Date	Current date -2
Posting Date	Current date -2
Reference Number	F-47/DDMMYYYY/001
Document header Text	DOWN PAYMENT REQUEST 001
Type	KA
Period	Current period
Company Code	1000
Currency	USD

Tab Vendor

Account

Your Vendor Account

Target Sp AP Account

Click Enter

Item 1/Down Payment Request / 39F
Amount	1000
Tax Amount	Blank
Due On	Current Date + 1 months
Text	Your choice

Click Smulate

Click Save

Configuration Automatic Posting Revaluation

2011-04-04T20:56:00.000-07:00

Here is a user manual how to configure automatic separately when posting to GL Accounts that are revalued. Configuration will be done when there are new additions as well as GL Accounts GL Accounts should be revaluation tesebut and recognition of gain or loss that allows SAP to perform automatic recognition of these journals. Hopefully helpful,

OPEN AND CLOSE PERIOD FI (OB52)

2011-04-04T20:49:00.000-07:00

Transaction Code OB52 is used for opening and closing of FI posting periods,
in this transaction, you can control the G/L account posting for a particular period.

Type rest of the post here

Step by step Add Custom Field (COOIS) with BADI

2010-07-20T01:15:00.000-07:00

In this tutorial I will share how to add fields in transaction code COOIS (Production Order Information System). Field to be added is WEMPF (goods receipt) and ABLAD (Unloading Point).

   - My first step would be to add custom fields.
     for these additions, can be added at the table IOHEADER_DELAY.
     open transaction code SE11, write IOHEADER_DELAY

so add field WEMPF and ABLAD.

- The second step is to edit the Badi. for this tcode SAPLCOISEXT I use the program with (include) LCOISEXTU02

My next step will modify the program

Data Declaration

finally we have successfully added a custom field and now we will try tcode COOIS

Creating Non-Valuated Material

2010-01-12T23:14:00.000-08:00

This Exercise explain how to make master material with non-valuated type in SAP.

Menu Path :

SAP Menu - Logistics - Material Management - Material Master - Material - Create (special) - Non Valuated Material

TCODE :
MMU1

choose Select view

Choose :
- Basic Data 1
- General Plant Data / Storage 1
- Generla Plant Data / Storage 2

press

choose
-plant PL01
-stor loc SL01

press

fill base unit of measure

press

choose Plant data / stor 2
click serial no profile

ALV GRID TEMPLATE

2010-01-11T19:44:00.000-08:00

ALV GRID is one of component in SAP to display data.
ALV GRID is very useful to display very big data in SAP.
Now i will share a template program to create ALV GRID with function 'REUSE_ALV_GRID_DISPLAY'.
I hope it useful for all.

INCLUDE ZALV_GRIR2_TOP . " global Data

START-OF-SELECTION.
PERFORM get_data.

END-OF-SELECTION.
IF NOT ta_report[] IS INITIAL.
PERFORM f_write_data.
ELSE.
MESSAGE 'Data Kosong' TYPE 'I'.
ENDIF.

TOP-OF-PAGE.

* INCLUDE ZALV_GRIR_O01 . " PBO-Modules
* INCLUDE ZALV_GRIR_I01 . " PAI-Modules
INCLUDE ZALV_GRIR2_F01 . " FORM-Routines

*&---------------------------------------------------------------------*
*& Include ZALV_GRIR_TOP Report ZALV_GRIR
*&
* Description : For Project in SMart Telkom, GR/IR Report
*&---------------------------------------------------------------------*

REPORT zalv_grir.
TYPE-POOLS : slis,
kkblo.

tables : bsis, "Accounting: Secondary Index for G/L Accounts
bsid, "Accounting: Secondary Index for Customers
bseg, "Accounting Document Segment
bkpf. "Accounting Document Header

TYPES : BEGIN OF report,
ebeln TYPE bseg-ebeln, "Purchasing Document Number
name1 TYPE lfa1-name1, "Vendor Master name1
xblnr TYPE bsid-xblnr, "Reference Document Number
zuonr TYPE bsid-zuonr, "Assignment Number
sgtxt TYPE bsid-sgtxt, "Item Text
dmbtr TYPE bsis-dmbtr, "Amount in Local Currency
belnr TYPE bsis-belnr, "Accounting Document Number
bldat TYPE bsis-bldat, "Document Date in Document
budat TYPE bsis-budat, "Posting Date in the Document
awkey TYPE bkpf-awkey, "Reference Key
END OF report.

DATA : ta_report TYPE TABLE OF report with HEADER LINE,
gs_report like ta_report.

DATA: gs_fieldcat TYPE slis_fieldcat_alv,
gs_selcrit TYPE slis_sel_hide_alv.

DATA: gt_fieldcat TYPE TABLE OF slis_fieldcat_alv,
gt_sort TYPE slis_t_sortinfo_alv,
gt_events TYPE slis_t_event,
gs_layout TYPE slis_layout_alv,
gv_repid TYPE sy-repid,
i_print TYPE slis_print_alv.

CONSTANTS : c_x VALUE 'X'.

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
PARAMETERS : pa_hkont TYPE bsis-hkont OBLIGATORY, "General Ledger Account
pa_bukrs TYPE bsis-bukrs OBLIGATORY, "Company Code
pa_gjahr TYPE bsis-gjahr OBLIGATORY. "Fiscal Year

SELECTION-SCREEN END OF BLOCK b1.

*&---------------------------------------------------------------------*
*& Include ZALV_GRIR_F01
*&---------------------------------------------------------------------*
*&---------------------------------------------------------------------*
*& Include ZALV_NON_SCR_F01
*&---------------------------------------------------------------------*

*&---------------------------------------------------------------------*
*& Form get_data
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*

FORM get_data.

DATA : BEGIN OF lt_bsis OCCURS 0,
dmbtr TYPE bsis-dmbtr,
belnr TYPE bsis-belnr,
bldat TYPE bsis-bldat,
budat TYPE bsis-budat,
xblnr TYPE bsid-xblnr,
zuonr TYPE bsid-zuonr,
sgtxt TYPE bsid-sgtxt,
awkey TYPE bkpf-awkey,
ebeln TYPE bseg-ebeln,
name1 TYPE lfa1-name1,
lifnr TYPE bseg-lifnr,
END OF lt_bsis.

DATA : BEGIN OF ls_lifnr,
ebeln TYPE bseg-ebeln,
lifnr TYPE bseg-lifnr,
END OF ls_lifnr.

DATA : BEGIN OF ls_lfa1,
name1 TYPE lfa1-name1,
END OF ls_lfa1.

DATA : lv_line_bsis TYPE i.

FIELD-SYMBOLS : LIKE lt_bsis.

REFRESH : lt_bsis , ta_report.

CLEAR : ls_lifnr , ls_lfa1.

SELECT a~dmbtr a~belnr a~bldat a~budat c~awkey
b~xblnr b~zuonr b~sgtxt INTO CORRESPONDING FIELDS OF TABLE
lt_bsis FROM ( ( bsis AS a
JOIN bsid AS b
ON a~belnr = b~belnr )
JOIN bkpf AS c
ON a~belnr = c~belnr )
WHERE a~hkont EQ pa_hkont AND
a~bukrs EQ pa_bukrs AND
a~gjahr EQ pa_gjahr.

DESCRIBE TABLE lt_bsis LINES lv_line_bsis.

IF lv_line_bsis > 0.

LOOP AT lt_bsis.

*ambil data untuk kolom lifnr dan ebeln
SELECT SINGLE ebeln lifnr FROM bseg INTO CORRESPONDING FIELDS OF
ls_lifnr
WHERE belnr = lt_bsis-belnr AND
hkont = pa_hkont AND
bukrs = pa_bukrs AND
gjahr = pa_gjahr.
IF sy-subrc = 0 .
lt_bsis-ebeln = ls_lifnr-ebeln.
lt_bsis-lifnr = ls_lifnr-lifnr.
ENDIF.

MODIFY lt_bsis.
ENDLOOP.

*ambil data untuk kolom name1 dari lfa1 table
LOOP AT lt_bsis.

SELECT SINGLE name1 FROM lfa1 INTO CORRESPONDING FIELDS OF
ls_lfa1
WHERE lifnr = lt_bsis-lifnr.

IF sy-subrc = 0 .
lt_bsis-name1 = ls_lfa1-name1.

ENDIF.

MODIFY lt_bsis.
ENDLOOP.

ELSE.

ENDIF.

*masukkan data dari lt_bsis ke ta_report
LOOP AT lt_bsis.

gs_report-ebeln = lt_bsis-ebeln.
gs_report-name1 = lt_bsis-name1.
gs_report-xblnr = lt_bsis-xblnr.
gs_report-zuonr = lt_bsis-zuonr.
gs_report-sgtxt = lt_bsis-sgtxt.
gs_report-dmbtr = lt_bsis-dmbtr.
gs_report-belnr = lt_bsis-belnr.
gs_report-bldat = lt_bsis-bldat.
gs_report-budat = lt_bsis-budat.
gs_report-awkey = lt_bsis-awkey+0(10).
* gs_report-awkey = lt_bsis-awkey.
APPEND gs_report TO ta_report.
ENDLOOP.

ENDFORM. "get_data

*&---------------------------------------------------------------------*
*& Form f_write_data
*&---------------------------------------------------------------------*
* Write Data
*----------------------------------------------------------------------*
FORM f_write_data .

gv_repid = sy-repid.
PERFORM f_fieldcat.
PERFORM build_sort.
PERFORM f_eventtab_build.
PERFORM build_layout USING gs_layout.

PERFORM f_display_alv TABLES ta_report.
ENDFORM. " f_write_data

*&---------------------------------------------------------------------*
*& Form f_print_control
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
FORM f_print_control.
i_print-no_print_listinfos = c_x.
i_print-no_print_selinfos = c_x.
i_print-reserve_lines = 0.
i_print-no_change_print_params = c_x.
ENDFORM. " f_print_control

*&--------------------------------------------------------------------*
*& Form eventtab_build
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->LT_EVENTS text
*---------------------------------------------------------------------*

FORM f_eventtab_build.

DATA: ls_events LIKE LINE OF gt_events.

"--- Callback events
ls_events-name = 'TOP_OF_PAGE'.
ls_events-form = 'F_TOP_OF_PAGE'.
APPEND ls_events TO gt_events.
ls_events-name = 'SUBTOTAL_TEXT'.
ls_events-form = 'F_SUBTOTAL_TEXT'.
APPEND ls_events TO gt_events.
* ls_events-name = 'END_OF_LIST'.
* ls_events-form = 'F_END_OF_LIST'.
APPEND ls_events TO gt_events.
ls_events-name = 'USER_COMMAND'.
ls_events-form = 'F_USER_COMMAND'.
APPEND ls_events TO gt_events.
CLEAR ls_events .

ENDFORM. "eventtab_build

*&--------------------------------------------------------------------*
*& Form f_menu_toolbar
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->FU_EXTAB text
*---------------------------------------------------------------------*
FORM f_menu_toolbar USING fu_extab TYPE slis_t_extab.
APPEND '&INFO' TO fu_extab.
SET PF-STATUS 'ALV' EXCLUDING fu_extab.

ENDFORM. "f_menu_toolbar

*&--------------------------------------------------------------------*
*& Form top_of_page
*&--------------------------------------------------------------------*
FORM f_top_of_page.

DATA: l_ta_list_top_of_page TYPE slis_t_listheader.

PERFORM f_comment_header USING l_ta_list_top_of_page[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = l_ta_list_top_of_page.

ENDFORM. "top_of_page

*&---------------------------------------------------------------------*
*& Form f_end_of_list
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
FORM f_end_of_list.

DATA: l_ta_list_end_of_list TYPE slis_t_listheader.

PERFORM f_comment_footer USING l_ta_list_end_of_list[].
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = l_ta_list_end_of_list
i_end_of_list_grid = 'X'.

ENDFORM. "top_of_page
*---------------------------------------------------------------------*
* FORM user_command *
*---------------------------------------------------------------------*
* Control fcode
*---------------------------------------------------------------------*
FORM f_user_command USING fu_ucomm LIKE sy-ucomm
fu_selfield TYPE slis_selfield.
DATA : ls_report LIKE ta_report.
DATA : lv_pilih(40) TYPE c.

CASE fu_ucomm.
WHEN '&IC1'. "Double Click
* READ TABLE ta_report INTO ls_report INDEX fu_selfield-tabindex.
*
* CONDENSE fu_selfield-value.
*
* IF fu_selfield-fieldname = 'CARRID'.
*
* SUBMIT zalv_non_scr_sbook
* WITH pa_carr EQ fu_selfield-value
* AND RETURN.
*
* ENDIF.
WHEN 'EXIT'.
LEAVE PROGRAM.

ENDCASE.
ENDFORM. "user_command

*&---------------------------------------------------------------------*
*& Form f_fieldcat
*&---------------------------------------------------------------------*
* Transfer of fields into field catalog
*----------------------------------------------------------------------*
FORM f_fieldcat .

REFRESH: gt_fieldcat.

*** Field categories
PERFORM f_set_fieldcat USING: 1 'EBELN' 'TA_REPORT' ''
text-h01 'K' '' '' '' '' '',
2 'NAME1' 'TA_REPORT' ''
text-h02 'K' '' '' '' '' '',
3 'XBLNR' 'TA_REPORT' ''
text-h03 '' '' '' '' '' '',
4 'ZUONR' 'TA_REPORT' ''
text-h04 '' '' '' '' '' '',
5 'SGTXT' 'TA_REPORT' ''
text-h05 '' '' '' '' '' '',
6 'DMBTR' 'TA_REPORT' ''
text-h06 '' '' '' '' 'X' '',
7 'BELNR' 'TA_REPORT' ''
text-h07 '' '' '' '' '' '',
8 'BLDAT' 'TA_REPORT' ''
text-h08 '' '' '' '' '' '',
9 'BUDAT' 'TA_REPORT' ''
text-h09 '' '' '' '' '' '',
10 'AWKEY' 'TA_REPORT' ''
text-h10 '' '' '' '' '' ''.

ENDFORM. " f_fieldcat

*&---------------------------------------------------------------------*
*& Form build_layout
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->P_LAYOUT text
*----------------------------------------------------------------------*
FORM build_layout USING p_layout TYPE slis_layout_alv.

p_layout-zebra = c_x.
p_layout-colwidth_optimize = c_x.
* p_layout-totals_before_items = 'X'.
p_layout-no_totalline = c_x.
p_layout-window_titlebar = 'GR/IR Report'.
gv_repid = sy-repid.
gs_selcrit-mode = 'C'.
p_layout-totals_text = 'Total'.
p_layout-subtotals_text = 'Sub Total'.

ENDFORM. "build_layout
*&---------------------------------------------------------------------*
*& Form build_sort
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
FORM build_sort.
DATA: ls_sort TYPE slis_sortinfo_alv.

DEFINE def_sort.
clear ls_sort.

ls_sort-spos = &1.
ls_sort-fieldname = &2.

ls_sort-tabname = &3.

* sort by ascending
ls_sort-up = c_x.

* subtot key
ls_sort-subtot = c_x.

* separate between group
ls_sort-group = 'UL'.
append ls_sort to gt_sort.

END-OF-DEFINITION.

def_sort '1' 'EBELN' 'TA_REPORT'.

ENDFORM. "build_sort
*&---------------------------------------------------------------------*
*& Form f_set_fieldcat
*&---------------------------------------------------------------------*

*&---------------------------------------------------------------------*
*& Form f_set_fieldcat
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->VALUE(FU_COLPOS) text
* -->VALUE(FU_FIELDNAME) text
* -->VALUE(FU_TABNAME) text
* -->VALUE(FU_CURRENCY) text
* -->VALUE(FU_TEXT) text
* -->VALUE(FU_KEY) text
* -->VALUE(FU_RFIELDNAME) text
* -->VALUE(FU_RTABNAME) text
* -->VALUE(FU_ROLLNAME) text
* -->VALUE(FU_DOSUM) text
* -->VALUE(FU_DATATYPE) text
*----------------------------------------------------------------------*
FORM f_set_fieldcat USING value(fu_colpos) TYPE any
value(fu_fieldname) TYPE any
value(fu_tabname) TYPE any
value(fu_currency) TYPE any
value(fu_text) TYPE any
value(fu_key) TYPE any
value(fu_rfieldname) TYPE any
value(fu_rtabname) TYPE any
value(fu_rollname) TYPE any
value(fu_dosum) TYPE any
value(fu_datatype) TYPE any.

CLEAR gs_fieldcat.
gs_fieldcat-col_pos = fu_colpos.
gs_fieldcat-fieldname = fu_fieldname.
gs_fieldcat-tabname = fu_tabname.
gs_fieldcat-seltext_m = fu_text.
gs_fieldcat-ddictxt = 'M'.
gs_fieldcat-ref_tabname = fu_rtabname.
gs_fieldcat-ref_fieldname = fu_rfieldname.
gs_fieldcat-rollname = fu_rollname.
gs_fieldcat-do_sum = fu_dosum.
gs_fieldcat-datatype = fu_datatype.

CASE fu_key.
WHEN 'K'. "Key
gs_fieldcat-key = c_x.
WHEN 'N'. "No Display
gs_fieldcat-no_out = c_x.
WHEN 'H'. "Hotspot
gs_fieldcat-hotspot = c_x.
WHEN 'I'. "Icon
gs_fieldcat-icon = c_x.

ENDCASE.

* IF fu_fieldname = 'CARRID'.
* gs_fieldcat-hotspot = c_x.
* ENDIF.
APPEND gs_fieldcat TO gt_fieldcat.
ENDFORM. " f_set_fieldcat

*&--------------------------------------------------------------------*
*& Form f_display_alv
*&--------------------------------------------------------------------*
* text
*---------------------------------------------------------------------*
* -->FT_OUTPUT text
*---------------------------------------------------------------------*
FORM f_display_alv TABLES ft_output.

CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = gv_repid
is_layout = gs_layout
it_fieldcat = gt_fieldcat[]
it_sort = gt_sort[]
it_events = gt_events[]
is_sel_hide = gs_selcrit
i_save = 'A'
is_print = i_print
i_background_id = 'ALV_BACKGROUND'
TABLES
t_outtab = ft_output
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc NE 0.
EXIT.
ENDIF.
ENDFORM. "f_display_alv

*&--------------------------------------------------------------------*
*& Form comment_header
*&--------------------------------------------------------------------*
FORM f_comment_header USING fu_top_of_page TYPE slis_t_listheader.

DATA: ls_line TYPE slis_listheader.
DATA: lv_text(50).

CLEAR ls_line.
ls_line-typ = 'H'.
ls_line-info = 'GR/IR Report'.
APPEND ls_line TO fu_top_of_page.

CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'Report'.
ls_line-info = sy-cprog.
APPEND ls_line TO fu_top_of_page.

CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'Client'.
ls_line-info = sy-mandt.
APPEND ls_line TO fu_top_of_page.

CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'User'.
ls_line-info = sy-uname.
APPEND ls_line TO fu_top_of_page.

ls_line-info = lv_text.
APPEND ls_line TO fu_top_of_page.

ENDFORM. "comment_build

*&---------------------------------------------------------------------*
*& Form f_comment_footer
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* -->FU_END_OF_LIST text
*----------------------------------------------------------------------*
FORM f_comment_footer USING fu_end_of_list TYPE slis_t_listheader.
DATA: ls_line TYPE slis_listheader.

* STATUS LINE: TYPE S
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'Pimpinan'.
ls_line-info = 'Rachmad Kurniawan'.
APPEND ls_line TO fu_end_of_list.

ENDFORM. "comment_build
*&---------------------------------------------------------------------*
*& Form f_subtotal_text
*&---------------------------------------------------------------------*
* text
*----------------------------------------------------------------------*
* --> p1 text
* <-- p2 text
*----------------------------------------------------------------------*
FORM f_subtotal_text USING u_f_alvout LIKE ta_report
u_f_subtot_text TYPE kkblo_subtot_text.

* IF u_f_subtot_text-criteria = 'CARRID'.
** IF u_f_alvout-carrid = 'AA'.
* u_f_subtot_text-display_text_for_subtotal =
* 'Total Penjualan AA :'.
** ELSEIF u_f_alvout-carrid = 'UA'.
** u_f_subtot_text-display_text_for_subtotal =
** 'Total Penjualan UA :'.
* ENDIF.
* ENDIF.
*
* IF u_f_subtot_text-criteria = 'DMBTR'.
* u_f_subtot_text-display_text_for_subtotal =
* 'Total Penjualan AA :'.
* endif.
ENDFORM. " f_subtotal_text

Price Comparison In SAP

2010-01-08T00:20:00.000-08:00

In our daily business process sometimes we want to compare price from one RFQ (Request for Quotation) to another RFQ to meet best price. SAP has provided for this condition. you can see it in TCODE ME49. the Price comparison consist of Basic Price, Discounts and Delivery charges

If you want to compare price for RFQ please bundle it with same collective no when you input RFQ

Convert Currency with Exchange Rate in SAP-Abap

2009-12-23T00:40:00.000-08:00

SAP can handle transaction with any currency. you can also convert it from one currency to another currency with different exchange rate in any date.
In some cases, we need to convert it to one currency.
for example we create BAPI for price comparison which the price must convert it into one currency, IDR. the solution for this case, first we can access the table for exchange rate TCURR, but we recommend to use function from SAP "BAPI_EXCHANGERATE_GETDETAIL".

CALL FUNCTION 'BAPI_EXCHANGERATE_GETDETAIL'
EXPORTING
rate_type = 'M' -----> type of rate
from_curr = 'USD' -----> From Currency
to_currncy = 'IDR' -----> to Currency
date = sy-datum -------> if you want use this time
IMPORTING
exch_rate = ------------> use structure BAPI1093_0
return = -----------> use bapiret1

List Of Movement Type In SAP

2009-07-24T01:48:00.000-07:00

there are so many movement type in SAP...
here therea are the list..

101 GR goods receipt
102 Reversal of GR
103 GR into blocked stck
104 Rev. GR to blocked
105 GR from blocked stck
106 Rev.GR from blocked
121 GR subseq. adjustm.
122 RE return to vendor
123 RE rtrn vendor rev.
124 GR rtrn blocked stck
125 GR rtn blkd stck rev
131 Goods receipt
132 Goods receipt
141 GR G subseq. adjustm
142 GR G subseq. adjustm
161 GR returns
162 GR rtrns reversal
201 GI for cost center
202 RE for cost center
221 GI for project
222 RE for project
231 GI for sales order
232 RE for sales order
241 GI for asset
242 RE for asset
251 GI for sales
252 RE for sales
261 GI for order
262 RE for order
281 GI for network
282 RE for network
291 GI all acc. assigmts
292 RE all acct assigmts
301 TF tfr.plnt.to plnt.
302 TR tfr.plnt.to plnt.
303 TF rem.fm.stor.to pl
304 TR rem.fm.stor.to pl
305 TF pl.in stor.in pl.
306 TR pl.in stor.in pl.
309 TF tfr.ps.mat.to mat
310 TR tfr.ps.mat.to mat
311 TF tfr. within plant
312 TR transfer in plant
313 TF rem.fm.str.toSLoc
314 TR rem.fm.str.toSLoc
315 TF pl.in str.in SLoc
316 TR pl.in stor.inSLoc
317 Create struct. mat.
318 RE create struc. mat
319 Split structured mat
320 RE split struct.mat.
321 TF quality to unrest
322 TR quality to unrest
323 TF quality in plant
324 TR quality in plant
325 TF blocked in plant
326 TR blocked in plant
331 GI to sampling QI
332 RE to sampling QI

333 GI to sampling unre.
334 RE to sampling unre.
335 GI to sampl. blocked
336 RE to sampling blkd
340 TF bch revaluation
341 TF unrestr.to restr.
342 TF unr. to rstricted
343 TF blocked to unre.
344 TR blocked to unre.
349 TF blocked to qual.
350 TR blocked to qual.
351 TF to stck in trans.
352 TR to stck in trans.
401 TP own from sls.ord.
402 TP own to sales ord.
403 TP own from consgt.
404 TP own to consgt.
405 TP own from project
406 TP own to project
411 TP own to own
412 Reversal own to own
413 TP SLoc to sls order
414 Rev. SLoc to sls ord
415 TP SLoc to project
416 Rev. SLoc to proj.
441 TP unrstr.to tiedEmp
442 TP tiedEmp.to unrstr
451 GI returns
452 RE returns (rev.)
453 TP returns to own
454 TP own to returns
455 TF st.tfr. returns
456 TR St.tfr. returns
457 TP Ret.to own QIS
458 TP Own QIS to ret.
459 TP Ret.to own blckd
460 TP Own blckt to ret.
501 GI receipt w/o PO
502 RE receipt w/o PO
503 GI receipt to qual.
504 RE receipt to qual.
505 GI receipt to blockd
506 RE receipt to blockd
511 GI deliv. w/o charge
512 RE deliv. w/o charge
521 GI receipt w/o PrOrd
522 RE receipt w/o PrOrd
523 GI quality w/o PrOrd
524 RE quality w/o PrOrd
525 GI blkd w/o prod.or.
526 RE blocked w/o PrOrd
531 GI by-product
532 RE by-product
533 GI by-product
534 RE by-product
535 GR by-prod. sls.ord.
536 GR by-prod. sls.ord.
541 GI whse to subc.stck
542 RE subctrStck toWhse
543 GI issue sls.ord.st.
544 GI receipt sls.or.st
545 GI rcpt SC by-prod.
546 GI issue SC by-prod.
551 GI scrapping
552 RE scrapping
553 GI scrapping QI
554 RE scrapping QI
555 GI scrapping blocked
556 RE scrapping blocked
557 GI adjust. transit
558 GI adjust. transit
561 GI entry of st. bals
562 RE entry of st.bals.
563 GI EntrStBals: QI
564 RE EntrStBals: QI
565 GI EntrStBals: blckd
566 RE EntrStBals: blckd
571 GI receipt assembly
572 RE receipt assembly
573 GI rcpt QI assembly
574 RE rcpt QI assembly
575 GI rcpt blkd assmbly
576 RE rcpt blkd assmbly
581 GI by-prod. network
582 RE by-prod. network
601 GD goods issue:delvy
602 RE goods deliv. rev.
603 TF rem.fm.stor.to pl
604 TR rem.fm.stor.to pl
605 TF pl.in stor.in pl.
606 TR pl.in stor.in pl.
621 GI ret.pack.:lending
622 GI ret.pack:ret.del.
623 GI iss:cust.ret.pack
624 GI rcpt:cust.re.pack
631 GI consgmt: lending
632 GI consgmt:ret.delvy
633 GI iss: cust.consgmt
634 GI rcpt:cust.consgmt
635 TF consgmt lending
636 TR consgmt ret. del.
641 TF to stck in trans.
642 TR to stck in trans.
643 TF to cross company
644 TR to cross company
645 TF cross company
646 TR cross company
647 TF to stck in trans.
648 TR to stck in trans.
651 GD ret.del. returns
652 GD ret.del. retn rev
653 GD returns unrestr.
654 GD returns unr. rev.
655 GD returns QI

656 GD returns QI rev.
657 GD returns blocked
658 GD returns blk. rev.
661 GI returns to vendor
662 RE ret. to vdr revrs
671 TR to stck in trans.
672 TF to stck in trans.
673 TF to cross company
674 TR to cross company
675 TR cross company
676 TF cross company
677 TR to stck in trans.
678 TF to stck in trans.
6A1 TF GI1
6A2 TR GI1
6A3 TF CC GI1
6A4 TR CC GI1
6A5 TF CC GI1
6A6 TR CC GI1
6A7 TF GI1
6A8 TR GI1
6B1 TF GI2
6B2 TR GI2
6B3 TF CC GI2
6B4 TR CC GI2
6B5 TF CC GI2
6B6 TR CC GI2
6B7 TF GI2
6B8 TR GI2
6K5 TF GI2 consi
6K6 TR GI2 consi
6W5 TF GI1 consi
6W6 TR GI1 consi
701 GR phys.inv.: whse
702 GI phys.inv.: whse
703 GR phys.inv: QI
704 GI phys.inv: QI
707 GR phys.inv.:blocked
708 GI phys.inv.:blocked
711 GI InvDiff.:whouse
712 GR InvDiff.:wrhouse
713 GI InvDiff: QI
714 GR InvDiff: QI
715 GI InvDiff.:returns
716 GR InvDiff.:returns
717 GI InvDiff.: blocked
718 GR InvDiff.: blocked
721 SlsVal.rec.n.afftMgs
722 SlsVal.iss.n.afftMgs
731 SlsVal.rec. afftgMgs
732 SlsVal.iss. afftgMgs
801 GR adv. inv. + tax
802 RGR ad. inv. + tax
803 GR AI ICMS/IPI
804 RGR AI ICMS/IPI
805 GR bl. AI w. tax
806 RGR bl. AI w. tax
811 GR TP dely w. tax
812 RGR TP dely w tax
815 GR B TP dely w. tax
816 RGR B TP dely w. tax
821 GR val. VS w. tax
822 RGR val. VS w. tax
825 GR B val. VS w. tax
826 RGR B val. VS w. tax
833 Reval. iss. w. tax
834 R reval. iss. w tax
835 Reval. rec. w. tax
836 R reval. rec. w tax
841 GR RTP
842 RGR RTP
843 GR RTP w. tax
844 RGR RTP w. tax
861 GR TF SD/MM
862 GI TF SD/MM
863 GI TF SD/MM return
864 GR TF SD/MM return
901 GI internal c.center
922 RE return to vendor

Create Report of Good Receipt Partial from PO

2009-07-24T01:44:00.000-07:00

few days ago i have functional spec to create Report of GR partial from PO.
Now i'll share it in this blog...may it useful..
i took from table ekbe and ekpo with movement type 101 or 102...

*&---------------------------------------------------------------------*
*& Report ZALTEST
*&
*&---------------------------------------------------------------------*
*&
*&
*&---------------------------------------------------------------------*

REPORT zaltest NO STANDARD PAGE HEADING LINE-SIZE 208.

TABLES : ekpo,
ekbe.

DATA: BEGIN OF t1 OCCURS 0,
ebeln(11),
ebelp(11) ,

budat TYPE budat,
bpmng TYPE bpmng,
bwart type bwart,
menge TYPE ekpo-menge,
matnr TYPE matnr,
txz01 TYPE txz01,
meins TYPE meins,
afnam TYPE afnam,
bedat TYPE ekko-bedat,
wemng TYPE wemng,
ameng TYPE ameng,
corek type ameng,
END OF t1,

corection like ekpo-menge,
temp1 type i,
temp2 type i,
qtygr type i value 0,
GRQTY type i ,
ponumber(10),
poitem(10).

SELECTION-SCREEN BEGIN OF block b1 with frame title text-001.
select-OPTIONS:
so_ebeln for ekpo-ebeln.
SELECTION-SCREEN END OF block b1.

START-OF-SELECTION.

SELECT ebeln ebelp budat bpmng bwart
FROM ekbe
INTO table t1
where ebeln in so_ebeln and ( bwart = 101 or bwart = 102 ).

LOOP AT t1.
SELECT SINGLE bedat
FROM ekko
INTO t1-bedat
WHERE ebeln = t1-ebeln .
MODIFY t1.
ENDLOOP.

LOOP AT t1.
SELECT SINGLE wemng
FROM eket
INTO t1-wemng
WHERE ebeln = t1-ebeln and ebelp = t1-ebelp .
MODIFY t1.
ENDLOOP.

LOOP AT t1.

SELECT single menge matnr txz01 meins afnam
FROM ekpo
INTO (t1-menge, t1-matnr, t1-txz01, t1-meins, t1-afnam)
WHERE ebeln = t1-ebeln and ebelp = t1-ebelp .

MODIFY t1.

ENDLOOP.

END-OF-SELECTION.

*read table t1 index 1.
qtygr = 0.

LOOP AT t1.

corection = t1-menge - t1-wemng.
temp1 = t1-bpmng.
if t1-bwart = 102.
temp2 = t1-menge - temp1.
elseif t1-bwart = 101.
temp2 = t1-menge - temp1.
endif.

t1-corek = corection.
if sy-tabix > 1.
at new ebelp.
qtygr = 0.
endat.

endif.

if qtygr = 0.
t1-ameng = temp2.
else.
if t1-bwart = 102.
t1-ameng = qtygr + temp1.
else.
t1-ameng = qtygr - temp1.
endif.
endif.

qtygr = t1-ameng.

* WRITE t1-ameng UNIT t1-meins.
* write t1-wemng to qtygr unit t1-meins.
* corection = t1-menge - t1-wemng.
MODIFY t1.
ENDLOOP.

LOOP AT t1.
* write: / t1-ebeln , sy-vline.
if t1-ameng > 0.
* if t1-wemng >= 0.

if sy-tabix = 1.
poitem = t1-ebelp.
elseif sy-tabix > 1.
poitem = ''.
at new ebelp.
poitem = t1-ebelp.
endat.

endif.

if ponumber = t1-ebeln.

elseif ponumber <> t1-ebeln.
ponumber = t1-ebeln.
uline.
WRITE: ' PO Number :' color 5, ponumber color 5.

elseif ponumber = ''.

ponumber = t1-ebeln.
uline.
WRITE: ' PO Number :' color 5, ponumber color 5.

endif.

ULINE.

WRITE: / sy-vline, poitem, sy-vline.
WRITE: t1-matnr, sy-vline.
WRITE: t1-txz01, sy-vline.
WRITE: t1-bedat, sy-vline.
WRITE: t1-budat, sy-vline.
WRITE: t1-bwart, sy-vline.
WRITE: t1-menge, sy-vline .
WRITE: t1-bpmng, sy-vline.
WRITE: t1-ameng, sy-vline.
WRITE: t1-corek, sy-vline.
WRITE: t1-afnam, sy-vline.

endif.

ENDLOOP.
uline.

TOP-OF-PAGE.
ULINE.
WRITE:
/ sy-vline,
(11) 'Item No' color 2, sy-vline,
(18) 'Material No' color 2, sy-vline,
(40) 'Description' color 2, sy-vline,
(10) 'PO Date' color 2, sy-vline,
(10) 'GR Date' color 2, sy-vline,
(3) 'Mov' color 2, sy-vline,
(17) 'Quantity PO' color 2, sy-vline,
(17) 'Quantity GR' color 2, sy-vline,
(17) 'Selisih' color 2, sy-vline,
(17) 'Correction' color 2, sy-vline,
(12) 'Requistioner' color 2, sy-vline.
uline.

Payroll Report

2009-07-02T19:55:00.000-07:00

this article will describe Payroll Process in SAP for Your Organization in several Country

Payroll Argentina (PY-AR)
Payroll Australia (PY-AU) Payroll Austria (PY-AT)
Payroll Basics (PY-XX-BS) Payroll Belgium (PY-BE)
Payroll Brazil (PY-BR)
Payroll Canada(PY-CA)
Payroll Denmark (PY-DK)
Payroll France (PY-FR)
Payroll Germany (PY-DE)
Payroll Great Britain (PY-GB)
Payroll Hong Kong (PY-HK)
Payroll in a Background Operation
Payroll Indonesia (PY-ID)
Payroll in the SAP System
Payroll Ireland (PY-IE)
Payroll Italy (PY-IT)
Payroll Japan (PY-JP)
Payroll Journal (Report RPCLJNx0;HxxCLJN0)
Payroll Malaysia (PY-MY)
Payroll Mexico (PY-MX)
Payroll New Zealand (PY-NZ)
Payroll Philippines (PY-PH)
Payroll Portugal (PY-PT)
Payroll Singapore (PY-SG)
Payroll Spain (PY-ES)
Payroll Sweden (PY-SE)
Payroll Taiwan (PY-TW)
Payroll Thailand (PY-TH)
Payroll United States (PY-US)
Payroll Venezuela (PY-VE)
Payroll South Africa (PY-ZA)
Payroll Switzerland (PY-CH)

LINQ To SAP

2009-07-01T20:31:00.000-07:00

I always looking for how to connect SAP from other interface...such as .Net With SAP Connector...a few days ago i found new method... LINQ To SAP...this article will explain how to connect SAP from LINQ..

in order to use this method, we need to install the .NET library ERPConnect.net from Theobald Software

Once the selection is made, the LINQ to SAP Designer will show up the Function Module dialog box with all data, properties and parameter definitions of the selected module BAPI_EQUI_GETLIST. The user can now change the naming of the auto-generated method as well as all used parameters.

the connection settings as well as other flags can be defined in the properties window of the LINQ to SAP Designer. The following code shows how to use the context class SAPContext:

class Program
{
static void Main()
{
SAPContext dc = new SAPContext("TESTUSER", "XYZ");

SAPContext.PlantTable plants = new SAPContext.PlantTable();
SAPContext.PlantStructure ps = plants.Rows.Add();
ps.SIGN = "I";
ps.OPTION = "EQ";
ps.LOW = "3000";

SAPContext.EquipmentTable equipList = dc.GetEquipmentList(plants);
}
}

After adding the SAP Table object from the toolbox in Visual Studio and finding the table with the search dialog, the Table dialog will show up:

The following code shows how to query the table T001W using the context class:

class Program
{
static void Main()
{
SAPContext dc = new SAPContext("TESTUSER", "XYZ");
dc.Log = Console.Out;

var res = from p in dc.T001WList
where p.WERKS == "3000"
select p;

foreach (var item in res)
Console.WriteLine(item.NAME1);
}
}

The code sample below shows how to add a partial class (file SAPContext.cs) which adds a new custom method GetEquipmentListForMainPlant to extend the context class generated by the LINQ to SAP designer. This new method calls internally the auto-generated method GetEquipmentList with a pre-defined parameter value. The C# compiler will internally merge the auto-generated LINQtoERP1.Designer.cs with the SAPContext.cs source file.

using System;

namespace LINQtoSAP
{
partial class SAPContext
{
public EquipmentTable GetEquipmentListForMainPlant()
{
SAPContext.PlantTable plants = new SAPContext.PlantTable();
SAPContext.PlantStructure ps = plants.Rows.Add();
ps.SIGN = "I";
ps.OPTION = "EQ";
ps.LOW = "3000";

return GetEquipmentList(plants);
}
}
}

SAP Java Connector

2009-06-30T01:43:00.000-07:00

Besides Visual Studio .NET 2003, Visual Studio 2005 and PHP, Java Can connect also to SAP. In Java, the SAP JAVA Connector (JCO) supports both inbound (JAVA Call Abap) and outbound (ABAP calls Java) calls in desktop and server applications.
this is a sample when JAVA Connect to SAP with call 2 BAPis

import com.sap.mw.jco.*;
JCO.Client mConnection;
try {
mConnection =
JCO.createClient(”400″, // SAP client
“c3026902″, // userid
“********”, // password
“EN”, // language
“iwdf5020″, // host name
“00″); // system number
mConnection.connect();
}
catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
}

“A Client object is created via a call to createClient(). You can use a specific application server (as in the above code) or a server group (load balancing).” REFER the JCO Javadoc for the overloaded createClient() method for the latter possibility.

“The Client class’s connect () method tries to log on to SAP. If that fails for any reason, an exception is thrown. If the call succeeds, we can now stay connected for as long as we like. When we are done, we can call disconnect () to explicitly log off.”

SAP Abap Performance Tunning

2009-06-30T01:37:00.000-07:00

Need for performance tuningABAP is the universal language in the World of SAP programming and the focus is also on getting a team of efficient programmers as early as possible in each and every part of the project, both for handing over the technical specifications to them and also for asking them to toss out the ABAP programs within the “given deadlines” as well.

The key focus of assembling an efficient program takes a back seat since this force has a greater pressure of schedules along with deliveries to accomplish successful outcomes. Also an proficient ABAP program is one which brings the wanted output to the user in a finite time according to the complexity involved in the program, rather than hearing the comment “I put the program to run, have my lunch and come back to check the results”.

A performance optimized ABAP program saves the time of the end user, thus increasing the productivity of the user, and in turn keeps the user as well as the management happy leaving aside the hyperbole. SAP ABAP performing tuning tips and tricks are used for making the ABAP programs efficient in doing their work. This tuning tips and tricks also assume that the reader is well versed in each and every concepts and syntax of ABAP programming.

SAP Implementation Benefits SAP solutions embrace an extensive range of business domains, such as Financial Accounting Controlling, Asset Management, Project System, Human Resources, Quality Management, Production Planning and Sales and Distribution. We also help for small and mid-size firms that achieve profits and have significant advantages through SAP investment via our expertise in presenting SAP solutions.

Some SAP implementation benefits include:

* Gradual declination in the total cost of ownership
* Accomplishment of faster return on investment
* Imparting flexibility in business processes
* Inspection of entire business processes
* Integration, collaboration, planning, execution, and coordination of the complete supply chain network
* Achievement of consistent as well as apparent business insights
* Develop employee productivity
* Creation of a quality work environment
* Achievement of operational excellence and growth
* Exploitation of additional solutions with ease

Both SAP Implementation and SAP training are worth investing since it takes into account regarding the benefits it offers. Our partnership with leading application vendors permits us to convey competitive SAP advantages to our enterprising customers. Enterprises get in touch for the processing of SAP Consulting and SAP Upgrade solutions. We also offer its consulting, implementation and training services for the upcoming Microsoft Dynamic Business Solutions.

ABAP interview questions and answers

2009-06-29T18:54:00.000-07:00

Thanks to the reader who sent in this question set:

What is an ABAP data dictionary?- ABAP 4 data dictionary describes the logical structures of the objects used in application development and shows how they are mapped to the underlying relational database in tables/views.
What are domains and data element?- Domains:Domain is the central object for describing the technical characteristics of an attribute of an business objects. It describes the value range of the field. Data Element: It is used to describe the semantic definition of the table fields like description the field. Data element describes how a field can be displayed to end-user.
What is foreign key relationship?- A relationship which can be defined between tables and must be explicitly defined at field level. Foreign keys are used to ensure the consistency of data. Data entered should be checked against existing data to ensure that there are now contradiction. While defining foreign key relationship cardinality has to be specified. Cardinality mentions how many dependent records or how referenced records are possible.

Describe data classes.- Master data: It is the data which is seldomly changed. Transaction data: It is the data which is often changed. Organization data: It is a customizing data which is entered in the system when the system is configured and is then rarely changed. System data:It is the data which R/3 system needs for itself.
What are indexes?- Indexes are described as a copy of a database table reduced to specific fields. This data exists in sorted form. This sorting form ease fast access to the field of the tables. In order that other fields are also read, a pointer to the associated record of the actual table are included in the index. Yhe indexes are activated along with the table and are created automatically with it in the database.
Difference between transparent tables and pooled tables.- Transparent tables: Transparent tables in the dictionary has a one-to-one relation with the table in database. Its structure corresponds to single database field. Table in the database has the same name as in the dictionary. Transparent table holds application data. Pooled tables. Pooled tables in the dictionary has a many-to-one relation with the table in database. Table in the database has the different name as in the dictionary. Pooled table are stored in table pool at the database level.
What is an ABAP/4 Query?- ABAP/4 Query is a powerful tool to generate simple reports without any coding. ABAP/4 Query can generate the following 3 simple reports: Basic List: It is the simple reports. Statistics: Reports with statistical functions like Average, Percentages. Ranked Lists: For analytical reports. - For creating a ABAP/4 Query, programmer has to create user group and a functional group. Functional group can be created using with or without logical database table. Finally, assign user group to functional group. Finally, create a query on the functional group generated.

What is BDC programming?- Transferring of large/external/legacy data into SAP system using Batch Input programming. Batch input is a automatic procedure referred to as BDC(Batch Data Communications).The central component of the transfer is a queue file which receives the data vie a batch input programs and groups associated data into “sessions”.

What are the functional modules used in sequence in BDC?- These are the 3 functional modules which are used in a sequence to perform a data transfer successfully using BDC programming: BDC_OPEN_GROUP - Parameters like Name of the client, sessions and user name are specified in this functional modules. BDC_INSERT - It is used to insert the data for one transaction into a session. BDC_CLOSE_GROUP - This is used to close the batch input session.

What are internal tables?- Internal tables are a standard data type object which exists only during the runtime of the program. They are used to perform table calculations on subsets of database tables and for re-organising the contents of database tables according to users need.

What is ITS? What are the merits of ITS?- ITS is a Internet Transaction Server. ITS forms an interface between HTTP server and R/3 system, which converts screen provided data by the R/3 system into HTML documents and vice-versa. Merits of ITS: A complete web transaction can be developed and tested in R/3 system. All transaction components, including those used by the ITS outside the R/3 system at runtime, can be stored in the R/3 system. The advantage of automatic language processing in the R/3 system can be utilized to language-dependent HTML documents at runtime.

What is DynPro?- DynPro is a Dynamic Programming which is a combination of screen and the associated flow logic Screen is also called as DynPro.

What are screen painter and menu painter?- Screen painter: Screen painter is a tool to design and maintain screen and its elements. It allows user to create GUI screens for the transactions. Attributes, layout, filed attributes and flow logic are the elements of Screen painter. Menu painter: Menu painter is a tool to design the interface components. Status, menu bars, menu lists, F-key settings, functions and titles are the components of Menu painters. Screen painter and menu painter both are the graphical interface of an ABAP/4 applications.

What are the components of SAP scripts?- SAP scripts is a word processing tool of SAP which has the following components: Standard text. It is like a standard normal documents. Layout sets. - Layout set consists of the following components: Windows and pages, Paragraph formats, Character formats. Creating forms in the R/3 system. Every layout set consists of Header, paragraph, and character string. ABAP/4 program.

What is ALV programming in ABAP? When is this grid used in ABAP?- ALV is Application List viewer. Sap provides a set of ALV (ABAP LIST VIEWER) function modules which can be put into use to embellish the output of a report. This set of ALV functions is used to enhance the readability and functionality of any report output. Cases arise in sap when the output of a report contains columns extending more than 255 characters in length. In such cases, this set of ALV functions can help choose selected columns and arrange the different columns from a report output and also save different variants for report display. This is a very efficient tool for dynamically sorting and arranging the columns from a report output. The report output can contain up to 90 columns in the display with the wide array of display options.

What are the events in ABAP/4 language?- Initialization, At selection-screen, Start-of-selection, end-of-selection, top-of-page, end-of-page, At line-selection, At user-command, At PF, Get, At New, At LAST, AT END, AT FIRST.

What is CTS and what do you know about it?- The Change and Transport System (CTS) is a tool that helps you to organize development projects in the ABAP Workbench and in Customizing, and then transport the changes between the SAP Systems and clients in your system landscape. This documentation provides you with an overview of how to manage changes with the CTS and essential information on setting up your system and client landscape and deciding on a transport strategy. Read and follow this documentation when planning your development project.

What are logical databases? What are the advantages/ dis-advantages of logical databases?- To read data from a database tables we use logical database. A logical database provides read-only access to a group of related tables to an ABAP/4 program. Advantages: i)check functions which check that user input is complete, correct,and plausible. ii)Meaningful data selection. iii)central authorization checks for database accesses. iv)good read access performance while retaining the hierarchical data view determined by the application logic. dis advantages: i)If you donot specify a logical database in the program attributes,the GET events never occur. ii)There is no ENDGET command,so the code block associated with an event ends with the next event statement (such as another GET or an END-OF-SELECTION).

What is a batch input session?- BATCH INPUT SESSION is an intermediate step between internal table and database table. Data along with the action is stored in session ie data for screen fields, to which screen it is passed, program name behind it, and how next screen is processed.

How to upload data using CATT ?- These are the steps to be followed to Upload data through CATT: Creation of the CATT test case & recording the sample data input. Download of the source file template. Modification of the source file. Upload of the data from the source file.

What is Smart Forms?- Smart Forms allows you to create forms using a graphical design tool with robust functionality, color, and more. Additionally, all new forms developed at SAP will be created with the new Smart Form solution.

How can I make a differentiation between dependent and independent data?- Client dependent or independent transfer requirements include client specific or cross client objects in the change requests. Workbench objects like SAPscripts are client specific, some entries in customizing are client independent. If you display the object list for one change request, and then for each object the object attributes, you will find the flag client specific. If one object in the task list has this flag on, then that transport will be client dependent.

What is the difference between macro and subroutine?- Macros can only be used in the program the are defined in and only after the definition are expanded at compilation / generation. Subroutines (FORM) can be called from both the program the are defined in and other programs . A MACRO is more or less an abbreviation for some lines of code that are used more than once or twice. A FORM is a local subroutine (which can be called external). A FUNCTION is (more or less) a subroutine that is called external. Since debugging a MACRO is not really possible, prevent the use of them (I’ve never used them, but seen them in action). If the subroutine is used only local (called internal) use a FORM. If the subroutine is called external (used by more than one program) use a FUNCTION.

Selection screen's Validation (ABAP)

2009-06-25T01:13:00.001-07:00

************************************************************************
* AT SELECTION SCREEN *
************************************************************************
at selection-screen.
perform validate_selection_screen using g_returkode.
if g_returkode = c_returkode_error.

exit.
endif.

*&---------------------------------------------------------------------*
*& Form validate_selection_screen
*&---------------------------------------------------------------------*
* Validation of selection screen
*----------------------------------------------------------------------*
* -->P_G_RETURKODE text
*----------------------------------------------------------------------*
form validate_selection_screen using p_returkode.

if s_framd > 12 or s_framd <> 12 or s_tilmd < p_returkode =" c_returkode_error."> s_tilmd.
message e997.
p_returkode = c_returkode_error.
exit.
endif.

if s_fraaar < p_returkode =" c_returkode_error.">

(ABAP) Create ALV Grid control

2009-06-25T01:04:00.000-07:00

*&---------------------------------------------------------------------*
*& Report Z_ALV_SKELETON
*&
*& Author: Sheila Titchener
*& Date: December 2006
*&---------------------------------------------------------------------*
*& ALV Grid control skeleton using OO Methods
*&
*&---------------------------------------------------------------------*
REPORT Z_ALV_SKELETON .
*&---------------------------------------------------------------------*
*&---------------------------------------------------------------------*
* internal tables
DATA: i_tab TYPE TABLE OF zchangereq,
w_tab TYPE zchangereq.
* display field details
DATA: w_field_cat_wa TYPE lvc_s_fcat. " Field Catalog work area
*
*&---------------------------------------------------------------------*
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-020.
*&---------------------------------------------------------------------*
PARAMETERS: p_outs RADIOBUTTON GROUP g1,
p_comp RADIOBUTTON GROUP g1.
SELECTION-SCREEN END OF BLOCK b1.
*&---------------------------------------------------------------------*
*MACROS
*&---------------------------------------------------------------------*
DEFINE add_field.
* &1 = FIELDNAME &2 = HEADING &3 = Key field flag
clear w_field_cat_wa.
w_field_cat_wa-fieldname = &1.
* lw_field_cat_wa-ref_table = p_ref_table.
* lw_field_cat_wa-inttype = p_inttype.
* lw_field_cat_wa-decimals = p_decimals.
* lw_field_cat_wa-coltext = p_coltext.
* lw_field_cat_wa-seltext = p_seltext.
* lw_field_cat_wa-do_sum = p_do_sum.
* lw_field_cat_wa-no_out = p_no_out.
* lw_field_cat_wa-col_pos = p_col_pos.
* lw_field_cat_wa-reptext = p_coltext.
* lw_field_cat_wa-colddictxt = p_colddictxt.
w_field_cat_wa-scrtext_m = &2.
w_field_cat_wa-key = &3.
append w_field_cat_wa to i_field_cat.
END-OF-DEFINITION.
*-----------------------------------------------------------------------
* ALV specific Declarations...........................................
*-----------------------------------------------------------------------

* ALV specific Internal table declarations.............................
DATA: i_field_cat TYPE lvc_t_fcat, " Field catalogue
i_alv_sort TYPE lvc_t_sort. " Sort table

* ALV variables........................................................
DATA: w_alv_layout TYPE lvc_s_layo, " ALV Layout
w_alv_save TYPE c, " ALV save
w_alv_variant TYPE disvariant. " ALV Variant

* ALV Class definitions................................................
*-----------------------------------------------------------------------
CLASS lcl_event_handler DEFINITION.
*-----------------------------------------------------------------------

PUBLIC SECTION.
METHODS: handle_double_click
FOR EVENT double_click OF cl_gui_alv_grid
IMPORTING e_row e_column.
METHODS: handle_hotspot
FOR EVENT hotspot_click OF cl_gui_alv_grid
IMPORTING e_row_id e_column_id.
ENDCLASS. " CLASS LCL_EVENT_HANDLER DEF..

* ALV Class implementation............................................
* In the Event of a Double Click drill down to the corresponding CHANGE REQUEST
*-----------------------------------------------------------------------
CLASS lcl_event_handler IMPLEMENTATION.
*-----------------------------------------------------------------------

METHOD handle_double_click.
DATA: l_tab LIKE LINE OF i_tab.
CHECK e_row-rowtype(1) EQ space.
READ TABLE i_tab INDEX e_row-index INTO l_tab.
SET PARAMETER ID 'ZTY' FIELD l_tab-ztype.
SET PARAMETER ID 'ZCR' FIELD l_tab-zcref.
CALL TRANSACTION 'ZCRT' AND SKIP FIRST SCREEN.
ENDMETHOD. " HANDLE_DOUBLE_CLICK

* not working yet - hotspot seems to stay in the gui!!
METHOD handle_hotspot.
DATA: l_tab LIKE LINE OF i_tab.
CHECK e_row_id-rowtype(1) EQ space.
READ TABLE i_tab INDEX e_row_id-index INTO l_tab.
SET PARAMETER ID 'ZTY' FIELD l_tab-ztype.
SET PARAMETER ID 'ZCR' FIELD l_tab-zcref.
CALL TRANSACTION 'ZCRT' AND SKIP FIRST SCREEN.
ENDMETHOD. " HANDLE_DOUBLE_CLICK

ENDCLASS. " CLASS LCL_EVENT_HANDLER IMPL...

* ALV Grid Control definitions........................................
DATA:
* ALV Grid Control itself
o_grid TYPE REF TO cl_gui_alv_grid,

* Container to hold the ALV Grid Control
o_custom_container TYPE REF TO cl_gui_custom_container,

* Event handler (defined in the class above)
o_event_handler TYPE REF TO lcl_event_handler.

*&----------------------------------------------------------------------*
INITIALIZATION.
*&----------------------------------------------------------------------*
PERFORM create_field_catalogue. " Create ALV Field Catalog

*&---------------------------------------------------------------------*
START-OF-SELECTION.
*&---------------------------------------------------------------------*
* Outstanding requests
IF p_outs = 'X'.
SELECT * FROM zchangereq
INTO TABLE i_tab
WHERE zstatus < zstatus =" 99." p_outs =" 'X'." container_name =" 'SC_GRID'," i_parent =" o_custom_container.">free.
SET SCREEN 0.
ENDCASE.

ENDMODULE. " USER_COMMAND_0100 INPUT

*----------------------------------------------------------------------*
* FORM DEFINE_ALV_LAYOUT *
*----------------------------------------------------------------------*
* This subroutine is used to Define the ALV layout. *
*----------------------------------------------------------------------*
FORM define_alv_layout .

w_alv_layout-numc_total = 'X'. " Numc total line
w_alv_layout-cwidth_opt = 'X'. " Optimal column width
w_alv_layout-detailinit = 'X'. " Show values that are initial in
" detail list.
w_alv_layout-sel_mode = 'A'. " Column selection mode
w_alv_layout-no_merging = 'X'. " No merging while sorting columns
w_alv_layout-keyhot = 'X'.
ENDFORM. " DEFINE_ALV_LAYOUT
*----------------------------------------------------------------------*
* FORM SAVE_ALV_LAYOUT_OPTIONS *
*----------------------------------------------------------------------*
* This subroutine is used to Save the ALV layout options. *
*----------------------------------------------------------------------*
FORM save_alv_layout_options.

* See the ALV grid control documentation for full list of options

w_alv_save = 'A'.
w_alv_variant-report = sy-repid.

ENDFORM. " SAVE_ALV_LAYOUT_OPTIONS
*----------------------------------------------------------------------*
* FORM CALL_ALV_GRID *
*----------------------------------------------------------------------*
* This subroutine is used to call ALV Grid control for processing. *
*----------------------------------------------------------------------*
FORM call_alv_grid.

CALL METHOD o_grid->set_table_for_first_display
EXPORTING
is_layout = w_alv_layout
i_save = w_alv_save
is_variant = w_alv_variant
CHANGING
it_outtab = i_tab[]
it_sort = i_alv_sort
it_fieldcatalog = i_field_cat.
* Link used Events and Event Handler Methods
CREATE OBJECT o_event_handler.

* Set handler o_event_handler->handle_top_of_page for o_grid.
SET HANDLER o_event_handler->handle_double_click FOR o_grid.

ENDFORM. " CALL_ALV_GRID
*&---------------------------------------------------------------------*
*& Form create_field_catalogue
*&---------------------------------------------------------------------*
* set up field catalogue
*&---------------------------------------------------------------------*
FORM create_field_catalogue .
* Fieldname Heading Key?
*eg add_field 'ZTYPE' 'Type' 'X'.

ENDFORM. " create_field_catalogue

Debugging of SAPClient Proxies

2009-06-23T03:35:00.000-07:00

Debugging of SAPClient Proxies

With the SAP .NET Connector you can debug from your C# proxy directly into the SAP

function module by setting the ABAP_DEBUG flag in the connection string. The best way to do

this is to set the AbapDebug and Trace flags on the SAPLogonDestination object.

Debugging through to the SAP system is useful when you are getting unexpected results

back from the SAP system. To use the ABAP_DEBUG option you must have installed SAPGUI

on your developer workstation. You cannot use the integrated ABAP debug option with web

applications because they run under another Windows context that is invisible to the

interactive user. For that reason it is often useful to test your proxy first against a Windows

form or Console application in case integrated debugging is required.

It is often useful to run the SAP RFC function directly in the SAP system using transaction

SE37. It is easier to isolate the problem once you are sure that input values are valid. In

addition, you can use the SAP function module documentation. The SAP data dictionary,

which is integrated in the function editor, also gives you information on valid input values.

In the SAP system, there are automatic formatting functions that are not available in the

connector, for example to add leading zeroes to a customer or invoice number. If the function

is working in the SAP system but not in your proxy, it could be that the SAP system has

applied one of these automatic formatting routines but you did not.

To see what values the SAP function module is using, proceed as follows:

1. Execute transaction SE37.

2. Enter the function name and select Single test (F8).

3. Enter valid parameters and select Debugging (Ctrl F7).

4. Use Single Step (F5) to examine the code execution and variable values in the SAP

function debugger window, part of the Abap/4 developer workbench.

You can turn on tracing in the SAP system by setting the environment variable CPIC_TRACE

and RFC_TRACE. For more information on RFC tracing, refer to SAP Note 65325.

CPIC_TRACE writes out detailed trace files to the application directory so it is

not advisable to leave tracing on any longer than you need it.

You can do advanced tracing within the SAP system, for example from transaction code

SM50 and by examining the work process trace files (for example, dev_w0 in the SAP work

directory).

We recommend developers to use the SAP .NET Connector exception classes in their code

to determine why an error has occurred and to use as a starting point for debugging.

TRFC applications can be monitored from the TRFC monitor (transaction SM58). QRFC

applications can be monitored from QRFC monitor (transaction SMQ2).

Coding Recommendations for RFC Exceptions

2009-06-23T03:30:00.000-07:00

SAPClient Exceptions

Errors in the .NET Connector are thrown as .NET exceptions. An exception is the preferred

method to handle errors because exceptions are harder to ignore than are return codes. They

also provide you detailed information to create more robust applications.

The SAP .NET Connector has the following exception classes:

• RfcCommunicationException

• RfcLogonException

• RfcSystemException

• RfcAbapException

• RfcException

• RfcMarshalException

Coding Recommendations for RFC Exceptions

We recommend you to have at least two catch blocks. The first catch statement is for SAP

exceptions (specific) and the second for others (generic), for example errors from the runtime

or other resources.

We recommend you to close the proxy connection in the finally programming block.

SAP .NET Connector closes connections eventually. However, to achieve better

performance, we recommend you to close the connection in the finally clause of your

class. We also recommend that you close any external resources such as open files or

database connections here as well.

Instead of providing a status of the SAP RFC connection, we recommend that you simply

invoke the method and deal with the exception. The SAP .NET Connector will maintain the

status of the connection internally.

The Proxy.Connection.Open() method causes an RFC ping. This allows

you to see if the system is up. Subsequent Proxy.Connection.open()

methods will be ignored until there is a Connection.Close().

Example

try

{

// Call methods here

proxy.Connection.Open();

proxy.Rfc_Function_Search(txtRFC.Text,"EN", ref tblRFC);

}

catch (RfcCommunicationException ex)

{

MessageBox.Show(ex.ToString());

return;

}

catch (RfcLogonException ex)

{

MessageBox.Show(ex.ToString());

return;

}

catch (RfcAbapException ex)

{

switch (ex.AbapException)

{

case (SAPProxy1.No_Function_Found):

MessageBox.Show("no function found");

break;

case(SAPProxy1.Nothing_Specified):

MessageBox.Show("Nothing specified");

break;

default:

MessageBox.Show("Some unknown abap error occurred");

break;

} //switch

}

catch (Exception ex)

{

MessageBox.Show(ex.ToString());

return;

}

finally {proxy.Connection.Close();}

Creating an ASP .NET Web Application Using the SAP .NET Connector

2009-06-23T03:19:00.000-07:00

The following example shows how to create a .NET project using Microsoft Visual Studio

.NET. In the example, a client application reads and displays customer data from an SAP

System using a search value and then displays it in a data grid.

The example uses the function module RFC_CUSTOMER_GET, which requires that customer

data exist in the target SAP System, for example, in IDES. Although it is possible to rename

all development objects and generated proxy classes, default names are used in this

example.

Procedure

1. Open Microsoft Visual Studio .NET.

2. Create a new C# Web form project:

Choose New → New Project → Visual C# Projects → ASP .NET Web Application.

You can also create a project in any other common programming language

for .NET, for example, in Visual Basic .NET. In this case, you must add the

SAP .NET proxy classes as a separate project in the Microsoft Visual Studio

.NET solution.

3. Rename the form Webform1.aspx to Default.aspx.

4. Add Web controls to your Web form.

In our example, we add a TextBox, a Button and a DataGrid control.

5. Add proxy classes to connect the Web applications to your SAP server.

a. In the Solution Explorer, right-click on your project.

b. Choose Add → Add new item.

c. Select Web Project Items → SAP Connector Class and choose Open.

The SAP .NET Connector Wizard opens.

d. Decide from where you want to generate the proxy classes.

You can create proxies from:

− Web Services Description Language (WSDL) files that originate in an SAP

interface repository (IFR)

− An SAP server

− Standard WSDL files

e. Select the client proxy object type and select beautify names option.

f. Select the Remote Function Modules (RFM) you want to use in your proxy object.

You can use search filters to look for the Remote Function Modules. In the example,

enter the search argument RFC_CUST* in Name-Filter and select

RFC_CUSTOMER_GET.

g. Add the modules to your proxy object and choose Next.

The proxy classes for the referenced table and structure types are automatically

created and added to the project.

6. Build the solution with Build → Build Solution.

7. Create an SAPLogin page to support user name and password authentication

a. In the Solution Explorer, right-click on your project.

b. Choose Add → Add New item.

c. Select Web Project Items → SAP Login Form

Leave the name as SAPLogin1.aspx.

8. Set the system connection information in the destination object of the SAPLogin1.aspx

page:

a. In the Solution Explorer window find the item SAPLogin1.aspx and double-click on

it to bring it up in the designer.

b. Look for the component destination1 on the bottom of the form.

c. Click on the destination component and set the properties for connecting to your SAP

system (for example AppServerHost and SystemNumber). The other properties

like client, Password and username will be set from the login page.

9. Databind the data grid to BRFCKNA1Table:

BRFCKNA1Table is the parameter of RFC_CUSTOMER_GET that contains the

list of customers.

a. Select SAP Table Wizard from the SAP proxy toolbox and Drag&Drop it to your

working area. In the dialog box, select BRFCKNA1Table.

b. Select the data grid, and under Properties change DataSource to BRFCKNA1Table

using the drop down list.

c. Customize the list of columns displayed on the data grid by modifying the Columns

collection property.

10. On the default.aspx page, double-click the Button control you added earlier to create

an event handler for the control.

11. Add the connect code to your project:

a. Select Connect code from the SAP proxy toolbox.

b. Drag&Drop it in the source code of your event handler.

A fragment of sample code is then inserted. It connects to the SAP server using the

authorization settings from the Proxy Wizard. Normally, you must change these

settings.

The code should look something like this:

private void btnSearch_Click(object sender, System.EventArgs e)

{

// Declare parameters here

SAPProxy1 proxy = new SAPProxy1();

try

{

proxy.Connection =

SAP.Connector.SAPLoginProvider.GetSAPConnection(this);

// Call methods here

proxy.Rfc_Customer_Get("", txtCust.Text, ref brfcknA1Table1);

// Now update Data Bindings. On WinForms this will be automatic, on

// WebForms call the following line

this.DataBind();

}

catch(Exception ex)

{

// If SAPLoginProvider.GetSAPConnection(this) cannot get a connection,

// we might get an error.

// Normally this can be ignored as it will automatically will force a

// relogon.

}

12. Build and run the application.

The browser window opens and you are redirected to your SAPLogin1.aspx login

page.

13. Enter connection data (for example user, password and client).

If you select Save this login information will be stored as an encrypted cookie

on your computer and will provide an alternative single sign-on capability the

next time you wish to access the site. If you do not select Save, the login

information will still be saved in the ASP .NET session state but will be lost

once the browser is closed.

14. Enter a search argument, for example A* in the TextBox field and choose Search.

Your application connects to the SAP System and displays the requested data in the

DataGrid.

Programming Clients for BAPIs in VB using a session object.

2009-06-23T03:09:00.000-07:00

Programming Clients for BAPIs in VB

Use this procedure to program a VB client that calls BAPIs using a session object.

You must already have created and installed the proxy object and session object.

Create an instance of the session object.
Use the PutSessionInfo method to set the connection parameters for the object.
Create instances of the relevant business objects
Call the BAPIs that you need
Call the CommitWork() method of your session object.
Release the objects that you have used.

Example

The following program retrieves a list of sales orders from an R/3 System and displays them in a Visual Basic program. It should work with any IDES System with Release 4.0B or higher, as long as you change the logon data in the oSession.PutSessionInfo function.

The example is contained in a standard EXE project with a single form called Form1.

The component T20Saleslib is a DCOM proxy for the business object SalesOrder plus a corresponding session object.

The data grid control is called DataGrid1. The Get Sales Orders function is implemented in the routine cmdGet_Click, and the Exit function is implemented in the cmdExit_Click routine.

The Source Code

Private Sub cmdGet_Click()

Dim oSession As New T20salesLib.SalesorderSessionComponent

Dim oOrders As Object

Dim oOrderList As ADODB.Recordset

Dim oReturn As ADODB.Recordset

oSession.PutSessionInfo "T20 [PUBLIC]", "TESTUSER", "LETMEIN", "EN", _"800"

Set oOrders = oSession.CreateInstance("T20.SalesOrder.1")

oOrders.DimAs "BAPIGETLIST", "SALESORDERS", oOrderList

oOrders.DimAs "BAPIGETLIST", "RETURN", oReturn

Set oOrderList = oOrders.BapiGetList(CustomerNumber:="0000001000", _

SalesOrganization:="1000", SalesOrders:=oOrders)

Set DataGrid1.DataSource = oOrders

DataGrid1.Refresh

Set oOrders = Nothing

Set oSession = Nothing

End Sub

Private Sub cmdExit_Click()

Unload Form1

End Sub

Using SAP Connector For Microsoft Visual Studio 2005

2009-06-23T01:18:00.000-07:00

As we know SAP Connector only worked on .Net 2003. but in this article i'll describe how to connect SAP Connector with Microsoft Visual Studio 2005.

To implement this workaround, you need the following installations:

• Visual Studio 2003

• SAP Connector for .NET 2.0

• A connection and valid credentials for an SAP application server

• Visual Studio 2005

• Microsoft .NET Framework 2.0 (for runtime environment)

1. Start Visual Studio 2003.

2. Create a new Class Library project either in VB or C#.

3. Add a new SAP Connector Proxy item to the project.

4. Configure the application server as required. For more information, see the .NET Connector documentation integrated with the Visual Studio 2003 on-line help.

5. From Server Explorer, select and drag the relevant BAPIs onto the proxy designer.

6. Save and build the project.

7. Close Visual Studio 2003.

8. If Visual Studio 2005 is installed on a different machine from Visual Studio 2003, copy the compiled .dll file from the /bin subfolder of its project folder, and the SAP.Connector.DLL and SAP.Connector.Rfc.DLL files from the C:\Program Files\SAP\SAP .NET Connector 2.0 folder to that machine.

The exact location of the DLL files on the Visual Studio 2005 machine is not important, as you will be referencing them in your projects.

9. Start Visual Studio 2005 and open your application project.

10. Add references to the three .DLL files to your project using the Browse tab of the Add Reference dialog box.

11. Open the proxy reference in the Object Browser. All BAPIs that you have selected in your Visual Studio 2003 project, are available here. You can now write your custom code and consume the BAPIs, as before.

Selamat Mencoba...