|
|
|
|
|
IDocs / BDocs
|
Written by Anon.
|
|
Friday, 03 August 2007 |
|
IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS — Customer Master, and WMMBID02 for message type WMMBXY— Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALE’s ability to redefine it for any message type. |
|
Read more...
|
|
|
Written by Kevin Wilson
|
|
Tuesday, 17 July 2007 |
|
Use the following BAdIs to change data in the MATMAS IDoc: - BADI_MATMAS_ALE_CR Change Data in MATMAS IDoc When Generating an IDoc
- BADI_MATMAS_ALE_IN Change Data in MATMAS IDoc Before Posting
|
|
|
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...
|
|
|
Written by Kevin Wilson
|
|
Monday, 09 April 2007 |
|
A comprehensive list of IDoc user exits split into inbound and outbound interfaces. |
|
Last Updated ( Monday, 09 April 2007 )
|
|
Read more...
|
|
|
Written by Kevin Wilson
|
|
Thursday, 08 March 2007 |
|
2 diagrams displaying the flow of inbound and outbound IDoc statuses. |
|
Last Updated ( Thursday, 08 March 2007 )
|
|
Read more...
|
|
|
|
|
|
