001 Sap Gts 7.2 Delta 1

© SAP AG 1

SAP GRC Global Trade Services

SAP GTS 7.2 Delta Overview

Part 1

© SAP AG 2

© SAP AG 2007

Objectives

This session focuses on the explanation of the Delta SAP GTS 7.2 and its benefits to customers

After completing this presentation, you will be able to:

To communicate and clearly understand the new functions of SAP GRC GTS Release 7.2

Communicate the value proposition of SAP GRC GTS 7.2

Communicate how SAP GRC GTS 7.2 alleviates customer pain points

© SAP AG 3

Risk Management

Compliance Management

Customs Management

Electronic Compliance Reporting

© SAP AG 4

Risk Management


Customs Management


© SAP AG 5

SPL TREX

Content Migration (Data Provider Integration)Content Upload (License Type Determination)

Trade Compliance EnhancementsITAR Nested License Delta Umstellung Sperrlogik für Kontrollstämme

© SAP AG 6

SPL TREX



© SAP AG 7

© SAP AG 2007

TREX Integration – Goal, Business Benefit

Goal of TREX integration in SPL Screening:

TREX is a basis component of Netweaver 2004s providing up-to-datetechnology (adopted for catalogue searches, A1S, etc…)

TREX offers an alternative search algorithm enhancing the existing GTS SPL search logic.

Activation of TREX is customizable and an additional option for SPL Screening per Comparison Procedure and Legal Regulation.

© SAP AG 8

© SAP AG 2007

TREX Integration – Goal, Business Benefit

Business benefit of TREX integration:

TREX is continuously improved and provides latest technology.

Being an additional option TREX offers a search algorithm, whichenlarges GTS SPL logic with a further fuzzy search logic.

As time-consuming maintenance and validation of normalization settings is not necessarily demanded, activation of TREX search algorithm requires less implementation effort.

TREX enabling is a further enhancement of SPL error-tolerant searchand improves the quality of delivered SPL matches perceptively.

© SAP AG 9

© SAP AG 2007

TREX Integration – Functional Scope

SPL logic:

GTS SPL search logic consists of four steps to screen business partner addresses against SPL lists:

1. Generation of Search Terms applying normalization settings in order to create an error-tolerant Search Index for addresses and SPL Lists.

2. SPL hits are found by comparing Search Index against each other. Normalized Search Terms should match exactly.

3. Original Terms of SPL hits are evaluated by using percentage of Minimal Similarity defined in the Customizing of the Comparison Procedure.

4. Originating feature: Number of matches per address category (e.g. name) iscalculated.

© SAP AG 10

© SAP AG 2007

TREX Integration – Functional Scope

TREX enhances step 2:

The TREX search algorithm softens SPL logic even further as nowSearch Terms can differ from each other according to defineddeviation of Match Record.

The evaluation of Search Terms by TREX make SPL logic becomemore flexible and error-tolerant and enhances the quality of SPL hits.

The hits made by Search Terms are transferred back to GTS wherethe SPL logic continues with step 3 as described.

GTS SPL Logic now calculates the similarity percentage of theOriginal Partner and SPL Terms.

© SAP AG 11

SPL TREX



© SAP AG 12

SPL TREX



© SAP AG 13

© SAP AG 2007

Content Migration (Goal , Business Benefits)

Features: Content Migration Toolset

1. Check the feasibility of content migration.

2. Check the content for possible errors.

3. Check the existing classification for possible errors.

4. Copy the classification of products using a particular source scheme to another classification using a particular target scheme.

5. Delete classifications of a given scheme

6. After migration the documents using the old classification still refer to the old data while the new documents refer to the new data scheme.

Business Benefit: Content Migration allows you to conveniently replace the content of data providers by checking and replacing number schemes for tariff and commodity codes (product classifications).

There are many reasons why at some point you may want to change your data provider.

With the GTS 7.2 content migration functionality it is conveniently possible to follow the market laws without much trouble of reconfiguring your system.

The GTS 7.2 content migration functionality allows great independence from content providers giving your company a high degree of flexibility.

The content migration tool assists in analyzing the relevant number schemes´ information (product classification) regarding corrupt or mismatching data.

For auditing reasons all classifications are held available in the system, i.e. information is transparently available based on defined validity periods.

