C++ Compilers for Beginners

Okay. So, let me just start by saying that I do not wish to download Xcode at this time, because it is MASSIVE and mostly superfluous for my limited needs...which are to learn the basics of writing programs in C++. Also, for whatever reason, it appears to want to take hours to download....and I just don't have that kind of time.
I looked into the possibility of using Text Wrangler with a separate compiler, but I don't quite know how to integrate the two or to just make programs executable from Text Wrangler.
I chose the Ch compiler as it was free for students, and it appeared to have a super clean/beginner-friendly interface. But when I downloaded it, nothing happened. I have a blank sheet icon in my applications folder and nothing pops up when I click on it.
Can anyone...who actually knows and is not just speculating...recommend either a new/better IDE or some sort of compiler that will work in conjunction with TextWrangler OR a method of trouble-shooting and figuring out how to work Ch/ChIDE?
It would be greatly appreciated! Thanks!
J

This is not the correct forum for such questions. There is a specialist Developers' forum here:
https://discussions.apple.com/community/developer_forums
Bob

Similar Messages

File TO File-Using XSLT mapping (for Beginners) --- Error in XSLT

Hi,
I am following this wiki (TO File-Using XSLT mapping (for Beginners))
https://wiki.sdn.sap.com/wiki/display/XI/FileTOFile-UsingXSLTmapping%28forBeginners%29
When creating Xslt from the MapForce, when I click on the XSLT Tab I am getting the following error
http://www.flickr.com/photo_zoom.gne?id=1216715484&size=o
How to correct this error ?.....
Thanks
srini
Message was edited by:
srinivas

Hello,
The XSD you are using is from Data Type and you are using it for mapping.
Instead export XSD for Message Type and also pass the XML schema for source that will solve the issue and your XSLT will be generated.
Regards,

DVD start menus and books for beginners

I would like to make a custom start menu using a jpg graphic and my own music. It would just have 2 options start video and scene selection.
I was fumbling around with PE11 yesterday and did it by accident. I added the picture and then added the audio with drag and drop....but when I tried to do it again, I could not remember what I selected.
Also is there a good book for beginners?
Thanks,
Matt

MHairell
Pending further information, this is what I came up with using
Premiere Elements 11 Windows
General/Grid
and its matrix_pal_s_mm.psd (for main menu) and its matrix_pal_s_sm.psd (for scene menu)
My Photoshop Elements is presently not allowing me to open the Photoshop Layer Sets in the .psd files, so I picked the above theme so I could get around having to do that.
This is the first try result
Main Menu....
Scene Menu
I tried it out in a DVD-VIDEO standard on DVD, and it did not look that bad.
My advice is to look at the theme as is to see what it is all about, and, if interested in getting a look like above, I will give you the step by step. But, you will need Photoshop Elements or Photoshop for the background exchanges. I did not find a theme where I could get a clean enough background replacement with just the customization within the Movie Theme section of the program. Again, Photoshop Elements that will not open the Layers Sets is OK in this instance since we are not opening any Layers Sets, we are just replacing backgrounds at the .psd level rather than within the project.
If interested, I will post further details which should be quick and easy to follow.
Thanks.
ATR

Which is better for beginners

Which Photoshop is better for beginners ???
SujithVijayan

For what purpose? Usage?
Elements will be OK for editing photographs. Just making them look their best, sort of thing. Photoshop is better if you want make composites, or radical changes, or build an image from scratch, or if you think you are really serious, and want the best tool for the job.

Tutorial: Flash Builder 4 beta 2 and PHP Data/Services for beginners

Hi fellas,
I've written this tutorial for total beginners to get quickly to FB4 and PHP. Comments welcome
Flash Builder 4 and PHP Data/Services for beginners
http://www.flashrealtime.com/flash-builder-4-and-php-data-services/

