Check : Are you using Group Assets ? If yes,

Check the values on your group asset consistent in relation to the assigned individual assets. With other words if your assigned individual asset(s) have accumulated APC values the group asset should have accumulated APC values, too.

SAP strictly recommends to assign NOT to one group asset single assets with postive and negative accumalted APCs values. Negative and positive individual assets should then be managed separately on one group asset in each case.

[wp_eStore_fancy2:product_id:7:end]

This document help you to organize your knowledge and make it in systematic and presentable form. This document can be use as power in your hand during your interview.

This document also useful for those who are going to appear for SAP HCM certification examination.

This document cover general question and answers as related to technical and functional side of HCM. This document will also be useful for if you are working on the project and you need to sound your fundamentals

Some of the related topics are as given below,

Approval adjustments
Automated Tab Control
Best Date for Hiring
Change Management
Compensation Management
Compensation Plan
Compensatory Time
Creating new infotypes
Custom Infotypes
Customizing PAW1
Data Migration
Debugging Rules
Deduction Wage Type
Default Wage Types
Deleting Employees
Employee Overpayment
Employee Subgroups
Employee Wages
Enter New Hire
Fast Entry
Hiring and Terminating
Holiday Calendar
HR Difficulty
HR Integration
HR Year End
Infotype IT0024
Infotype PA61
Infotypes and Users
IT0015
Leave Credits
Leave Quota
Locking Infotypes
Manual Overtime Approval
MBP Appraisal Transactions
New Hire Action
P60 Form
Payroll Classes
Payroll Results
Payroll Run
Payroll Simulation
Payroll Simulation
Payroll Wage types
PCL Error
PCR Accumulation
Personnel Calculation Rules
Personnel Rules
Planed Overtime
Profile Match
Query
Quota Computation
Quota Problems
Retroactive Accounting
Screen Header
Screen Modification
Single Payroll
Small HR Department
Taxable Wage Types
Time Confirmation
Time Evaluation
Time Types
Transporting Layouts
Upgrading HR
User management
Wage Components
Wage Type Leave Allowance
Wage type values
Wagetype Adjustment
Wagetype Processing
Web Appraisal

This document is available for download ! Click Here to know More and Buy Now !

SAP HR Interview Questions, Answers, and Explanations

 

This document is available for download ! Click Here to know More and Buy Now !

Class for order classification has not been generated

Message no. KU363

Diagnosis
To be able to classify orders for order selection or order summarization in the information system for Cost Object Controlling, you must first:
•    select the characteristics that are active in your system
•    generate the characteristics that you selected
•    generate the class in which these characteristics are to be included
You do this in Customizing under Choose and generate characteristics.

Procedure
Go into Customizing and process the step Choose and generate characteristics.

Proposed Solution

You have two options to resolve the problem depending on your business
requirement in Controlling:

1) If you required classification in controlling, you need to generate
class SAP_KKR_CLASS via OKQ3.

2) If you don’t require classification in controlling, you could
deactivate ‘Classification’ indicator for the order type via OPJH.

More infos on this issue can be found in the mentioned note 356327.

[wp_eStore_fancy2:product_id:171:end]

This document provide solution for the SAP FI AA Error AC309 Account  XXXX not allowed to be defined as reconciliation account. You can fix your problem immediately and you can do your configuration.

Details,

While assigning accumulated depreciation for unplanned depreciation GL in the AO95 screen you are getting the below error.

Account  XXXX-XXXXXX not allowed to be defined as reconciliation account
Message no. AC309

Diagnosis

Account XXXXXX is defined as a reconciliation account for fixed assets for chart of accounts XXXX and account determination XXXXXX. This is not correct in the circumstances (Balance sheet account for unplanned depreciation).

Keep in mind that the Customizing definition of the given depreciation area also influences the consistency check of the G/L accounts. This is particularly true for the posting settings in the depreciation area, if the accounts are value adjustment (depreciation) accounts.

Procedure

Change the account definition, or assign a different account.

Solution

A perfect explanation and consulting solution has been given in this document and you can fix this issue in your system immediately.

This document is available for download ! Click here to know more any Buy Now

