What is the 'Use of SAP implimentation particularly in SD'?

Hi SAP experts,
I would appriciate if any one can clearify the basic question of 'Use of SAP implimentation particularly in SD. Though it seems a simple question, but contains a very good information.
<REMOVED BY MODERATOR>.
Thanks inadvance
Namrata

Dear Namarta
The Materials Management (MM) module is fully integrated with the other modules of the SAP System. It supports all the phases of materials management: materials planning and control, purchasing, goods receiving, inventory management, and invoice verification.
MM Purchasing component are as follows:
     External procurement of materials and services
     Determination of possible sources of supply
     Monitoring of deliveries from and payments to vendors
Integration:
Controlling (CO): materials intended for direct consumption and for services, since these can be directly assigned to a cost center or a production order.
Financial Accounting (FI): The vendor master record represents the creditor account in financial accounting.
Sales and Distribution (SD):
Within the framework of materials planning and control, a requirement that has arisen in the Sales area can be passed on to Purchasing
Process Flow:
1)Determination of Requirements: Through MRP, purchase requisitions
2)Source Determination: helps you identify potential sources of supply, creating requests for quotation (RFQs
3) Vendor Selection and Comparison of Quotations: The system is capable of simulating pricing scenarios
4) Purchase Order Processing: information from the requisition and the quotation to help you create a purchase order. scheduling agreements and contracts are also supported.
5) Purchase Order Follow-Up: The system checks the reminder periods you have specified. up-to-date status of all purchase requisitions, quotations, and purchase orders.
6) Goods Receiving and Inventory Management: Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number
7) Invoice Verification: The system supports the checking and matching of invoices, and clearing invoices for payment.
This is a overview of SAP MM.If u find useful please reward points,
Vivek Maitra

Similar Messages

What is the use of varients in sap?

what is the use of varients in sap?

hi,
Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific selections. To select a certain set of data, you enter an appropriate range of values.
For further information about selection screens, refer to Selection Screens in the ABAP User's Guide.
If you often run the same program with the same set of selections (for example, to create a monthly statistical report), you can save the values in a selection set called a variant.
You can create any number of variants for any program in which selection screens are defined. Variants are assigned exclusively to the program for which they were created.
You can also use variants to change the appearance of the selection screen by hiding selection criteria. This is particularly useful when you are working with large selection screens on which not all of the fields are relevant.
Reports, module pools, and function groups may have several selection screens. It is therefore possible to create a variant for more than one selection screen.
Variants are an interface between the user and the selection screen. They can be used both in dialog and in background mode, although their uses are slightly different.
Variants in Dialog Mode
In dialog mode, variants make things easier for the user, since they save him or her from continually having to enter identical values. They can also make the selection screen easier to read, because you can use them to hide input fields. Running an executable program with a variant containing an optimal set of values also reduces the capacity for user error. The optimized database selections speed up the runtime of the program.
Variants in Background Mode
Variants are the only method for passing values to a report program in a background job. Therefore, when you run a program in the background, you must use a variant (or SUBMIT... VIA JOB). To avoid you having to create a new variant each time you run the report, ABAP contains a mechanism allowing you to pass variable values to variants. See Variable Values in Variants.
To ensure that an executable program is always started using a variant, you can specify in the program attributes that the program may only be started in this way.
report variants
Definition
Group of selection criteria that has been saved. A report can have several different variants, with each variant retrieving different types of information. For example, a vendor report might have one variant for U.S. vendors and another variant for European vendors.
Use
Instead of entering the same values in the selection criteria input fields each time you execute a report, you can enter the values once and then save the selection criteria as a variant. The next time you execute the report, you only need to enter the variant name, not the selection criteria. If you use variants, the selection criteria screen is already filled with data.
To execute certain reports, you must use a variant. In this case, a system message prompts you to do so. Although you are not always required to use variants or selection criteria, it is a good idea to use them when possible. Your resulting lists will be smaller and take less time for the system to process.
reward points if helpful,
shylaja

What is the use varients in sap?

what is the use varients in sap?

