Inventory Management DataSource

Hello Experts -
Are there any datasources for the following fields? These fields are available in the MM03 t-code. These are related to Inventory Management. I checked 2LIS_03_BF and 2LIS_03_UM but couldn't find these. Any ideas any one?
FIELD                                                   TechName Tbl
X plant matl status from Basic Data     MSTAE     MARA
UOM from Basic data                                     MEINS     MARA
Material Type from Mrp 1                     DISMM     MARC
Min lot size MRP 1                                     BSTMI     MARC
Safety Stock level MRP 2                     EISBE     MARC
SLOC MRP indicator MRP 4                     DISKZ     MARD
Replen order pt MRP 4                     LMINB     MARD
Replen qty MRP4                                      LBSTF     MARD
Special procurement key - MPR2     SOBSL     MARC
Rounding value - MRP1                      BSTRF     MARC

these are master data tables..
look at :
0material_attr
0mat_plant_attr
Assign points if it helps

Similar Messages

2LIS_03_BF - Inventory Management DataSource

Dear reader,
i scheduled LBWE for 2LIS_03_BF Datasource about 30 hrs ago and the job is till running on R3 side. the extraction was set from year 2006 july.
does it normally take this long. If not, what could be the problem. Shall i schedule it again, or it normally takes this long.
please advise and let me know if you need more information to find out the cause.
regards.

You're correct...I did mean LBWG. I was typing too fast and got my LBW* tcodes all mixed up.
You would use the LO Cockpit (LBWE) for scheduling the V3, or other delta job, anytime after you have done an init InfoPackage in your BW environment. This job will fill the delta queue table for the extractor. The delta queue table differs from the setup table, therefore you can schedule this job while the OLI*BW setups are executing.
OLI*BW tcodes execute initial setups of LIS DataSources, whereby it extracts everything into a setup table and this setup table is the source from which Full and Init w/ Data Transfer extract InfoPackages will pull data.
LBWE is the Logistics Cockpit, which is used for maintaining the LIS DataSource structures, activation of LIS DataSources and scheduling of Update (delta) jobs. The delta jobs fill the delta queue table, which you can view in RSA7, and is the source from which Delta extract InfoPackages will pull data.

Inventory Management: Valuated Stock Value

Hello Experts -
We're using inventory management. We're just bringing in 2lis_03_bf which is the material movements and the standard price datasource.
The plant valuated stock quantity and the valuated stock value are fine. The SLOC valuated stock quantity is fine. We're using the non-cumulative key figures for the valuated stock quantity and the valuated stock value. The SLOC valuated stock value isn't correct. So I just created a calculated key figure where I'm multiplying the quantity with the standard price.
This works fine but when I look at the plant level and use this CKF, the aggregation threw me off. So I changed the aggregation on CKF at the Bex level.
This works fine in dev and qa where I don't have too much of data. But as soon as I'm in in production, the query times out and gives me an error saying I reached the buffer limit.
I was thinking of calculating the valuated stock value at the ETL layer but now I'm thinking that if I do that and the price of a material changes, I'll again have the same problem. I can't re-load every time a material price changes.
Can someone please help me with this scenario?
Thanks!
Edited by: Siegfried Szameitat on Oct 29, 2008 9:30 AM
do not offer points, it is against the rules

Hi Syed,
Deriving values by multipling with price also not correct. results will not match with R/3.
Value Calculation
In principle, values are updated with Plant, Material, and Stock Category only. Quantities are updated with these characteristics, as well as with Storage Location, Batch Number, and Stock Characteristic
Check SAP Note 589024: Evaluations in BW with the Characteristics Storage Location and Stck Char.).
Hope it Helps
Srini
Edited by: Siegfried Szameitat on Oct 28, 2008 4:17 PM

Inventory management: Validy dates in queries???

Hi experts,
We have BW 7.0.
I have loaded data on 04.03.2010 with BF- and UM-datasources and compressed it correctly.
When I now look into the validy table for plant 0001 there is a validy range from 03.07.1997 to 08.02.2010.
But when I start a query for 09.02.2010 system says "no data found".
The document "How To Handle Inventory Management Scenarios in BW" says that I should show the result in parenthesis!
What is up here?
But I don't want to update this validy table!!!
Pls help!
KR,
Raimund
Text in document:
...For example, if data with document data was loaded into the
InfoCube with values from 01.01.2002 to 15.02.2002 (assigned to the respective time
characteristic), the validity interval is also determined by these two date values. You can
extend the intervals by maintaining the table (transaction RSDV). Stock balances are
displayed for requests that relate to this period. If you start a query that requests the
stock balance for 16.02.2002 or later, the result is displayed in parenthesis (a blank
value is displayed in BW 2.0B and 2.1C), since it lies outside the validity area (providing
that the validity table was not manually extended using transaction RSDV)....

