Support #102
closedUser Manual Creation for SAP MIRO Wizard
90%
Description
SAP MIRO Wizard --- Detailed Project README¶
Custom Belimo | Canofy¶
Purpose: Automate the preparation of the SAP MIRO Excel workbook
from a Bill of Entry (BOE) maintained in Canofy, reducing manual
duty-value entry while preserving a review step for exceptional or
ambiguous material matches.
1. Project Overview¶
The SAP MIRO Wizard is a Canofy-based utility for the Custom
Belimo workspace.
Its purpose is to take:
- one validated Bill of Entry (BOE) from Canofy,
- one standard SAP MIRO Excel Template,
- optionally one or more supplier invoice PDFs, and/or
- an optional PO Number,
and produce a new, populated SAP MIRO workbook.
In simple terms¶
INPUTS
│
┌──────────┼──────────┐
▼ ▼ ▼
BOE SAP MIRO Invoice / PO
Canofy Template Optional
│ │ │
└──────────┼──────────┘
▼
┌──────────────────┐
│ SAP MIRO WIZARD │
└────────┬─────────┘
▼
Match Materials
│
▼
Read BOE Duty Values
│
▼
Resolve PO / Invoice Data
│
▼
Review Match Status
│
▼
Generate Output Workbook
│
▼
SAP MIRO Matched Workbook
The wizard does not modify the source BOE and does not overwrite
the uploaded template. It creates a new output workbook.
2. Business Objective¶
The manual SAP MIRO preparation process requires users to take
information from the BOE and populate the SAP MIRO Excel template.
The wizard reduces this manual work by:
- Reading the selected BOE directly from Canofy.
- Reading the material and quantity information from the uploaded SAP
MIRO template. - Matching SAP Material Codes against BOE Part Codes.
- Matching quantities against BOE CQTY.
- Reading customs duty values from the BOE.
- Determining PO information from the invoice or supplied PO number.
- Populating the duty-related columns.
- Marking each line with a matching result.
- Generating a separate output workbook.
- Providing a Summary Log for validation before SAP MIRO posting.
The source manual describes the core model as:
One BOE + One SAP MIRO Template
│
▼
SAP MIRO Wizard
│
▼
One Ready SAP MIRO Workbook
3. Important Scope Boundary¶
The wizard prepares the Excel workbook used for SAP MIRO.
It does not itself perform the final SAP MIRO posting.
Canofy BOE
│
▼
SAP MIRO Wizard
│
▼
SAP MIRO Excel Workbook
│
▼
User reviews workbook
│
▼
Workbook used for SAP MIRO
The source manual explicitly states that the wizard reads the BOE and
creates a new Excel file; it does not change anything in Canofy. The
uploaded template also remains unchanged.
4. Application Context¶
Property Value
Application Canofy
Workspace Custom Belimo
Feature SAP MIRO Wizard
Main input Bill of Entry
Template SAP MIRO Excel Template
Optional input Supplier Invoice PDF
Optional input PO Number
Main output Populated SAP MIRO Excel workbook
Additional output Summary Log
Additional output Invoice Extracted Data, when invoice is supplied
5. End-to-End Workflow¶
The wizard contains three main steps, preceded by a mandatory
BOE/Part Code pre-check.
┌──────────────────────────────────────────┐
│ STEP 0 — PRE-CHECK │
│ Logistics verifies BOE Part Codes │
└────────────────────┬─────────────────────┘
▼
┌──────────────────────────────────────────┐
│ STEP 1 — UPLOAD │
│ │
│ Select BOE │
│ Upload SAP MIRO Template │
│ Upload Invoice PDF (optional) │
│ Enter PO Number (optional) │
└────────────────────┬─────────────────────┘
▼
Continue & Analyze
│
▼
┌──────────────────────────────────────────┐
│ STEP 2 — REVIEW │
│ │
│ Match materials │
│ Review quantities │
│ Review PO matching │
│ Review status / remarks │
└────────────────────┬─────────────────────┘
▼
Generate SAP MIRO Output
│
▼
┌──────────────────────────────────────────┐
│ STEP 3 — DOWNLOAD │
│ │
│ Review final result │
│ Download populated workbook │
└────────────────────┬─────────────────────┘
▼
SAP MIRO Workbook Ready
The source manual identifies the three wizard steps as Upload → Review
→ Download, with the current step shown in black and completed steps
shown with a green check. fileciteturn44file0
6. Mandatory Pre-Check¶
Responsibility¶
Logistics Team
Timing¶
After the BOE is created and before the SAP MIRO Wizard is run.
This is a critical prerequisite.
The wizard identifies materials by comparing:
SAP Material Code
↓
SAP MIRO Template
│
▼
PART CODE
↓
BOE Item
If the BOE Part Code is incorrect, incomplete, blank, contains an extra
space, or has a formatting difference, the wizard may classify the
material as Unmatched / Product Not Found.
The system does not automatically correct a wrong Part Code.
7. Part Code Validation¶
Every BOE item should be checked.
Correct Part Code characteristics¶
Check Correct Example of Problem
No spaces 08-0002-0045-00 08-0002-0045-00
Same code as Item Description Exact match Digits swapped
Same dash format 08-1155-0401-02 081155040102
Correct characters 01APS-10R 0IAPS-1OR
Not blank Code present Empty PART CODE
The manual notes that the correct Part Code is usually available inside
square brackets in the BOE ITEM DESCRIPTION, for example:
[08-0002-0045-00]
8. Correcting a Part Code¶
If the Part Code is incorrect:
- Open the BOE.
- Navigate to the Item tab.
- Filter the rows if required.
- Open the relevant line using the Edit icon.
- Read the correct Part Code from the Item Description.
- Replace the PART CODE with the exact value.
- Remove all leading, internal, or trailing spaces.
- Save/update the BOE.
- Repeat for all incorrect rows.
Important restriction¶
During this correction:
Change:
PART CODE
Do not change:
Quantity
Duty values
Other BOE fields
The source manual specifically warns that Part Codes should be typed
exactly and not copied from Excel/email when hidden spaces could be
introduced.
9. Pre-Check Sign-Off¶
Before the wizard is run, the Logistics Team should be able to confirm:
✓ Every BOE Item line reviewed
✓ Every PART CODE is populated
✓ Every PART CODE is correct
✓ No unwanted spaces
✓ Every "Is Part Code Match = No" line investigated
✓ BOE saved after corrections
✓ SAP MIRO Wizard team informed that BOE is ready
10. Opening the SAP MIRO Wizard¶
- Log in to Canofy.
- Open the left menu.
- Under PUBLIC, select Custom Belimo.
- Open SAP MIRO Wizard from Quick Access.
Alternative:
Ctrl + G
↓
Search "SAP MIRO Wizard"
↓
Open Wizard
The source manual identifies the wizard as a Custom Belimo workspace
feature.
11. Step 1 --- Upload¶
Objective¶
Select the shipment and provide the files/data required for analysis.
Fields¶
Field Required? Purpose
Bill of Entry Yes Identifies the Canofy
BOE to read
SAP MIRO Template Yes Provides SAP
material, quantity
and Particular lines
Invoice PDF(s) Optional Used to determine PO
numbers per material
PO Number Optional Provides one PO
number for applicable
lines
Continue & Analyze Action Starts the matching
process¶
The source manual marks Bill of Entry and SAP MIRO Template as
required fields.
12. Selecting the Bill of Entry¶
- Click the Bill of Entry field.
- Search using either:
- BOE ID, e.g.
BE-00015 - BE Number, e.g.
2666385
- BOE ID, e.g.
- Select the correct BOE.
Critical validation¶
Always verify the BE number twice.
Selected BOE
│
▼
Check BOE ID
│
▼
Check BE Number
│
▼
Confirm shipment
Do not create a new BOE from the wizard's selection list. The BOE must
already be fully created and checked in Canofy.
13. SAP MIRO Template¶
The wizard expects the standard SAP MIRO Template.
Do not:
- add columns,
- remove columns,
- rename columns,
- move columns,
- change the expected structure.
The standard data sheet is named:
DataSheet
14. SAP MIRO Template Column Structure¶
The template contains 12 columns.
Column Field Filled By Purpose
A SAP Material Code User Material/item code
B SAP In Qty User SAP quantity
C Particular User Duty type
D SAP PO Number User / Optional PO number
E Assessable Value Wizard BOE assessable value
F Amount Wizard Duty amount
G Rate Wizard Duty rate
H BE Qty Wizard BOE quantity
I IGST Rate Wizard IGST rate
J IGST Amount Wizard IGST amount
K BE PO Number Wizard PO determined from invoice/PO input
L Remarks Wizard Matching result
User-entered columns¶
A — SAP Material Code
B — SAP In Qty
C — Particular
D — SAP PO Number (optional)
Wizard-populated columns¶
E — Assessable Value
F — Amount
G — Rate
H — BE Qty
I — IGST Rate
J — IGST Amount
K — BE PO Number
L — Remarks
15. Mandatory Template Inputs¶
The following three fields must be populated for every template line:
SAP Material Code
SAP In Qty
Particular
The SAP PO Number is optional.
Each material normally has three template lines, one for each
Particular.
For example:
01APS-10R | 25 | IN Basic customs
01APS-10R | 25 | CustomsEducationCESS
01APS-10R | 25 | Customs Sec H CESS
16. Uploading the Template¶
- Go to SAP MIRO Template.
- Click Choose.
- Select the standard Excel template.
- Verify that the selected filename is displayed.
- Confirm that the template structure has not been modified.
17. Invoice PDF --- Optional¶
The supplier invoice can be uploaded when PO information must be
determined per material.
The invoice is particularly useful when one shipment contains multiple
POs.
Example:
Shipment
│
├── Material A → PO 1766754
├── Material B → PO 1766754
└── Material C → PO 1767371
An invoice can allow the wizard to identify the correct PO for each
material instead of applying one PO to every line.
Current supplier support¶
According to the supplied manual, invoice extraction is currently
supported for BELIMO invoices.
For other suppliers:
Do not upload invoice
↓
Use PO Number field
18. PO Number --- Optional¶
If all materials in the shipment belong to one PO, a single PO Number
can be supplied.
Example:
PO Number = 1740766
The wizard uses this number for applicable lines.
19. PO Resolution Logic¶
The supplied manual defines the following behavior:
Input PO resolution
Invoice PDF only PO is taken from invoice for each
material
PO Number only Same PO is used for every line
Both Invoice is used first; PO Number
fills lines not covered by invoice
Neither Matching uses Material Code +
Quantity against BOE¶
Decision flow¶
PO Inputs
│
┌────────┴────────┐
▼ ▼
Invoice? No Invoice
│ │
▼ ▼
Extract PO data PO Number?
│ │
│ ┌──────┴──────┐
│ ▼ ▼
│ YES NO
│ │ │
│ ▼ ▼
│ Use supplied No PO
│ PO matching
│
▼
Invoice PO has priority
where available
20. Continue & Analyze¶
Before proceeding:
✓ Correct BOE selected
✓ BE number verified
✓ Standard template uploaded
✓ Material Code populated
✓ SAP In Qty populated
✓ Particular populated
✓ Invoice uploaded if required
✓ PO Number supplied if required
Then click:
Continue & Analyze →
The wizard reads the BOE/template data and performs the matching.
For large invoices, the manual advises waiting for processing to
complete rather than clicking the button repeatedly.
21. Step 2 --- Review¶
Objective¶
Review the material matching results before generating the workbook.
The wizard compares the uploaded template against:
- BOE data,
- BOE quantities,
- BOE duty values,
- and invoice information when an invoice was uploaded.
No final output workbook is created until the output-generation action
is selected.
22. Review Summary¶
The Step 2 summary displays:
Count Meaning
Total Materials in the uploaded template
Matched Material and quantity found correctly in BOE
Flagged Material found but manual review is required
Unmatched Material not found in BOE
Example from the manual:
Total 76
Matched 76
Flagged 0
Unmatched 0
The desired result described in the manual is:
Matched = Total
Flagged = 0
Unmatched = 0
23. Material Review Table¶
The Step 2 material list contains:
Column Meaning
Material SAP Material Code
SAP Qty SAP In Qty from template
SAP PO PO identified for material
Status Matching result
Remarks Explanation of result
24. Match Statuses¶
Matched¶
Material + Quantity found in BOE
No manual action is normally required.
Flagged¶
The material was found, but the wizard cannot safely determine which BOE
line should be used.
Manual review is required.
Unmatched¶
The material was not found in the BOE.
The material code should be checked in:
- SAP MIRO Template
- BOE Part Code
- Product/Part Code source data
25. Generate SAP MIRO Output¶
After reviewing the summary and material list:
- Confirm the correct BOE.
- Review statuses.
- Review remarks.
- If required, click Back and correct Step 1.
- Otherwise click:
Generate SAP MIRO Output
The wizard proceeds to Step 3.
Important¶
The wizard allows output generation even when some materials are Flagged
or Unmatched.
Those lines are not automatically populated and must be manually
reviewed/filled in the resulting workbook.
26. Step 3 --- Download¶
Objective¶
Download the generated SAP MIRO workbook.
The result screen provides:
- success message,
- final match counts,
- Download Workbook,
- Start New Process.
Result statuses¶
The final result may contain:
Status Meaning
Matched Direct material/quantity match
Aggregation-Matched Multiple BOE lines combined to
match template quantity
Positional-Matched Duplicate material/quantity
resolved by line position
Flagged Requires manual review
Unmatched Not found in BOE¶
27. Aggregation-Matched¶
Aggregation occurs when the same material exists on multiple BOE lines
and the quantities together match the SAP template quantity.
Example:
BOE:
Material X → CQTY 30
Material X → CQTY 20
Template:
Material X → SAP Qty 50
The wizard can aggregate:
30 + 20 = 50
and populate the output.
However, the manual requires this to be checked.
Review procedure¶
- Open the BOE.
- Find every line for the material.
- Add the BOE quantities.
- Compare with SAP In Qty.
- If equal, the aggregation is consistent.
- If not equal, investigate the quantity mismatch.
28. Positional-Matched¶
Positional matching applies when the same material and quantity occur
multiple times and the wizard resolves the match using line order.
These lines should still be reviewed.
29. Download the Workbook¶
- Click Download Workbook.
- Wait for the generation message.
- Wait for the successful-generation message.
- The workbook is saved in the computer's Downloads folder.
Example filename format:
<template>_populated_<date>_<time>.xlsx
Example shown in the manual:
...Sea_populated_20260924_163611.xlsx
30. Start New Process¶
After downloading the workbook:
- Click Start New Process.
- The wizard returns to Step 1.
- The input fields are cleared.
Important¶
Always download the workbook before clicking Start New Process.
The current process screen is cleared when a new process starts.
31. Output Workbook Architecture¶
The generated workbook contains up to three sheets:
┌───────────────────────────────────────────┐
│ Generated SAP MIRO Workbook │
├───────────────────────────────────────────┤
│ 1. SAP MIRO Matched │
│ → Final populated MIRO data │
│ │
│ 2. Summary Log │
│ → Match / exception / duty summary │
│ │
│ 3. Invoice Extracted Data │
│ → Invoice extraction details │
│ → Present when invoice was uploaded │
└───────────────────────────────────────────┘
32. SAP MIRO Matched Sheet¶
This is the primary sheet used for SAP MIRO preparation.
It retains the template structure and contains populated duty
information.
Example structure:
Material Qty Particular SAP PO Assess. Amount Rate BE Qty IGST IGST Amt BE PO Remarks
Value Rate
01APS-10R 25 IN Basic customs 1766754 15378.19 1537.8 0.1 25 0.18 3072.6 1766754 Matched
01APS-10R 25 CustomsEducationCESS 1766754 153.8 0.1
01APS-10R 25 Customs Sec H CESS 1766754 0 0¶
33. Population Rules¶
According to the supplied manual:
Basic customs line¶
The following are populated on the IN Basic customs line of each
material:
- Assessable Value
- BE Qty
- IGST Rate
- IGST Amount
- BE PO Number
- Remarks
Every duty line¶
The following are populated for each applicable Particular:
- Amount
- Rate
Therefore, a material can have multiple Particular rows while the
material-level values are represented on the Basic Customs line.
34. Remarks Column¶
The Remarks column is critical.
Always check column L.
Remarks = Matched
↓
Normal result
Remarks ≠ Matched
↓
Review required
Do not ignore a non-Matched remark simply because the workbook was
generated successfully.
35. Summary Log¶
The Summary Log provides an audit-style summary of the run.
It includes:
Header¶
- Run date/time
- Template filename
- Bill of Entry
- BE number
- PO matching method
A --- Matched Items¶
Contains information such as:
- Material
- SAP Qty
- SAP PO
- BE CQTY
- BE PO
- Number of rows
- Status
- Notes
Aggregation and positional matches are also identified here.
B --- Flagged Items¶
Contains:
- Material
- Flag Type
- Action Required
C --- Unmatched Items¶
Contains:
- Material
- Reason
Totals¶
Contains:
- Final counts
- Total Duty Populated in INR
36. Duty Validation¶
Before SAP MIRO posting:
Summary Log
│
▼
TOTALS
│
▼
Total Duty Populated
│
▼
Compare with BOE
│
▼
Confirm consistency
The manual specifically recommends cross-checking the Total Duty
Populated against the BOE before posting in SAP.
37. Invoice Extracted Data Sheet¶
When an invoice PDF is uploaded, the generated workbook can contain an
Invoice Extracted Data sheet.
It contains information read from the invoice, including:
- Invoice Number
- Position
- Material
- Description
- Quantity
- UOM
- Origin
- Unit Price
- Net Price
- HSN Code
- PO Number
This sheet can be used to verify that the invoice was read correctly.
38. Exception Handling¶
The wizard uses specific remarks to identify cases that require review.
The four primary cases documented in the manual are:
1. Aggregation Detected
2. Duplicate – Unresolved
3. Quantity Mismatch
4. Product Not Found / Unmatched
39. Exception --- Aggregation Detected¶
Example¶
BOE:
Material X → 30
Material X → 20
Template:
Material X → 50
Wizard result¶
AGGREGATION DETECTED
Action¶
- Open BOE.
- Find all occurrences of the material.
- Add CQTY values.
- Compare with SAP In Qty.
- Confirm the aggregation is correct.
40. Exception --- Duplicate Unresolved¶
Meaning¶
The same material appears multiple times in the BOE with different
quantities, but no single line or clear aggregate matches the template
quantity.
Example BOE quantities:
24
1
125
25
The wizard does not automatically populate the line when it cannot
safely resolve the correct BOE record.
Action¶
- Open Summary Log → Flagged Items.
- Identify the material.
- Review the BOE occurrences.
- Use PO and invoice information to identify the correct line(s).
- Populate the SAP MIRO Matched sheet manually after verification.
41. Exception --- Quantity Mismatch¶
Meaning¶
The material exists, but:
SAP In Qty ≠ BOE CQTY
Action¶
- Check the template quantity.
- Check the BOE quantity.
- Determine which source is incorrect.
- Correct the template or request correction of the BOE.
- Run the wizard again using corrected data.
42. Exception --- Product Not Found / Unmatched¶
Common causes¶
- Extra space
- Missing dash
- Incorrect character
- Incorrect Part Code
- Blank Part Code
- Wrong BOE selected
- Material genuinely missing from BOE
Resolution¶
Unmatched
│
▼
Check Summary Log
│
▼
Compare Template Material
with BOE Part Code
│
├── Template wrong
│ ↓
│ Correct template
│
├── BOE Part Code wrong
│ ↓
│ Logistics corrects BOE
│
└── Material missing
↓
Verify BOE with team
│
▼
Run Wizard Again
The manual warns against entering duty values manually for an Unmatched
material without first checking the BOE.
43. Important Matching Logic¶
The overall matching concept can be represented as:
SAP MIRO Template
│
├── Material Code
├── Quantity
├── Particular
└── PO
│
▼
Matching Engine
│
┌─────┴───────────┐
▼ ▼
BOE Data Invoice Data
│ │
└────────┬────────┘
▼
Match Resolution
│
┌────────┼───────────┬─────────────┐
▼ ▼ ▼ ▼
Matched Aggregated Positional Flagged /
Match Unmatched
44. Data Flow¶
CANOFY
│
│ Read
▼
┌───────────────┐
│ BOE │
│ Items + Duty │
└───────┬───────┘
│
│
┌────────────────────┼────────────────────┐
│ │ │
│ │ │
▼ ▼ ▼
Material Code Quantity Duty Values
│ │ │
└────────────────────┼────────────────────┘
│
▼
Matching Engine
▲
│
SAP MIRO Template
│
┌──────┴──────┐
▼ ▼
Material Code Qty
│
▼
PO Resolution
▲
│
┌──────┴────────┐
▼ ▼
Invoice PDF PO Number
│
▼
PO by Material
│
▼
Output Workbook
45. Full Decision Flow¶
START
│
▼
Is BOE created?
│
├── NO → Create / complete BOE
│
└── YES
│
▼
Logistics Part Code pre-check
│
▼
Are all Part Codes correct?
│
├── NO → Correct BOE Part Code
│ Save BOE
│ Re-check
│
└── YES
│
▼
Open SAP MIRO Wizard
│
▼
Select BOE
│
▼
Upload template
│
▼
Invoice / PO if required
│
▼
Continue & Analyze
│
▼
Review results
│
┌──────┼───────────────┐
▼ ▼ ▼
Matched Flagged Unmatched
│ │ │
│ │ │
│ ▼ ▼
│ Manual review Check code
│ in output / BOE
│ │ │
└──────┼───────────────┘
▼
Generate SAP MIRO Output
│
▼
Download Workbook
│
▼
Review Summary Log
│
▼
Cross-check duty
against BOE
│
▼
Ready for SAP MIRO
46. Troubleshooting¶
Problem Likely Reason Action
BOE does not appear BOE not created or Verify BE number and
wrong number confirm BOE exists
Continue & Analyze does Required field is empty Fill Bill of Entry and
nothing SAP MIRO Template
Template rejected Standard format changed Use the standard
template without
changing columns
SAP PO values are empty No invoice and no PO Upload invoice or enter
Number PO Number
Wrong PO on lines One PO supplied for Upload invoice for
multi-PO shipment material-level PO
matching
Invoice not read Supplier not currently Use PO Number instead
supported
Many materials Wrong BOE selected Go back and select the
unmatched correct BOE
Material unmatched Part Code has Logistics corrects BOE
although present in BOE typo/space/format issue Part Code
Duty values look wrong BOE source values are Correct source BOE and
wrong rerun
Workbook does not Browser blocked Allow downloads and
download download retry
Flagged material Duplicate/ambiguous BOE Review Summary Log and
lines output manually
Quantity mismatch Template quantity Verify both sources and
differs from BOE CQTY correct the wrong
source¶
47. Operational Safety Rules¶
Rule 1 --- Never select the wrong BOE¶
The wizard reads the duty values directly from the selected BOE.
Wrong BOE
↓
Wrong source values
↓
Wrong SAP MIRO workbook
Always verify the BE number twice.
Rule 2 --- Do not modify the template structure¶
Do not:
- add columns,
- remove columns,
- rename columns,
- move columns.
Use the standard template.
Rule 3 --- Do not ignore Remarks¶
The workbook can be generated even when some lines require review.
Always inspect:
SAP MIRO Matched → Remarks
Summary Log → Flagged Items
Summary Log → Unmatched Items
Rule 4 --- Do not guess duty values¶
For exceptions:
Source BOE
↓
Verify
↓
Correct source/template
↓
Regenerate
Do not guess customs duty values.
Rule 5 --- Download before starting another process¶
The current process is cleared when Start New Process is clicked.
Therefore:
Generate
↓
Download
↓
Review / Save
↓
Start New Process
48. Best Practices¶
The supplied manual recommends:
- Run the wizard only after Logistics completes the Part Code
pre-check. - Verify the BE number twice.
- Always use the standard SAP MIRO Template.
- Never add, remove, or rename template columns.
- Keep material codes exactly aligned with the BOE.
- Upload the BELIMO invoice when multiple POs exist.
- Read the Summary Log after every run.
- Review every line that is not
Matched. - Cross-check Total Duty Populated against the BOE.
- Download the workbook before starting a new process.
49. Quick Reference¶
Step User Action Button / Result
0 Logistics checks BOE Update / Save
Part Codes
1 Select BOE, upload Continue & Analyze
template, invoice/PO if →
required
2 Review matching results Generate SAP MIRO
Output
3 Review result and Download Workbook
download workbook¶
50. User Journey at a Glance¶
SAP MIRO PREPARATION
│
▼
┌────────────────────┐
│ 1. BOE Pre-Check │
│ Part Codes correct │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 2. Upload │
│ BOE + Template │
│ Invoice / PO │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 3. Analyze │
│ Material Matching │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 4. Review │
│ Match / Flag / │
│ Unmatched │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 5. Generate │
│ SAP MIRO Output │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 6. Download │
│ Excel Workbook │
└─────────┬──────────┘
▼
┌────────────────────┐
│ 7. Validate │
│ Remarks + Duty │
│ against BOE │
└─────────┬──────────┘
▼
READY FOR SAP MIRO
51. Source Manual Visual Reference¶
The supplied SAP MIRO Wizard User Manual v2 contains 27 pages of UI
guidance and screenshots.
Important visual sections include:
-
Pages 6--10: BOE search, BOE verification, Item tab, Part Code
review and correction. -
Page 11: Custom Belimo workspace and SAP MIRO Wizard entry
point. -
Pages 12--16: Step 1 Upload interface, template structure,
invoice upload and PO handling. -
Pages 17--19: Step 2 Review, summary counts, material statuses
and output generation. -
Pages 20--21: Step 3 result screen, final match categories and
workbook download. -
Pages 22--23: Generated workbook structure and invoice extracted
data. - Pages 24--25: Exception handling and remarks.
- Pages 26--27: Troubleshooting and best-practice guidance.
The screenshots on these pages are particularly important for
identifying the actual Canofy controls and workflow labels used by the
application.
52. Project Outcome¶
The SAP MIRO Wizard changes the preparation process from manual
duty-value entry to a controlled data-driven workflow:
BEFORE
BOE
│
▼
User manually reads duty values
│
▼
User manually enters Excel
│
▼
Manual verification
│
▼
SAP MIRO
AFTER
BOE ───────────────┐
│
SAP MIRO Template ─┼──► SAP MIRO Wizard
│ │
Invoice / PO ──────┘ ▼
Automated Matching
│
▼
Duty Population
│
▼
Review / QC
│
▼
SAP MIRO Output Workbook
│
▼
Final SAP MIRO Use
53. Final Acceptance Checklist¶
Before using the generated workbook for SAP MIRO, confirm:
Source¶
- Correct BOE selected.
- BE number verified twice.
- BOE Part Codes checked by Logistics.
- No unwanted Part Code spaces.
- Template uses the standard structure.
Inputs¶
- SAP Material Code populated.
- SAP In Qty populated.
- Particular populated.
- SAP PO Number supplied when appropriate.
-
BELIMO invoice uploaded when material-level PO extraction is
required.
Matching¶
- Step 2 summary reviewed.
- Matched materials reviewed.
- Flagged materials investigated.
- Unmatched materials investigated.
- Aggregation-Matched lines checked.
- Positional-Matched lines checked.
Output¶
- SAP MIRO Matched sheet reviewed.
- Remarks column reviewed.
- Summary Log reviewed.
- Invoice Extracted Data reviewed when invoice was uploaded.
- Total Duty Populated cross-checked against BOE.
- Workbook downloaded and saved.
Final¶
✓ Source BOE verified
✓ Matching reviewed
✓ Exceptions investigated
✓ Duty cross-check completed
✓ Output workbook downloaded
✓ Workbook ready for SAP MIRO processing
Document Control¶
Field Value
Document SAP MIRO Wizard --- Detailed Project README
Application Canofy
Workspace Custom Belimo
Feature SAP MIRO Wizard
Source SAP_MIRO_Wizard_User_Manual_v2 (1).docx
Source pages 27
Primary input Bill of Entry
Secondary input SAP MIRO Excel Template
Optional input BELIMO Invoice PDF / PO Number
Primary output Populated SAP MIRO Workbook
Validation output Summary Log
Invoice output Invoice Extracted Data
Final business use SAP MIRO preparation
Files