Duplicate alias during ERPi metadata load

Hello All,
I am trying to load metadata to Hyperion Planning using ERPi from EBS GL. However, many of our descriptions may be same across accounts or other dimensions. In Planning, we generally combine member name plus description to create a unique alias. How can I combine account name and account description to load to load as alias in Hyperion Planning? I am on v11.1.2.2
TIA

duplicate post :- ODI - Hyperion Planning Metadata load issue
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

How to choose member position during ERPi metadata load ?

Dear All ,
We are using ERPi to load data and metadata from EBS to our target Hyperion Planning Application .
during metadata load , members set to be at the root of the dimension .
My question , How to choose where the extracted members to be placed at certain position at EPMA Hierarchy

What you would do is set up your load rule as a dim build too. First pass you would load the data file as a dim build adding unknown members to a default parent like "Unknown Members". Then second pass, load the file again as data load and all members will exist for load to complete successfully.

Duplicate records during master data loading.

hello guys,
I am reading one blog where the blogger wrote about 'Various issues in a BW Production project'.....I came across one issue which I couldnot understand...
Data loading failed due to Duplicate records during master data loading.......
Why do this error occur?How can we rectify this in a production environment?
Thanks and Regards,
S

Hi SChandx200 ,
May I ask where you get "Various issues in a BW production project"?
Many Thanks,

Scheduling ERPI metadata load rule

Hi,
I have an ERPI metadata load rule that I have to schedule. Are there ERPI APIs available for this? Is there a way to schedule the metadata loads?
Thanks.

This stands out to me
"Plan Type (FINANCE)] which has no corresponding column on the planning side."
If there definitely a plan type called FINANCE in application Main on vm-hypplantst0
Cheers
John
http://john-goodwin.blogspot.com/

ERPI Metadata load fails

Hi,
1. I am trying to load metadata to classic essbase application from peoplesoft using ERPI. The process fails with the below error.
ERPI Process Start, Process ID: 19
ERPI Logging Level: DEBUG (5)
ERPI Log File: C:\Windows\TEMP\/aif_19.log
Jython Version: 2.1
Java Platform: java1.4.2_08
COMM Dimension Pre-Processing - Multi Process Validation - START
COMM Dimension Pre-Processing - Multi Process Validation - END
Error in Start PS Load Dimension Members
java.lang.Exception: The scenario did not end properly.
When looked at ODI, the error is as below.
java.sql.SQLException: java.sql.SQLException: ORA-00001: unique constraint (TST_ERP.AIF_DIM_MEMBERS_STG_U1) violated
2. Chartfields in Peoplesoft does not have the hierarchy structure of parent child relationship. How will ERPi build the hierarchy in Hyperion if the chartfield do not contain the hierarchy structure.
Regards,
Ragav.

