Recognizing Changes in System_Constants.lgl

I've made changes in the System_Constants.lgl file whereby I've changed the:
*FUNCTION ACCOUNTDIM=ACCOUNT_FS (from the default ACCOUNT)
However when I try to load DATA via the IMPORT Package, the error message I receive is: Invalid dimension ACCOUNT in lookup.
What we're seeing is that any changes in the System_Constraint isn't being reflected (this has happened when we change the Entity Dimension to something else). Our default "Finance" Application is able to load data however, so the issue is for any dimensions we've created and renamed as ENTITY or ACCOUNT, the error seems to occur.
We've done a full process as well, and still receive this error.
Thanks,
Pras

Pras,
After you change the system contants file, you have to recompile all the logic in both the logic file (like fxtrans) and default (if the logic is called from default). That should fix the issue. If it does not, then copy the fx_restatement package in the edata --> and run the logic file individually - that will tell you whether or not the logic is fixed or if there is other logic that is causing the problem. Let me know if you need any other help.
Thanks,
Bart

Similar Messages

Recognizing change in client IP during an ARD session ?

Let's assume I work on a client computer over the Internet (WAN) by using its hostname (e.g. server1.domain.tld). The computer is not within our LAN and can be only accessed via its hostname (respectively its IP).
In the case the IP address of the remote computer changes, does Remote Desktop recognize this and keeps the current session alive - or do I need to re-connect by using the new IP address of the client ?
I'm not sure about, because once the IP changes, a connection done via client's hostname should interrupt, because the DNS information still points to the old IP at this time.
I got told that ARD 3.x remembers the MAC address and rebuilds the connection, but I'm not sure if this would be only an option when having the client within the LAN and/or connecting by IP (so ARD does not need to ask a DNS server for the IP of the host/domainname).
Since I found no information in ARD's user manual, I would be interested to hear your experiences.

Thanks for your reply. As long as a reconnect is done when the IP changes, anything would be well.
I just be a bit concerned that the DNS records of the hostname/domainname still points to the old IP (the DNS servers may simply take some hours to update DNS).

Changes in TR from 4.7 to ECC 6.0

Hi All,
Our client have just upgraded from 4.7 to ECC 6.0 and when processing securities, according to them they didn't need to go through TBB1 before doing TPM10 back in 4.7. In summary this is their process:
4.7 (OLD) --> FWZZ (Create contract master data) --> TS01 (create transaction) --> TS04 (settle transaction) --> TPM10 (post transaction) --> TPM18 (fix amortization).
When they tried doing the above steps in ECC 6.0, they can not proceed with TPM10 because the system can not find the specific transactions. I've researched about it and I've read in SAP HELP that you would have to do TBB1 first before doing TPM10. Is this a documented/recognized change for the Treasury module when upgrading from 4.7 to ECC 6.0? Is there any SAP note or document that could enumerate normal changes for the Treasury module and could explain the reason for such change? Please assist us on this as I am not so familiar with the Treasury processes. Thank you!

Hi,
Correct process flow is:
1. FTR_CREATE (TS01) -> Create securities transaction
2. FTR_EDIT (TS04) -> Settle transaction
3. TBB1 -> Post transaction to FI
In case, you need to reverse the above transaction which is already posting to FI, then follow the following steps:
4. FTR_EDIT (TS07) -> Reverse Settlement for the transaction
5. TPM10 -> Reverse accounting entries posted to FI in step 3.
5. FTR_EDIT (TS07) -> Reverse Contract completely.
Now if you accounting entries are incorrect in step 3 or 5 above, then you would need to look at account determination. You may just need to set your GL accounts right in the account determination.
Update type SE1000 posts purchase transactions. Check the posting specification assigned to it -> debit & credit account symbols within posting specification and -> the GL a/cs assigned to these symbols along with combination of valuation area & AAR.
Thanks and regards,
Abhinav Sethi

Change of IP in RAC

Hi,
Thanx a lot for this discussion forms as i am getting the response very quickly.
What happens in RAC environment if i change my instances public IP /virtual IP.
Does it affects ????
If it doesn't what and where are the changes have to be made??
Thank you.

