Routines related to SAP SD module

Hi can anyone give me some links related to SAP SD module plz. I am new to routines, please help me out.
Thanks in advance.
I apprecieate ur help

Here are some links related to SD Module.
http://www.sap-img.com/sap-sd.htm
http://help.sap.com/saphelp_46c/helpdata/en/8c/df293581dc1f79e10000009b38f889/frameset.htm
Regards,
RIch Heilman

Similar Messages

  • Case studies  related to SAP-PS

    Hi All,
    What is case studies  related to SAP-PS module. If anyone has kindly let me know.
    Regards

    Hi Virendar,
    Case studies means from where I can get the business  scenario related with SAP PS for various industries.
    Regards

  • Relation between SAP Modules

    Hi ,
    I am looking for some document or some website where I can get information on the relation between SAP Modules. For example, How SD, MM, PP, FI and other modules are related to each other in what functionality and how, etc. Diagram or even document is fine.
    Pls. help me out.
    Regards,
    VaishaliRaj
    Please search the forum before posting a thread
    Edited by: Pravender on Aug 2, 2010 1:05 PM

    HI VAISHALI,
    Pls see below links u will get help--
    http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
    Relation between SD and MM  modules - Table name which links 2 modules
    hope it helps
    Thanks,
    Nilesh Pathak

  • Work flow and tables related with ESS Travel Module

    Hi Experts,
    I am new for work flow. Presently I am working for SAP ESS / MSS Travel module. Can you please let me know the names of work flows and tables related with ESS Travel module.
    Regards,
    Gary

    Hi Gary,
    Check if this [thread1|Let us learn SAP ESS Travel] [thread2|Travel Management Tables] helps you.
    Regards,
    Saumya

  • QUERY RELATED WITH SAP HR CERTIFICATION

    I like to do the SAP HR training . Myself MBA, working in manufacturing company having over 04 years of experience. As i am not into any IT related company nor having any prior experience or course related with computers, So, would be relevant enough for me to go for ILT from institute, and if yes, then would I be able to get job offer right after completion of course in MNC/ IT industry with good enough package though i know in starting i wont be able to get jobs with high package, but I dont have any idea about the placement criteria of MNC's for SAP HR candidates.
    Also, kindly suggest me right institute for SAP HR training and which provide good placement in Delhi/ NCR region.

    Hi Priyanka,
    as you are itself remains a recruiter so i think you better knows what will be there, but as far as i concern you will be considered as an experienced professional having exposure to SAP, not it depends on the IT Company at some extent that they will take it as a fresher, but anyhow your experience will get counted.
    When it comes to get Salary, you can get a handsome salary if they will consider you along with your experience, but literally saying some points.
    1. As most of the IT companies has started outsourcing its recruitment process, so he will not take you as you have recruitment process knowledge           (means generally they have already excluded recruitment to other firms) .
    2. HR process in SAP involves process of recruitment, appraisals , payroll management and more generally process of PMS.
    3. As job in Hr are always limited, as they are mainly hired through Campus drives, so little openings as a whole.
         So, what i will suggest you to take the help of your contacts in getting a job when you complete SAP  HR module, if you are not getting a good job in SAP HR in IT company, then you can look into non-it companies, because in non-it companies you will get more time to learn as there are no strict deadlines, as moving towards any new technology becomes handy in early days, so you can work for one more years in any non-it companies, where you clear all your doughts in SAP HR  module, then if you will move towards an IT company, it will become more fruitful to you.

  • SAP HR Module - Benefits

    Hi Gurus,
    Can you please give me any documentation or ppt's on the benefits or why to implement SAP HR Module???
    Please give me some details.
    Thank You

    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
     Basic Settings  Benefits IMG Path: Personnel Management  Define Benefit Area
    Assign Currency to Benefit Area:
    In this step, you specify the currency for the benefit area
    IMG Path: Personnel Management   Assign Currency Basic Settings Benefits
    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
    Define Basic Settings  Benefits IMG Path: Personnel Management  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  Set Current Benefit Area Basic Settings  Benefits Management
    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  Define Benefit Plan Plan Attributes  Basic Settings  Benefits Management  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   Define Benefit Plan Plan Attributes  Basic Settings Benefits  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
     Basic Settings  Benefits IMG Path: Personnel Management   Define Parameter Define Employee Criteria Groups Define Employee Groupings  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
    Define Basic Settings  Benefits IMG Path: Personnel Management   Define Age Define Employee Criteria Groups Employee Groupings  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   Define Cost Define Employee Groupings  Basic Settings Benefits  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
    Define Basic Settings  Benefits IMG Path: Personnel Management   Define Coverage GroupingsEmployee 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  Define Define Employee Groupings  Basic Settings  Benefits Management  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
    Define Basic Settings  Benefits IMG Path: Personnel Management   Define Employer Contribution GroupingsEmployee 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
     Benefits IMG Path: Personnel Management   Define Employer Contribution Groupings Health Plans Plans
    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
     Benefits IMG Path: Personnel Management   Define Options for Health Plans Health Plans 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   Define Dependent Coverage Options Health Plans  Plans Benefits
    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
    Health Plans  Benefits IMG Path: Personnel Management   Define Minimum and Maximum Number of DependentsPlans
    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
    Define Health Plans  Plans  Benefits IMG Path: Personnel Management  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
    Health Plans  Benefits IMG Path: Personnel Management   Define Cost RulePlans
    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   Assign Health Plan Attributes Health Plans  Plans Benefits
    Insurance Plans:
    In this step, you define general data for insurance plans
    IMG  Define Insurance Plans  Plans  Benefits Path: Personnel Management  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
     Plans  Benefits IMG Path: Personnel Management  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
     Insurance Plans  Plans  Benefits IMG Path: Personnel Management  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:  Define Cost Insurance Plans  Plans  Benefits Personnel Management  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
    Insurance Plans  Benefits IMG Path: Personnel Management   Define Cost RulesPlans
    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
     Insurance Plans  Plans  Benefits IMG Path: Personnel Management  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   Combined Combined Coverage  Insurance Plans  Plans Benefits  Coverage
    Combined Coverage Limit Expressions:
    In this step, you enter the second half of the equation, as discussed in combined coverage
    IMG Path:  Combined Coverage  Insurance Plans  Plans  Benefits Personnel Management  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  Combined Insurance Plans  Plans  Benefits Path: Personnel Management   Review Age Groups for Imputed IncomeCoverage
    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   Review Calculation Combined Coverage  Insurance Plans  Plans Benefits  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
     Savings Plans  Plans  Benefits IMG Path: Personnel Management  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:  Define Employee Savings Plans  Plans  Benefits Personnel Management  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:  Define Employee Savings Plans  Plans  Benefits Personnel Management  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  Define Employer Contribution Savings Plans  Plans  Benefits Management  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:  Define Employer Savings Plans  Plans  Benefits Personnel Management  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
     Plans  Benefits IMG Path: Personnel Management   Assign Savings Plan AttributesSavings Plans
    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  Define Flexible Spending Accounts (FSAs)  Plans  Benefits Management  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
    BenefitsIMG Path: Personnel Management   Assign Spending Account Flexible Spending Accounts (FSAs)  Plans  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
     Flexible Administration  Benefits IMG Path: Personnel Management  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  Benefits Flexible Administration  Benefits Path: Personnel Management   Define Benefit Adjustment GroupingsAdjustment Reasons
    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
     Flexible Administration  Benefits IMG Path: Personnel Management   Define Benefit Adjustment ReasonsBenefits 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
     Benefits IMG Path: Personnel Management   Define Adjustment Benefits Adjustment Reasons Flexible Administration   Health PlansPermissions
    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   Define Benefits Adjustment Reasons  Flexible Administration Benefits   Insurance PlansAdjustment Permissions
    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  Benefits Flexible Administration  Benefits Path: Personnel Management   Savings Plans Define Adjustment Permissions Adjustment Reasons
    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
     Benefits IMG Path: Personnel Management   Define Adjustment Benefits Adjustment Reasons Flexible Administration   Spending AccountPermissions
    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  Define First Programs  Flexible Administration  Benefits Management  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
    Flexible Benefits IMG Path: Personnel Management   Define Second Program Grouping Programs Administration
    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:  Employee Programs  Flexible Administration  Benefits Personnel Management   Define Eligibility GroupingsEligibility
    Eligibility Variants:
    In this step, you define eligibility variants. These consist simply of an identifier and a description
    Flexible Benefits IMG Path: Personnel Management   Define Eligibility Employee Eligibility  Programs Administration  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
    Flexible Benefits IMG Path: Personnel Management   Define Eligibility Employee Eligibility  Programs Administration  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:  Programs  Flexible Administration  Benefits Personnel Management   Define Termination GroupingsParticipation Termination
    Termination Variants:
    In this step, you define termination variants. These consist simply of an identifier and a description
    IMG Path: Personnel Management   Participation Termination  Programs  Flexible Administration Benefits  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
    Flexible Benefits IMG Path: Personnel Management   Define Termination Participation Termination  Programs Administration  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  Programs  Flexible Administration  Benefits Path: Personnel Management  Define Benefit Programs
    Dependent/Beneficiary Eligibility:
    In this step, you define family member groupings and determine how family members are allocated to these groupings
     Benefits IMG Path: Personnel Management   Define Family Dependent/Beneficiary Eligibility Flexible Administration  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   Define Dependent/Beneficiary Eligibility  Flexible Administration Benefits  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
     Flexible Administration  Benefits IMG Path: Personnel Management   Define Dependent EligibilityDependent/Beneficiary 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  Dependent/Beneficiary Flexible Administration  Benefits Management   Define Beneficiary Eligibility Rule VariantsEligibility
    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
     Flexible Administration  Benefits IMG Path: Personnel Management   Define Beneficiary EligibilityDependent/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
     Flexible Administration  Benefits IMG Path: Personnel Management   Assign Eligibility Rule Variant toDependent/Beneficiary Eligibility  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
    Choose COBRA COBRA  Benefits IMG Path: Personnel Management  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
    Choose COBRA Spending COBRA  Benefits IMG Path: Personnel Management  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.
    Define Qualifying Event COBRA  Benefits IMG Path: Personnel Management  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
    Assign COBRA  Benefits IMG Path: Personnel Management  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
    Define Notification COBRA  Benefits IMG Path: Personnel Management  and Payment Intervals

  • Sap Function module

    Hello
    May I know is there any existing SAP function module that can be used to read description of status for table VBUK-KOSTA,FKSTA,WBSTA etc .. (picking status, billing status).
    Points will be rewarded if answer is helpful. TQ
    Message was edited by:
            Hui Leng Yeoh

    hi,
    Refer to this related thread
    Purpose of STATUS_READ function module
    Regards,
    Santosh

  • How to create a routine call in FM (FI Module)

    How to create a routine call in FM (FI Module)

    Anu,
    I've attached a really short example that does something like what you're talking about.  It just compares the user's username and password a pre-determined username and password and then "logs the user in" based on that comparison.  Like Greycat said, you probably want to store this username and password info in some sort of file on the PDA that's in an encrypted format for both security and flexibility of your application.
    I hope this helps,
    Justin D.
    Applications Engineer
    National Instruments
    Attachments:
    LoginVI.vi ‏17 KB

  • Exception handling for a standard SAP Function Module - the OO way

    Hello,
    I was wondering what is the correct way to call a standard SAP function module inside a method of global class.
    I want to display the error via the:
    get_text( ) and get_longtext( ) methods.
    I don't want to use the sy-subrc check. Is this possible?
    My example doesn't seem to work...
    See example bellow:
    DATA: ex_object_cx_root TYPE REF TO cx_root,
          ex_text TYPE string,
          ex_text_long TYPE string.
    TRY.
          CALL FUNCTION 'L_TO_CONFIRM'
            EXPORTING
              i_lgnum                        = i_lgnum      " Warehouse number
              i_tanum                        = i_tanum      " Transfer order number
              i_quknz                        = '1'          " '1' - confirm withdrawal only (picking )
              i_commit_work                  = 'X'          " Indicator whether COMMIT WORK in function module
            TABLES
              t_ltap_conf                    = it_ltap_conf " Table of items to be confirmed
            EXCEPTIONS
              to_confirmed                   = 1    " Transfer order already confirmed
              to_doesnt_exist                = 2
              item_confirmed                 = 3
              item_subsystem                 = 4
              to_item_split_not_allowed      = 51
              input_wrong                    = 52
              OTHERS                         = 53.
        CATCH cx_root INTO ex_object_cx_root.
          ex_text = ex_object_cx_root->get_text( ).
          ex_text_long = ex_object_cx_root->get_longtext( ).
          " Error:
          RAISE EXCEPTION TYPE zcx_transfer_order
            EXPORTING textid = zcx_transfer_order=>zcx_transfer_order
                 err_class = 'ZCL_WM_TRANSFER_ORDER'
                 err_method = 'CONFIRM_TO_2STEP_PICKING'
                 err_message_text = ex_text
                 err_message_text_long = ex_text_long.
      ENDTRY.
    Thank you very much in advance

    Hello Marko,
    If i understand correctly you've enclosed the call to the FM 'L_TO_CONFIRM' inside the TRY ... CATCH ... ENDTRY block.
    CATCH cx_root INTO ex_object_cx_root.
          ex_text = ex_object_cx_root->get_text( ).
          ex_text_long = ex_object_cx_root->get_longtext( ).
    You can't do this because the FM 'L_TO_CONFIRM' doesn't propagate OO exceptions!
    Your approach is almost correct, what you've to do is goes like this:
    CALL FUNCTION 'L_TO_CONFIRM'
      EXPORTING
        i_lgnum                        = i_lgnum      " Warehouse number
        i_tanum                        = i_tanum      " Transfer order number
        i_quknz                        = '1'          " '1' - confirm withdrawal only (picking )
        i_commit_work                  = 'X'          " Indicator whether COMMIT WORK in function module
      TABLES
        t_ltap_conf                    = it_ltap_conf " Table of items to be confirmed
      EXCEPTIONS
        to_confirmed                   = 1    " Transfer order already confirmed
        to_doesnt_exist                = 2
        item_confirmed                 = 3
        item_subsystem                 = 4
        to_item_split_not_allowed      = 51
        input_wrong                    = 52
        OTHERS                         = 53.
    IF sy-subrc <> 0.
      MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
              WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4
              INTO ex_text. "Get the ex_text by this technique & not by CX_ROOT->GET_TEXT()
    ENDIF.
    I'll have to check how to fetch the long text of the message
    BR,
    Suhas

  • IDOC message type for "Site" in SAP Retail module?

    Hi All,
    We have the need to transfer master data (through master data change pointers) of Retail Sites within the SAP Retail module (transaction:  WB01, WB02).  Does anyone know if there's an IDOC message/type already associated with this?  Thanks in advance for your help!
    Cheers,
    Matt

    Hi,
    please read SAP notes 892103 and 551035.
    The correct IDOC type should be FIDCC1 / FIDCC2.
    Best regards,
    Andreas

  • Configuration steps involved after creation of new personnel subarea in sap hr module

    Dear Friends,
    Let me know what all config to be done after creation of a new personnel sub area in SAP HR module?
    So that all infotypes including IT0007 & IT0008 are captured for hiring an employee & running the payroll ?
    Reg,
    TD

    Hi Tanuja,
    Normal customization only you have to do for every PA & PSA. if you don't have the steps i will give you the steps.

  • Queries related to sap Basis.

    Dear  All
                     Can any body tell me queries related to sap Basis.
                     Which data sources need to be installed and what are the cubes and dso's  which gives information related to SAP BASIS.

    Hi,
    It might not be installed in ur system Thats y u are unable to find.
    Goto rsa1->BI Content ->Infoproviders by infoareas....There u shall find 0DBH infoarea. It is Database performance.
    In my client Basis people are using some of the cubes from this infoarea.
    But datasources are generic.
    Hope this helps.
    Regards,
    Guru

  • REQ SAP FI MODULE- CERTIFICATION EXAM QUESTIONS AND ANSWERS

    REQ SAP FI MODULE- CERTIFICATION EXAM QUESTIONS AND ANSWERS
    Moderator: We should be thankful that you don't require to solve the exam for you

    Please type "certification" in the search field, you can find many threads regardding this.

  • Query related to SAP

    I have a query relating to SAP, specifically when using the Create New Session button. In the past when using this button, it has always created a new SAP session with the window displaying the SAP Easy Access  User Menu... front end, with all my favourite transactions listed. However, recently this user menu has disappeared and the window is blank, meaning I have to type the transaction in the top left box, which, whilst not preventing use, is a little annoying and awkward!
    I dont believe I have changed any options recently and can find no settings that look like they would bring the user menu back but it would be really useful if it did! (It is probably worth mentioning that this only occurs when creating a new session; when starting a new SAP session in the first instance, the user menu appears...)
    Please help me out
    Many Thanks,
    Sunny

    Hi,
    SAP GUI version - 7.10
    i am using a desktop, tried logging in another desktop ,same problem.
    Recently there is a HARDWARE migration occured , might be this also effects the settings ?
    please Advise.
    Sunny

  • Reading SAP function modules using FromSAPIdentity pass

    Hi,
    We have SAP NW IDM 7.2 SP7 environment
    And I have been using FromSAPIdentity pass to read SAP function modules.
    A typical configuration will looks like below
    Above works like a charm and everything is as expected :-)
    Now i am trying to fetch data from another function module.
    Here the challenge is import parameter entry need to be provided with selection criteria say something like below for PARAMETER1
    SIGN=E
    OPTION=EQ
    LOW=<Value>
    HIGH=<Value>
    Does FromSAPIdentity pass accepts selection criteria input for "PARAMETERS" ?
    If yes, which format should i follow to provide those values ?
    Thanks
    Karthik

    Use DD03L table .
    Also use this FM.
    F4_DD_TABLE_FIELDS
    DD_GET_DD03P

