Essbase Load Meta Data

Hello,
I am using the IKM - SQL to Hyperion Essbase (Meta Data). I am receiving an error that the RULES_FILE option is not valid. I am using the Default value of NULL. Is a RULES file required for the meta data updates to Essbase?
Thanks!

Yes you need to use a load rule for metadata loads.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Problem in loading meta data !!!!

Hi,
While creating metadata in IDX2, I am getting communication error 'Error when opening an RFC connection' .
I have created port SAP<SYSTEM ID> and client no & giving rfc des of sap system in idx1 . and while loading meta data i an getting above error .
I able to load meta data if i use other (non sap ) port eg abc and usng   rfc des of sap system . but idocs are not reaching xi
What are the steps we should do for loading metadata by using sap port i.e client .
Please help me solve this problem
Thanks,
Sridhar

HI
ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1)   Create an RFC Destination to the Sending System in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a)   Select create new button
b)   Enter the port name as SAP+SID (The starting char should be SAP)
c)   Enter the destination client
d)   Enter the RFC Destination created in SAP R/3 towards other system
e)   Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
                    SETTINGS IN SAP R/3
     We need to do the following settings in R/3
     Logon to Sap R/3 System
1)   Create an RFC Destination to XI in transaction code (SM59)
a)   Choose create
b)   Specify the name of the RFC destination
c)   Select connection type as 3 and save
d)   In the technical settings tab enter the details SAP SID/URL and system number#
e)   Enter the Gateway host as same details above SID/URL
f)   Gateway service is 3300+system number#
g)   In the Logon /Security tab, enter the client user & Password details of Destination system
h)   Test the connection and remote logon.Both must be succesful
2)   Create communication Port for Idoc processing Using Transaction(We21)
a)   First Select Transactional RFC and then click create button
b)   Enter the destination port name as SAP+SID (The starting char should be SAP)
d)   Enter the RFC Destination created in SAP R/3 towards other system.
e)   Save
3)   Create Partner Profile with Outbound Parameters (WE20)
a)   Create New
b)   Create the Partner no. name as same the logical system name of the destination system
c)   Select Partner type LS
d)   Enter details for Type: US/USER, Agent, and Lang
     Then Save
e)   Select Partner no. and LS which were create above
f)   Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g)   Select Message type
h)   Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I)   save
4)   In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
     and then assign logical systems
b)   Double click on Define the logical systems
c)   Give data for your Logicaal System and Name
d)   Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e)   Assign the logical system name to the client
5)   Create Customer Distribution model in the transaction code BD64
1)   Click on the Create modal View button and enter the short text, Technical name etc as shown below
2)   Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3)   Save the Distribution model
    Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
    It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
    Then, you will be intimated about the partners, port creation, and outbound parameters creation
4)   Distribute Customer Distribution Model
    In the menu item GO to Edit->Modal View-> Distribute to the destination client
    Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
PLZ REWARDS POINTS
VIKAS

Issue loading Meta Data for IDoc Type WPUKSR01 in XI Integration Repository

Hi,
I want to load the Meta Data for IDoc Type WPUKSR01 in XI Integration Repository out of BI. Unfortunately, this IDoc is not available in the IDoc List. I checked in BI and the IDoc Type is available in WE60 and WE30. Also, I can load the Meta Data for the Idoc in XI ABAP (IDX2).
Can someone tell me why the IDoc doesn't show up in XI Integration Repository Import Object List?
Thanks in advance.
Best Regards.
Alex

Hi Aamir,
The Idoc is released since Release 30A. I also tried to load the IDoc Meta Data from ERP with the same result: it does not show up in the list.
Thanks anyway.
Alex

Error in Loading Meta Data File for Service 'CL_ACCOUNTING_DOCUMENT_DP'

Hi Guys,
Need to your assistance in solving the below Error.
1. Error while loading metadata file for various service which required Connectors to be created .
Example : CL_ACCOUNTING_DOCUMENT_DP',
BEP
ZCB_COST_CENTER_SRV
1
Cost Center Service
CB_COST_CENTER_SRV
1
BEP
ZCB_GOODS_RECEIPT_SRV
1
Goods Receipt Service
CB_GOODS_RECEIPT_SRV
1
2. While Expanding the node for connectors in ESH_COCKPIT for SAPAPPLH . Below Error occurs
Could not rename Data Type "SIG_IL_USA_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "SIG_IL_SDR_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "SIG_IL_RES_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "SIGN_TYPE_UD_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "SIGN_TYPE_SM_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "SIGN_TYPE_RR_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "RMXTE_TRIALID_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QZUSMKZHL_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QWERKVORG_1" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QVNAME_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QVMENGE_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QVINSMK_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QVGRUPPE_2" in SWC EAAPPLH - errors occurred during renaming
Could not rename Data Type "QVEZAEHLER_2" in SWC EAAPPLH - errors occurred during renaming

