RUNLOGIC_PH

We have implemented RUNLOGIC_PH in out current BPC 10.0 SP05 version. It is working great. We migrated all our objects to HANA environment. I would like to know whether we can import the transport into the following HANA environment? Would it work or create any issues?
BPC 10.0 SP05
HANABPC 10.0 SP03
Compatibility with HANA DB 1.00.73

Hi
I know this thread is old, but I will try anyway.
We have the same landscape as you Ravi:
BW 7.4 SP09, CPMBPC 801 SP07 and BPC verison 10.0. The system is running on HANA.
Now we try to apply the HANA BPC 810, but it fails on the prereq saying its missing CPMBPC 810.
This is true, because we have CPMBPC 801.
If we try to upgrade CPMBPC from 801 to 810, SAINT will not find the Add-On.
How can we upgrade our version from 10.0 to 10.1 ?

Similar Messages

  • RUNLOGIC_PH implemented, Package runs successfully bu error showing Log

    Hello All,
    I have implemented RUNLOGIC_PH to call Main logic script in Profit Model. It all executes without any errors in UJKT as well as in Data Manager package.
    But when I try to see the details it shows the below error message
    model: PROFIT. Package status: SUCCESS
    Unable to contact the server. There was no endpoint listening at <Serverdetails>sap/bpc/files?method=preview&package_size=200.
    Framework message:
    The remote server returned an error: (404) Not Found.
    Please help.
    Many Thanks
    Krishna

    Dear Gresh,
    When we tried with SNOTE to implement this note, it says Note cannot be implemented. But in the Note, if I see I found some corrective instructions.
    CPMBPC 800 800 1359444. This suggests some changes in class CL_UJD_BPC_RUN_LOGIC method RUN.
    But all the corrective instructions are present in the RUN Method. Still it gives me the same error message.
    Unable to contact the server. There was no endpoint listening at http<ServerName>/sap/bpc/files?method=preview&package_size=200.
    Any clue please. All the Backend processign works fine.
    Thanks
    Krishna

  • Can we call default.lgf in BADI logic

    Hello All,
    can we call default.lgf logic script to run in the BPC in the BADI ? If yes then can someone please let me know the relevant Method or Class etc.
    For e.g. we have a BADi logic that does a data push from Profit model to Main model based on some conditions. After all this processing in the BADi and writes to Main model, there is a requirement to run the default logic which is there in Profit Model. Which I want to handle in BADI itself after processing the earlier BADI.
    If you need more details please let me know.
    Many Thanks
    Krishna

    Hi Vadim,
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = DEFAULT.LGF
    APPSET = UUG
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    DEFAULT.LGF has 2 logic scripts calling.
    *account.lgf
    *balance.lgf
    This only executes the first LGF and ignores the second one. I executed each one at a time and all works fine but if I give both together it executes first one in the sequence and ignores the other. Any idea why it is doing like that ??
    Try 1)
    *START_BADI TRANSPROFITTOMAIN
    QUERY = OFF
    WRITE = OFF
    *END_BADI
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = FLOW_BALANCE.LGF
    APPSET = <appset name>
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = CALCACCOUNT.LGF
    APPSET = <appset name>
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    it runs flow_balance.lgf and I can see the log for it..In the log it says the below
    SCRIPT RUNNING TIME IN TOTAL:109.42 s.
    LOG END TIME:2014-06-26 15:17:31
    Amount of time to run script:                                         110797.19 ms
    BADI EXECUTION TIME IN TOTAL :111233.64 ms.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:DATASRC WILL QUERY ON ALL BASE MEMBERS.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:INFLATION WILL QUERY ON ALL BASE MEMBERS.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:INTORDER WILL QUERY ON ALL BASE MEMBERS.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:PROFITCENTRE WILL QUERY ON ALL BASE MEMBERS.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:PROFIT_ACCOUNT WILL QUERY ON ALL BASE MEMBERS.
    [WARNING!] NO MEMBER SPECIFIED FOR DIMENSION:TIME WILL QUERY ON ALL BASE MEMBERS.
    EXECUTION BADI:RUNLOGIC_PH
    QUERY: OFF
    WRITE: ON
    Parameter DIMENSION not specified. ALL values used.
    Dimension ACCOUNT not specified and doesn't exist in current context.
    Error in RUNLOGIC call.
    BADI EXECUTION TIME IN TOTAL :2.07 ms.
    SCRIPT RUNNING TIME IN TOTAL:132.65 s.
    Please advise.
    individually they both work fine..meaning Try 2 and Try 3 works fine.
    Try 2)
    *START_BADI TRANSPROFITTOMAIN
    QUERY = OFF
    WRITE = OFF
    *END_BADI
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = CALCACCOUNT.LGF
    APPSET = <appset name>
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    Try 3)
    *START_BADI TRANSPROFITTOMAIN
    QUERY = OFF
    WRITE = OFF
    *END_BADI
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = FLOW_BALANCE.LGF
    APPSET = <appset name>
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    Try 4) Default.lgf contains 2 include statements
    *include FLOW_BALANCE.LGF
    *include calcaccount.LGF
    In this case it executes only the fist lgf in the sequence and ignores the other. I cant see anything in the log for the 2nd LGF.
    *START_BADI TRANSPROFITTOMAIN
    QUERY = OFF
    WRITE = OFF
    *END_BADI
    *START_BADI RUNLOGIC_PH
    QUERY = OFF
    WRITE = ON
    LOGIC = Default.LGF
    APPSET = <appset name>
    APP = MAIN
    DEBUG = OFF
    *END_BADI
    Thanks
    Krishna

  • 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

Maybe you are looking for