Regarding using PARAMETERS:p_prefil TYPE rlgrap-filename.

Hi when
I use this parameter
PARAMETERS:p_prefil TYPE rlgrap-filename.
in order take the input from the user for filename when downloading to the Presentation server i get the conflict type error and the program goes to dump.
But if i use the same p_prefil as string type it works.Could anyone tell me the reason for this.

Hi..
To avoid this problem you have to declare a Separate variable.
PARAMETERS:p_prefil TYPE rlgrap-filename.
data : v_file type string.
START-OF-SELECTION.
MOVE P_PREFIL TO V_FILE.
call function 'GUI_DOWNLOAD'
exporting
FILENAME = V_FILE "This parameter accepts only STRING
This will work..
reward if Helpful.

Similar Messages

Parameter: p_file LIKE rlgrap-filename.

Hi I have given this in my code 'p_file LIKE rlgrap-filename.' and it showing that put your address in this bar and it will take you to required area. Now I want using p_file LIKE rlgrap-filename with browsing facility. How I will do that. Need info.
TYhanks...............

Hi,
 Try the following code.
tables: sdokpath.
parameters:
p_path(250) type c.
data:
w_path(250) type c,
w_size type i,
w_name type rlgrap-filename.
data:
t_contents like
 standard table
 of sdokpath.
data:
 t_contents1 like
 standard table
 of sdokpath.
data:
begin of fs_size,
 name like w_name,
 size type i,
end of fs_size.
data:
t_size like
standard table
 of fs_size.
at selection-screen on value-request for p_path.
call function 'WS_FILENAME_GET'
EXPORTING
DEF_FILENAME = ' '
DEF_PATH = W_PATH
MASK = ' '
MODE = ' '
TITLE = ' '
 importing
 filename = p_path
RC =
 exceptions
 inv_winsys = 1
 no_batch = 2
 selection_cancel = 3
 selection_error = 4
 others = 5
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
at selection-screen.
if p_path is initial.
message 'Enter the file path'(001) type 'E'.
endif.
end-of-selection.
call function 'WS_QUERY'
 exporting
ENVIRONMENT =
 FILENAME = W_PATH
 query = 'CD'
WINID =
 importing
 return = w_path
 exceptions
 inv_query = 1
 no_batch = 2
 frontend_error = 3
 others = 4
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
write:/ '-------CURRENT DIRECTORY IS -
write:/10 w_path.
write: /,/,/.
call function 'TMP_GUI_DIRECTORY_LIST_FILES'
 exporting
 directory = w_path
FILTER = '.'
IMPORTING
FILE_COUNT =
DIR_COUNT =
 tables
 file_table = t_contents
 dir_table = t_contents1
 exceptions
 cntl_error = 1
 others = 2
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
loop at t_contents into sdokpath.
 w_name = sdokpath.
 call function 'GUI_GET_FILE_INFO'
 exporting
 fname = w_name
 importing
FILE_VERSION =
FILE_DBGREL =
FILE_LANG =
 file_size = fs_size-size
EXCEPTIONS
 FILEINFO_ERROR = 1
 OTHERS = 2
 if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 endif.
 write:/ w_name,40 fs_size-size.
 fs_size-name = w_name.
 append fs_size to t_size.
endloop.
sort t_size by size descending.
read table t_size index 1 into fs_size.
skip 3.
write: fs_size-name,30 'is the file having maximum size of',
 70 fs_size-size.
regards,
kiran kumar k

Regarding using of LDB PNPCE in sap hr

Can some one please tell me how to disable some of the selection screen fields and blocks of LDB PNPCE selection-screen which are not used in my report selection-screen?
Thanks,
Phanisreedhar.L

*: Report: ZP_POSTCODE :
*: Author: www.SAPDev.co.uk :
*: Date : 2004 :
*: Description: Displays report of employees by postcode area, :
*: includes current travelling allowances (i.e. parking :
*: permit or transport card etc..) :
*: Use: Help encourage the use of car sharing and public :
*: transport where appropriate. :
REPORT zp_postcode.
type-pools: slis. "ALV Declarations
NODES: pernr.
INFOTYPES: 0000, 0001, 0002, 0006, 0008, 0014, 0105, 0121.
SELECTION-SCREEN BEGIN OF BLOCK pcode WITH FRAME TITLE text-s01.
SELECT-OPTIONS: so_pcode FOR p0006-pstlz.
SELECTION-SCREEN END OF BLOCK pcode.
TYPES: BEGIN OF t_output,
pernr TYPE p0001-pernr, "personnel name
anredtxt TYPE t522t-atext, "title (based on p0002-anred)
fname TYPE p0002-vorna, "first name
lname TYPE p0002-nachn, "last name
orgtx TYPE t527x-orgtx, "dept
fte TYPE p0008-bsgrd, "fte
parking(20) TYPE c,
payslip TYPE t526-sachn, "payslip address
telno TYPE p0105-usrid_long, "tel number(p0105-usrty = 0020)
email TYPE p0105-usrid_long, "email (p0105-usrty = MAIL)
postcode type p0006-pstlz,
END OF t_output.
DATA: it_output TYPE STANDARD TABLE OF t_output INITIAL SIZE 0,
 wa_output TYPE t_output.
*ALV data declarations
data: fieldcatalog type slis_t_fieldcat_alv with header line,
 gd_tab_group type slis_t_sp_group_alv,
 gd_layout type slis_layout_alv,
 gd_repid like sy-repid,
 gt_events type slis_t_event,
 gd_prntparams type slis_print_alv,
 gd_count(6) type n,
 gd_outtext(70) type c,
 gd_lines type i.