Hi,
do you have solved this issue? We have the same problem with ESH_COCKPIT and SAPAPPLH component.
Regards,
Martin Sindlar

Loading IDOC meta data into Xi not working

Hello,
I'm trying to load IDOC meta data using trx IDX2 but the program is not able to recognize the port "SAPRD1_222" I previously defined in trx IDX1.
Any ideas, what Im missing here?
Ruud

Ruud,
Pls take a look of this thread:
Re: Importing Metadate from IDES 4.7 into Integration Server Rep

I use Windows XP. The problem now is that on two consecutive occasions when I open iTunes it either says the library is corrupt and creates a new one or will not load a previous one from the file. All my meta data and 2K songs are "missing".

Can I recreate my proper library with its 8700+ songs and a load of meta data from the iPod. Since two upgrades ago iTunes, for me, has become very unreliable.

Hi there caunsall!
I have an article for you that can help you re-create your iTunes library. That article can be found right here:
iTunes: How to re-create your iTunes library and playlists
http://support.apple.com/kb/ht1451
That article will walk you through all the steps to take care of re-creating your library. Take care, and thanks for visiting the Apple Support Communities.
-Braden

IDOC ADAPTER Issue, some meta data loads, some doesn't

Hey all,
I just started trying to setup the IDOC adapter connection between our R/3 system and our XI system. I decided to try and pull in some meta data via IDX2 to start. The weird thing is that I get some IDOC structures successfully, but not others. I think it has to do with some requirnments that I am missing on the R/3 side. For instance, outside of setting up the RFC connection, creating the tRFC port and the partner profile for the Logical system what else is needed. Do I have to assign the basic type to the outbound partner profile to access it? Do I have to actually create IDOCS for the basic type? Just curious. Here are the details of what I have done so far. A lot of this I pulled from other peoples postings here on the forum, I think I am just missing a few steps!
Our current configuration is as follows:
SAP R/3 Enterprise to post IDOCs to XI .
- R/3 Configuration:
logical system created: DXICLNT200
we20 : Partner Type LS: partner number: DXICLNT200.
we21 : IDOC Ports: Transactional RFC: Port name: DXICLNT200. IDOC record type SAP Release 4.x. RFC Destination : DXICLNT200
sm59 : create RFC destination : DXICLNT200. Target host: the XI box. Logon security: Client 200. XIAPPLUSER. PASSWORD (for XIAPPLUSER). Testing the connection works.
- XIHOST Configuration:
sm59 : created RFC destination to DDSCLNT210. Gateway options used, NO Client or User specified, are these needed, if so, is there a particular user to use.
Test connection works.
IDX1 : Created Port - DDSCLNT210. client 210. RFC destination DDSCLNT210.
IDX2 : Able to load metadata for IDoc Type CHRMAS01, of port DDSCLNT210. NOT ABLE TO IMPORT CREMAS03 or MATMAS03!
Any help is greatly apprciated!
Thanks,
Chris

There was a problem in the RFC connection, the target host was not populated correctly. All meta data can now be pulled.
However, I am curious about where the meta data for CHRMAS and CLSMAS came from. the RFC connection was NOT working, so where could it have pulled this information from????

Validate step retrieves ESSBASE target system meta data

Dear all,
for partucular reason we use for a specific dimension only *:* mappings.
This mapping causes that the validate step is always succesful for that dimension.
Sometimes we get an error during the export step, which says that the element does not exist in the ESSBASE meta data.
So, I we implemented a logic that is retrieving the imported elements in the target system ESSBASE meta data.
If they do not exist, the usre gets at the validate script an error pop-up.
more or less following logic:
          Set API.IntBlockMgr.IntegrationMgr.PobjIntegrate = BlOCKPROC.ActConnect("GetDimensionMembers")
          If API.IntBlockMgr.IntegrationMgr.PobjIntegrate.intResult Then
                    'Get the Dimension list
                    Set objR = BlOCKPROC.DimensionList(CStr("UD1"), 99)
                    If objR.lngListCount > 0 Then
                         Set RES.PobjXArray = DW.DBTools.fCreateXArrayDB()
                         RES.PobjXArray.LoadRows objR.varList
                         For lngDimCounter = 0 To objR.lngListCount
                              USERARRAY.Add UCase(RES.PobjXArray(lngDimCounter, 0)), UCase(RES.PobjXArray(lngDimCounter, 0))
