Indicator: Message to inventory management

Hello!
During material creation in tab warehouse management 1, there is a field Mesage to IM : Indicator: Message to inventory management.
can you please explain me the functionality of it?
Thank you.

Certain transactions result in a data transfer from the R/3 System to the R/2 System. "Message to IM" is a communication indicator, they affect how and when the transmission of communication documents to the R/2 System take place. The following information applies to the transfer order created for the 40 pallets of material in the example:
If you use the communication indicator "1" for the Source item field (immediate confirmation and transfer of a communication document to R/2), no quant is built in the goods receipt (GR) area. Instead, one communication document is created for each pallet resulting in 40 communication documents.
If you use the communication indicator "2" for the Source item field, and you have identified the material as a non-critical material, the process is cumulative and negative quants are created in the GR area. In this case, data for all 40 pallets is contained in one communication document for the negative quant in the GR area.
For details and further reference, check http://help.sap.com/saphelp_45b/helpdata/en/c6/f84ba64afa11d182b90000e829fbfe/frameset.htm

Similar Messages

HU without inventory management and message L3778 in storage type 999

Hi experts,
Need suggestion on the process to add inventory of an HU with status 'HU without inventory Management'. This issue has occurred out of the below scenario:
1. our warehouse is HU & WM managed.
2. We have a transfer order for a delivery document requesting to pick up 100 cases of MAT1 which is assigned to HU1.
3. While confirming the transfer order user has confirmed difference for the full quantity of 100 because the SU/HU was not found in the bin.
4. The system has set the status of HU as 'HU without inventory Management'. The HU is empty.
5. system has moved the stock from the bin to difference storage type 999.
Now user has found the stock for this HU and he wants to post the stock back into the bin. system does not allow to move the stock back to bin using LT01 as we get error message 'L3 778'.
What will be the best practice to get the stock back into the bin and post the stock into the same old HU.
Is there a process wherein we can post this stock to another bin and repack into the old HU?
Thanks,
Harish

Thanks Manish on the hint. I was able to transfer stock to partner location and then bring back to original Storage type/Bin. Below steps was used to fixed the issue:
1. Initiate a transfer of stock from WM/HU Sloc where the IM stock resides into Sloc 9099. An outbound delivery is created during this process.
2. Create a transfer order with reference to delivery and pick the stock from 999 storage type.
3. Create a Pick HU using LH01 and assign the HU on the pallet to the transfer order.
4. Confirm the transfer order using LT12.
5. Perform PGI for the delivery.
6. Use HUMO to display the HU and then you can transfer the stock back to WM/HU location using the storage location transfer option available on the HUMO screen(EDIT à change HU posting à Storage location)
7. Perform Bin to bin transfer to move the SU from 921 storage type to putaway the HU/SU back to the destined Storage type/Bin.
Best Regards,
Harish

Error message rgd. Material Movements / Inventory Management

Hello,
We have Problem to load Material Movements data in Inventory Management InfoCube.
On BW-Side we had deleted Inventory Management InfoCube content completely before we started with opening stock, Material Movements.
We have filled set up tables for opening stocks, Material Movements and Revaluation successfully on R/3 Side. We have also filled archive data for Material Movements and Revaluation in set up tables.
We have loaded the opening stock balance into InfoCube. The request containing the opening
stock has been compressed.
We are trying to load the material movements (Initialize delta) into Cube. We get the error message:
u201CThe material XXXXXXXX does not exist or is not activatedu201D.
We have analyzed these materials (from error message) and find out that these materials are already archived on R/3 side but these materials are in Master Data table on BW-Side.
How we can deal with this problem? The BW-System is SAP NetWeaver 2004s (Support
Package SAPKW70016). The SAP R/3-System is SAP ECC 6.0.
We had same proceeding in March 2008 with BW 3.0B and R/3 4.7 and had no problem at all.
Many thanks

Hi,
Hope u have loaded the master data in BW side and also activated the Master data i.e i assume that u have done Attribut change run.
Rgds
SVU123

