0ic_c03 infocube

We are being told to run the start program RMCBNEUB for 2lis_03_BF and we don't know the infostructure.
Thanks for your help.
Calvin

We've worked with start program RMCBINIT_BW for 2lis_03_BX and RMCBNEUB for LIS_03_BF and RMCBNERP for LIS_03_UM and we've also used lbwg to delete data in the setup tables. We then went back to load data into the infocube for the three and now we are only receiving 13 records. Our goal is to load the data and then do some reports.
I've looked online looking for many different possible ways to do this and to do it right. We then did what they said and were only receiving 13 records.
I thank you for your help

Similar Messages

After inital stock load in 0ic_c03 infocube "seems" empty

Hi everybody,
I carried out the steps in the document How to handle inventory management scenarios in BW ... to load data in 0IC_C03 infocube
to keep things simple I only setup table MC03BX0SETUP ...
i performed the following steps:
1) initialization of current stock in r3
exec tc MCNB
2) then check when tc RSA3 the structure 2LIS_03_BX which shows 66378 records
3)Upload data to the infocube (selection "create opening balance" radio button ). The monitor showed 66378 records
4) Compressed the request (the check box "no marker update" was blank)
5) then went to tc RSA1 and select the infocube 0IC_C03 -> right click -> manage ->and check the contents of the infocube. in the selection screen no selections were made and execute, but no data was shown. Why I can't see any data
thanks for any help with this
rgds
Azael

According to the aforementioned document, page 14, "when historical material movents are not required" step for loading statistical data isn't needed, only a delta initialization with no data is requiered which I already did.
What I d'ont understand is why I can't se any rows of the infocube.
As I understand, after loading stock initialization (2lis_03_bx), compressing this request and initialized delta without data transfer (2LIS_03_BF), data with the stock figures at the moment of creating the oppening balance in R3 must be shown in the infocube, is it right?
Is it correct that historical data is only required if I need stock figures in past? for example I run MCNB at 10.05.2006 and I'am intereisting in what the stock was at 01.05.2006, if I do'n need that past sate I don't need to load 2LIS_03_BF, only delta initialization without data transfer is rquired, right?
sorry for the long text, but I only want to make sure I understand the process
thanks

Inventory Management - 0IC_C03 InfoCube Partitioning (Recommendations)

Hello Everyone,
I have gone through most of the postings available on SDN and other white papers related to Inventory management implementation.
I did not get enough information and most of the information has given me both yes and no answers for partioning of the InfoCube.
I am looking for,
Can you please recommend what is the best practice for Physical and logical partitioning of 0IC_C03 InfoCube.
We have Calendar Day, Calendar Month, Calendar year in time characteristics and plant as the validity characteristic.
I have gone through couple of white papers which recommend avoid using the time characteristics for partitioning and rather use plant or territory grouping as applicable.
But some forum postings I have gone through mention that the partitioning has been done on time characteristics.
What is the impact of marker update and the paritioning being done on the time characteristics.
So, can you please let me know what the best practice would be and the reason for partitioning in the way whichever you recommend.
I really appreciate your input.
Thanks
Dharma.

Hello Naveen,
Thanks for the prompt response.
I understand that the partitioning by time characteristics is not useful because of how the data is accessed.
When I mentioned that the partitioning is considered on Plant or Territory.
I mean to use the logical partitioning where I am thinking of loading in my data based on the territory field which would then be grouped into regions.
In this case it can be Region 1, Region 2 and Region 3
Where
Region 1 --> Data from Territories 1,2,3
Region 2 --> Data from Territories 4,5,6
Region 3 --> Data from Territories 7,8,9
Once this has been done, I am planning of implementing the entries in RRKMULTIPROVHINT table to accordingly split the queries from Multiprovider.
The reason being most of the reporting is done at the territory level which in turn would help re-route the queries to appropriate part provider.
I am more worried about the physical partitioning for an InfoCube in order to have good database breakdown.
Thanks
Dharma.

0IC_C03 InfoCube Issue?

