General presentation

Objective of the application

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.

History

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:

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 in SAP GTS from main tcode /SAPSLL/MENU_LEGAL:

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


The SAP papers indicate the main processes by the standard datasources 0SLL_CD_1 and 0SLL_CD_2. However because we have specific requisites in Solvay, the project team recrated the compliance management process (0SLL_CD_2) in the generic function module datasource DTS_SLL_CD_2 (function module Z_BW_GET_CD_2).

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

    End of the note.


Starting from:

      SELECT  DISTINCT
      h~corder     AS cdnum
      h~coyear     AS cdyea
      i ~itvsy      AS cditn
      h~indei      AS indei
      h~crtsp      AS crtsp
      h~chtsp      AS chtsp
      h~guid_cuhd  AS guid_cuhd
      i ~guid_cuit  AS guid_cuit
      i ~ctydp      AS ctydp
      i ~ctyar      AS ctyar
      i ~ctypl      AS ctypl
      i ~ctyiv      AS ctyiv
      h~cuhda      AS cuhda
      i ~cuita      AS cuita
      i ~quant_flt  AS quand
      i ~quaum      AS quaud
      i ~weigro_flt AS weigro_flt
      i ~weinet_flt AS weinet_flt
      i ~weidim     AS weidim
      f~partner    AS ftorg
      i ~netval_flt AS ntval
      i ~ntcur      AS ntcur
      FROM
      /sapsll/cuhd AS h                                 "Customs Document: Header

      LEFT  JOIN /sapsll/cuit AS  i                   "Customs Document: Item
          ON h~mandt  i ~mandt
         AND h~guid_cuhd  i ~guid_cuhd

      LEFT  JOIN /sapsll/cuhddat AS d         "GTS: Customs Document: Header Dates
          ON h~mandt d~mandt
         AND d~mobjt  'O'
         AND h~guid_cuhd d~guid_mobj

      LEFT OUTER JOIN but000 AS f            "Businness Partner: General data
          ON  h~mandt f~ client
         AND h~guid_ftorg f~partner_guid

    WHERE  h~crtsp IN g_r_crtsp
        OR h~chtsp IN g_r_crtsp )   " FD 41031
      AND   h~corder IN g_r_corder
      AND   h~cdtyp IN  (space 'A' 'C' )
      AND   h~cuhda IN g_r_cuhda.


  • All other DataSources for master data extraction from SAP GTS to SAP BW have the type direct update.


Roles & Access

Roles and access

The GTS objects are under SCMS layer by the roles:

Role CodeRole DescriptionExplanation
ZR_RCS_CA_M49SD - Sales and DistributionRole menu

Authorization objects

List of autorisation objects mandatory for the application.

Authorization objectExplanation
ZR_SD_CA_P05Global Business Unit (CPFCTR1_2)
ZR_TOUT_CA_P01

Company Code (C_COMPCDE)

Dataflow overview

GTS - Customs Document (MPR_GTS01)

Flow to control imports and exports from standard datasource 0SLL_CD_1 (no specific business rules applied in this flow).


GTS Product Compliance (IFS_PR92)

Flow to control the compliance over the existent products.

C_PRNCTY - GTS Product by Country

Master data to convert the external combination of product number and country in the corresponding objects in SAP code.

Source material plant (c_matpnt2) and DTS_PROD_EXTN (material extension)


DP_GTS92 - GTS Product - Compliance

Daily full reload to assign the corresponding legal regulation according to the combination of product and country from plant.

The source DTS_PROD_LEG takes into account the assignments done at level of product x compliance and the other one DTS_PROD_LEG2 is used by a view linked to compliance x classification of the products.


DP_GTS94

Daily full reload from master data GTS Product x Country to explode the information according to the legal regulation.


The legal regulations come from the table APSDGT01 where we retrieve data from the GTS tables /SAPSLL/ALGR01 (legal regulation per country) and /SAPSLL/ALGR11 (legal regulation per country group). 

Sales Order x Classification (CPSDGT01)

Join between sales orders and billing document with the legal regulations available by material and country assignments.

Trade Compliance (CPSDGT02)