Hi,
The first issue will be the pathing differences between wamp/mamp/xampp, some use www as root others htdoc you need to setup the php services on your local machine rather than importing a project.
The created services will have a connection array declared at the top of the code that points to the mysql server, in the project default debug folder you will have the config file that has the zend and webserver path
top of service file
============
var $username = "root";
var $password = "";
var $server = "localhost";
var $port = "3306";
var $databasename = "zend";
var $tablename = "clients";
var $connection;
amfconfig.ini
=========
[zend]
;set the absolute location path of webroot directory, example:
;Windows: C:\apache\www
;MAC/UNIX: /user/apache/www
webroot =C:/wamp/www
;set the absolute location path of zend installation directory, example:
;Windows: C:\apache\PHPFrameworks\ZendFramework\library
;MAC/UNIX: /user/apache/PHPFrameworks/ZendFramework/library
;zend_path =
[zendamf]
amf.production = false
amf.directories[]=Zender-debug/services
In your main project folder you have a .model folder the file there is an *.fml file that contains your channel endpoints etc.
David.

What are the best books for PL/SQL and Forms for BEGINNERS?

I asked about learning Oracle Forms in an earlier thread. Some suggested Oracle training at official Oracle Training centers like Koenig. I just went to the Koenig site. The OCA & OCP Forms Developer Training Boot Camp is a whopping 2,610 USD. That’s like 1/4 Million LKR. It’s more that the yearly salary of both the 2 new developers we got and want to train. That’s out of the question.
Some have suggested shadowing experiences programmers and team coding. Both options are out, since those things don't work here.
Learning from sites such as Francois Degrelle's blog is no good for new people since they will get confused.
I have come to the conclusion that the only way to do is to buy 2 books, one for PL/SQL and another for Oracle Forms, give it to them and ask them to follow the book and learn it and also give a time period like 2 or 3 months.
What are the good books out there for BEGINNERS to learn PL/SQL and Forms?
Edited by: Channa on Aug 8, 2010 10:08 PM
Edited by: Channa on Aug 8, 2010 10:12 PM

In addition to the books the chapter Application Developer's Guide - Fundamentals in the documentation is also worth giving a shot:
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/toc.htm
Just for the record: I believe leaving them alone with the books won't do it. I'd at least define objectives (e.g. $chapters of the books in a week) and after they achieved them I'd test their knowledge of the individual objectives (like it was back in school :p ). By that you have control over how they are proceeding, you can focus on the things they didn't understand and you are able to eradicate some bad habits they might adopt during their studies.
If you don't take your time to train them proper you won't get good developers anyway and you will loose much more time and money...
cheers

Sun Studio Compilers for Linux: Problems with undefined variables using CC

I am experiencing the following errors below while trying to compile C++ programs using Sun C++ from the latest release of Sun Studio Compilers for Linux Alpha, on Red Hat Enterprise Linux 4 with kernel 2.6.9-34.EL and Ubuntu Breezy Badger 5.10 with kernel 2.6.12-10-686. I get the same exact errors on both OS's and on two different machines.
root@ubuntu:/home/jc/cs225/Machine Problems/cs225/mp1/cs225_mp1# make
CC -c -g string.cpp
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 74: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 75: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 191: Error: "," expected instead of "state_type".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 194: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 261: Error: "," expected instead of "get_state".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 265: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 299: Error: "," expected instead of "state_type".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 302: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 410: Error: "," expected instead of "get_state".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 414: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 506: Error: The function "strstr" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 523: Error: The function "strcspn" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 529: Error: The function "strspn" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: Template parameter std::stateT requires a type argument.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: Template parameter std::stateT requires a type argument.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 214: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 221: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 277: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 335: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 392: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 443: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 504: Error: Template declarations cannot have extern "C" linkage.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/limits", line 558: Error: Template declarations cannot have extern "C" linkage.
Compilation aborted, too many Error messages.
make: *** [string.o] Error 1
Except on ubuntu, it has one more error
"/usr/include/wctype.h", line 47: Error: A declaration was expected instead of "}".
and what is on line 47 is below
__END_NAMESPACE_C99
When I comment this line out, that particular error does not show up but still the other errors above still show up.
From the testing I did, it appears to have these problems for most of the C++ programs I have written, especially the ones that involve object oriented programming. All programs that I wrote do not have these problems with g++ or Sun CC for Solaris. It does however work fine only for small fraction of the programs I have written. I dont quite understand why it works in some cases and others it doesnt, but I know for sure, that it should be working for all cases when Sun CC from Sun Studio 10 on Solaris 10 for X86 has no problems compiling the same programs.