*START-OF-SELECTION.
START-OF-SELECTION.
clear: gd_count.
GET pernr.
Infotype 0121 is used to store multiple contracts for personnel.
Field p0121-hpern contains the personnel number for the main contract.
PROVIDE * from p0121 between pn-begda and pn-endda.
Check if main contract
 if p0121-pernr ne p0121-hpern.
 reject.
 endif.
ENDPROVIDE.
add 1 to gd_count.
concatenate 'Processing personnel data'(m10) gd_count into gd_outtext
 separated by ' '.
Display indicator for employee count
perform progress_indicator using gd_outtext.
Retrieve datd from infotypes
rp_provide_from_last p0000 space pn-begda pn-endda.
rp_provide_from_last p0001 space pn-begda pn-endda.
rp_provide_from_last p0002 space pn-begda pn-endda.
rp_provide_from_last p0006 space pn-begda pn-endda.
rp_provide_from_last p0008 space pn-begda pn-endda.
rp_provide_from_last p0014 space pn-begda pn-endda.
Check post code
CHECK p0006-pstlz IN so_pcode. "cp
Post code
wa_output-postcode = p0006-pstlz.
Personnel number
wa_output-pernr = pernr-pernr.
Personnel title
SELECT SINGLE atext
 FROM t522t
 INTO wa_output-anredtxt
 WHERE sprsl EQ sy-langu AND
 anred EQ p0002-anred.
First name
wa_output-fname = p0002-vorna.
Last name
wa_output-lname = p0002-nachn.
Organizational Unit text (dept)
SELECT SINGLE orgtx
 FROM t527x
 INTO wa_output-orgtx
 WHERE sprsl EQ sy-langu AND
 orgeh EQ p0001-orgeh AND
 endda GE sy-datum.
FTE
wa_output-fte = p0008-bsgrd.
Parking / travel deducted?
CASE p0014-lgart.
 WHEN '7180' OR '7181' OR '7182'.
 wa_output-parking = text-002.
 WHEN '7183'.
 wa_output-parking = text-001.
 WHEN '7171' OR '7172' or '7173' or '7174' or
 '7175' or '7176' or '7177' or '7178'.
 wa_output-parking = text-003.
ENDCASE.
Payslip Address
SELECT SINGLE sachn
 FROM t526
 INTO wa_output-payslip
 WHERE werks EQ p0001-werks AND
 sachx EQ p0001-sacha.
PROVIDE * from p0105 between pn-begda and pn-endda.
Telephone numbers
 if p0105-usrty = '0020'.
 wa_output-telno = p0105-usrid_long.
 endif.
Email address
 if p0105-usrty = 'MAIL'.
 wa_output-email = p0105-usrid_long.
 endif.
ENDPROVIDE.
append wa_output to it_output.
clear: wa_output.
*END-OF-SELECTION.
END-OF-SELECTION.
describe table it_output lines gd_lines.
if gd_lines gt 0.
perform build_fieldcatalog.
perform build_layout.
perform display_alv_report.
else.
message i003(zp) with 'No records found'.
endif.
*& Form PROGRESS_INDICATOR
 Displays progress indicator on SAP screen
form progress_indicator using p_text.
call function 'SAPGUI_PROGRESS_INDICATOR'
 exporting
 PERCENTAGE = 0
 text = p_text.
endform. " PROGRESS_INDICATOR
*& Form BUILD_FIELDCATALOG
 Build Fieldcatalog for ALV Report
form build_fieldcatalog.
fieldcatalog-fieldname = 'PERNR'.
fieldcatalog-seltext_m = 'Personnel No.'.
fieldcatalog-col_pos = 0.
fieldcatalog-outputlen = 10.
fieldcatalog-emphasize = 'X'.
fieldcatalog-key = 'X'.
fieldcatalog-do_sum = 'X'.
fieldcatalog-no_zero = 'X'.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'ANREDTXT'.
fieldcatalog-seltext_m = 'Title'.
fieldcatalog-col_pos = 1.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'FNAME'.
fieldcatalog-seltext_m = 'First Name'.
fieldcatalog-col_pos = 2.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'LNAME'.
fieldcatalog-seltext_m = 'Last Name'.
fieldcatalog-col_pos = 3.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'ORGTX'.
fieldcatalog-seltext_m = 'Department'.
fieldcatalog-col_pos = 4.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'FTE'.
fieldcatalog-seltext_m = 'FTE'.
fieldcatalog-col_pos = 5.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'PARKING'.
fieldcatalog-seltext_m = 'Parking/Metrocard'.
fieldcatalog-col_pos = 6.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'PAYSLIP'.
fieldcatalog-seltext_m = 'Payslip Add.'.
fieldcatalog-col_pos = 7.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'TELNO'.
fieldcatalog-seltext_m = 'Telephone'.
fieldcatalog-col_pos = 8.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'EMAIL'.
fieldcatalog-seltext_m = 'E-mail'.
fieldcatalog-col_pos = 9.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
fieldcatalog-fieldname = 'POSTCODE'.
fieldcatalog-seltext_m = 'Post code'.
fieldcatalog-col_pos = 10.
append fieldcatalog to fieldcatalog.
clear fieldcatalog.
endform. " BUILD_FIELDCATALOG
*& Form BUILD_LAYOUT
 Build layout for ALV grid report
form build_layout.
gd_layout-no_input = 'X'.
gd_layout-colwidth_optimize = 'X'.
gd_layout-totals_text = 'Totals'(201).
gd_layout-zebra = 'X'.
endform. " BUILD_LAYOUT
*& Form DISPLAY_ALV_REPORT
 Display report using ALV grid
