urgent Inventory

Hi Gurus,
I have a question, Is there a new functionality for a datasource to extract Opening balance in Inventory as part of new BI 2004s. Would anyone please reply to this question its pretty urgent and if you can send me any link or doc that will be great, thanks in advance.
****Gurantee of assign points if its helpful*******
Regards
Baba.

Check this "How to" PDF file ...it has all about inventory management
I hoop this help you
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Regards

Similar Messages

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

Urgent:Inventory Modelling with Moving price

I have to create an Inventory report storage locationwise material stock along with standard price and moving average price.
We have a z cube zic_c03.
Moving price and standard price is stored an Z ODS on fiscal/period wise.
I need to have the following fields in the report
charactersitics
Plant
Material
Storage location
Price control(from Z ods)
keyfigures:
Valuated stock qty(from zic_c03)
Valuated stock value(from zic_c03)
Standard price(from ods)-Using routine
Moving Price(from ods)-Using Routine
I have created another cube(included all the fields from zic_c03 and added the three fields from ODS).
For the fields included from ODS, I have written an lookup routine in the new cube (zic_c04) update rule.
For ex.Stand price routine as follows:
PROGRAM UPDATE_ROUTINE.
TABLES: ...
DATA : tstd like /BIC/AZMM_O0200-pRICE_std.
DATA : tavg like /BIC/AZMM_O0200-pRICE_avg.
DATA : tpc like /BIC/AZMM_O0200-PRICE_CTRL.
fill the internal table "MONITOR", to make monitor entries
select single PRICE_STD
into tstd
from /BIC/AZMOV_O0100
where material = COMM_STRUCTURE-material
and plant = COMM_STRUCTURE-plant
and FISCPER = COMM_STRUCTURE-FISCPER.
RESULT = tstd.
RETURNCODE = 0.
ABORT = 0.
I have the following issues:.
1)After adding the price control Indicator(assigned to all keyfigures in update rule) Valuated stock qty and value showing in negative.
2)Intially I didn't compress the new cube(zic_c04).After seeing negative values I compressed(no marker update enabled) it and checked.But still showing negative.
2)If I assign price control Indicator to only standard price and moving price Iam not getting any results for valuated qty and stock(price control Indicator = 'not assigned')
Pls help me to do the right modelling for the above requirement.
Thanks in advance.
Regards
Soujanya

Hi,
I have different Modeling scenario to get MAP in BIW.
Take a Look on this thread:
Re: 2lis_03_um and MBEW- STPRS
Re: How to get Moving Average Prince and Standard Price in BW (inventory cube).
With rgds,
Anil Kumar Sharma .P

URGENT inventory reports

Hi friends,
I would like to see a report by Product line/Profit center,
I checked these reports, MCBE,MMBE,MCBC,ME80AN. Where I dont see any field that can show Profit center,
And also I would like to see a inventory report by material, qty, batch, and serial number.
Please let me know if we have any report like that ,

this will help you
*& Report Z_OPEN_CLOSE                                                *
REPORT Z_OPEN_CLOSE MESSAGE-ID YW2 LINE-SIZE 231 LINE-COUNT 45
NO STANDARD PAGE HEADING.
Type Declaration *
TYPE-POOLS SLIS.
Tables *
TABLES: MKPF, " Material Document: Header Data
        MSEG, " Material Document: Item Data
        MARA,
        MARD,
        S031,
        EKKO,
        EKPO,
        LIKP,
        MAKT,
        J_1IWRKCUS,
        T001W,
        WB2_V_MKPF_MSEG2,
        MMIM_REP_PRINT,
        YW2_STKMOVEMENTS,
        YPLNT,
        MARDH.
Internal Tables *
DATA: I_WERKS LIKE J_1IWRKCUS OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF I_YPLNT OCCURS 0,
         PPLNT LIKE YPLNT-PPLNT,
         WPLNT LIKE YPLNT-WPLNT,
      END OF I_YPLNT.
DATA: BEGIN OF I_MKPF OCCURS 0,
        MBLNR LIKE MKPF-MBLNR,
        MJAHR LIKE MKPF-MJAHR,
        BUDAT LIKE MKPF-BUDAT,
        VGART LIKE MKPF-VGART,
        BWART LIKE MSEG-BWART,
        MATNR LIKE MSEG-MATNR,
        WERKS LIKE MSEG-WERKS,
        LGORT LIKE MSEG-LGORT,
        MENGE LIKE MSEG-MENGE,
        MEINS LIKE MSEG-MEINS,
        KUNNR LIKE MSEG-KUNNR,
        ZEILE LIKE MSEG-ZEILE,
        XAUTO LIKE MSEG-XAUTO,
        SHKZG LIKE MSEG-SHKZG,
        MATNR1 LIKE MSEG-MATNR,
      END OF I_MKPF.
DATA: BEGIN OF I_MARDH OCCURS 0,
       WERKS LIKE MARDH-WERKS,
       MEINS LIKE MARA-MEINS,
       MATNR LIKE MARDH-MATNR,
       LGORT LIKE MARDH-LGORT,
       LABST LIKE MARDH-LABST,
       LFGJA LIKE MARDH-LFGJA, "Added -MB
       LFMON LIKE MARDH-LFMON, "Added -MB
       PERIO(6),
       INSME LIKE MARDH-LABST,
       EINME LIKE MARDH-LABST,
       SPEME LIKE MARDH-LABST,
       RETME LIKE MARDH-LABST,
       O_STK LIKE MARDH-LABST, " Opening Stock
       C_STK LIKE MARDH-LABST, " Closing Stock
      END OF I_MARDH.
DATA: BEGIN OF I_MARD OCCURS 0,
       WERKS LIKE MARD-WERKS,
       MATNR LIKE MARD-MATNR,
       LGORT LIKE MARD-LGORT,
       LABST LIKE MARD-LABST,
       INSME LIKE MARD-LABST,
       MEINS LIKE MARA-MEINS,
       EINME LIKE MARD-LABST,
       SPEME LIKE MARD-LABST,
       RETME LIKE MARD-LABST,
      END OF I_MARD.
