Stock Reconciliation Report

HAND OVER Stock Counts 2024

EXCELLENCE SIMPLY DELIVERED

1
Introduction

• The stock snapshot is an interactive report that provides the

business with a view on stock on hand between KNAPP and S/4
Hana. There are different processes to be triggered to get to the
end result.

• Also , during a stock count that will be done for a DC in KNAPP,

preparation must be done up front and a stock reconciliation
report MUST balance 100% before handing over to the team who
is doing the stock count.

• The process involves a snapshot taken within a time of what the

KNAPP system has and what S/4 Hana has and throws it into a
report for a comparison.
EXCELLENCE SIMPLY DELIVERED
2
To Note:

• Before the results are on the stock snapshot report, a stock on

hand request must be triggered in S/4 and sent through to
KNAPP.

• Once this is executed from S/4 , an interface is triggered via the

Proxy to CPI and then sent to KNAPP

• When Knapp receives this instruction, they drop a file off for that
instance onto the relevant KNAPP server.

• CPI will then pick this file up and start processing into S/4, this
will take around 5 to 10 minutes. You can monitor this process
via the SRT_MONI if successful or not.

EXCELLENCE SIMPLY DELIVERED

3
Process Steps

Step One Trigger Request To KNAPP

Transaction code ZSOH_REQUEST

The organizational structure to be used will be the one intended for the
snapshot. See print screen as below:

When you see that message, 1 record sent to CPI via a proxy, then go to
transaction code and step two below.

EXCELLENCE SIMPLY DELIVERED

4
Process Steps

Step Two Web Service

Transaction code SRT_MONI

You can see if the file you just executed has successfully left the S/4
system. These are the 2 variants; the first one is the STOCK on hand
request, and the second is when the files come back into S/4 from
KNAPP via CPI. Always check these to confirm all files are back in
before we run the reports.

EXCELLENCE SIMPLY DELIVERED

5
Process Steps
Step Three Stock Reconciliation
Transaction code ZMM_STOCK_RECON

When all files have come into S/4 , you can start running the stock
reconciliation report. Once you download each of the options below, then you
need to send through to Edward the three report options available for each DC
as shown below:

EXCELLENCE SIMPLY DELIVERED

6
Process Steps
Step Four Stock adjustments
Transaction code ZMM_STOCK_RECON

We still on the same transaction. The last option (Stock Alignment)

must be used to adjust stock. Click on this option and Execute:

EXCELLENCE SIMPLY DELIVERED

7
Process Steps
Step Four Stock adjustments
Transaction code ZMM_STOCK_RECON
• FFD – Flagged for deletion checkbox, if no checkbox, no need to select, few of
these will exist. This will have to be done manually and recorded.
• BATCH- See a checkbox , means there is not batch against this material and we
would be required to create a new batch before as can adjust.
• ALIGN – Lastly, we click on select all align and then click on post.

EXCELLENCE SIMPLY DELIVERED

8
Process Steps
Step Four Stock adjustments
Transaction code ZMM_STOCK_RECON
NB: Before doing the stock recon again from step one, two and three, the restricted
stock will not be adjusted via the report. This will need to be done manually and
hopefully business together with SUPPORT can sort out before stock count is
performed.
It will be advisable to resolve differences between restricted stock before the actual
day of the count from business and support, but if not done, then stock MUST be
adjusted manually before the next SOH request is sent through.

MIGO must be used to manually balance back to KNAPP.

Important Note:
Please check that you have access to all these transactions before
you support the count.

EXCELLENCE SIMPLY DELIVERED

9
Process Steps

ONLY, once all batch creation is done, we can start with execution of the adjustments.
An indication will also be the “check boxes” been selected for the stock alignment
column. Click on “post align stock” the system will start posting the adjustments via
idoc creation. You can see this on WE02.

We would now be required to start the reconciliation process again and

MUST balance between the systems before we notify Edward that the business
can start with their stock count.

Follow steps one, two and three as above again.

EXCELLENCE SIMPLY DELIVERED

10
Additional Notes

When the count has begun, the messages will start to post into S/4 via
idocs. WE02 must be monitored to check if there are any failures.
Error idocs must be processed, also check why they occurring and notify
the team (Edward L and or Eugene G) from business.

NB: Lastly, before DD can close of on their end, another balancing act of
stock on hand must take place before handing over to business to start
trading again.

If all idocs are posted successfully, this reconciliation should not take to
long. There could be discrepancies though. Once again, when recon is
done notify Machiel or Edward for business to start trading.

ONLY, once all batch creation is done, we can start with execution of the
adjustments. An indication will also be the check boxes been selected for
the stock alignment column. Click on “post align stock” the system will
start posting the adjustments via idoc creation. You can see this on
WE02.

EXCELLENCE SIMPLY DELIVERED

11
Technical Additions

An ABAP Proxy is used for the integration here: to connect and send
data from SAP ECC to XI system with out sender communication channel.

Proxy Name: SOH_Request_MT

EXCELLENCE SIMPLY DELIVERED

12
Technical Additions

An ABAP Proxy is used for the integration here: to connect and send
data from SAP ECC to XI system with out sender communication channel.

Proxy Name: Stock Recon

EXCELLENCE SIMPLY DELIVERED

13
SAP Custom Tables

Tables Used for this process

Table Name Description Comments
ZMM_STCK_RCN_HDR KNAPP 3IS Inventory Snapshot Header Values for KNAPP
ZMM_STCK_RCN_ITM KNAPP 3IS Inventory Snapshot Item Values for KNAPP

ZMM_STCK_RCN_MCH SAP MCHB Batch Stock Snapshot Values From S/4

ZMAIN_PARAMETERS Maintain parameters for constants Used for SOH Request
ZMAIN_PARAMETERS Maintain parameters for constants Mapping Stock Types

The KNAPP and SAP Tables are what is used for the snapshot. When the
files come into SAP, we process and update these tables to run the
snapshot between the systems. These are the first three above.

EXCELLENCE SIMPLY DELIVERED

14
SAP Custom Tables

The parameter table is a constants table used to drive certain logic in the
program. This first one is to drive the stock on hand request.

Parameter Type = IN18

Filed Name = STOCKOWNER
Field Constant = plant number
Text = Stock Owner

EXCELLENCE SIMPLY DELIVERED

15
SAP Custom Tables

The parameter table is a constants table used to drive certain logic in the
program. These values are to drive and map the stock types in KNAPP
and SAP. This one depicts that Both stock are on QI inspection

Parameter Type = KNAPP_IN

Filed Name = STOCKQTY
Field Constant = QUARANTINESHORT_DATE
Text = QUALITY

EXCELLENCE SIMPLY DELIVERED

16
Re-cap Summary

• A stock on hand request must be triggered from S/4.

• Stock files will trickle back into S/4 from CPI.
• Run stock reconciliation reports and send through to Edward.
• Adjust all stocks before trigger of new snapshot.
• Once all files are in, check and no stock discrepancies must be
on the report.
• Once no discrepancies on the report, Notify Edward and send all
options from report again.

Final:
When stock is finally done, reconciliation must be done again and no
discrepancies on any DC, adjust stock if any found.

END of process

EXCELLENCE SIMPLY DELIVERED

17