HELP : Inventory Cube - Missing routines in transformation

Hi all,
Im working with BI 7.0 and i've activated Inventory Cube from Business Content. Checking the the entire data flow i saw that there were a lot of missing routines in the transformations from datasource to the cube (UM, BX and BF).
My question are :
1) Where can i find the corresponding routines (abap code OO) to all that missing routines?
2) In order to avoid this issue, which is the correct way to activate this Cube?
I'have activated other cubes and i did not have any issue.
THANKS IN ADVANCED
Regards

Hi,
Install the cube using the 3.x dataflow. In that dataflow you'll find the routines.
Replicate the same to your transformations. Its not necessary to convert them to OO. You can still use standard ABAP.
Cheers,
Kedar

Similar Messages

Loading to inventory cube - LBWQ ( entry MCEX03 missing )

Dear Guru's,
My main idea is to store only last 1 years of data in inventory cube .
I do not want to load the movements & revaluation data from ECC but reconstruct.
I have successfully initialized only 2LIS_03_BX and filled the set up table and further loaded in to BW.
For movements data i wanted to recontruct , so i reconstructed .
BW --> opening stock is correct.when compared with MB5B
Movements ( some data missing ) -- If i check for the historical stock , results does not tally.
I further checked and found some transactions missing in the cube ( when compared to MB51 movements list )
I tried to bring in these into BW using full load of 2LIS_03_BF.
it fetched 0 records.
I deleted the initialization request from info package in BW for 2lis_03_bf earlier
RSA3 --> also 0 records.
LBWE --> Job control scheduled to run every 1 hour.
RSA7 --> found job scheduled.
LBWQ --> no entry for MCEX03
I have run init with out data transfer and then tried to load full . still 0 records .
Also at rsa3 0 records.
Please help to advise how i can fetch these missing movements / records in to BW
Thanks & regards,
Sudhir.

Hello Janardhan,
When ever a full update is complete, the next records i.e. delta records moves into the Extractor Queue (LBWQ ) and after this moves through Scheduled process in delta Queue ( RSA7) .
The role of Setup tables is limited when you need the full extraction from the Application tables . Setup tables are restructuring tables .. basically are pooled tables which are introduced in the LO Extraction to ease up the extraction . Here System doesn't need to look for the Application table for data , this saves down time and consistency of records.
From Reconstruction it is relevant in 3x. Could you please elaborate what you tried to do..!
You can refer to the below links
Setup tables
LO Cockpit data extraction
Hope this helps...!
Regards
YN

ODS, Inventory cube, and WM- Trying to run a report but not working! Help

Hi Gurus,
Hope somebody can help me here....
I have an Inventory Cube and an ODS on Material Plant and another on Warehouse Management. For my reports I need fields from three of them so I created a Multi Provider by using these. But I have only Material and Plant as common in three of them, which is used in defining the Multi Provider. Along with these I have used some more characteristics which are not common. So now when I run a query on this MP, I am getting a display wherein the common characteristics get the values that are correct but for uncommon chars the values for the kfs from other data targets become blank and an additional row comes too.
For example, I have kfs like Blocked stock in the cube and in one of the ODS I have kfs like standard price. So, in the query for the char material group which comes from the ODS there are no values for Blocked stock, I mean I can see a row wherein there is a value for Blocked stock and a blank for Standard Price, in the additional row there is a blank for Blocked stock and a value for Standard price. This is the case with all the other kfs of different info providers.
Is it because they are not common in all the info providers? Is there anyway to solve this? RRI will not work as I need the KFs from both the info providers.
I am stuck now with this problem, so any guidence would be a BIG help.
Thanks

Is it because they are not common in all the info providers?
-->Yes
Is there anyway to solve this?
--> Yes and no. If there is a join condition between the ODSs that you can use to get the fields on the same row, you can do an infoset.
--> To achieve something like an outer join, you can create RKF for your base KFs, and restrict them on uncommon chars with 'constant selection'. This may not work in all cases. Search for a blog by Prakash Darzi on 'Constant selection' to understand this.
If logically there doesn't exist a relation (try to visualise how you will derive your output row if you were given these two in a file or spreadsheet - is there a logical link to connect the two sets of data?) you cannot expect the results that you look for.

Damaged inventory cube 0IC_C03

Hi all,
          My inventory cube is damanged because some data is not loaded via delta.
what i done is i stopped the back ground job which is running for compression of the request.i done Init with full repair request loaded missing data.(_03_BF). full load.
         now my question is setting up marker for BF . my opening stock is around 2006. I loaded from 02.2007 to till the date. It is not a historical data(Because it after 2006). current data.