Print Smartforms in Inventory Management

Dear Sappers,
My client requires a lot of samrtform in INventory Management including SC DC, Stock Transfer DC, GR etc.GR Smartform is coming as per my configuration.But other smartforms are not coming as per y configuration.
When I see the material documnet in MB02.I saw all the o/p types are coming for the respective transaction.Foe ex: If i'm going for Stock Transfer Smartform Print, I can see all the O/P types in the material document.So when I'm going to Print in MB90, the smartform is not triggering and system is giving one message.
Output could not be displayed (it may not be complete) Message no. VN069
Same thing applicable to S/C DC and other smartforms.
Is there any link between movement types and O/P types with access sequence??
Is there any other settings are there to take print????
Our client requires a smartform for Sub Contract DC.It's developed.In Inventory management I've assigned the programme name and smartform name and made the necessary settings.Even though I made the print is not coming.
Can anybody tell me where I've done the mistake?
I've created my o/p copying the standard WLB3 and created my own.
IN general data I put access sequence as 0004 & in default value I put dispatch time as 3 and transmission medium as 1.I made Print parameter as 7 plant/ storage location.
In processing routine I put the necessary programme name and smartform name.
In NACE, I've taken ME - Inventory Management.Out O/P type and Trans/Event Type as WA, print Version 3, Print Item 3 and debit/Credit Indicator as H (Credit).
I assigned the Printer name there.
Apart from that I made the goods movement respect to plant and storage location as well as movement type.
Still my print is not coming.
Any suggestions.
Thanks & Regards
PKB
Edited by: Pranaya Barik on Oct 13, 2009 1:48 PM

Hi
I'm waiting for the reply still I'm not getting any suggestions from.
We've developed smart form for Sub Contract DC.I've made the necesssary settings for this. Still Smartform print is not coming.If anyone works on Smartform for S/C DC, tell me how to do the necessary settings to get print preview of S/C DC.
Waiting for the respond??
Thanks & Regards
PKB

Special Stock Indicator (SOBZK) and Inventory Extractors

I have activated business Business Content for the Inventory Management (0IC_C03) cube with Grouping as In DataFlow Before and Afterwards. However, the special stock indicator field which is part of the extractor and not hidden does not come across into the Transfer Structure, is there a reason and how can I resolve? Thanks
I have gone to the DataSource/Trans Struc tab, have seen in the Data Source and am able to transfer across
Message was edited by: Niten Shah

Hi
In the Standard Sytem these are the special Stock Indicators
E     Orders on hand
K     Consignment (vendor)
M     Ret.trans.pkg vendor
O     Parts prov. vendor
P     Pipeline material
Q     Project stock
V     Ret. pkg w. customer
W     Consignment (cust.)
Y     Shipping unit (whse)
I have not found B - Special Stock indicator.
You can use Accotunt assignment Category D - with Special Stock Indicator E to get the Material into Stock Under Sales Order Stock..
Item Category S - Third Party is used only in case of Third Party Process & athe Account assignment Category Picked is X - All aux.acct.assgts.
Thanks & Regards
Kishore
Thanks & Regards
Kishore

Inventory Management - Snapshot Scenario

Hi,
We are implementing the Snapshot scenario for inventory management based on the "How to Handle Inventory Management Scenarios in BW" and am facing the problem on the point 51 in the document.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
"51. Create a start routine to multiplicate the old row with minus 1, set the record mode to R Reverse-Image and create a new row with the month 12.9999, if the ...."
the logic seems to be incomplete. Has anyone implemented this scenario. Please let me know what is the missing piece.
Thanks
RK

I am only in design phase. I have post this message because the How to guide is old and I would know if someone have find a new solution ( with less step to reduce development phase).
As not recent solution is provided, I use the how to guide and adapt because I have more indicator to implement in my solution.

Analysis Process Designer and Inventory Management

In the How to guide for Inventory Management it mentions that you can you can intialise stock in the Snap shot Cube using the Analysis Process Designer (APD). Has anyone done this and if so can you explain how or outline some steps? Thanks

