Diff Between USEREXITS and CUSTOMER EXITS?

Hi all,
What is the Diff Between <b>USEREXITS</b> and <b>CUSTOMER EXITS.</b>REgards,
Kishore.

Hi,
A point in an SAP program where a customer's own program can be called.
In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system.
There are the following types of user exit:
User exits that use INCLUDEs -
These are customer enhancements that are called directly in the program.
User exits that use tables -
These are used and managed using Customizing.
Customer Exit
SAP creates customer exits for specific programs, screens, and menus within standard applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
· They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
· They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
Customer exits are not available for all programs and screens found in the SAP System. You can only use customer exits if they already exist in the SAP System. You find find more information about locating applications with pre-defined exits in Locating Applications that have Exits
User Exits:
User exits allow you to add additional functions to the SAP standard.
Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
Advantage: In principle, customers can modify anything they want that is found in the include (tables, structures, and so forth).
Disadvantage: SAP cannot check the individual enhancements themselves which often leads to errors in the enhancement process.
Thanks and Regards,
Bharat Kumar Reddy.V

Similar Messages

Diff between userexit and customer exits

hi friends,
             what is the diff b/w userexit and customer exits.
thanks in Advance.

Hai,
Here is the clear differentiation:
User exit - A user exit is a three character code that instructs the system to access a program during system processing.
SXX: S is for standard exits that are delivered by SAP.   XX represents the 2-digit exit number.
UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number
Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
User Exits : -
1. User exits are routines which SAP allows you to add in additional
customized programs process without affecting the standard SAP programs. SAP
user exits are usually declared as a form routine :-
form userexit_xxxxx
endform.
2. No need to create project in CMOD/SMOD.
3. Won't be automatically transported during version upgrade.
Customer Exits :-
1. Could be either Function Exits or Menu Exits. SAP will provide certain
FMs which will be called during the execution of SAP transactions.
2.Generally require the developer to create a project in CMOD/SMOD.
3. Will be automatically transported during version upgrade.
Types of Exits
There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.
Menu Exits
Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.
SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu items text when activating the item in an add-on project.
Screen Exits
Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screens flow logic.
Function Module Exits
Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.
When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.
Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.
These calls have the following syntax:
CALL CUSTOMER-FUNCTION 001.
Field Exits
Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a companys international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.
The field exit concept lets you create a special function module that contains this logic.
You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.
In 4.6c, you can use "RSMODPRF" program to create field exits.
An example of a user exits :-
MODULE user_exit_0001 INPUT
    CASE okcode.
        WHEN 'BACK OR EXIT'.
            CASE sy-dynnr.
                    WHEN '100'.
                         SET SCREEN 0.
                         LEAVE SCREEN.
                    WHEN '200'.
Note that you can write any code that satisfy your needs.                                                     ****
But in this case, this was wrote as a sample code for reference sake.                                    ****
And you can test it.                                                                                ****
                         SET SCREEN 100.
                         LEAVE SCREEN.
             ENDCASE.
      ENDCASE.
Hope u got the difference now.
Reward points if it helps you.
Regds,
Rama.Pammi

Diff between BADI and USER EXITs

Hi,
What is the difference between the BADI and USER EXITs?
Thanks,
Satish

HI
GOOD
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......
THANKS
MRUTYUN

Difference between USER-EXISTs and Customer-Exits???

Hi,
Can anyone give me the difference between the user-exits and customer-exits?
Please respond at the earliest. Thanks in advance.

Hi,
USER EXITS->
1. Introduction:
User exits (Function module exits) are exits developed by SAP.
The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen by the developer.
You are not writing the code directly in the function module,
but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
CUSTOMER EXITS-> t-code CMOD.
As of Release 4.6A SAP provides a new enhancement technique, the Business Add-Ins.
Among others, this enhancement technique has the advantage of
being based on a multi-level system landscape (SAP, country versions, IS solutions, partner,
customer, and so on)
instead of a two-level landscape (SAP, customer) as with the customer exits.
You can create definitions and implementations of business add-ins at any level of the system landscape.
To unify enhancements of the SAP Standard you can migrate customer exits to business add-ins.
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/content.htm
In order to find out the user exits for any tcode,
1. get the developement class of the tcode from SE93.
2. Now goto transaction SMOD and press F4,
3. give in the Deve class in the dev class and Press ENTER
this will show u the exits for any tcode.
or execute this report
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
Regards,
Lijo Joseph
*Reward if useful.