can i do compression with marker or without marker.
pls help me this is very important for me.
thanks .

Hi
About the Marker - understood........I did....without checking it.   that is not the issue. Please see below the detail of the error log. Listcube does not show any entries. the range of posting dates i loaded was 1/1/2000 to 1/10/2010....valuated stock only..........
this is the error message..........
Multiple entries found with NCUMTIM 'unlimited'; compression not possible
Message no. DBMAN380
Diagnosis
The time dimension contains multiple entries for which the time
reference characteristic (NCUMTIM) is set to 'unlimited'.
The value 'unlimited' is the maximum possible value for the time
reference characteristic. This value is reserved for markers in
non-cumulative InfoCubes and cannot be used for standard transaction
records.
System Response : Compression is terminated.
Procedure : Contact your system administrator.
Procedure for System Administration
To allow compression to be carried out, the entries must first be
removed from the InfoCube.
To do this, you can proceed as follows:
1. Delete all packages that contain records in which the time reference
characteristic has the value 'unlimited'. You can identify these
packages by using transaction LISTCUBE.
2. Reload these packages and create a rule in the transformation that
maps the value 'unlimited' to a year before 9000.
3. Using transaction RSRV, then delete all entries that are no longer
used from the time dimension.
The InfoCube can be compressed again.

Difference between Start Routine and End Routine in Transformations

Hi Friends,
I'm using BI 7.0... here in Transformations step we have two options..that is START ROUTINE... and END ROUTINE... What is the Difference between Start Routine and End Routine in Transformations..
When we go for Start Routine.. and when we go for End Routine..
Plz clarrify... points will be rearded..
thanks
babu

Hi,
One real time scenario for End Routine.
We have a scenario where in a datasource field is mapped to three infoobjects on the datatarget side. There are 2 key figures which need to get data after these these Infoobjects are filled. The best place for this to happen would be in a End Routine, where in we would loop through the results package and using the values of the infoobjects from the data target ( Cube in this case).
Hope this helps,
HD

Inventory Cube Stock Quantity/Value Issue

Hi Experts,
I have an issue regarding inventory cube about the stock value and quantity.
The Issue is:
1. I Loaded the 2LIS_03_BX first to initialise the materials opening balance, after compressed ther request with the Marker (checked) .
2. I loaded the 2LIS_03_BF with Initialize without data transfer infopackage and compressed in the cube
3. And I did full load 2LIS_03_BF and compressed with check box selected for marker update.
The issue I have is, when the stock quantity/value of a material ( BX , for example is taken on Dec.2011) is calculated(non cumulative key figure ex.0VALSTCKVAL/0VALSTCKQTY in the inventory cube) backwards based on Issues and received stock/value of material , I am not getting the value/stock equal to the value when the business started ( i.e for example Dec.2009, time at which the material opening stock is counted and entered in the system).
example: When I loaded BX ( intialize opening stock), let us suppose for Material A , have 1000kg in Dec 2011. When the non cumulative key figure (0VALSTCKQTY/0VALSTCKVAL) is calicualted for each month or day , at the end of the period for example Dec.2009 the stock should be 100, but I am getting more than 100 like 150 for example, even though all the issued,received and 0valstckval/0valstckqty are correct upto Dec.2009.
am i missing any steps or please let me your thoughts on this one.
Regards
Vamsi

Hi,
Please follow the steps mentioned in this link.I think 2LIS_03_BX full load should not be compressed with marker update only deltas to be updated in marker table of BF and UM.
http://wiki.sdn.sap.com/wiki/display/BI/StepbyStepLoadingDatatoInventory+Cube
Hope it helps.
Regards,
AL

Inventory cube with Movement Type

In standard Inventory cube 0IC_C03 we have added movement type and loaded the data(followed the process exactly as mentioned in the How to handle Inventory management and compressed).
After loading the data materialwise valuated stock qty and value is matching, but when we drill down movement typewise(for ex.101,102 etc) data is not matching with R/3.All 101 movement types showing in negative values.
Do we have to do any changes in the standard routines if we add movement types in the cube 0IC_C03?.We are loading the data based on processing keys as per the standard routines.
Please help me with your inputs.
Thanks in advance..
Soujanya

Hi,
1)Receipt and Issue key figures already avilable in the cube right?.Still do I have to add in the zic_c03?.
I would like to suggest you to take fields of the cube as it is the fileds available in BF datasource . And any way have those Kf mentioned by you are already in 0IC_C03 cube,so no need to take them here also.
2)If we drill down based on movement type in the report we have to include on receipt and issue key figures?.
In the drill down report , you better take KF 0QUANT_B,0VALUE_LC into columns and Movement type into Rows.
3)We shouldn't look valuated stock qty and valuated stock value based on movement type?
Yes,It does not make scence.
With rgds,
Anil Kumar Sharma .P

