The following are the problems in EDI outbound with message control.

1 . Message control might not be available for your application document. Here we have no choice. Applications are programmed to make use of the Message control service, and it is not automatically available for every application. The FI applications, for example, do not use Message control. The REMADV message is generated by the Payment Run program, which does not use Message control. Most ALE processes do not use Message control.

2 · The Message control component is intricate because of its generic technology of building business rules without coding ABAP/4 programs. Here client may not want to maintain Message control because of its complexity and decided to bypass it completely. This is not a configuration option. The client had developed custom programs to select IDoc data and pass it directly to the ALE/EDI layer.

Here are the following steps in this process.

Processing in the Application Layer :

1. The application document is entered by way of a transaction.
2. The business rules for selecting objects for EDI output are established through a selection screen or a dialog box.
3. The data−extraction logic, which is built into the application, is implemented as a separate function module but is still a part of the application logic. This concept is different compared to the outbound process with Message control, in which the data−extraction logic is not part of theapplication logic.
4. The application builds the IDoc and passes control to the ALE layer. The interface to the ALE layer is through the function module MASTER_IDOC_DISTRIBUTE.

Processing in the ALE/EDI Layer

1. The ALE/EDI layer checks for the sender and receiver fields. If they are not supplied, the ALE distribution model is consulted to determine the recipients. The ALE distribution model is used to model the messages exchanged between the systems. A message can have multiple recipients.
2. After the set of receivers is determined, the IDocs are processed for filtering, data conversion, and version change. An IDoc is generated for each partner identified in the distribution model. These IDocs, called communication IDocs, are then saved in the SAP database. That IDoc gets a status record with a status code of 01 (IDoc Created).
3. The IDoc goes through a syntax check and other validations. If there are no errors, the IDoc gets a status of 30 (IDoc Ready for Dispatch to ALE Service).(40.2)