form display_alv_report.
gd_repid = sy-repid.
call function 'REUSE_ALV_GRID_DISPLAY'
 exporting
 i_callback_program = gd_repid
 is_layout = gd_layout
 it_fieldcat = fieldcatalog[]
 i_save = 'X'
 tables
 t_outtab = it_output
 exceptions
 program_error = 1
 others = 2.
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. " DISPLAY_ALV_REPORT
The following program allows you to retrieve all the individuall sickpay values for a given period and person.This data is then exported to memory using the memory id entered on the selection screen. This thereforeallows you to submit this program from another program and then process the data within the calling programby importing the data from memory. Click here for example .
Report: ZSXP_ABSENCE_DATA ** ** Author: www.SAPdev.co.uk ** ** Date : 12.02.2003 ** ** Description: Retrieve maternaty/Sickness Absence data* ************************************************************************REPORT ZSXP_ABSENCE_DATA LINE-SIZE 100 NO STANDARD PAGE HEADING MESSAGE-ID 5g.TABLES: t554s, pernr, pcl1, pcl2.INCLUDE rpclst00.INCLUDE rpc2rx09. "Payroll results datadefns-Intl.INCLUDE rpc2rxx0. "Payroll results datadefns-Intl.INCLUDE rpc2rgg0. "Payroll results datadefns-GBINCLUDE rpcfdcg0. "Payroll results datadefns-GBINCLUDE rpcdatg0.INCLUDE rpc2cd00. "Cluster Directory defns.INCLUDE rpc2ps00. "Cluster: Generierte SchematasINCLUDE rpc2pt00.INCLUDE rpcfdc10.INCLUDE rpcfdc00.INCLUDE rpppxd00.INCLUDE rpppxd10.INCLUDE rpcfvp09.INCLUDE rpcfvpg0.INCLUDE rpppxm00.INFOTYPES: 0001, "Organisational assignment 0002, "Personal Data 0003, "Payroll Status 0088, "SMP 2001, "Absences 0086. "SSP/SMP ExlclusionsDATA: ssp_weeks TYPE p DECIMALS 2 VALUE 0.DATA: ssp_total TYPE p DECIMALS 2 VALUE 0, total_val TYPE p DECIMALS 2 VALUE 0, smp_weeks TYPE p DECIMALS 2 VALUE 0, smp_value TYPE p DECIMALS 2 VALUE 0, gross LIKE pc207-betrg, dis_gross TYPE p DECIMALS 2 VALUE 0.DATA: gd_begda(10) TYPE c, gd_endda(10) TYPE c.DATA: ld_orgtxt LIKE t527x-orgtx.DATA: name(30).DATA: BEGIN OF itab OCCURS 0, pernr LIKE p0002-pernr, perid LIKE p0002-perid, name LIKE name, END OF itab.TYPES: BEGIN OF t_report, pernr TYPE pernr-pernr, "8 name TYPE name, "30 awart TYPE p2001-awart, "4 begda TYPE p2001-begda, "10 endda TYPE p2001-endda, "10 wkspaid TYPE p DECIMALS 2, "10 amtpaid TYPE p DECIMALS 2, "10 END OF t_report.DATA: it_report TYPE STANDARD TABLE OF t_report INITIAL SIZE 0, wa_report TYPE t_report.DATA: moabw LIKE t001p-moabw.DATA: printheader TYPE i VALUE 1, gd_success TYPE i. NCALE declarationsTYPES : BEGIN OF pfra0_pcale, annee(4) TYPE c. INCLUDE STRUCTURE pcint.TYPES : END OF pfra0_pcale.TYPES : pfra0_tab_pcale TYPE pfra0_pcale OCCURS 0.DATA: it_ncale TYPE STANDARD TABLE OF pcnat INITIAL SIZE 0, wa_ncale TYPE pcnat, it_pcale TYPE pfra0_tab_pcale, pcale TYPE pfra0_tab_pcale.* SMP/SSP absence datadata begin of it_msa occurs 0. include structure pc27j.data end of it_msa.parameters: p_memid type char30.************************************************************************STAR-OF-SELECTIONSTART-OF-SELECTION.gd_begda = pn-begda.gd_endda = pn-endda.gd_begda6(2) = '01'.gd_endda6(2) = '01'.refresh: it_msa.clear: it_msa.GET pernr.* PERFORM IMPORT_PC USING GD_SUCCESs. PERFORM get_rgdir. while gd_begda le gd_endda. PERFORM get_new_rg USING gd_begda. CALL FUNCTION 'CALCULATE_DATE' EXPORTING* DAYS = '0' MONTHS = '1' START_DATE = gd_begda IMPORTING RESULT_DATE = gd_begda. endwhile. msa[] = it_msa[]. EXPORT msa TO MEMORY ID p_memid.&---------------------------------------------------------------------& Form GET_RGDIR&-------------------------------------------------------------------FORM get_rgdir. rp-init-buffer. CLEAR rgdir. REFRESH rgdir. MOVE pernr-pernr(8) TO cd-key-pernr. rp-imp-c2-cd. IF rp-imp-cd-subrc = 0. "rgdir success SORT rgdir BY seqnr ASCENDING. CLEAR rgdir. ENDIF.ENDFORM.-----------------------------------------------------------------** FORM get_new_rg **-----------------------------------------------------------------** ........ **-------------------------------------------------------------------** > search_date **-----------------------------------------------------------------FORM get_new_rg USING search_date. DATA: rg_day TYPE d, rgbeg TYPE d, rgend TYPE d. MOVE: search_date TO rg_day. CLEAR: msa. LOOP AT rgdir WHERE void NE 'V'. MOVE: rgdir-fpbeg TO rgbeg, rgdir-fpend TO rgend. IF ( rgbeg <= rg_day ) AND ( rgend >= rg_day ) AND rgdir-srtza = 'A'. "Must be periods actual set of results EXIT. ENDIF. ENDLOOP. UNPACK rgdir-seqnr TO rx-key-seqno. MOVE pernr-pernr(8) TO rx-key-pernr(8). rp-imp-c2-rg. append lines of msa to it_msa. IF rp-imp-rg-subrc <> 0. rg fail ELSE.* rg success ENDIF.ENDFORM.Text elements------------------------------------------------------* 001 Sickness History for SSP 1* 002 Employee Name.* 003 National Insurance Number.* 004 Payroll Number.* 005 Sickness Start Date* 006 Sickness End Date* 007 Number of weeks paid* 008 system-error:* 009 No SSP / SMP record found* 010 Absence type* 011 No. weeks paid* 012 Amount* 013 Organisation Unit.* T01 Sickness Absence typesSelection texts--------------------------------------------------------* SO_SAP SAP Att./absence types* SO_SMP SMP Att./absence types* SO_SPP SPP Att./absence types* SO_SSP SSP Att./absence types
Uses Logical database 'PNP'(entered in program attributes) to retrieve various personnel data and downloadit to an excel / tab delimited file.
.......................................................................: Report: ZDOWNEMPDATA :: :: Author: www.SAPDev.co.uk :: :: Date : 2004 :: :: Description: Downloads employee data to TAB delimited flat files :: ::.....................................................................:.......................................................................: Report: ZDOWNEMPDATA :: :: Author: www.SAPDev.co.uk :: :: Date : 2004 :: :: Description: Downloads employee data to TAB delimited flat files :: ::.....................................................................:REPORT zdownempdata .INFOTYPES: 0000, 0001, 0007, 0008, 0121, 0615.NODES: pernr.TABLES: t001p.TYPES: BEGIN OF t_employee,* INCLUDE STRUCTURE hrms_biw_io_occupancy. begda TYPE begda, endda TYPE endda, pernr TYPE pernr_d, rfpnr TYPE rfpnr, bukrs TYPE bukrs, werks TYPE persa, btrtl TYPE btrtl, persg TYPE persg, persk TYPE persk, orgeh TYPE orgeh, stell TYPE stell, plans TYPE plans, kokrs TYPE mast_coar, kostl TYPE mast_cctr, abkrs TYPE abkrs, molga TYPE molga, trfar TYPE trfar, trfgb TYPE trfgb, trfkz TYPE trfkz, trfgr TYPE trfgr, trfst TYPE trfst, bsgrd TYPE bsgrd, ansal TYPE ansal_15, ancur TYPE ancur, empct TYPE empct, stat2 TYPE stat2, ncsdate TYPE hiredate, sltyp TYPE p_sltyp, slreg TYPE p_slreg, slgrp TYPE p_slgrp, sllev TYPE p_sllvl, ansvh TYPE ansvh, vdsk1 TYPE vdsk1, sname TYPE smnam, END OF t_employee.DATA: it_employee TYPE STANDARD TABLE OF t_employee INITIAL SIZE 0, wa_employee TYPE t_employee.TYPES: BEGIN OF t_emptexts,* INCLUDE STRUCTURE hrms_bw_txt_employee. DATEFROM TYPE RSDATEFROM, DATETO TYPE RSDATETO, PERNR TYPE PERSNO, TXTMD TYPE EMNAM, END OF t_emptexts.DATA: it_emptexts TYPE STANDARD TABLE OF t_emptexts INITIAL SIZE 0, wa_emptexts TYPE t_emptexts.TYPES: BEGIN OF t_contract,* INCLUDE STRUCTURE pa0615. pernr TYPE p0615-pernr, begda TYPE p0615-begda, endda TYPE p0615-endda, aedtm TYPE p0615-aedtm, ctype TYPE p0615-ctype, cbeg TYPE p0615-cbeg, cend TYPE p0615-cend, END OF t_contract.DATA: it_contract TYPE STANDARD TABLE OF t_contract INITIAL SIZE 0, wa_contract TYPE t_contract.DATA: it_tabemp TYPE filetable, gd_subrcemp TYPE i, it_tabempt TYPE filetable, gd_subrcempt TYPE i, it_tabcont TYPE filetable, gd_subrccont TYPE i.DATA: gd_downfile TYPE string.SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME TITLE text-001.PARAMETERS: p_emp LIKE rlgrap-filename, p_empt LIKE rlgrap-filename, p_cont LIKE rlgrap-filename.SELECTION-SCREEN END OF BLOCK block1.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_emp. REFRESH: it_tabemp. CALL METHOD cl_gui_frontend_services=>file_open_dialog EXPORTING window_title = 'Select File' default_filename = '.xls' initial_directory = 'C:\' multiselection = ' ' "No multiple selection CHANGING file_table = it_tabemp rc = gd_subrcemp. LOOP AT it_tabemp INTO p_emp. ENDLOOP.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_empt. REFRESH: it_tabemp. CALL METHOD cl_gui_frontend_services=>file_open_dialog EXPORTING window_title = 'Select File' default_filename = '.xls' initial_directory = 'C:\' multiselection = ' ' "No multiple selection CHANGING file_table = it_tabempt rc = gd_subrcempt. LOOP AT it_tabempt INTO p_empt. ENDLOOP.***********************************************************************at selection-screenAT SELECTION-SCREEN ON VALUE-REQUEST FOR p_cont. REFRESH: it_tabcont. CALL METHOD cl_gui_frontend_services=>file_open_dialog EXPORTING window_title = 'Select File' default_filename = '.xls' initial_directory = 'C:\' multiselection = ' ' "No multiple selection CHANGING file_table = it_tabcont rc = gd_subrccont. LOOP AT it_tabcont INTO p_cont. ENDLOOP.************************************************************************START-OF-SELECTION.START-OF-SELECTION.GET pernr. Selecting the latest infotype record rp_provide_from_last p0000 space pn-begda pn-endda. rp_provide_from_last p0001 space pn-begda pn-endda. rp_provide_from_last p0007 space pn-begda pn-endda. rp_provide_from_last p0008 space pn-begda pn-endda. rp_provide_from_last p0121 space pn-begda pn-endda. rp_provide_from_last p0615 space pn-begda pn-endda. MOVE-CORRESPONDING p0001 TO wa_employee. wa_employee-rfpnr = p0121-rfp01. "????? MOVE-CORRESPONDING p0007 TO wa_employee. MOVE-CORRESPONDING p0008 TO wa_employee. MOVE-CORRESPONDING p0000 TO wa_employee. SELECT SINGLE molga FROM t001p INTO wa_employee-molga WHERE werks EQ p0001-werks AND btrtl EQ p0001-btrtl. SELECT SINGLE trfkz FROM t503 INTO wa_employee-trfkz WHERE persg EQ p0001-persg AND persk EQ p0001-persk. CALL FUNCTION 'HR_ENTRY_DATE' EXPORTING persnr = pernr-pernr* RCLAS =* BEGDA = '18000101'* ENDDA = '99991231'* VARKY = IMPORTING entrydate = wa_employee-ncsdate* TABLES* ENTRY_DATES = EXCEPTIONS ENTRY_DATE_NOT_FOUND = 1 PERNR_NOT_ASSIGNED = 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.* append employee data APPEND wa_employee TO it_employee. CLEAR: wa_employee. wa_emptexts-datefrom = p0001-begda. wa_emptexts-dateto = p0001-endda. wa_emptexts-pernr = p0001-pernr. wa_emptexts-txtmd = p0001-ename.* append employee texts data APPEND wa_emptexts TO it_emptexts. CLEAR: wa_emptexts. MOVE-CORRESPONDING p0615 TO wa_contract.* append employee contract data APPEND wa_contract TO it_contract. CLEAR: wa_contract.************************************************************************END-OF-SELECTION.END-OF-SELECTION. download employee data IF NOT p_emp IS INITIAL. gd_downfile = p_emp. CALL FUNCTION 'GUI_DOWNLOAD' EXPORTING filename = gd_downfile filetype = 'ASC' write_field_separator = 'X' TABLES data_tab = it_employee. IF sy-subrc EQ 0. WRITE:/ 'Employee file downloaded to', gd_downfile. ELSE. WRITE:/ 'There was an error downloading Employee file to', gd_downfile. ENDIF. ENDIF.* download employee texts data IF NOT p_empt IS INITIAL. gd_downfile = p_empt. CALL FUNCTION 'GUI_DOWNLOAD' EXPORTING filename = gd_downfile filetype = 'ASC' write_field_separator = 'X' TABLES data_tab = it_emptexts. IF sy-subrc EQ 0. WRITE:/ 'Employee text file downloaded to', gd_downfile. ELSE. WRITE:/ 'There was an error downloading Employee text file to', gd_downfile. ENDIF. ENDIF.* download contract data IF NOT p_cont IS INITIAL. gd_downfile = p_cont. CALL FUNCTION 'GUI_DOWNLOAD' EXPORTING filename = gd_downfile filetype = 'ASC' write_field_separator = 'X' TABLES data_tab = it_contract. IF sy-subrc EQ 0. WRITE:/ 'Employee contract file downloaded to', gd_downfile. ELSE. WRITE:/ 'There was an error downloading Employee contract file to', gd_downfile. ENDIF. ENDIF.

