Unilever Integration Quick Start Guide
Unilever Integration Quick Start Guide
Introduction to Integration
Introduction
Regardless of how your buyer is connected to the Ariba Network, you may integrate your back-
end ERP system in following ways: Supplier
Unilever
EDI
EDI (ANSI X.12/
EDIFACT) Integration
CSV Integration
CSV
(Invoice only)
Integration is recommended for suppliers with 300+ documents/year. In case your transactional
volume is lower, we recommend submitting invoices online.
cXML > 500 docs/year All (Ariba supported) HTTPS Premier and • Ariba Standard
• existing integration above • Must adhere to Ariba cXML guides
capability
EDI - X.12 > 500 docs/year * 810 (Invoice) VAN / AS2 Premier and • Industry Standard
• existing EDI * 820 (Remittance advice) (Service Request above • Must adhere to the relevant Ariba EDI guide
needs to be
infrastructure * 850 (Purchase Order) submitted for
• Following doc. types are NOT supported:
* 855 (Order confirmation) connectivity Summary invoice with line item details, Credit
* 856 (Shipping note) setup) note with line item detail, BPO
* 997 (Acknowledgement)
EDI – > 500 docs/year * ORDERS (Purchase VAN / AS2 Premier and • Industry Standard
EDIFACT • existing EDI Order) (Service Request above • Must adhere to the relevant Ariba EDI guide
needs to be
(D98A) infrastructure * INVOIC (Invoice) submitted for
• Following doc. types are NOT supported:
* DESADV (Shipping note) connectivity Summary invoice with line item details, BPO,
* CONTRL setup) Order Confirmation, Remittance Advice
(Acknowledgment)
CSV > 500 docs/year Invoice only Manual Premier and • Only if Unilever enables this functionality
• lack of infrastructure for upload via AN above • CSV Format/template specific to a Buyer and
cXML/EDI cannot be used generically for another Buyer
> 500 docs/year All (Ariba supported) • Database Enterprise • Very flexible
• no need for additional • Disk (Dell Boomi • Dell Boomi Supported SaaS and On-Premise
Infrastructure/software • FTP Standard) or Applications:
• Flat file • HTTP/S Enterprise • Sage Peachtree
• XML Plus • Intuit Quickbooks
• EDI (Extended) • Microsoft Dynamics
• Database • Any other ERP/Package listed other than above
will need to be build from scratch:
• Design/Requirements of Integration
solution & Transactions
• Development by Ariba
• Testing Between Buyer-Ariba-Supplier
• Deployment
Once all prerequisites have been completed, you will be contacted by our Integration specialist. Please note
that each buyer might have different required fields and our specialist will guide you through the process.
Standard integration process takes 6 to 8 weeks. It is recommended that you transact online via your Ariba
account before integration is completed.
The benefit of Integration is that systems communicate with each other, without manual human intervention.
EDI integration is recommended, when you have an existing integration infrastructure. If you don’t have an
EDI infrastructure already, cXML is always recommended, as it is Ariba’s native language without any
limitations of scope or content.
To select the right integration type, please review the Integration options (slide 3) to verify transaction
volume, supported documents and connection types.
Boomi is recommended to sellers with no EDI or cXML capabilities. It requires no additional resources and
allows quick and efficient document exchange.
Dell Boomi facilitates mapping and communication between your ERP system and Ariba Network (under
secure web services).
Data integration requires testing, before you start transacting with real trading
documents. Please set up your test account as per below.
To create a test account, select your name in top right corner and choose
“Switch to Test ID”. Click OK when Ariba Network displays a warning
indicating You are about to switch to Test Mode. Create Username and
Password for your test account (first time only).
Your Test account should be configured to match your Production account - this will ensure the testing
results are consistent with what will result in Production. Please follow steps from Configuration Guide for
detailed account setup.
Your technical specialist will need to have access to your company’s Ariba account.
To create a User, select your company name in top right corner and go to Users.
First create a Role, add ALL permissions that are needed for thorough testing (usually you add only the
permissions that correspond to the user’s actual job responsibilities) and type a descriptive Name.
2
The same process needs to be
repeated in Test account as well.
Once the administrator of your company’s Ariba account provides you with access, you’ll have two different
credentials for your Production and your Test account. You can login to both of these accounts under
http://supplier.ariba.com.
1 2
EDI connection requires a service request to establish connectivity. To submit a ticket, log into your account.
Click the Help link in top right corner. Click Help Center and go to Support section.
Search for “EDI connectivity” and click button Create Online Service Request.
Fill out our webform, select Problem Type, note Unilever in the Issue Description and click Submit.