The following will have to be considered:
>
- You must ensure to your SAN storage vendor that the IP change will not affect the RAC servers. On my client's case, they moved from 192.xxx.xxx to 172.xxx.xxx segment. We consulted to the EMC engineer if there will be problems with the Navisphere detecting the new IP (172.xxx.xxx) of the RAC servers, luckily after the restart, the LUNs were still detected and the new IP was recognized
- Changing the Public and VIP will entail updating the Net Services for the new IPs
- Database links going to the RAC servers have to be modified to reflect the new IPs
- NFS mount points on RAC servers should be noted, edit the /etc/exports on the source servers to reflect the new IPs
- DNS entries on the 172.xxx.xxx have to be created
- DNS entries on the 192.xxx.xxx have to be deleted
- If you are using OCFS2, you to edit the /etc/ocfs2/cluster.conf to reflect the new IPs
- Also, you must be with your network engineer during the activity. If ever you encounter some route problems, he could easily solve it.
>
Will there be a data center movement? Or just physical rewiring?
There are metalink notes that will help you on this activity:
>
How to Change Interconnect/Public Interface IP or Subnet in Oracle Clusterware
     Doc ID:      283684.1
Modifying the VIP or VIP Hostname of a 10g or 11g Oracle Clusterware Node
     Doc ID:      276434.1
Considerations when Changing the Database Server Name or IP
     Doc ID:      734559.1
Preparing For Changing the IP Addresses Of Oracle Database Servers
     Doc ID:      363609.1
The Sqlnet Files That Need To Be Changed/Checked During Ip Address Change Of Database Server
     Doc ID:      274476.1
>
- Karl Arao
http://karlarao.wordpress.com

Printing a PO change from me22n for z-field change from subscreen

I have incorporated a subscreen in PO me22n.Now I want to automatically trigger PO printing for any change done to this ztable-zfield on subscreen!
I tried setting the customizing option where we can add our own print relevent field to trigger printing for PO.I added here my ztable-zfield .When I change this field via PO subscreen,it tries to trigger for ZNEU (my output) and fails with RED! stating no print relevant changes made to PO!
I also tried triggering for a EKPO-Zfield by first setting the customizing and then triggering printing for a changed field...
ANY LIGHT on this OR ANY KNOWN OSS HELP appreciated!Regards,Shankar

Hi Jeet,
I want the PO to automatically trigger the ZNEU output just like it successfully does for create mode.not from ME9F!
In MM customizing > table T166C is where we add print- relevant fields and table names -->whose value changes for any PO should trigger an output automatically.Apparently this is not recognizing change to a ztable-zfield or even ekpo-zfield from a PO.
Now this field for my client's POs happens to be in my custom subscreen a ztable-zfield for line item in PO.
Yes the messages,further data,communication method are all set proper.
Since you mentioned,I also checked NAST and it has entry in NAST...that is why I am getting RED radio in messages..it is apparently trying to output and then it finds this field change for the PO is not print relevent field change!
any light on how to trigger an output manually programmatically from userexit or something when ever this zfield in a PO is changed using Me22n ?

.LGF Modification Error

