For the element that’s text cannot be hardcoded or the element that’s visibility needs to change during runtime, the context needs to be used. The data that is seen on the screen is not stored within the web browser itself. The Web Dynpro application makes calls to the server to retrieve data to be displayed. This is where the context comes into play. The context is the memory on the server that stores data for the Web Dynpro application. When setup correctly a context can hold tables, structures or single element variables. Here is an example of how to build a context and then make method calls to read or set the context.

Select the ‘Context’ tab. Right click on the context node and select ‘Create’ -> ‘Node’ and fill out the fields according to the picture below.

Right click on the BUTTON_PROPERTIES node and select ‘Create’ -> ‘Attribute.’

Now we have created an attribute in the context that will hold a string value. By the names I have given to the node and the attribute you can guess that this node will hold any attributes related to the button we created. The attribute that we created will be used to hold text value of the button.

Now that the context attribute has been created, let’s fill it with a value. Go back to the button properties under the ‘Layout’ tab and find the ‘onAction’ properties under ‘Events.’ Click the create button, it looks like a white piece of paper with the top right edge folded down, and fill in the fields as below.

Double click on the name of the new action we just created, SHOW_TEXT and this will take you to the methods tab. Here we are going to use the Web Dynpro Code Wizard to set the value of the attribute.
Click on the Web Dynpro Code Wizard icon (or Ctrl +F7), select ‘Read’, click and select the attribute that was created, TEXT. (Illustrated Below)

Now repeat the same steps starting with the Web Dynpro Code Wizard except this time select ‘Set’ instead of ‘Read.’ Each time the Web Dynpro Code Wizard is used DATA variables are created.

Note: If there are multiple attributes within a node, all of the attributes can be read or set at once by selecting the node.

After using the Web Dynpro Code Wizard the second time we now have two copies of the data variables that will not compile. Select the second set and delete them and in place put the following code:

Now if the application was tested the value of the attribute TEXT would be changed  between ‘Hide Text’ and ‘Show Text’ every time the button is pushed.

That is the rundown of how to build, read and set the context’s nodes and attributes. Now the context needs to be linked or ‘bound’ to the UI elements. Go back to the Layout tab and select the button. Under the properties find the ‘Text’ property. Click the yellow box to the right of the property and select the attribute to create the binding .

Binding

Binding is linking the data in the context to the UI elements. Here we have created an attribute that holds text. The ‘Text’ property of the button is set to the value within that property. Activate the Web Dynpro Component, create an application and test it.

For a little extra practice, add a TextView by dragging and dropping into the layout or right clicking on ROOTUIELEMENTCONTAINER and selecting ‘Insert Element.’ In the properties section set the Text value to ‘Now you see me!’ Create another node and attribute for the TextView by going to the ‘Context’ tab and right clicking on the ‘Context’ node and selecting ‘Create’ -> ‘Node’. Then create the attribute with the properties below.

Go to the ‘Methods’ tab and go into the method we was worked on earlier, ONACTIONSHOW_TEXT. Place the cursor after the ‘if’ statement that was put in, approximately line 33. Use the code wizard to set the new context we made. Then cut and pasted the DATA declarations just created and move them up to the top of the code. Then edit the ‘if’ statement to look like this:

Return to the ‘Layout’ tab, select the TextView and set the ‘Visible’ property to the new attribute. Activate the Web Dynpro Component and test the application.

Before you embark on your project’s first data migration test cycle, your data migration plan will probably start out as a simple list of preparation steps, data load dependencies, and cleanup steps.  As you progress through your several data migration test cycles, your plan should evolve into a rather complex list containing load methods, responsible persons, historical data volumes, historical execution times, steps that need to be modified and additional steps that need to be added.

I always find it rather interesting to compare the very first plan to the plan that is actually used in the cutover process.  Many project factors will cause you to amend your data migration plan.  Newly-discovered gaps, changes in the business requirements, the decision to load all of the legacy customers instead of only those customers which have been active for the past two years, and toggling back and forth between “should this one be a manual or an automated load” are only a few.   Always keep in mind that the goal in amending the plan is to keep it compatible with the changing requirements of the project.

The Data Migration Preparation Phase

Before you actually start the data migration main course, you will probably want to execute a series of preparation steps.  Some of these preparation steps may have a significant lead time; while others may require a system reboot to take effect.  Make sure that you carefully plan accordingly.  Here are some data migration preparation steps that I have found useful:

• Obtain a Data Migration Login
  Obtain a special data migration login, with all of the authorizations needed to execute all of the required tasks.  This login is only to be used during the data migration process, and is to be deleted upon the completion of the data migration process. Using the data migration login makes identification of migrated data very easy both now and several years down the road.  It also facilitates implementing a general user lockout while the data migration user is performing data migration activities.
• Technical client preparation
  The BASIS team may want to configure the data migration target client to have less dialog processes and more background and update processes.  This configuration can significantly improve data migration performance, especially if you have the opportunity to parallel process IDOCs.  In a Virtual Machine environment, the infrastructure team can even provision additional processors and memory.  You may also need additional disk space to handle large upload files, and any intermediate files that a load program might need to create.
• Configuration for IDOC processing
  If a data migration process involves creating and processing IDOCs, you may need to configure the ports, partner profiles, message types, and processing modules.  My preference for IDOC triggering is by using the ABAP program RBDAPP01 rather than immediate triggering.  This allows me to exercise the most scheduling control over the background processing options.
• Change Pointers
  During a data migration turn off change pointers.  Creating what could potentially be hundreds of thousands of change pointer records that are never going to be processed is an overhead burden on system performance and disk space that you do not need.  If the migrated data needs to be sent to external systems, manually send the data after the data migration is complete.
• Set the Correct Open Posting Period
  Some of the transactional data will want to post into an open financial or manufacturing posting period.  You will want someone from the business to make sure that the correct posting periods are open for business.
• Configuration Settings
  Sometimes, special temporary functional configuration settings are made to facilitate the data migration process.  Several functional analysts may be responsible identifying and setting these prior to the start of data migration.  As these are temporary configuration settings, it is expected that they will be set to their production values after the data migration is complete.
• Basic Setup Data
  Some data migration objects are dependent on reference data – a template from which new data migration objects can obtain some of their default values.  You will want to make sure that those who are responsible for setting up this reference data have completed their task before you start the actual data migration.  Sometimes this data is moved from the Golden Client into the target client via ALE, so you may need to set up RFC destinations, ports, distribution models, etc.
• General user lockout
  All users except for the data migration user should be locked out of the data migration client during the actual data migration activity.  It is impossible to verify that we moved exactly $15,386,254.23 in inventory from the source system to the target system if users are performing material movements in either system during the conversion.
• Connections to External Systems
  Depending on what connections to external systems are doing, you may want to make sure that they are disconnected prior to the start of data migration.  This will ensure that inbound interfaces, which may either modify existing migrated data or add new data, are disabled.

The Data Migration Phase

When all of the preparation steps are complete, it is time to start the actual data migration.  Data must be loaded into the target system in a certain sequence that is dictated by their data dependencies.  Customers must exist before sales orders can be migrated, vendors must exist before purchase orders, materials must exist before either sales orders or purchase orders, etc.  This dependency exercise varies a bit from project to project, and should have already been determined well before you start loading the data.

Automated data migration tasks for a single object (e.g. customer master data) usually include some or all of the following:

1. Creation of an upload file from the source system
2. Technical validation of the upload file
3. Functional validation of the upload file
4. Execution of a technical object to load the data into the target system
5. Technical validation of the migrated data
6. Functional validation of the migrated data
7. Collection and reporting of load statistics
8. Analyzing the fallout
9. Correcting the fallout
10. Reprocessing  the fallout

Checkpoints

At a higher level, the data migration plan will string together an end to end list of all of data migration objects.  I strongly suggest that you study the list and judiciously intersperse several checkpoints at appropriate places in the plan.  A checkpoint is an activity where all interested parties meet to review status and metrics, and to determine whether or not to proceed forward.  Keep in mind that what fails to load early in the plan will geometrically cascade into larger fallout later in the plan.  That single vendor which failed to load may cause several hundred open purchase orders to also fail.  And while the business owner of the vendor master data may think the fallout of a single vendor to be quite insignificant, the business owner of open purchase orders may have an entirely different perspective.  It is important here to make sure that all of the right stakeholders are participating, and that all are in agreement about whether or not to proceed.

Backup or Restore Points

Another activity that you should judiciously sprinkle into the plan is several backup or restore points.  It is very painful to have successfully navigated seventy-five percent of the data migration plan, only to have the next load create a huge and unrecoverable mess in the target system.  Without a backup or restore point available, you may have to wipe the slate clean and restart the entire data migration process again.

