Show TOC

 iPPE Consistency Check

Use

The iPPE consistency check is used to check the master data of one or more products that were maintained with iPPE in SAP APO and DIMP. You execute the check before the data is used in other functions, such as Requirements Planning or Production Planning .

Integration

  • The master data required to manufacture a product are bundled in a production version. ‘Therefore, the data in production versions are checked with the consistency check.You can choose several production version for the check.

  • You can call up the consistency check in the following ways:

    • As a program for checking mass data with the following names:

      • PPEAPO_CONSISTENCY_CHECK in SAP APO

      • PPEDI_CONSISTENCY_CHECK in DIMP

    • As a report on the Reports tab page in the navigation area of the iPPE Workbench Professional for checking one or more production versions.

    • In the context menu of the iPPE Workbench Professional

    • As a transactionOn the SAP Easy Access screen, choose Start of the navigation path Integrated Product and Process Engineering Next navigation step iPPE Consistency Check End of the navigation path .

  • The system executes the iPPE consistency check automatically if you generate a PDS for all models in SAP APO. See Generate Production Data Structures (PDS) for all Models .

Prerequisites

  • There are one or more production versions for the product.

  • There are line balances and line networks when you work with lines.

  • There are routings when you are working with shop-floor-oriented manufacturing.

Features

  • You can save the results of the consistency checks and call these up at a later point in time.

  • In the results screen of the consistency check, you can go to the iPPE Workbench by choosing iPPE Workbench , and correct any errors contained in the data.

  • When you execute a new consistency check, first determine which production versions and which time period you want to find and check.

  • Then determine which checks should be executed. There are the following checks, listed according to application:

    Product Structure:

    • Plant-Specific Material Status :

      Checks if materials in the specified plant have been released in the validity period of the production version.

    • Item Without Material :

      Checks if variants or assembly items exist in the product structure that have no material assigned to them.

    • Object Dependency Status :

      Checks if the object dependency at the variants has the status Released .

    • Variants Without Object Dependency :

      Checks if there are variants in the product structure that have no object dependencies assigned to them and for which the Standard Variant indicator is not set.

    • Standard Configuration Available :

      Checks if there is a configuration at the variants of the structure or access node in the production version.

      Process Structure:

    • General Structure Check :

      Checks for all routing types

      • If at least one activity exists in the routing.

      • If an operation has at least one activity.

      • If an activity has at least one mode.

      • If routing objects are used multiple times in a routing.

        Checks for routings and SNP routings

      • If recursions occur in the relationships.

      • If all activities above relationships are connected.

      • If redundancies occur when maintaining relationships between operations and activities in multi-level routings.

      • If scheduling data is complete.

      • If primary resources that can be used in capacity requirements planning are specified.

      • If capacity requirements are complete.

      • If at least one mode of an activity can be selected automatically.

      • If different change statuses of a mode have different valid-from dates.

        Checks for routings only

      • If the mode linkage via primary resources or mode IDs are consistent for different change statuses at the mode.

      • If scrap and reporting points only exist at the last production activity below operations.

      • If only the first setup activity below the operation has a setup group or setup key.

      • If the following was selected below an operation for individual relationships:

        Mode linkage via primary resources

        Continuous load

        End-start relationships

      • If SA assignments are unique and complete.

      • If object dependency is released.

      • If only end-start relationships and mode linkages via primary resources exist in CTM planning.

        Checks for SNP routings only

      • If a maximum of one mode is maintained at an activity, or no breaks have been maintained in CTM planning.

        Checks for CTM planning

      • If all activities form a sequence.

      • If modes do not have different change statuses.

      • If no setup groups and setup keys have been maintained.

      • If no consumption times exist for components.

      • If output is available at the last production activity only.

    • Component Assignments :

      Checks

      • If components are assigned multiple times in a routing

      • If components exist that are not assigned in the routing

      • If redundant assignments exist (nodes and variants of a structure node are assigned to an activity).

    • Activities Without Component Assignment :

      Checks

      • If operations exists whose activities have no components assigned (materials / products).

      • If activities exist that have no components assigned to them.

        These checks are not planning and backflush-relevant.

    • Block Planning Check

      Checks if the activity in iPPE is assigned the same characteristics and characteristic values as the resource in the block basis definition.

    • Model Assignment: APO Resources

      Checks if the planning resource is assigned to the same model(s) as the production version.

      Line Structure:

    • Multiple Usage of Line Objects

      Checks if line objects are used multiple times in a line structure.

    • Missing Sequence Relationships

      Checks if all line objects are linked to one another through sequence relationships.

    • Objects Without Supply Area Assignment

      Checks if there are line objects without supply areas.

    • Production Rate of Line Resource

      Checks if the base production rate has been maintained for the line resource.

    • Multiple MRP Areas Within Grp of Alt. Lines

      The lines in a group of alternative lines can only be assigned to one MRP area. No different MRP areas or a combination of MRP area and plant are allowed. Checks if this is the case in the line structure.

    • Reporting Point Assignment

      Checks

      • If there is a reporting point at the end of a complete line that backflushes components and production activities.

      • If there is a reporting point before splitting to parallel structures that backflushes components and production activities.

      • If there is a reporting point at the end of alternative line structures that backflushes components and production activities.

      • If there are reporting points at the same logical position (for example, a reporting point at the last line in a series of lines in a line network, and a reporting point at the end of the line network itself).

    • General Structure Check:

      Checks for all line structures

      • If multiple work centers are assigned over several levels below an alternative line segment.

        Checks for line structures to part of line networks

      • If there is a continuous path in the line structure with the assignments of lines and buffers to a part of line network.

    • Model Assignment:APO Resources

      Checks if the line resource is assigned to the same model(s) as the production version.

      The resource must always be assigned to all models that are also assigned to the production version.

      Line Balance:

    • Valid Line Balances Missing :

      Evaluates the Do Not Include Line Balances indicator at a line network. Checks if there are valid line balances at the objects for which the indicator has been set.

    • Unassigned Activities

      Checks if all activities in the routing of the line structure specified in the production version are assigned.

    • Line Bal. Relatshps Outside Line Str.

      Checks if there are relationships to line objects in an exploded line balance that do not belong to the line structure that is valid for the line balance.

    • Invalid Multiple Assignments

      Checks if activities of the line structure are assigned multiple times. This check does not refer to alternative lines and alternative work centers.

    • Consistency of Alternative Lines

      Checks if the activities assigned to an alternative line are also assigned to all other lines in the group of alternative lines.The same mode does not have to be assigned.

    • Consistency of Multiple Work Centers

      Checks if the activities at a work center in a group of alternative work centers are also assigned to all other work centers in this group.The same mode has to be assigned.