The composite provider is composed by two different views for trade compliance documents.

  • CV_SD_GT_CPSDGT02 - GTS documents by locked partner (payer, ship-to, sold-to and billing to).

           

  • CV_SD_GT_CPSDGT02_0002 - SPL view following the movements of the blocked and released documents and licenses.

Both views have as background the provider DB_GTS03, where the main source is the customized datasource mentioned previously DTS_SLL_CD_2. 

The datasource extracts data from document item level in SAP GTS created or changed in the last 40 days.


Main business rules:

Foreign trade organization starting with LU_S belongs Solvay plants. The plant is assigned with the char 6 to 9. While Rhodia plants are based on char 4 to 7.


This table saves by look up from DB_GTS01, the actions performed on embargo, spl and others legal controls using document and year as reference.


On time that DB_GTS01 is result from the logs table (CDHDR and CDPOS) on status table (/SAPSLL/CUHDSTA) by the program ZBW_PRG_CHANGE_ST.

Locked Partners (CPSDGT03)

View ZV_BLBP (Santioned Party List Screening: Blocked Business Partners) result from partner information available on KNA1 and BUT00 with legal Control from  the corresponding address.

GTS Licenses (CPSDGT04)

View based on master data C_LICNUM, which use as source the table /SAPSLL/LCLIC.


Reporting documentation drive folder:

https://drive.google.com/drive/folders/0B0qn89R0RGdqYkZZOFZyYXlXVkE

dataflow overview :

https://drive.google.com/file/d/1_gTYCXm6O6To6xyVR58QzG0q5QnKjavSbLyHrrGG_vk/view


Functional and Technical rules on Workbench + Reporting

Rules & Explanations


•Main analysis axis
  •  Customs Doc. No.
  • Legal Unit
  • Goods Supplier
  • Country of Departure
  • Document Status
  • Customs Procedure Code
  • Customs Duty
  • Customs Value
  • Net Weight
  • VAT Calculation Amnt
  • VAT Paid Amount
  • Third-Country Duty
  • Percentage Duty  Rate (Third-Country Duty / Customs Value)


•Main reports
  • Supplier Bills
  • Imports by plant
•Technical scope
  • GTS standard extractors


Explanations about the links in GTS :


Dependencies with other applications

Dependancies with SD and GSV application (old purchase application)

Check the transformation : TRSF : 0SLL_CD_1 -> ODSGTS01 

In the start routine :

Data loadings

Info providers and objects loaded


Loading frequency

Daily - process chain GTS_MASTER_MAIN


Average performance



Key FigureEstimation
~ Average Process Chain Runtime1,5 hour
~ Average nb of rows loaded per load
~ Total nb of rows loaded (if full)
~ Average Runtime for 10k lines

Record Keeping


Reporting

Queries End User Documentation



Main queries

The main reports available in the GTS models are:

Customs

 

Export

BW_QRY_MPR_GTS01_0004

Import

BW_QRY_MPR_GTS01_0001

Material

 

 

 



Customs classification

BW_QRY_IFS_PRCT2_0001

Legal Regulation + Sales

BW_QRY_CPSDGT01_0001

Legal Regulation

BW_QRY_CPSDGT05_0001

Trade Preference

BW_QRY_MVSDGT93_0001

Compliance

 

 

Trade Compliance: SPL

BW_QRY_CPSDGT02_0002

Trade Compliance: License

BW_QRY_CPSDGT02_0001

Licenses

BW_QRY_CPSDGT04_0001

Locked Partners

BW_QRY_CPSDGT03_0001


Main functionalities

Broadcast

Maintenance

Known bugs

Recurring procedure


DataSource for Customs Documents

DataSource Transactional Data 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.

Technical Data

Application ComponentsSAP GTS (SLL-LEG)
Available as of Release3.0
ShipmentNovember 2004
Content VersionNo
RemoteCube-CapableNo
Delta-CapableYes
Extraction from ArchivesNo
VerifiableNo

Prerequisites

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.

  1. Document level

  2. Item level

  3. Organizational unit level (FTO).

Integration