Jeff,
Thanks for response. I had opened an SR with oracle for this. It was a bug and the resolution is below. After this change, the process succeeds. However the metadata does not flow inside Hyperion Essbase application. Load method is classic. Do I need to configure any adapters for ERPI to work with Essbase?
SYMPTOMS
Issue Clarification
When running a metadata rule within ERPi for a PeopleSoft Source System the metadata rule fails. The ODI Operator shows that the "PS_GL_LOAD_DIMENSION_MEMBERS" process is failing at step 20 PS Extract Dimension Members.
java.sql.SQLException: ORA-00001: unique constraint (ERPINTEGRATOR.AIF_DIM_MEMBERS_STG_U1) violated
CAUSE
This caused a unique constraint exception as there were multiple records with the same "NAME" but with different EFFDT values in the AIF_PS_CF_METADATA table.
SOLUTION
Until the fix is included in the next service pack, the following update
statement can be run *after* every execution of the Initialize Source System
process on a PSFT source system:
UPDATE AIF_PS_CF_METADATA
SET EFFDT_FLAG = 'Y'
WHERE SOURCE_SYSTEM_ID = ?
AND EFFDT_FLAG = 'N'
AND (
(FIELDNAME = 'AFFILIATE_INTRA1' AND RECNAME = 'AFFINTRA1_VW')
OR (FIELDNAME = 'AFFILIATE_INTRA2' AND RECNAME = 'AFFINTRA2_VW')
Regards,
Ragav.

Metadata load using ERPi

Hi All,
I am new to ERPi, Our client is willing to implement ERPi Metadata load. The source is People soft 9.1 and the target Hyperion EPMA planning 11.1.2.2.300.20.
My source COA tree structure is different with my target Hyperion COA structure, can we implement metadata load using ERPi, if so how can we do it?.
and what are the considerations to be taken care in the metadata load.
Any thoughts on these would really appreciate your response. Thanks in advance.
Best regards,
Vishy

The response from support is correct.

HFM Metadata Loading On-going Problem

Hi There,
We just migrated to HFM 11.1.1.3 from HFM 4.
We used to have an issue in HFM 4 where almost everytime we loaded metadata, the system would hang and become unresponsive. The load screen would just sit there without ever completing the load. You could still use the system but the metadata load would never actually load. The only thing that would resolve it would be to reboot all of the HFM application servers.
This happened to us again the other day but now we're on the new HFM 11.1.1.3. Again, the resolution was to reboot the HFM applications. We tried just restarting the services on the various servers but that didn't work. A full reboot was required.
And nothing was wrong with the metadata itself as it quickly loaded without errors into our DEV and QA environments. As well, we kicked all of the users out of the system prior to the metadata load. Most get out immediately and certainly no heavy calculations or consolidations are being performed during the metadata load.
Has anyone else experienced this issue? Should a reboot always precede or accompany a metadata load? Is there any recommendation as to how often you should reboot the Hyperion servers (monthly, quarterly, etc.) as good practice?
Many Thanks,
Mike

We are having a similar issue with version 11.1.2.0.0
We try to run an application metadata load from the client and we get an error message
Unexpected error: 80005005 occurred.
Running the load from the workspace, we receive the following message.
An error has occurred. Please contact your administrator.
Show Details:
Error Reference Number: {F187C156-ABDA-40DD-A687-B471F35535E3};User Name: mpus54965@gsd1w105c
Num: 0x80004005;Type: 0;DTime: 4/27/2011 1:27:41 PM;Svr: GSD4W023C;File: CHsvMetadataLoadACV.cpp;Line: 347;Ver: 11.1.2.0.0.2762;
This is the second time we have encountered this problem. Oracle support was not able to determine the cause. The fix is to reboot the database server, but we are looking for insight to the problem. Note: Our current development environment is a single server virtual environment connected to a database server. We are planning to move to a more robust test environment with four applications and one database server in a few weeks.
Thanks for your help,

Ignoring duplicate Alias in the load rule

Hi,
Could anyone tell me how to ignore duplicate alias in the load rule while creating the dimension.
Thanks,
Ankoosh

There is no option in load rule to ignore the duplicate alias. Either you need to modify the source or make aliases as unique by appending member names etc..
Thanks,
Naveen Mikkilineni

FDM Metadata Load Method in ERPI

Hi,
Can anyone point me in the right documentation for how the FDM metadata load rule in ERPI works? I've read through the ERPI admin guide which gives the basics but I want to know more detailed information. If we have this method selected for our source Ebusiness system, do we still need to run the metadata rule everytime we need to run a data load into Planning ?
Thanks

You do not need to execute the metadata rule each time you do a load to PLanning. The Metadata Load Rule is used to load metadata from EBS into the target environment. What specifically are you looking for?

Metadata load during 24 hours and still has not finished

Hi all,
I have a problem with the metadata load on HFM 9.3.1.3
It seems it is running from about 24 hours.
it happened some time that the log has not been produced from the HFM client, but I always have found in the log that the metadata load had finsihed succesfully.
This time I have no clue that the dataload has completed.
I have performed some times ago the delete invalid record task, that completed succesfully.
Can some one tell me wich are the drivers that make the data load process last so long?
Regards, Andrea Zannetti.

Changes to the Entity or Currency dimensions can take far longer than changes to the Account, Custom, or Scenario dimensions. The reason for this lies primarily with the calc status tables, since changes to Entity or Currency require HFM to make changes including inserts to all of the CSE/CSN tables. Changes made to the Accounts or Customs do not require updates to the CSE/CSN tables.
Another common place for very long metadata loads lies with journals. The "Check integrity" box for metadata loads tells HFM to read through each and every journal and journal template in the entire application, checking to see whether even a single journal or template could become invalid if it allowed the metadata to be loaded. NEVER uncheck this, since once metadata has invalidated even one journal, you can never load metadata with the check in place afterward.
Another possibility is that metadata loads have to wait for all currently running data loads and consolidations to complete before the metadata load can start. Once it starts, subsequent data loads and consolidations have to wait for the metadata load to complete before they can start. This is to preserve data integrity.
One last place to look for long metadata load times comes with an application whose database is performing poorly, possible because of missing/broken/out of date indexes.
--Chris

Error during Olap metadata retrieval

Hi all,
We are getting the following error while trying to establish connection to the olap catalog to retrive olap metadata information for BI Beans
"Successfully connected to the Oracle database but failed to retrieve metadata.
Although the database connection succeeded,metadata in the OLAP Catalog is not
valid and could not be retrieved.In order to create OLAP queries against the
database,you must ensure that the OLAP Catalog metadata is valid."
On running the BI Beans configuration diagnostic utility we get the following error
<?xml version="1.0" encoding="UTF-8" ?>
<BICheckConfig version="1.0.0.0">
<Check key="JDEV_ORACLE_HOME" value="D:\JDev_57_Oct14Class"/>
<Check key="JAVA_HOME" value="D:\jdk1.3.1_04"/>
<Check key="JDeveloper version" value="9.0.3.998"/>
<Check key="BI Beans version" value="9.0.3.4.0"/>
<Check key="BI Beans internal version" value="2.7.0.11.3"/>
<Check key="host" value="ap950sun.us.oracle.com"/>
<Check key="port" value="1521"/>
<Check key="sid" value="HCXD2BI"/>
<Check key="user" value="hbi"/>
<Check key="Connecting to the database" value="Successful"/>
<Check key="JDBC driver version" value="9.2.0.1.0"/>
<Check key="JDBC JAR file location" value="D:\JDev_57_Oct14Class\jdbc\lib"/>
<Check key="Database version" value="9.2.0.2.0"/>
<Check key="OLAP Catalog version" value=""/>
<Check key="OLAP AW Engine version" value=""/>
<Check key="OLAP API Server version" value=""/>
<Check key="BI Beans Catalog version" value="N/A; not installed in hbi"/>
<Check key="OLAP API JAR file version" value="9.2"/>
<Check key="OLAP API JAR file location" value="D:\JDev_57_Oct14Class\jdev\lib\ext"/>
<Check key="OLAP API Metadata Load" value="Unsuccessful"/>
<Check key="Failure Point" value="MDMLoadFailed"/>
<Check key="StackTrace">
<![CDATA[
============================================================================
1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
1) An error occurred during olap API metadata retrieval. This is probably caused by inconsistent metadata.
============================================================================
oracle.express.idl.util.OlapiException
     at oracle.express.idl.ExpressConnectionModule.ConnectionInterfaceStub.getDefaultDatabase(ConnectionInterfaceStub.java:1465)
     at oracle.express.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:200)
     at oracle.express.mdm.MdmMetadataProvider.<init>(MdmMetadataProvider.java:187)
     at oracle.express.olapi.data.full.ExpressDataProvider.getDefaultMetadataProvider(ExpressDataProvider.java:549)
     at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.getMdmMetadataProvider(MDMMetadataDriverImpl_92.java:1134)
     at oracle.dss.metadataManager.server.drivers.mdm._92.MDMMetadataDriverImpl_92.attach(MDMMetadataDriverImpl_92.java:811)
     at oracle.dss.metadataManager.server.drivers.mdm.MDMMetadataDriverImpl.attach(MDMMetadataDriverImpl.java:133)
     at oracle.dss.metadataManager.server.MetadataManagerImpl.buildObjectModel(MetadataManagerImpl.java:1085)
     at oracle.dss.metadataManager.server.MetadataManagerImpl.attach(MetadataManagerImpl.java:962)
     at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:866)
     at oracle.dss.metadataManager.client.MetadataManager.attach(MetadataManager.java:792)
     at BICheckConfig.checkConnection(BICheckConfig.java:250)
     at BICheckConfig.main(BICheckConfig.java:1172)
]]>
</Check>
</BICheckConfig>
We are getting the same error for 2 different users.
We are using Jdeveloper 9.0.3 with BI Beans 9.0.3 and 9.2.0.2 database
Could someone help us with this.
Thanks in advance.
Nigel

