Kontakt

Ansicht
Dokumentation

R_EHPRC_TASK_TO_WF_MIGRATION - Task to Workflow Migration to SAP EHS Management

R_EHPRC_TASK_TO_WF_MIGRATION - Task to Workflow Migration to SAP EHS Management

Addresses (Business Address Services)   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report migrates open tasks from SAP Product and REACH Compliance 2.0 to component extension 3.0 for SAP EHS Management.

Run this report to check the status of the data migration, and run it again once you have eliminated any occurred errors until no longer errors can be detected.

You have the option to run the report either in interactive mode or as a background job. SAP recommends executing this report as a background job because in the interactive mode an application timeout could occur due to the duration.

You can avoid application timeouts in interactive mode by using smaller packages of tasks. Build packages with ranges of task numbers and/or workflow categories such as Compliance Check Conflicts, Business Partner Communications, or additional categories.

Integration

Prerequisites

  • You use SAP Product and REACH Compliance 2.0and you are upgrading to component extension 3.0 for SAP EHS Management.
  • You execute the following reports before:
  • R_EHPRC_DATA_MIGRATE (Namespace Migration)

  • R_EHPRC_COMP_PROP_MIGRATE (Migrate Compositions, Properties and Characteristics from CfP 2.2)

  • R_EHPRC_MIGRATE_CHECK (Check Master Data for Migration)

  • R_EHPRC_MATERIALS_MIGRATE (Migrate Basic Materials)

  • R_EHPRC_SUPPLIER_PART_MIGRATE (Migrate Supplier Parts)

  • R_EHPRC_SPEC_PROD_COMP_MIGRATE (Migrate Products and Components)

  • R_EHPRC_START_COMPL_CHECK (Start Compliance Check After Migration)

  • Force Task Migration
If you have already migrated your tasks; see Activities for more information about forcing the task migration to migrate a task again.
  • No Parallel Reports
You cannot run more than one report in parallel neither in interactive mode nor as background job. If you start a report a second time, before the first one was finished, the second report outputs an error and aborts. Take care about this when scheduling jobs for different clients.

Features

The migration table EHPRCD_TASK_MIGcontrols the task migration process. This table determines that a task is already migrated. When the system receives response documents from the business partners with old task identification, then the migration table is used to find out the new workflow process, which can now handle these documents.

The following categories of workflows/tasks are supported:

  • Business Partner Communication Process (Supply Chain Collaboration)
Each open task which represents a business partner communication will be migrated into this type of workflow. In this category there is a 1:1 migration between the tasks and workflow processes. However, a process can only be created if a communication process is not running with the same business partner, material/substance and compliance check. Otherwise, a log entry will be created.
  • The migration report supports the task status Created(CREAT) and In work (INWRK) and starts the business partner process until it reaches the status to define and send the e-mail manually.

  • The migration report supports the task status In Work Externally (INWEX) and starts the business partner process until it reaches the status to wait for a reply from the business partner.

  • The migration report supports the task status Completed (COMPL) and starts the business partner process until it reaches the status to verify and load the response from the business partner.

  • For all other task statuses, the migration report starts the business partner process until it reaches the status to wait for a reply from the business partner.

Note: If the report finds a running communication process, you have to wait until this process is finished before you can migrate the task.
  • Assign E-Mail Process
Each open task which was created for the task category E-Mails (EML) will be migrated into this type of workflow. In this category there is a 1:1 migration between the tasks and workflow processes.
  • BOM-BOS Process
Each open task which represents a BOM-BOS transfer (messages /TDAG/CPM_BOMBOS030 and 021) or Single Material Transfer (messages /TDAG/CPM_BOMBOS 067) will be migrated into a new BOM-BOS process.

Note:If a task does not belong to one of the categories above, it will be ignored. This may occur if you have defined your own tasks.

Selection

You can select to run the report either in interactive mode or as batch job without or with a variant. The following selection options are available:

  • Workflow Category or Instance ID: Restrict the size of the data migration by specifying either workflow categories or task numbers or both, which means an AND selection starts. In all cases you can choose one value or a value range
