What is the uses of a Transport order ?

Hi,
Can any one tell what is the the link between Transport Order, client field ( MANDT ) and Systems (Dev, Integration and production) ?
In other words, How can I create an object in Deveopment System and send it to Intergration System?
Thnaks
Edited by: moutaa noureddine on Jun 21, 2008 4:24 PM

HI,
Looks like you are very new to SAP world.
For eg: the landscape in company could be:
                       Dev. System                                                         QA system             Production
Client no.             050 { gold client for config chagnes}                       100                        100
                           051 { Sand box for config changes }
                           052 { Dev. client }
                           053 { Testting client }
Client 050 in dev. system is for the configuration changes and used by functional analyst.
051 is the functional analyst's sand box for playing around
052 is the developer's client for making all the changes to the customer namespace {Z and Y} objects
053 is the testing client for developer and funtional client
You can make change only in client 052 and not in any other client.
Only in development you will have multiple clients. In all the other QA & Prodn system there is only one client maintained. You cannot make changes in QA unless you are provided with any developer key access. { Generally no one is given devlopment rights in QA, unless it is an emergency fix before prodn.migration }
The path of the migration will be from Dev.052 -> (all clients in Dev. system (if dependent) )
                                                                  -> QA system
Then after all the successful testing of the object in QA it is migrated to production.
Does this help.
Regards,
SUbramanian

Similar Messages

What is the use of confirmation tab in Purchase order ?

what is the use of confirmation tab in Purchase order?

Hello Balaji
In Purchasing, the term Confirmation is an umbrella term for various kinds of information provided by a vendor to a customer with regard to ordered goods.
Possible types of confirmation include the following:
Order acknowledgments
Loading or transport confirmations
Shipping notifications. (Note that shipping notifications may also be referred to by a number of other names, including "advice (note)", "advice of dispatch", "ship notice", and "advance(d) shipping notice" ("ASN").)
A further form of confirmation frequently used in Purchasing is the Inbound Delivery, which is created on the basis of an incoming shipping notification. The shipping notification represents a vendors confirmation to a purchasing organization of a delivery date for a certain quantity of ordered materials (or the date of performance of ordered services).
You can enter incoming vendor confirmations manually. Alternatively, you can receive them via EDI and have them processed automatically.
When working with vendor confirmations, you have the following options:
You can enter the order acknowledgment number if you simply wish to provide a basis for monitoring the receipt or non-receipt of acknowledgments.
You should enter the confirmed quantities and delivery dates if you wish to provide more detailed information in support of the purchasing, inventory management, and materials planning/control functions within your enterprise.
Regards

What is the use of production order without material?

Hi gurus,
can anyone plz tell what is the use of production order without material?
n steps involve to perform this task?

Dear amnpp,
It's widely used for capturing the rework activities(components and activity cost),both for final rework and inprocess rework
activities.
Check these links,
Rework order manually (not Trigger)
rework order
Rework Order Steps
Re: Coustomization order type for Rework
Regards
Mangalraj.S

What is the BADI while SAVING purchase order using me22n?

what is the BADI while SAVING purchase order using me22n?
while i will save purchase order through me22n, badi should be fire what is badi for that?
regards,
dushyant.

Dushyant,
Hopefully you know how to implement the BADI ME_PROCESS_PO_CUST now.
The following are the codes that you can put in the method "Post".
DATA: LW_HEADER        TYPE MEPOHEADER,
        LW_POSTED_HEADER TYPE MEPOHEADER,
        LW_VALID         TYPE MMPUR_BOOL,
        ITAB_ITEM        TYPE PURCHASE_ORDER_ITEMS,
        LW_ITEM          TYPE MEPOITEM,
        ITEM_INTERFACE   TYPE PURCHASE_ORDER_ITEM,
        ITAB_ACCT        TYPE PURCHASE_ORDER_ACCOUNTINGS,
        ACCT_INTERFACE   TYPE PURCHASE_ORDER_ACCOUNTING,
        LW_ACCT          TYPE MEPOACCOUNTING,
        LW_POSTED_ACCT   TYPE MEPOACCOUNTING,
        W_ACCT_CHANGED TYPE C,
        W_GRANT_AMT      TYPE EKPO-NETWR,
        W_FINANCE_AMT    TYPE EKPO-NETWR,
        W_FLAG           TYPE C.
Check if PO header data is valid
CLEAR LW_VALID.
CALL METHOD IM_HEADER->IS_VALID
    RECEIVING
      RE_VALID = LW_VALID.
