EIS - AIS conversion

Has anyone successfully exported EIS models from 7.1.2 into 9.3? I've tried to do 5 models and all of them crash the AIS console when I try to open the imported model. If I import a model, it will allow me to export it, and there are differences with the new file having
Desc= "" or
extractionrule=""
or
staticvalue=""

Thanks for the reply.Actually i need the installation guide for release 6.5.7

Similar Messages

EIS/AIS [Essbase Integration Service] and SHARED SERVICES

I got the following error message when trying to get Shared Services Connection with integarion server:
Error -1: Contact your AIS administrator because the Java runtime
environment may not be set appropriately on the server machine…
Exception in thread "main" java.lang.NoSuchMethodError:
com.hyperion.interop.lib.Repository.createProject
(Ljava/lang/String;Ljava/lang/String;)Lcom/hyperio n/interop/lib/ProjectResource; at eieapi.eieapis.createProject(eieapis.java:150)
can you help me how to reslove this issue...

"Lcom/hyperio n/interop/lib/ProjectResource;"
^-- did you create a variable that contains a blank space? --> "hyperio n"

Inserting the Brio Query Data into EIS OLAP Model tables directly

Dear Experts,
Can someone please suggest how we can export data (result set records) from bqy files' queries into an EIS server's OLAP Model's tables?
Right now I have a cube on Essbase server getting the data from excel sheets which store the data from the execution of .bqy files.
Use of file system (excel sheets) has not been liked by my business users so now I need to avoid storing the data from brio queries into excel sheets for loading into the Essbase cube. This I am required to achieve using EIS/AIS so that the data from brio queries(.bqy files) can be directly inserted into Essbase cube with the help of (i.e. via) EIS/AIS.
Any quick help would boost the life of this project of mine.
Thank you,
Vikas Jain

user12072290 wrote:
Dear Experts,
Can someone please suggest how we can export data (result set records) from bqy files' queries into an EIS server's OLAP Model's tables?
Right now I have a cube on Essbase server getting the data from excel sheets which store the data from the execution of .bqy files.
Use of <A class=bodylinkwhite href="http://www.software-to-convert.com/h264-conversion-software/h264-to-quicktime-software.html">file</A> system (excel sheets) has not been liked by my business users so now I need to avoid storing the data from brio queries into excel sheets for loading into the Essbase cube. This I am required to achieve using EIS/AIS so that the data from brio queries(.bqy files) can be directly inserted into Essbase cube with the help of (i.e. via) EIS/AIS.
Any quick help would boost the life of this project of mine.
Thank you,
Vikas JainHave you got the answer? Would you pls post it here?

EIS load kickouts handling to an "unassigned" parent bucket

Hello, a question for the Essbase EIS/AIS pros out there. Is it possible and if so, where in the EIS GUI could I specify where to drop a given dimension member record kickout during EIS the member load? For example, if I created an "Unassigned" parent member in a couple of major DIMS (accounts and locations, for example) each and wants any kickout goes there instead of the usual text file, how'd would I do that? Thanks.

Currently you would have to use another product to do this, namely your relational database. This is a documented feature for EIS, however it doesn't work correctly. I opened a trouble ticket, after months of going back and forth proving it was in fact a defect, they admitted it was a defect. However, since I am on version 7x and there are no patch releases set for version 7, I would have to pay to move to System 9 to get this feature. Actually, as far as I know it's not working properly in System 9 either, but at least if I was on System 9 they would have to commit to a patch. I work around this in my relational database. It's a pain, but it works. To answer your question specifically, if the feature worked properly you would set it by going into your meta-outline, right clicking on the dimension in question, go to the 'Outline build' tab and enable the default misc member.

AIS freezes when trying to create a new metadata catalog

Hi,
I'm really new in EIS/AIS. We are using EIS and Essbase version 9.3.1. I just created a new odbc connection to our data warehouse (Oracle in OraHome92). I tried to create a new catalog but EIS freezes. When I tried to "end task" the console, it closes and would get a message "olapbldr error". Need to know how to fix this. Any help would be greatly appreciated.

Hi,
I'm really new in EIS/AIS. We are using EIS and Essbase version 9.3.1. I just created a new odbc connection to our data warehouse (Oracle in OraHome92). I tried to create a new catalog but EIS freezes. When I tried to "end task" the console, it closes and would get a message "olapbldr error". Need to know how to fix this. Any help would be greatly appreciated.

