Big4Guy
Big4GuyWelcome to Big4Guy.com. Big4Guy is an online resource where I will share with you the latest news, insights, knowledge and some experiences as a Big 4 consultant. We will discuss some of the important issues which organisations are facing today in the areas of information security, security and controls in SAP R/3, Oracle Applications, J.D.Edwards, Peoplesoft and various other ERP's. You will also find information on latest complaince regulations like Sarbanes Oxley, Basel II and so on. Big4guy will also attempt to provide valuable resources for individuals interested in examinations the CISA, CISM, CISSP, PMP and various other security certifications considered essential for entry in any Big 4 accounting, auditing and consulting firms. You are invited to post your comments and viewpoints to posts here. I sincerely hope this online journal will be useful to everyone from a budding student to a professional in the accounting, auditing, management and consultancy professions.
|
Post details: SAP R3 ODE Objects in Development Environment
12/19/06
07:36:32 pm, Categories: SAP R/3 Technical Interview Questions & Answers, Advanced Level Questions, SAP R/3, 194 words 
SAP R3 ODE Objects in Development Environment
ODEs in SAP R3 paralance mean objects in development environment. ODE is a functionality within the SAP SAP WBOT workbench organizer and transport system. It is important to understand the pervasive effect of ODE. ODEs are valid system wide as a result, it is important to keep the test and production SAP systems seperate. Many readers here have asked as to how a system change is implemented in SAP R3.
To answer the above question, the WBOT workbench organizer and transport system, keeps a system log of all changes. This history file acts as a reference is changes need to be rolled back. Also, WBOT uses a locking functionality to avoid changes made by multiple SAP developers. SAP developers should also be cautious of Once changenaming conventions they use for ODEs. SAP naming conventions should be used as a best practices. i.e. ODEs are developed, they need to be tested adequately to ensure it is working as desired. The user access testing needs to be performed by the user requesting the change.
Related Posts
Key Milestones in ERP Implementation
SAP Questions & Answers Database
Change Documents in SAP R/3
Breakpoints in SAP R/3
Comments:
No Comments for this post yet...
Categories
Archives
Search
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| << < | > >> | |||||
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||
Misc
All content copyright © 2005-2008
Big4Guy.com
Do not reproduce either in part or full without the express permission of the
Webmaster
