FX conversion formula [AS_IS]

Hi all,
I am having a bit of a problem with the currency conversion in a consolidation application.
I have a flow F_OPE which is the opening balance, it is the only flow marked as OPENING. In my currency conversion business rule I have defined that OPENING is converted [AS_IS] with no specified target account and flow. (According to the SAP HELP
[AS_IS]: Leave untouched a value already existing in the destination currency.
As a first step I enter data onto another flow F_ADD which is converted at the average rate from LC to KONZ ( my currency dimension is called CONSOLVIEW and KONZ is defined with CURRENCY_TYPE G and GROUP_CURRENCY EUR.). This works fine. As a second step I copy my opening balances, which copies the values in LC and KONZ from F_TOT (which includes F_ADD where I have just entered data) into the next year and onto flow F_OPE. This works absolutely fine. When I check via an EVDRE or in MS SQL I can see both values.
I then run the currency conversion (*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%',[%CATEGORY_SET%],[%ConsolView_SET%], 'GLOBAL','%SCOPETABLE%','%LOGTABLE%')).
If I then check via an EVDRE there is no converted value on F_OPE. Checking in MS SQL I can see that the original value from copying is still there, but the currency conversion has created a new entry with the same value but the opposite sign, so the total is 0.
I was expecting the system to not do anything for F_OPE on currency conversion. Was this a wrong expectation or am I doing something wrong?

found the problem, I misunderstood the use of currencies

Similar Messages

Multiple Unit of Measure (No Fix Conversion Formula)

Dear All,
Cilnet has given me requirement to book the sales document for the particualr product in unit of mesure 'Nos/PC', and the stock is maintained in Base Unit of Measure 'Qtl' (100 Kg = 1 Qtl). Price is also applicable or calculated on the basis of QTL but there is no fix conversion formula of 1 PC = How Many QTL.
Please guide me on this point.
Regards
Rahul

Hi,
I was facing the same Problem ,well for this you need to define a character and associate the same to a Class .
And Finally need to assign Combination of these to material in material master classification view.
Define Charter :
http://wiki.sdn.sap.com/wiki/display/PLM/Howtocreateacharacteristic
Assign the Char to Class :
Tcode : CL02
Under Char Tab Give the Charcter Name and Place "S" in Org. Area.
Thanks.
Edited by: C.Ankit on Mar 7, 2012 8:18 AM
Edited by: C.Ankit on Mar 7, 2012 8:18 AM

Conversion formulas from RGB to CMYK

Hi,
I've been writing a Colour swatch tool (in excel! hell yeah!) which allows me to pick a bunch of colours, generate complimentary colours from them, blend between 2 colours in a set number of steps and a whole bunch of other cool stuff, and then output this as a photoshop or illustrator swatch file.
As part of this tool I want to be able to covert the rgb values to cmyk. There is very little information on this on the web and what there is is fairly inaccurate.
For example,
RGB:50,128,128
Converts to CMYK 61,0,0,50 (%) using the formula found at easyrgb.com (this formula is the most prevalent one on the web/web forums)
Photoshop converts these RGB values as CMYK: 80,33,48,8 (%)
While these two colour values are *similar* the ones generated by the easyrgb formulas are nowhere near the photoshop values.
See? stupid useless formulas. (I am aware of the differences and overlap of the two gamuts)
Whilst I know that the conversion done in photoshop is done using ICC templates, and that often these conversions are device dependant, there must be a more realiable way of converting from one colour space to another using good old reliable cold hard maths.
Does anyone know what that might be? you guys at Adobe: I AM LOOKING AT YOU.
Hope you guys can help,
~silvery~
For reference I have included and commented the easyrgb formulas:
First: RGB -> CMY
C = 1 - ( R / 255 )
M = 1 - ( G / 255 )
Y = 1 - ( B / 255 )
Second: CMY -> CMYK
var_K = 1
Initally sets var_K as 1, although this is dependant on variables below
if ( C < var_K )   var_K = C
if ( M < var_K )   var_K = M
if ( Y < var_K )   var_K = Y
This bit finds the smallest value from the CMY range and sets this value as var_K
if ( var_K == 1 ) { //Black
    C = 0
    M = 0
    Y = 0
If var_K (the value that K is calculated from) is 1, then all the CMY values are reset to 0
else {
    C = ( C - var_K ) / ( 1 - var_K )
    M = ( M - var_K ) / ( 1 - var_K )
    Y = ( Y - var_K ) / ( 1 - var_K )
If the value of var_K is anything other than 1 then use the smallest value from the CMY range
K = var_K
The value of K as filtered out from the conditions above

Oliver,
I'm not sure what you mean by the term 'meta' color profiles, but I'll take a stab at what I "think" you are asking. There are some fairly widely accepted "standards" out there for both RGB and CMYK.
In the RGB world, for example, sRGB, Adobe RGB (and to some extent, ProPhoto RGB) have a fairly wide following. These are all ICC profiles, which nail down the boundaries of the color gamut and the definitions of any tri-stimulus combination of red, green and blue. Basically, they are matrix profiles that establish the positions of the Red, Green and Blue primaries, and these positions define the outer limits, or color gamut, of the color space. sRGB is a relatively small color space, so some viewable and printable colors get clipped (sRGB is the general internet, email standard and is widely assumed for many non-color managed appplications, printers, etc). sRGB can handle a fairly wide range of colors, but does clip some colors in brightly colored originals. It has the advantage of being the most widely adopted standard, plus the steps between colors are very close together. I use sRGB for average images, most people pictures, etc. Adobe RGB spreads the primaries further apart, so it describes a wider color gamut. Because the primaries are further apart, the steps are slightly larger from one color to the next, but marginally so. I use Adobe RGB for most of my brightly colored images that will get clipped in sRGB. Adobe RGB is also generally a good choice for images that will ultimately go to a printing press or inkjet. ProPhoto RGB pushes the primaries WAY apart, so it describes a HUGE color gamut...in fact, many of the colors that can be defined in ProPhoto fall outside human vision, and certainly monitors and printers.Due to the wide spacing of steps in ProPhoto RGB, images should be worked in in 16 bit, otherwide you may see some banding and posterization if large edits are made.
In the CMYK world, certain "standards" have been established, mainly for commercial offset printers (both web and sheetfed presses). By creating a standard, they are trying to establish the ink limit, densities, color gamut, dynamic range, gray balance, etc, of a "generic" sheet of commercial printing paper on the average well-maintained press using standard ISO inks, using good process control, mesurements, etc. By it's nature, this process has to encompass a wide cross section of presses, so it may act as a limitation on what some modern presses are capable of, but that's what standards usually do. If a good printer, with a modern press and great process control decides to sidestep the standard, they can probably extend color gamut, dynamic range, etc, but at the cost of no longer being "standardized". If commercial printers are "truly" trying to meet the standard, they will run tests, take measurements, and adjust their entire workflow so it matches the standard, within acceptable tolerances. Lots of shops "claim" to adhere to SWOP or GRACoL standards, but the majority of them don't. Standards for presses make some sense, because blending CMYK inks together (especially if they use ISO standard inks) on paper usually has a reasonably narrow range that works, though the paper makes a huge difference. (the same cannot be said for inkjets, monitors and many other processes, so they generally do not have standards). So for presses, there are standards for matte and coated papers, web presses, sheetfed presses, newsprint, etc. Each of these standards has its own ICC profile (or a family of profiles) that establishes ink limits, color gamuts, etc.
All ICC profiles have the necessary tags and data to comply with the ICC specification. One of those requirements is a "profile connection space", which is usually L*a*b* or a variant. So, an file on your computer may be tagged as an Adobe RGB file, and if you wish to prepare it for a sheetfed press using glossy stock, you could convert the file to GRACoL2006_Coated1v2.ICC (an industry standard profile for No. 1 coated stock on a sheetfed press). Since both files have the ability to "speak Lab" a translation can be made from one color space to the other. The numbers in the Adobe RGB file will be converted to L*a*b* (the universal translator), and then the L*a*b* numbers will be converted to CMYK, specifically GRACoL2006_Coated1v2.ICC. So, now you have a file in CMYK space with new numbers. It is worth noting that RGB has only three colorants to define colors, but CMYK has four. So, while in RGB there is only one way to define a specific color, in CMYK, there are many possible combinations that can generate many colors. This adds complexity to the equation. The CMY colors are called subtractive primaries, and are opposites of RGB (additive primaries). The "K" (black ink) is added for text, line art, neutrality, extra Dmax, and because the CMY inks are not pure and don't deliver a true black all by themselves. If the inks and paper were perfect, you could theoretically get away with CMY all by themselves, except for registration issues, text, line art, etc. Also, the additional "K" ink can help reduce the total ink limit, save ink, reduce costs, and improve quality.
Sorry for the book. This is not a simple subject, and we have only touched the surface.
Lou

Date Conversion- Formula

Hi All,
I have Info Object 0DOC_DATE - Data type (DATS ) Length - 8 ; in transfer rules i need to write a formula to convert the date format as MM/YYYY Instead of DD/MM/YYYY.
Please suggest to write formula in transfer rules ASAP.
Thanks

Hi,
DD/MM/YYYY is a display format, the storage is always without "/", you wanna change it to MM/YYYY, means you only wanna to display month rather than whole date, so you can use formula DATE_MONTH to get the month, and it will display as MM/YYYY automatically if you set your own data date format as DD/MM/YYYY.

Thermistor conversion formula is wrong?

There is a VI found in the DAQ>>Signal Conditioning subpalette called "Convert Thermistor Readings" (I have LabVIEW 5.1.1 and 6.0.2). There seems to be some blatant inconsistency with the thermistor formula inside.
The standard thermistor formula is 1/T = a + b(lnRt) + c(lnRt)^3. (This agrees with all the documentation I've seen, including within this VI!) However, the formula node contains a different equation:
T = 1/ (a + lnRt*(b + c*(lnRt**2)));
Note the bracket position around the 'b' and the exponent '2' vs the '3'.
What gives?

David,
Equations written in plain text are always hard to get a grip of. However, I guess the two equations you mentioned,
1/T = a + b(lnRt) + c(lnRt)^3
and
T = 1/ (a + lnRt*(b + c*(lnRt**2)))
are identical.
First invert the second eq. and multiply lnRt with c*(lnRt**2) in it. You will then get the first equation since
lnRt*c*(lnRt**2) = c(lnRt)^3.
I guess the confusion is that
lnRt**2 =(lnRt)^2 and not ln(Rt^2).
Hope this helps. /Mikael

Currency translation [AS_IS] formula on FX Simulation Category

Hi,
We are currently experiencing the following problem on currency translation, any assistance will be appreciated.
The [AS_IS] formula in the currency translation business rule , does not leave the USD amount in the FX Simulation Category (ACTSTAT) , it replaces the amount with the USD amount in the source category (ACTUAL) when currency translation package is run for ACTSTAT.
Background info:
We are running SAP BPC 10 NW EP 801 SP4
Our financial year is OCT 2013 – SEP 2014
We have two categories ACTUAL used for management reporting and ACTSTAT used for
statutory reporting
All data is entered in LC against the category ACTUAL and FX translation for ACTUAL
represent the management accounting numbers where the simulation of category
ACTSTAT on the base data provide us with the statutory translation
We have two sets of rates that are applicable for management reporting and one for
statutory reporting.
We have a problem with the rules we use for FX translation for accounts that should
be reported at historic values.
We use the formula [AS_IS] to leave group currency values unchanged when values
are carried forward from one year to the next. This is the intention of
the formula as explained in documentation
For this example we used reporting currency USD ( US Dollars)
ACTSTAT is a FX simulation category with ACTUAL as the base / source category ( No data
is loaded to LC)
We have a FX translated value closing balance for the prior year on ACTUAL
(management accounting) and ACTSTAT (statutory reporting) that are different
from each other. The rule builds the closing balance through opening
balance against historic values plus any movements at an average periodic rate.
We execute the carry forward of closing balances which transfers the closing
balance to the opening balance of the respective categories – ACTUAL and
ACTSTAT. This works beautifully
When we run the FX translation in the new year the system does not leave the
translated value unchanged in the category ACTSTAT as the formula [AS_IS] was
designed to do.
Data after carry forward is run:
Sep-13
Oct-13
Nov-13
Dec-13
Jan-14
Feb-14
Mar-14
Apr-14
May-14
Jun-14
Jul-14
Aug-14
Sep-14
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
F99 - Closing
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
F00 - Opening
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
200000 - Ordinary share capital
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
-3193.890012
Problem
The AS_IS formula retrieves the data from the ACTUAL category USD amount and
replaces the USD amount on ACTSTAT.
After
currency translation:
Sep-13
Sep-13
Oct-13
Nov-13
Dec-13
Jan-14
Feb-14
Mar-14
Apr-14
May-14
Jun-14
Jul-14
Aug-14
Sep-14
ACTUAL
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
ACTSTAT
F99 - Closing
F99 - Closing
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
USD
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
F00
200000 - Ordinary share capital
3 750.00
-3 193.89
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
3750
Thanks
Gavin

Hi Gavin,
I don't think there is a way to customise the FX business rule by category, so you would have to use a script. I would create an additional flow (say Fxx), then amend the carry forward rule to copy from F99 to F00 and to Fxx.
After you run the FX conversion you could then for ACTSTAT only copy the Fxx amount in converted currency back to F00. Essentially overwriting the amount the system took from ACTUAL again with the carried forward amount.
BR,
Arnold

BPC Netweaver version - Conversion File Formulas

BPC (Netweaver) Expert,
When creating formulas on the Data Conversion File that is called by the Transformation File, the Formulas are not working on the Netweaver Version. Does anyone have any idea what may not be set up correctly?
Thanks,
Greg Rotvold

Hello Greg,
BPC Netweaver uses somewhat different syntax for conversion formulas, and uses javascript for complex formulas, so formulas written using Visual Basic on the MS version will not work, though the basic *IF logic should work (I think I'm remembering MS conversion formulas correctly, but it's been a while). You can find the relevant Netweaver version documentation here: [http://help.sap.com/saphelp_bpc75_nw/helpdata/en/81/94a8a5febd40268d5c59b4fc31be37/frameset.htm]
If you want help specifically on the Netweaver version I suggest you ask your question in the Netweaver forum. I'm not sure what forum is most appropriate for questions about the differences between the two versions
Ethan

Spot-to-CMYK conversion: Pantone vs. ID

I know this is not a new issue, and was discussed here, but more from the point of view of the visual aspect of colors on one's screen.
I'm baffled as to the conversion of spot colors for printing purposes (sheet-fed).... My client wants me to use PMS 322c in a CMYK job, and she's been always very picky about colors and the way they print. The difference in the conversion formulas between ID and using Pantone's website -- is striking.... See how ID has a significant amount of M, yet low K, while Panton suggests ZERO M and lots of K.... So I'm asking, WHO CAN I TRUST???....

Part of the “problem” is that of how you actually represent the Pantone spot colors. Yes, Pantone provide CMYK equivalent values, but in exactly what CMYK color space? According to what I have been told by Pantone, those CMYK values are nominally SWOP.
You didn't indicate what your full workflow looks like, but the most reliable method of dealing with spot colors, whether used as real spot colors (i.e., you actually have those spot color inks at the press) or you are simulating them, is to pass through the spot color information in the PDF file exported from InDesign or at least as LAB colors otherwise. Preferably, you are using a PDF/X-4 workflow.
Bring in the swatch at follows:
The swatch will then look like:
When you export PDF, you have two choices. If you are actually printing spot color or if you don't know whether real spot color inks are available, set the Ink Manager as follows:
In this case, the RIP will use the spot color if available or if not, it will convert Pantone's more precise LAB color values specified as the “alternate color space” to the press' CMYK color space.
If you know that the press definitely won't have the spot colors, set the Ink Manager as follows:
On PDF export, all references to PANTONE 322 C will be output to the PDF with the exact LAB color values which your RIP will convert to CMYK and no references to the spot color at all.
This is the method getting precisely what Pantone defines for the spot colors and how they will look in process color.
Note that many Pantone spot colors cannot precisely be matched in process color simply because such colors are outside the gamut of whatever process CMYK color space your printing workflow supports.
- Dov

Formula to convert Hex to Decimal

Hello All,
I have "upgraded" from AppleWorks to iWork Numbers. Yes I've read all about how somethings didn't get ported over, etc. What I need is a formula to convert base 16 to base 10. Any ideas how to do this? I see that numbers has a formula editor so is it possible to make up a conversion formula? Someone done this who would like to share?
Thanks,
Dan

Dan,
Here's a brute-force solution. There may be more elegant ones out there.
DEC formula is: =IF(ISERROR(LOOKUP(MID(A2, 1, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^3+LOOKUP(MID(A2, 2, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^2+LOOKUP(MID(A2, 3, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16+LOOKUP(MID(A2, 4, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16)),"", LOOKUP(MID(A2, 1, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^3+LOOKUP(MID(A2, 2, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16^2+LOOKUP(MID(A2, 3, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16) * 16+LOOKUP(MID(A2, 4, 1), LOOKUP TBL :: A$1:A$16, LOOKUP TBL :: B$1:B$16))
Be sure to Format Col A of both tables to Text.
Regards,
Jerry

Doing mathematical formulas with numbers stored as strings

Hi Everybody.
I know I must be doing something stupid here, but I just can't see it.
I'm just trying to do a simple maths formula of one number divide by another. However, one of the numbers is stored as a string.
I have tried 'X' / Ccur ({'String'}) and even done a seperate formula that succesfully converts the string to a number and then try 'X' / ({'conversion formula'}) and still no luck.
What am I missing and can anybody help please?
Thanks
Graham

Thanks both.
Works perfectly. Didn't see the ToNumber conversion in the choices available and have not used it before.
I'll also provide better descriptions as well in the future.
Regards
Graham
Points awarded accordingley :O)

UOM Conversion in a Infoset

Hello Experts,
I try to made a Unit Conversion in a Infoset but appear one error that said me that the 0material infoobject is not in the query, but is in the query the problem is that for infoset now is INSOFETNAME_FXXX.
Is possible made a unit conversion using a infoset like infoprovider?
Can anyone help me?
Thanks in advance!!

It would be more helpful if you could list everything in your infoset.
If you really want to convert, I would do it in my update rules to the data target where I wanted the conversion to happen. An infoset is not going to be easy since you will have to use a conversion formula on your query.
Brian

BPC 7.5: FX rate for opening balance from different category

Hi,
I have three categories in my system, ACTUAL, ESTIMATE and BUDGET. When we submit ACTUAL data, we also submit a forecast for the year end period (DEC in our case). We also have currency rates for FORECAST for the DEC period.
We are now working on the budget and the opening balances (business rule) are coming from the forecast since we obviously do not yet have actuals.
This copying works fine (CATEGORY_FOR_OPE on BUDGET is set to FORECAST).
However, when we run a currency conversion, we have a problem. The opening balances are set to convert at the previous year end rate which is fine. But the system uses the BUDGET category rates whereas we want it to use the FORECAST rates. But only for the opening balances, all other flows should be converted using the BUDGET rates.
Is it possible when using the currency conversion business rule, to use the FORECAST rates from the previous year end for opening flows but BUDGET rates for all other flows?
Thanks,
Arnold

Hi Arnold,
Yes this can be done.
Basically in your FX business rule table you need to have your opening flow/acctdet to use the formula [AS_IS]. This will take the group currency value from the previous period (in your case the last period of year -1 in the FORECAST category) and enter that value in the group currency field in the current year for BUDGET.
Note - If you are doing detailed balance sheet planning and you need it to always to balance to 0, then you will also need to put a line in your business rule to take [END]-[AS_IS] to the currency translation reserve. Otherwise this [AS_IS] value in GC will mean your GC balance sheet will be out of balance.
Hope this solves your issue.
Tom.

NOTRANS is not working

Hi
Wonder whether anybody can share their experience regarding this.
According to the documentation, NOTRANS is a reserved Ratetype that you enter under the "Ratetype" property of an ACCOUNT and the consolidation engine will leave this ACCOUNT so tagged alone when doing currency translation. I take this to mean that I can enter an amount both in local currency (which is, say, USD) and translated currency (say MYR) and the translated currency amount will not be translated. This is great for ACCOUNTS that need to be translated at historical rate, or so I thought.
So I created an ACCOUNT, say, Reserves, and entered "NOTRANS" in the Ratetype property. Next, I entered 1,000 under Local Currency, switched the dimension to "MYR" and entered 2,333. After running SPRunConso, I expect the local currency and translated currency amount to remain at 1,000 and 2,333 respectively. However, the translated currency amount got zeroised instead.
Is there something I ought to be doing to make NOTRANS work?
Thank you.
Regards.

Hi Joost,
Thank you for solving the mystery of the disappearing translated currency amounts!
Since NOTRANS is out, then what should I do if I need to fix the value of a local currency amount to a specified translated currency amount i.e. translate the ACCOUNT at historical (instead of AVG or END).
Can I put "HIST" as the Ratetype of the ACCOUNT that requires translation at historical rate and in the Currency Conversion Rules Table, create a new rule saying Account Ratetype = "HIST" and Formula = "AS_IS"?
Is this the correct way to go?
Thank you.
Regards.

Error while defining alt unit of measurement in material master

All SAP gurus,
i am trying to define a alt unit of measurement in a finished material, the base unit of measurement is in MT, and the sales unit is nos. the conversion formula is 53 nos = 1kg i.e. 1MT = 53000 nos. as conversion can be done only with base unit of measurement i am giving 53000 nos = 1 MT, but system unable to calculate the conversion as it is not taking mere than 3 digit after decimal.
e.g. if 53000 nos = 1 MT
then 1 nos should be = 0.000018 MT
but system not taking this value as this value contain 6 digit after decimal
suggest me what can be the way out? with detailed steps. can i increase the post decimal value or i have to define another middle alt unit of measurement (like KG). and if that is to be done then how.
Regards
BKR

Hi,
With help of Basis team check the decimal places for u r user ID.
In t-code SU01 >>> Under Default tab
Kapil

Stock report in different of measurements.

Hi dudes,
i want to get stock of materials in 2 other UOMs along with base unit of measurement ( Base UOM which normally comes).
suppose base UOM is PC and sales unit is M2 ( sq.mtr)
and i need report in which stock should be appeared in PC, M2 and M3 also.
in report like MB51,MB5B etc, what is to done
whether we need to maintain conversion formula for M3 and PC.
i would appreciate quick response.
regards
Robert

Hi,
Base unit is the only stock keeping unit. The stock is always calculated on the basis of base UOM. Other units are Issue unit or order unit. Those are not stock keeping unit.
But in MMBE if the conversion ratio is maintained then stock can be viewed in those units also. But not at a time.
Regards
Amit PArkhi

FX conversion formula [AS_IS]

Similar Messages

Maybe you are looking for