An output type defines the characteristics and attributes of the output itself, as shown in figure below. We access the output types on transaction NACE by selecting an application and clicking the Output type button.
Then double click an output type to see its details. Examples of output types available for a sales order are BA00 (sales order response), ESYM (internal output), and MAIL (mail).
We define the following attributes for an output type, beginning with the output type name, which is a maximum of four characters long. Examples of output type names are NEU and BA00.
On the General Data tab, we define the following:
Access Sequence: Basically, this is a set of business rules.
Access to Conditions: If you select this flag, the values for the output medium and timing are determined from the condition records using the access sequence. For the output types used in the SD modules (sales, shipping, and billing), if this flag is not selected, the values for the output medium and timing are not determined from the condition records. Instead, those values are determined from the customer master data.
In the customer master data, an output view exists in the sales area data to specify the values for the output medium and the language. Specifying the values in the customer master is useful when you do not have any complex rules and the values for the output medium and timing are based on the customer number.
Cannot Be Changed: This determines whether the output can be edited.
Multiple Issuing: This determines whether multiple outputs are permitted.
Change Output: Here we can specify a program and form routine that determines whether changes made to the document are relevant for sending the output in a change mode.
On the Default Values tab, we define the following:
Transmission Medium: Possible values include EDI, print, SAP office mail, workflow, and ALE.
Dispatch Time:This determines whether the message is sent immediately or in batch.(86)
Related Posts
EDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
EDI outbound parameters view part one and Two
EDI partner profile configuration
Then double click an output type to see its details. Examples of output types available for a sales order are BA00 (sales order response), ESYM (internal output), and MAIL (mail).
We define the following attributes for an output type, beginning with the output type name, which is a maximum of four characters long. Examples of output type names are NEU and BA00.
On the General Data tab, we define the following:
Access Sequence: Basically, this is a set of business rules.
Access to Conditions: If you select this flag, the values for the output medium and timing are determined from the condition records using the access sequence. For the output types used in the SD modules (sales, shipping, and billing), if this flag is not selected, the values for the output medium and timing are not determined from the condition records. Instead, those values are determined from the customer master data.
In the customer master data, an output view exists in the sales area data to specify the values for the output medium and the language. Specifying the values in the customer master is useful when you do not have any complex rules and the values for the output medium and timing are based on the customer number.
Cannot Be Changed: This determines whether the output can be edited.
Multiple Issuing: This determines whether multiple outputs are permitted.
Change Output: Here we can specify a program and form routine that determines whether changes made to the document are relevant for sending the output in a change mode.
On the Default Values tab, we define the following:
Transmission Medium: Possible values include EDI, print, SAP office mail, workflow, and ALE.
Dispatch Time:This determines whether the message is sent immediately or in batch.(86)
Related PostsEDI Message control configuration and part two
Maintaining partner profiles in EDI
EDI in bound parameters over view
EDI outbound parameters view part one and Two
EDI partner profile configuration
No comments :
Post a Comment