CHECK LW_VALID = 'X'.
PO header data is valid
Get the newly updated PO header data
CLEAR LW_HEADER.
CALL METHOD IM_HEADER->GET_DATA
    RECEIVING
      RE_DATA = LW_HEADER.
Get the posted PO header data
CLEAR LW_POSTED_HEADER.
CALL METHOD IM_HEADER->GET_PERSISTENT_DATA
    IMPORTING
      EX_DATA = LW_POSTED_HEADER
    EXCEPTIONS
      NO_DATA = 1.
IF SY-SUBRC <> 0.
    CLEAR LW_POSTED_HEADER.
ENDIF.
Get PO line items
REFRESH ITAB_ITEM.
CALL METHOD IM_HEADER->GET_ITEMS
    RECEIVING
      RE_ITEMS = ITAB_ITEM.
LOOP AT ITAB_ITEM INTO ITEM_INTERFACE.
Check if PO line item is valid
    CLEAR LW_VALID.
    CALL METHOD ITEM_INTERFACE-ITEM->IS_VALID
      RECEIVING
        RE_VALID = LW_VALID.
    IF LW_VALID <> 'X'.
This PO line item is not valid
      CLEAR W_ACCT_CHANGED.
      EXIT.
    ENDIF.
    CLEAR LW_ITEM.
    CALL METHOD ITEM_INTERFACE-ITEM->GET_DATA
      RECEIVING
        RE_DATA = LW_ITEM.
Get the account interface
    REFRESH ITAB_ACCT.
    CALL METHOD ITEM_INTERFACE-ITEM->GET_ACCOUNTINGS
      RECEIVING
        RE_ACCOUNTINGS = ITAB_ACCT.
    LOOP AT ITAB_ACCT INTO ACCT_INTERFACE.
      CLEAR LW_ACCT.
Get the newly updated PO item data
      CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_DATA
        RECEIVING
          RE_DATA = LW_ACCT.
      CLEAR LW_POSTED_ACCT.
Get the posted PO item data
      CALL METHOD ACCT_INTERFACE-ACCOUNTING->GET_PERSISTENT_DATA
        IMPORTING
          EX_DATA = LW_POSTED_ACCT
        EXCEPTIONS
          NO_DATA = 1.
      IF SY-SUBRC > 0.
        CLEAR LW_POSTED_ACCT.
      ENDIF.
      IF LW_ACCT-LOEKZ <> LW_POSTED_ACCT-LOEKZ OR
         LW_ACCT-KOSTL <> LW_POSTED_ACCT-KOSTL OR
         LW_ACCT-PRCTR <> LW_POSTED_ACCT-PRCTR OR
         LW_ACCT-PS_PSP_PNR <> LW_POSTED_ACCT-PS_PSP_PNR.
Account assignment was changed
We will force this PO to go through workflow
        W_ACCT_CHANGED = 'Y'.
      ENDIF.
    ENDLOOP.
ENDLOOP.

What is the use of transporting BEx query to production from development ?

Hi !
if create a query by copying an existing query and make some modification in production and sent it to client..and client is happy as it satisfies all his requirement .
Then what is the use of creating Bex query in development and transport it in quality and then to production if we can create directly in production ?

Hi,
There is something called as SOX compliance..and three system landscape.
First of all you are not suppose to make changes to standard qeuries.
You can give it to the client a new copied query wirth required changes and it is very much accepted as well but how will it be tracked for future support.
Suppose there is a change in the underlying cube...this will affect all the queries and the new copied query which no one knows about will be affected too.How will you test it if its workinf fine with the new flow.
If you want to do the testing in production as well.... then you are not following SAP guidelines and may be you are violating the contract signed by you and your client.
Thanks
Ajeet

What is the use of Framework Order type purchase order ?

what is the use of Framework Order type purchase order ? How it differs from other regular type?

Hi,
The document type of Framework Order is "FO" .The regular use of document type for purchase order is "NB".The use of "NB" and "FO" Document type in Purchase order to differentiate the how your material behave or to have different different purchasing document.
Example:Document type "NB" have to the process like Goods Receipt,inoice receipt & payment .In the case of Document type "FO" no Goods Receipt required but IR and payment have to be done."FO"(Framework Order) only deals with low value item with validity period as well as the limits on value/price.
Hope helpful to you and then reward.
Regards,
Biju K

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

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 hot key...

what is the use of hotkey in elementary search helps...how to use this in elementary search helps...can anybody send any navigations on these ..