Hi,
I am using BPC Version 7.0.104 MS
OS: 2003 server edition
I have created one application "Consolidate_1" using new dimension in it "C_Acct" , "C_Datasrc" ,"C_FLOW" and "C_Category"
RATE1 application has been created and successfully imported.
(Validation of Transformation file, Package execution and script logic validated)
Well i am facing problem in the script logic for the consoildate_1 application
I have modified my SYSTEM_CONSTANT.LGF file (from adminapp/consolidate_1) as follows:
// application constants //
*FUNCTION CATEGORYDIM=C_CATEGORY
*FUNCTION TIMEDIM=TIME
*FUNCTION CURRENCYDIM=GROUPS
*FUNCTION ENTITYDIM=ENTITY
*FUNCTION ACCOUNTDIM=C_ACCT
*FUNCTION INTCODIM=INTCO
*FUNCTION DATASRCDIM=C_DATASRC //
This part is needed when a RATE cube
// is associated to the application //
(FX = single or multi currency) //
*FUNCTION THISAPP=CONSOLIDATE_1 -- My consolidation application
*FUNCTION RATEAPP=RATE1 ---New Rate Application consisting of in-built dimension.
*FUNCTION RATEENTITYDIM=RATESRC
*FUNCTION RATEACCOUNTDIM=RATE
*FUNCTION INPUTCURRENCYDIM=INPUTCURRENCY
*FUNCTION RATEENTITYMBR=RATEINPUT
*FUNCTION RATESRCCALCMBR=RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
The modified FXTRANS.LGF (In the application) looks like :
//============================================= //
Currency translation logic //
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB SYSTEM_LIBRARY.LGL
*SYSLIB MULTICURRENCYTRANS.LGL
*RUN_PROGRAM
CURR_CONVERSION CATEGORY=%C_CATEGORY_SET%
CURRENCY=%INPUTCURRENCY_SET%
TID_RA=%TIME_SET%
OTHER=ENTITY=%ENTITY_SET%
RATEENTITY=Global
*ENDRUN_PROGRAM
*COMMIT
I am facing 2 situations where I am getting errors:
1. While executing the package - Error --> Mapping error; the dimension does not exist in the application. CATEGORY
2. While validating the FXtrans.lgf/Default.lgf - Error --> "Invalid line in logic section : category = %C_categoy_set% invalid line in logic section"
I have referred the threads mentioned below but still unable to resolve this issue as this is the first time I am working on SAP BPC so I don't know much about this tool!
Invalid Dimension Entity in lookup
Re: Invalid Dimension SALESACCOUNT in Lookup rule
Can somebody show me the right path..
Thanks
SG

Hi Nilanjan,
yesterday i created new appset, application and new customized dimensions also.
I have replaced RateSrc with R_Entity every where (System constant, in Default.lgf, Datafile and in Transformation file)
Ratesrc -Entity - RptCurrency ( Dimension name- Dim Typ- Ref Dimension)
R_Entity- Entity -InputCurrency ( Dimension name- Dim Typ- Ref Dimension)
The why this RateSrc dimension error is coming up..
My Questions:
1. Do i need to change the default.xls of rate1 application also?
2. Do i need to change the default.xls of other related application like finance which are referred by rate1 application?
3. I have copied system_constant.lgl to my rate application from finance application but scrap this stuff n removed the file from rate1 application and created consolidate1 application and now the logic looks like below.
*INCLUDE ..\consolidate1\system_constants.lgl
*SELECT(%RATEMBRS%,[ID],RATEACCOUNTDIM,"CALC='N'")
*XDIM_MEMBERSET RATEACCOUNTDIM=%RATEMBRS%
*SELECT(%CURRMBRS%,[ID],INPUTCURRENCYDIM,"CALC='N'")
*XDIM_MEMBERSET INPUTCURRENCYDIM=%CURRMBRS%
*XDIM_MEMBER RATEENTITYDIM=RATEINPUT
*WHEN INPUTCURRENCY.MD
*IS "D"
*REC(EXPRESSION=ROUND(1/%VALUE%,6),RATEENTITYDIM="RATECALC")
*ELSE
*REC(R_Entity="RATECALC")
*ENDWHEN
*CLEAR_DESTINATION
*DESTINATION R_Entity=RATECALC
also the system_constant.lgl look like:
// application constants //
*FUNCTION CATEGORYDIM=C_CATEGORY
*FUNCTION TIMEDIM=TIME
*FUNCTION CURRENCYDIM=INPUTCURRENCY
*FUNCTION ENTITYDIM=R_ENTITY
*FUNCTION ACCOUNTDIM=R_ACCT
This part is needed when a RATE cube
// is associated to the application //
(FX = single or multi currency) //
*FUNCTION THISAPP=CONSOLIDATE1 -- My consolidation application
*FUNCTION RATEAPP=RATE1 ---New Rate Application consisting of in-built dimension.
*FUNCTION RATEENTITYDIM=R_ENTITY
*FUNCTION RATEACCOUNTDIM=R_ACCT
*FUNCTION INPUTCURRENCYDIM=INPUTCURRENCY
*FUNCTION RATEENTITYMBR=RATEINPUT
*FUNCTION RATESRCCALCMBR=RATECALC
*FUNCTION AVGRATEID=AVG
*FUNCTION ENDRATEID=END
Can you make out where i am missing??
Thanks for the help till now..
Saurabh

Error Invalid object name 'mbrGROUPS'.

I'm attempting to validate the standard elimination logic for Intercompany eliminations. I'm getting the following error when I try to validate:
Invalid object name 'mbrGROUPS'. in:select [ID] from mbrGROUPS where [REPORTING] = 'Y'
Below is my logic for this. I'm trying to use this logic for a Legal consolidations application.
//=============================================
// Default Intercompany Eliminations
//=============================================
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB ICELIMWITHCURR.LGL
//=============================================
// Elimination logic for three organization(H1, H2, H3)
//=============================================
INITIALIZE_ELIM()
ELIMINATE_ORG(H1)
ELIMINATE_ORG(H2)
ELIMINATE_ORG(H3)
*COMMIT

I fixed this myself. I forgot to change the "CURRENCYDIM" in the ICElimWithCurr file to my Reporting Currency, which in this case is "ConsolView"
Logic can be so humbling sometimes.

How to create a Cash Flow Statement?

Dear all:
I am trying to create a Cash Flow Statement, and my approach is to use Dimension formula to calculate on the fly. Is my approach the best practice, or should I use script logic instead?
Based on my understanding, if I use Dimension formula, I won't need to create new set Dim members to store the calculated values (such as Increase (Decrease) in A/R = A/R this month - A/R last month). However, I am having problem constructing the formula in FORMULAH1 column.
Given above A/R example, I tried to use [NetAR] - ([NetAR],[Time].[PRIOR]) to get the difference in value between this month and last month, but I received error message saying that "The hierarchy '[PRIOR]' was not found in the cube when the string, [TIME].[PRIOR], was parsed". Is there anyway to retrieve Next or Prior months data in MDX?
If my approach is not correct, please advise correct way.
P.S. I have searched the forum and someone mentioned using Account Transformation logic. I looked up Administration Help file but didn't grasp the concept of Account Transformation logic. Can someone explain in detail for me?
Thank you for your help!
Brian

Try not to use DIMENSION LOGIC, unless it is really simple.
This is a set of ideas from the BPC 5 demo that I often use for Cash Flow Statements. This may be modified for your use, but the idea is consistent. Just remember to prep the customer to understand that 1 time charges and 1 off changes to CF statements are more often added and managed manually since it they would always impact a CF report.
Logic from version 5 BPC Demo- Finance App
*INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB CONSOLIDATION_LIBRARY.LGL
// MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
RUNSUMMARIZE(ThisApp,CF_SUMM,%CATEGORY_SET%,%LC_RPT_CURR%)
//CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
*SELECT(%FROM_ACCOUNT%, "[ID]", "ACCOUNT", "[CF_TO_ACCT] <> ''")
*XDIM_MEMBERSET ACCOUNT = %FROM_ACCOUNT%
*XDIM_ADDMEMBERSET TIME = PRIOR
*XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
*WHEN TIME
      *IS %TIME_SET%
            *REC(ACCOUNT=ACCOUNT.CF_TO_ACCT)
      *IS PRIOR
            *REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT)
*ENDWHEN
*COMMIT
Changes to above:
Dependencies (libraries, properties, etc.)
- SYSTEM_CONSTANTS.LGL
- CONSOLIDATION_LIBRARY.LGL u2013 to run the Business Rules section
- The following dimensions, members and properties are assumed
          Account
               CF_TO_ACCT property which is on all base level accounts which are part of the cash flow statement. The value should be the cash flow account that they map to. The dimension values are the IDs so they are all assumed as names
               CF_SUMM property used to move the income statement items to the cash flow statement. Contains the formulas on the destination cash flow accounts that map the Income statement accounts.
          Time u2013 just the dimension name
          RptCurrency
          CURRENCY_TYPE property with a value of L or R