DATA: I_MARD1 LIKE I_MARD OCCURS 0 WITH HEADER LINE.
DATA: I_MARDH1 LIKE I_MARDH OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF I_MKPF1 OCCURS 0,
        MBLNR LIKE MKPF-MBLNR,
        WERKS LIKE MSEG-WERKS,
        MATNR LIKE MSEG-MATNR,
        BUDAT LIKE MKPF-BUDAT,
        BWART LIKE MSEG-BWART,
        MJAHR LIKE MKPF-MJAHR,
        VGART LIKE MKPF-VGART,
        LGORT LIKE MSEG-LGORT,
        MENGE LIKE MSEG-MENGE,
        MEINS LIKE MSEG-MEINS,
        XAUTO LIKE MSEG-XAUTO,
        SHKZG LIKE MSEG-SHKZG,
      END OF I_MKPF1.
DATA: BEGIN OF I_MKPF2 OCCURS 0,
       WERKS LIKE MSEG-WERKS,
       MATNR LIKE MSEG-MATNR,
       BUDAT LIKE MKPF-BUDAT,
       BWART LIKE MSEG-BWART,
       MJAHR LIKE MKPF-MJAHR,
       VGART LIKE MKPF-VGART,
       LGORT LIKE MSEG-LGORT,
       MENGE LIKE MSEG-MENGE,
       MEINS LIKE MSEG-MEINS,
       XAUTO LIKE MSEG-XAUTO,
     END OF I_MKPF2.
DATA: BEGIN OF I_FINAL5 OCCURS 0,
       WERKS LIKE MSEG-WERKS, " Plant
       MATNR LIKE MSEG-MATNR, " Material
       LGORT LIKE MSEG-LGORT, " Storage Location
       BUDAT LIKE MKPF-BUDAT, " Posting Date
       MTART LIKE MARA-MTART, " Material Type
       SPMON LIKE S031-SPMON, " Month
       MAKTX LIKE MAKT-MAKTX, " Description
meins(3), " UOM
        MEINS LIKE MSEG-MEINS,
        O_STK LIKE MARDH-LABST, " opening stock
        TRECEP LIKE MARDH-LABST, " total receipts
        PRODU LIKE MARDH-LABST, " Net Receipts - Production
        RECEP LIKE MARDH-LABST, " Net Receipts - Receipts
        SAL_RET LIKE MARDH-LABST, " Net Receipts - Sales Return
        TDISP LIKE MARDH-LABST, " total dispatches
        CUSTMR LIKE MARDH-LABST, " Net Dispatches - Customers
        OPLANT LIKE MARDH-LABST, " Net Dispatches - To Other Plant
        TLOSS LIKE MARDH-LABST, " Total Loss
        TRLOSS LIKE MARDH-LABST, " Transit Loss
        WHLOSS LIKE MARDH-LABST, " Warehouse Loss
        C_STK LIKE MARDH-LABST, " Closing Stock
        TRFSTK LIKE MARDH-LABST, "Transfer stock
        MENGE LIKE MSEG-MENGE,
        OTHADJ LIKE MARDH-LABST,
      END OF I_FINAL5.
DATA: BEGIN OF I_FINAL OCCURS 0,
        WERKS LIKE MSEG-WERKS, " Plant
        MATNR LIKE MSEG-MATNR, " Material
        BUDAT LIKE MKPF-BUDAT, " Posting Date
        MTART LIKE MARA-MTART, " Material Type
        SPMON LIKE S031-SPMON, " Month
        MAKTX LIKE MAKT-MAKTX, " Description
meins(3), " UOM
        MEINS LIKE MSEG-MEINS,
        O_STK LIKE MARDH-LABST, " opening stock
        TRECEP LIKE MARDH-LABST, " total receipts
        PRODU LIKE MARDH-LABST, " Net Receipts - Production
        RECEP LIKE MARDH-LABST, " Net Receipts - Receipts
        SAL_RET LIKE MARDH-LABST, " Net Receipts - Sales Return
        TDISP LIKE MARDH-LABST, " total dispatches
        CUSTMR LIKE MARDH-LABST, " Net Dispatches - Customers
        OPLANT LIKE MARDH-LABST, " Net Dispatches - To Other Plant
        TRFSTK LIKE MARDH-LABST, "Material Transfer stock
        TRLOSS LIKE MARDH-LABST, " Transit Loss
        WHLOSS LIKE MARDH-LABST, " Warehouse Loss
        TLOSS LIKE MARDH-LABST, " Total Loss
        C_STK LIKE MARDH-LABST, " Closing Stock
        OTHADJ LIKE MARDH-LABST,
       END OF I_FINAL.
DATA: I_FINAL1 LIKE I_FINAL OCCURS 0 WITH HEADER LINE.
DATA: BEGIN OF I_FINAL_TEMP OCCURS 0,
        WERKS LIKE MSEG-WERKS, " Plant
        MATNR LIKE MSEG-MATNR, " Material
        MTART LIKE MARA-MTART, " Material Type
        MAKTX LIKE MAKT-MAKTX, " Description
        MEINS LIKE MSEG-MEINS,
        O_STK LIKE MARDH-LABST, " opening stock
        TRECEP LIKE MARDH-LABST, " total receipts
        PRODU LIKE MARDH-LABST, " Net Receipts - Production
        RECEP LIKE MARDH-LABST, " Net Receipts - Receipts
        SAL_RET LIKE MARDH-LABST, " Net Receipts - Sales Return
        TDISP LIKE MARDH-LABST, " total dispatches
        CUSTMR LIKE MARDH-LABST, " Net Dispatches - Customers
        OPLANT LIKE MARDH-LABST, " Net Dispatches - To Other Plant
        TRFSTK LIKE MARDH-LABST, "Material Transfer stock
        TRLOSS LIKE MARDH-LABST, " Transit Loss
        WHLOSS LIKE MARDH-LABST, " Warehouse Loss
        TLOSS LIKE MARDH-LABST, " Total Loss
        C_STK LIKE MARDH-LABST, " Closing Stock
        OTHADJ LIKE MARDH-LABST,
      END OF I_FINAL_TEMP.
For Materials
DATA: BEGIN OF I_MARA OCCURS 0,
       MATNR TYPE MARA-MATNR,
       MTART TYPE MARA-MTART,
       MEINS LIKE MARA-MEINS,
       LABST TYPE MARD-LABST,
       MAKTX LIKE MAKT-MAKTX,
      END OF I_MARA.
DATA: BEGIN OF I_STKMVMNTS OCCURS 0,
       BWART LIKE MSEG-BWART,
       SHKZG LIKE MSEG-SHKZG,
       VZBEW LIKE YW2_STKMOVEMENTS-VZBEW,
      END OF I_STKMVMNTS.
