About PPR Data

The PPR data checkers can check and repair, when possible, the data.

The PPR data checkers use external rule files to:

1. Detect errors and warnings regarding PPR data inconsistencies.
2. Try to repair these connections.

The PPR data checkers used to check and repair, when possible, the PPR data and inconsistent links are the following:

• ImplementLinkPrdPrcsChecker which detects patterns regarding the implement link connections between Manufactured Product and Product or EBOM.
• ImplementLinkPrcsProdSysChecker which detects patterns of implement link patterns regarding the implement link between Production System (System & Operations) and Manufactured Product.
• ImplementLinkProdSysRscChecker which detects data patterns regarding the implement link between Resource and Production Systems.
• PPRLinkChecker which detects data model patterns regarding three kinds of PPR connections: the Data Requirement connection which defines the explicit requirement in a Manufactured Product Structure; the Product Flow connections that are used to define the flows between Operations and Systems; and the Time Constraint connection that is used to define the constraint of time in the Production System Modeler.
• MfgProductInstChecker which detects specific cases of implement links between Manufactured Product and Product that are considered as inconsistent.

A semantic relation, or SR, is a path which links a source object to a target object.

The following describes the graphical elements used for semantic relations:

Element	Concept	Description
	Semantic relation removed	The semantic relation has been removed from the connection using the Edit Link isolate functionality, for example.
	Semantic relation broken	At least one of the object pointed by the semantic relation does not exist anymore in the database.
	Semantic relation resolved	The semantic relation is not removed and the all the objects pointed by the semantic relation exist in the database.