SAP ABAP IMG Activity EHS_SD_100_10_033 (Check Determination of MSDS Data)
Hierarchy
EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   EHS (Application Component) Environment, Health and Safety
     CBIMG1 (Package) EH&S: IMG Migration
IMG Activity
ID EHS_SD_100_10_033 Check Determination of MSDS Data  
Transaction Code S_SH8_72001002   IMG Activity: EHS_SD_100_10_033 
Created on 19990122    
Customizing Attributes EHS_SD_100_10_033   Check determination of MSDS data 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name EHS_SD_100_10_033    

This chapter describes how the SAP System determines the information relevant for MSDS shipping.

MSDS shipping is triggered when a delivery containing an environmentally relevant material is posted. You must maintain delivery type, sales organization, customer, goods issue date, and material for each delivery.

The system then selects data relevant to MSDS shipping as follows:

  1. Determination of output type SDB

For every delivery document item, the system determines the item category and uses this to determine the output determination procedure. The output determination procedure must contain the condition type SDB so that the SAP System can assign the output type SDB for that item.

See: Check External Prerequisites, section 2c.

  1. Determination of the customer whose partner function is entered in the condition record for output type SDB.

To determine the recipient of the output, the SAP System selects the partner function from the condition record for output type SDB in the output determination procedure.

To do this, several requirements must be fulfilled:

  1. For output type SDB, the access sequence and default for the condition record must be maintained in Customizing.
  2. See: Check Output Types.
  3. The condition records for output type SDB must be maintained in the SD master data.
  4. When a delivery has been created, the SAP System checks the condition records according to the access sequence.
    In the standard system, the output recipient is the ship-to party (partner function WE).

Note:

From the delivery note via Item -> Output, you can check if the SAP System was able to assign the output type SDB and the corresponding condition record entries (in the standard, partner function WE, transmission medium 8, send time 1).

If entries are missing, check which outputs were not found by the SAP System via Goto -> Determin. analysis.

  1. Determination of MSDS recipient

The customer master record for the output recipient (partner function WE) must be maintained. All partners with partner functions SR for this customer are read from the customer master. They are regarded as recipients of material safety data sheets (MSDS recipients). There must be at least one MSDS recipient.

As standard, the ship-to party is entered as both ship-to party and MSDS recipient.

See: Set Up Partner Determination

The MSDS recipient can be changed manually or others added to the list. The address data is read for every MSDS recipient. It must be maintained. If contact persons are maintained for an MSDS recipient, they are read.

See: Check External Prerequisites, section 3 (Note on creating a ship-to party (customer))

  1. Determination of validity area

The validity area is determined by the report generation variant. This is selected via the condition tables in the Product Safety component.

For more information, see the Implementation Guide for Product Safety under Condition Schemas for RGV Selection

  1. Determination of key date

All delivery-relevant data is read by the SAP System in order to determine the key date.

For more information, see the Implementation Guide for Product Safety under Specify Key Date for Shipping

  1. Determination of MSDS sender data

The sales organization that generates the delivery appears as the material safety data sheet sender. It must be maintained.

See: Check External Prerequisites, section 1 (Notes for sales organization (MSDS sender))

  1. Determination of delivery document and material master data

Delivery type, document number, and item number are read from the delivery document. The SAP System reads the material key and the article short text. (The SAP System takes the article short text from the material master. You can still change the text in the delivery document.) This data must be maintained.

See: Check External Prerequisites, section 2 (Notes for creating environmentally relevant materials)

  1. To check this from the initial SAP menu, choose Logistics -> Sales and distribution -> Shipping -> Outbound delivery -> Change.
  2. Enter the delivery key and choose ENTER.
  3. Select the desired delivery item and choose Item -> Item details.
  4. You can change the material key and the article short text.

Note: Both fields belong to the LIPS table. (Table names are a standard part of symbol names that must be generated for creating document templates for table fields.)

Further notes

You can use the IMG activity Develop Enhancement for Sorting Parameters for filtering parameters.

For more information, see the documentation for the Product Safety component in the Report Shipping section.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 1   Mandatory activity 
Critical / Non-Critical 1   Critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG EHS_SD_100_10_033 0 ALR0000063 Report Shipping 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  20010320 
SAP Release Created in 46C