Component Scrap

This is the scrap percentage used to increase the required quantities of the
components by the calculated scrap quantity. This increment is used in MRP
and SAP PP order.
Operation Scrap
Operation Scrap is that scrap which is expected in one operation for the
quantity of a component to be processed.

1. Scrap
2. Types of Scrap
3. Assembly Scrap
4. Component Scrap
5. Operation Scrap
6. Scrap Calculation
Scrap Definition:
Non-conforming material that cannot be reworked or used
and has no value except for its material content.
Types of Scrap
The following are the various scraps that are maintained
1. Assembly Scrap
2. Component Scrap
3. Operation Scrap

Assembly Scrap
i)Percentage scrap that occurs during production of the
material if the material is an assembly.
Takes into account all faults that occur when the
individual components of an assembly are assembled (in
production).
ii)Maintained in the Material Master - MRP 1 View as
percentage
iii) Assembly scrap is used in materials planning to
calculate the lot size of the assembly. The system increases
the quantity to be produced by the scrap quantity
calculated.
Dependency:

The system increases the quantity to be produced for

all of the assembly's components accordingly.
Assembly Scrap-MRP1 View

Assembly Scrap Calculation

Let the material master record of header material FERT

contains an 10% of assembly scrap. The subordinate
component ROH quantity will be calculated as below to
include the scrap.

The resulting component quantities for ROH is calculated for

1,100 pieces of assembly FERT.

Component Scrap
Percentage of scrap that occurs during production of
the material if the material is a component. It takes into
account all faults that occur before the component is put into
an assembly (material provision scrap).
Applies only to one component
Component scrap can be maintained
- In the BOM on the Item detail screen: basic data under
Quantity data. This component scrap is only relevant to the
individual BOM.
- In the material master record on the MRP 4 screen under
Requirements explosion. If the same component scrap
applies to a material in a number of BOMs, then it can be
maintained in the material master record.

Component scrap is used in material requirements

planning (MRP) to determine the quantities of components
required. When exploding the bill of material (BOM), the
system increases the required quantities of the components
by the calculated scrap quantity

Component Scrap - Dependencies

Component scrap maintained for a material component

in a BOM overrides the component scrap maintained in the
material master record.
If there is also assembly scrap for a higher-level
assembly, the system adds together the two types of scrap
BOM Item detail screen: Basic data

If the component scrap is only relevant to the individual

BOM, then it can be maintained in the BOM Item detail
screen

Component Scrap - MRP4 View

If the same component scrap applies to a material in a

number of BOMs, then it can be maintained in the material
master record.

Component Scrap Calculation

If a component scrap of 10% is maintained for the material
component ROH in the BOM, then the component quantity
will be calculated to include the scrap as below.

Component Scrap & Assembly Scrap

Assembly scrap of 10% is maintained in the material master
record of assembly FERT.
In BOM, component scrap of 10% is maintained for a
material component ROH. The component quantity will be
calculated as below to include the scrap.

If an adjusted required quantity of 1,100 pieces of FERT is to

be produced, then 1,210 pieces of component ROH are
required.

Operation Scrap
Scrap that is expected in one operation for the quantity
of a component to be processed
Used to override the assembly scrap for materials of
high value

If operation scrap is maintained, situations where too

much of the material is planned in MRP for the components
of subsequent operations can be avoided
If an entry for Operation scrap is made, then Net Scrap
Indicator must be set to active
Applies to only one component
Operation Scrap - BOM Item detail screen: basic data

Net Scrap Indicator

Determines whether scrap for the component is

calculated on the basis of the net required quantity (the
required quantity without assembly scrap from the material
master record).
Must be set to exclude Assembly scrap
Must be set to override assembly scrap with operation
scrap
Can be set if only component scrap is entered, to
calculate scrap on the basis of the net required quantity for
the assembly
Net Scrap Indicator - BOM Item data

Operation Scrap Calculation

Operation scrap is maintained as 1% for one of the
component ROH2 in the BOM. This component is also subject
to assembly scrap of 10%. For 1000 pieces of FERT
assembly, the following is the scrap calculation for
component quantities.

Scrap Calculations
Scrap calculation depends on the entry of various scraps
(Assembly, Component & Operation scrap) for the Assembly
& Component Material and also influenced by Net Scrap
Indicator in the BOM Item detail.
Master data:

The following are the scrap quantities calculated for the

above master data:

**** END OF THE DOCUMENT ****Regards,

Keerthi

between Component Scrap

rap
5:09 PM

Repl
y

n to me what's the difference between Component Scrap (STPO-AUSCH)

p (STPO-AVOAU)?
e set in the BOM with CS02; for a component mat1 I've tried first to put
o 1% and then Operation Scrap to 1% and I've obtained in both cases the
requirement for mat1 when I create a Process Order with COR1; and
antity with COR6N the 261 movement for the material mat1 is the same

seems to be that if you put a non-zero value into Operation Scrap, then
e "Net Indicator" (STPO-NETAU); instead if you put a non-zero value into
hen you don't have necessarily to flag the "Net Indicator"...
k this is the only difference...!
me?