[wp_eStore_fancy:product_id:171:end]

You may also be interested in …..

[wp_eStore_fancy:product_id:27:end]

[wp_eStore_fancy:product_id:33:end]

[wp_eStore_fancy:product_id:42:end]

This document is available for download! Click here to know more any Buy Now!

SAP Customer Relationship Management with SAP CRM 4.0

Customer Relationship Management (CRM) is a comprehensive sales, service and marketing approach to building long-term customer relationships, improving business performance, and by doing so increasing revenues and profitability.

Traditional customer relationship management relied mostly on decentralized units and in some cases only individual employees had knowledge about the customer and the company’s interaction with the customer. History of contacts with a customer and customer issues remained restricted to few people within the company.

Today SAP CRM allows all interactions to be readily available to all persons who need access to information about a customer. Contact channels include the Internet, call centers, and personal contacts.

CRM will base corporate decision making on more reliable information and thus lead to improving service, solving problems faster, retaining customers, and improving relationships.

This document cover the following concepts,

What is customer relationship management?
CRM marketing
CRM marketing planning and campaign management
Tpm – trade promotion management
Campaign automation
CRM lead management
External list management
Business partner segmentation
System landscape for CRM marketing
CRM enterprise sales
Business transactions
Sales order exchange
Sales order management in CRM
Activity management in CRM
System landscape for enterprise sales and service
CRM enterprise service
Service order management
Complaint and return management
CRM customer interaction center
Inbound telesales
Telesales outbound
Customer service and support in interaction center
Complaint management in interaction center
Complaint management in interaction center (automotive)
System landscape for customer interaction center
CRM e-commerce
E-commerce – key capabilities
E-selling b2b: sales order management
E-selling b2c: sales order management
E-selling system landscape
Internet sales (r/3 edition)
System landscape for e-selling r/3 edition
CRM field applications
Field sales order management
Additional mobile client functions:
System landscape for CRM field applications
People-centric CRM
Enterprise portal
People centric user interface (pc-ui)
Pc-ui capabilities
Customizing the pc-ui
System landscape for pc-ui:
CRM channel management
CRM channel marketing
CRM channel sales
CRM channel service
CRM channel commerce
CRM partner management
System landscape for CRM channel management
Mobile engine scenarios
System landscape components overview
Performance analysis
Marketing
Customer interaction center
E-commerce
Field sales

SAP Customer Relationship Management with SAP CRM 4.0

$40.00

[Product Details...]

Types of Configuration

Table Maintenance

Many of the transactional fields in SAP are populated from drop-down lists, maintenance of these lists is a standard activity on any project and is not considered a modification. 

Examples of Table Maintenance:

Payment Terms – Most if not all clients attach payment terms to their Sales Orders.  SAP comes loaded with a set of default terms, which can be hidden or others can be added, to fit a particular client’s needs. 

Material Groups – In the material master SAP provides Material Groups so that clients can group their materials by product line, product family, etc.  The values in this table can be changed as needed.  The values themselves are used in things like pricing, but changing the values does not change how SAP works.

No standard code or functionality is affected by adding values to these tables.

Z Conditions and Z Document types

These objects are table entries or views of several tables which are merely containers for sets of instructions SAP uses in its’ standard code to perform tasks.

Example of Z Configuration:

SAP comes with a variety of preloaded “standard” configuration, for example out-of-the-box SAP provides a standard Sales Order called OR in the system, This OR has default settings that trigger certain functions within SAP. The settings take the form of fields populated by drop down lists, check boxes, and free form text fields.  All of these settings can be changed without any development time.  SAP realizes that the Standard Sales Order may not meet a client’s needs.  The standard policy is to use the copy function, make a duplicate of the OR and rename it by putting a “Z” in front of it. So the custom order type would be called ZOR. The character Z lets anyone working on the system know that this is a copy of standard configuration and has been changed for the customers needs. Making a copy of the “OR” rather than changing the “OR” provides a baseline model incase the implementation team needs a point of reference.  This does not require development time, though the new configuration does have to be tested.  This is not considered a modification by SAP.

Formulas, Requirements and Data Transfer Routines