We are having an interesting issue with the 0IC_C03 material movements cube. We ran the initial, "BX", load near the end of January, on the 26th, and the data ties out to R/3 on that day. After loading the deltas though "BF", when we attempt to tie out to R/3 for the month end January, there are some plants that do not exist.
In drilling into the issue, we found that the plants that are not showing up do not have material movements between the 26th and the end of January. When filtering on a specific plant (one that does not appear when drilldown by plant is selected) and drilling down by calendar day, the quantities match exactly on the 26th, but the dates from the 27th to the 31st have the exact same number but with brackets "[]" around the numbers.
It appears as though the data is not "cumulating" correctly if no material movements are loaded in the deltas.
Any ideas? What do the brackets mean?
Thanks in advance
Rodney

Hi,
Have done the compression with marker update after uploading the deltas of BF?
To get the plants into report even though there were no postings occured for that palnt in the specified date range, I hope,you need to Manually update the validity table.
Re: Non availability of closing stock for 'no transactions'
With rgds,
Anil Kumar Sharma .P
Message was edited by:
Anil Kumar Sharma

Closing Stock For Each Period in Inventory Infocube

Hello Guru's,
Can we have closing stock of each material for entire period in Invnetory Infocube ? or through any logic or transformation routine can we create this keyfigure at infocube level ?
I know that to get Closing Stock ( Opening Stock + Goods Receipt - Goods Issue), we have to have Opening Stock as well for each month. in 0IC_C03 infocube, we only have Goods Receipt Qty and Goods Issue Qty keyfigures. We don't have Opening Stock and Closing Stock keyfigures as those are calculation which works during run time of query but still we want to have this information at Infocube Level.
Do please let me know your thought as i appreciate your help in advance.
Regards,
Komik Shah

hi,
I will check that t code.
thanks and regards,
Devina

Inventory Mangement Infocube without Routines.

Hi,
I have to install 0IC_C03 infocube for the customer in SAP BI. Initially I had issues in mapping the fields for this cube with datasources BX, BF and UM. Then I realized that since there are many Non Cumulative Key Figures in the cube, most of the data loads will take place using routines.
I want to know can we use this infocube without having to write any routines in ABAP. I don't know ABAP and there is no programmer with me. So there's no way I can write codes.
Is there a way or an alternative of using Inventory Cube. I have gone through "How to handle Inventory Mangement Scenarios in BW" document but that's of no use, since it suggests many routines, almost for every keyfigure.
Is there any other way I can do Inventory for them. The client's requirement is to see all the standard reports present in SAP for Inventory.
Please help me solve this issue, as I am really running short of time in this project.
Thanks.

Hi,
Besides what I know is:
Load BX DTP
compress with Marker Update. --> uncheck the check box during compression on with zero elimination.
Load BF DTP
compress without Marker Update followed by deltas with Marker.-- check the check box
Load UM DTP
compress without Marker update followed by deltas with Marker Update.
--uncheck teh check box on zero elimination.
After installation check wheather all teh objects are active or not. There will not be any difference in the content for BI 7.0 when compared with BW 3.x versions as the business content is not delivered in 7.0 version.
Please folow teh steps speficed in document How to after the installation of content.
Hope this helps.
Regards,
Reddy

Inventory Management (0IC_C03) cube

When I carry out delta loads to the Inventory Management (0IC_C03) InfoCube do I need to compress these delta loads with No Marker Update? Thanks

hi Nitish,
1. Compressing the request containing the opening stock that was just uploaded. Make
sure the "No marker update" indicator is not set. Please consider note very carefully
643687 before you carry out the compression of requests in stock InfoCubes!
2. Loading the historical movements into the InfoCube 0IC_C03 via the DataSource /
InfoSource 2LIS_03_BF. Choose the upload mode "Initializing the delta process"
here.
3. After successfully uploading the historical material movements, the associated
request has to be compressed. You must make sure the "No marker update"
indicator is set. This is necessary because the historical material movements are
already contained in the opening stock. Well look more closely at markers later on.

0IC_C03 related Inventory Process - Logical Partitioning (Vs) Physical Part

