Enter Text:
SAP

SD

Enter Text:

abap

Book Link:
Questions and Answers Book

Hi,

Can please

some one help me to give me a document of all user eixts, validations and substutuions that are used in only FICO.

Or

atleast can some one help to get a list of user exits only that are used in FICO. Please dodnt give the trasaction

code CMOD or SMOD, which will give us whole list of user exits in SAP

Thanks
Jayapal

I was recently thinking that

if you are starting a new SAP implementation - what are major things that you would like to nail down first at the team

level? Some of the things that you would attack the first! Here are some of the Org Structure and other stuff that I could

think of. Do you have anything to add to this list?

• Chart of Accounts - Fiscal year Variants, Posting Period

  Variant

• Company Codes

  - incl. International Company codes.

This is indeed incredible pace! These guys have trained 500 users in just 3 weeks in multiple modules. We have generally used

personal training formats.. but the softwares like STT trainers may help ease out the Change Management rigors!

Jo Ann Stores, the leading national fabric and craft retailer in the U.S., successfully

trained and tested 500 of their end users on SAP in just three weeks, using simulations generated with Kaplan's leading

enterprise application training software, STT Trainer.Simulations are realistic recreations of applications in

which end users are free to learn how to use an application without fear of impacting the "live" system.

Simulations also provide end users onscreen guidance and instruction on how to perform tasks.STT Trainer enabled

the rapid development and deployment of Jo Ann Stores' software simulations for the training and testing of over 500 of

their end users during the company's SAP R/3 upgrade project. The customized simulations trained users across a range of Jo

Ann Stores' SAP modules, including Financial Accounting, Controlling, Materials Management, and Sales and

Distribution.

Here are some best practices for BI Tool selection. These are good pointers

here from Tim Furey - however, he has analyzed this important decision

from the BI silo only! In my view, that is a major problem with most of the decision making that goes

about in the industry today! BI is the HOTbed on which most of the future applications (assuming the company is still

running with OLTP but not much of OLAP environment in place).Â

Data Locking is another concern that we all face in BPS but not many folks understand it

completely.

Data is locked against access from other planning sessions within a planning session from the

moment where it was accessed with write access. A lock generated once by the system lasts until the planning session is

terminated.

The background for this behavior is that only in this way can an improvement in the response

times be reached: Only when accessing the data for a certain characteristic combination for the first time, is the database

is accessed. session.
...

Text Body:
I love the Characteristic Relationships as they help and

automate the validation and data entry stuff.. here is another piece of gem from the SAP HELP!!

The

following advantages result from data entry in manual planning:
In a planning layout for which the option "All

Possible Characteristic Combinations" was selected, the Cartesian product is not (as in earlier releases with the option

"form-based") formed of all theoretically possible combinations of characteristic values, but instead only those combinations

that were defined as sensible in the defined characteristic relationship. For example, in a lead column that contains the

characteristics cost center and currency only the valid currency for this is offered for data entry for every cost center

(and not all currencies contained in the package selection) As a result, data entry is made much easier since only the really

relevant value combinations are offered. In addition, such planning layouts are now much more compact and clearer and this

leads to better answer times of the system.

Here is another cool example of copying from one Planning Area to another

(using Multi-Planning Area, of course) - from a granular level to a rolled up aggregated

level:

Copying with Automatic Summarization

You want to copy the transaction data from

planning area G1 into area G2. Both areas contain the same key figures. Whereas the independent characteristics article and

article group are in G1, G2 only contains the characteristic article group. For this reason, the breakdown according to

individual articles will inevitably be lost for the data to be copied to G2 – the data is automatically aggregated. To

achieve this, you create the copy function in the context of a planning level, which only contains the characteristic article

group. Therefore, you require the following objects in all: