Application Development and Automation Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
Shyam4U
Explorer
26,289

In SAP, effective document management is essential for seamless business operations. Transaction code NACE serves as a critical tool for configuring and managing output determination, enabling organizations to generate and distribute documents such as invoices, purchase orders, and delivery notes. This blog provides a comprehensive overview of NACE and its applications. 

In SAP, the output management process plays a crucial role in generating and distributing business documents like invoices, purchase orders, and delivery notes. One of the primary tools used for configuring these outputs is the NACE transaction code. This blog will guide you through the process of creating and customizing an output type in SAP using NACE. 

NACE T-code  

NACE is a transaction code in SAP ABAP used for output determination. It helps in configuring and managing the output types for various documents like purchase orders, sales orders, delivery notes, and billing documents. Here's a brief overview of its components: 

  • Application: Defines the type of document (e.g., EF for purchase orders, V1 for sales documents). 
  • Output Types: Specifies the format and medium of the output (e.g., print, email, fax). 
  • Processing Routines: Links the output type to the driver program and the form (e.g., SAP script or Smart form) used for generating the output. 

Using NACE, you can dynamically determine the output based on various conditions, making it a flexible tool for managing document outputs in SAP. 

Key Features of NACE 

Centralized Configuration: Simplifies the setup and management of output determination for different business processes. 

Support for Multiple Application Areas: Covers diverse areas such as sales (V1), purchasing (EF), and inventory management (ML). 

Customizable Output Types: Allows the creation and configuration of custom output types tailored to business needs. 

Integration with Forms: Supports integration with SAP script, Smart Forms, and Adobe Forms for document formatting. 

SAP Output Processing – SAP Output Message with SAP NACE 

This article explains how to create a new SAP Output Message using the NACE T-code. It provides a step-by-step tutorial covering all the necessary customizations to set up a fully functional output message type from scratch. 

Create a new sap output message Type 

Step 1: Call NACE T-code and Go to Output Types 

Launch the SAP Transaction Code NACE for Conditions for Output Control. 
First let’s select the Output Types as following and The Application (for Sales, Application is V1) Shyam4U_0-1735884710170.jpeg

Step 2: Change display mode to edit mode then Create New entryShyam4U_1-1735884710172.jpeg

Step 3: Fill ID of SAP Output Message Type, description and access typeShyam4U_2-1735884710174.jpeg

Create the output type with a custom name starting with "Z." 

Step 4: Set NACE Output Type Dispatch Time for? sap output message 

You can process a message immediately by updating the application document or you can process it at a later time. For later processing you must use the report program RSNAST00? or a corresponding application function.Shyam4U_0-1735885850817.jpeg

  • Send with periodically scheduled job: The message is processed through report program RSNAST00. This report program can be scheduled periodically or started manually 
  • Send with job, with additional time specification: As in time 1, but the message contains an earliest processing date and a requested processing time. The message is ignored by report program RSNAST00 before the requested date. 
  • Send with application own transaction: The message is selected and processed by application specific programs. Processing can take place online or in the background 
  • Send immediately (when saving the application): The message is processed when the application document is saved. No further processing of the message is necessary.

Step 5: Set Message Transmission Medium Specifies how the output will be produced. 

You can specify, for example, that the output is printed or that it is produced and sent by other means, such as fax, electronic mail, or electronic data interchange (EDI/ IDoc). Shyam4U_0-1735886165581.jpeg

Step 6: Set Partner Function a sample list of used function partner in Output TypeShyam4U_0-1735887628938.jpeg

SP: Sold-To Party 

BP: Bill-to Party 

SH: Ship-To Party 

PY: Payer 

LS: Logical System? 

Etc....... 

Step 7: Set Processing routines 

For each Transmission Medium, a processing routine must be configured. For this sample, the Output Type triggers an IDoc with the program RSNASTED within the routine EDI_PROCESSING. Shyam4U_0-1735888962513.jpeg

You can leave all the rest of tabs blank.
When Saving, SAP will ask you for customization request. (Good point: Nace Configuration in transportable)

Step 8: Set Partner Functions Determination

Here by clicking the 'New Entries' fill the value as shown belowShyam4U_0-1735889235458.jpeg

Step 9: Create Condition Records 

Go Back to NACE transaction and select Condition Records 
Remember we have configured the Access sequence defined in a previous step, create condition for output type. Shyam4U_0-1735889381293.pngShyam4U_0-1735889462648.jpegStep 10: Create Output Procedure

Go Back to NACE transaction and select Procedures Shyam4U_0-1735889652688.pngShyam4U_0-1735889704190.jpeg

Step 11: Assign Output Procedure to transaction type

Go to SPRO Customizing and find where the customizing point to maintain Output DeterminationShyam4U_0-1735890666979.jpegShyam4U_0-1735890827698.jpeg

Test Output Message 

here the last step. test your output message and check if the SAP Output processing in well done.

(For Order, for example? try to modify an SAP order, then save. Go to message > Header > and check the output processing if it is green)

Troubleshooting 

if Message Output doesn't appear in header > message on Transaction, verify this point:

  • Is record conditions meet the criteria of the Transaction?
  • Is record conditions maintained?

if you can add manually the Output type you have created, make sure this Output is used on output procedure (NACE) Active for the transaction type (SPRO)

Conclusion  

Transaction code NACE is a powerful tool for configuring output determination in SAP. By following the steps outlined in this blog, you can create and manage output types effectively, ensuring smooth and automated document processing for your business processes. Whether you are dealing with invoices, purchase orders, or delivery notes, NACE provides the flexibility and control needed to meet your organization's requirements.

1 Comment