Rec doubt

hi folks,
I am facing a peculiar prob while uploading the receipt using bdc by calling the transaction mb01
....i shall explain a more ellabroately
i am trying to create a receipt for multi line purchase order i have created in mb01 when i try to do the same by directly using mb01 i m able to create the receipt but when i use the prog n then execute i m able create the receipt for first line item but when i do it again after receiving the secong line item it says
PU Ordered quantity exceeded.....i have compared the code its fine.....
i even tried to execute this using the same peice of code in 4.7 server its working fine im able to create receipt for first line item as well as the second .....when i do the same in 5.0 server i m able to recive only the first line item when i receive the second i get the said error ....i m unable to know the kind of error plz let me if u guys know.....
thanks,

Hi,
Its may be becoz of the configuration settings .Goto to spro to check the same . or ask the functional consultant abt the same.
(i had this peculair problem in call transaction PA30 giving unwanted errors .then after a long research i found that cofiguration settings was in made in such a way)

Similar Messages

Alternate Recon A/c

Hi
pls explain alternate recon a/c and where we need to assign in which t-code ans what is the purpose of it?
mallikarjuna

Hi
In this step, you define accounts in which the postings to a customer account are managed in the general ledger. The posting is automatically made to these accounts instead of to the normal reconciliation account.
Note
The specification is dependent on account type, special G/L indicator, chart of accounts and reconciliation account.
Activities
1. Specify the number of the alternative reconciliation account.
2. Make sure that the account is created.
D        Dbt Rec    Doubtful Receivables
E        Reserve    Reserve for bad debt
H        Securit    Security deposit
I        BR Vend    BR: Vendor Operation
P        PmntReq    Payment request
Z        Int.due    Interest receivable t-code OBXY
D        Disct      Discounts
G        Guaran.    Guarantee received
H        Securit    Security deposit
P        PmntReq    Payment request-T_code- OBXT
Please assign points

E-Rec 6.04 Doubts with transaction pa48.

Hi,
We are on E-Rec 604 with seperated standalone e-rec system.
When I run pa48 transaction y realized that I have two doubts.
First of them is that if there is a customizing table to change the action type wich propose for the two options, New hire and Internal movility.
I know that using the combo I can change if I need another action type, but I suppose that there must be one table to customize that so I can´t find it.
The other problem is that when I chosse a candidate for a New Hire in the secuence of infotipes in the action type 01 (New Hire) there is the 0006 infotipe in the secuence and in our client this infotipe should not be appear. When I go to see the infogroup that is used in this action type the infotype 0006 doesn´t in the list, so I imagine that there is any dynamic action which is the responsible of that... But I can´t find it... And we want to delete it...
Could someone guide me, please?.
Best Regards,
Esther

Hello Esther,
The action type defaulted in PA48 is always the first one from table T572F.
IT0006 is a pre-requisite infotype in E-Recruiting, so we send the address from the external candidate to HR and request it also if the internal candidates are then transported to E-Recruiting back.
Regards
Nicole

Doubts in installation of E-rec

Hi Expert,
I would lile to share my doubts with you. I have to install an environment to work on E-rec system.
For the same, i am going to install backend system(ECC 6.0 EHP 4) and on another side we will have
E-REC portal for this i will be installing SAP Netweawer 7.0 EHP1.
As i heard, for E-rec, TREX has to installed on another system and connected with backend.
Request you to throw some light with regards to E-Rec installation
in terms of backend, Portal and TREX.

Hi.
I think you should read installation guides before posting your question here (No Offense).
1) Install ECC 6.0 EHP4 with E-rec on 604.
2) Install EHP1 portal with E-rec business packages.
3) Install Trex and connect it with your portal/ECC 6.0 system.
Thanks
Sunny

E-Recruiting - Doubt about job for changes in HR system.

Hi,
We are on E-Rec 604 with seperated standlone e-rec system.
I did the initial transfer of the Org Management and employees data through PFAL from ECC to E-Recruit and all were ok.
Now we are planning the job for future changes.
The job in e-recruiting is ok, using RBDMIDOC and RBDAPP01.
But I have some doubts with the job in HR system. I think I have to use those steps in the job:
RBDMIDOC
RSEOUT00
RBDMOIND
RBDCPCLR
It´s true?.
And in this case, with those steps the new employees in HR system will be created as internal candidates in E-Recruiting without problems?.
Could somebody help me, please?.
Best Resgrads,
Esther