Hello Everyone,
After going through multiple postings throughout the form and documentation from SAP, it states that the 0IC_C03 InfoCube when used with Non Cumulative keyfigures is not recommended to be partitioned logically by physical year/calendar year as the query will read all the data sets due to the stock marker logic.
In our specific scenario,
1. After the InfoCube (0IC_C03) was enhanced with additional characterisitcs such as Doc Number, Movement type and so on due to business requirements I was not able to actually use the Non Cumulative Keyfigures as they were not populated within the report.
2. So, we decided not to use the Non Cumulative keyfigures but rather create two cumulative keyfigures (Issue Stock Quantity - Receipt Stock Quantity) and (Issue Valuated Stock Value - Receipt Valuated Stock Value) and both of these are available in the InfoCube and are calculated during the update process.
These two keyfigures are cumulative with exception aggregation of LAST based on 0CALDAY.
The question is,
Since we are not using the actual Non Cumulative Keyfigures (even though we are not using these, we still have the stock marker updated and data compressed based on this along with Validity table defined) can we do logical partitioning on the InfoCube based on Calendar year.
Thanks....

Hello Elango,
Appreciate your response.
First of..I do understand the difference between logical and physical partitioning and the question is not about joining them together.
I am sorry, if others cannot understand the detailed issue posted. My apologies was a part of polite gesture, and please do respond back with proper precise answer if you think you did actually understand the question....
The question here is about how I can leverage the performance and administrative performance by logically breakingdown the data.
The issues due to which I am trying to look into different aspects of logical partitioning are:
1. If I do logical partitioning by Plant due to the stock marker logic then I cannot do archiving as a Plant and its related data cannot be archived by time characteristic as the partitioning is not done by time characteristic.
2. The reason I would have to have document number and movement type in the InfoCube is due to the kind of reporting users perform.
We have a third party system whose data needs to be reconciled to the data in the plants and storage locations.
And in order to do so, the first step users would be running the report is plant, storage location and sku. From here on for the storage locations which have balance they would like to drill down on to the document number and movement type to see what the actual activity is.
So, to support this requirement I would have to have the above characterisitcs in the InfoCube.
The question again is,.....what is the exact list of issues I would be having doing the logical partitioning by time characteristic.
Once again, even though the non cumulative keyfigures are available in the InfoCube we are not using them for any reporting purpose....so please keep that in consideration while replying back.
Thanks
Dharma.

0IC_C03 Inventory Control Data Issue

Dear Gurus,
We have implemented BI 7.0 with the latest support package as of 1st May 2011. Issues are coming relavent to 0IC_C03 infocube for inventory control. I have followed the how to guideline but issues are there.
I have done the following settings:
1:To fill up the extractor for 2LIS_3_BX i have used the Transaction MCNB (All Stock Including non-valuated).
2: To fill up the extractor for 2LIS_3_BF i have used the Transaction OLI1BW (Posting Date till 2999).
3: To fill up the extractor for 2LIS_3_UM i have used the Transaction OLIZBW (Posting Date till 2999).
4: To generate the IP for 2LIS_3_BX for the opening stock balances the update mode CREATE OPENING BALANCE is not showing so i have used the update mode Generate Initial Status.
5: After running the IP for 2LIS_3_BX i run the DTP with extraction Mode "Initialize non commulative".
6: In the infocube Manage for 0IC_C03 i go in the collapse tab and enter the 2LIS_3_BX Request ID and uncheck the "NON Marker Update" to compress the request.
7: I generate the IP & DTP for both 2LIS_3_BF & Then 2LIS_3_UM and compress both the requests in the cube by the checking the "NON MArker Update"
8: When i run the query the data is not coming out right. Some records have negative values and some have wrong values.
Kindly tell me what to do.
Also, ive seen people using 2LIS_3_BF & UM only but not BX. How will this solution be implemented?
Regards,
Shahzad Khero

