phpOLAPi is a PHP-client for XMLA webservices. It allows to build and execute MDX queries, transform the results into different structures and even explore database schemas, cubes, measures, dimensions, etc.
SAP UI5 and OpenUI5 provide a cool numeric input control called sap.m.StepInput. For some reason it cannot be emptied though: removing it's value makes it be zero, not empty. Unfortunately, this makes it impossible to use it as a filter or for optional inputs. Here is a simple custom control, that extends sap.m.StepInput and allows empty values (resulting in empty strings).
This demo page lets you play around with the settings of onScan.js to find the best setup for a specific scanner. Just connect the scanner to your device and open this page in it's browser - than start scanning and watch the output in the console-box below.
Here is how to mass-extract all attachments from a folder with .eml files using absolutely free tools only: no shareware! This method can also be used to download all attachments from an email account if you save the messages as .eml files first.
Looking for a good standard web API to use? Here is a detailed feature-comparison for the most common free API standards. See if features important for your project are built-in or if you will need to invent your own specification for them.
Most enterprise applications require a web service interface sooner or later. The official requirements are mostly pretty straightforward: state-of-the-art, easy-to-use, wide-spread format, easy-to-maintain (= cheap) and ideally generic. But in the past couple years, I found myself often in search for a good list of common technical requirements to pick from for a specific project. In other words, a check-list to compare different approaches. So here it goes...
Did you know, there is a 100%-native web service built into SAP NetWeaver, that performs any read-only OpenSQL statement provided? Build SQL-based data extractors, ETL-process, do rapid prototyping for UI5 apps - all without a single line of ABAP code! Here is how...
OData Services and other web services running on SAP NetWeaver use so-called CSRF tokens to secure requests, that can potentially modify data (i.e. POST, PUT, DELETE, etc.). Here is how to handle them in non-SAP applications.