Objective

The F&B Power BI Mapping view connects source F&B departments with the intended PMI cockpit mapping. In the legacy screen, the table separates Source Interface information from PMI Mapping and includes a Cockpit selection and an Ignore option.

This is a configuration view for the authorized mapping owner. It should be used with a confirmed understanding of the source department codes and the intended reporting structure.

Read the mapping table

Confirm the property and interface context. Review each source item and its current cockpit destination. Expand source rows where the screen provides additional detail.

A source name describes the incoming item; a cockpit name describes the PMI destination. Similar names are not enough to establish the correct relationship. Use the agreed mapping specification or confirm it with the source-data owner.

Review a proposed change

  1. Identify the source department or item that needs attention.
  2. Confirm the intended PMI cockpit with the operational/reporting owner.
  3. Inspect its existing mapping and whether Ignore is selected.
  4. Apply the approved mapping through the current interface’s supported control.
  5. Confirm that the change was saved and review the resulting reporting data using the supported refresh/reload process.

Do not use Ignore simply because an item is unfamiliar. Confirm whether excluding that source item is intentional and what it means for the report.

Example

A fictional source department named Outlet A appears without its expected destination. The mapping owner confirms that it belongs to Demo Restaurant, updates the supported mapping and checks the result with the reporting owner. The owner also checks that the item is not represented by another source code already mapped to the same business activity.

Investigate missing or unexpected data

Check source delivery, interface context, expanded child rows, the selected cockpit and any Ignore state. A correct mapping does not by itself prove that the source file arrived or the analytics report refreshed.

For historical corrections, confirm whether a reload or a report refresh is required. Do not promise that a mapping edit automatically recalculates all prior periods without checking the supported process.