Dear Esther,
In HR system, you only need to schedule these reports to transfer HR data from change pointers :
RBDMIDOC to created idocs from change pointers
RSEOUT00 to send idocs to the target system
RHALESMD : is used to generate Idocs that have already been processed or failed when report RBDMIDOC was running so
still with change pointers unprocessed in table BDCPV
Hope it helps,
Kind Regards
Christine

Doubt in MOVE statement

what is the arrtibute value of this hex1 type .. in CL_ABAP_CHAR_UTILITIES.
hex1 TYPE x VALUE '0D',
my req is this value is in structure n
data: begin of itab_input
         c1(40) type c value 'hgfsdhfjsdf'.
         hex1 type x value '0D',
     end of itab_input.
data: begin of itab_output
         c3(42) type c
     end of itab_output.
MOVE ita_input TO itab_output.                         .
im doing unicode conversion.. this MOVE is gving error in unicode conversion
please explain how to do it..

Hi Atish..one more doubt same here..
types: begin of itab,
          a(5) type c,
          b(5) type dec,
end of itab.
types: begin of des ,
          rec(10),
        end of des.
gw_itab type itab.
ga_des type des.
move ga_des-red to gw_itab.
here i get error moveing this type as gw_itab contains dec fld..
if its c type it wont gv any error ..
how to solve this type error?

Doubt in ABAP OOP

CLASS SAMPLE DEFINITION.
PUBLIC SECTION.
DATA : PU_A TYPE I.
METHODS : CONSTRUCTOR,MM1,MM2.
PRIVATE SECTION.
DATA : PR_B TYPE I.
ENDCLASS.
CLASS SAMPLE IMPLEMENTATION.
METHOD CONSTRUCTOR.
ENDMETHOD.
METHOD MM1.
ENDMETHOD.
METHOD MM2.
ENDMETHOD.
ENDCLASS.
DATA : OBJ_SAMPLE TYPE REF TO SAMPLE.
CREATE OBJECT OBJ_SAMPLE.
In CREATE OBJECT OBJ_SAMPLE its giving err msg that statement could not be accessible.why id it so?.plz help

hi
copy paste my code and check. its very simple one that ur are looking for.
REPORT zaaclc_report.
* CLASS lcl_test_class DEFINITION
CLASS lcl_test_class DEFINITION.
PUBLIC SECTION.
 METHODS increment_counter.
 EVENTS break_statement EXPORTING value(count) TYPE i.
PRIVATE SECTION.
 DATA: num TYPE i,
 max TYPE i VALUE 5.
ENDCLASS. "lcl_test_class DEFINITION
* CLASS lcl_test_class IMPLEMENTATION
CLASS lcl_test_class IMPLEMENTATION.
METHOD increment_counter.
 num = num + 1.
 IF num EQ max.
 RAISE EVENT break_statement EXPORTING count = num.
 ENDIF.
 WRITE:/ num .
ENDMETHOD. "increment_counter
ENDCLASS. "lcl_test_class IMPLEMENTATION
* CLASS event_receiver DEFINITION
CLASS event_receiver DEFINITION.
PUBLIC SECTION.
 METHODS handler FOR EVENT break_statement OF lcl_test_class IMPORTING count.
 endclass.
* CLASS event_receiver IMPLEMENTATION
CLASS event_receiver IMPLEMENTATION.
METHOD handler.
* count = count + 10.
 WRITE :/ count.
 WRITE :/ 'Event Raised'.
 endmethod.
ENDCLASS. "event_receiver IMPLEMENTATION
DATA:obj TYPE REF TO lcl_test_class,
 rec TYPE REF TO event_receiver.
START-OF-SELECTION.
CREATE OBJECT: obj,rec.
set handler rec->handler for obj." for all instances.
DO 10 TIMES.
 CALL METHOD obj->increment_counter.
ENDDO.
 hope it clears ur doubt
regards
ravish
plz dont forget to reward points if helpful
Message was edited by:
 ravish goyal

Info Recs and Source List

