Design Avant! Integration for HR Recruitment Integration

© 2001 Synopsys, Inc. (2) CONFIDENTIAL Agenda Background Current Process Option 0: Description, Pros and Cons Option 1: Description, Pros and Cons Option 2: Description, Pros and Cons Recommendation

© 2001 Synopsys, Inc. (3) CONFIDENTIAL Background For integration of Avant! employees, following activities are necessary Resume tracking Interviewing Employment Offer Authorization Offer Acceptance Incoming and Hiring process As system enhancements are necessary, they can be made in a way to accomplish ongoing integration between recruitment system and Personnel Administration within SAP Three options have been discussed within the team and are presented here along with pros and cons.

© 2001 Synopsys, Inc. (4) CONFIDENTIAL Current Process

© 2001 Synopsys, Inc. (5) CONFIDENTIAL Goals of Integration Eliminate manual re-entry of applicant data in the incoming form - get the data from recruitment information automatically Eliminate manual re-entry of new hire data in the Hire Event in SAP. Obtain as much data as possible from applicant and from incoming form Link the position and requisition information and streamline the process of position creation and requisition approval. Position should start in SAP and should be fed to Employ! and Employ! should create the requisition in reference to the position.

© 2001 Synopsys, Inc. (6) CONFIDENTIAL Option 0 - One-time upload programs Maintain system functionality status quo; Develop batch programs to  create requisitions in Employ!,  upload applicant data into Employ! from Avant! Data,  download selected candidates information from Employ! and add incoming data to it  upload applicant data into SAP HR Level of Effort  9 Person weeks for Employ! (to be confirmed)  4 Person weeks for SAP ABAP (to be confirmed) Pros  No system functionality changes Cons  Throw-away effort

© 2001 Synopsys, Inc. (7) CONFIDENTIAL Option 1 - Integration with existing systems

© 2001 Synopsys, Inc. (8) CONFIDENTIAL Option 1 - Integration with existing systems Description  Continue to create and approve requisitions in Employ!  Build an open-ended interface (service) in SAP HR using Business Connector for hiring an employee.  Modify the incoming form and Employ! to automatically identify accepted and to-be-hired candidates from Employ! and transfer them to SAP Level of Efforts  SAP BC Service - 3 person weeks using Idoc Config (TBC)  Incoming and Employ! interfaces - 4 person weeks (TBC) Pros  Re-usable effort  Integration Cons  Position not linked with Requisitions

© 2001 Synopsys, Inc. (9) CONFIDENTIAL Option 2 - Integration using SAP Recruitment

© 2001 Synopsys, Inc. (10) CONFIDENTIAL Option 2 - Integration using SAP Recruitment Description  Position approval done in SAP  Employ! handles interviewing and transfers selected candidate to SAP for offer generation Level of Efforts  SAP Recruitment Config - 3 person weeks (TBC)  Position transfer interface (TBD)  Applicant transfer interface (TBD)  Position approval front end if licenses for all managers is not possible Pros  Integration  Position always originates in SAP and is linked to requisition  Incoming forms runs off SAP data  SAP reports show full information about open reqs and filled reqs Cons  More effort  SAP licenses may be required for Recruiters and Staffing Admins for SAP Recruitment

© 2001 Synopsys, Inc. (11) CONFIDENTIAL Recommendations Option 2, due to streamlined process and best use of strengths in both systems. Feasibility of Applicant Transfer is already investigated. Feasibility of Position Approval and transfer to Employ! will need to be verified

© 2001 Synopsys, Inc. (12) CONFIDENTIAL Next Steps Detailed feasibility analysis for interface and effort estimates Budget Request