What does it do?
Step 1 - MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
Use the formulas in the CF_SUMM accounts to move income statement values to the cash flow statement for all currencies based on the Currency_Type property
Step 2 - CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
·        Select all accounts that have values in the CF_TO_ACCT property
·        Add the Prior time period to the time memberset
·        Run this process for all currencies based on the Currency_Type property
·        Take the value in the current period and the negative value of the prior period to calculate the periodic cash flow amount and write to the account designated in the CF_TO_ACCT property
IMPORTANT NOTE: this step does have an issue that will be corrected in future versions of the sales demo. The issue is that if you run this logic for 2007.MAR, the negative balance for 2007.MAR will be written to 2007.APR as well as 2007.FEB being written to 2007.MAR. The logic needs to be changed as follows to work
First create two members in the DataSrc dimension that both consolidate to PreAdj member of the DataSrc dimension named CF_Current and CF_Prior
Add the following statement after the *XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
*XDIM_MEMBERSET DATASRC=
Change the REC statements as follows
*REC(ACCOUNT=ACCOUNT.CF_TO_ACCT,DATASRC=u201CCF_Currentu201D)
*REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT,DATASRC=u201CCF_Prioru201D)
Hope this helps somewhat. It is really hard to send this detailed stuff usingthe FORUM.
Edited by: Petar Daniel on Dec 11, 2008 8:39 PM

Business rules: Account transformation

Hi everyone.
I am trying to populate my cash flow statement using the Account Transformation. E.g For the changes in my inventories: I want the difference between the closing balance of DEC (of the previous year) and the closing balance of the current month.
I thought I could use "Source Period" and "Source Year" in the account transformation. Any idea how they can be used? I want to use a property: u201CPrevious yearu201D to make the time dynamic. Is that possible?
Thanks for your help
Esther

I would suggest using the dimension Account library functions and a dimension calculations or script logic calculations to create the value from the cube values, rather than during the data load process.Script Logic might look something like the following:
INCLUDE SYSTEM_CONSTANTS.LGL
*SYSLIB CONSOLIDATION_LIBRARY.LGL
// MOVE INCOME STATEMENT ITEMS TO CASH FLOW STATEMENT
RUNSUMMARIZE(ThisApp,CF_SUMM,%CATEGORY_SET%,%LC_RPT_CURR%)
//CALCULATE BALANCE SHEET MOVEMENTS AND POST TO CASH FLOW STATEMENT
*SELECT(%FROM_ACCOUNT%, "[ID]", "ACCOUNT", "[CF_TO_ACCT] <> ''")
*XDIM_MEMBERSET ACCOUNT = %FROM_ACCOUNT%
*XDIM_ADDMEMBERSET TIME = PRIOR
*XDIM_MEMBERSET RPTCURRENCY=%LC_RPT_CURR%
*WHEN TIME
      *IS %TIME_SET%
            *REC(ACCOUNT=ACCOUNT.CF_TO_ACCT)
      *IS PRIOR
            *REC(FACTOR=-1,ACCOUNT=ACCOUNT.CF_TO_ACCT,TIME=NEXT)
*ENDWHEN
*COMMIT
But this will require a few properties on the accounts members to support the calculations. The idea for cash flow is to have the basic values in the accounts, and then provide the calculations to place values into another set of accounts that build the CAshFLow statement. The most difficult part will be dealing with the exceptions, changes to the Cash Flow statement process a customer will need to work with each reporting period. But Script logic generally works the best.

Invalid Dimension SALESACCOUNT in Lookup rule

