BPC Carry foward of auto adjustments (Consol)

Hi,
We are using BPC periodic model for Consolidation. Our carry forward tasks, basically carries forward the closing balance for balance shet items from the prior period to the current period. It does not carry forward any values that have datasource type "A", which is fine. I have read the consolidation configuration notes, and its states that the datasource type "A" will be carried forward when running the consolidation (auto adjustment task), it will adjust carry forward balances for prior period auto adjustments (datasource type "A")
This does not seem to be automatically happened, has anyone got any ideas? Thanks

Dear All:
I have a similar question about this automatical funcion in copying A-Type dadasource. I did see such copying of datasource with A-type in BPC 5.0 MS version, however, I had no idea why BPC does this copy automatically? Can I disable this and just copy datasource with type I and M into next year instead? Or how to explain this in terms of accounting consolidasion? Can anyone share your experience in it?Thanks in advance.
Fred Cheng

Similar Messages

US Eliminations vs Auto Adjustments

Hello Folks,
I have two set of questions relating Eliminations and Please share your valuble inputs in this regards.
Q1> How to decide whether to go for US Eliminations or Auto Adjustments Business Rules? I
My thoughts:
was under impression that US Eliminations need a seperate Elimination Entites. And also it can be done only for Entities having common parent (nothing but with in a Group) But for Auto Adjustments Elimination Entires will be captured under seperate Data Sources. And it can support Inter Group Eliminations also.
Your inputs here:
Q2>How Eliminated/Adjusted amounts of an Account will be distributed into entities much lower than Company Code when we do eliminations at Company Code level? How to capture Eliminations at lower level than Company Code(Ex, Profit center, Cost center, WBS element, Internal Order)
My thoughts:
Eliminated Values when we performed Auto Adjustments gets captured in seperate Data Source and seperate Elimination Accounts we create exclusively in BPC.(Ex IC_DIFF, IC_REC, IC_SAL, IC_REV..)
Eliminated Amounts by Account, by Company Code cannot be distributed to further lower level entities like Cost Center, WBS Element, Internal Order. Eliminated Ammount will remain in Elimination Account in that Co Code as an aggregated value with all other Loew Enties as None_LLEntity)
Ex: In an Entity ABC, there is an account 123 is holding an amount of $ 1000. This value is coming out of combnations of Account, Company Code, Cost Center. After we performed US eliminations or Auto Adjustments $ 100 got Adjusted/Eliminated and resulted with $ 900 as Consolidated Value.
If we report it by Account, Company Code,Cost Center I guess we see Eliminated value something like this.
Account, Co Code, Co Ctr, Data Src, Amount
123, ABC, CC1, INPUT_DS = 1000
IC_DIFF, ABC, CC_None, ELIM_DS = (100)
Your Inputs:??
Please correct me if Iam wrong. Highly appreciates your inputs of these 2 set of questions.
Thanks,
BIBPC

Q1: US Elimination only works when entity hierarchy is static ( which means the hierarchy does not change as time goes by), and the share of parent entity over child entity is also static (100% always). Auto Adjustment is much more powerful (supposed) to do legal consolidation.
Q2: Do you mean the Cost Center is a 'Inter Company'? Btw, It's more clear to get the answer by hands on

How do I turn off ALL auto adjustments in Camera Raw?