SAP provides “holes” in its’ code where instruction sets can be “included”.  Sample sets are included with SAP but they intend for customers to create their own as required to custom, ”configure” the system to meet business needs.  SAP does provide standard formulas, which are listed and defined in a separate document in the ASAP Implementation Assistant.  However when new formulas, requirements, or data transfer routines are needed a development resource and time must be set aside, because they are written in ABAP  or Java code. These types of code are typically not complex and do not require significant time to produce.

Example of a Formula:

In many cases rounding routinely is an issue during implementations depending on the customers pricing model.  Standard SAP rounding will round to two decimal places, however if requirements dictate that rounding should be done to the nearest nickel, dime, dollar etc., a formula could be written to satisfy this requirement.

User Exits

See Formulas, Requirements, and Data Transfer Routines.

Where Formulas, Requirements and Data transfer Routines are usually no more than a few lines of code, User Exits can be quite complex and perform a variety of functions throughout the SAP system.  But since they reside in the “holes” in Standard SAP code that SAP provides they are not considered modifications to CORE SAP.
SAPScripts/SAPSmartForms

A SAPScript is a printing program.  These programs process the outputs from SAP, Order Acknowledgements, Purchase Orders, Invoices, etc. The SAPScripts contain the layouts for the outputs and hence SAP expects every customer to customize the layouts of their documents.  This functionality is being phased out by SAP Smart Forms which are object oriented and easier to maintain.

OSS Notes

Changes (Bug Fixes) and/or corrections to SAP code which can be initiated and implemented by SAP and/or SAP customers which are properly documented and identified in such a manner as too easily allow migration to future releases with little or no intervention.

Whenever bugs are reported to SAP, the fixes they put out are call OSS notes.  By entering transaction OSS1 in SAP and assuming you have a connection to SAP, you will be linked to their OSS System, which gives you access to all of the notes, which are sorted by release and module.  If you are on ECC Release 5.0 none of the notes for prior releases should be important to you since a fix created for 4.6c would have been incorporated as standard in 5.0.  So when searching the Database you would look for notes for release ECC 5.0 or higher.

OSS Notes document the problem and the resolution. They require that an ABAP developer apply them, since it more often than not requires inserting and changing lines of Code in SAP.

During Upgrades an evaluation must be done of all the OSS notes that have been applied to see which ones are covered by the upgrade.  Any notes not covered by the new release need to be reapplied after SAP has been upgraded.

IPC aka Internet Pricing Configurator

For pricing in SAP CRM, all pricing must be loaded into the IPC a java based application. This requires that any custom pricing requirements or formulas, which were created in SAP’s ABAP programming language must be recreated in Java and loaded onto the IPC in order to do comparable pricing.

To accomplish this a java developer is required as well as extensive testing.  Pricing is very complicated in standard SAP, let alone replicating that model in another programming language and setting up communication between the two.

MAS aka Mobile Application Studio

The Mobile Application studio allows you to customize the screens in the SAP CRM Mobile client.  This is an object oriented programming tool that can be used to change layouts and remove or add fields to screens in SAP.  These screen changes do not carry over into CRM Online or SAP R/3. 

Effective use of this tool requires a developer familiar with Visual Basic and object oriented programming methodologies.

MODs aka Modifications

Changes to SAP code which are initiated and developed by SAP customers.  When Properly documented and identified these can be readily recognized and retrofitted during migration to future releases.

SAP discourages MODs without their involvement and approval.  In all cases MODs  are not support under service agreements and SAP will not support any problems they cause with the system.

If a customer works with SAP on the MOD then SAP may incorporate it in future releases at which point it becomes part of standard. 

The following OSS note should be considered before any modifications are built.

170183: What to consider when applying modifications

*SAP may support MODs if they are involved in the custom development process and support the change.
** SAP will support work in these areas only so far as it does not impact standard SAP/CRM Functionality.

Content Highlights

There are 6 different techniques available to restrict the domain of characteristic values in Variant Configuration. This document will discuss each technique in detail and offer insights into the benefits and pitfalls of each technique. In conclusion, a recommendation of the best practice will be made. This document is the precursor to the only worldwide CWG and SAP approved best practice for Variant Configuration techniques.