Cannot generate/find dataload.txt

I'm having some records being rejected during data load of a cube via AIS. I want to be able to see which records are rejected, so I looked for the dataload.txt file in the LoadInfo directory. No dataload.txt is being generated in this directory after my load. I have edited the start.bat file to include a "-L0" in the appropriate place per the AIS documentation, and done a reload after restarting the AIS server, but no cigar. I have also inserted a "[L]=0" in ais.cfg, but this doesn't seem to have any effect either..
Would appreciate any advise on how to generate/locate the dataload.txt file for my loads.
thanks,
Axe

Hi Axe,
In EIS/AIS, after completion of member/data load, if we get to see the msg. box saying- "*Data load terminated with errors*", then- AIS won't generate the rejection dataload.txt file in loadinfo. In this case, the only way to check what went wrong is- To open the log file (either from the same dialog box OR navigating AIS folder, log -> olapisvr.log).
Let me know incase of any further questions.
- Natesh

Cubes in Hyperion

Hi all,
I am very new to Hyperion Essbase. I am trying to create cubes in hyperion. What I saw is I can create multiple 'metaoutlines'with a single 'olap model' in hyperion integration service console. I made a single cube an loaded in essbase server through Intergretion services and I can acces that cube through admin service console/excel addins.But I am not getting that how to create multiple cubes(e.g- sales, out of stock ..) in hyperion and how can I access those differently?
Thx sai

To understand fully, I would suggest taking the EIS/AIS class, but the short answer is create multiple metadata outlines from the one model pointing to different cubes. Select the hierarchies you want in each cube and which accounts

HFM to Essbase \ Planning via EA and EIS or AIS, whatever it is today..

Have HFM data and metadata being spilled into the EA repository...pretty good using taskflow... Now for the getting into Essbase \ Planning....
How do you decipher what HFM is dumping to the repository into something useful? Going to go down the path of AIS possibly use HAL to get it into planning but don't know where to start. If anyone is willing to point me in the right direction, would be grateful. If you would be willing to share any examples or tips \ tricks, that would be great also!
9.2.0.2 about to be 9.2.0.3
Thank you!

Where does the data go missing? i.e. Is there data at the Import, Validate, Export steps but no export file is produced or, for instance is no data imported at the import step. It should be pretty ovbvious at which stage the data is lost.

Error while verifying the sample application in AIS 9.3

Hi All,
I am getting an error "Physical table TBC.sales does not exist" similar error for all other tables. Any one got similar error while creating sample application in AIS.
Thanks
Sudheer.T

Hi
The reason might be probably because of not properly configuring the Catalogue to the database during the installation.
During the installation of EIS, you will be asked to give specific database details where the AIS can store the metadata of sample applications of the model and metaoutline. If the database login credentials fail or, now while opening the model, if u are referring to other database/ with other credentials who essentially donot have access to those tables, you might get this error.
So, please check with configuring the AIS associated Database and Catalogue that you are referring to.
Regards
Puliga

Conversion Agent; NameNotFoundException

Hi Guy,
A similar discussion, might be helpful --
Re: Conversion Agent Error in Adapter Module ?
Regards,
Neetesh

Hi Nateesh,
Than ks for your reply. Min eis indeed the same symptom, but not the same cause. Interestingly, I do not see a reference to the the CMTransformBean in the JNDI browser of the NetWeaver Administrator. Thsat seems like a likely cause of the problem, but why is that ?
Thanks,
Guy

EIS migration from 7.1.2 to System 9.3

We are migrating EIS 7.1.2 to System 9.3 AIS. I can't connect to shared services from AIS and it seems like all the import/export of the models/metaoutlines are done through shared services. I get a JDBC error while connecting to shared services. If anyone has any experience, please let me know how you fixed it. Thanks

Hi,
Now my problem is not data mismatching...
Recently i have changed Database names in essbase production box(7.1.2). Now i have added 7.1.2 to 11.1.1.3 (new production box) there i am unable to see the new Database names, it is reflecting old database names only.
If i click on Edit properties it is showing database not found.
If i click on preview data it is showing *#MISSING*.
Please suggest to resolve this issue...
Thanks,
Prathap

EIS drill through reports in Analyzer

