Inventory Management Extractors via DSO to Cube 0IC_C03

Dear experts,
to fulfill the requirements of DataWarehouse spirit using Entry-, Harmonization- and Reporting-Layer I want to use for Inventory Management a Data Flow from extractors 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM via DSO/DSOs and later on to Cube 0IC_C03.
In this forum there are some opened threads about this issue, but none has been resolved! Many hints are about the "How to Inventory Management..." - some other say: "You can use DSO's!" - others say: "Don't use DSOs!". So: Where is the truth? Is there anybody who can provide a really praticable way to implement the above mentioned data flow?
I'm so excited about your suggestions and answers.
Thanks in advance and regards
Patrick
--> Data Flow has to be in BW 7.0

Hi Patrick,
Yes indeed there is.
Using DSOs in inventory flow is absolutely possible. Here's what you need to know and do:
1 - Firstly don't be apprehensive about it. Knowledge is power! We know that inventory uses ABR delta update methodology and that is supported by DSOs so no doubt abt it.
2 - Secondly Inventory is special because of non-cumulative and several rule group at cube level for BX and BF.
3 - Now as you want to use a DSO and I am presuming that this will be used for staging purpose, use a write optimized DSO as the first layer. While mapping from DS to this DSO, keep one to one mapping from field to Info-objects.
4- Keep in mind that from Infosource to 0IC_C03 there would be multiple rule groups present in transformations.
These rule groups will have different KPIs mapped with routines. The purpose is that from ECC only 1 field for quantity (BWMNG) and one field for value (BWGEO) is coming but from Infosource to 0IC_C03 the same fields in different rule groups are mapped to different KPIs (Stock in transit, vendor consignment, valuated stock etc) based on stock category, stock type and BW transaction keys.
5- So create a write optimized DSO. map it one to one from datasource fields. create/copy transformations from this DSO to cube maintaining the same rule groups and same logic.
6- you can also use standard DSO and create rule groups and logic at DSO level and then do one to one from DSO to Cube.
Keep in mind that these rule groups and logic in them should be precisely the same as in standard flow.
This should work.
Debanshu

Similar Messages

Inventory Management - BADI

Good day,
Currently the Inventory Management extractors(2LIS_03_BF, 2LIS_03_BX, 2LIS_03_UM) only extracts Local Currency. We would like to extract the values in Group Currency as well. Doing currency translations is not an option for several business reasons. We have to have the Group currency as it appears in the Material Ledger. I debugged the standard extractor for Inventory management and noticed that the extractor caters for a BAdI(Business Add In). Can anyone please give me an indication where I can look for this BAdI. I looked on SPRO on R/3 and there is a list of BAdI's under BW, but I don't know which one to use and how to use it. I would appreciate help in this regard.
Thank you.
Regards.
Verushca Hunter

Hi dear and welcome on board !
I think you have to fill your additional field in the usual exit provided for customer enhancement (RSAP0001) in CMOD transaction, EXIT_SAPLRSAP_001 in the include ZXRSAU01...
Otherwise you can go fot the new RSU5_SAPI_BADI...
Hope it helps!
Bye,
ROberto
...and please don't forget to reward the answers...it's THE way to say thanks here !

Business Content Inventory Management (0IC_C03) Cube

I am thinking of adding a data staging ODS to our Inventory Management model. However, I wanted to check whether the delivered cube 0IC_C03 is aggregated or whether it is a representation of the R3 extraction. If the latter is the case I do not see the purpose of an additional ODS layer. Could anyone pass their thoughts? Thanks

