Tnventory Management Weekly snapshot 0IC_C03

Hi,
We are trying to instal the stocks Flow, with the 0IC_C03 cube. Our Business Content (Release 703 Level 8) has the new Infosources (2LIS_03_BF_TR, 2LIS_03_BX_TR and 2LIS_03_UM_TR) and the related transformations from the Infosources to the cube. But We've realized taht there is not one of the Transformations from 2LIS_03_BF datasource to 2LIS_03_BF_TR infosource. (The othrer 2 transformations appear in our Business Content)
We are thinking to do the following: mantain the transformations for the 2LIS_03_BX and 2LIS_03_UM side, and copy from another business Content (manually, of course) the 2LIS_03_BF side. Has anybody know if it is OK?
On the other hand, we need to create a Weekly snapshot, and reviewing the document "How to... handle Inventory Management Scenarios in BW", there is described the process to make a monthly snapshot if the old flow of the 3 datasources (2LIS_03_BF, 2LIS_03_BX and 2LIS_03_UM) is built (the flow with the Transfer and Update Rules)
So, is it recomended to implement the old flow for the 3 datasources (the one with Transfer and Update Rules)? And does anybody knows how can we modify the routines in order to make it weekly, not monthly?
Thanks in advance for your help.
Best regards

Hello Angel Moro,
Were you able to implement weekly snapshot cube? If yes, Can you please email me step by step how you did it at [email protected]

Similar Messages

Manage btrfs snapshots

