Debugging Outbound IDoc Output Control scenarios
My previous blog gave some insights into configuring message control: Message Control (Output Control) for ALE But how do we test the scenarios involving message control. How do I debug the outbound IDoc generation programs involved in message control (most of the time there is a need to test the custom logic within the user-exits of outbound program)? Example scenario: I have configured message control for Delivery IDoc (DELVRY03) generation (message type DESADV). Whenever the outbound delivery is saved the output type is proposed and outbound IDocs are triggered. Generally while defining the condition record we set the “Date/Time” field to 4 (Send immediately (when saving the application)). Due to this whenever we save the delivery document (which satisfies the message control configuration) the output type is proposed and the IDocs are triggered. Even if we have set a breakpoint in the outbound application IDoc generation program, we do not stop to that break-point. When we do an F4 on the “Date/Time” field we find the other 4 options. Our interest is in option 1 = “Send with periodically scheduled job”. With this option the output type is proposed but not processed immediately by output type processing program (RSNAST00). The output type entry remains unprocessed in NAST table. With this setting when I create an outbound delivery and check in the delivery output we find the output type in yellow traffic light. Now when we run the program RSNAST00 for the output application and output type (other parameters can also be specified if we want to be specific) the program will stop at the break-point in the outbound function module (IDOC_OUTPUT_DELVRY in this case). We can debug from hereon.