SUMMARY:
I am simply trying to open my images in Camera Raw (version 8.6.0.254) via Bridge CC exactly how they were shot in camera, with no auto adjustments whatsoever. I already have all of the auto boxes unchecked in the Camera Raw Preferences dialogue box under Default Image Settings. I am shooting raw on a Sony A7r.
MORE INFO:
This discussion is not being created without prior research on how to solve it. Hopefully there is a simple solution that I have overlooked and missed when looking for it.
I shoot my raw images flat on purpose. The in-camera saturation is turned down, along with a lot of the other picture profile settings in the camera.
I use Bridge CC to sort though my images and make selects. In Bridge, I have "Prefer Embedded" selected for my thumbnails in order to stop the auto processing to happen to the thumbnails there.
The problem is, as soon as I open my raw images in Camera Raw from Bridge, the auto adjustments kick in and the saturation and exposure are automatically adjusted. I can't figure out how to stop Camera Raw from making adjustments to my raw images. As stated above, all of the auto check boxes are unchecked in the Camera Raw Preferences.
When the "Command U" shortcut is pressed after an image is opened, it applies the auto settings, making it clear the Camera Raw thinks that nothing has been applied yet. Toggling between "Camera Raw Defaults" and "Image Settings" in the side drop down menu does nothing either.
Below are two screen shots. One of how the thumbnail looks in Bridge, desaturated and flat. The other is how the image opens in Camera Raw with no user adjustments what so ever. You can see how the saturation and exposure have been adjusted:
Bridge Preview - this is how the image was shot in camera.
Camera Raw - Straight after opening the file with no user adjustments. You can clearly see the dramatic auto adjustments, but all of the sliders are set to default.
I would love to get some help with this, so I can see and work on my images as they were shot. Im really hoping it is a stupid oversight on my part with an easy fix. Thanks for the help.

As was already said: the camera's interpretation of the raw data is just one interpretation, and not the same as Adobe's. Don't confuse it with "exactly how they were shot", as this doesn't apply when shooting Raw. Granted it IS the manufacturer's interpretation, but you wouldn't be shooting Raw and using Adobe Camera Raw if you thought the manufacturer was always right.
One thing nobody has mentioned is Adobe's "baseline exposure" compensation factor. Camera Raw adjusts the default preview exposure by a factor of EV based on their measurements of the camera sensor. My present camera is boosted by 0.35EV and my last camera by 0.5EV. There is a way of determining this using EXIFTOOL, but I can't remember how to do it offhand. For the last few years, I have adjusted my own Camera Raw defaults by reversing this compensation, so it more closely matches the exposure I was expecting.
EDIT: here's the procedure, if you're interested. Re: Baseline Exposure

Best practices when carry forward for audit adjustments

Dear experts,
I would like to know if someone can share his best practices when performing carry forward for audit adjustments.
We are actually doing legal consolidation for one customer and we are facing one issue.
The accounting team needs to pass audit adjustments around April-May for last year.
So from January to April / May, the opening balance must be based on December closing of prior year.
Then from May / June to December, the opening balance must be based on Audit closing of prior year.
We originally planned to create two members for December period, XXXX.DEC and XXXX.AUD
Once the accountants would know their audit closing balance, they would have to input it on the XXXX.AUD period and a business rule could compute the difference between the closing of AUD and DEC periods and store the result on an opening flow.
The opening flow hierarchy would be as follow:
F_OPETOT (Opening balance Total)
F_OPE (Opening balance from December)
F_OPEAUD (Opening balance from the difference between closing balance of Audit and December periods)
Now, assume that we are in October, but for any reason, the accountant run a carry forward for February, he is going to impact the opening balance because at this time (October), we have the audit adjustments.
How to avoid such a thing? What are the best practices in this case?
I guess it is something that you may have encounter if you did a consolidation project.
Any help will be greatly appreciated.
Thanks
Antoine Epinette

Cookman and I have been arguing about this since the paleozoic era. Here's my logic for capturing everything.
Less wear and tear on the tape and the deck.
You've got everything on the system. Can't tell you how many times a client has said "I know that there was a better take." The only way to disabuse them of this notion is to look at every take. if it's not on the system, you've got to spend more time finding the tape, and adding "wear and tear on the tape and the deck." And then there's the moment where you need to replace the audio for one word from another take. You can quickly check all the other takes (particularly if you've done a thorough job logging the material - see below)_.
Once it's on the system, you still need to log and learn the material. You can scan thru material much faster once it's captured. Jumping around the material is much easier.
There's no question that logging the material before you capture makes you learn the material in a more thorough way, but with enough selfdiscipline, you can learn the material as thoroughly once it's been captured.

Develop Mode Auto Adjustments

Hello,
When I am loading RAW files in to LR, in the Develop mode they start off as a pretty flat image (as I shot them) but then LR slowly adjusts each photos as it loads which looks like it is bumping the saturation and contrast then lowering the exposure.
What are these auto adjustments and how can I turn them off? I would rather edit my images as shot in camera, not after LR makes its own adjustments without my help.