Hi Experts
I want to be able create a Source List for a small number of non valuated Material Masters which will be available when creating a P Req. The P Req will be priced by the creator and the P Req prices should flow through to the P Ord when adopted without being overwritten by an info rec price or previous P Ord price. Do you have any thoughts on this ?
Thanks in anticipation
Digidick

I doubt if standard SAP supports your required process, because SAP always give a first preference to Price Conditions from Info Record to fetch into PO..
If the Info record is available, SAP will not fetch the price from PR into PO.
However, you can look for any BAPI or OSS note

Document on E-rec........

Hi,
I am an HR abap programmer. I would like to to know what E-rec and LSO are? Also, I would like to know about the job of an HR abap programmer in that modules. So, it would be great if anyone could share a document on E-rec and LSO which can clarify my doubts.
Thanks in advance.
Regards,
Ramana

This link will help you.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/80/ea89395eb58c4f9d0c3e837cf0909d/frameset.htm
Go to www.help.sap.com for more info.
All the best,
Santosh

Doubt regarding editable ALV report using Classes

I need to create an ALV report and make few fields editable
and i need to update the changes to the corresponding database tables
for that please suggest me some idea or provide me sample code for that
urgent

Hi ramesh,
Please check this example program. I think it will help for some extent.
[code]&----
*& Report ZSUMA_INTERACTIVEREPORT *
report zsuma_interactivereport.
tables: vbak.
data :gr_alvgrid type ref to cl_gui_alv_grid,
 gr_cc_name type scrfname value 'CC_ALV',
 gr_ccontainer type ref to cl_gui_custom_container,
 gr_fieldcat type lvc_t_fcat,
 gr_layout type lvc_s_layo,
 gr_sort type lvc_t_sort,
 gr_get_cell type lvc_t_cell,
 gr_set_cell type lvc_t_cell,
 gr_hyper type lvc_t_hype,
 gr_drop_down type lvc_t_drop,
 is_variant type disvariant,
 line_number type lvc_s_roid-row_id,
 line(5) type c ,
 cell_value type lvc_value.
data: begin of it_vbak occurs 0,
 vbeln type vbak-vbeln,
 erdat like vbak-erdat,
 erzet like vbak-erzet,
 netwr like vbak-netwr,
 waerk like vbak-waerk,
*Below field is useful for making the entire row with different colors.
it must be a char of 4.and layout-info_fname should populate with
*this field.
 rowcolor(4) type c,
*Below field is useful for making the INDIVIDUAL CELL with different
*colors.for this we have to include structure of type lvc_t_scol.
*layout-ctab_fname should be populate with this field.
 cellcolor type lvc_t_scol,
*below field is added for for providing the hyperlinks to perticular
*field. at the time of field catalog , it_fcatalog-web_field should be
*populate with this field.
 vbeln_hyper type int4,
*For displaying one cell as button.we have to declare one styles
*internal table .it has to be populate.at layout structure this table
*name has to be populate at layout-stylename.
 cellstyle type lvc_t_styl,
 end of it_vbak.
*& SELECTION SCREEN
selection-screen begin of block b1 with frame title text-001.
select-options s_vbeln for vbak-vbeln.
selection-screen end of block b1.
start-of-selection.
select vbeln
 erdat
 erzet
 netwr
 waerk
 from vbak
 into corresponding fields of table it_vbak
 where vbeln in s_vbeln.
data: wa_cellcolor type lvc_s_scol,
 wa_style type lvc_s_styl.
loop at it_vbak.
FOR ROW COLORING
if sy-tabix = 1.
it_vbak-rowcolor = 'C511'.
FOR PUTTING THE HYPERLINKS ON VBELN FIELD
it_vbak-vbeln_hyper = '1'.
modify it_vbak.
endif.
FOR CELL COLORING
if sy-tabix = 2.
wa_cellcolor-fname = 'ERZET'.
wa_cellcolor-color-col = '6'.
wa_cellcolor-color-int = '1'.
wa_cellcolor-color-inv = '1'.
append wa_cellcolor to it_vbak-cellcolor.
modify it_vbak index 2.
endif.
FOR DISPLAYING THE CELL AS A BUTTON
clear it_vbak-cellstyle.
at last.
read table it_vbak index sy-tabix.
wa_style-fieldname = 'NETWR'.
wa_style-style = cl_gui_alv_grid=>mc_style_button.
append wa_style to it_vbak-cellstyle .
modify it_vbak .
endat.
endloop.
if not it_vbak[] is initial.
call screen 100.
endif.
*CLASS DEFINITION FOR HANDLING THE EVENTS IN ALV GRID
class gr_event_handler definition.
public section.
methods:handle_hotspot_click
 for event hotspot_click of cl_gui_alv_grid
 importing e_row_id e_column_id es_row_no.
