Re: System maintenance in SAP each module

Dear consultant,
I need some information from Business process consultant. How do maintain the system maintenance for SAP each module?
We have maintained the system in SAP system. Please reply me.
Regards,
Krishnna.

Ámit Güjärgoüd wrote:
>
> Rolling On The Floor Laughing My Apple Off ?
>
LOL
Click to see what it is!
prashanth kishan wrote:
> > Rolling On The Floor Laughing My Adam's-Apple Off
> > pk

Similar Messages

Interface between business ware house system and SAP SD module

hi,
I want to develop interface between business ware house system(file adapter) and SAP SD module. how can i post the data into SD system? can any one tell me which Idoc i should use in receiver side?
if i want to go abap proxy how can do it?
give some inputs(methods which i should use)
Thanks in advance
regards
Ruban

Hey
the selection of IDOC depends upon what you wanna post into SD.get in touch with the ABAP guys and they should be able to tell u exactly which IDOC to use.
once u have decided on IDOC,you can go for a File to IDOC scenario.
as far as proxies are concerned,they kinda give better performance compared to IDOC but you need to do ABAP coding for them,in that case u dont need any IDOC
Thanx
Aamir

Create user in SAP GRC AC 5.3 for each module (RAR, CUP, SPM, ERM).

Hello,
I have a doubt.
The users of the modules of the SAP GRC AC 5.3 have to created in the UME of the EP Core, is that right?? And thet add the roles of each user for each module (RAR, CUP, SPM, ERM), is that right?
Best Regards.
Pablo Mortera.

Hi Pablo,
To access GRC AC 5.3 you can create one UME user and assign different roles related to four GRC component.
Or you can create different GRC user and assign respective components roles.
The example of GRC Admin role are.
AEADMIN
READMIN
VIRSA_CC_ADMINISTRATOR
regards,
Sudip,

'Log Book' in plant maintenance (SAP PM module)

Dear Experts
I want to know about 'Log Book' in plant maintenance (SAP PM module). How to work on LOG BOOK & what are the configuration settings available in SAP PM for Log Book?
Basically, the concept of logbook is to update shift activities & measures during Plant Maintenance without SAP. but in SAP, What i know about the Log book in SAP PM is : It is an industry specific feature, before it was only used in (IS- Aeronautical). but now it is available in ECC 6.0 also. To activate this node, we need to update the patch 2.0 in ECC 6.0
Thanx,
PMGURU

Dear,
The Logbook is an easy-to-use tool that supports the controlling and execution of daily maintenance tasks for assets in operation. This tool provides personnel, who are operating the assets, with the functions to log defects and operational data. It provides maintenance personnel, such as maintenance engineers and technicians, with functions that ensure the timely and reliable execution of their maintenance tasks.
Logbook is easy to use and provides functionality that is seamlessly integrated with follow-on processes of the mySAP for Aerospace & Defense solution for Maintenance, Repair and Overhaul (MRO). For example, operational data captured in the Logbook updates measurement points that, in turn, trigger preventive maintenance events. Maintenance work steps created in the Logbook generate material and resource requirements in materials and capacity planning. Material exchanges update the asset structure and automatically generate the required goods movements.
An important business example for using the Logbook is to control the daily line maintenance tasks for aircrafts.
The logbook helps you record defects encountered during aircraft flights and the actions taken to correct them. The log may also include the space to record additional flight data, such as the names of the crew members, flight parameters, payload data, fueling data, flight hours, and cycles operated.
Regards,
Rakesh

How to know each field function in sap mm module ?

how to know each field function in sap mm module ?
i know by press f1 but any easy way that to brief explanation.

Dear Ramakrishna,
What you have mentioned is correct.
Press F1 to find out the meaning of that field and you can also refer this link to know more about MM
Module,
http://help.sap.com/saphelperp60_sp/helpdata/en/9c/df293581dc1f79e10000009b38f889/frameset.htm_
http://www.sap-img.com/
Regards
Mangalraj.S

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

To implement SAP HCM module in existing SAP ECC 6.0

Hi,
I have SAP ECC 6.0 system already implemented 2 years back.
I am planning to implement SAP HCM with OM, PA, SAP Time management, SAP PAYROLL in existing SAP ECC 6.0 system.
I have currently 3 system landscape for SAP ECC.
I would like to know what change/addition is required in above landscape to implement SAP HCM module in existing SAP ECC 6.0
Do share your view.
Regards.