How to use parameterized statements with labSQL?

Hi everybody,
I have a big problem with labSQL. Every statement or query I have to use in my program works correctly, but I have a performance problem when writing my data to the database. The problem is the handling of the SQL statements by the DB. The solution will be the use of parameterized statements with labSQL.
The manual for NI Labview Database Connectivity Toolkit provides such information, but there are large differences to labSQL, and I don't get the clue. Is anybody able and would be so kind to help me? If someone has an example for using parameterized SQL statements with labSQL or the ADO methods for such stuff, please be so kind to share it with me.
Thank you for reading all of this
Best regards,
Matthias

Thank you very much for your help. I already had set up the correct SQL statement and created the parameters but got errors when executing the command object. After some tries I found that neither the SQL statement nor the parameters were the source of the error, as I had expected first.
The problem was that I was sending the wrong data type to the execute method of the command object. It expected some variant input for the parameters. I send an array of strings, which caused an error. I casted that array to variant with the same result. But a single string to variant worked well (with only one parameter in the SQL statement). The easy solution was to cast all strings to variants, and then build an array out of them. The execute method worked with that. Now the transaction is 4 times faster than before
Thanks again!
Edit:
If someone is interested in some example VI, please let me know. I should have some time next week to build one.
Message Edited by manicnobody on 02-26-2009 10:19 AM