endclass.
*CLASS IMPLEMENTATIONFOR HANDLING THE EVENTS IN ALV GRID
class gr_event_handler implementation.
method handle_hotspot_click.
perform handle_hotspot_click using e_row_id e_column_id es_row_no.
endmethod.
endclass.
*& Form BUILDING_FIELDCATALOG
 text
 <--P_GR_FIELDCAT text
form building_fieldcatalog changing p_gr_fieldcat type lvc_t_fcat.
data s_fieldcat type lvc_s_fcat.
s_fieldcat-fieldname = 'VBELN'.
s_fieldcat-outputlen = '15'.
s_fieldcat-col_pos = '1'.
s_fieldcat-coltext = 'DOCCUMENT NO.'.
s_fieldcat-key = ' '.
s_fieldcat-emphasize = 'C511'.
s_fieldcat-web_field = 'VBELN_HYPER'.
append s_fieldcat to p_gr_fieldcat .
clear s_fieldcat.
s_fieldcat-fieldname = 'ERDAT'.
s_fieldcat-outputlen = '15'.
s_fieldcat-col_pos = '2'.
s_fieldcat-coltext = 'REC CREATE DATE.'.
s_fieldcat-emphasize = 'C311'.
s_fieldcat-hotspot = 'X'.
append s_fieldcat to p_gr_fieldcat .
clear s_fieldcat.
s_fieldcat-fieldname = 'ERZET'.
s_fieldcat-outputlen = '15'.
s_fieldcat-col_pos = '3'.
s_fieldcat-coltext = 'TIME ENTRY.'.
*S_FIELDCAT-EMPHASIZE = 'C311'.
append s_fieldcat to p_gr_fieldcat .
clear s_fieldcat.
s_fieldcat-fieldname = 'NETWR'.
s_fieldcat-outputlen = '15'.
s_fieldcat-col_pos = '4'.
s_fieldcat-emphasize = 'C311'.
s_fieldcat-coltext = 'NET WEIGHT.'.
s_fieldcat-do_sum = 'X'.
append s_fieldcat to p_gr_fieldcat .
clear s_fieldcat.
s_fieldcat-fieldname = 'WAERK'.
s_fieldcat-outputlen = '5'.
s_fieldcat-col_pos = '5'.
s_fieldcat-emphasize = 'C511'.
s_fieldcat-coltext = 'CURR.'.
FOR PUTTING THE DROP DOWN BOX.
s_fieldcat-drdn_hndl = '1'.
s_fieldcat-edit = 'X'.
append s_fieldcat to p_gr_fieldcat .
clear s_fieldcat.
endform. " BUILDING_FIELDCATALOG
*& Form CREATE_CCONTAINER_INSTANCE
 text
--> p1 text
<-- p2 text
form create_ccontainer_instance .
create object gr_ccontainer
exporting
container_name = gr_cc_name
exceptions
cntl_error = 1
cntl_system_error = 2
create_error = 3
lifetime_error = 4
lifetime_dynpro_dynpro_link = 5
others = 6
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. " CREATE_CCONTAINER_INSTANCE
*& Form CREATE_ALVGRID_INSTANCE
 text
--> p1 text
<-- p2 text
form create_alvgrid_instance .
create object gr_alvgrid
exporting
 i_parent = gr_ccontainer
exceptions
 error_cntl_create = 1
 error_cntl_init = 2
 error_cntl_link = 3
 error_dp_create = 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.
endform. " CREATE_ALVGRID_INSTANCE
*& Form DISPLAYING_ALVGRID
 text