hi Niten,
check oss note 581778-ODS capability of extractors from Inventory Management
Symptom
Data is not updated into the ODS when you load certain data records of the 2LIS_03_BF extractor.
Other terms
ODS, 2LIS_03_BF, 2LIS_03_UM, 2LIS_03_BX, 2LIS_40_S278, 0STORNO, ROCANCEL, RODMUPDMOD, 0RECORDMODE, Inventory Management, 0IC_C03,
Application 03, Logistics Extraction Cockpit, LBIW
Reason and Prerequisites
The 2LIS_03_BF extractor does not return any "connected" after and before images, as in the SD extraction, for example.
Originally, the extractor was only designed for updating into an InfoCube. The extraction method was converted from the "D" delta process to "ABR1" with PI 2000.1 patch 4, or PI-A 2000.1 patch 4 so that it could be updated into an ODS object (see notes 322303, 385703 and 323811).
If documents are canceled in Inventory Management, a new document is generated (new document and item number).
This type of operation is transferred into BW with the "ROCANCEL" field set to 'X'. This results in the necessary inversion of quantities or value key figures. A new record is generated for this in the ODS (the "preceding document" has another key).
Example:
ODS key: Doc.
Movement data:
Document   Item    Document year   Movement type     Qty     ROCANCEL
4711       1       2002             101              +100
4712       1       2002              102              -100     X
ODS contents:
Document   Item.   Document year   Movement type    Quantity
4711       1       2002             101                 +100
4712       1       2002                                   -100
The "Movement type" field was set to "initial" in the data record for document "4712" by the processing during the ODS update.
Document 4712 is a before image (0RECORDMODE = 'X') for the ODS. Therefore, this data does not arrive in the ODS. Nevertheless, the before image (document 4712) does not have any context with the after image (document 4711) because there are different keys (document/item/document year). The SAP R/3 inventory management controls these activities with new material documents and (reversal) movement types.
BW technology note no. 747037 provides more information.
Solution
You have two options to evaluate cancellations or operations which contain reversal movement types and ROCANCEL = "X" in the ODS:
1. Implement a start routine
Insert the following code into the start routine of your update:
ODS key: Material doc.|Item number|Calendar year
BEGIN******************************
LOOP AT DATA_PACKAGE.
if DATA_PACKAGE-recordmode eq 'X'.
    DATA_PACKAGE-recordmode = ''.
    modify DATA_PACKAGE.
endif.
endloop.
END********************************
2. Change the transfer rules
With the transfer rules, do not assign the "ROCANCEL" DataSource field to the "0RECORDMODE" InfoObject in the InfoSource. As a result, only records with "0RECORDMODE" = ' ' are transferred to the ODS. For the ODS, the after images whose characteristics or key figures that are set to overwrite, are not deleted.
Other special features when updating the extractors of the inventory management into ODS objects:
1. 2LIS_03_BF and 2LIS_03_UM
a) ODS capability
For more information, see notes 322303, 323811 and 385703.
b) Key creation
For 2LIS_03_BF, see note 417703.
The following keys are available for 2LIS_03_UM:
1. MCMSEG-BUKRS
2. MCMSEG-BELNR
3. MCMSEG-GJAHR
4. MCMSEG-BUZEI
Field no. 4 is not delivered as standard in the extract structure, but it can be added using the Logistics extract structures Customizing Cockpit.
Field no. 1 may not be included in the relevant organizational structure.
2. 2LIS_03_BX (up to and including 3.0B 2LIS_40_S278)
The dynamic stock calculation from stocks (2LIS_03_BX) and movements (2LIS_03_BF) is only possible with (non-cumulative) InfoCubes.
Using ODS technology is only useful in this context for:
- an Enterprise DataWarehouse layer
- the realization of a snapshot scenario:
See the How to paper for this topic at:
-> http://service.sap.com/bw
-> left navigation area: SAP BW InfoIndex
-> info index: N ("Non-cumulatives") ->
"How to... handle inventory management scenarios in SAP BW 3.x" (pdf)
Use note 773823 to update the 2LIS_03_BX InfoSource into an ODS.
Note also that you cannot update any key figures into an ODS object (see notes 752492 and 782314).

Inventory Management Cube 0ic_c03, 0StockType

