EDI Message Control Configuration

Message control also referred to as output control or conditioning techniques a cross application component used as a service program in several areas. The biggest application is in pricing, but you also use Message control for output determination in EDI and account determination and material determination in the SD (Sales and Distribution) module.

The basic concept behind Message control is to generate and manage outputs from an application and control their timing and medium of exchange. We can create the following outputs when a sales order is entered in the system
  1. An internal mail message to the production control staff immediately ·
  2. A sales order response to the customer via fax immediately ·
  3. Printed output for warehouse personnel when necessary ·
  4. A sales order response to the customer via EDI at night ·
  5. Workflow notification to the quality engineer at the end of the day ·
  6. A sales order to another system via ALE.
The Message control encapsulates if−then business rules without having to write ABAP/4 programs. The Message control technique has proven to be quite useful and provides a consistent way of generating outputs from several applications. Most SD and MM applications are enabled to use the Message control component.

Benefits of Message Control:

Disconnecting the process of creating an application document from the process of generatingoutputs: For example, the sales order transaction VA01 does not have any logic in its code to generate IDocs for the EDI process. Creating application documents and generating IDocs are two separate processes. The separation helps keep errors in one process from affecting the processing of the other component.

Automatically proposing output based on business rules specified in Message control: Rules can be very generic or very specific. After the business rules are encapsulated in the Message control, the output is proposed only when the business conditions are met.

Overriding the automatic proposal: Although you can set up the system for automatic proposal, the system allows for the outputs to be edited before they are sent. For example, an EDI message is sent to vendor xxxxx for purchase orders. However, the vendor has reported some temporary problems and does not want to accept EDI for a certain time period. We can delete the proposed output, and the system will not send the EDI document.

Manually selecting an output: Some business rules require human intelligence and, therefore, cannot be encapsulated in the Message control. For example, an internal notification is to be sent to an MRP (Material Requirements Planning) planner when the delivery date proposed by the sales system is unacceptable to a customer and the customer is a major one.

Generating multiple outputs:The system can propose any number of desired outputs (for example, printed output and order response via EDI) at the same time.

Controlling the timing, medium, and language of the output messages: As part of the configuration, you can specify all these parameters. For example, EDI can wait until the end of the day for transmissions, but the internal notifications can be printed immediately.

Retransmitting an output: If a printed output is lost or if an EDI transmission fails at the subsystem level and it is necessary to retransmit the output, the system can resend the output without having to duplicate the application document.

Monitoring the results of execution: The results of processing an output type are logged in the system, and they can be monitored from the application document.

Related Posts

Maintaining partner profiles in EDI
EDI in bound parameters over view
EDI outbound parameters view part one and Two
EDI partner profile configuration
EDI inbound process

No comments :

Post a Comment