| TIP: Check out the site map |
Click on the site map in the menu option to browse, on 1 page, all articles with their titles. A good way to see what's in our database.
 Links to many Forums , Events and News articles. Tell us what user you are... (Poll)
ADVERTISEMENT |
|
|
Written by Kevin Wilson
|
|
Monday, 23 July 2007 |
|
Ever needed to kick off a job from another external system? This tip shows you how to kick off an event. A background job is then created in SM36 that waits for this event to occur. Scheduling this job as a periodic job will cause this job to be kicked off each time this event happens. It has the ability to send in a parameter which allows you to configure the ABAP of the job to react differently based on the event parameter. Use SM62 to create the user defined event. |
|
Read more...
|
|
|
Written by Kevin Wilson
|
|
Tuesday, 10 July 2007 |
|
We used to be able to start a workflow using the transaction SWUG but that is no longer available. To do the procedure in the NetWeaver environment do the following: |
|
Read more...
|
|
|
Written by Goodwin Yee
|
|
Monday, 25 June 2007 |
|
Links are written in the ALE and IDoc environment which result in entries in the IDOCREL and SRRELROLES tables. These links are required for IDoc monitoring for the document trace and for the ALE audit.
The business objects in a link are stored in the SRRELROLES table. The business objects are assigned a role type which specifies the role played by the business objects in the links.
The following link model is based on the links in the IDOCREL table: |
|
Read more...
|
|
|
|
<< Start < Prev 1 2 3 4 5 Next > End >>
|
| Results 1 - 4 of 20 |
Developing a BAPI and Calling it with JCo
Taking you through ALE
SAP Order Status tables and Doc Flow table
E-Book - ABAP Programs (1385)
ALV Report Template (612)