Last edited: 1999-07-18 20:35 +0200
To be honest: creating IDocs for outbound is a widely mechanical task, which involve mainly a very limited number of transactions. It pays be speeding up your work to know them by heart, instead of searching them in the menus.
Transaction WE31 |
Define IDoc segments |
Transaction WE30 |
Define IDoc type |
Transaction WE21 |
Define logical port |
Transaction WE20 |
Define partner profile |
Table NAST |
If IDocs shall be triggered from message output, you must be sure that a message is generated in table NAST when the document is saved. The creation of such messages is done in the same manner as for SAPSCRIPT messages. This message must also be defined along with the partner profile in WE20. |
Table SWECDOBJ |
If you want to trigger the IDoc from a change document, you must create a
function module and enter its name in the table SWECDOBJ. This function module is called
from the function SWE_EVENT_CREATE and the interface
looks like that:
|
Transaction BD88 or ABAP RSEOUT00 |
With BD88 you actually dispatch the data to the data port, if the profile is not set to immediate and automatic dispatch. |