Showing results for 
Search instead for 
Did you mean: 

how to configure Email output in SD

Former Member
0 Kudos

Dear friends Pls sent me details of how to configure email output in SD module.


Thanks & Regards,


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos


If your SD output configuration is set up correctly, an e-mail from SAP using medium 5 should go through just fine via SAPconnect (transaction SCOT). When it works, the external recipient should receive an e-mail with a PDF attachment containing the form image, regardless of whether it has been created via SAPscript or Smart Forms. Depending on your output determination settings, this even can happen in the background, without any interaction with the SAP front end (e.g. for invoices created automatically by a batch job).

Typically, a failed send will be flagged in the message control table (NAST), and this table should be monitored closely. However, there are many reasons why a document hasn't gone through, and this can be the case with both outgoing faxes and e-mails from SAP. The solution to both is the same: After identifying the failed document, re-send it manually by going inside it in change mode and repeating the appropriate output. If an obsolete customer e-mail address was the culprit, a customer master change would also be required, along with an audit of any docs recently created for this customer.

If any underlying data has changed since initial issuance, a re-sent document may not appear identical to the (failed) original. Sometimes, as when address info has been corrected, this can be a good thing. After all, the new document is more accurate than the old one.

In other cases, such as when pricing info has changed, it might be a cause for serious concern. There are several ways to deal with this concern:

1) Limit the types of changes allowed on certain docs after creation

2) Set up a doc image archive via ArchiveLink and re-issue output from there instead of from the current doc; or

3) For highly sensitive docs, consider a more secure delivery method.


<a href=",289625,sid21_gci1027361_tax294895,00.html">Sending a Smart Form output via e-mail</a>

Answers (4)

Answers (4)

0 Kudos


Idoc Def :Standard SAP format for electronic data interchange between systems (Intermediate Document). Different message types (such as delivery confirmations or purchase orders) normally represent different specific formats, the IDoc types. However, multiple message types with related content can be assigned to one IDoc type: For example, the IDoc type ORDERS01 transfers the "logical" message types ORDERS (purchase order) and ORDRSP (order confirmation).

Idocs are of two types basic type and the extension type .we need to configure the system settings for this process .

IDOC (Intermediate Document) - A data holder.

IDOC is divided in to three parts.

Control Record

Data Record

Status Record

Control record (Table: EDIDC):

- Every IDOC has only one Control Record

- Each Control Record contains header information like:

o IDOC Number

o Direction of IDOC: Inbound or Outbound

o Date and Time of creation of IDOC

o Date and time when the IDOC was last modified.

o Message Type of IDOC

o IDOC type and extension of IDOC

o Sender and Receiver Partner

Data record – (Table: EDID4):

- Data Record contains Data to be processed.

- Every IDOC has one data record with multiple segments in hierarchy.

- Segments and Hierarchy of Segments are defined by IDOC Type and Extension.

- IDOC created has to strictly follow the hierarchy; else IDOC fails with Syntax error.

- Segments which are repetitive have qualifiers attached to it

Status record – (Table: EDIDS):

- Status Record describes the status of IDOC.

- Each IDOC contains one status Record with multiple status information.

- Status at each level is appended to IDOC. E.g. When IDOC is created in SAP, Status is “This IDoc has been generated through a test transaction”, When the IDOC is added to system it is “IDOC added”, “IDOC ready to be transferred to Application”……

- Status should always be read bottom-up. Status at the top is the latest status.

- Some Example of Status Records:

o Inbound:

§ 53 - IDOC successfully posted

§ 51 – IDOC Failed

§ 64 - IDOC ready to be transferred to Application



§ 30 – IDOC ready for Dispatch

§ 03 – IDOC passed to port OK

§ 12 – IDOC Dispatched

§ 16 – Functional Acknowledgement Positive

§ 17 – functional Acknowledgement Negative

IDoc Type: Defines the segments and hierarchy of segments

o Transaction Code:

§ WE30 – To create, change or display the IDOC type and the extension.

§ WE31 – To create the Segment

- IDOC type defines the segments to be used in the IDOC.

- It also defines the hierarchy and syntax of the segments.

- IDOC extension is nothing but to add segments to standard IDOC types.

- Transaction WE31 allows you to create segments.

- Program RSEIDOC3 documents the use of each IDOC type.


Attributes of a Segment:

- Mandatory Segment: If checked, this segment should always exist in the IDOC.

- Minimum Number:

- Maximum Number: Maximum number of times this segment can be repeated in IDOC. -

Parent Segment: Parent of this segment

- Hierarchy level: Level of hierarchy.

Segment Definition (WE31):

Messsage Type: Defines the type of data in the IDOC

o Transaction Code:

§ WE81 – To create, change or display the Message type and the extension.

§ WE82 – Using this transaction you can link Message Type, IDOC Type, IDOC Extension and version.

- Message type identifies the type of data IDOC holds. E.g. Orders (ORDERS), Delivery (DESADV), Invoice (INVOICE). It also defines what needs to be done with the data in the IDOC, in case of Inbound IDOC, and which data to be extracted in case of Outbound IDOC.

- Message Type is linked to a process code, which in turn is linked to a Function Module. This function module extracts from or posts data to SAP depending on direction of IDOC.

- Relation between Message Type, IDOC type and IDOC extension needs to define. Without this relation Message type or IDOC type cannot be used.

Message Type Create, Change or Display (WE81):

Setup link between Message Type, IDOC Type, IDOC Extension and Version (WE82)

Process Code: Function Module is linked to a process code. This function module in executed for inbound or outbound IDOC.

o Transaction Codes:

§ WE41 – Outbound Process Code

§ WE42 – Inbound Process Code

- Process codes are linked to a Function Module.

- Relationship is Message Type is linked to a Process Code which is linked to a Function Module.

- In case if you are using a stand alone code to trigger an IDOC, you need not define a process code.

RFC Destination: System definition of destination.

o Transaction Code: SM59

- RFC destination identifies the destination of IDOC.

- In case of ALE:

o In ALE the communication mode is IDOC to IDOC, hence the type used is R/3 Connections.

o It is the destination SAP system which will receive the IDOC.

o In RFC destination you define the destination SAP system details like System, Login and Password.

Go thr below links:


Former Member
0 Kudos

mail sent from


0 Kudos
0 Kudos

Hi Sridhar,

check the forum before posting the question .

you need to maintain the email address of the customer in the customer master and then need to configure the output type in the NACE transction .and in the settings choose the medium as email.


Former Member
0 Kudos

Dear friends !!

Can any one tell me about IDOCs and how to configure IDOCs and where to assign them for automatic output between vendors and customers.

If possible with configuration document and screen shots!!

Sreedhar Kodali