Be aware of the following details:
  • If you want to execute the task migration in interactive mode, split the tasks into packages to avoid application timeouts.

  • For example, you can run the task migration for packages of 50 tasks. Therefore, you can run the first data migration for task numbers 1 to 50, the second from task numbers 51 to 100, and so on.

  • When restricting the size of the task migration, the report checks and migrates only the specified number of tasks.

  • RFC Destination old Processes:Provide an RFC destination to specify from which system the report should read source data; leave it empty if source data is located on the local system.
Use transaction SM59 to define an RFC destination. In general you should use connection type 3 ABAP Connection and provide a logon procedure to be able to use an RFC destination for this migration report.
  • Run in Test Mode: Choose this option to execute the report in a test run mode searching for potential errors. The application log shows if everything worked fine or which problems occurred, but no data is persisted at all. You can solve the issues before starting the report again in the normal mode.

Standard Variants

Background Job

If the report is run as a background job and you do not provide a report variant, the following default conditions apply:

  • The task migration size is not restricted, all tasks will be migrated
  • The source data is read from the local system
  • Tasks will be migrated and workflow processes will be created (real conversion)

You can provide a report variant to change any of these parameters, for example, you can provide an RFC destination from which source data is read, or you can perform a migration check only.

Output

Application Log

The application log (transaction SLG1, object EHPRC_MIGRATE, subobject R_EHPRC_TASK_MIGRATE) contains the following details:

  • If the report ran in test mode or not.
  • About the client where the report ran.
  • About the RFC destination that was provided to read source data from.

You can read additional details in the following cases:

  • The report run as a background job.
  • The report run in interactive mode to check the task migration, and to check that valid selection criteria are entered.
  • The report run in interactive mode to perform the task migration, and to check that valid selection criteria are entered.

If the report run in interactive mode, the application log is written and in addition the content is displayed on the screen.

Job Log

If the report runs as a batch job the system writes the status Execution Complete into the job log, including a reference about how to access the application log for more information.

Activities

Jobs for Each Client

Data migration is client-specific. So, if you execute this report for client 001, data is migrated for client 001 only. Execute this report for each client that you want to move data for.

Scheduling Batch Jobs

You cannot run the report more than once simultaneously. If you run the report a second time, the report outputs an error and aborts. If you run data migration using batch jobs for different clients make sure that the batch jobs do not overlap (one batch job must be finished before the next one is started).

Remote System

  • If source data (tasks and documents) is located in a remote system, the report can migrate the tasks only if the materials, substances, customers, suppliers, system users, and DMS documents of the tasks are available in the system where you execute the task migration.
  • If your source data is located on a remote system and you use a batch job to migrate data, define a report variant specifying the RFC destination that you want to read source data from. Use this variant for the batch job.
  • It is important to have the same system users in the current and the remote system. For example, in business partner communication, the responsible user is used in the process as the creator/sender of the request. If the system user is not available on the local client, then the log includes a warning and the current user is used as the responsible user.

Reply E-mail

When migrated tasks from a remote system, ensure that the reply e-mail, used in the existing attachments, will forward the E-mails to the new SAP EHS Management system.

Errors in Application Log

If the report outputs errors, correct the error cause, then decide if you want to re-execute the migration process to ensure that it is completed properly.

Force Data Migration

You can force to migrate a task again by deleting in transaction SE16N, in table EHPRCD_TASK_MIG the record for the task.; then execute or re-execute this report. If the task represents a business partner communication, you have to check that the old communication process was canceled or completed before you start the migration again.

Own Defined Checks or Tasks

If you have defined your own compliance requirement checks or other tasks, the report does not know how to handle these tasks, and will ignore them. To resolve this you can copy the report to a local object and update the report according to your requirements.

Example






Addresses (Business Address Services)   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 12809 Date: 20240520 Time: 141700     sap01-206 ( 144 ms )