Difference between Userexits and BADI

Pls give me the Difference between Userexits and BADI.

Hi,
hope this is helpful
Difference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

Differences between BADIS and User-exits

Hi everybody,
I am new to ABAP and wonder what are the differences between BADIS and User-Exits. I read paper but did not find a SAP documentation yet.
Does anybody know where to find a sap document which explains both technologies?
Greetings, AD

Hi,
User-Exit is a specific place in a transaction-process where SAP offers
third parties to include there own business functionality. Actually
User-Exit is the namespace used for Exits programmed by SAP specifically
for SD. For the other modules it's called Customer-Exit.=20
>Business Add-Ins (BADI) =20
The use of object orientated code within SAP has lead to new method of
enhancing standard SAP code called Business Add-Ins or BADI's for short.
Although the implementation concept is based on classes, methods and
inheritance you do not really have to understand this fully to implement
a BADI.
For better understanding visit.
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/779183#
Hope it was useful.
Thansk,
Sandeep.

Diff Between PCC and PC by Order

Dear Team,
Why PCC does not support Actual Cost Method and Why PC by Order does't not support Target Cost Method?
Please give your views and comments.
Best Regards,
Satish

hi
=========================
what is diff between billing and invoice?
From the help for cash order, it says that the invoice will print immediately after order created, the billing will be done seperately by transaction after delivery. Can anyone explain more detail.
=================
based on ur query.. Billing and Invoice are one and the same.. the difference is that in general business terminology Billing means the process of crediting the customer to the certain sum of money either by cash or credit, for the goods or services purchased by him... this process consists of many other documents like credit note, debit note, invoice, etc.
Invoice is the Printed format of the Bill ie, the sum of amount the customer is credited is made available in the printiable format....
dont get confused by the Billing and Invoice words.. in simple way invoice is one of the documents generated during the billing process.. Billing is a process which consists of various different documents which are generated depending on the business requirements...
Reward if USeful
Thanx & regards.
Naren..

Diff between cusztmizing and workbench request

could u please let me know what is diff between workbench and custmizing req ?
Regards

Hello,
customizing req vs workbench request
Check this info.
Workbench Requests
When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
Customizing requests
Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
Hope this resolves your query.
Reward all the helpful answers.
Regards,
Jorge Diogo

Difference Between BADI and User Exits

Hi..
generally BADIs & User Exis are used exensively in SAP SD...
Can anybody throw some light waht is difference between them ...
Kindly please reply......
Regards
Nisha

Hi
ifference Between BADI and User Exits
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects. They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software.
As with customer exits two different views are available:
In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object.
In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available.
In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure.
SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR.
The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example).
All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task.
The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects.
What is difference between badi and user-exists?
What is difference between enhancements and user-exists? and what is the full form of BADI?
I have another doubt in BDC IN BDC WE HAVE MSEGCALL (i did not remember the > correct name) where the error logs are stored, MSEGCALL is a table or structure.
What is the system landscape?
1) Difference between BADI and USER-EXIT.
    i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
       Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
    ii) BADI's are oops based.
2) About 'BDCMSGCOLL' it is a structure. Used for finding error records.
3) Full form of BADI 'Business addins'.
3) System land scape will be depends on your project
    Ex:- 'Development server'>'Quality server'-> 'Production server'......

DIFF BETWEEN ABSOLUTE AND PERCENTAG TOLERANCE LIMITS

Gud morning Gurus
Can anyone tell me what is the exact difference between Absolute & Percentange tolerance limits in invoices that we set in customizing.
it wud be better if any example is given.
Thanks