nd Operation

Repl
y

ults that occur before the component is put into an assembly (material

ctive on delivery.

mbly. When you explode the BOM, the system increases the quantity of

424c7211d189520000e829fbbd/frameset.htm

that does not meet quality requirements.

ess.

n/ea/e9b3764c7211d189520000e829fbbd/frameset.htm

meet the required production quality.

scrap is considered for all components contained in the assembly. The
for which the net operation scrap indicator is set.
master from the MRP view.

764c7211d189520000e829fbbd/frameset.htm

etailed explanation of the scrap data.

Posts: 2,117
Registered:
1/1/07
Forum Points:
5,514

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 4, 2008
5:26 PM in response
to: G R
Hi,

Repl
y

Component scrap means, during

processing particular component is going to
be scrapped, so system will plan for the
component More.

If the Component scrap is 1%, then the

system will plan 1% more for this
component.
Operation Scrap:
The Net indicator will work in a different
way.
Say, your Assembly scrap is 10%, then the
system will plan all the components 10%
more, if you want to over ride this, then
you can use the net indicator where in
actually one particular component might be
scrapped only 5%. in this case, system will
plan for this component only 5% more.
Refer below link for better understanding..
Scrap Data
Hope this helps..
Regards,
Siva

Posts: 16
Registered:
7/25/08
Forum Points:
0

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 4, 2008
6:14 PM in response
to: Siva Kumar M

Repl
y

Thank you Ashok, thank you Siva,

for your answers...
But with reference to Siva's answer, I can
manage your second example even without
using Operation Scrap: if Assembly

Scrap=10% and I want one component to

be planned only 5% more, I can flag the
"Net Indicator" and putting Component
Scrap=5%.
The result would be the same.
So what's the reason of two fields if I can
manage both scrap before process and
scrap during process with one field?

Posts: 233
Registered:
2/12/10
Forum Points:
424

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008
8:44 AM in response
to: G R
Hi,

Repl
y

If Operation scrap is entered and Net ID is

checked, the assembly scrap entered at the
parent level is ignored and only operation
scrap is considered.
But Component scrap is independent. It is
calculated over and above the assembly
scrap.
Eg: If FG reqmt is 200 (assy scrap 10%)
then reqmt for component is 220 nos.
Now if component has a component scrap
of 5% (Net ID not checked) then the
component scrap value is 5% of 220 ie 11
nos and total reqmt for component is
200+20+11 = 231 nos...
In the above case is if Component scrap is
entered and Net ID is checked then Comp
scrap value is 5% of 200 =10 and total
remt for component is 200+20+10 =230
nos

You can also Hit F1 on Net ID field in BOM

to see a good example of all possible
combinations...
Hope this clarifies...
Regards,
Ashok

Posts: 16
Registered:
7/25/08
Forum Points:
0

Posts: 233
Registered:
2/12/10

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008
10:22 AM in response
to: Ashok Babu.R

Repl
y

Hi Ashok,
yes but hitting F1 on Net ID in the BOM I
find six examples: the third one doesn't
agree with your example:
in fact the quantity of the component is
10500 (being 2% the assembly scrap, 5%
the component scrap, 100 pieces the
required quantity and being checked the
net indicator).
If your example was correct, we would
have:
component quantity=
10000+200+500=10700
and not:
component quantity= 10000+500=10500
How do you explain this disagreement?
Re: PP-PI: Difference
between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008

Repl
y

Forum Points:
424

10:36 AM
to: G R

in response

Hi G R,
Sorry, That was my mistake..
I wanted to explain as below. but typed it
differently.
If component scrap% is entered and Net ID
is clicked, the componenet scrap value is
calculated as a percentage of original net
requirement (10000 * 5%) and not as a
percentage of the adjusted net requirement
( (10000+200)*5%). Also assy scrap is
ignored.
If net ID checked assembly scrap at parent
level is always ignored.
So the primary difference is Operation
scrap always overrides assembly scrap
(Since net ID should always be checked if
you enter operation scrap).
But with Component scrap it is optional and
can be a function of the adjusted net reqmt
if net ID is not checked.
Rgds,
Ashok

Posts: 16
Registered:
7/25/08
Forum Points:

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008
10:52 AM in response
to: Ashok Babu.R

Repl
y

Posts: 233
Registered:
2/12/10
Forum Points:
424

Hi Ashok,
that's what I meant!
Now you have confirmed what I thought.
Thank you very much.
Bye,
GR
Re: PP-PI: Difference
between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008
11:06 AM in response
to: G R
Hi GR,

Repl
y

Though this is the difference for the PP

user, we should also remember the basic
reason why 2 fields have been provided. It
is to differentiate your operational loss and
loss due to other reasons. This will help for
reporting purposes and also for remedial
action to reduce scrap.
Rgds,
Ashok

Posts: 16
Registered:
7/25/08
Forum Points:
0

Re: PP-PI: Difference

between Component
Scrap and Operation
Scrap
Posted: Sep 5, 2008
2:54 PM in response
to: Ashok Babu.R

Repl
y

Hi Ashok,
thank you very much!
You've been very helpful to me, even with
this last clarification.
Bye,

GR
scrap Management in Finished Product
Can anybody tell me that how I will manage scrapped finished product.
For e.g, If I already entered operational scrap and component scrap
percentage at the required fields.
Let us say, planning is of 250 pcs., as we have put some percentage of
scrap so the planning is of 270 pcs.
But in actual production 255 are correct and 15 are defective.
So where I will keep the record of these defective pcs. and how I will
plan for reworking of these defective items.
Also , if I want a report that during on date (x), in shift (y) how much
were scrap or defective item, how I will get?
Why are you not using by-product and confirm the production under 531
movement. In this way you find everything against material code.
Sanjay
In order confiramtion screen, you can put the quantity which is ok. Rest of
the qty you will have to enter in rework or scrap qty. But, alone entry in this
field will give only information that how much qty is rejected or to be
reworked.You will have to make an additional GR for scrapped qty,stating it
in the code of scrap. If you want to rework, then make a new rework order
of the qty not confirmed in prodn order.
You can also have a trigger point, in order confirmation screen which will
trigger new rework order or generation of scrap if you entered any qty in
respective fields.
I think this can solve your problem.
Mahendra
It is not correct to put scrap % for all materials. This is to be used only in
case of fix rejection which is by virtue of process e.g. molding casts, sheet
metal, pipes, gaskets, lids etc.

It is better to use 531 movement if it is a single component e.g. casting by

putting the scrap quantity.
Please note that if those can be reworked then you shall use quality module
e.g. Final Assembly (entire final assembly never gets scrapped). So that
product will go in quality & then accept the OK quantity & reject rework.
After reworking accept those parts. Alternately for recording rework use
rework orders.
Best way to scrap material is manually post actual rejection using 551movement separately.
Prasad Indapwar
You have take the help of Quality management in which you have to create
lot for each production shift wise and aganinst each lot you have to record
good, diffective stocks you will get total MIS.
A.Surendra Kumar
Re: Difference between plan, target
Reply
and actual cost of an order
Posted: Nov 28, 2011 5:01 AM in
response to: Chris SAP
Plan cost - is as per Order planned and can be changed while
creation of the order.
Target Cost - is the cost as per BOM and Routing for the actual
quantity delivered and is calculated at the time of variance
calculation.
Actual Cost - is the cost incurred for producing the product.
Regards,
Divraj

Delete Costing run marked and released

Posted: Dec 3, 2011 2:59 PM
Hi

Reply

I did one costing run which was marked and

anolther costing run which was marked and
released also.
I want to delete both the above.
Which transaction I can use for this and what is the
implication of them ?

Posts: 1,400
Registered:
8/20/08
Forum Points:
2,546

Re: Delete Costing run marked and released

Posted: Dec 3, 2011 3:28
PM in response to:
nikkitha
CK44 - Delete Costing Run

Reply

Srinivas
Edited by: Srinivasa Maruvada on Dec 3, 2011
7:58 PM

Posts: 7,943
Registered:
3/21/08
Forum Points:
19,502

Re: Delete Costing run marked and released

Posted: Dec 3, 2011 3:51
PM in response to:
nikkitha
Hi Niki & Srinu

Reply

CK44 does not delete Cost Estimate.. it only

deletes the Costing run
You need to use CKR1 for deleting Marked or
Released Cost estimate.. Select the buttons
"Future Cost" for deleting Marked Cost and
"Current Cost" For released costs
br, Ajay M

Posts: 1
Registered:
8/29/09
Forum Points:
358

Re: Delete Costing run marked and released

Posted: Dec 3, 2011 6:11
PM in response to:
nikkitha
Hi ,

Reply

First you need to delete costing run through T.

code CK44 and then after you can delete
standard cost estimate by using T. code CKR1
accordingly.
Regards,
Shailesh Verma

Posts: 10
Registered:
11/30/11
Forum Points: 2

Re: Delete Costing run marked and released

Posted: Dec 5, 2011 7:26
AM in response to:
nikkitha
Hi NIkhitha,

Reply

CKR1 is the Tcode for Deletion of Cost Estimate

as told by Ajay. However to add few implications
and points to be reviwed before deletion.
1. Check whether it is really necessary to delete
2. Any Orders are being valuated by this Cost

Estimate price
SB

Posts: 362
Registered:
3/26/09
Forum Points:
398

Re: Delete Costing run marked and released

Posted: Dec 5, 2011 7:34
AM in response to:
Shailesh Verma
Dont delete the costing run initially.

Reply

First go to CKR1 select the expand button plus

sign (Shift + F7). There mention the costing run
and date and delete the future or current std. cost
estimates as applicable.
Then go to ck44 and delete the costing run.
Regards,
Divraj

http://sapfinance.blogspot.com/2011/02/sap-fico-interviewquestions-product.html