Hi all,
I craeted a New logic Sales_to_PL and provided the below script. But while validating it I get the message as
"Invalid Dimension SALESACCOUNT in Lookup rule"
Please advice.
// LOGIC FOR BEST PRACTICES - BP_SALES APPLICATION
*INCLUDE SYSTEM_CONSTANTS.lgl
// SEND THE RESULTS to THE PROFIT AND LOSS APPLICATION
*DESTINATION_APP=PROFIT_AND_LOSS
*SKIPDIM=PRODUCT
*RENAME_DIM SALESACCOUNT = Account
*XDIM_MEMBERSET Category <> ACTUAL
*XDIM_MEMBERSET PRODUCT = <ALL>
*WHEN SALESAccount.TRANSFER
*IS "Y"
*WHEN SALESAccount.PROFITLOSSACCT
*IS <> ""
*REC(EXPRESSION=%VALUE%,SALESACCOUNT=SALESACCOUNT.PROFITLOSSACCT,DataSrc="BP_SALESApp")
*ENDWHEN
*ENDWHEN
*COMMIT
// Calculate the FX in the P&L Application after Sales data is Transferred
*RUNLOGIC
*APP = BP_Profit_Loss
*LOGIC = FXTRANS
*ENDRUNLOGIC
Thanks
LAK

As my Dimension name is SalesAccount, I even tried changing the constantsllgl file in server and also the script with same SalesAccount instaed of SALESACCOUNT as shown below. Still it did not work.
// LOGIC FOR BEST PRACTICES - BP_SALES APPLICATION
*INCLUDE SYSTEM_CONSTANTS.lgl
// SEND THE RESULTS to THE PROFIT AND LOSS APPLICATION
*DESTINATION_APP=BP_Profit_Loss
*SKIPDIM=PRODUCT
*RENAME_DIM SalesAccount = Account
*XDIM_MEMBERSET Category <> ACTUAL
*XDIM_MEMBERSET PRODUCT = <ALL>
*WHEN SalesAccount.TRANSFER
*IS "Y"
*WHEN SalesAccount.PROFITLOSSACCT
*IS <> ""
*REC(EXPRESSION=%VALUE%,SalesAccount=SalesAccount.PROFITLOSSACCT,DataSrc="BP_SALESApp")
*ENDWHEN
*ENDWHEN
*COMMIT
// Calculate the FX in the P&L Application after Sales data is Transferred
*RUNLOGIC
*APP = BP_Profit_Loss
*LOGIC = FXTRANS
*ENDRUNLOGIC

Help with Script Logic

Hi All
I am trying to write the following script
*INCLUDE ..\finance\system_constants.lgl
*XDIM_MEMBERSET RATE=AVG,END
*SELECT(%IP_Currencies%, "[ID]", "INPUTCURRENCYDIM", "[MD] = 'D' OR [MD]= 'M'") )
*XDIM_MEMBERSET INPUTCURRENCY= %IP_Currencies%
*XDIM_MEMBER RATESRC=RATEINPUT
*WHEN INPUTCURRENCY.MD
*IS "D"
*REC(EXPRESSION=ROUND(1/%VALUE%,6),RATESRC="RATECALC")
*ELSE
*REC(RATESRC="RATECALC")
*ENDWHEN
*CLEAR_DESTINATION
*DESTINATION RATESRC=RATECALC
My LGX file looks like this.
*XDIM_MEMBERSET RATE=AVG,END
*XDIM_MEMBERSET INPUTCURRENCY= DZD,USD,ARS,AUD,ATS,BSD,BBD,BEF,BMD,BRL,GBP,BGN,CAD,CLP,CNY,CYP,CZK,DKK,XCD,EGP,EUR,FJD,FIM,FRF,DEM,XAU,GRD,HKD,HUF,ISK,INR,IDR,IEP,ILS,ITL,JMD,JPY,JOD,LBP,LUF,MYR,MXN,NZD,NOK,NLG,PKR,PHP,XPT,PLN,PTE,ROL,RUR,SAR,XAG,SGD,SKK,ZAR,KRW,ESP,XDR,SDD,SEK,CHF,TWD,THB,TTD,TRL,VEB,ZMK
*XDIM_MEMBER RATESRC=RATEINPUT
*WHEN INPUTCURRENCY.MD
*IS "D"
*REC(EXPRESSION=ROUND(1/%VALUE%,6),RATESRC="RATECALC")
*ELSE
*REC(RATESRC="RATECALC")
*ENDWHEN
*CLEAR_DESTINATION
*DESTINATION RATESRC=RATECALC
It gets validated fine and it also runs successfully through DPM. But the problem i am facing is that the above script is only running and posting data for USD in RATECALC where as I have lot many currencies listed in "INPUTCURRENCYDIM". It does not execute for any other currency except for USD. I want to run it for all the currencies.
Please suggest.
Diksha.
Edited by: Diksha Chopra on Jun 3, 2010 9:23 PM

