Dynamics 365 & SAP Logistics Integration Consultant
Budget: €3,000 – €5,000 EUR
Request for Business Central Integration Consultant (Spain) Project: Integration between Microsoft Dynamics 365 Business Central (SaaS) and 3PL Logistics Provider Project Overview Our company operates Microsoft Dynamics 365 Business Central (SaaS) as ERP system for our Spanish sales entity. Warehouse operations and order fulfillment are outsourced to a Spanish 3PL provider operates SAP and exchanges operational data with our Business Central system via XML-based message interfaces. The integration currently processes multiple business documents automatically, including: -Sales Orders-Delivery / Shipment confirmations-Invoices-Return OrdersThe Business Central implementation and the integration layer were developed by an external Business Central development partner. While the current integration handles the majority of standard scenarios successfully, several complex logistics scenarios and edge cases still cause processing issues, including: -Partial shipments-Multiple deliveries per order-Returns and reverse logistics-Inconsistent master data references-Ambiguities in XML message field definitionsA major challenge is the technical clarification of the interface semantics and business process logic between the logistics provider and the Business Central development team due to language barriers and incomplete documentation. We are therefore looking for an experienced Business Central Integration Consultant based in Spain who can act as a functional and technical interface between the logistics provider and the Business Central development team.
Objectives of the Engagement
The objective of this engagement is to stabilize and complete the existing system integration by: - Clarifying the EDI/XML message structure and semantics - Aligning the business process logic between SAP and Business Central - Defining clear functional requirements and integration rules - Supporting integration testing and validation
Scope of Work
1. Analysis of Current Integration Architecture
The consultant will analyze the existing integration landscape, including: - Overall system architecture - Document flow between Pharma provider SAP and Business Central - Current XML message structure - Existing EDI mapping and message processing logic - Business Central posting logic triggered by incoming messages Key tasks include: - Reviewing the current integration architecture and document flow - Understanding the implemented message processing logic - Identifying failure points and missing scenarios - Reviewing dependencies on master data and reference data
2. Interface Clarification with Logistics Provider (Spanish)
The consultant will communicate directly with Pharma provider (in Spanish) to clarify technical and functional aspects of the interface. This includes: - Validation of XML message schemas and field semantics - Clarification of SAP document structures - Identification of event triggers and message generation logic - Verification of field-level meaning and mapping assumptions Particular focus should be placed on: - Delivery confirmation messages - Quantity logic (ordered vs delivered vs cumulative) - Document references - Return processing flows The consultant should collect example XML messages for each business scenario.
3. Definition of Integration Logic and Functional Requirements
Based on the analysis and clarification phase, the consultant will define the required integration behavior. Deliverables include: - Functional integration specifications - Documented EDI field mappings - Definition of message processing rules - Business rules for document creation and posting in Business Central Typical artifacts include document flow definitions, field mapping specifications, business scenario definitions and error handling logic.
4. Integration Testing and End-to-End Validation
The consultant will support end-to-end integration testing in cooperation with the Business Central development partner. Responsibilities include: - Definition of integration test scenarios - Verification of correct document creation and posting - Validation of EDI message processing - Coordination of test cycles with the development team Example test scenarios include: - Standard order fulfillment - Partial shipment handling - Split deliveries - Return processing - Invoice generation based on shipment data
Required Qualifications
Microsoft Dynamics 365 Business Central
Strong functional knowledge of Business Central SaaS, especially in: - Sales and order management - Sales shipment and invoice posting - Integration-related document processing Experience with custom integrations and extension-based implementations is preferred.
Integration / EDI Experience
Strong experience in system integrations in supply chain environments, including: - EDI integrations
- XML-based message exchange - Message transformation and mapping - Document flow orchestration between systems Experience with ERP-to-3PL integrations is highly desirable.
Logistics / Supply Chain Understanding
Understanding of logistics execution processes, including: - Order fulfillment - Shipment confirmation - Partial deliveries - Return logistics
Language Skills
- Native or fluent Spanish - Professional English The consultant will act as a communication bridge between the Spanish logistics provider and the international development team.
Nice to Have
- Experience with SAP-based integration partners - Experience with 3PL logistics environments - Experience with Business Central integration architecture
Engagement Model
- Project-based consulting engagement - Remote collaboration with international stakeholders - Estimated effort: several weeks or months depending on analysis results
Expected Outcome
At the end of the engagement, the integration between Business Central and the logistics provider should be clearly documented, functionally aligned, technically stable and capable of handling complex logistics scenarios automatically.
Objectives of the Engagement
The objective of this engagement is to stabilize and complete the existing system integration by: - Clarifying the EDI/XML message structure and semantics - Aligning the business process logic between SAP and Business Central - Defining clear functional requirements and integration rules - Supporting integration testing and validation
Scope of Work
1. Analysis of Current Integration Architecture
The consultant will analyze the existing integration landscape, including: - Overall system architecture - Document flow between Pharma provider SAP and Business Central - Current XML message structure - Existing EDI mapping and message processing logic - Business Central posting logic triggered by incoming messages Key tasks include: - Reviewing the current integration architecture and document flow - Understanding the implemented message processing logic - Identifying failure points and missing scenarios - Reviewing dependencies on master data and reference data
2. Interface Clarification with Logistics Provider (Spanish)
The consultant will communicate directly with Pharma provider (in Spanish) to clarify technical and functional aspects of the interface. This includes: - Validation of XML message schemas and field semantics - Clarification of SAP document structures - Identification of event triggers and message generation logic - Verification of field-level meaning and mapping assumptions Particular focus should be placed on: - Delivery confirmation messages - Quantity logic (ordered vs delivered vs cumulative) - Document references - Return processing flows The consultant should collect example XML messages for each business scenario.
3. Definition of Integration Logic and Functional Requirements
Based on the analysis and clarification phase, the consultant will define the required integration behavior. Deliverables include: - Functional integration specifications - Documented EDI field mappings - Definition of message processing rules - Business rules for document creation and posting in Business Central Typical artifacts include document flow definitions, field mapping specifications, business scenario definitions and error handling logic.
4. Integration Testing and End-to-End Validation
The consultant will support end-to-end integration testing in cooperation with the Business Central development partner. Responsibilities include: - Definition of integration test scenarios - Verification of correct document creation and posting - Validation of EDI message processing - Coordination of test cycles with the development team Example test scenarios include: - Standard order fulfillment - Partial shipment handling - Split deliveries - Return processing - Invoice generation based on shipment data
Required Qualifications
Microsoft Dynamics 365 Business Central
Strong functional knowledge of Business Central SaaS, especially in: - Sales and order management - Sales shipment and invoice posting - Integration-related document processing Experience with custom integrations and extension-based implementations is preferred.
Integration / EDI Experience
Strong experience in system integrations in supply chain environments, including: - EDI integrations
- XML-based message exchange - Message transformation and mapping - Document flow orchestration between systems Experience with ERP-to-3PL integrations is highly desirable.
Logistics / Supply Chain Understanding
Understanding of logistics execution processes, including: - Order fulfillment - Shipment confirmation - Partial deliveries - Return logistics
Language Skills
- Native or fluent Spanish - Professional English The consultant will act as a communication bridge between the Spanish logistics provider and the international development team.
Nice to Have
- Experience with SAP-based integration partners - Experience with 3PL logistics environments - Experience with Business Central integration architecture
Engagement Model
- Project-based consulting engagement - Remote collaboration with international stakeholders - Estimated effort: several weeks or months depending on analysis results
Expected Outcome
At the end of the engagement, the integration between Business Central and the logistics provider should be clearly documented, functionally aligned, technically stable and capable of handling complex logistics scenarios automatically.