Difference between Classic Planning and EPMA Application 11.1.2.2

what is the major variaine between Classic and EPMA Planning
Please advise

one works well and one is a lifetime of pain... let you decide which is which
See the search up on the right, put in the following
difference classic epma
and go to the results, where would we be without search engines.
Also do you ever get the feeling of Deja Vu - 11.1.2.1 Classic Planning vs EPMA Planning
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

Difference between Classic Planning and EPMA Application

Hi All,
We are currently working Hyperion Planning version 9.3.1 and we do use Classic Planning Administration. We are in the phase of upgrading to version 11.1.2 and thinking of using Enterprise Performance Management Architecture to work with applications . Kindly let me the difference between Classic Planning and EPMA Application and its cosequences on upgradation.
Thanks in advance

Instead of explaining it all again here are some posts around the same subject
Re: what is the Differenc between Classic Planning and EPMA
Hyperion Planning - Classic Administration vs EPMA ....
Re: The advantage of using EPMA?
EPMA compare to Classic
Cheers
John
http://john-goodwin.blogspot.com/

What is the Differenc between Classic Planning and EPMA

Hi All,
What is the Difference between Classic Planning and EPMA in terms of functionality. If we choose the EPMA what are the additional benefits we will get over Classic?
Please Explain in detail way.
In what scenarios we go for Classic Planning and EPMA ( we are not using Financial Management. Only Planning,Essbase and FR)
Please suggest me. We are using 9.3.1. Client wants leverage maximum of Hyperion in future.
Thanks in advance.
Regards,
Sravan Kumar.

Hi,
This post should help you :- Hyperion Planning - Classic Administration vs EPMA ....
Cheers
John
http://john-goodwin.blogspot.com/

Difference between classic App and EPMA Appl

hi,
I am very new to hfm...
So could you plz explain about what is difference between Classic Application and EPMA Application.
In which cases we will create these applications.
What is the uses of Both Applications?
How do we create EPMA Application? Usually which application is more flexible?
Edited by: 809370 on Dec 6, 2010 5:24 AM

Hi,
The basic difference is that you would be able to share dimensions across applications through EPMA.If you have a Planning application and a HFM app. and they both use a same dimension, then you don't need to create the dimension twice in EPMA. You can share the dimension across both applications. 'Dimension Library' enables youto do that.
Regards,
Sounak

Difference between ISA webshop and ISA application

Hi ,
I have a basic question regarding the ISA , I work on ISA b2c and b2b application and came across webshop what is the difference betwwen an ISA application and ISA webshop where does this Webshop reside ? on J2EE engine and is it default provided by when a application server like 6.2 or 6.4 is installed or where dose it reside ? I know it is accessed through and URL shopadmin or so ? but not sure how to install it on my local server and so forth please some one give me anidea of it and let me know in lane terms what does this webshop mean . If you want to send any documents feel free to send it to [email protected]
Thanks in advance

Instead of explaining it all again here are some posts around the same subject
Re: what is the Differenc between Classic Planning and EPMA
Hyperion Planning - Classic Administration vs EPMA ....
Re: The advantage of using EPMA?
EPMA compare to Classic
Cheers
John
http://john-goodwin.blogspot.com/

Differences between Classic BW and HANA on BW?

Dear Friends,
can we discuss here what are main difference between classic BW and HANA on BW?
Please share your thoughts who was involved in RAMPup.
already know some differences IMDB DSO, Cube, still some gaps are not clarify till i install BW on HAN
thanks
rao

First of all , HANA Enterprise Extend edition DOES NOT Meets all BW features.
There are no best scenario, it is dependent on scenarios.HANA SPS3 scenarios would be great fit for Agile Data mart however BW on HANA would be great fit for EDW scenarios.
For users who already have BW with BWA, BW on HANA bring performance improvement on the other side of equation (ETL side) along with query improvement.
At high level, following are some of techinal issues with using HANA SPS 3 as "One fit for all" :
1. Currently, there is no reporting tool available which can recogonize variable functionality of HANA. One may use universe variable functionality however the functionality will not provide all exhaustive options.
2. Currently Hierarchies cannot be recogonized by any of reporting tools.
3. Currently Data Level security options in HANA is limited.
Another dimension to consider is if you have planning application,Integrated Planning is currently supported and BPC will be supported soon (the scenario is only possible BW on HANA).
Hope this is helpful.
PS:
Regarding HANA 1.0 SPS3, for your below scenario:
SAP & non SAP - BODS 4.0 -- HANA 1.0 SPS3 -- BI 4.0( Any front end ODBC support )
you will need BODS 4.1 version.

Difference between Classic RE and RE-FX (Real Estate Management)?

Hi all,
I am in a product developement team for developing a industrial Solution for HomeBuilding, for that we require Real estate(RE) Management Component....
So i want to know some of the basics of the RE....
Can someone explain me,
1) The difference between Classic RE and RE-FX.
2) Now which we have to use for Homebuilding.
3) what are the prerequisites for using RE or RE-FX.
4) From which version they are available. can we still use classic RE.
5) What is the difference in using RE Management as individual application and as a part of Homebuilding....