Business Transaction Profile - Error when using Z-Transaction Type

Dear Experts,
we are using SAP CRM 7.0 (Support Level 0007 - SAPKU70007). I have created a Z-Business Transaction Profile Z_IC_SERVICE.
SAP Help says:
Enter the transaction type to be used as a default in your scenario in the IC WebClient. For example, choose the transaction type 0010 (Interaction Record) if an interaction record is to be created automatically. The system creates this interaction record automatically after the interaction has started (for example, after accepting a call). During this, the activity clipboard in the interaction record is filled with the relevant data.
So when I am using the transaction type 0010 (Interaction Record) in my Business Transaction Profile all is OK that means I can search for accounts and I can confirm them to go on with the process.
BUT: When I entering here a Z Transaction Type (Z000) the systems shows the errors:
- Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event InteractionStarted.
- Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event BPConfirmed.
Then I have made a copy of the transaction type 0010 (Name of copy: Z010) and tried to use it in my Business Transaction Profile the system says:
Customizing settings missing. Assign partner functions to Z010
Anybody know what to do and where to avoid errors? Note 1346892 is obsolete in this case because we already have the highest Support Package Level.
Best Regards
Oliver

Hi yes you were right. In the case of both transaction type I have corrected the customizing parameters in
SPRO -> Customer Relationship Management -> Interaction Center WebClient -> Business Transaction -> Assign Partner Functions to Business Transactions
In the case of Transaction Type Z010 I had Z-Partner Functions and and that leaded to the errors:
- Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event InteractionStarted.
- Error occurred in class CL_ICCMP_CUCOIREC_IMPL, event BPConfirmed.
In case of the Transaction TYPE Z000 I forgot to assign the Partner Functions that is why this error appeared:
Customizing settings missing. Assign partner functions to Z010
Thread Closed

