ENTERPRISE FIRST: Global Template

Interface Specification Functional Document

Interface Name: NIS Inbound to SAP - Shipment Contents
Generated Document Name: PBNAW1_MTD_IM_ I002337

Market / Project : PBNA Wave 1

Author : Sumit Talukdar
 ENTERPRISE FIRST: Global Template

1. Document Information

Document Location

Document Name Sol Man Folder Path Document # Solman Link

Revision History
Revision Summary of Changes Revised
Revision Date Project
Number By(GPID/Name)
1 4/21/2021 PBNA Initial Draft 09313022/Sumit
Talukdar
2 07/19/2021 PBNA ADO # 1323992 : xref change for 09313022/Sumit
packaging material E1EDL37- Talukdar
VHILM
3 02/09/2021 PBNA ADO # 1489255 : additional 09313022/Sumit
E1EDL24 segment generation Talukdar
removed

Design Authority Approval Details

Approval Date Approved By

2|Page
 ENTERPRISE FIRST: Global Template

Table of Contents
0. Document Information_________________________________________________________2
Document Location_____________________________________________________________________________2
Revision History________________________________________________________________________________2

1. General Information___________________________________________________________4
2. Desired Functionality / User Story________________________________________________4
2.1 Business Benefits___________________________________________________________________4
2.2 Scope____________________________________________________________________________4
2.3 Solution Details____________________________________________________________________4
2.4 Initiating Process / Process Type / Transaction / Program__________________________________7
2.5 Impact to Markets__________________________________________________________________7
2.6 Translation Requirements___________________________________________________________7
3. Design considerations for Developers_____________________________________________7
4. Integration Impacts___________________________________________________________8
5. SAP Data Archiving Access Requirements__________________________________________8
6. Acceptance Criteria___________________________________________________________9
7. Assumptions_________________________________________________________________9
8. Error Handling/Monitoring Requirement_________________________________________10
8.1 Error Conditions and Logging________________________________________________________10
8.2 Notification______________________________________________________________________10
8.3 Restart / Recovery________________________________________________________________10
8.4 Monitoring Requirements__________________________________________________________10
9. Security Requirements/ Authorization Details_____________________________________10
Process Level_________________________________________________________________________________11

10. Controls Impacts_____________________________________________________________13

11. Issues______________________________________________________________________13
12. Dependencies_______________________________________________________________13
13. Unit Test Plan_______________________________________________________________14
13.1 Key Test Conditions______________________________________________________________14
13.2 Technical Test Conditions – ERROR CONDITIONS______________________________________14
13.3 Risk and Controls Test Conditions__________________________________________________15
13.4 Testing Considerations/Dependencies_______________________________________________15
13.5 Exception and Error Handling Test conditions_________________________________________15
14. Open Points_________________________________________________________________16

3|Page
 ENTERPRISE FIRST: Global Template

2. General Information

RICEFW ID I002337
Short Description NIS Inbound to SAP - Shipment Contents
Process Owner Dawn Wagner / Matt Hantzarides
Implementation Phase PBNA Wave 1
Transaction(s) (if applicable)
Run Frequency Ad-hoc Language English

3. Desired Functionality / User Story

Stock transfer will be required between plants where SAP S4 is deployed in receiving plant but not deployed in
the sending plant. This will be achieved through an interim buy-sell type solution.
When the sending plant runs on NIS legacy system, an interface is required to receive the ASN in receiving
plant.

3.1 Business Benefits

Business will be ale to run uninterrupted while SAP S4 will be rolled out to different plants in phased manner.

3.2 Scope
This document describes the inbound interface needed to capture ASN from NIS system. This Document
covers all messages for inbound delivery or ASN coming from NIS to SAP S4.

3.3 Solution Details

Data Source
System:
NIS

Data Target
SAP S/4HANA
System:
Direction X Inbound Interface data flows inbound to SAP R/3
(with Outbound Interface data flows outbound from SAP R/3
respect Other Specify:
to SAP R/3)

4|Page
 ENTERPRISE FIRST: Global Template

One-way transfer of “accumulated” data set; Usually done

Batch
by scheduled file transfer.
Near Real- One-way message-based transfer of data; Usually
X
Time triggered by event.
Interface Immediate transfer of small data set; Usually triggered by
Real-Time
Type event.
Manually invoked from SAP session; Local spreadsheet
Excel Upload
file uploaded from PC.
Other Specify:

Hourly Details:
Daily Details:
Weekly Details:
Monthly Details:
Interface Quarterly Details:
Frequency Yearly Details:
How
X On-Demand 15 minutes
often:
Other Specify:

Full record load Send all records every time interface is executed
Delta full Only send records where one or more fields have changed
Type of records since previous execution
Records Only send fields (and keys) that changed since previous
X
Sent Delta records interface execution
Other Specify:

Volume
Peak Volume – 100 KB per execution (~1000 records)
(per single
Average Volume – 50 KB per execution (~600 records)
execution)

1. Quality of Legacy Data: ( ) Good. ( ) Average ( ) Poor ( X ) N/A

2. Complexity of Legacy Data: ( ) Simple ( ) Average ( ) Complex ( ) Extra-complex ( X )N/A
3. Complexity of a Manual Input: ( ) Simple ( ) Average ( ) Complex ( X ) N/A
4. Number of SAP Screens: N/A

5|Page
 ENTERPRISE FIRST: Global Template

High Level Process Flow:

Legacy Shipping to S/4 (S/4 Receiving via PO) – Non-Deployed to Deployed

Start Here BOL Updated Avail is Update 16 is not

Avail

Avail Generates / BOL updated with required if 14

with ASN Sets BOL to
Updates BOL S/4 PO # Ref is updating
Shipped Complete
Avail already

6 8
Voice/
WMS

Pick, Pack and Data

14
1 to 16
Ship
ETMS
5 7
2 9 13
NNIS BOL
updated with S/4 NNIS BOL ASN NNIS BOL 15
NIS

updated and on NNIS BOL Closed

NNIS BOL Created PO # Ref and Updated Recv’d
transport after 48HR rule
Released to 12 by Whse
Warehouse
PTP S/4

PO
Purchase Order 10
Acknowledgment
Created/Updated
4 with S/4 PO #

3
Receiving
MTD S/4

Location

Inbound Delivery Inbound Delivery 11

for PO updated Receipt
Created for PO Completion
with ASN

Data setup considerations? LMP Ship Lanes? Unmatched Shipper Process? Legacy to S4 Buy / Sell Model
RTR requirements intercompany JE + 7% COGS markup shipper?