Actions

  1. In the navigation area of the iPPE Workbench, choose the Reports tab page.

  2. Choose the report iPPE Consistency Check by double-clicking on it.

    The iPPE Consistency Check screen appears.

  3. Choose Create New Consistency Log .

    Specify which production versions you want to check using the Choose Production Version group box.

  4. Enter the required data and choose Execute .

    The production versions found are shown in the Scope of Check group box.

  5. Specify the checks you want to execute on the Restrict Check Functions tab pages.

  6. Choose Continue to start the check.

    The iPPE Consistency Check – Log Output screen appears. In the left part of the screen, you can see all the production versions that were checked.

  7. Choose the incorrect production versions by double-clicking on them and correct all errors before continuing to work with the data.

Or:

If you want to check mass data, you can start this as a separate job with selection variants.

  1. Choose Start of the navigation path System Next navigation step Services Next navigation step Reporting End of the navigation path .

    The ABAP: Execute Program screen appears.

  2. Enter PPE_CONSISTENCY_CHECK or PPEDI_CONSISTENCY_CHECK in the Program field and choose Execute .

    The Program PPEXXX_CONSISTENCY_CHECK screen appears.

    You can specify which production versions the report checks by entering the relevant data in the Choose Production Version group box.

    You can control which checks are executed by entering the relevant data in the Select Checks group box.

  3. Enter the required data and choose Execute .

    The consistency check is executed and the results are saved in the system.