Although I started working with SAP in 2000, I didn’t get around to doing my ABAP Certification till 2005. My second assignment after certification was to rewrite an SAP report-writer transaction in ABAP Objects, and this was a great assignment because it made me really think about SAP’s “project/wbs/network/activity” backbone that I had previously taken for granted. In particular, suppose there’s a big project P with lots of sub-projects with lots of wbs’s with lots of sub-wbs’s associated with lots of networks associated with lots of activities. Can SAP’s current role-based/transaction based security be configured “out-of-the-box” to permit a given staff-member to access information on certain sub-projects or wbs’s or sub-wbs’s or networks and/or activities within the project P, but not information on other sub-projects or wbs’s or sub-wbs’s or networks or activities within the project P? If so, then could someone explain how? (25 words or less, of course.)** But if not, then it seems to me that a piece of software that protects project sub-areas in this way would be a “gimme” for the SAP marketing and sales teams, because it’s so easy to play on guilt, fear, and paranoia when trying to market and sell this kind of thing. **Please note that I don’t mean using transaction-based or role-based security to protect certain types of materials. I mean keeping a staff-member from accessing the same type of material in one sub-project but allowing this access in a different sub-project (for example).