Creating Elementary Search Helps
Procedure
In the initial screen of the ABAP Dictionary, select object class Search help, enter the name of the search help and choose Create.
A dialog box appears in which you must select the type of search help.
Select Elementary search help and choose .
The maintenance screen for elementary search helps appears.
Enter an explanatory text in the field Short text.
You can for example find the search help at a later time using this short text.
In the Definition tab page enter the selection method of the search help.
You can enter the name of a table or a view (database view, projection view or help view) here. If you enter a table that has a text table, the name of the text table is automatically entered in the corresponding field.
Using the input help (F4 help), select fields of the selection method as parameter in the Search help parameter area. Select the fields that should be used in the dialog box for value selection or in the hit list.
If the selection method is a table that has a text table, both the fields of the table and the fields of the text table are offered in the input help.
The data element of the parameter is automatically copied from the selection method. The data element defines the output attributes and the F1 help of the parameter in the hit list and in the dialog box for value selection.
You can assign the parameter another data element. To do so, select the Mod flag. The Data element field is now ready for input. Then select a data element with the input help (F4 help). Only data elements whose data type, length and number of decimal places is the same as those of the previous data element can be assigned.
This removes the link between the data element of the search help parameter and the data element of the selection method field having the same name. If you cancel the Mod flag, the data element of the assigned table field is used again.
Define the attributes of the search help parameters.
Select the IMP flag if it is an import parameter. Select the EXP flag if it is an export parameter.
You can define the dialog for the input help with the fields LPos, SPos and SDis. Enter the parameter position in the hit list in LPos. If you enter nothing or the value 0 here, the parameter is not displayed in the hit list.
Enter the parameter position in the dialog box for value selection in SPos. If you enter nothing or the value 0 here, the parameter is not displayed in the dialog box for value selection.
Set the SDis flag if the parameter should be a pure display field in the dialog box for value selection. The user is thus informed that the contents of the parameter restrict the value, but he cannot change this restriction. This makes sense for example when the parameter is an import parameter or if it has a default value.
You can assign the parameter a default value in the Default value field.
Select the dialog type of the search help.
The dialog type defines how the hit list is displayed in the input help.
Save your entries.
A dialog box appears in which you have to assign the search help a development class.
Choose .
Do not forget to link the search help to a screen field. The search help attachment is not part of the search help definition; it is part of the object definition to which the search help is attached.
Result
The search help is activated. You can find information about the activation flow in the activation log, which you can display with Utilities ® Activation log. If errors occurred during activation, the activation log is automatically displayed.
Other Options
Assign a hot key: If the search help is to be accessed with a hot key, you must enter a one-place ID in the Hot key field. All the elementary search helps contained in a collective search help should have different short cuts.
Assign a search help exit: In exceptions, you might have to change the standard flow defined by the search help with a search help exit. In this case enter the name of the search help exit in the corresponding field.
Test the search help: You can test the flow of an input help defined by the elementary search help with . A dialog box appears in which you can simulate the behavior of the search help under different conditions. You can obtain information about the options provided in this window with .
See also:
Example for Search Helps
Each customer of a carrier (see Flight Model) or of a travel agency has a customer number. You want to find a search option for this customer number.
The user must be offered two different search paths.
The user should be able to search for the customer number using the customer data, such as the name and address.
The user should be able to search for the customer number using existing customer bookings.
You can provide the required search option by creating a collective search help SCUSTOM. Two elementary search helps SCUSTOM_NAME (for searching with the customer data) and SCUSTOM_BOOK (for searching with the existing bookings) are created for the actual search paths. These elementary search helps are included in the collective search help.
Elementary Search Help SCUSTOM_NAME
This elementary search help should enable you to search for the customer number using the name and address (street, city, country). All this data is contained in table SCUSTOM. Table SCUSTOM must therefore be selected as the selection method of the elementary search help.
You now have to decide which fields of the selection method are needed for the input help process. These are the fields that should appear either in the dialog box for restricting values or in the hit list.
In the dialog box for restricting values, the user should be able to restrict values with the customers name and address, i.e. the fields for the street, city and country. These fields as well as the customers number (the information to be found must always be in the hit list) should appear in the hit list. The fields ID, NAME, STREET, CITY and COUNTRY of table SCUSTOM must be included in the search help as parameters.
The parameter ID is declared to be an import parameter. A pattern entered in the corresponding field of a screen template can therefore be used directly for the value selection. Restrictions for the other parameters of the search help must be entered in the dialog box for value selection.
All the parameters of the search help are declared to be export parameters. As a result, all the parameters of the hit list can be returned to the screen template if the corresponding fields are available there.
Elementary Search Help SCUSTOM_BOOK
This elementary search help should enable you to search for the customer number using existing customer bookings. The flight data for the booking (flight number, date of flight, city of departure, city of arrival) and the name of the customer should be used for the search here. This data is distributed on the tables SBOOK (bookings), SCUSTOM (name) and SPFLI (cities of departure and arrival). The following graphic shows the relationship between the relevant tables, that is the existing foreign key relationships.
In this case a database view SCUS_BOOK must be created on these three tables (see Example for Views) as selection method. The tables in the view (join) are linked as defined by the existing foreign key relationships (see Foreign Key Relationship and Join Condition).
In the dialog box for restricting values, the user should be able to restrict the search for booking data with the carrier ID, customer name, city of departure and city of arrival The flight date and of course the customer number should also be displayed in the hit list. Fields CARRID, FLDATE, CUSTOMID, NAME, CITYFROM and CITYTO of view SCUS_BOOK must be included in the elementary search help as parameters of the search help.
The parameter CUSTOMID is declared to be an import parameter. All the parameters of the search help are export parameters.
Collective Search Help SCUSTOM
The two elementary search helps are now included in the collective search help. You must now allocate the parameters of the elementary search helps to the parameters of the collective search help.
The parameter ID of the collective search help is marked as an import parameter. All the parameters are export parameters. The values can thus be copied from the hit list to the screen template.
Attaching the Search Help
In order to be able to use the search help SCUSTOM in screen templates, the attachment of the search help (see Attaching Search Helps with Screen Fields) must be defined.
Attaching to the Check Table SCUSTOM
The search help should be available for all the fields that are checked against table SCUSTOM. The search help therefore must be attached to table SCUSTOM. The search help parameters must therefore be assigned to the key fields of table SCUSTOM.
The parameter ID of search help SCUSTOM is here assigned to the field ID of table SCUSTOM in this field assignment. No assignment is possible for all other parameters of the search help (NAME, CITY and COUNTRY) since table SCUSTOM does not contain this information as key fields.
Attaching to a Field of Table SCUSTOM
In order that the search help is available when the field SCUSTOM-ID is directly copied to the input template, you have to attach the search help to this field.
With this type of attachment, all the parameters of the search help can be assigned to the corresponding fields of the table.
Structure of an Elementary Search Help
An elementary search help defines the standard flow of an input help. You can define the following components of this flow in the search help:
where does the data displayed in the hit list come from (selection method)
what information should be displayed in the dialog box for value selection and in the hit list (search help parameters)
what field contents can be taken into account for hit list selections and which values in the hit list can be returned to the screen fields (search help parameters)
what dialog steps should be executed in the input help (dialog behavior)
Selection Method
The possible input values displayed for a field in the hit list are determined at runtime by database selection.
If all the data required in the hit list comes from one single table, you only have to select this table (or a projection view on this table) as selection method. If there is a text table for the table, its fields are also available in the input help. A table entry is linked with the corresponding text by the existing foreign key.
If the data needed in the hit list comes from more than one table, you must link these tables with a view (database view or help view). This view must be defined as the selection method.
If the underlying tables are client-specific, the client field must be contained in the view. Otherwise selection for the input help would be for all clients.
Search Help Parameters
A search help has an interface consisting of parameters. These parameters define the fields of the selection method that should be used in the input help.
A parameter of the search help must correspond to each field in the dialog box for value selection and to each field of the hit list. The parameters are copied from the corresponding selection method, that is they always have the same name as the corresponding field of the selection method.
If the search is restricted with a parameter of the search help, this is used in the data selection for formulating a WHERE condition for the field of the selection method with the same name. Vice versa, the parameters of the search help are assigned the contents of the fields of the selection method having the same name.
The search help should not contain any parameters for the clients. In the input help, selection is automatically in the logon client of the user.
A data element must be assigned to each search help parameter, that is a type is always defined for the search help parameters.
A search help can contain further parameters that do not correspond to any field of the selection method. This is normally only necessary if the standard flow of the input help described by the search help still has to be modified by with a search help exit.
Import and Export Parameters
When an input help is called, the entries that the user already made in the input template are taken into consideration. For example, if a user calls the input help for the flight number and already specified the carrier, of course only the numbers of flights of this carrier should be offered.
On the other hand, if the user selects one row of the hit list, more than one field of the input template might have to be filled with data from the selected row of the hit list. For example, if the flight number is obtained from the hit list, the city of departure and the destination should also be returned in the screen template.
The interface of a search help defines the context data that can be used in the input help and the data that can be returned in the input template.
A parameter of a search help can be classified as:
Import parameters: Parameters with which context information from the processed input template (screen) may be copied to the help process.
Export parameters: Parameters with which values from the hit list may be returned to the input template.
A parameter can simultaneously be an input and an export parameter. A search help can also contain parameters that are neither import nor export parameters. Such parameters could be required for the internal input help process, for example.
When you attach a search help, you must define where the import parameters of the search help get their values from and the fields in which the contents of the export parameters are returned. See also Value Transport for Input Helps.
Description of the Online Behavior
The online behavior defines the steps executed in the input help process and the structure of the hit list and dialog box for value selection.
The dialog type defines whether or not the dialog box for value selection should be displayed. If you want to skip the dialog box for value selection, the hit list is displayed directly after calling the input help.
When you define an elementary search help, you can define how the dialog box for value selection and the hit list should look. For example, you can define the position of a parameter in the dialog box for value selection here. The column position in which the values of a parameter are displayed in the hit list can also be defined here
Please reward points..
regards

