Product Assistance for SAP Corporate Serialization

PUBLIC

Product Assistance

Document Version: 1.0 – Final

Date: June 7, 2021

Product Assistance for SAP Corporate Serialization


Public

2

Document History

Document Version Date Comment

1.0 June 7, 2021 First version released


Public

3

Table of Contents

1 SAP CORPORATE SERIALIZATION .......................................................................................... 5 1.1 Product Information .................................................................................................................. 5 1.2 What Is SAP Corporate Serialization? ...................................................................................... 5 1.3 Implementation Considerations ................................................................................................ 6 1.4 Related Information................................................................................................................... 7 1.5 Glossary .................................................................................................................................... 7

2 SAP CORPORATE SERIALIZATION CORE COMPONENTS...................................................... 8 2.1 SAP Corporate Serialization Data Cockpit ............................................................................... 8

2.1.1 Data Cockpit Overview ............................................................................................... 8 2.1.2 Master Data .............................................................................................................. 13 2.1.3 Serial Number Management ..................................................................................... 36 2.1.4 Repository Browser ................................................................................................. 47

2.2 Object Tracing and Event Processing .................................................................................... 53 2.2.1 EPCIS Event Types and Features ............................................................................ 54 2.2.2 EPCIS Inbound Processing ...................................................................................... 55 2.2.3 Additional Business Steps....................................................................................... 57

2.3 AIF Error Handling and Alerting for SAP Corporate Serialization .......................................... 58 2.3.1 Customizing of AIF Error Handling and Alerting ..................................................... 58 2.3.2 Assign Users for Standard Alert Recipient Determination ...................................... 58 2.3.3 Usage of the AIF Interface Monitor .......................................................................... 59

3 SAP S/4HANA ADD-ON FOR SAP CORPORATE SERIALIZATION ......................................... 62 3.1 Master Data Maintenance and Integration .............................................................................. 63

3.1.1 Integrate Customers and Vendors as Business Partners ....................................... 63 3.1.2 Integrate Plants and Storage Locations as Locations............................................. 64 3.1.3 Enhancement of Material Maintenance .................................................................... 65

3.2 Transactional Data Integration ............................................................................................... 66 3.2.1 Integrate Production Orders, Process Orders, Purchase Order, Inbound Deliveries,

Outbound Deliveries and Return Deliveries ............................................................ 66 3.2.2 Batch Enhancements and Integration from SAP S/4HANA to SAP Corporate

Serialization ............................................................................................................. 68

4 SAP CORPORATE SERIALIZATION FIORI APPS ................................................................... 71 4.1 Display Serialized Objects ...................................................................................................... 71

4.1.1 Setup & Configuration ............................................................................................. 71 4.1.2 List Report................................................................................................................ 71 4.1.3 Object Page .............................................................................................................. 72


Public

4

Table of Figures

Figure 1: Capabilities of the Solution ........................................................................................................................ 6

Figure 2: High-Level Landscape .............................................................................................................................. 6

Figure 3: Main Tasks of SAP Corporate Serialization Data Cockpit ........................................................................... 9

Figure 4: Data Cockpit Screen Areas ..................................................................................................................... 10

Figure 5: Entity Screen Elements........................................................................................................................... 11

Figure 6:Capture EPCIS inbound processing ......................................................................................................... 55

Figure 7: Display Serialized Objects App – List Report ........................................................................................... 71


Public

5

1 SAP Corporate Serialization

1.1 Product Information

Product SAP Corporate Serialization

Release 1.0

Based On SAP S/4HANA Foundation 1909

User Assistance Published June 2021

1.2 What Is SAP Corporate Serialization?

SAP Corporate Serialization offers serialization, and tracking and tracing capabilities to support companies in tackling

counterfeit products in their supply chains.

While batch management and serial numbers have been used for many years, these have not been enough to

prevent counterfeiting. So, SAP Corporate Serialization enables you to issue unique identifiers for individual products

and provides interfaces to interact with scanners, readers, or apps. You can verify the identifiers and check the

authenticity of the products as they move within the supply chain, or when they are sold to a customer.

A critical aspect for establishing serialization within a company is integration into internal processes as well as

involving dedicated partners where suitable. Therefore, the focus of SAP Corporate Serialization is on automation to

minimize the overhead for establishing track and trace processes.

The following figure highlights the main capabilities of the solution:


Public

6

Figure 1: Capabilities of the Solution

1.3 Implementation Considerations

SAP Corporate Serialization is a standalone serialization repository based on the SAP S/4HANA Foundation running

on a separate server to keep the load produced by serialization and tracking off the core. It provides predefined

content and interfaces for SAP S/4HANA that can easily be enabled via business function for out of the box

integration of master and transactional data as well as warehouse processes.

For more information, see chapter SAP S/4HANA Add-on for SAP Corporate Serialization in this document.

Furthermore, it provides interfaces that can be used by any system to support serialization as well as track and trace

processes.

Figure 2: High-Level Landscape


Public

7

1.4 Related Information

For more information on how to install SAP Corporate Serialization, see the administration guide on the SAP Help

Portal at https://help.sap.com/cors.

For more information on how to configure SAP Corporate Serialization, see the configuration guide for SAP

Corporate Serialization on the SAP Help Portal at https://help.sap.com/cors.

1.5 Glossary

Term Abbreviation Definition

application identifier

AI

A prefix used in barcodes, EPC and RFID tags

that specifies the meaning and the format of the

data attributes.

Core Business Vocabulary

CBV

A set of guidelines that define vocabulary

elements for the EPCIS standard to ensure that all

parties exchanging EPCIS data have a common

understanding of the semantic meaning of that

data.

enterprise identifier

EID

A unique identifier of a specific type used for

encoding and decoding that can be assigned to

business partners.

enterprise identifier type

A type of identifier of a business partner used for

encoding and decoding.

external identifier

A unique identifier of a business partner, location

or product that identifies them in communication

with external parties or systems.

external identifier type

A type of identifier of a business partner, location

or product, such as GTIN or SGLN, that is used in

external communication.

issuing agency An organization responsible for assigning a

nonrepeatable identifier to an enterprise, for

example., Dun & Bradstreet's Data Universal

Numbering System.

https://help.sap.com/cors



Public

8

2 SAP Corporate Serialization Core Components

This chapter provides an overview of the core components of SAP Corporate Serialization.

2.1 SAP Corporate Serialization Data Cockpit

Getting to Know the Data Cockpit

The Corporate Serialization Data Cockpit lets you search, display, and manage all the relevant entities of Master

Data, Serial Number Management and Repository Browser. Using the Data Cockpit you can monitor and manage

all relevant data in a consistent and coherent user interface. You can manage your master data, generate and

exchange serial numbers and keep track of all serialized objects and associated events. Using the advanced context-

based navigation, you can easily navigate from one entity screen to a related entity screen on the cockpit.

To access the Data Cockpit use the SAP User Menu:

SAP User Menu Corporate Serialization Repository Data Management Corporate Serialization

Data Cockpit .

Alternatively use the transaction /CORS/COCKPIT.

2.1.1 Data Cockpit Overview

The following figure shows the main tasks that you can perform using the data cockpit. You can find more information

about the tasks in their respective chapters in this document.


Public

9

Figure 3: Main Tasks of SAP Corporate Serialization Data Cockpit

2.1.1.1 Data Cockpit Structure

This chapter explains the structure of the Corporate Serialization Data Cockpit.

2.1.1.1.1 Screen Areas of the Data Cockpit

The main areas of the Corporate Serialization Data Cockpit are the navigation tree and the entity screen.

Furthermore, there is an application toolbar at the top of the cockpit screen that provides general and supportive

functions.


Public

10

Figure 4: Data Cockpit Screen Areas

Navigation Tree

From the navigation tree on the left side of the cockpit, you can navigate to the different entity areas represented as

nodes.

Entity Screen

The entity screen is the central area of the cockpit. It lets you search, display and maintain all entities.

Application Toolbar

The application toolbar provides general functions in the data cockpit available for all entities, regardless of the node

selected in the navigation tree.

2.1.1.1.2 Screen Elements of the Entity Screen

The screen elements of the entity screen are divided into three areas as illustrated in the following figure.


Public

11

Figure 5: Entity Screen Elements

An entity screen can be divided into three sections – the selection pane, the results pane, and the details pane.

Selection Section

Using the selection options in this section, you can search and filter for entities of the currently selected entity type

from the navigation tree. It supports advanced features like variant management and visibility control of the selection

parameters. The selection screen is available in all entity screens of the navigation tree.

Results Section

The results section displays the results matching the search criteria in the selection screen upon execution of the

search. The result list is represented as a standard ALV list, supporting functions like create, sort, print, export and so

on. As the selection screen, the result list is available in all entity screens of the navigation tree. Depending on the

selected node, the result section provides additional context-dependent functions like creation of data, status change,

and so on.

Details Section

In this pane, you can see the details of the item selected in the results list. Apart from the Details and Administrative

tabs, this pane includes various related tabs. The tabs vary based on the entity you are working on. The related tabs

in each entity allow you to navigate to other related entities without going to the entity tree. For more detailed

information on each tab of the Details pane, see the individual entity topics.


Public

12

2.1.1.2 General Data Cockpit Functions

This chapter describes general, context-independent functions that are available in the Corporate Serialization Data

Cockpit.

2.1.1.2.1 Data Cockpit Application Toolbar

The Application Toolbar provides the following functions that are always available in the Data Cockpit:

• Show/Hide Tree

Use this button to toggle between showing or hiding the navigation tree on the left.

• Show/Hide Selection

Use this button to toggle between showing or hiding the selection area in the entity screen.

• User Selection

SAP Corporate Serialization supports variant management to facilitate searching and filtering for entities. Using

the button User Selection, you can choose a selection screen variant. A popup displays the context-dependent

selection screen variants of the cockpit that users have saved for every entity. In this popup, you can mark one

variant as the default. This means that when you select an entity in the navigation tree of the cockpit, the default

variant screen is directly displayed. You can also select one variant for the current session.

• Display Log

Use this button to display the application log. The log is displayed in a popup. It lists all messages that have been

issued by the backend system and logs the findings detected by the backend system or the solutions’ screens. It

shows the successfully executed actions or errors of the current session, if any.

• Display/Edit

Use this button to toggle between the display mode and the edit mode of the cockpit. By default, the cockpit is

opened in display mode. You need to switch to edit mode using this button to be able to change entities in the

Corporate Serialization Data Cockpit. You can only edit the attributes of one single entity at a time.

2.1.1.2.2 Search Data Using the Data Cockpit

The selection section is available for all entity screens of all nodes of the SAP Corporate Serialization Data Cockpit

and works similar in all the entity screens. It provides some predefined selection fields that can be used to filter and

search for data in the Data Cockpit. To execute a search, you can optionally provide some values in the selection

fields and press Search. The results are displayed in the results section.

To facilitate searching entities in the Data Cockpit, SAP Corporate Serialization provides the following additional

functions in the selection section:

• Search: Use this to search for all possible results based on the values specified in the selection parameters.

• Clear: Use this to clear the values from all the selection fields.


Public

13

• Save Variant: Corporate Serialization Data Cockpit supports variant-enabled search. Use this to save

parameter selections as a variant. This helps you to avoid recreating the selection variant every time you

use the cockpit. It also saves the currently visible fields of the selection screen, added or removed via the

options Add Selection and Delete Selection.

• Get Variant: Saved variants are available for selection in this catalog even after you exit and re-enter the

cockpit.

• Delete Variant: Use this to delete a saved variant.

• Add Selection: Use this to add more selection parameters to the selection section. Some parameters are not

displayed by default and can be added for a more advanced search.

• Delete Selection: Use this to remove selection parameters from the selection pane.

2.1.2 Master Data

2.1.2.1 Creating or Changing Master Data Entities

To change master data entities, choose the editing mode using the Display/Edit option on the menu bar in the

Corporate Serialization Data Cockpit

2.1.2.1.1 Create New Entity

To create a new entity object:

• Choose the Create button in the results pane. A new empty row is added to ALV grid, and relevant fields are

ready for input in the detail area.

• Enter the necessary data and choose Save to save the new entity.

Note

Depending on the currently selected node in the navigation tree, there are different mandatory attributes that

needs to be provided before you can save your new entity.

2.1.2.1.2 Change Attributes

To change an attribute:

• Select the attribute in the Details pane, while in the Edit Mode.

• Make the necessary modifications to the required attribute fields.

• Save the changes.


Public

14

2.1.2.1.3 Mass Change Status

To change the status:

• Select one or more rows while in the Edit Mode

• Select the status from the Change Status drop down list.

The following status transitions are possible:

From To

Created Active or Obsolete

Active Created or Obsolete

Obsolete Active or Created

2.1.2.1.4 Change Documents for Master Data Change Logging

Most attributes of all master data objects can be edited as long as they are in status Created or Active. Such

changes made to master data objects are logged using change documents, which you can see via the tab Change

Documents in the Details pane of the Data Cockpit.

When searching for master data objects, by default the current state of the object is displayed.

Via additional selection Display Local Date/Time Old State, a master data object can also be displayed for a past

date. Enter the date and time, and then the master data object is displayed in the state it had at that point of time.

On the tab Change Documents, those change documents that are not relevant to be displayed as part of the object's

old state (for the given date) are marked as Temporarily Revoked. When the master data objects are displayed for a

date in the past, they cannot be changed even if the cockpit is in Edit mode.

You also can use the feature Display Old State when navigating from transaction data to master data objects. For

example, when navigating from a serialized product (SGTIN) to the product (GTIN), the product is displayed

corresponding to the past date when the serialized product was created in the system.

Note

When an object is created in the system, the current valid state of the master data object is used to create

the transactional object.

The following specifics apply to master data change logging:

• Business Partners

o External Identifiers: Whenever the assignment of an external identifier (for example, SGLN) to the

business partner is changed, a change document is written. To enable performant navigation for

historical transaction data, historical external identifiers assignments are additionally stored in a

separate database table.

o Assigned Plants: The assignment of a business partner to a plant location is managed at the

location. Therefore, the corresponding change documents are visible via the location node only.

o Assigned Systems The assignment of a business partner to a system is managed in the system.

Therefore, the corresponding change documents are visible via the system node only. Furthermore,


Public

15

system assignments can only be displayed for the current state of the business partner. When you

select via a key date, no system assignments can be shown for the old state of the business partner. If

you want to verify whether a system has been assigned to a particular business partner in the past,

then, check the change documents of the system.

• Locations

o External Identifiers: Whenever the assignment of an external identifier (for example, SGLN) to the

location is changed, a change document is written. To enable performant navigation for historical

transaction data, historical external identifiers assignments are additionally stored in a separate

database table.

• Products

o Systems: The product to system assignment can be changed from both the system and the

product nodes. Each change is visible in the change documents of both the system and the product.

When displaying the old state of a product, only manually assigned systems are displayed.

2.1.2.2 Business Partner

Business Partners are any trading partners with whom traceability data is being exchanged, for example, a CMO

(contract manufacturing organization), CPO (contract packaging organization), wholesaler, Third-party Logistics

(3PL) company.

Business Partners in SAP Corporate Serialization can have multiple roles reflecting the different business processes

a partner participates in. In SAP S/4HANA, there are separate master data objects for these roles. For example,

there is a customer for sales processes and a vendor for purchasing processes although physically this is the same

organization having these roles with same physical attributes such as Global Location Number (GLN).

Activities

You can do the following from the results pane:

● Create a new business partner

● Assign a new business partner role

● Reassign business partner roles

● Delete business partner roles

● Maintain Enterprise IDs and serialization settings for business partners

● Maintain External IDs for business partners

● Check Business Partner Usage and Assignments

● Maintain Company Registrations

● Change the status of a business partner

Business partner hierarchy

A business partner can have a parent business partner, and with this a business partner hierarchy can be modeled.

The business partner hierarchy is not displayed as a hierarchy in the search result list of the Data Cockpit. If needed,

the parent business partner can be displayed in the list via the standard ALV option Change Layout.

A parent business partner can be set to status Obsolete only if all child business partners have status Obsolete as

well. It is not possible to integrate business partner hierarchies.

Integration of a Business Partner from SAP S/4HANA


Public

16

When a business partner is integrated to SAP Corporate Serialization, the system checks whether the business

partner already exists in this system. The system uses the GLN to check the existence of the business partner. If a

business partner is found with the same GLN, the system adds a new role to the existing business partner. If not, the

system creates a new business partner with a new role. However, every role can be assigned only once for a

business partner.

2.1.2.2.1 Create a New Business Partner

To create a new business partner, do the following

1. Choose Business Partner from the navigation tree.

2. Toggle the Display/Edit option on the application toolbar to activate the edit function.

3. Choose Create from the Results pane.

4. In the New Business Partner pane, enter the following details:

a. Business partner name

b. You can enter the following optional attributes:

i. Business partner category

ii. Parent business partner number

iii. Supply chain notification profile

iv. Address

5. Create the role assignments: See chapter Assign a new Business Partner Role /Create a Business

Partner Role:

6. You can add the additional details for your business partner. Your business partner may need different

types of identifiers

a. Set up enterprise ID. See chapter Assign an Enterprise Identifier to a Business Partner

b. Set up the external identifier. See chapter Maintaining External Identifiers and External

Identifier Types .

7. Save to create a new business partner.

2.1.2.2.2 Assign a New Business Partner Role

You can create and maintain business partner roles from the Details pane, via the tab Role Assignments.

When creating a business partner, you must assign at least one business partner role by providing the following:

1. External Business Partner Number: Identifies the role and typically reflects the externally known ID such as

the customer number or vendor number. One business partner role can have different externally known

identifiers in different source systems.

2. Business Partner Role Type: Describes the type of the business partner role (for example, vendor or

customer).

3. Business Partner Role Variant: If a business partner has different external identifiers (external business

partner number) for the same role, then, for every external identifier a new role variant is created. If, for

example, a business partner has three roles and per role it has two variants, then you will see six lines in the

table of Role Assignments for this business partner.


Public

17

Note A business partner that represents your own organization must be modeled as a business partner with own

organization as the role type

To assign a new business partner role to a business partner, do the following:

1. Select the business partner that you want to create the new role for.


3. In the Details pane, on the Role Assignments tab, enter the following business partner details:

a. Choose Create Role to define the kind of business partner you want to create.

b. Select the role type from the popup.

c. Enter the business partner number if you need to refer to it, for example in an EPCIS message or

in a read point or business location.

d. Save to assign the role to the business partner.

2.1.2.2.3 Reassign Business Partner Roles

You can also reassign business partner roles. For example, when you integrate business partners from an ERP system,

then to avoid grouping the roles wrongly, you can reassign roles without deleting them.

To reassign a role, do the following:

1. Select the business partner role to be reassigned and choose Reassign Role.

2. In the popup, select the target business partner and confirm.

2.1.2.2.4 Delete Business Partner Roles

To delete Business Partner Roles:

1. Select the business partner role that you want to delete from the list in the Details pane.

2. Choose 'Delete Role' from the Details pane.

3. Save to mark the role as deleted.

4. Deleted roles can be shown by selecting Include Deleted Roles as additional selection criteria.

Note

For each business partner there must be at least one role. This means you cannot delete the last remaining role

of a business partner at any time.


Public

18

2.1.2.2.5 Maintain Enterprise Identifiers and Serialization Settings for

Business Partners

2.1.2.2.5.1 Set Up Enterprise Identifiers

2.1.2.2.5.1.1 Enterprise Identifier Type

In the standard delivery of SAP Corporate Serialization, the following enterprise identifier types are available:

• CP GS1 Country Prefix

• DODAAC Department of Defense Act Address Code

• DUNS Data Universal Numbering System

• GCP GS1 Global Company Prefix

• NCAGE NATO Commercial and Gov Entry

You can add additional enterprise identifier types via Customizing Corporate Serialization → Master Data → Maintain

External Identifier Types or via transaction /CORS/C_EID.

An enterprise identifier type has the following attributes:

• Enterprise Identifier Type

• Enterprise Identifier Name

• Enterprise Identifier Group

You must assign an enterprise identifier group to your EID type. It is not possible to save an EID type without EID

type group assigned. The EID type group specifies the name of the group that is used to collect different enterprise

ID types together.

The grouped enterprise ID types are processed together via the same call of the BAdI implementation of BAdI

definition /CORS/BADI_EID_CHECKS. However, for EID type groups GCP and DUNS, there is no BAdI

implementation, but only the standard implementation.

2.1.2.2.5.1.2 Enterprise Identifier

An enterprise identifier (EID) is a unique identifier of a specific type used for encoding and decoding that can be

assigned to business partners.

An enterprise identifier must be assigned to an enterprise identifier type.


Public

19

Features

You can maintain enterprise identifiers under the node Enterprise IDs for a specific EID type in the customizing

activity Corporate Serialization → Master Data → Maintain External Identifier Types, or via transaction

/CORS/C_EID.

Download (Download List)

You can select and download all EIDs of the current EID type as a file. You can adapt this excel and use it for

uploading EIDs

The file has the following information separated by ";":

• EID Type

• EID

EIDs with leading zeros are also downloaded with leading zeros to the CSV file.

Note

Leading zeros are automatically deleted when the CSV file is processed by some spreadsheet processing

programs. In such case, the function Merge List, where the list is uploaded and merged to SAP Corporate

Serialization, will not be able to find the matching EIDs again. This can lead to inconsistencies.

You can also upload a list of EIDs from a file in the following ways:

Upload and Replace (Replace List)

When you upload a file using Replace List, all EIDs maintained for the current EID Type that are listed in the file are

uploaded to the system. All EIDs in the system for this EID type, that are not in the file, are deleted.

File entries with a nonexisting EID type are not uploaded.

Upload and Merge (Merge List)

When you upload a file using Merge List, all EIDs maintained for the current EID Type that are listed in the file are

uploaded into the system. If they already exist, the system will not create duplicates.

File entries with a nonexisting EID type are not uploaded.

Check (Check List)

You can check the EIDs using the EID type-specific check rules.

For EIDs of EID type groups GCP and DUNS, the check rules are already delivered with SAP Corporate Serialization.

The following criteria for new or updated EIDs of type group GCP are checked:

• The GCP must only consist of numeric characters.

• The number of characters must be less than or equal to 12.

• The number of characters must be greater than or equal to 6.

• There must not be any duplicates.

• There must not be a smaller GCP with the same pattern.

• There must not be a smaller country prefix with the same pattern.

There is a special check in place for any EID that is of pre-delivered EID type CP:

• Country Prefixes must only consist of numeric characters

• The number of characters must be less than or equal to 11

• The number of characters must be greater than or equal to 3


Public

20


• There must not be a smaller GCP with the same pattern.

• There must not be a smaller country prefix with the same pattern.

The following criteria for new or updated EIDs of type group DUNS are checked:

• The DUNS must only consist of numeric characters.

• The number of characters must be exactly 9.


For any other Enterprise ID Type Groups, the check can be implemented in the BAdI /CORS/BADI_EID_CHECKS of

the enhancement spot /CORS/ES_ID_CHECKS.

When saving the EIDs in the customizing activity, the check rules get executed. If there are errors, an error message

is displayed and the EIDs are not saved. To find the detailed messages in a log, the function Check List can be used.

The system provides a detailed list of the check results.

2.1.2.2.5.2 Assigning an Enterprise Identifier to a Business Partner

You can assign an enterprise identifier to a business partner in the Data Cockpit directly, even if the enterprise

identifier is not defined in Customizing. You can do this only when the enterprise identifier type is defined in the

Customizing. The Customizing is updated with the value of the new enterprise identifier if it does not already exist

there. The same checks are applied for the specific EID types as during the maintenance of enterprise identifiers in

the Customizing.

To assign an enterprise identifier to a business partner, do the following:

1. Select the business partner.


3. In the Details pane, on the Enterprise ID and Serialization Settings tab, enter the following details:

a. Select the enterprise identifier type.

b. Enter the enterprise identifier.

c. You can select the profile category to use the functionality Determine Profile.

d. Alternatively, you can select a suitable profile key from the value help in the field. Ensure that you

have already maintained the profile via Customizing Corporate Serialization → General Settings →

Maintain Serialization and Range Automation Profiles, or via transaction /CORS/C_SERPRFL.

e. Choose Assign Range Definition and confirm the details in the New Range Definition popup to

create the range definition.

4. Save to assign the enterprise identifier.

2.1.2.2.5.3 Determine Serialization Profile

Serialization profiles for enterprise identifiers can be determined automatically using Determine Profile. The

determination is done based on the serialization profile category. If no serialization profile category is assigned to EID,

this function is not possible. Also, if serialization profile category is not assigned to any serialization profile in

Customizing, the profile cannot be determined.


Public

21

If more than one serialization profile is found, the system chooses the profile with the highest priority of the serialization

profile category assignment. Alternatively, you can select the value directly in the field or by using the value help. The

field then displays all the serialization profiles relevant for the serialization profile category if it is provided. If no category

is provided, all serialization profiles available in the system are displayed via the value help.

2.1.2.2.5.4 Assign a Range Definition

After assigning an enterprise ID and a serialization profile to the Enterprise ID and Serialization Settings table of the

business partner, you can use Assign Range Definition to assign a range definition to the selected enterprise

identifier. This is to comply with the definition of uniqueness scope in the serialization profile. Based on the

uniqueness scope and the range definitions that already exist, the system determines if a new range definition must

be created, or if an existing one can be reused.

Alternatively, you can use the value help of this field, to choose the available range definitions complying with the

uniqueness scope of the serialization profile.

Note

When you assign a new range definition, you can overrule the logic that is defined by the uniqueness scope

of the serialization profile.

You can assign the same enterprise ID several times to business partners only if serial numbers of the range

definitions assigned to this enterprise ID have no overlaps. This is ensured by different lengths of these range

definitions. Empty range definitions are considered as well.

After the assignment of the range definition, the EID is ready for serial number management. If the serialization

profile used for creation of the range definition has a range automation profile assigned, then serial number entities

are automatically prepared for productive use. For more information, see Serial Number Management (especially

Serialization Profile) for more information. Enterprise identifiers without an assignment of range definition are not

relevant for serial number management. You can use such enterprise identifiers for data processing only.

2.1.2.2.6 Maintain External Identifiers for Business Partners

During event reporting and processing, business partners can be identified using external Identifiers that are

sent in the EPCIS XML messages. Therefore, it is recommended to assign an external identifier to every

business partner that is used to report events.

To maintain external identifiers for a business partner, execute the following steps in the Corporate Serialization

Data Cockpit:

1. Navigate to Business Partners in the navigation tree.

2. Search and select the business partner for which you would like to maintain an external identifier.

3. In the Details section, navigate to tab External Identifiers and use the Assign/Unassign buttons to manage

external identifiers.

4. Provide a Business Partner Identifier Type and a Business Partner Identifier and save.


Public

22

Note

The business partner identifier type should be maintained in the customizing transaction /CORS/C_EXTID_TYPE

before it can be used. In addition, the external identifier type must be active for business partner usage within the

same transaction. For more information, see the configuration guide for SAP Corporate Serialization on the SAP

Help Portal at https://help.sap.com/cors.

Hint

Depending on the selected external identifier type, some checks might be executed when providing an external

identifier number that are checking for correctness, consistency, and duplicates of the identifier. Depending on

the selected type, you need to make sure to provide a valid identifier number.

Business partner identifiers can be assigned to a business partner only for a certain period of time and can be

unassigned later. Therefore, in the External Identifiers tab of the business partner entity screen you can check the

historic identifiers using button Show Historic External IDs.

2.1.2.2.7 Check Business Partner Usage and Assignments

As business partners can be linked to other master data objects like locations and systems, the business partner

entity screen provides an overview of where the business partner is used, and to which other master data objects the

business partner is assigned.

To check the locations assigned to a business partner follow these steps in the Corporate Serialization Data Cockpit:

1. Choose Business Partners from the navigation tree.

2. Search and select the business partner for which you would like to check the assignments.

3. In the Details section, navigate to tab Assigned Locations to check the locations assigned to the business

partner. This is a display-only view of the assignments. To assign a location to a business partner, see

chapter Assign Location to Business Partner of this guide.

To check the systems assigned to a business partner follow these steps in Corporate Serialization Data Cockpit:


2. Search and select the business partner for which you would like to check the assignments.

3. In the Details section, navigate to tab Assigned Systems to check the locations assigned to the business

partner. This is a display-only view of the assignments. To assign a system to a business partner, see

chapter Assign System to Business Partner of this guide.

2.1.2.2.8 Maintain Company Registrations

You can assign and unassign registration IDs to your business partner via the Corporate Serialization Data Cockpit:

1. Navigate to Business Partners in the Navigation Tree



Public

23

2. Search and select the business partner for which you would like to maintain the registration IDs.

3. In the Details section, navigate to tab Company Registrations and use the Assign/Unassign buttons to

manage the company registrations.

4. Provide a Registration Type and a Registration Number as well as a validity period (Valid From, Time zone)

and save.

Note

The registration type should be maintained in the Customizing transaction /CORS/C_REGTYPE before it can be

used. For more information, see the configuration guide for SAP Corporate Serialization on the SAP Help Portal

at https://help.sap.com/corshttps://help.sap.com/cors.

2.1.2.2.9 Change the Status of a Business Partner

To change the status of a business partner, execute the following steps in the Corporate Serialization Data Cockpit:


2. Toggle the Display/Edit option on the application toolbar to switch to edit mode.

3. Search and select the business partner for which you want to change the status. Select the line in the results

section

4. Choose button Change Status in the results section and select one of the available statuses as the target

status.

Note

If you select multiple lines in the result list before executing the status change, the status is changed for all

selected lines, if the status transition is allowed for all selected business partners.

2.1.2.3 Location

You can use Locations to model physical locations that are used within your supply chain processes. In SAP

Corporate Serialization, a location typically represents a plant or a storage location, but it can also represent other

entities such as storage bins or resources. It is intended to be used for tracking the physical location of serialized

objects. A location can belong to a hierarchy, e. g. storage locations can be assigned as sub-entity to plants.

Using the Corporate Serialization Data Cockpit, you can manage your locations that can be used along the

processes.

Besides manual creation within SAP Corporate Serialization, plants and storage locations can be integrated from an

SAP S/4HANA system. For more information, please see chapter Integrate Plants and Storage Locations as

Locations in this document.




Public

24

Activities

You can do the following within the results section of the location entity

● Create a New Location

● Assign a Location to Business Partner

● Maintain External Identifiers

● Maintain Location Registrations

● Change the Status of a Location

2.1.2.3.1 Create a New Location

To create a new location, do the following in the Corporate Serialization Data Cockpit:

1. Choose Locations from the navigation tree.


3. Choose Create from the Results section.

4. In the New Location section, enter the following details:

a. Location Number

b. Location Name

5. Select a Location Type from the available types.

6. Optionally, you can provide a Parent Location Number to define that the location belongs to a location

hierarchy.

7. Optionally, you can provide additional attributes available in the Details section of the entity screen.

8. Press the Save button in the application toolbar to save the new location.

To be able to use the location along your track & trace processes, the following prerequisites need to be fulfilled:

• Assign an external identifier. For more information see chapter Maintain External Identifiers for Location.

• The location must be in status Active. For more information, see chapter Change the Status of a Location.

• Assign the location to a business partner. See chapter Assign Location to a Business Partner

2.1.2.3.2 Assign Location to Business Partner

It is recommended that you assign locations to business partners before using them in the track & trace processes.

By assigning the location to a business partner, you can control the ownership of a location:

• If you assign the location to an internal business partner (business partner with role type 5 – Own

Organization), the location is considered internal

• If you assign the location to an external business partner (business partner with role type other than 5 – Own

Organization), the location is considered external

This differentiation is crucial to record changes in ownership of serialized goods along your track & trace processes.

Furthermore, the differentiation is important for event reporting. Using the event location, you can differentiate, if an

event is reported internally or externally. Events reported by external locations do not impact the logistic status of an

object. In addition, you can decide on whether to block or admit certain events based on whether they are internal or


Public

25

external based on the location. For more information see the configuration guide on the SAP Help portal at


To assign a location to business partner, follow these steps in the Corporate Serialization Data Cockpit

1. Navigate to Locations in the Navigation Tree.

2. Search and select the location for which you would like to assign the business partner.

3. In the Details section provide the associated business partner ID in the field Location Business Partner No.

2.1.2.3.3 Maintain External Identifiers for Location

During event reporting and processing, locations are identified using external Identifiers that are sent in the

EPCIS XML messages. Therefore, it is recommended to assign an external Identifier to every location that is

used to report events. An external identifier must always uniquely identify a location within SAP Corporate

Serialization.

To maintain External Identifiers for a location, execute the following steps in the Corporate Serialization Data

Cockpit:

1. Navigate to Locations in the Navigation Tree

2. Search and select the location for which you would like to maintain an external identifier.

3. In the Details section, navigate to tab External Identifiers and use the Assign/Unassign buttons to manage

External Identifiers.

4. Provide a Location Identifier Type and a Location Identifier Number and save.

Note

The location external identifier type should be maintained in the customizing transaction

/CORS/C_EXTID_TYPE before it can be used. In addition, the external identifier type must be active for

location usage within the same transaction. For more information, see the configuration guide for SAP

Corporate Serialization on the SAP Help Portal at https://help.sap.com/cors.

Depending on the selected external identifier type, some identifier type-dependent checks are executed when

providing an external identifier number. Those are checking for correctness, consistency, and duplicates of the

identifier. Depending on the selected type, you need to make sure to provide a valid identifier number.

Example: If you select identifier type SGLN, you need to make sure to provide a valid SGLN according to the GS1

standard.

Location identifiers can be assigned to a location only for a certain period of time and can be unassigned later.

Therefore, in the External Identifiers tab of the location entity screen you can check the historic identifiers using

button Show Historic External IDs.




Public

26

2.1.2.3.4 Maintain Location Registrations

You can assign and unassign registration IDs to your location via the Corporate Serialization Data Cockpit

1. Navigate to Locations in the Navigation Tree

2. Search and select the location for which you would like to maintain the registration IDs.

3. In the Details section, navigate to tab Location Registrations and use the Assign/Unassign buttons to

manage the location registrations.

4. Provide a Registration Type and a Registration Number as well as a validity period (Valid From,

Timezone) and save.

Note

The registration type should be maintained in the Customizing transaction /CORS/C_REGTYPE before it can

be used. For more information, see the configuration guide for SAP Corporate Serialization on the SAP Help


Deletion of company registrations is only possible if the valid from date is in the future. In case the valid from date is

in the past then the entry cannot be deleted anymore. Instead you need to modify the valid to date.

The same registration number must be unique. The same registration number can only be reused by another location

in case the validity period is not overlapping.

2.1.2.3.5 Change the Status of a Location

To change the status of a location, execute the following steps in the Corporate Serialization Data Cockpit:

1. Choose Location from the navigation tree.


3. Search and select the location for which you want to change the status. Select the line in the

results section

4. Choose button Change Status in the results section and select one of the available statuses as the

target status.

Note

If you select multiple lines in the result list before executing the status change, the status will be changed for all

selected lines, if the status change is allowed for the specific status.

2.1.2.4 System

Systems entities are used for all communication with known external systems. Specifically, systems are used to

control the serial number exchange and distribution and hence play an important role in serial number management.

Systems are assigned to ranges and once assigned they can request either ranges or lists from that range. If the

system receives a serial number list, the system is stored at every serial number provided to the system to allow



Public

27

verification later when receiving a creating event for this serial number. As this verification is done at the business

partner level, it is mandatory for the systems used for serial number management to have a business partner

assigned. If the system receives a range, then the system is stored at the range request to verify during creating

objects whether the serial number received from the system is within a valid range request.

Note

Systems are only defined within SAP Corporate Serialization locally and are not integrated from SAP S/4HANA.

Note

Systems are not integrated from SAP S/4HANA, but are primarily defined within SAP Corporate Serialization

only.

Activities

You can perform the following actions in the results sections of the system entity:

• Create a new System

• Assign System to Business Partner

• Maintain System Communication Settings

• Control Serial Number Request Access Restrictions for Systems

• Change the Status of a System

2.1.2.4.1 Create a New System

To create a new system, do the following steps in the Corporate Serialization Data Cockpit:

1. Choose System from the navigation tree.


3. Choose Create from the results section.

4. In the New System section, enter the following details:

a. System Name

c. System Description

5. Select the System Type using the value help.

6. Assign a business partner. See chapter Assign System to Business Partner

7. Maintain serial number access for this system. See chapter Control Serial Number Request Access

Restrictions for System.

8. Maintain Communication Settings. See chapter Maintain System Communication Settings.

9. Use the Save button to create a new system.


Public

28

2.1.2.4.2 Assign System to Business Partner

It is recommended to assign systems to business partners before using them in the track & trace processes. By

assigning the system to a business partner, you can control the ownership of a system:

• If you assign the system to an internal business partner (business partner with role type 5 – Own

Organization), the system is considered internal

• If you assign the system to an external business partner (business partner with role type other than 5 – Own

Organization), the system is considered external

This differentiation is crucial to determine current ownership of serial numbers as soon as they are requested and

distributed. Upon commissioning of the serial numbers, it is checked if the serial numbers are used by the same

business partner who requested the serial numbers. Therefore, a business partner must be assigned to all systems

requesting serial numbers. If the business partner is not maintained, then commissioning of serialized products fails.

To assign a system to business partner, follow these steps in the Corporate Serialization Data Cockpit:

1. Navigate to Systems in the Navigation Tree

2. Search and select the system for which you would like to assign the business partner.

3. In the Details section provide the associated business partner ID in the field Business Partner of System

and press save to save the changes.

2.1.2.4.3 Maintain System Communication Settings

You can request serial numbers using various communication scenarios. Via the Corporate Serialization Data

Cockpit, you can control the way serial number are requested. The following communication scenarios are supported:

• Request Serial Numbers via synchronous RFC interface

• Request Serial Numbers via asynchronous RFC interface

• Request Serial Numbers via synchronous Web Service interface

• Request Serial Numbers via asynchronous Web Service interface

To maintain the system communication settings, do the following in the Corporate Serialization Data Cockpit:


2. Search and select the system for which you would like to maintain the communication settings.

3. Navigate to tab Communication Settings and maintain the settings according to your needs.

4. Choose the following:

a. Communication Type = 1 for RFC communication

If you select RFC communication, provide a Logical System connected to an RFC destination in

table TBLSYSDEST.

b. Communication Type = 2 for Web Service communication

If you select Web Service communication, provide a Logical Port Name of the service consumer

/CORS/CO_SNR_REQUEST maintained in transaction SOAMANAGER.

5. Using attribute Communication Mode below Serial Number Request Settings you can choose between 1 -

Synchronous and 2 - Asynchronous communication. This parameter is only taken into account if not

defined within the context.


Public

29

6. Provide an External System Name which represents the name of the serial number requestor system in

the serial number provider system. It is used in the sending a response to the correct destination

For more information on how to configure the RFC destination and Web Services, see the configuration guide on the

SAP Help Portal at https://help.sap.com/cors.

2.1.2.4.4 Control Serial Number Request Access Restrictions for

System

For each single system you can control if and to what extend a system can request serial numbers from the SAP

Corporate Serialization System on a granular level. Using the Serial Number Request Parameters, you can control if

a system can request serial numbers for enterprise identifiers and products and can also specify the amount of

numbers that can be requested at a time.

Those parameters can be accessed the following way:


2. Search and select the system for which you would like to maintain the communication settings.

3. In the Details section you can maintain the Serial Number Request Parameters.

The parameters control the following functionalities:

• Allow Serial Number Request for All Products:

Selecting this check box indicates that the system is allowed to request serial numbers for all products.

Alternatively, instead of selecting this check box, the allowed products can be explicitly added on tab

Allowed Products and then the system is only entitled to request serial numbers for all explicitly added

products.

• Allow SSCC Range Request:

Selecting this check box indicates that the system is allowed to request serial numbers for SSCCs

• Maximum Serial Numbers per Request:

You can define the maximum number of serial numbers that this system receives per request. If the system

requests more than the number specified here, then the returned number is reduced to the maximum

number.

• Default Outstanding Numbers:

With defining outstanding numbers you can limit the total outstanding serial numbers a system can request.

outstanding numbers are the serial numbers requested by a requesting system for a particular product or

enterprise identifier which are not reported back as commissioned or lost.

Default outstanding numbers define the maximum outstanding numbers that will be taken as a default for

this system. So, this system in total may not have more outstanding serial numbers for a particular product

or enterprise identifier than defined by this setting. If with a serial number request, the maximum outstanding

number is reached, the requested quantity is reduced in a way that the maximum outstanding numbers is

not exceeded in total.

For products, the maximum outstanding numbers can be defined at a more granular level per product on the

tab Allowed Products. If no outstanding numbers are defined, then the system may request infinite amount

of serial numbers.



Public

30

Using the Serial Number Request Parameters described above, you can control the access on system level. For

serial number request for products you can control the access on a more granular level as follows:


2. Search and select the system for which you would like to maintain the control the serial number request.

3. Navigate to tab Allowed Products and maintain the list of products for which the system is allowed to

request serial numbers. the settings according to your needs. Provide Product Identifier Type and Product

Identifier Number and press save.

Note

The maintenance of Allowed Products is only required if you have not selected the check box Allow Serial

Number Request for all Products in the tab Details.

In addition, for each product you can define the maximum outstanding numbers that this system can have for a

particular product. If not defined here the default outstanding numbers defined on the tab Details will be taken for

this product.

2.1.2.4.5 Change the Status of a System

To change the status of a system, execute the following steps in the Corporate Serialization Data Cockpit:

1. Choose System from the navigation tree.


3. Search and select the system for which you want to change the status. Select the line in the results section.


status.

Note

If you select multiple lines in the result list before executing the status change, the status will be changed for all

selected lines, if the status change is allowed for the specific status.

2.1.2.5 Product

A product stores all common master data of serialized products that are handled in supply chain processing. In SAP

Corporate Serialization serial numbers can be generated and exchanged for products. A product is identified by a

combination of product external identifier type and product external identifier number.

Products are typically integrated from SAP S/4HANA materials, but they can also be maintained locally in the SAP

Corporate Serialization system and one can also integrate products from other non-SAP ERP systems.

Activities

You can perform the following actions in the results pane:

● Create a new Product


Public

31

● Maintain Product Variant Data

● Maintain Product Serialization Settings & Assign Range Definition

● Maintain Usage and Assignments for Products

● Maintain Additional Product Attributes

● Maintain Additional Product Texts

● Change the status of a Product

2.1.2.5.1 Create a new Product

To create a new product, do the following in the Corporate Serialization Data Cockpit:

1. Choose Product from the navigation tree.


3. Choose Create from the results section.

4. In the New Product section, enter the following details, select a Product Identifier Type, provide an