Dear Guru,
As off now here are the issues:
Quantity Total Stock is matching the stock in ECC 6.0 in transaction MB5B. The issue lies with the Issue Quantity Total Stock
& Receipt Quantity Total Stock. The values are not showing accurately but the new balance per posting date are showing accurately.
For e.g. Cube: 0IC_C03
Calendar Day     Issue Quantity Total Stock           Receipt Quantity Total Stock                          Quantity Total Stock
03/31/2010                           0.000 MT                                 63.000 MT                                                63.000 MT
04/1/2010                           78.940 MT                                 91.410 MT                                                75.470 MT
04/2/2010                           18.000 MT                                 0.000 MT                                                57.470 MT
MB51
Posting Date      Issue Quantity Total Stock           Receipt Quantity Total Stock                          Quantity Total Stock
03/31/2010                           0.000 MT                                 63.000 MT                                                63.000 MT
04/1/2010                           68.940 MT                                 81.410 MT                                                75.470 MT
04/2/2010                           18.000 MT                                 0.000 MT                                                57.470 MT
As you can see the issue & reciept docs are different but the impact on quantity total stock is fine. On top of that the material documents showing in PSA are slightly more than actual showing in MB5B & MB51. Some material documents are showing as a debit entry as well as credit entry in PSA but in reality they have a debit entry or a credit one. Kindly give me a feedback.
Regards,
shahzad

BI Content Update rules not available for 0IC_C03 cube

Hi
We have recently did technical upgrade to our DEV box and made a system copy for sand box. I am trying to install the BI content for 0IC_C03 infocube. I cant see update rules for this data flow. I could see Transformations and can also see info source (ex: 2LIS_03_BF_TR) which we dont expect. We havent migrated or never used inventory BI content. What is the reason we could see transformations for this cube data flow in BI content? We are on SP15. I tried to install transformations but cant install them properly.

Hi A,
Business content it's still using 3.x data flow. That's why you see a 3.x infosource.
You won't have transformations for this. The update rules icon is like a transformation but with a small white square on the left.
So the dataflow you should have is:
Cube
Update Rules (0IC_C03 2LIS_03_BF)
    3.x InfoSource (Material movements (as of 2.0B))
      Transfer Rules
        Datasource
You'll see a small square next to all the objects, except for the cube. This means 3.x object.
Hope this helps.
Regards,
Diego

0IC_C03 Set up tables

Gurus/Experts
I have to delete and reload the 0IC_C03 infocube in the middle now.
Can any one tell me the steps from R3 side for setting up the delta update please
Is the BX datasource needed for initialization ?? if yes then i have to do the SBIW-->Stock Initialization
or i can just go to the
SBIW>Logstics>Managing extract structures-->Initialization -->Inventory management setup should work
please help

Okay, so following will be the steps:
1. Make sure the users are locked
1.1 Make sure you delete any existing data in the setup tables for Inventory (LBWG: application 03)
2. Setup for BX : Transaction MCNB
3. Load to cube and compress with Marker update (no check in check box)
4. Setup for BF: Give selection for posting date as from 01/01/2008 to 03/15/2008
5. Once setup run is done, load this to the BW cube. You can load as Full load
6. Compress this request without updating the Marker (Put a check in the checkbox)
7. Do an init for BF (Init without data) and compress this request also without updating the Marker (Put a check in the checkbox).
8. You can unlock users now.
9. Schedule the delta load for BF and from now onwards all requests will be compressed with Marker update (no check in check box).
Hope this helps...

0IC_C03 Navigational Attributes

Hi all,
Can you please let me know what are the possible Navigational Attributes we can have in 0IC_C03 infocube.
Points will be assured.
Thanks & Regards
vadlamudi

HI,
In the same MetaData Repository Click the InfoCube the list will be diplayed ,search for the cube.Then select the cube and drag down there you will find more documents in the below table u can find infoobjects see the 3rd column will display the navigational attribute...x mark will be there for non navigational attribute...
hope this helps...

Mapping(type routine) missing in transformation 2lis_03_bf - BCT 703, 704

Hi Friends,
i am on 703 BI content, than when i activated the 0ic_c03 infocube I observed that in transformation 2lis_03_bf mapping is missing, target field should is not mapped with source field, in earlier version of bi content target fields is gettinc caluclated by some routine and secondly start routine of 2lis_03_bf have syntax error, same with 2lis_03_bx and um transformation.
so we upgraded to BI conetent 704 with patch 0001 than i reactivated the 0ic_c03 cube but though problem is same.
so, we are now planning to upgrade support patch 0003 for BI content 704, will support patch 0003 for BI content 704 solve the problem or anyother thing required to do with current status of BI conetent 704 with patch 0001 to solve this issue?
Regards,
dushyant,