DATA: BEGIN OF I_FINALT OCCURS 0,
       WERKS LIKE MSEG-WERKS, " Plant
       MATNR LIKE MSEG-MATNR, " Material
       BUDAT LIKE MKPF-BUDAT, " Posting Date
       MTART LIKE MARA-MTART, " Material Type
       SPMON LIKE S031-SPMON, " Month
       MAKTX LIKE MAKT-MAKTX, " Description
meins(3), " UOM
       MEINS LIKE MSEG-MEINS,
       O_STK LIKE MARDH-LABST, " opening stock
       TRECEP LIKE MARDH-LABST, " total receipts
       PRODU LIKE MARDH-LABST, " Net Receipts - Production
       RECEP LIKE MARDH-LABST, " Net Receipts - Receipts
       SAL_RET LIKE MARDH-LABST, " Net Receipts - Sales Return
       TDISP LIKE MARDH-LABST, " total dispatches
       CUSTMR LIKE MARDH-LABST, " Net Dispatches - Customers
       OPLANT LIKE MARDH-LABST, " Net Dispatches - To Other Plant
       TRFSTK LIKE MARDH-LABST, "Material Transfer stock
       TRLOSS LIKE MARDH-LABST, " Transit Loss
       WHLOSS LIKE MARDH-LABST, " Warehouse Loss
       TLOSS LIKE MARDH-LABST, " Total Loss
       C_STK LIKE MARDH-LABST, " Closing Stock
       OTHADJ LIKE MARDH-LABST,
       MONTH(8) ,
      END OF I_FINALT.
DATA: IMKPFT LIKE I_MKPF OCCURS 0 WITH HEADER LINE.
DATA: IMKPFT1 LIKE I_MKPF1 OCCURS 0 WITH HEADER LINE.
DATA: IMARDT LIKE I_MARD OCCURS 0 WITH HEADER LINE.
DATA: IMARDHT LIKE I_MARDH OCCURS 0 WITH HEADER LINE.
DATA: T_FINAL LIKE I_MKPF OCCURS 0 WITH HEADER LINE.
DATA: IMKPFT2 LIKE I_MKPF OCCURS 0 WITH HEADER LINE.
FCAT is used for the field catalog
DATA: FCAT TYPE TABLE OF SLIS_FIELDCAT_ALV WITH NON-UNIQUE DEFAULT KEY
                  WITH HEADER LINE INITIAL SIZE 0,
for excluding the ICONs from the application toolbar
      FEXC TYPE TABLE OF SLIS_EXTAB WITH NON-UNIQUE DEFAULT KEY
                 WITH HEADER LINE INITIAL SIZE 0,
FS_LAYO is used for Grid Layout
      FS_LAYO TYPE SLIS_LAYOUT_ALV,
FEVENTS to handle the events TOP OF PAGE & USER_COMMAND
      FEVENTS TYPE TABLE OF SLIS_ALV_EVENT WITH NON-UNIQUE DEFAULT KEY
                 WITH HEADER LINE INITIAL SIZE 0,
FHEADER is used for List header
      FHEADER TYPE TABLE OF SLIS_LISTHEADER WITH NON-UNIQUE DEFAULT KEY
                 WITH HEADER LINE INITIAL SIZE 0,
sort is used for sorting
      FSORT TYPE TABLE OF SLIS_SORTINFO_ALV WITH NON-UNIQUE DEFAULT KEY
                 WITH HEADER LINE INITIAL SIZE 0,
      FCAT1 TYPE TABLE OF SLIS_FIELDCAT_ALV WITH NON-UNIQUE DEFAULT KEY
                WITH HEADER LINE INITIAL SIZE 0,
      FS_LAYO1 TYPE SLIS_LAYOUT_ALV,
      GT_LIST_TOP_OF_PAGE1 TYPE SLIS_T_LISTHEADER,
      FEVENTS1 TYPE TABLE OF SLIS_ALV_EVENT WITH NON-UNIQUE DEFAULT KEY
             WITH HEADER LINE INITIAL SIZE 0,
       FHEADER1 TYPE TABLE OF SLIS_LISTHEADER WITH NON-UNIQUE DEFAULT
              KEY WITH HEADER LINE INITIAL SIZE 0,
       G_STATU_071 TYPE SLIS_FORMNAME VALUE 'Z_PFSTATUS',
       ALV_VARIANT1 LIKE DISVARIANT.
Variable Declaration *
TYPES: TRFF_TYPE_DEC_6_5(6) TYPE P DECIMALS 5.
DATA: FYEAR(4),
      MON(2),
      FYEAR1(4),
      MON1(2),
      OBAL LIKE MARD-LABST,
      CBAL LIKE MARD-LABST,
      INDEX TYPE I,
      COUNT,
      COUNT1 TYPE I,
      O_STK TYPE P DECIMALS 3,
      C_STK TYPE P DECIMALS 3,
      V_MJAHR LIKE MKPF-MJAHR,
      MONTHS TYPE TRFF_TYPE_DEC_6_5,
      MONTH TYPE I.
Global variables for handling ALV functionality
DATA: ALV_KEYINFO TYPE SLIS_KEYINFO_ALV,
      ALV_VARIANT LIKE DISVARIANT,
      ALV_LAYOUT TYPE SLIS_LAYOUT_ALV,
      ALV_REPID LIKE SY-REPID,
      ALV_PRINT TYPE SLIS_PRINT_ALV,
      ALV_DETAIL_FUNC(30),
      ALV_DEFAULT_VARIANT LIKE DISVARIANT-VARIANT,
      ALV_COLOURIZE_FIELDS LIKE MMIM_REP_PRINT-COLOR.
RANGES: R_BUDAT FOR MKPF-BUDAT.
*Added by Prabhu for year on 26.4.05.
DATA: IDATE LIKE R_BUDAT OCCURS 0 WITH HEADER LINE.
Selection Screen Elements *
SELECTION-SCREEN BEGIN OF BLOCK BLK WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS: S_WERKS FOR MARD-WERKS OBLIGATORY NO INTERVALS.
PARAMETER: P_SPMON LIKE S031-SPMON NO-DISPLAY .
SELECT-OPTIONS: S_MATNR FOR MARA-MATNR OBLIGATORY,
                  S_LGORT FOR MSEG-LGORT NO-EXTENSION NO INTERVALS,
                  S_MBLNR FOR MKPF-MBLNR,
                  S_BUDAT FOR MKPF-BUDAT OBLIGATORY .
