Urgent-Inventory Management in case of a glass or ply industry

A typical scenario.
I am facing a problem in inventory management for a client of mine who is into glass cutting and supply. The glass sheets are purchased in sheets from the vendor and is cut into various shapes and dimensions according to the order recieved by him. now in most of the cases the entire sheet is not used in a particular order. the remaining part which is not used goes to the inventory. Now for a next order all the remaining part may be used if it matches the lengthXBreadth specifications. So the inventory items should show the length X Width specification. The dimensions are not fixed and there may be "n" number of variables.
Example- A default sheets of sizes 10"X10" is purchased form vendor. Seperate shapes of 6"X4" and 4"X 4" is cut out from it. Then the remaining part will have a dimension of 6"X10", which goes to the inventory. Now whenever he will see te inventory report he should be able to see that 1qunty of 6"X10" is ther in the inventory. So that when if he recieves an order of 6"X8" or 6"X10" he can use that and save cutting a new sheet (10"X10"). This will minimise the wastages.
I had planed to do it by the area but then that does not solve the perpose as the inventory total will show the sum area of all the dimensions in the inventory in "sq@units". Makong item masters for different dimensions will involve a huge inventory management and the users may land up in making numerous masters evry day and also risk of the duplication of the same masters will prevail.
Please anyone who has done any implementation for such clients or of similar type or any one having a suitable solution to this issue........please help!!!

Debraj,
In that case the option you could try is to enable batches and store the size as a batch number
For example: The inventory could have 10 pieces of item A
Qty......Batch
..2.......6x10
..3.......6x8
..5.......6x6
Now when ever you want to add a cut piece of item A which is of size 6x10, you simply enter Batch 6x10 and this will not only increase stock by1 but also you now the visiblity of what the stock is made up of by running the Batch report.
If you want to do it in a much better way then you need to probably go with an AddOn
Suda

Similar Messages

Inventory managment Snap Shot scenario.Urgent

Hi,
I am doing snapshot scenario for inventory management in BI 7.0. , when i am doing that i have small doubt , as said in stepo by step process of that document i am doing, for the non-cumulative key figures we need to use cumulative key figures as inflow and out flow.
my question is when we create transformation i could not see my non-cumulative key figures where in i am supposed to write routines at traansformations level, i could see only cumulative key figures.
Can any one give me idea why it is happned.
i am using ODS and as well as cube.
Regards
Ram

You need not to write any routine or do any assignment for non-cummulative kyf.
In the definition of non-cummm kyf u have already defined inflow and out flow which will take care. U may not also see the data for non-cumm kyf in display data of ods but in report u will see the data.
Regards,
Mahendra

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

The interface connecting Lean-WM and inventory management

Dear experts!
Thank you for your attention!
I am confused at the interface connecting Lean-WM and inventory management.
there are so many concepts in this field, such storage location, picking areas, storage types and so on.
Could you please give me an real case or a illustration to discribe that how the interface connecting Lean-WM and inventory management works?
Best regard!
Tangdark

you do nto need to enter serial numbers while clearing inventory at WM level but at IM in case you have the serial profile activated then you need to enter serial numbers when clearing inventory from the IM level.
according to what you have said it should automatically pop up a screen where you need o enter the serial numbers but this is weird it is not doing.
Please check the following:-
Does the serial number profile config in OIS2 have "MMSL" as a property and if so is entry of serial numbers mandatory during goods receipt and issue ad if there is a stock check active

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

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"

Error "Material not subject to inventory management in Plant " on the STO

I want to create a Stock tansport order ( plant to plant transfer) with stock & non-stock item and non stock item is giving an error "Material not subject to inventory management in Plant". Please tell me how to clear this error. Plant / SLOC view is already maintained and no qty/value update selected on the material type because of non stock item. Please tell me how to overcome this error on the STO

Hello,
As you said you want to move nonstock item through STO.
It seems that in your case say for example your plant 1000 has material ABC which is maintained as stock item.
Now you have another plant 2000, whaich has same material ABC which is maintained as non-stock item (generally used in third party sales or cross docking).
If your material ABC is nonstock in plant 2000 where no stocks are mainatined, then how can you move the stock to plant 1000 where it is stock item.
Could you please confirmthat can you see the stock in MMBE for plant where that material is maintained as non stock item.
If so, then you have chnage the plant specific material status for that plant from non stock item to stock item.
This is maintained in material master in purchasing view.
The other way out is you have to third party sales with ship to party as the plant where that item is maintained as stock item.
In this case flow is
Sales order>>Purchase requistion>>Purchase order>>(Vendor supplies material directly to customer (which is you plant where that item is stock item))
Br,
Tushar
Instead you can acheive

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

Problems reloading Inventory Management

We have been struggling to reload our Material Movements cube (0IC_C03). We have been following the SAP documentation titled 'How to handle inventory management scenarios in BW'.
Our initial loads (Stock Opening Balance, Movements Init, Revaluations Init) have all been successful and validation looks good. The problem is that when the first delta UPDATE runs we end up having many negative inventory quantities appearing. We are not sure what we could be doing wrong.
Compression settings are as follows
1) Run stock opening balance (2LIS_03_BX)
2) Run statistical setup for 4/3 only for Revaluations and Movements (2LIS_03_BF, 2LIS_03_UM)
(Compress with Marker option NOT CHECKED)
3) Load Stock infoPackage 2LIS_03_BX with 'Opening stock balance checked ' (ie: not full update)
(Compress with marker option NOT CHECKED)
4) Run delta init for Movements
(Compress delta init with marker option CHECKED)
5) Run delta init for Revaluations
(Compress delta init with marker option CHECKED)
6) Setup job control in logistics cockpit
7) Run delta update for Movements
Compress delta with marker option NOT CHECKED
8) Run delta update for Revaluations
Compress delta with marker option NOT CHECKED
The issue seems to occur with steps 7 and 8. The initial time we do these steps we get zero records and everything looks good. Then the next day the same steps occur in our nightly process chain and then the data is bad with negative values.
Any ideas what we could be doing wrong?
Thanks!

Hello Patrick,
Whic values you are getting as negative, the non-cumulative key figures or the inflow and outflow key figures? If the inflow and outflow KFs are coming correctly, then problem is in BW side e.g. compression sequence. But in case inflow and outflow KFs itself are coming worngly with negative sign from R/3, then problem lies in R/3 side. In that case you can check the corrsponding data in tables MSEG and BSEG. Let me know in which part the problem lies and from there we can take it forward.
Regards,
Praveen

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

Hi Experts,
We are using Inventory management on MSCA mobile apllication using by Motorola MC75A6 ,Now we are feel Very slow in the device,Any other device better than this device,Kindly advice me...
Thanks and regards,
Kumar

Hi,
Your requirement is not clear or could be wrong. You didn't mention the mobile page where you want this to be achieved. Also usually items in inventory will reside in multiple locators or subinventories. In that case which sub and loc you want to get defaulted ? what is the criteria that decides it ?

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

Urgent-Inventory Management in case of a glass or ply industry

Similar Messages

Maybe you are looking for