appropriate and valid Product Identifier Number and a Product Description.

The product identifier type determines how the product is identified usually represented by a standard (for

example, GS1 GTIN, GSMA TAC/IMEI). However, also customer specific identifier types are supported.

Usually the product identifier is used in combination with the respective serialization settings of the product

to generate serial numbers for the specific product. For example, the GTIN is used with respective

serialization settings to compose an SGTIN according to GS1 standard.

An external identifier must always uniquely identify a product within SAP Corporate Serialization and is not

editable, once the product is created.

Note

Please note that the product identifier type should be maintained in the customizing transaction

/CORS/C_EXTID_TYPE before it can be used. In addition, the external identifier type must be active for

product usage within the same transaction. For more information, see the configuration guide for SAP

Corporate Serialization on the SAP Help Portal at https://help.sap.com/cors

Depending on the selected product identifier type, some identifier type dependent checks are executed

when providing a product identifier number. Those are checking for correctness, consistency and duplicates

of the identifier. Depending on the selected type, you need to make sure to provide a valid identifier

number.

Example: If you select identifier type GTIN, you need to make sure to provide a valid GTIN according to the

GS1 standard.

5. Select the Serialization Type from the value help. The following values are available

o 0 - Not Serialized: The product is not relevant for serialization. No events to be received or

composed for such products

o 1 - Lot Managed: The product is subject to lot level tracking. Only event messages for lots are

considered for such products.

o 2 – Serialized (Publishing only): The product is serialized. The commissioning is posted to a

repository and, eventually, regulatory reporting is triggered for commissioning if relevant. No

further events are recorded and stored in the repository.



Public

32

o 3 - Serialized & Traced: The product is serialized, and all received events are recorded and stored

in the repository.

6. Enter a new or select existing Product Category from the value help.

7. If the product is serialized externally (i.e. not using serial number management capabilities of SAP

Corporate Serialization, select the checkbox Serial Number Management Not Used as needed. In all other

cases, you need to provide the Serialization Settings for this attribute in tab Assigned Range Definitions.

See chapter Maintain Product Serialization Settings & Assign Range Definition.

8. Provide a Unit of Measure

9. Enter the product variant data. See chapter Maintain Product Variant Data.

10. Press save to create and save the newly created product within SAP Corporate Serialization.

Optional Activities

• You can maintain location and system assignments. See chapter Maintain Usage and Assignments for

Products.

• You can maintain additional product attributes. See chapter Maintain Additional Product Attributes.

• You can maintain additional product texts. See chapter Maintain Additional Product Texts.

2.1.2.5.2 Maintain Product Variant Data

As business users typically know the material number from the SAP S/4HANA system better than any external

identifiers like the GTIN, SAP Corporate Serialization additionally stores such common identifiers as product variant

data. One product can have multiple product variants. The purpose of supporting such variants is that the source

systems might have different identifiers for the same product (for example, various material numbers for the same

GTIN) in different system. SAP Corporate Serialization tries to harmonize this in one common master data objects

and providing variants that are linked to that main object.

Example

A GTIN may be assigned to two different materials in two different ERP systems, but still represent the same

trade item. Whenever such a case happens and the same GTIN is integrated with another material

reference, then a new product variant is created. So, the product variant carries a different alternative

material assignment for the same product (GTIN).

With this approach, users can search and display products for their externally known material numbers. The material

assignment is only used for this purpose. SAP Corporate Serialization solely use the product identifier types and

product identifier numbers to identify products internally.

Each product must have at least one variant.

To maintain product variants manually, follow these steps in the Corporate Serialization Data Cockpit:

1. Choose Product from the navigation tree.


3. Search and select the product for which you would like to check the assignments.


Public

33

4. In the Details section, navigate to tab Variant Data and use button Create Variant to create a new product

variant.

You can use the Discard New Variant button only to delete a newly created variant, that is not saved in the data

base.

2.1.2.5.3 Maintain Product Serialization Settings & Assign Range

Definition to Product

To enable serial number management for a product, the serialization settings need to be maintained in the product

master data and a range definition must be assigned. Therefore, at least one range definition must be assigned to a

product when serial numbers should be managed within SAP Corporate Serialization.

Note

This is only applicable if the flag Serial Number Management Not Used is not set in the Details tab of the Product

entity screen.

A range definition is a set of master data that defines the metadata (format, length, number ranges, and so on) of the

serial numbers.

For further information on range definitions, ranges and serial number management, see chapter Serial Number

Management.

To maintain range definitions assigned to a product, do the following in the Corporate Serialization Data Cockpit:

1. Choose Products from the navigation tree.

2. Search and select the product that you want to assign the Range Definition for.


4. Navigate to tab Assigned Range Definitions and use the Assign/Unassign buttons to assign/unassign Range

Definitions to/from the product.

To assign a new Range Definition in a guided approach, follow these steps in tab Assigned Range Definitions.

1. Select a Serialization Profile Category using the value help. This category is used to determine the right

Serialization Profile that is applicable

2. Decide whether the serial numbers are centrally managed internally or externally

a. Select I as Product Serial Number Management Type if the serial numbers are managed by the

SAP Corporate Serialization instance

b. Select E as Product Serial Number Management Type if the serial numbers are managed externally

by another system or SAP Corporate Serialization system. If serial numbers are managed by another

system you need to provide the Business Partner to Provide Serial No. Provide the business partner

number is responsible for the serial number generation and distribution.

3. Select the new line and press Determine Profile to determine the Serialization Profile. The system will try to

find an appropriate Serialization Profile. For more information see chapter Serialization Profile.

a. If no Serialization Profile was found you need to create an appropriate Serialization Profile and assign

the same Serialization Profile Category using transaction /CORS/C_SERPRFL. For more information

see chapter Serialization Profile.


Public

34

b. In case exactly one Serialization Profile was found, the Serialization Profile will be entered in the field

Serialization Profile.

c. In case more than one Serialization Profile is found, the system chooses the profile with the higher

priority of the category assignment maintained in the Serialization Profile Configuration. Alternatively,

you can select one of the available Serialization Profile using the value help.

4. Select the new line again and press Assign Range Definition. Based on the uniqueness scope of the

Serialization Profile, the system determines whether a new Range Definition has to be created or an existing

one can be reused.

a. If a suitable Range Definition already exists, it is assigned in field Range Definition of the currently

selected line.

b. If no suitable range definition exists, a popup appears to create a new range definition. Check the

serialization attributes of the Range Definition to be created and confirm the creation. The newly

created Range Definition will be assigned in field Range Definition of the currently selected line.

5. Save your changes.

After the assignment of the Range Definition, the product is ready for serial number management. Serial numbers for

this product can be generated and exchanged. For further prerequisites and information on serial numbers see chapter

Serial Number Management.

2.1.2.5.4 Maintain Usage and Assignments of Product

As products can be linked to other master data objects like locations and systems, the product’s entity screen

provides an overview of where the product is used, respectively to which other master data objects the product is

assigned to. You can also assign new locations and systems from the product’s entity screen.

To check and maintain the locations assigned to a product follow these steps in the Corporate Serialization Data

Cockpit:



3. In the Details section, navigate to tab Assigned Locations to check the locations assigned to the business

partner.

4. If you want to maintain the assignments, use the Display/Edit button to switch to edit mode and use the

Assign/Unassign buttons to assign/unassign locations to/from the product.

To check and maintain the systems assigned to a product follow these steps in the Corporate Serialization Data

Cockpit:



3. In the Details section, navigate to tab Assigned Systems to check the locations assigned to the business

partner.

4. If you want to maintain the assignments, use the Display/Edit button to switch to edit mode and use the

Assign/Unassign buttons to assign/unassign systems to/from the product.

Only systems that are included in the list will be able to request serial numbers for the product.


Public

35

2.1.2.5.5 Maintain Additional Product Attributes

SAP Corporate Serialization provides the capability to maintain a list of additional attributes on each product that will

be linked to the product master data object. It can be used generically to define some characteristics, thresholds, and

so on. To maintain additional product attributes, execute the following steps in the Corporate Serialization Data

Cockpit:



3. Search and select the product for which you want to change the status. Select the line in the results section

4. Navigate to the tab Additional Attributes and use buttons Assign/Unassign to maintain additional texts.

5. Provide a Property Name and Generic Property Value and save.

Note

The property name must be maintained as product property in the customizing transaction

/CORS/C_PROPNAME before it can be used. Please refer to the Configuration Guide on the SAP Help


2.1.2.5.6 Maintain Additional Product Texts

SAP Corporate Serialization provides the capability to maintain several language-dependent descriptions and texts

on a product. To maintain the texts of a product, execute the following steps in the Corporate Serialization Data

Cockpit:




4. Navigate to the tab Texts and use buttons Assign/Unassign to maintain additional texts.

5. Provide a Text Type, Language and Product Text and save.

Note

The product text type should be maintained in the Customizing transaction /CORS/C_TEXT_TYPE before it

can be used. Please refer to the Configuration Guide on the SAP Help Portal at https://help.sap.com/cors.

2.1.2.5.7 Change the Status of a Product

To change the status of a product, execute the following steps in the Corporate Serialization Data Cockpit:





status.




Public

36

Note

If you select multiple lines in the result list before executing the status change, the status will be changed for

all selected lines, if the status change is allowed for the specific status.

2.1.3 Serial Number Management

2.1.3.1 Range Definitions

A range definition covers the potentially available number space that can be used for serial number management.

Besides the ID and the version, the range definition contains the attributes from the serialization profile, a status,

certain statistical attributes, and the expiry date. When you create a serial number range definition, the system

copies all relevant parameters of the serialization profile into the range definition. Hence, the serialization profile is

relevant only until the range definition is created.

The range definition allows multiple versions to allow the reuse of the contained serial numbers after a defined period

of time the range definition version is deactivated. This is possible by specifying the reuse horizon in the serialization

profile. For more information, see Reuse Serial Numbers.

Activities


• Create a New Range Definition

• Create a New Range Definition Version

• Delete a Range Definition Version

• Change the Status of a Range Definition Version

• Reset the alert status of a Range Definition Version

• Display Range Definition Statistics

• Maintain Range Definition Automation Settings

• Maintain Ranges for Range Definition

• Check Range Definition Usage and Assignments

• Reuse Serial Numbers

2.1.3.1.1 Create a New Range Definition

To create a new range definition, do the following steps:

1. Choose Range Definitions from the navigation tree.




Public

37

4. In the popup New Range Definition, enter the range Definition Name

5. Select the Serialization Profile Key to get defaults for the Serialization attributes

6. Enter the details for serialization attributes

• From the serialization Profile (For more information, see chapter Serialization Profile)

o Serial Number Type

o Serial No. Excluded Characters

o Serial Number Length

o Serial No. Randomization Mode

o Serial Number Uniqueness Scope

• In case you need 2 range definition versions set the Reuse Horizon for Serial Number in Years to a

value not zero

7. Enter the details for Range Definition origin.

8. Choose Confirm and a new Range Definition Version get created.

9. Choose Change Status to activate the Range Definition Version.

10. Assign the Range Definition to your master data object.

• For more information about specifics for Ranges with origin External, see chapters Assigning an

Enterprise Identifier to a Business Partner and Maintain Product Serialization Settings & Assign Range

Definition to Product.

• Ranges and Serial numbers, which are imported through a serial number request, carry an Enterprise

ID or product designation. They can only be used for the assigned Enterprise ID or product, also when

the range definition addresses multiple Enterprise IDs or products.

2.1.3.1.2 Create a New Range Definition Version

To create a new range definition version, do the following steps:

1. At the save of a New Range definition automatically a Range definition Version get created.

2. In case you need more the one range definition versions, the serialization attribute Reuse Horizon for Serial

Number in Years of the Range definition should be set to a value not zero.


4. Select the Range Definition version you want to create an additional Version for.

5. The selected Range Definition Version and all other Versions of the same Range Definition should have the

status active.


7. Choose Create Version from the Results pane.

A new Range Definition Version get created.

2.1.3.1.3 Delete a Range Definition Version

To delete a range definition version, do the following steps:


Public

38


2. Select the Range Definition Version you what to delete.

3. Only Range definition Versions in Status Created can be deleted. Range definition Versions in status Active

can be set to status Created.


5. Choose Delete Version from the results pane

6. Confirm the deletion in the popup

2.1.3.1.4 Change the Status of a Range Definition Version

To change the status of a range definition version, do the following steps:


2. Select the Range Definition Versions you what to change the status. Multiple selection is possible.


4. Choose Change Status from the results pane.

5. Select the new status from the drop-down list.

2.1.3.1.5 Reset the Alert Status of a Range Definition Version

To reset the alert status of a range definition version, do the following steps:


2. Select the Range Definition Versions you what to reset the alert status. Multiple selection is possible.


4. Choose Reset Alert from the results pane

2.1.3.1.6 Display Range Definition Statistics

To display the Range Definition Statistics, do the following steps:


2. Select the Range Definition Versions you what to display the Range definition Statistics. Only active ranges

are considered by the selection.

3. Choose Range Definition Statistics from the results pane

4. The serial number statistics of the selected range definition version get displayed.


Public

39

2.1.3.1.7 Maintain Range Definition Automation Settings

To maintain the Range Definition Automation Settings, do the following


2. Select the Range Definition Versions you what to maintain change the Range Definition Automation

Settings.


4. Choose the Detail Tab

5. Maintain the Range Definition Automation Settings:

• Number of Characters for Auto Range

• Range. Expiry. in Months

• Default Alert Fill Level

• Default Threshold

• Default Lot Size

2.1.3.1.8 Maintain Ranges for Range Definition

To maintain the Ranges for Range Definition, do the following


2. Select the Range Definition Versions you what to maintain the Ranged.


4. Choose the Ranges Tab

5. Create new Ranges, see chapter Create a new Range

6. or Delete existing Ranges, see chapter Delete a Range

2.1.3.1.9 Check Range Definition Usage and Assignments

To Check the Range Definition Usage and Assignments, do the following


2. Select the Range Definition Versions you what to check the Range Definition Usage and Assignments

3. Choose the Product Assignments or the Business Partner EID Assignment Tab

4. Create new Ranges, see chapter Create a new Range

5. or Delete existing Ranges, see chapter Delete a Range

2.1.3.1.10 Reuse Serial Numbers

Serial numbers assigned to a range definition can be reused once the range definition passes the expiry date

specified in the reuse horizon. This attribute defines after how many years a range definition version (and the serial


Public

40

numbers that it comprises of) can be reused again. If you want to restrict reuse of serial numbers, then you can set

the reuse horizon value to 0. Thus, the range definition will have only one version which never expires (for example,

expiry date 31.12.2099).

Furthermore, this attribute defines the number of range definition versions that will be created. The number of the

version is always equal to the value in the reuse horizon field +1).