One of the feature that i much like about btrfs is Snapshot.
What i want to do is to create snapshots of /home every 5/15 minutes (i have to test better the impact on performance) and retain:
02 - Yearly snapshots
12 - Monthly snapshots
16 - Weekly snapshots
28 - Daily snapshots
48 - Hourly snapshots
60 - Minutely snapshots
The above scheme is indicative and i'm looking for suggestion in order to improve it.
After long google searching finally i've found a very simple but powerful bash script to manage btrfs snapshots: https://github.com/mmehnert/btrfs-snapshot-rotation
I've changed a bit the script in order to use my naming scheme
#!/bin/bash
# Parse arguments:
SOURCE=$1
TARGET=$2
SNAP=$3
COUNT=$4
QUIET=$5
# Function to display usage:
usage() {
scriptname=`/usr/bin/basename $0`
cat <<EOF
$scriptname: Take and rotate snapshots on a btrfs file system
Usage:
$scriptname source target snap_name count [-q]
source: path to make snaphost of
target: snapshot directory
snap_name: Base name for snapshots, to be appended to
date "+%F--%H-%M-%S"
count: Number of snapshots in the timestamp-@snap_name format to
keep at one time for a given snap_name.
[-q]: Be quiet.
Example for crontab:
15,30,45 * * * * root /usr/local/bin/btrfs-snapshot /home /home/__snapshots quarterly 4 -q
0 * * * * root /usr/local/bin/btrfs-snapshot /home /home/__snapshots hourly 8 -q
Example for anacrontab:
1 10 daily_snap /usr/local/bin/btrfs-snapshot /home /home/__snapshots daily 8
7 30 weekly_snap /usr/local/bin/btrfs-snapshot /home /home/__snapsnots weekly 5
@monthly 90 monthly_snap /usr/local/bin/btrfs-snapshot /home /home/__snapshots monthly 3
EOF
exit
# Basic argument checks:
if [ -z $COUNT ] ; then
echo "COUNT is not provided."
usage
fi
if [ ! -z $6 ] ; then
echo "Too many options."
usage
fi
if [ -n "$QUIET" ] && [ "x$QUIET" != "x-q" ] ; then
echo "Option 4 is either -q or empty. Given: \"$QUIET\""
usage
fi
# $max_snap is the highest number of snapshots that will be kept for $SNAP.
max_snap=$(($COUNT -1))
# $time_stamp is the date of snapshots
time_stamp=`date "+%F_%H-%M"`
# Clean up older snapshots:
for i in `ls $TARGET|sort |grep ${SNAP}|head -n -${max_snap}`; do
cmd="btrfs subvolume delete $TARGET/$i"
if [ -z $QUIET ]; then
echo $cmd
fi
$cmd >/dev/null
done
# Create new snapshot:
cmd="btrfs subvolume snapshot $SOURCE $TARGET/"${SNAP}-$time_stamp""
if [ -z $QUIET ]; then
echo $cmd
fi
$cmd >/dev/null
I use fcontab
[root@kabuky ~]# fcrontab -l
17:32:58 listing root's fcrontab
@ 5 /usr/local/bin/btrfs-snapshot /home /home/__snapshots minutely 60 -q
@ 1h /usr/local/bin/btrfs-snapshot /home /home/__snapshots hourly 48 -q
@ 1d /usr/local/bin/btrfs-snapshot /home /home/__snapshots daily 28 -q
@ 1w /usr/local/bin/btrfs-snapshot /home /home/__snapshots weekly 16 -q
@ 1m /usr/local/bin/btrfs-snapshot /home /home/__snapshots monthly 12 -q
And this is what i get
[root@kabuky ~]# ls /home/__snapshots
[root@kabuky ~]# ls -l /home/__snapshots
total 0
drwxr-xr-x 1 root root 30 Jul 15 19:00 hourly-2011-10-31_17-00
drwxr-xr-x 1 root root 30 Jul 15 19:00 hourly-2011-10-31_17-44
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-18
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-20
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-22
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-24
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-26
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-32
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-37
drwxr-xr-x 1 root root 30 Jul 15 19:00 minutely-2011-10-31_17-42

tavianator wrote:
Cool, I just wasn't sure if the "And this is what i get" was what you were expecting.
Looks good, I may take a look since I'm using btrfs. Don't confuse this for a backup though .
Sorry for confusion, my english is not very good
Yes this is not a backup.
It's a sort of parachute if you do something stupid with your files you can at any time come back

Inventory management with SnapShots

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

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

Inventory Management, New Snapshot Scenario

We are planning to implement the New Snapshot scenario for Inventory Management. This is based on the "How to...." document. As per what is shown in the document, all the 3 extractors feed into the same DSO. However, when I try to create the Update Rules for BX, I get a error that there is no key figure. However, the DSO (Standard) has the Key figures. These are cummulative. Maybe, because of that I get the error when I create update rules for BX. But then, in the document the key figures appear. How is this possible.
Has anyone tried this and has been successful. If so, I'd appreciate if you could send some tips.
Thanks

hello
can you please take a screenshot of your data model and update rules (inside) and send me to (see email in card)
It will really help me!
Alex

Last Week - This Week Snapshot

Hi,
I'm trying to produce a sales pipeline report to show comparisons from last week to this week on certain fields within the sales stage history subject area. I have got this to work for the Total Contract Value field by using the variables VALUEOF("LAST_WEEK_BEGIN_DT") and VALUEOF("CURRENT_WEEK_BEGIN_DT"), within a column formula and filtering that column by last week, then dulicating that column and filtering by this week, i.e. FILTER("Historical Sales Stage".Revenue USING (Opportunity."Close Date" >= VALUEOF("LAST_WEEK_BEGIN_DT"))). The issue I'm having is if I then want to do this for other non - metirc columns (i.e. Probability %), it doesnt allow me because you cant filter on non metric columns within a formula. So how else can I go about this please??
Regards

Hi,
Unfortunately version 1.3 does not support custom ringtones.
However, there is a workaround:
you can search and install this app on your device through the Marketplace:
https://marketplace.firefox.com/app/ringtone-picker

Demand Management Week Calendar

Dear All,
I'm putting a plan in MD61, first I need to know if there's a possible way of seeing what W21 (week 21) and WXX stand for (What's the start/end date for this week in normal days).
Second, it ALWAYS considers the begining of the week to be Monday, how can I change that to Sunday?
Please inform
Thank you
Edited by: Rafik Wassef on May 13, 2009 12:31 PM

Dear,
Please create a Planning Calendar in MD25 and assign it on the Planning cycle of Material master MRP-2 view.
While creating the Planning Calendar enter Plant and name for the calendar and press enter.
Type description and click Calculate Periods, click on Week(Week days) and select Continue rom sunday. In OMPD define date type as week.
Then in MD61 assign the planning calander under user setting.
Or else to make Sunday as first working day, use transaction SCAL, choose factory calendar and then check.
Also refer this thread,
MD61: Factory calendar in planned Indep Requirmt
Regards,
R.Brahmankar
Edited by: R Brahmankar on May 13, 2009 4:51 PM

Weekly/Monthly Snapshot Report

Hi,
I have now three cubes Daily,Weekly and Monthly cubes...
I had made copy of the daily cubes as weekly and monthly.. There is no difference as such structure wise...
But what extra i need to do to make these weekly snapshot report and monthly snapshot report..
Now all three cubes are added in multiprovider and multiprovider was used in the definition of the query..
For daily cube report though, i had simply restricted infoprovider as daily cube and designed the query..
But what about weekly and monthly snapshot reports?
as snapshot reports are basically meant for comparing time periods how i could achive the same in reporting?
What i am contemplating as follows:
1) Since these are comparing different times ( for weekly snapshot, you must have at least two different weeks of data to compare ) i guess we need to include a time chararistic 0CALWEEK for Weekly snapshot, 0CALMONTH for Monthly snapshot..
But even after including this time charactristic, how i would be comparing?
i am not clear on how to creata a snapshot report
What one has to do in the weekly and monthly cube to be able to compare the data on weekly/monthly basis?

Simran,
Weekly Snapshot means entire data has to restated against each week.
For example to check open orders status week wise, entire open orders(till end of current week) has to restate against current week. at end of the week, need to pass remaining open orders as next weeks snap shot.
In this way we will get snapshoting of open orders week wise. We can use these weeks to compare.
For weekly snapshot add week to cube, and at end of each week pass current week closing balances as next week opening balances + transactions in that Week gives snap shot of that week.
For example Check: [HOW TO HANDLE INVENTORY MANAGEMENT SCENARIOS IN BW (NW2004)|http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
Snapshot scenario.
Hope it Helps
Srini

Inventory management: non-cumulatives VS. snapshots

In the How to Handle Inventory Management Scenarios in BW, I read that (p. 2):
- Inventory management with non-cumulative key figures is better when "90 percent of all materials were moved 1 time in the month";
- Inventory management with SnapShots is better when "90 percent of all materials were moved 1 time in the month".
I think the second sentence is not correct. But what can be the right number of movements to be considered?
Thanks a lot,
Davide

Hi Ajay,
so my next question is:
Besides the time granularity needed (daily-level vs. monthly-level), is there a threshold for the number of movements, that could be used to choose one of the two models?
I mean, if materials are moved on average e.g. less than 10 times per month, the non-cumulative architecture could be best one. While if there are more than 10 times per month, the snapshot architecture could be more appealing. In this example, 10 movements per month is the threshold.
Cheers, Davide

Problems Implementing SnapShots Scenario for Stock Management

Hello All,
I am trying to configure the Inventory Management with snapshots and I am using the snapshot scenario. According to the document I have created alternative ODS ODSSNAP and infocubes to accumulate 2LIS_03_BX, 2LIS_03_BF and 2LIS_03_UM.
My problem is with the key figures ZTOTALST,ZVALSTCKV and ZVALSTCKQ.
I am facing this problem in the ODS when i try to create the update rule for 2LIS_03_BX. I have the two Characteristics Unit and Currency automatically mapped but i don´t see the key figures of the ODS. I supposed that my key figures may appear without assignment but they don´t appear.
I should have my key figures non mapped but instead I cannot see them.I tried with another standard infosource 2LIS_03_BF and I see my key figures.
I have BW 3.5 patch level 20.
Can you please let me know any ideas?
Thanks
TK

OK, non cumulative are not stored in your provider but calculated on the fly:
NonCum = InFlow - OutFlow.
then you have to work with your good receipts and goods issue flow key figures....
For your scenario, as far as I understood you just need to see a "snapshot" (latest know stock values) you just need to update your receipts and issues with summation in your ODS; your stock will then be calculated.
Usually a "snapshot" scenario means that you want to store your stock at the end of each month for example; in this case you need to use cumulatives with exception aggregation "LAST" on your time period so that the stocks aren't summarized over time. This way you update your cumulative Stk KF is updated with goods receipts - good issues. Also remind that in this scenario you'll have to load the previous month stock into the next
Stock July = Stock June + Receipts July - Issues July.
As you realize, it can get quite complex...
Please precise your requirement and we'll help you further since I am doing all kind of scenario re stocks...
hope this helps...
Olivier.

Schedule Snapshots Rotation

Hello,
I have two Hyper-V servers running Replica feature, it is working great, but it only protects me from hardware failure.
Now I want to have snapshots enabled for quick rollbacks (and full backups for more restoring options, but that's for later).
I found this script which describes how to schedule a snapshot each 7 days: https://support.managed.com/kb/a1872/how-to-automatically-rotate-hyperv-snapshots.aspx
From what I understand, it will rotate the Snapshot each 7 days, creating a new one and deleting the previous... but I am looking for something more complicated.
What I really wanted was having a snapshot each 7 days, just like that example, but keeping the last two weeks, and also have a new snapshot daily. So I would always have three separate snapshots instances (2 weeks old, 1 week old and "yesterday").
If I notice performance degradation, I will only keep 2 snapshots (1 week and 1 day old).
Does anyone know how to do it?
Thanks,
Rafael

Hi Brian,
Thank you very much for your answer.
Well, I am not thinking of snapshots as a backup. I am thinking about a fast way to do a rollback in case of need.
Recently I had a problem with a server where the last backup I had was 5 days before, and recover was not very fast (very fast I mean a few minutes, if that much). Snapshots are a way to cover me from that kind of problem.
Because of the quantity of servers I run, most of them have automatic updates. I had a case not long ago that one update messed up the "fonts" on a windows server 2003. I also have some servers where more then one people have access... once a employee
deleted by accident something he was not supposed to.
Beyond having snapshots, I will also have proper backup. Maybe having 2 weeks of snapshots is a little too much. But I think having at least one day and a week always recoverable can save me some headaches.
So... my question is how to make a script to always have a one week old and a one day old snapshot. The script I have for a week is:
$Days = 7 #change this value to determine the number of days to rotate.
$VMs = Get-VM
foreach($VM in $VMs){
$Snapshots = Get-VMSnapshot $VM
foreach($Snapshot in $Snapshots){
if ($snapshot.CreationTime.AddDays($Days) -lt (get-date)){
Remove-VMSnapshot $Snapshot
Checkpoint-VM $VM
How to add a daily snapshot without overwriting the weekly snapshots?

How to handle inventory management scenario

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

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

Inventory Management DSO Capabilities

Hi All,
In a typical inventory management scenario (for 0IC_C03), we have inventory datasources (BF, BX and UM) directly feeding the cube.
Due to system architecture we now have to place data coming from these datasources into a DSO first and then feed the inventory cube.
Please guide me as to what should be the key combination for the DSOu2019s of these datasources (i.e. for BX, BF and UM) .
Regards
Anshul

Hey!
Search in OSS for the following note:
Note 581778 - ODS capability of extractors from Inventory Management
This will help you for this what you need to know.
I think for BX is a DSO not necessary because you use it just for the initial load.
Best regards,
Peter

Time Machine Snapshots are taking too much HDD space

It has taken so far over 155 GB as you can see on this link.
http://i1102.photobucket.com/albums/g445/comics_addict/ScreenShot2011-11-22at112 226PM.png
It appears under "Other" due to me disabling the snapshots on the terminal but unlike I read it still hasn't erase the items from memory.
Any help?
Thanks for your time.

Local snapshots are periodically condensed into daily or weekly snapshots to minimize the space used on your disk. If your disk is low on space, Time Machine stops creating new snapshots, and some or all existing snapshots may be removed to make space available for applications to use. If sufficient disk space becomes available again, Time Machine resumes creating local snapshots. This means your disk will have the same amount of available space as it would if Time Machine were not enabled.
OS X Lion: About Time Machine's "local snapshots" on portable Macs
Disk Space considerations:
Local snapshots require space on your internal HD (and any other disk/partition that Time Machine is backing-up). Time Machine will, however, delete some or all as necessary if it gets too full. The exact criteria are not documented, but appears to vary depending on the size of the volume. On a very small volume (under about 50 GB), it may be as little as 75%; on larger volumes (1 TB or more) it may be as much as 90%. This is doneindependently for each disk/partition. Time Machine does not send any messages when it deletes snapshots.
Pondini's excellent blog on Time Machine: 30: what are local snapshots?

Local Time Machine snapshots in Mountain Lion on Macbook Pr

Does Time Machine take local snapshots in Mountain Lion? When I enter Time Machine on my Macbook Pro, it shows only backups made with my external hard drive. The timeline appears white. Where do I find the local (internal) backups?

Yes, Time Machine takes local snapshots in Mountain Lion. To see them, try disconnecting your external drive and then entering Time Machine.
The following bit is from Mac Help.
charlie
About local snapshots
If you have a portable computer, Time Machine keeps a copy of everything on your computer’s internal disk, and saves hourly “snapshots” of files that have changed. Because Time Machine stores the snapshots on your computer’s internal drive, they are called “local snapshots” to distinguish them from backups stored on an external backup drive. Time Machine saves local snapshots on portable computers only, and not on desktop computers.
Local snapshots are periodically thinned to save disk space. A single daily snapshot is saved for every 24 hours, counting from the time you start or restart your computer. Similarly, a single weekly snapshot is saved for one week.
If disk space becomes very low, additional thinning is done:
When the disk’s free space is less than 20% of its total available space, Time Machine removes snapshots starting with the oldest one first, and working toward the newest one. If enough space becomes free so that the disk’s free space is more than 20% of its total available space, Time Machine stops removing snapshots.
If the disk’s free space falls below 10% of its total available space, or is less than 5 GB, the task of removing snapshots will be given high priority on your Mac. When free space is between 10%–20% of total available space, removal continues at a lower priority.
If Time Machine is unable to free up enough space to get above the 10% or 5 GB threshold, Time Machine removes all snapshots except the current one, and stops creating new snapshots. Once free space rises above the 10% / 5 GB threshold, a new snapshot is created, and the previous one is removed.
If you want Time Machine to stop saving local snapshots, open Time Machine preferences and slide the switch to Off. Snapshots will resume when you turn Time Machine back on.

Snapshot copy of file is locked by another process?

Hey guys,
 
 
 
I've never run into this before, but I am having an issue where running robocopy to restore a folder and it's contents from the weekly snapshot I get errors on several files that they are currently in use?
 
The syntax: robocopy Y:\~snapshot\weekly.2015-08-02_0015\Foldername Y:\Foldername-RESTORED /MIR /Z
 
The error: Error 32 <0x00000020> filepath The process cannot access the file because it is being used by another process.
 
As a snapshot copy is read-only and there are no other processes currently accessing the files (closed all explorer sessions, unmounted and remounted cifs share, and even rebooted host) to ensure there were no processes using this snapshot and still several files are failing to copy.
 
if you cancel the process and run it again immediately the last file you hung on, will usually copy just fine, but another one shortly thereafter will hang.
 
I used the SysInternals Process Explorer program to see if I could see what had those files locked and could find nothing. I check for vscan, and for volume clones based on that snapshot and again found nothing.
 
Just curious if anybody else had seen this behavior?
 
Data Ontap 8.2.3 (CDOT)

Guess may be when you are performing ROBOCOPY at that time snapmirror or snapvault transfer is going on . I would like you check that. Even Dirty snapshot create those problem RegardsRaghuveer(wellsfargo)

Tnventory Management Weekly snapshot 0IC_C03

Similar Messages

Maybe you are looking for