© SAP AG 14

SPL TREX



© SAP AG 15

© SAP AG 2007

Trade Compliance Enhancements – Part 1

1. Re-Design SPL Screening Results

2. Compliance Check at Customs Declaration

3. Compliance Survey

4. SPL Offline Screening

5. SPL Simulation Audit Trail Update

6. Audit Trail Update during Document Transfer

7. SPL Screening Details in Audit Trail

8. Audit Trail Report for External Auditor

© SAP AG 16

© SAP AG 2007

Trade Compliance Enhancements – Part 2

9. E-mail notification for blocked business partners

10.Workload blocked business partners / documents

11.Distinguish soft blocked documents

12.Blocked documents selection criteria

13.Analyze SPL-comments from blocked partners and documents reports

14.Analyze SPL details from blocked partners and documents reports

15.Analyze valid-to date in blocked partners report as SPL block validity

16.SPL cross-check enhancement

17.Consideration of Positive and Negative List during SPL screeningafter Business Partner transfer

© SAP AG 17

© SAP AG 2007

1. Re-Design SPL-Screening Result Screen – Goals, Business Benefits

Goals

Provide and a new UI for all existing SPL Screening scenario

Business Benefits

Flexible screen area with easy navigation.

Old tree structure is replaced by ALV grid which allows user to select required columns to view, export data in various format etc.,

All required information can be seen in single window. Detailed analysis of SPL match entries which was part of a sub-screen now available on the main screen it self.

© SAP AG 18

© SAP AG 2007

2. SPL Screening of Customs Declarations/Customs Shipments – Reasons and Benefits

1. If the business partners of an inbound or outbound transaction changes in the GTS customs declarations/customs shipments it was not possible to recheck them against official sanctioned party lists.

2. With the new functionality it is possible to simulate an SPL screening in the customs declarations/customs shipments and place dubious documents into the blocked-documents-worklist until release.

3. This functionality also helps to bridge possible time-spans between the creation of the GTS customs declarations/customs shipments and the actual customs declaration. For compliance audit reasons you can perform an additional SPL-check.

4. Please note that the check can also be performed on embargo situations, i.e. on country level.

© SAP AG 19

© SAP AG 2007

3. Compliance Survey - Goals & Business Benefits

Goal

To provide a facility to classify the reason for the release of a Business Partner or Document in Compliance Management using standardized customizable options, which can be used later for analysis.

Business Benefits

Analysis of the SPL customizing and its fine tuning is enabled based on the analysis of the data presented by the Compliance Survey Report for SPL

Fine Tuning of the Embargo configuration is enabled based on the analysis of the data presented by the Compliance Survey Report for SPL

© SAP AG 20

© SAP AG 2007

3. Compliance Survey - Functional Scope

When Documents and Business Partners which are blocked due to SPL checks are released comments can be entered. But due to the free text nature analysis based on these comments is not possible. For this purpose predefined texts or Reasons for Release can be used. These Reasons for Release can be defined in customizing and can be associated with an individual object such as Document or Business Partner during release. The Compliance Survey report enables analysis of the objects released or associated with Release Reasons.

The same facility is available during release of Embargo blockeddocuments.

Note: This feature is not meant to replace the comments functionality that already exists.

© SAP AG 21

© SAP AG 2007

Offline-SPL-Screening allows you to conveniently check external lists (.xml-files) against the sanctioned party lists maintained in GTS 7.2.

The result of the screening is documented both in the system´s audit trail and as external .xml file.

4. SPL Offline Screening - Business Benefit

With offline screening, a new approach for checking address information is provided.

Already existing methods include:

Online simulation of addresses entered via SAP GUI or BSP-Application

Remote Functions Call to /SAPSLL/SPL_SCENARIO_S3_RFC

The new method now allows checking addresses delivered via data files.

© SAP AG 22

© SAP AG 2007

Perform a compliance check of business contacts on external documents (.xml-files)

Edit the results manually in GTS

Archive the results in the GTS audit log

Save the results into an .xml-file for external use.

Simplify compliance checks and extend the checking routines to external documents

4. SPL Offline Screening - Features Delivered with SAP GTS 7.2

Prepare an xml-file with address data

Execute a compliance check on the local file

Examine the results, [Release Partners]

Save results in Audit Trail and/or local file