I'm having trouble pulling SQL drill through reports defined in EIS when using Analyzer. I can pull the report when I'm in Excel, but when I go into Analyzer and double click, I get the related content box to open, but no links to the drill through report. I did some searching on the Hyperion support site and found an entry in the knowledge base that said the Grid API option had to be turned on for this functionality to work. Of course there was no mention of how to turn the Grid API on and I have not been successful in finding anything in the install guide or the admin guide. I'm using Essbase 7.1.5 with EIS 7.1.2 and Analyzer 7.2.5. Is anyone using Analyzer to successfully pull EIS drill through reports? Did you have to turn on the Grid API option? How is this feature turned on? Or, any other suggestions? TIA

Hi, I am also facing few issues related to AIS: I am unable to use Drill Through (1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck (2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further Can anybody help me?

Drill-Through reports in EIS 7.1.X

Hi, We had some problem migrating to EIS 7.1 from 6.5.4. EIS seems to ignore all the dimension tables defined in the model whenever executing the drill-through reports, and only using fields in fact table in the "where" clause. The same report/"intersection points" works perfectly in 6.5.4.

Hi, I am also facing few issues related to AIS: I am unable to use Drill Through (1) Smart View: It is asking for Connections and i am unable toprovide Shared Services Provider Information. It throws an error.In case i use URL as add feature then it asks for credential butstill no luck (2) Then i tried to used Add-In Excel and (This is my 1st time):When i double click on the data figure based on Intersaction leveli defined, it is taking me LRO's and now i don't know hoe toproceed further Can anybody help me?

Hyperion Integration server - updating the cube through AIS

Hi All,
we have an existing ASO cube with 12 dimensions and there is a requirement to add another dimension to the same cube. There are currently 16 drill through reports defined against the cube. I have not worked with the AIS earlier but have an overall idea . So if i want to add another dimension through AIS..What are the
things i have to do ..starting from creating/having a dimension table for the new dimension
what are the things i have to take care of?etc
Thanks a lot for your time

Ensure you have a column(s) in your dimension table that can join to the fact table. In EIS open the Model for this particular cube. On the left side find your dimension table and drag it on to the model. Answer yes when it asks if you want to add the table to the current model. Click the "Add Joins Mode" icon then click the fact table object and DRAG and let go on your dimension table. A popup should appear "Create new dimension". Change the name if you wish, then click OK. Another popup appears "Edit join info for...". Choose the columns to join on and click "Add" then "Close". Save the model. Open the EIS outline for this model and assuming you didn't already have it open you'll find your new dimension table on the left. Drag the level-0 (bottom most level) column that you're putting in this cube over to the outline name on the right and let go, or wherever you want to add the dimension and go from there.
If the outline is using User Defined SQL then you'll be prompted "User defined data load SQLs may not be valid anymore. Do you want to delete them? Pressing No will prompt you to edit the SQLs." Choose "No". A "SQL Override" window will appear where you can type in your column name to the Select list (for a hint of what to do look at what it put in the Standard Dataload SQL in grey at the bottom & go from there). Put your new column in the same order in the Select statement that the Standard Dataload SQL has it in.
Then it's probably good to edit each of the drillthrough reports. With the EIS outline open, from the menu choose Edit | Drill-through Reports. Expand each report and decide whether you need to specify a certain intersection level for this new dimension - meaning, at what level do you want to force the users to have to select a value before you'll let them 'see' the drillthrough report. If it doesn't matter for this new dimension then just click OLAP Intersection Levels, Add, then click on your new dimension then the right arrow to add it to the list of intersections and click Close.
Let me know if you need additional assistance.
Good luck,
Karen Smejkal

Idoc conversion rule

Hi,
What is idoc conversion rule? Why we need this?
While upgrading from 4.7 to ECC 6.0 what all precautions need to be taken for the existing standard idocs and custom idocs in the system.
Thanks & Regards,
Soumya.

Hi,
ALE allows the user to perform an SAP transaction in the sending system, after-which the following steps occur:
1 or more communication IDocs (intermediate documents: container for the application data) are created in the sending system database. An ALE distribution model, that needs to have been configured, determines which systems the IDocs are to be sent
These communication IDocs, that contain the relevant application data of the transaction that was performed, are then passed to the ALE communication layer
This layer performs an RFC call, using the port definition and an RFC destination determined through the customer model
The IDocs are then transferred to the respective receiving systems. These could be SAP R/3, R/2 or external systems
If the receiving system is an SAP system then:
In the case of master data distribution the same transaction that was performed on the sending system is again performed on the receiving system with the data contained in the IDoc. This allows the data to go through the SAP checks before posting occurs
In the case of transaction scenarios the relevant data is passed to the respective transactions in order to load the required application document. Eg. A PO is loaded on the sending side, yet a SO is created on the receiving system
Master data has another difference:
It can be set up in such a way that any changes made to specific fields in master data tables can automatically trigger off the ALE distribution process for that particular master data object
If a master data object is created or changed on a sending system and distributed to another system the respective transaction is used to either create or change that respective master data object on the receiving system
In general, if standard SAP can't perform the task required then neither can ALE. It doesn't add functionality, it merely decouples it and allows you to distribute it onto other remote systems.
The Detail as described by SAP
In the output processing one of the function modules of the application creates an IDoc, the so-called master IDoc. This IDoc is sent to the ALE layer where the following processing steps are applied:
Outbound processing
Receiver determination
An IDoc is similar to a normal letter in that it has a sender and a receiver. If the receiver has not been explicitly identified by the application, then the ALE layer uses the customer distribution model to help determine the receivers for the message.
The ALE layer can find out from the model whether any distributed systems should receive the message and, if so, then how many. The result may be that one, several or no receivers at all are found.
For each of the distributed systems that have been ascertained to be receiver systems, the data that is specified by the filter objects in the customer distribution model is selected from the master IDoc. This data is then used to fill an IDoc, and the appropriate system is entered as receiver.
Data selection
Segment filtering
Individual segments can be deleted from the IDoc before dispatch by selecting Functions for the IDoc processing -> Settings for filtering in ALE Customizing. The appropriate setting depends on the sending and receiving logical R/3 System.
Field conversion
Receiver-specific field conversions are defined under Functions for the IDoc processing -> Conversions.
General rules can be specified for field conversions; these are important for converting data fields to exchange information between R/2 and R/3 Systems. For example, the field "plant" can be converted from a 2-character field to a 4-character field.
The conversion is done using general EIS conversion tools (Executive Information System).
Version change
SAP ensures that ALE functions between different R/3 System releases. By changing the IDoc format you can convert message types of different R/3 releases. SAP Development use the following rules when converting existing message types:
Fields may be appended to a segment type;
Segments can be added;
ALE Customizing keeps a record of which version of each message type is in use for each receiver. The correct version of the communication IDoc is created in the ALE output.
The resulting IDocs (it is possible that several IDocs could be created in the receiver determination) are referred to as communication IDocs and are stored in the database. The dispatch control then decides which of these IDocs should be sent immediately. These are passed to the communications layer and are sent either using the transactional Remote Function Call (RFC) or via file interfaces (e.g. for EDI).
If an error occurs in the ALE layer, the IDoc containing the error is stored and a workflow is created. The ALE administrator can use this workflow to process the error.
Inbound processing
After an IDoc has been successfully transmitted to another system, inbound processing is carried out in the receiver system, involving the following steps in the ALE layer:
Segment filtering
Segment filtering functions the same way in inbound processing as in outbound processing.
Field conversion
Specific field conversions are defined in ALE Customizing.
The conversion itself is performed using general conversion tools from the EIS area (Executive Information System).
Generalized rules can be defined. The ALE implementation guide describes how the conversion rules can be specified.
One set of rules is created for each IDoc segment and rules are defined for each segment field.
The rules for converting data fields from an R/2-specific format to an R/3 format can be defined in this way. An example of this R/2 - R/3 conversion is the conversion of the plant field from a 2 character field to a 4 character field.
Data transfer to the application
Input control
When the IDocs have been written to the database, they can be imported by the receiver application.
IDocs can be passed to the application either immediately on arrival or can follow in batch.
You can post an inbound IDoc in three ways:
by calling a function module directly: A function is called that imports the IDoc directly. An error workflow will be started only if an error occurs.
by starting a SAP Business Workflow. A workflow is the sequence of steps to post an IDoc.
by starting a work item A single step performs the IDoc posting.
The standard inbound processing setting is that ALE calls a function module directly. For information about SAP Business Workflow alternatives refer to the online help for ALE programming.

EIS - AIS conversion

Similar Messages

Maybe you are looking for