Process

• Initial creation of first version

o When you create a range definition, the first version is created which only covers a part of the

overall space (space divided by number of range definition versions). With the creation of a range

definition version, the expiry date is set to today + 1 year. While in status Version created, the

expiry date is given only as information.

• Activation of version

o At activation of the version, the expiry date is updated again with today + 1 year and this date now

defines the expiration date of the active usage of the range definition version.

• Close to expiry of active usage

o Once an active version passes the expiry date, this version shall not be used actively anymore, and

the version shall be set to status version closed soon. To determine range definitions that are close

to expiry date and set an alert status, you can schedule the report Check and Set Alert Status to

run regularly. You can use this alert status to select the range definitions which require action.

• Creation of subsequent versions

o As soon as a range definition version is nearing its expiry date, a new version needs to be created

which covers the next portion of the overall space and which will become the next active version.

You can activate this second version while the first version is still active to allow a seamless

changeover between versions. The expiry date now denotes the expiry of the retention period of

the serial numbers.

Note

A maximum of two versions can be active in parallel.

• Setting version to closed

o When setting the status to version closed, the expiry date is recalculated and updated with 'today +

reuse horizon'. The expiry date now denotes the expiry of the retention period of the serial

numbers.

• Reuse version

o When the serial numbers have passed the expiry date of the retention period, a new range

definition version can be created covering the space of the initial range definition and you can

reuse the serial numbers.


Public

41

2.1.3.2 Ranges

Serial number ranges segment the overall available numbers into smaller sets within a range definition version.

When you create a range definition version, there is always one initial range created that covers the full space of the

range definition version. Depending on the business context, you can further divide the ranges.

Activities


● Create a new Range

● Delete a Range

● Change the Status of a Range

● Generate Serial Numbers

● Request a Range

● Request Serial Numbers

● Reset Alert

● Navigate to Range Definition

● Automate Serial Number Generation

2.1.3.2.1 Create a New Range

To create a new Range, do the following steps:

1. Choose Ranges from the navigation tree.



4. In the popup New Range, enter the Range Definition and the Range Definition Version you want to create

the range

5. Define the type on how to create the range

• with Serial number prefix

• with Serial number from & quantity

• with Serial number from and to

6. Confirm the Popup to create the Range

7. The new Range get created. Already existing Ranges for the same Range Definition Version get adjusted.

2.1.3.2.2 Delete a Range

To delete a Range, do the following steps:



3. Mark the range you what to delete

4. Choose Delete from the Results pane.

5. The marked Range get deleted. Existing Ranges for the same Range Definition Version get adjusted.


Public

42

2.1.3.2.3 Change the Status of a Range

To change the status of a Range, do the following steps:



3. Mark the range you what to change the status. Multiple selection is possible.



Note

If open serial numbers or requests exist, a range cannot be closed normally. Then you need to choose Force

close. A forced closing sets the status of all open serial numbers to lost. Any potentially issued serial numbers

are not allowed to be commissioned any longer after that.

2.1.3.2.4 Generate Serial Numbers

To generate serial numbers for a Range, do the following steps:



3. Mark the range you what to generate serial numbers. Only relevant for range types list managed or range &

list managed.

4. In the popup Generate Numbers, you may specify a product external ID when generating serial numbers.

Then the generated serial numbers will only be usable for that specific product. If you do not specify a

product, the serial number is available for requests against any product or EID that has the same range

definition assigned – the actual assignment to the product or EID will be made at time of the serial number

request.

5. Confirm the Popup to generate the serial numbers

You can request serial numbers using various communication scenarios. See Chapter Maintain System

Communication Settings.

2.1.3.2.5 Request a Range

Range request can only be executed for the following ranges:

• Only relevant for range type range managed.

• Only relevant for Range Definition Origin Indicator external.

To request a Range, do the following steps:



3. Mark the range you what to request serial numbers.


Public

43

4. In the popup Request Range, you can request a range from the external system that owns the serial

numbers. Upon receiving the range, it is entered as a new range in status created. Now the new range can

be used just like an own range. It can be split. Once activated, serial number requesting systems can

request serial numbers from this range and use them for example, for manufacturing. The action is only

relevant if the range definition origin is external and range type is range managed.

5. Confirm the Popup to generate the serial numbers.

2.1.3.2.6 Request Serial Numbers

Serial Number request can only be executed for the following ranges:

• Only relevant for range types list managed.

• Only relevant for Range Definition Origin Indicator external.

To request Serial Numbers, do the following steps:



3. Mark the range you what to request serial numbers.

4. In the popup Request Serial Numbers, you can request a serial number list from the external system that

owns the serial numbers. Upon receiving the list, the serial numbers are imported as individual serial

numbers in status created. Subsequently systems linked to the serial number providing systems can request

these serial numbers and use them for example, for manufacturing. The action is only relevant in case of

range definition origin external and range type list managed. A request of serial numbers from another

system always requires that an External ID or Enterprise ID is specified.

2.1.3.2.7 Reset Alert Status

To reset the alert status of a range, do the following steps:



3. Mark the ranges you what to reset the alert status. Multiple selections are possible.

4. Choose Reset Alert from the results pane

2.1.3.2.8 Navigate to Range Definition

To navigate from a Range to the corresponding range definition version, do the following steps:


2. Mark the range you what to navigate from

3. Choose Display Range Definition from the results pane

4. The related range definition version gets displayed


Public

44

2.1.3.2.9 Automate Serial Number Generation

To automate generating serial numbers, do the following steps:


2. Mark the range for which you want to maintain the Automate Serial Number Generation settings

3. Check the Serial number & Range usage

4. Choose the Detail Tab

5. The setting for the automatic serial number generation are in the section Serial Number Generation and

Request Parameters.

• Serial Number Threshold specifies the threshold for numbers that are always available for list

requests.

• Lot Size for Serial Number defines the quantity of serial numbers that will be generated when

there is a request for the generation of serial numbers.

2.1.3.3 Range Request

Whenever a serial number requestor system sends a request for a serial number range, it is reflected in the serial

number management as a range request. The range request entity documents every request from a requestor

system.

Activities


• Create a new Range Request

• Change the Status of a Range Request

• Navigate to related Range Definition

• Navigate to related Range

2.1.3.3.1 Create a New Range Request

This option shall be used in exceptional scenarios to create a range request on behalf of another system, when the

consumer system is unable to implement the service to request serial numbers. When executing the action, you must

specify the quantity of serial numbers, the requesting system, and the External ID or Enterprise ID.

To create a Range Request, do the following steps:

1. Choose Ranges Requests from the navigation tree.


3. Choose Create Range Request from the Results pane.

4. In the popup New Range Request, enter the Number of requested Serial numbers, the requesting System

and the Product ID Type and number or the Enterprise ID Type and Number


Public

45

2.1.3.3.2 Change the Status of a Range Request

To change the status of a range request, do the following steps:

1. Choose Ranges Requests from the navigation tree.


3. Mark the Range Request you want to change the status

4. Choose Change Status from the Results pane.


2.1.3.3.3 Navigate to Related Range Definition

To navigate from a Range request to the related Range Definition Version, do the following steps:

1. Choose Range Requests from the navigation tree.

2. Mark the range request you what to navigate from


4. The related range definition version gets displayed.

2.1.3.3.4 Navigate to Related Range

To navigate from a Range request to the Range, do the following steps:

1. Choose Range Requests from the navigation tree.

2. Mark the range request you what to navigate from

3. Choose Display Range from the results pane

4. The related range get displayed.

2.1.3.4 Serial Numbers

Ranges of type List Managed and Range and List Managed can hold serial numbers. Every serial number created is

unique and can be followed individually throughout its lifecycle. The serial number status specifies the current phase

of the serial number in its lifecycle.

Activities


• Create a Serial Number Request

• Report lost Serial Numbers

• Navigate to related Range Definition

• Navigate to related Range


Public

46

2.1.3.4.1 Create a Serial Number Request

This option shall be used in exceptional scenarios only, when the consumer system is unable to implement the

service required to generate serial numbers. When executing the action you have to specify the quantity of serial

numbers, the requesting system and the external identifier type with external identifier number or the enterprise

identifier type with enterprise identifier number. Furthermore, you have to specify a file share location where the CSV

file containing the serial numbers shall be stored. After the download you can distribute the CSV file to the consumer

for example. by Email or other means.

To create a Serial Number Request, do the following steps:

1. Choose Serial Number from the navigation tree.


3. Choose Create Serial Number Request from the Results pane.

4. In the popup New Serial Number Request enter:

• Number of requested Serial numbers

• Requesting System

• Range Selection Key. This key is needed to determine the range that should be used to provide

serial numbers. Please note that an empty value, is also a valid key.

• Optional: if you want to request serial number for a specific product, select the checkbox Create

Serial Number Request for External ID and provide the External ID type and number of the product.

• Optional: if you want to request serial number for a specific business partner, select the checkbox

Create Serial Number Request for Enterprise ID and provide the Enterprise ID type and number of

the business partner.

• Optional: If you want that receive fully encoded object codes in the response of the serial number

request, select the checkbox Readily Encoded and provide the desired encoding type and format.

2.1.3.4.2 Report Lost Serial Numbers

To report Serial numbers as lost, do the following steps:

1. Choose Serial Numbers from the navigation tree.


3. Mark the Serial Number you what to report lost. Multiple selection is possible.


5. Select the Report as Lost from the drop-down list.


Public

47

2.1.3.4.3 Navigate to Related Range Definition

To navigate from a Serial Number to the Range Definition Version, do the following steps:


2. Mark the Serial Number you what to navigate from


4. The related range definition version gets displayed.

2.1.3.4.4 Navigate to Related Range

To navigate from a Serial Number to the related Range, do the following steps:


2. Mark the Serial Number you what to navigate from

3. Choose Display Range from the results pane

4. The related range is displayed.

2.1.4 Repository Browser

This section will have a closer look onto the Repository Browser as part of the Corporate Serialization Data Cockpit.

The Repository Browser section contains the captured data of the event messages that have been processed in SAP

Corporate Serialization. The Repository Browser consists of the following nodes:

• Serialized Objects

• Lots

• Serialized Trade Items

• Serialized Containers

• Events

• Business Documents

2.1.4.1 Forward Object Navigation

In the Repository Browser, you can navigate to an object from a different entity in several ways.

The main way of forward navigation to a selected object from the Objects tab for entities Events or Business

Documents, is either by double clicking on the object, or by selecting the row and then choosing Display Object from

the toolbar in the Details pane.

If the object exists in SAP Corporate Serialization, the object will be displayed with all its detailed information’s of the

Details tab

By default, depending on the type of the object, a GS1 object will be displayed in the GS1 specific object node

corresponding to its type (Lots, Serialized Trade Items, Serialized Containers). All other objects will be displayed in


Public

48

the generic Serialized Objects node if the corresponding node is set to Active (via transaction /CORS/C_NAV_TREE -

Define Navigation Tree Active Nodes). If the corresponding node is not active, forward navigation is not possible. The

default behavior can be changed by setting the user parameter /CORS/UI_NODE_REL to “GEN” in transaction

SU01. For more information, see the Configuration Guide on the SAP Help Portal at https://help.sap.com/cors.

2.1.4.2 Serialized Objects

Serialized Objects node generically represent different objects created during the serialization process including the

following object types:

• Lot (for example, GS1 LGTIN) is a non-serialized quantitative object with a quantity that is typically more

than 1.

• Serialized trade items (for example. GS1 SGTIN ) typically represents a saleable and uniquely identifiable

product. It can be represented differently, such as a GS1 element string or an EPC URI format.

• Serialized shipping container (for example. GS1 SSCC) which is a uniquely identifiable transport unit like

a pallet or a carton. Serialized containers typically carry a hierarchy of lower level Container and hierarchies

of products. Usually the top-level container of a packaging hierarchy is the object that is tracked and traced

in the supply chain. All events captured for the top-level object are inferred to all child objects.

All objects have these tabs in common:

• Object Hierarchy

Navigate to the tab Object Hierarchy to display all objects of the serialized object (upper and lower level). By

double click on one raw it's possible to navigate to this object. The same can be done by selecting one row

and executing action Display Object.

• Events

Navigate to the tab Events to display all events related to this object. By double click on one row, you will be

forwarded to this event in the Repository Browser. The same can be done by selecting one or several rows

and executing action Display Events.


Navigate to the tab Business Documents to display all business documents that are linked to this node. By

double click on one row, it's possible to navigate to this business document. The same can be done by

selecting one or several rows and executing action Display Business Documents.

All object types excluding Lots have the following tab:

• Related Lot

Navigate to the tab Related Lot to display the lot-related information of the selected serialized object.

Objects of type Lot have the following tab:

• Related Serialized Objects

Navigate to the tab Related Serialized Objects to display the objects of the selected lot.



Public

49

2.1.4.3 Lots

A lot is also known as a batch or an LGTIN (EPCIS), is a non-serialized quantitative object with a quantity that is

typically more than 1. A physical lot may be present at the same time in many different places with partial quantities

and therefore cannot be uniquely identified.

A lot is identified by its External Identifier Type and Ext. ID Number and its lot number. You can convert it into

different representations like GS1 element string (example –(01)03953720000003(10)BT290504) or EPC URI format

(example – urn:epc:class:lgtin:395372.0000000.BT290504).

Activities

You can perform the following actions:


Navigate to the view Object Hierarchy to display all objects of Lot (upper and lower level). By double click on

one row it's possible to navigate to this object. The same can be done by selecting one row and executing

action Display Object or Display Lot.

• Related Serialized Products

Navigate to the view Related Serialized Trade Items to display products of the selected Lot. By double click

on one row it's possible to navigate to a serialized trade item. Select one or multiple rows and execute

action Display Serialized Trade Items to display selected Items in entity screen for Serialized Trade Items.

• Events

Navigate to the view Events to display all Events of this node. By double click on one raw it's possible to

navigate to this Event. The same can be done by selecting one or several rows and executing action Display

Events.


Navigate to the view Business Documents to display all Business Documents of this node. By double