SELECTION-SCREEN END OF BLOCK BLK.
SELECTION-SCREEN BEGIN OF BLOCK BLK3 WITH FRAME TITLE TEXT-004.
      PARAMETER : MTART LIKE MARA-MTART DEFAULT 'FERT' NO-DISPLAY.
SELECTION-SCREEN END OF BLOCK BLK3.
SELECTION-SCREEN BEGIN OF BLOCK BLK2 WITH FRAME TITLE TEXT-003.
SELECTION-SCREEN END OF BLOCK BLK2.
ADDED BY PRABHU FOR DAY-WISE REPORT.
SELECTION-SCREEN BEGIN OF BLOCK B3 WITH FRAME TITLE TEXT-007.
PARAMETERS: D1 RADIOBUTTON GROUP P1 DEFAULT 'X',
              M1 RADIOBUTTON GROUP P1,
              Y1 RADIOBUTTON GROUP P1.
SELECTION-SCREEN END OF BLOCK B3.
SELECTION-SCREEN BEGIN OF BLOCK B2 WITH FRAME TITLE TEXT-006.
PARAMETERS: ALV_DEF LIKE DISVARIANT-VARIANT.
SELECTION-SCREEN END OF BLOCK B2.
DATA: S_BUDAT1 LIKE S_BUDAT OCCURS 0 WITH HEADER LINE."prabhu
Initialization *
INITIALIZATION.
PERFORM ALV_INIT.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR ALV_DEF.
PERFORM ALV_F4.
At Selection Screen
*AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_spmon.
PERFORM monat_f4.
At Selection Screen *
AT SELECTION-SCREEN.
checking for the layout
PERFORM ALV_CHECK.
authorisation check for the Plant
PERFORM auth_check.
Validation for the Plant
PERFORM VALIDITY_CHECK.
IF MTART NE 'FERT'.
    MESSAGE E041 WITH 'Material Type must be FERT Only...'.
ENDIF.
IF D1 = 'X'." On 26.4.05.
    P_SPMON0(4) = S_BUDAT-LOW0(4).
    P_SPMON4(2) = S_BUDAT-LOW4(2).
ELSE.
    P_SPMON0(4) = S_BUDAT-LOW0(4).
    P_SPMON4(2) = S_BUDAT-LOW4(2).
ENDIF.
LOOP AT S_BUDAT.
    IF S_BUDAT-HIGH IS INITIAL.
      S_BUDAT-HIGH = S_BUDAT-LOW.
      MODIFY S_BUDAT.
    ENDIF.
ENDLOOP.
IDATE-LOW = S_BUDAT-LOW.
IDATE-HIGH = S_BUDAT-HIGH.
CALL FUNCTION 'FIMA_DAYS_AND_MONTHS_AND_YEARS'
    EXPORTING
       I_DATE_FROM = IDATE-LOW
       I_DATE_TO = IDATE-HIGH
   IMPORTING
E_DAYS =
      E_MONTHS = MONTH
E_YEARS =
DATA: I(3) TYPE C.
I = S_BUDAT-LOW+4(2).
CLEAR: R_BUDAT.
REFRESH: R_BUDAT.
*added by Prabhu for Only for Oneday.on 18.5.5
IF MONTH EQ '0'.
    MONTH = MONTH + 1.
ENDIF.
*added by Prabhu for Only for Oneday.on 18.5.5
DO MONTH TIMES.
    R_BUDAT-LOW = S_BUDAT-LOW.
    APPEND R_BUDAT.
ENDDO.
I = 0.
LOOP AT R_BUDAT.
    R_BUDAT-LOW4(2) = S_BUDAT-LOW4(2) + I.
    I = I + 1.
    R_BUDAT-LOW+6(2) = '01'.
    MODIFY R_BUDAT.
ENDLOOP.
LOOP AT R_BUDAT.
    CALL FUNCTION 'RP_LAST_DAY_OF_MONTHS'
       EXPORTING
         DAY_IN = R_BUDAT-LOW
       IMPORTING
         LAST_DAY_OF_MONTH = R_BUDAT-HIGH
      EXCEPTIONS
        DAY_IN_NO_DATE = 1
        OTHERS = 2
    MODIFY R_BUDAT.
ENDLOOP.
LOOP AT R_BUDAT.
    IF R_BUDAT-LOW4(2) = S_BUDAT-LOW4(2).
      R_BUDAT-LOW = S_BUDAT-LOW.
      MODIFY R_BUDAT.
    ENDIF.
    IF R_BUDAT-HIGH4(2) = S_BUDAT-HIGH4(2).
      R_BUDAT-HIGH = S_BUDAT-HIGH.
      MODIFY R_BUDAT.
    ENDIF.
For Summary on 26.4.05.
    IF Y1 = 'X'.
      CLEAR R_BUDAT.
      REFRESH R_BUDAT.
      R_BUDAT-LOW = S_BUDAT-LOW.
      R_BUDAT-HIGH = S_BUDAT-HIGH.
      APPEND R_BUDAT.
      CLEAR R_BUDAT.
    ENDIF.
ENDLOOP.
At Selection Screen *
AT SELECTION-SCREEN OUTPUT.
Start of Selection *
START-OF-SELECTION.
V_MJAHR = P_SPMON+0(4).
Get plant distinction warehouse/production
PERFORM GET_PLANT_DISTINCTION.
Collect the data from various tables
PERFORM GETDATA_FG_STOCK.
here the number of rows in the output table is found
PERFORM OUTPUT_TABLE_CHECK.
here the top of the page code is written, that is to be displayed
in the output
PERFORM Z_TOP_OF_PAGE.
here ALV layout properties are set
PERFORM Z_LAYOUT_SETTINGS.
ALV EVENTS for TOP OF PAGE and for USER COMMAND
PERFORM Z_ALV_EVENTS.
The field catalog is defined for the Primary List is defined in
the subroutine CREATE_FIELD_CATALOG include program ZPRRDOCR_FCAT
PERFORM Z_CREATE_FIELD_CATALOG.
This is for displaying the output
PERFORM Z_REUSE_ALV_GRID_DISPLAY.
*& Form getdata_fg_stock
Getting data from standard tables
FORM GETDATA_FG_STOCK.
For getting the Start date & end date of the month
PERFORM get_month_dates.
Getting the Opening Stock from MARDH table
IF MON EQ '01'.
    MON1 = MON.
    FYEAR1 = FYEAR.
    MON = '12'.
    FYEAR = FYEAR - 1.
ELSE.
    MON1 = MON.
    FYEAR1 = FYEAR.
    MON = MON - 1.
    FYEAR = FYEAR.
