Recursive Material

Hi All,
I have a peculiar requirement
Please find it below.
There is a Select Options for Material.
Based on the Material BOM Explosion should happen.
Now in the resultant set of Materials if the Material (in Select Options) is present and this is treated as Recursive.
For Ex:
s_matnr = 1
now when material 1 is exploded its giving
2     3       4    1
Hence in the above case since 1 is appearing in the exploded set it is treated as "Directly Recursive"
Now again when 2 is exploded
we get 5    6    7
and when 3 is exploded
we get 8    9    10
and so on so forth.
If in any hierarchy / level the material in s_matnr ( 1 ) is appearing then its "Indirectly recursive".
The Explosion will continue for all the resultant set of exploded materials.
Please give me some kind of clue about this.'
The report they want is to display all the Materials with Direct/Indirect Recursive.
Waiting eagerly for your Hints/Replies
Hope you all have understood the requirement.
Please revert for further clarification i shall articulate the requirement .
Thanks
Sri

Check this wiki for recursive logic link:[http://wiki.sdn.sap.com/wiki/display/Snippets/InverseBOMExplosion-ABAP]
For sequential logic use function CSAP_MAT_BOM_READ instead of fm CS_WHERE_USED_MAT used in the above link.

Similar Messages

Recursive material code

Hi guys,
a question:my customer has several Bills of Materials which have recursive codes but with a particular thing and that is--->these recursive codes have obviously the same material code but also the same material type,the same valuation class that is they are perfectly equal to the finish product father and so now I am confused..Is this thing correct taht is SAP permits a process like this or the recursive material codes must have a different material type, different valuation class etc...?Or how must I manage this situation to make that these material codes are valuated and costified correctly?..
I hope to have explained myself good, THANKS IN ADVANCE to all
Bye
Maximilian

hi,
yes all the parameters will be same ...
Bcoz
Suppose you create a material with material name XYZ...
now you assign material type, val. class etc ...
Now you go to create BOM...and assign same item as XYZ, then system auto takes it as recursive material BOM and shows you the message...
In SAP, You can't create the 2 material code with same name....right...so material code will be same...n along with this val. class, material type ...all para. will be same...
Hope you understand...
Regards
Priyanka.P

Rework scenerio for recursive material

Dear all,
I have recursive BOM material having thickness "X"mm and wanted to reduse it "Y" mm of same material may i use rework scenerio. please guide.
thanks

I am still not clear on the stock part. Yes in classification you can maintain thickness as one characteristic.
I take the example of a bar which has say thickness 100 mm, now you have 4 such bars. If I reduce the thickness of one bar from 100mm to say 75mm, another to 80mm, what will you maintain in the classification for thickness characteristic? Also what will the stock report show? Are you working with batch management for this?
If the need is to just capture the costs of this activity, yes you can do this by creating an indirect order via CO07.

Run time error while try to display challan after reconcillation.

All experts,
Here I m getting an runtime error...when I M going in t-code j1ifr....after reconcillation of recursive material bom po.
thankx in adv.

Runtime Errors         DYNPRO_FIELD_CONVERSION
Date and Time          07.05.2010 08:49:15
ShrtText
     A conversion error occurred.
What happened?
     The current screen processing was terminated, since a situation
     occurred from which it could not continue processing.
     This is probably due to an error in the current screen of the ABAP
     program.
What can you do?
     Make a note of the actions and input which caused the error.
     To resolve the problem, contact your SAP system administrator.
     You can use transaction ST22 (ABAP Dump Analysis) to view and administe
     termination messages, especially those beyond their normal deletion
     date.
Error analysis
     The program flow was interrupted and could not be resumed.
     Program "SAPMJ1IFN" tried to display fields on screen 1210. However, an
     error occurred while this data was being converted.

Material cost estimate using recursive BOM

Hello everybody.
I want create material cost estimate (CK11N) using a recipe with recursive BOM. When I execute the transaction CK11N the following message is display Costing of cycle 00001 does not converge
Do you know what is missing?
Thanks in advance.

Dear,
Message no CK740?
Please do check the link below......
http://help.sap.com/erp2005_ehp_03/helpdata/EN/f8/a3e333bf3d11d189900000e8214595/content.htm
and OSS note : 858384
Regards,
R.Brahmankar

Change material BOM / item / Class Recursion

I'm looking for a way to change the "recursiveness allowed" flags in the "Class Recursion" tab of a BOM item in transaction CS02. The flag corresponds with the fiels REKRS in table CLRK. No BAPI or FM found after half a day of searching. The CSAP_* function modules don't seem to cover this data.

Hi,
This indicator is automatically set based on the conditions mentioned here [Class Recursiveness|http://help.sap.com/saphelp_470/helpdata/en/ea/e9b54a4c7211d189520000e829fbbd/content.htm]. You can have look at fm CSAI_BOM_MAINTAIN which has that indicator FL_RECURSIVE. As the documentation says
The system recognizes recursiveness for a class item if the following objects are allocated to the class in the class item:
    The BOM header material
    A material with a BOM which contains the BOM header material as an item
    A class to which one of the materials described above is allocated
You can try logics like removing the header material from the item, so that recursiveness is avoided, May be by using CSAP_BOM_ITEM_MAINTAIN. Explode the existing BOM using CS_BOM_EXPLOSION and compare the header & item materials.

Sales order costing is not possible for recursive configurable material

User is creating cost estimate for sales order, where system is throwing above error.
The diagnosis is like below
The system recognized that the BOM structure being costed is a recursive production process in which configurable materials are used. This scenario is not supportive by sales order costing
System resopose
Material XXXX in plant XXXX can not be exploded further.
If anyone has come across such error or knows the solution, please help.
Thanks

Answered

SSRS Recursive Hierarchy for Bill of Material

OK, here we go. I have been absolutely unable to find an answer anywhere after extensive searching so I will ask this here.
First of all, I am trying to create an SSRS report for a Bill of Materials (product structure) with parent child recursive grouping to enable drill down to multiple levels. For the most part, I have achieved the goal of doing this with a proper CTE stored
procedure and including a parent recursive reference to the Child group. Here is my result set of the CTE and the grouping settings:
This produces a very pretty report that allows for drill down to levels with indents and levels and everything! Just one problem..... By grouping on the Component to get the recursive technology to work, the result set of my CTE which has 37 rows gets truncated
down to 32 due to multiple rows getting merged because part numbers can be the same while used on more than one part. In this case, see rows 30 and 34. The child (component) is PLA331. Because they are the same part number but used with different parents,
one of them gets eliminated and the result of my report looks like this:
PLA331 should be listed under SA-0482 but it is not due to the grouping of the part PLA331. How do I get all of the results to display even if I am grouping on the component? I have tried removing 'Hide Duplicates' and it does nothing.
BOMs are a very important part of a business so I am actually quite shocked that I am the only one having this structure issue. Perhaps everybody else doesn't have the same part listed on multiple levels of a BOM? Or a lot of people THINK they have the correct
BOM structure but are unaware of this little problem?
Thanks,
Sayslah

Hi Sayslah,
Based on your description, I create a similar report in my test environment. However, I cannot reproduce the same issue as your post.
Please refer to the steps below to check if there is something different. I create a dataset with three fields: Component, Parent, Qty.
1. Add a table in the report body.
2. In the Row Group dialog box, add Parent Group: [Component].
3. Setting Component Group with Recursive parent: Component.
4. Add Qty field in the table.
You can refer to the screenshot below:
If there are any misunderstanding, please feel free to let me know.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Materialized View with recursive join

Why is this not allowed?
create materialized view bone_mv
refresh complete
on commit
as
select
a.pk
from
tablea a,
tableb b,
tableb b2
where
tablea.col1 = b.col1 and
tablea.col2 = b2.col2
If I use "on demand" there is no problem.

Hi,
Have you managed to overcome this problem? If so, could you please let me know.
Thanks
Raja

Material to be produce included in production order component review

Hello gurus, i have a issue about production order.
1. The BOM of XXXX material have the next components:
    A
    B
    C
2. When i create a production order for 100 ST of XXX material, the component review in production order includes the next:
Position Material Quantity
0000      XXXX        100 (row blocked)
0010     A                  20 ST
0020     B                   1.5 KG
   0030    C                    10 ST
3. I don´t know why the component review in production order includes the position 0000 and blocked. It looks like the BOM of XXXX material have a recursive position, but isn´t real.
Please, help me with this issue
Regards,
Johnny Leguia

The issue was solved.
The co-producto indicator in a BOM position makes that all co-product materials (that hace co-product indicator in mrp view) were listed in component overview. The material to be produced had this co-product indicator in mrp view.
Thanks for help.
Regards,
Johnny Leguia

Need help on tuning materialized view refresh

Hi All,
I am working on materialized view refresh tuning.Initially it was complete refresh and used to take more than 90 mins to complete.
I changed it to fast refresh now it is completing fast. Now i have partitioned the base tables gl_balances and gl_code_combinations of column code_combination_id and created a local index on column code_combination_id then i am trying to partition the materialized on the same column to take advantage of partition change tracking.
Size of gl_balances base tables is 40Gb and all others tables sizes are small. In where clause there all the 4 tables are mapped. If i will create the partition only on code_combination_id will i the materialized will become the candidate for partition change tracking. As i know it will be applicable for PCT. I need expert advice on this.
While doing a fast refresh. the refresh takes less time. when there is a change in gl_balances , gl_code_combinations or gl_periods it completes in 20-30 mins. When there is a change in gl_set_of_books tables. It creates a problem here.DEL query takes more than 48 hours to complete.
CREATE MATERIALIZED VIEW apps.BAL_PART
REFRESH FAST ON DEMAND
ENABLE QUERY REWRITE as
SELECT GL.GL_CODE_COMBINATIONS21.ROWID C1,GL.GL_BALANCES21.ROWID C2, GL.GL_SETS_OF_BOOKS.ROWID C3,
GL.GL_PERIOD.ROWID C4,
"GL"."GL_BALANCES21"."ACTUAL_FLAG" ,
"GL"."GL_BALANCES21"."CURRENCY_CODE" ,
"GL"."GL_BALANCES21"."PERIOD_NUM" ,
"GL"."GL_BALANCES21"."PERIOD_YEAR" ,
"GL"."GL_BALANCES21"."SET_OF_BOOKS_ID" "SOB_ID",
"GL"."GL_CODE_COMBINATIONS21"."CODE_COMBINATION_ID" "CCID",
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT1" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT10" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT11" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT12" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT13" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT14" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT2" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT3" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT4" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT5" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT6" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT7" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT8" ,
"GL"."GL_CODE_COMBINATIONS21"."SEGMENT9" ,
"GL"."GL_PERIODS"."PERIOD_NAME" ,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_CR", 0) Open_Bal_Cr,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_CR", 0) +
NVL("GL"."GL_BALANCES21"."PERIOD_NET_CR", 0) Close_Bal_Cr,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_DR", 0) Open_Bal_Dr,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_DR", 0) +
NVL("GL"."GL_BALANCES21"."PERIOD_NET_DR", 0) Close_Bal_Dr,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_DR", 0) -
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_CR", 0) Open_Bal,
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_DR", 0) -
NVL("GL"."GL_BALANCES21"."BEGIN_BALANCE_CR", 0) +
NVL("GL"."GL_BALANCES21"."PERIOD_NET_DR", 0) -
NVL("GL"."GL_BALANCES21"."PERIOD_NET_CR", 0) Close_Bal,
NVL("GL"."GL_BALANCES21"."PERIOD_NET_CR", 0) Period_Cr,
NVL("GL"."GL_BALANCES21"."PERIOD_NET_DR", 0) Period_Dr
FROM GL.GL_CODE_COMBINATIONS21,
GL.GL_BALANCES21,
GL.GL_SETS_OF_BOOKS,
GL.GL_PERIODS
WHERE GL.GL_BALANCES21.CODE_COMBINATION_ID =GL.GL_CODE_COMBINATIONS21.CODE_COMBINATION_ID
AND GL.GL_SETS_OF_BOOKS.SET_OF_BOOKS_ID = GL.GL_BALANCES21.SET_OF_BOOKS_ID
AND GL.GL_PERIODS.PERIOD_NUM = GL.GL_BALANCES21.PERIOD_NUM
AND GL.GL_PERIODS.PERIOD_YEAR = GL.GL_BALANCES21.PERIOD_YEAR
AND GL.GL_PERIODS.PERIOD_TYPE = GL.GL_BALANCES21.PERIOD_TYPE
AND GL.GL_PERIODS.PERIOD_NAME = GL.GL_BALANCES21.PERIOD_NAME
AND GL.GL_PERIODS.PERIOD_SET_NAME = GL.GL_SETS_OF_BOOKS.PERIOD_SET_NAME
and gl.GL_CODE_COMBINATIONS21.summary_flag != 'Y'TRACE 1046 del statement
DELETE FROM "APPS"."apps.BAL_PART" SNA$
WHERE "C3" IN (SELECT /*+ NO_MERGE */ * FROM (SELECT
CHARTOROWID("MAS$"."M_ROW$$") RID$     FROM "GL"."MLOG$_GL_SETS_OF_BOOKS"
"MAS$"   WHERE "MAS$".SNAPTIME$$ > :B_ST1 ) AS OF SNAPSHOT(:B_SCN) MAS$)
call     count       cpu    elapsed       disk      query    current        rows
Parse        1      0.00       0.00          0          0          0           0
Execute      1 17759.00 171782.99 159422121    1267371 2564144739           0
Fetch        0      0.00       0.00          0          0          0           0
total        2 17759.00 171782.99 159422121    1267371 2564144739           0
Misses in library cache during parse: 1
Misses in library cache during execute: 1
Optimizer mode: ALL_ROWS
Parsing user id: 175 (APPS)   (recursive depth: 1)
Rows     Row Source Operation
      0 DELETE apps.BAL_PART (cr=0 pr=0 pw=0 time=0 us)
