Skip to Content
author's profile photo Former Member
Former Member

realtime data integration with Third party application

A customer wants to send data to a third party application when a user modifies some information on a business object (ie PO Amount, Employee Name etc). How can you trap this change as close to realtime as possible within SAP?

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Jan 07, 2005 at 12:40 AM

    The requirements are in very high level. It will be very difficult to comment exactly.

    On a General SAP perspective, following can be done.

    1. Consider a standard ALE distribution system established from SAP to Non-SAP systems using standard message type.

    2. Change-pointers is the funda to capture the immediate changes occured in day-to-day business processess.

    This can be acheived by using foll transactions :

    BD61,BD50,BD59 etc., After the required configuration of ale processess, change in business processess captured based on message type in BDCPV.

    3. Based on the requirement, standard program or custom program can be written to read changer pointers,create idocs and send to SAP port. Third-party system will capture the changes from the Port.

    The above solution is suitable for ALE process.

    SAP change-pointers also can be found in CDHDR and CDPOS tables for a SAP object like material,assets etc.,

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 07, 2005 at 09:23 AM

    In addition to Senthil's reply, it may also be possible to hook into a workflow event, provided such an event is raised. Whilst I prefer the change pointer approach outlined by Senthil, it does enforce a delay between the "application event" itself and change pointer processing.

    To see if a workflow event is raised, in a non-production system, use transaction SWU8 to activate the workflow trace. Next perform the update that you wish to trap. Finally, use transaction SWU9 to display the workflow log. Hopefully you'll see a workflow event raised for your update (for example a CHANGED event).

    This will allow you to perform either synchronous or asynchronous processing immediately (the norm is for workflow processing to be triggered immediately but asychronously).

    It would be great if all SAP objects supported a common event model, with BADI's for standardised events for create, change, etc. Maybe one day, but not today...

    Cheers,

    Scott

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.