ENDIF.
PERFORM GET_RECORDS_FROM_DB.
*added for Month Summary on 26.4.05.
LOOP AT R_BUDAT.
    S_BUDAT-LOW = R_BUDAT-LOW.
    S_BUDAT-HIGH = R_BUDAT-HIGH.
*for Month
    P_SPMON0(4) = S_BUDAT-LOW0(4).
    P_SPMON4(2) = S_BUDAT-LOW4(2).
*for summary.
    IF Y1 = 'X'.
      LOOP AT S_BUDAT.
        S_BUDAT1-SIGN = 'I'.
        S_BUDAT1-OPTION = 'NB'.
        S_BUDAT1-LOW = S_BUDAT-LOW.
        S_BUDAT1-HIGH = S_BUDAT-HIGH.
        APPEND S_BUDAT1.
        CLEAR S_BUDAT1.
      ENDLOOP.
    ENDIF.
    IMKPFT[] = I_MKPF[].
    IMKPFT2[] = I_MKPF[].
    IMARDT[] = I_MARD[].
    IMARDHT[] = I_MARDH[].
    PERFORM MONTH_WISE.
    PERFORM PROCESS_MOVEMENTS.
    PERFORM CALCULATE_OPENING_STOCK.
    PERFORM UPDATE_NON_TRANSACTION_ITMS.
    PERFORM DELETE_EMPTY_RECORDS.
    CLEAR: IMARDHT,IMARDT,IMKPFT1,IMKPFT,I_FINAL,I_FINAL5.
    REFRESH: IMARDHT,IMARDT,IMKPFT1,I_FINAL,I_FINAL5,IMKPFT.
ENDLOOP.
CLEAR: R_BUDAT.
REFRESH: R_BUDAT.
*end of changes for month.
ENDFORM. " getdata_fg_stock
FORM MONAT_F4 *
F4-Hilfe für Monat *
FORM MONAT_F4.
DATA: BEGIN OF MF_DYNPFIELDS OCCURS 1.
          INCLUDE STRUCTURE DYNPREAD.
DATA: END OF MF_DYNPFIELDS.
DATA: MF_RETURNCODE LIKE SY-SUBRC,
         MF_MONAT LIKE ISELLIST-MONTH,
         MF_HLP_REPID LIKE SY-REPID.
FIELD-SYMBOLS: .
Wert von Dynpro lesen
GET CURSOR FIELD MF_DYNPFIELDS-FIELDNAME.
APPEND MF_DYNPFIELDS.
MF_HLP_REPID = SY-REPID.
DO 2 TIMES.
    CALL FUNCTION 'DYNP_VALUES_READ'
      EXPORTING
        DYNAME               = MF_HLP_REPID
        DYNUMB               = SY-DYNNR
      TABLES
        DYNPFIELDS           = MF_DYNPFIELDS
      EXCEPTIONS
        INVALID_ABAPWORKAREA = 01
        INVALID_DYNPROFIELD = 02
        INVALID_DYNPRONAME   = 03
        INVALID_DYNPRONUMMER = 04
        INVALID_REQUEST      = 05
        NO_FIELDDESCRIPTION = 06
        UNDEFIND_ERROR       = 07.
    IF SY-SUBRC = 3.
Aktuelles Dynpro ist Wertemengenbild
      MF_HLP_REPID = 'SAPLALDB'.
    ELSE.
      READ TABLE MF_DYNPFIELDS INDEX 1.
Unterstriche durch Blanks ersetzen
      TRANSLATE MF_DYNPFIELDS-FIELDVALUE USING '_ '.
      EXIT.
    ENDIF.
ENDDO.
IF SY-SUBRC = 0.
Konvertierung ins interne Format
    CALL FUNCTION 'CONVERSION_EXIT_PERI_INPUT'
      EXPORTING
        INPUT         = MF_DYNPFIELDS-FIELDVALUE
      IMPORTING
        OUTPUT        = MF_MONAT
      EXCEPTIONS
        ERROR_MESSAGE = 1.
    IF MF_MONAT IS INITIAL.
Monat ist initial => Vorschlagswert aus akt. Datum ableiten
      MF_MONAT = SY-DATLO(6).
    ENDIF.
    CALL FUNCTION 'POPUP_TO_SELECT_MONTH'
      EXPORTING
        ACTUAL_MONTH               = MF_MONAT
      IMPORTING
        SELECTED_MONTH             = MF_MONAT
        RETURN_CODE                = MF_RETURNCODE
      EXCEPTIONS
        FACTORY_CALENDAR_NOT_FOUND = 01
        HOLIDAY_CALENDAR_NOT_FOUND = 02
        MONTH_NOT_FOUND            = 03.
    IF SY-SUBRC = 0 AND MF_RETURNCODE = 0.
ASSIGN (MF_DYNPFIELDS-FIELDNAME) TO <MF_FELD>. " ==>> note 148804
<MF_FELD> = MF_MONAT.
      CALL FUNCTION 'CONVERSION_EXIT_PERI_OUTPUT'
        EXPORTING
          INPUT = MF_MONAT
        IMPORTING
          OUTPUT = MF_DYNPFIELDS-FIELDVALUE.
      COLLECT MF_DYNPFIELDS.
      CALL FUNCTION 'DYNP_VALUES_UPDATE'
        EXPORTING
          DYNAME               = MF_HLP_REPID
          DYNUMB               = SY-DYNNR
        TABLES
          DYNPFIELDS           = MF_DYNPFIELDS
        EXCEPTIONS
          INVALID_ABAPWORKAREA = 01
          INVALID_DYNPROFIELD = 02
          INVALID_DYNPRONAME   = 03
          INVALID_DYNPRONUMMER = 04
          INVALID_REQUEST      = 05
          NO_FIELDDESCRIPTION = 06
          UNDEFIND_ERROR       = 07. "<<== note 148804
    ENDIF.
ENDIF.
ENDFORM.                                                    "MONAT_F4
*& Form get_month_dates
Calculating the Month Start & End Date
FORM GET_MONTH_DATES.
IF M1 = 'X'.
    FYEAR = P_SPMON+0(4).
    MON = P_SPMON+4(2).
    CONCATENATE FYEAR MON '01' INTO R_BUDAT-LOW.
    R_BUDAT-SIGN = 'I'.
    R_BUDAT-OPTION = 'BT'.
    CALL FUNCTION 'BKK_GET_MONTH_LASTDAY'
      EXPORTING
        I_DATE = R_BUDAT-LOW
      IMPORTING
        E_DATE = R_BUDAT-HIGH.
    APPEND R_BUDAT.
    CLEAR S_BUDAT.
    REFRESH S_BUDAT.
    S_BUDAT-SIGN = 'I'.
    S_BUDAT-OPTION = 'BT'.
    S_BUDAT-LOW = R_BUDAT-LOW.
    S_BUDAT-HIGH = R_BUDAT-HIGH.
    APPEND S_BUDAT.