Hi,
Hi,
Use 2LIS_03_BX, 2LIS_03_BF, 2LIS_03_UM to 0IC_C03 Cube and design the report.
Use :
0VALSTCKVAL   " for Value
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month
Use the above combinations in New Selections in columns and go it.
For Qty Opening:
New Selection bad drag abd drop following things
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input) and set the offeset
                               value = -1 bcoz if user will give 12.2009 , so it will display 11.2009 closing stock, this is opening for 12.2009.
For Qty Closing:
New Selection bad drag abd drop following things
0VALSTCKQTY   " for Qty
0CALMONTH        " for Month and restrict with less then or equalto option variable (single value, user input) .
In the same way build for Value and other Keyfigures on 0IC_C03.
And
Drag & drop
0MATERAIL
0PLANT " Give some Input Variable.
See the steps.
Treatment of historical full loads with Inventory cube
Setting up material movement/inventory with limit locking time
If it is BI 7 then for BX in in DTP in Extraction Tab you need to select Extacrion mode = NON-Cumulative option.
See this thread related to Inventory.
Re: Inventory Mangement steps - questions
Thanks
Reddy
Thanks
Reddy

Inventory Management Scenario

Hi BW Experts,
I was working on the Inventory Management screnario as in How to Handle Inventory Management Scenarios in BW with cumulative KFs. I read many of the forum postings but I am still little bit confused about the sequence of the loading. As per my understanding, BX goes to 0IC_C03 bus. content cube and snapshot ODS. BX load in 0IC_C03 is compressed. Then BF and UM goes to snapshot ODS, snapshot infocube and 0IC_C03 (initilized for Delta). Then the generic extractor from snapshot ODS goes to snapshot infocube as monthly load and also to ODS itself. Now the questions are:
1-) Is the sequence above correct? If not could you pls. explain? What are reasons behind of this?
2-) What are the functions of these objects exactly, in detailed? How do you validate data (by comparing 0IC_C03 and snapshot cube)?
3-) Why the generic extractor goes to infocube and ODS together, what is the reason?
4-) Is snapshot infocube loaded with BF and UM as delta daily? After initialization am I going to load the snapshot infocube every night or just the 0IC_C03?
5-) Do I have to put 0CALDAY into Agg. Ref. char. in the maintenance screen of the defined custom KFs (Z* keyfigurs for this scenario) or just in the report enough?
6-) Are the routines working correctly except for
diff_month(2) type i-> "i" is going to be changed into "n"
After I loaded in the above sequence when the bx is loaded into 0IC_C03 cube transferred data records are less than added. What is the reason?
Contributions are highly appreciated. Thanks.
Best Regards,
Message was edited by: John Seker
Message was edited by: John Seker

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

Inventory management with SnapShots

Hi
I've got this document, "How to handle inventory management scenarios in BW".
It's generally very clear, no problem to understand the standard solution (0IC_C03, non-cumulatives).
But I really didn't understand the explanation about Snapshot on the monthly positions.
So I ask someone to explain how does the concept work.
Example:
The document refers to material movements in 01.2004 and 03.2004.
Question 1:
What are the values posted to the DSO and to the InfoCube after initial load (after the first load of datasources BX and BF/UM) ???
Will we have registers to 01.2004, 02.2004, 03.2004 and 12.9999, both in the DSO and in the InfoCube ?
How does month 12.9999 work?
Question 2:
What are the values posted to the DSO and to the InfoCube after the second BF load?
Let's suppose 2 movements in 04.2004 and 2 movements in 05.2004.
Will we add registers to 04.2004 and 05.2004 both in the DSO and in the Cube?
Thanks in advance.
Cesar Menezes

Hi Cesar,
Not sure if this could be helpful.. but still sharing..
http://www.biportal.org/discussion_forum?mode=MessageList&eid=350671
As even I want to understand differences between 2 methods.. Snapshot and 0IC_C03 (non cumulative)
Could you find any leads?
Regards, Vittali

Inventory management process key values plz

Hi gurus,
can anyone help me with the process key values
in my update rules i have this for issues
process keys= 100,101,104,105,106,110
and for receipts 000,001,004,005,006,010
what do they mean i am using the standard update rules
its very urgent becoz i am getting the stock values wrong
thanks and regards
neelu