Hi Prashanth, this will clear ur doubt.
You can create any number of selection sets (variants) for a program. The variants are allocated to the program uniquely.
Creating variants makes sense when you frequently start a program with the same selection default values.
You can mark Start with variants in the program attributes. Users (system, services, reporting) can then start the program only with a variant.
If the program uses several selection screens, you can choose to create a variant for all the selection screens or individually for each selection screen.
Naming conventions and transporting variants
"SAP&xxx" are supplied by SAP
"CUS&xxx" are created by customers (in client 000)
Variants that follow these naming conventions are client-independent and will automatically be transported along with the report. If these naming conventions are not followed, an entry for a request (task) must be added to the object list: LIMU VARI .
You have to assign a name and a description to each variant. By default, variants are available for both online and background processing. You can also define a variant exclusively for use with background processing.
You can protect the variant itself and the individual selection criteria and parameters against unauthorized changes. If you select Display only in catalog, this variant will not be displayed in the general value help (F4).
The type of a selection is determined in its declaration: Type s for SELECT-OPTIONS, type p for PARAMETERS. If you select Selections protected, then the field(s) will not be ready for input. You can use the hide attribute to suppress selection criteria and parameters on the screen, if required, resulting in a less cluttered selection screen.
When you use selection variables, there are three basic ways of supplying your selections with values at runtime:
From table TVARV (type T)
Date fields using dynamic date calculation (type D), such as today's date
User-specific variables (type B); Prerequisite: The selection must be declared with the MEMORY ID addition.
kindly reward if found helpful.
cheers,
Hema.

Whats the use of sap queries

whats the use of sap queries

Hi,
http://www.sap-img.com/abap/what-is-sap-queries.htm
http://www.informit.com/articles/article.asp?p=664660&rl=1
def sap query
http://help.sap.com/saphelp_bw21c/helpdata/en/f1/0a5625e09411d2acb90000e829fbfe/content.htm
In HR
You can use SAP Query in HR to report on HR data.
how to create sap query
http://help.sap.com/saphelp_46c/helpdata/EN/d2/cb4145455611d189710000e8322d00/content.htm
for maintain SAP query in HR
http://help.sap.com/saphelp_46c/helpdata/EN/d2/cb42cb455611d189710000e8322d00/content.htm
http://help.sap.com/saphelp_46c/helpdata/EN/d2/cb455f455611d189710000e8322d00/content.htm
If you want to create InfoSets for HR, you can use logical databases PNP, PAP, and PCH . The database you must use to create your InfoSet depends on the component in which the data you want to report on is stored.
Creating InfoSets
The maintenance procedure for HR InfoSets differs from the procedure described so far in this section inasmuch as HR data fields are grouped together in infotypes. To set up an InfoSet for the HR application, proceed as follows:
   1. On the initial screen for maintaining InfoSets, enter a name for the InfoSet and choose Create.
   2. On the next screen, enter a name for the InfoSet and select one of the HR logical databases in accordance with your reporting requirements.
Customer infotypes can be created on all HR logical databases. In each individual case, therefore, you must decide which database to select so that you can report on customer infotypes.
This screen enables you to enter an authorization group. All of the queries that are subsequently created using this InfoSet can only be executed by persons who have this authorization group.
   3. Choose .
This takes you to the Infotype Selection for InfoSet screen. You now have the option of creating field groups and assigning fields as required for non-HR InfoSets. Field groups that correspond to infotypes and already contain fields, however, are always created for HR InfoSets. The field groups are displayed in an overview tree in the top right section of the screen.
The infotypes that you included in the InfoSet are displayed in an overview tree on the left of the screen. The infotype fields that are already included in field groups are displayed in a different color, and the field group ID is displayed.
In the standard system, a field group is created automatically for each infotype that you included in the InfoSet (a field group corresponds to an infotype).
In the standard system, each field group contains the infotype-specific fields. To ensure that working with the InfoSet is as easy as possible, you are advised to restrict your use of fields in each field group to those you really require. This means you should remove fields that are not required.
An infotype's fields must only be assigned to the pertinent field group. Make sure this assignment is correct. If the assignment is incorrect, the InfoSet could be rendered unusable.
When an InfoSet is created, the following fields are transferred automatically to the first field group:
Logical database PNP Personnel number
Logical database PAP Applicant number
Logical database PCH Object ID, plan version, and object type
   6. Determine the fields that must be included in the field groups of your InfoSet. If you require further information, see
      Assigning Fields to a Field Group.
If you want, you can change the default sequence of field groups and fields as required using drag & drop.
   7. To save the InfoSet, choose .
   8. To generate the InfoSet, choose .
      On the Change InfoSet (InfoSet name) screen, you can choose Edit ® Change infotype selection to add more infotypes to the InfoSet, or to remove infotypes from the InfoSet. Remember to regenerate the InfoSet afterwards.
      This screen also enables you to update InfoSets if, for example, the system contains new additional fields for specific key values. To do so, choose InfoSet ® Additional functions ® Update additional HR fields.
   9. Go back to the initial screen for InfoSet maintenance.
10. Choose User group assignment.
11. Select a user group, and save your entry.
Please reward points.

What is the use of variant in the alv report

hello all,
what is the use of variant in the alv report