In the Inventory Management Cube 0ic_c03 queries,I've found that 0StockType has descriptions that are misleading because of the way they are written in domain bstaus (R3 side), especially when seeing the key and SHORT description (truncated beyond meaning).
OK I can correct these by changing BStaus 's texts.
The main changes I'd do are for the Customer Consigment, Customer Return Packaging and Material Provided to Vendor descriptions.
But what does 0StockType 'blank' (or #) mean ?
(It seems to mean something like Valuated Stock Valuation and 'Not Defined' is not very good in a Query result)

Well, no one replied, but I got feedback from OSS. So just in case anyone is interested.....
I had to use r3 > se11 to change the domain descriptions myself.
Bstaus 'blank' I put as 'Valuation'
I also improved some of the Bsttyp descriptions whilst there

Queires on Non-Cumulative Inventory Management Cube 0IC_C03 Not Working

Hello all.
I am trying to use the 0IC_C03 Inventory Management cube with non-cumulative key figures. I followed the How to...Handle Inventory Management Scenarios in BW paper to a tee.
Steps I followed:
1. Ran initialization of beginning balance with 2LIS_03_BX
2. Ran the historical job with 2LIS_03_BF
3. Uploaded to BW the Initialization (BX) and compressed without setting the "No Marker Update" flag
4. Uploaded the historical movements (BF) and compressed setting the "No Marker Update" flag
Now, to this point, everything was fine. Quantities were as expected. Dollar values were as expected. The problem occurs once I load deltas:
5. Loaded delta for 2LIS_03_BF and compressed without setting the "No Marker Update" flag as instructed in the How To... paper
Query example:
MATERIALA:
Initial Stock Balance = 1000 EA
Delta had stock issue of 150 EA (so the stock balance should have decreased from 1000 to 850)
Now, I have the record in BW showing the stock issue of 150. However, the non-cumulative key figure within the query still shows 1000. And when I drill down by calendar day, I would expect the result to show 850, but it seems to add the 150 before taking it away resulting in 1000 which is actually the initial stock balance. It is like it is not recognizing the updates.
Any help would be appreciated.
Thanks,
Brent

Hi!
Here is what helped in my case, very similar to your:
In DTP for 2lis_03_bx (not only in infopackage, as it is said in manual!) you have to change "Extraction Mode" parameter to "Initial Non-cumulative for Non-cumulative values"

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.

Missing content for inventory management (cube 0IC_C03)

Hi everybody,
I installed the following BI content for inventory management: Cube 0IC_C03, InfoSource 2LIS_03_BX and transfer rules from data source 2LIS_03_BX to info source 2LIS_03_BX. However, I'm not able to the update rule from info source 2LIS_03_BX to info cube 0IC_C03. I can only find the old update rule 0IC_C032LIS_40_S278 -> 0IC_C03.
I also couldn't find the update rule for material movements from 2LIS_03_BF to infocube 0IC_C03.
How can I find this missing content. We are using BI Content Release 704 Level 1.
Thanks for your help!
Thomas

Hi Oscar,
unfortunately, I was not able to find a transformation for the datasource migrated to 7.0.
Btw, how do I determine to which version data sources are replicated. I have an underlying ECC6.0 system. When I replicate all data sources for that source system, datasources automatically show up as 7.0. I'm missing the pop-up question whether or not I want to replicate as 3.5 or 7.0.
Thanks in advance!
Thomas

Selective Deletion on Inventory Cube 0IC_C03 via Calendar Day

Hello Group
I am trying to do a selective delete to our inventory cube 0IC_C03 and found there is not an option to select day.
Does anyone have any thoughts on how do delete using day? Please note that my cube has been compressed and I do not have a request in the cube.
Thanks
Frank

Hi Frank,
REPORT ZRSDRD_SEL_DELETION                     .
DATA:
    l_thx_sel   TYPE rsdrd_thx_sel,
    l_sx_sel    TYPE LINE OF rsdrd_thx_sel,
    l_s_range   LIKE rsdrd_s_range,
    l_t_range   TYPE rsdrd_t_range,
    l_t_msg     TYPE rs_t_msg.
******************* 0CALDAY *****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = '20030308'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0CALDAY'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0PLANT **********************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'PLNT'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0PLANT'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
************** 0MATERIAL ****************
l_s_range-sign   = 'I'.
l_s_range-option = 'EQ'.
l_s_range-low    = 'MATERIAL'.
*l_s_range-high   = .
l_s_range-keyfl = 'X'.
APPEND l_s_range TO l_t_range.
l_sx_sel-iobjnm   = '0MATERIAL'.
l_sx_sel-t_range = l_t_range[].
INSERT l_sx_sel INTO TABLE l_thx_sel.
CLEAR l_s_range.
REFRESH l_t_range.
CALL FUNCTION 'RSDRD_SEL_DELETION'
     EXPORTING
          I_DATATARGET      = 'ZICRT_C37'
          I_THX_SEL         = L_THX_SEL
          I_AUTHORITY_CHECK = 'X'
          I_THRESHOLD       = '1.0000E-01'
          I_MODE            = 'C'
          I_NO_LOGGING      = ''
          I_PARALLEL_DEGREE = 1
          I_NO_COMMIT       = ''
     CHANGING
          C_T_MSG             = L_T_MSG.

Inventory Management DSO Capabilities

Hi All,
In a typical inventory management scenario (for 0IC_C03), we have inventory datasources (BF, BX and UM) directly feeding the cube.
Due to system architecture we now have to place data coming from these datasources into a DSO first and then feed the inventory cube.
Please guide me as to what should be the key combination for the DSOu2019s of these datasources (i.e. for BX, BF and UM) .
Regards
Anshul

Hey!
Search in OSS for the following note:
Note 581778 - ODS capability of extractors from Inventory Management
This will help you for this what you need to know.
I think for BX is a DSO not necessary because you use it just for the initial load.
Best regards,
Peter

Inventory Management 0IC_C03 customizations

Dear Experts,
I have a task in hand to implement Inventory Management in SAP BW 3.5. Now, this is the first time that we will be implementing anything related to Logistics and I havenu2019t done so earlier in my support projects. I have got 10 hrs of downtime.
I need to fetch the report for both Trading as of now.
The fields needed in the report by the customer are:
Plant
Plant Description
S. Loc.
S.Loc. Description
Opening Stock Qty,
Opening Stock Value,
Receipts against PO Qty,
        Value,
Receipt against STO Qty,
        Value,
Receipt against return SO Qty,
     Value,
All Other Receipts Qty,
      Value,
RevaluationValue,
Miro Differences,
Issue against SO Qty,
      Value,
Issue against STO Qty,
        Value,
All Other Issues Qty,
      Value,
Closing Stock Qty,
           Value,
Book Inv Qty,
Physical Inv Count.
I am planning to define these as Zkey-figures and write routines in update rules based on processing keys to capture each qty and value separately.
My questions are:
1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
2) For every above field, customer has given standard movement types.
For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
            for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