Depending on the target system and the facilities available, the backup or restore point could be a full system backup, a client copy, or a virtual machine snapshot.  Whatever the means, make sure it is a part of your plan.  It’s really great if you don’t need it.  It’s also really great to have if you do need it!

The Data Migration Cleanup Phase

When the data migration loads are finally complete, it’s time to exercise a series of cleanup steps.  This is where we:

1. Undo the special temporary settings and configurations that were done prior to the start of the data migration activity.
2. Adjust the technical configuration of the system to a more user-oriented system with the right amount of dialog, background, and update processes.
3. Turn change pointers back on.
4. Allow the general user population to access the system.
5. Connect the system to its inbound and outbound communication partners.
6. Disable the data migration user.
7. Archive those massive upload files.
8. Delete any intermediate processing data files.
9. Clean up the IDOC tables if needed.  But first make sure that you do not need to keep the IDOCs  for legal reasons.

An Example Data Migration Plan

Click on the link below to access an example data migration plan.  This plan is not a complete data migration plan, but is intended to demonstrate format and content.
Sample Data Migration Plan

Stay tuned!

In part 3 of this series on Data Migration, I will be discussing how to deal with fallout from automated data loads.

EDITOR’S NOTE: NCo 3.0 has now been released.  Read more details here.

NCo 3.0 Logon

One of the new features implemented to combat the malevolent for RFC client attacks is the interface IDestinationConfiguration. This interface contains method IDestinationConfiguration.GetParameters(string destinationName) which allows .NET programmers to provide their own secure method for storing and retrieving logon information, be it encrypted database, encrypted file, or even LDAP.  There is also a corresponding interface and method to secure NCo 3.0 RFC servers.

Additionally, there is updated functionality to support single sign-on (SSO) and X.509 certificates.

Say Goodbye to Data Containers and Generated Code

In SAP Connector 2.0, working with RFCs required the generation of proxy code via the SAP .NET Connector design-time tool.  This tool would convert the IMPORTING, EXPORTING, CHANGING, and TABLES parameters from the RFC you were calling/serving to .NET representations of the same.  With NCo 3.0 there is no longer any kind of generated code.  Instead of one generated proxy method for each function module, there is one single RfcFunction class, whose Invoke() method dynamically executes every given ABAP function module. Additionally, all ABAP parameters will be represented by the class RfcStructure instead of a dedicated generated class for every structure; All tables will be represented by class RfcTable.  So, instead of hard-coding all of the data and variable bindings statically at design time, NCo 3.0 now handles everything dynamically at runtime.

NCo 3.0 uses SAP’s data dictionary to determine the function interface for the called RFCs.  While this data is cached locally for performance reasons, NCo 3.0 is robust enough to detect changes in RFC interface signatures so your code will still execute if you’ve added, deleted, or changed RFC parameters.  If there arises a situation where the dynamic lookup of RFC interface signature is not wanted, there is also an option to hard code the RFC parameter metadata.

The biggest benefit of NCo 3.0′s new dynamic function handling is that NCo 3.0 no longer has a design-time component.  This releases the Visual Studio version restriction that .NET 2.0 had.  Let me rephrase that, NCo 3.0 will work with any version of Visual Studio you like! The only requirement is that at runtime, a .NET Framework version is installed that is compatible with the NCo 3.0 libraries.

Anxiously Waiting

NCo 3.0 figures to be a much-needed update to a vital SAP integration technology.  I, for one, cannot wait for the new functionality to be generally released.  Once NCo 3.0 is released we’ll be posting blogs highlighting the new features.  We’ll also include helpful information regarding a .NET Connector 2.0 to NCo 3.0 upgrade.  In the meantime, if you have any leave any questions or comments you have regarding NCo 3.0 below.  You may also email me directly at csta...@dataxstream.com if you’d like to set up a detailed conversation.

This would, in turn, generate a short dump:

My initial thought was that this was a TemSe issue, meaning it was a true BASIS issue.  Upon further examination, I came to the conclusion that it was actually a security/access issue.  The user did not have create rights for TemSe.  Find the Role path Basis: Administration -> TemSe: Actions on TemSe objects -> TemSe: Action ID for Authorization and make sure that the user has the value “CRE” (for create).