What is the use of additon in up to 1 rows in SELECT statement

Hi All,
         What is the use of up to 1 rows in select statement.
for example
SELECT kostl
      FROM pa0001
      INTO y_lv_kostl UP TO 1 ROWS
      WHERE pernr EQ pernr
      AND endda GE sy-datum.
    ENDSELECT.
I'm unable to get in wat situations we hav to add up to 1 rows
please help me out...
Thanks,
santosh.

Hi,
Use "select up to 1 rows" only if you are sure that all the records returned will have the same value for the field(s) you are interested in. If not, you will be reading only the first record which matches the criteria, but may be the second or the third record has the value you are looking for.
The System test result showed that the variant Single * takes less time than Up to 1 rows as there is an additional level for COUNT STOP KEY for SELECT ENDSELECT UP TO 1 ROWS.
The 'SELECT .... UP TO 1 ROWS' statement is subtly different. The database selects all of the relevant records that are defined by the WHERE clause, applies any aggregate, ordering or grouping functions to them and then returns the first record of the result set.
Regards,
Bhaskar

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 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 access level

Hi Experts,
What is the access level and what is use of each option in access level
1 Application
2 Superior component
3. Top Component
4. Sap
5. Global
and in Details section what is the use Properties tab
1. Application Component
2. Software Component
3. Development Package
4. Settings Class
Please explain Each option use.
Thank you in advance,
Srini M.