If you know which processing key can be used for above fields, please let me know.
3) What are the other fields that need to be considered in routines. If possible please specify field wise.
4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
Thanks friends.

BJ,
My questions are:
1) What are the fields from above that can be pulled from standard BI Content Reports (if possible, please specify which report)? OR fields (or combination of fields) that are already in the cube?
~ You will get fields from the Cube only.
2) For every above field, customer has given standard movement types.
For ex: for Receipts against PO = Mov Types 101,105,123,162 (Doc Type IN/IM)
for Receipt against STO = Mov Types 351, 352 (Doc Type UB)
~ Check this Table in Source system for BW Keys : TMCLVBW
But when brought in BI, all routines are based on processing keys (BW Transaction key). Where can I find mapping of each processing key to the corresponding movement type?
If you know which processing key can be used for above fields, please let me know.
Check this table
3) What are the other fields that need to be considered in routines. If possible please specify field wise.
That depends upon your requirement in the report or Check the standard Dcoument for Inv management in SDN search.
you will get lot of help.
4) Should I extend the 0IC_C03 with these new custome KFs creating a new zcube or should I add only required fields in zcube.
If I follow the latter, will there be any impact on standard BF/UM runs as in If I load till PSA and from PSA I follow my customized update rules terminating into my customized cube?
~Best Practice and even SAP Recommends Make a ZCUBE and then enhance or customize to fullfill your rek.
No impact follow IM steps for BW.
Make sure you keep these things in Mind:
There are 3 SAP delivered transactional data sources for stock management.
2LIS_03_BX : Always needed to carry the initialization of the stocks.
2LIS_03_BF : Initialize this in source if you need historical data else an empty init can be done for this to load only future delta records. If the Source system is new then no need to do an initialization.
2LIS_03_UM : Only needed if revaluations are carried out in Source. This data source is helpful if adjustment in material prices is done time to time otherwise it wonu2019t extract any data.
2. Check list for source system. Needs to be carried out before initialization of the above 3 data sources .
A.   Table TBE11 : Maintain Entry u2018NDIu2019 with text u2018New Dimension Integrationu2019 and activate the flag(Note 315880)
B.   Table TPS01 : Entry should be as below(Note 315880)
PROCS u2013 01010001
INTERFACE - SAMPLE_PROCESS_01010001
TEXT1 u2013 NDI Exits Active
C.   Table TPS31 : Entry should be as below(Note 315880)
PROCS u2013 01010001
APPLK - NDI
FUNCT u2013 NDI_SET_EXISTS_ACTIVE
D.   Tcode u2013   MCB_
In most cases you need to set the industry sector as u2018standardu2019. For more info please see Note 353042
E.    Tcode u2013 BF11
Set the indicator to active for the Business warehouse application entry. This entry may needs to be transported to the production system. (Note 315880)
3. After running the setup data, check the data for the fields BWVORG, BWAPPLNM, MENGE. If no data available in these fields then some setting mentioned in the above checklist are missing in R/3. Correct the issue and rerun the setup data.
4. Data staging with DSO for BX extractor is not allowed. Data should directly load from extractor to Cube only once. Choose the extraction mode as u2018Initial Non-cumulative for Non-cumulative valuesu2019 in the DTP.
5. DSO is possible for BF. If you are creating a standard DSO then choose the fields MJAHR,BWCOUNTER,MBLNR,ZEILE as key fields. Some of these fields wonu2019t be available in the standard data source but the data source can be enhanced using LO Cockpit (LBWE) to add these fields. In addition to these other fields depending upon the DSO structure is also possible.
Note 417703 gives more info on this.
6. Point-5 is valid for UM also. The Key fields could be a combination of MJAHR,MBLNR,ZEILE,BUKRS fields. Note 581778
7. Data load to the cube should follow the below process
A.      Load the BX data. Compress the request with stock marker(uncheck the marker option).
B.      Load the BF and UM init data. Compress the loads without the stock maker(Check the marker option).
C.      The future delta loads from BF and UM should be compressed with Stock marker(uncheck the marker option).
8. If in future the cube needs to be deleted due to some issues then the load process should also be carried out as above. (only init of BF and UM should be loaded first and then the deltas should be processed)
9. To check the data consistency of a Non cumulative cube the standard program SAP_REFPOINT_COMPLETE can be used. To check the compression status of the cube the table RSDCUBE can be refered. Before the compression of BX request, the u2018REFUPDATEu2019 field should be blank and after the compression the value should become u2018Xu2019. Check Note 643687 for more info.
10. After BX data load to cube the data wonu2019t be visible by LISTCUBE. Only after compression the data can be seen by running a query on the Non cumulative cube.
~AK