I WENT THRU THE URL SUGGESTED BY YOU.
BUT I WANT TO KNOW IN WHAT CASES EXACTLY THE SYSTEM CONSIDERS ABSOLUTE AND PERCENTAGE LIMITS.
ACTUALLY I READ A STATEMENT THAT THERE IS A DIFF BETWEEN ABSOLUTE AND PERCENTAGE LIMITS, SO WHAT IS IT?
IN QUANTITY VARIANCES,AMOUNT VALRIANCES ETC.
. Quantity variance: For a purchase order, the open quantity to invoice is a result of the delivered quantity and the quantity already invoiced. There is a quantity variance if the invoice quantity does not match this open quantity. At the absolute upper limit, the quantity variance is evaluated on the basis of the amount in the invoice item. This means that invoice items with a small amount result in a relatively large quantity variance, and that invoice items with a large amount result in a small variance. You can also define percentage limits for the quantity variance check, for which the system does not take account of the purchase order price.
WHAT DOES THE ABOVE STATEMENT EXACTLY MEAN?CAN U EXPLAIN UDAY...
THANKS
Edited by: sapppfresher on Oct 3, 2011 6:56 AM

What is diff b/w user & customer exit

Hi
Good afternoon everybody,
Plz differentiate user exit and customer exit.
What is the way to findout user exits and how to modify it.
Thanks in advance
Venkat

Hi Venkat,
Check the following description
Customer exits: The R/3 enhancement concept allows you to add your own functionality to SAPs standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.
If you want to enhance the functionality of your SAP System, you should take advantage of the exits available in standard R/3 applications. There are two main reasons why you should use exits rather than modifying SAP software yourself. Add-ons attached to exits have the advantage that:
They do not affect standard SAP source code
When you add new functionality to your SAP System using SAPs exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAPs standard software package.
They do not affect software updates
When you add new functionality to your SAP System using SAPs exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects names ensure that they will not be affected by any changes or new additions to the standard software package.
In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System.
User exits: Programs with user exits contain subroutine calls at certain points in their syntax that are identified by the prefix USEREXIT. The actual user exits are located in an include that has been assigned to a module pool. This is where customers can include any changes (enhancements) that they want to make to the system. These includes are always processed during program flow.
I hope this helps.
Regards,
Kinshuk

Difference in the Balance between FS10N and Customer Balances in Local Curr

Hi,
When i am trying to match the Balances between FS10N and Customer Balances in Local Currency for the Period 8, we are getting the difference, The reconcilliaton Account was changed on 30.08.2010.
Please help Us in tracing the differences between FS10N and Customer Balances in Local Currency.
What could be the possible reasons for the differences..
Thanks

Hi Varshani,
Please use the program/report SAPF070 to compare or reconcile your AR with GL balances. You can use SAPF071 to correct any inconsistencies. Provided below documentation for these programs.
SAPF070 - Compare Documents and Account Transaction Figures
Description
This program compares debit and credit transaction figures in customer, vendor, and G/L accounts with the debit and credit totals from documents posted in the corresponding posting period (accounting reconciliation). The sales totals are also compared for customer and vendor accounts. There is no separate comparison for special G/L transactions.
A comparison for G/L accounts can be made in company code currency and in parallel currencies (such as group currency). A comparison for customer and vendor accounts can only be made in company code currency.
After the program has finished, a message is issued to the user that started the program. This message summarizes the results of the reconciliation.
Output
The program compares the totals of an account on a periodic basis. If the debit and credit total differs between account and documents, the account is printed with the debit and credit totals and the difference.
Differences in G/L accounts are shown per transaction currency. The first line shows the amount in local currency, the second line shows the amounts in transaction currency.
If a document which falls within the selection range is posted during the program run, the program is terminated since a reliable result can no longer be delivered.
SAPF071 - Adjust Balances after Comparing Documents/Transaction Figures
Description
If a financial accounting comparative analysis (SAPF190) or a comparison of documents and transaction figures (SAPF070) shows that there are differences between documents and transaction figures, you can use this program to make an adjustment. The documents form the basis for this adjustment. The program adjusts the (redundant) transaction figures, which are only totals of amounts from documents.
Requirements
All of the following listed requirements must be fulfilled:
1. A financial accounting comparative analysis (SAPF190) or a comparison of documents and transaction figures (SAPF070) must be made, and differences must be found between documents and transaction figures.
2. There must not be any inconsistent documents found. These are listed in both SAPF070 and SAPF190 as well as in this program.
3. There cannot be any problems in the other modules. Caution: You have to check this yourself. Financial Accounting may be correct but the other modules may not be, and this will adversely affect the program run.
4. You can only make the adjustment in the ledgers which are compared by program SAPF070. This is ledger 00 or a user-defined ledger for all parallel local currencies except the group currency. (The program displays these ledgers). You have to adjust any additional ledgers as well as average balance ledgers yourself.
5. No documents during the period in which you are adjusting transaction figures can be archived. Caution: You must ensure that these documents are not archived by establishing appropriate organizational rules and procedures.
Only use this program after consulting with SAP or after checking the prerequisites thoroughly.
You should adjust all differences together for a single company code. By setting the program parameters you can limit the adjustment to G/L currency types or to balances in subledgers.
It is advisable to execute a test run first, which will list any differences that are found.
Further notes - Authorizations
Repair program authorization group (F_005)
Company code authorization (F_BKPF_BUK)
Thanks
Venkata Ganesh Perumalla
Edited by: Venkata Ganesh Perumalla on Sep 28, 2010 1:30 PM