hi Neel,
check oss note 352344 - Process key + reversals in Inventory Management ?
Symptom
This note is a consulting note and describes the use of the process key (0PROCESSKEY) in Inventory Management (MSEG). It focusses on the way the system deals with reversed transactions for DataSources 2lis_40_s279 and 2lis_03_bf.
To be able to use theses DataSources, you ABSOLUTELY MUST activate the transaction key generation (process key, PROCESSKEY) using Transaction MCB_ (from the OLTP IMG for BW: SBIW) (standard, retail or consumption goods).
The following transaction keys are available
(PROCESSKEY/Appl. Component/Description):
000/MM        Misc. receipts
001/MM        Goods receipt / vendor
004/MM        Article transfer posting receipt
005/MM        Stock correction inventory +
006/MM        Stock correction other +
007/IS-R      Receipt value-only article (single article
              posting)
010/MM        Receipt from stock transfer
002/IS-R      Merchandise clearing receipt
003/IS-R      GR from DC
100/MM        Misc. issues
101/MM        Returns / Vendor
104/MM        Article transfer posting issue
105/MM        Stock correction inventory -
106/MM        Stock correction other -
107/IS-R      Issue value-only article (single article
              posting)
110/MM        Issue from stock transfer
102/IS-R      Merchandise clearing issue
103/IS-R      GI from DC
450/IS-R      Generic Article (not relevant)
Remark: Transaction keys 002/003, 102/103 break down the core keys 010/110 in more detail with respect to retail processes. They are only available in an R/3 Retail.
As you can see in the overview, the transaction keys can be divided according to receipts and issues in Inventory Management. Furthermore, the transaction keys are displayed according to reversed and regular transactions.
A regular receipt has a debit/credit indicator "S" (SHKZG, 0DCINDIC), whereas a regular issue has a debit/credit indicator "H".
For reverse transactions the opposite is true.
Transaction                            D/C ind.   D/C ind.
                                        S          H