Extend Inventory Management (0IC_C03) with new field MSEG-INSMK

Dear Experts, We are using Business Content InfoCube "Material stocks/movements" (0IC_C03) in Area "Inventory Controlling/Inventory Management" in BW. We are using following Business Content DataSources: Stock Initialization for Inventory Management 2LIS_03_BX Goods Movements From Inventory Management 2LIS_03_BF Revaluations 2LIS_03_UM Everything works fine with delta load till now. Now we have a new requirement so that we have to fill additionally the R/3-Field MSEG-INSMK in existing Inventory Management InfoCube (0IC_C03). The Business Content DataSource (2LIS_03_BX/BF/UM) doesn't provide R/3-Field MSEG-INSMK and I don't find any other Datasource for the R/3-Field MSEG-INSMK ("Document Segment: Material" - Stock Type). How can we extend the InfoCube 0IC_C03 with the R/3-Field MSEG-INSMK? Should I define a new Generic Datasource based on the table MSEG to extract the field INSMK. The table MSEG is very large. What would be Delta-Specific Field for Generic Delta? I would load the data from generic DataSource into a new DSO. And I can read the field MSEG-INSMK per Look-Up from the DSO in the transformation to the InfoCube 0IC_C03. Is this the solution? Many Thanks Moha

2LIS_03_BX cannot be enhanced. There is an SAP note that says enhancing this Datasource is not supported.
2LIS_03_BF can be enhanced though, and the process is just like enhancing any other LO Datasource.
So you can include the new field in the cube, enhance BF and load to the cube. With this, you will be able to report the INSMK field on the goods movements. But as INSMK is not present in BX, you will not be able to report the INSMK field on stock position reports.

Inventory loads to cube 0IC_C03

Hi Guys ,
I am loading data to Inventory Cube 0IC_C03 .I have done all the steps .I have 1 question ie ..intilally i loaded data to cube from 2LIS_03_BF data source .I did the following steps :
u2022 Init Delta (2LIS_03_BF) with data transfer.
u2022 Release Request with No Marker Update (Tick).
Now from tomorro we will get delta loads .My question is do we need to compress delta request with NO MARKET UPDATE (TICK) ?
Or
Do i need to unTick The option NO MARKER UPDATE .
The data is very critical here .Please let me know if you have the right answer .
Regards
Santosh