clicking on one row it's possible to navigate to this Business Documents. The same can be done by

selecting one or several rows and executing action Display Business Documents.

2.1.4.4 Serialized Trade Items

A Serialized Trade Item (for example GS1 SGTIN) typically represents a saleable and uniquely identifiable product.

Serialized Trade Items are identified by External ID Type set to GTIN, the External ID Number, and the serial

number. They can be represented in different ways, such as GS1 element string (for example,

(01)07501200000027(21)81502241000000000004) or EPC URI format (example,

urn:epc:id:sgtin:750120.0000002.81502241000000000004).

A serialized Trade Item always has a quantity equal to 1 in its unit of measure (UoM) and therefore can only be at

one place and in one state at a given time. Therefore, Trade Items can be included within an object hierarchy. Trade

Items typically carry a reference to a lot. In such a case, the lot of a serialized trade Item can be determined and

displayed. The lot data such as expiry date or manufacturing date can be displayed together with the serialized item.


Public

50

Activities

In the Serialized Trade Items node, you can perform the following actions:


Navigate to the view Object Hierarchy to display all objects (upper and lower level). By double click on one

row it's possible to navigate to this object. The same can be done by selecting one row and executing action

Display Object or Display Lot.

• Related Lot

Navigate to the view Related Lot to display Lot of the selected product.

• Events

Navigate to the view Events to display all Events of this node. By double click on one raw it's possible to

navigate to this Event. The same can be done by selecting one or several rows and executing action Display

Events.


Navigate to the view Business Documents to display all Business Documents of this node. By double click

on one row it's possible to navigate to this Business Documents. The same can be done by selecting one or

several rows and executing action Display Business Documents.

2.1.4.5 Serialized Containers

A Serialized Shipping Container Code (GS1 SSCC) is a uniquely identifiable transport unit like a pallet or a covering

box.

Serialized containers typically carry a hierarchy of lower level containers and hierarchies of products. Usually the

top-level Container of a packaging hierarchy is the object that is tracked and traced in the supply chain and all

events captured for the top-level object are inferred to the child objects.

Serialized containers are identified in EPCIS by the GS1 element string which contains the GS1 global company

prefix and the serial item reference. You can convert the SSCC into alternative representations such as the EPC

URI.

Serialized containers always have a quantity equal to 1 and therefore can only be at one place and in one state at a

given time. Therefore, serialized containers can be included in an object hierarchy.

Activities

You can perform the following actions:


Navigate to the view Object Hierarchy to display all objects of serialized container (upper and lower level).

By double click on one row it's possible to navigate to this object. The same can be done by selecting one

row and executing action Display Object or Display Lot.

• Events

Navigate to the view Events to display all captured events of this node. By double click on one row it's

possible to navigate to this event. The same can be done by selecting one or several rows and executing

action Display Events.


Navigate to the view Business Documents to display all Business Documents of this node. By double click


Public

51

on one row it's possible to navigate to this Business Document. The same can be done by selecting one or


2.1.4.6 Events

Events are the main entry point into SAP Corporate Serialization transactional data processing. Events trigger the

creation and update of objects and transactions and set the relations between the different objects. In other words,

you can change the transactional data only through events. Furthermore, the solution allows you to only create an

event but not change it. If an event contains wrong objects or has changed the wrong data, you can create another

event or even a series of events to rectify the error.

SAP Corporate Serialization's object and event model is oriented at the GS1 EPCIS Event data model. The primary

data exchange format in inbound and outbound communication is EPCIS.

SAP Corporate Serialization can receive and send EPCIS events based on the following supported event types:

• Object Event: Create, change, and delete (de-commission) objects

• Aggregation Event: Aggregate and disaggregate objects

• Transaction Event: Add and remove transaction relations to objects

• Transformation Event: This event type helps in adding or removing a transaction reference to or from an

object

Events do not have an external identifier. Events are identified by the date and time when they occurred.

Event Inference and Event – Object relation

Events carry a reference to all objects that participated in the event. Events are typically captured for the top object of

a packaging hierarchy. During event processing, all child objects of the current hierarchy are determined, and the

event is inferred to all child objects. A native indicator at the event-object relationship, stores the information in the

following ways:

• Native Indicator is true: Whether the object has directly participated at the event

• Native Indicator is false: Whether the event was inferred to the object

Events are also interrelated to the other entities:

• The Business Documents tab can be used to display all transactions that participated in an event. For more

details, see chapter Business Documents

Activities

There are several buttons located on top of the result list like:

• Message AIF

This button creates a new window and starts the AIF Monitoring and Error Handling transaction (/AIF/ERR)

• Message File -> Display Message File

When selecting an event of the result list, the inbound message file can be displayed.

• Message File -> Download Message File

When selecting an event of the result list, the inbound message file can be downloaded to local storage.


Public

52

• Process Event XML

This starts a new window with the Post Manual Event: Process XML Message report.

In the lower area the different tabs also provide activities:

• Objects

Navigate to the view Objects to display all objects. By double click on one row it's possible to navigate to

this object. The same can be done by selecting one row and executing action Display Object.

• Source/Destination

Navigate to the view Source/Destination to display the related source and/or destination. By selecting one

row, it’s possible to navigate to the location by clicking on Display Location or the related business partner

by Display Business Partner.


Navigate to the view Business Documents to display all Business Documents of this event. By double click

on one row it's possible to navigate to this Business Document. The same can be done by selecting one or


2.1.4.7 Business Documents

Business documents in SAP Corporate Serialization reflect business documents like production order, inbound or,

outbound delivery. They are stored as a separate entity within the SAP Corporate Serialization Repository Browser.

Business documents can be created in two ways:

• Explicitly via integration from SAP S/4HANA

• Implicitly “on the fly” in case they are referred within an EPCIS document and do not exist yet in SAP

Corporate Serialization.

Business documents have relations to events and objects:

• Document-Event Relationship: This documents that a business document participated in a particular

event. As events can only be created and not updated, the document-event relationship is available

permanently.

• Document-Object Relationship: This documents the business document and the object that are currently

related to each other. This relationship can be created and removed with the help of Events.

2.1.4.7.1 Create New Business Documents

There are two ways for creating new Business Documents:

• Explicit creation through SAP S/4HANA integration

The SAP Corporate Serialization add-on for ERP offers the option to integrate certain business document types. In this case these business documents are integrated from SAP S/4HANA at creation (for example, deliveries) or release (for example, production, process order) of the business documents.


Public

53

Furthermore, the business transaction will be created with items and the processing status of the business transaction is integrated as well and reflected as business transaction item status and transaction summary status.

• Implicit creation of business documents through EPCIS event

If there is a business document reference within an EPCIS message and the business document does not yet exist in the repository system, then the business document is created as an external business document together with the document relations.

In this case, the business document serves as an abstract linked object which can be used to search for objects or events but have no connection to an existing document within ERP.

Through this approach any supported business document type beyond the currently supported SAP S/4HANA transactions can be created and referenced within SAP Corporate Serialization.

The document status will always be created externally, and the document summary status will always be Created as

EPCIS only supports transaction references but does not handle transaction status information.

2.1.4.7.2 Business Document Status Handling

This section deals with the business document status and the status of the serialized objects. The business

document status is relevant for all kind of business documents. In case of an externally created business documents,

the document status is set to created externally at the creation and never changed again.

The status handling only takes place in case the business document is integrated from SAP S/4HANA. In this case,

the document status reflects the overall status of the document.

Document Status

• Created externally: Only status used for external business transactions.

• Initially Integrated: Initial status value for business transactions integrated from SAP S/4HANA.

• Closed or Finished: Transaction summary status is closed. Deleted in Source System: Set in case business

transaction is deleted in SAP S/4HANA.

• Replicated: Used in case of distributed repository systems to indicate that business transaction has been

replicated

Item Status

• Created: Initial status after creation of item.

• In Process: Partial confirmations on item level in SAP S/4HANA.

• GM posted: Final confirmation done at item level in SAP S/4HANA

2.2 Object Tracing and Event Processing

SAP Corporate Serialization is designed in such a way, that it can receive and process events in different message

formats (supported by default, or through additional development). A message must contain at least one event and

can contain even more.


Public

54

An event contained in an event message documents and traces an atomic business activity that happened to the

objects contained in the event. An event therefore contains four main parts:

1. When – represented by the time stamp of the event

2. Where – represented by the BizLocation (object location) and ReadPoint (event location) of the event

3. What – represented by the SAP Corporate Serialization event action

4. Why – represented by the business step and the disposition, which can be further accompanied by

referenced business documents

Therefore, the required information are mapped from message dependent format to a fitting SAP Corporate Serialization data entity. By default, this functionality is built in for EPCIS message format.

2.2.1 EPCIS Event Types and Features

EPCIS describes the following different event types that are to be used to trace events:

● Object Event

This event type helps to publish the existence or to end the lifecycle of a serialized object. In addition, you can use it to trace any observation to a serialized object. Transaction references can be attached but are not mandatory. The event generally applies to a list of EPCs or LGTINs. Extensions are possible at event header level. The extensions may also reference list of EPCs they apply to.

The actions ADD, DELETE, OBSERVE are supported.

● Aggregation Event

This event type helps to publish the aggregation or disaggregation (pack / unpack) of serialized objects to or from a parent EPC. Transaction references can be attached but are not mandatory. The event generally applies to the packing or unpacking activity which references a number of EPCs or LGTINs being added to or removed from a hierarchy. Extensions are possible at event header level. The extensions may also reference list of EPCs they apply to.


● Transaction Event

This event type helps in adding or removing a transaction reference to or from an object. You can use this as an alternative to the object event to observe any activity that is executed with a serialized object. The event generally applies to a list of EPCs or LGTINs. Transaction reference is mandatory.


● Transformation Event

This event type helps to transform input objects into output objects. You can use this to destroy a list of input objects while commissioning a list of output objects at the same time. The event generally applies to an input list and an output list of EPCs or LGTINs. An optional Transformation ID can connect several transformations. If a special dedicated business step is used, this event can be used instead to assign a new lot to a list of objects. In this case, those objects need to be represented in the input and output list and the lists have to be identical.

For the Transformation Event no actions are supported.


Public

55

2.2.2 EPCIS Inbound Processing

2.2.2.1 Overview End to End Event Message Processing

Figure 6:Capture EPCIS inbound processing

The Inbound processing of event messages is handled through SAP Application Interface Framework (AIF).

This means that for each desired message type or format, an AIF interface must exist for receiving the messages.

Within these interfaces, the message data is mapped into compliant, specific structures for further processing.

The event processing decodes the event and objects data, validates the data, creates or, updates all the repository

entities (objects, events, business documents) and also the relations between entities.

The AIF EPCIS mapping interface performs the following steps:

• It receives the EPCIS XML message.

• It determines whether the message must be processed sequentially in a queue or can be processed in

parallel to other messages.

• It sorts the events within the message based on the event time stamp. If the time stamp is the same, the

events are processed in the order that is in the event message.

• It maps the data from the external EPCIS XML to SAP internal EPCIS-like ABAP structures.

• It splits the message into its single events.

• It calls event processing separately for each event.

• It controls the commit handling dependent on the message content and the configuration, or on one of the

