Purchase Order Template Business Central

Standard Operating Procedure: Purchase Order (PO) Template Standardization in Microsoft Dynamics 365 Business Central

Document ID: TR-OPS-BC-042
Effective Date: 2023-10-27
Version: 1.0.4
Review Cadence: Semi-Annual
Target Audience: Procurement Specialists, Finance Controllers, Systems Architects

---

1. Executive Summary & Scope

This SOP defines the standardized configuration and deployment of Purchase Order (PO) templates within Microsoft Dynamics 365 Business Central (BC). The scope encompasses the design of the Word Layout, data mapping via XML mapping pane, and the integration of these templates into the Report Selection - Purchase module. Adherence to this procedure ensures compliance with IFRS/GAAP reporting standards and maintains data integrity across the Procure-to-Pay (P2P) lifecycle.

---

2. Prerequisites & Tool Requirements

• Software: Microsoft Dynamics 365 Business Central (Cloud/On-Prem), Microsoft Word (Desktop App with Developer Tab enabled).
• Access: Permissions granted for "Report Selection - Purchase" and "Custom Report Layouts."
• Certifications: Completion of internal BC Configuration Module 4 (Purchasing Workflows).
• File Assets: Original .docx template file (TR_Master_PO_v1.docx).

---

3. Roles & Responsibilities (RACI Matrix)

---

4. Step-by-Step Operational Procedure

Phase I: Exporting the Base Layout

• Navigate to Custom Report Layouts in the Business Central global search.
• Select the Report ID 405 (Purchase Order).
• Select "Export Layout" to save the .docx template to the local workstation.

Phase II: Template Customization & Data Mapping

• Open the file in Microsoft Word and enable the Developer tab.
• Open the XML Mapping Pane (Developer > XML Mapping).
• Set the Custom XML Part to urn:microsoft-dynamics-nav/reports/Purchase_Order/405/.
• Insert required data fields (e.g., PurchasesHeader.No, PurchasesHeader.VendorName, PurchasesLine.Description) using the "Insert Content Control" function.
• Format visual elements, logo, and terms of service in accordance with the TR Brand Guidelines.

Phase III: Import & Activation

• Return to Custom Report Layouts in BC.
• Click "New" > "Insert Word Layout" and upload the modified file.
• Navigate to Report Selection - Purchase.
• Change the "Usage" filter to "Purchase Order."
• Select the newly uploaded template in the "Custom Layout Description" column.

---

5. Quality Assurance & Verification Criteria

• Audit Checklist:
  • Does the document header match the legal entity registration?
  • Are all mandatory fields (VAT ID, PO Number, Delivery Date) mapped to live BC tables?
  • Is the watermark functionality disabled to prevent layout overlapping?
• Tolerance Thresholds: Margin of error for line-item calculations must be 0.00.
• Acceptance Benchmark: Template must successfully trigger a Print/Preview action without generating a "Field Mapping Missing" error.

---

6. Practical Troubleshooting Scenarios

Scenario A: "Content Control" is grayed out/unavailable.

• Cause: The XML Mapping Pane is not linked to the specific BC namespace.
• Corrective Action: Close the document, reopen, and ensure the urn:microsoft-dynamics-nav/reports/Purchase_Order/405/ namespace is selected in the XML Mapping dropdown before attempting to map fields.

Scenario B: Purchase Order PDF shows empty fields despite correct mapping.

• Cause: Field referencing is occurring outside the Repeat tag for line items.
• Corrective Action: Highlight the Table Row in Word, navigate to the XML Mapping Pane, right-click the Line node, and select "Repeating."

Scenario C: Report Selection not updating after layout change.

• Cause: Cache synchronization delay or incorrect Report Selection Usage designation.
• Corrective Action: Clear browser cache/BC temporary data; confirm that the usage index in "Report Selection - Purchase" matches the assigned Document Type in the PO header.

---

Authorized by: Julian Vance, Chief Operations Architect