Issue

In Syensqo Composite Materials, batch is used to manage/track & trace the individual material items in some business scenarios. This KDD is to assess the option of using SAP serial number to handle the relevant scenarios. 

Decision

Introduce Serial Number (SN) concept and use SN to manage, track and trace the material at the individual item level rather than using batch number to handle the same. 

Background & Context

In Composite Materials GBU, batch number is used to manage the following 2 business scenarios:

1). Sublot Scenario

For example, a Process Order is created in SAP to make the Master Roll, which is a piece of carbon fabric of 1 meter wide x 100 meters long. A SAP batch number, for example MROLL1, is generated and assigned to the Master Roll. Later, another Process Order is created to consume Master Roll (MROLL1) and produce 5 separate pieces. Each is 20 CM wide and 100 meters long. Then another 5 SAP batch numbers are generated to represent sublot rolls as shown below to identify each of the sublots.

2). Non-Sublot Scenario 

For example, 500 liters of a liquid adhesive is produced with SAP batch BATCH1. It's been packed in 5 liter cans. In total, there are 100 cans of  the adhesive in BATCH1. Business may number each individual cans by using unique numbers related to adhesive BATCH1, eg. BATCH1001 for can#1, BATCH1002 for can#2, etc. Those unique numbers look like sub-batch numbers, but they will only be used for physically identify the cans. They are not SAP batch numbers and are not stored in SAP currently. So those sub-batch numbers cannot be used for tracking or tracing. In other words, business can't track & trace each individual cans in SAP at the moment.

Business will print the Master and/or Sub Batch depending on the requirement. Batch numbers are limited to 10 characters. Most are 6+4 or 6+3, but other schemes are also possible.

Assumptions

1. Business needs to track & trace the relevant materials at the individual item level.

Constraints

1. SAP Standard serialization numbering doesn't have straightforward connection with the relevant Batch number. 
2. May have constraints on standard Fiori Apps. => Version to be checked. Alternative: use Fiori GUI transactions such as MIGO to perform goods receipt instead of Fiori Apps such as F3110 - Post Goods Receipt for Production Order (Refer to SAP Notes# 3459964)

   https://userapps.support.sap.com/sap/support/knowledge/en/3459964

Impacts

Describe the impact of the decision on processes, infrastructure, other SAP modules or systems, data cleansing and migration, developments, automations, interfaces, in-flight projects, etc.

1. Impact on Processes
   1. Sublot Scenario

• • • In addition to batch numbers, business will also need to generate and record serial numbers when performing relevant transactions.
    • The numbering of Serial numbers (SNs) will not reflect the connections of master batch numbers. (But SNs will always be associated with relevant master batch numbers). 

1. 1. Non-Sublot Scenario

Business Rules

The decision may translate into business rules which enforce the decision and will require configuration. List these business rules here. For example, "An Outline Agreement cannot be created via the RFQ process. An awarded RFQ can only result in a Purchase Order". 

Options considered

List the options (viable options or alternatives) you considered. These often require a longer explanation with diagrams, or references to other documents (links are best, but attachments are also possible). Use enough detail to adequately explain what you considered so that a project or business stakeholder reviewing this decision will not come back and ask "did you think about...?"; this leads to loss of credibility and questioning of other decisions. This section also helps ensure that you considered enough suitable alternatives rather than just copy/pasting SAP's recommendations.

Option A: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option B: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option C: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Option D: Option Title

Decribe the option in sufficient detail for a reader familiar with the subject matter to understand it properly

Evaluation

Outline why you selected a position. The best format could be a pro/con table (sample below), but is up to you as the author. You must consider complexity, feasibility, cost/effort to implement, but also ongoing operational impact and cost. You must consider the program principles and explain any deviations in detail. This is probably as important as the decision itself.

	Option A	Option B	Option C	Option D
Criterion 1	Pro Con	Pro Pro	Pro Con	Pro Con
Criterion 2	Pro Con	Con	Pro Pro	Con Con
Criterion 3	Pro	Con	Con	Pro

See also

Insert links and references to other documents which are relevant when trying to understand this decision and its implications. Other decisions are often impacted, so it's good to list them here with links. Attachments are also possible but dangerous as they are static documents and not updated by their authors.

Change log

Workflow history