ELSE.
    FYEAR = P_SPMON+0(4).
    MON = P_SPMON+4(2).
    CONCATENATE FYEAR MON '01' INTO R_BUDAT-LOW.
    R_BUDAT-SIGN = 'I'.
    R_BUDAT-OPTION = 'BT'.
    CALL FUNCTION 'BKK_GET_MONTH_LASTDAY'
      EXPORTING
        I_DATE = R_BUDAT-LOW
      IMPORTING
        E_DATE = R_BUDAT-HIGH.
    APPEND R_BUDAT.
ENDIF.
ENDFORM. " get_month_dates
*& Form output_table_Check
checking for records for output
FORM OUTPUT_TABLE_CHECK .
DESCRIBE TABLE I_FINALT LINES INDEX.
IF INDEX EQ 0.
    MESSAGE I041 WITH TEXT-005.
    LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM. "OUTPUT_TABLE_CHECK
*& Form Z_TOP_OF_PAGE
for setting the details in the top of page *
has no formal paramters *
FORM Z_TOP_OF_PAGE.
DATA: V_MON(2),
V_YR(40),
V_FIN(18),
V_FIN1(48),
LOW(10),
HIGH(10).
V_MON = P_SPMON+4(2).
V_YR = P_SPMON+0(4).
FHEADER-TYP = 'H'.
FHEADER-INFO = 'Stock Register Report (FG Stock)'.
APPEND FHEADER.
CLEAR FHEADER.
*if m1 = 'X'.
CONCATENATE 'Month = ' v_mon '.' v_yr INTO v_fin.
fheader-typ = 'H'.
fheader-info = v_fin.
APPEND fheader.
CLEAR fheader.
*endif."prabhu on 18.5.5
IF D1 = 'X'.
    CLEAR S_BUDAT.
    LOOP AT S_BUDAT.
      CONCATENATE S_BUDAT-LOW6(2) '/' S_BUDAT-LOW4(2) '/'
      S_BUDAT-LOW+0(4) INTO LOW.
      CONCATENATE S_BUDAT-HIGH6(2) '/' S_BUDAT-HIGH4(2) '/'
      S_BUDAT-HIGH+0(4) INTO HIGH.
      CONCATENATE 'Date = ' LOW ' - ' HIGH INTO V_FIN1.
      FHEADER-TYP = 'H'.
      FHEADER-INFO = V_FIN1.
      APPEND FHEADER.
      CLEAR FHEADER.
    ENDLOOP.
ENDIF.
ENDFORM. " Z_TOP_OF_PAGE
*& Form Z_LAYOUT_SETTINGS
this is done for setting the properties for the layout of the *
grid *
has no formal paramters *
FORM Z_LAYOUT_SETTINGS.
FS_LAYO-ZEBRA = 'X'. " Output in Zebra pattern
FS_LAYO-DETAIL_POPUP = 'X'. " A popup window appears to give
FS_LAYO-DETAIL_TITLEBAR = TEXT-022.
FS_LAYO-COLWIDTH_OPTIMIZE = 'X'.
ENDFORM. " Z_LAYOUT_SETTINGS
*& Form Z_ALV_EVENTS
This is used for handling the events TOP OF PAGE and the USER *
COMMAND event *
has no formal paramters *
FORM Z_ALV_EVENTS.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      I_LIST_TYPE = 0
    IMPORTING
      ET_EVENTS   = FEVENTS[].
READ TABLE FEVENTS WITH KEY NAME = 'TOP_OF_PAGE'.
IF SY-SUBRC = 0.
    FEVENTS-FORM = 'Z_TOPOFPAGE'.
    MODIFY FEVENTS INDEX SY-TABIX.
    CLEAR FEVENTS.
ENDIF.
READ TABLE FEVENTS WITH KEY NAME = 'USER_COMMAND'.
IF SY-SUBRC = 0.
    FEVENTS-FORM = 'Z_USER_COMMAND'.
    MODIFY FEVENTS INDEX SY-TABIX.
    CLEAR FEVENTS.
ENDIF.
ENDFORM. "Z_ALV_EVENTS
*& Form Z_CREATE_FIELD_CATALOG
here the field catalog is created for the primary list *
no formal parameters *
FORM Z_CREATE_FIELD_CATALOG.
for the Plant
FCAT-FIELDNAME = 'WERKS'.
FCAT-KEY = 'X'.
FCAT-OUTPUTLEN = '000005'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Plant'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'CHAR'.
APPEND FCAT.
CLEAR FCAT.
for the Material Type
FCAT-FIELDNAME = 'MTART'.
FCAT-KEY = 'X'.
FCAT-OUTPUTLEN = '000006'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'MatTyp'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'CHAR'.
APPEND FCAT.
CLEAR FCAT.
for the Material No.
FCAT-FIELDNAME = 'MATNR'.
FCAT-KEY = 'X'.
fcat-hotspot = 'X'.
FCAT-OUTPUTLEN = '000018'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Material'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'CHAR'.
APPEND FCAT.
CLEAR FCAT.
for the Material Description
FCAT-FIELDNAME = 'MAKTX'.
FCAT-KEY = ''.
FCAT-OUTPUTLEN = '000040'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Description'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'CHAR'.
APPEND FCAT.
CLEAR FCAT.
for the Unit of Measure
FCAT-FIELDNAME = 'MEINS'.
FCAT-KEY = ''.
FCAT-OUTPUTLEN = '03'.
FCAT-JUST = 'C'.
FCAT-SELTEXT_M = 'UOM'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'UNIT'.
APPEND FCAT.
CLEAR FCAT.
for the Plant
FCAT-FIELDNAME = 'MONTH'.
FCAT-KEY = 'X'.
FCAT-OUTPUTLEN = '08'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'MONTH'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'C'.
FCAT-DATATYPE = 'CHAR'.
APPEND FCAT.
CLEAR FCAT.
for the Opening Stock
FCAT-FIELDNAME = 'C_STK'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Opening Stock'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
fcat-do_sum = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND FCAT.
CLEAR FCAT.
for the Total Receipts
FCAT-FIELDNAME = 'TRECEP'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Total Receipts'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
FCAT-DO_SUM = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND FCAT.
CLEAR FCAT.
for the Production
FCAT-FIELDNAME = 'PRODU'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Production'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
FCAT-DO_SUM = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND FCAT.
CLEAR FCAT.
for the Other Plant Receipts
FCAT-FIELDNAME = 'RECEP'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Othr Plnt Recpts'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
FCAT-DO_SUM = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND FCAT.
CLEAR FCAT.
Sales Return
FCAT-FIELDNAME = 'SAL_RET'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Sales Return'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
FCAT-DO_SUM = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND FCAT.
CLEAR FCAT.
Total Dispatches
FCAT-FIELDNAME = 'TDISP'.
FCAT-HOTSPOT = ' '.
FCAT-OUTPUTLEN = '000016'.
FCAT-JUST = 'L'.
FCAT-SELTEXT_M = 'Total Dispatches'.
FCAT-DDICTXT = 'M'.
FCAT-INTTYPE = 'Q'.
FCAT-DATATYPE = 'QUAN'.
FCAT-DO_SUM = 'X'.
FCAT-JUST = 'R'.
FCAT-NO_ZERO = 'X'.
APPEND

