01 Configuration

Upon successfully installing the application you can see the FTP/SFTP/AS2 Syncing menu.

02 AS2 (Applicability Statement 2) Configuration

If you would like to use the AS2 protocol please follow steps below.

Your Configuration

• Your GLN Number: Enter your company's unique GLN (Global Location Number). This number identifies your organization in EDI communication. Maximum length is 13 digits.

• Certificate Validity (Days): If you are generating the certificate from the button, then you have to enter the validity of the Certificate. In simple terms, for how much period of time you want this certificate to be valid?

• Your Certificate: You have to either upload the certificate along with the private key. If you do not have the public/private keys then you can generate them with given "Generate your Certificate & Key" button.

• Your Private Key: You have to upload the private key if you have. If not then, you can generate the key-pair from given "Generate your Certificate & Key" button.

Partner Configuration

• Partner: Select the partner (customer or supplier) for whom the AS2 configuration is being created.

• Partner's GLN Number: Enter the partner's GLN (Global Location Number) used to identify them in EDI transactions.

• Partner's URL: Enter the URL provided by the partner. This URL is used to send EDI messages through the AS2 protocol.

• Upload Partner's Certificate: Upload the partner’s public certificate. This certificate is used to encrypt messages before sending them to the partner.

Export Data File Configuration

• Encryption Policy: Define how outgoing EDI messages should be secured.
• The following policies are supported:

• Un-signed & Un-encrypted

• Un-signed & Encrypted

• Signed & Un-encrypted

• Signed & Encrypted

Choose the option based on the security requirement agreed with the trading partner.

Message ID Customisation: Specify a custom identifier to be included in the AS2 Message ID header.This helps partners identify the source system or sender of the message.

Import MDN Configuration

MDN Policy: Defines how the system should handle Message Disposition Notifications (MDN).

• Supported policies

• Un-signed MDN Required

• Signed MDN Required

MDN confirms that the partner has successfully received the AS2 message.

ANSI Customer Side Configuration

• ANSI Update Inventory Location: Select the inventory location where product stock quantities will be updated when the Product Inventory (846) file is imported from the partner.

• Warehouse: Select the warehouse where the inventory operations will be applied during the import of the Product Inventory (846) file. The stock quantities received from the partner will be updated for this selected warehouse.

• Use 997 Confirmation: If this option is enabled, the system will import the Functional Acknowledgment (EDI 997) for the exported files.

EDI File Mapping

• Message Type: in which define the only ANSI import file message type. for example if bill import then according ANSI file format 810 is come in the edi file format. only need to define for import file.

03 Export Purchase Order Process

Click the Export 850(PO) button to export the Purchase Order (850) in RFQ state. and the PO is automatically exported using AS2 configuration. and the exported file is attached to the record. and with that if 997(functional ackwoldgemnt) required then it also imported. You can view the attachment and msg in the chatter for reference.

If there are any changes in the PO, update it and click Export 860 (CPO) in the RFQ Sent state. The PO is automatically exported using AS2, and the file is attached to the record.

If 997 (Functional Acknowledgment) is enabled, both 997 and 855 (PO Acknowledgment) will be imported; otherwise, only 855 will be imported. You can check the attachment and messages in the chatter for reference.

04 Import Vendor Bill Process

You can view the imported Vendor Bill(810) using the Vendor Bill smart button. You can also check the source of the imported bill from the "EDI AS2 ANSI(Customer)" page.

05 Import ASN Process

Inside the purchase order, you can find the receipt(856) that will be updated.

It updates the quantity and tracking reference in the receipt.

The source for this document update, such as the purchase reference and AS2 reference, can be seen in the Related AS2 Receipt Import tab. Update messages are also available in the chatter.

06 Import Vendor Pricelist Process

This Vendor Pricelist is created through the AS2 import process(832),You can view it in the Vendor Pricelist menu.

07 Import Product Inventory Process

In this process, the Product Quantity (846) file is imported into the Odoo database and updates the On Hand Quantity of the products. The Stock Quants are created through the AS2 import process, which retrieves the product quantity information from the AS2 partner.

Log details can be found under the 'Log Details' menu in FTP/SFTP/AS2 syncing, capturing both successful and failed operations for reference.

If you encounter any issues while using our app that are caused by the app itself, we offer complimentary support for 90 days from the date of purchase.