Hi Diksha,
Please check in your inputcurrency dimension, how many members are there with the property MD as D?
I would suggest you to change your scritp to
*INCLUDE ..\finance\system_constants.lgl
*XDIM_MEMBERSET RATE=AVG,END
*XDIM_MEMBER RATESRC=RATEINPUT
*WHEN INPUTCURRENCY.MD
*IS "D"
*REC(EXPRESSION=ROUND(1/%VALUE%,6),RATESRC="RATECALC")
*IS "M"
*REC(RATESRC="RATECALC")
*ENDWHEN
*COMMIT
*CLEAR_DESTINATION
*DESTINATION RATESRC=RATECALC
Hope this helps.

SPRUNCALCACCOUNT able to execute without Currency dimension?

Hi,
I have an application, which doesn't have currency dimension. I'd like to use SPRUNCALCACCOUNT for copying values to cash flow statement.
According to the example written in the Administration Guide, I need to put currency parameter in addition to application set, category etc.
*RUN_STORED_PROCEDURE=SPRUNCALCACCOUNT([LEGALAPP], [ACTUAL], [USD],
[%SCOPETABLE%], [%LOGTABLE%],[Transformation group],[MAXSTATUS])
Is the currency dimension a must? I tried running it without putting currency and it doesn't work. Is there any workaround?
Thank you!
Sunny

I would be very surprised if it works without a currency-type dimension. It doesn't look like anyone on the forum here has experience with this; you may want to confirm with SAP support.
I would guess that the stored proc behind the scenes is looking up the name of the currency-type dimension, and then dropping that "USD" parameter into a SQL query's where clause in something like:
... select someStuff from mbrMyCurrencyTypeDimensionName where ID = 'USD'
If you're feeling adventurous, you might try to change one of your existing dimensions to a currency-type dimension, if that's possible. It would only work if the calculation makes sense by passing a single member of that chosen dimension into the SP.
A few versions back, I'd recommend playing with the system_constants.lgl file in the adminapp\application folder, to trick the BPC SQL logic in this way. The following would tell the system that the currency-type dimension is now named Product:
*FUNCTION CURRENCYDIM=Product
However, I think that these days, the stored procs all take their dimension-type metadata from tblDimension in the database, and not that system constants file.
Otherwise, your only other choice may be to add another dimension to the app -- even though it only has one member, LC. Not ideal, but maybe it's still worthwhile if your calcs can be done using the Account Transformation rules.

Work status Data Manager

Hello!
We can run a package from Data Manager on periods that have the status of "Locked"
We have a package with the following script:
'DEBUG(ON)
PROMPT(SELECTINPUT,,,"Please select category, entity and time for restatement","%CATEGORY_DIM%%TIME_DIM%%CURRENCY_DIM%")
TASK(Execute formulas,USER,%USER%)
TASK(Execute formulas,APPSET,%APPSET%)
TASK(Execute formulas,APP,%APP%)
TASK(Execute formulas,SELECTION,%SELECTIONFILE%)
TASK(Execute formulas,LOGICFILE,%APPPATH%\..\AdminApp\%APP%\FXCONSOL_Restatement.lgx)
TASK(Execute formulas,RUNMODE,1)
TASK(Execute formulas,LOGICMODE,1)
TASK(Execute formulas,CHECKLCK,1)
The logic used are as follows:
*INCLUDE SYSTEM_CONSTANTS.LGL
//Kr omflyttning av obeskattade reserver
*INCLUDE ObeskRes.lgf
// Kr berkningar av elimineringar och konsolidering
*RUN_STORED_PROCEDURE = SPRUNCONSO('%APP%', [%KATEGORI_SET%], [%GRUPP_SET%],'%SCOPETABLE%','%LOGTABLE%')
*COMMIT
*INCLUDE Calculations_H2.LGF
If we use this package in Data Manager for a period which has the status of "Locked" the package will run. Should not this be stopped because we have the status of "Locked" on the period and the script says that it will check Work Status