Hope your answers will be as simpler and eloborate so as to my understading as a fresher in this field....
I Expect more links for online resources, presentations and Documents if any...
Thanks in advance....
Regards,
Karthik D

So you want to know some of the basics of the RE....
Real Estate Management module is more robust in managing Real Estate properties for activities and processes like leasing, property maintenance like manging repairs etc (when attached to Plant Maintenance module). You can also use it for Lease in's. (caution: please associate 'renting' wherever lease is mentioned, not to get confused with lease of machinery or financia lease etc.)
The main master data in RE are like Business Entity,Property, Buildings, Rental Units and Leaseout. These are called RE-Objects and they are also Controlling objects. For example let's take Spenzer Plaza in Chennai and you are the owner. The whole Spencer Plaza will be a Business Entity. The land in there will be created as a Property and the building structure as Building. The several floors or the individual rentable portions will be created as Rental Units. When 'Planet M' approaches you to rent one of the floors, you create a Lease out with reference to one of the Rental Unit.
The system automatically creates a schecule of periodic rentals called cash flow and it has the capabilities to debit the customer Planet M account with the rent due. etc.
You can also maintain information to land through Land Register.
2) Now which we have to use for Homebuilding. and
5) What is the difference in using RE Management as individual application and as a part of Homebuilding....
These are not used for Homebuilding.
3) what are the prerequisites for using RE or RE-FX.
You need to have FI and CO before you can use REM.
4) From which version they are available. can we still use classic RE.
4.5B onwards RE was introduced as a Inudstry specific module under FI. It became as a part of FI from 4.6B December 1999. The RE-FX cameinto effect from Enterprise version.
You can continue to use RE Classic even in later releases. But once you activate the RE-FX you can no longer user Classic. There is a switch to start using RE-FX.
1) The difference between Classic RE and RE-FX.
There were some restriction in classic RE that you must have an RE Objects before you can create a contract. In RE-FX these have been removed. For more information on RE-FX you can read the release notes available on SAP's help portal.

Difference between database, websheet and packaged applications

Hi,
Can any one explain the difference between database, websheet and packaged applications?
So far i have worked on database application and not aware of the other applications.
Regards
Narender B

Narender wrote:
Can any one explain the difference between database, websheet and packaged applications?
So far i have worked on database application and not aware of the other applications.
This is fully covered in the documentation:
About Database Applications
About Websheet Applications
About Packaged Applications
There is little difference between packaged applications and database applications, other than that packaged applications are supplied by Oracle and database applications are created by you.

What is the basic difference between Hyperion Planning and HFM

Hi GURU'S,
what is the basic difference between Hyperion Planning and HFM and when do we choose them.

On a high level the difference is this:
1. HFM is best for global collection (collecting data from scattered entities), group consolidation and for easily structuring financial reporting (mainly consisting of financial data)
2. Planning is best for modeling your business, starting from a demand forecast and arriving to capacity planning and finally to financial statements, by utilizing business drivers (non-financial data like volumes, prices, productivity rates etc)
Of course, differences may be analyzed at several levels down to technical, but the discussion may turn out to be too long, yet adding little value to the question: "when do we choose the one over the other". Bear in mind that your requirements may turn out that you need both.

What is major difference between hyperion planning and hyperion essbase

hi
what is the differences between hyperion planning and hyperion essbase.i dont know about planning much.but as far i know.i think we can do every thing in essbase also(planning,budgeting and forecasting)
what u say.what we actually do in planning.
regards
bharat

Hi Bharat
Although as you mention in your post Essbase can do plans/budgets etc it may not be simple to provide complex planning process control and ease of data entry etc.
Planning delivers these benefits and some through web delivered components such as forms, business rules and workflow for instance. There are some restrictions to using planning and these need tobe well understood before embarking on a project.
It would be worth having a look at product sheets from Oracle and/or presentations from various events to get a feel for planning capabilities.
Hope this helps.
Andy King
http://www.analitica.co.uk

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

Difference between Pension plans and savings plans

Dear Friends,
I'm familiar with the configuration of savings plans. But I have no idea about the pension plans. I realize that some of the basic steps are common to both savings and pension plans but what is the main difference from a config perspective?.
If any one can kindly explain the necessary steps to set up pension plans or if there is any document which talks about it please please let me know.
I appreciate the help and thanks in advance.

IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
Define Cost Variants:
In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Option
u2022 Dependent coverage
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
Health Plan Attributes:
In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
You assign to each health plan:
u2022 Its options
u2022 Relevant dependent coverages
u2022 The cost variants for the combination of options and dependent coverages
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
Insurance Plans:
In this step, you define general data for insurance plans
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
Coverage Variants:
In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual coverage in this step. You simply define how coverage varies according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define coverage variants, you need to do the following:
1. Determine how often coverage varies for different coverage options.
This indicates how many coverage variants you need. Note the following:
u2022 If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
u2022 If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
u2022 If a plan has options, you will need a coverage variant for each option.
2. Determine how coverage varies according to employee data.
This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
Coverage Rules:
In this step, you define the actual coverages for a plan.
You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
Coverage can be defined as a flat amount or as a factor of salary
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
Cost Variants:
In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often cost varies for different coverage options:
u2022 If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
u2022 If you have set flat coverage options and the flat costs are directly
proportional to the coverage stated in the flat cost, you need only one
cost variant.
u2022 If an employee can choose any amount of coverage within a range and the
cost of the coverage is directly proportional to the coverage, you need
only one cost variant.
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
Insurance Plan Attributes:
In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
You define the insurance plan options, then associate to each insurance plan:
u2022 Cost variant
u2022 Coverage variant
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
Combined Coverage Limits:
When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
In this chapter, you define these combined limits as follows:
1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
3. The second view defines the other side of the equation in terms of the plan coverages
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
Combined Coverage Limit Expressions:
In this step, you enter the second half of the equation, as discussed in combined coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
Imputed Income for Selected Benefits:
In this section of the IMG, you define the criteria needed to calculate Imputed Income.
Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
Review Calculation Factors for Imputed Income:
In this step, you check that the Imputed Income Rate Table entries are correct.
The imputed income age groups are associated with the rates/factors set by the IRS
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
Savings Plans:
In this step, you define general data for savings plans.
You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
Employee Contribution Variants:
In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contributions in this step. You simply define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
Employee Contribution Rules:
In this step, you define the employee contribution limits for each plan.
You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define minimum and maximum employee contribution in the following ways:
u2022 As a fixed amount
u2022 As a percentage of salary
u2022 As a contribution unit
In Payroll, the total employee contribution is the sum of these amounts
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
Employer Contribution Variants:
In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contribution in this step. You only define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
Employer Contribution Rules:
In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define the employer contribution and the contribution limit in either of the following ways:
u2022 As a fixed amount / as an amount per unit contributed by the employee
u2022 As a percentage of employee base salary or employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
Assign Savings Plan Attributes:
In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
u2022 EE contribution variant
u2022 ER contribution variant

Difference between Classic, Enjoy and Signature design

Hi guys,
We are about to install SAP GUI version 720 for accessing SAP GL on ECC6 (NW7.01) and are looking into the desktop requirememnts in terms of CPU, Memory etc.
The various SAP notes mention that there will be a different requirement depending on whetter you activate the Classic, the Enjoy or the Signature design.
Can anyone explain what the difference between these actually is? All we want to do is use the SAP GUI for journal entry/change, basic reporting and workflow tasks.
Many thanks

My apologies.
I cannot speak for SAP's reasons as I do not work for them, however, the difference here which we have encountered is just the choice for users to make it more aesthetically pleasing. There are no items/options/buttons which are missing due to the theme selection. (At least that we have heard or come across) It is more of a personal choice. I do not use the signature design personally but many users have adopted the new theme. We have about 20-30 thousand users of SAP gui and just have a document posted on how to change the theme if they do not like the SAP Signature one as it was the default when rolled out.
Multiple options just gives the users more choices to find something which they may like better than forcing the default on everyone. I would look at it more like Microsoft Windows themes. Gives options to users for going with the new Windows 7 theme, revert to the old Vista look or all the way back to XP, etc.
Regards,
Zecher

Difference between DB adapter and Ebusiness Application adapter

Could anyone please explain the difference between the two adapters?
If you want to access Applications objects, you could this via the DB adapter - so why use the other one?
Rgds, Henrik

DB adapter connect to any database, bu form most of all the Oracle database.
The Apps Adapter is based on the DB adapter, and access only the specific components of Oracle EBS, that are exposed.
Marc

SAP GUI 720 - difference between Classic, Enjoy and Signature

Hi experts,
We intend to use the SAP GUI 720 for Finance uers entering journals and using workflow. I have checked out the PC requirements for the GUI and they vary depending on whether you opt for Classic, Enjoy or Signature design.
Can anyone explain what the difference is between these options?
many thanks
mike

Hi Adrian,
the difference is the look and a few option (like setting a different color in the different systems (like different colors for E, Q and P), a focus frame, and so on.
I googled for some pictures:
Signature Theme: http://www.sapdesignguild.org/resources/vd_images/revolutions/GUI_Signature_Theme.png
Enjoy Theme: http://www.sapdesignguild.org/resources/vd_images/revolutions/Win_Enjoy_Tradeshow_Themes_large.png
Classic Theme: http://support.citrix.com/article/html/images/CTX127399-2.gif
I prefer using the Signature Theme because it is clear and has the focus frame.
Hope this helped.
Regards,
Jann

Difference between Classic Planning and EPMA Application 11.1.2.2

Similar Messages

Maybe you are looking for