Tables for inventory report(proper sequence)---urgent

Hi all,
i want to write a report for physical inventory for both raw & finished goods.
in selection screen there will be customer, plant & date.
for this customer & current date, i have to extract the raw & finish goods (material & qty) from all storage locations under that plant.
can u plz tell me the proper sequence of the database tables , i need to use to achieve the above things?
it is urgent.
Thanks for ur help.
ur help will be appreaciated.
reagards
pabitra

Hi,
Please have a look at table:
LQUA - Quants
Krzys

Physical Inventory Freezed - Urgent Customer Order

Hi Gurus,
While performing physical Inventory, all my Org/Sub Inventory has been freezed.
Same time my regular, important export customer requested sales order for few items, needs to ship items urgently?
How to perform transactions in the system, if Org is freezed.
I have advised the client to do offline transaction and perform the transaction once Org is unfreeze but client has to export items to other country, all documents BOL, Commercial invoice all are compulsory.
Please advise the best solution to achieve this scenario.
Regards
Chini

what you described is not subject to customer material inforecord.
Your scenario can be met with material determination. This can be maintained in VB11.
When you enter material number 536 in sales order, SAP automatically finds 235. where your inventory is managed.
But if 536 is your customers material number, then you can maintain this as info in the customer material inforecord, and it will print in your sales order. But you then will never enter 536 in the sales order, you will always enter 235 in the sales order. You can just use the F4 search help to search for your 235 by specifying 536 in the matchcode (material to customer)

URGENT : Please help: Purchasing and Inventory loads

I am currently in BWQ. I did the inital deletion of set up tables by LBWG and then ran the set up jobs through SBIW for Purchasing and Inventory.
I also did the industry setting and processkey .
I ran the init load yesterday and it gave some records and then deltas brought 0 records . For some reason I felt that there should not be 0 records and I went and deleted the set up table again and ran the set up jobs. I can see records in the set up table and RSA3.
But when I am running the load today it brings 0 records. I thought may be the delta ran this morning so it brought 0 records. therefore I ran the full repair reuqest but still there only 0 records.
Can someone explain this and advice what needs to be done.
Thanks

Hi BI TCS
Initially when you loaded init data you got some records and delta brought 0 records. This is logical if there are no new records creates in R/3 system or you have not executed delta collector job - Job control through LBWE for a particular application.
Now carry out following steps for purchasing data loads -
1.delete the setup tables using tcode LBWG
2.perform set up for the purchasing in background mode
3.check the job log for step 2 in SM27
4. find out no of documents written to setup tables for purchasing using tcode NPRT
5.Now load the init load to BW- this will load the data that you have covered under setup tables
6. Now create/change some data in R/3. This data must be withing your init range used in init infopackage. If you have done init load with no selection parameters then no problem.
7. Run job control for purachasing in LBWE
8. Now load the delta load -> it should load the correct delta data into BW.
Hope this resolves
Regards
Pradip

Inventory aging report, plz help me its very urgent

Hi experts,
i have a problem in reporting, yesterday i got requirement form uesrs for Inventory Aging report,
the report fields Contains
1) Plant
2) Meterial
3) Stock as on date( closing stock) with both fields Quantity & value fields
4) Average Useage in 6 months with both fields Quantity & Value
5) Month on Hand in units
6)Inventory Aging 30 days with Units and quantity
                           60 days with Units and quantity
                           90 days with Units and Quantity
                           120 days
                            150days
                             180 days
                              270 days
                               365 + days
we are using bw 3.5 version
note: we are u using standard Business Content Cube ( 0IC_C03) with is coming fron standard Business content DataSources 2Lis_03_BX, 2Lis_03_BF, 2Lis_03_UM
please suggest me to make this report, please send process in clearly.
i will assign full points
Advance thanks,
Sudheer

hello Sudheer,
I remember once creating an Inventory aging document whcih had somwhat the same requirment of going back 6weeks and the other was like 18 weeks from the current week.Do you have cubes regarding the diffrent types of orders, like Planned order, Purchase order, production order and purchase requistion or a multi on top of it.If so then create query on top of this multiprovider like Inventory aging 30days, inventory aging 60days etc.then in that query create a variable on calweek (Single value,mandatory and customer exit), this variable should be able to get the current week (depending on when your table was loaded in R3 and if you can get that info thru rfc in BI), this is so that you can determine current week and then specify variable off set in diffrent queries with diffrent requirements of going back, ex: -4 (for 4 weeks ie 1 month) etc, or just create your variable on calmonth and then you need to set an offset just one month back ex -1.
Create APDs and then load the data in transactional DSOs.Excecute the APD one at a time into the diffrent cubes .Create a multiprovider if you want on top of it.
Hope this can get you started....
Krrish

Urgent: regarding physical inventory report display

hi,
i had made a report in which i have to display the physical inventory report details in which details about the material is to be given.
I want to check the details which are present in the tcode MI07 . Can anybody tell me any tcode in which i can see the details of mi07 tcode(including the reason of it).