Most common sequence of actions.

Using xml as an intermediate format allows checking from arbitrary sources.

© SAP AG 23

© SAP AG 2007

5. SPL-Simulation Audit Trail Update - Goals & Business Benefits

Goals

Save audit for Sanctioned Party List address simulation screening results.

Business Benefits

Users can have a log of all checked results which can be cross checked for audit purpose

This functionality is optional so users can decide if they want to activate this feature or not

© SAP AG 24

© SAP AG 2007

5. SPL-Simulation Audit Trail Update - Functional Scope

1. The program shall provide an option to user to save SPL simulation results

2. The program shall provide an UI to view stored SPL simulation results

3. The program shall provide user to activate save option via standard GTS customizing

© SAP AG 25

© SAP AG 2007

6. SPL Screening Audit During Document Transfer – Goal, Business Benefit

Goal:

During document transfer an audit trail shall be written if SPL status check is performed for document partners. Audit trail is relevant for both asynchronous / synchronous SPL scenario.

Business benefit:

The SPL audit trail presents user with information regarding the SPL check during document transfer.

© SAP AG 26

© SAP AG 2007

6. SPL Screening Audit During Document Transfer –Functional Scope

Functional Scope:

1. Documents are transferred from feeder system to SAP GTS for SPL screening. User can choose in the customizing settings if synchronous or asynchronous SPL screening shall be performed on transfer.

2. A document address may undergo a SPL screening if address has been changed within the document manually. Else only a status check is performed of the partner in SAP GTS.

3. In synchronous screening SPL screening is performed for the changed address and status check for unchanged addresses within document.

4. In asynchronous screening status check is performed for unchanged address, but for changed address SPL screening is not run – and is deferred until user starts it manually in SAP GTS.

5. An audit trail is to be written for all status checks / SPL screening performed during document transfer.

© SAP AG 27

© SAP AG 2007

7. SPL Check Details – Goal , Business Benefit

Goal:

During SPL check if a partner / address is blocked, then on saving results, detail analysis shall be saved as well. If shall be accessible from the audit trail reports.

Business benefit:

The SPL audit trail review presents user with more information regarding the block of a business partner / address.

© SAP AG 28

© SAP AG 2007

7. SPL Check Details – Functional Scope

Functional Scope:

Business partner and documents are transferred to SAP GTS for SPL screening. An address is SPL blocked if corresponding entry is found in SPL master. User can control via customizing settings the minimum percentage match between terms.

The percentage match between the address terms & SPL entity terms is displayed on the SPL check result screen. On saving the SPL check results, this detail analysis regarding percentage match between original terms shall be saved. It can be reviewed later via the Audit trail report.

© SAP AG 29

© SAP AG 2007

Goals

To present the Audit data for Documents or Business Partners in a easy to read format to the external auditor with all the relevant data in a single screen.

Business Advantages

All the necessary data is displayed in a single screen

The individual objects Business Partners, Customs Documents, Comments and SPL Master data can be navigated to directly from this screen

The data can be printed from the ALV grids for hard copies

The data can be exported to MS Excel sheets for external processing

No SAP GTS experience is required to use the transaction

8. Audit Trail Report for External Auditor - Goals & Business Benefits

© SAP AG 30

© SAP AG 2007

8. Audit Trail Report for External Auditor - Functional Scope

The results of Sanctioned Party List Screenings performed maybe saved for audit purposes in the Audit Trail.

To enable the External Auditors to clearly understand and analyze audit data for a Customs Document or a Business Partner the all the relevant data is presented in a single window using the Audit Trail Report for External Auditor.

The report provides the SPL audit data, the data about the entities matched and the match details in a format that can be printed and also downloaded into an MS Excel file for external processing.

© SAP AG 31

© SAP AG 2007

9. E-mail Notification – Goal , Business Benefit

Goal of e-mail notification functionality:

1) During synchronous SPL screening of partners - if a partner is blocked - an e-mail notification is sent to a designated user group.

2) Activation of e-mail notification is customizable.

Business benefit of e-mail notification functionality:

Users does not have to monitor the blocked business partner report in SAP GTS on a regular basis to check new blocked partners. Notification of new blocked partners is sent via e-mail to designated user group.

© SAP AG 32

© SAP AG 2007