Hi,
For Variants
follow the link:
http://help.sap.com/search/highlightContent.jsp
Variants allow you to save sets of input values for programs that you often start with the same selections. You can use them for any programs except subroutine pools (type S).
Contents
Variants: Overview
Initial Screen
Displaying a Variant Overview
Creating and Maintaining Variants
Creating Variants
Attributes of Variants
Changing Variants
Deleting Variants
Printing Variants
Variable Values in Variants
Creating Variables for Date Calculations
User-specific Selection Variables
Creating User-specific Variables
Changing Values Interactively
Changing Values from the Program
Fixed Values from Table TVARV
Creating Table Variables from TVARV
Changing TVARV entries
Running a Program with a Variant
Variants: Overview
Use
Whenever you start a program in which selection screens are defined, the system displays a set of input fields for database-specific and program-specific selections. To select a certain set of data, you enter an appropriate range of values.
For further information about selection screens, see Working with selection screens in the ABAP User's Guide.
If you often run the same program with the same set of selections (for example, to create a monthly statistical report), you can save the values in a selection set called a variant.
You can create any number of variants for any program in which selection screens are defined. Variants are assigned exclusively to the program for which they were created.
You can also use variants to change the appearance of the selection screen by hiding selection criteria. This is particularly useful when you are working with large selection screens on which not all of the fields are relevant.
Reports, module pools, and function groups may have several selection screens. It is therefore possible to create a variant for more than one selection screen.
Variants are an interface between the user and the selection screen. They can be used both in dialog and in background mode, although their uses are slightly different.
Variants in Dialog Mode
In dialog mode, variants make things easier for the user, since they save him or her from continually having to enter identical values. They can also make the selection screen easier to read, because you can use them to hide input fields. Running an executable program with a variant containing an optimal set of values also reduces the capacity for user error. The optimized database selections speed up the runtime of the program.
Variants in Background Mode
Variants are the only method for passing values to a report program in a background job. Therefore, when you run a program in the background, you must use a variant (or SUBMIT... VIA JOB). To avoid you having to create a new variant each time you run the report, ABAP contains a mechanism allowing you to pass variable values to variants. See variable values in variants.
To ensure that an executable program is always started using a variant, you can specify in the program attributes that the program may only be started in this way.
Features
Creation of variants
Display, change, copy, print, and delete variants
Use and definition of variables in variants
Variable date calculation
User-specific fixed values
Fixed values in table TVARV
You access the variant maintenance tool from the initial screen of the ABAP Editor. Enter the name of the program, select Variants in the Sub-objects group box, and then choose Display or Change.
Functions
The above screen allows you to:
Create variants
Display the variant directory
Display and change values and attributes
Copy, delete, and rename variants
Before creating a new variant for a program, you should check whether you can use or adapt an existing variant instead.
There are two ways to display variants:
Position the cursor on the Variant field on the initial screen and press F4. The following dialog box lists all of the available variants:
Choose Variants ® Directory on the initial screen:
Creating Variants
Prerequisites
You must have defined one or more selection screens for the relevant program. The program may have any type except type S.
Procedure
On the initial screen of the ABAP Editor, enter the name of the program for which you want to create a variant, select Variants in the Sub-objects group box, and choose Change.
On the variant maintenance initial screen, enter the name of the variant you want to create.
Note the naming convention for variants (see below).
Choose Create.
If the program has more than one selection screen, a dialog box appears in which you can assign the variant to one or more screens. The dialog box does not appear if the program only has one selection screen. In this case, the selection screen of the program appears straight away.
If there is more than one selection screen, select the screens for which you want to create the variant.
Example:
If you choose Variant for all selection screens, the variant also applies to any selection screens that you create after creating the variant.
Otherwise, the variant only supplies values to the selection screens that you select in the list.
Choose Continue.
The (first) selection screen of the program appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them. If you keep scrolling forwards, the Continue button appears on the last selection screen.
Enter the required selections, including multiple and dynamic selections.
Choose Continue.
Result
When you have finished, an overview screen appears (ABAP: Save Attributes of Variant), on which you can enter the attributes of your variant and save it.
Note that when you create a new variant, you must enter both values and attributes.
Names of variants: Names can consist of up to 14 alphanumeric characters. The "% " character is not allowed. If you want the variant to be transported automatically with its program, you must create a system variant. The name of a system variant starts "CUS&" for customers, and "SAP&" for SAP system variants. You can only use the "&" character within this prefix in the name of a system variant. It may not occur in any other context. System variants are administered by the Workbench Organizer. Although you can create and access variants from any client, they are always stored in client "000".
Creating Variants
Prerequisites
You must have defined one or more selection screens for the relevant program. The program may have any type except type S.
Procedure
On the initial screen of the ABAP Editor, enter the name of the program for which you want to create a variant, select Variants in the Sub-objects group box, and choose Change.
On the variant maintenance initial screen, enter the name of the variant you want to create.
Note the naming convention for variants (see below).
Choose Create.
If the program has more than one selection screen, a dialog box appears in which you can assign the variant to one or more screens. The dialog box does not appear if the program only has one selection screen. In this case, the selection screen of the program appears straight away.
If there is more than one selection screen, select the screens for which you want to create the variant.
Example:
If you choose Variant for all selection screens, the variant also applies to any selection screens that you create after creating the variant.
Otherwise, the variant only supplies values to the selection screens that you select in the list.
Choose Continue.
The (first) selection screen of the program appears.
If your program has more than one selection screen, use the scroll buttons in the left-hand corner of the application toolbar to navigate between them. If you keep scrolling forwards, the Continue button appears on the last selection screen.
Enter the required selections, including multiple and dynamic selections.
Choose Continue.
Result
When you have finished, an overview screen appears (ABAP: Save Attributes of Variant), on which you can enter the attributes of your variant and save it.
Note that when you create a new variant, you must enter both values and attributes.
Names of variants: Names can consist of up to 14 alphanumeric characters. The "% " character is not allowed. If you want the variant to be transported automatically with its program, you must create a system variant. The name of a system variant starts "CUS&" for customers, and "SAP&" for SAP system variants. You can only use the "&" character within this prefix in the name of a system variant. It may not occur in any other context. System variants are administered by the Workbench Organizer. Although you can create and access variants from any client, they are always stored in client "000".
reward all help full answers

