Trigger IDOC_OUTPUT_ORDRS using custom program.

Question

Hello.
I have a requirement to send an order response (ORDERS05) IDoc by calling FM IDOC_OUTPUT_ORDRS using a custom program.  Wanted to know if anyone had suggestions on the best approach.  We are using much of the native mapping and adding a few segments (which I would handle updating in the customer exits).
My biggest question is how to setup the call to IDOC_OUTPUT_ORDRS.  I think I need to simulate the NAST table entry.  Is that the recommended approach?  Any tips or hints would be appreciated.
Thanks,
Cal
Edited by: Cal on Feb 3, 2009 7:07 PM

Answer 1

Actually condition technique based on which output determination works - is designed for exactly what you are asking - triggering the output type under certain conditions.
You can create ouput condition records with key fields that represent your business conditions: for example certain sales org, distrib channel, certain sales order type can only trigger the output. You can make it as finer as you want (like even including sold-to as a criteria), like you can include any field that appears in the sales document as a criteria to trigger the idoc.
The tables that store condition records - condition tables - are custom created with your business field combination that you want to base the triggering upon.
Goto the IMG path:
IMG -> SD -> Basic functions -> Output control -> Output determination -> Maintain output determination for sales documents.
1. A o/p determination procedure is assigned to sales document type
2. A o/p determination procedure comprise a list of output types, which are checked sequentially by the system
3. Custom condition tables with new business criteria can be assigned to new or existing access sequence
4. Access sequence is attached to output type
How the system triggers a particular output type during application document processing, say sales order processing:
1. From the sales document type, the o/p determination procedure is determined
2. The system then checks the output types inside the procedure one by one
3. Say at output type 1, the system checks to see what access sequence it has
4. The access sequence comprises of 1 or more condition tables.
5. The system then checks each condition table, by comparing the key fields of the condition table with the correpsonding sales document fields - like comparing sales org, documen type in the condition record with what the sales document has. If every thing matches, the output type is triggered.
I have just simplified the whole o/p determination. There are several other features which are controlle at o/p determination, procedure, output type and access sequence levels. Spend some time one these, it is a neat, flexible and future proof concept. You will never regret! )