Wednesday, August 31, 2011

Triggering a workflow from abap

Last week’s post was about creating a workflow on a custom object.

In a normal situation, when using standard objects in workflow, you subscribe your workflow on existing events on existing standard objects.

These events are raised in standard coding, at the right time.

When using custom objects, you should also raise the event in custom coding, so for instance after saving an instance of your custom object to the database, you should raise the CREATED event.

Wednesday, August 24, 2011

Using custom objects in SAP Workflow

When implementing workflow, you have the possibility to trigger workflow from an event in a BOR object (transaction SWO1) and passing the object to the workflow and use it in tasks and activities in the workflow.

Now imagine you want to create a workflow on a custom object, an object not supported with a standard object in SWO1 or even an object in another system. You would not be able to do this unless you create a custom object in SWO1. Let’s see what needs to be done.

Wednesday, August 17, 2011

Adding a mash-up to the screen using the AET

Last week’s blog introduced the Application Enhancement Tool (AET). Adding new fields to the web UI screens is reduced to a relatively easy job using the AET. In SAP CRM 7.0 EhP1 the AET has been extended significantly.

It is not only possible to add fields in this new version, but the same concept can now also be used to add mash-ups, transparent tables, database views and the results of webservice calls to the web UI screens.

Adding web content to the account overview screen can now be implemented in less than 5 minutes. The following example demonstrates adding Google Maps content to the account overview screen.

Wednesday, August 10, 2011

Adding custom fields to the screen using the AET

AET stands for Application Enhancement Tool, and as the name suggests, the AET helps you enhance the application.
In many previous posts, tools were explained on how to influence and enhance the application by implementing logic. The AET enables you to enhance the application by implementing new fields.

Adding fields might not look like rocket science (and it isn't of course), but is technically more complex than you might imagine. SAP CRM is designed according to a layered model, like the OSI model. Which is good from a software engineering perspective. Decoupling the functions in each layer enables you to change stuff in one layer without disturbing the others.

The biggest downside of the layered design would be that adding a field at database level, will not automatically also add the field in the Generic Interaction Layer, nor in the Business Object Layer, nor in the Presentation Layer. 

The AET takes care of this for you. Beside adding the field to all the layers, the field is also added to the applicable BW Datasource, so the information that is entered will also be available in BW.

Wednesday, August 3, 2011

Adding functions to events using CRMV_EVENT

Another great tool to influence the system is adding Callback Functions in CRMV_EVENT. This is a totally different mechanism from last weeks' IC Event mechanism.
The similarity between the two is that both enable you to add custom coding to standard. The difference is that IC events occur because they are raised in specific coding (can be anytime), while the events available in CRMV_EVENT are always triggered from an operation on a oneorder object (where a oneorder object can be a salesorder, activity, service order, etc etc.).