In this article

Product Information

Introduction
FAQ
Core module
- Introduction
- Process overview
- Trading partners and documents
- FAQ
- Setup
  - EDI parameters
  - EDI shared parameters
  - Trading partners
  - Batch control group
  - Document type mapping
  - UOM mapping
  - Cleanup profile
  - Reset status
  - Connection setup
- Processing
  - Functional acknowledgement outbound
  - Functional acknowledgement inbound
- Managing files
- Workspaces
  - EDI document maintenance workspace
- Inquiries
  - Functional acknowledgement received
  - Trading partner documents
- Other
- Technical Guide
Customer module
- Introduction
- Process overview
- FAQ
- Setup
  - Trading partners
  - Warehouses
- Processing
- Workspaces
  - Sales order processing workspace
- Other
  - Data entities
  - Security configuration
Vendor module
- Introduction
- Process overview
- FAQ
- Setup
  - Trading partners
- Processing
- Workspaces
  - Purchase order processing workspace
- Other
  - Data entities
  - Security configuration
3PL module
Freight forwarder for Landed cost module
- Introduction
- Process overview
- FAQ
- Setup
  - Trading partners
- Processing
- Workspaces
  - Landed cost processing workspace
- Other
  - Data entities
  - Security configuration
Integration systems module
- Introduction
- Setup
  - Integration systems
  - Trading partners
- Processing
  - Customer
  - Customer group
Roadmap and release schedule
Definitions and Acronyms

Release Notes

10.0.43.20250829
Installation process

Previous Versions

Archive

Deprecated

This document describes the features that are either new or changed in the release version .

Deprecated

Microsoft deprecation notice

Microsoft notice

Likely to affect: Companies that uses Database credential type for their Azure blob connections. Key Vault credential type is not affected. These connections can be found at ‘EDI > Setup > Connection setup > Azure sites’
Status: Rollout for the change by Microsoft begins in October 2024 in a phased manner. Changes will be backported to 10.0.41 (PU65) and all later releases.
What do you need to do if affected:
- Step 1 - Create Connection string in Azure portal
- Step 2 - In Key vault parameters create a Secret using the value created in step 1.
- Step 3 - Change all applicable Azure blob connections:
  • Credential type: Key Vault
  • Key vault: Secret setup in step 2