What is the use of account modifier in automatic account

hi
can someone explain the use of account modifier in automatic account

The Account Modifier is used to break account determination down by movement type.
For example, by default in SAP, the system says for movement type 101 and posting key PRD there is no modification. However, I can enter a code (e.g. XXX) against movement type 101 and posting key PRD and code YYY against movement type 102 and PRD.
Then in u2018Configure Automatic Postingsu2019 when we go into posting key PRD, we will make entries for u2018general modifieru2019 XXX, account 400001 and YYY of 400002 (there will also need to be an entry for a u201Cblanku201D modifier which should cover all the other movement types).
Regards,
Chandra

Similar Messages

  • What is the use of OASV transaction in Asset accounting

    Dear Experts,
    Could you please advise me clearly what is the use of OASV transaction in Asset accounting and which GL account we need to use for debit and credit while using this t code. Can you please provide me along with examples for better understand and that would be great for me.
    Thanks in Advance,
    Murali

    Transfer Balances
    In this step you can post balances to G/L accounts which have already   been defined as reconciliation accounts. You can only post these   corrections in company codes which have implementation status.
         The transfer of legacy asset data using the legacy asset transaction  does not affect the balances of the corresponding reconciliation  accounts in Financial Accounting. Therefore no automatic balance formation or reconciliation takes place and you will need to manually  reconcile the balances. You can ascertain the Asset Accounting values  using of the asset list. When you start this report, specify January 1st  of the current fiscal year as the report date. The system will then  provide data as of December 31st of the previous fiscal year (in other words, no depreciation from the current fiscal year is included).
    Activities
    Copy the balances from any suspense accounts to the Asset Accounting  reconciliation accounts.

  • What is the use of  SWIFT CODE IN BANK ACCOUNTS

    What is the use of  SWIFT CODE IN BANK ACCOUNTS

    HI kishore,
    The SWIFT code is used for identifying banks in international payment transactions.
    see these links for your refernece
    http://sapexperts.blogspot.com/2007/01/bank-accounts.html
    http://www.answers.com/topic/international-bank-account-number
    thanks
    karthik

  • What is the use of general modifier?

    Hi,
    Please note while using mvt type 201 we will give cost center and assign a G/L account.
    Eg: Cost Center -1000, G/L account 400000
    It means that consumption is captured in the G/L account 400000.
    Why we have to assign a G/L account for VBR key?
    What is the purpose of it?

    Hi,
    General Modifer used for  to break account determination down by movement type.
    VBR: for internal goods issues (for example, for cost center)
    Regards,
    Biju K

  • What is the use of provision account in vkoa t.code

    Hi,
    i have a doubt regarding in vkoa t.code there are G/L Accounts column and Provisions column what is the use of provision column and what is the difference between these two.
    i am waiting for u r replies.
    Thanks & Regards,
    Kishore.

    Hi,
    'The provision account is only required if there are conditions that are relevant for accrual, for example, rebate conditions. If this is the case, account determination takes place in the billing document with the field'
    In other words it will be used to store the valuue of a( for eg.,Rebate) condition type in a different GL a/c for the periodic calculation of the total value of the same cond.type...
    chk this thread for more clarity on Accrual
    Re: Rebate Accrual Rate
    Reg
    JJ
    Edited by: Jagsap on Jul 10, 2009 1:03 PM

  • What is the use of split valuation Accounting view

    Hi
    What is the use of split valuation Accounting view.is it compulsary to give for every materisl?
    regards
    Ashok

    Hii Ashok,
    The SAP R/3 System allows you to valuate stocks of a material either together or separately, that is, according to different valuation criteria. Split valuation is necessary if, for example:
    1. Stock from in-house production has a different valuation price than externally procured stock.
    2. Stock obtained from one manufacturer is valuated at a different price than stock obtained from another manufacturer.
    3. Different batch stocks of a material have different valuation prices.
    4. Value damaged and repair part differently from a new part.
    To used split valuation, you have to activate it using 'OMW0'.
    To change split material valuation once it has been set, you must
    1. first post out all stocks (for example, to a cost center or with movement type 562)
    2. then change the control parameters
    3. if necessary, change the automatic account determination
    4. finally post the stocks back in again
    In split valuation, you can distinguish between partial stocks of a material according to certain criteria and valuate them separately.
    The material stock is divided according to valuation category and valuation type.
    The valuation category determines how the partial stocks are divided, that is, according to which criteria.
    The valuation type describes the characteristics of the individual stocks.
    With the function "Setting" you can determine:
    which valuation categories exist in your company (global categories)
    which valuation types exist in your company (global types)
    which valuation types belong to which valuation category
    which valuation categories exist in a valuation area (local categories)
    Your entries are only relevant if you set split valuation as active in the function "Global settings".
    In the standard SAP R/3 System, the following valuation categories are default settings :
    B procurement type
    with the valuation types:
    "EIGEN" for in-house production
    "FREMD" for external procurement
    H Origin
    X automatic valuation (only for batch)
    To select split valuation ('OMWC'), proceed as follows:
    1. Determine the valuation categories and valuation types that are allowed for all valuation areas:
    global valuation categories via menu "Goto --> Global Categories"
    global valuation types via menu "Goto --> Global Types"
    2. Allocate the valuation types to the valuation categories.
    a) Select "Goto --> Global Categories".
    b) Position the cursor on a valuation category and select
    "Goto --> Global Categories --> Assignments --> 'Types->Category'".
    c) Activate the valuation types you want.
    3. Determine the local valuation categories for each valuation area.
    a) Select "Goto --> Local definitions".
    b) Position the cursor on a valuation area and select
    "Goto --> Local Definitions --> Allocate Categoires->Org.units (button Cats->(OU)".
    You obtain a list of the global valuation categories.
    c) Activate the categories to be used in this valuation area.
    The system creates the local valuation types based on the allocations under point 2.
    Only now can you create a master record with split valuation.
    Regards,
    Kumar

  • 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 customer’s name and address, i.e. the fields for the street, city and country. These fields as well as the customer’s 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 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 commit work and rollback work

    hao friends,
    what is the use of commitwork and rollback work where we can use these open sql statements .
    thanks,
    anji

    hi all
    i have written the following code in my development system to change the records of my database.
    SELECT * FROM zyikostl INTO TABLE itab.
      LOOP AT itab INTO wtab.
        tabix = sy-tabix.
        DO.
          READ TABLE itab INTO ktab WITH KEY kostl_alt = wtab-kostl_neu.
          IF sy-subrc = 0.
            wtab-kostl_neu = ktab-kostl_neu.
            MODIFY itab FROM wtab INDEX tabix.
            CONTINUE.
          ELSE.
            EXIT.
          ENDIF.
        ENDDO.
      ENDLOOP.
    MODIFY zyikostl FROM TABLE itab.
    In the development system i have only few records its working fine,but when it is been moved to test system there are 2500 records in the database so the report is taking much time(more than 5 hours )
    i sthere any solution for this ....
    thanks,
    vaasu.

  • What is the use of T.Code: FAGLCOFIFLUP - Post CO Documents to FI?

    Expects...
    What is the use of T.Code: FAGLCOFIFLUP - Post CO Documents to FI
    Accounting> Financial Accounting> General Ledger> Corrections> FAGLCOFIFLUP - Post CO Documents to FI
    Thanks & Regards
    Bhagiradha.P

    Hi,
    The real-time integration of Controlling with Financial Accounting was active at the time the CO documents were posted.
    CO documents could be not transferred to financial accounting on behalf of errors which are only known to occur in the following situations:
    - During mass processing such as internal CO assessments or distributions
    - Manual posting of individual CO documents is not possible if errors occur in financial accounting.
    - If real-time integration was not active when the CO document was posted, you must use the report   FAGL_COFI_TRANSFER_CODOCS to transfer these CO documents to financial accounting because they are not in the worklist.
    Regards,
    Eli

  • What is the use of transaction code VF24

    what is the use of transaction code VF24. if possible please provide some documentation

    Hi,
    The main use of VF24 transaction code : edit work list for invoice list.
    This enables the user to understand the processes left during the combine processing of invoices.
    like which are left for releasing to accounts, which have still pending payment posting, with respect to the invoice list consisting of the combination of invoices.
    invoice list is a combination of different invoices with same critierias. so to check and process these invoice lists collectively this function is used.
    regards,
    siddharth.
    regards,
    Siddharth.

  • What is the use of valuation class in Finished Material Master?

    Dear Expert
    What is the use of valuation class in Finished Material Master?
    Thanks of Advance

    hi,
    this is to inform you that,
    generally 7920 - will be the valuation class for the finished goods.
    Allows the stock values of materials of the same material type to be posted to different G/L accounts & vice versa.
    this is an integration field which identifies the G/L accounts & goods movement types.
    balajia

  • What is the Use of Zone (Characteristic) in CO-PA

    Hi,
    What is the Use of Zone (Characteristic) in CO-PA
    Regards
    Bhagirdha

    hi bagiradha,
    This is pradheep i have one question in asset accounting depreciation is diferent in tally and sap i want eqwal the balance in sap how i balance
    please give me the solution
    Thank you!
    Kind Regards,
    Pradheep.

  • What is the use of points earned in apple support communities??

    what is the use of points earned in apple support communities??

    mende1      Valmojado, Toledo, Spain
    This solved my questionRe: How the heck do you get points on your apple support communities account?
    Jul 12, 2013 10:20 PM (in response to BMPU)
    To get points, you have to answer questions. If the user that created the post tested your solution and it worked, he/she (may) give you a "This solved my question". As you can see in the right part of this page, a solved question adds 10 points to your account. If you helped solve the problem, you receive 5 points. On a single thread, the original poster can only give 1 "This solved my question" and 2 "This helped me", so you can receive a total of 20 points.
    With these points, there are levels that you can see in this page > https://discussions.apple.com/static/apple/tutorial/reputation.html When you level up, you receive privileges like report posts, access to Community Calls... The most important level respecting to privileges is the level 6, that gives you access to a special forum called "The Lounge" (where you can talk about anything you want, complain about an user or report problems with the forum), and you also receive gifts from Apple and other privileges

Maybe you are looking for