0IC_C03 related Inventory Process - Logical Partitioning (Vs) Physical Part

Hello Everyone,
After going through multiple postings throughout the form and documentation from SAP, it states that the 0IC_C03 InfoCube when used with Non Cumulative keyfigures is not recommended to be partitioned logically by physical year/calendar year as the query will read all the data sets due to the stock marker logic.
In our specific scenario,
1. After the InfoCube (0IC_C03) was enhanced with additional characterisitcs such as Doc Number, Movement type and so on due to business requirements I was not able to actually use the Non Cumulative Keyfigures as they were not populated within the report.
2. So, we decided not to use the Non Cumulative keyfigures but rather create two cumulative keyfigures (Issue Stock Quantity - Receipt Stock Quantity) and (Issue Valuated Stock Value - Receipt Valuated Stock Value) and both of these are available in the InfoCube and are calculated during the update process.
These two keyfigures are cumulative with exception aggregation of LAST based on 0CALDAY.
The question is,
Since we are not using the actual Non Cumulative Keyfigures (even though we are not using these, we still have the stock marker updated and data compressed based on this along with Validity table defined) can we do logical partitioning on the InfoCube based on Calendar year.
Thanks....

Hello Elango,
Appreciate your response.
First of..I do understand the difference between logical and physical partitioning and the question is not about joining them together.
I am sorry, if others cannot understand the detailed issue posted. My apologies was a part of polite gesture, and please do respond back with proper precise answer if you think you did actually understand the question....
The question here is about how I can leverage the performance and administrative performance by logically breakingdown the data.
The issues due to which I am trying to look into different aspects of logical partitioning are:
1. If I do logical partitioning by Plant due to the stock marker logic then I cannot do archiving as a Plant and its related data cannot be archived by time characteristic as the partitioning is not done by time characteristic.
2. The reason I would have to have document number and movement type in the InfoCube is due to the kind of reporting users perform.
We have a third party system whose data needs to be reconciled to the data in the plants and storage locations.
And in order to do so, the first step users would be running the report is plant, storage location and sku. From here on for the storage locations which have balance they would like to drill down on to the document number and movement type to see what the actual activity is.
So, to support this requirement I would have to have the above characterisitcs in the InfoCube.
The question again is,.....what is the exact list of issues I would be having doing the logical partitioning by time characteristic.
Once again, even though the non cumulative keyfigures are available in the InfoCube we are not using them for any reporting purpose....so please keep that in consideration while replying back.
Thanks
Dharma.

