One discrepancy would have only one disposition

Once supplier resubmit disposition, Previous disposition would close. MHI would suggest new
disposition.

RSA

1.For a defect in a NCR, if liability is supplier and for same, once status is change to supplier buyoff
required , then a corrective action notification would be created and system would check if
corrective action header is created for supplier,material,liability and defect combination. If yes,then
corrective action would update in that corrective action header.

If not , it would create corrective action header for that supplier,material,liability and defect
combination.Then corrective action would update in that header.

2.further corrective actions would keep update in that corrective action header.

3.When that corrective action header would update with “Answer RSA”.Then that would update as
RSA with all those corrective action in supplier portal and sent to supplier.

4.once RSA submit by supplier, then that would update in those corrective actions which would be
open.

5. RSA should have table for corresponding corrective action and NCR with status.

NCR disposition in SAP

1.Once NCR created with discrepancy and Disposition, then that disposition would update as
proposed.

2.Supplier buyoff line item would add automatically.

3.MHI would change status of that disposition after internal review of the disposition with respective
department such as MRB quality, Engineering review.

4.If disposition is ok for MHI, then status would change to supplier buy off required.

5.If supplier would provide buy off, then it would close disposition.

Re-submit

6.If supplier resubmit disposition, then that disposition would update as “resubmit of disposition”. In
this case either supplier propose disposition or MHI would provide disposition.

7.
Details from NCR to be copied while creation of Corrective Action (Notification type – CD)

BAPI_QUALNOT_CREATE – Using NCR number by removing 00 in between.

1. Reference Notification
2. Purchase Doc/ No
3. Material Number
4. Supplier details in Partners
5. Coding
6. Liability
7. Defect
8. Preliminary Investigation
9. Preliminary Root Cause Analysis
10. Serial Number/ traceability Number
11. Product code

Updating of Corrective action cause and Task details from RSA once RSA Action is “RSA submitted
for approval”

Check status of corrective action notification available in assigned objects of RSA.

1. Corrective action notification is completed (Closed).

NO UPDATES required from RSA.

2. Corrective action, Cause and Task details are empty.

BAPI: BAPI_QUALNOT_ADD_DATA

3. Corrective action, Cause and Task long text are available and adding RSA details to it.
BAPI: BAPI_QUALNOT_MODIFY_DATA

Creation of RSA while creating Corrective action -Notification Type “CH”

1. Material
2. Supplier in Partners
3. Defect
4. Corrective Action Number in Assigned objects (BAPI – QNAO_PS_SAVE)

Updating already existing RSA for a new corrective action

1. Corrective Action Number in Assigned objects

2. RSA number in “REFERENCE NUMBER” newly created corrective action
To achieve this:

Before creating a corrective action check if RSA notification is available for

Material, Supplier and Defect. If available while creating corrective action
notification include RSA number in the BAPI.
 If RSA notification is not available, then create RSA notification with corrective
action details and updated corrective action notification with REFERENCE NUMBER
3. RSA notification should not appear in portal if status if “CAH Initiated” and “RSA
Confirmed”
Creation of RSA: BAPI_QUALNOT_CREATE
Updating of RSA: BAPI_QUALNOT_ADD_DATA