Delta Update

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 StructureDescription of the Field in the Extract StructureTable of OriginField in the Table of Origin
CDNUMCustoms Document Number/SAPSLL/CUHDCORDER
CDYEACustoms Document Year/SAPSLL/CUHDCOYEAR
CDITNCustoms Document Item Number/SAPSLL/CUITITVSY
INDEIImport/Export Indicator/SAPSLL/CUHDINDEI
ROCANCELCancel FieldHard-codedHard-coded
CDSTAStatus of Customs Document/SAPSLL/CUHDSTAPROST
FCOTDFlag: Customs or Transit DocumentHard-codedHard-coded
FRELPFlag: Relevant for Preference ProcessingHard-codedHard-coded
PREFLFlag: Eligible for PreferenceHard-codedHard-coded
FRELRFlag: Relevant for RestitutionHard-codedHard-coded
CDDATCustoms Document Date/SAPSLL/CUHDDATSHPTS, PTCTS
EXDATExport Date/SAPSLL/CUHDDATEXPTS
CRDATCreated-On Date/SAPSLL/CUHDCRTSP
NSCTCNumbering Scheme for Tariff Code Number/SAPSLL/CTSNUMC, /SAPSLL/CTSNUMSTCTS
NUCTCCountry for Tariff Code Number/SAPSLL/CTSNUMCLAND1
NUMTCTariff Code Number/SAPSLL/CTSNUMC, /SAPSLL/CTSNUMEXSID
NSCCCNumbering Scheme for Commodity Code/SAPSLL/CTSNUMC, /SAPSLL/CTSNUMSTCTS
NUCCCCountry for Commodity Code/SAPSLL/CTSNUMCLAND1
NUMCCCommodity Code/SAPSLL/CTSNUMC, /SAPSLL/CTSNUMEXSID
NSCRCNumbering Scheme for Common Agricultural Policy (CAP) Numbers for Restitution Handling/SAPSLL/CTSNUMC, /SAPSLL/CTSNUMSTCTS
NUMRCCAP Numbers for Restitution/SAPSLL/CTSNUMEXSID
BOPNOBill of Product Number/SAPSLL/BOPHDBOPNPO
SECNCSecurity Number for Customs Processing and Transit Procedure/SAPSLL/LCLICEXTNO
SECNRSecurity Number for Restitution/SAPSLL/LCLICEXTNO
PRNUMProduct Number/SAPSLL/PRPRNUM
CTYDPCountry of Departure/SAPSLL/CUIT, /SAPSLL/CUHDCTYDP
CTYARCountry of Destination/SAPSLL/CUIT, /SAPSLL/CUHDCTYAR
CUCOOCountry of Origin/SAPSLL/CUITCUCOO
FTORGForeign Trade OrganizationBUT000PARTNER
LEGUNLegal Unit/SAPSLL/CORPARPARNO
PSENDSender/Exporter/SAPSLL/CORPARPARNO
VSENDSender/Exporter SAP R/3 Vendor (Import)/SAPSLL/PNTBPBPVSY
PRECPRecipient/Importer/SAPSLL/CORPARPARNO
CRECPRecipient/Importer SAP R/3 Customer (Export)/SAPSLL/PNTBPBPVSY
PDECLDeclarant/SAPSLL/CORPARPARNO
PDECSDeclarant (Substitute)/SAPSLL/CORPARPARNO
POENTOffice of Entry/SAPSLL/CORPARPARNO
PODESOffice of Destination/SAPSLL/CORPARPARNO
PODEPOffice of Departure/SAPSLL/CORPARPARNO
POEXIOffice of Exit/SAPSLL/CORPARPARNO
CCAFARequested Concession/SAPSLL/LEGCUSCCAFA
CUPROProcedure/SAPSLL/LEGCUSCUPRO
DCTYPDeclaration Type/SAPSLL/LEGACTDCTYP
CSSTACustoms Status of GoodsLEGCUSCSSTA
MTRDODomestic Mode of Transport/SAPSLL/LEGTPRMTRDO
MTBRCMode of Transport at the Border/SAPSLL/LEGTPRMTBRC
CUHDADocument Type of Customs Document/SAPSLL/CUHDCUHDA
CUITAItem Category of Customs Document/SAPSLL/CUITCUITA
LREGCLegal Regulation for Customs Processing/SAPSLL/LEGTPRLGREG
LREGPLegal Regulation for Preference ProcessingHard-codedLGREG
LREGRLegal Regulation for Preference Processing/SAPSLL/LEGCONLGREG
INCOTIncoterm 1/SAPSLL/CUHDINCOT
INCOLIncoterm 2/SAPSLL/CUHDINCOLO
EXARTCustoms Business Transaction Type/SAPSLL/LEGTPREXART
PYTYPPayment Method/SAPSLL/LEGTPRPYTYP
AUTNOAuthorization Number/SAPSLL/LCLICEXTNO
ADDD1Additional Data 1/SAPSLL/CUITADDDA1
ADDD2Additional Data 2/SAPSLL/CUITADDDA2
ADDD3Additional Data 3/SAPSLL/CUITADDDA3
NETVANet Price/Invoice Value/SAPSLL/LEGCULCAMNT_CUS
STAVAStatistical Value/SAPSLL/LEGCULCAMNT_CUS
CUSVACustoms Value/SAPSLL/LEGCULCAMNT_CUS
TCODUThird-Country Duty/SAPSLL/LEGCULCAMNT_CUS
PREDUPreferential Duty/SAPSLL/LEGCULCAMNT_CUS
PHPDUPharmaceutical Products Duty/SAPSLL/LEGCULCAMNT_CUS
SUSDUSuspension of Duty/SAPSLL/LEGCULCAMNT_CUS
ADUDUAnti-Dumping Duty/SAPSLL/LEGCULCAMNT_CUS
SUMDUTotal: Duties/SAPSLL/LEGCULCAMNT_CUS
CURCUCustoms Currency/SAPSLL/LEGCULCCUR_CUS
PRRVAComparison Value/SAPSLL/CUITEXPVAL_FLT
PRTVAThreshold Value/SAPSLL/CUITCPVAL_FLT
CURPRPreference Currency/SAPSLL/CUITPRCUR
RESVAExport Refund Amount for Restitution/SAPSLL/LEGCULCAMNT_CUS
CURRERestitution Currency/SAPSLL/LEGCULCCUR_CUS
QUANBQuantity in Base Unit of MeasureCalculatedHard-coded
QUAUBBase Unit of MeasureCalculatedHard-coded
QUANDQuantity in Document Unit of Measure/SAPSLL/CUITQUANT_FLT
QUAUDDocument Unit of Measure/SAPSLL/CUITQUAUM
WEIGRGross Weight/SAPSLL/CUITWEIGRO_FLT
WEINENet Weight/SAPSLL/CUITWEINET_FLT
WEIDIUnit of Weight/SAPSLL/CUITWEIDIM
NUMITNumber of Document ItemsCalculatedHard-coded
Extractor Logic

This DataSource has the following data flow: DataSource 0SLL_CD_1 → ODS Object 0SLL_DS01 → InfoCube 0SLL_C01. The extractor method is F1.

Planned Evolution


There are some changes in progress for some GTS queries according to the specifications in the link below


https://drive.google.com/a/solvay.com/folderview?id=0B2clPECaPXrkZkRqN3Y2QWlaTVE&usp=sharing_eid&ts=57209386


1) BW - GTS : Export Statistics (Core Query) - BW_QRY_MPR_GTS01_0004

2) BW - GTS : Import Statistics (Core Query) - BW_QRY_MPR_GTS01_0001

3) BW - GTS : Trade compliance follow-up (Core Query) - BW_QRY_MPR_GTS02_0001 

   This query will be splitted in 3 different ones:

⇨ SPL  - to be created

⇨ Embargo - BW_QRY_MPR_GTS02_0002 (in validation)

⇨ License - to be created


Aside from modifications in the queries (layout, filters, etc) some new developments are in progress:

  • Activation of datasource DTS_USERNAME_TEXT in PF1 (currently it's available in SF1) to get user name from PF1 too
  • Analysis to enhance field "Release Reason" in datasource DTS_GTS_CHANGEDOC_STATUS






  • No labels