Kontakt

Ansicht
Dokumentation

R_EHPRC_COD_ADJUST_ASSEMBLYIND - Program R_EHPRC_COD_ADJUST_ASSEMBLYIND

R_EHPRC_COD_ADJUST_ASSEMBLYIND - Program R_EHPRC_COD_ADJUST_ASSEMBLYIND

General Material Data   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

Use this report to verify that the assembly indicator for all compliance data objects has the correct value.

In addition, use this report as the last step of data migration when you use the reference function for specifications. The report R_EHPRC_SPEC_CDO_MIGRATE adjusts the assembly indicator for only the master specification, but not for the referencing specifications or their CDOs.

Integration

Every compliance object has some indicators that determine whether it is, for example, a product, an assembly, a component, or an external part. One of these indicators is the assembly indicator. It determines if a component is assessed in the component compliance or product compliance area. If it is not set correctly, you may, for example, expect the object in the component compliance area but find it in product compliance area, or the other way around.

A component is an assembly when the related specification has an input composition. If an input composition exists, the system sets the assembly indicator; otherwise the system resets the indicator.

Features

In rare cases, the assembly indicator is not set correctly. The report verifies the assembly indicator and the input composition within the entire database and corrects the assembly indicator where needed.

You can either process this report manually or set up a batch job to process the report at night. To execute the report in the background, use the role SAP_EHSM_PRC_AUTO_CHANGE_PROC, which has the required authorizations.

Selection

If you run the report in interactive mode, you can select the following options:

  • Run in Test Mode: Choose this option to execute the report in test run mode to search for potential errors. The application log shows if everything worked successfully or which problems occurred. In this mode, the system does not write any persistent data. If errors occur, solve them before starting the report again in productive mode.
  • Package Size: This parameter defines how many compliance objects are corrected in one step. Whenever the selected number of compliance objects has been completed, the report saves the data (if not in test mode) and continues with the package until all found objects are processed. In test mode, this parameter is irrelevant.

Application Log

You can view the application log in the transaction SLG1, object EHPRC_CP_CORE, subobject AUTO_CHANGE_PROC.






ABAP Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 2756 Date: 20240601 Time: 134217     sap01-206 ( 64 ms )