It is possible to add transport requests to the buffer, and even import them via the CLI (Command Line Interface).  Keep in mind, whenever working on an instance at the OS level, you should be logged in as [sid]adm.

To add transports to the buffer:
tp addtobuffer [transport number] [SID] Client=[client number] pf=/usr/sap/trans/bin/TP_DOMAIN_[DOMAIN_SID].PFL

If I wanted to add transport number DV1K907046 to the buffer for Q01 client 400 and the transport domain controller was DV1 the string would look like this:
tp addtobuffer DV1K907046 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL

To import transports via CLI:
tp pf=/usr/sap/trans/bin/TP_DOMAIN_[DOMAIN_SID].PFL import [transport number] [SID] U128 client=400

Since I’ve added DV1K907046 to the buffer, I can now import it with this string:
tp pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL import DV1K907046 Q01 U128 client=400

It is also possible to create shell or batch scripts from these commands to do multiple transports at one time. I’ve found that this is when CLI tp management is most effective.
Using your favorite text editor, simply “stack” the commands ontop of each other:

tp addtobuffer DV1K907046 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL
tp addtobuffer DV1K907047 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL
tp addtobuffer DV1K907048 Q01 Client=400 pf=/usr/sap/trans/bin/TP_DOMAIN_DV1.PFL
....

Then save as either a .sh for Unix or .bat for Windows.

The batching approach works for both adding to the buffer and for actual import. It’s best to seperate each task (addtobuffer in one script, import in another).

Q2Q3Y6XJM37U

Office/Excel 2003:

Open Excel

Tools -> macro -> security

Security Level tab:
make sure level is set to “medium”

Trusted Sources tab:
Check the box beside “Trust access to visual basic project.”

Office 2007:

Click the Office button.  Click Excel Options.

Click on Trust Center -> Trust Center Settings

Check the box beside “Trust access to VBA project object model”

Close Excel and try to view your report again.  The workbook should no longer be blank and it should be populated with the correct data.

Sometimes, a special business or security requirement does not permit the “business as usual” scenario.  It is these situations which nudge me down the path which I have never explored.

Take, for example, a simple flat file interface outbound from SAP to an external system.  In the typical scenario, at the 50,000 foot level, it works like this:

In a scheduled batch job step, an SAP ABAP program extracts data and creates a flat file in a folder somewhere on the network that is commonly visible to both SAP and the external system.

The external system acquires the flat file, processes the data and then archives the file, just in case we need to play “where is my data” or “I sent it, why didn’t you get it”.

Here is the process diagram:

In this scenario, OS administrators on both sides of the interface have agreed to grant to the common folder all of the permissions needed so that each side of the interface can perform its tasks.

But what if that is not the case?  What if the external system administrator cannot permit a common SAP/external system mount; but will permit receiving the file via ftp?

Let’s redraw the process diagram:

In this scenario, SAP drops the output file into its own outbound network OS folder.
The file is then moved to an inbound network folder on the external system via an ftp script.

The question now becomes, how do we execute the ftp script after the first step of the batch job which creates the outbound data file?

It turns out that SAP provides a facility to do just that.  Effectively, SAP will allow the ftp script to be entered as a step in a batch job.

We begin to assemble our batch job with SM36 as usual.

As shown here, the batch job is named Z_OUT_INTERFACE_2_EXTERNAL_SYST.

The first step of the batch job executes ABAP program Z_OUT_MATERIAL_EXTRACT with variant PRODUCTION_VAR.

This is the step which creates the outbound data file.

Once the file is created by the ABAP program in step 1, we would like an ftp script to execute, and copy the file to a folder on the remote system.
SAP allows an external program (e.g. our ftp script) to be executed as a batch job step.  We are going to  make this step 2 in our job.
(This is the section of batch job land which I had never before explored.)
To set up an external program as an SAP batch job step, click the External Program button.
The External program block is now open for input.

In the Name box, enter the complete path name of the location of the external program.
In this case, our external program is an ftp script which takes two input parameters:
1) The complete pathname of the data file.
In this example, the complete pathname is /data/dx1/ftpscript.ksh.
2) The path name and the name of the outbound data file.
In this example, the path name of the outbound data file is /data/dx1/interfaces/materials/outbound,
and the name of the outbound data file is materials.txt.
Both of these parameters are entered in the Parameter box.

SAP also allows for the external program standard output or error output to be displayed in the SAP job log.
These are turned on/off using control flags.

