Standard objects to store employee dependant details
is there any standard CUBE or DSO to store the dependant details of the employees in BI(HR Module)
tht infoobject covers only the type of coverage. i like to have the dependant details, like spouse name, child name , parent's name , their DOB etc.,
I got your doubt . Please find the steps to your requirement .
1. Copy the infoobject for employee under a new infoobject created by you by copying .
2. Parallaly look for infoobjects in other session that have data types and legths that matches for
spouse name, child name , parent's name , their DOB .
If you are not able to find the same go create it for the fields for which infoobjects are not available .
3. Then at the attribute level add all these infoobjects .
4. I hope you will be creating a datasource for the same and then do the rest of the things to bring in
the data .
Assign marks is the best way to appreciate help
Similar Messages
-
Abap-hr : error in retrieving employee's family dependent details
Hi all,
while retreiving family dependent details of employee of subtype de01 its throwing up a dump
<REMOVED BY MODERATOR>
*& Report ZABAP_HR *
REPORT ZABAP_HR .
TABLES : PERNR.
INFOTYPES : 0000, 0001, 0002, 0006, 0105, 0021.
* STRUCTURES
TYPES : BEGIN OF TY_EMP,
PERNR(20) TYPE C, "PERSONNEL NO
NACHN TYPE NACHN, "FIRST NAME
VORNA TYPE VORNA, "LAST NAME
* ANSSA TYPE ANSSA, "ADDRESS TYPE
STRAS TYPE STRAS, "STREET
PSTLZ TYPE PSTLZ, "POSTAL CODE
ORT01 TYPE ORT01, "CITY
LAND1 TYPE LAND1, "COUNTRY
STRAS1 TYPE STRAS, "STREET
PSTLZ1 TYPE PSTLZ, "POSTAL CODE
ORT011 TYPE ORT01, "CITY
LAND11 TYPE LAND1, "COUNTRY
PLANS TYPE PLANS, "POSITION
EMAILID TYPE COMM_ID_LONG, "EMAIL ID
FAMSA TYPE FAMSA, "DEPENDENT TYPE
FAVOR TYPE FAVOR, "FIRST NAME
FANAM TYPE PAD_NACHN, "LAST NAME
FAMSA1 TYPE FAMSA, "DEPENDENT TYPE
FAVOR1 TYPE FAVOR, "FIRST NAME
FANAM1 TYPE PAD_NACHN, "LAST NAME
FAMSA2 TYPE FAMSA, "DEPENDENT TYPE
FAVOR2 TYPE FAVOR, "FIRST NAME
FANAM2 TYPE PAD_NACHN, "LAST NAME
FAMSA3 TYPE FAMSA, "DEPENDENT TYPE
FAVOR3 TYPE FAVOR, "FIRST NAME
FANAM3 TYPE PAD_NACHN, "LAST NAME
FAMSA4 TYPE FAMSA, "DEPENDENT TYPE
FAVOR4 TYPE FAVOR, "FIRST NAME
FANAM4 TYPE PAD_NACHN, "LAST NAME
FAMSA5 TYPE FAMSA, "DEPENDENT TYPE
FAVOR5 TYPE FAVOR, "FIRST NAME
FANAM5 TYPE PAD_NACHN, "LAST NAME
FAMSA6 TYPE FAMSA, "DEPENDENT TYPE
FAVOR6 TYPE FAVOR, "FIRST NAME
FANAM6 TYPE PAD_NACHN, "LAST NAME
FAMSA7 TYPE FAMSA, "DEPENDENT TYPE
FAVOR7 TYPE FAVOR, "FIRST NAME
FANAM7 TYPE PAD_NACHN, "LAST NAME
FAMSA8 TYPE FAMSA, "DEPENDENT TYPE
FAVOR8 TYPE FAVOR, "FIRST NAME
FANAM8 TYPE PAD_NACHN, "LAST NAME
FAMSA9 TYPE FAMSA, "DEPENDENT TYPE
FAVOR9 TYPE FAVOR, "FIRST NAME
FANAM9 TYPE PAD_NACHN, "LAST NAME
FAMSA10 TYPE FAMSA, "DEPENDENT TYPE
FAVOR10 TYPE FAVOR, "FIRST NAME
FANAM10 TYPE PAD_NACHN, "LAST NAME
FAMSA11 TYPE FAMSA, "DEPENDENT TYPE
FAVOR11 TYPE FAVOR, "FIRST NAME
FANAM11 TYPE PAD_NACHN, "LAST NAME
FAMSA12 TYPE FAMSA, "DEPENDENT TYPE
FAVOR12 TYPE FAVOR, "FIRST NAME
FANAM12 TYPE PAD_NACHN, "LAST NAME
FAMSA13 TYPE FAMSA, "DEPENDENT TYPE
FAVOR13 TYPE FAVOR, "FIRST NAME
FANAM13 TYPE PAD_NACHN, "LAST NAME
FAMSA14 TYPE FAMSA, "DEPENDENT TYPE
FAVOR14 TYPE FAVOR, "FIRST NAME
FANAM14 TYPE PAD_NACHN, "LAST NAME
END OF TY_EMP.
* INTERNAL TABLES
DATA : IT_EMP TYPE STANDARD TABLE OF TY_EMP.
* WORK AREAS
DATA : WA_EMP TYPE TY_EMP.
DATA : N TYPE I.
* START-OF-SELECTION
START-OF-SELECTION.
GET PERNR.
* SUBROUTINE TO FETCH DATA FROM INFOTYPES
PERFORM FETCH_DATA_INFTY.
END-OF-SELECTION.
* SUBROUTINE TO DISPLAY DATA
PERFORM DISPLAY_DATA.
*& Form FETCH_DATA_INFTY
* text
* --> p1 text
* <-- p2 text
*PERSONAL DETAILS
RP_PROVIDE_FROM_LAST P0002 SPACE PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-PERNR = P0002-PERNR.
WA_EMP-NACHN = P0002-NACHN.
WA_EMP-VORNA = P0002-VORNA.
ENDIF.
*ORGANIZATIONAL DETAILS
RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-PLANS = P0001-PLANS.
ENDIF.
*PERMANENT ADDRESS DETAILS
RP_PROVIDE_FROM_LAST P0006 0001 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-STRAS = P0006-STRAS.
WA_EMP-PSTLZ = P0006-PSTLZ.
WA_EMP-ORT01 = P0006-ORT01.
WA_EMP-LAND1 = P0006-LAND1.
ENDIF.
*TEMPORARY ADDRESS DETAILS
RP_PROVIDE_FROM_LAST P0006 0002 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-STRAS1 = P0006-STRAS.
WA_EMP-PSTLZ1 = P0006-PSTLZ.
WA_EMP-ORT011 = P0006-ORT01.
WA_EMP-LAND11 = P0006-LAND1.
ENDIF.
*COMMUNICATION DETAILS
RP_PROVIDE_FROM_LAST P0105 0010 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-EMAILID = P0105-USRID_LONG.
ENDIF.
*DEPENDANT DETAILS
FORM FETCH_DATA_INFTY .
DATA : ITAB1 TYPE P0021-FAMSA VALUE 'DE01'.
DATA : ITAB TYPE I.
MOVE ITAB1 TO ITAB.
RP_PROVIDE_FROM_LAST P0021 0001 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA = P0021-FAMSA.
WA_EMP-FAVOR = P0021-FAVOR.
WA_EMP-FANAM = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0002 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA1 = P0021-FAMSA.
WA_EMP-FAVOR1 = P0021-FAVOR.
WA_EMP-FANAM1 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0003 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA2 = P0021-FAMSA.
WA_EMP-FAVOR2 = P0021-FAVOR.
WA_EMP-FANAM2 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0004 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA3 = P0021-FAMSA.
WA_EMP-FAVOR3 = P0021-FAVOR.
WA_EMP-FANAM3 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0005 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA4 = P0021-FAMSA.
WA_EMP-FAVOR4 = P0021-FAVOR.
WA_EMP-FANAM4 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0006 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA5 = P0021-FAMSA.
WA_EMP-FAVOR5 = P0021-FAVOR.
WA_EMP-FANAM5 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0007 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA6 = P0021-FAMSA.
WA_EMP-FAVOR6 = P0021-FAVOR.
WA_EMP-FANAM6 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0008 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA7 = P0021-FAMSA.
WA_EMP-FAVOR7 = P0021-FAVOR.
WA_EMP-FANAM7 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0009 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA8 = P0021-FAMSA.
WA_EMP-FAVOR8 = P0021-FAVOR.
WA_EMP-FANAM8 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0010 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA9 = P0021-FAMSA.
WA_EMP-FAVOR9 = P0021-FAVOR.
WA_EMP-FANAM9 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0011 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA10 = P0021-FAMSA.
WA_EMP-FAVOR10 = P0021-FAVOR.
WA_EMP-FANAM10 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0012 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA11 = P0021-FAMSA.
WA_EMP-FAVOR11 = P0021-FAVOR.
WA_EMP-FANAM11 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0013 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA12 = P0021-FAMSA.
WA_EMP-FAVOR12 = P0021-FAVOR.
WA_EMP-FANAM12 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0014 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA13 = P0021-FAMSA.
WA_EMP-FAVOR13 = P0021-FAVOR.
WA_EMP-FANAM13 = P0021-FANAM.
ENDIF.
*DATA : DE01 LIKE P0021-FAMSA.
*DATA : ITAB TYPE I.
*DATA : DE01(4) TYPE C.
RP_PROVIDE_FROM_LAST P0021 ITAB PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA14 = P0021-FAMSA.
WA_EMP-FAVOR14 = P0021-FAVOR.
WA_EMP-FANAM14 = P0021-FANAM.
ENDIF.
APPEND WA_EMP TO IT_EMP.
CLEAR WA_EMP.
ENDFORM. " FETCH_DATA_INFTY
*& Form DISPLAY_DATA
* text
* --> p1 text
* <-- p2 text
FORM DISPLAY_DATA .
LOOP AT IT_EMP INTO WA_EMP.
AT FIRST.
WRITE : /02 'PERSONNELNO',
15 'FIRSTNAME',
25 'LASTNAME',
35 'POSITION',
45 'PERMANENT ADDRESS : ',
65 'STREET',
80 'POSTALCODE',
93 'CITY',
100 'COUNTRY',
110 'EMAILID',
130 'DEP TYPE : ',
147 'DEP FIRSTNAME',
160 'DEP LASTNAME'.
ULINE.
ENDAT.
WRITE : /02 WA_EMP-PERNR,
15 WA_EMP-NACHN,
25 WA_EMP-VORNA,
35 WA_EMP-PLANS,
65 WA_EMP-STRAS,
80 WA_EMP-PSTLZ,
90 WA_EMP-ORT01,
100 WA_EMP-LAND1,
110 WA_EMP-EMAILID,
137 WA_EMP-FAMSA,
147 WA_EMP-FAVOR,
160 WA_EMP-FANAM.
WRITE : /137 WA_EMP-FAMSA1,
147 WA_EMP-FAVOR1,
160 WA_EMP-FANAM1.
WRITE : /137 WA_EMP-FAMSA2,
147 WA_EMP-FAVOR2,
160 WA_EMP-FANAM2.
WRITE : /137 WA_EMP-FAMSA3,
147 WA_EMP-FAVOR3,
160 WA_EMP-FANAM3.
WRITE : /137 WA_EMP-FAMSA4,
147 WA_EMP-FAVOR4,
160 WA_EMP-FANAM4.
WRITE : /137 WA_EMP-FAMSA5,
147 WA_EMP-FAVOR5,
160 WA_EMP-FANAM5.
WRITE : /137 WA_EMP-FAMSA6,
147 WA_EMP-FAVOR6,
160 WA_EMP-FANAM6.
WRITE : /137 WA_EMP-FAMSA7,
147 WA_EMP-FAVOR7,
160 WA_EMP-FANAM7.
WRITE : /137 WA_EMP-FAMSA8,
147 WA_EMP-FAVOR8,
160 WA_EMP-FANAM8.
WRITE : /137 WA_EMP-FAMSA9,
147 WA_EMP-FAVOR9,
160 WA_EMP-FANAM9.
WRITE : /137 WA_EMP-FAMSA10,
147 WA_EMP-FAVOR10,
160 WA_EMP-FANAM10.
WRITE : /137 WA_EMP-FAMSA11,
147 WA_EMP-FAVOR11,
160 WA_EMP-FANAM11.
WRITE : /137 WA_EMP-FAMSA12,
147 WA_EMP-FAVOR12,
160 WA_EMP-FANAM12.
WRITE : /137 WA_EMP-FAMSA13,
147 WA_EMP-FAVOR13,
160 WA_EMP-FANAM13.
WRITE : /137 WA_EMP-FAMSA14,
147 WA_EMP-FAVOR14,
160 WA_EMP-FANAM14.
ULINE.
AT FIRST.
WRITE : /45 'TEMPORARY ADDRESS : ',
65 'STREET',
87 'POSTALCODE',
100 'CITY',
120 'COUNTRY'.
ULINE.
ENDAT.
WRITE : /65 WA_EMP-STRAS1,
87 WA_EMP-PSTLZ1,
100 WA_EMP-ORT011,
120 WA_EMP-LAND11.
ENDLOOP.
ENDFORM. " DISPLAY_DATA
Thanks & Regards
Jerry
Code Formatted by: Alvaro Tejada Galindo on Jun 5, 2008 11:36 AMHi Ira , thanks for your help.......... I checked it but still getting the same error as unable to interpret de04 as number....see the below code..........this I am executing for all active employees.....
regards
John
*& Report ZABAP_HR *
REPORT ZABAP_HR .
TABLES : PERNR.
INFOTYPES : 0000, 0001, 0002, 0006, 0105, 0021.
STRUCTURES
TYPES : BEGIN OF TY_EMP,
PERNR(20) TYPE C, "PERSONNEL NO
NACHN TYPE NACHN, "FIRST NAME
VORNA TYPE VORNA, "LAST NAME
ANSSA TYPE ANSSA, "ADDRESS TYPE
STRAS TYPE STRAS, "STREET
PSTLZ TYPE PSTLZ, "POSTAL CODE
ORT01 TYPE ORT01, "CITY
LAND1 TYPE LAND1, "COUNTRY
STRAS1 TYPE STRAS, "STREET
PSTLZ1 TYPE PSTLZ, "POSTAL CODE
ORT011 TYPE ORT01, "CITY
LAND11 TYPE LAND1, "COUNTRY
PLANS TYPE PLANS, "POSITION
EMAILID TYPE COMM_ID_LONG, "EMAIL ID
FAMSA TYPE FAMSA, "DEPENDENT TYPE
FAVOR TYPE FAVOR, "FIRST NAME
FANAM TYPE PAD_NACHN, "LAST NAME
FAMSA1 TYPE FAMSA, "DEPENDENT TYPE
FAVOR1 TYPE FAVOR, "FIRST NAME
FANAM1 TYPE PAD_NACHN, "LAST NAME
FAMSA2 TYPE FAMSA, "DEPENDENT TYPE
FAVOR2 TYPE FAVOR, "FIRST NAME
FANAM2 TYPE PAD_NACHN, "LAST NAME
FAMSA3 TYPE FAMSA, "DEPENDENT TYPE
FAVOR3 TYPE FAVOR, "FIRST NAME
FANAM3 TYPE PAD_NACHN, "LAST NAME
FAMSA4 TYPE FAMSA, "DEPENDENT TYPE
FAVOR4 TYPE FAVOR, "FIRST NAME
FANAM4 TYPE PAD_NACHN, "LAST NAME
FAMSA5 TYPE FAMSA, "DEPENDENT TYPE
FAVOR5 TYPE FAVOR, "FIRST NAME
FANAM5 TYPE PAD_NACHN, "LAST NAME
FAMSA6 TYPE FAMSA, "DEPENDENT TYPE
FAVOR6 TYPE FAVOR, "FIRST NAME
FANAM6 TYPE PAD_NACHN, "LAST NAME
FAMSA7 TYPE FAMSA, "DEPENDENT TYPE
FAVOR7 TYPE FAVOR, "FIRST NAME
FANAM7 TYPE PAD_NACHN, "LAST NAME
FAMSA8 TYPE FAMSA, "DEPENDENT TYPE
FAVOR8 TYPE FAVOR, "FIRST NAME
FANAM8 TYPE PAD_NACHN, "LAST NAME
FAMSA9 TYPE FAMSA, "DEPENDENT TYPE
FAVOR9 TYPE FAVOR, "FIRST NAME
FANAM9 TYPE PAD_NACHN, "LAST NAME
FAMSA10 TYPE FAMSA, "DEPENDENT TYPE
FAVOR10 TYPE FAVOR, "FIRST NAME
FANAM10 TYPE PAD_NACHN, "LAST NAME
FAMSA11 TYPE FAMSA, "DEPENDENT TYPE
FAVOR11 TYPE FAVOR, "FIRST NAME
FANAM11 TYPE PAD_NACHN, "LAST NAME
FAMSA12 TYPE FAMSA, "DEPENDENT TYPE
FAVOR12 TYPE FAVOR, "FIRST NAME
FANAM12 TYPE PAD_NACHN, "LAST NAME
FAMSA13 TYPE FAMSA, "DEPENDENT TYPE
FAVOR13 TYPE FAVOR, "FIRST NAME
FANAM13 TYPE PAD_NACHN, "LAST NAME
FAMSA14 TYPE FAMSA, "DEPENDENT TYPE
FAVOR14 TYPE FAVOR, "FIRST NAME
FANAM14 TYPE PAD_NACHN, "LAST NAME
END OF TY_EMP.
INTERNAL TABLES
DATA : IT_EMP TYPE STANDARD TABLE OF TY_EMP.
WORK AREAS
DATA : WA_EMP TYPE TY_EMP.
DATA : N TYPE I.
START-OF-SELECTION
START-OF-SELECTION.
GET PERNR.
SUBROUTINE TO FETCH DATA FROM INFOTYPES
PERFORM FETCH_DATA_INFTY.
END-OF-SELECTION.
SUBROUTINE TO DISPLAY DATA
PERFORM DISPLAY_DATA.
*& Form FETCH_DATA_INFTY
text
--> p1 text
<-- p2 text
FORM FETCH_DATA_INFTY .
*PERSONAL DETAILS
RP_PROVIDE_FROM_LAST P0002 SPACE PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-PERNR = P0002-PERNR.
WA_EMP-VORNA = P0002-VORNA.
WA_EMP-NACHN = P0002-NACHN.
ENDIF.
*ORGANIZATIONAL DETAILS
RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-PLANS = P0001-PLANS.
ENDIF.
*PERMANENT ADDRESS DETAILS
RP_PROVIDE_FROM_LAST P0006 0001 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-STRAS = P0006-STRAS.
WA_EMP-PSTLZ = P0006-PSTLZ.
WA_EMP-ORT01 = P0006-ORT01.
WA_EMP-LAND1 = P0006-LAND1.
ENDIF.
*TEMPORARY ADDRESS DETAILS
RP_PROVIDE_FROM_LAST P0006 0002 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-STRAS1 = P0006-STRAS.
WA_EMP-PSTLZ1 = P0006-PSTLZ.
WA_EMP-ORT011 = P0006-ORT01.
WA_EMP-LAND11 = P0006-LAND1.
ENDIF.
*COMMUNICATION DETAILS
RP_PROVIDE_FROM_LAST P0105 0010 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-EMAILID = P0105-USRID_LONG.
ENDIF.
*DEPENDANT DETAILS
DATA : ITAB1 TYPE P0021-FAMSA VALUE 'DE01'.
DATA : ITAB(4) TYPE C .
MOVE ITAB1 TO ITAB.
RP_PROVIDE_FROM_LAST P0021 0001 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA = P0021-FAMSA.
WA_EMP-FAVOR = P0021-FAVOR.
WA_EMP-FANAM = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0002 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA1 = P0021-FAMSA.
WA_EMP-FAVOR1 = P0021-FAVOR.
WA_EMP-FANAM1 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0003 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA2 = P0021-FAMSA.
WA_EMP-FAVOR2 = P0021-FAVOR.
WA_EMP-FANAM2 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0004 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA3 = P0021-FAMSA.
WA_EMP-FAVOR3 = P0021-FAVOR.
WA_EMP-FANAM3 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0005 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA4 = P0021-FAMSA.
WA_EMP-FAVOR4 = P0021-FAVOR.
WA_EMP-FANAM4 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0006 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA5 = P0021-FAMSA.
WA_EMP-FAVOR5 = P0021-FAVOR.
WA_EMP-FANAM5 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0007 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA6 = P0021-FAMSA.
WA_EMP-FAVOR6 = P0021-FAVOR.
WA_EMP-FANAM6 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0008 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA7 = P0021-FAMSA.
WA_EMP-FAVOR7 = P0021-FAVOR.
WA_EMP-FANAM7 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0009 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA8 = P0021-FAMSA.
WA_EMP-FAVOR8 = P0021-FAVOR.
WA_EMP-FANAM8 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0010 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA9 = P0021-FAMSA.
WA_EMP-FAVOR9 = P0021-FAVOR.
WA_EMP-FANAM9 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0011 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA10 = P0021-FAMSA.
WA_EMP-FAVOR10 = P0021-FAVOR.
WA_EMP-FANAM10 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0012 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA11 = P0021-FAMSA.
WA_EMP-FAVOR11 = P0021-FAVOR.
WA_EMP-FANAM11 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0013 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA12 = P0021-FAMSA.
WA_EMP-FAVOR12 = P0021-FAVOR.
WA_EMP-FANAM12 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 0014 PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA13 = P0021-FAMSA.
WA_EMP-FAVOR13 = P0021-FAVOR.
WA_EMP-FANAM13 = P0021-FANAM.
ENDIF.
RP_PROVIDE_FROM_LAST P0021 ITAB PN-BEGDA PN-ENDDA.
IF PNP-SW-FOUND = 1.
WA_EMP-FAMSA14 = P0021-FAMSA.
WA_EMP-FAVOR14 = P0021-FAVOR.
WA_EMP-FANAM14 = P0021-FANAM.
ENDIF.
APPEND WA_EMP TO IT_EMP.
CLEAR WA_EMP.
ENDFORM. " FETCH_DATA_INFTY
*& Form DISPLAY_DATA
text
--> p1 text
<-- p2 text
FORM DISPLAY_DATA .
LOOP AT IT_EMP INTO WA_EMP.
AT FIRST.
WRITE : /02 'PERSONNELNO',
15 'FIRSTNAME',
25 'LASTNAME',
35 'POSITION',
45 'PERMANENT ADDRESS : ',
65 'STREET',
80 'POSTALCODE',
93 'CITY',
100 'COUNTRY',
110 'EMAILID',
130 'DEP TYPE : ',
147 'DEP FIRSTNAME',
160 'DEP LASTNAME'.
ULINE.
ENDAT.
WRITE : /02 WA_EMP-PERNR,
15 WA_EMP-NACHN,
25 WA_EMP-VORNA,
35 WA_EMP-PLANS,
65 WA_EMP-STRAS,
80 WA_EMP-PSTLZ,
90 WA_EMP-ORT01,
100 WA_EMP-LAND1,
110 WA_EMP-EMAILID,
137 WA_EMP-FAMSA,
147 WA_EMP-FAVOR,
160 WA_EMP-FANAM.
WRITE : /137 WA_EMP-FAMSA1,
147 WA_EMP-FAVOR1,
160 WA_EMP-FANAM1.
WRITE : /137 WA_EMP-FAMSA2,
147 WA_EMP-FAVOR2,
160 WA_EMP-FANAM2.
WRITE : /137 WA_EMP-FAMSA3,
147 WA_EMP-FAVOR3,
160 WA_EMP-FANAM3.
WRITE : /137 WA_EMP-FAMSA4,
147 WA_EMP-FAVOR4,
160 WA_EMP-FANAM4.
WRITE : /137 WA_EMP-FAMSA5,
147 WA_EMP-FAVOR5,
160 WA_EMP-FANAM5.
WRITE : /137 WA_EMP-FAMSA6,
147 WA_EMP-FAVOR6,
160 WA_EMP-FANAM6.
WRITE : /137 WA_EMP-FAMSA7,
147 WA_EMP-FAVOR7,
160 WA_EMP-FANAM7.
WRITE : /137 WA_EMP-FAMSA8,
147 WA_EMP-FAVOR8,
160 WA_EMP-FANAM8.
WRITE : /137 WA_EMP-FAMSA9,
147 WA_EMP-FAVOR9,
160 WA_EMP-FANAM9.
WRITE : /137 WA_EMP-FAMSA10,
147 WA_EMP-FAVOR10,
160 WA_EMP-FANAM10.
WRITE : /137 WA_EMP-FAMSA11,
147 WA_EMP-FAVOR11,
160 WA_EMP-FANAM11.
WRITE : /137 WA_EMP-FAMSA12,
147 WA_EMP-FAVOR12,
160 WA_EMP-FANAM12.
WRITE : /137 WA_EMP-FAMSA13,
147 WA_EMP-FAVOR13,
160 WA_EMP-FANAM13.
WRITE : /137 WA_EMP-FAMSA14,
147 WA_EMP-FAVOR14,
160 WA_EMP-FANAM14.
ULINE.
AT FIRST.
WRITE : /45 'TEMPORARY ADDRESS : ',
65 'STREET',
87 'POSTALCODE',
100 'CITY',
120 'COUNTRY'.
ULINE.
ENDAT.
WRITE : /65 WA_EMP-STRAS1,
87 WA_EMP-PSTLZ1,
100 WA_EMP-ORT011,
120 WA_EMP-LAND11.
ENDLOOP.
ENDFORM. " DISPLAY_DATA -
Standard IDoc / BAPI to get Employee Personal Details
Hi All,
Is there any Standard IDoc / BAPI to get Employee Personal Details like EMP-ID Name, Address in HR Modules.
Bye
Satish Reddycheck with this: bapi_persdata_getdetailedlist
-
How to Use Transient View Objects to Store Session-level Global Variables
hi
Please consider section "40.8.5 How to Use Transient View Objects to Store Session-level Global Variables"
at http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/bcstatemgmt.htm#ADFFD19610
Based on this documentation I created the example application
at http://www.consideringred.com/files/oracle/2010/ProgrammaticalViewObjectAndRollbackApp-v0.01.zip
It behaves as show in the screencast at http://screencast.com/t/qDvSQCgpvYdd
Its Application Module has a Transient View Object instance "MyEmployeesContextVOVI", as master for the child View Object instance "EmpInCtxJobVI".
On rollback the Transient View Object instance keeps its row and attribute values.
Also when passivation and activation is forced (using jbo.ampool.doampooling=false ) the Transient View Object instance seems to keep its row and attribute values.
questions:
- (q1) Why does the expression #{bindings.MyEmployeesContextVOVIIterator.dataControl.transactionDirty} evaluate as true when a Transient View Object instance attribute value is changed (as shown in screencast at http://screencast.com/t/qDvSQCgpvYdd )?
- (q2) What would be a robust approach to make a Transient View Object instance more self-contained, and manage itself to have only one single row (per instance) at all times (and as such removing the dependency on the Application Module prepareSession() as documented in "5. Create an empty row in the view object when a new user begins using the application module.")?
many thanks
Jan VerveckenThanks for your reply Frank.
q1) Does sample 90 help ? http://blogs.oracle.com/smuenchadf/examples/
Yes, the sample from Steve Muench does help, "90. Avoiding Dirtying the ADF Model Transaction When Transient Attributes are Set [10.1.3] "
at http://blogs.oracle.com/smuenchadf/examples/#90
It does point out a difference in marking transactions dirty by different layers of the framework, "... When any attribute's value is changed through an ADFM binding, the ADFM-layer transaction is marked as dirty. ...".
This can be illustrate with a small change in the example application
at http://www.consideringred.com/files/oracle/2010/ProgrammaticalViewObjectAndRollbackApp-v0.02.zip
It now shows the result of both these expressions on the page ...
#{bindings.MyEmployeesContextVOVIIterator.dataControl.transactionDirty}
#{bindings.MyEmployeesContextVOVIIterator.dataControl.dataProvider.transaction.dirty}... where one can be true and the other false respectively.
See also the screencast at http://screencast.com/t/k8vgNqdKgD
Similar to the sample from Steve Muench, another modification to the example application introduces MyCustomADFBCDataControl
at http://www.consideringred.com/files/oracle/2010/ProgrammaticalViewObjectAndRollbackApp-v0.03.zip
public class MyCustomADFBCDataControl
extends JUApplication
@Override
public void setTransactionModified()
ApplicationModule vApplicationModule = (ApplicationModule)getDataProvider();
Transaction vTransaction = vApplicationModule.getTransaction();
if (vTransaction.isDirty())
super.setTransactionModified();
}Resulting in what seems to be more consistent/expected transaction (dirty) information,
see also the screencast at http://screencast.com/t/756yCs1L1
Any feedback on why the ADF Model layer is so eager to mark a transaction dirty is always welcome.
Currently, question (q2) remains.
regards
Jan -
Dear Gurus,
In which infotype we can maintain for Employee Work Details like Project Name, Project Role, Project location, Area of Responsibility etc.,
Regards,
Ravi Kanth .GHI Ravi,
There is no such infotype where we can store these information.
We have to go for Z infotype.
Regards,
Kapil Kaushal -
Hi Experts,
How can we distinguish between any of the standard BW objects and a custom or a user defined infobject.
My understanding in this regard is that standard objects always starts with any number, and the custom or user defined objects are otherwise.
Pls provide me precise and detailed information, not simply links,
Useful answers will rewarded for sure,
Thanks,
Happy Life,
AravindHi Aravind,
All standard BW objects start with numeric number especially the business content starts with "0". The other ones are custom and they can start with any alpha character from A to Z.
Bye
Dinesh -
Standard table that stores communication channel parameters
Hi All,
Can you tell me if there is a standard table that stores the parameters of communication channel?
For example, Which table has the value of "Quality of Service" in "Processing Parameters"?
Regards,
NishaCan you tell me if there is a standard table that stores the parameters of communication channel?
not aware of a standard table....each communication has its own QOS.....you can check it in the log in SXMB_MONI....opne the particular message processing and look in the upper window (Window 1) where all the details are mentioned. -
HR Report shows Employee & Supervisor details
Hi All,
I have requirement were I have to display list of employees personal and position data along with his supervisor position data (like job class, class title) and also few personal data (like work phone).
Currently we have only the Personnel Actions and Headcount cube. How to display employee and its supervisor detail.
Do I need to create another data target to store employee and supervisor relationship?
Regards,
AnandHI,
I think there is no need to create supervisor data target.
Supervisor for any employee will be another employee so we have to maintain the data for the supervisor.
or we can onclude another field in the target where we can maintain this information.
Another appoach:
We can create supervisor master data infoobject where we can main tain data for supervisor and all the attributes of supervisor can be used in the reports.
You can follow any one of the above appoach.
Hope this will help you..
Thanks,
Jitendra -
Standard functionality of ESS Leave Request Details.
Hi Gurus,
Can anybody share the links of Standard functionality of ESS Leave Request Details..?
And,Is there any standard functionality in ESS Leave Requests that if a User raises a Leave Request and want to extend the leave...is there any rule that User First cancel the previous Leave Request and raise a New Leave Request .
Please explain briefly for the same.
Thanks,
Prakash.Prakash,
ESS Leave Request with WebDynpro technology:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/5b/76a6d7fd3a4e91bfb422405bf3e04d/frameset.htm
ESS Leave Request with ITS technology (old):
http://help.sap.com/erp2005_ehp_04/helpdata/EN/80/58dce8142711d289b50000e8216659/content.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/d9/359018129c11d3964400a0c930669b/content.htm
You've all the customizing in SPRO > Personnel Management > Employee Self-Service > Service-Specific Settings > Working Time > Leave Request
You define:
1) A Rule with certain settings
2) Absences/Attendances to display in ESS, with certain settings, and its assignation to a Rule
3) A WF (commonly based on standard 12300111) --even you could not use a WF, check customizing
4) Run process (manually or not) for analyze, correct and delete or save the entries finally in SAP through PTARQ transaction
And,Is there any standard functionality in ESS Leave Requests that if a User raises a Leave Request and want to extend the leave...is there any rule that User First cancel the previous Leave Request and raise a New Leave Request .
The employee can be able to cancel the request even when attendance/absence was approved. You define this behaviour for each Absence/Attendance in customizing.
Regards -
Decompiling employee bank details KFF into component fields
Hi
I've got a requirement to trigger off a standard letter within HRMS whenever one of our employee's bank details e.g. account number, sort code is updated. My thoughts on this were to put some logic in the CUSTOM.pll library linking it to the Pay Method form to track events there.
Our application setup has employee bank details saved in the GB Bank Details KFF which is visible on the Pay Method form; if the user clicks on the Bank Details field, it opens up a new window for updating the KFF where the data is split up into the component fields.
The problem I have is I need an elegant way to check on the values of that KFF in the form prior to it being saved and compare it to what's on the database to identify what has changed. I can resort to using the substring function to extract the pieces of data I need from the KFF but this is messy. Does anyone know of a better way of getting at the individual values of a KFF that I can use in the CUSTOM library?
Thanks
GeoffTry using either some of the FND routines or alternatively pick up the segment values from pay_external_accounts table.
I think its pretty simple unless of course I have got the requirement incorrect. -
How to find out Oracle 11i Standard Objects
Hi Gurus,
There is a requirement from my client. My client is on 11i Oracle Applications. He has many customization. But somehow he failed to use naming convention and all during implementation. Now he wants us to write a program which can tell us how many custom database objects are created as a part of implementation.
Hence in order to know this, first I need to find out what are the standard objects provided by Oracle for its 11i application so that I can write a program which will take difference (custom DB objects - standard Oracle 11i Object)
It will be great assistance if you let me know how to find out standard objects provided by Oracle for its 11i application?
Looking forward to your reply.
Thanks.
-SunilMoved to the EBS General Discussions forum
There is no easy or programmatic way to determine the custom objects. All custom objects need to be documented and need to follow the recommended XX naming convention. If that has not been done, then someone will have to manually input each object name that is possibly custom at https://etrm.oracle.com which documents all seeded objects - if no match is found, it is most likely a custom object.
HTH
Srini -
Re: [SunONE-JATO] Re: Using an object to store and display data
Personally, I think there is little or no value to creating a "domain"
object that itself relies on a JATO QueryModel internally, but hides that
fact and requires use of BeanAdapterModel.
It would be more appropriate (and much less work, and more scalable) to just
derive a QueryModel subclass and add the domain-specific behavior to the
model. In other words, what's the point of creating an object that hides
JATO inside it when you're running in JATO to begin with? Now if the domain
object were doing plain JDBC, and thus trying to be JATO independent, that
would be different. However, you could still implement the Model interface
on the object (or use BeanAdapterModel) to integrate it seamlessly with the
View tier.
Todd
----- Original Message -----
From: "grschroeder" <grschroeder@y...>
Sent: Wednesday, July 31, 2002 12:00 PM
Subject: [SunONE-JATO] Re: Using an object to store and display data
Craig,
I think it all finally makes sense. First, your assumption is
correct regarding the process flow. The ViewBean will interact with
a custom Javabean which will then in turn interact with a SQL Model
to access the database. So now let me make sure I understand what I
need to do. Basically the custom Javabean will have a method to get
the SQLModel. I would then invoke the setValue method on the
SQLModel and call the appropriate execute method( e.g.,
executeUpdate, etc. ) just like I would do from a ViewBean. Does
this sound correct?
Thanks,
Greg
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
Greg,
see below...
grschroeder wrote:
Thanks for the help Craig. I looked at the sample code that makes
use of the BeanAdapterModel. Basically it looks like it allows a
view to interact with a bean the same way it would interact with
any
other model. That part I think I understand.
This is correct.
The part I'm a little
unclear on still is how to interface this BeanAdapterModel( which
is
a very basic model ) that I now have with a query model toactually
interact with the database.
Not sure what you mean by "interface this BeanAdapterModel ... witha
query model". Does this mean that you have a ViewBean the interactswith
a custom JavaBean via the BeanAdpterModel wrapper, and from the
JavaBean you are interacting with the SQL Model?
So it looks like this: ViewBean > BeanAdapterModel(Custom JavaBean)
SQL Model > RDBMS
That's what I am reading anyway. Please explain this to me.
Would I need to make direct JDBC calls
from my custom model instead of letting JATO dynamically create
the
calls for me?
If my assumptions above are correct, then the custom JavaBean cansimply
use the SQL Model in exactly the same manner as the ViewBean,otherwise,
if no SQL Model is involved, then yes, you need to handle JDBCdirectly,
which is fine, if you do it "right" (connection pooling, result set
handling, etc.).
Thanks,
Greg
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
I think the best approach would be to treat your Domain Objects
(DO) as
the Database (the enterprise tier) from JATO's perspective. You
could
create custom models that interface with our DO's and then the
JATO
Views could easily bind to the custom DO models just like anyother
model. This should eliminate the need for pushing data/objectsfrom
>
view
to model to database.
There is a JATO class called BeanAdapterModel that might be just
what
you need, however, I am not experienced with using it. Maybe
someone
else on my team or in the community could better explain how to
use
>
this
class.
craig
grschroeder wrote:
Venki,
Thanks for the response. Actually, I'm not sure if I can answer
all
of your questions because those are some of the same questions
that
we're trying to answer ourselves. Basically, what we're trying
to
>do
is incorporate our domain object model into the JATO framework.
My
thinking was that one way we could accomplish this was by
storing
>a
Javabean object in the HTTPSession to represent an object in the
domain model, and that the Viewbean and JATO Model could get and
set
data from there. If you have a better suggestion of how to
accomplish this, I'm definitely open to hearing it.
Thanks,
Greg
--- In SunONE-JATO@y..., Venki <heyvenki@y...> wrote:
OK grschroeder , first let me get this straight:
0. Are you going to pass this object to the model, or are u
going
>
to pass the session object to the model?
1. Is there any specific reason for this approach you are
taking?
2. Will there be a notification from the object u havementioned
>to
have the model persist the data?
3. What about the reverse case, when the model refreshes the
data,
how are you going to refresh you object?
4. The JavaBean Object that u are talking about, is it your own
object or is it implementation of an existing JATO interface?
~Venki
grschroeder wrote:I'm fairly new to JATO, but I think I now
have
>a
basic understanding
of how Viewbeans and Models interact. However, I want to
incorporate
the use of a Javabean object that will be stored in the HTTP
session
and will act as the connection between the Viewbean and Model
instead
of having the Viewbean and Model interact directly with each
other.
Basically I would like to have the Model set data in the object
stored in the session so that the Viewbean can pull it out to
display
it. And vice versa, once the user modifies the data and is
ready
>
to
persist it, I would like to have the Viewbean set data in the
object
stored in the session so that the Model can pull it out to
store
>it
in the database. I'm not sure what the best approach would be
to
accomplish this. Any help you could give would be greatly
appreciated.
Thanks,
Greg
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
Service.
Venki
IT Solutions
#6, Pycrofts Garden Road, Nugambakkam, Chennai - 600 006
91-44-4925740(Home) 91-44-8212877(Work)
* Luck is what happens when Preparation meets Opportunity.
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
>To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jspPersonally, I think there is little or no value to creating a "domain"
object that itself relies on a JATO QueryModel internally, but hides that
fact and requires use of BeanAdapterModel.
It would be more appropriate (and much less work, and more scalable) to just
derive a QueryModel subclass and add the domain-specific behavior to the
model. In other words, what's the point of creating an object that hides
JATO inside it when you're running in JATO to begin with? Now if the domain
object were doing plain JDBC, and thus trying to be JATO independent, that
would be different. However, you could still implement the Model interface
on the object (or use BeanAdapterModel) to integrate it seamlessly with the
View tier.
Todd
----- Original Message -----
From: "grschroeder" <grschroeder@y...>
Sent: Wednesday, July 31, 2002 12:00 PM
Subject: [SunONE-JATO] Re: Using an object to store and display data
Craig,
I think it all finally makes sense. First, your assumption is
correct regarding the process flow. The ViewBean will interact with
a custom Javabean which will then in turn interact with a SQL Model
to access the database. So now let me make sure I understand what I
need to do. Basically the custom Javabean will have a method to get
the SQLModel. I would then invoke the setValue method on the
SQLModel and call the appropriate execute method( e.g.,
executeUpdate, etc. ) just like I would do from a ViewBean. Does
this sound correct?
Thanks,
Greg
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
Greg,
see below...
grschroeder wrote:
Thanks for the help Craig. I looked at the sample code that makes
use of the BeanAdapterModel. Basically it looks like it allows a
view to interact with a bean the same way it would interact with
any
other model. That part I think I understand.
This is correct.
The part I'm a little
unclear on still is how to interface this BeanAdapterModel( which
is
a very basic model ) that I now have with a query model toactually
interact with the database.
Not sure what you mean by "interface this BeanAdapterModel ... witha
query model". Does this mean that you have a ViewBean the interactswith
a custom JavaBean via the BeanAdpterModel wrapper, and from the
JavaBean you are interacting with the SQL Model?
So it looks like this: ViewBean > BeanAdapterModel(Custom JavaBean)
SQL Model > RDBMS
That's what I am reading anyway. Please explain this to me.
Would I need to make direct JDBC calls
from my custom model instead of letting JATO dynamically create
the
calls for me?
If my assumptions above are correct, then the custom JavaBean cansimply
use the SQL Model in exactly the same manner as the ViewBean,otherwise,
if no SQL Model is involved, then yes, you need to handle JDBCdirectly,
which is fine, if you do it "right" (connection pooling, result set
handling, etc.).
Thanks,
Greg
--- In SunONE-JATO@y..., "Craig V. Conover" <craig.conover@s...>
wrote:
I think the best approach would be to treat your Domain Objects
(DO) as
the Database (the enterprise tier) from JATO's perspective. You
could
create custom models that interface with our DO's and then the
JATO
Views could easily bind to the custom DO models just like anyother
model. This should eliminate the need for pushing data/objectsfrom
>
view
to model to database.
There is a JATO class called BeanAdapterModel that might be just
what
you need, however, I am not experienced with using it. Maybe
someone
else on my team or in the community could better explain how to
use
>
this
class.
craig
grschroeder wrote:
Venki,
Thanks for the response. Actually, I'm not sure if I can answer
all
of your questions because those are some of the same questions
that
we're trying to answer ourselves. Basically, what we're trying
to
>do
is incorporate our domain object model into the JATO framework.
My
thinking was that one way we could accomplish this was by
storing
>a
Javabean object in the HTTPSession to represent an object in the
domain model, and that the Viewbean and JATO Model could get and
set
data from there. If you have a better suggestion of how to
accomplish this, I'm definitely open to hearing it.
Thanks,
Greg
--- In SunONE-JATO@y..., Venki <heyvenki@y...> wrote:
OK grschroeder , first let me get this straight:
0. Are you going to pass this object to the model, or are u
going
>
to pass the session object to the model?
1. Is there any specific reason for this approach you are
taking?
2. Will there be a notification from the object u havementioned
>to
have the model persist the data?
3. What about the reverse case, when the model refreshes the
data,
how are you going to refresh you object?
4. The JavaBean Object that u are talking about, is it your own
object or is it implementation of an existing JATO interface?
~Venki
grschroeder wrote:I'm fairly new to JATO, but I think I now
have
>a
basic understanding
of how Viewbeans and Models interact. However, I want to
incorporate
the use of a Javabean object that will be stored in the HTTP
session
and will act as the connection between the Viewbean and Model
instead
of having the Viewbean and Model interact directly with each
other.
Basically I would like to have the Model set data in the object
stored in the session so that the Viewbean can pull it out to
display
it. And vice versa, once the user modifies the data and is
ready
>
to
persist it, I would like to have the Viewbean set data in the
object
stored in the session so that the Model can pull it out to
store
>it
in the database. I'm not sure what the best approach would be
to
accomplish this. Any help you could give would be greatly
appreciated.
Thanks,
Greg
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
Service.
Venki
IT Solutions
#6, Pycrofts Garden Road, Nugambakkam, Chennai - 600 006
91-44-4925740(Home) 91-44-8212877(Work)
* Luck is what happens when Preparation meets Opportunity.
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
>To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp
To download the latest version of JATO, please visit:
http://www.sun.com/software/download/developer/5102.html
For more information about JATO, please visit:
http://developer.iplanet.com/tech/appserver/framework/index.jsp -
LSMW Standard object for class
hi,
I am trying to upload class data through LSMW standard object,0140,
but while specifying file step it is giving error , No logical path has been specified.
how to solve this problem.
RegardsI repeatedly do this with LSMW by recording method. (recording done once and using repeatedly)
The recorded template is
EQUNR KLART CLASS_01 STDCL_01
If it is the case of Functional Location TPLNR in place of EQUNR.
May try this way.
Regards
Jogeswara Rao -
How to track changes made to the standard objects by SAP during upgrade ?
Hi All,
Can any one of you please let me know if there is any straight forward method to find any change made to the standard objects by SAP in different versions ?
Like for eg, during upgrade from 4.6c to ECC 6.0.
Thanks in advance.> For eg , if SAP has made any change in the standard transaction IE02, in ECC 6.0 how will we come to know those changes?
There are two sources for that:
The "Solution Browser" (http://solutionbrowser.erp.sap.fmpmedia.com/) which lists the differences between source and destination release and the release notes (http://service.sap.com/releasenotes). You'd need to read here all those from 4.6 to ERP 6.0 (so 4.7, ECC 5.0 and ERP 6.0) to find out the behaviour changes.
Markus -
Query to find Employee Salary Details
Hi,
Could anyone help in writing the query to find employee salary details.
Thanks in advance.This should get you started:
SELECT papf.full_name
,papf.email_address
,ppp.proposed_salary_n salary
FROM per_pay_proposals ppp
,per_all_assignments_f paaf
,per_all_people_f papf
WHERE ppp.assignment_id = paaf.assignment_id
AND paaf.assignment_type = 'E'
AND paaf.primary_flag = 'Y'
AND paaf.person_id = papf.person_id
AND nvl(papf.current_employee_flag, 'N') = 'Y'
AND trunc(sysdate) BETWEEN
ppp.change_date AND ppp.date_to
AND trunc(sysdate) BETWEEN
paaf.effective_start_date AND paaf.effective_end_date
AND trunc(sysdate) BETWEEN
papf.effective_start_date AND papf.effective_end_date;
Maybe you are looking for
-
How do I create an "executable" for users to run calcs?
I need to create an executable that users can launch. I would like it to 1) log in as a "test" user that I have set up in Native Directory, 2) select app/database then 3) launch a series of calcs. I had something set up previously in an earlier ver
-
Why I'm not able to create my account?
Hi, I'm trying to create my account for Itunes, It just don't work. I From Brasil and I have an international credit card. But I just can't type my address. It force me to give an American Address. So I try to create my pay-pal account, and I have th
-
Every time i turn my touch on, a long code scrolls down the screen and then i can't do anything else. My computer also doesn't detect it when plugged in
-
Hi all, I have maintained exchange rate type 'M' for daily transaction and 'T' for Tax calculation. But the problem, when I want to clear tax transaction with T-code F-04, the amount is translated with exchange rate type 'M'. How can I change this tr
-
Hi I have a situation where in am not able to send emails to a vendor from ME22N I get the following error "E-mail address incorrect or non-existent". This issue is particular to a vendor,the email id maintained for the vendor is a valid one too. Ema