9. E-mail Notification– Functional Scope

Functional Scope:

Business partners from feeder system are transferred to SAP GTS for compliance checks like Sanctioned Party List (SPL) screening. Ifsynchronous SPL screening is activated, SPL check is performed as soon as business partner is transferred to SAP GTS. If the partner is blocked due to SPL entity, an e-mail is sent to designated user groups. One e-mail is generated for each blocked business partner.

The activation of e-mail notification service for business partners is customizable.

© SAP AG 33

© SAP AG 2007

10. Analyze Blocked Parnter & Documents– Goal , Business Benefit

Goal:

Blocked business partners & documents which are already reviewedshall be distinguished from the ones, which are new and not reviewed yet in the monitoring reports.

Business benefit:

User has to know which blocked partners / documents have been already reviewed and which are yet to be reviewed.

© SAP AG 34

© SAP AG 2007

10. Analyze Blocked Parnter & Documents– Functional Scope

Functional Scope:

Business partners and customs documents from feeder system are transferred to SAP GTS for compliance checks like Sanction Party List ( SPL ) screening.

Partners or documents can be blocked due to matching SPL entity. They are monitored in SAP GTS by blocked partner or blocked document monitoring report. Once reviewed, user may be interested in reviewing only the new blocked partners or documents in the next run of reports.

In the monitoring report user has the option to mark partners / documents which have already been reviewed as ‘Confirm’ or ‘On hold’. On the selection screen of monitoring reports, user has the option if he would like to see all partners or only ‘new’, ’confirmed’, ‘on hold’.

© SAP AG 35

© SAP AG 2007

11. Analyze Soft Block Documents– Goal , Business Benefit

Goal:

Documents blocked due to asynchronous SPL screening (so-called soft-blocks) shall be distinguished from real SPL-blocked documents in the monitoring report.

Business benefit:

User has to know which documents are soft blocked and which are real SPL-blocks from the monitoring report.

© SAP AG 36

© SAP AG 2007

11. Analyze Soft Block Documents– Functional Scope

Functional Scope:

Documents from feeder system are transferred to SAP GTS forcompliance checks like Sanctioned Party List (SPL) screening.

User can choose if they would like to have synchronous or asynchronous screening for documents. In synchronous screening SPL screening is performed at runtime, i.e. at the same time when the document is transferred to GTS. In asynchronous mode, SPL screening is deferred to a later time when user decided to run it in SAP GTS. Till that time, document is classified as soft-blocked.

In the monitoring report for blocked documents, user can identify which document is soft-blocked and which ones are real-blocked.

© SAP AG 37

© SAP AG 2007

17. Consideration of Positive and Negative List During SPL Screening After Business Partner Transfer – Goals, Business Advantage

Goals

Business Partners that are on the Positive or Negative list must not be screened in SPL screening done after they are retransferred to GTS from the feeder system.

Business Advantage

1. Business Partners added to the SPL Positive List are retained after retransfer to GTS

2. Business Partners added to SPL Negative List are retained after retransfer to GTS

3. No extra effort needed to track changes to SPL status of Business Partner after retransfer to GTS

© SAP AG 38

© SAP AG 2007

12. Select Blocked Documents– Goal , Business Benefit

Goal:

Documents blocked in SAP GTS are monitored using blocked documents report. User shall be able to select blocked documentsbased on the document type in SAP GTS.

Business benefit:

Users don’t have to check the document type in the result screen if they are looking for a particular type of documents. They can directly specify on the selection screen the type of document they would like to monitor.

© SAP AG 39

© SAP AG 2007

12. Select Blocked Documents– Functional Scope

Functional Scope:

Various types of Customs documents like sales order, delivery etc. from feeder system are transferred to SAP GTS for compliance checks like Sanction Party List ( SPL ) screening.

Documents can be blocked due to matching SPL entity. They are monitored in SAP GTS by blocked document monitoring report.

They can be monitored based on document type in SAP GTS.

© SAP AG 40

© SAP AG 2007

13. Analyze SPL-Comments – Goal , Business Benefit

Goal:

Comments entered during SPL-check shall be accessible via monitoring reports for blocked partners and documents.

Business benefit:

Users does not have to check the audit trail report separately to read the SPL-comments. SPL-check comments can be seen directly through the blocked partner or blocked document report.