Purpose of using parameters defined below in FM 'REUSE_ALV_GRID_DISPLAY'

Hi,
Iwant to know the purpose of using parameters defined below in FM ''REUSE_ALV_GRID_DISPLAY' :---
EXPORTING.
I_INTERFACE_CHECK =
I_BYPASSING_BUFFER =
I_BUFFER_ACTIVE =
IS_SEL_HIDE =
IS_PRINT =
IS_REPREP_ID =
I_SCREEN_START_COLUMN =
I_SCREEN_START_LINE =
I_SCREEN_END_COLUMN =
I_SCREEN_END_LINE =
IT_ALV_GRAPHICS =
IT_HYPERLINK =
IT_ADD_FIELDCAT =
IT_EXCEPT_QINFO =
I_HTML_HEIGHT_TOP =
I_HTML_HEIGHT_END =
IMPORTING
E_EXIT_CAUSED_BY_CALLER =
ES_EXIT_CAUSED_BY_USER =
small example codes are most welcome.
Regards,
Rahul

Go To SE37 AND Give the function module name and press Button 'FUnction Moudule Documentation' There you will get the documentation for each parameter
* I_INTERFACE_CHECK =
Interface consistency check log output
Description
So that the performance of the list output is not reduced due to interface consistency checks, these checks are performed in a special call mode.
If this parameter is set to 'X', interface consistency is checked when the function module is called and an error log is displayed.
You should only set this parameter for testing purposes during the development process (for example, for debugging).
You can also perform the interface check on the result list by entering function code &SOS.
THIS PARAMETER IS CURRENTLY NOT SUPPORTED IN FULLSCREEN MODE! As a workaround, go to the print preview from within the list and enter function code &SOS there.
Default
SPACE
*IS_SEL_HIDE = 
Description
This parameter is currently not supported!
Only relevant if layout parameter
LAYOUT-GET_SELINFOS of IMPORTING structure IS_LAYOUT is set.
Complex type for modifying information displayed on the selection dialog box:
mode: 'R' = Only entries passed in internal table
 IS_SEL_HIDE-T_ENTRIES are output on
 the dialog box. Selection information
 obtained by the list tool by reading the
 selection screen again (only if the report
 is called with selection screen) are
 replaced by the entries passed.
 'S' = The selection information obtained by the
 list tool by reading the selection screen
 of the calling report again, are modified
 by the entries of table
 IS_SEL_HIDE-T_ENTRIES.
t_entries: Table with selection information
t_entries-mode: 'A' = Display selection information of the current
 table row on the information dialog box.
 'D' = Do not display selection information of the
 the Select option or of parameter SELNAME
 on the dialog box.
t_entries-selname: (required only if t_entries-mode = 'D')
 name of Select option or parameter
The following table fields are only required if t_entries-mode = 'A'. They contain the selection information to be added.
t_entries-field: DDIC field name of the field for which selection
 information is to be displayed
t_entries-table: DDIC table name of t_entries-field.
t_entries-stext: Field description on the information dialog box.
 If t_entries-field and t_entries-table were
 filled, this text is taken from the DDIC.
t_entries-valuf: Selection condition from-value (external format)
t_entries-valut: Selection condition to-value (external format)
t_entries-sign0: (I)nclusive (E)xclusive
t_entries-optio: All values of the option field of the Select
 option are allowed.
The remaining fields are used internally and are irrelevant to the caller.
* IS_PRINT =
Print information
Description
Control parameters relevant for printing
PRINT
Value range: SPACE, 'X'
'X' = Print list and do not display it on the screen. Further settings can be made on the print parameter screen.
NO_PRINT_SELINFOS
Value range: SPACE, 'X'
'X' = Do not print existing selection information (see also LAYOUT-GET_SELINFOS)
NO_COVERPAGE
Value range: SPACE, 'X'
'X' = Print selection information and list status, if available, on a separate page.
NO_NEW_PAGE
Value range: SPACE, 'X'
Internal use only
RESERVE_LINES
Value range: 0, n
n = Number of lines output in the footer by the user during printout at END_OF_PAGE in the corresponding callback event.
NO_PRINT_LISTINFOS
Value range: SPACE, 'X'
'X' = Do not print list status (sort information, subtotals information and filter information).
NO_CHANGE_PRINT_PARAMS
Value range: SPACE, 'X'
SPACE = (default) The output format (number of columns) is dynamically adjusted depending on the list width (255 at most).
'X' = The current print parameters are always used. If the list is wider, the output width is not adjusted dynamically.

