Object Specification

SAP Enhancement
Functional
OSD_OTC_E01_3.3.5
Picking Door stocks
Table of Contents
1. VERSION CONTROL..........................................................................................................3
2. SIGN-OFF..............................................................................................................................3
3. CONTRIBUTORS AND PARTICIPANTS........................................................................3
4. REVIEWERS.........................................................................................................................3
5. OBJECT REQUIREMENT SUMMARY...........................................................................4
5.1. OBJECT INFORMATION AND ATTRIBUTES........................................................................4
5.2. REQUIREMENTS SUMMARY AND BUSINESS DRIVER........................................................5
5.3. CURRENT FUNCTIONALITY...............................................................................................6
5.4. REQUIRED FUNCTIONALITY.............................................................................................6
5.5. ASSUMPTIONS...................................................................................................................6
5.6. PROJECT / DEVELOPMENT CONSTRAINTS........................................................................7
5.7. PERFORMANCE CRITERIA.................................................................................................7
5.8. OTHER OBJECTS AFFECTED.............................................................................................7
6. DETAILED ENHANCEMENT SPECIFICATIONS........................................................8
6.1. RICEFW TYPE SPECIFIC INFORMATION – ENHANCEMENT.............................................8
6.2. ERROR HANDLING..........................................................................................................14
7. ADDITIONAL INFORMATION.......................................................................................15
7.1. UNIT TEST PLAN............................................................................................................15
7.2. INFORMATION SECURITY................................................................................................15

2
1. VERSION CONTROL
Date Description of Change Owner Version
23-10- Rupesh
Initial Creation for CR-DTS-041 1.0
2020 Ramamurthy
23.10.202 Shyam
Update of the CR-DTS-041 1.1
0 Angara/Venkata

2. SIGN-OFF
Role Name Signature
Corbion WS Lead Robert Lundgren
Rupesh
Capgemini Sap Teamlead
Ramamurthy

3. CONTRIBUTORS AND PARTICIPANTS

Role Name
Shyam Angara
Capgemini consultant
Venkata Kaja

4. REVIEWERS
Role Name Status Date
Reviewed
Integration Management Westdijk, Hans

5. OBJECT REQUIREMENT SUMMARY

5.1. Object Information and Attributes

The following is current information about this object and document:

Object ID OTC_E01_3.2.5
Title Picking and Goods issue of stocks at Door

3
Team Which OTC
Owns the Object
System Version S4HANA
Development Enhancement
Type
Estimated L(Low), M(edium), C(omplex) or VC (very complex) – From RICEFW
Complexity Justification
Link to Process This functional enhancement is connected to EWM Storage BIN
Flow stocks to Pick and perform goods issue.

4
 5.2. Requirements Summary and Business
Driver
Requirements

The new way of the picking will be required in Corbin for all the below mentioned four
Scenarios.
The Custom Pick Strategy should be applicable only for the Below Scenarios,

i) DTS.053_EWM Shuttle truck process

ii) DTS.094_EWM_Inter-company replenishment with Push PO/ SO
iii) OTC.105 - EWM_MTO - Packed Product - GR in Warehouse (Incl Putaway)
iv) OTC.109 - EWM_MTO_with_Direct delivery_Replenish

 As the pallets (Handling units) are loaded into the truck already, we need to make sure
that exactly these handling units are 'Picked' and 'Goods Issue' to the stock transfer
order or outbound deliveries.
 The best option is to create an auto-picking strategy where the system recognizes the
HU that belong to a specific shuttle truck.
 The shuttle truck is recognized by the Loading door.

Business Driver

The Text Object Configured at S4ERP will be configured the same in SAP ewm so the door bin
information will be entered manually in the S4 ERP Purchase order/outbound delivery text
objects and the same door bin information will be displayed in the ewm outbound delivery.

Based on the Information that gets displayed in the EWM outbound delivery/PO/Outbound
delivery the system will pick the inventory only from that door mentioned in the text object.

Get the EWM Outbound Delivery from the table /SCDL/DB_PROCH_O and pass the Document
number and get the Document GUID from the above table.

Once we get the DOC GUID number pass the information to the table /SCDL/DB_REFDOC and
get the ERP/PO ref doc categories.

Get the Door Bin Information from the ERP purchase order header text (PICKING
DOOR)/outbound delivery header text (Picking Door)/EWM outbound delivery text (Picking
door) pass this Door information to the EWM table.

5
Door Bin Information should be Provided to the Table /SCWM/LAGP, Pass the information like
warehouse Number (X312/31G1/34M1) and the Storage BIN which we will get from the
Delivery Header Text Object.

5.2.1 Alternatives to Object

N/A

5.2.2 Impact of Implementation