Table of Content

Foreword
Introduction
Background
Description of Techniques
Technique 1-Create 2 Unique Characteristics
Technique 2-Utilize Preconditions to Hide the Values until Appropriate
Technique 3-Specialize the Characteristic During Class Inheritance
Technique 4-Overwrite the Characteristic During Assignment to a Class
Technique 5-Utilize a Function Based Value Check Against a Ztable
Technique 6- Utilize Constraint Based Modeling
Comparison of Techniques
Best Practice Recommendation

This document is available for download! Click here to know more and Buy Now!

Restricting Characteristic Value Domains

[Product Details...]

]]> http://www.sapebooks.com/info/general/restricting-characteristic-value-domains/feed/ 0 http://www.sapebooks.com/info/funds-management/remove-former-budget-inconsistency/ http://www.sapebooks.com/info/funds-management/remove-former-budget-inconsistency/#comments Mon, 07 Sep 2009 11:30:40 +0000 admin http://www.sapebooks.com/info/uncategorized/remove-former-budget-inconsistency/ 1.- Run transaction FMBV ( Former budgeting) in order to reconstruct
Budget values.
2.- Run report RFFMRC04 in Test mode in order to check if there is still some inconsistency.
3.- If RFFMRC04 shows inconsistencies, then run this report in Update
Mode.
4.- Total up Budget FM9QBUD
5.- Reconstruct assigned values with FMBV again.

The question that immediately comes to your mind is naturally, “What does this mean to me?” Not much of anything until you get that fateful call from your manager. He tells you something like “We are going to put in the Variant Configuration module of SAP, and you are going to run the project!”

Sounds great right?? However, what if the only exposure you’ve ever had to SAP is seeing those interesting logo’s on sponsor advertising at the Formula One races or the local football match? “Variant Configuration”? What in the world does that mean??

The reality is many projects start out in exactly this manner. If you are lucky, you are involved in one of the good projects, where you were involved in the selection team that chose the software. In that case, you already know what Variant Configuration (also known as VC or LO-VC) is. If not, you will know it by the time you get done reading this book! Either way, you have some interesting times ahead. In this section, we will try to show you some of the typical challenges you will encounter as well as give you some practical advice on overcoming them.

To allow the project manager with no experience in configuration software to understand the challenges they may face. This document will cover a Variant Configuration project from the selection of the solution to the post go live impacts of problem solving. Along the way, helpful tips to resolve common project problems unique to variant configuration projects will be presented. This is not a technical explanation of Variant Configuration, but rather a primer for the non technical project manager.

Click here to Know more and Download Now !

!! Click Here to Free Download Sample Document !!

You can download one of sample documents for Grantor Management EUT to understand the depth of explanation and help given in these documents.

These documents cover following business processes of Grantor Management in very systematic manner.

01 – Logon to CRM GM System
02 – Create a Program (PSCD)-MultiFund-APAR
03 – Create Budget for program
04 – Register a Grantee
05 – Create an Application Form as Grantor
06 – Create an Application Form as Grantee
07 – Assess Application (BSP Web Request)
08 – Show Pre-commitment in ERP
09 – Show Budget Consumption
10 – Create Agreement
11 – Show commitment in ERP
12 – Show Budget Consumption After Commitment
13 – Invoicing Run (PSCD)
14 – Invoicing Run (AP-AR)
15 – Payment Run (PSCD)
16 – Payment Run (APAR)
17 – Claim Processing
18 – Change Request Processing
19 – Show Case Record
20 -Transfer PSCD to FI-GL (PSCD)
21 – Demonstrate MS Word integration
22 – Change the CRM User Interface

These documents can use for end user training and you can use this documents to learn grantor management. With the help of these documents you will be able to learn Sap Grantor Management very quickly.

These documents help you to understand how to run transactions in SAP CRM Grantor Management and complete your business process. These documents are very helpful for the entire sap user even if they are new to SAP CRM screens.

This document is available for immediate download. Click here to know more and Buy Now!

SAP Grantor Management End User Documents