Maybe you are looking for

  • Could not create certificate request

    jdev version: 10.1.2.3.0 Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Prod PL/SQL Release 10.2.0.4.0 - Production TNS for Linux: Version 10.2.0.4.0 - Production How can i create a certificate signing request like that: CN=EURTRANSBEL O

  • CAT2 - making user defined feild visible in profile

    Hello , am facing a issue , I need to create a New profile in CAC1 [ done] by coping the already existing profile. IN already existing profile we have made DISPLAY settings to "CATS_ADDFI-FIELD1" - Additional field 1. This is defined as ACTIVITY DESC

  • Problems in UJD_TEST_PACKAGE - AnswerPrompt

    Hi gurus, I am facing a problem, when I'm trying to automate Master Data from a flat file to a dimension. I make a prompt to load the data, but when I try to upload to the UJD_TEST_PACKAGE program, I select it from the matchcode but nothing is update

  • LDB reg

    Hi all, WHile using LDB (PNP) how to make the current year as default. tnx tnx for your replies. but it is like selecting the current year option(radio button) by default in standard LDB(PNP). is it neccessary that i have to go for Module Pool Progra

  • What are your views on view?

    Hi, On the record set there is a feature on, view! How will this be use? Is this at the database stage where User access to the database tables are restricted and where it could trigger off a user login?