pscMita: Interface to SAP IS-M/AM by

There are several programs known connecting third party advertising systems with SAP IS-M/AM. One of them 4 years ago I personally designed, partly programmed and finally performed the official SAP certification.

What's new in pscMita?

If you are interested, you can learn some more technical details about pscMita here.

pscMita is much faster than known solutions.

In the known programs the application scans the data coming from SAP. Then it builds SQL strings to insert the data into its data base.

In case of loops (e.g. for different publishing dates) the SAP data are read again and again causing rather long unnecessary process time. Also a lot of senseless work is done when items in the SAP order do not have publishing dates.

In the pscMita system the SAP data are classes with their own intelligence, programmed as separate DLLs, e.g. pscMitaOrder, pscMitaError etc. They tell the application what and when to do. As a result, processing of a SAP order takes much less time, and the application itself is very small, e.g. pscMitaOLP has a size of about 100 kB.

In a test on my system I compared pscMita  with my old program mentioned above using the same data for both.

The result was: 60 seconds for the old program compared with 18 seconds for  pscMita.

See test conditions and log files of the Old program and pscMita.

pscMita is independent from the SAP Release.

It handles the current SAP releases 4.6.x and 4.7.x.

Even a future upgrade to a newer SAP release with change of structures and function names is assumed to be a task of some minutes using pscMitaTools.

After the upgrade pscMita allows you to switch between the old and new SAP release on the fly, just by choosing the release when starting the pscMitaXXX Application.

pscMita is nearly independent from the third party advertising system.

Most customer specials like "User Exits" with different SAP structure and function names can be handled by definition with pscMitaTools.

Here also pscMita allows you to switch between standard and special on the fly when starting the pscMitaXXX Application.

Only some customer specials (e.g. combinations) have to be programmed in the pscMitaXXX Application.

pscMita allows distributed processing.

Orders designed or positioned in the third party ad designer/positioning system can be processed in background at the individual client's PC where they have been designed.

pscMita can be controlled remotely.

You can watch the pscMita applications activity.
You can start, shut down or kill any  pscMita application from anywhere in the network using pscMitaWatch.

pscMita is fault tolerant.

pscMita can make data base access retries.

E.g in case of a deadlock it makes sense to retry rather than to generate an error.

The cases where to do a retry can individually be defined by the user using pscMitaTools.

pscMita setup and feature control is stored in the data base.

pscMita does not use local INI files or registry entries.

Only local information like size and location of the application are stored in the local registry.
So on the next start the application has the same location and size like in the previous run.

If you make some setup changes using pscMitaTools, all changes are in effect at any pscMita application after its next start.

So you just have to restart the applications remotely by using pscMitaWatch.

pscMita has a sophisticated build in report system.

Using pscMitaTools you can generate report control templates about orders, SQL logs and events like "All Errors of last Friday".

The templates are stored in the database and can be used from any PC in the network to generate the actual report (Also by using pscMitaTools ).

pscMita sends error reports to SAP off line.

To process SAP orders into the data base, pscMita usually does not need a SAP connection. Only if an error has to be reported to SAP the connection is used.

If the connection is currently not available e.g. because of network problems, order processing would stop until the connection is available again.

To avoid this problem, errors for SAP optionally are written into the database and sent by the separate application pscMitaERR.

pscMita is programmed using actual 32 bit technology.

Older programs are, due to the time of creating, written in 16 bit C++ or VB. They partly use techniques which are not longer supported by modern operating systems like XP.

This may cause problems when upgrading the servers where the programs run.

The pscMita package is written completely in Microsoft .NET and does not have the above mentioned problems.