7 STEP TRACKING SUMMARIES
Problem Number
Problem Title:
Business Impact:
Impacted Location(s)
(e.g. Global, Region, Country, Site)
Impacted Business Unit(s)
Impacted Service Tower(s)
Name of Impacted Application/
Infrastructure/
Services
(Indicate if Critical Set)
Number of Incidents Reported
Details of the Problem
Details of Possible Causes
Short term Action (Workaround)
PBI000001093302
DEP - VMI Supplier Reconciliation Issue.
As a part of VMI Supplier consignment process, supplier is getting
different picture of their quantities. There is mismatch between Actual
Material On-hand and Custom 4930 Framework On-hand.
DEP Oracle Application Instances
DEP Oracle Application Instances
20+
DEP is following a Custom BOLT ON VMI Process (C&I 4930) with
few suppliers.
There has been discrepancy on the consumption rate and on hand
balances as seen in system (Oracle Seeded as well as Custom VMI
figure) as well as What Supplier believes.
This is creating a Supplier payment issues. Which can be sorted out by
necessary financial adjustment (one time), however DEP wants to have
sustainable process so on going this type of discrepancies are identified
promptly and fixed, if existing there by no impact to the business.
After analysis we found that, due to below transactions are not
considering while 4930 programs, system is not able to calculate the On-
hand for supplier.
 PO Receipt Against BPA
 Return to Vendor Transaction
User is raising ticket to do correction of quantities in 4930 custom tables
(XXWMS_PRESENTATION_TBL and

Root Cause Investigation Details
(Gather Data / Design Test)
XXWMS_RECPT_DTLS_TBL).
Below is the detailed root cause analysis for each transaction.
 PO Receipt Against BPA
Issue
- As per the VMI process, PO Receipt should be happened
against Standard PO.
- For few historical items, PO Receipt was done against BPA.
- As per the 4930 C&I, it will consider only Standard PO
Receipt.
Recommendation
- When user do PO Receipt, how BPA got populated on
Scanner/System. – We need to restrict BPA using form
personalization.
 Return to Vendor Transaction
Issue
- Business wants consumption against Receipt on FIFO bases
but when 4930 programs is considering Receipt for Return to
Vendor transaction, it already consumed.
Case 1
- Sometimes, DEP consumed quantity and then they realize that,
they need to Return quantity to Vendor.
- So, they will perform Return to Vendor transaction but in VMI
tables (4930), DEP already consumed quantities.
- When 4930 programs run, it cannot find open quantities and
not able to perform the Return to Vendor transaction in VMI
table.
 Case 2
- There are 126 quantities open for this week.
- User performed Return to Vendor transaction for 50 quantities
and Consumed 126 quantities.
- When 4930 runs, program is not calculating proper quantity,
the result of Finishing on Hand is -50, and this is wrong.

 Recommendation
- When any Return to Vendor transaction happen for specific
Receipt and Receipt was already consumed then Return to
Vendor transaction should happen against open Receipt for that
part.
Solution Identification and Data analysis/reconciliation for VMI parts.
Verification (Conduct Test / Analyze
Data / Select Solution)
04-Apr-2019%20VMI
%20Consumption%20Report.xlsx

Queries
VMI Consumption Query

VMI Consumption
Query.sql

PO Receipt Query

1 PO Receipts Query
for Consigned Checks.sql

Transfer to Regular Query

2 Consigned Item -
Transfer to Regular query.sql

Material Workbench On-Hand Query

3 On hand extract
with dates.sql
Closure Summary We will raise Enhancement CRQ to work on VMI Consignment issue.

Implementation Progress {Plan / Implement / Failsafe Solution}

Corrective Actions - Actions to be implemented to remove the root cause

Item Action description Action Owner Global Service Due Date

# if appropriate Name of Support Group and Assignee to Owner (DD-MMM-
include perform this activity YY)
Requirement
e.g. Infrastructure
Change, Process
Improvement,
Training, etc
1 Code change is Scerp.Apps.Support/ Amol Korde 02-Mar-
required. Kpit.Global.Tech.Oracleappssupport 2019
<kpit.global.tech.oracleappssupport@cumm
ins.com>

Assignee name: Maulik Chauhan (PP596)

Preventative Actions – Actions to be implemented if a Root Cause Cannot be found

Item # Action description if Action Owner Global Service Due Date

appropriate include Name of Support Group Owner (DD-MMM-YY)
Requirement and Assignee to perform
e.g. Infrastructure Change, this activity
Process Improvement, Training,
etc