Hi,
Pl look at below
Marker Update is used to reduce the time of fetching the non-cumulative key figures while reporting. It helps to easily get the values of previous stock quantities while reporting. The marker is a point in time which marks an opening stock balance. Data up to the marker is compressed.
The No Marker Update concept arises if the target InfoCube contains a non-cumulative key figure. For example, take the Material Movements InfoCube 0IC_C03 where stock quantity is a non-cumulative key figure. The process of loading the data into the cube involves in two steps:
1) In the first step, one should load the records pertaining to the opening stock balance/or the stock present at the time of implementation. At this time we will set marker to update (uncheck 'no marker update') so that the value of current stock quantity is stored in the marker. After that, when loading the historical movements (stock movements made previous to the time of implementing the cube) we must check marker update so that the marker should not be updated (because of these historical movements, only the stock balance / opening stock quantity has been updated; i.e. we have already loaded the present stock and the aggreagation of previous/historical data accumulates to the present data).
2) After every successful delta load, we should not check marker update (we should allow to update marker) so that the changes in the stock quantity should be updated in the marker value. The marker will be updated to those records which are compressed. The marker will not be updated to those uncompressed requests. Hence for every delta load request, the request should be compressed.
Check or uncheck the Marker Option:
Compress the request with stock marker => uncheck the marker update option.
Compress the loads without the stock maker => check the marker update option.
Relevant FAQs:
1) The marker isn't relevant when no data is transferred (e.g. during an delta init without data transfer).
2) The marker update is just like a check point (it will give the snapshot of the stock on a particular date when it is updated).
Reference information:
Note 643687 Compressing non-cumulative InfoCubes (BW-BCT-MM-BW)
Note 834829 Compression of BW InfoCubes without update of markers (BW-BEX-OT-DBIF-CON)
Note 745788 Non-cumulative mgmnt in BW: Verifying and correcting data (BW-BCT-MM-BW)
Note 586163 Composite Note on SAP R/3 Inventory Management in SAP BW (BW-BCT-MM-IM)
Thanks and regards

Inventory Management 0IC_C03: Beginning and ending inventory

Hi Gurus
My report is based on Inventory Management cube and I have a requirement where in I need to show Begining Inventory and Ending Inventory for Plant per Period.
There is no KF for Beginning Invin SAP standard model in inventory management cube (0IC_C03 cube), so I thought to restricting total quantity by Fiscal period and Offset by minus one to get begining inventory.
Here is my report layout:
I have got : Period , Plant in rows and Beginning and ending inventory in Columns.
Desired Output:
Fiscal Period | Plant | | Begining Inventory | Ending Inventory.
03/2009        | 1001 |    100                       | 50
Actual Report output
Fiscal Period | Plant | | Begining Inventory | Ending Inventory.
02/2009        | 1001 |                 100          |
03/2009        | 1001 |                                | 50
So basically report is being split on two lines for current and previous (due to restriction in begining period : Offset =-1 on period).
Question is how to achieve both begining and ending inventory for a period in same line.
Thanks in avdance for help and time
SA

HI Naveen
Thanks for the reply. Non *** KF are already being used and Standard SAP model is being followed. Problem is not with back end but with frontend. Data coming on the report is fine but problem is how to show them on same line. Remember Beginning inventory for current open is ending inventory for previous month and in SAP content there is no KF called as begining inventory. Basically data from two consecutive periods (current and previous one) needs to be on same row of report, but they are coming on different rows if we have period in drilldown by period. this makes sense but how to overcome this.
This, We have all the correct data but facing issue while displaying that on frontend.
Thanks
Sorabh
Edited by: Sorabh on Mar 23, 2009 5:01 PM

Movement Type in Inventory Management Cube

Hello Guys,
I am new to the area of Invenotry Management. I have seen the How to Guide and blogs by Surendra for Inventory Management scenarios.
One of initial doubt is that the cube 0IC_C03 does not have Movement Type. As per the blog, we can define transaction keys in BW but how do I pull it in my Cube. Is ehnacing the extract strcuture BF the only option? If yes, what logic do we follow to add movement type to BF?
Also as per SAP Note, we cannot enhance BX to include movement type. So would it create a problem if BX does not have a movement type and BF has?
Looking forward to solutions
Thanks n Regards,
Abhishek

Dear John
The movement type has important control functions in Inventory Management.
For example, the movement type plays an important role in
=> updating of quantity fields
=> updating of stock and consumption accounts
=> determining which fields are displayed during entry of a document in the system
thanks
G. Lakshmipathi

Cubes on the Materials management Cube 0IC_C03

HI,
We need to create cubes on the Materials management Cube 0IC_C03 to take care of the huge inventory data we have . These will be a copy of 0IC_C03 and 0IC_C03 will be a staging layer.
Want to know how will the marker update will work on the new cubes?
Thanks.
Nitin

Hi,
Look this link wll give u full detailes about marker updats and so on....
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
***********Asign Points if usefull*******
Cheers,
Satya

Inventory Management Extractors via DSO to Cube 0IC_C03

Similar Messages

Maybe you are looking for