I will use this Wiki Space for my session content for TechEd09@Phoenix - Session CD205 - Tips and Tricks to Learn and Leverage Newer Technologies. I ended up using the ABAP Development category although the content is much more broader than just ABAP. I wish there was a category called 'NetWeaver Development' without any sub-categories. I will keep this wiki updated daily (at least till my session @ TechEd).

 The purpose of this wiki is to try and build a well-rounded 'NetWeaver Developer' - someone who can work on traditional and the newest features of ABAP, BW, BI, PI, Portals and can go across different solution sets such as ECC, SCM, SRM, MDM, GRC etc.

 Learning points from the session (now the Wiki):

Developers, especially ABAP developers, will be able to:

Understand SAP NetWeaver  technologies
Leverage newer technologies for best business benefits
Create a Plan to learn newer development tools
Leverage NETWEAVER Technology platform to it's fullest potential

Managers will be able to:

Plan on best use of their technical resources
Plan on best use of SAP tools

Reason behind this session

• Thought process behind this session - the need for a well rounded NetWeaver Technology Developer
• A Challenging Economy
• Companies are looking for developers who can do more than just traditional ABAP
• The winners are people who can deliver above and beyond...
   

Classic ABAP Skills:
Reports (Lists, ALV etc)
Screen Painter, Menu Painter
SAP Scripts, SMART Forms
BDCs / LSMW
RFCs / FMs
User Exits
Internet Transaction Server (IACs / Internet Services)
IDOCs

• Skills that Developers will need moving forward:

Apart from the classic / traditional skills, Classic / Traditional Developers need skills on:
Object Oriented Programming
Workflow (considered a classic) - many flavors available now
Adobe Interactive / PDF Forms
SAP Internet communication framework (SICF)
HTTP Services
BSPs (Still around and may continue to be there)
WebDynpro (ABAP or Java)
Enterprise Services (Publish and Consume)
                                                                      
       .....and that may not be enough

Cross Application Integration Skills:

IDOCs / BAPIs/ RFCs (Classic)
Enterprise services
XML Mapping (Simple Transformations or XSLT)
CIF (for Integration with SCM)
      .....and that may not be enough

NetWeaver Portal Skills:

Creating Visual Composer Models
General Know-how (iViews, Pages, Worksets, Roles)
System Configuration
Enabling SSO between different SAP systems
Web Page Composer
Collaboration rooms (Basic functionality)
Knowledge Management (Basic functionality)

Advanced - Setting up external facing portal
   -  AD / LDAP Integration with Portal

SAP BW

Reporting (Creating Queries, Workbooks)
General know-how of BEx and Web Analyzer
Creating filters / variables etc in BEx
Transfer a Transparent table to BW (generic data source)
Create and Broadcast Reports / Workbooks
Developing Extractors
Enhancing standard extractors
Create Dashboards using Visual composer / Web Application Designer
Publish to NetWeaver Portal / Collaboration rooms

SAP BI

General Know-how of:
Crystal Reports
xCelsius
Webi (Web Intelligence)
Explorer (Polestar)

NetWeaver PI (Process Integration)

Learn basics of B2b
Different channels for communication
Interface mapping, Messages etc

Refer to the PI handbook

Governance, Risk and Compliance

Niche Market

General Know-how of:
Segregation of Duties
Risk management
Mitigation Controls

At some point in the future, Developers will be evaluated based on their security skills. It's strange but true...

Other Areas to consider:

CRM
SRM
MDM
SNC (Supplier Network Collaboration)

General Know-How of Key Business Processes:

Procure-to-Pay
Order-to-Cash
Manufacturing / Shop Floor Control
Master Data Management

 Lest we forget....

Communication Skills
Team Player
Mentor

Web 2.0 Skills...

Blogs, Forums, Wikis, Mashups

Traditional Training

Books / CDs

Magazines

Training Sessions

Conferences

Modern Day Training (Traditional Training plus the ones below):

Online Help

Blogs

Wikis

Forums

User Communities

Other Web 2.0 tools...

Introducing the Daily Action Requests:

• The 'Daily action list' (DAL) is a list of tasks, that are logically grouped and are usually completed sequentially. All tasks in the list may not be completed same day, but the important thing is that it should be started as planned and completed on time. For e.g. 'Learn WebDynpro' is a task on the DAL, but will take at least 3 to 4 days to complete.
• Tasks should be logically grouped - for e.g. Do not combine a NW Process Integration (PI) task with BW or NW Portal. It will only make the learning process more difficult. Instead, choose related tasks and group them together.
• The DAL should be reviewed at the beginning of the day. It may not be 100% complete for the previous day, but it's important to know that something is pending and the DAL should be adjusted accordingly.
• The success or failure of this approach does not depend on the mere completion of the task - instead it depends on how well one has assimilated the contents of each task. Remember, it's an iterative process - hence, review the previous day's contents and repeat this process at least once in 3 months.
• Do not let failure or incompletion of a few tasks bother you. Instead, dedicate more time in the following days and make up for the lost time. Do not procrastinate - you will never be able to catch up again.

Key success factors:
 - Be realistic and not be overambitious
 - Update action lists in a timely manner
 - Provide for contingency time for the unexpected

- Discuss among teams

- Hold training sessions among team members