MY ISSUE:
With the upper logic all leaf members are retrieved. Is it possible to retrieve (a subset) only a specific node an its children/children-children/etc. or tree
e.g. for this hierarchy only the recent members tree
DIMENSION
x Archived Members (not in Scope)
x Member1
x Member2
x Member3
x Recent Members (in Scope)
x Member5
x Member6
x Member7

yes you are right.
Unfortunately every FDM run would cause a large number o elements that have to be mapped. even it is a 1:1 mapping. -> a huge work
furthermore: FDM in standard does not catch the mapping only on specific (allowed) nodes in the essbase meta data.

How to integrate Oracle Ebs to FDQM to load the data to Essbase

Hi Experts,
I need a document regarding how to integrate Oracle EBS to FDQM.I am taking target as Essbase.I know how to integrate to HFM and loading the data to HFM.So please share me the document like How to get source file from E-Buisiness suite to load into Essbase.Pleaae share with an example
Thanks in advance

The following link:
http://docs.oracle.com/cd/E24674_01/epm.1112/fdm_adapter_readmes/es_g4_h_target_adapter_readme.html
You need to configure the target dimensions of Essbase within the Essbase adapter of FDQM.
For source integration of EBS, you have two options:
1. Use Oracle ERPI (ERP Integrator)
2. Make a custom data pump import script in FDQM to retrieve data from EBS database

Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)

Hi
We are using 10.1.3.6, and got the following error for just one of the thousands of transactions last night.
cannot end dataload. Essbase Error(1003050): Data Load Transaction Aborted With Error (1220000)
The data seems to have loaded, regardless of the error. Should we be concerned, and does this suggest something is not right somewhere?
Your assistance is appreciated.
Cheers

Hi John
Not using a load rule.
There were two other records which rejected based on absentee members. The error message was different for them, and easily fixed.
But this error doesn't tell us much. I will monitor the next run to see if the problem persists.
Thanks

IDoc meta data load problem in IDX2

