Enterprise Resource Planning, Design, and Implementation

Instructor: Richard W. Vawter ITP 454x, Fall 2009

Office: OHE 530B Location: OHE 406

E-Mail: vawter@usc.edu Thurs. 5:00-8:00 p.m.

Phone: (213) 740-9541

Office Hours: Mon. 11:00 - 12:00 p.m. Class Web Page:

2:00 - 4:00 p.m. http://www-rcf.usc.edu/~vawter/classes.html

Tues. 11:10 - 12:00 p.m. or

Wed. 10:30 - 12:00 p.m. http://blackboard.usc.edu/

Thurs. 10:30 - 12:00 p.m.

or by appointment

Course Description:

This course takes an in-depth look at the process and requirements necessary to implement an Enterprise Resource Planning System (ERP) for an organization. The Accelerated SAP method (as outlined by the ERP tool SAP) will be followed throughout the semester. Students will first be grouped into small project teams. Each team will be responsible for setting up a Windows Server system and monitoring that server system during the semester. The teams will then implement onto the servers an ERP system used for coordinating an organization's activities. The final tasks performed by the teams will be the transportation of data from a case company's legacy system into the newly implemented ERP system and the configuration of that ERP system to model the case company's Customer Order process.

Suggested Textbooks:

All other necessary material will be provided to you in class.

Class Schedule:

Class		Topic		Class Assignment		Lab Assignment
1. Aug. 27		Course Overview Review: Customer order mgnt. process		Class notes on the COM process		Project #1 – The COM process. Due Sept. 3.
2. Sept. 3		ASAP Overview		Class notes on ASAP		Project #2 – ASAP Overview. Due Sept. 17.
3. Sept. 10		ASAP (cont.)		Handout: R/3 Imple-mentation Guide		Continue w/ Project #2, due Sept. 17.
	4. Sept. 17		Installation Concepts: Planning for an R/3 installation		Class notes: ERP Planning & Preparation.		Setup Server OS. Planning Worksheet due Sept. 24. Project #3 – R/3 4.7 Implementation Due Wed, Oct. 7.
	5. Sept. 24		Installing the R/3 System		Continue with the R/3 Implementation Guide.		Continue w/ Project #3. Set up Oracle Db Load R/3 software
	6. Oct. 1		Post Implementation Procedures		Handout: Installing the SAP GUI and Setting Profile Files		Fine tune & check your R/3 System. Install GUI. Due Wed., Oct. 7.
	7. Oct. 8		Exam 1 Continue with Post Installation activities: Upgrade Kernel and Load patches		Handout: Installing Patches		Upgrade kernel and add all patches to get R/3 system up to date
	8. Oct. 15		System Monitoring and Performance tools. Client Copies.		Class notes: System Monitoring Handouts: List of Transactions for Daily Check and Performance Roadmap Handouts: SAPDBA and Client Copy		Project #4 – Install the pre-configured client. Due Wed., Oct. 28. Project #5 – System Monitoring. Due Oct. 22.
	9. Oct. 22		System Administration and Security Issues. Importing Best Practices.		Class notes: System Administration Handouts: Pre-BP Install and J00, J01, & J30		Continue w/ pre-configured client (Project #5). Project #6 – System Administration. Due Wed., Oct. 28.
	10. Oct. 29		Exam 2 Configuration and the IMG		Class notes: Configuration Handouts: Post BP Installation Configuration		Complete importing the Best Practices programs Begin configuring the new client based on the case company's requirements.
	11. Nov. 5		Configuration (cont.)		Handout: Testing the System Configuration for COM		Continue configuring the new client. Test the system by completing a Customer Order.
	12. Nov. 12		Data Transfer Overview		Class notes on data transfer strategies.		Finish the configuration. Test the system by com-pleting a Customer Order. Project #7 – Transferring Legacy Data to your new system. Due Wed, Nov. 25 by 5:00 pm.
	13. Nov. 19		Performing the Data Transfer step		Handout: Data Transfer Made Easy.		Continue working on Project #7. Due Wed., Nov. 25 by 5:00 pm
	14. Nov. 26		*Thanksgiving Holiday* No class		No reading assignment Final system preparation		Final Preparation for COM. (Run Project #1)
	15. Dec. 3		Course Review		GO LIVE !		Implementation Notebook is due. Final system test.

Lab Projects: · In the fourth week of class, you will be grouped into teams of four for setting up and implementing an R/3 system.

· Your team will be assigned a machine that you will be responsible for during the semester. At the end of the semester, your team's system will be tested to verify its integrity and ability to complete a standard customer order, including creating a delivery document, an invoice, and collecting/recording payment for the order.

· During the semester, projects will be assigned to provide you with practical information needed, and to guide you through the implementation process.

· Some of the projects are to be worked on individually; other projects can be worked on as a team. Each project will explain how it is to be completed.

· It is your responsibility (or in some cases, your team's responsibility) to submit the lab projects to the class blackboard assignment’s page before the beginning of lecture on the dates indicated on the class schedule. You will not have time to complete the project during class on the date the project is due!

· Late projects will automatically have 50% of the possible points deducted prior to grading. So, please turn in your projects on time!

· No projects will be accepted after 2 weeks beyond the project’s original due date or after the last day of the semester (Dec. 4).

Implementation: Each team is responsible for putting together a notebook, the purpose of which would

Notebook be to aid in the installation of an R/3 System upon a Windows - Oracle platform. At minimum, the notebook should contain:

· Steps in setting up a Windows server including issues & decisions made.

· Steps in implementing the R/3 System including problems encountered and the appropriate release notes.

· Information on installing a pre-configured client.

· Notes on administering and monitoring the R/3 system.

· Notes on transferring data from a legacy system to your R/3 System.

Additional items that should be included in the notebook will be mentioned in class during the semester.

Examinations: There will be two exams and a final covering material from the reading assignments, lectures, and lab projects. They will be of the form: multiple-choice, true/false, and short answer. The exams will be both closed book and closed notes. The final exam will focus on material presented during the last third of the semester but will also include a review of material from the first two thirds of the semester. In addition, there will be a final check of your R/3 system on the last day of class - something that your team will be working toward during the entire semester.

· Exam 1: Thursday, Oct. 8, 5:00-6:00 p.m.

· Exam 2: Thursday, Oct. 29, 5:00-6:00 p.m.

· Final exam: Thursday, Dec. 10, 4:30-6:30 p.m.

Note: No make-up exams will be offered nor will there be any changes made to the Final Exam schedule as established by the University.

Grading: Grading Scale:

Ave. of all Lab Projects 20% 94% and above A

Final System Check 20% 90% - 94% (not including 94%) A-

Exam 1 10% 87% - 90% (not including 90%) B+

Exam 2 15% 83% - 87% (not including 87%) B

Final Exam 20% etc.

Lab Notebook 10%

Inner-team Evals 5%

100%

Students with Disabilities:

Any student requesting academic accommodations based on a disability is required to register with Disability Services and Programs (DSP) each semester. A letter of verification for approved accommodations can be obtained from DSP. Please be sure the letter is delivered to me (or to your lab assistant) as early in the semester as possible. DSP is located in STU 301 and is open 8:30 a.m. - 5:00 p.m., Monday through Friday. The phone number for DSP is (213) 740-0776.

Student Conduct: (Excerpts taken from SC Campus Student Guidebook, 04/05)

§11.00 Behavior Violating University Standards and Appropriate Sanctions

“…individual work will be submitted [by the student], and [it’s the student’s] obligation both to protect one’s own academic work from misuse by others as well as to avoid using another’s work as one’s own.”

§11.11 Plagiarism (Definition)

“The submission of material authored by another person but represented as the student’s own work, whether that material is paraphrased or copied in verbatim or near verbatim form.”

§11.14 Plagiarism (Definition continued)

“Obtaining for oneself, or providing for another person a solution to a homework project or other assignments, or a copy of an exam or exam key without the knowledge and expressed consent of the instructor.”

“Students are expected to make themselves aware of and abide by the university community’s standards of behavior as articulated by the Student Conduct Code.”

Any violation will be immediately reported to the Office of Student Judicial Affairs and Community Standards. The alleged violation will then be reviewed by the board. If the student is determined to be responsible for the violation, appropriate disciplinary action will be determined and then implemented by the University.