--> p1 text
<-- p2 text
form displaying_alvgrid .
call method gr_alvgrid->set_table_for_first_display
exporting
 I_BUFFER_ACTIVE =
 I_BYPASSING_BUFFER =
 I_CONSISTENCY_CHECK =
 I_STRUCTURE_NAME =
 is_variant = is_variant
 i_save = 'A'
 I_DEFAULT = 'X'
 is_layout = gr_layout
 IS_PRINT =
 IT_SPECIAL_GROUPS =
 IT_TOOLBAR_EXCLUDING =
 it_hyperlink = gr_hyper
 IT_ALV_GRAPHICS =
 IT_EXCEPT_QINFO =
changing
 it_outtab = it_vbak[]
 it_fieldcatalog = gr_fieldcat
 it_sort = gr_sort
 IT_FILTER =
EXCEPTIONS
 INVALID_PARAMETER_COMBINATION = 1
 PROGRAM_ERROR = 2
 TOO_MANY_LINES = 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.
*CALL METHOD GR_ALVGRID->GET_FRONTEND_LAYOUT
IMPORTING
 ES_LAYOUT = GR_LAYOUT
*GR_LAYOUT-GRID_TITLE = 'HAI ALV'.
*CALL METHOD GR_ALVGRID->SET_FRONTEND_LAYOUT
EXPORTING
 IS_LAYOUT = GR_LAYOUT
endform. " DISPLAYING_ALVGRID
*& Form REFRESH_DISPLAY_TABLE
 text
--> p1 text
<-- p2 text
form refresh_display_table .
call method gr_alvgrid->refresh_table_display
EXPORTING
 IS_STABLE =
 I_SOFT_REFRESH =
exceptions
 finished = 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. " REFRESH_DISPLAY_TABLE
*& Form SETTING_LAYOUT
 text
 <--P_GR_LAYOUT text
form setting_layout changing p_gr_layout type lvc_s_layo.
p_gr_layout-grid_title = 'ALV GRID USING ABAP OBJECTS'.
p_gr_layout-zebra = 'X'.
p_gr_layout-no_toolbar = ''.
p_gr_layout-sel_mode = 'D'.
p_gr_layout-info_fname = 'ROWCOLOR'.
p_gr_layout-ctab_fname = 'CELLCOLOR'.
p_gr_layout-stylefname = 'CELLSTYLE'.
endform. " SETTING_LAYOUT
*& Module STATUS_0100 OUTPUT
 text