Regarding changing parameters

hi experts,
cud u plz send me your own small coding which let me about the functionality of changing parameters.....thnx in advance....
plz dnt copy and paste it from net.......

Hi,
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter. TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
REPORT demo_mod_tech_example_2 .
DATA: num TYPE i VALUE 5,
fac TYPE i VALUE 0.
PERFORM fact USING num CHANGING fac.
WRITE: / 'Factorial of', num, 'is', fac. "#EC NOTEXT
FORM fact
USING value(f_num) TYPE i
CHANGING f_fact TYPE i.
f_fact = 1.
WHILE f_num GE 1.
f_fact = f_fact * f_num.
f_num = f_num - 1.
ENDWHILE.
ENDFORM.
Regards,
Priyanka.

Error while Driving a view using parameters from other view

Hi,
I have created a report with streamlist and Barchart view.Driving option is used in streamlist to drive the barchart. The driving works well untill i dont use any filters in the Streamlist.Once i use parameters in streamlist , the driving works only for the default values set.When Second set of values are chosed for the parameter,the values are displayed correctly , but once they are selected for driving,the current values are replaced by the results of the default parameter settings.
I have already done the tutorials for driving and it worked well untill i use filters in the main view,from where the driving is done.
I would really appreciate if someone could give a solution for this problem.
Regards,
Lathika

Hi,
Login as i.e. sys as sysdba. Standard password is change_on_install.
Or you can login in using user that has CREATE VIEW WITH ADMIN OPTION and then grant CREATE VIEW privilege to user to want.
Peter D.

Can i use technical system type 'third party' for r3 system in idoc2file sc

Hi,
i am doing a sample out bound scenario (idoc 2 file), distributing idoc from sap system to csv file (in same network). in this can i use thchnical system type 'third party' for R3 system. will the scenario work properly or not.
And some times some of the business systems in SLD are not visible in ID, when assigning business system in ID.can any one tell reason for this.
can any one suggest me,........ Thanks in advance & would be appreciated.
Regards
Rajesh

Hi,
 can i use thchnical system type 'third party' for R3 system. will the scenario work properly or not.
--- No u can't use this...Ur technical system must be "WebAS ABAP" only. For file system you use 3rd party system. means ur technical system like follows.
sender
R/3 -- WebAs ABAP
Receiver
File - 3 rd pary system
And some times some of the business systems in SLD are not visible in ID, when assigning business system in ID.can any one tell reason for this.
Click "Clear SLD cache" repeatly for some time in ID, it will come.
regards,
Ansar.

How to use the customer types in customer master data

how to use the customer types in customer master data?
menu path is Extras -> account group info -> customer types

hi,
This is an option given to you to choose (if you need to) the way you perceive this customer.Here you get options including ompetitors,Salespartner, prospect,
default sp ,consumer.
See it helps you to differentiate between prospect(which you may use for quotation or inquiry purpose)Sales partner and the competetor.
I hope this clarifies your quiery.Reward points if so.
Thanking you,
Best regards,
R.Srinivasan

Using RB00 condition type for Price Adjustment

Hi,
I have to do a price adjustment due to some rounding issues in the pricing of my sales order.(Using standard Pricing Procedure RVAA01). I am thinking of using manual condition type RB00 at Item level that can accept both positive and negative values depending on the situation.
If the calculated value>expected value then the user will enter negative RB00 value manually and
if the calculated value<expected value then the user will enter positive RB00 value manually.
The account key is however different in standard Pricing procedure for RB00 and it is ERS and for standard Base Price (PR00) it is ERL.
So, my question is that does that make any difference if I maintain condition records in VKOA for RB00 same as PR00?

Hi
If you are looking for rounding then you round the decimals by not maintaining any decimals.But if it is a price adjustment then your approach is correct
If it is VK11 then there is no need to maintain condition record for RB00 as it is a manual condition type at item level
If you are talking to maintain revenue account determination VKOA then you have to maintain as whenever you give discount then it will hit some G/L account .So you should assign a G/L account also
Regards
Srinath

Need links for creation varaibles using different processing types....

Hi All,
can you provide me links for creation of variables using diiferent processing types...
it would be grateful if you peovide any links which covers all most all the topics in bi reporting....
Thanks All.

Hi,
Pl refer to following link as well
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b0b25093-b548-2e10-0cba-fcac7890585f?QuickLink=index&overridelayout=true
Customer exit for text variables
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d343131313235%7d
http://help.sap.com/saphelp_nw04/helpdata/en/61/579b3c494d8e15e10000000a114084/content.htm
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313535373530%7d
Thanks and regards
Kiran

Is there any downside to using a reference type library if I use Time Capsule and will do file management only from within Aperture?