193128740   NESTED LOOPS (cr=592437 pr=592422 pw=0 time=945244160 us cost=339302 size=168 card=1)
      3    SORT UNIQUE (cr=7 pr=0 pw=0 time=15832 us cost=2 size=138 card=1)
     24     TABLE ACCESS FULL MLOG$_GL_SETS_OF_BOOKS (cr=7 pr=0 pw=0 time=19 us cost=2 size=138 card=1)
193128740    INDEX RANGE SCAN C3BOOKS (cr=592430 pr=592422 pw=0 time=789499200 us cost=339299 size=3318314250 card=110610475)(object id 2114736)
error during execute of EXPLAIN PLAN statement
ORA-08187: snapshot expression not allowed here
parse error offset: 314
Elapsed times include waiting on following events:
Event waited on                             Times   Max. Wait Total Waited
----------------------------------------   Waited ---------- ------------
db file sequential read                   159520897        2.12     144415.96
latch: cache buffers chains                   134        0.06          0.68
latch: undo global data                        33        0.02          0.15
latch: object queue header operation          521        0.02          0.53
log file switch (private strand flush incomplete)
                                                532        0.31         28.26
resmgr:cpu quantum                            155        1.40         13.49
resmgr:internal state change                   25        0.11          2.21
latch free                                     10        0.00          0.00
latch: cache buffers lru chain                  4        0.00          0.00
rdbms ipc reply                               489        0.02          0.54
reliable message                              587        0.00          0.56
latch: row cache objects                        3        0.00          0.00
********************************************************************************GL_SETS_OF_BOOKS has only 6 rows. I know there is complete refresh as a option which will again take more than 90 mins.
I want to do the fast refresh. Tables rows details below.
SQL> select count(*) from gl.gl_code_combinations21;
COUNT(*)
3075255
SQL> select count(*) from gl.GL_PERIODS;
COUNT(*)
1160
SQL> select count(*) from gl.gl_balances21;
COUNT(*)
477613527
SQL> select count(*) from gl.gl_sets_of_books;
COUNT(*)
6gl_sets_of_books has less rows. Whenever there is a change then it mapped to huge rows hence during materialized view has delete huge number of rows.
select count(*) from apps.BAL_PART group by C3;
C3 is the rowid which is present in create materialized statement.
COUNT(*)
292927011
210215
69330
184406971
Is there any way to improve the plan. As i created a partition on code_combination_id and local index on code_combination_id which will not help in set_of_books_id case. I dont PCT will help here or not. Is it possible to use PCT refresh by equipartitioning only one column in where clause.
Please assist me in improving refresh of materialized view using fast refresh.
Thanks and Regards,
Edited by: user646034 on Feb 23, 2013 11:13 PM
Edited by: user646034 on Feb 23, 2013 11:19 PM
Edited by: user646034 on Feb 23, 2013 11:46 PM
Edited by: user646034 on Feb 25, 2013 11:46 AM

Hi
The below explain without index and with index.
/* MV_REFRESH (DEL) */ DELETE FROM "APPS"."BAL_PART
" SNA$ WHERE "C3" IN (SELECT /*+ NO_MERGE */ * FROM (SELECT
CHARTOROWID("MAS$"."M_ROW$$") RID$     FROM
"GL"."MLOG$_GL_SETS_OF_BOOKS" "MAS$"   WHERE "MAS$".SNAPTIME$$ > :B_ST1
) AS OF SNAPSHOT(:B_SCN) MAS$)
Plan hash value: 2704021294
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | Id | Operation            | Name                          | E-Rows |E-Bytes| Cost (%CPU)| E-Time   |
|   0 | DELETE STATEMENT     |                               |        |       |   339K(100)|          |
|   1 | DELETE              | BAL_PART                          |        |       |            |          |
|   2 |   NESTED LOOPS       |                               |      1 |   168 |   339K (1)|999:59:59 |
|   3 |    SORT UNIQUE       |                               |      1 |   138 |     2   (0)| 00:02:31 |
|   4 |     TABLE ACCESS FULL| MLOG$_GL_SETS_OF_BOOKS        |      1 |   138 |     2   (0)| 00:02:31 |
|   5 |    INDEX RANGE SCAN | C3BOOKS                       |    110M| 3164M|   339K (0)|999:59:59 |
If i will not use the C3 index then the query will use the belolw plan, I guess this will also take same time or more time.
|   0 | DELETE STATEMENT       |                               |        |       | 9743K(100)|          |
|   1 | DELETE                | BAL_PART                          |       |            |          |

Discontinuation indicator and follow up material.

Hi,
I am facing the strange issue for which i need your expertise. The requirement is like:
1. "X" material is discontinued and "Y" is as follow-up in two plants A & B. Discontinaution group and follow-up group has also been assigned in the BOM.
2. Now The client want to reverse the settings . means "Y" should be discontinued and "X" should be follow-up in both plants A & B.
Now I have removed the discontinuation indicator and follow up material from "X" in both plants. But when I am going to discontinue the "Y" material and putting " X" as a follow-up material, The system is giving the message "The specified follow-up material results in recursiveness
Message no. M3609
Diagnosis
You have entered a follow-up material. However, the BOM explosion for the follow-up material leads to the discontinued material, resulting in unpermissible recursiveness.
Procedure
Enter another follow-up material or cancel the entry.
Please suggest me where I am missing in my settings and what is the reason for this message.
Regards
Deepak Sharma

Dear ,
Check the following :
1.Validity of the Bill Of Material or any deletion flag is set in the present BOM.
2.Please check the following SAP notes :
Note 161742 - Consulting note: BOM recursion/low-level code 999
Note 839879 - Trace 'BOM is recursive'
Note 139517 - Recursiveness for follow-up materials
Note 42891 - Recursiveness check
Hope this will help you to figure it out
Regards
JH

The follow up material results in recurssiveness

HI,
I have two BOMs one is plant specific production bom
& the other is group BOM which is engineering/design bom
     Production Bom(plant specific)
parent     MO
child 1     m1
child 2     m2
     Enginering/desing bom(indepent of plant)
parent     MO
child 1     m1
child 2     m2
     m3
So in material master of m3 iam trying to discontinue with discontinuation indicator 1 with follow up material MO
The sytem is issuing the "the specified followup material results in recurssiveness"
why the system is throwing this message though m3 is not present in the production bom (which is plant specific)

Praveen,
Are you trying to say that if you maintain the material BOM for M0 with M3 as component and a follow up material as M0 again..?
It will definitely a recursive bom.
Or is it that you are maintaining a material M3 with follow up material as M0, where the M0 bom has components as m1 and m2 and you are getting this error in this case?
Please explain clearly..
Sumeet

Automatic equipment creation at the time of GR of material - Subcontracting

Dear Experts ,
I have created a non valuated material .
I have created a serial number profile in which the setting is that the equipment is created automatically at the time of GR.
I have attached the above serial number profile to the above material. Due to this whenever the material is purchased & GR for the same is done , an equipment is created automatically with with construction type having the GR material & serial number of the material assigned to the equipment . The sattus of the equipment is ESTO( In ware house )
The material is then issued to using T Code MB1B & the stock is reduced to zero .Due to this the equipment status is changed to AVBL( available ).
The functional location is then assigned to the equipment & all its maintenance activities are carried out .
Now the same equipment needs to be sent to a subcontractor for repair . For this i need the make a subcontracting PO with recursive BOM & hence i need the stock of the material . So i diamantle the equipment & generate its stock which is sent outside to the subcontractor through the subcontracting PO .
Now when i do the GR , THE SYSTEM AGAIN CREATES A NEW EQUIPMENT FOR THE MATERIAL . I want this to be avoided as i want the old already existing equipment to be used .
How can this be done
Pls Guide
Regards
Anis