© SAP AG 41

© SAP AG 2007

13. Analyze SPL-comments – Functional Scope

Functional scope:

Business partners and customs documents from feeder system are transferred to SAP GTS for compliance checks like Sanctioned Party List (SPL) screening.

Partners or documents can be blocked due to matching SPL-entity. During the check users have the possibility to enter comments onresult screen. They are monitored in SAP GTS by blocked partner or blocked document monitoring report.

Comments entered during check are later viewed by audit trail report. Now they can also be reviewed directly through the monitoring reports of blocked partners and blocked documents.

© SAP AG 42

© SAP AG 2007

14. Analyze SPL Details – Goal , Business Benefit

Goal:

Details of SPL-block shall be accessible via monitoring reports for blocked partners and documents.

Business benefit:

Users does not have to check the audit trail report separately to know the SPL details. SPL check details can be navigated directly through the blocked partner or blocked document report.

© SAP AG 43

© SAP AG 2007

14. Analyze SPL Details– Functional Scope

Functional scope:

Business partners and customs documents from feeder system are transferred to SAP GTS for compliance checks like Sanctioned Party List (SPL) screening.

Partners or documents can be blocked due to matching SPL entity. They are monitored in SAP GTS by blocked partner or blocked document monitoring report. The details of SPL check are saved during SPL check and can be viewed later via audit trail report.These details of SPL check can now also be checked directly by blocked business partner or blocked documents report.

© SAP AG 44

© SAP AG 2007

15. SPL Block Validity– Goal , Business Benefit

Goal:

Business partners blocked in SAP GTS are monitored using blockedpartners report. The Valid-To date in blocked partners display shall represent the date till which SPL block is valid.

Business benefit:

Users don’t have to check the SPL master to find out the validity of SPL entity which caused the block. They can directly check the valid-to date in the display to know the validity of block.

© SAP AG 45

© SAP AG 2007

15. SPL Block Validity – Functional Scope

Functional scope:

Business partners from feeder system are transferred to SAP GTS for compliance checks like Sanctioned Party List (SPL) screening.

Partners can be blocked due to matching SPL entity. They are monitored in SAP GTS by display blocked partners monitoring report.

The matching SPL entity has a validity date. The SPL block obly valid till that date.

The display of blocked partners via blocked business partner report displays valid-to date as SPL block validity date.

© SAP AG 46

© SAP AG 2007

16. SPL Cross Check – Goal , Business Benefit

Goal:

User can activate search terms relevant for SPL check in customizing settings. Only search term types, which are activated in customizing shall be considered for SPL during cross-check.

Business benefit:

Cross-check scenario becomes more intuitive to user, where only those search terms are considered which are activated for SPL check in customizing.

© SAP AG 47

© SAP AG 2007

16. SPL Cross Check – Functional Scope

Functional Scope:

Business partner and documents are transferred to SAP GTS for SPL screening. User can activate in customizing which search terms are relevant for SPL check like Name, Street, City, Country etc.

In normal SPL scenario ( i.e. without cross-check active), a Name of partner is matched with Name of SPL entity , Street with Street etc.

But if cross-check is activated, then Name of partner could match with for example, Street of SPL entity.

New functionality ensures that even if cross-check is active, system shall consider only those search terms which are activated for SPL check in customizing and find cross-checks only among them, and not for search terms which are not active in customizing.

© SAP AG 48

© SAP AG 2007

17. Consideration of Positive and Negative List During SPL Screening After Business Partner Transfer – Functional Scope

Business partners that are to remain released always can be added to theSPL positive list. Similarly business partners that are to remain blockedalways can be added to the SPL negative list. The business partners on theselists are excluded during normal SPL screening of business partners, sincetheir SPL status has already been fixed by the user.

However if the business partners are changed in the feeder system and retransferred to GTS then these business partners are included in by theprevious versions of GTS during the screening in A1 or synchronousscreening scenarios, depending on the customizing. The result is that thesebusiness partners will no longer appear on SPL positive and negative lists.

With GTS 7.2 during retransfer of changed business partners into GTS fromthe feeder system there is consideration of the presence of the businesspartner on either the SPL positive or SPL negative list, and therefore thebusiness partner will be excluded from the SPL screening in A1 orsynchronous screening scenarios, depending on the customizing.