What is the use implemention of work flow

Hi guis,
can u plz tell me what is the uses, u implement a workflow, and also please give the one scenrio on purchase order or invoice or anything, one scenrio explain me.

Workflow is a tool for automating the business process so that the process itself flows smoothly, without bottlenecks and without dead ends. Critical parts of the process can be streamlined with deadline monitoring and contingency options. Participants are informed of milestones in the process. The process definition itself is powerful enough to allow business re-engineering with re-training and to eliminate the impact of workforce changes on the basic business process.
SAP Business Workflow is the R/3 tool for handling the process automation within R/3 or between R/3 systems and other systems involved in the business process. It is flexible enough to handle ad hoc processes such as the circulation of an electronic document. It is robust enough to handle mission critical process in the production system such as the creation of a material master.
The different R/3 applications supply standard workflows for the commonly occurring processes. Once these workflow templates are activated, they are ready for immediate use. A complete set of workflow tools, including the workflow editor and workflow generation wizard, are provided to enhance these standard workflows or create new workflows. These tools are complemented with transactions for monitoring, tracking and the statistical analysis of the processes.
Because the business process often does not step at the R/3 boundary, various interfaces and third party tools are available for extending the process across systems.
Workflow is the technique for automating business processes. It is particularly beneficial
u2022 when different people are involved in different parts of the process
u2022 when a process only occurs sporadically and the users need to be reminded of what they need to do
u2022 when the duration of the process is critical and deadlines have to be met
u2022 when the process definition is likely to change on the fly and retraining users is not possible.
By automating the process, you free the users from having to know what to do when. Work items are sent to the participants notifying them of what they have to do, and a single click on the notification calls the correct transaction and navigates to the relevant screen.
When the workflow runs it creates work items which are like e-mails, but
u2022 they have the advantage that they contain the intelligence needed to execute the relevant task with the correct data when the operational user executes them,
u2022 they provide their own functionality so that the operational user has access to everything that is useful to improve the flow of the process,
u2022 they disappear on their own when they have been executed by someone else or made obsolete.
These work items can be received in the R/3 business workplace, MS Outlook (or any other MAPI compatible client), Lotus Notes, or work item notifications can be distributed by e-mail.
SAP Business Workflow:
u2022 accelerates the workflow across applications, functional areas, organizational units, and time periods,
u2022 supplements the integrated management of processes in the SAP System with individually tailored options for automating and actively controlling business and communication processes,
u2022 combines integrated organizational management with flexible assignment of tasks and responsibilities to locations, positions, jobs, groups, or individuals,
u2022 actively supports a quick implementation of workflow technologies through predefined workflow templates, Workflow Wizards and flexible adjustment options,
u2022 integrates every employee in the value chain by providing a versatile integrated inbox ("universal inbox") at their work centers that can be configured individually,
u2022 provides a Workflow Information System that is the foundation for process change management and continuous business engineering,
u2022 was designed to be a change-management tool,
u2022 simplifies continuous business engineering and process change management with user-friendly tools for defining and dynamically changing workflow tasks
u2022 conforms to the workflow standards of the Workflow Management Coalition (WfMC)
u2022 interfaces to other mail clients such as Lotus Notes and MS Outlook
Check these links.
http://www.sapgenie.com/workflow/index.htm
Link workflow business objects to your collaboration tasks!!
http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm
http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm
http://www.sap-press.com/product.cfm?account=&product=H950
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
Hope this resolves your query.
raj

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT

WHAT IS THE USE OF COPY/MATCH OPTION IN BUISNESS CONTENT GIVE DETAILS

Hi,
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.
With the most important object types, the active version and the SAP delivery version can be matched.
From a technical point of view, the SAP delivery version (D version) is matched with the M version. As in most cases the M version is identical to the active version (A version) in a customer system, this is referred to as a match between the D and A versions for reasons of simplification.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually. A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content. When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
Example of an automatic match
Additional customer-specific attributes have been added to an InfoObject in the A version. In the D version, two additional attributes have been delivered by SAP that do not contain the customer-specific attributes. In order to be able to use the additional attributes, the delivery version has to be installed from Business Content again. At the same time, the customer-specific attributes are to be retained. In this case, you have to set the indicator (X) in the checkbox. After installing the Business Content, the additional attributes are available and the customer-specific enhancements have been retained automatically. However, if you have not checked the match field, the customer-specific enhancements in the A version are lost.
Example of a manual match
An InfoObject has a different text in the A version than in the D version. In this case the two versions have to be matched manually. When Business Content is installed, a details screen appears which asks you to specify whether the text should be transferred from the active version or from the D version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Install indicator separately.
The active version is overwritten with the delivery version if
¡        the match indicator is not set and
¡        the install indicator is set.
In other words, the delivery version is copied to the active version.
If the Install indicator is not set, the object is not copied or matched. In this case, the Match indicator has no effect.
In the context menu, two options are available:
                            a.      Merge All Below
The object in the selected hierarchy level and all objects in the lower levels of the hierarchy are selected as to Match.
                            b.      Copy All Below
The Match indicators are removed for the object in the selected hierarchy level and all objects in the lower levels of the hierarchy. If the Install indicator is also set, these objects are copied from the delivery version to the active version.
The most important properties which are taken into account when versions are matched are now listed.
When referring to InfoObjects it is important to differentiate between:
§         Characteristics
§         Time characteristics
§         Key figures and
§         Units
Valid for All InfoObjects Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        Texts
·        Description
If texts/descriptions in the delivery version do not yet exist in the active version, they are transferred.
·        Attribute only (flag)
·        Short and long text (description)
·        Time dependency of attributes
·        Transfer routine
Valid for Characteristics
Properties Matched Automatically:
Properties Matched Manually:
·        Compounding
New InfoObjects are included in compounding
·        Referenced characteristic
Reference characteristics are transferred automatically. A warning is issued.
·        Attributes / navigation attributes
New attributes are included.
If an attribute is added by the customer, the settings for this attribute are transferred (for example, F4 sequence).
·        Application components
If the entry for the active version is initial, the delivery version is used.
·        BEx display
·        Characteristic constants
·        Default member
·        Authorizations (flag and field)
·        Selection (CHASEL)
·        InfoObject is document attribute
·        Data type
·        Length
·        Output length
·        Conversion routines
·        Lower case allowed (flag)
·        Contains master data (flag)
·        Master data is authorization relevant (flag)
·        Export DataSource (Flag)
·        F4 query design
·        F4 query runtime
·        Check ODS object
·        Contains text tables (flag)
·        Texts are language-dependent (flag)
·        Short, medium and long texts exist (each with flag)
·        Default currency
·        GIS attribute
·        Hierarchies exist (flag)
Valid for Key Figures
Properties Matched Automatically:
Properties Matched Manually:
·        Type of key figure
·        Fixed unit
·        Fixed currency
·        Aggregation
·        Exception aggregation
Valid for Units
Properties Matched Automatically:
Properties Matched Manually:
·        See the table above (Valid for Characteristics), if these properties are also relevant for the units.
When referring to InfoProviders it is important to differentiate between:
¡        MultiProviders
¡        InfoCubes
¡        ODS Objects and
¡        InfoObjects
InfoObjects are discussed above (see the first table Valid for All Objects Named Above).
Valid for All InfoProviders Named Above:
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoObjects
If InfoObjects in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for MultiProviders
Properties Matched Automatically:
Properties Matched Manually:
·        New InfoProviders
If InfoProviders in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
Valid for InfoCubes
Properties Matched Automatically:
Properties Matched Manually:
·        New dimensions
If dimensions in the delivery version do not yet exist in the active version, they are transferred.
·        Manual matching is not necessary.
With the InfoObject catalog object type, InfoObjects that are assigned to a catalog in the delivery version are transferred to the active version automatically. Manual matching is not necessary.
With the transfer rule object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional attributes) are added automatically when the match is performed. Manual matching is not necessary.
With the process chain object type, those objects that exist in the delivery version but are not yet contained in the active version (for example, additional objects in the process chain) are added automatically when the match is performed. Manual matching is not necessary.
·        Active Version Available
In this column, the following display options are available:
¡        : The object is available in an active version. You decide whether you want to retain this version or reinstall the latest version of the object.
¡        Date symbol: The object is already available in an active version. However, the active version belongs to an older Content release. SAP recommends that you install the latest version.
¡        Gray symbol: An activated version of the object is available in the system. However, the object status is inactive. If an object version is activated, this indicates that all metadata for the object can be created successfully. The inactive object status indicates that the processed object is inconsistent and cannot currently be used for processing data. Transfer the object again from the SAP delivery version (D version). If this is not enough to change the object status from inactive to active the object has to be postprocessed. You find notes on postprocessing in the activation log.
Postprocessing: An inactive object status may also occur for an InfoObject if changes are made to the structure at field level. Postprocessing the object involves converting the relevant tables in accordance with the activation log.
¡        No indicator: The object is not available in an active version.
7. Make Settings in the Selection List and Install.
Make the required settings in the Install selection list:
Installation Type
Installation Type
Information
Simulate installation
The system runs a test to see whether any errors are likely to occur during the installation. However, not all errors that may occur can be identified during simulation: Some error messages can only be generated when a real A version (and not just a simulation) is available in the system. You should, therefore, only use the simulation function as a rough guide to help you identify and remove basic errors.
Install
The selected objects are installed immediately.
Install in background
The selected objects are installed in the background.
Install and transport
The selected objects are installed immediately and then written to a transport request.
SAP recommends you use the Install in background option because installing a large number of objects can take a long time. Modifying objects that are already active can take an especially long time to complete. Make sure that when you install objects in the background that the versions are not matched. It is always the delivery versions that are installed. These are not matched with any available customer versions.
Refer
Business Content (Versions)
http://help.sap.com/saphelp_nw04/helpdata/en/c1/ea683cc5e8ca68e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a66d5e07211d2acb80000e829fbfe/frameset.htm
Thanks,
JituK