Ryan.Polei wrote:
This doesn't happen in Bridge
The difference: Lightroom is a raw editor, Bridge is not.
So, Bridge shows you what the camera did (if unedited raw file) instead of what it would look like with Lightroom edits. And Lightroom edits have to start somewhere, and that somewhere CAN'T be the same as the jpeg, or the same as another raw editing software (they use different settings, different software, different starting point..).
Don't get me wrong: I think Adobe should have better support for displaying embedded preview / sidecar jpegs (which is what Bridge does), and have an option to detect in camera profile setting and select a "nearest fit" Lightroom profile, but none of that will change the basic "deal" - different software, different settings, different starting point...
Note: this may seem odd to you now, but it's how all proprietary raw editors work, i.e. all those except the camera manufacturer's own (or those using the camera manufacturer's raw-rendering toolkit under the hood, instead of it's own), which emulates in-camera settings pretty-much exactly - no others can interpret a custom picture style, granted some may try to start with a somewhat closer look.
To review: all proprietary raw software does the same thing: interpret raw data according to invented algorithms and settings. That's what Lightroom software does, and that's what Capture NX2 does (and that's what your camera firmware does to come up with the jpegs), but they are different software, with different algorithms, which use different settings.
So your choices are:
* shoot jpeg
* use the camera manufacturer's software to process, or
* wean yourself from custom camera styles and learn to setup Lightroom processing instead.
PS - I recommend the later. Actually, you can use a plugin to somewhat translate camera settings to Lightroom settings, but I don't recommend doing it, because it tends to prolong your dependency on camera settings, rather than wean.
My advice? - Learn to use Lightroom (and get it set up optimally for your druthers) for post-production, and forget about camera settings whilst shooting (except for exposure and focusing etc., of course). Then, delete all the custom profiles you created in your camera, for therapeutic purposes .
Rob

Camera Raw 3.7 no longer supports per slider auto adjustments

Nobody else resent this "improvement"?
Now the only way to have the image properly scaled (while not affecting everyting else by the automatic guesswork) is to have the settings in custom non-automatic default and then one has to use the Exposure slider manually with the aid of the Highlights Clipping Warning, for each and every image.
Compared to the 3.6 where this is fully automatic and works very very well.

sorry for the confusion, it is indeed shift double click and double click to change from auto to standard.
If you use your own created standard setting both automatic and standard on top of the sliders are blue colored and visible. Using auto does gray out the auto setting and using standard does gray out this option which is logical because you have to click on the highlighted option to change.
So this is the way to see in what mode you are.
underneath a copy from the original post that came with the release,
regards
Omke
Topic
Camera Raw 3.7 Now Available
Tom Hogarty - 09:36pm Feb 18, 2007 Pacific
The Photoshop Camera Raw 3.7 plug-in is now available on adobe.com.
http://www.adobe.com/products/photoshop/cameraraw.html
Important Notes Regarding Camera Raw 3.7
There are several significant changes to Camera Raw 3.7 in how it handles auto and default settings:
Applying auto settings by default is no longer controlled on a model by model basis, but instead there is a single global preference checkbox Apply auto tone adjustments that controls this adjustment for all camera models at once.
Camera Raw 3.7 no longer supports per slider auto adjustments. One Auto control at the top of the panel now sets the Exposure, Shadows, Brightness, and Contrast sliders to their auto values. The Default control at the top of the panel sets these same four sliders to their default values. The keyboard shortcut for the Auto control is CMD/CTRL-U.
The keyboard shortcut for the Default control is CMD/CTRL-R.
Double clicking on a slider to set that single slider to its default value.
Shift double clicking on a slider to set that single slider to its auto value.
Previously, default image settings could only be applied per camera model. Camera Raw 3.7 can now:
-Apply default image settings specific to a camera serial number
-Apply default image settings specific to a camera ISO setting
The additional criteria are located in the Camera Raw preferences.
The default settings (including the global auto preference) are now shared with the DNG Converter.
The DNG Converter requires OS X 10.3.9 as a minimum operating system.

Consolidation Balance Carry foward

Dear All,
After performing a balance carry foward in ECCS from 2007 to 2008. The Accumulated Surplus / Deficit FS item is comming up with a difference as a result of currency translation. Even though, the translation method is configured as historical. Please can any one let me know if I missed somthing.
Regards!

Hi,
Run...
trx. F.16 for GL accounts
(trx. FAGLGVTR if you're using NewGL)
trx. F.07 for AP/AR
Kyoko

Full Directory option on auto attendant consoles

Hi All,
I have been following the guide and there is something that isn't clear. Is the full directory setting mapped to the ldap settings on the cucm? if i have added a local user manually on cucm will this not show on the full directory of the auto-attendant console?
I have already configured the settings on server to sync contacts.
Please advise.
Thanks

Yes, all End Users (not Application Users) from CUCM should appear in the CUxAC directory provided that it meets any rules you have configured. By default it should pull everything over. This does not happen in realtime so you may need to force a sync, most commonly through a service restart.
Please remember to rate helpful responses and identify helpful or correct answers.

SEM BCS - Balance Carry Foward

Hi,
What is the prerequisites to execute task balance carry foward?
I have already create task for carry foward and assign it to task hierarky, but the task doesn't appear in the consolidation monitor.
Thanks in advance

I have solve this problem using SAP Notes : 699111
Thanks.

LR makes auto adjustments even when prefs are set not to

Using LR 5.5 on a Mac with Mavericks.
I import photos in LR then when I begin to look through them, one by one, in Library Module Loupe view, I can see the photo the way I took it (low contrast and saturation) for a second while it's "loading" then LR seems to make an adjustment. I looks like it adds a lot of contrast. I believe I have all of the auto adjustments turned off in preferences.
I took a video of it below. The change happens quickly.
http://nickdantonio.com/wp-content/uploads/2014/06/IMG_0173.mov
What is happening here and how to do fix it?
Thanks.

After viewing the movie, what I saw is what I would expect to see with LR set to the defaults.
After the image is imported, the initial view will use the JPG preview contained in the raw file, this JPG preview will have all your camera settings baked into it.. After the raw file is processed, all your camera settings are ignored and the default LR profile is applied to it. The default LR profile is the "Adobe Standard" profile, which does up the contrast and saturation.
To prevent similar discrepancies, I created a user preset that applies the "camera neutral" profile and assigned that preset as the "apply during import".

Carry Foward BPC NW

Hi experts,
I get next error in the execution of the opening balance package:
"Time is not avaiable on the legal application"
This is the Opening_balance logic:
*RUN_PROGRAM COPYOPENING,CATEGORY = %C_Category_SET%,CURRENCY = %Groups_SET%,TID_RA = %Time_SET%
*ENDRUN_PROGRAM
It is necessary the names of the fields in the logic are with the same description as in the BPC adminstrator?
Can anybody tell me where is the problem.
Thank you in advance.

David,
Yes, variables of the type %DIMNAME_SET% are special. They must start with exactly the name of a dimension and end with _SET. They return the list of members that is in the current memberset for that dimension.
See this help page for more information: [http://help.sap.com/saphelp_bpc70sp02/helpdata/en/59/f145f708724b9c86d8a65dd57d5e4f/frameset.htm]
Ethan
Edited by: Ethan Jewett on Sep 8, 2009 10:05 AM

Auto Login (Console, No Manager) [SOLVED]

I'm a noob to archlinux and the forums here, but hopefully I can become part of it!
I'm looking for a way to autologin to the console on boot, as I'll be running this computer as an SSH server for secure connections from anywhere in the world, and if I reboot it I really need it to login as root automatically. No login managers, just the lovely black console, that's what I need to auto-login. If that isn't possible... It would be a shame, but I couldn't find anything about just the console in the wiki or forums, only auto-logins for window managers and the like.
Also, if there's a way to start the SSHd after my wpa_supplicant has run on boot, I'd like your help with that too! To be specific: I figured out how to run wpa_supplicant on boot, but SSHd doesn't start automatically (I assume because when it does there's not yet a network connection), so how can I make it wait (say... 30 seconds) before starting itself, to be sure my Wifi will have authenticated by then (WPA)?
Help is much appreciated!
Ian
You're right, it works fine either way! Thanks for your help, I just though that maybe it'd need to be locally logged in to operate the SSHd, but that is false.
Last edited by suplegolas (2009-10-11 18:35:11)

It's a server, and I'd like it to auto-login after I reboot it from afar.
That's all. Security doesn't matter, as no one will have physical access to the logged in machine, that's why I disregard the security concerns of auto-login for local root.

Inexplicable Auto-Adjustments on Import

I've looked through my settings and Google, and it appears that my LR installation is set up as it should be, however, when I import an image, it applies some kind of auto-mix to the images. The images will show up for a split second as they should while loading, then when the standard size preview has been generated, it will shift to some kind of default adjustments.
I don't have any preferences that I'm aware of set to do this, so I'm not sure what's going on. Here's an example. This is how it's supposed to look:
Then when it's done loading, this is how it looks:
I know, we don't all have the same calibration, but you should be able to see some differences. The contrast is higher on the second image, the blue is a little less teal, and there even appears to be some added vignetting.
Sometimes it's not a problem, since almost everything gets some minor adjustments anyway. But in some situations, it will affect things dramatically, for example, sometimes a properly exposed image will all of a sudden become very under-exposed, presumably because it's detecting that's over-exposed, when it's not.
Can anyone give me a clear answer on why this is happening, and ideally how to fix it?

http://forums.adobe.com/thread/358016?tstart=0

LR5 and Photoshop CC-weird auto adjustments on return to LR

This pertains to the use of LR5 and Photoshop CC.
. This problem that’s plagued me since LR4 has been when I’m working with plug-ins via Photoshop (now in PSCC). The transfer from LR to PS is no problem. It’s when I save the file and bring it back into LR that things change and the image barely resembles what the image looked like when saved in PS. Back in LR the exposure gets a wild increase in exposure as well as adjustments in contrast, highlight/shadow and clipping. The Basic adjustment panel is the only panel effected. So, like Nasim, I have to go back and change everything. A funny thing about this is that the history panel does not reflect these changes, so I can’t just step back in history. Drives me absolutely NUTS!

photowhiz wrote:
I would rather not chang the auto-tone adjustment pref as it IS usable on new (original from camera) imported files. And secondly, there isn't (IMHO) any reason why I should expect such wild swings in exposure executed by the auto-adjustment, especially when this does not occur when files are originally imported - it only happens when the PS edited file is returned to LR. The plug-in I use via PS is Niks Color Efex Pro 4. While I can just as easily go directly from LR5 to my plug-in I go through PS so I can flatten the image and thereby reduce file size. This is especially important when the original file is 35+MB.
I agree that it would be better if LR did not apply auto-tone when re-importing images from Ps editing - even if configured to do so at original import time - in fact, I am surprised that this is happening.
One workaround which would give you control over when auto-tone happens and when it does not, would be to remove it from your overall LR prefs, but include it into a Develop preset which you can then call at import time (as part of your Import settings). Perhaps you are already using such a preset, and can add this option to that. Then the only situation where auto-tone will happen, is where you explicitly ask for it to happen - the selection of this preset at import time, along with the remainder of the import options, can be automated by including it in a named import preset. Perhaps have differing import presets, for different import scenarios, e.g. as to whether you want autotone or not. There's some flexibility there.
regards, RP

Auto adjustments repeatable?

OK guys..In LR, I can save adjustments that I made on one image and can apply it to all images. Is there a way in aperture 2 that I can do this as well? Basically what i am doing is auto adjusting the image with exposure, color, levels. I just want to be able to auto adjust the image with the previous adjustment that I made to the last image without hitting three different buttons. Maybe like a copy and paste. In LR, you can copy and paste to all images the same adjustment. Any way to do this in Aperture 2?

bsmith0517 wrote:
Aperture has a bit of a learning curve.
That Aperture has a bit of a learning curve seems to be one of the least-understood aspects of the program.
It's huge, complex, powerful, and comes almost completely dis-assembled. There is a lot to learn.
Again, I don't know Ap2, but if you post specific questions someone here is likely to be able to help.
Sorry to hear about your change of circumstances. Best of luck!

BPC Carry foward of auto adjustments (Consol)

Similar Messages

Maybe you are looking for