In this example, I have turned on the control flags which allow any standard output and error output from the external program to be displayed in the SAP job log.  I have also set the control flag which requires that the external program complete before the SAP job ends.  If this control flag is not set and there are no further job steps, the SAP job will complete without waiting for the external program.

Here is the entire SAP batch job with two job steps.
The first step is the ABAP program which creates the outbound data file.
The second step is the ftp script which will ftp the file to the external system.
This is the result that we want.

And, for all of you SAP documentation fans, yes, this is documented in SAP.  This documentation describes the external command and external program facilities, as well as the authorizations needed to utilize them.

SAP Documentation about using External Commands and External Programs as batch job steps can be found at: http://help.sap.com/saphelp_nw70/helpdata/EN/c4/3a7f2c505211d189550000e829fbbd/content.htm

This blog is a recap of the liveblog of the keynote address of the SAP TechEd 09 conference.  To read in chronological order, start from the bottom and work your way up.

• Craig Stasila: 8:57 am on October 13, 2009
  

  If you missed anything, check back for the full blog posting at http://www.dataxstream.com/category/sap-consultants-blog/

• Craig Stasila: 8:55 am on October 13, 2009
  

  Well, that’s it. The keynote speeches are over. I hope you enjoyed following along with the DataXstream’s first foray into liveblogging. Make sure you check back tonight at 11pm EDT (8pm PDT) for our liveblog of the Demo Jam.

• Craig Stasila: 8:53 am on October 13, 2009
  

  Ray’s parting shot: Even life expectancy is growing exponentially.

• Craig Stasila: 8:52 am on October 13, 2009
  

  2029: An intimate merger
  $1,000 of computation = 1,000 times the human brain
  Reverse engineering of the brain complete
  Computers pass the Turing test!!
  Skynet goes online (OK, I made this one up)

• Craig Stasila: 8:48 am on October 13, 2009
  

  There are only about 800 million bytes in the entire genome and it can be compressed into about 50 million bytes. The brain is made up of about 25 million bytes of data.

• Craig Stasila: 8:45 am on October 13, 2009
  

  

  The brain is getting reverse-engineered.  Individual brain components (e.g. visual cortex, cerebellum, etc.) are getting reverse engineered by researchers.

• Craig Stasila: 8:44 am on October 13, 2009
  

  Ray is now on Artificial Intelligence (AI). AI is all around us, but we’re too accustomed to it to notice it.