Greetings,
It might shed some light to read about the display in your portable computer: http://en.wikipedia.org/wiki/LCD
LCDs are primarily plastic panels with various layers inside. Pressure applied to those panels can cause them to crack, leaking the liquid crystal components about. Pressure could be heavy books in a bag pushing against the screen, heavy cat sitting on a closed lid, dog, other animal, someone slamming the lid, child running through the room, etc. This applies to any LCD whether it be in a computer or in a Television (don't press too hard on your TV screen!!).
Displays don't exhibit the type of damage you indicate by themselves. A single pixel might go dead in an LCD but zig zag lines indicates cracking of the layers inside the panels themselves. Something from the outside world made an impact on the display resulting in the damage you see. You may not have been the one pressing hard on it and you may not have seen it happen, but something happened.
The 1 year limited warranty and AppleCare protection plan offer coverage for component failures, not damage.
Coverage for damage would be provided by something along the lines of insurances (home owners, renters, etc.) If you purchased this computer with a Credit Card you may wish to contact your Credit Card company. Many cards have included insurance for purchases you make so even if an item is damage during your use of it, they will cover it.
Best of luck.

Urgent help need:How inventory system and fulfillment system work

Hi Every one ,
I have an requirement to work on inventory and fulfillment system,below are my questions,
1)I have stock level quantity for an sku is 2 ,if one user done with his order with quantity of 2 then how we can show quantity to the second customer (if stock not available we gone loss the business )
how we can handle this ?
2)There are few orders are completed(if some are orders are having quantity available in stock some or backorders)
here how the fulfillment system understand those orders and how it will update the inventory.
Could you please any one help me how to work on above requirements or else give me some other solutions to full fill above .
Regards,
Jyothi Chidurala
Edited by: Jyothi.mj on May 22, 2013 5:08 AM
Edited by: Jyothi.mj on May 23, 2013 4:28 AM

>
1)I have stock level quantity for an sku is 2 ,if one user done with his order with quantity of 2 then how we can show quantity to the second customer (if stock not available we gone loss the business )
how we can handle this ?
you can always call InventoryManager.AVAILABILITY_STATUS_IN_STOCK to check whether the item is available in inventory , It is the business call if item not available how they want to handle this .
hope this helps

Physical inventory 4.6c & Ecc 6.0(urgent)

Hi all
We are in to 4.6 c and planned to move to Ecc 6.0 in few months. I have a situation like to do the physical inventory of the warehouse but my thoughts would be to do it after the upgrade as we'll have additional features in ECC6.0 for counting.
Do anybody know how ECC 6.0 helps than 4.6C,what will be the advantages to justify it.
please drop whatever suggestions u have, iam sure that will help a lot or direct me to proper docs plz.
Thank you all.

Hi Terry,
are you talking about IM or WM inventory ?
If I remember correctly WM Dynamic Cycle Count (DCC) was introduced from version 4.7 and, as Sap states
"<i>DCC enhances the previous inventory counting functionality by enabling you to count physical inventory at storage bin and quant level during the performance of normal warehouse operations, and allowing the creation of inventory documents when open transfer orders (unconfirmed picks and putaways) exist for a bin. This ensures continued warehouse operations and facilitates cycle counts during peak activity periods</i>".
Is this what are you looking for ?
Best regards,
Enrico

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

Urgent:Receipt and Issue values in Inventory 0IC_C03

Dear friends,
In standard cube 0IC_C03 keyfigures Valuated stock Qty and value is matching with R/3 Transaction code MB5B.
Receipt quantity and Issue quantity in MB5B is not matching for some of the materials.But it matches with R/3 Tcode MB51 as it have all the movement types.
1.Pls suggest what needs to be done in BW to match the data with MB5B Receipt and Issues?
2.What are the movement types are used in MB5B?.(For ex 321 is displayed in MB51 but not included in the R/3 report MB5B)
Thanks in advance for your help..

Dear Gurus,
Recently we had Implemented the Inventory Management for Retail. Taken downtime and loaded the data by following all the steps. The data is successfully loaded till Nov 2010 to till date. Now when I am comparing the data with R3 using MB51, I am getting the below issues.
We have report in BI, on Material Ledger and we run above query for the duration of 1st Jan 2011 to 31st Jan 2011, This appear to be difference in the output.
BI opening quantity does not match with ECC MB5B opening matches.
1. Few of my BI entries of Movements are not present in R3.
2. Few entries are with no movements present in BI.
3. Some entries of R3 are not present in BI.
Can anyone guide me....

URGENT, Creating the Oracle Inventory Group

OS: 5.2
DB:10g Rel 2
Hello All,
I am installing 10g on AIX.
Per below link/document.
Page 2-11 (Pre Installation Task)
$ more /etc/oraInst.loc
/etc/oraInst.loc: A file or directory in the path name does not exist.
** Creating the Oracle Inventory Group
If the oraInst.loc file does not exist, then create the Oracle Inventory group by
using the following procedure:
1. Enter the following command:
smitty security
Choose the appropriate menu items to create the oinstall group.
http://download-west.oracle.com/docs/cd/B19306_01/install.102/b19075.pdf
But I alreday created oinstall group.
Please note: we used oraabc instead of oracle.
id oraabc
uid=207(oraabc) gid=14(oinstall) groups=15(dba),16(oper)
Do I still need to create the oraInst.loc file or its is a part of installation?
DN

As far I know oraInst.loc file is created during installation procedure.
It consists of path to oracleInventory directory and installation group in your case - oinstall.
I never installed Oracle on AIX but I belive installation is (allmost) the same as on Linux or Solaris.

Creating the Oracle Inventory Group, Urgent

OS: 5.2
DB:10g Rel 2
Hello All,
I am installing 10g on AIX.
Per below link/document.
Page 2-11 (Pre Installation Task)
$ more /etc/oraInst.loc
/etc/oraInst.loc: A file or directory in the path name does not exist.
** Creating the Oracle Inventory Group
If the oraInst.loc file does not exist, then create the Oracle Inventory group by
using the following procedure:
1. Enter the following command:
smitty security
Choose the appropriate menu items to create the oinstall group.
http://download-west.oracle.com/docs/cd/B19306_01/install.102/b19075.pdf
But I alreday created oinstall group.
Please note: we used oraabc instead of oracle.
id oraabc
uid=207(oraabc) gid=14(oinstall) groups=15(dba),16(oper)
Do I still need to create the oraInst.loc file or its is a part of installation?
DN

It should be taken care of by the installer.
on the same page, it says "When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file."

urgent Inventory

Similar Messages

Maybe you are looking for