Show TOC

 Report Shipping: Changes for Outbound Processing

Report Shipping (Changed)

These enhancements are part of the release note PS: Management of Exposure Scenarios - Outbound Processing.

As of SAP enhancement package 7 SP 06 for SAP ERP 6.0 (EA-APPL 617), business function EHS - Continuous Improvements for Product Safety (LOG_EHS_PS_CI_5), the following new functions are available in the Report Shipping (EHS-SAF-RSH) component:

New Functions
Shipping of ESComXML Files

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 following shipping reasons are supported for sending ESComXML files together with extended safety data sheets.

  • Manual shipping (MAN_CALL) from the report information system

  • Automatic shipping from Sales and Distribution (SD_CALL) if an order (cause type ORDER) or a delivery (cause type DELIVERY) is created

  • Subsequent shipping (SUB_CALL) if a new main version for a report is generated

Selection of 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).

If you want to prevent the system from doing this when extended safety data sheets with ESComXML files are shipped automatically from Sales and Distribution (SD_CALL), you can change the standard setting in the Customizing activity Specify Settings for Shipping ESComXML Files so that the system selects the communication type in the same way as for reports without ESComXML files.

Report Shipping Order for ESComXML Files

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.

  • The system automatically assigns the communication type Mail via Internet (INT) and the communication group ESComXML Over Internet (ESC) to the additional report shipping order.

  • The additional report shipping order for the ESComXML file is part of the shipping order package in which the corresponding extended safety data sheet is shipped.

  • The additional report shipping order for the ESComXML file uses the same status network as the template shipping order.

  • If the status of the report shipping order for the extended safety data sheet and the corresponding ESComXML file is changed from Complete to Historic, the report shipping order for the ESComXML file is deleted from the system.

Report Shipping Package

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

  • If a shipping package containing an extended safety data sheet and ESComXML file exceeds the maximum package size set for the shipping object STD_MAIL in the Customizing activity Specify Shipping Objects, the extended safety data sheet and ESComXML file are divided between two shipping packages, each with its own cover sheet and, if required, acknowledgement of receipt.

  • If the shipping packages are still too large, the shipping orders are assigned error status.

ESComXML File in Report Shipping

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: The system determines the sender using the MSDS initiator (sales organization).

    • E-Mail Address for Information Relevant to Product Safety (for supplier): The system determines the e-mail address of the supplier using the sales organization that you defined in the Customizing activity Specify Additional Data for Sales Organization for each sales organization.

    • DUNS Code: The system determines the DUNS code using the sales organization that you defined in the Customizing activity Specify Additional Data for Sales Organization for each sales organization.

  • 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.

  • The ESComXML file is sent in compressed format together with the extended safety data sheet. In Customizing for Exposure Scenario Management, you can configure whether the ESComXML file is to be compressed in the e-mail attachment. Note that the document is not password protected when compressed.

Monitoring of Shipping Orders with ESComXML Files

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, for example, 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.

  • You can Accept or Reject either the report shipping order of the extended safety data sheet or the report shipping order of the ESComXML file; the entire shipping package is then accepted or rejected.

  • You can change the communication type in the header of an incorrect report shipping order for the extended safety data sheet. You can select only the communication type and not the communication group for shipping ESComXML files. This communication group is determined automatically by the system.

Effects on Customizing
Report Shipping Package

A new user exit is available in the Customizing activity Manage User Exits with the user exit category SRE_DIST for packing report shipping orders with ESComXML files:

  • User exit: ESC_PACK_B

  • Function module: EHSS_ESCOM_PACKAGE_BYTES

Communication Group

A new communication group for shipping ESComXML files is available in the Customizing activity Specify Communication:

  • Communication type: INT

  • Communication group: ESC

  • Source document format: WWI

  • Group description: ESComXML Over Internet

In the Customizing activity Assign Names for User Exits, the new communication group for shipping ESComXML files for user exits is made available:

  • Communication type: INT

  • Communication group: ESC

  • Exit category: GENERATE

  • User exit: EHS_GEN

  • Communication type: INT

  • Communication group: ESC

  • Exit category: PACKAGE

  • User exit: ESC_PACK_B

  • Communication type: INT

  • Communication group: ESC

  • Exit category: BUNDLE

  • User exit: EHS_SEND_I

More Information

For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.comInformation published on SAP site under Start of the navigation path SAP ERP Central Component Next navigation step Logistics Next navigation step Environment, Health and Safety (EHS) Next navigation step Product Safety (EHS-SAF) Next navigation step Exposure Scenario Management End of the navigation path.

For more information, see SAP Library for SAP ERP on SAP Help Portal at http://help.sap.comInformation published on SAP site under Start of the navigation path SAP ERP Central Component Next navigation step Logistics Next navigation step Environment, Health and Safety (EHS) Next navigation step Product Safety (EHS-SAF) Next navigation step Report Shipping (EHS-SAF-RSH) End of the navigation path.

For more information about implementing Exposure Management, see Customizing for Product Safety under Exposure Scenario Management.