The screen and the API count the same products, and the screen is sealed
The number of products in the EPM demo model is counted twice on the same system: with the “Number of Entries” button of SE16 in SAP GUI, and with the $count of the OData service that projects the same table. The two must be equal; a gap would reveal a service that filters, a phantom record or a mismatched client. The selection screen used for the count is then compared with a reference screenshot by perceptual fingerprint (Screen Should Match Baseline), volatile areas masked: the pixel channel sees what neither the API nor scripting can see.
Proof: Suite “API cross-check and screen sealed by a visual assertion”: 3/3 on A4H (release 754), validated on July 17, 2026 and replayed on October 5, 2026, with 205 EPM products via OData and 205 via SE16.
Product Count Agrees Across API And GUI Channels # … ${gui_count}= Count Table Entries ${EPM_PRODUCTS_TABLE} Should Be True ${gui_count} > 0 ... msg=Table ${EPM_PRODUCTS_TABLE} vide : données EPM absentes sur ce système ? ${api_count}= Get Odata Count ${EPM_PRODUCTS_PATH} alias=a4h Should Be Equal As Integers ${api_count} ${gui_count} ... msg=OData $count (${api_count}) ≠ SE16 ${EPM_PRODUCTS_TABLE} (${gui_count}). Log Produits EPM : ${api_count} via OData == ${gui_count} via SE16. # … SE16 Product Screen Matches Its Visual Baseline # … Open Table In SE16 ${EPM_PRODUCTS_TABLE} Log Screenshot Écran de sélection SE16 de ${EPM_PRODUCTS_TABLE} (source du compte GUI) Screen Should Match Baseline ${VISUAL_BASELINE_NAME} ... threshold=${VISUAL_THRESHOLD} baseline_directory=${VISUAL_BASELINE_DIR} ... mask_elements=auto per_resolution=${True}

















