cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Receiving Parts with Changed Part Number

Former Member
0 Kudos
1,204

First off, let me explain that I do not have SAP access at my company, so any notes I make, or questions I ask, are without the firsthand knowledge of working in SAP itself. So please bare with me, I will do the best I can.

With that said, I am reaching out to the experts in SAP to help me with an issue that has plaguing my company and I for 6+ months, with 100's of hours spent on the issue right now. The company is one of the "Big 3" Aerospace companies in the US, and somehow we have not found a way to complete the task at hand.

Scenario is this: We have a part that has a given part number on it now (1234-1), and needs to be upgraded to another part number (2341-1) at an outside supplier. There are changes made to the part physically during the upgrade that affect form, but not fit or function (involves making a sub-component out of steel versus aluminum). We have established Purchase Requests to move the part out of the plant under the old part number, but are having challenges trying to get it received under the new part number.

So I think there are two questions ultimately:

1.) How should the PR be structured in the first place, before the part is sent out? Should the PR that leads to a PO call out the original part number, the upgraded part number, or the new upgraded part number and have the old part number 'hung to it' like a 'make from' requirement?

2.) How does the new part number get accepted into stock? Assuming both part numbers are material mastered, what transaction in SAP could i use to a.) change the part number from the old part number to the new number when it is received, or b.) just receive the new part number from the supplier, with traceability back to the original part number?


Thank you to everyone who reads this and tries to help. Cost and schedule are both suffering on my project becasue we cannot get this right.

Accepted Solutions (0)

Answers (0)