BOR - How to instantiate EMPLOYEEI, EMPLOYEESU, ABSENCE, etc

[Cristiana D'Agosto]

Solved! I knew it was something that I have forgotten to do.

My BOR didn't exist in table T777IBO, therefore the method couldn't not 
work out that ZINFT0019 is linked to Infotype 0019.

Thanks for all the good ideas anyway!

Cheers,

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services




"Dart, Jocelyn" <jocelyn.dart at sap.com> 
Sent by: sap-wug-bounces at mit.edu
29/06/2007 09:37 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>


To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
RE: BOR - How to instantiate EMPLOYEEI, EMPLOYEESU, ABSENCE, etc






Well Cristina, If you are on ECC 6.0  how about... ditching the BOR 
altogether and creating ABAP OO classess instead of BOR object types.  You 
can then call HR_READ_INFOTYPE or the equivalent BAPI where available 
(e.g. BAPI_EMPLOYEE_GETDATA, BAPI_EMPLCOMM_GETDETAILEDLIST) from your 
class, completely control whether HR Structural authorisation is used or 
not, and not have to deal with a whole heap of historical red herrings 
from EMPLOYEET and BUS1065. 
 
Cristina I know you are an ABAP-er - read my blogs on ABAP OO for Workflow 
and you will find it is very simple to put a class together quickly. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Cristiana D'Agosto
Sent: Thu 28/06/2007 3:10 PM
To: SAP Workflow Users' Group
Subject: RE: BOR - How to instantiate EMPLOYEEI, EMPLOYEESU, ABSENCE, etc



Hello Jocelyn, 

I changed it as you suggested, logged out, logged on again and still get 
the message 'Object does not exist'. 

We are on ECC 6.0 

Any other ideas? My new object was created by copying from EMPLOYEESU 
(just like we did at Dept of Housing - gee that was sooooo long ago!) - I 
generated the object, saved, refreshed buffers, the works. 

Cheers,

Cristiana
_________________________________
Cristiana d'Agosto
IBM Global Business Services




"Dart, Jocelyn" <jocelyn.dart at sap.com> 
Sent by: sap-wug-bounces at mit.edu 

28/06/2007 02:44 PM 
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>


To
"SAP Workflow Users' Group" <sap-wug at mit.edu> 
cc
Subject
RE: BOR - How to instantiate EMPLOYEEI, EMPLOYEESU, ABSENCE, etc  

 




Cristina, Check HR structural authorizations aren't killing you.  Put 
yourself in table T77UA with profile ALL. 
Jocelyn

________________________________

From: sap-wug-bounces at mit.edu on behalf of Cristiana D'Agosto
Sent: Thu 28/06/2007 10:07 AM
To: SAP Workflow Users' Group
Subject: BOR - How to instantiate EMPLOYEEI, EMPLOYEESU, ABSENCE, etc



Hi all, 

i am sure this is something silly that I might be forgetting to do... 

Several of the HR Objects have the following key: 
Personnel number 
Subtype 
Object ID 
Lock indicator 
To 
>From 
Record number 

I have created a new object type to represent Infotype 0019 and set the 
key as above. I checked table PA0019 and entered the appropriated values 
in the attributes when I tried to Create Instance via SWO1. 

I am in SWO1 and trying to 'test' the new object type but not getting 
anywhere. I then tried to instantiate the SAP delivered ones (i.e. 
EMPLOYEEI, EMPLOYEESU, ABSENCE) and getting nowhere as well. 

Any ideas on what I might be missing? 

Sorry if this is a silly question & thanks for any help! 

Cheers

Cristiana


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070629/73b61d8b/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/octet-stream
Size: 6633 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20070629/73b61d8b/attachment.obj