Concat member names in *REC statement

Hi Experts,
I am trying to generate a sql register with concatenated code.
e.g.
*REC(account=entity.id&category.id
If entity. id= company1 and category=actual
I would like to generate
account=company1actual
Is this possible to achieve something similar?
Regards

Dear Pablo.Ausin,
I has combined some words with member dimension in *REC function likes:
*REC(account= ABC + account.ID
Perhaps, you can change you case such as:
*REE( account=entity.id + category.id)
Kind Regards,
Wandi Sutandi
Edited by: wandi sutandi on Jan 20, 2011 6:07 AM

Similar Messages

Set dynamic member to dimension in *REC statement

BPC Experts,
Please refer to the below script logic . In this i wanted to pass the dynamic value to the BPC dimension. For the INPUT auditidm , i want to update different AUDITID value based on the dynamic selection in BPC . But the below script logic is throwing warning message and the dynamic value to the auditid is not considered, instead it uses the variable name itself while generating the records. I m using BPC 10 version SP Level 12.
*XDIM_MEMBERSET CATEGORY = %CATEGORY_SET%
*XDIM_MEMBERSET TIME = %TIME_SET%
*XDIM_MEMBERSET ACCOUNT = %ACCOUNT_SET%
*XDIM_MEMBERSET AUDITIDM= INPUT
*WHEN AUDITIDM
*IS *
*REC(EXPRESSION = %VALUE% * ($PER_INPUT$/100), AUDITIDM = $HLA_INPUT$ )
*ENDWHEN
*COMMIT
PROMPT(SELECT,,,,"CATEGORY,ACCOUNT,TIME,")
PROMPT(TEXT, %PER_INPUT%, "Input Percentage",,)
PROMPT(COMBOBOX, %HLA_INPUT%, "Select HLA AudiitID from the list",0,"HLA_01",{"HLA_02","HLA_03","HLA_04"},)
INFO(%EQU%,=)
INFO(%TAB%,;)
TASK(/CPMB/FX_RESTATMENT_LOGIC,SUSER,%USER%)
TASK(/CPMB/FX_RESTATMENT_LOGIC,SAPPSET,%APPSET%)
TASK(/CPMB/FX_RESTATMENT_LOGIC,SAPP,%APP%)
TASK(/CPMB/FX_RESTATMENT_LOGIC,SELECTION,%SELECTION%)
TASK(/CPMB/FX_RESTATMENT_LOGIC,REPLACEPARAM,PER_INPUT%EQU%%PER_INPUT%%TAB%,AUDITIDM%EQU%%HLA_INPUT%)
TASK(/CPMB/FX_RESTATMENT_LOGIC,LOGICFILENAME,HLA.LGF)
After the run package, warning messages shows
ENDWHEN ACCUMULATION: 1 RECORDS ARE GENERATED.
Invalid Members [AUDITIDM]=%HLA_INPUT%
How to pass dynamic value to the REC statement ? Please provide your inputs

TASK(/CPMB/FX_RESTATMENT_LOGIC,REPLACEPARAM,PER_INPUT%EQU%%PER_INPUT%
%TAB%,AUDITIDM%EQU%%HLA_INPUT%) -> you have given comma after %TAB% remove that and use HLA_INPUT not AUDITIDM
Correct:
TASK(/CPMB/FX_RESTATMENT_LOGIC,REPLACEPARAM,PER_INPUT%EQU%%PER_INPUT%
%TAB%HLA_INPUT%EQU%%HLA_INPUT%)
Also remove inverted comma in combo box.
Correct:
PROMPT(COMBOBOX, %HLA_INPUT%, "Select HLA AudiitID from the list",0,HLA_01,{HLA_01,HLA_02,HLA_03,HLA_04},)
Hope this helps..

REC Statement with IIF

Hi experts,
We are using SAP BPC 7.5 SP08. I have written a script logic wherein, i am dynamically populating the opening balance(CPLCLPTCOO) to the next month
*FOR %TIM_MEM%="2011.AUG","2011.SEP","2011.OCT","2011.NOV","2011.DEC","2012.JAN","2012.FEB","2012.MAR","2012.APR","2012.MAY","2012.JUN","2012.JUL"
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS CPLCLPTCOSA
*REC(EXPRESSION=[P_ACCT2].[CPLCLPTCOO]+[P_ACCT2].[CPLCLPTCOTOTP]-[P_ACCT2].[CPLCLPTCOTOTOF],P_ACCT2="CPLCLPTCOO",TIME=TIME.NEXT)
*ENDWHEN
*COMMIT
*NEXT
This code is working fine. However the problem comes when the user does not give any value in the input schedule for the member CPLCLPTCOSA in one month but gives it for subsequent months. For this i tried modifying the scipt logic as
*FOR %TIM_MEM%="2011.AUG","2011.SEP","2011.OCT","2011.NOV","2011.DEC","2012.JAN","2012.FEB","2012.MAR","2012.APR","2012.MAY","2012.JUN","2012.JUL"
*XDIM_MEMBERSET TIME =%TIM_MEM%
*REC(EXPRESSION=IIF([P_ACCT2].[CPLCLPTCOSA]=0,[P_ACCT2].[CPLCLPTCOO][P_ACCT2].[CPLCLPTCOTOTP]-[P_ACCT2].[CPLCLPTCOTOTOF],[P_ACCT2].[CPLCLPTCOO][P_ACCT2].[CPLCLPTCOTOTP]-[P_ACCT2].[CPLCLPTCOTOTOF]),P_ACCT2="CPLCLPTCOO",TIME=TIME.NEXT)
*COMMIT
*NEXT
However, this code doesnot work as it is giving a validation error "Invalid dimemnsion name "[P_ACCT2].[CPLCLPTCOSA" in application PLANNING"
Can you please help me out on how i can include an IIF statement in a REC statement.
Thanks in advance
Edited by: Appu Del on Dec 30, 2011 4:36 PM

place *WHEN_REF_DATA = MASTER_DATA at the beginning .Try this statement with 1 st code . Do not try with 2 ed code . it has lot of syntax errors.
*WHEN_REF_DATA = MASTER_DATA
*FOR %TIM_MEM%="2011.AUG","2011.SEP","2011.OCT","2011.NOV","2011.DEC","2012.JAN","2012.FEB","2012.MAR","2012.APR","2012.MAY","2012.JUN","2012.JUL"
*XDIM_MEMBERSET TIME =%TIM_MEM%
*WHEN P_ACCT2
*IS CPLCLPTCOSA
*REC(EXPRESSION= ([P_ACCT2].[CPLCLPTCOSA]>0 )*([P_ACCT2].[CPLCLPTCOO]+[P_ACCT2].[CPLCLPTCOTOTP]-[P_ACCT2].[CPLCLPTCOTOTOF]) + ([P_ACCT2].[CPLCLPTCOSA]<0 )* (calculation if there is no value in CPLCLPTCOSA) ,P_ACCT2="CPLCLPTCOO",TIME=TIME.NEXT)
*ENDWHEN
*COMMIT
*NEXT
Hope this helps.

Script Logic: Using a property in MDX *REC statement (BPC NW)

Hi,
Is it possible to use a Property in an MDX statement without using *LOOKUP() function? I have script successfully working but it takes 15 minutes to execute and would like to speed it up.
I understand that [DIMENSION].[MEMBER].Property is not valid syntax, and do not believe NW has any other functions to resolve the issue, except *LOOKUP which takes a long time.
Specific Example is below:
I have a piece of script that successfully splits JV Expense by customers. A Profit Share planning driver determines the percentage that each customer is entitled to. Typically this will be 100%, but could be 50% between two customers.
The PROFIT SHARE planning drivers records, and PARTNER_INCOME transactional records are below:
ACCOUNT
ENTITY
PARTNER
SIGNED DATA
PROFIT_SHARE
UK_001
PARTNER_A
0.5
PROFIT_SHARE
UK_001
PARTNER_B
0.5
PROFIT_SHARE
UK_002_PLANNING_DRIVERS
PARTNER_B
1.00
PARTNER_INCOME
UK_001
NO_PARTNER
$5,000
PARTNER_INCOME
UK_002
NO_PARTNER
$5,000
UK_001 has two partners that are each entitled to 50% of the $5,000 NET PROFIT.
For UK_002, one one single Partner is entitled to 100% of the $5,000 NET PROFIT.
Using script logic, you can scope the Profit Share account (PROFIT_SHARE) - , and use a *REC statement to multiply this by the driver. It would look like:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*REC (EXPRESSION = %VALUE% * ([ACCOUNT].[PROFIT_SHARE],[PARTNER].[NO_PARTNER]), ACCOUNT = PARTNER_PROFIT_SHARE)
*ENDWHEN
This wouldn't be a problem if the Planning Driver is always stored on the same Entity that the Income is stored on, but for UK_002, the planning driver is stored on another Entity - which is stored in a the PLAN_DRIVER_REF property of the entity. It should use UK_002_PLAN_DRIVERS
ID (Entity)
PLAN_DRIVER_REF
UK_001
UK_002
UK_002_PLAN_DRIVERS
UK_002_PLANNING_DRIVERS
In this scenario, we need to switch out the Entity used in the MDX, however I do not believe you can use a property in MDX - can anyone confirm?
I have currently implemented the *LOOKUP functionality to loop through, changing each *LOOKUP partner for each loop.
Lookup:
*LOOKUP PLANNING_JV_US
*FOR %LOOP_ASLS% = %ASL_LOOKUP_LOOP_VARIABLE%
*DIM LOOK_%LOOP_PARTNERS%:ACCOUNT = "PROFIT_SHARE"
*DIM LOOK_%LOOP_PARTNERS%:PARTNER= %LOOP_PARTNERS%
*NEXT
*DIM ENTITY = ENTITY.PLAN_DRIVER_REF                   //   Use PLAN_DRIVER_REF Property of Entity
*ENDLOOKUP
Scope and *REC:
*XDIM_MEMBERSET ACCOUNT = PROFIT_SHARE
*WHEN ACCOUNT
IS *
*FOR %LOOP_PARTNERS% = %PARTNER_LOOKUP_LOOP_VARIABLE%      // 1000 Partners
*REC(EXPRESSION = %VALUE% * LOOKUP(LOOK_%LOOP_PARTNERS%), PARTNER= %LOOP_PARTNERS%, ACCOUNT = TCOJVSHAR_CALC, AUDIT_ID = PP_EXPENSE_BY_PARTNER)
*NEXT
*ENDWHEN
The problem with the above, is that because the Lookup is being generated for every single Partner, there are significant numbers of loops.
Does anyone know of another way this can be implemented in Script Logic? Otherwise we'll need to explore BAdI route.
Thanks,
Nick

Hi Nick,
Use property in LOOKUP - will dramatically speed up the calculation without FOR/NEXT.
Vadim

List of avaliable MDX properties / Always show member name instead of alias

Hi all,
does anyone know if there is a list of ALL available MDX properties which can be used in an MDX query with Essbase?
There is a very small list in the technical documentation (http://docs.oracle.com/cd/E12825_01/epm.111/esb_techref/mdx_properties.htm), however I know there are a lot more properties.
E.g. one property which is not documented is ANCESTOR_NAMES:
WITH MEMBER [Year].[dummy] AS '0', SOLVE_ORDER = 0
SELECT {[Year].[dummy]} on columns,
[Account].Members properties ANCESTOR_NAMES on rows
FROM [App.Db];
Anyone knows if there is such a list?
And another question:
The Query always brings up the alias of the members (e.g. [Account].Members). Is there a way that per default the member name instead of the alias is used? Without using the MEMBER_NAME property?
Essbase version: 11.1.1.3
Thanks
Th

amaerki wrote:
For the second question regarding the member name try the following statement in a MaxL session:
alter session set dml_output alias off;works like a charm, many thanks.
Anyone an idea on the list of properties?
Edit: found something related to XMLA: http://docs.oracle.com/cd/E12825_01/epm.111/aps_admin/ch03s03s07.html
However, e.g. the porperty PARENT_UNIQUE_NAME does not work. Also the Book MDX solutions has a list with it with e.g. PARENT_UNIQUE_NAME specified which does not work...
Anyone an idea how to get a list of all properties valid with MDX using Essbase?

Can we use Aliases instead of member name in Calc Manager

We migrated business rules to Calc Manager. After migration Calc Managers are not getting validated (stating the member is missing in the database). Later found out that in the script it has alias name instead of member name which was causing this error.
example
Member name = C001
Alias = Texas
in the script it is mentioned Texas = 5; (this statement throws an error while validating, stating Texas is not present in the outline, even though Texas is present in the Alias table as an alias for C001).
Once I modify the script to C001 = 5; it gets validated without any issue.
Does this mean in Calc Manager we cannot use Aliases unlike business rules and Calc Scripts?
Please advice.

The 'Defects Fixed' section of the release notes for 11.1.2 includes...
"Calculation scripts validate inconsistently in Essbase and Calculation Manager (8800397)."
...which is pretty broad!
Can you run the rules OK? If so, I'd just ignore the Calculation Manager validation message.

Dynamic tuple expression in *REC statement

Hi there,
I think I know the answer to this already, but here goes...
I need to use a tuple expression in a *REC statement (in place of the old-fashioned GET) but I want it to be dynamic, so at least one of the tuple members changes at runtime.
To use the basic example from SAP Help, but amended slightly, let's say this is the standard expression:
*XDIM_MEMBERSET P_ACCT = CE0004010,CE0652000
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/([P_ACCT].[CE0652000],[P_ACTIVITY].[LABPRD],[P_ENTITY].[E123]), P_ACCT="CE0661000")
*ENDWHENBut what if the P_ENTITY member should be dynamic, depending on the ENTITY member the user selects in the DM package? What I WANT to do is something like this:
*XDIM_MEMBERSET P_ACCT = CE0004010,CE0652000
*WHEN P_ACCT
*IS "CE0004010"
*REC(EXPRESSION=%VALUE%/([P_ACCT].[CE0652000],[P_ACTIVITY].[LABPRD],[P_ENTITY].[%ENTITY_SET%]), P_ACCT="CE0661000")
*ENDWHEN
...but it doesn't work. Is this even possible? And if so, what am I doing wrong?
Thanks very much,
Jason
PS. I'm already using a lookup to pull out a tax% in the same script, so I can't use it for this as well...

Some theory:
You have some scope at the script start (defined by user selection in DM prompt)
For each dimension you have variable %SOMEDIM_SET% containing initial script scope. If you change scope of some dimension using *XDIM_MEMBERSET SOMEDIM=MEM1,... you can always later restore original scope with *XDIM_MEMBERSET SOMEDIM=%SOMEDIM_SET%
WHEN/ENDWHEN will loop records with base members of the scope before WHEN. %VALUE% is a current record value.
You can use tuple references to other members in EXPRESSION=... Dimensions not defined in tuple will have the same base member as current record. In tuple you can also use parent members.
You can use LOOKUP as a replacement of FLD to get member from the property of the member in current record. LOOKUP can get data from current model or other model.
Vadim

Reading data from a text file into PAS - Dimension member names truncated

Hi,
I created a procedure to dump variables and data into a text file to load into another model. I used a semicolon as a field seperator.
The data, measures and dimension members are dumped properly into a text file and no dimension member names are truncated .
However when I read the data into a measure, and I issue a peek command, dimension meber names are read in truncated
and remain full names in the text file. Any reason for this? What do I need to do to prevent this from happening?
THanks.
Lungile

Hi Lungile,
The problem that you're likely having is that you haven't created a file description for the file from which you're reading. When loading data into Application Server from a text file, you would normally go through three steps:
1. Enter the ACCESS EXTERNAL subsystem
2. Specify the name of the file to be read
3. Specify the format of the file field names, types, widths, and positions.
If you go into the Application Server help, select "Application Server Help", then "Application Server at the command level", then "Variables and reading in data", and then "Reading an external file", you will have the process of the steps you need to follow outlined for you, including links to the help topic for each command you need to issue.
So what I think you need to do is use the DESCRIPTION command to specify the names of your fields, their type, and also their width, in order to ensure no truncation of data on the load.
The same DESCRIPTION statement is required if you want to use your text file as the source of a dimension.
Hope this helps,
Robert

Specify schema name in select statements

Is there a way to specify the schema name for the connection so that I don't have to specify schema name with every statement?
Currently I am executing the statement:
Statement stmt = null;
ResultSet rs = null;
String getAllNames =
"SELECT NAME FROM " + schemaName +".NAMES " + schemaName +" WHERE STATUS_CODE != 12 ";
stmt = conn.createStatement();
rs = stmt.executeQuery(getAllNames);
But I have a lot of such statements, a few which uses parameters.
Is there a way I can specify the schemaName once and for all so that I don't have to perform string concat everytime the function is invoked.

well I tried that, since the application runs under CICS which uses the trusted connection with DB2, all CICS application will be using the same userid and there is no way to ensure that other applications would not be using the same table name in some other application. So the only option I have is to specify the schema name with the select statements but I don't want to append the schema name with each statement.

Using properties in a *REC statement

Hi
I want to copy the result of a cost center allocation from the source cost center profit center to the destination cost center profit center. We use a property on the cost center dimension to define the profit center of the cost center.
I first use *RUN ALLOCATION to generate the cost center allocation results but I then need to copy the results to the right profit center. I have written the following code to do this which validates successfully:
*WHEN ACCOUNT
*IS A10000
*REC(PROFITCENTER=COSTCENTER.PROFITCENTER)
*ENDWHEN
However when I run it I receive the following error message:
'RUN_LOGIC Property value not found'
Does anybody know whether it is possible to use properties in *REC statements and if so how I should write the logic?
Kind Regards
Wayne

Hi,
Try following code. However you should be sure that all the profitcenter property members of costcenter exist in profitcenter dimension members. For example if you have a member of costcenter like na_cc and if property profitcenter of this member is blank, this code doesnt work. So you have to add a XDIM_MEMBERSET.
XDIM_MEMBERSET COSTCENTER <,> NA_CC or
XDIM_MEMBERSET COSTCENTER = BAS(CC)
*WHEN ACCOUNT
*IS A10000
*REC(FACTOR=1, PROFITCENTER=COSTCENTER.PROFITCENTER)
*ENDWHEN
Hope this helps.

Concatenate property with two other dimension values in REC statement

Greetings,
I am attempting to concatenate a member property with two member values to create a this dimension member ID in a REC statement, as in the example:
*REC(FACTOR=1, COSTCENTER = PROFITCENTER.PCID + %DEPARTMENT% + %COMPANY%)
So the COSTCENTER member is the concatenation of the PCID property of the current PROFTCENTER member and the ID of the current DEPARTMENT member and the ID of the current COMPANY member.
I appreciate your help.
Regards,
Craig
P.S. This syntax works fine in the Microsoft version
Edited by: Craig Tennant on Oct 27, 2010 9:58 AM

Gersh,
I have tried:
*REC(FACTOR=1, COSTCENTER = [PROFITCENTER].PCID %DEPARTMENT%) //PROFITCENTER has brackets around it and there is a space between the two.
When I validate and save it tells me "Attribute PCID%DEPARTMENT% does not exist in dimension PROFITCENTER"
*REC(FACTOR=1, COSTCENTER = [PROFITCENTER].PCID_%DEPARTMENT%) //PROFITCENTER has brackets and there is an underscore between the two.
When I valiudate and save it tells me "Attribute PCID_%DEPARTMENT% does not exist in dimension PROFITCENTER"
*REC(FACTOR=1, COSTCENTER = [PROFITCENTER].PCID [DEPARTMENT].ID) //PROFITCENTER and DEPARTMENT have brackets around them and there is a space between the two.
When I validate and save it tells me "Member [PROFTCENTER].PCID[ does not exist"
*REC(FACTOR=1, COSTCENTER = [PROFITCENTER].PCID_[DEPARTMENT].ID) //PROFITCENTER and DEPARTMENT have brackets around them and there is an underscore between the two.
When I validate and save it tells me "Member [PROFTCENTER].PCID[_ does not exist"
Again I appreciate your help and insight
Cheers,
Craig

Duplicate member names in member formulae

How do you reference duplicate member names in a member formulae? In Excel or dimension building you say i.e. [TEST].[test1]. That format doesn't work in member formulae. Is anyone using duplicate name? If you do, maybe you have an answer.

In System 9 databases, you can use a "duplicate member name" outline, in which case when you have the same member name more than once in an outline, Essbase automatically tells them apart. For example, you could have a Gen3 member named "New York" with a child named "New York", or many different states with children named "Springfield", for example. Or you could have a product code named "100" and also a customer code named "100". You don't have any control over how the names are constructed, and unfortunately the automatically-generated name for a member may change if a duplicate for it is introduced in the outline, so you really don't want to use the "unique name" values returned from API calls. You can always refer to them by using a full ancestor path, like this: [Geography].[East].[New York].[New York] I don't know for sure but I would imagine the same is true in calc scripts and non-MDX member formulas: "Geography"."East"."New York"."New York" HTH

Duplicate member names 9.3.1

The planning documentation seems to suggest that duplicate member names can occur in Planning 9.3.1 although I have seen a post ~(Nov 2007) on here that states that this won't be available until 9.5.
Is this still the case?
If not, is there any documentation showing how this can be achieved from within bpma/planning? It all seems to suggest it is done in Essbase but that leaves me in a chicken and egg situation as I can't deploy it to essbase with duplicates.
Cheers

Ok guys, back on this issue.
If I wanted to model the following hierarchy in Planning, given the absence of the duplicate members facility, how would you go about it?
Group - Product
Cars - Wheel
Cars - Seat
Cars - Window
Vans - Wheel
Vans - Seat
etc
where all products are not shared and must be able to accept individual values. This is a simple example so creating another dimension isn't an option.
This is a very real requirement and I'm wondering whether I'm missing something very obvious here. Are we really limited to planning hierarchies where duplicate product names are not used? Am I going about this in the wrong way?
Any guidance on how I should be solving this problem greatly appreciated.
Regards

MDX member names

When I run an MDX query it returns aliases...how can I return member names?
Thanks,
er

You’re not going to be happy with the way it looks.
SELECT{[Year]} ON AXIS(0),
{[Product].members} PROPERTIES [MEMBER_NAME] on AXIS(1)
FROM Sample.Basic
As Spofford points out in his book, “While the values of the properties requested with the PROPERTIES statement in an MDX query are returned, along with all other result information in the result data structures, it is up to the client application to retrieve and utilize this information.”
I haven’t been able to come up with a cleaner way to do it. MDX really isn’t a report language, its one step below a reporting language, so it has a number of limitations on how the data looks when you pull it and defers to the front end application pulling the data.

Renaming Existing Member Names

We are trying to do a long list of outline Member name changes (~200 changes) for Level 0 or Parent Level members and noticed the API function ESBOTLRENAMEMEMBER . It looks like this could be used by others and have seen several Threads in OTN talking about the function, but I haven't seen any posts pointing to a working Excel VBA to do a Find/Replace with this function. Can Anyone point to a working VBA code to do a find/ replace?
what I am trying to do is have a worksheet with a "Original Names" and a column with "New Names" and have the code to a loop through the list.
This sounds like a basic task that many folks could use. Does anyone have something similar that they have created?
Thanks ahead of time!
Robert

I was doing exactly this recently with a 9.3.1 ASO cube. The forum will screw up the formatting but you can probably work out what's going on. Note the ???? placeholder for the number of lines and placeholders for APPNAME etc. This is very basic and features no error trapping - it was for a one time deal in a development environment, not regular and / or production use.
Any use is entirely at your own risk.
Good luck!
============================
Public Sub UpdateOutline()
Dim Init As ESB_INIT_T
Dim ObjDef As ESB_OBJDEF_T
Dim ProcState As ESB_PROCSTATE_T
Dim lngCount As Long
Dim strOldName As String
Dim strNewName As String
Dim lngInst As Long
Dim lngCtx As Long
Dim lngStatus As Long
Dim lngOutline As Long
Dim lngMember As Long
Dim intItems As Integer
'Init API
Init.Version = ESB_API_VERSION
lngStatus = EsbInit(Init, lngInst)
'Log in
lngStatus = EsbLogin(lngInst, "SERVER", "USERNAME", "PASSWORD", intItems, lngCtx)
'Open the outline
lngStatus = EsbSetActive(lngCtx, "APPNAME", "DBNAME", intItems)
With ObjDef
.AppName = "APPNAME"
.DbName = "DBNAME"
.FileName = "DBNAME"
.hCtx = lngCtx
.Type = ESB_OBJTYPE_OUTLINE
End With
lngStatus = EsbOtlOpenOutline(lngCtx, ObjDef, ESB_YES, ESB_YES, lngOutline)
'Loop through all members in the sheet
For lngCount = 1 To ????
strNewName = ActiveSheet.Cells(lngCount, 1)
strOldName = ActiveSheet.Cells(lngCount, 2)
lngStatus = EsbOtlFindMember(lngOutline, strOldName, lngMember)
lngStatus = EsbOtlRenameMember(lngOutline, lngMember, strNewName)
Next
'Write the outline
lngStatus = EsbOtlWriteOutline(lngOutline, ObjDef)
'Restructure
lngStatus = EsbOtlRestructure(lngCtx, ESB_DOR_ALLDATA)
'Call EsbGetProcessState until completed
lngStatus = EsbGetProcessState(lngCtx, ProcState)
While ProcState.State <> ESB_STATE_DONE
Application.Wait DateAdd("s", 10, Now())
lngStatus = EsbGetProcessState(lngCtx, ProcState)
Wend
'Unlock the outline
lngStatus = EsbUnlockObject(lngCtx, ESB_OBJTYPE_OUTLINE, "APPNAME", "DBNAME", "DBNAME")
'Close the outline
lngStatus = EsbOtlCloseOutline(lngOutline)
'Log out of server
lngStatus = EsbLogout(lngCtx)
'Terminate API instance
lngStatus = EsbTerm(lngInst)
End Sub

Concat member names in *REC statement

Similar Messages

Maybe you are looking for