module status_0100 output.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
set pf-status 'MENU'.
if gr_alvgrid is initial.
*CREATING THE CONTAINER INSTANCE BY SENDING THE CONTAINER NAME( IT HAS
*TO COINSIDE WITH COSTUM CONTROL NAME OF TRANSACTION SCREEN
perform create_ccontainer_instance.
perform create_alvgrid_instance.
*VARIANT POPULATION.
perform setting_variants changing is_variant.
*BELOW FORM IS USEFUL TO FILL THE HYPER LINK TABLE AND WE PASS THAT
*TABLE TO 'IT_HYPERLINK' PARAMETER IN FIRST DISPLAY METHOD.
perform setting_hyperlinks_field changing gr_hyper.
*TO MAKE THE COLOUMN AS DROP DOWN.
perform setting_dropdown_column changing gr_drop_down.
perform building_fieldcatalog changing gr_fieldcat.
perform setting_layout changing gr_layout.
perform setting_sorting changing gr_sort.
perform setting_cells changing gr_set_cell.
perform displaying_alvgrid.
*PERFORM GETTING_CELL_DETAILS CHANGING GR_GET_CELL. " IT IS NOT WORKING
 FOR ME AND I HAVE DOUBT .
perform creating_event_object.
*PERFORM REFRESH_DISPLAY_TABLE.
endif.
endmodule. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
 text
module user_command_0100 input.
case sy-ucomm.
when 'BACK'.
leave to screen 000.
endcase.
endmodule. " USER_COMMAND_0100 INPUT
*& Form SETTING_SORTING
 text
 <--P_GR_SORT text
form setting_sorting changing p_gr_sort type lvc_t_sort.
data: lr_sort type lvc_s_sort.
lr_sort-spos = '1'.
lr_sort-fieldname = 'VBELN'.
lr_sort-up = 'X'.
append lr_sort to p_gr_sort.
lr_sort-spos = '2'.
lr_sort-fieldname = 'ERDAT'.
lr_sort-up = 'X'.
append lr_sort to p_gr_sort.
endform. " SETTING_SORTING
*& Form GETTING_CELL_DETAILS
 text
 <--P_GR_GET_CELL text
form getting_cell_details changing p_gr_get_cell.
call method gr_alvgrid->get_selected_cells
importing
 et_cell = p_gr_get_cell
*CELL_VALUE = P_GR_GET_CELL-VALUE.
endform. " GETTING_CELL_DETAILS
*& Form SETTING_CELLS
 text
 <--P_GR_SET_CELL text
form setting_cells changing p_gr_set_cell type lvc_t_cell.
data:s_gr_set_cell type lvc_s_cell.
s_gr_set_cell-col_id-fieldname = 'NETWR'.
s_gr_set_cell-row_id-index = '3'.
append s_gr_set_cell to p_gr_set_cell.
call method gr_alvgrid->set_selected_cells
exporting
 it_cells = p_gr_set_cell.
endform. " SETTING_CELLS
*& Form SETTING_HYPERLINKS_FIELD
 text
 <--P_GR_HYPER text
form setting_hyperlinks_field changing p_gr_hyper type lvc_t_hype.
data: is_hype type lvc_s_hype.
is_hype-handle = '1'.
is_hype-href = 'HTTP://WWW.GOOGLE.CO.IN'.
append is_hype to p_gr_hyper.
is_hype-handle = '2'.
is_hype-href = 'HTTP://SDN.SAP.COM'.
append is_hype to p_gr_hyper.
endform. " SETTING_HYPERLINKS_FIELD
*& Form SETTING_DROPDOWN_COLUMN
 text
 <--P_GR_DROP_DOWN text
form setting_dropdown_column changing p_gr_drop_down type lvc_t_drop.
data: wa_drop type lvc_s_drop.
wa_drop-handle = '1'.
wa_drop-value = '$'.
append wa_drop to p_gr_drop_down.
wa_drop-handle = '1'.
wa_drop-value = 'Rs'.
append wa_drop to p_gr_drop_down.
wa_drop-handle = '1'.
wa_drop-value = 'CUR'.
append wa_drop to p_gr_drop_down.
call method gr_alvgrid->set_drop_down_table
exporting
 it_drop_down = p_gr_drop_down
 IT_DROP_DOWN_ALIAS =
endform. " SETTING_DROPDOWN_COLUMN
*& Form SETTING_VARIANTS
 text
 <--P_IS_VARIANT text
form setting_variants changing p_is_variant type disvariant.
p_is_variant-report = sy-repid.
endform. " SETTING_VARIANTS
*& Form HANDLE_HOTSPOT_CLICK
 text
 -->P_E_ROW text
 -->P_E_COLUMN text
 -->P_E_ROW_NO text
form handle_hotspot_click using p_e_row_id type lvc_s_row
 p_e_column_id type lvc_s_col
 p_es_row_no type lvc_s_roid.
read table it_vbak index p_es_row_no-row_id.
if sy-subrc = 0 and p_e_column_id-fieldname = 'ERDAT'.
line = p_es_row_no-row_id.
line_number = p_es_row_no-row_id.
leave to screen 200.
endif.
endform. " HANDLE_HOTSPOT_CLICK
*& Form CREATING_EVENT_OBJECT
 text
--> p1 text
<-- p2 text
form creating_event_object .
data event_handle type ref to gr_event_handler.
create object event_handle.
set handler event_handle->handle_hotspot_click for gr_alvgrid.
endform. " CREATING_EVENT_OBJECT
*& Module STATUS_0200 OUTPUT
 text
module status_0200 output.
set pf-status 'BB'.
SET TITLEBAR 'xxx'.
*LINE = LINE_NUMBER.
endmodule. " STATUS_0200 OUTPUT
*& Module USER_COMMAND_0200 INPUT
 text
module user_command_0200 input.
if sy-ucomm = 'BACK'.
leave to screen 100.
endif.
endmodule. " USER_COMMAND_0200 INPUT[/code]
Reward points if helpful
Thanks,
Suma.

MOPZ issue for E-Rec 6.0 Server

Hi Experts,
             I configured MOPZ in solution manager for E-Rec 6.0 server, If i choose calculate the files automatically I am getting error as " No Addon Product Version allowed for transaction: SAP E-RECRUITING 6.0 (01200615320900001315)". Kindly help me.
     Thanks in advance.
Regards,
Sampath.

Hi Sunny,
            Sorry if i go to system -> status -> our server is "SAP NetWeaver 2004s", But is is E-recuirement server, if i go to smsy i can able to find SAP E-RECURTING. Here my doubt is i need to register under SAP E-RECURTING or I need to register under SAP NETWEAVER.
            Kindly help me.
Regards,
Sampath.

E-Recruiting 604 Doubt about the planning of the background job.

Hi,
We are on E-Rec 604 with seperated standlone e-rec system.
I did the initial transfer of the Org Management data through PFAL from ECC to E-Recruit and all were ok.
Now I have to planed the job for the future changes.
This is my doubt, I just have to plan the program RBDMIDOC in the HR system, or should I add something more?.
Please somebody could guide me?.
Thanks a lot,
Esther

Hello Esther,
there are some more configuration steps for the regular update after the initial load.
Probably already done by you is the activation of the change pointers for the message type otherwise RBDMIDOC won't create any IDoc.
Additional settings to the ALE you should apply to the system:
- In the e-recruiting system, go to the partner profile settings for the ALE. Open the inbound parameters for the message type and switch radio button in the "process by function module" section from trigger immediatly to trigger by background program.
- Create a variant for report RBDAPP01 on the e-rec system setting the package size to 1
- Plan the report RBDAPP01 as job on the e-recruiting system to process the incomming IDocs
Ensure in the job scheduling of RBDMIDOC and RBDAPP01 that both are running before midnight and the RBDMIDOC is running before RBDAPP01 of course.
Additional E-Recruiting settings you have to do:
- schedule HRALXSYNC on the e-rec system as daily job
- Ensure that the e-rec periodical service PROCESS_CAND_STATUS_CHANGE (class CL_HRRCF_UPDATE_P_STAT) is activated in the e-rec customizing under E-Recruiting -> Technical Settings -> Periodical Services
Best Regards
Roman

Rec/Client

Hi Gurus,
We want to activate the parameter REC/CLIENT in our production Environment.We know that activating this parametre will create a huge logs
Please any body clarify the below doubts:
1) where will be the logs stored at OS level
2) What would be the amount of Logs generated for one day, we have more than 700 Users and 74000 thousand table in our Production system.
3) We want to activate the logs for only 3 tables like USR02...
but when I saw in table DD09L there were more than 28000 tables, already activated log data changes, So we want to deactivate this option from 28000 tables and activate for only 3 tables.Please tell me the process step by step.
4) If we want to deacivate the loging for the above said tales, what is the process (I want to know is there any other process with out deactivating the REC/CLIENT parameter because this need system reboot)
Thanks & Reagrds,
Veda Gandham

