Skip to main content

SAP Configuration and Setup

Library: Track & Trace Documentation Library
Document: SAP Configuration and Setup
Version: 1
Effective date: March 10, 2022

Contents​

1 Standard Description​

This document describes the process of SAP configuration and setup in the scope of the Market Implementation Procedure.

2 Document Objectives and Benefits​

2.1 Objectives​

The objectives of the document are:

  • Describe the process of SAP configuration and setup for the Sourcing factory
  • Describe the process of SAP configuration and setup for the Market entity

2.2 Benefits​

The document helps to identify steps to handle SAP configuration and setup process within the scope of the Market Implementation Procedure.

3 Definitions​

Abbreviation / termExplanation
SAPPrimary global Enterprise Resource Planning system used in JTI

Please refer to IT Glossary in the IT P&P portal for further definitions.

4 Roles & Responsibilities​

#ActivityGSC CPIT BTS TTGDC TTMarket / Factory
1Define and maintain standardARCI
2Apply the standardR/ARRR/I

Role indicators:

IndicatorMeaning
AAccountable
RResponsible
CConsulting
IInformed

5 SAP Configuration and Setup for Sourcing Factory​

The following SAP configuration and setup for sourcing factories are considered essential for a new market setup process.

5.1 Supplying Factory Setup​

  • Material master data for Product, BOM and T&T relevant components are maintained and have all necessary parameters for proper T&T production, for example, GTIN codes are maintained
  • GLA system is implemented for factory and SAP-GLA Production orders interface is implemented and executed by corresponding SAP system account for Factory GLA, which has necessary permissions

5.2 Distribution Process Setup for JTI SA (1799)​

It is assumed that Factory shipments will be realized as Option 1 shipments, i.e. shipments will be executed based on SAP Delivery documents, scanning messages will be executed by Factory WMS (Movilizer) with reference to SAP Delivery #, and Invoice and Payment messages will be generated by SAP, if it is required by regulation.

In case if shipments will be executed according to Option 2, delivery is executed based on local ERP/WMS system document.

  • Material Master data should be enhanced for JTI SA
  • Destination Economic operator and Facility are maintained in SAP as either JTI entity and Plant or as Sold-to / Ship-to Customer, depending of the process, and have all necessary parameters required by Market regulation, such as EOID and FID, GLN or SGLN
  • In case if supply process will be realized via T-plant, for example CHT1, it is necessary to:
    • Identify the corresponding storage location at this T-plant
    • Ensure that the storage location address is maintained
    • Make configuration to associate this plant and storage location with destination ship-to using parameter TPD2_DEL_TRLOC in table ZTCPO_GTT_CONFIG
  • In case if supply process will be realized via V-plant, no additional SAP T&T configuration is needed

6 SAP Configuration and Setup for Market Entity​

SAP configuration and setup for Sourcing factory and Supply processes are described in this chapter.

For Market sales, it is necessary to decide which shipment process will be applicable.

6.1 Option 1 Process​

It is based on SAP distribution and sales documents chains.

6.1.1 Delivery​

It is generated in SAP S/4 HANA system and used as base document for goods picking, shipment preparation and execution processes.

Delivery information is sent by SAP to Corporate Repository and available for further matching with scanning data for shipment message generation, for example, EDP (3.3) Dispatch Event according to EU TPD regulation.

Only T&T relevant deliveries are considered and reported to CR. Relevance criteria are:

  • JTI Entity code is defined as T&T relevant in SAP T&T configuration
  • T&T relevant material groups are stated in SAP T&T configuration—for example, Delivery must contain at least one SKU or SKR item to be considered T&T relevant
  • Source and Destination of shipment are analyzed to identify T&T relevance—for example, EU TPD regulation considers now only SKU or SKR products which are manufactured by factory within EU, Country of Origin criteria, or for EU, Prime Market criteria, relevance

6.1.2 Billing Document​

It is generated in SAP S/4 HANA system and sent to Corporate Repository as Invoice message, which is used by CR to generate corresponding Invoice to government system, for example, EIV (4.1) Message to report an invoice in context of EU TPD regulation.

Relevance criteria for invoices are mainly the same as for Deliveries, namely:

  • JTI Entity code should be T&T relevant
  • Material groups should be T&T relevant
  • JTI Selling entity and Sold-to should be T&T relevant

6.1.3 Payment Message​

It is generated by SAP S/4 to report information about incoming Payment or other activity which corresponds to a T&T relevant Invoice, for example, EPR (4.3) Payment record.

Payments are reported for EU and UK TPD only, and only when they are linked to corresponding T&T relevant invoices via Clearance.

6.2 Option 2 Process​

It is fully based on Market ERP/WMS distribution and sales documents chains; consequently, Market WMS/ERP system is fully responsible for proper messages generation.

7 Document Control​

7.1 Contact Person​

07/25: Questions and feedback regarding this standard should be submitted to George Postelnicu.

7.2 Revision History​

VersionEffective datePurpose of changeAuthor
1March 10, 2022First version of the documentVladislav Balabanov

8 References​

References will be provided here when necessary.