Ansicht
Dokumentation
R_EHPRC_REMIGRATE_BOM - Program R_EHPRC_REMIGRATE_BOM
CL_GUI_FRONTEND_SERVICES - Frontend Services PERFORM Short ReferenceThis documentation is copyright by SAP AG.
Purpose
You can use this report to migrate the node BOMfor the business object EHPRC_COMPLIANCE_DATA (abbreviated with CDO) after you have done the data migration from SAP Product and REACH Compliance 2.0or Compliance for Products 2.2to component extension 4.0 or 5.0 for SAP EHS Management. .
You need the report only if you have done the data migration in one of the following versions without having SAP Note 2080359 installed.
- EHS Management 4.0 without any SP or with SP01..03
- EHS Management 5.0 without SP or with SP01
Integration
Prerequisites
- You used SAP Product and REACH Compliance 2.0 or Compliance for Products 2.2 and you are upgrading to component extension 3.0 for SAP EHS Management or higher as mentiioned before.
- You executed the following report before:
- R_EHPRC_SPEC_CDO_MIGRATE
Features
This report completes the data migration regarding the BOM transfer information. It serves for two purposes:
- If no BOM transfer information exists for a specification at all it adds this information to the CDO.
- If the BOM transfer date is empty it sets this date to the creation date of the specification.
Selection
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.
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 fine, or which problems occurred. In this mode the system does not write any persistent data. Solve the issues 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 before, and correct all issues that appear.
Update Empty Transfer Dates: If you choose this option, the report searches for BOM transfer information with empty transfer dates and adjusts it to the creation date of the specification.
Package Size: This parameter defines how many specifications are migrated in one step. Whenever the selected number of specifications have been migrated, the report saves data (if not in test mode) and continues with the next specifications until the whole number of specification that is defined in the parameter Specification have been migrated. The parameter can have a significant impact on performance, do not change the default value without reason.
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
- 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. On the initial screen, enter the just copied value of SE37 inparameter I_LOGNUMBER.
Fill RESBD Structure from EBP Component Structure BAL_S_LOG - Application Log: Log header data
This documentation is copyright by SAP AG.
Length: 4332 Date: 20240601 Time: 134610 sap01-206 ( 96 ms )