> Hi
>
> You can configure the client that should be logged by
> the
> R/3 profile parameter rec/client (see documentation
> in your R/3 system)
>
> Generally, there should not be too many entries
> logged, because
> logging is only set for cusomizing tables (by
> default) and
> customizing should not happen too often.
>
> Also see note 41300, 1916
>
> Reward points if useful
Hi, thanks for your reply. Looking at S Note 1916 this states that all servers must have the same setting for logging to work correctly, which is what i wanted to know. However there is no explanation of what occurs if settings are different or otherwise, anyone know the background on how this param (rec/client) works?
Thanks
Ash

Bdc rec - reg

Hi guru's,
after i have done bdc rec, i have imported the code to my program. but i have a small problem.
1. i have selected some views for my trn mm03(during bdc rec). while executing the Final program, the view at the last is not being selected until i scroll it until that view. (but in bdc rec i hav selected them) . hope u understood.
my code snippet:
PERFORM open_group.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0060'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTR'.
        PERFORM bdc_field       USING 'RMMG1-MATNR'
                                      WA_FINAL-MATNR.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(02)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(01)'
                                      c_x.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(02)'
                                      c_x.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(12)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(12)'
                                      c_x.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'MSICHTAUSW-DYTXT(13)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTR'.
        PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(13)'
                                      c_x.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '0080'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-WERKS'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=ENTR'.
        PERFORM bdc_field       USING 'RMMG1-WERKS'
                                       plant.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_dynpro      USING 'SAPLMGMM' '4000'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '/00'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'RMMG1-MATNR'.
        PERFORM bdc_dynpro      USING 'SAPLSPO1' '0300'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
        PERFORM bdc_transaction USING 'MM03'.
        PERFORM close_group.