Hi.
As per you, Already designed Landscape. Why dont you follow you existing Landscape which is alredy proved for other modules.
Normally Dev/Quality/Production clients will there..
If more that depends upon flexibility in Each client and defining different business for testing and production interfaces purpose.
Better use Existing only remaining modules already sucessfully running in Production Right????

What is the Three System Landscape in SAP

Hi All,
Please explain me What is the Three system Landscape in SAP.
Thank you very much,
Kavya.

1. Database Layer
The database layer consists of a central database system containing all of the data in the R/3 System. The database system has two components - the database management system (DBMS), and the databse itself. SAP does not manufacture its own database. Instead, the R/3 System supports the following database systems from other suppliers: ADABAS D, DB2/400 (on AS/400), DB2/Common Server, DB2/MVS,INFORMIX, Microsoft SQL Server, ORACLE, and
ORACLE Parallel Server. The database does not only contain the master data and transaction data from your business applications, all data for the entire R/3 System is stored there. For example, the database contains the control and Customizing data that determine how your R/3 System runs. It also contains the program code for your applications. Applications consist of program code, screen
definitions, menus, function modules, and various other components. These are stored in a special section of the database called the R/3 Repository, and are accordingly called Repository objects. You work with them in the ABAP Workbench.
2. Application Layer
The application layer consists of one or more application servers and a message server. Each application server contains a set of services used to run the R/3 System. Theoretically, you only need one application server to run an R/3 System. In practice, the services are distributed across more than one application server. This means that not all application servers will provide the full range of services. The message server is responsible for communication between the application servers. It passes requests from one application server to another within the system. It also contains information about application server groups and the current load balancing within them. It uses this information to choose an appropriate server when a user logs onto the system.
3. Presentation Layer
The presentation layer contains the software components that make up the SAPgui (graphical user interface). This layer is the interface between the R/3 System and its users. The R/3 System uses the SAPgui to provide an intuitive graphical user interface for entering and displaying data. The presentation layer sends the users input to the application server, and receives data for display from it. While a SAPgui component is running, it remains linked to a users terminal
session in the R/3 System.
REWARD POINTS IF HELPFUL
Message was edited by:
vijay kamath

Getting error while opening layout in mobile system maintenance

Hi Experts,
I implemented note 904571 to prefilldata, with which all standard layouts loaded to mobile system maintenance. But problem here is if I try to open any one of the layout its giving following error
"An unhandled exception has occured in your application. If you click continue, the application will ignore this error and attempt to ccontinue. If you click Quit, the application will be shut down immediately.
Object variable or with variable not set."
If I click on details of error, its giving following details
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
Exception Text **************
System.NullReferenceException: Object variable or With block variable not set.
   at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
   at MSY.Tlayoutdet1.ctrlctrlbtnOpen_onClicked() in C:\Ars_Translation50\Batch\app\MSY\src\Tlayoutdet1.vb:line 281
   at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.BtnClicked()
   at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.IPeerCtrlListener_btnClicked()
   at SAP.MT.FW.UI.PeerLayer.PeerCtrlButton.button_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NBaseControl.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NButton.OnClick(EventArgs e)
   at SAP.MT.FW.UI.NativeControl.NButton.mButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Loaded Assemblies **************
mscorlib
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
MobileClient
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MobileClient.exe
UFCore
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCore.DLL
UFCoreExt
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCoreExt.DLL
System.Windows.Forms
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2365
    CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
System
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
UFInternal
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFInternal.DLL
UFCommon
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCommon.DLL
UFStorage
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFStorage.DLL
Interop.Scripting
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.Scripting.DLL
Microsoft.VisualBasic
    Assembly Version: 7.0.5000.0
    Win32 Version: 7.10.6310.4
    CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
UFControlLibrary
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFControlLibrary.DLL
Interop.UFGeneratorInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFGeneratorInterfaces.DLL
System.Drawing
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2327
    CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
MTIServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTIServices.DLL
UFDialogs
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFDialogs.DLL
UFIPlugins
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFIPlugins.DLL
System.Xml
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2371
    CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
Interop.ERRCOMPLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.ERRCOMPLib.DLL
MTBLLFWInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWInterfaces.DLL
Accessibility
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.573
    CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
MSY
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bin/MSY.dll
MTBLLFW
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFW.DLL
MTFWServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTFWServices.DLL
MTServices
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTServices.DLL
OnlineOffline
    Assembly Version: 1.0.2477.11060
    Win32 Version: 1.0.2477.11060
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/OnlineOffline.DLL
vqq-mx7r
    Assembly Version: 0.0.0.0
    Win32 Version: 1.1.4322.2407
    CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
