Delivery GI Posted' Condition in SAP Delivery Outputs: Routine Assignment and Testing

Introduction

Output management in SAP plays a critical role in document-driven business processes. From sales orders to purchase documents, from deliveries to invoices, the system generates outputs based on specific triggers. These outputs are managed through output determination schemas, where each output type is activated under certain conditions. This article focuses on how routines (conditions) assigned to output types work and how they are configured.

What Are Output Determination Schemas and Output Types?

An output determination schema defines which output types are applicable for a specific document type and under what access sequences and conditions they will be triggered. Each output type—such as a sales order confirmation or an invoice printout—is defined in the system via NACE or SPRO. Output types can be triggered based on document content, document type, recipient, or other criteria.

What Is a Routine (Condition) and Why Is It Used?

Routines are ABAP functions used to make output conditions more dynamic and specific. Each output type can be linked to a routine, which checks conditions beyond the general configuration rules. For example, if an output should only be triggered when the document value exceeds a certain amount, this logic can be implemented through a routine.

To access the output determination procedure used for delivery documents, follow the SPRO path below:

📍 SPRO > Logistics Execution > Shipping > Basic Shipping Functions > Output Control > Output Determination > Maintain Output Determination for Outbound Deliveries > Maintain Output Determination Procedure

This screen displays the output procedures for outbound deliveries, showing how output types are linked to access sequences and conditions. The path is clearly highlighted in the attached screenshot.

Then follow this:

I am assigning the 'Delivery GI Posted' condition to our delivery output. After adding this condition, I expect the output to be triggered only when the Goods Issue has been posted for the delivery document.

We are checking the output of the delivery document for which the picking process has been completed and saved.

We can see that the output was not triggered because the Goods Issue has not been posted

Now let’s post the Goods Issue and check the output

We can see that the output is triggered once the Goods Issue is posted.

Through this example, we have demonstrated how to integrate a custom routine into a delivery output and verified how it controls the output triggering process. By defining the right conditions, outputs can be restricted to trigger only after specific business steps are completed, ensuring process integrity and system accuracy.

We hope this approach to conditional output management in SAP helps bring more control and precision to your logistics processes. See you in our next article.

OĞUZHAN VURUŞKAN

SAP SD CONSULTANT