© SAP AG 49

SPL TREX



© SAP AG 50

© SAP AG 2007

ITAR Nested License Delta – Business Benefit

US ITAR (International Traffics and Arms Regulation) is a new process within SAP GTS 7.2 Compliance Management to support the requirements of the US International Traffic in Arms Regulations (ITAR). ITAR is a complex set of regulations from the US State Department that affect US importers and exporters who deal in military, aerospace, nuclear program or any other commodity or transaction that is deemed to relate to US national security.

In order to an exporter or an importer to conduct business with any ITAR controlled product or service, various license types are required from the US State Departments DDTC (www.pmdtc.org).

These licenses are for various types of processes including

physical shipment of hardware or equipment,

transfer of expertise or assistance and

technical data or information.

Each of these categories of controlled processes can require one or more ITAR licenses to conduct the complete transaction.

A single export process may require more than one license to be applied for the sameline item on the same shipment. The licenses assigned to the line item must be related and validated to all attached license.

© SAP AG 51

© SAP AG 2007

ITAR Nested License Delta – Business Benefit

There are 3 main categories of licenses from the US State Department:

• Hardware License• Technical Assistance Agreement• Manufacture License Agreement

Each of these license types have a district purpose and can be applied for and used independently or on as a group of license for a single process.

As an example, an aerospace company wants to bid on an engine design for a military jet. Before the bid can even be engaged and the product specification can be shared, the exporter must apply for an receive a TAA (Technical Assistance Agreement).

If the export is consulting or in anyway sharing data, process, or any other controlled knowledge with the oversea customer, the TAA is required. The TAA operates very much as a license and can be designated for a specific product, USML, customer, country, etc. Once the exporter then wants to ship physical goods (hardware) out of the country, he needs to apply for an export license. This typically is referred to as a DSP-5 from the DDTC and the application for this license must reference the existing and valid TAA associated to the project involved with this sale/shipment.

The application of the DSP-5 must take into account the attributes on the TAA such as dates, values, quantities, etc.

Department of State responsibility for the control of the permanent and temporary export and temporary import of defense articles and services is governed primarily by 22 U.S.C. 2778 of the Arms Export Control Act (AECA) and Executive Order 11958, as amended. The AECA, among these other requirements and authorities, provides for the promulgation of implementing regulations, the International Traffic in Arms Regulations (ITAR) (22 CFR 120-130). The ITAR is available from the Government Printing Office (GPO) either as an annual hardcopy publication as part of the Code of Federal Regulations or as an e-document. The annual GPO publication includes all amendments to the ITAR made since the last annual printing. (Currently those amendments occur from April 1 through March 31 of each year)

© SAP AG 52

SPL TREX



© SAP AG 53

Risk Management


Customs Management


Generic Functions

© SAP AG 54

REACH (EH&S Integration)

ClassificationSAP GTS PI

© SAP AG 55



© SAP AG 56

© SAP AG 2007

Compliance Management - REACH (EH&S Integration) –Scope

REACH (Registration, Evaluation and Authorization of Chemicals) is an EU wide legal framework to controll the imported chemical substances into EU.

The Companies have to register all substances (new and already existing substances) as well as recheck constistantly the registration-status of substances delivered by vendors to the demandingEU-company (import). In addition, the importer has to be aware of the substance-dossier.

Therefor SAP offers a SAP REACH Compliance Management:

Enterprise SOA by EvolutionSAP NetWeaver

Composite for REACH Compliance

SAPERP

EH&S

DMS

cProjects

RegistrationDatabase

TaskManagement

Up& DownstreamCommunication

Reports &Analytics

3rd Party

IUCLID5

ES/CSA/CSR

SIEF

SAPGTS

Compliance ManagementImport ControlExport Control

© SAP AG 57

© SAP AG 2007

Compliance Management - REACH (EH&S Integration) –Business Benefit

For supporting the import process of substances, SAP GRC GTS 7.2 offers the new Service „Hazardous Substance Check“.

If the new legal legislation „REACH“ is activated in SAP ComplianceManagement, the „Hazardous Substance Check“ provides the benefit of the integration to SAP ERP Environment, Health and Safet (ERP EH&S).