I have been trying to load meta deta for some idocs and am getting message 'Basic type <idoc_type> is unknown'. Interesting to note is that I could load ECMMAS01 idoc type but other idoc types like MATMAS01 ..04, ORDERS01 ...04, DOCUMENT_LOAD01 ... and many others that I tried, I got the same message. The config has been done in IDX1 and IDX2 (that's how I got the ECMMAS01 in).
There is an OSS note '0000751839 IDoc Adapter: Basic type 'XYZ' is unknown. ' It seems we are already on that patch level. Can't verify if the note has been really applied or not for authorization issues for now. The note also mentions about a workaround to set the category level to '0' (i.e. blank) in the Integration server configuration. But that doesn't seem to help either.
Anyone else had this problem and resolved it?
Harshad

Problem stands resolved. I realized that the RFC destination in XI for the R/3 system had a problem. What still is not answered is how come I was able to import ECMMAS01?!?! One explanation could be that the RFC connection was ok then. Don't know, but I am happy that it works now.

SQL Interface - Error in Loading the data from SQL data source

Hello,
We have been using SQl data source for loading the dimensions and the data for so many years. Even using Essbase 11.1.1.0, it's been quite a while (more than one year). For the past few days,we are getting the below error when trying to load the data.
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Info(1021013)
ODBC Layer Error: [S1000] ==> [[DataDirect][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]CURSOR IDENTIFIED IN FETCH OR CLOSE STATEMENT
IS NOT OPEN (DIAG INFO: ).]
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Info(1021014)
ODBC Layer Error: Native Error code [4294966795]
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Error(1021001)
Failed to Establish Connection With SQL Database Server. See log for more information
[Mon Jan 10 11:02:56 2011]Local/{App Name}/{DB Name}/{User Id}/Error(1003050)
Data Load Transaction Aborted With Error [7]
[Mon Jan 10 11:02:56 2011]Local/{App Name}///Info(1013214)
Clear Active on User [Olapadm] Instance [1]
Interestingly, after the job fails thru our batch scheduler environment, when I run the same script that's being used in the batch scheduler, the job completes successfully.
Also, this is first time, I saw this kind of error message.
Appreciate any help or any suggestions to find a resolution. Thanks,

Hii Priya,
The reasons may be the file is open, the format/flatfile structure is not correct, the mapping/transfer structure may not be correct, presence of invalid characters/data inconsistency in the file, etc.
Check if the flatfile in .CSV format.
You have to save it in .CSV format for the flatfile loading to work.
Also check the connection issues between source system and BW or sometimes may be due to inactive update rules.
Refer
error 1
Find out the actual reason and let us know.
Hope this helps.
Regards,
Raghu.

Import Meta Data from CSV - Export Meta Data to CSV

Ability to import meta data into selected images from CSV file containing a number of fields, one of which is file name. The other fields would be selected tags to import.
Import logic would be, Where file name in column 1 matches current selected filename, then take following fields 2, 3, etc and import into Bridge.
Export selected meta data from selected files to CSV to form reverse of above to allow edit of data in Excel etc.
Further enchancement on import would be to allow instead of just filename, but date/time range matching.
Logic would be, Where date/time in column 1 is within X hours of selected
image creation date/time then import following fields into image meta data.
Useful for example if you already have a GPS tracklog in CSV and want to try and update images with GPS. Assuming camera clock approx same as GPS clock.

The issue was within the .csv file. There were duplicate records that were attempting to load as the ID value. After deleting the duplicate records, the transformation file ran successfully.
Debbie

Adaptor meta data &mapping templtes

hi
1. explain about adaptor meta data &mapping templtes what does use with them?
2.what is exchange fault data and exchange log data under data types
3.what are web as apart from 6.2 and 6.4?
4.describe about sap xi 3.0 like SP's what are types
5.about content
pls give details mentioned above .
thanks & regards

>>1. explain about adaptor meta data &mapping templtes what does use with them?
Adapter Metadata is the foundation configuration for the Adapters used in XI for message transfer. The functions provided allow either the creation of new Adapters or the modifications of existing ones.
Just like you can reuse data types in different message types, you can also save parts of message mappings as Mapping Templates and reuse them elsewhere. Once you have saved a mapping template it serves as a copy template that you can then load into other message mappings and modify to fit your requirements.
>>2.what is exchange fault data and exchange log data under data types
Fault message types contain data types defining application errors. Application errors are errors that occur on the inbound side of a message transfer when the application could not process successfully.
>>3.what are web as apart from 6.2 and 6.4?
The Web Application Server is a platform for efficient development and allows you to implement Web applications. It builds upon proven and stable application server
technology and Internet-based infrastructure from SAP.
>>4.describe about sap xi 3.0 like SP's what are types
check http://service.sap.com
>>5.about content
The contents of the Integration Repository are collectively known as XI Content (Process Integration Content); XI content is the integration knowledge that is required for describing collaborative processes (collaboration knowledge).
For an overview of the XI Content currently provided by SAP, see SAP Service Marketplace at http://service.sap.com/solutions -> SAP NetWeaver -> SAP NetWeaver in Detail -> Process Integration -> SAP Exchange Infrastructure -> SAP XI in Detail -> XI Content Catalog.

Error loading the data into cube

Hi All,
wen i am loading the data in the ASO Cube its giving warning but i did every thing correct yester day it was loaded correctly buttoday its not loading its giving warning ASO application ignore update to derived cells even i clear the data wats this error
so plz can any one help
Reading Rule SQL Information For Database accdb
Reading Rules From Rule Object For Database accdb
Parallel dataload enabled: [1] block prepare threads, [1] block write threads.
Aggregate storage applications ignore update to derived cells. 29 cells skipped
Data Load Elapsed Time with http://dataldcu.rul : http://0.094 seconds
Database import completed
Output columns prepared: [0]
Thanks
Ram

In ASO cubes you can only load data at level 0 (=leaf level). Every upload to aggregated dimension members are ignored. The warning message "ignore update to derived cells" is meaning that you are trying to load data at node level. As this is not possible with ASO cubes, essbase ignores that data.

Essbase Load Meta Data

Similar Messages

Maybe you are looking for