Hi Colin Moloney ,
we applied the 0003 support pack/patch for the BI content 704 from patch 0001 of BI content 704,
now start routine error of 2lis_03_bf is gone, transformation is comin as active verson once we do reactivation of object from BI content,
But still missing the mapping rules in transformation.
note 1179880 is saying that Import Support Package 3 into your system. is that mean patch 0003 for BI content 704?
note content - "Solution
Implement Note 1171293 in your system. The following procedure depends on the release you are using.
BI_CONT 7.04:
A Support Package that contains all transformations is available for Release BI_CONT 7.04. Import Support Package 3 into your system.
If you install Release 7.04 by upgrading from Release 7.03, only the changed objects (delta) are imported into the system. As a result, transformations may be deleted in the system, and you may only notice this when you activate the new BI Content from Release 7.04. The missing transformations are delivered completely in this Support Package"
now what to do?
regards,
dushyant.

Using CL_RSR_WWW_MODIFY_TABLE to remove rows completely from output!

Hello All,
I have a problem I am trying to work thru and I need some assistance.
Here is the issue...
I have a report, in which I want to completely remove uneeded rows (depending on the contents of the row).
I have had a look thru the how-to papers on the TAble interface (so please don't post links to those, they are not what I am searching for as they only describe things like not displaying cell contents, and like I stated, I want to not show rows...ie, delete them from output.)
Does anyone have some code to show me how to accomplish this?
Here is my scenerio...
I have a query, from the 0IC_C03 infocube (I understand the IM scenerio, so don't post links to the SAP help for How-to on this subject), and in the query, I have storage location and material. As we all already know, the infocube does not give a good solution to provide values only on Storage location. But, to get around this, you can have a report with Material in the rows, and do a calculation (Price * Qty) to get the totals by storage location. But, I do not want to show the materials. (Yes, I know there is yet another how to paper on realizing inventory on storage location level, but that does not produce correct results).
The query is doing exactly what I want...here is the results.
STORLOC____MATERIAL_____VALUE
LOC1________RESULT_______$200000
LOC1________MATNR1_______$150000
LOC1________MATNR2_______$50000
LOC2________RESULT_______$2500
LOC2________MATNR3_______$1500
LOC2________MATNR4_______$1000
LOC3________RESULT_______$500
LOC3________MATNR5_______$500
You get the idea...
Anyway, I want to turn the above, into the following..
STORLOC____MATERIAL_____VALUE
LOC1________RESULT_______$200000
LOC2________RESULT_______$2500
LOC3________RESULT_______$500
Essentially, removing everything but the results rows...
Now, I have read a few other questions out here on something similiar (someone else was trying to accomplish the same thing) but nobody has ever posted a reasonable answer to the above question, so I am hoping, some of you have a solution, either via defining my own CL_RSR_WWW_MODIFY_TABLE solution or via Javascript.
If someone has accomplished this with the table interface, which method and how did you change the table?
If someone has accomplished this with javascript or something else, I would like the details of that as well.
Note: I was able to read the table, and was able to use a temp table, and remove the rows I did not want, but, I was not able to update the table passed by the interface.
This code works to get the right rows, but, it doesn't allow me to update the passing table.
DATA:wa_y_axis_data LIKE LINE OF
I_r_data_set->n_sx_version_20a_1-axis_data,
wa_cell_data LIKE LINE OF
I_r_data_set->n_sx_version_20a_1-cell_data,
set LIKE LINE OF wa_y_axis_data-set,
TUPLE_ORDINAL like set-TUPLE_ORDINAL,
l_counter TYPE i,
l_index TYPE sy-index,
l_trade_fvalue LIKE wa_cell_data-formatted_value.
* prerequesite in example: 1 key figure and 1 calc. key figure column
LOOP AT I_r_data_set->n_sx_version_20a_1-axis_data INTO wa_y_axis_data
WHERE AXIS = 1.
LOOP at wa_y_axis_data-set into set.
 l_index = sy-index.
 if set-chanm = 'A0MAT_PLT' AND set-chavl NE 'SUMME'.
 delete wa_y_axis_data-set where tuple_ordinal = set-tuple_ordinal.
 ENDIF.
ENDLOOP.
ENDLOOP.
Any similiar experiences or feedback is appreciated.
Cheers!
/smw

Hi Steve,
just want to know why the material has to be present in this report - when not shown in the end - just to have it in the column or why wonder?
regards, Johannes

Non-Cumulative vs. Cumulative KeyFigures for Inventory Cube Implementation?

A non-cumulative is a non-aggregating key figure on the level of one or more objects, which is always displayed in relation to time. Generally speaking, in SAP BI data modeling, there are two options for non-cumulative management. First option is to use non-cumulative management with non-cumulative key figures. Second option is to use non-cumulative management with normal key figures (cumulative key figures). For SAP inventory management, 0IC_C03 is a standard business content cube based upon the option of non-cumulative management with non-Cumulative key figures. Due to specific business requirements (this cube is designed primarily for detailed inventory balance reconciliation, we have to enhance 0IC_C03 to add additional characteristics such as Doc Number, Movement type and so on. The original estimated size of the cube is about 100 million records since we are extracting all history records from ECC (inception to date). We spent a lot of time to debate on if we should use non-cumulative key figures based upon the standard business content of 0IC_C03 cube. We understand that, by using Non-Cumulative key figures, the fact table will be smaller (potentially). But, there are some disadvantages such as following:
(1) We cannot use the InfoCube together with another InfoCube with non-cumulative key figures in a MultiProvider.
(2) The query runtime can be affected by the calculation of the non-cumulative.
(3) The InfoCube cannot logically partition by time characteristics (e.g. fiscal year) which makes it difficult for future archiving.
(4) It is more difficult to maintain non-cumulative InfoCube since we have added more granularity (more characteristics) into the cube.
Thus, we have decided not to use the Cumulative key figures. Instead, we are using cumulative key figures such as Receipt Stock Quantity (0RECTOTSTCK) , Issue Stock Quantity(0ISSTOTSTCK)
, Receipt Valuated Stock Value (0RECVS_VAL) and Issue Valuated Stock Value (0ISSVS_VAL). All of those four key figures are available in the InfoCube and are calculated during the update process. Based upon the study of reporting requirements, those four key figures seems to be sufficient to meet all reporting requirements.
In addition, since we have decided not to use cumulative key figures, we have removed non-cumulative key figures from the 0IC_C03 InfoCube and logically partitioned the cube by fiscal year. Furthermore, those InfoCube are fiscally partitioned by fiscal year/period as well.
To a large extent, we are going away from the standard business content cube, and we have a pretty customized cube here. We'd like to use this opportunity to seek some guidance from SAP BI experts. Specifically, we want to understand what we are losing here by not using non-cumulative key figures as provided by original 0IC_C03 business content cube. Your honest suggestions and comment are greatly appreciated!

Hello Marc,
Thanks for the reply.
I work for Dongxin, and would like to add couple of points to the original question...
Based on the requirements, we decided to add Doc Number and Movement type along few other characteristics into the InfoCube (Custom InfoCube - article movements) as once we added these characteristics the Non Cumulative keyfigures even when the marker was properly set were not handling the stock values (balance) and the movements the right way causing data inconsistency issues.
So, we are just using the Cumulative keyfigures and have decided to do the logical partitioning on fiscal year (as posting period is used to derive the time characteristics and compared to MC.1 makes more sense for comparison between ECC and BI.
Also, I have gone through the How to manual for Inventory and in either case the reporting requirement is Inception to date (not just weekly or monthly snapshot).
We would like to confirm if there would be any long term issues doing so.
To optimize the performance we are planning to create aggregates at plant level.
Couple of other points we took into consideration for using cumulative keyfigures are:
1. Parallel processes possible if non-cumulative keyfigures are not used.
2. Aggregates on fixed Plant possible if non-cumulative keyfigures are not used. (This being as all plants are not active and some of them are not reported).
So, since we are not using the stock keyfigures (non cumulative) is it ok not to use 2LIS_03_BX as this is only to bring in the stock opening balance....
We would like to know if there would be any issue only using BF and UM and using the InfoCube as the one to capture article movements along with cumulative keyfigures.
Once again, thanks for your input on this issue.
Thanks
Dharma.

0ic_c03 infocube

Similar Messages

Maybe you are looking for