Ansicht
Dokumentation

EHS_MD_120_40_02 - Set Up Distribution of Specification Data

Addresses (Business Address Services)   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

In this IMG activity, you set up the distribution of data on specifications (see also Information About the Concept in Application Link Enabling (ALE)).

1. Setting the Active Code Page
2. Settings in Customizing for Application Link Enabling (ALE)

You have made the required settings in Customizing for ALE.

1. Settings in the SAP Basic Data and Tools Component

Make sure that you have fulfilled the following prerequisites:

1. Edit the environment variables for serialization

Serialization collects the IDocs and makes sure that they are processed in the correct order. For more information, see the section Serialization for Sending and Receiving Data in the Implementation Guide (IMG) for ALE.

You specify the serialization number for the logical sending system in the IMG activity Specify Environment Parameters in the environment parameter ALE_SERIAL_ID. You specify one unique channel per logical system.

1. Specify specifications to be distributed

If you want to distribute specification data manually, choose the specification directly from the hit list in specification management.

For automatic distribution, the specifications must appear in a set of hits that is assigned to the distribution method. If a set of hits has not been assigned, all of the specifications are distributed, providing that you have not defined filters.

Apart from standard filters (see below), you can use the following customer exits to define other restrictions and filters:

- Specify Additional Table and Parameter Filter (1)

- Specify Additional Table and Parameter Filter (2)

1. Ensure unique identification of specifications

The specification object must have a unique specification key. In the standard system, identification is supported by the specification key.

You can use the customer exit Develop Enhancement for Identification to enhance the identification, for example, to link with one or more identifiers.

1. Check authorizations

For manual distribution and automatic scheduling, you must have read authorization for all the specification data to be distributed.

You also need the appropriate authorizations for inbound processing in the target system.

1. Specify the Distribution Model in Customizing for ALE

In Customizing for ALE, call the IMG activity Maintain Distribution Model and Distribute Views.

For more information, see the documentation for the IMG activity.

To guarantee communication between systems during distribution, you must make the following entries in the IMG activity Maintain Distribution Model and Distribute Views by choosing Add BAPI:

Field	Entry
Sender/client:
Receiver/server:	, for example,
Sales and Distribution system (SD), on which Product Safety and Stewardship
is installed.
Object name/interface:	Substance (substance(specification), BUS1077)
Method:	SavRepMul (save replicated specifications)

Note:

The message type SUBMAS is supported.

You can set the following filters:

• Reducing specifications by determining recipients:

You can reduce the specifications to be distributed by defining the following filters:

- Specification type

- Authorization group

- Substance nature

- Set of hits (external key of group object)

You can enter several values for a filter field. Individual values are linked with OR, whereas the filter groups are linked with AND.

If no filters are entered, all specifications are distributed.

• Reducing specifications using IDENTHEADER filtering

You define the identification category and identification type whose specifications are to be distributed.

• Reducing data using PROPHEADER filtering

You specify the value assignment types for which specification data is to be distributed.

• In Customizing for ALE, you can use the IMG activity Filter IDoc Segments to exclude further tables from distribution, for example:

- Material assignment

- Regulatory list assignment

- Reference specification assignment

- Usage

- Assessment

Then edit the IMG activity Generate Partner Profiles in Customizing for ALE.

1. Make Settings in the Sending and Receiving Systems

The following tables must be identical in the sending and receiving systems:

• Value assignment type TCG01 and description TCG02 (system tables)

• Table of names for the DDIC objects TCG03 (system table)

• Table of names for the child DDIC objects TCG04 (system table)

• Specify Value Assignment Types

Value assignment type TCG11 and description TCG12

Value assignment type-specification type assignment TCG13

• Identification category TCG21 and description TCG22 (system tables)

• Check Identification Types

Identification type TCG23 and description TCG24

• Check Identification Listing

Identification listings TCG26 and description TCG27

Definition of identification listings TCG28

• Assign Characteristic-Specific Identification

Overriding identification list definitions TCG29

• Specify Specification Types

Specification type TCG31 and description TCG32

• Specify Authorization Groups

Authorization object TCG36 and description TCG37

• Specify User-Defined Text Types

User-defined text type TCG41 and description TCG42

• Specify Sources

Source TCG46

• Specify Source Types

Source type TCG47 and description TCG48

• Set Up Property Trees

Property tree TCG51 and description TCG52

Property tree-value assignment type assignment TCG53

• Specify Data Origin

Data origin TCG56

• Specify Phrase Libraries and Phrase Groups

Phrase library TCG61 and description TCG62

Phrase group TCG63 and description TCG64

• Specify Language Selection

Phrase language (languages supported in phrase library) TCG65

• Value assignment type class characteristic TCG66

System table, filled using master data matchup

• Check Assessments

Value assignment assessment TCG71 and description TCG72

• Specify Component Types for Compositions

Component type TCG76 and description

• Specify Regulatory Lists

Regulatory list TCG81 and description TCG82

• Specify Ratings

Value assignment rating TCG86 and description TCG87

• Specify Validity Areas

Validity area TCG91 and description TCG92

• Specify Usage Profiles

Usage profile TCG96 and description TCG97

Usage profile-rating-validity area assignment TCG98

• Specify Exchange Profiles

Exchange profile TCGC3 and description TCGC4

• Specify Environment Parameters

General environment parameters TCGENV

• Protect Characteristics Within Namespace

Namespaces for characteristics TCGK1

• Manage User Exits

User exit parameters from user exit management TCGUEEN

User exits from user exit management with function module assignment TCGUEFU

Language-dependent user exit names from user exit management TCGUENA

User exit categories from user exit management TCGUETY

1. Check Master Data to Be Distributed

For the ALE process, the following master data must be distributed to all the relevant systems:

• Phrases

• Phrase sets (for systems, in which data is created)

• Classes and characteristics

• Materials (all material data that is required for material-specification assignment)

• Change numbers

Note:

Classes and characteristics are distributed via export and import. The help texts and phrase sets are also transferred to other systems along with the classes and characteristics.

Classes and characteristics can also be distributed using ALE.

Note:

1. Check Control Data to Be Distributed

See above: Make Settings in the Sending and Receiving Systems

1. Check Consistency

A consistency check can be run for the settings in the distribution model and the partner profiles.

To run the consistency check, call the IMG activity Check Technical Consistency in Customizing for ALE.

The distribution model must have been distributed and the partner profiles must have been entered in all relevant systems.

1. Error Handling

If an error occurs when an IDoc is being processed, the whole IDoc is not updated. You can include a workflow to correct errors. IDocs can be modified manually (you can change the identifier, for example) and subsequently updated.

General Procedure

1. In a customer reference model you define which data is to be distributed to which system. You use sets of hits to define the specifications that are to be distributed and specify filters with regard to specifications or specification data as required.
2. The first time you distribute specifications to the target systems, you do it manually, using the REPLICATE method in accordance with the distribution model. Serialization must be deactivated.
3. You activate serialization and switch on delta distribution as follows:

The following applies when transferring data:

• If a specification is not found in the target system, it is created with the specification key that is transferred.

• If a specification exists in the target system, its data is updated.

• When complete specification data is being sent, the specification is locked and no changes can be made to it. If this lock cannot be set, the specification cannot be edited. The IDoc is given the status With error and a work item is created.

Note:

CPI1466 during Backup   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 16701 Date: 20240523 Time: 163422     sap01-206 ( 127 ms )