Hi,
The issue here is if the whole catalog is corrupt or just one schema. So to try and determine the status of the catalog I would try:
1) Using OEM remove all the objects you created
2) I presume you created your database using the Database Configuration Assistant? You should have used the warehouse template
3) Make sure the following accounts are unlocked and also not expired : SH, OLAPSYS
4) Make sure the password for the SH schema is SH
5) Make sure the password for the OLAPSYS account is manager
6) Install the BIBDEMO schema that is shipped with BI Beans. This in the jdev_home/bibeans/bibdemo_schema
The installation process will remove SH schema from the OLAP catalog.
7)Once this is installed use JDeveloper to see if you can create a crosstab or graph.
8) If the BIBDEMO schema works try creating your new schemas one at a time.
9) Make sure the if you define the a dimension as type time it has END_DATE (column type DATE) and TIME_SPAN (column type number) defined. Otherwise don't define the dimension as type time.
Hope this helps
Keith Laker
Product Manager
Oracle Business Intelligence Beans

Getting Duplicate data Records error while loading the Master data.

Hi All,
We are getting Duplicate data Records error while loading the Profit centre Master data. Master data contains time dependent attributes.
the load is direct update. So i made it red and tried to reloaded from PSA even though it is throwing same error.
I checked in PSA. Showing red which records have same Profit centre.
Could any one give us any suggestions to resolve the issues please.
Thanks & Regards,
Raju