So, in the above code, i want the views to be selected directly without me pressing enter. so which fiels should i change in the above code for the dynamic selection of the views in trn 'mm03'.
2. i have to skip the first two screens, like entering the materialno & selecting the views. As i have already selected them durin bdc rec.
How to code for skipping these two screens.
can anyone solve my two probs.
ask me for any clarity in my doubts.
please help me
regards,
chaitanya
Edited by: chaitanya on Mar 13, 2008 11:02 AM

hi
for ur first query :
     i am giving u sample code for view selection on second screen
         perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(17)'.
perform bdc_field       using 'BDC_OKCODE'
                              'P+'.perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(02)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(03)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(04)'
                                'X'.
                             record-KZSEL_04_005.
perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                                'X'.
                             record-KZSEL_05_006.
perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                                'X'.
                             record-KZSEL_06_007.
perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                                'X'.
                             record-KZSEL_01_004.
*perform bdc_field       using 'MSICHTAUSW-KZSEL(08)'
                               'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                                'X'.
                             record-KZSEL_09_008.
perform bdc_field       using 'MSICHTAUSW-KZSEL(10)'
                                'X'.
                             record-KZSEL_01_004.
*perform bdc_field       using 'MSICHTAUSW-KZSEL(11)'
                               'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(12)'
                                'X'.
                             record-KZSEL_12_009.
perform bdc_field       using 'MSICHTAUSW-KZSEL(13)'
                                'X'.
                             record-KZSEL_13_010.
perform bdc_field       using 'MSICHTAUSW-KZSEL(14)'
                                'X'.
                             record-KZSEL_14_011.
perform bdc_field       using 'MSICHTAUSW-KZSEL(15)'
                                'X'.
                             record-KZSEL_15_012.
perform bdc_field       using 'MSICHTAUSW-KZSEL(16)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(17)'
                                'X'.
                             record-KZSEL_17_013.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(02)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(05)'
                                'X'.
                             record-KZSEL_13_014.
perform bdc_field       using 'MSICHTAUSW-KZSEL(06)'
                                'X'.
                             record-KZSEL_14_015.
perform bdc_field       using 'MSICHTAUSW-KZSEL(07)'
                                'X'.
                             record-KZSEL_01_004.
perform bdc_field       using 'MSICHTAUSW-KZSEL(08)'
                                'X'.
                             record-KZSEL_16_016.
perform bdc_field       using 'MSICHTAUSW-KZSEL(09)'
                                'X'.
                             record-KZSEL_01_004.
here important is use P+ code to page down for select last views, and after that it may possible
that value 'MSICHTAUSW-KZSEL(07)'   may be greater then 15 so change this by counting position . like
for 16 -
> 01
     17 -
> 02
2. For ur second problem .
       as u asking to eleminate 1and 2 screen , it is not possible bcoz
as u enter t.code first screen will come .
and without selecting VIEW u can not go further in t.code.
what u can do is make the entries in fields of these screen default then u will not requied to give them in flat file .
reward if helpful.

Doubt in fbl1n transaction

hi i have a doubt....
in fbl1n transaction, there are open items and cleared items.
in it the cleared items for certain document types such as invoice etc is not present in the open item table (bsik)
however the cleared items for document types such as general voucher its present in the open items table (bsik)
is this possible as all cleared item entries shld b present in the open item table with an indicator set for cleared or not...
plz exlain!

Hi
There are 2 tables(open and Closed Items) in FI for Account Payables and Account Receivables and GL accounts
1.Account payables: BSIK is Open Items and BSAK is Closed items
2.Account Receivables; BSID and BSAD for OPEN and closed items
3/GL accounts : BSIS and BSAS for Open and Closed Items
Reward points for useful Answers
Regards
Anji

Rec doubt

Similar Messages

Maybe you are looking for