• Craig Stasila: 8:42 am on October 13, 2009
  

  They already had this technology in the 80s. I saw Innerspace (http://www.imdb.com/title/tt0093260/usercomments)

• Craig Stasila: 8:41 am on October 13, 2009
  

  Someday you will have millions or billions of nano-engineered devices coursing through your body keeping you healthy.

• Craig Stasila: 8:40 am on October 13, 2009
  

  Miniaturization is another exponential trend. “What used to fit in a building now fits in my pocket. What fits in my pocket now will fit inside a cell in a few years”

• Craig Stasila: 8:39 am on October 13, 2009
  

  Ray is now going over how the exponential growth in technology power is also mirrored by exponential decrease in price. RAM, processing power, human genome decoding, wireless devices. All adhere to the exponential growth curve.

• Craig Stasila: 8:38 am on October 13, 2009
  

  

  Ray thinks we’re due for a new paradigm shift away from flat integrated circuits.  He’s been talking to Intel about their development of 3D processors.  I’ve not heard of this before, but it sounds very cool.

• Craig Stasila: 8:34 am on October 13, 2009
  

  

• Craig Stasila: 8:32 am on October 13, 2009
  

  Some critics say that exponential growth can’t go on forever. Ray counters that by saying that there can be periods of relatively slow advancements, but over time, progress will catch up.

• Craig Stasila: 8:29 am on October 13, 2009
  

  You may think that he only picked events that matched his theory. But, now he’s showing another graph comparing his viewpoints with 15 others. There is a very high correlation.

• Craig Stasila: 8:27 am on October 13, 2009
  

  

  From life to now, this chart shows how life and technological advancements have followed a constant, exponential growth.  Both axes are logarithmic.  Very cool, indeed.

• Craig Stasila: 8:24 am on October 13, 2009
  

  

  As big as a washing machine.  Stevie Wonder bought one.  In 2002, it was still a desktop device.  Now, it is a cell-phone based app.

• Craig Stasila: 8:21 am on October 13, 2009
  

  It took 10 years to bet the first billion phones in the market. Now 2/3 of the world’s population has them!

• Craig Stasila: 8:20 am on October 13, 2009
  

  “The tools of disruptive change are in everybody’s hands”

• Craig Stasila: 8:20 am on October 13, 2009
  

  Technology is a democratizing force. Back in the day, you had to be a recording studio or movie studio to create content. Now a couple of hundred dollars can be used to create great content.

  • Craig Stasila: 8:18 am on October 13, 2009
    

    Back in the 70s, Ray projected that the two-thousand user ARPAnet would grow into a million user internet in the 90s. Umm. Yeah. I saw that coming, too!

  • Craig Stasila: 8:17 am on October 13, 2009
    

    Exponential growth even applies to solar energy. Solar energy may be a fringe player now, but Ray sees it growing.

  • Craig Stasila: 8:16 am on October 13, 2009
    

    This exponential growth is unaffected by any financial or other external pressures.

  • Craig Stasila: 8:15 am on October 13, 2009
    

    There are many underlaying properties of technology (MIPS, # of bits, # of genomes typed). Regardless of the property, technology follows a smooth exponential growth.

  • Craig Stasila: 8:13 am on October 13, 2009
    

    Not many pictures right now. Ray is just standing in one place and talking.

  • Craig Stasila: 8:12 am on October 13, 2009
    

    Only 10 years ago, people barely used search engines.  Now we can’t live without them.

    I’m always amazed how true genius can point out the obvious and make it sound profound.

  • Craig Stasila: 8:10 am on October 13, 2009
    

    Using the human genome project as an example of exponential growth in technology.

  • Craig Stasila: 8:09 am on October 13, 2009
    

    And progress is getting faster…

  • Craig Stasila: 8:09 am on October 13, 2009
    

    Your phone in your pocket is a thousand times more powerful and million times cheaper than a computer from 40 years ago. “What fit in a building 40 years ago, fits in your pocket today”

  • Craig Stasila: 8:08 am on October 13, 2009
    

    Ray thinks genes are software written in COBOL.

  • Craig Stasila: 8:08 am on October 13, 2009
    

    Oh Ray! Retalling the story of how Viagra was developed and discovered. Got a few chuckles from the crowd.

  • Craig Stasila: 8:06 am on October 13, 2009
    

    Ladies & Gentlemen, Ray Kurzweil

  • Craig Stasila: 8:06 am on October 13, 2009
    

    Vishal is done. Last parting shot: “Timeless Software”

  • Craig Stasila: 8:05 am on October 13, 2009
    

    

    Vishal’s only slide.  All the rest were just pretty pictures.  Notice the public clouds in the lower right.  SAP is looking to be able to be run on public clouds in the future.  Currently there are development and test systems on public clouds.  Getting production systems on public clouds is coming.

  • Craig Stasila: 8:03 am on October 13, 2009
    

    

  • Craig Stasila: 8:03 am on October 13, 2009
    

    “Change is the fundamental dimension in which we all live”

  • Craig Stasila: 8:02 am on October 13, 2009
    

    Cestbon “listens” for business content on your computer and links to it. You can hop straight from Cestbon to the data in SAP.

  • Craig Stasila: 8:01 am on October 13, 2009
    

    The presenter is British and doesn’t like the frenchies. Demoing Cestbon–An Outlook integration example.

  • Craig Stasila: 7:59 am on October 13, 2009
    

    Example #4: Ambient, Real-Time Systems

  • Craig Stasila: 7:59 am on October 13, 2009
    

    Six blade servers = 1 Nehalem processor.

  • Craig Stasila: 7:58 am on October 13, 2009
    

    Vishal is talking about optimization across all layers. This relates to hardware manufacturers (memory, processors, blade servers). Modularity is making optimization happen.

  • Craig Stasila: 7:57 am on October 13, 2009
    

    All the demos were very cool. As a geek, I would love to check out the technology involved in each one.

  • Craig Stasila: 7:57 am on October 13, 2009
    

    Excel integration now being demoed. The 166 million records can’t be loaded to Excel (for memory reasons). The solution allows the end-user to drill down and get the data from SAP as needed.

  • Craig Stasila: 7:55 am on October 13, 2009
    

    Business Objects Explorer being demoed. Crunching through 166 million records. The example is trying to be green by reducing paper and electricity.

  • Craig Stasila: 7:55 am on October 13, 2009
    

    

  • Craig Stasila: 7:53 am on October 13, 2009
    

    A Dilbert Example! Wow, the pop-culture touchpoints never end!

  • Craig Stasila: 7:52 am on October 13, 2009
    

    Example #3: Coherent Visualization of Massive Information. Looking at Coherent Modularization.

  • Craig Stasila: 7:50 am on October 13, 2009
    

    Containers need not only modularity, but also locality of design.

  • Craig Stasila: 7:49 am on October 13, 2009
    

    Now talking about SOA and its growth. Using it as a basis of modularity and coherence.

  • Craig Stasila: 7:49 am on October 13, 2009
    

    

    Too many tools on the stage… (ahem)

  • Craig Stasila: 7:47 am on October 13, 2009
    

    

  • Craig Stasila: 7:46 am on October 13, 2009
    

    Live tracking of tools being checked in and out of the tool crib.

  • Craig Stasila: 7:45 am on October 13, 2009
    

    Aircraft mechanics were using SAP, but equipment check-in check-out took too long via SAP GUI.

  • Craig Stasila: 7:43 am on October 13, 2009
    

    Example #2: Extending Information into Physical Systems. SAP runs on aircraft carriers. I hope they bring one in…

  • Craig Stasila: 7:42 am on October 13, 2009
    

    

    Google Wave and SAP!  So happy together.

  • Craig Stasila: 7:42 am on October 13, 2009
    

    Cutting edge technology BCE edition: Rosetta stone. Using the analogy to show that we need to be able to work with others

  • Craig Stasila: 7:38 am on October 13, 2009
    

    They’re pulling out all the stops!!! Google Wave! Google Wave isn’t complying with the demo. “Thank god that’s Google software and not SAP!” Big crowd laughs.

  • Craig Stasila: 7:37 am on October 13, 2009
    

    The example is now showing our good-ole familiar SAP GUI showing the timesheet approval process for the contractor timesheet application

  • Craig Stasila: 7:36 am on October 13, 2009
    

    Containers need to be extended. Either to SAP applications or to other Web 2.0 applications.

  • Craig Stasila: 7:35 am on October 13, 2009
    

    Another ooh-ahh moment! iPhone timesheet app.

• Craig Stasila: 7:34 am on October 13, 2009
  

  

  Content separated from applicatons

• Craig Stasila: 7:34 am on October 13, 2009
  

  Oh Snap!!! Cloud computing!! The example is running through a container. The backend is on Amazon S3

• Craig Stasila: 7:32 am on October 13, 2009
  

  Example uses managers, contractors, and purchasing department.

• Craig Stasila: 7:32 am on October 13, 2009
  

  Examples of design thinking, and separation of intent and optimization.

• Craig Stasila: 7:31 am on October 13, 2009
  

  An example of intent being separated from optimization: A painter does not need a scaffolding to paint a building, the scaffolding optimizes the process.

• Craig Stasila: 7:29 am on October 13, 2009
  

  

• Craig Stasila: 7:29 am on October 13, 2009
  

  Next, the intent needs to be separated from the optimization.

• Craig Stasila: 7:28 am on October 13, 2009
  

  Techies need to start with “design thinking”. Start with end-user in mind. “Start from the screen and work backwords”

• Craig Stasila: 7:27 am on October 13, 2009
  

  

• Craig Stasila: 7:25 am on October 13, 2009
  

  Content is independent of containers in long-lived systems

• Craig Stasila: 7:24 am on October 13, 2009
  

  Looking back at the IT industry, a new, major language emerges about every ten years. While Java will be around for a long time, we’re due for a new major language. SAP thinks that Ruby is the future. Ruby reached 1 million developers faster than any other programming language in history.

• Craig Stasila: 7:22 am on October 13, 2009
  

  Vishal is teasing Ray Kurzweil’s speach on how the rate of change is increasing. Moore’s law gets a shout out.

• Craig Stasila: 7:22 am on October 13, 2009
  

  There are hundreds of SAP customers that have been using the software for over 30 years. None have left SAP. Vishal is highlighting the change that the companies underwent and how SAP changed with their customers.

• Craig Stasila: 7:20 am on October 13, 2009
  

  SAP has been around for 37 years. Have worked with over 85,000 customers, tens of thousands of partners, and tens of millions of users.

• Craig Stasila: 7:19 am on October 13, 2009
  

  Vishal isn’t going to be focusing on the technology. He’ll be focusing on… “change”. Do you sense a theme?

• Craig Stasila: 7:18 am on October 13, 2009
  

  Dr. Vishal Sikka, CTO SAP is now on the stage. He is the first of two keynote speakers.

• Craig Stasila: 7:18 am on October 13, 2009
  

  

  “Welcome to TechEd 2009. You are the star of the show”

• Craig Stasila: 7:16 am on October 13, 2009
  

  Zia is really pumping up “the community”. The SAP user community is almost 2 million strong now.

• Craig Stasila: 7:16 am on October 13, 2009
  

  “After the PowerPoints, it’s time for action” SAP wants the BPEs to make it happen! I already feel pumped. Let’s go out there an do this!!!! Oh wait, the Keynote hasn’t even started yet.

• Craig Stasila: 7:14 am on October 13, 2009
  

  

  • To enter a new market, business process have to change. SAP’s emphasis on Business Process Expert community will pay dividends.

  • Craig Stasila: 7:12 am on October 13, 2009
    

    Zia is giving an example using Dunder Mifflin as a “well-run company”. Perhaps he hasn’t seen The Office…

  • Craig Stasila: 7:11 am on October 13, 2009
    

    Zia is telling the conference attendees that we are the agents of change–A very person-centric focus.

  • Craig Stasila: 7:11 am on October 13, 2009
    

    

  • Craig Stasila: 7:10 am on October 13, 2009
    

    The world is changing. SAP is changing.

  • Craig Stasila: 7:09 am on October 13, 2009
    

    Change is constant. Michael Jackson gets a shout-out!

  • Craig Stasila: 7:09 am on October 13, 2009
    

    On the stage now: Zia Yusuf, Executive Vice President, Global Ecosystem & Partner Group, SAP

  • Craig Stasila: 7:08 am on October 13, 2009
    

    Inspirational Video: “Clarity is a necessity”.

    and

    SAP: “It’s time for a clear new world”

  • Craig Stasila: 7:06 am on October 13, 2009
    

    And away we go. Lights down. Check. Ominous Music. Check. Inspiring Opening Video. Check. Can you feel the excitement?

  • Craig Stasila: 7:05 am on October 13, 2009
    

    

    The crowd is filling in nicely.  Sorry guy-behind-me for accidentally flashing the camera in your face TWICE before I snapped one without the flash.

  • Craig Stasila: 7:03 am on October 13, 2009
    

    

    Uploaded from backup backup plan.  This is from my iPhone.  Doug, Adam, Tim say “hi”

  • Craig Stasila: 7:00 am on October 13, 2009
    

    Cell phones off, y’all!

  • Craig Stasila: 6:59 am on October 13, 2009
    

    

    Pictures will be slow, but here is a teaser

  • Craig Stasila: 6:57 am on October 13, 2009
    

    Five minutes to go. With me are Tim Cooper, Doug Foss, and our good friend Adam Blum from Grom & Associates

  • Craig Stasila: 6:55 am on October 13, 2009
    

    

    Here we go!

  • Craig Stasila: 6:49 am on October 13, 2009
    

    We had an awesome setup to capture pictures from the event, but it relied on the conference WiFi. We’re working on a backup solution now.

  • Craig Stasila: 6:48 am on October 13, 2009
    

    The conference public WiFi isn’t working. I have to be working on backup off of my Verizon Aircard, so posts may be a little slower.

  • Craig Stasila: 6:47 am on October 13, 2009
    

    First take from the keynote address. The welcoming music is horrible, but we’ll survive

  • Craig Stasila: 6:45 am on October 13, 2009
    

    Welcome to the DataXstream Liveblog of the SAP TechEd 09 Conference Keynote address

Head over to live.dataxstream.com on Tuesday, October 13, 2009 to get up to second updates from the show.  We will be getting our liveblog on starting at 8am PDT (that’s 11am for you right-coasters) for the general keynote session.  We’ll also be liveblogging from SAP TechEd 09 Demo Jam at 8pm PDT on Tuesday.  The Demo Jam promises to be a great time, so plan to join us online after you put the kiddies to bed!

This is our first foray into liveblogging.  Hopefully it will go off without too many technical glitches.  We hope you’ll enjoy following the events with us!