RegexAssembly40_0
    Assembly Version: 0.0.0.0
    Win32 Version: n/a
    CodeBase:
MTBLLFWMetaInternal
    Assembly Version: 5.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWMetaInternal.DLL
TLSender
    Assembly Version: 1.5.1.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/TLSender.DLL
Interop.CRYPTINGLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.CRYPTINGLib.DLL
Authentication
    Assembly Version: 5.5.0.0
    Win32 Version: 5.5.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Authentication.DLL
System.Data
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2365
    CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
System.EnterpriseServices
    Assembly Version: 1.0.5000.0
    Win32 Version: 1.1.4322.2326
    CodeBase: file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
sfabol
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bol/apps/sfabol/vba/WBIT/sfabol/bin/sfabol.dll
SSActiveTreeView.SSTree
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.SSTree.dll
SSActiveTreeView
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.DLL
AxSSActiveTreeView.AxSSTree_EventsRouter
    Assembly Version: 0.0.0.0
    Win32 Version: 0.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/AxSSActiveTreeView.AxSSTree_EventsRouter.dll
Interop.UFBBInterfaces
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFBBInterfaces.DLL
StdType
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/StdType.DLL
Microsoft.VisualBasic.Compatibility
    Assembly Version: 7.0.5000.0
    Win32 Version: 7.10.3077
    CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic.compatibility/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.compatibility.dll
stdole
    Assembly Version: 7.0.3300.0
    Win32 Version: 7.00.9466
    CodeBase: file:///c:/windows/assembly/gac/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
RFMobileReporting
    Assembly Version: 1.0.0.0
    Win32 Version: 5.11.0.40
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/RFMobileReporting.DLL
AxInterop.SAPCalendar50
    Assembly Version: 1.1.0.0
    Win32 Version: 1.1.0.0
    CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/AxInterop.SAPCalendar50.DLL
