The new pushbutton UUID is available on the Identifiers tab page in transaction Substance Workbench (CG02) for the specification types Contributing Scenario Environment (CS_ENV), Contributing Scenario Worker (CS_WRK), and Contributing Scenario Consumer (CS_CON). The UUID (Universal Unique Identifier), defines a contributing scenario uniquely.

The new pushbuttons UUID and Date Timestamp are available on the Identifiers tab page in transaction Substance Workbench (CG02) for the specification type Exposure Scenario Header Data (ES_HEAD). The UUID (Universal Unique Identifier), together with the date timestamp, defines the version of an exposure scenario so that the exposure scenario can be identified uniquely.

In Report Management, you can generate and manage ESComXML files together with extended safety data sheets. The ESComXML file is generated if the extended safety data sheet can also be generated successfully. (You cannot generate ESComXML files for existing extended safety data sheets.)

In transaction Edit Reports (CG50), new icons are available in the report tree to indicate the generation status of the ESComXML file. The XML page icon indicates that the ESComXML-Datei was generated by the system. The lightning flash icon indicates that report generation failed. The empty page icon indicates that you can request the report or start report generation.

The system determines the ESCom phrases while the ESComXML file is being generated. The ESCom phrase key is an 11-digit number, for example, 11133170850. The phrase key in phrase management is made up of a prefix together with the ESCom phrase key, for example, ZESX11133170850. Using the 4-character prefix in the phrase key, for example, "ZESX", the system can recognize whether the phrase is an ESCom phrase. You define the prefix in the new Customizing activity Specify Settings for Generating ESComXML Files. For more information, see Phrases for Exposure Scenarios.

New checks are delivered for generating ESComXML files. In the new Customizing activity Specify Settings for Message Types for Checks, you can define the message type with which messages are written to the generation log. The messages for the checks are displayed in transaction Edit Reports (CG50) in the generation log.

The following new Business Add-In (BAdI) is available: BAdI: Generate and Ship Additional Documents. Using this BAdI, you can create an additional document when generating reports and store it for the generated report. If you have stored your ESComXML-relevant data differently to the structure specified in specification management, you can make the necessary adjustments in "BAdI: Generate and Ship Additional Documents".

In Report Shipping, you can send ESComXML files together with extended safety data sheets to your customers if shipping by communication type Mail via Internet (INT) is possible. The shipping reasons manual shipping (MAN_CALL), automatic shipping from Sales and Distribution (SD_CALL), and subsequent shipping (SUB_CALL) are supported.

When reports are shipped with ESComXML files, a different logic is available for selecting the communication type. An ESComXML file is only shipped if it is possible to ship to the recipient with communication type Mail via Internet (INT). A prerequisite is that an e-mail address is maintained for the recipient. Automatic shipping from Sales and Distribution (SD_CALL) takes place by Mail via Internet (INT) if an e-mail is maintained, regardless of the standard communication type configured in the address data of the customer (business partner, customer, company).

A separate report shipping order is created for ESComXML files and processed in Report Shipping. The additional report shipping order for the ESComXML file is created and the final ESComXML file generated as soon as the report shipping order for the extended safety data sheet has the status Generated.

Each shipping package that contains an ESComXML file contains exactly one extended safety data sheet and the corresponding ESComXML file.

The final ESComXML file is generated during report shipping. The following header data is filled in the ESComXML file: material name, material number, supplier name, e-mail address for supplier information that is relevant to product safety, and DUNS code. Customer-specific and/or material-specific exposure scenarios are filtered so that the ESComXML file contains the same exposure scenarios as the corresponding extended safety data sheet that is being shipped.

Shipping orders with ESComXML files can be monitored in transaction Edit Report Shipping Orders (CVD1). If a final ESComXML file has already been generated for a report shipping order, the XML page icon is displayed in the hit list in the Final Report column. You can use the XML page icon to call the ESComXML file and display it on the PC. If the hit list contains report shipping orders with ESComXML files, the Communication Group column is also displayed with the value ESC so that you can see whether report shipping orders for extended safety data sheets also contain ESComXML files that are being processed in a separate report shipping order.