Hi Raju,
I assume there are no routines written in the update rules and also you ae directly loading the data from R/3 ( not from any ODS). If that is the case then it could be that, the data maintained in R/3 has overlapping time intervals (since time dependency of attributes is involved). Check your PSA if the same profit center has time intervals which over lap. In that case, you need to get this fixed in R/3. If there are no overlapping time intervals, you can simply increase the error tolerance limit in your info-package and repeat the load.
Hope this helps you.
Thanks & Regards,
Nithin Reddy.

Metadata Loads (.app) - What is best practice?

Dear All,
Our metadata scan and load duration is approximately 20 mins (full load using replace option). Business hfmadmin has suggested the option of partial dimension loads in an effort to speed up the loading process.
HFM System Admins prefer Metadata loads with replace option as there seems to less associated risk.
Using partial loads there appears to be risk to cross dimension integrity checking, changes are merged, potentially duplicating of members when moved in Hierarchy.
Are there any other risk with partial loads?
Which approach is considered best practice?

When we add new entities to our structure and load them with the merge option, they will always appear on the bottom of the structure. But when we use the replace option they will appear in the order that we want it. For us, and for the user friendlyness we always use the replace option. And for us the Metadata-load usually takes at least 35 minutes. Last time - 1.15...

Automated MetaData Load

Greetings,
I'm curious to know how some of the users in this forum perform automated metadata load against dimensions in the Shared Library (and subsequently against any EPMA Planning apps). We have several apps whose dimensions are shared amongst various Planning apps which are updated manually when the dataload fails because of missing members. These are updated manually on a monthly basis due to the relative mall number of missing members.
However, we are building an app with a dimension that is quite dynamic (a lot of new members are added and a few are deleted). This woud be insane to perform manually to update the Shared Library. Thus I'm looking for any suggestions on how to automate this via batch file or via any other means, including using "Create Member Properties".
Any suggestions or ideas would be greatly welcomed...
Many thanks.
cg

CG,
.err genrates only when
no proper names for member
no proper alise name .. while data loading...etc etc
These things can also be achived via some programing langague ... like java .. but u need to know all the possible error and your programme should be able to find out where it has gone wrong so that it can rebuild if any new member or child is missing via data load
unix > u can use SED functions to do that which will find and replace any possible outcomes
itb happen to me some time back where i used Java to replace some mmebr which used to get rejected while data loading .. but it was like specific butin ur case u have to know all possible outcomes ...

"MDL1223: Metadata Loader cannot be executed ..." error?

Hi folks,
Am getting this strange error from OMBPlus (11Gr2):
MDL1223: Metadata Loader cannot be executed while other user(s) are accessing the workspace.
when trying to import an MDL file, when using this statement:
catch {OMBIMPORT MDL_FILE '$projname.mdl'\
                            USE UPDATE_MODE\
                            CONTROL_FILE 'control.txt'\
                            OUTPUT LOG '$projname.log'} result
where the CONTROL_FILE (control.txt) simply has:
IGNOREUOID=Y
CONFIGPARAM=N
SINGLEUSER=Y
Am thinking that SINGLEUSER setting may have something to do with it? Have got an SR open with Oracle on it but no luck there so far - just wondering if anyone else has come across something like this...? Seems to certainly sound like a new 11G-ish/workspace-y kind of thing. Am really curious to know how to determine what users are currently accesing a workspace?
Thanks,
Jim

Hi Jim,
I would be the SINGLEUSER tag. In 11.1 and 11.2 you should connect using the USE SINGLE_USER_MODE option and remove the SINGLEUSER setting from the param file.
Regards,
John

Duplicate alias during ERPi metadata load

Similar Messages

Maybe you are looking for