Process observer and event type linkage

1. A computer-implemented method comprising:

receiving, at a process-observer-enabled server, a communication from a non-process-observer-enabled server, wherein the communication is received at the process-observer-enabled server from the non-process-observer-enabled server as a result of a remote function call made by the non-process-observer-enabled server, wherein the remote function call includes identification of a specified target module at the process-observer-enabled server to be used to process the communication;

translating, at the process-observer-enabled server, at least event information included within the received communication from a non-process-observer-compatible format to a process-observer-compatible format;

adding an event in the process-observer-compatible format to a process observer queue for subsequent processing by a process observer with other events, wherein the process observer is configured to process events from the process observer queue, correlate application events with a defined workflow/process model, and create process instances in a process log; and

processing, by the process observer, the event from the process observer queue.

2. The method of claim 1 wherein the communication is from a slave system of the process observer and includes information about a business object event at the slave system.

3. The method of claim 2 wherein the non-process-observer-compatible format is a raw format of the corresponding slave system.

4. The method of claim 1 wherein processing the communication includes translating at least event information included within the communication.

5. The method of claim 1 wherein the process observer includes one or more target function modules, and wherein communications from the non-process-observer-enabled server are received at a particular target function module identified in a remote function call made by the non-process-observer-enabled server.

6. The method of claim 1 wherein processing the event from the process observer queue includes matching the event to a defined process/workflow model associated with at least one business object.

7. The method of claim 1 wherein processing the event includes:

mapping the event to a task in a process;

determining at least one predecessor to the task; and

using the determination to update process data associated with the process.

8. A computer-program product, the computer program product comprising computer-readable instructions embodied on tangible, non-transitory media, the instructions operable when executed by at least one computer to:

receive a communication from a non-process-observer-enabled server, wherein the communication is received at the process-observer-enabled server from the non-process-observer-enabled server as a result of a remote function call made by the non-process-observer-enabled server, wherein the remote function call includes identification of a specified target module at the process-observer-enabled server to be used to process the communication;

translate, at the process-observer-enabled server, at least event information included within the received communication from a non-process-observer-compatible format to a process-observer-compatible format;

add an event in the process-observer-compatible format to a process observer queue for subsequent processing by a process observer with other events, wherein the process observer is configured to process events from the process observer queue, correlate application events with a defined workflow/process model, and create process instances in a process log; and

process at least one event from the process observer queue.

9. The computer program product of claim 8 wherein the communication is from a slave system of the process observer and includes information about a business object event at the slave system.

10. The computer program product of claim 9 wherein the non-process-observer-compatible format is a raw format of the corresponding slave system.

11. The computer program product of claim 8 wherein processing the communication includes translating at least event information included within the communication.

12. The computer program product of claim 8 wherein the process observer includes one or more target function modules, and wherein communications from the non-process-observer-enabled server are received at a particular target function module identified in a remote function call made by the non-process-observer-enabled server.

13. The computer program product of claim 8 wherein processing the event from the process observer queue includes matching the event to a defined process/workflow model associated with at least one business object.

14. The computer program product of claim 8 wherein processing the event includes:

mapping the event to a task in a process;

determining at least one predecessor to the task; and

using the determination to update process data associated with the process.

15. A system, comprising:

memory operable to store at least process and event information; and

at least one hardware processor interoperably coupled to the memory and operable to perform instructions to:

receive a communication from a non-process-observer-enabled server, wherein the communication is received at the process-observer-enabled server from the non-process-observer-enabled server as a result of a remote function call made by the non-process-observer-enabled server, wherein the remote function call includes identification of a specified target module at the process-observer-enabled server to be used to process the communication;

translate, at the process-observer-enabled server, at least event information included within the received communication from a non-process-observer-compatible format to a process-observer-compatible format;

add an event in the process-observer-compatible format to a process observer queue for subsequent processing by a process observer with other events, wherein the process observer is configured to process events from the process observer queue, correlate application events with a defined workflow/process model, and create process instances in a process log; and

process at least one event from the process observer queue.

16. The system of claim 15 wherein the communication is from a slave system of the process observer and includes information about a business object event at the slave system.

17. The system of claim 16 wherein the non-process-observer-compatible format is a raw format of the corresponding slave system.

18. The system of claim 15 wherein processing the communication includes translating at least event information included within the communication.

19. The system of claim 15 wherein the process observer includes one or more target function modules, and wherein communications from the non-process-observer-enabled server are received at a particular target function module identified in a remote function call made by the non-process-observer-enabled server.

20. The system of claim 15 wherein processing the event from the process observer queue includes matching the event to a defined process/workflow model associated with at least one business object.

21. A computer-implemented method comprising:

receiving, at a process-observer-enabled server that includes a process observer, a communication from a slave system of a non-process-observer-enabled server, wherein the communication includes information about a business object event at the slave system, wherein the communication is received as a result of a remote function call made by the non-process-observer-enabled server, wherein the remote function call includes identification of a specified target function module at the process-observer-enabled server to be used to process the communication, and wherein the communication is received at the specified target function module;

translating, by the specified target function module at the process-observer-enabled server, at least event information included within the received communication from a non-process-observer-compatible format to a process-observer-compatible format, wherein the non-process-observer-compatible format is a raw format of the corresponding slave system;

adding an event in the process-observer-compatible format to a process observer queue for subsequent processing by the process observer with other events, wherein the process observer is configured to process events from the process observer queue, correlate application events with a defined workflow/process model, and create process instances in a process log; and

processing, by the process observer, the event from the process observer queue, including matching the event to a defined process/workflow model associated with at least one business object, and wherein processing the event includes:

mapping the event to a task in a process;

determining at least one predecessor to the task; and

using the determination to update process data associated with the process.