ERP EH&S can be discribed as an admin-tool on substance-level (not on material- or product-level as usual for SAP ERP) and integrates a service especially made for REACH: „Substance Volume Tracking“(SVT).

The goal of SVT is to check the threshold Limit (substance dossiers)and Notification Status of Substances as well as consistant rewrite and update the number of already imported substances.

Finally, with the „Hazardous Substance Check“ and the integration to ERP EH&S / SVT the possibility is given to „pre-check“ the purchase-order (item-level) created/modified in ERP MM the threshold limit andRegistration Status

before the import-process can be fulfilled in SAP GRC GTS.

© SAP AG 58

© SAP AG 2007

Compliance Management - REACH (EH&S Integration) –Functional Scope

© SAP AG 59



© SAP AG 60

© SAP AG 2007

Currently all feeder functionality used to feed SAP GTS depends on standard Plug-Ins and/or Release Levels in the feeder systems.

From now on, a separate Plug-In with dedicated functionality to support SAP GTS will be provided.

This allows

To easily implement the feeder systems support for new GTS functions

To reduce test effort at the feeder site when solely GTS is to be upgraded

To reduce total implementation costs

SAP GTS Plug-In - Change in Paradigm

This new feature introduces more flexibility for connecting feeder systems to SAP GTS.

It should be convenient for customers who want to upgrade SAP GTS but stay to a well established Service Pack Level in the feeder system.

© SAP AG 61

Upgrade Path

Plug-In Deployment up to GTS 7.1

Plug-In Deployment from GTS 7.2 Onwards

Maintenance Strategy

© SAP AG 62

Upgrade Path




© SAP AG 63

© SAP AG 2007


SAP_APPL 600, SP06ERP 2005PI 2004_1_500, SP13ERP 2004PI 2004_1_470, SP134.7PI 2004_1_46C, SP134.6C7.1SAP_APPL 600, SP06ERP 2005PI 2004_1_500, SP09ERP 2004PI 2004_1_470, SP094.7PI 2004_1_46C, SP094.6CPI 2004_1_46B, SP104.6B7.0SAP_APPL 600, SP06ERP 2005PI 2004_1_500, SP03ERP 2004PI 2004_1_470, SP034.7PI 2004_1_46C, SP034.6C

PI 2004_1_46B, SP034.6B

PI 2004_1_45B, SP034.5BPI 2004_1_40B, SP034.0B3.0

Plug-InR/3 ReleaseGTS Release

The table above lists all PI und SP Levels needed for the corresponding SAP GTS SP levels if the most recent functions are required.

© SAP AG 64

© SAP AG 2007

Plug-In Deployment up to GTS 7.1 – Compatibility

GTS-PI is upwards compatibleI.e. the PI deployed for GTS 3.0 supports GTS 7.1Limitation:in the example above only the functional scope of GTS 3.0 can be used in the GTS 7.1 installation

GTS-PI is downwards compatibleI.e. the PI deployed for GTS 7.1 supports GTS 3.0

All Plug-In and Service Packs with feeder system functions for SAP GTS are upwards and downwards compatible regarding GTS Levels

© SAP AG 65

Upgrade Path




© SAP AG 66

© SAP AG 2007

Plug-In Deployment from GTS 7.2 0nwards

New GTS-Plug-In will provide independent functions:Independent of Plug-In PI 2004_1_xxx (R/3 4.6C – ERP 2004)Independent of SAP_APPL (ERP 2005)

New GTS-Plug-In will allow independent InstallationIndependent of PI 2004_1 and SAP_APPLSeparate release cycle synchronized with GTS-release, i.e.

GTS 7.2 corresponds with GTS-PI 7.2GTS x.y corresponds with GTS-PI x.y…

New GTS-Plug-In will be downwards compatiblei.e. the PI deployed for GTS 7.2 also supports GTS 3.0i.e. the PI deployed for GTS x.y also supports GTS 3.0 … GTS 7.2

New GTS-Plug-In will be upwards compatibleYou don’t have to upgrade your separate GTS Plug-In unless you want to use new functions offered by higher release levels.

GTS Plug-In will be independent and fully compatible in both directions

Plug-In will be in synch with GTS Releases

© SAP AG 67

Upgrade Path




© SAP AG 68

© SAP AG 2007

Copyright 2007 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.