Hi Daniel,
'Normal' logic should listen to the 'locked' settings. Please double check the workstatus settings to see if DM=locked is correct for the 'locked' workstatus.
BUT:
The businessrules stored procedures do not listen to these settings. Most SP calls have there own locking methods.
For example the SPRUNCONVERSION call is as follow:
*RUN_STORED_PROCEDURE=SPRUNCONVERSION(u2018APPLICATIONu2019,u2019CATEGORY_SET%u2019,
u2019%CURRENCY_SET%u2019,u2019GLOBALu2019,u2019%SCOPETABLE%u2019,u2019%LOGTABLE%u2019,impact,destination,
ratedimension,maxstatus)
The maxstatus setting here is the maximum status which allows change of data.
The one exception here is SPRUNCONSO which can not be prevented from running and storing data.
Normally this is good behaviour;
SPRUNCONSO doesn't change LC data and shouldn't therefore not calculate other numbers than the previous run.
The behaviour of other sp's could/must sometimes be different then normal datamanager packages; for example when the status is submitted, users should not be able to upload/clear data, but should be able to run conversion and consolidations, that is why the sp's have there own locking section in the call itself.
Alwin

Error While Sending Data for Currency Translation

Hello Experts,
I am trying to send data via template. Data is getting saved but I am getting following error displayed.
1.) When I try to enter data for a particular month then, error as FX-200.
2.) When I try to enter data accross months of more than year then , FX-045 and FX-310 error.
I had look on various SAP Notes available for the errors.
As per them, I ran Full optimization, I checked rates are maintained for previous year too, I checked for LC Currency Type Property is maintained as L.
But nothing Worked.
Currently only the 3 members are maintained in Rate Dimension, so exceeding the size limit cannot be an issue.
Kindly Suggest, what could be another possible reason for the errors.
Regards,
Apoorva Garg

Hello,
1.) I am getting issues for example for 2010.Mar, 2010.Dec, 2013.Dec, 2012.Dec
2.) Business Rules Maintained
3.) Business Rule called via Default Script Logic
// Default base level logic - applies to all base members in all dimensions
*INCLUDE system_constants.lgl
//Process_Each_Member = TIME
*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','KPI_Working_Act_FX','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
*COMMIT
//*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','KPI_Working_AOP_FX','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
//*COMMIT
Regards,
Apoorva

*Prior statement in script logic

Hi,
I'm getting started with script logic and I'm trying to create a record that will be the result of the current amount in a specific account minus the amount for the same account in the previous period.
I was thinking to use a "prior" statement, but not really sure how to do that. Do somebody could write me an example that would sbustract my current amount minus the amount from the previous period where the account is the same in a sql logic?
Thanks
Martin

Hi,
This should do the trick.
*INCLUDE SYSTEM_CONSTANTS.LGL
*XDIM_MEMBERSET TIMEDIM=PRIOR,%TIME_SET%
*XDIM_Member DataSrc=INput
*WHEN *
*IS *
*REC(EXPRESSION=GET(DATASRC="INPUTSAP",TIME=PRIOR)-GET(DATASRC="INPUTSAP"),NOADD,DATASRC="Movement")
*ENDWHEN
*commit
Cheers,
AvdB
Edited by: Gert Andries van den Berg on Aug 12, 2009 9:14 AM

Recognizing Changes in System_Constants.lgl

Similar Messages

Maybe you are looking for