Have done a lot of reading to get prepared to convert to Aperture 3 and have this question regarding setting up my library type.
I'm not a professional -just a heavy user hobbyist.
It appears that the major factors in using reference style is to backup the images with Time Capsule and always do moves or deletes from within the Aperture application.
If my architecture matters here's what I have that may be involved in photo management and editing:
iMac (latest 27" high power version with lots of memory)
Internal 2TB HD where the library is stored
External (FireWire) 2TB HD where the images are stored
External (FireWire) 6TB HD backup drive
In the future an iPad for remote work on images (when/if available) and a Mac laptop (for same remote use)
I see major downside issues to letting the library manage my files - such as inaccessibility (or awkward accessibility) to the images for other programs, and performance issues when the library gets large (thousands of images or 100+ gb in size)
The chief complaints I've seen regarding using a reference mode is the broken link issues created if file management is done outside of Aperture (adds, deletes, moves of files) and the inability to use the Vault function for backup.
One feature that I imagine I'd like to have is maximum integration with Final Cut Pro X and that's one area I haven't seen much on and would be interested to hear about if that integration is affected with the choice of managed vs referenced library types. (I like to produce film clips that are combinations of pics and video and want to be set up so that is done in the easiest fashion when working in FCP X)
I'm sure I've not seen all sides of this issue and would like to see some discussion around this question.
Thanks to everyone contributing!
Craig

Goody, Goody, you hit a few of my favorite subjects! Herewith some comments, with the usual caveats - true to the best of my knowledge and experience, others may have different results, YMMV, and I could be wrong.
I run Aperture on two machines:
-- 2007 Mac Pro with 2x2.66 GHz Xeon, 21 GB of RAM, a 5770 GPU, and multiple HD. I have about 11,000 images, taking up 150 GB. (Many are 100 MB TIFF, scanned slides)
-- 2006 Mac Book Pro with 1 2.0 GHz Core Duo, 2 GB of RAM and a 240 GB SSD.
Two very different machines.
-- Aperture Libraries are all the same - Managed or Referenced. If Managed, then the Master image files are inside the Package, if Referenced, they are outside, and you can have any combination you want. Managed is easier, but Referenced is not hard if you are the least bit careful.
-- While the sheer size of an Aperture Library is not a big issue, the location on disk of the different components can have a tremendous impact on performance.
-- Solid State Drives (SSD) read and write faster than regular Hard Disks (HD) and, what is more important, empty HD read and write much faster than full HD.
-- Aperture speed requires a combination of RAM, CPU, graphics processing unit (GPU) speed, and disk speed. The more RAM you have, the less paging you will see. With enough RAM, the next bottle neck is CPU (speed and cores) and GPU speed. But even then you will still have to fetch an image (longer if you pull the full resolution Master, read and rewrite the Version file, and update the Preview and Thumbs.
So what works?
-- RAM, RAM, and more RAM. 4 GB will work, but you will page a bit. 8 GB is much faster. On my old MacPro the sweet spot was about 16 GB of RAM.
-- Keep your Library on your fastest (usually internal) drive. Keep that disk as unloaded as possible. How do you keep it unloaded? Either buy BIG, 1 TB+ or move your Masters off onto another disk. The good news here is that as Master files are written only once and never rewritten, speed of this disk, as opposed to the disk that holds the Library, is not important. There is a one second pause as the Master is read into memory and, if you have enough RAM, that is it - the Master will never be paged out. If, on the other hand, you do not have enough RAM, and you do a lot of adjusting at full resolution, then the speed of the disk that holds your Masters will become very important due to paging.
-- I found that I picked up a tiny bit of speed by keeping the Masters on a dedicated disk. Thus, in your configuration, if you can dedicate that 2 TB FW HD to your Masters, you should see very nice performance.
Final notes on backups and archives:
-- One conventional wisdom is that you should make an archive copy of every image file before or as you load them into your system. (Aperture in this case.) This archive is then never touched or deleted.
-- An alternative approach is that you do not keep such an archive, but only the images that you have in your Aperture Library. And when you delete from the Library, you no longer keep a copy anywhere.
I do the following:
-- Card to Aperture. Card is then kept at least 24 hours until all of my backups have run. (I use three - Time Machine, Clone, and off site.)
-- I do not keep archive copies. If I decide to delete a file, my only recourse is to recover it from Time Machine during the six month cycle of my Time Machine backups. Thereafter, it is lost.
There are merits to both approaches.
Hope this is clear, correct, and responsive to your needs.
DiploStrat

What are Parameters? How are they differenet from Variables? Why can't we use variables for passing data from one sequnece to another? What is the advantage of using Parameters instead of Variables?

Hi All,
I am new to TestStand. Still in the process of learning it.
What are Parameters? How are they differenet from Variables? Why can't we use variables for passing data from one sequnece to another? What is the advantage of using Parameters instead of Variables?
Thanks in advance,
LaVIEWan
Solved!
Go to Solution.

Hi,
Using the Parameters is the correct method to pass data into and out of a sub sequence. You assign your data to be passed into or out of a Sequence when you are in the Edit Sequence Call dialog and in the Sequence Parameter list.
Regards
Ray Farmer

You cannot use this transaction type to post to this asset Message no. AA83

< MODERATOR: Message locked. Please post this message in the [Asset Accounting forum|SAP ERP Financials - Asset Accounting;. >
Hi,
I am settling credit values [-ve values] from WBS to Asset Under Constructions Assets during CJ88 period settlement run.
These assets belongs to Investment Measure. For few assets I am getting below error and
You cannot use this transaction type to post to this asset
Message no. AA834
Diagnosis
The transaction type entered belongs to transaction type group 15. According to the specifications for this transaction type group, posting with transactions types belonging to this group are only allowed in specific asset classes (for example, asset classes for assets under construction).
The asset to which you are posting belongs to class XXXXX (chart of depreciation XXXX). You cannot post to this class using the transaction type you have entered.
Procedure
Check the asset number entered. You may want to allow posting with this transaction type group for the asset class of the asset.
I know normally we do this way
During charging
Dr Exp A/c WBS name
Cr B.S A/c
During settlement
Cr Exp A/c WBS name
Dr AuC GL A/c
But we have situation that during settlement, we are doing reverse
ie., Cr AuC GL A/c
Dr Exp A/c WBS Name
These expenses are through POs and no downpayments. The below error taking me to down payment accounts config but we dont have down payment scenario, can any one advise, thanks
Regards,
Sridhar

Hi,
Please check the SAP note 1091728 for this.
Regards

Regarding using PARAMETERS:p_prefil TYPE rlgrap-filename.

Similar Messages

Maybe you are looking for