I did some reasearch and seen a lot of posts about SAPHistory*.mdb file in the SapWorkDir directory. The user’s history was was being generated so the problem was being caused by something else.

Then I came across a post talking about Low Speed Connection [Reduced Network Traffic] setting which can be found by going through your login pad, clicking on the system and displaying the properties window – followed by going to the Network tab.  From what I’ve read it seems that having the setting set to Low Speed Connection could cause the problem of missing input field history.  Even though this seemed promissing after getting the user to try a different machine with the High Speed enabled he was still showing the problem.

The final peace of information that I’ve aquired from the web was a little neat SAP feature: if you get to an input field and hold down your Ctrl button you can right click on your  mouse and get a pop-up window that would allow you to Disable/Enable History functionality.  Typically the field is set to Defaut Settings, so the only thing left to do was to figure out if the user’s default settings were set to Disable History for his SAP system.

to be continued…

PS: another interesting fact that I picked up somewhere: if you scroll up/down using your keyboard in the history field you can delete entries by pushing the delete key.  I know, it’s neat.

1. Execute transaction: SPAD
2. Select your output device and enter the configuration screen
3. On a 4.6C version you can go to the Output attributes tab and look at the “Output attributes for list drivers and Smart Forms” section
4. Examine the drop down for the Print mode
5. Typically by default you will see DEFAULT as the setting that is displayed, simply change the value to S SIMPLEX to allow the data to be prined on a Single Side

For more information on the matter for SAP version 7.0 you can have a look at this document.

Useful transport tables [listed above].

Go to:

Advanced -> Configuration ->File Handling -> Backup

By default the configurations are set up to create a .BAK file in the same directory.  Although the functionality is annoying I still think it’s quite useful.  So the best thign to do [in my oppinion] is to populate the default directory field with the a directory somewhere on your local computer.

Action Message Format(AMF) is a binary file format representing a serialized ActionScript object. The AMF file type is used throughout the Flash Player for data storage and data exchange. For example in the Flash Player AMF is used in SharedObjects, RemoteObjects, LocalConnection, ByteArray, RTMP, and all RPC operations. Some of the benefits of AMF include:

• File Size – AMF objects are very small and are compressed using zlib.
• Fast Serialization/ Deserialization – AMF is transformed using native C code in the Flash Player making it very fast. The AMF format was designed to serialize and deserialize quickly under low memory and slower CPU conditions making it perfect for the web. AMF data is parsed directly into objects, meaning there is no lag for interpretation or parsing of AMF making the creation of objects complete in a single pass.
• Native Types and Custom classes supported – You can serialize any object in Flash Player with the only exception being a displayObject.you can also map serialized objects back to custom class instanced provided the custom class is in the Flash Player when the AMF object is deserialized.

AMF existed in ActionScript 2 and was just called AMF as of ActionScript 3 the AMF protocol has been updated and is referred to as AMF3. For historical reasons the original AMF format is now referred to as AMF0. One of the main upgrades to AMF3 is that the object is now zlib compressed for faster transfer do to the smaller file size and the additional of data types that were released with ActionScript 3.

The two alternative frameworks that I am looking at are AMFPHP and Zend_AMF.

I’ve created the file in the root directory and specified in the Flex Compiler [Additional compiler arguments] the following string -locale en_US -services “services-config.xml”.

As soon as I clicked OK an error popped up with a message unable to open ‘services-config.xml’.   After trying varying things I was able to figure out that the problem was with the location of the file.  Simply placing the file at the root of the directory wasn’t the right location.  I needed to put the file in the same directory as the main MXML executable – after that the program worked as expected.

1. Set up of a sandbox account that would allow you to play with your virtual development shopping cart.
2. Go look at the development center for the PayPal SDK