on 01-16-2008 7:13 AM
Dear Experts,
I am from the XI background and am new to EH&S. I would like to know whether there exists an extraction program to extract substance data from EH&S(ECC) and send it to XI. If yes then what is it? The EH&S team here doesn't know of any kind. They have only used Change pointers to extract data from one client to the another.
Please help.
Thanks,
Merrilly
Hi,
Please let me know how to get a hazardous material text given a hazardous material.
Please let me know ASAP.
Thanks in advance,
Sowjanya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
EH&S supports ALE to distribute substance data from one system to another.
You can set up ALE to send IDOCs to XI.
Greets
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I'm trying to take data from EH&S and give it to MDM, which accepts data only in xml or csv format. So here we might have to use XI.
The problem i'm facing is not at the XI level but at the R/3 side itself. Unless and untill i know how to extract data from R/3, i won't be able to send it to XI.
thanks and regards,
Merrilly
Hello,
How to set up ALE for substances is described in the IMG / Customizing for EH&S.
For EH&S 2.7B on R/3 4.6C this is located under:
Environment, Health & Safety -> Product Safety -> Interfaces -> EH&S Application Link Enabling (ALE) -> ALE for Specification Management.
All necessary information should be found in 'Set up Distribution of Specification Data':
Set Up Distribution of Specification Data
In this IMG activity you set up the distribution of data on
specifications (see also Information About the Concept in EH&S
Application Link Enabling (ALE)).
Requirements
1. Setting the Active Code Page
To transfer the data using ALE, you must ensure that the active code
pages are the same in the receiving system and sending system as
follows:
- You must select a code page for transfer (for example, SAP(ISO)
code page 1100) that you set up on all SAP Systems that belong
to your ALE distribution model.
- In Customizing for Product Safety in the IMG activity Specify
Environment Parameters using the environment parameter
ALE_TRANSFER_LANGUAGE, you must specify a language of the
previously selected code page as the transfer language in the
sending system. This language controls which code page is active
in the sending system during data transfer.
- The RFC destinations of the target systems must be defined with
the logon language that corresponds to the specified code page.
- If data is to be transferred to different SAP(ISO) code pages,
the operating systems of the sending and receiving systems must
use the same character sets (ASCII or EBCDIC):
Sending system Receiving system Transfer possible
AS400 AS400 Yes
UNIX UNIX Yes
NT NT Yes
NT UNIX Yes
UNIX NT Yes
AS400 NT No
AS400 UNIX No
NT AS400 No
UNIX AS400 No
For more information, see:
- The IMG activity Specify Environment Parameters
- The IMG activity Set Up EH&S Native Language Support
- The Product Safety documentation in the section EH&S Native
Language Support
2. Settings in Customizing for Distribution (ALE)
You have made the necessary settings in Customizing for Distribution
(ALE).
Also maintain, for example, the sections
- Basic Settings
- Communication
3. Settings in the Product Safety Component
Make sure that you have fulfilled the following prerequisites:
a) Maintain the environment variables for serialization
Serialization collects the IDocs and makes sure that they are
processed in the correct order. For more information, see
section Serialized Distribution in Customizing for Distribution
(ALE).
You specify the serialization number for the sending logical
system in the IMG activity Specify Environment Parameters using
the environment parameter ALE_SERIAL_ID. You specify one unique
channel per logical system.
b) 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 further restrictions and
filters:
- Specify Additional Table and Parameter Filter (1)
- Specify Additional Table and Parameter Filter (2)
c) 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.
d) Check authorizations
For manual distribution and automatic scheduling, you must have
the read authorization for all the specification data to be
distributed.
You also need the appropriate authorizations for inbound
processing in the target system.
Activities
1. Maintain the Distribution Model in Distribution (ALE) Customizing
In Customizing for Distribution, call the IMG activity Maintain
Distribution Model.
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 by choosing Add method:
Field Entry
Sender/client: <Key for EH&S system>
Receiver/server: <Key for target system>, for example,
Sales and Distribution system (SD), on which EH&S
is installed.
Object name/interface: Substance (substance(specification),
BUS1077)
Method: SavRepMul (save replicated specifications)
Note:
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 Distribution (ALE) Customizing, you can use the IMG activity
Set Up Segment Filtering to exclude further tables from
distribution, for example:
- Material assignment
- Regulatory list assignment
- Reference specification assignment
- Usage
- Assessment
Then in Distribution (ALE) Customizing, you maintain the IMG
activity Generate Partner Profiles.
2. Maintain Settings in the Sending and Recipient Systems
The following tables must be maintained in the same way in the
sending and recipient 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 Types for User-Defined Texts
Value assignment text type TCG41 and description TCG42
- Create 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 Value Assignments
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
3. 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:
The required data providers must have been created manually in the
Product Safety component under Tools -> Edit addresses -> Data
provider before data is distributed in the recipient system. The
data providers must be unique with regard to the following three
fields:
- Name (NAME1)
- City (CITY1)
- Country (COUNTRY)
During distribution, the data providers of the specification to be
sent are read and also distributed. When writing to the recipient
system, the SAP System determines the corresponding address number
for the data provider in the recipient system by comparing the three
fields Name, City and Country for the address numbers that were
sent, and then transfers this address number that was determined to
the Data provider field (OWNID).
You can determine the address number of the data provider in
Customizing for Product Safety in the IMG activity Specify
Authorization Groups.
To do this, call the input help for the Data prov. field in the IMG
activity. You will find the value you require in the Addr. no.
field.
The address number is not displayed in address management in the
Product Safety component.
4. Check Control Data to Be Distributed
See above: "Maintain Settings in the Sending and Recipient Systems"
5. Check Consistency
A consistency check can be performed for the settings in the
distribution model and the partner profiles.
To do this, in Distribution (ALE) Customizing, call the IMG activity
Check Partner Profiles and Model Settings.
The distribution model must have been distributed and the partner
profiles must have been maintained in all relevant systems.
6. Error Handling
As soon as an error occurs when an IDoc is processed, the whole IDoc
is not updated. You can use a workflow to correct errors. IDocs can
be modified manually (you can change the identifier, for example)
and updated retrospectively.
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 method REPLICATE according to the
distribution model. Serialization must be switched off.
3. You activate serialization and switch on delta distribution as
follows:
Activating Serialization
a) In Customizing for Product Safety, in the IMG activity Specify
Environment Parameters specify the channel for the parameter
ALE_SERIAL_ID through which the ALE data is to be distributed.
b) In Customizing for Distribution (ALE) choose Set Up Data
Distribution -> Serialized Distribution -> Serialized
Distribution Using Object Types -> Activate Inbound Object Types
and specify the inbound object types for which serialization is
to be performed.
c) Schedule a job (RBDAPP01) that posts the IDocs that arrive in
series in the recipient system.
Switching On Delta Distribution
a) Activating change pointers for a message type
Changes to master data objects are logged in the form of change
pointers during master data distribution. To activate the
writing of change pointers, in Customizing for Distribution
(ALE) choose Set Up Data Distribution -> Master Data
Distribution -> Activating Change Pointers -> Activate Change
Pointers for Message Types and set the Active indicator for the
message type for which you want to realize delta distribution.
b) Activating change pointers for each field
From the SAP R/3 screen, choose Tools -> Business Framework ->
ALE -> Development -> Master data -> Activate change pointer for
each field and enter the message type for which you want to
determine fields, for which the SAP System writes change
pointers. All relevant data fields are delivered. If necessary,
adjust the table to your requirements.
c) Activating change pointers generally
To generally activate master data distribution using change
pointers, in Customizing for Distribution (ALE), choose Set Up
Data Distribution -> Master Data Distribution -> Activating
Change Pointers -> Activate Change Pointers (generally) and set
the active indicator.
d) Scheduling delta distribution as a job
You can perform delta distribution manually or schedule it as a
job.
To perform delta distribution manually, from the SAP R/3 screen
choose Tools -> Business Framework -> ALE -> Administration ->
Periodic processing -> Process change pointers and enter the
message type you require and choose Execute.
To schedule delta distribution as a job, in Customizing for
Distribution (ALE) choose Scheduling Periodic Processing ->
Scheduling Generation of IDocs from Change Pointers -> Define
Variants and create a variant. Then in the IMG activity Schedule
Jobs create a job (RBDMIDOC) for the variant. You can set the
time at which distribution is performed, for example,
immediately after a change or periodically.
The following applies when transferring data:
o If a specification is not found in the target system, it is created
with the specification key that is transferred.
o If a specification is available in the target system, its data is
updated.
o 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 processed. The IDoc is given the status
with error and a work item is created.
Note:
In manual distribution, change pointers are not taken into account.
In other words, the entire data record is distributed and delta
distribution is not performed.
Note on Executing the Report Program RC1PHDEL:
You must NOT schedule the report program RC1PHDEL (physical deletion
of data) to run in the source system or manually run it between
initial distribution and delta distribution, because the keys of
logically deleted data records can no longer be read and distributed
by delta distribution after the report program has been executed.
Before initial distribution you can execute the report in the source
system.
In the target system you can execute the report program independent
of distribution, as long as the target system does not serve as the
source system for further distribution.
If you want to execute the report program after the first delta
distribution, you must first make sure that all change pointers
created have been fully processed by the delta distribution and, if
possible, that all IDocs (intermediate documents) created were also
successfully posted in the target system. Otherwise, there is no
guarantee that the source and target systems will be consistent.
Example
The report program RC1PHDEL was executed in the source system so
that the deletions of an identifier of the identification category
NUM and the identification type CAS and a phrase item were not
distributed.
Then an identifier of the identification category NUM and
identification type CAS with the identical value that was previously
deleted and a phrase item for the same phrase in the previously
deleted language are created. The following errors occur in the
subsequent delta distribution:
- The identifier cannot be created because the NUM-CAS value
already exists. The IDoc cannot therefore be posted.
Notes:
If you attempt to create duplicate identifiers in the dialog,
the same error messages will be displayed as when posting using
ALE.
If the NUM-CAS identifier was not identical to the previously
deleted identifier, the IDoc would be posted successfully and
the identifier would be created in addition.
- The phrase item cannot be created, because only one phrase item
is permitted for a phrase in each language. The old phrase item
must be deleted first before the IDoc can be posted.
The next section describes the solution for similar error cases. You
should, however, try to avoid the need for this procedure by not
executing the report program.
e) In the target system in the dialog, delete the EH&S objects
(specifications, phrases, reports), for which you have already
run delta distribution. These objects are internally marked with
a deletion indicator.
Caution:
When you distribute reports, the report bodies are distributed.
To delete these, you simply need to delete all report reference
specifications. Deleting report bodies is not necessary and also
not possible. If you cannot delete objects (such as
specifications or phrases) owing to their where-used-list, it is
sufficient to delete the 'deleted' detail data in the target
system that has not been distributed. This may require more
processing effort than if you delete all the objects using the
hit list and distribute all the data again in full.
f) In the target system, set the Set missing deletion indicators
and Delete physically indicators in the RC1PHDEL report program
and execute the report program in the target system.
This triggers the following actions:
- The deletion indicator is set in the tables that depend on the
header data to be deleted.
- All data with deletion indicators is deleted physically.
- The corresponding entries in the table ESTALE (conversion
table for ALE) are deleted physically.
g) Deactivate the active serialization and the writing of change
pointers and start initial distribution of all objects again.
h) You can now activate the writing of change pointers and
serialization again and use delta distribution as usual.
Note:
If you still have IDocs in the source system or target system that
were created before the deletion in your target system, but were not
distributed or posted, ignore these IDocs and do not post them. You
can do this by changing the channel before repeating the initial
distribution by using the environment parameter ALE_SERIAL_ID (for
more information on the environment parameter, see the IMG activity
Set Up Distribution of Specification Data).
Return ->
Application
Hope this helps
Mark
If you are looking for the jobs to do the IDOC processing - take a look at these standard (meaning not EH&S specific) programs:
RBDIDOCA - Program for object type IDOC: EDI intermediate document
RBDIDOCCHAN - Serialization Using Object Types: Display Serialized IDocs
RBDIDOCPROCESS - Manual Processing of IDocs
RBDIDOCR - IDoc Reduction
RBDMIDOC - Creating IDoc Type from Change Pointers
RBDMONI_CCMS_IDOC - ALE CCMS Monitoring: Data Supplier for IDoc Groups
Useful TRs
WE05 : IDOC Display
WE09 : Find IDOc by segment data
WE19 : Test / Reporocess IDOCs
WE20 : IDOC Partner Profiles
WE51 : System
WE53 : Sucesfully Processed
WE57 : Assigne IDCO Type Message
Programs to 'kick' idocs:
RBDAPP01 for status 64
RBDCHSTA for status 62.
BD87 : Reporcess error idocs
Hope this helps
Mark
This issue is regrding the distribution model. We want to transfer the EHS data from 4.6 to ECC 6.0. Below is the requirement:
1. There are few classes which needs to be distributed and not all classes and its charecterstics in the property tree.
2. I have created a distribution model for it and entered the classes which are relevant for e.g. Flash point is the class (SAP_EHS_1014_009) which is there in the dist model. So when I change any charecterstics value in this class and Run BD21 then I can see the Class in the list under the segment E1BP1077VH and the changed charecteristics is under the segment E1BP1077PR. Which seems to be correct- But when I change another charecterstics of another class (SAP_EHS_1013_013) which is not there in the dist model. Then BD21 and still I can see the new Charecte. in the WE02 though the class is not in the distribution model. Meaning its not filtering out the irrelavant charecterstics in the property tree. Thats the reason all property data is getting transfred.
Is there is any customizing setting? I think as a Standard process it must filter out the changes of the classes which are not there in the distribution model. DO you have any hint on this?
Hi,
Designated Substance Compliance Program
Program:
Designated Substances are those substances designated as hazardous by the Ministry of Labour under the Occupational Health and Safety Act, Section 70 (2) 23.
The Act defines a designated substance as:
a biological, chemical or physical agent or combination thereof prescribed as a designated substance to which the exposure of a worker is prohibited, regulated, restricted, limited or controlled.
A regulation specifies procedures for control of the substance. The following substances have been designated:
Acrylonitrile (1984)
Arsenic (1986)
Asbestos (1982)
Asbestos - Construction, Building & Repair (1985)
Benzene (1984)
Coke Oven Emissions (1982)
Ethylene Oxide (1987)
Isocyanates (1983)
Lead (1981)
Mercury (1982)
Silica (1983)
Vinyl Chloride (1982)
When a designated substance is present in the workplace, the Occupational Health and Safety Act requires the employer to review the work methods and assess the likelihood of worker exposure. When there is likelihood of worker exposure, a control program must be instituted that includes engineering controls, work practices, hygiene practices, record keeping and medical surveillance, if applicable.
The Joint Health and Safety Committee (JHSC) must be consulted with regard to both the assessment and the control program.
Environmental Health and Safety (EHS) in the Department of University Safety coordinates the Designated Substances Compliance Program.
Implementation:
When a designated substance is present in the workplace, the supervisor must complete an assessment of the use of the substance. This assessment is to determine if a health hazard exists for workers and whether or not a control program is required. The assessment will include the following:
information regarding the use, handling, storage and disposal of the designated substance,
actual and potential exposure of workers to the substance, and
methods and procedures required to control that exposure.
Assessment forms and copies of the Regulations for each substance are available from EHS.
The completed document will be sent to EHS for consultation with the JHSC.
In some cases, further evaluation of the assessment and establishment of a control program may be required. The supervisor and department head will develop the control program. The control program includes action taken to protect workers from exposure to the designated substance and procedures to monitor exposure. Documentation of the control program will be provided to EHS.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
9 | |
7 | |
3 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.