Similar Messages

  • Any real reason for logical partitioning over physical?

    Hi!
    I have seen a number of scenarios where SAP BI (assuming BI 7.0 for the rest of the discussion), running in high volume scenarios, have been cluttered by a lot of logically partitioned cubes joined by multi providers....
    Obviously the disadvantage of using logical partitions is that it increases maintenance efforts: you need a new update rule for each logical partition (cube) , then you need to manually add/delte cubes from the multiprovider, filtering data in the update rules to reach the correct cube based on time characteristic etc etc...
    I have seen one clear advantage which is the parallelization of queries run against a multiprovider - assuming you wan't to all underlying cubes ... but are there any other advantages which overcome the mainenance overhead?
    For me it feels like using physical database partitions in the same cube would be the correct decision in 90% of the cases. It seems to me that the underlying RDBMS should be able to handle itself to:
    1) Parallellize a query over several physical partitions if needed.
    2) Be smart enough to only query the needed partition if the query is restricted based on the partitioning characteristic.
    Please correct me anyone? - When is logical partitions really motivated?
    Best regards,
    Christian
    Edited by: Christian on May 15, 2008 3:55 PM

    Hi,
    This is a great question. Generally it is very difficult to understand the real motivation for the physical partioning - multiple cubes. You are right, it definitely increases the maintenance overhead. And you have already pointed out both the advantages and disadvantages.
    Physical Partitioning is more useful where we have huge amounts of data. Imagine a cube with 3 or 4 GB of data - which are not usual - but possible.  The Table Partioning is useful with small infocubes, less than 1 GB. With bigger Infocubes, Table level partitioning may not provide the required level of performance. If we have too many small partitions, that would also reduce the perfomance. If we have too few  partitions, the query performance will not be as much as we want. In this scenario, we can use Physical partitioning (Multiple Cubes) combined with Table Level Partitioning to achieve the required performance levels. On top, we can even think of using Aggregates for further betterment of the performance.
    While all the above seems to be relevant for older versions of BW (upto 3.5), BI 7.0 has the BIA (BI Accelerator), which works on the Blade Server with all the data cached directly on the main memory. I am not sure how much this would impact the data modeling - I have not started working on the BIA as yet.
    rgds
    naga

  • Physical Vs Logical Partitioning

    We have 2 million records in the sales infocube for 3 years. We are currently discussing the pros and cons of using Logical partitioning Vs Physical Partitioning. Please give your inputs.

    hi
    there are two types of partitioning generally talked about with SAP BW, logical and physical partitioning.
    Logical partitioning - instead of having all your data in a single cube, you might break into separate cubes, with each cube holding aspecific year's data, e.g. you could have 5 sales cubes, one for each year 2001 thru 2005.
    You would then create a Multi-Provider that allowed you to query all of them together.
    A query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, running at the same time. The system automatically merges the results from the 5 queries into a single result set.
    So it's easy to see when this could be a benefit. If your queries however are primarily run just for a single year, then you don't receive the benefit of the parallel processing. In non-Oracle DBs, splitting the data like this may still be a benefit by reducing the amount of rows in the fact table that must be read, but does not provide as much value to an Oracle DB since Infocube queries are using a Star_Transformation.
    Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. This is a separately licensed option in Oracle.
    Physical partitioning allows you to split an Infocube into smaller pieces. The pieces, or partitions, can only be created by 0FISCPER or 0CALMONTH for an InfoCube (ODSs can be partitioned, but require a DBAs involvement). The DB can then take advantage of this partitioning by "pruning" partitions during a query, e.g. a query only needs data form June 2005
    The DB is smart enough to restrict the indices and data it will read to the June 2005 partition. This assumes your query restricts/filters on the partitioning characteristic. It can apply this pruning to a range of partitions as well, e.g. 0FISCPER 001/2005 thru 003/2005 would only look at the 3 partitions.
    It is NOTsmart enough, however, to figure out that if your restrict to 0FISCYEAR = 2005, that it should only read 000/2005 thru 016/2005 since 0FISCYEAR is NOT the partitioning characteristic.
    An InfoCube MUST be empty in order to physically partition it. At this time, there is no way to add additional partitions thru AWB, so you want to make sure that you create partitions out into the future for at least a of couple of years.
    If the base cube is partitioned, any aggregates that contain the partitioning characteristic (0CALMONTH or 0FISCPER) will automatically be partitioned.
    In summary, you need to figure out if you want to use physical or logical partitioning on the cube(s), or both, as they are not mutually exclusive.
    So you would need to know how the data will be queried, and the volume of data. It would make little sense to partition cubes that will not be very large.
    physical partitioning is done at database level and logical partitioning done at data target level.
    Cube partitioning with time characteristics 0calmonth Fiscper is physical partitioning.
    Logical partitioning is u partition ur cube by year or month that is u divide the cube into different cubes and create a multiprovider on top of it.
    logical Vs physical partitions ?

  • Output type for HU physical inventory process

    Hi All,
    During a HU physical inventory process we print the physical inventory
    document (the list) by transaction HUINV02.
    The customer would like to make a few changes in the layout.
    we didnt find the standard form and also not the output type.
    is anybody know if there is a form or output type for this list?
    Thanks,
    Sharon.

    Ok.
    I think you need to create a new output type for this. Because even I did not find it anywhere in NACE.
    Here is the print program: RM07IDRU.
    As you already have the form name, you can create the output type.
    Vishwa.

  • Logical vs. Physical Partitioning

    Hi,
    In a discussion of logical partition the author pointed out that
    “… if a query that needs data from all 5 years would then automatically (you can control this) be split into 5 separate queries, one against each cube, running at the same time. The system automatically merges the results from the 5 queries into a single result set.”
    1. Can you direct me on how to “control this” as the author indicated?
    2. Also, the author noted that
    “… Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. …”
    a) Does it mean that BW does not use physical partitioning?
    b) Where do we indicate physical or logical partitioning as an option in BW?
    c) Or, when we talk about dimension table, etc. is there always an underlining database such as Oravle, Infomix, etc in BW? If so, what does BW use?
    3. For physical partitions, I read that the cube needs to be empty before it can be partitioned. What about logical partition?
    4. Finally, what are the underlying criteria to decide on logical or physical partitioning or both
    Thanks

    . Can you direct me on how to “control this” as the author indicated?
    You make this setting RSRT.
    2. Also, the author noted that
    “… Physical Partitioning - I believe only Oracle and Informix currently support Range partitioning. …”
    DB2 also support partiioning. Also the current relese of SQL server support partitioning.
    b) Where do we indicate physical or logical partitioning as an option in BW?
    Physical parittions are set up in the cube change option. When you are in  the cube change mode, on the themenu, chose extras - performance / DB parameters - parttitios.
    Now a screen will pop giving the time characteristics in the cube and choose the characteristic (s) that you wish to chose and confirm the entries - then you will get another small pop up where you set the no of parittions.
    Also, pl note that you can partition only on fiscalyear and fiscal period and not on other time characteritsitcs.
    Logical partitions: Logical paritions are nothinb but spilting the cube into numerous cubes of smaller sizes. You combine all these cubes by means of multi provider. For example, if you have 1000 cost centers , you may want to split into cubes based on the cost cenree numbers and combine them into a multi provider.
    No more setting is required.
    c) Or, when we talk about dimension table, etc. is there always an underlining database such as Oravle, Infomix, etc in BW? If so, what does BW use?
    Dimension tables / fact tables/ ODS tables /master data tables are all database tables. Which ever database you use and when yu activate these objects, the tables are created in the underlying database.
    3. For physical partitions, I read that the cube needs to be empty before it can be partitioned. What about logical partition?
    Logical partiton can be done any time.
    4. Finally, what are the underlying criteria to decide on logical or physical partitioning or both
    The underlying criteria is facotrs such as :
    (a) the no of years of history tou wish to view in reports.
    (b) te no ofyears you will hold the data in BW before archiving.
    (c) othe performance matters related tro sizing.
    Ravi Thothadri

  • Cannot create another 2 logical partitions on another physical server

    when i installed the BI 7.0 on AIX/DB2 9 platform. i can create 2 logical partition on the main server , yet i couldn't create another 2 logical parttions on the second server.  the following is the error message
    INFO       2008-02-21 03:49:03.490
    "sapinst_dev.log" [Read only] 20411 lines, 744293 characters
    TRACE      2008-02-21 03:51:28.513 [iaxxejsexp.cpp:199]
               EJS_Installer::writeTraceToLogBook()
    Found Error, error_codes[1] = <db2start dbpartitionnum 5 add dbpartitionnum hostname sapaix08 port 3 without tablespaces
    SQL6073N  Add Node operation failed.  SQLCODE = "-1051".>
    TRACE      2008-02-21 03:51:28.513 [iaxxejsexp.cpp:199]
               EJS_Installer::writeTraceToLogBook()
    During execution of <AddPart.sql>, <2> errors occured.
    ERROR      2008-02-21 03:51:28.513 [iaxxinscbk.cpp:282]
               abortInstallation
    MDB-01999  Error occured, first error is: <SQL6073N  Add Node operation failed.  SQLCODE = "-1051".>
    TRACE      2008-02-21 03:51:28.514 [iaxxejsbas.hpp:388]
               handleException<ESAPinstException>()
    Converting exception into JS Exception Exception.
    ERROR      2008-02-21 03:51:28.515
               CJSlibModule::writeError_impl()
    MUT-03025  Caught ESAPinstException in Modulecall: ESAPinstException: error text undefined.
    TRACE      2008-02-21 03:51:28.515 [iaxxejsbas.hpp:460]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2008-02-21 03:51:28.516 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step AddDB6Partitions with step key |NW_DB6_DB_ADDPART|ind|ind|ind|ind|0|0|NW_DB6_AddPartitions|ind|ind|ind|ind|12|0|
    AddDB6Partitions was executed with status ERROR .
    TRACE      2008-02-21 03:51:28.539 [iaxxgenimp.cpp:719]
               showDialog()
    the following is my prerequisite for the installation
    1. the user and group id and property is the same as the primary (server1)
    2. the ssh trust relationship has built , i can ssh  server1 from server2 or server2 from server1 with db2sid, sidadm users
    3. i mount the /db2/db2sid , /db2/SID/db2dumps, /sapmnt/SID/exe on server2 as NFS
    4. install the db2 software on /opt/IBM/db2/V9.1   (the location is the same as the primary's)
    HI , DB2 experts. Could you give me some suggestion?   thanks!

    Hi,Thomas,
    Thanks for your help.  the db2 database  desn't use the autostoarge method and the relevant permission is the same as server1.  i checked the db2dialog.log.  the following is the detail information
    "Storage path does not exist or is inaccessible" is the error message . i was wondering which storage path does not exit or inaccessible .
    at the same time i have login on all /db2 with db2sid and run touch to test the permision . it sounds good. I don't know what happens , could you give me some suggestion ? thanks!
    2008-02-21-08.10.56.442000-300 I14165596A287      LEVEL: Event
    PID     : 843832               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
    DATA #1 : String, 26 bytes
    Stop phase is in progress.
    2008-02-21-08.10.56.444783-300 I14165884A302      LEVEL: Event
    PID     : 843832               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
    DATA #1 : String, 41 bytes
    Requesting system controller termination.
    2008-02-21-08.10.56.450366-300 I14166187A403      LEVEL: Warning
    PID     : 712906               TID  : 1           PROC : db2sysc 5
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
    MESSAGE : Bringing down all db2fmp processes as part of db2stop
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFE400 : 0000 0000                                  ....
    2008-02-21-08.10.56.456345-300 I14166591A304      LEVEL: Event
    PID     : 843832               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
    DATA #1 : String, 43 bytes
    System controller termination is completed.
    2008-02-21-08.10.56.461462-300 I14166896A381      LEVEL: Event
    PID     : 843832               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
    DATA #1 : String, 24 bytes
    There is no active EDUs.
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFCEE0 : 0000 0000                                  ....
    2008-02-21-08.10.56.504322-300 I14167278A342      LEVEL: Severe
    PID     : 823374               TID  : 1           PROC : db2acd 5
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFF5A4 : FFFF FBEE                                  ....
    2008-02-21-08.10.56.654959-300 E14167621A301      LEVEL: Event
    PID     : 843832               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
    MESSAGE : ADM7514W  Database manager has stopped.
    STOP    : DB2 DBM
    2008-02-21-08.11.09.664000-300 I14167923A417      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 53 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 0 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0022                                  ..."
    2008-02-21-08.11.10.176098-300 I14168341A417      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 53 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 1 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0022                                  ..."
    2008-02-21-08.11.10.595702-300 I14168759A417      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 53 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 2 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0022                                  ..."
    2008-02-21-08.11.11.124888-300 I14169177A417      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 53 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile FORCE1 3 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0022                                  ..."
    2008-02-21-08.11.12.070605-300 I14169595A410      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 46 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile 0 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0020                                  ...
    2008-02-21-08.11.12.694723-300 I14170006A410      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 46 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile 1 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0020                                  ...
    2008-02-21-08.11.13.115940-300 I14170417A410      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 46 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile 2 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0020                                  ...
    2008-02-21-08.11.13.632046-300 I14170828A410      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 46 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile 3 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0020                                  ...
    2008-02-21-08.11.14.577056-300 I14171239A418      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 54 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 0 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0024                                  ...$
    2008-02-21-08.11.15.004794-300 I14171658A418      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 54 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 1 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0024                                  ...$
    2008-02-21-08.11.15.425920-300 I14172077A418      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 54 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 2 0
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0024                                  ...$
    2008-02-21-08.11.15.941622-300 I14172496A418      LEVEL: Event
    PID     : 639410               TID  : 1           PROC : db2stop
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 54 bytes
    /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 3 1
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9CBC : 0000 0024                                  ...$
    2008-02-21-08.11.17.002107-300 I14172915A422      LEVEL: Event
    PID     : 639412               TID  : 1           PROC : db2start
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 57 bytes
    /db2/db2ab7/sqllib/adm/db2rstar db2profile SN ADDNODE 4 2
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9C2C : 0000 0011                                  ....
    2008-02-21-08.11.18.055723-300 E14173338A856      LEVEL: Warning
    PID     : 806940               TID  : 1           PROC : db2star2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
    MESSAGE : ADM12007E  There are "80" day(s) left in the evaluation period for
              the product "DB2 Enterprise Server Edition". For evaluation license
              terms and conditions, refer to the IBM License Acceptance and License
              Information document located in the license directory in the
              installation path of this product. If you have licensed this product,
              ensure the license key is properly registered. You can register the
              license via the License Center or db2licm command line utility. The
              license file can be obtained from your licensed product CD.
    2008-02-21-08.11.18.296453-300 E14174195A1040     LEVEL: Event
    PID     : 806940               TID  : 1           PROC : db2star2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W  Database manager has started.
    START   : DB2 DBM
    DATA #1 : Build Level, 152 bytes
    Instance "db2ab7" uses "64" bits and DB2 code release "SQL09012"
    with level identifier "01030107".
    Informational tokens are "DB2 v9.1.0.2", "special_17253", "U810940_17253", Fix Pack "2".
    DATA #2 : System Info, 224 bytes
    System: AIX sapaix08 3 5 00CCD7FE4C00
    CPU: total:8 online:8 Threading degree per core:2
    Physical Memory(MB): total:7744 free:5866
    Virtual  Memory(MB): total:32832 free:30943
    Swap     Memory(MB): total:25088 free:25077
    Kernel   Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
                     shmMax:68719476736 shmMin:1 shmIDs:131072
                     shmSegments:68719476736 semIDs:131072 semNumPerID:65535
                     semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
    2008-02-21-08.11.19.312894-300 I14175236A428      LEVEL: Error
    PID     : 835728               TID  : 1           PROC : db2agent (instance) 4
    INSTANCE: db2ab7               NODE : 004
    APPHDL  : 4-7                  APPID: *LOCAL.db2ab7.080221131118
    FUNCTION: DB2 UDB, base sys utilities, sqleGetAutomaticStorageDetails, probe:111111
    DATA #1 : <preformatted>
    dataSize 752 pMemAlloc 1110cdac0 sizeof(struct sqleAutoStorageCfg) 16
    2008-02-21-08.11.19.346560-300 I14175665A497      LEVEL: Error
    PID     : 835728               TID  : 1           PROC : db2agent (instance) 4
    INSTANCE: db2ab7               NODE : 004
    APPHDL  : 4-7                  APPID: *LOCAL.db2ab7.080221131118
    FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
    MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    DATA #1 : String, 17 bytes
    /db2/AB7/sapdata1
    2008-02-21-08.11.19.349637-300 I14176163A619      LEVEL: Severe
    PID     : 835728               TID  : 1           PROC : db2agent (instance) 4
    INSTANCE: db2ab7               NODE : 004
    APPHDL  : 4-7                  APPID: *LOCAL.db2ab7.080221131118
    FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
    MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    DATA #1 : String, 46 bytes
    Error during storage group file initialization
    DATA #2 : Pointer, 8 bytes
    0x0ffffffffffed006
    DATA #3 : Pointer, 8 bytes
    0x00000001110b3080
    2008-02-21-08.11.19.355029-300 I14176783A435      LEVEL: Error
    PID     : 835728               TID  : 1           PROC : db2agent (instance) 4
    INSTANCE: db2ab7               NODE : 004
    APPHDL  : 4-7                  APPID: *LOCAL.db2ab7.080221131118
    FUNCTION: DB2 UDB, base sys utilities, sqleStartDb, probe:5
    RETCODE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    2008-02-21-08.11.19.357831-300 I14177219A370      LEVEL: Warning
    PID     : 835728               TID  : 1           PROC : db2agent (instance) 4
    INSTANCE: db2ab7               NODE : 004
    APPHDL  : 4-7                  APPID: *LOCAL.db2ab7.080221131118
    FUNCTION: DB2 UDB, base sys utilities, sqle_remap_errors, probe:100
    MESSAGE : ZRC 0x800201a5 remapped to SQLCODE -1051
    2008-02-21-08.11.19.374857-300 I14177590A336      LEVEL: Severe
    PID     : 803022               TID  : 1           PROC : db2sysc 4
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, sqleSysCtrlAddNode, probe:6
    MESSAGE : ADD NODE failed with SQLCODE -1051 MESSAGE TOKEN /db2/AB7/sapdata1 in module SQLECRED
    2008-02-21-08.11.19.381604-300 I14177927A440      LEVEL: Event
    PID     : 639412               TID  : 1           PROC : db2start
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 75 bytes
    DB2NODE=4 DB2LPORT=2 /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 4 2
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9C2C : 0000 0024                                  ...$
    2008-02-21-08.11.20.255191-300 I14178368A287      LEVEL: Event
    PID     : 700804               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
    DATA #1 : String, 26 bytes
    Stop phase is in progress.
    2008-02-21-08.11.20.258575-300 I14178656A302      LEVEL: Event
    PID     : 700804               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
    DATA #1 : String, 41 bytes
    Requesting system controller termination.
    2008-02-21-08.11.20.265164-300 I14178959A403      LEVEL: Warning
    PID     : 803022               TID  : 1           PROC : db2sysc 4
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
    MESSAGE : Bringing down all db2fmp processes as part of db2stop
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFE400 : 0000 0000                                  ....
    2008-02-21-08.11.20.271570-300 I14179363A304      LEVEL: Event
    PID     : 700804               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
    DATA #1 : String, 43 bytes
    System controller termination is completed.
    2008-02-21-08.11.20.276550-300 I14179668A381      LEVEL: Event
    PID     : 700804               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
    DATA #1 : String, 24 bytes
    There is no active EDUs.
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFCEE0 : 0000 0000                                  ....
    2008-02-21-08.11.20.312260-300 I14180050A342      LEVEL: Severe
    PID     : 774176               TID  : 1           PROC : db2acd 4
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFF5A4 : FFFF FBEE                                  ....
    2008-02-21-08.11.20.474332-300 E14180393A301      LEVEL: Event
    PID     : 700804               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 004
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
    MESSAGE : ADM7514W  Database manager has stopped.
    STOP    : DB2 DBM
    2008-02-21-08.11.20.600512-300 I14180695A422      LEVEL: Event
    PID     : 671870               TID  : 1           PROC : db2start
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 57 bytes
    /db2/db2ab7/sqllib/adm/db2rstar db2profile SN ADDNODE 5 3
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9C2C : 0000 0011                                  ....
    2008-02-21-08.11.21.620771-300 E14181118A856      LEVEL: Warning
    PID     : 819454               TID  : 1           PROC : db2star2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, license manager, sqllcRequestAccess, probe:1
    MESSAGE : ADM12007E  There are "80" day(s) left in the evaluation period for
              the product "DB2 Enterprise Server Edition". For evaluation license
              terms and conditions, refer to the IBM License Acceptance and License
              Information document located in the license directory in the
              installation path of this product. If you have licensed this product,
              ensure the license key is properly registered. You can register the
              license via the License Center or db2licm command line utility. The
              license file can be obtained from your licensed product CD.
    2008-02-21-08.11.21.839933-300 E14181975A1040     LEVEL: Event
    PID     : 819454               TID  : 1           PROC : db2star2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
    MESSAGE : ADM7513W  Database manager has started.
    START   : DB2 DBM
    DATA #1 : Build Level, 152 bytes
    Instance "db2ab7" uses "64" bits and DB2 code release "SQL09012"
    with level identifier "01030107".
    Informational tokens are "DB2 v9.1.0.2", "special_17253", "U810940_17253", Fix Pack "2".
    DATA #2 : System Info, 224 bytes
    System: AIX sapaix08 3 5 00CCD7FE4C00
    CPU: total:8 online:8 Threading degree per core:2
    Physical Memory(MB): total:7744 free:5859
    Virtual  Memory(MB): total:32832 free:30936
    Swap     Memory(MB): total:25088 free:25077
    Kernel   Params: msgMaxMessageSize:4194304 msgMaxQueueSize:4194304
                     shmMax:68719476736 shmMin:1 shmIDs:131072
                     shmSegments:68719476736 semIDs:131072 semNumPerID:65535
                     semOps:1024 semMaxVal:32767 semAdjustOnExit:16384
    2008-02-21-08.11.22.860106-300 I14183016A428      LEVEL: Error
    PID     : 37336                TID  : 1           PROC : db2agent (instance) 5
    INSTANCE: db2ab7               NODE : 005
    APPHDL  : 5-7                  APPID: *LOCAL.db2ab7.080221131121
    FUNCTION: DB2 UDB, base sys utilities, sqleGetAutomaticStorageDetails, probe:111111
    DATA #1 : <preformatted>
    dataSize 752 pMemAlloc 11099bac0 sizeof(struct sqleAutoStorageCfg) 16
    2008-02-21-08.11.22.886670-300 I14183445A497      LEVEL: Error
    PID     : 37336                TID  : 1           PROC : db2agent (instance) 5
    INSTANCE: db2ab7               NODE : 005
    APPHDL  : 5-7                  APPID: *LOCAL.db2ab7.080221131121
    FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
    MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    DATA #1 : String, 17 bytes
    /db2/AB7/sapdata1
    2008-02-21-08.11.22.889226-300 I14183943A619      LEVEL: Severe
    PID     : 37336                TID  : 1           PROC : db2agent (instance) 5
    INSTANCE: db2ab7               NODE : 005
    APPHDL  : 5-7                  APPID: *LOCAL.db2ab7.080221131121
    FUNCTION: DB2 UDB, buffer pool services, sqlbInitStorageGroupFiles, probe:50
    MESSAGE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    DATA #1 : String, 46 bytes
    Error during storage group file initialization
    DATA #2 : Pointer, 8 bytes
    0x0ffffffffffed006
    DATA #3 : Pointer, 8 bytes
    0x0000000110981080
    2008-02-21-08.11.22.894826-300 I14184563A435      LEVEL: Error
    PID     : 37336                TID  : 1           PROC : db2agent (instance) 5
    INSTANCE: db2ab7               NODE : 005
    APPHDL  : 5-7                  APPID: *LOCAL.db2ab7.080221131121
    FUNCTION: DB2 UDB, base sys utilities, sqleStartDb, probe:5
    RETCODE : ZRC=0x800201A5=-2147352155=SQLB_AS_INVALID_STORAGE_PATH
              "Storage path does not exist or is inaccessible."
    2008-02-21-08.11.22.897320-300 I14184999A370      LEVEL: Warning
    PID     : 37336                TID  : 1           PROC : db2agent (instance) 5
    INSTANCE: db2ab7               NODE : 005
    APPHDL  : 5-7                  APPID: *LOCAL.db2ab7.080221131121
    FUNCTION: DB2 UDB, base sys utilities, sqle_remap_errors, probe:100
    MESSAGE : ZRC 0x800201a5 remapped to SQLCODE -1051
    2008-02-21-08.11.22.913142-300 I14185370A336      LEVEL: Severe
    PID     : 758092               TID  : 1           PROC : db2sysc 5
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, sqleSysCtrlAddNode, probe:6
    MESSAGE : ADD NODE failed with SQLCODE -1051 MESSAGE TOKEN /db2/AB7/sapdata1 in module SQLECRED
    2008-02-21-08.11.22.918953-300 I14185707A440      LEVEL: Event
    PID     : 671870               TID  : 1           PROC : db2start
    INSTANCE: db2ab7               NODE : 000
    FUNCTION: DB2 UDB, base sys utilities, sqleIssueStartStop, probe:1100
    DATA #1 : String, 75 bytes
    DB2NODE=5 DB2LPORT=3 /db2/db2ab7/sqllib/adm/db2rstop db2profile NODEACT 5 3
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFF9C2C : 0000 0024                                  ...$
    2008-02-21-08.11.23.793386-300 I14186148A287      LEVEL: Event
    PID     : 823654               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:240
    DATA #1 : String, 26 bytes
    Stop phase is in progress.
    2008-02-21-08.11.23.796267-300 I14186436A302      LEVEL: Event
    PID     : 823654               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:250
    DATA #1 : String, 41 bytes
    Requesting system controller termination.
    2008-02-21-08.11.23.802154-300 I14186739A403      LEVEL: Warning
    PID     : 758092               TID  : 1           PROC : db2sysc 5
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
    MESSAGE : Bringing down all db2fmp processes as part of db2stop
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFE400 : 0000 0000                                  ....
    2008-02-21-08.11.23.808100-300 I14187143A304      LEVEL: Event
    PID     : 823654               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:260
    DATA #1 : String, 43 bytes
    System controller termination is completed.
    2008-02-21-08.11.23.812951-300 I14187448A381      LEVEL: Event
    PID     : 823654               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:280
    DATA #1 : String, 24 bytes
    There is no active EDUs.
    DATA #2 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFCEE0 : 0000 0000                                  ....
    2008-02-21-08.11.23.882148-300 I14187830A342      LEVEL: Severe
    PID     : 684418               TID  : 1           PROC : db2acd 5
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpOneTimeInit, probe:100
    DATA #1 : Hexdump, 4 bytes
    0x0FFFFFFFFFFFF5A4 : FFFF FBEE                                  ....
    2008-02-21-08.11.24.008936-300 E14188173A301      LEVEL: Event
    PID     : 823654               TID  : 1           PROC : db2stop2
    INSTANCE: db2ab7               NODE : 005
    FUNCTION: DB2 UDB, base sys utilities, DB2StopMain, probe:911
    MESSAGE : ADM7514W  Database manager has stopped.
    STOP    : DB2 DBM
    2008-02-21-08.41.01.094426-300 I14188475A371      LEVEL: Warning
    PID     : 741576               TID  : 1           PROC : db2bp
    INSTANCE: db2ab7               NODE : 002
    FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
    RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
              "SQLCA has been built and saved in component specific control block."
    2008-02-21-08.41.01.109657-300 I14188847A371      LEVEL: Warning
    PID     : 741576               TID  : 1           PROC : db2bp
    INSTANCE: db2ab7               NODE : 002
    FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
    RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
              "SQLCA has been built and saved in component specific control block."
    2008-02-21-08.41.01.115152-300 I14189219A371      LEVEL: Warning
    PID     : 741576               TID  : 1           PROC : db2bp
    INSTANCE: db2ab7               NODE : 002
    FUNCTION: DB2 UDB, Connection Manager, sqleUCappImpConnect, probe:150
    RETCODE : ZRC=0x8005006D=-2147155859=SQLE_CA_BUILT
              "SQLCA has been built and saved in component specific control block."

  • How to do Physical inventory process in Warehouse

    Hi Guys
    What is the procedure for Physical inventory process in Ware house
    Kindly provide step by step procedue

    Hi
    Please go with following transaction
    MI01>Create physical inventory document>Enter Document Date>Planned count date>Plant Code>Storage Location>Click on Enter button>you will get the separate screen>Enter material code>and click on SAVE button (Ctrl+S)>you will get Physical inventory document number. (MI02-Use for delete)
    (After getting Physical inventory document number you go with MIO4)
    MI04>click on enter button>you will get "Enter inventory count screen>Enter Phys. inventory doc.no>Fiscal year>Count date>click on enter button>you will get separate screen>Enter physical qty>and click on save button ((Ctrl+S)>you will get massage from the SAPu201D Count entered for phys. inv. doc. 100000112"
    (After completed above transaction you please go with MI07)
    MI07>you will get Post inv.differences: initial screen>Enter Phys. inventory doc.> Fiscal year> Posting date>click on enter button>you will get separate screen with deference qty>click save button (Ctrl+S)> you will get document number generated from the system (Diffs in phys. inv. doc. 100000112 posted with m. doc. 4900001246)
    Physical Inventory:
    Physical Inventory is a business process in which physical stock is matched with book (system) stock. It is legal requirement to carry out physical inventory at least once in a year.
    Physical inventory can be carried out both for a companyu2019s own stock (Unrestricted, Quality, Blocked Stock) and for special stocks (Customer Consignment stock, Vendor consignment stock from vendor, Returnable packaging). This inventory is carried out saperately for both type of stocks.
    Physical Inventory Processes:
    Several inventory processes available for physical inventory which includes as follow:
    1. Periodic Physical Inventory
    o All stocks of the company are physically counted on the balance sheet key date
    o Every material must be counted
    o Entire warehouse must be blocked for material movements during count.
    2. Continuous Physical Inventory
    o Stocks are counted continuously during the entire fiscal year.
    o It is important to ensure that every material is physically counted at least once during the year.
    3. Cycle Counting
    o In this method of physical inventory, inventory is counted at regular intervals within a fiscal year.
    o These intervals (or cycles) depend on the cycle counting indicator set for the material in Material Master record as CC indicator in plant view data.
    o With this Cycle Counting Method of Physical Inventory allows fast-moving items to be counted more frequently than slow-moving items.
    4. Inventory Sampling
    o Randomly selected stocks of the company are physically counted on the balance sheet key date.
    o If found not much variance between the counted stock and the book book stock, it is presumed that the book inventory balances for the other stocks are correct.
    Physical Inventory Process Cycle Flow
    1. Creation of physical inventory document
    - Physical inventory document(s) is created individually or using the batch program, click for more information
    - The transaction codes for creation physical inventory are as follow
    Individual Inventory documentation creation
    MI01 - Individual physical inventory creation
    MIS1 - Inventory Sampling document creation
    MICN - Cycle count inventory document creation
    Collective Inventory document creation
    MI31 - Own stock without special stock
    MIK1 - Vendor consignment
    MIQ1 - Project stock
    MIM1 - Returnable Transpiration material
    MIW1 - Customer Consignment stock
    MIV1 - Returnable material with customer
    MIO1 - Material provided to Vendor (Subcontracting material)
    2. Print physical inventory document
    - Physical Inventory document can be printed based on the physical inventory document status and or item status
    - Transaction code MI21 is used to print the inventory document where print default value can be populated
    3. Count the physical stock
    - Based on the inventory document printout, the warehouse person will check the stock of material physically and note that on print out. This is completely physical process.
    4. Enter count in system
    - On completion of physical count, the count result is needs to be entered in the system. This can be with reference (using Tcode MI04) or without reference (using Tcode MI04) to the physical inventory document.
    - If count quantity for that material is ZERO then select ZC (zero count) column instead of putting 0 in qty field. If 0 is used for zero count then systm will consider that as "not counted"
    5. Analyze difference
    - Once count is posted in the system, difference analysis can be carried out using transaction MI20
    - The output gives information based on the input criteria i.e. physical inventory document, plant, material etc.
    - The output gives information about the book quantity, Counted quantity, difference in quantity and value.
    - From this output list, you can carry out further process ie initiate recount, change count quantity, post difference
    6. Initiate recount and follow the steps 3,4,5
    - If found unacceptable difference, recount is initiated using directly from difference analysis list (transaction code MI20) or using transaction code MI11.
    - New inventory document will be created for selected items or for entire document
    - The original document items will be deactivated once recount is initiated so original document will not be available for further process.
    - On initiating recount, you need to process same as for new count document.
    7. Post the difference
    - Several options are available for posting difference
    - Post difference after count is posted using transaction code MI07
    - Posting the count and inventory differences using transaction code MI08, here you have created physical inventory but not counted so with this you can count and post difference in sinle step.
    - Entering the count without a document reference using trasnaction code MI10, with this you can create inventory document, enter the count and post difference in single step.
    some more points for posting difference
    - Posting period must be open to post inventory difference.
    - The fiscal year is set by specifying a planned count date when creating a physical inventory document.
    - Tolerence to crear difference per user group can be set in customization.
    - The system will generate material document for the difference qty and post the value to appropriate account (for valuated stock)
    - The movement type in material document will be 701 or 702 based on gain or loss of material.
    Serial Numbers in Physical Inventory
    If material is managed with serial number then it is possible to carry out physical inventory for material with serial number. There are some pre-requisite before you carry out physical inventory for serialized materials.
    - Serial number profile must be maintained in the material master.
    - the serialization procedure MMSL (maintaining goods receipt and goods issue documents) has to be assigned to serial number profile.
    - The stock check indicator in the serial number profile should be configured.
    - Maintain basic settings for the serial numbers in customization for Serial Number Profile.
    - Configure serial number management for physical inventory in the Settings for Physical Inventory step in Customizing for Inventory Management.
    Blocked Stock Returns are the stock which is return stock from Customer or the stock which can be return back to vendor. To restrict the usage of this stock mostly business do transfer posting for this mateial as BLOCKED stock
    Goto SPRO -> Sales and Distribution -> Billing -> goto Copy Control -> use Copy control Between billing doc to sales doc.
    select the line which refers to ur billing doc and Return Sales doc.
    Goto Item level and please check the Check box saying Update Doc Flow .
    This check box will keep track of Refernce qty between Billing Doc and Return Sales Doc.
    Rgds,
    Rajesh

  • Need to Block storage location through physical inventory process

    Hello My client want to Block few storage locations not through authorisation objects but using physical inventory process.
    can this be achieved through any configuration settings so that when we run physical count the SLoc blocks till the count completes & posted.or Any other method to block Sloc.
    Please guide me on this.

    Hi,
    You can use check box of "Posting block" in physical inventory document.  Posting block indicates that no goods movements involving the materials listed in the physical inventory document can be posted for the duration of a physical inventory count.The  indicator is set for the affected stocks in each case for all associated stock types and is not cancelled until the count results are posted.The blocking indicator can be set in one of two ways:                                                                               
    A.Directly upon entry of the physical inventory document (if the count is to take place immediately)         
    B.Shortly before the count (if the count is to take place later)
    Regards,
    Biju K
    Moderator message:
    Warning.
    You copy-pasted someone else's work as your own message. Please don't do it in the future.
    http://www.dfa.arkansas.gov/offices/informationServices/aasis/MM/Documents/InventoryPlanningandMonitoringManual.pdf
    Edited by: Csaba Szommer on Oct 27, 2011 8:33 PM

  • Physical Inventory Process in Material Management

    Hello All,
    I have blogged on the physical inventory process in Inventory management. This will be more helpful for the new guys in the area of SAP / Material management.
    <a href="/people/community.user/blog/2007/05/04/physical-inventory-in-material-management Inventory Process in Material Management</a>
    You are welcomed to put the comment or feedback
    Regards
    Arif Mansuri

    Hi Arif,
    I added a comment on 'distribution of usage variances' to the blog, to make people aware on that useful, but not yet very well-known feature in newer releases.
    <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d2/cb532d455611d189710000e8322d00/frameset.htm">http://help.sap.com/saphelp_erp2005/helpdata/en/d2/cb532d455611d189710000e8322d00/frameset.htm</a>
    best regards,
                   Udo

  • Relation between Inventory Process keys and movement types

    Dear All,
    Is there any way to find the relation between Inventory process keys (which is in SBIW-> Settings for Application specific data sources(PI) -->Logistics -->Settings for IBU Retail / CP --> Transaction key maintenance for SAP BW) and movement types .
    Thanks in advance...
    Regards,
    Raju

    Hi,
    Please read the note below.
    Note 353042 - Howto: Activate transaction key (PROCESSKEY)
    It has something for you ....
    The process key (0PROCESSKEY and 0BWAPPLNM) of the InfoSources has not been filled. As a result, no key figures are updated because of the update routine of the participating InfoCube and along with it no records are inserted into the InfoCube. In each update routine, the system checks the content of the PROCESSKEY. If this field has no contents, then no data is written into the InfoCube because of the IF condition in the update rules.
    Solution
    So that you can work in the above mentioned InfoSources, you MUST activate the determination of the process key. This is done with the help of Transaction MCB_ which you can find in the OLTP IMG for BW (Transaction SBIW) in your attached R/3 source system.
    Here you can choose your industry sector. 'Standard' and 'Consumer products' are for R/3 standard customers, whereas 'Retail' is intended for customers with R/3 Retail only.
    You can display the characteristics of the process key (R/3 field BWVORG, BW field 0PROCESSKEY) by using Transaction MCB0.
    If you have already set up historical data (for example for testing purposes) by using the setup transactions (Statistical Setup Programs) (for example: Purchasing: Tx OLI3BW, material movements: OLI1BW) into the provided setup tables (for example: MC02M_0SCLSETUP, MC03BF0SETUP), you unfortunately have to delete this data (Tx LBWG). After you have chosen the industry sector by using  MCB_, perform the setup again, so that the system fills a valid transaction key for each data record generated. Then load this data into your connected BW by using 'Full update' or 'Initialization of the delta process'. Check, whether the system updates data into the involved InfoCubes now.
    If all this is not successful, please see Note 315880, and set the application indicator 'BW' to active using Transaction 'BF11'.
    Hope this helps.
    Raj

  • Things to be done before Physical Inventory Process

    Hi
    Just before i do Physical Inventory process, what are the pre-requisites should I consider.
    For example, Sales order stock already alloted. And I am posting a count value less than that. I usaully get an error.
    Kindly list me such things which i should clear in the SAP system before i do PI process.
    Regards
    Maruthi Ram

    hi,
    before doing physical inventory we need to check the following
    1. check the ware house stock thru MB53.MB5B
    2. confirm whether physical inventory for the entire plant or a particular sto loc
    3. decide which process you are going to use for PI count ( either manual/batch /cycle count)
    4. if the process is cycle count check whether all the materials having CC indicator
    5. decide whether we need to block or freeze the posting
    6. decide which you are going to stop the transaction if the physical inv is blocked.
    hope this will be useful
    Regards
    Sridharan

  • Skipping of physical inventory process

    Hi,
      In each FY we carry out the physical inventory process,  but as in this year user have monitor all the stock proeprly and online monitoring is done every month, so user want to not to carry physical inventory process so is there in problem or we can skip this process for this year.
      Is there any eefect of this on system in present of future FY.
    regards,
    zafar
    Edited by: zkarnalkar on Apr 1, 2011 8:32 AM

    there is no negative effect within your SAP system if you do not perform a phyiscal inventory.
    However, a physical inventory is in many countries demanded by law. If you can attest that you have done it, even you did not use SAP for this activity, then it is okay.

  • Merge physical and logical partitions

    How do I extend my physical arch partition with an unallocated space logical partition?
    I want to add an unallocated space logical partition to a physical partition
    or better said I want to grow my existing arch physical partition with the unallocated space logical partition.
    Last edited by karlzt (2010-03-20 15:50:31)

    It is not that easy. You can resize and/or move either physical partitions or locical partitions inside the space of the (physical) "extended partition". But you cannot simply take space from a logical partion and assign it to a physical partition adjacent to the extended partition it is part of. Which means you can extend a physical partion only from free space which you can produce by a prior shrinking/moving another adjacent physical partition.
    The problem is, I currently know of no way to shrink an extended partition without losing some of the enclosed logical partition data (or even all logical partions at once). One could try, as a proper backup is advisable in any case before messing around with partitions.

  • How to build the Logical cube and physical cube

    Hi All,
    I have to build the logical cube and physical cube ,i dont have idea about this ,that means i think for that we have to do the partition for the cube
    may i correct , correct me if i wrong ,plz help me on this
    Thanks

    Hi,
    1. Firsty, logical model and physical model are the terms ,which we generally use in the context of database modelling excercise.
    2. Coming to essbase, I am not sure ,what exactly you are trying to co relate . but as you termed 'partitions'. There is one of the types in partitioning called 'Transparent Partition'. Where, you have one cube ( which has data in it) and you can have one mroe cube ( which actually has no data in it). But it can be connected to the former cube with the help of transparent partition. This way, you have 2 cubes , but only one cube has data in it.
    Sandeep Reddy Enti
    HCC
    http://hyperionconsultancy.com/

  • Logical Partition.

    Hello All,
    I have a lil knowledge about logical partition. Could you please send me some document related to logical partition?
    Where and how it can be used in BW?
    Thanks.

    Hi ,
    1.Partitioning the cube in both physical and logical way helps you to increase its performance on Queriying.
    Partitioning InfoCubes Using the Characteristic 0FISCPER (At Infocube maintainance)
    Prerequisites
    When partitioning using 0FISCPER values, values are calculated within the partitioning interval that you specified in the InfoCube maintenance. To do this, the value for 0FISCVARNT must be known at the time of partitioning; it must be set to constant.
    Procedure
    1. The InfoCube maintenance is displayed. Set the value for the 0FISCVARNT characteristic to constant. Carry out the following steps:
    a. Choose the Time Characteristics tab page.
    b. In the context menu of the dimension folder, choose Object specific InfoObject properties.
    c. Specify a constant for the characteristic 0FISCVARNT. Choose Continue.
    2. Choose Extras -->DB Performance --> Partitioning. The Determine Partitioning Conditions dialog box appears. You can now select the 0FISCPER characteristic under Slctn. Choose Continue.
    3. The Value Range (Partitioning Condition) dialog box appears. Enter the required data.
    Pls chk the below link for partioning..
    http://help.sap.com/saphelp_bw33/helpdata/en/33/dc2038aa3bcd23e10000009b38f8cf/content.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/0a/cd6e3a30aac013e10000000a114084/frameset.htm
    Re: logical Vs physical partitions ?
    Regarding Partitioning
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
    /message/4204952#4204952 [original link is broken]
    How i can partioning the  BW?
    Partioning and ETable
    What is the use of cube partition?
    Re: logical Vs physical partitions ?
    *Hope this helps*
    Regards
    CSM reddy

Maybe you are looking for