Anis,
This scenario sounds like 'Refurbishment through external resources for materials with serial numbers". This is a tricky process and standard SAP doesn't help.
Think you need to discuss with your MM guy to create a special movement type for receiving materials with the same serial number.
Regards,
Seran

Recursive Loop Error while doing standard cost estimate

SAP Gurus,
We are trying to do standard cost estimate on a material and we are getting error because it is going in recursive loop even though we have used "recursive allowed" indicator for item components in the BOM. The error message numbers are CK 730 and CK 740. We are using 4.6c. I have tried the same scenario in ECC 6.0 and still I get the same problem.
Below is my BOM structure:
Material 10890345 (has low-level code 012)
        ---> 10867220 (has low-level code 013) and has recursive allowed indicator
10867220
        ---> 10846733 (has low-level code 014) and has recursive allowed indicator
10846733
        ---> 10890345 (has low-level code 012) and has recursive allowed indicator
According to me, the BOM for material 10846733 is causing the problem.
For some weird reason while doing the costing run for material 10890345, it s not stopping and going in a loop.10890345 and 10846733 should ideally have the same low-level code as they are recursive.
Please help to provide some solutions at the earliest on how to avoid recursive loop during costing.
Regards,
Swapnil

Dear,
I have 2 things to shear with you.
The method we followed to solve the iteration is as below
1.Config change -
Valuation variant in the costing variant, we changed the sequence as below
material valuation
4 planned price 1
2 std price
3 Mov ave price
2. Material master change
made all the semi finished goods and finished goods
procurement type = E,
costing with qty structure,
Enter the planned price1
By doing this what happens is
when system first start the iteration, takes the planned price 1 and start iterating and next time in the second iteration it takes the calculated price from qty structure till it finds the difference between the value calculated is less than .001. Then it gives the result
Why lot size is important is, in our case in some levels the usage is very less compared to the first material header qty and system used to stop in between and not even reaching the last level as during the cycle it was reaching less .001 difference. may be in your case it may not be the case...just check
Please come back after trying this. this was the only last option i had to solve the issue in my client.
Another alternative is to have a different material for costing purpose to stop the iteration which i will not recommend as we need to do some calculation for each stage and input the cost of dummy material in each stage.
My client is happy with the result as the difference between manual calculation and system calculation is less then .1%...this is because SAP will not consider the difference beyond .001, but in excel you get as many as decimals you want.

Recursive Material

Similar Messages

Maybe you are looking for