Kontakt

Ansicht
Dokumentation

R_EHPRC_SPEC_CDO_MIGRATE - Migrate Specifications to Compliance Data Objects

R_EHPRC_SPEC_CDO_MIGRATE - Migrate Specifications to Compliance Data Objects

ABAP Short Reference   Vendor Master (General Section)  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report migrates specifications from SAP Product and REACH Compliance 2.0 or Compliance for Products 2.2 only to component extension 3.0 or higher for SAP EHS Management.

You can run this report in interactive mode or as a background job. If you want to migrate a large number of specifications, we recommend that you run this report as a background job since it may take some time. In interactive mode, an application timeout could occur.

Perform the four logical steps of the migration in the correct order:

  1. Basic data
  2. Compositions
  3. Declaration data
  4. Deactivate Compositions

Note:

  • Be aware that after migration, all existing reference or inheritance relationships in the source system are no longer available in the target system. The migration report only copies the values.
  • Deactivate Compositions deactivates the input composition of the specifications and adapts the assembly indicator of the corresponding CDO. If you use specification referencing, the report deactivates the input composition of only the master specification and adapts its assembly indicator. It does not search for all the referencing specifications to adapt their assembly indicator additionally. To verify that all assembly indicators of all CDOs in the database are correct and to adjust them, use the report R_EHPRC_COD_ADJUST_ASSEMBLYIND after completing the data migration.

Integration

Prerequisites

  • You have used SAP Product and REACH Compliance 2.0 or Compliance for Compliance 2.0 or Compliance for Products 2.2 to component extension 3.0or higher for SAP EHS Management only.
  • You have executed the following reports in advance:
  • R_EHPRC_DATA_MIGRATE (Namespace Migration)

  • R_EHPRC_COMP_PROP_MIGRATE (Migrate Compositions, Properties, and Characteristics from Compliance for Products 2.2)

  • R_EHPRC_MIGRATE_CHECK (Check Master Data for Migration).

  • If you have exemptions with different IDs in the source and target system, you need a mapping of exemptions for the migration. Use the edit view of the table EHPRCC_EXM_MAP to map the exemptions, and ensure that you map only the exemption ID and not the legal identifier or annex.

Features

  • Touched data
Component extension 3.0 or higher for SAP EHS Management use a compliance data object (CDO) as the main business object. The report creates a CDO for each specification that has a certain category (see Customizing activity Assign Material Category to Compliance Data) and copies the following data from the specification database to the CDO:
  • Substance ID

  • Product name

  • Supplier ID in case of supplier specifications

  • Mass information

  • CDO category

  • Material assignment

  • Basic material composition (not for basic materials)

  • Supplier listing (for purchased parts)

  • Check results are migrated to compliance requirement revisions. The compliance requirement revisions are set to status In Processor Not Relevant depending on their release relevance.

  • Copied Data
The report copies the source data, which also remains in the specification database. Therefore, you can execute the report again. After migration be aware that you should not change or create these kinds of data in the specification workbench,only use SAP EHS Management therefore.
  • Parallelization
You can run multiple instances of the report for one migration step, using distinct sets of specifications.

Selection

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

  • Specifications: You can select one or more specifications, use an asterisk (*). The other option is to leave the parameter empty so that the report migrates all specifications in one step.
  • Migration Step:
  • Step 1: Migrate Basic Data:Migrates the header data with the specification and material link

  • Step 2: Migrate Compositions: Migrates the supplier listing and basic material composition

  • Step 3: Migrate Declarations: Migrates compliance requirements and declarable substances

  • Step 4: Deactivate Compositions:Deactivates basic material compositions that have been copied to the compliance data object

Note:
  • Steps 2, 3 and 4 can be run successfully only after all substances have passed migration step 1. Otherwise the necessary dependencies (composition references or homogeneous materials) may not exist. For a productive migration, we highly recommend that you finish each migration step for all substances before you continue to the next step.

  • Step 4 can be performed only one time in productive mode, because it deactivates the original data. Before executing this step, perform all other migration steps and ensure that the data is migrated correctly.

Allow Mixed Input Compositions (Step 2 only):Choose this option if you have mixed basic materials and surfaces, as well as other material categories, within one input composition. In this case, the migration report creates a basic material composition for the compliance data object, and uses the input composition for further processing.
If you do not choose this option but a specification contains a mixed input composition, an error message appears in the log, and the system continues to the next specification.

  • Run in Test Mode: Choose this option to execute the report in a 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 have occurred, solve them before starting the report again in productive mode.
  • Run in Productive Mode:Choose this option to execute the report productively. All data that is written is persistent to the database. We recommend that you run the report in test mode beforehand, and correct all errors that occur.
  • Delete Existing Objects Before Migration (Step 1-3 only): When you run the report in productive mode, you can delete any data that was created during any previous productive runs. The data is then migrated again. If you do not choose this option, all existing objects are skipped.
Note:
  • If you choose this option for migration step 1, all data for a specification is deleted, including compositions and declaration data. Therefore, you also have to run migration steps 2 and 3 for the substance again.

  • Step 4 does not support this option. It can be run only once in productive mode.

  • Package Size: This parameter defines how many specifications are migrated in one step. Whenever the selected number of specifications has been migrated, the report saves the data (if not in test mode) and continues with the next specifications until the entire number of specifications that is defined in the parameter Specificationhas been migrated. The parameter can have a significant impact on performance; do not change the default value without a reason.

Standard Variants

We recommend using batch jobs with report variants that define the parameters described in the Selection section.

Output

Application Log

After the execution of the report start the application log (transaction SLG1, object EHPRC_MIGRATE, subobject CDO_MIGRATION). Here you find the following details:

  • Which specifications are successfully migrated
  • Which specifications were skipped because they already exist in the system (if you did not choose the option Delete Existing Objects Before Migration)
  • All error messages that are created

If the report runs in interactive mode, the system writes the application log. In addition, after executing the report, the system shows the content of the application log on the screen.

If the report runs in background mode, you can see the specification ID for each message in a separate column by executing the following steps:

  1. Start in transaction SLG1(object EHPRC_MIGRATE, subobject CDO_MIGRATION)
  2. Search for your application log
  3. Copy your Log number
  4. Start transaction SE37
  5. Execute function module EHPRC_CP_LB03_DISPLAY
  6. Enter in the initial screen for the parameter I_LOGNUMBER the value of SE37, which you just copied.

Activities

Example






CL_GUI_FRONTEND_SERVICES - Frontend Services   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 11327 Date: 20240601 Time: 053458     sap01-206 ( 186 ms )