EDI Print Output
EDI(Electronic Data Interchange) – It is a electronic data change between two parties to reduce the paper based work.
There are different EDI formats used for invoice, few of them are like below
EDI 810- Invoice
EDI 850- Purchase Order
EDI 856- Advance Shipment Notification
Consider the company sales a product to one of its customer and finally the company creates a Billing Document and sends this document to its customer to make the payment.
So this billing document can be send to the customer by many ways: Print Output(Smart Form/Adobe Form) and send to the customer or Send the FAX is another option or Send by EDI process. Etc.
In SAP, EDI uses the IDoc container to carry the data(billing information).
The below post shows how to set the EDI output for billing process.
Go to Tx- NACE
Select Application as: V3 and choose output Types.
SAP already gives a sample EDI output type – AUS1 ( this will be used for the demo).
Double click on the output type.
In Default Values tab, the transmission medium is EDI and partner function is SH- Ship to party. Choose processing routines from left side.
The program – RSNASTED executed when this output type is triggered and send EDI to the target customer.
Now from Tx- NACE choose application as – V3 and choose procedures.
Select the procedure which is used in billing. For demo its- V10000 , choose the procedure and select Control from left side.
Here we can add the EDI output type and save it.
Now create a sales document and then create a billing.
Open the billing document in Tx- VF02 .
To see the output types, navigate as shown with the menu path.
Here few output types are triggered automatically but the EDI output type is not determined.
In Tx- VF02 go to change mode.
Navigate along the menu path to see the output.
We are in change mode now.
As the EDI output type AUS1 is not determined automatically, we can add it manually. Now add it and choose Medium as EDI.
We get the below error message.
When you set the EDI output for the billing document and save it, the system tries to send the billing information in EDI format to the customer. In the system the customer partner profile must be created with the PORT( RFC Destination).
Now we have to define a customer partner profile in the Tx- WE20.
Choose Create.
The partner number must be same as the CUSTOMER number to whom you want to send the EDI. Choose partner type as KU- Customer.
As you want to send something to the customer, the outbound process section to be filled. Choose + button.
The below screen appears.
Provide partner role as SH- Ship to party. In SAP, EDI uses the IDoc container to carry the data. Provide the message type.
Port number- ( must be defined in Tx- WE21) point to the customer system RFC destination.
Provide the IDoc type. Select Message Control tab.
Select + button.
Here provide application as V3 and message type as AUS1 and process code as – SD09 and save.
Once the customer partner profile is ready, we can add the EDI output type AUS1 for the billing document and Save. Once SAVE happens the output AUS1 processing routine is executed which tries to send EDI with IDoc.
Let’s check the billing output again.
Now the Status is Green for AUS1. Choose this and select Processing Log button.
The processing log says the IDoc with number sent to the target.
We can track the IDoc in Tx- WE02
Provide the IDoc number and execute.
IDoc is sent to the customer sytstem.
For the demo, the port contains the RFC destination of another SAP system but not the customer system.
In the target system, we can check the Idoc with Tx WE02
The IDoc status is red. So the inbound process must be configured properly to make the status as green.
SAPCODES 