Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

EDI-IDoc Method

Download as pdf or txt
Download as pdf or txt
You are on page 1of 23

Efficient EDI-IDoc

Method for Sending


Billing Documents
Efficient EDI-IDoc Method for Sending Billing Documents:

Step 1: Prepare Data


• Gather all necessary billing document information such as invoice numbers,
customer details, and line item data.

Step 2: Determine Communication Protocol


• Choose the appropriate communication protocol for EDI-IDoc transmission,
typically using protocols like AS2 or SFTP.

Step 3: Configure IDoc


• Configure the IDoc (Intermediate Document) to represent the billing document. This
involves defining the structure of the IDoc and mapping the relevant data fields.

Step 4: Generate IDoc


• Create the IDoc using your ERP system or a dedicated middleware. Populate the
IDoc with the billing data from Step 1.

Step 5: Translate to EDI Format


• Convert the IDoc data into the EDI (Electronic Data Interchange) format. This
involves transforming the structured IDoc data into the specific EDI syntax required
for transmission.

Step 6: Validate EDI Data


• Validate the EDI data for compliance with the selected EDI standards and partner-
specific requirements.

Step 7: Secure Data

• Ensure the data is secure by implementing encryption and digital signatures as


required by your communication protocol.

Info@ambikeya.com || www.ambikeya.com || +917746805189


Step 8: Transmit EDI Data
• Transmit the EDI data via the chosen communication protocol. This might involve
establishing a connection, sending the data, and receiving acknowledgments.

Step 9: Monitor Transmission


• Monitor the transmission process to ensure the EDI data reaches the intended
recipient. Check for any errors or issues that might arise during transmission.

Step 10: Receiving and Processing


• The recipient's system will receive the EDI data and convert it back into an IDoc
format.

Step 11: Inbound IDoc Processing


• Process the inbound IDoc within the recipient's ERP system. This might involve
validating the data, updating records, and triggering appropriate actions (e.g.,
payment processing).

Step 12: Acknowledgment


• The recipient's system generates an acknowledgment (typically an EDI
acknowledgment) indicating the successful receipt and processing of the billing
document.

Step 13: Error Handling


• Establish a process for handling errors, including failed transmissions, data
discrepancies, or rejected IDocs. Implement retries or manual intervention as
needed.

Step 14: Logging and Reporting


• Maintain logs of all EDI-IDoc transactions for audit and reporting purposes. This
helps in tracking the history of transactions and troubleshooting any issues that may
arise.

Info@ambikeya.com || www.ambikeya.com || +917746805189


Topics covered:
1) What is EDI
2) Create a logical system
3) Assign the logical system to the client
4) Create the RFC destination with the external system information and login
credential
5) Create RFC port
6) Configuration of output determination
7) Define Partner profile 8) Business process

Introduction:

In order to cash process we have different documents that we have to exchange with our
customer among them there is the billing document it comes after the shipment of the
product to the customer thanks to this document the customer can make the payment
now the question that may come from our mind is that by what means we can send the
billing document to our customer?
Of course, in SAP there are different ways to send the billing document to the customer,
but one that is commonly used in the project is: EDI (Electronic Data Interchange).
And that is exactly what we are going to see today, how to send the billing document by
EDI in SAP S/4HANA.

1) What is EDI
EDI means Electronic Data Interchange in SAP, EDI makes it possible to exchange
business application documents with an external partner's system instead of
printing them on paper.

2) Create a logical system

Tcode : SALE

Info@ambikeya.com || www.ambikeya.com || +917746805189


Info@ambikeya.com || www.ambikeya.com || +917746805189
3) Assign the logical system to the client
Select the client and press display

Info@ambikeya.com || www.ambikeya.com || +917746805189


Create the RFC destination with the external system information and login credential

T-code: SM59
Select ABAP connections and click on create button

Info@ambikeya.com || www.ambikeya.com || +917746805189


In the Target Host put the IP address of the receiver system
But for the test purpose I will use the ip address of my own system but it real time
scenario you should maintain the IP address of the customer’s system

Info@ambikeya.com || www.ambikeya.com || +917746805189


After click on logon and security tab
Here maintain the user id of the customer and password
Click save button

After click on connection test

Info@ambikeya.com || www.ambikeya.com || +917746805189


4. Create RFC port
T-code : WE21

Select transactional RFC and click to create button

Fill in the description and assign the RFC destination we created earlier.

Info@ambikeya.com || www.ambikeya.com || +917746805189


Our port is : A000000020

4) Configuration of output determination


Output determination is the process to determine the “media” such as printouts, telexes,
faxes, e-mails, or EDI that are sent from one business to any of its business partners.

Go to Tcode: NACE

Select Application as: V3 and press output Types.

Info@ambikeya.com || www.ambikeya.com || +917746805189


We will use the standard EDI output type – AUS1
Double click on the output type AUS1

The transmission medium is EDI and partner function is SH- Ship to party
Select processing routines

Info@ambikeya.com || www.ambikeya.com || +917746805189


So far we don't need to customise anything, we just use the standard tool
provided by SAP through the program - RSNASTED, and our customer will receive
the invoice document via EDI.

Go back to Tcode: NACE select application V3 and choose procedures

Info@ambikeya.com || www.ambikeya.com || +917746805189


Choose the procedure V10000 and press control button

Remember we already manage the standard EDI output type – AUS1


Just add it here and save

Info@ambikeya.com || www.ambikeya.com || +917746805189


7) Define Partner Profile
T-code: WE20
Choose Create.

The partner number is the number of the customer to whom we want to send the invoice.
Partner type: KU- Customer. And click to save button

Info@ambikeya.com || www.ambikeya.com || +917746805189


Select + button to fill the outbound parameters because our purpose is to send the billing
document to our customer to make a payment

This screen appears.

Info@ambikeya.com || www.ambikeya.com || +917746805189


Provide this information
Output Mode: select Pass IDoc Immediately Partner role:
SH- Ship to party.
Message type: INVOIC
Receiver port: A000000020
And Select Message Control tab.

Info@ambikeya.com || www.ambikeya.com || +917746805189


Info@ambikeya.com || www.ambikeya.com || +917746805189
Choose + button.

Provide this information:

Application: V3
Message type: AUS1

Process code: SD09 and save.

Info@ambikeya.com || www.ambikeya.com || +917746805189


8) Business Process
All configuration it’s done now we are ready to test our business process
Remember our purpose is that once we save the billing document the output type AUS1
is executed and send EDI with IDoc immediately

This is our invoice in VF02 T-code

Save

Info@ambikeya.com || www.ambikeya.com || +917746805189


Check the output type

The status is green, which means that the output type AUS1 has been successfully
executed.
Select Processing Log button

Everything is green, proof that our client has received the invoice

We can display the IDoc in Tcode: WE02

Info@ambikeya.com || www.ambikeya.com || +917746805189


IDoc is executed successfully

Info@ambikeya.com || www.ambikeya.com || +917746805189


Info@ambikeya.com || www.ambikeya.com || +917746805189

You might also like