Inventory Management Info Cube Compression!

Hi Experts!
Anybody please let me know the use of 'No Marker Update' while compressing the request in an infocube of inventory management.
Best Regards
Snuil.

Hello Sunil,
Three datasources that are mainly involved :2lis_03_BX, BF & UM.
BX is used to load the opening balance. This request (for opening balance using BX) when compressed uses the marker update( i.e the No marker update is NOT checked).
This will update the marker and set a reference points that will be used to determine the stock figures.
BF is used to load the actual material documents. First load using BF when compressed need not update the marker( i.e the No marker update is Checked!!). Here the historic documents(for which the opening balance is already loaded) are loaded but the marker need not be updated.
Then onwards the delta loads the marker needs to be updated( i.e the No marker update is NOT checked).
Follow the same strategy for UM as in case for BF!!
Please also refer to
how to inventory management
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Hope it helps..
thanks,

Similar Messages

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 (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.

Inventory Management - SnapShot Cube

Why am I not able to load the Stock Init extractor 2LIS_03_BX into the SnapShot Cube? Thanks

Hi,
The Diagnosis says:
This InfoSource is specifically set for the initial run of non- cumulatives. Only certain non-cumulative key figures are therefore displayed in the update rules.
If you donot have any Non Cumulative KF in the cube you can not use 2LIS_03_BX.
With rgds,
Anil Kumar sharma .P

Enterprise Compensation Management Info Cube

SAP BI contains a special enterprise compensation management InfoCube and queries that can be used to analyze all compensation data in detail. Now, if one has to use R/3 4.6C for the backend compensation management, can this InfoCube (using BW 3.5 on NW '04) be leveraged?...or, does the back-end have to be upgraded to the '04 Business Suite level?
Quick response from someone who has done it or from SAP will be highly appreciated!!!

Bryan,
Great response. One last question: The comment you have made about what we get with "BI Content 3.5.1 (same as BI Content 3.3 Add-on)" in terms of the "1 InfoCube, enabling the evaluation of LTI awards" is of particular interest to us. To leverage this BI content, what should be in the back end? In other words, can I leverage this BI business content using R/3 4.6C in the backend or will I need to upgrade to mySAP ERP (NW '04) and mySAP HCM?
Thanks and regards,
Puneet
> Puneet,
>
> Yes, you can still use those in BW 3.5. If you go to
> the Business Content tab in the Administrator
> Workbench you'll see them. You can also check
> help.sap.com and the Service Marketplace alias /bw
> for more details on the content delivered with each
> release.
>
> With BI Content 3.5.1 (same as BI Content 3.3 Add-on)
> there is additional content delivered:
>
> The BW Business Content for mySAP HR Enterprise
> Compensation Management comprises:
>
> <u><b>Extractors</b></u> for transferring data from
> mySAP HR Enterprise Compensation Management (PA-EC)
> to SAP Business Information Warehouse
>
> Predefined Data Models, including:
>
> 8 ODS objects, collecting data about compensation
> processes, compensation budgets, employee pay
> categories, composite market data, raw market data,
> job matching, salary structure of jobs as well as
> active and planned salary structures
>
> 5 InfoSets, providing data on compensation processes,
> compensation budgets, Comparison of Market Data and
> Employee Payment, Salary Survey Market Data and Job
> Matching as well as Comparison of Salary Structure
> Against Market
>
> 1 InfoCube, enabling the evaluation of LTI awards
>
> 24 predefined standard queries
>
> Increased visibility of all information around the
> compensation management process at your enterprise.
>
> Thanks,
> Bryan
>
>
> Message was edited by: Bryan Katis

Loading to Inventory Management Snapshot ODS and Cube

I am trying to develop an Inventory data model and have already created and loaded to the Inventory Management (0IC_C03) cube.
I have now created a Snap Shot ODS and Snap Shot cube, is there a way that I can load to these objects without having to do a re-init? Thanks

Hello Niten,
There is no need to do re-init, you can load the data into non-cumulative and snapshot targets in parallel. Through sam infopackage with which you are loading to 0IC_C03, load to snapshot targets also.
Regards,
Praveen

Inventory Management Data Model

Can I have a combined Inventory Management Snapshot and Non Cumulative? By this I mean as follows:
1. Use the Business Content model to load to the Inventory Management (0IC_C03) cube on a daily basis (loading delta from 03_BF and 03_UM)
2. Create a Snap Shot model which is loaded on a monthly basis using 03_BF and 03_UM
Thanks

Hello Niten,
Absolutely. You can use these two scenarios in combination. In fact, it is highly recommended to use snapshot scenario in combination with non-cumulative model and not as a stand alone solution.
But you need to evaluate the business requirement before taking the decesion of going with combined solution. Snapshot scenario is used to improve the query prformance.
Regards,
Praveen

Stock Valuation - Inventory Management Cube

Dear Sap Gurus,
We have implemented the Inventory Management Cube in BW.
Quantities are correct, but we have difference on the stock valuation.
For some material stock value are correct, for some other they are not correct.
A saw a lot of OSS notes and how to on this subject, I am trying to solve this issue using these documents, but based on your experience could you explain me how you solved this issue ????
Thanks,

Hi
Did you follow the correct steps?
Initialisation of BX data in the first step.(Loading of Opening Stock)
Then The request in which the opening stock was loaded must always be
compressed with a marker update
Init load of BF And UM in the second step
The request in which the historical material documents were contained
must always be compressed without a marker update and
Successive delta uploads must always be compressed with marker
updates
Check this whether you have done this or not.
Because of missing the steps here also would give you wrong values,
Regards
Ram

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 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

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

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

About archiving BW Inventory Management cubes

Hi everyone!
I would like to know what a marker in Inventory Management (BW) is. This question comes from the following: I need to archive a IM cube, and it presents the following option:
Stocks:
Only transactions
Transactions and Markers
I don't know what a marker is, so I'm kinda lost here...
Any help would be greatly appreciated (and rewarded, ofc!).
Best Regards,
Luís.

Hi,
Marker is fairly simple, you will get the details also on help.sap.com with more detailed explanation.
In a brief here is what i can tell you :
1. The marker is set on a specific date and the value of the inventory KF( NON CUMULATIVE KF) the value on that particular date is stored in the cube.
2. Since Inventory is working on the non cumulative method the difference is calculated since DAY 1. but with Marker the difference is calculated from the day of marker.
Hence it helps in retrieving faster results.
Let me know if you want more information.
Regards,
Den

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

When to compress Info Cube Data?

Dear Gurus,
I am mohan. I have a doubt regarding compression of Info Cube data. When will we get a situation to compress the info cube data. Is BW statistics used in taking this decision? Is it to be done by analysing the query runtime in the Transaction ST03? Please give me detailed information.
Best Regards
Mohan Kumar

Hi,
For performance reasons, and to save space on the memory, summarize a request as soon as you have established that it is correct, and is no longer to be removed from the InfoCube.
Note : the request ID concept can also cause the same data record (all characteristics agree, with the exception of the request ID) to appear more than once in the fact table. This unnecessarily increases the volume of data, and reduces performance in Reporting, as the system has to aggregate using the request ID every time you execute a query.
Using compressing, you can eliminate these disadvantages, and bring data from different requests together into one single request (request ID 0).
-Shreya

Inventory Management Info Cube Compression!

Similar Messages

Maybe you are looking for