JIT Debugging **************
To enable just in time (JIT) debugging, the config file for this
application or machine (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the machine
rather than being handled by this dialog.
Its urgent, Please help me out to rectify this error.
Thanks & Regards,
Venkata Ramana

This seems like an error with standard SAP solution. I would suggest raising an OSS message and SAP should be able to help you out.
Hope this helps.
Regards,
Kaushal

For Professional level certification aspirants in SAP Controlling module

Dear all Professional level Certification aspirants in SAP CO module,
I have recently passed the Certification test on SAP Management Accounting (CO) module in version ERP 6.0 EHP4. I have more than 4 years experience in SAP Controlling module.The following are some of my suggestions regarding preparation for the exam.
1. All the questions were scenario based. The exam tests expert level knowledge and real time scenarios in the module. The theoritical knowledge is not sufficient to clear the exam. Unless you have atleast 5 to 6 implementations in Controlling module, it is not advisable to give it a try.
2. Detailed knowledge of the system configuration settings about the various courses mentioned in the syllabus is required. One needs a clear understanding of Special costing functions, ERP integration, Transfer Pricing, Material ledger, New GL Parallel valuation, Planning and Budgeting fuctions in various components etc.
3. The exam tests in-depth knowledge about various integration aspects of Controlling module with other modules. The advanced master data functionalities of other logistical modules like MM, SD, PP, PM, QM, PS, CS, HCM is tested in detail.
4. Several methods of process and performance optimization of the system are also tested.
3. Some reporting aspects of BW and BI are also tested. The cross application aspects of the system are also tested.
4. The exam also tests the real time skills in preparing Blueprints, Business Process design and trouble shooting the system. Being knowledgeable about some of the processing errors and message classes will be of great help.
Hope this information helps you in preparing for the certification.
Should you need any clarifications, please post a reply to this thread and I will post answers.
All the Best!!
VS.

Hi Vikrant,
the pass mark for the exam is 58%. However it may be different. The passing mark shown on your screen on the day will be the correct passing mark.
All the questions were scenario based which would involve high analytical skills and through understanding of the system integration. It would be difficult to tell any specific question. The questions carry different weightage. If you answer the questions with less weightage correctly than the questions with more weightage, you end up scoring less though you answer more number of questions correctly. and it is vice versa. Go through your syllabus and cources and try to concentrate on the topic areas which contain more weightage.
Moreover, the exam is not completely technical in nature. It tests a lot of analytical and problem solving skills required on the job.
Note:Please do not ask the questions or contents of the exam as they are confidential.
Hope this information helps you.
All the best for your exam!
Regards,
Vishnu.

BAPI's in SAP SRM Module

Hi SAP Gurus,
Please provide me the list of BAPI's with its descriptions for SAP SRM module.
regards,
George.

Hi,
Which BAPIs are you looking for ? What's your detailed requirement ?
Using SE37 Transaction, you cand find the BAPI Function modules.
Search using BAPI* or META* to get all the existing SRM BAPIs.
Meta function are generic call to external system. Depending on system kind and release, the function to call is different. The bapi that the Meta will effectly call in a backend is defined in table bbp_function_map.
Some sample BAPIs in SRM ->
Re: get vendor number BAPI or functional module
Standard BAPI to pull out data from SRM 5.5
BAPI_POEC_CREATE
bapi_srm_doc_getlist
BBP_VENDOR_GET_NON_BAPI
BAPI_PCA_MASTER_CREATE
BAPI_ORGMASTER_REPLICATE
PCA_MASTER_CREATE
BAPI_ORGMASTER_SAVE_ORIG_MULT
BAPI_ORGMASTER_SAVE_REPL_MULT
BBP_BAPI_CONF_CREATE_IN
BBP_BAPI_CONF_RESPONSE_CRT
BBP_BAPI_INV_RESPONSE_CRT
BBP_BAPI_INV_SEND
BBP_BAPI_IV_CREATE_IN
BBP_BAPI_PCO_CREATE_IN
BBP_BAPI_PO_SEND
ALE_ORGMASTER_SAVE_REPL_MULT
IDOC_INPUT_ORGMASTER
RSO_GET_MASTER_DATA
RSSEM_UPB_MASTER_DATA
UPDATE_MASTER
MASTERIDOC_CREATE_REQ_ADRMAS
MASTERIDOC_CREATE_SMD_ADRMAS
UPC_MASTER_DATA_MAINTAIN
RSDPW_MASTERDATA_UPLOAD
UPC_BW_MASTER_DATA_MAINTAIN
UPSDL_MASTER_IDOC_CREATE
MASTER_IDOC_CREATE_UPSMAS
MASTER_IDOC_CREATE_UPSRCP
BR,
Disha.
Do reward points for useful answers.

SAP Functional Module for authorization tables

I would like to know are there any standard SAP Functional Modules which could update the Authorization Tables, like AGR_1251.
Thank you

Hi Prabhu,
Other than function modules with role, I had also tried to look for function modules with AuthObject*.
Because, I would like to update remove one of the authorization object from the system. For example, remove all data which AUTHORIZATION OBJECT = S_SCD0 and ACTIVITY = 06 in the system.
I got the list of functions from the search, but all of them are without proper documentations. So is very hard for me to understand their functionalities and purposes.
Kindly advice.
Thank you.

SAP HR MODULES

hi
what are the SAP HR Modules that I can specialize in as a SAP HR Support consultant?

Hi Vee Nel,
If you are working in a support project you can get expertise on the modules that are been used in that specific project.It all depends on the project which you are working or going to work.
In support projects you can expect lot of work if the project is not stabilised , and on the other hand you may not have hands on enough work if the project is stabilised.
Comming to Modules in HCM, as I said earlier each client will have different modules and based on country specific too. If you are suppporting US clients then you will get a chance to work on OM PA TIme, Payroll ( some time upto gross calculations, and some times till net calculation) Travell, and Benefits. Compensation management, LSO, PD , TE will be used by some clients. Same with Indian and UK Clients too. It all depends on client and project which we are working on.
All the best.
Regards,
Sri..

Programmed system maintenance

I read that OSX has pre-programmed system maintenance and there is discussion on whether the computer should be turned off at night.
Is there someplace I can check or reset my system maintenance?

To check when your Periodic Maintenance Scripts, which I hope is what you want to know, open Terminal and type this exactly:
ls -al /var/log/*.out
Press Return
and you should see three lines of info, one for each script: Daily, Weekly & Monthly. The date and time they were last run is in each line.
To manually run the scripts open Terminal and type:
sudo periodic daily weekly monthly
Press return. You will be prompted for your Admin password and you need to type this into Terminal. Be warned, it might take a long time to run the scripts.
For more info checkthe most excellent:
The X Lab
Hope this helps
MacBook Pro 15" Mac OS X (10.4.9) 1.83 GHz Intel Core Duo

Can a SQL Server stored procedure call an SAP function module?

Can a SQL Server stored procedure call an SAP function module.? The stored procedure will be called via a trigger when data records are added to a Z table.

You have two options:
- the other software can use the RFC SDK and call directly in the system
- the other software can use a database connect
Markus

Re: System maintenance in SAP each module

Similar Messages

Maybe you are looking for