Reserves stock quantity in the Inventory cubes

Hello
I need to add a new KF: reserved stock qty to the inventory cubes? Does anyone have an idea if there is any R.3 field for the same or any specific t-codes where I can search. Or is it a calculated kF in the cube (with routines) or in the query?
Thanks.
Srini.

HI,
You talk to MM guys an dask how to capture the reversals using some MOvement types and Item Catogories and then you just add one norma Keyfigure and write code in Transformations like below, this code is sample one and I'm using for other purpose, in the same way you do it..
CLASS lcl_transform IMPLEMENTATION.
METHOD compute_ZQMM_TURS.
*   IMPORTING
*     request     type rsrequest
*     datapackid type rsdatapid
*     SOURCE_FIELDS-BWAPPLNM TYPE /BI0/OIBWAPPLNM
*     SOURCE_FIELDS-MOVETYPE TYPE /BI0/OIMOVETYPE
*     SOURCE_FIELDS-CPQUABU TYPE /BI0/OICPQUABU
*     SOURCE_FIELDS-BASE_UOM TYPE /BI0/OIBASE_UOM
*    EXPORTING
*      RESULT type _ty_s_TG_1-/BIC/ZQMM_TURS
    DATA:
      MONITOR_REC    TYPE rsmonitor.
*$*$ begin of routine - insert your code only below this line        *-*
**********SURENDRA REDDY ON 12-09-2009**************BEGIN*****
... "insert your code here
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*-   to make monitor entries
... "to cancel the update process
*    raise exception type CX_RSROUT_ABORT.
... "to skip a record
*    raise exception type CX_RSROUT_SKIP_RECORD.
... "to clear target fields
*    raise exception type CX_RSROUT_SKIP_VAL.
IF ( SOURCE_FIELDS-MOVETYPE EQ '453'
OR SOURCE_FIELDS-MOVETYPE EQ '454')
* AND COMM_STRUCTURE-/BIC/ZXAUTO IS INITIAL
AND SOURCE_FIELDS-BWAPPLNM EQ 'MM'.
* result value of the routine
RESULT = SOURCE_FIELDS-CPQUABU .
where ZQMM_TURS = normal kf to get the quanity based on movement type and others..
Thanks
Reddy

Error while Migrating the custom routines in Transformations

Dear All,
I am in the process of migrating BW 3.5 to BI 7.0.I migrated the Standard cubes and DSO's from BW3.5 to BI 7.0 flow successfully.
But while migrating the transformations which are having the custom routines,I am facing the below errors.
The data object "COMM_STRUCTURE" does not have a component called BIC/ZGROSSPRI".But the routine contains BIC/ZGROSSPRI.
I tried to change the BW 3.5 terminology to BI 7.0 terminology.(Like COMM_STRUCTURE replaced by SOURCE_FIELDS).But unable to solve.There are nearly 20 custome routines written in all transformations.
Can any one guide me who faced the same tyepe of problem?
Thanks & Regards,
Dinakar

HI,
We need to include Source and Target see the below article.
http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
How to Correct Routines in Transformations
http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/business-intelligence/g-i/how%20to%20correct%20routines%20in%20transformations.pdf
Thanks
Reddy

Inventory Cube Compression - Non-Cumulative

Dear All
I have loaded setup tables in R/3
BX as on date TAC MCNB1
BF i.e. Historical TAC OLI1BW
UM TAC OLIZBW
I have loaded the Inventory Cube form all the three Data Sources
2LIS_03_BX : Initial Status
2LIS_03_BF : Initialization
2LIS_03_UM : Initialization
The queries are fine without compression
I have compressed the cube
2LIS_03_BX : with marker update
2LIS_03_BF : without marker update
2LIS_03_UM : without marker update
After compression the data for Stock issues in 24,36,48,60 months is giving vague values i.e.. IT IS ADDING UP ALL THE PREVIOUS VALUES TO SHOW FINAL VALUE
WHAT ARE THE SETTINGS TO BE MADE FOR COMPRESSION OF NON-CUMULATIVE CUBES ?
AM I MISSING ANYTHING (STEPS) ?
Thanks & Regards
Daniel

Dear Anil
I have followed the same procedure
i.e.
BX-init: Compression with marker update
BF-init: Compression without marker update
UM-init: Compression without marker update
BF-delta loads: Compression with marker update
UM-delta loads: Compression with marker update
But surprisingly the values are not reflecting correctly
Thanks & Regards
Daniel