I tried workaround number 2 from the 3 choices that were listed by horsh. That fixes the mathcalls.h problem but still I have the following errors.
jcurran2@ubuntu:~/cs225/Machine Problems/cs225/mp1/cs225_mp1$ make
CC -c -g string.cpp
"/usr/include/wctype.h", line 47: Error: A declaration was expected instead of "}".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 74: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/iosfwd", line 75: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 191: Error: "," expected instead of "state_type".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 194: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 261: Error: "," expected instead of "get_state".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 265: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 299: Error: "," expected instead of "state_type".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 302: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 410: Error: "," expected instead of "get_state".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 414: Error: Use ";" to terminate declarations.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 506: Error: The function "strstr" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 523: Error: The function "strcspn" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/traits", line 529: Error: The function "strspn" must have a prototype.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 125: Error: Template parameter std::stateT requires a type argument.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/rwlocale", line 130: Error: Template parameter std::stateT requires a type argument.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 55: Error: mbstate_t is not defined.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 55: Error: Template parameter std::stateT requires a type argument.
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 61: Error: "," expected instead of "state_type".
"/opt/sun/LinuxCompilers/sunstudiomars/prod/include/CC/Cstd/rw/codecvt", line 63: Error: Use ";" to terminate declarations.
Error: Cannot continue processing because of prior errors.
Compilation aborted.
make: *** [string.o] Error 1
jcurran2@ubuntu:~/cs225/Machine Problems/cs225/mp1/cs225_mp1$
Can someone please respond? There is more to the problem. Perhaps
there are more glibc headers that have problems. In addition, if Sun wants to port the Sun Studio Compilers for linux to be stable on all linux distributions I suggest using VM ware and installing several linux distrobutions as virtual machines and testing this software on each virtual machine to see the problems that occur on each distribution. That way you might be able to uncover more problems to find a solution that will work best for portability on all linux distributions.

Suggest book on SAP HR Functional for beginners

Dear All,
Request you to suggest me a book for SAP HR Functional
for beginners.
Thanks in advance for the help.
Regards,
Taranjit