What is the use of ST05 ? and how to use " ST05 "

can anybody tell me what is the use of " ST05 "
and how can we handle it.

SQL Trace
SQL trace(ST05) provides the developer with the ability to analyse database select statements. Simply execute ST05
to turn on SQL trace, then execute the statement/program you want to analyse. Now turn off SQL trace using ST05
and click on list trace to view the details.
You can also perform traces on other items such as authorisation objects.
Authorisation trace analysis 1. Open two sessions
2. Execute transaction ST01 in one of the sessions
3. Select the authorisation checkbox, note the other traces
you can perform (SQL, RFC, Table Buffer etc)
4. Click the 'Trace On' button
5. Within your other session execte the transaction/report
you want to trace or get the user in question to do it
6. Return to the session where you turned the trace on and
click on 'Trace Off' otherwise it will continue to record
all athorisation checks
7. Click on the 'Analysis' button
8. Enter appropriate data into selection screen such as
Username, type of trace records (i.e. Authorization check)
9. Click on the Execute button.
10. Report displaying trace results will now be displayed
http://www.sapdevelopment.co.uk/perform/perform_sqltrace.htm
Some useful transaction related to this are ..
ST01 SAP system trace
ST02 Buffer statistics.
ST03 Workload analysis.
ST04 Database performance analysis.
ST05 SQL trace .
ST06 Operating system monitor ...
From the recorded SQL trace you can deduce:
· Which SQL statements your application carries out
· Which values the system uses for specific database accesses and changes
· How the system translates ABAP OPEN SQL commands (such as
SELECT) into standard SQL commands
· Where your application positions COMMIT statements
· Where your application makes repeated database accesses
· What database accesses or changes occur in the update section of your
application
Look at the below links, you will get the idea
http://help.sap.com/saphelp_erp2005/helpdata/en/d1/801f89454211d189710000e8322d00/content.htm
http://www.sapbrain.com/TOOLS/SQLTRACE/SQL_TRACE.html
Check the following links:
http://www.sapbrainsonline.com/TOOLS/RUNTIMEanalysis/SAP_runtime_analysis.html
http://www.sapbrainsonline.com/TOOLS/SQLTRACE/SQL_TRACE.html
Use
The Performance Trace allows you to record database access, locking activities, and remote calls of reports and transactions in a trace file and to display the performance log as a list. It also provides extensive support for analyzing individual trace records.
SQL Trace: This allows you to monitor the database access of reports and transactions.
Enqueue Trace: This allows you to monitor the locking system.
RFC Trace: This provides information about Remote Function Calls between instances.
While the trace is switched on, the SQL Trace function records all database activity by a particular user or group of users. The R/3 System takes OPEN SQL statements and converts them in to embedded SQL statements that it passes to the database. It is the embedded SQL statements, their parameters, return codes, and the number of entries retrieved, inserted, or deleted that are recorded in the SQL Trace file. The log file also contains the runtime of the statement and the place in the application program from which it was called.
The SQL trace tells you:
The SQL statements executed by your program.
The values that the system uses for particular database access and changes.
How the system converts ABAP Open SQL statements (such as SELECT) into Standard SQL statements.
Where your application executes COMMITs.
Where your application repeats the same database access.
The database accesses and changes that occur in the update part of your application.
Refer
http://help.sap.com/saphelp_erp2005vp/helpdata/en/43/cb632772cd0cd4e10000000a1553f7/frameset.htm
Regards
Vasu