Hallo,
the APD does`nt be a useful tool for modeling a performant
data flow. A lot of SAP BW user think so.
The performance problems are given by the ddic intern table, using to uploading the extracted data into the apd used wa_table and structures.
To have the best performance on your scenario, please use the following scenario as possible.
Step 1.
upload the extracted data from the psa into a data layer
there you can reduce and harmonize the data by using a transactional ods
Step 2.
build a infoset that joins the data
Step 3.
build one query to reducing data and make two copies of ist
Step 4.
build a useful data mining model
Step 5.
upload the results of the data mining model into a transactional ods
Step 6.
link the uploaded data into a infoset ore write back into a standard ods
Step 7.
query the data
If you use this scenario you have a lot of benefits. Better performance, better quality of persistent data and actual and traininged data.
The recommend next step (if you want a alerting) is to build a reporting agent report - if you have usefull processes in the query.
There are a workshop for Data mining and APD, named BW380.
I hope I helped you.
Otherwise give me a message.
[email protected]

Handling unit without inventory management

Hi Experts,
In our scenario, we have Goods reciept from production into Storage location 1000 which is IM managed, Later the stocks are transfer posted into storgae location 1100 which is HU/WM managed. Now in 1100 i have found HU's which have been created with status 'Handling unit without Inventory management'.
Can someone explain to me what does it mean when a HU gets created with this status? under which scenario does the system create the HU with this status?
Also when this HU is scanned for putaway the system gives error message Handling unit does not exist in SAP. Can someone let me know the resolution or the root cause for this issue.
Thanks in advance.
Harish

Hi,
The above mentioned status is when a Handling Unit created, but the Inventory management is not yet posted for the content materials of the HU
I can give an example: Created a Inbound Delivery for material XXX. Then a HU is created in Packing screen, but the PGR is not yet done. At this stage, HU has the same status
Hope this helps
If the GR/GI is reported for HU contents, then the HU status will change. With you case, a Handling Unit is just created, but no further tansaction like, packing, GI or GR is done.
Regards,

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

Material is subject to inventory management in care unit storage facility

Dear All,
when using Transaction NMM5 for material requisition the system displays the message
"Material is subject to inventory management in care unit storage facility"
what steps are required to overcome this error.
I have already assigned storage location and plant to the nursing OU in NB20 for which the
material is required.
Please assist.
Regards
Ramit

Go to MM02, select the Purchasing view of that material and check whether any value is maintained for the field Plant specific matrl status
thanks
G. Lakshmipathi

Error: material not subjected to inventory management in a plant

While creating a STO . I am getting the following error
Error: material not subjected to inventory management in a plant
What should be done??????????/

Dear anamicabhardwaj ,
You need to check transaction OMS2 for the material type you use for the material.
Basically for STO which need to inventorized, the quantity updating need to check
for the material type, then only it can be inventorized. There is no other option but check
the quantity update indicator.
Regards,
ian, Wong Loke Foong

Regarding inventory management

Hi,
I have documnet How To Handle Inventory Management Scenarios in BW
Version 1.3 January 2005.
But it gives the details about 3.5 version. If i want to implemnet in 7.0 what all i need?
also i w2as trying to find the 'No marker update' option and all in 7.0 but coudnt find the same. Is thr so much difference in implementing INVENTORY in 7.0
*Please help.

Hi Jino,
Briefly,
a) Single Step transfer: -
this comes in STO, while transfer material between plants.
if you tick the indicator as one step in config,
Generally, when you do the PGI for material from supply plant to receiving plant, goods issue document will generate in Issuing plant.
Similarly goods receipt (GR)document generate in receiving plant.
in One step procedure, GR will create automatically in background after you do PGI.
where as in Two Step Plant Transfer. AFter PGI, you have to create GR-MIGO also.
Hope it clears. Try and let me know

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

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.

Indicator: Message to inventory management

Similar Messages

Maybe you are looking for