Hi Srini,
just read the documentation (although the current status on SAP Help Portal isn't really up-to-date):
1. [Entry point|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/cc/85414842c8470bb19b53038c4b5259/frameset.htm]
2. [Setting an Access Level|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/32/6aba9c49fd41a5a14f710e121220f1/content.htm]
W/r to "Application Component" etc., docu on Help Portal is definitely not sufficient. Here, the following applies:
An application offers attributes for the application component and the software component. The application component and software component have to be the same as defined for the development package. Application and software component are automatically derived from the development package if they are not set explicitly.
For the definition of the development package, application component, and software component, we recommend that you choose the same values that are in effect for the software solution that you want to enhance by a new BRFplus application. This simplifies all activities related to the software infrastructure, especially transports.
CU
Claus

What is the need of creating New order type in PO

Dear Experts,
I have a doubt in MM, what is the need of creating New Order Types? Please explain with Business scenario. Thanking you,
Regards,
Elangovan.A

Hi Elangovan
Whenever you have a doubt like this...
--- just verify the config settings for your parameter (order type here).
---Also check whether authorizations can be given for this ?
---Do you need it for specific analysis ? Are there standard reports/listings available ?
So, some of the uses of order type are:
1) What are the parameters controlled by order type ?
It controls the number ranges and screen layouts etc. So, if you want to have different set of number ranges and different screen settings, then you may need a new order type.
2) Authorizations can be controlled with order type.
3) You can also use it in analysis/listings
Best regards
Ramki

How to make the dblink and what is the use of this

plz any body tell me "how to make the dblink and what is the use of this"
sujit

Do you understand how to make the Slider work using code to read its value? You will need to look into that in order to do this.
What you can do is have the yello rectangle be a movieclip that sits over the red rectangle and use the Slider to control the yellow rectangle's alpha property from 0 to 1. That way the yellow will gradually fade as you slide.
What you will then need to do is figure out how to make the number of dots that appear reduce from 15 to 8 over the same range of the slider. You need to use the fractional value from the slider to decide how many dots either appear or do not appear.
You should not start new postings for the same topics that you arlready have postings for. Doing so in the future might result in them being removed.

What is the uses of a Transport order ?

Similar Messages

Maybe you are looking for