Interface Process flow diagram (Step #10 in above diagram):

SAP
Inbound Delivery updated
PI/ Shipment Details against
PEPSICO with Shipment details PO Bill of Lading
NIS
SAP

Transmission failure:
IDOC should update - Standard error Transmission failure:
the inbound delivery handling at SAP
PI/PO
 Standard
that is already created error
in S4 system (in Step - Re-transmission
handling at
#3 above) of the failed item.
NIS
- .

Field mapping sheet:

FMD_NIS_Inbound_V FMD_NIS_Inbound_V
7.xlsx 8.xlsx
SAP PO will fetch the data from Staging table PEPSI.BOL_NIS_LTTS_PROC_HDR for header and
PEPSI.BOL_NIS_LTTS_PROC_DTL for detail and post IDoc (DELVRY07) in SAP S4 HANA.

o SAP PO Extract Logic – Query the PEPSI.BOL_DSPTCH_PROC_HDR Table for any rows with
NIS_PROC_FLG = 5.  If any rows are returned, extract the ASN data for each BOL into S/4.

6|Page
 ENTERPRISE FIRST: Global Template

o SAP PO Update Logic – Based on the result of the prior query (say 4 BOLs have an
NIS_PROC_FLG = 5), once SAP PO has processed the BOLs and created IDOCS for posting into
S/4, the NIS_PROC_FLG needs to be updated to value 15 for any BOL ASN data retrieved
from NIS (in this case 4 rows, one for each BOL, will be updated to 15) to prevent re-
extraction to S/4.

3.4 Initiating Process / Process Type / Transaction /

Program
The scenario is relevant when the stock is transferred from NIS system (in non-deployed plant) to SAP S4
system (deployed plant). This interface is triggered when NIS sends the shipment details against the Bill of
Lading to S4 system. An IDOC is posted in S4 system at this time.

3.5 Impact to Markets

This is an interim solution to enable stock movements from non-deployed plants to deployed plants.

3.6 Translation Requirements

N/A

4. Design considerations for Developers

1. IDoc message type DESADV will be used for updating the inbound delivery.

IDoc Type/ Extension FSHGMCR01

Message Type WHSCON

IDOC Type DELVRY07

Process Code Custom

Port TBD

Partner Type LS

Partner No TBD

Partner Profile NIS

Direction Inbound (02)

Message code
Message Function

A new Function Module needs to be developed and tagged to a new process code for posting this IDOC. The
function module should have the following logic inside it, in addition to the standard posting logic.

ABAP Logic for IDOC field Derivation

Functiona IDOC Segment

l Name Table Field Segment Field
Name Name Name Name ABAP Logic
HU VEKP EXIDV & E1EDL37 EXIDV EXIDV will not accept alphanumeric LPN number as HU

7|Page
ENTERPRISE FIRST: Global Template

Functiona IDOC Segment

l Name Table Field Segment Field
Name Name Name Name ABAP Logic
number as per the system set up. Hence, populate the LPN
Number number coming in the IDOC in EXIDV field to VEKP-EXIDV2.
(EXIDV
and The HU number VEKP-EXIDV should be populated with the
EXIDV2) & smallest free number in the ‘external’ number range of the NR
EXIDV2 E1EDL44 object HU_VEKP (external number range only).
The Bill of lading number (E1EDL20-BOLNR) should be
searched in PO header (EKKO_IHREZ). Note this PO number.
Then find the Inbound delivery number corresponding to this
PO.
Delivery
Error Handling: If more than one PO from same supplier
Number
(EKPO-LIFNR) with same BOLNR is found, the IDOC should
get failed with appropriate message in the status for trouble
shooting.
LIKP VBELN E1EDL20 VBELN
In the inbound delivery determined as above, find the item
number that corresponds to the material (E1EDL24-MATNR).
Delivery
Item Note: If there is a batch split (meaning, more than one batch
Number specified for same line item, then the POSNR should be of the
pattern 90000* and original line item number should be
LIPS POSNR E1EDL24 POSNR populated in E1EDL24-HIPOS field of IDOC)
 For this segment, batch number is to be derived as
per the intelligent batch design logic specified in
WRICEF E000340. Use Production date from LPN
no for this purpose.
o For each Item, supplier batch number is
specified in E1EDL24-LICHN. Derive
production date using 3rd to 7th char of
LPN numberLICHN.
o If E1EDL24-LICHN is not populated, use
Batch system date as production date.
Number o The last 2 char of the batch number
should be first two char of the supplier
name in uppercase.
 If this SAP batch (CHARG) does not exist for the
material and plant, then create this batch (for the
material and plant).
 Shelf-life expiry date of the batch must be calculated
from the production date and the shelf life
maintained in material master. This calculated SLED
LIPS CHARG E1EDL24 CHARG must be updated in the newly created batch.
 For this segment, batch number is to be derived as
per the intelligent batch design logic specified in
WRICEF E000340. Use Production date from LPN
no for this purpose. LPN number is populated in
each parent segment field E1EDL37-INHALT for a
given E1EDL44 segment.
o Derive production date using 7 to 11 char
of LPN number.
o If LPN number is not populated, use
Batch system date as production date.
Number o The last 2 char of the batch number
should be first two char of the supplier
name in uppercase.
 If this SAP batch (CHARG) does not exist for the
material and plant, then create this batch (for the
material and plant).
 Shelf-life expiry date of the batch must be calculated
from the production date and the shelf life
maintained in material master. This calculated SLED
VEPO CHARG E1EDL44 CHARG must be updated in the newly created batch.
 This will be the POSNR of E1EDL24 found by
Delivery matching the supplier’s batch number mentioned in
Item E1EDL24 (E1EDL24-LICHN) with the batch number
Number of E1EDL44 (5th to 12th char of E1EDL44-EXIDV)
LIPS POSNR E1EDL44 POSNR

8|Page
 ENTERPRISE FIRST: Global Template

5. Integration Impacts
Buy-sale / stock transfer between non-deployed and deployed sites.

6. SAP Data Archiving Access Requirements

Data Archiving Data Archiving is the process used to delete data that is no longer needed
from online database and storing same in an external storage that allows
for data retrieval and analysis when need be. 
Data that have been archived cannot be changed/updated.
Residency Time The period of time that the document is stored in the online database
before the document can be archived. Usually, the archiving process
checks the last changed date to calculate the residency time.
Retention Time The total period of time that a document exists in the online database +
archived storage until it is required to be destroyed. From document
creation to document’s end-of-life.

1. Will access to data older than 2 years be required? YES No

2. If YES to question 1:

a. Will the data older than 2 years need to be updated. Why? What process would
require this update, please specify?

b. Please specify reason / explain the need for these data required? Please check all that
applies.

Legal requirement:
Explain: ______________________________________________________

Business
Explain: ______________________________________________________

Tax
Explain: ______________________________________________________

Audit
Explain: ______________________________________________________

Others: Specify ________________________________________________

Explain: ______________________________________________________

9|Page
 ENTERPRISE FIRST: Global Template

3. Please indicate the type of data used in this FSD

Shipments Shipment Costs

Deliveries SD Billing documents
Sales documents Material Documents
Purchase Orders Purchasing Requisitions
Financial Documents Material Ledger
COPA Handling Units
Others:
please specify _Inventory stock data per valuation area (Plant)____

Comments/Notes






7. Acceptance Criteria
1. As specified in section 3.

8. Assumptions
1. BOL number is saved in PO header.
2. Handling units coming from NIS are not ‘nested’.
3. NIS only ships in Case quantities
4. One inbound delivery will not have the same material repeated in more than one line item.
5. At the time of writing this specification, the design of NIS for this interface is not completed.
Hence there might be some fine tuning / retouch of this document when this NIS design part
is completed.
6. xREF table will be leveraged to map NIS pallet types with SAP S4 Packaging material
7. Lot No / Batch: If the material is batch managed, then providing Batch number is mandatory. Hence, if
Supplier Batch number information does not come from NIS system (like when Pallet is not a full-
pallet), SAP will create a new batch number and assign to the item.
Note: If NIS cannot provide production date / best before date, then receiving date will be taken as
production date (as decided during E001716- RF receiving WRICEF)

9. Error Handling/Monitoring Requirement

9.1 Error Conditions and Logging

In the case of an error in posting IDOC, fail the IDOC and show the appropriate error message in
the IDOC status. This will enable us to troubleshoot.

10 | P a g e
 ENTERPRISE FIRST: Global Template

9.2 Notification
Error How error message should be Error Messages Corrective action
reported

9.3 Restart / Recovery

N/A

9.4 Monitoring Requirements

Standard S/4 HANA interface monitoring should be used as well as the middleware monitoring tools.
IDOC log report needs to be checked daily.
No additional error handling needed. SAP standard error handling is sufficient – IDoc List Tcode:
WE05.
All segments that in error must appear in red font in WE05
If required, he can make changes on the segment and then reprocess the IDOC successfully via
BD87

10. Security Requirements/ Authorization Details

Certain PepsiCo Users will need to have access to reprocess IDOCs and monitor IDOCs list:
 WE02/WE05
 BD87
 WE09
 In case of error, necessary data correction needs to identified and reported to authorized body –
to process the corrected IDOC. In case of automation, next iteration of IDOC processing batch job
should pickup the corrected IDOC and reprocess.
RICEF is used to update, display or print data? Please capture the details here:
X Update
Display
Print
All

Please indicate which SAP module the RICEF applies to.

Module Check (X) Module Check (X)

MM x PP
WM X FI
SD CO
PM BI
XI Security
Master Data ABAP
Other Please Specify

Please indicate which scenario, process and process steps the RICEF impacts since the BPML will be
updated in line with the security change.

11 | P a g e
 ENTERPRISE FIRST: Global Template

rocess Level Description

Scenario
Process
Process Step(s)

Please give a brief description of the functionality the RICEF is used for?

This WRICEFF enables the transfer of stock from NIS supported plant to S4 plant

RICEF needs additional authorization checks on already known organizational levels (e.g. company
purchasing organization, plants etc.)?

X Yes
No

When answer yes, the following organizational levels need to be checked:

Organizational levels Check (X)
Company Code
Cost Center
Profit Center
Sales Organization
Purchasing Organization
Plants
Other Please Specify

Note: In case of additional control at Org level in future, Pep IT Governance team to define the rule.
To be filled by Security Team / Development Team

Additional security requirements needed? (to be filled by security)

Yes Proceed in filling the requirements – Developers to implement security requirements
No No further information needed – No implementation of additional security requirements needed.

Information for developer to implement security requirements in RICEF:

Authorization group to be assigned to report / program (to be filled by developer)

RICEF is started by using an SAP transaction (to be filled by developer)

Custom SAP Transaction Name:
None
Transaction type (only to be filled when transaction is used)
Report transaction
Parameter transaction

12 | P a g e
 ENTERPRISE FIRST: Global Template

Does the report call another custom or standard transaction? (to be filled by developer)
Yes Name:
No

RICEF needs to have additional authorization checks included? (to be filled by security)
Yes Organizational segregation needed – e.g. Report is able to access data from all market units
No Organizational segregation not needed – e.g. Report only handles market unit specific data

When answer is yes, please implement the following authorization check in the RICEF before any
data is displayed or manipulated:
Authorization object Authorization field: Authorization values

Information for security to setup relation between transactions and implemented authorization
checks:

RICEF is using standard components and already has included authorization checks? (to be filled by
developer)

Yes Includes standard components with standard authorization checks

do not include standard authorization checks or is called by standard
No transactions.

When answer yes, the following authorization objects need to be maintained in SU24:
Authorization object Authorization field: Authorization values

11. Controls Impacts

Standard interface controls should be used to ensure accuracy, completeness, and duplicate record
controls.

12. Issues

Issue Date Issue Description Issue Resolution

# Raised
1 04/21/2021 Production date, best-before date or Shelf-life expiry date is
not sent by NIS

13 | P a g e
ENTERPRISE FIRST: Global Template

Issue Date Issue Description Issue Resolution

# Raised
2 04/26/2021 It is not clear what batch number / lot number will be sent
by NIS and how that will be processed in SAP
3 04/26/2021 It not clear at the moment whether the SSCC number or
LPN number should be mapped to the SAP Handling Unit
number
4 04/26/2021 It is not clear at the moment whether PALLET TYPE is the
right source field to map to SAP packaging material.

13. Dependencies
 This object is dependent upon E000340 - SAP Intelligent batch design.
 xREF table will be leveraged to map NIS pallet types with SAP S4 Packaging material
 The Production date, Best before date or Shelf-life Expiration date need to be received
from NIS. This information will be known when the NIS part of the interface will be
designed.

14 | P a g e
 ENTERPRISE FIRST: Global Template

13. Unit Test Plan

14.1 Key Test Conditions

Test Step Step Description Test Data Expected Result Actual Result Executed Remarks
Condition By/Date
1 SAP S4 receives IDOC The IDOC should post
with all correct data and all the relevant fields
(Happy Path) in the inbound delivery are
updated correctly.
2 SAP PO sends file with IDOC should fail.
formatting error Standard error message
would appear in the
status.
3 SAP batch (CHARG) Batch number is updated
exists for combination of in the inbound delivery
PO, supplier number and
Supplier batch number
(LICHN), then update
E1EDL24-CHARG with
existing SAP batch.

4 No SAP batch (CHARG) New batch is created and

exists for combination of this new batch number is
PO, supplier number and updated in the inbound
Supplier batch number delivery
(LICHN).

14.2 Technical Test Conditions – ERROR CONDITIONS

Test Step Step Description Test Data Expected Result Actual Result Executed Remarks
Condition By/Date
1 Multiple PO found from IDOC should error out.
same supplier with same The message in the IDOC
Bill of Lading number status should describe this
error cause.
 14.3 Risk and Controls Test Conditions

Test Step Step Description Test Data Expected Result Actual Result Executed Remarks
Condition By/Date
1

14.4 Testing Considerations/Dependencies

14.5 Exception and Error Handling Test conditions

Exception - special logic or exceptions (e.g. do not process Government Markets customers, only process pre-packs)

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition

Error Handling - functionality in case of errors (e.g. Customer not found, Record already exists)

Test Step Step Description Test Data Expected Result Actual Result Executed By/Date Remarks
Condition

14. Open Points

16 | P a g e