What is t-code SM66? what is the use of it?

hi all,
what is t-code SM66? what is the use of it? plz tell me with an example and steps
thanks,
jack

Hi Jack,
The T-CODE SM66 is Global servers work area. That means it is having all the servers running with in an organization/company etc. When you again double click on any one of the server at that time it shows SM50 of that particular server. SM50 is local server work area and SM66 is global work area.
Check this link
http://help.sap.com/saphelp_nw70/helpdata/EN/ed/a9bb3f8e236d3fe10000000a114084/frameset.htm
Award points if helpfull
Thanks,
Sujeet

What is the diffrence between sap events and application events

Hi all,
what is the diffrence between sap events and application events.Can any one tell me with examples.
regards,

Hi,
Look at this,
System Events (Default)
The event is passed to the application server, but does not trigger the PAI. If you have registered an event handler method in your ABAP program for the event (using the SET HANDLER statement), this method is executed on the application server.
Within the event handler method, you can use the static method SET_NEW_OK_CODE of the global class CL_GUI_CFW to set a function code and trigger the PAI event yourself. After the PAI has been processed, the PBO event of the next screen is triggered.
The advantage of using this technique is that the event handler method is executed automatically and there are no conflicts with the automatic input checks associated with the screen. The disadvantage is that the contents of the screen fields are not transported to the program, which means that obsolete values could appear on the next screen. You can work around this by using the SET_NEW_OK_CODE method to trigger field transport and the PAI event after the event handler has finished.
Application Events
The event is passed to the application server, and triggers the PAI. The function code that you pass contains an internal identifier. You do not have to evaluate this in your ABAP program. Instead, if you want to handle the event, you must include a method call in a PAI dialog module for the static method DISPATCH of the global class CL_GUI_CFW. If you have defined an event handler method in your ABAP program for the event (using the SET HANDLER statement), the DISPATCH method calls it. After the event handler has been processed, control returns to the PAI event after the DISPATCH statement and PAI processing continues.
The advantage of this is that you can specify yourself the point at which the event is handled, and the contents of the screen fields are transported to the application server beforehand. The disadvantage is that this kind of event handling can lead to conflicts with the automatic input checks on the screen, causing events to be lost.
Hope u understood.
Thanks&Regards,
Ruthra.R

What is the diffrence between SAP View and CAD View ?

What is the diffrence between SAP View and CAD View ?
What is the main purpose of SAP View
and
What is the main purpose of CAD View
On SAP help i found
SAP View is used for :The SAP view displays the SAP structure (document-based structure) for the active CAD object, or another document info record (header document), with a single-level or multilevel document structure in a tree structure. You can variably configure the fields using the layout editor.
CAD View is used for :The CAD view displays the document-based structure of the currently active CAD object, such as the structure of an assembly. The CAD system determines the complete (multilevel) structure and copies it either completely or in stages to the SAP system, in accordance with the default explosion level.
BUT I did not understand it well
Can someone explain this with an example
THanks
Raj

Hello Raj,
SAP View can be further described as the view that is based on what is existing already in the SAP system. This view is generally used by SAP purchasing, MM people etc
CAD view is nothing but the replication of the model tree view in the SAP system. This is used by the design engineer and this view replicates only the parts that are actively displayed on the CAD tool window.
hope this helps. Let me know if you have further questions else please close the message.
regards
N K

What is the use of Alternative Calculation Type =2 and 4

Dear Friends
In pricing procedure in gross value, Net value for Item and Net value has Alternative calucation type is 2.
What is the use of it?
Without using it these value line are also fetching net value then what is the work of it. Please give me detail information with its effects in pricing condition tab page in sales document.
Thanking You
Arun

Arun biswal,
Correct Biswal. We have at varoius stages within Pricing procedure the "net value" which is calculated. Not only the alternative calculation type "2" is used if you notice carefully they are stored as subtotals at various levels.
For Ex Gross Value --> Subtotal =1 --> Calc type = 2
similarly for Net value for Item --> Subtotal =2 --> Calc type = 2
Net value 2 --> Subtotal =3 --> Calc type = 2
See, these are used to calculate the net value at various levels in pricing. The calculation Type has got a set of routines that will facilitate us in pricing. SAP has provided certain clauclated formulas or routines to facilitate us during calculation within pricing . Here the "2" is used for calculation without tax and store it as subtotal and display it or use it for further calculations.
We can use this "netvalue" amount for further calculations. It is used for clarity purpose when you issue a statement to customer. (like Confirmation order) at various levels like discount amt involved, Freight involved, Rebate amount invloved.....
Even without this Calc type or using sub total u can proceed....
Finally we have TOTAL --> Subtotal =A --> Calc type = 4
In the above line we have Calc type as 4, which means when you use TAX this calc type is used .
Routines are used to facilitate your process....
Regards
Sathya