two (either commit by event or by complete message. For more information, see the section Commit

Handling below').


Public

56

2.2.2.2 Message Serialization and Message Simulation

You can configure whether event messages will be processed parallelly or sequentially. That forces the processing in

the same sequence as of the arrival message. In the case of serialized processing, when the processing of one

message fails, this message blocks the queue and all the subsequent messages wait until the blocking message is

either removed or reprocessed successfully.

In addition to the message serialization, a simulation mode enables the processing of EPCIS messages without

changing the objects on the database. A rollback will be triggered if the simulation mode is enabled for a specific

message sender.

You can configure message serialization in the Customizing activity Maintain Sender Queue and Commit Settings

under Corporate Serialization → Event Capture, or via transaction /CORS/C_MSG_CUST. Here you can define a

sender and for each sender, you can maintain whether messages from this sender shall be serialized. If nothing is

maintained, by default two event messages from a sender will be processed in parallel and independent of each

other.

In addition to the customizing, the event message needs to contain the sender information. Therefore, the sender

name must be included in the XML tag queueMessageSender in the message header.

Example

The following example show an excerpt of an XML message, which refers to the sender name SENDER_1 in

its header:

<cors:envelope

xmlns:cors=http://www.sap.com/sap_cors/

xmlns:epcis="urn:epcglobal:epcis:xsd:1">

<cors:header>

<cors:queueMessageSender>SENDER_1</cors:queueMessageSender>

</cors:header>

<cors:content>

<epcis:EPCISDocument>

…

</epcis:EPCISDocument>

</cors:content>

</cors:envelope>

Serialized messages are visualized in the AIF message monitor (transaction /AIF/ERR) as an aggregate under the

tree node for the sender that defines the serialization queue. Messages visualized under the undefined node are the

ones processed in parallel.

2.2.2.3 Commit Handling

In the Customizing activity Maintain Sender Queue and Commit Settings under Corporate Serialization → Event

Capture (transaction /CORS/C_MSG_CUST) you can configure if you want the messages from this sender to be

committed for every message, or if every event contained within the message should be committed separately.

http://www.sap.com/sap_cors/


Public

57

For commit by message, even successfully processed events within the same message will be rolled back if any

subsequent event fails.

In all cases, the failure of an event will stop subsequent events within the same message to be processed.

2.2.2.4 Rollback Handling

If the event is considered as failed during inbound processing:

• all the non-committed changes are rolled back and the event is considered failed and the AIF inbound

message is also considered failed.

• No further events from the same message are processed.

• In AIF, the message appears as failed. The failed inbound messages can be queried and displayed in the

AIF monitor (transaction /AIF/ERR). You can review the application log messages and identify the errors. If

applicable, you can restart the processing and only those parts of the message that have not been

committed are restarted.

2.2.2.5 Extension Concept for EPCIS Inbound Processing

SAP Corporate Serialization offers powerful extension capabilities to receive and process custom attributes at

different levels of the EPCIS XML message.

To process enhanced EPCIS messages, it is not necessary to modify or enhance the definition of the EPCIS

messages based on a custom WSDL file that has to be implemented by all senders of EPCIS messages. Instead, the

EPCIS inbound processing only interprets the tags in the message it identifies. Unidentified tags are ignored during

processing.

The existing SAP Extensions (SAPExtension) are supported natively. For more information, see the Configuration

Guide for SAP Corporate Serialization on the SAP Help Portal at http://help.sap.com/cors.

2.2.3 Additional Business Steps

There are some special cases, where the required event handling cannot be managed by the default SAP Corporate

Serialization event capture framework. Therefore, there is the possibility to implement own handlers for the specific

format.

2.2.3.1 Assign New Lot

This is a rather extraordinary case, which allows you to assign a new lot to an SGTIN. It will trigger a transformation

event during which the relation between the listed objects and the currently assigned batch will be altered to a new

batch object. Within the triggering event it is required that the inputEPCList and the outputEPCList within the

EPCIS inbound message are identical, and that the new batch is declared within the object attributes section.

http://help.sap.com/cors


Public

58

2.3 AIF Error Handling and Alerting for SAP Corporate Serialization

SAP Corporate Serialization uses AIF standard functionalities for error handling and alerting of interfaces. More

information about AIF and the available possibilities for error handling and alerting can be found in the SAP

Application Interface Framework for SAP S/4HANA Application Help at http://help.sap.com/aif.

2.3.1 Customizing of AIF Error Handling and Alerting

All available namespaces and assigned interfaces are predefined in SAP Corporate Serialization. As the settings for

error handling and alerting are part of this Customizing, these settings can’t be changed in the customer system.

Nevertheless, SAP Corporate Serialization provides flexible capabilities to set up customer-specific error handling

and alerting.

2.3.1.1 Details on Error Handling and Alert Customizing

For all Interfaces, a specific Standard Alert Receiver and a specific Alert Category is defined. The standard alert

receiver enables you to find a specific alert receiver for each interface. The alert category let you set up alert mails

with interface-specific content (for example, long texts). You can change the provided alert categories using

transaction ALRTCATDEF. For example, texts for the alert category and more information about the Customizing

settings, see the configuration guide for SAP Corporate Serialization on the SAP Help Portal at

http://help.sap.com/cors.

2.3.1.2 Specific Error Handling and Alerting for EPCIS Interface

Besides the previously mentioned standard alert receiver for each interface, SAP Corporate Serialization lets you set

up a sender-specific error or alert handling for the EPCIS interface. That means you can define a custom alert

recipient for each sender that is used in the EPCIS inbound message.

For more information about the Customizing settings, see the Configuration Guide for SAP Corporate Serialization on

the SAP Help Portal at http://help.sap.com/cors.

2.3.2 Assign Users for Standard Alert Recipient Determination

The assignment of users to the standard alert recipient needs to be done if specific users are to be informed about a

situation (this could be an error or a warning message) during the processing of an interface. The definition of

standard alert recipients is already predefined in SAP Corporate Serialization. That means only the assignment of

users to the alert recipient must be done on the customer system.

To assign different interfaces and their standard alert recipients to a specific user:

1. Call transaction /AIF/RECIPIENTS

http://help.sap.com/aif

http://help.sap.com/aif




Public

59

2. Enter the user as Work Area.

3. On the next screen enter the namespace of the standard alert recipient.

4. Enter the message type. Following message types are supported:

• N – None. Alerts will be raised for the ABAP message types E and A.

• I – Info. Alerts will be raised for the ABAP message types I, S, W, E and A.

• S – Success. Alerts will be raised for the ABAP message types S, W, E and A.

• W – Warning. Alerts will be raised for the ABAP message types W, E and A.

• E – Application Error. Alerts will be raised for the ABAP message types E and A.

• A – Technical Error. Alerts will be raised for the ABAP message types S, W, E and A.

• Empty Value – Application Error or Technical Error. Alerts will be raised for the ABAP message

types E and A.

5. Select the checkbox Overview. This lets you display the alert recipients in the AIF Interface Monitor

(transaction /AIF/IFMON).

After you have saved the assignment of the namespace or alert recipient to the user, this user will receive alerts.

These alerts are visible within the AIF Interface Monitor (Transaction /AIF/IFMON). For more information, see

chapter Usage of the AIF Interface Monitor. If the Mail Server is set up in your system, and an email address is

assigned to the user, an alert mail will be sent to the user.

Tip If the determination of the standard recipient fails, ensure that the AIF default recipient ALL is not used for all

interfaces. To check whether the AIF default recipient ALL is used or not, do the following steps:

1. Call transaction SM30 and enter view name /AIF/V_ALRT_DET

2. Leave Namespace, Interface and Version empty and press Enter

3. Confirm the next popup with CONTINUE

4. If the following entry is displayed, the AIF Default recipient is active:

Namespace Interface Version Recipient for Alert

ALL

5. To use the AIF default recipient, you must delete the recipient ALL from the table.

Furthermore, it is possible to customize a Sender Specific Alert Recipient Determination and a Message-Specific

Recipient Determination.

For more information on how to setup these alert methods, check the Configuration Guide of SAP Corporate

Serialization on the SAP Help portal at http://help.sap.com/cors.

2.3.3 Usage of the AIF Interface Monitor

The AIF Interface Monitor (transaction /AIF/IFMON) provides a user-specific overview about the interfaces and the

alert recipients assigned to the user.

Recipients used in the alert recipient table, as well as the standard recipient, are displayed in the AIF Monitor if the

checkbox Overview is selected in the transaction /AIF/RECIPIENTS. If the BAdI is used to add recipients in

specific situations, this recipient will not be displayed in the AIF Monitor. For the EPCIS interface, you can display

this recipient by adding the recipient to the Recipient assignment table.

If an alert is raised, this status is indicated by an active alert icon.



Public

60

In the column Mail the user can set up the mail notification for each recipient. The following setup is possible:

Icon Icon Text Mail Notification

No mail The user will not get notifications via

mail for this recipient

Mail for next alert The user will get notifications via mail

for the next alert. That means the user

will get a mail if an alert is raised. The

user will not get any further mails until

the existing alert is confirmed and a

new alert is raised.

Mail for every error The user gets notifications via mail for

all alerts (also if there is an existing

alert) with Message Type A or E.

Tip

If the error messages does not appear in the AIF Interface Monitor for recipients in customer namespace, assign

the standard recipient for SAP Corporate Serialization via transaction /AIF/RECIPIENTS for the initial setup.

2.3.3.1 Usage of AIF Error Monitor

The AIF Error Monitor (transaction /AIF/ERR) is used to monitor the AIF interfaces and can be used alternatively to

the AIF Interface Monitor to view details of the message processing and errors.

Error Logging for EPCIS Inbound messages

All errors that occur during the processing of EPCIS Inbound Messages are logged in the AIF interface EPCIS_MSG

(Interface for EPCIS Inbound Message processing) assigned to namespace /CSINB.

If an error occurs the XML Event and additional Details can be displayed or the XML Event can be downloaded

depending on the error. For more information on the maintained functions for the Error Monitor, see the chapter

Setting Up Application Interface Framework in the configuration guide for SAP Corporate Serialization on the SAP

Help Portal at http://help.sap.com/cors.

Error Logging for Serial Number Requests

All errors that occur during the processing are logged in the AIF interface SN_REQ_ALT (Serial number request

threshold alert) assigned to namespace /CSSER



Public

61

If you are dealing with range definitions with randomization scope 8 – Manual Randomization, then an automated

serial number request is not possible because the process is mostly manual. So, for a range definition that manages

serial numbers for such products, the user needs to upload serial numbers to SAP Corporate Serialization.

The only step which can be automated is that after every serial number request, it is checked whether the threshold

of available serial numbers is reached. If it is reached, an alert is triggered in the AIF interface SN_REQ_ALT (Serial

number request threshold alert) assigned to namespace /CSSER. Based on this alert, a user can be notified. SAP

Corporate Serialization will inform the user to initiate the manual procedure described above to request and upload

new serial numbers.

For more information on the maintained default recipients and alert categories, see the Configuration Guide for SAP

Corporate Serialization on the SAP Help Portal at http://help.sap.com/cors.



Public

62

3 SAP S/4HANA Add-on for SAP Corporate

Serialization

Starting from SAP S/4HANA 2020 FPS02, you can integrate master and transactional data from SAP S/4HANA to

SAP Corporate Serialization using the existing functionality of SAP Advanced Track and Trace for Pharmaceuticals.

Note

Though SAP Corporate Serialization supports several different industry standards, the existing functionality of

SAP Advanced Track and Trace for Pharmaceuticals in SAP S/4HANA supports only the GS1 standard. For

more information on how to install, configure, and use SAP Advanced Track and Trace for Pharmaceuticals, see

the user assistance for SAP Advanced Track and Trace for Pharmaceuticals on the SAP Help Portal at

https://help.sap.com/attp.

SAP Advanced Track and Trace for Pharmaceuticals is part of the SAP S/4HANA core delivery. This functionality can

be used for the integration to SAP Corporate Serialization without additional enhancements. However, specific

settings for SAP Corporate Serialization should be maintained in SAP S/4HANA:

1. The application STTPEC should be activated

2. Switch on the integration to SAP Corporate Serialization.

The following business functions are available:

• /STTPEC/APPL_S4H to activate STTPEC application in the system

• /STTPEC/INT_CORS to activate integration to SAP Corporate Serialization

Features

• Master Data maintenance and integration

o Customers and vendors are integrated as business partners.

o Plants and storage locations are integrated as locations.

o Material master is enhanced, and materials are integrated as products.

o Product serialization attributes can be maintained in a separate transaction.

• Transactional Data Integration

o Production orders and process orders are integrated as business documents.

o Inbound deliveries, outbound deliveries and return deliveries are integrated as business

documents.

o Batch is enhanced and batches are integrated as lots.

• Warehouse integration with Warehouse Toolbox and SAP Corporate Serialization functions:

o The warehouse toolbox is collection of functions that you can use for processes related to your

warehouse activities.

https://help.sap.com/attp


Public

63

o Warehouse business functions (activities) including validation and buffering for a series of typical

warehouse activities.

o Compose and send EPCIS event message for warehouse activity

o Warehouse comfort functions such as get contents, get hierarchy, serial number request

o Warehouse test UI

o RF demo implementation for inbound and outbound processing showcases potential usage of the

toolbox

For more information, see the Configuration Guide for SAP Corporate Serialization on the SAP Help Portal at


3.1 Master Data Maintenance and Integration

SAP Corporate Serialization needs master data to identify, interpret, and process transactional data. Typically,

master data is integrated from an external system to SAP Corporate Serialization. In many cases this external

system is an SAP S/4HANA system. However, SAP Corporate Serialization offers open APIs that you can use to

connect non-SAP systems. Besides this you can also maintain master data locally in the SAP Corporate

Serialization repository instance without integration from any external system.

In general, the integration from multiple logical systems is also supported for master data objects. Therefore, the

logical system group parameter is stored at the respective master data entity. The external ID of a master data entity

is only unique together with the logical system group.

3.1.1 Integrate Customers and Vendors as Business Partners

Integration from SAP S/4HANA to the repository system is done through a batch report. Vendors and customers are

integrated to the repository system as business partner roles. If a vendor and a customer share the same Global

Location Number (GLN) in SAP S/4HANA, they would reflect in the repository system as one business partner with

two roles – customer and vendor and with external identifier type GLN. Hence, only one business partner is created

with two roles. If a customer or a vendor is not assigned a GLN, or is assigned different GLNs, they are integrated as

independent business partners with the customer role and vendor role respectively.

Note

You can reassign the role from one business partner to another using the Reassign Role feature in the business

partner entity in the Data Cockpit.

Customers and vendors are not extended in SAP S/4HANA and are integrated in their current state. The integration

is always a full update which means that for all selected business partners in SAP S/4HANA always all attributes are

integrated and overwritten in the repository system.



Public

64

Integration Report for Business Partners

In the SAP S/4HANA system, you can access the integration report in Customizing for Business Partner

Integration under Advanced Track and Trace → Repository Integration, or via transaction /STTPEC/INT_BUP. On

the selection screen of the integration report, you have the following report selection parameters:

• Vendor Selection

o Business partner type for vendor selection

o Account number of Vendor or Creditor • Customer Selection

o Business partner type for customer selection

o Customer Number

To integrate only business partners that have a GLN assigned, select the appropriate checkbox on the screen.

To activate the business partners directly with the integration, select the checkbox Activate Business Partner.

To enable vendor and customer selection based on the business partner type, you must maintain Customizing for

mapping the vendor account group and customer account group to the business partner type. For data selection, the

vendor account groups, and customer account groups are determined and used as criteria for data selection. For

more information about the Customizing activity, see the configuration guide for SAP Corporate Serialization on the

SAP Help Portal at http://help.sap.com/cors.

3.1.2 Integrate Plants and Storage Locations as Locations

You can integrate the location entity in the repository system from SAP S/4HANA through a batch report. Plants and

storage locations in the SAP S/4HANA system are integrated to the repository system as locations of types Plant and

Storage Location. Storage locations are created as child locations of the plant locations that are the parent locations.

Plants and storage locations are not extended in SAP S/4HANA and are integrated in their current state. The

integration is always a full update, which means that for all the selected plants and storage locations in the SAP

S/4HANA system, all attributes are integrated and overwritten in the repository system.

Integration Report for Plant and Storage locations

In the SAP S/4HANA system, you can access the integration report by navigating to Advanced Track and Trace →

Repository Integration → Plant & Storage Loc. Integration, or via transaction /STTPEC/INT_LOC. On the report

integration interface, you have the following report selection parameters for plants and storage locations:

• To integrate only plants that have a GLN assigned, select the checkbox Integrate Plants only if they have

GLN assigned.

• To activate the locations directly with the integration, select the checkbox Include Storage Locations.

Whenever a plant is integrated to the repository system, during data collection, the SAP S/4HANA system checks if a

GLN is assigned to the plant and only then it transfers the GLN together with the plant to the repository system. An

external identifier type GLN will be created for the location in repository system.

Note

Assignment of GLN to plant is done within transaction EANGLN or via assigning a business partner with GLN to

a plant.



Public

65

3.1.3 Enhancement of Material Maintenance

This chapter explains the enhancement of Material Maintenance and Material Integration as product. As part of

Material Master Integration, you need to create the Material Master data in the SAP S/4HANA system. SAP

Advanced Track and Trace for Pharmaceuticals functionality provides enhancements to the Material Master

Maintenance and enables the integration of the material masters as a product.

3.1.3.1 Material Maintenance in SAP S/4HANA

This functionality extends the existing material maintenance in SAP S/4HANA with serialization attributes needed by

SAP Advanced Track and Trace for Pharmaceuticals and SAP Corporate Serialization. However, most of the

necessary product attributes can be maintained in SAP S/4HANA and integrated into SAP Corporate Serialization.

The material master database tables and maintenance UIs have been extended for this purpose. Enhancement of

material maintenance is described in the application help for SAP Advanced Track and Trace for Pharmaceuticals.

For more information, see the application help for SAP Advanced Track and Trace for Pharmaceuticals on the SAP

Help Portal at http://help.sap.com/attp.

3.1.3.2 Integrate Materials

Materials can be integrated either online or through batch report.

Unlike the Business Partner and Location where all the selected objects are always transferred for integration, the

material integration uses only the changed materials for integration. Therefore, while saving changes to a material,

the system checks for differences in the attributes relevant for Serialization. If the system detects differences, the

check box Changed Since Integration is set. Furthermore, you can use the Customizing activity /STTPEC/V_PMDCF -

Maintain Material Fields to define additional fields of the material master that triggers the integration. For more

information, see the configuration guide for SAP Advanced Track and Trace for Pharmaceuticals on the SAP Help

Portal at http://help.sap.com/attp

Online Integration of Material to Repository System During Save

If online integration for materials is activated, the system automatically triggers this type of integration if a material is

changed and the integration relevance for the material is determined. However, this type of integration is only

applicable for material changes.

Note

The very first integration to SAP Corporate Serialization must always be triggered through the report. You can

configure online integration using the General Customizing. For more information, see the Configuration Guide

for SAP Corporate Serialization on the SAP Help Portal at http://help.sap.com/cors.

Integration from SAP S/4HANA through a Report

You can use the batch report (transaction /STTPEC/INT_MAT - Material Master Integration) to trigger:

http://help.sap.com/attp




Public

66

• Delta Update ensures the integration of only those serialization-relevant materials that are not yet

integrated, and of the ones that are already integrated but were changed since the last integration.

• Full Update ensures the integration of all materials which are relevant for serialization.

Optionally you can trigger activation of product and assignment or the creation of serial number entities (range

definition and range) at integration. By maintaining all serialization attributes in the material master maintenance and

by setting these two checkboxes, you may integrate the product, create and activate serial number entities and

activate the product. As a result you may directly start requesting serial numbers and commission serialized items

without any further manual interaction in the repository system.

As a prerequisite you need to define a range automation profile and assign it to the serialization profile in the

repository system. If you are dealing with externally managed serial number range definitions (serial number

management type E) then, in addition, you need to ensure that the Business Partner To Provide Serial Numbers is

maintained. Ensure that in the repository system the notification system is assigned to this business partner, and for

this system all relevant data to trigger a serial number request is maintained.

For more information, see chapter Serialization Settings in the Configuration Guide for SAP Corporate Serialization

on the SAP Help Portal at http://help.sap.com/cors.

3.2 Transactional Data Integration

The transactional data integration handles the integration of business documents such as production order, process

order, purchase order, inbound delivery, outbound delivery and return delivery. Furthermore, it handles the

integration of the batch from SAP S/4HANA to SAP Corporate Serialization.

3.2.1 Integrate Production Orders, Process Orders, Purchase Order,

Inbound Deliveries, Outbound Deliveries and Return Deliveries

SAP S/4HANA for SAP Corporate Serialization offers the option to integrate business documents such as production

order, process order, purchase order, inbound delivery, outbound delivery and return delivery.

The business document will be created with items and the processing status of the business document is integrated

as well and reflected as business document item status and business document summary status. Besides this, the

following item attributes are also integrated:

• Planned quantity: Total quantity of an item planned for execution.

• Confirmed quantity: Actual item quantity which was posted as goods movement.

• Batch / Lot number: Batch / Lot number assigned to a business transaction document item.

In case of split items both the parent item as well as the split items are integrated. The parent only carries a planned

quantity if the total planned quantity is not fully assigned to the split items (Remark: Item split can happen for

outbound deliveries for example, in case different batches executed for one item).

General Behavior

• Within SAP S/4HANA



Public

67

o It can be configured in General Customizing whether inbound deliveries, outbound deliveries, (return

deliveries are special outbound deliveries), production orders, process orders and purchase orders shall

be integrated (in general or per plant)

o Furthermore, it can be configured whether a business document will be integrated immediately (online)

or only through integration report

o The relevant business document items and sub-items are integrated as well.

o Integration is triggered at creation or release of the transaction and if a relevant business document

data is changed.

Example

The following example show an excerpt of an XML message, which refers to the sender name SENDER_1 in

its header:

• Deletion of document

• Deletion or addition of item

• Update item: For example, because of change of planned quantity or assignment of batch

• Split of item

• Update confirmed item quantity at post goods movements

For more information, see the configuration guide for SAP Advanced Track and Trace for Pharmaceuticals on the

SAP Help Portal at http://help.sap.com/attp

• Within SAP Corporate Serialization:

o When a business document first is integrated the document status is set to Initially Integrated

o The business document type reflects the GS1 core business vocabulary (prodorder for production order, recadv for inbound delivery, desadv for outbound delivery, rma for a return

delivery and po for purchase order)

o The document type and document number reflect the document type and number known to SAP S/4HANA

o The document status reflects the summary of all item status values.

o Location Identifier type is determined as SGLN

o Location Identifier number is converted from GLN value into SGLN

o Business Transaction items contain the following information:

▪ Item number

▪ External ID type is GTIN + External ID number is GTIN value

▪ Item status

▪ Planned quantity and confirmed quantity

▪ Batch/lot

Specifics for Delivery Integration

• Deliveries are integrated after creation

• By using parameter TRN_GM_SEND Send Goods Movement Event to SAP Corporate Serialization, it can be

configured in general customizing whether action Post Goods Movement inbound delivery, outbound

delivery or return delivery will compose and send a receiving or shipping event for all objects that are

currently related to the transaction.

o Post Goods Receipt for Inbound Delivery

▪ Query all objects related to business document from SAP Corporate Serialization ▪ Compose Object Event with Action Observe and Business Step Receiving

• EPC list as determined

• Disposition: active



Public

68

• Read point/Business location: determined from plant (EANGLN)

• Source/Destination: determined from inbound delivery

o Post Goods Issue for Outbound Delivery ▪ Query all objects related to business document from SAP Corporate Serialization ▪ Compose Object Event with Action Observe and Business Step Shipping


• Disposition: in_transit

• Read point: determined from plant (EANGLN)

• Business location: empty

• Source or Destination: determined from outbound delivery

o Post Goods Receipt for Return Delivery ▪ Query all objects related to business document from SAP Corporate Serialization ▪ Compose Object Event with Action Observe and Business Step Receiving


• Disposition: active

• Read point/Business location: determined from plant (EANGLN)

• Source/Destination: determined from return delivery

• When reverting post goods issue of outbound delivery, post goods receipt of return delivery or post goods

receipt of inbound delivery via transaction VL09 - Cancel Goods Issue for Delivery Note, the solution

composes and sends an opposite event message. To revert a shipping event, a receiving event is

composed and sent and vice versa.

For more information, see the Configuration Guide for SAP Corporate Serialization on the SAP Help Portal at


Specifics Production or Process Order Integration

• The output material is integrated as item 1.

• Integration is triggered only when releasing order.

3.2.2 Batch Enhancements and Integration from SAP S/4HANA to

SAP Corporate Serialization

Batch Enhancements

The batch database tables in SAP S/4HANA are enhanced with following attributes:

• Serialization type: This indicates whether the batch is serialized, lot managed, or not serialized.

• Synchronization time stamp: This indicates the time when the last synchronization of the batch happened.

• Synchronization active: If this checkbox is selected, it indicates that true the batch has been successfully

integrated to the repository system

These additional attributes are not visible in the standard batch transactions in SAP S/4HANA, but you can visualize

them through the report /STTPEC/INT_BATCH Batches Integration.

The serialization type of the batch is determined during the creation of the batch and it is determined in the following

different ways:



Public

69

• If the batch has a manufacturing date assigned, then the serialization type of the batch is determined based

on the manufacturing date and the Serialized From date. If the manufacturing date is the same or later than

the Serialized From date the serialization type of the material header is copied to the batch. If not the

serialization type of the batch is set to Not Serialized.

• If the batch has no manufacturing date assigned, then the serialization type of the batch is determined

based on the creation date of the batch and the Serialized From date. If the creation date is the same or

later than the Serialized From date the serialization type of the material header is copied to the batch. If not

the serialization type of the batch is set to not serialized.

• The logic of determining the serialization type is encapsulated in a BAdI. For more information, see the

Configuration Guide for SAP Corporate Serialization on the SAP Help Portal at http://help.sap.com/cors.

The attributes synchronization time stamp and synchronization active are set after successful integration of the batch.

Batch Integration from SAP S/4HANA to SAP Corporate Serialization

The batch can be integrated as a lot (LGTIN) from SAP S/4HANA to SAP Corporate Serialization.

Prerequisites

The following prerequisites must be fulfilled to enable batch integration:

• Customizing:

In the General Customizing in SAP S/4HANA it must be defined whether lot-level batches or serialized

batches will be integrated to SAP Corporate Serialization. If neither of the two is active, then it is not

possible to integrate batches.

• SAP S/4HANA Material master:

o Tab Basic Data 1 (MARA): Serialization Type must be other than not serialized

o Tab Work Scheduling (MARC) : Serialized From must be maintained o SAP S/4HANA material must be integrated to SAP Corporate Serialization

• Batch master must be created for the plant

The batch integration is triggered online after a successful creation of a plant batch. An object event with action ADD is composed for the LGTIN and sent to SAP Corporate Serialization via RFC interface:

• The disposition of the event is determined based on the batch status as following:

o Batch status restricted results in event disposition non sellable other

o Batch status non-restricted results in event disposition event disposition active

• Batch attributes like expiry date and manufacturing date are included within the SAP extensions (if data is

set in SAP S/4HANA).

• The quantity list of the event just carries the LGTIN in EPC URI format and no quantity. This indicates that

the message addresses the complete lot.

The batch integration is triggered online after a successful change of the plant batch. An object event with action

OBSERVE is composed for the LGTIN and sent to SAP Corporate Serialization via RFC interface:

• The quantity list of the event just carries the LGTIN in EPC URI format and no quantity. This indicates that

the message addresses the complete Lot.

• The disposition depends on the status of the batch.

• If maintained, batch attributes like expiry date and manufacturing date are included within the SAP

extensions. Such attributes can only be updated in the repository system as long as the batch is restricted

(disposition in repository system = non sellable other). In case the batch status is unrestricted (disposition in



Public

70

repository system = active), then change within the repository system is not possible, and these attributes

will be neglected during event processing and a warning is logged

Integration of Produced Quantities for Batch

Produced quantities for a batch can be integrated from SAP S/4HANA to SAP Corporate Serialization to allow

comparisons with the serialized trade items (reconciliation of data).

Prerequisites

• You have integrated the material and the batch into SAP Corporate Serialization.

• You have created a production order.

• You have maintained a batch reference for the production order.

Whenever a goods receipt is posted in transaction MIGO with reference to the production order and the batch then an

object event with Action ADD is composed for the LGTIN and sent to SAP Corporate Serialization through RFC

interface.

• This time the quantity list carries the LGTIN and the quantity that has been confirmed in MIGO for the batch.

(Note: As soon as the quantity is defined, this means that the event message does not deal with the batch

as a whole, but just with a partial quantity of the batch. As a consequence, the event processing will ignore

changes that refer to the lot as a whole. See below.)

• Furthermore, the event carries a transaction reference to the production order.

• The disposition depends on the status of the batch (restricted vs non-restricted).

• Batch attributes like expiry date and manufacturing date are included within the SAP extensions if defined.

However, in case of an event that carries a batch quantity, these attributes are only set in the repository

system if they are initial and not defined yet. Changing the manufacturing or expiry date of an LGTIN is only

possible in case the quantity list carries no quantity and with this addressing a partial quantity of the batch.

Batch Integration Report

If the necessary prerequisites are not met, then the online batch integration will fail. However, the batch still is marked

as relevant for integration and the transaction /STTPEC/INT_BATCH Batches Integration enables you to select these

batches and integrate them as soon as the prerequisites are met. Besides this you can also visualize already

integrated batches. In addition to the standard batch attributes, the report also visualizes the batch extension

attributes such as serialization type, synchronization time stamp and synchronization active checkbox.


Public

71

4 SAP Corporate Serialization Fiori Apps

4.1 Display Serialized Objects

The Serialized Objects FIORI application includes all standard behavior known by Fiori Applications. Serialized

Objects is currently used only for display purposes of the data.

Please be aware that the display of serialized objects is not enhanced for any kind for forward navigation. If you want

to navigate from a serialized object to an event for example this is currently not available.

4.1.1 Setup & Configuration

Ensure that you read the corresponding chapters for setting up and configuring Fiori Application in the administration

guide as well as configuration guide for SAP Corporate Serialization on the SAP Help Portal at

https://help.sap.com/cors.

4.1.2 List Report

The list report displays the same data as Serialized Objects node in the Data Cockpit (see Serialized Objects). You

have the same flexibility as in the Data Cockpit just as a Fiori application.

Figure 7: Display Serialized Objects App – List Report

The List Report page is presented with a couple of filters such as Object Code and Serial Number / Lot. If no filter is

chosen you can get a list of all serialized objects by clicking on Go. A navigation from the list to a detailed view of a

serialized object can be done by clicking on the corresponding row.



Public

72

A detailed explanation of the standard Fiori List Report elements can be found in the Fiori Design Guidelines on the

SAP Help Portal at https://help.sap.com/fiori.

4.1.3 Object Page

The Object Page of the Fiori Application represents the detail view section of the Serialized Objects node in the Data

Cockpit when selecting Serialized Objects. The Object Page shows the details of a serialized objects as well as the

event list, the Object Hierarchy and the related documents.

A detailed explanation of the standard Fiori Object Page elements can be found in the Fiori Design Guidelines on the

SAP Help Portal at https://help.sap.com/fiori.

https://help.sap.com/fiori

https://help.sap.com/fiori

www.sap.com/contactsap © 2021 SAP SE or an SAP affiliate company. 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 SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies. See www.sap.com/copyright for additional trademark information and notices.

https://www.sap.com/copyright

Product Assistance for SAP Corporate Serialization

Documents

Transcript of Product Assistance for SAP Corporate Serialization