I Qwes. Re: What are the Standard output types in SD?

Standard Output Types in SD are as under: 1. Sales Order Confirmation: 2. Outbound Delivery Note: 3. Billing Document: 5. Cash Sales: 6. Inquiry: 7. Quotation: 8. Contract: 9. Picking List:
The output type is used to represent various forms of output in the SAP R/3 system. Sales and Distribution processing uses output types such as order confirmation, freight list, invoice, and so on. You use the output type to control whether an order confirmation, for example, is sent through EDI. In the Customizing application, you can display the output types available in the SAP R/3 system. To display sales output types, for example, go to Customizing and choose Sales and Distribution → Basic Functions → Output Control → Output Determination → Output Determination Using the Condition Technique → Maintain Output Determination for Sales Documents → Maintain Output Types.

BA00 LD00 RD00

RD03 AF00 AN00 KO00



Output Type
An output type (or also a "condition type") summarizes messages of the same meaning. It contains parameters that are valid for all its assigned messages, for example appropriate partner functions.

BA00 (order confirmation), MAIL (internal message), KRML (credit limit exceeded)

For each transmission medium, one form routine in a program is assigned to the output type. This form routine is called for processing the message (message status record).

Select your application and select Edit → Output types. The following diagram shows that for order messages the output type BA00 (order confirmation) was defined with condition access (that is to say the message determination is called). IV Defining Output Types Prerequisites Archiving An object type and a document type are needed for archiving. for example transmission medium 6 (EDI). in the messages. In addition. Here you can also determine whether specific processing times should be excluded. In change mode select Edit → New entries. that is to say. Save your entries. The document type is defined in SAP ArchiveLink Customizing. You can select one of the two following alternatives: • Select the appropriate activity from Customizing in the relevant application • Use transaction NACE in expert mode. It makes no sense to create a . 3. In addition. however in some cases it is dynamically transferred by the application to Message Control. The document type to be used can then be entered in the Storage system title of the message type The Storage mode selection field controls whether a message is outputted. 4. Procedure 1. The object type is mostly predefined for the application. stored or outputted and stored.For transmission medium 7: SAPoffice mail you can assign the output type title and text of mails which are used as default values in the condition records. It is important that the object type used there is assigned to the document type. one or more condition tables (last hierarchy level) can be assigned to an access sequence. 2. One access sequence (next hierarchy level) is assigned to the output type. control parameters for message determination and exits (that can occur during message determination) are declared for the transmission media "Print" and "Mail" (SAPoffice). see Defining Output Types Integration Output types come after procedures in the condition component hierarchy. The following describes this alternative. The entry of a document type is only necessary in the last two cases. Default values are declared for the condition record for output type BA00. For more information. You can also define default values for the condition records in your new definition.

the communication strategy stored here would then be followed. It makes sense for transmission medium 5: When creating a condition record for order acknowledgment. .communication strategy for this transmission medium.

Sign up to vote on this title
UsefulNot useful