Incorrect Picking Strategy will be proposed by the system when picking based on loading door
performed in Corbion.

5.2.3 Impact of No Implementation

Correct Picking Strategy will be proposed by the system when picking based on loading door

5.3. Current Functionality

No Current Functionality Available in Standard SAP for picking based on Door

5.4. Required Functionality

DTS.053

The STO text ( Picking door) with Door bin (917.D00R.XX) info will be passed on to the ERP
Delivery and then to the EWM outbound delivery text ( Picking door) with Door bin
(917.D00R.XX) will then be used for the determination of Door for picking the entire stocks in
the Door for CGM Shuttle scenario.

6
DTS 094
The YIC Intercompany purchase order-> Sales order ERP Delivery text ( Picking Door) with
Door Bin (917.DOOR.XX) will be passed on to the EWM outbound delivery text ( Picking door)
with Door bin (917.D00R.XX) will then be used for the determination of Door for picking the
entire stocks in the Door for CMO Shuttle scenario.

7
 OTC.105
The MTO Packed Product for Sales order ERP Delivery Text( Picking Door) with Door Bin
(917.D00R.XX) will be passed on to the EWM outbound delivery text ( Picking door) with Door
bin (917.D00R.XX) will then be used for the determination of Door for picking the entire stocks
in the Door (Truck Trailer to customer).

OTC .109
The MTO Direct delivery for Sales order ERP Delivery Text (Picking Door) with Door Bin (917-DOOR-XX)
will be passed on to the EWM outbound delivery text ( Picking door) with Door bin (917.D00R.XX) will
then be used for the determination of Door for picking the entire stocks in the Door (Sea Container to
Yard).

8
 5.5. Assumptions

Business user will enter the correct Material + Quantity in the STO or Purchase order or ERP
Outbound Deliveries. If the quantity goes wrong from the Trailer/Shuttle/Container vs Goods
issue document, then the reversal of the documents should be done manually. It is
responsibility of the user to perform the correct Goods receipt into the Doors as the System will
pick the contents of the Door Bin with Material/Batch/HU/Quantity.

User will enter the Door bin information in the STO or ERP outbound deliveries to have the
automatic picking to be performed in the SAP EWM.

If No door information is entered in the deliveries the system will not have the Custom strategy
determined .

5.6. Project / Development Constraints

No constraints

5.7. Performance Criteria

Performance Requirements for Enhancements
Average Frequency: <Number> Per <Year, Month, Day, Hour, Minute,
Second>. <If applicable, explain how
this will change over time.>
Frequency per Peak: <Number> Per <Year, Month, Day, Hour, Minute,
Second> <If applicable, explain how
this will change over time.>

9
 Performance Requirements for Enhancements
Availability: <24/7>/<1
2/6>
Expected Average
Response Time:
Expected Peak Response
Time:

5.8. Other Objects Affected

Object Impact/Change Description

10
 6. DETAILED ENHANCEMENT
SPECIFICATIONS
6.1. RICEFW Type Specific Information –
Enhancement

Enhancement Details (if applicable)

SAP Transaction Code < Transaction Code which will be modified>
Menu Path <Menu path used to modify the transaction>
User Exit Name/BADI/New <Name of the program which will be modified>
BADI
SPOT <Name of the spot which will be modified>

Enhancement Requirements
Number Description of Requirement
1. Custom Pick Strategy need to be proposed based on the EWM Outbound Delivery
Text Information

11
6.1.1 Selection Criteria/Screen
Refer 6.1.3
N/A

Type of Fields
Field Search Grouping
(Check Box Help / /Frame
/ Radio Pick Validati name
Button / List / on (Mandat
Selection Select- List of Require Defaul ory / Single/Multiple/R
Field Text / Option / values d t Optional ange/all possible
Name Description Parameter) (Y / N) (Y / N) Value ) combinations

6.1.2 Enhancement – Screen Layout (N/A)

<Insert the Screen Print of the GUI>

12
Enhancement – Screen Layout (N/A )

Number of Source Table Field Field Conditions / Default Value If Rea Field Len Inpu Mandat Form Validation
the field on Of Data Name Name Description Data Retrieval Not Given d Type1 gth t or ory or attin s / Error
the attached For Logic Onl Outp Option g Messages
Form Layout Field y? ut? al? Rule
s
<Table / <Field Label <Zero, Spaces, Null <Y/ <See <$ZZ  <Valida
Field or – Description Values, Value> N> list ,ZZ9. tion,
calculati of field> below> 99, ”Error
on or MM/D Messag
transfor D/YY e”>
mation> Bold,
Color
s>



Event Action Matrix