What is the difference between SAP NW PI7.1 and PI7.1 EHP1

We have a customer using SAP PI7.1 EHP1. The application to be deployed
isdeveloped on SAP Netweaver PI 7.1 SP06.
We need to know if application developed and transported from PI7.1 is
compatible with EHP1?
Below are the Components used by the application .
1) SSL communication using SOAP adapter
2) Java mapping , Graphical mapping , XSLT mapping
3) Customised EJB modules
4) Adapter framework
5) ALE layer for IDoc communication from ERP to PI
6) RFC lookups to PI system and ERP system.
Questions
1)Will PI EHP1 be able to communicate with PI7.1 using SOAP adapter ?
2) What is the difference between SAP NW PI7.1 and PI7.1 EHP1 ?
Regards,
Sneha

Hi,
EHP Pi7.1 new
IPv6 Support in SAP Systems (new)
Async/Sync and Sync/Async Bridge in the JMS Adapter (New)
High Availability (New) Locate the document in its SAP Library structure
Use
A new concept is available for setting up a high availability environment for SAP NetWeaver Process Integration (PI). To do this, you need SAP Web Dispatcher for load balancing, and you must reconfigure your HTTP, RFC, and RMI connections so that they can be used for load balancing. You must also make various configuration steps in other components of your PI environment.
[Level 4: Document: XML to Text Conversion Module (New)] XML to Text Conversion Module (New)
Message Packaging (New)
Monitoring Milestones (New) Locate the document in its SAP Library structure
Use
You can use the new scenario variant Monitoring Milestones of the Business Process Management scenario to define a monitoring process that can monitor events from different applications. A monitoring process can subscribe to events from SAP or non-SAP systems.
check given Link
http://help.sap.com/saphelp_nwpi711/helpdata/en/61/8c3842bb58f83ae10000000a1550b0/frameset.htm
Regards,
Amit

What is the use of Withholding tax identification number field?

Hello SAP Experts,
I posted this question earlier but had to close because of no replies from anybody. Posting it again to see if I am lucky to get some answer this time.
Can someone tell what is the use of field Withholding Tax Identification Number? Does it help with the reporting? Where does it get populated on the report if given at vendor or master record or within the withholding tax customization for company code? What is the difference between creating it in the customization for withholding tax information for company code and vendor/customer master record?
As per SAP: Withholding tax identification number
This is a number issued by the tax authorities per withholding tax type.
This number must be specified in Customizing either:
(a) As part of the withholding tax information defined for the company code, or
(b) As part of the withholding tax information defined in the customer or vendor master record.

Hi Pete,
The only thing that I could check is the content used in US:
See content of this field for US:
LFA1-STCD1 Social security number
LFA1-STCD2 Employer identification number
LFBW-WT_WTSTCD Withholding tax identification number for WT Type
In order to populate it, please kindly check the following:
The reason why you cannot fill in the field WT_WTSTCD in transaction
Fk02 however you can do it in XK02 (Change vendor centrally) can be due
to wrong customizing of the field status group.
Kindly check the following:
SPRO->
Finantial accounting -> Accounts receivable and accounts payable ->
Define screen layout per activity (vendors) -> Change Vendor(Accounting)
Company code data -> W/holding tax data, w/h tax 2 ->
FIELD Withholding tax code,w/h tax 2 will be probably just available to
display. Please, change it to optional entry.
I hope I could be of assistance.
Kind Regards,
Fernando Evangelista

What is the use of end routine in bi 7.0

hi friends,
what is the use of end routine in bi 7.0. what scenerio we use end routine.
Thanking u
suneel.

hi Suneel,
check
http://help.sap.com/saphelp_nw70/helpdata/en/e3/732c42be6fde2ce10000000a1550b0/frameset.htm
End Routine
An end routine is a routine with a table in the target structure format as input and output parameters. You can use an end routine to postprocess data after transformation on a package-by-package basis. For example, you can delete records that are not to be updated, or perform data checks.
If the target of the transformation is a DataStore object, key figures are updated by default with the aggregation behavior Overwrite (MOVE). You have to use a dummy rule to override this.
hope this helps.

What is the 'Use of SAP implimentation particularly in SD'?

Similar Messages

Maybe you are looking for