RECEIPTS
0 Misc. receipts                        regular    reversed
1 Goods receipt / vendor               regular    reversed
2 Merchandise clearing receipt        regular    reversed
3 GR from DC                            regular    reversed
4 Article transfer posting receipt    regular    reversed
5 Stock correction inventory +        regular    reversed
6 Stock correction other +            regular    reversed
7 Receipt value-only article          regular    reversed
10 Receipt from stock transfer        regular    reversed
ISSUES
100 Misc. issues                       reversed   regular
101 Returns / vendor                   reversed   regular
102 Merchandise clearing issue        reversed   regular
103 GI from DC                         reversed   regular
104 Article transfer posting issue    reversed   regular
105 Stock correction inventory -      reversed   regular
106 Stock correction other -          reversed   regular
107 Issue value-only article          reversed   regular
110 Issue from stock transfer         reversed   regular
Note: You can also recognize a reversal for DataSource 2lis_03_bf by means of the entry 0STORNO = ´X´. The fields that are marked with X in the table are then transferred with negative +/- sign. This was not the case with DataSource 2LIS_40_S279!!! In the case of DataSource 2LIS_40_S279 more logic was required in the BW update rules to make sure that key figures were updated correctly.
Example:
In the delivered InfoCubes 0CP_IC_C1 (CP) and 0RT_C01 (Retail), for example in key "Stock correction +", transaction keys 5 and 6 were grouped together. Furthermore, distinction is to be made between the different stock types. Depending on which stock types you want to distinguish between in different key figures, you must use a corresponding condition (IF statement) in the update rules in the BW.
Example (pseudo source code):
Updating Routine "stock adjustment +" for 2lis_02_bfIF ( STOCKCAT is initial ) AND         "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 )._ RESULT = TRANS_AMOUNT. RETURNCODE = 0.    "Updating Key figureELSE. RETURNCODE = 4.    "No Updating of KeyfigureENDIF.
The pseudo source code for 2LIS_40_S279 read as follows:
Updating Routine "stock adjustment +" for 2lis_40_s279IF ( STOCKCAT is initial ) AND         "Evaluated stocks ( PROCESSKEY = 5 OR PROCESSKEY = 6 ).    IF DCINDIC = 'S'.      RESULT = TRANS_AMOUNT.    "regular    ELSE.      RESULT = -1 * TRANS_AMOUNT.    ENDIF.    RETURNCODE = 0.    "Updating Key figureELSE.     RETURNCODE = 4.    "No Updating of KeyfigureENDIF.
Here, the debit/credit indicator must be checked in accordance with the table above. Transactions 5 and 6 are receipts in Inventory Management. As the debit/credit indicator is set to "S", it is a regular transaction whose value(TRANS_AMOUNT) is assigned to the key figure. In the other case (debit/credit indicator = "H") it is a reversal, that is, the transaction should reverse a transaction that has already been updated. For this, the value is multiplied by -1 so that a corresponding decrease/reduction of this key figure is achieved during the update of the key figure in the InfoCube.
This logic is no longer required for the 2LIS_03_BF (see first pseudo source code), because the reversed quantity and values are automatically provided as negative with the help of the 0STORNO field.
Using this DataSource 2LIS_03_BF, it is for example possible to create a key figure such as "Reversed receipts", which is not a part of the Business Content delivered. The following pseudo source code of an update routine makes this clear:
Update routine "Reversed receipts"
IF ( PROCESSKEY = 1 ) AND   (STORNO = ´X` ) "Reverse     RESULT = -1 * TRANS_AMOUNT.     RETURNCODE = 0.ELSE.     RETURNCODE = 4.      "no update of key figure!ENDIF.
Note: For DataSource 2LIS_40_S279 the pseudo source code read as follows:
Update routine "Reversed receipts"
for 2LIS_40_S279IF ( PROCESSKEY = 1 ) AND   ( DCINDIC = H ) "Reverse     RESULT = TRANS_AMOUNT.     RETURNCODE = 0.ELSE.   RETURNCODE = 4.      "no update of key figure!ENDIF.
To be able to understand the overall scheme more comprehensively, you should have a look at the update rules of the Standard Business Content for retail or consumption goods (for example InfoCubes 0RT_C01 or 0CP_IC_C1).

Starting Inventory Management in BW

Hi experts,
I am starting Inventory Management in BW and using the How to Guide.
I understand how important the Stock init is and the need to block postings or to init during a period when no sotck movements occur.
This is especially important for us as we have stocks in Europe and Stock in the US.
Though I am still a little confused of during which steps of the Init the stock movements have to be blocked.
Here is how I processed in Dev system:
1- Activated necessary BI content in BW and 2LIS_03_ datasources in R/3 (transaction LBWE)
2- Intilialized the current stock in R/3 (transaction MCNB)
3- Executed INIT Infopackage to load current stock PSA table and then DTP (Extraction mode set to Initial Non-Cumulative for Non-Cumulative Values) to load the 0IC_C03 Cube
4- Deleted 03 Setup Tables in R/3 (transaction SBIW)
5- Initialized 03 Setup Tables (transaction SBIW)
6- Executed INIT Infopackage to load Good Movements PSa and then DTP to 0IC_C03 Cube (delta extraction)
7- Handle Delta movements in Process chain
Here are the questions I have:
- Am I missing any steps (except stock valuation part)?
- Do Stock posting have to be blocked during all these phases ? Or can they be queued in delta queue before doing the INIT of Infopackage (Step 6)?
- There doesn't seem to go through step 5 restricting on plant/stock. So I need to init for all plants (seems to be only possible to restrict on posting date or document) and make sure all postings are blocked right?
Thanks a lot for your answeres.
Olivier

See if this helps:
http://help.sap.com/saphelp_nw04/helpdata/en/99/27443cbe062e59e10000000a114084/frameset.htm

Posting block Question in How to handle inventory management scenarios

Hi all - I have a question in document
<b>"How to...Handle Inventory Management Scenarios in BW"</b>
can anyone please tell me what a posting block is in this document...
also I did not understood what a Validity table is?
thanks,
Sabrina.

Hi Sabrina!
A 'posting block' period is something that now you are facing in inventory management, but you have to consider it in ALL logistic cockpit flows (what you can see in LBWE).
This requirement can be easily explained in this way: as you know, to fill a setup table you have to activate the extract structure of the datasource for which you want to run the setup job (otherwise the system says that no active extract structure exists, do you remember ?); but, by doing so with the posting operations open (in other words, users can create new document or change the existing ones), you run the risk that these records are automatically included in the extraction queue (or in SM13 if you are using unserialized method) AND also collected in setup table ! And you will have the same records with the initial load (from setup table) and then the same from delta load (from the queue): a nice data duplication.
To avoid this situation, a "posting block" (or a "free-posting period" or a "downtime") is requested. No one can post new document during your setup job...
Hope now is clearer...
Bye,
Roberto

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.

Prod issue with Inventory management in BW ..please help

hi Folks
i am new into inventory management extraction into BW. i have read all the document regarding the extraction. My question is
1. what all the comon produciton issues you wil come across when you do the inventory management
2. what is the dificlut challenge you face during extraction and validation
3. what all things you need to consider or keep in mind while doing this process
4. what is pros and cons of this process ..any bettar way to improve this process?
please shoot me your thougths ..which will helpfull for my new task..

My Dear Friend...
Typical Steps for refreshing your understanding :
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialization.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
ALWAYS LOAD in order as BX datasource first then BF datasource and then UM datasource in cube
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with posting Block.
And about Reconcilitation of data ...Count the number of records in R/3 in particular table and check with BW is its matching...When you request in Detail Tab you can find the number of records...
Then check if the balances are matching in R/3 and BW...saying for ex: Check opening Stock for today in both the systems...
If you follow the process properly I dont think you will face any issues...I havent ever seen any complication in Inventory loading...Dont worry...Just follow the typical LO Extraction steps...All Good
Regards...
Sandhya

How to handle inventory management scenario

Hi All,
In How to handle inventory management scenario whitepaper, I fail to understand the basic difference between 'Inventory Management with non-cumulative Key Figures' and 'Inventory Management with Snapshots'. Can anyone please explain me the basic difference.
Thanks
PB

Hi Loic
Can u please see if all the steps listed below are OK.
While setting up the IM Scenario
I have jotted down the steps with valuable inputs from you and paper 'How to Hanlde IM scenarios'
Please find the steps below. Kindly review them and let me know in case I have got anything wrong or missed out on anything.
1. Transfer Business Content Datasources 2LIS_03_BX , 2LIS_03_BF, AND 2LIS_03_UM in RSA5.
2. Go to Transaction LBWE, Activate Datasources 2LIS_03_BF, AND 2LIS_03_UM.
3. Go to Transaction MCB_ select SAP BW usage 'Standard' Radio button.
4. Save it.
5. Go to Transaction MCNB, enter name of run Stock_init. Enter Termination date in future. Enter Datasource as 2LIS_03_BX.
6. Execute the initialisation.
7. Entries can be found in SETUP Table MC03BFSETUP & MC03BFSETUP.
8. Run SETUP for 2LIS_03_BF, AND 2LIS_03_UM using TCodes OLI1BW and OLIZBW respectively.
9. Run the extraction for 2LIS_03_BX in BW.
10. Compress the request with No Marker Update NOT SET i.e. unticked or unchecked.
11. Run the extraction for 2LIS_03_BF in BW.
12. Compress the request with No Marker Update SET i.e. ticked or checked.
13. Run the extraction for 2LIS_03_UM in BW.
14. Compress the request with No Marker Update SET i.e. ticked or checked.
Steps 1 and 2 shall be executed in Development and transported to production and step 3 onward should be carried out in Production itself with Posting Block.
Thanks in advance.
Regards
PB

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,

Inventory Management Issue

Hi Friends,
I'm working on inventory management.
I have activated my datasources in rsa5 and when i'm looking in LBWE i'm able to see only two data sources. (i.e., 2lis_03_bx) is not visible. When activating the data source i tried to create the append structure after that i thought that there is no use of creating the append structure i deleted it. But when we do for MCNB Tcode i'm unable to execute my data source and its showing any error like the append structure is not active.
Please Do help me.
Thanks & Regards,
Renu

Jyothi,
know the Inventory flow from Surender reddy documents from wiki - http://wiki.sdn.sap.com/wiki/display/profile/Surendra+Reddy
Usualy, BX - deals with Stock initialisation and there is no need of delta load for this datasource , so it will not available in LBWE.
Where as BF,UM will avaiblw in LBWE, as they should load with deltas regularly.
understanding logistics is bit difficult, but study in sdn. You wil get the flow and understand the functional concept.
Regards,
rvc

Inventory Management Loads

Hi
I have a requirement in Inventory Management where the client wants to empty the complete Infocube(0IC_C03).
Now he is just interested in loading previous 3 months data as historic data.
Now my problem is how do i go about it once i have cleared the Infocube.
all standard datasources are in use.
2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
Summary
Restart Reporting with previous 3 months data available in BIW and delta loads every day later on.
Also guide me over the downtime required.
Akshay Chonkar

Hi All
I wish to Clear the Infocube completely so as to start afresh.
Please correct me if i am wrong
Fill Setup table for 2LIS_03_BX
I will run the Opening Stock Infopackage for 2LIS_03_BX
Compression without marker update
I will be filling setup tables of 2LIS_03_BF and 2LIS_03_UM giving posting date range of previous 3 months and will run Init with data transfer infopackage of the two data sources.
Followed by Compression with marker update for the two requests
Regards
Akshay Chonkar

Inventory Management DataSource

Similar Messages

Maybe you are looking for