Event Action Updates That Occur When This Event Is Initiated
<Description of Event (i.e. Save <Description of the event – details about <List of tables / fields created, deleted, or updated when this event occurs.>
button is clicked)> how the screen responds when the event
occurs.>

1
Note: Field Type “TB” = Text box; ”LB” = List box; “DL” = Dropdown listing; “CB” = Checkbox; “”RB” = Radio Button

13
6.1.3 Enhancement – Additional Processing Logic

14
 7. ADDITIONAL INFORMATION

7.1. Unit Test Plan

shuttle truck.xlsx

7.2. Information Security

7.2.1 Information Classification

General Information

Businesses Impacted:
Information Classified by Date
whom:
Contact Information
Company Name Phone E-mail Address
List Potential
Information Owners:
Architecture
Development Test Training
Environments: (impacted by this Fspec):
Production
Public (Internet) Facing Internal Only
Architecture: (system exposure): 3rd Party Hosted Company *
Hosted

Identity & Access Management

During Project Offshore? List the 3rd
3rd party system access Yes Yes Parties:
required? No No
Post Implementation Offshore? List the 3rd
3rd party system access Yes Yes Parties:
required? No No
Business Impact Analysis
What may be impacted if the system or information/data is compromised? Check all that
may apply.

15
 Brand Reputation/Trust Regulatory
Associate Relations Compliance
Competitive Advantage Securities & Exchange Commission (SEC)
Financial Impact Payment Card Industry (PCI)
Productivity Sarbanes-Oxley (SOX)
Supply Chain Privacy Laws
Contractual (i.e. NDA’s, MSA’s)

Input any additional details related to business impact in the event of compromise:

Information Classification
Action #1: Check the box below that represents the most restrictive
classification.
Action #2: If Level 1 or 2 is selected, check the box below indicating data storage
or data transmission.

See “Information Classification, Labelling and Handling” in Client A’s ISC

Standards for details on the formal classifications and data handling standards.

Information has been defaulted to level 3. Please review and update in

collaboration with the security team

16
 Level 1 – Confidential – Secure Handling Required “SHR”

Confidential – Secure Handling Required represents the most sensitive data classification
related to individual personal identifiable information and personal financial account information.
This information considered critical to Client A such that, if disclosed, may disrupt or impede
business operations, and due to legal, reputational, or operational concerns, requires additional
security controls. Information in this category includes, but is not limited to:
1. Social Security Number
2. Driver’s License Number or Government-issued Identification Number
3. Financial Account Number (card number or personal bank number)
4. Protected Health Information & Electronic Protected Health Information

SHR data stored? SHR data transmitted? SHR data stored and transmitted?

Level 2 – Confidential

Confidential represents the second most sensitive data classification related to operationally
significant business information. This information considered critical to Client A such that, if
disclosed, may disrupt or impede business operations. Examples of Restricted Confidential include
but are not limited to regulatory governed data, trade secrets, mergers and acquisition discussions,
product formulas and designs, corporate earnings data prior to public announcements,
reorganization details prior to announcements, current/closed company investigations and litigation,
detailed network diagrams that could jeopardize network security, strategic development/marketing
plans and information integral to the success and operations of the company.

This includes: Pre-release aggregated financial data relevant to U.S. Securities and Exchange
Commission oversight; Client A’s own commercial bank account numbers (i.e. where Client A makes
deposits, pays checks and executes ACH transfers for their own account)

Confidential data stored? Confidential data transmitted? Confidential data

stored and transmitted?

Level 3 – Internal Client A Use Only

Internal Client A Use Only represents the third most data. It represents information that is less
critical to privacy and business operations but still must not be publicly disclosed. This information is
not approved for general circulation outside Client A.

This includes most transactional financial information.

Level 4 – Public

Public represents information that has been declared public knowledge by the information owner
and can freely be given to anyone without any possible impact to Client A. As a result, no special
data handling protections are required.

7.2.2 Security Roles (Profiles and Authorizations)

17
 Security Requirements for Enhancements
Security Type Role Access Allowed
Screen Level <BPP Role 1> <read, read/update>
Security <BPP Role 2>
Field Level <BPP Role 1> <List restrictions on the fields on the form
Security <BPP Role 2> that individuals with this role can either
see. The fields like SSN number, Credit
Card number, etc that has sensitive
information need to be listed with the kind
of access for query, display and print.>
Button Security <BPP Role 1> <Any restrictions on the buttons that
<BPP Role 2> someone with this role can either see
and/or invoke>
Data Security <BPP Role 1> <Any restrictions on the data that someone
<BPP Role 2> with this role can either see and/or update>

7.2.3 Audit

Audit Trail Requirements

Audit Event Description Audit Trail Updates
<Event which <Description> <Audit message / fields audited>
causes the need
for an audit trail;
e.g., data is
changed>

18