Diff between Serialization and Synchronization

Hi I am new to java.
Pl. give me the difference between Serialization and Synchronization.
Thankq
Sridhar

Don't you look at the timestamps of posts? They could
have been typing at the same time.
/KajPlease stop! I'll die laughing. LOL
Re: Diff between Serialization and Synchronization
Author: Annie. Apr 11, 2005 10:30 AM (reply 1 of 4)
Re: Diff between Serialization and Synchronization
Author: glrao Apr 12, 2005 8:31 AM (reply 2 of 4) I really like your sense of humor.
xH4x0r

Types of DTP , Diff between Standard and Error DTP

Hi experts,
What is DTP , are the Types of DTP , Diff between Standard and Error DTP , how it works in BI 7.0.
I will assign points for your valuable answers.

Hello ,
Data transfer process (DTP) to transfer data within BI from one persistent object to another object, in accordance with certain transformations and filters. In this respect, it replaces the data mart interface and the InfoPackage. As of SAP NetWeaver 7.0, the InfoPackage only loads data to the entry layer of BI (PSA).
The data transfer process makes the transfer processes in the data warehousing layer more transparent. Optimized parallel processing improves the performance of the transfer process (the data transfer process determines the processing mode). You can use the data transfer process to separate delta processes for different targets and you can use filter options between the persistent objects on various levels. For example, you can use filters between a DataStore object and an InfoCube.
Data transfer processes are used for standard data transfer, for real-time data acquisition, and for accessing data directly.
1.Benefit: Data Distributionwithin BI Capabilities (from PSA or InfoProviders to InfoProviders)
2.Improved transparency of staging processes across data warehouselayers (PSA, DWH layer, ODS layer, Architected Data Marts)
3.Improved performance and high scalability
4.Separation of delta mechanism for different data targets: delta capability is controlledby the DTP
5.Enhanced filtering in dataflow
6.Repair modus based on temporary buffers (buffers keep complete set of data)
See these docs for more info
[Data Transfer Process |http://help.sap.com/saphelp_nw04s/helpdata/en/42/f98e07cc483255e10000000a1553f7/content.htm]
[Enterprise Data Warehouse (EDW)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/67efb9bb-0601-0010-f7a2-b582e94bcf8a]
[What's New with SAP NetWeaver 2004s - Detailed|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/910aa7a7-0b01-0010-97a5-f28be23697d3]
[SAP NetWeaver 7.0 ETL and EII|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b24053-654e-2a10-4180-b0e7c7b4c9f2]
[How to Create Monitor Entries from a Transformation Routine (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50fda171-e36e-2910-9290-e3dab26c50b5]
FAQ on SAP NetWeaver 2004s
[Modeling the Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7c2a7c65-0901-0010-5e8c-be0ad9c05a31]
[Enterprise Data Warehousing for SAP NetWeaver 2004s FAQ|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c9f5fb91-0c01-0010-67a8-fd35946e9403]
Thanks
Chandran

Differentiate between Items and Customer Items

Differentiate between Items and Customer Items
pls try to give information about this
thanx

Hi Joel,
Funny you mentioned it, because just today I was thinking about that, and I thought that if it will happen, I will rant you on your forum dereliction of duties. So it seems you’re off the hook now :)
Anyway, judging from the last 3.0/3.0.1 versions it seems like you are doing your other duties very well so I really don’t mind you keeping the lead.
Best regards,
Arie.

Diff Between USEREXITS and CUSTOMER EXITS?

Similar Messages

Maybe you are looking for