Inventory Cube Issue

Hi Experts,
We have created a copy of 0IC_C03 with more no of fields added to the copy cube CIC_C03. We had lot of data mismatch in the earlier stage & now after a long time this copy cube is working fine in production. We have not yet compressed the deltas in the cube.
Now, later there was a field to be added in the inventory cube which takes data from an ODS. For this we created one more copy cube as we didnot want to disturb the inventory cube in production, hence we created one Zcube which is the copy of CIC_C03 with an added field. In the update rules we have a routine which fills with data from the ODS. The CIC_C03 acts as datasource for this Zcube.
My question is:
1) I dont feel that after a month or so, we require the data in CIC_c03 as the same data comes in ZCube. So will deletion of data from CIC_C03 affect my data?
2) The intial data in CIC_C03 are compressed whereas the deltas are not yet compressed. Should the full upload to Zcube take after compression only?
3) Suppose we delete the data from CIC_C03 after 2 months after a full upload is taken till that point. After deletion, the deltas will be coming in CIC_C03, canl these everyday delta be transfeered to Zcube?
Waiting for reply.
Regards,
Vaishnavi.

Hi,
The note(637927) is saying that the KFs which represents the values of Stock-in-transit (issue, receipt, current) are deleted in the cube . But still the cube is containint the KF which represents the quntity of Stock-in-transit (issue, receipt, current) .
So the deleted KF are :
0VALTRANSST - Stock-in-transit value
0RECCCNSVAL - Stock-in-transit issue value
0RECTRFSTVA - Stock-in-transit receipt value
Available KF are:
0TRANSSTOCK - Stock in transit Qty
0RECTRANSST - Receipt quantity: stock in transit
0ISSTRANSST - Issue quantity: stock in transit
So to find out the value of Stock-in-transit , you will use the Stock in transit. The scenario has to be used in this calculation is same as explained in note:589024.
With rgds,
Anil Kumar Sharma .P

Inventory cube adding fields

HI,
What If I will add two new fields(key figures) to the standard inventory cube 0IC_C03.
These two fields for opening stock, closing stock and end value.
regards,
Balarm

Hello Srikar,
To populate those 2 fields for the History data:
1 If you have those 2 fields coming in from some Master Data, then you can probably have a look up to those master data and load the fields.
2 If you have those fields coming from modified Datasource, then you have to delete and reload the data to have those fields populated in the Cube.
I hope this helps.
Regards
Rohit

Inventory Cube Loading - Questions....

This is the process I intend to follow to load InfoCube 0IC_C03 and the questions therein. I have the "how to handle inventory scenarios" document, so please don't suggest I read that.
1A) Delete Set-up tables for application 03
1B) Lock Users
1C) Flush LBWQ and delete entries in RSA7 related to application 03 (optional - only if needed)
2A) Fill set up tables for 2LIS_03_BX. Do Full load into BW Inventory Cube with "generate initial status" in InfoPackage.
2B) Compress request with a marker update
3A) Fill set up table for 2LIS_03_BF with posting date 01/01/2006 to 12/31/2007 (Historical) and load to Inventory Cube with a full update
      QUESTION1: Does this need a marker update?
      QUESTION2: Is this a good strategy - do movement documents that old get updated once posted?
      QUESTION3: Does the posting dates restriction depend on on how far back in history we want to go and look at stock values?
3B) Fill set up table for 2LIS_03_BF with posting date 01/01/2008 to 9/9/999 (Current) and load to Inventory Cube with a delta init with data transfer.
3C) Compress load in 3B without a marker update
4A) Fill set up table for 2LIS_03_UM and load to Inventory Cube with a delta init
4B) Compress load in 4A without a marker update
      QUESTION4: How should we select the posting date criteria? Do I need to load from 01/01/2006 to 9/9/9999 since that's the range used for BF?
5) Start V3 update jobs via Job Control
6) Intiate subsequent delta loads from BF and UM and compress with marker update
QUESTION 5: Is the sequence of loading BX first, then BF and UM fixed? or can I do BF and then BX, UM
QUESTION 6: Any tips on minimizing downtime in this particular scenario? Please don't suggest generic steps. If you can suggest something specific to this situation, that'd be great.
I hope you can help with the 6 questions I asked above.
Regards,
Anita S.

Hi Anita,
Please find my answers below. I have worked enough with this scenario and hence feel that these would be worth considering for your scenario.
3A) Fill set up table for 2LIS_03_BF with posting date 01/01/2006 to 12/31/2007 (Historical) and load to Inventory Cube with a full update
QUESTION1: Does this need a marker update?
In this step we dont need marker update while compressing.
QUESTION2: Is this a good strategy - do movement documents that old get updated once posted?
I am able to get the question quite clearly.
QUESTION3: Does the posting dates restriction depend on on how far back in history we want to go and look at stock values?
Yes. We need to start from latest and then go back as backwards as we want to see the stock values. This holds true when we are using non cumulative key figures
4B) Compress load in 4A without a marker update
QUESTION4: How should we select the posting date criteria? Do I need to load from 01/01/2006 to 9/9/9999 since that's the range used for BF?
No need to provide any selection criteria for UM while loading to BW, as this would fetch the same data filled in setup of revaluations.Unless you are looking for only some history other wise you can fill that for company code list and bring the whole data to BW by a single full load, as the data wont be that huge as compared to BF
6) Intiate subsequent delta loads from BF and UM and compress with marker update
QUESTION 5: Is the sequence of loading BX first, then BF and UM fixed? or can I do BF and then BX, UM
This is fixed in terms of compression with marker updates.
QUESTION 6: Any tips on minimizing downtime in this particular scenario? Please don't suggest generic steps. If you can suggest something specific to this situation, that'd be great.
*Yes. Most of time consuming activity is for filling BF history. Negligable for BX and UM comparitively.
Either try having multiple BF selective setup filling based on posting date based on available background processes or filli open months setup during downtime and rest history once you unlock the system for postings. The reason for this being we dont expect any posting for history*
Feel free to ask any further questions about this.
Naveen.A

Inventory Cube -

Hi All,
I have a need for a customized inventory cube, and am planning to use BX, BF and UM extractors into the same cube. I will enhance all the 3 extractors where they have all the characteristics needed for my cube and queries to match my requirements.
I have the following questions.
1. Some of my reports will require to report weekly and some monthly and some adhoc or when ever they want to see (like daily). So we will be updating the cube every night. Since it gets loaded every night if I left 'No marker Update' unchecked, but COMPRESS the cube after daily load how the data will be kept in the cube? and the impact on the queries.
2. How to decide which key figure should be non-cumulative. I have beginning balance, receipts, issues adjustments and turn rate for each week. But I believe except beg balance rest of the key figures can be cumulative.
If you have done inventory please advice.
Thanks,
Alex.

Alex,
If I define the amount as non-cumulative (what ever the KYF) and gets calculated during the query run time and based on the time requested in the query (cal week, calmonth etc) the value will be internally calculated and displayed in the query. is this a valid stament?
--> Yes. That is the advantage of Non-Cumulative keyfigures.
--> Inventory CUBE: 0IC_C03 contains calday, week, month. Based on user selection it displays balances for day level or week level or monthe level. No need to do any speicific calculation at updaterules or transformation level.
--> Just do delta's daily and compress with marker update(means no check box).
Check: [Inventory management: Usage of 2LIS_03_BX datasource |http://sapbwneelam.blogspot.com/2009/03/inventory-management-usage-of-2lis03bx.html]
[How to Handle Inventory Management Scenarios in BW (NW2004) |http://sapbwneelam.blogspot.com/2008/11/how-to-handle-inventory-management.html]
Srini

Inventory cube datamart from one BW system to other BW system

Hi experts,
I have a requirement wherin I have to load the data from Inventory Cube 0IC_C03 from my old BW system to new BW system along with the markers & historical data.
So I have generated the Export datasource of 0IC_C03 and mapped with transformations to my new cube.
As per the 'Note 375098 - Data mart extraction from non-cumulative InfoCubes' , I have extracted using infopackage from the source infocube using the 0RECORDTP = 1 but I am not getting the option in DTP as 'Initial Non-Cumulative for Non-Cumulative values'.Since my datasource is not having the check box 'Opening balance'.
If I try running it as normal update then the DTP load is failing with the error as unlimited time characteristic as the 0calday is having the date 31.12.9999 for all marker records.
After the Full load (0RCEORDTP=1) to PSA,I also tried making the datasource to have 'Opening balance' marked using the ROOSOURCE table STCKUPD field and then tried using the option 'Initial Non-Cumulative for Non-Cumulative values' but still it's extracting zero records to Target cube from PSA.
Please guide me how to proceed with this without extracting the BX initialisation from R/3 system.
Thanks & Regards,
Ugendhar

Hi Ugendhar,
did you manage to solve your issue? I'm getting the exact same problem....
Thanks,
Enric

HELP : Inventory Cube - Missing routines in transformation

Similar Messages

Maybe you are looking for