Describe in a few words the content of application + link with functional or technical specifications (google links) done with during the project or linked with PPMO
Tool Leader + IT leader of the application:
With SAP Global Trade Services (SAP GTS), you can manage all the complexities of international trade including full regulatory compliance, electronic communication with customs authorities, and risk mitigation, while importing and exporting on a global basis. Business Content for SAP GTS enables you to analyze your import and export transactions and perform strategic reporting for the following areas:
SAP Customs Management: 'Customs Processing' Service
SAP Customs Management: 'Transit Procedure' Service
SAP Risk Management: 'Preference Processing' Service
SAP Risk Management: 'Restitution Handling' Service
SAP Compliance Management: 'Import Legal Control' Service
SAP Compliance Management: 'Export Legal Control' Service.
A large amount of transaction data and master data is available in SAP GTS. A selection of the data is extracted into SAP Business Information Warehouse (SAP BW) and evaluated there. The data flows for transaction data that is extracted from the customs documents which are created in SAP GTS are as follows:
For the data extraction and strategic reporting for SAP Customs Management and SAP Risk Management, the data flow is as follows: DataSource 0SLL_CD_1 → ODS Object 0SLL_DS01 → InfoCube 0SLL_C01
For the data extraction and strategic reporting for SAP Compliance Management, the data flow is as follows: DataSource 0SLL_CD_2 → ODS Object 0SLL_DS02 → InfoCube 0SLL_C02
Note
All other DataSources for master data extraction from SAP GTS to SAP BW have the type direct update.
The following functions are available:
Data extraction for strategic reporting for customs processing, transit procedure, preference processing, restitution handling and legal controls on imports and exports.
Strategic reporting for customs processing
Strategic reporting for preference processing
Strategic reporting for restitution handling
Strategic reporting for import legal control
Strategic reporting for export legal control.
Using the following reports that are available, you can evaluate and analyze data for any of the services you use inSAP GTS:
Import
Imports by product
Imports by country
Import analysis
Imports by office of entry or destination
Comparison of imports between transit and customs processing document items
Export
Exports by product
Exports by country
Export analysis
Export by customs office
Comparison of exports between transit and customs document items
How many users? Which user category ? Is there critical period ? Which geographical perimeter? Describe in one sentence: around 50 users, worldwide or 200 users / European Site
Provide some history of the application : When was it created ? What was the initial project ? Who was the original requestor ? If possible provide link to the project information
List of application role + menu role and explanation if we have several applications role with specials rules.
| Role Code | Role Description | Explanation |
|---|---|---|
List of autorisation objects mandatory for the application.
| Authorization object | Explanation |
|---|---|
Reporting documentation drive folder:
https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE
dataflow overview :
https://docs.google.com/presentation/d/1xnWxI4GErX5vLJ7BvtkxQ7tYSXyG5dLOGN_2aXr5API/edit#slide=id.p
Explanations about the links in GTS :
| Key Figure | Estimation |
|---|---|
| ~ Average Process Chain Runtime | |
| ~ Average nb of rows loaded per load | |
| ~ Total nb of rows loaded (if full) | |
| ~ Average Runtime for 10k lines |
List the most important and complex queries only with a link to the documentation
Give detail on all complex functionalities: list most important and/or complex KPI, query jump, alerts
Indicate if there are broadcasts and give some details on the broadcast settings.
Give the list and explanation on the known, not-solved, bugs.
DataSource Transactional Data: 0SLL_CD_1
This DataSource contains transaction data from customs documents that are created in SAP GTS in the following services:
Customs Processing
Transit Procedure
Preference Processing
Restitution Handling
The data that is extracted to SAP BW then serves to update the ODS object customs document 0SLL_DS_01.
The customs document date, which is extracted from either field SHPTS or PTCTS in the table of origin /SAPSLL/CUHDDAT, depends on whether the customs procedure is for an import or an export transaction. In the case of an import transaction, the source field in the customs document is the date on which the goods are presented to customs for import (Recording/Decl. Date). Fore more information, see the transportation tab page (Transport.) in the 'Customs Processing' service of SAP GTS. In the case of an export transaction, the source field in the customs document is called the transit date for export (Shipping Date). For more information, see the transportation tab page (Transport.) in the 'Transit Procedure' service of SAP GTS.
In any of the services you use in SAP GTS, the country of departure, which is extracted from field CTYDP in either table of origin /SAPSLL/CUIT or /SAPSLL/CUHD, can be extracted at both header and item level in the customs document. For more information, see the transportation tab page (Transport.) at header level (Countries →Issue ) and the Placement tab page at item level (Country of Departure).
The country of destination, which is extracted from the field CTYAR in either table of origin /SAPSLL/CUIT or /SAPSLL/CUHD, can only be extracted at header level in the customs document. For more information, see the transportation tab page (Transport.) in SAP Customs Management at header level (Countries → Placement ).
The following fields contain values that you maintain in the Implementation Guide (IMG) for SAP GTS under SAP Customs Management → 'Customs Processing' Service → Calculation of Customs Duty → Define Customs Duty Framework:
NETVA: Net Price/Invoice Value (001)
STAVA: Statistical Value (003)
CUSVA: Customs Value or Value not Shown Separately (002 or C1)
TCODU: Value not Shown Separately (third-country duty — B1)
PREDU: Value not Shown Separately (preferential duty — B2)
PHPDU: Value not Shown Separately (duty on pharmaceutical products — B3)
SUSDU: Value not Shown Separately (suspension of duty — B4)
ADUDU: Value not Shown Separately (anti-dumping duty — B5)
SUMDU: Value not Shown Separately (total duties — D0)
CURCU: Customs currency
For more information on the value types, such as invoice values and statistical values, and the customs duty types to which you assign the values, see the IMG documentation.
| Application Components | SAP GTS (SLL-LEG) |
|---|---|
| Available as of Release | 3.0 |
| Shipment | November 2004 |
| Content Version | No |
| RemoteCube-Capable | No |
| Delta-Capable | Yes |
| Extraction from Archives | No |
| Verifiable | No |
You have completed the following activities in the Implementation Guide (IMG) for SAP GTS:
You have activated the BIW indicator to transfer customs documents from SAP GTS to SAP BW under SAP Global Trade Services → General Settings → Organizational Structure → Control Settings at Foreign Trade Organization Level.
You have entered a unit of weight in the table for Control Settings at Foreign Trade Organization Level. This unit of weight must be the common unit of weight that you want to be used in the strategic reporting in SAP BW. The values in the fields for gross weight (WEIGR), net weight (WEINE) and unit of weight (WEIDI) depend on the unit of weight you maintain at FTO level in the IMG for converting weights for SAP BW. Note that the value for field NUMIT, number of document items, is always one.
You have activated document types for transferring relevant data from customs documents in SAP GTS toSAP BW. You do this in the IMG for SAP GTS under SAP Customs Management → General Settings →Document Structure → Define Customs Document Types. You have set the indicator Transfer to SAP Business Information Warehouse Active.
You have activated the appropriate item categories in the customs documents for transferring relevant data from business transactions in SAP GTS to SAP BW. You do this in the IMG for SAP GTS under SAP Customs Management → General Settings → Document Structure → Define Customs Item Categories. You have set the indicator Transfer to SAP Business Information Warehouse Active.
You must have set the indicators at all of the following three levels in the Customizing settings for SAP GTS to ensure the necessary transfer of data to SAP BW.
Document level
Item level
Organizational unit level (FTO).
It is possible to perform a delta extraction for this DataSource using the delta method AIMD. However, delta data cannot be extracted from data archives.
Fields of Origin for the Extract Structure| Fields in the Extract Structure | Description of the Field in the Extract Structure | Table of Origin | Field in the Table of Origin |
|---|---|---|---|
| CDNUM | Customs Document Number | /SAPSLL/CUHD | CORDER |
| CDYEA | Customs Document Year | /SAPSLL/CUHD | COYEAR |
| CDITN | Customs Document Item Number | /SAPSLL/CUIT | ITVSY |
| INDEI | Import/Export Indicator | /SAPSLL/CUHD | INDEI |
| ROCANCEL | Cancel Field | Hard-coded | Hard-coded |
| CDSTA | Status of Customs Document | /SAPSLL/CUHDSTA | PROST |
| FCOTD | Flag: Customs or Transit Document | Hard-coded | Hard-coded |
| FRELP | Flag: Relevant for Preference Processing | Hard-coded | Hard-coded |
| PREFL | Flag: Eligible for Preference | Hard-coded | Hard-coded |
| FRELR | Flag: Relevant for Restitution | Hard-coded | Hard-coded |
| CDDAT | Customs Document Date | /SAPSLL/CUHDDAT | SHPTS, PTCTS |
| EXDAT | Export Date | /SAPSLL/CUHDDAT | EXPTS |
| CRDAT | Created-On Date | /SAPSLL/CUHD | CRTSP |
| NSCTC | Numbering Scheme for Tariff Code Number | /SAPSLL/CTSNUMC, /SAPSLL/CTSNUM | STCTS |
| NUCTC | Country for Tariff Code Number | /SAPSLL/CTSNUMC | LAND1 |
| NUMTC | Tariff Code Number | /SAPSLL/CTSNUMC, /SAPSLL/CTSNUM | EXSID |
| NSCCC | Numbering Scheme for Commodity Code | /SAPSLL/CTSNUMC, /SAPSLL/CTSNUM | STCTS |
| NUCCC | Country for Commodity Code | /SAPSLL/CTSNUMC | LAND1 |
| NUMCC | Commodity Code | /SAPSLL/CTSNUMC, /SAPSLL/CTSNUM | EXSID |
| NSCRC | Numbering Scheme for Common Agricultural Policy (CAP) Numbers for Restitution Handling | /SAPSLL/CTSNUMC, /SAPSLL/CTSNUM | STCTS |
| NUMRC | CAP Numbers for Restitution | /SAPSLL/CTSNUM | EXSID |
| BOPNO | Bill of Product Number | /SAPSLL/BOPHD | BOPNPO |
| SECNC | Security Number for Customs Processing and Transit Procedure | /SAPSLL/LCLIC | EXTNO |
| SECNR | Security Number for Restitution | /SAPSLL/LCLIC | EXTNO |
| PRNUM | Product Number | /SAPSLL/PR | PRNUM |
| CTYDP | Country of Departure | /SAPSLL/CUIT, /SAPSLL/CUHD | CTYDP |
| CTYAR | Country of Destination | /SAPSLL/CUIT, /SAPSLL/CUHD | CTYAR |
| CUCOO | Country of Origin | /SAPSLL/CUIT | CUCOO |
| FTORG | Foreign Trade Organization | BUT000 | PARTNER |
| LEGUN | Legal Unit | /SAPSLL/CORPAR | PARNO |
| PSEND | Sender/Exporter | /SAPSLL/CORPAR | PARNO |
| VSEND | Sender/Exporter SAP R/3 Vendor (Import) | /SAPSLL/PNTBP | BPVSY |
| PRECP | Recipient/Importer | /SAPSLL/CORPAR | PARNO |
| CRECP | Recipient/Importer SAP R/3 Customer (Export) | /SAPSLL/PNTBP | BPVSY |
| PDECL | Declarant | /SAPSLL/CORPAR | PARNO |
| PDECS | Declarant (Substitute) | /SAPSLL/CORPAR | PARNO |
| POENT | Office of Entry | /SAPSLL/CORPAR | PARNO |
| PODES | Office of Destination | /SAPSLL/CORPAR | PARNO |
| PODEP | Office of Departure | /SAPSLL/CORPAR | PARNO |
| POEXI | Office of Exit | /SAPSLL/CORPAR | PARNO |
| CCAFA | Requested Concession | /SAPSLL/LEGCUS | CCAFA |
| CUPRO | Procedure | /SAPSLL/LEGCUS | CUPRO |
| DCTYP | Declaration Type | /SAPSLL/LEGACT | DCTYP |
| CSSTA | Customs Status of Goods | LEGCUS | CSSTA |
| MTRDO | Domestic Mode of Transport | /SAPSLL/LEGTPR | MTRDO |
| MTBRC | Mode of Transport at the Border | /SAPSLL/LEGTPR | MTBRC |
| CUHDA | Document Type of Customs Document | /SAPSLL/CUHD | CUHDA |
| CUITA | Item Category of Customs Document | /SAPSLL/CUIT | CUITA |
| LREGC | Legal Regulation for Customs Processing | /SAPSLL/LEGTPR | LGREG |
| LREGP | Legal Regulation for Preference Processing | Hard-coded | LGREG |
| LREGR | Legal Regulation for Preference Processing | /SAPSLL/LEGCON | LGREG |
| INCOT | Incoterm 1 | /SAPSLL/CUHD | INCOT |
| INCOL | Incoterm 2 | /SAPSLL/CUHD | INCOLO |
| EXART | Customs Business Transaction Type | /SAPSLL/LEGTPR | EXART |
| PYTYP | Payment Method | /SAPSLL/LEGTPR | PYTYP |
| AUTNO | Authorization Number | /SAPSLL/LCLIC | EXTNO |
| ADDD1 | Additional Data 1 | /SAPSLL/CUIT | ADDDA1 |
| ADDD2 | Additional Data 2 | /SAPSLL/CUIT | ADDDA2 |
| ADDD3 | Additional Data 3 | /SAPSLL/CUIT | ADDDA3 |
| NETVA | Net Price/Invoice Value | /SAPSLL/LEGCULC | AMNT_CUS |
| STAVA | Statistical Value | /SAPSLL/LEGCULC | AMNT_CUS |
| CUSVA | Customs Value | /SAPSLL/LEGCULC | AMNT_CUS |
| TCODU | Third-Country Duty | /SAPSLL/LEGCULC | AMNT_CUS |
| PREDU | Preferential Duty | /SAPSLL/LEGCULC | AMNT_CUS |
| PHPDU | Pharmaceutical Products Duty | /SAPSLL/LEGCULC | AMNT_CUS |
| SUSDU | Suspension of Duty | /SAPSLL/LEGCULC | AMNT_CUS |
| ADUDU | Anti-Dumping Duty | /SAPSLL/LEGCULC | AMNT_CUS |
| SUMDU | Total: Duties | /SAPSLL/LEGCULC | AMNT_CUS |
| CURCU | Customs Currency | /SAPSLL/LEGCULC | CUR_CUS |
| PRRVA | Comparison Value | /SAPSLL/CUIT | EXPVAL_FLT |
| PRTVA | Threshold Value | /SAPSLL/CUIT | CPVAL_FLT |
| CURPR | Preference Currency | /SAPSLL/CUIT | PRCUR |
| RESVA | Export Refund Amount for Restitution | /SAPSLL/LEGCULC | AMNT_CUS |
| CURRE | Restitution Currency | /SAPSLL/LEGCULC | CUR_CUS |
| QUANB | Quantity in Base Unit of Measure | Calculated | Hard-coded |
| QUAUB | Base Unit of Measure | Calculated | Hard-coded |
| QUAND | Quantity in Document Unit of Measure | /SAPSLL/CUIT | QUANT_FLT |
| QUAUD | Document Unit of Measure | /SAPSLL/CUIT | QUAUM |
| WEIGR | Gross Weight | /SAPSLL/CUIT | WEIGRO_FLT |
| WEINE | Net Weight | /SAPSLL/CUIT | WEINET_FLT |
| WEIDI | Unit of Weight | /SAPSLL/CUIT | WEIDIM |
| NUMIT | Number of Document Items | Calculated | Hard-coded |
This DataSource has the following data flow: DataSource 0SLL_CD_1 → ODS Object 0SLL_DS01 → InfoCube 0SLL_C01. The extractor method is F1.
Detail planned major evolution if already known. Example: complete decommissioning of application is planned in 2017 / Extension to solvay perimeter planned in 2nd semester of 2016