Benefit Administration:
This section of the Implementation Guide (IMG) is where you set the SAP Benefits Administration component.
Here you enter in the system all the details of the benefit plans offered by your company.
Benefit Area:
Benefit areas allow you to have separate administration of different benefit plan pools. This division is primarily for administrational purposes and would not normally be used for eligibility
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Area
Assign Currency to Benefit Area:
In this step, you specify the currency for the benefit area
IMG Path: Personnel Management  Benefits  Basic Settings  Assign Currency
this step, you enter the providers of the benefit plans you offer.
This could be the Insurance company, or Health Maintenance Organization that receives the benefit plan costs
IMG Path: Personnel Management  Benefits  Basic Settings  Define Benefit Providers
In this step, you set relevant benefit area for your Customizing activities
If you have more than one benefit area to set up, you must set up each independently. After you have set up all the plans in one area, you must return to this view, set the next current benefit area and work through the IMG again, setting up the new benefit area.
IMG Path: Personnel Management  Benefits  Basic Settings  Set Current Benefit Area
Benefit Plan Types:
In this step, you enter the benefit plan types that you require for the plan categories predefined in the system.
The following plan categories are provided by MSD:
Health Plans
o Medical
o Dental
o Vision
Insurance Plans
o Basic Life
o Supplemental Life
o Accidental Death & Dismember
Savings Plans
o 403B
o 457
o PERS (Public Employees retirement Scheme for CP Benefit Plan) & TRS
(Teachers Retirement Scheme for TP Benefit Plan)
Flexible Spending Accounts
o Health care
o Dependent care
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Types
Define Benefit Plan Status:
It is important that you assigning statuses in order to be able to control the availability of plans with a minimum of effort. For example, you can control whether or not employees can enroll in a plan simply by changing its status
IMG Path: Personnel Management  Benefits  Basic Settings  Plan Attributes  Define Benefit Plan Status
Benefit Plan Status:
In this step, you define parameter groups. You decide which groups you require in two stages:
1. You consider which costs, credits, coverage and employee and employer contributions for your plans vary according to the age, salary and/or seniority of employees (or possibly the age of the employee's spouse).
2. You determine the different ways in which you need to divide your employees according to different value ranges for these criteria.
It is not possible to define overlaps of ranges for a criterion within a single parameter group. Therefore, if you require different employee groupings for different plans, you need to create a separate parameter group.
For each unique combination of criteria and their values, you need to define a parameter group.
In this step, you simply create the parameter groups to which you assign groups for the individual criteria in the following steps. You later refer to the parameter groups, where applicable, in the individual rule variants for plans. Since one parameter group can be referenced by multiple plans, Customizing effort is kept to a minimum. In the plan variant, you also have the flexibility of being able to specify that you only want to use certain criteria values belonging to a parameter group, for example, age ranges
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Parameter Groups
Age Groups:
In this step, you define the age groups for the parameter groups that you defined in a previous step.
Depending on your needs, you may find for some parameter groups, you can leave out this step, if for example there is no requirement to differentiate between employees based on age
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Criteria Groups  Define Age Groups
Age Groups under Parameter grouping PAR1
Cost Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, job classification, marital status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying costs for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Cost Groupings
Coverage Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, employment contract, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying coverage for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Coverage Groupings
Employee Contribution Groupings:
In the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employee Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Basic Settings  Define Employee Groupings  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Employer Contribution Groupings
the parameter group you could differentiate between employees based upon age, salary and seniority. Here you can further differentiate between employees, based on other employee criteria, such as geographical location, weekly hours, residence status and so on. Only set up this feature, if you find that the parameter group does not adequately cover your needs, when specifying employee contribution for different groups of employees
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Options for Health Plans
Dependent Coverage Options:
In this step, you define the dependent coverage that are used in health plans.
Define all possible variations that you need, because this view is not specific to any plan or plan option
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Dependent Coverage Options
Number of Dependents:
In this step, you can restrict participation in a health plan under a dependent coverage option to certain types of dependent, as determined by the subtypes of the Family/Related Persons infotype (0021). You can also define a minimum and maximum number of persons of a particular type that can be covered. During enrollment, the system only includes those dependent coverage options in the benefit offer for which the appropriate dependents are available
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:
Plan
Option
Dependent coverage
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:
Its options
Relevant dependent coverages
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:
Plan
Coverage option
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:
If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
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:
Plan
Coverage option
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:
If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
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.
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:
Cost variant
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:
Plan
Option (only for plans in the plan category Miscellaneous)
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:
As a fixed amount
As a percentage of salary
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:
Plan
Option (only for plans in the plan category Miscellaneous)
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:
As a fixed amount / as an amount per unit contributed by the employee
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:
EE contribution variant
ER contribution variant
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Assign Savings Plan Attributes
Flexible Spending Accounts (FSAs):
In this step, you define general data for flexible spending accounts (FSAs).
Requirements
You have created the appropriate plan type , plan status, and benefit provider in the preceding steps
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Define Spending Account General Data
Assign Spending Account Attributes:
In this step, you enter the details of your flexible spending accounts including contribution limits, an employer contribution variant (if required), and rules for the reimbursement of claims
IMG Path: Personnel Management  Benefits  Plans  Flexible Spending Accounts (FSAs)  Assign Spending Account Attributes
Flexible Administration:
In this chapter, you define the flexible aspects of your Benefits administration. You define the availability of plans to your employees, in terms of the plans themselves. You also define aspects of the enrollment process.
you enter parameters that apply to processing within an entire benefits area, including:
Open enrollment period dates
Default validity dates for adjustment/standard plan records
Advance availability of future plans
Dependent age limits
IMG Path: Personnel Management  Benefits  Flexible Administration  Define Administrative Parameters
Benefit Adjustment Groupings:
In this step, you define adjustment groupings. These groupings allow you to specify different adjustment permissions for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Groupings
Benefit Adjustment Reasons:
In this step, you define adjustment reasons to control changes to employee enrollments according to company policy.
The adjustment reason types that you define here are assigned as subtypes of Adjustment Reasons records (infotype 0378) in HR Master Data. Since a record can only have one subtype, a new record must be created for every adjustment reason an employee experiences.
According to the adjustment concept, an employee can only make changes to her enrollments if she has an Adjustment Reasons record (infotype 0378) with the required adjustment reason as a subtype. The only exceptions to this are if changes are made during an open enrollment period or if an anytime adjustment reason is assigned to the plan type.
In addition to defining adjustment reasons for certain events that can trigger changes, you may also want to define a special adjustment reason to allow changes to plans at any time
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Benefit Adjustment Reasons
Adjustment Permissions:
In this section, you assign adjustment permissions to each benefit plan type for an adjustment reason and any adjustment grouping that you have defined.
Note that the elements for which you can define permissions are automatically determined by the system, dependent on the plan category
Health Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Health Plans
this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Insurance Plans
Savings Plans:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Savings Plans
Spending Accounts:
In this step, you define the changes permitted for all plans of this type. You do this for each combination of adjustment reason, adjustment grouping, and plan type
IMG Path: Personnel Management  Benefits  Flexible Administration  Benefits Adjustment Reasons  Define Adjustment Permissions  Spending Account
Programs:
In this section of the IMG, you define benefit programs and the eligibility restrictions and termination conditions for the plans within these programs.
Within a program, eligibility for plans can be determined on two levels:
Program groupings control eligibility on a high level (macro-eligibility) by allocating an employee a defined program, depending on his/her organizational and employment data.
Eligibility rules are optional and control eligibility on a low level (micro-eligibility) by determining whether an employee can participate in a plan within the relevant program. An employee must fulfill the conditions defined in the rule in order to be able to enroll. Eligibility rules are assigned to plans in programs by means of an eligibility variant.
First Program Grouping:
In this step, you define first program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define First Program Grouping
Second Program Grouping:
In this step, you define second program groupings. Later, you define programs for a combination of first and second program groupings.
Identical attributes are available for the setup of both the first and second program groupings, and they are therefore interchangeable. The fact that you determine macro-eligibility for a program using two dimensions means that you are able to make finer distinctions between groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Second Program Grouping
Employee Eligibility:
In this section of the IMG, you define the criteria according to which you control eligibility for individual benefit plans within a benefits program (definition of micro-eligibility). You perform the following steps to set up eligiblity requirements:
You define eligibility grouping to identify groups of employees for whom
certain eligibility criteria apply.
You create eligibility variants, which you later use to link eligibility
rules to programs.
If necessary, you define dynamic eligibility conditions relating
specifically to actual hours worked/length of service, or zip codes.
You bring your definitions together in the eligibility rule, where you
can also specify further conditions for enrollment.
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Groupings
Eligibility Variants:
In this step, you define eligibility variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Variants
Eligibility Rules:
In this step, you define eligibility rules for the benefit plans offered by your organization. You define these rules for combinations of eligibility grouping and eligibility variant, thereby determining the eligibility conditions that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Employee Eligibility  Define Eligibility Rules
Participation Termination:
In this section of the implementation guide you define criteria for the termination of benefit plans
Termination Groupings:
In this section of the implementation guide you define criteria for the termination of benefit plans
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Groupings
Termination Variants:
In this step, you define termination variants. These consist simply of an identifier and a description
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Variants
Termination Rules:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Participation Termination  Define Termination Rules
Define Benefit Programs:
In this step, you define termination rules. You define these rules for every combination of termination grouping and termination variant, thereby determining the coverage continuation periods and termination day that will apply for different groups of employees
IMG Path: Personnel Management  Benefits  Flexible Administration  Programs  Define Benefit Programs
Dependent/Beneficiary Eligibility:
In this step, you define family member groupings and determine how family members are allocated to these groupings
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Family Member Groupings
Dependent Eligibility Rule Variants:
In this step, you define the dependent eligibility variants to which you want to assign dependent eligibility rules. You also specify whether you wish to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rule Variants
Dependent Eligibility Rules:
In this step, you define dependent eligibility rules to determine which types of family member are eligible as dependents. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Dependent Eligibility Rules
Beneficiary Eligibility Rule Variants:
In this step, you define the beneficiary eligibility variants to which you assign beneficiary eligibility rules in the next step. You also specify the following:
Whether you want to use a family member grouping in the associated eligibility rule to restrict eligibility to types of family members with certain characteristics
Whether the following apply for plans to which the variant is assigned:
 The employee can be a beneficiary
 Contingency beneficiaries can be named
 Spouse approval is required if beneficiaries other than the spouse are to be amed (the system only takes this setting into consideration for plans of the category avings)
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rule Variants
Beneficiary Eligibility Rules:
In this step, you define beneficiary eligibility rules to determine which types of family member are eligible as beneficiaries. You then assign your rules to the appropriate plans by means of a rule variant in the step Assign Eligibility Rule Variant to Plan
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Define Beneficiary Eligibility Rules
Assign Eligibility Rule Variant to Plan:
In this step, you assign dependent eligibility variants and beneficiary eligibility variants to plans, thereby assigning the eligibility rules associated with these variants
IMG Path: Personnel Management  Benefits  Flexible Administration  Dependent/Beneficiary Eligibility  Assign Eligibility Rule Variant to Plan
COBRA Plans:
In this step, you specify which health plans that you have already defined in the system are COBRA-relevant.
When a clerk collects COBRA-qualified beneficiaries, the system only considers employee enrollments in the plans you select here as legitimate cases where COBRA must be offered to the employee
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Plans
this step, you determine for which flexible spending accounts (FSAs) you will offer continuation of coverage under COBRA. You need to do this for each benefit area separately
IMG Path: Personnel Management  Benefits  COBRA  Choose COBRA Spending Accounts
Qualifying Event Coverage Periods:
In this step, you define the events that qualify individuals for COBRA coverage, and the periods of permitted coverage continuation for each qualifying event type. COBRA legislation states the following regarding coverage continuation periods:
In the case of Termination of employment and Reduction in working hours, only 18 months coverage must be provided. If qualified beneficiaries are determined to be disabled within 60 days of the COBRA event, they are entitled to a further 11 months of coverage, as are the other qualified beneficiaries who experienced the original event.
For all other qualifying events except Bankruptcy of employer, a qualified beneficiary is entitled to 36 months continuation coverage, and there is no extension provision for disability.
In the case of the event Bankruptcy of employer, the coverage continuation period is the life of the retired employee or retired employee's widow/widower. You therefore do not need to define a continuation period in this case.
IMG Path: Personnel Management  Benefits  COBRA  Define Qualifying Event Coverage Periods
Assign COBRA Events to Personnel Actions:
In this step, you define how the system recognizes COBRA-qualifying events from employee personnel actions (infotype 0000) records. You do this by creating a link between the two.
The only COBRA-qualifying event types that you assign to personnel actions are:
Termination
Death of employee
Reduction in hours
You need to assign these COBRA-qualifying event types since they are based on customizable entries in your HR master data and therefore cannot be delivered as standard.
When the system collects COBRA-qualified beneficiaries, it considers employee records within the date range you specify in two stages as follows:
1. The system searches for employee personnel action (infotype 0000) records. The COBRA qualifying events assigned to any personnel actions found are collected.
2. The system checks other employee infotype records for specific information which corresponds to COBRA-qualifying event types
IMG Path: Personnel Management  Benefits  COBRA  Assign COBRA Events to Personnel Actions
Notification and Payment Intervals:
In this step, you define details of COBRA administration for those states where state law concerning COBRA differs from federal law.
Federal regulations are reflected in the state settings for the District of Columbia, which is also the system default.
If you must comply with state regulations that differ from the federal regulations, you should create a new state entry. Otherwise, you can use the DC version for all employees, regardless of which state they reside in
IMG Path: Personnel Management  Benefits  COBRA  Define Notification and Payment Intervals
heck this one and let me know if there is anything else even arun has also given nice response so if u have any query pls revert back
6

Small Application for Beginners

I am new to the world of coldfusion and taking training since
2 months.....
I have gone through macromedia live documentation
My problem is that when i see the code i understand the flow
very easily .. But i am not able develop the logic..
can anybody help me out...??????
Plz suggest me how do i improve my logic and where can i get
the source code for small applications that are meant for
beginners...?????

If you read Ben Forta's ColdFusion MX Web Application
Construction Kit cover-to-cover, I guarantee that you'll really
understand the language.

Need help or documentation for beginners with SAP BI7

I am relatively new to SAP (less than a year) and I am still having difficulties understanding the basics about SAP. I write queries and reports and would appreciate any links or books that would help guide me. I have bought a book through SAP Press but I need a SAP for beginners books that is really easy to understand.
Thanks

Hi......
Check this link :
http://www.youtube.com/watch?v=nWsvV6Z64yw&feature=related
Also you will get everything in SAP Library : help.sap.com
Regards,
Debjani..........

Tutorial for beginners on Oracle 9iDS

Check out the simple tutorial on Oracle 9iDS in the link below. This tutorial is idle for beginners and for those working in 6i to have a feel of 9i Forms and Reports.
You just have to give ur mail id and select 9iDS tutorial.
Also post any such tutorials on 9iDS.
http://cisnet.baruch.cuny.edu/holowczak/oracle/

See: Publishing With iBooks Author
http://shop.oreilly.com/product/0636920025597.do

Is there any book for troubleshooting issues for basis consultants for beginners.

is there any book for troubleshooting issues for basis consultants for beginners.

Have you tried taking a look at the books at SAP press?
Administration - Books by SAP PRESS
https://www.sap-press.com/it-management/sap-for-beginners/topic/

Oracle BPM 12C Guide/Book for beginners

Hi,
Can anyone let me know whether there is any Oracle BPM12C Book/Training material available in the market or with any person for beginners ??
If yes , can you share the same,,,
Regards,
Vinit Ahuja,
[email protected]

HI Vinit,
you can start with Oracle Manuals "Getting Started": https://docs.oracle.com/middleware/1213/bpm/index.html
Additional You can check following links:
http://blog.c2b2.co.uk/2014/08/new-features-and-changes-in-bpm-12c.html
http://soabpm-jeqo.blogspot.de/2014/09/getting-started-with-oracle-bpm-12c.html
Regards
Borys

How to publish iPhone Apps with Flash CS5 for beginners

After many trial/errors and with lots of support from this site, I've decided to start building some tutorials to help people get into the packager. This is the first one and, now I'll work on a usual erros handle tutorial.
Any comments and/or critics are welcome.
http://www.chrisid.com/blog/2010/10/how-to-publish-iphone-app-with-flash-cs5-for-beginners /
cheers,
Chris.

It helped me a lot, exept I hav this little problem ..
I can't select the .p12 file .. it's disabled..

Lightroom VS Photoshop Elements for Beginners

Hey Everyone!
I am creating a website for beginners on computers and other home electronics and I am going to do a post about what the best program is to get for a beginner at photo editing. I have seen so many people using Photoshop Elements to start out with but many people who have gotten editing programs prefer Lightroom and use it and say its a better program to begin with... Do you have any suggestions on which I should tell poeple to go with? Here is a link to my blog http://cowtechtutor.com so that you know the kind of posting I've been doing also if you have any suggestions on how I can improve the design it would be awesome! Thanks very much!
Andrew

They each have strength and weaknesses. LR for example has the same full RAW processor as full Photoshop, but doesn't have the full range of image editing features.
There isn't a simple answer. I think you would be better off reviewing both and pointing out the differences so that your blog audience can make an informed decision for themselves.
Cheers,
Neale
Insanity is hereditary, you get it from your children
If this post or another user's post resolves the original issue, please mark the posts as correct and/or helpful accordingly. This helps other users with similar trouble get answers to their questions quicker. Thanks.

C++ Compilers for Beginners

Similar Messages

Maybe you are looking for