Regarding FXTRANS.LGF

Hi,
I have encountered an error while running FXTRANS.LGF script logic.
I am using in my finance application V_CATEGORY, V_GROUPS and V_ENTITY.
While i tried to run delivered FXTRANS, it kicked back with an error saying as C_CATEGORY., So i went back to re-check logic
and changed to V_CATEGORY and changed ENTITY to V_ENTITY and tried to 'validate and save' and it throwed programm error of validation.
I went to BI side and tried to check CURR_CONVERSION program, but i couldnot able to find program CURR_CONVERSION
at se38. Can you please help me out.
                          Thank you.

These are the below code.
FXTRANS SCRIPT LOGIC
*RUN_PROGRAM CURR_CONVERSION
      CATEGORY     = %V_CATEGORY_SET% 
      GROUP = %V_GROUPS_SET% 
      TID_RA = %TIME_SET%
      RATEENTITY = GLOBAL
      OTHER = [ENTITY=%ENTITY_SET%]//For More than one other scope parameters: OTHER = [ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...]
*ENDRUN_PROGRAM
on Advanced.
PROMPT(SELECTINPUT,,,,"%CATEGORY_DIM%,%GROUP_DIM%,%TIME_DIM%")
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SUSER,%USER%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPPSET,%APPSET%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SAPP,%APP%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,SELECTION,%SELECTION%)
TASK(/CPMB/DEFAULT_FORMULAS_LOGIC,LOGICFILENAME,FXTRANS.LGF)

Similar Messages

  • FXTRANS

    When I am trying to run the Currency Conversion I am getting the following error.
    I maintained the dimension as GLOBAL as the rate entity in the Rate Model.
    “RUN_LOGIC: Rate entity not found in application Consolidation model: Consolidation. Package status: ERROR”
    My Script Logic for the Currency Conversion is as follows:
    *RUN_PROGRAM CURR_CONVERSION
    CATEGORY = %CATEGORY_SET%
    GROUPS=%GROUPS%
    TID_RA = %TIME_SET%
    RATEENTITY = GLOBAL
    *ENDRUN_PROGRAM
    After maintaining the Entity as GLOBAL in Consolidation Model, I re-ran the Package and I got the same error.
    RUN_LOGIC:Rate entity not found in application CONSOLIDATION Model
    I changed the dimension to Global and the package ran successfully but no record was translated
    LOG BEGIN TIME:2014-05-10 16:07:59
    FILE:\ROOT\WEBFOLDERS\COG_CONS\ADMINAPP\LEGCONS\FXTRANS.LGF
    USER:210214
    APPSET:COG_CONS
    APPLICATION:CONSOLIDATION
    RUN CURRENCY CONVERSION
    0  SUBMITTED, 0  SUCCESS, 0  FAIL.
    Is there anything that I am missing here.
    This is on BPC NW 10.
    Appreciate help.
    SAP Boss

    My observations are wrong.
    It is working for the following parameters:
    Rate model Entity dimension - GLOBAL.
    No Entity dimension  Global maintained in Consolidation Model
    LOG BEGIN TIME:2014-05-10 19:59:32
    FILE:\ROOT\WEBFOLDERS\COG_CONS\ADMINAPP\LEGCONS\FXTRANS.LGF
    USER:210214
    APPSET:COG_CONS
    APPLICATION:LEGCONS
    RUN CURRENCY CONVERSION
    38  SUBMITTED, 38  SUCCESS, 0  FAIL.
    Regards
    SAB BOSS

  • BPC NW10.0 Execute the currency translation in DEFAULT.LGF

    Hello,
    I would like to execute the task currency translation in DEFAULT.LGF
    Nb : we used the DEFAULT.LGF when we import the actual and budget data with Excel file (.csv)
    I created the DEFAULT.LGF and inserted the following rows:
    *XDIM_MEMBERSET CATEGORY=%CATEGORY_SET%
    *XDIM_MEMBERSET RPTCURRENCY=LC
    *XDIM_MEMBERSET TIME=%TIME_SET%
    *XDIM_MEMBERSET DATASRC=INPUT
    * INCLUDE FXTRANS.LGF
    But, not currency translation when we import the actual and budget data
    Nb : When I execute FXTRANS.LGF (FX_STATEMENT), it's OK , the system created the new records for translation currency
    Best regards
    Bastien

    Hi,
    If I used the input schedule, the records are converted in EUR
    If I used manually  the fonction the currency translation , the records are converted in EUR
    Example of conversion
    COSTCENTER
    COSTELEMENT
    INTERCO
    COMPANY
    DATASOURCE
    CATEGORY
    RPTCURRENCY
    TIME
    Measures
    S169100
    G502
    P_SND
    S0168
    IMPORT_SAP
    BUDGET
    LC
    2013.OCT
    100,0000000
    S169100
    G502
    P_SND
    S0168
    IMPORT_SAP
    BUDGET
    EUR
    2013.OCT
    68,0000000
    Bastien

  • .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 Script Logic FXTrans

    Hi All,
    Under script logic section under my application, I have maintain
    *RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','%CATEGORY_SET%','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
    and added below it the following
    *INCLUDE SYSTEM_CONSTANTS.LGL
    *INCLUDE SYSTEM_LIBRARY.LGL
    *SYSLIB MULTICURRENCYTRANS.LGF
    I receive the following error, " Application: FINANCE
    Logic file: FXTrans.LGF
    Validation status of executable file: Failed
    - missing file:D:\PC_MS\DATA\WebFolders\BSB\AdminApp\FINANCE\SYSTEM_LIBRARY.LGL
    Validation status of syntax: Failed
    - Invalid syntax found; see statements in red"
    The Red ones are
    - SYSTEM_LIBRARY.LGL
    - MULTICURRENCYTRANS.LGF
    Could anyone advise me how do go about on this
    Thanks
    Zan

    Hi,
    I'd like to clarify first that SPRUNCONVERNSION and MULTICURRENCYTRANS.LGL do the same thing using different methods. The first requires you to maintain appropriate business rule table called Currency Conversion and the latter is Script Logic-based functinality. Typically you do not need to maintain bot as SPRUNCONVERSION is pretty robust and should fulfil all your needs unless you have to do some truly exotic variation of the business calculation.
    So to conclude you probably only need the following in your script logic:
    *RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','%CATEGORY_SET%','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
    *COMMIT
    and also maintain rates in the rate application. Please refer to user guide section Business Rule Management for further details: [http://help.sap.com/saphelp_bpc75/helpdata/en/b1/f5839e6ba74a22aa4ce9470179c854/content.htm]
    In order to use script logic you will need to write the logic yourself or to use the one supplied with the system (in the SYSTEM_LIBRARY).
    The logic library is stored in the file on the server %APPSET%\System Library\Logic Library\SYSTEM_LIBRARY.LGL
    IN your script logic you need to include the library to use in your logic:
    *SYSLIB SYSTEM_LIBRARY.LGL (SYSLIB tells the system to look at the specific place in the appset folder and LGL is the extension for appset-level logic files)
    After this you need to call appropriate subprogram from that library and pass some parameters to it:
    RunFX(%APP%,%CATERGORY_SET%)
    *COMMIT
    for example.
    Hope this helps,
    Madis

  • Regarding error while running currency conversion

    While running currency conversion delivered package FXTRANS.LGF, I am getting an error as
    'Failed to analyse prompt %CURRENCY_DIM%. Can you please help me out.
    I checked currency dimensions----- Input currency and rpt currency and was fine with dimension type currency.
    Can anyone please suggest some solutions.
                            thank you.

    Are your performing the currency conversion for a financial or consolidation application ?
    If it is a consolidation application, you need to include in your script the "Group" dimension, not the "currency" one

  • APO DP: currency conversion with CURR_CONV_FAC

    Dear DP experts,
    we have currently a problem  that is described in a similar thread, however the solution is not yet clear.
    Demand planning: Change currency in unit column with a macro function?
    We are using the currency conversion: on planning book, top left corner - right mouse button - UoM - Set - In currency field put USD. (*) The planning area currency is RUB. To work with USD, the program takes the currency exchange rate of today. However we need to use the currency exchange rate that is maintained in SPRO on a monthly basis.
    We were advised by SAP that it is a program limitation and there is a macros CURR_CONV_FAC to make currency conversion based on periods.
    As we want to keep the conversion functionality  as is (*), did anyone try to implement the conversion in such a way and could help us with advice?
    For example , we think that this macros
    1) has to be DEFAULT,
    2) has to find the planning area currency
    3) has to read the new currency from the UoM column
    4) has to recognize that the currency change event has to happen.
    5) has to be allways called after setting the new currency.
    There are some doubts that this can work, can anyone advise?
    Best regards
    Vladimir Ermoshin

    Hi BPC Gurus,
    I too have the same issue.
    We are in the process of upgrading BPC7.5NW to BPC10.0 NW.
    1) I am validating the below Currency Conversion script in BPC10.0:-
    *RUN_PROGRAM CURR_CONVERSION
    CATEGORY = %CATEGORY_SET%
    CURRENCY = %RPTCURR_SET%
    TID_RA = %TIME_SET%
    RATEENTITY = GLOBAL
    OTHER = [ENTITY = %COMPANY_SET%]
    *ENDRUN_PROGRAM
    The data manager package runs w/o any errors, but log says:-
    LOG BEGIN TIME:2013-02-26 20:36:16
    FILE:\ROOT\WEBFOLDERS\XXXXX\ADMINAPP\LEGAL_CON\FXTRANS.LGF
    USER:JXXXX
    APPSET:XXXXX
    APPLICATION:LEGAL_CON
    RUN CURRENCY CONVERSION
    0  SUBMITTED, 0  SUCCESS, 0  FAIL.
    SCRIPT RUNNING TIME IN TOTAL:1.16 s.
    LOG END TIME:2013-02-26 20:36:18
    2) When tested in UJKT in BW I have the below error LOG:
    UJK_VALIDATION_EXCEPTION:Dimension set:"CATEGORY" not assigned in Data Manager
    3) Model is of consolidation type with dummy(no data) Ownership model.
    4) Below is screen shot of my Currency Translation rules post upgrade in BPC10.0NW.
    Any clue why currency conversion is not picking any records??
    Thanks in advance for your earliest help.
    GMR

  • ERROR with CX_SY_ARITHMETIC_OVERFLOW and RAISING clause (for Consolidation)

    Hello,
    When we run the Consolidation several times on the same data range several times the tool adds the results, so we need to execute in a single package a CLEAR data, the Currency Conversion and the Consolidation.
    Our package launches a ScriptLogic  with the following code:
    *XDIM_MEMBERSET C_ACCT=<all>
    *XDIM_MEMBERSET FLOW=<all>
    *XDIM_MEMBERSET TIME= %TIME_SET%
    *XDIM_MEMBERSET GROUPS= %GROUPS_SET%
    *XDIM_MEMBERSET C_CATEGORY=%C_CATEGORY_SET%
    *XDIM_MEMBERSET ENTITY=<ALL>
    *XDIM_MEMBERSET C_DATASRC = <ALL>
    *XDIM_MEMBERSET CECO = <ALL>
    *XDIM_MEMBERSET INTCO = <ALL>
    *WHEN GROUPS
    *IS <>"LC", "EUR"
         *WHEN C_DATASRC
         *IS <>"INPUT","T_MAN"
              //Here, we need an instruction to erase the data
              *REC(FACTOR=-1,
                        TIME="%TIME_SET%",
                        GROUPS="%GROUPS_SET%",
                        C_CATEGORY="%C_CATEGORY_SET%")
         *ENDWHEN
    *ENDWHEN
    *COMMIT
    *INCLUDE FXTRANS.LGF
    *INCLUDE CONSOLIDATION.LGF
    And when we run the package we get the following error:
    An exception with the type CX_SY_ARITHMETIC_OVERFLOW occurred, but was neither handled locally, nor declared in a RAISING clause
    Overflow in the operation *
    On the one hand, we want to solve the issue and, second, Is it normal that the tool accumulates the results when we run several times the consolidation?
    Best regards,
    Miguel.

    Miguel,
    Check  if you  are  running  in t o  this  note..
    Note 1355621 - overflow in WriteBack concurrent locking
    https://websmp230.sap-ag.de/sap%28bD1lbiZjPTAwMQ==%29/bc/bsp/spn/sapnotes/index2.htm?numm=1355621
    Summary
    Symptom
    System exception CX_SY_ARITHMETIC_OVERFLOW throwed. The exception occurs in CL_UJR_WRITE_BACK=>CHECK_CONCURRENT_LOCK.
    Other terms
    WriteBack, Overflow
    Reason and Prerequisites
        This is a program error. The variable(integer) is not large enough to calculate number of all possible combination of dimension members used in one WriteBack data package.
        This Note will increase the variable length to 100 to handle a googol (10E100) of combinations.
    Solution
    Please apply this Note or upgrade to Support Package.
    Header Data
    Release Status:     Released for Customer
    Released on:     16.07.2009  05:08:14
    Master Language:     English
    Priority:     Correction with low priority
    Category:     Program error
    Primary Component:     EPM-BPC-NW-DM-WBV WriteBack Validation
    Secondary Components:     EPM-BPC-NW NetWeaver Version
    Affected Releases
    Software
    Component
    hope  this helps..
    Edited by: Vishal Mahawadhi on Dec 10, 2009 10:28 AM

  • FX_RESTATEMENT- automatic process chain

    Hello!
    Question about package FX_RESTATEMENT.
    It is necessary to limit data for a currencies restatment. Example, can I change parameter TIME dynamically for automatically organised chains (through UJD_TEST_PACKAGE)?
    Or how it is possible to start the package FX_RESTATEMENT for defined C_DATASRC? File FXTRANS.LGF does not content this dimension as parameter.
    Thanks!
    Best regards,
    Svetlana.
    Edited by: Svetlana Kazaneva on May 1, 2010 3:14 PM

    Dear Sweatha,
    1 - You have to create a process chain with a start step, error handling step and a step to edit data and then a post step
    2 - If error occurs during ILTC, the error handling chain will be started automatically. Data will be stored in the error handling step.
    To process the error really you have to go to the error handling monitor and press the continue button. Data will be sent to the edit step. Here you can correct manually the errors.
    Please find additional information in the SAP Help Portal: http://help.sap.com/saphelp_mdm300/helpdata/EN/88/454ba493cb43f1b74336772a7f3508/frameset.htm
    Kind regards,
    Markus

  • Error while running FX restatement process for currency translation

    Hi Experts,
    I am facing errors while trying to run FX_Restatement process to do currency translation.
    I am having the error: RUN_LOGIC:Member u201CXXXu201D not exist => where XXX is any currency I am trying to convert.
    Below is the script logic (FXTRANS.LGF)used.
    *RUN_PROGRAM CURR_CONVERSION
          CATEGORY     = %FX_CATEGORY_SET% 
          CURRENCY     = %FX_INPCURRENCY_SET% 
          TID_RA = %FX_TIME_SET%
          OTHER = [ENTITY=%FX_ENTITY_SET%]     
          RATEENTITY = GLOBAL
          //For More than one other scope parameters: OTHER = [ENTITY=%FX_ENTITY_SET%;INTCO=%INTCO_SET%...]
    *ENDRUN_PROGRAM
    I am working on BPC 7.5 NW version.
    Can you help us with this?

    For the currency you are converting to: XXX
    INPUTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y"
    and
    RPTCURRENCY dimension must have XXX as a member with "REPORTING" property set to "Y" and "CURRENCY_TYPE" property set to "R"
    It needs to be in both dimensions with the right properties.  INPUTCURRENCY is the currency dimension in the RATE cube, RPTCURRENCY is the currency dimension in the financial or consolidations cube.

  • BPC 7.5 NW - COPY DATA in ScriptLogic

    Hi we have this code ok.
    *WHEN CTA_HHRR
    *IS BAS(REMUNERACIONES)
    *REC( FACTOR = ([CTA_HHRR].[PARAM_000000001],[Centro_De_Costo].[Dummy]),BAS(REMUNERACIONES) )
    *ENDWHEN
    Now, we need copy data value inserted in ACCOUNT1 for 2010.ENE to FEB.2010 until 2010.DEC.
    But MONTH is Dinamic, Code need work for any YEAR, 2010 or 2011, or 2012, etc.
    We all time insert value in Current view for  ????.ENE
    After value is inserted in ????.ENE need run ScriptLogin for Copy Values from ????.ENE to ????.FEB until ????.DEC
    For all ACCOUNTS inside BAS(REMUNERACIONES).
    After COPY process, we run Code:
    *WHEN CTA_HHRR
    *IS BAS(REMUNERACIONES)
    *REC( FACTOR = ([CTA_HHRR].[PARAM_000000001],[Centro_De_Costo].[Dummy]),BAS(REMUNERACIONES) )
    *ENDWHEN
    This Code Ajust IPC value, after call Currency Convert to USD and PEN.
    We insert in Include :
    *include COPIA.LGF
    *include FXTRANS.LGF
    Working good.
    FXTRANS.LGF
    *RUN_PROGRAM CURR_CONVERSION
          CATEGORY     = %CATEGORY_SET% 
    //GROUP = NON_GROUP 
          TID_RA = %TIME_SET%
          R_Entity = GLOBAL
          OTHER = [Centro_De_Costo=%Centro_De_Costo_SET%]//For More than one other scope parameters: OTHER = [CentroDeCosto=%ENTITY_SET%;INTCO=%INTCO_SET%...]
    *ENDRUN_PROGRAM
    Thank you.

    This code working:
    *XDIM_MEMBERSET CATEGORY = PLAN
    *XDIM_MEMBERSET Centro_De_Costo = Dummy
    *XDIM_MEMBERSET CTA_HHRR = BAS(REMUNERACIONES)
    *XDIM_MEMBERSET Empleado = %Empleado_SET%
    *XDIM_MEMBERSET RPTCURRENCY = LC
    *XDIM_MEMBERSET TIME = %YEAR%.JAN
    *XDIM_MEMBERSET MEASURES = "PERIODIC"
    *WHEN TIME
    *IS %YEAR%.JAN
    *REC(FACTOR=1, TIME = TMVL(1,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(2,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(3,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(4,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(5,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(6,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(7,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(8,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(9,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(10,2010.JAN))
    *REC(FACTOR=1, TIME = TMVL(11,2010.JAN))
    *ENDWHEN
    But not want coding in ScriptLogin : 2010 i need var
    This code Working only for first line or single line the REC:
    *XDIM_MEMBERSET CATEGORY = PLAN
    *XDIM_MEMBERSET Centro_De_Costo = Dummy
    *XDIM_MEMBERSET CTA_HHRR = BAS(REMUNERACIONES)
    *XDIM_MEMBERSET Empleado = %Empleado_SET%
    *XDIM_MEMBERSET RPTCURRENCY = LC
    *XDIM_MEMBERSET TIME = %YEAR%.JAN
    *XDIM_MEMBERSET MEASURES = "PERIODIC"
    *WHEN TIME
    *IS %YEAR%.JAN
    *REC(FACTOR=1, TIME = %YEAR%.FEB )
    *ENDWHEN
    This code not working:
    *XDIM_MEMBERSET CATEGORY = PLAN
    *XDIM_MEMBERSET Centro_De_Costo = Dummy
    *XDIM_MEMBERSET CTA_HHRR = BAS(REMUNERACIONES)
    *XDIM_MEMBERSET Empleado = %Empleado_SET%
    *XDIM_MEMBERSET RPTCURRENCY = LC
    *XDIM_MEMBERSET TIME = %YEAR%.JAN
    *XDIM_MEMBERSET MEASURES = "PERIODIC"
    *WHEN TIME
    *IS %YEAR%.JAN
    *REC(FACTOR=1, TIME = %YEAR%.FEB )
    *REC(FACTOR=1, TIME = %YEAR%.MAR )
    *REC(FACTOR=1, TIME = %YEAR%.ABR )
    *REC(FACTOR=1, TIME = %YEAR%.MAY )
    *REC(FACTOR=1, TIME = %YEAR%.JUN )
    *REC(FACTOR=1, TIME = %YEAR%.JUL )
    *REC(FACTOR=1, TIME = %YEAR%.AGU )
    *REC(FACTOR=1, TIME = %YEAR%.SEP )
    *REC(FACTOR=1, TIME = %YEAR%.OCT )
    *REC(FACTOR=1, TIME = %YEAR%.NOV )
    *REC(FACTOR=1, TIME = %YEAR%.DEC )
    *ENDWHEN
    Any idea ?

  • BPC NW 10 Currency Conversion

    Dear All,
    I want to do a currency conversion in my application. is there any step by step for BPC NW 10 ?
    i already put my data in dimension member LC and i want to convert it to USD. i'm also already do a corversion via menu :
    1. Data Manager - Run package
    2. FX Restatement
    but nothing happen.
    Thanks in advance
    Suprapto

    Dear Raghu,
    okay, after i use FX Restatement, here is the error :
    Server message:
    code: UJD_EXCEPTION_018
    severity: error
    description: Failed to analyze prompt %GROUP_DIM%
    log id: 051MjG0Q7k6ndmT8pF9Rr0
    CHAIN_TEMPLATE:
    ERROR:%GROUP_DIM%
    HIER_NAME:
    HIER_PATTERN:
    IOBJ:
    OPERATOR:
    VARIANT_NAME:
    VARIANT_TYPE:
    Fyi, my dimension is only :
    Time | Account | P_Entity | category | RptCurrency
    after i download the FXTrans.LGF , i found there is a code like these :
    //Handling the scenario groups and currency members are existing, where they are created within one dimension with "R" type
    *RUN_PROGRAM CURR_CONVERSION
          CATEGORY     = %CATEGORY_SET% 
          GROUP = %GROUPS_SET%  //
          TID_RA = %TIME_SET%
          RATEENTITY = GLOBAL
          OTHER = [ENTITY=%ENTITY_SET%]//For More than one other scope parameters: OTHER = [ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...]
    *ENDRUN_PROGRAM
    The question is, how i can change the FXTrans.LGF , i want to remove that code and only use these code .
    /Handling the scenario without group dimension, where the currency dimension only holds the currencies
    *RUN_PROGRAM CURR_CONVERSION
          CATEGORY     = %CATEGORY//(category dimension name)//_SET% 
          CURRENCY = %RPTCURRENCY_SET% 
          TID_RA = %TIME_SET%
          RATEENTITY = GLOBAL
          OTHER = [ENTITY=%ENTITY_SET%]//For More than one other scope parameters: OTHER = [ENTITY=%ENTITY_SET%;INTCO=%INTCO_SET%...]
    *ENDRUN_PROGRAM
    Thanks,
    Suprapto

  • Runlogic PH issue on BPC 10 for parallel run

    Hi,
    We have implemented runlogic PH keyword on BPC 10 for running currency translation in parallel with change parameter Time.
    for ex: if we run the package with time period 2013.01. as per logic it is supposed to run for all months in 2013 from 2013.01 to 2013.12 in parallel.
    some times when we run this package, it tends to skip few months(it does not translate for few months and these months are different for each run) in between and it is random.
    Main script
    *SELECT(%YEAR_F%,[YEAR],TIME,[ID]='2013.02')
    *SELECT(%MONTH_F%,[BASE_PERIOD],TIME,[ID]='2013.02')
    *SELECT(%TIME_F%,[ID],TIME,[YEAR]='%YEAR_F%' AND [BASE_PERIOD] >= '%MONTH_F%' AND [CALC]='N')
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    VALIDATION = OFF
    DEBUG = OFF
    LOGIC = FXTRANS_FCS.LGF
    APPSET = BEACON
    APP = VOLUMES
    DIMENSION CATEGORY = %CATEGORY_SET%
    DIMENSION ENTITY = %ENTITY_SET%
    DIMENSION TIME = %TIME_F%
    CHANGED = TIME
    *END_BADI
    for ex: if i select 2013.01 - based on the above select statements it takes from 2013.01 to 2013.12
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    VALIDATION = OFF
    DEBUG = OFF
    LOGIC = FXTRANS_FCS.LGF
    APPSET = BEACON
    APP = VOLUMES
    DIMENSION CATEGORY = %CATEGORY_SET%
    DIMENSION ENTITY = %ENTITY_SET%
    DIMENSION TIME = 2013.02,2013.03,2013.04,2013.05,2013.06,2013.07,2013.08,2013.09,2013.10,2013.11,2013.12
    CHANGED = TIME
    *END_BADI
    Called function:standard fxtrans.lgf
    /Currency Translation
    *RUN_PROGRAM CURR_CONVERSION
    CATEGORY = %CATEGORY_SET%
    CURRENCY = %RPTCURRENCY_SET%
    TID_RA = %TIME_SET%
    OTHER = [ENTITY=%ENTITY_SET%]
    RATEENTITY = GLOBAL
    *ENDRUN_PROGRAM
    //Reverse Non-Monetary Quantity conversion
    *SELECT (%ACCTN%, [ID], VOLACCT, CALC = 'N')
    *SELECT (%QUANTU%, [ID], QUANTITY, NO_CURR = 'N')
    *SELECT(%CATEG%, [FX_SOURCE_CATEGORY], CATEGORY, [ID] = %CATEGORY_SET%)
    *XDIM_MEMBERSET BU = BAS(TOTBU)
    *XDIM_MEMBERSET BUILDSTATE = BAS(TOTBS)
    *XDIM_MEMBERSET BUSINESS = BAS(TOTBUS),MP_VB
    *XDIM_MEMBERSET CTRTYPE = BAS(TOTCTR)
    *XDIM_MEMBERSET PRODUCT = BAS(TOTPRODUCT)
    *XDIM_MEMBERSET QUANTITY = %QUANTU%
    *XDIM_MEMBERSET TECHPLATF = BAS(TOTTP)
    *XDIM_MEMBERSET VOLACCT = %ACCTN%
    *XDIM_MEMBERSET AUDITTRAIL = BAS(D_INPUT),D_OTHER
    *XDIM_MEMBERSET CATEGORY = %CATEG%
    *XDIM_MEMBERSET ENTITY = %ENTITY_SET%
    *XDIM_MEMBERSET RPTCURRENCY = C_LC
    *XDIM_MEMBERSET TIME = %TIME_SET%
    *WHEN QUANTITY.NO_CURR
    *IS N
    *REC(FACTOR=1,RPTCURRENCY=%RPTCURRENCY_SET%,CATEGORY=%CATEGORY_SET%)
    *ENDWHEN
    *COMMIT
    Kindly advise.
    Thanks,
    Madhav

    Hi Vadim,
    specified all dimensions inside badi but still the same issue. Two months are not translated.. there are no locks in the system too..
    Pkg log shows that it was run for all months
                                                   12 Data Regions will be generated.
                                                   12 parallel processes will be used.
    Dimension TIME memeber 2013.01 used for a new Data Region.
    Process Task  1 Started at 10:42:17.
    Dimension TIME memeber 2013.02 used for a new Data Region.
    Process Task  2 Started at 10:42:17.
    Dimension TIME memeber 2013.03 used for a new Data Region.
    Process Task  3 Started at 10:42:17.
    Dimension TIME memeber 2013.04 used for a new Data Region.
    Process Task  4 Started at 10:42:17.
    Dimension TIME memeber 2013.05 used for a new Data Region.
    Process Task  5 Started at 10:42:17.
    Dimension TIME memeber 2013.06 used for a new Data Region.
    Process Task  6 Started at 10:42:17.
    Dimension TIME memeber 2013.07 used for a new Data Region.
    Process Task  7 Started at 10:42:17.
    Dimension TIME memeber 2013.08 used for a new Data Region.
    Process Task  8 Started at 10:42:17.
    Dimension TIME memeber 2013.09 used for a new Data Region.
    Process Task  9 Started at 10:42:17.
    Dimension TIME memeber 2013.10 used for a new Data Region.
    Process Task 10 Started at 10:42:17.
    Dimension TIME memeber 2013.11 used for a new Data Region.
    Process Task 11 Started at 10:42:17.
    Dimension TIME memeber 2013.12 used for a new Data Region.
    Process Task 12 Started at 10:42:17.
    Process Task  8 Ended at 10:42:35.
    Process Task  7 Ended at 10:42:35.
    Process Task  4 Ended at 10:43:00.
    Process Task  5 Ended at 10:43:00.
    Process Task  3 Ended at 10:43:03.
    Process Task  6 Ended at 10:43:03.
    Process Task 12 Ended at 10:43:03.
    Process Task 10 Ended at 10:43:03.
    Process Task 11 Ended at 10:43:04.
    Process Task  2 Ended at 10:43:05.
    Process Task  1 Ended at 10:43:06.
    Process Task  9 Ended at 10:43:52.
    BADI EXECUTION TIME IN TOTAL :97294.41 ms.
    SCRIPT RUNNING TIME IN TOTAL:97.76 s.
    LOG END TIME:2014-05-22 10:43:52
    Thanks,
    Venu

  • Logic doesn't unless run with Default logic

    Hi Experts,
    I have a logic named Variation.lgf which is included in the Default.lgf logic, FXTrans.lgf and LegalConsolidation.lgf. When I try to run the FXTrans logic or LegalConsolidation logic, Variation don't run. But if I run the Default logic manually, it runs. What I'm wondering is first it's included in my other two logics and also Default logic runs automatically whenever I run either of the two packages(FX Trans and Legal Consolidation) all logics are validate and saved. Is it a bug or something?
    Thanks,
    Marvin

    Hi Nilanjan,
    Thanks for the reply but still it doesn't run even if I used *RUNLOGIC, this is the syntax right?
    *RUNLOGIC
    *APP = LegalApp
    *LOGIC = Variation
    *ENDRUNLOGIC
    *COMMIT
    Hi Sorin,
    I'm quite sure that I've validated the Variation.LGF first before I've validated the other logics. To be sure I always checked the .LGX file of my logics.
    Thanks,
    Marvin

  • JOURNAL.lgf can take too long

    Hello,
    We are facing an issue with the JOURNAL.lgf and I would really appreciate your feedback.
    Our JOURNAL logic generates an additional record with the closing balance, however even though for most of the users, the process of this logic is instantaneously, for some users it can take up to hours to refresh the additional record that the JOURNAL logic has to generate.
    I am not able to reproduce the issue because in my case, I post a journal and it generates the records instantaneously.  Is there a way to track how long the logic takes? (BIF transaction, etc.)
    Why could it be that this issue is only happening to few users with the same authorizations?
    Has anyone faced this issue?
    We are using SAP BPC 7.5 NW SP03
    Many thanks in advance
    Best regards
    Dani
    Edited by: Daniel Sobrino on Feb 1, 2011 5:13 PM
    Edited by: Daniel Sobrino on Feb 1, 2011 5:35 PM
    Edited by: Daniel Sobrino on Feb 1, 2011 5:35 PM

    Hello,
    We found out with te audit data report that for some oof the user facing this problem, the JOURNAL.lgf is not being executed until another user posts a journal and updated the previous journal.
    We will create the user ID's again
    Regards
    Dani
    Edited by: Daniel Sobrino on Feb 2, 2011 12:42 PM

Maybe you are looking for