User Exit for material valuation is not called up

Dear all,
We want to add special logic when user process the material valuation through CK11N.
We have also activated the project with the user exit COPCP005, changed valuation variant to "valuation price with user exit" and modified ZXCKAU08 in the component EXIT_SAPLCK21_002.
And this special logic is correctly workd on development but we are not able to get the desired result on pre-production and production.
Could you please guide that I check anything more?
Thanks in advance.
SK Roh.

Can you explain a little more where you encountered the problem?
1. Is there a Val Strategy before the Val Strat U that is probably able to find a price for costing?
2. Is the User Exit being triggered?
3. Can you run CK11N in the debug mode (/h) and check if the User Exit is triggered?
4. If all of these occur, the problem probably lies in the ABAP code... check for changes in the material number range or plant codes, or the plant-specific material status - the system does not valuate if the status does not permit it to.
If nothing works, come back with confirmation of the above and we'll go forward from there.
Cheers.

Similar Messages

  • PC-WQS: User exit for material valuation

    Hello,
    Currently we use data from the purchase info records to carry out material valuation of raw materials in the cost estimate. The client would like to get this data from the contracts instead of the info records since all purchase orders get information from the contracts. The second reason is that maintenance of the info record is very cumbersome and prone to errors when creating or updating the cost/ quantity.
    My question is, has anyone used the user exit COPCP005 - User exit for material valuation (strategy U) in the valuation variant and has anyone gone after the contracts to get the purchase price?
    If yes, I would like to know how you did it.
    Thanks,
    dinesh

    Can you explain a little more where you encountered the problem?
    1. Is there a Val Strategy before the Val Strat U that is probably able to find a price for costing?
    2. Is the User Exit being triggered?
    3. Can you run CK11N in the debug mode (/h) and check if the User Exit is triggered?
    4. If all of these occur, the problem probably lies in the ABAP code... check for changes in the material number range or plant codes, or the plant-specific material status - the system does not valuate if the status does not permit it to.
    If nothing works, come back with confirmation of the above and we'll go forward from there.
    Cheers.

  • User-Exit for material

    Hi!
    I have to create an user-exit for a material to force a water content value to be added to it. Can anyone tell me what user-exit should I be using for it please.
    Thanks

    Actually there is a material by number 20000 which alreday has this functionality set up for it and the method (ABAP objects) for it is :
    ZCL_IM_SD_SHP_DEL_PROCESS    IF_EX_LE_SHP_DELIVERY_PROC~SAVE_DOCUMENT_PREP
    . But I am not sure if this can be used for the other material too which si 73420.
    I have never used a user-exit like this before so not aware how to use it or what to do. Can anyone explain me plz.
    Thanks

  • User exits for Material Master in ECC 6.0

    Hello,
    We would like to have a function for checking descriptions when we are saving a material in the material master. We are today running R/3 on release 4.6C and as I understad there are no user exits at that point for this release. We are going to do an upgrade to ECC 6. Do you know if there are more user exits for the material master for this release?
       Regards
       Ann-Sofie

    Following are the user exists available for Material master :-
    -> MGA00001
          Enhancement and addition of checks and (limited) changes to data
    -> MGA00002
         Control for the material number assignment
    -> MGA00003
         Control for the material number display
    -> MGV00001
         Distribution via ALE
    -> MGV00002
         Read customer-specific filter objects for a material

  • User Exit for Material Plan Costs

    I have an escenario where the client needs another option to calculate the material plan costs, but need to identify the correct user exit.
    In transaction OKYF exist the option "U Valuation Price with User Exit" but need the user exit to use.
    Hope to receive information soon...
    Best Regards...

    Hi
    you can use unit costing for material option for this...
    Automatic netowrk costing for material component
    you need to maintain proper costing variant for material component in config.
    in projects assign material then select material -edit - cost - unit costing.
    which will get reflected in network cost in CJ40.
    Venkatesh

  • User Exit for Material Master

    Hi everybody,
    I'm looking for a BAdi or an userexit for material master data (TA MM01/MM02). This BAdi should be used every time a user press the save button. I could not find any BAdi in the SAP help.
    Do anybody of you know if there is a BAdi implementation or userexit exists?
    Regards
    Berthold

    Hi Berthold,
    Here are user exits and BADI available for MM01/MM02.
    User Exits:
    MGA00001                             
    MGA00002                             
    MGA00003                             
    BADIs:                     
    MG_MASS_NEWSEG                       
    MATGRP_SKU_UPD                       
    CDT_CHECK_MATERIAL                   
    BADI_MM_MATNR                        
    BADI_MAT_F_SPEC_SEL                  
    BADI_MATNR_CHECK_PVS                 
    BADI_MATERIAL_REF                    
    BADI_MATERIAL_OD                     
    BADI_MATERIAL_CHECK                  
    BADI_GTIN_VARIANT                    
    BADI_EAN_SYSTEMATIC       
    Regards,
    Ferry Lianto

  • User exits for payroll PCPO0001- EXIT_RPCIPE00_002 not working

    We have activated User exit PCPO0001- EXIT_RPCIPE00_002, requirement was to set the line item text SGTXT of the subsequent Accounting document, but there seem to be no activity happening for it  (assigned breakpoints in the exit codes but transaction PCP0 does not stop at the breakpoint).
    I have created the Include program and the actviated the Exit and the Project from SMOD and I think I have followed all the necessary steps.
    Is there anything I am missing, are there any Business Transaction Events that we can use.
    Would be greatful for your reply.
    Regards

    Thanks for your reply
    We did tried to apply breakpoints on EXIT_RPCIPE00_001 but it did not stop at that also, although we haven't implemented EXIT_RPCIPE00_01's INCLUDE program does that makes any difference ?
    Is there any other way we can run our code during payrol's posting to accounting?
    Our scenartio is that we need to add some Text from the Payroll information into the subsequent Accounting Document's line Item text (SGTXT).
    Do need some answers?
    Regards

  • User exit for material code based on number range

    Hi viewers,
    Can you please tell me the User exit to be identified for material code t based on  the number range (External or Internal)
    For ex: LAFAMLP is the material code I want this material code as case sensitive .
    It should take what ever case we give.
    Regards
    Kumar

    Hi,
    First goto MM01 transaction code in menu System-> status..pick the program name ,then
    Goto SE38 give that program name select Attributes radio button click on Display button,
    you will get one popup from the popup pick Package ...
    Then now goto SMOD transaction in menu utilities(or/any one of the menu you will find (find option ))->Find this will list out all the possible exits...As follow
    mga00001 material master (industry): checks and enhancements
    mga00002 material master (industry): number assignment
    mga00003 material master (industry and retail): number display
    I think second one will help for you ,,,here you can code your requirement

  • User Exit for Material Group...Urgent help needed

    Does anybody have an idea of which user exit can be used to capture the changes made to material group in MM02(Material)..... Urgent help needed...

    See  the below user exit and this will trigger under MM01,MM02 and MM17 Transaction
    Enhancement name : MGA00001
    Function module :EXIT_SAPLMGMU_001
    Include : ZXMG0U02
    Reward Points if it is helpful.
    Thanks
    Seshu

  • User exit for material document.

    Hi,
    does any one know and user exit or BADi which gets triggered when ever a material document is posted  ( Saved) in to the system and is irrespective of transaction used.  we want to send the updated stock information and their status to a third party system when ever there is a material document posted via an IDoc.

    Try BAdI [MB_DOCUMENT_BADI|http://www.sdn.sap.com/irj/scn/advancedsearch?query=mb_document_badi], method [IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_UPDATE|http://www.sdn.sap.com/irj/scn/advancedsearch?query=mb_document_badi+mb_document_update]
    Regards,
    Raymond

  • User exits for VA01

    Hi Experts,
    For transaction VA01, is it possible to know list of  user-exits available.
    Thank you

    Hi Peter,
    You can have the User Exits for sales order processing not for the VA01 transaction.
    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.
    I hope it will help you,
    Regards,
    Murali.

  • User Exits for Purchase order Header Text Validation

    Hi Experts,
    I need user exit for validate a  Long text in Purchase order header data for a Particular Doc type.
    We are using 4.6 B so badi is not available .
    So pls tell me user exit for the same or any other method as i was unable to find user exit for this scenario.
    Note :  This valiadation should trigger whhile creating  PO.
    Warm Regards
    Santosh Kumar
    Edited by: Santosh L on Mar 19, 2010 9:58 AM

    i have used concept of global memory through call stack

  • EXIT_SAPLEBND_002 -- user exit for release strategy

    Hi,
    This is regarding help on user exit for release strategy, ref: note no. 365604, however after going through all the config part given in the given note we activate the fm in cmod.... but after activating the release tab goes off from  me29n.
    That is after you activate in cmod and then if u create po and go to me29n the relese tab is not there.
    if u deactivate and create po and then relese the release tab in me29 would appear.
    All we are trying is that the po in me29n should be open to release again if we change the delivery date. However what coding and how is still a second step , first is as soon as the exit is active the tab goes off.
    New to user exit . plz help.

    Hi Again,
    I guess I have solved the issue temporarily, however Am not sure if this is the best which cld be doen to the issue.
    I didnt make any new characteristics in ct04, for the delivery dats since i didn't want to restrict the delivery date. All I did i yje coding below in the exit :
      DATA wa_eket TYPE LINE OF mmpur_beket.
      DATA wa_eket1 TYPE LINE OF mmpur_beket.
      data: c type i.
       data: p type i.
      break1.
      break2.
      e_cekko   = i_cekko.
    loop at it_beket into wa_eket . " for comparing previous and the current del date
      e_cekko-usrc1 = wa_eket-eindt.
      SELECT SINGLE * FROM eket INTO wa_eket1 WHERE ebeln = wa_eket-ebeln
      AND ebelp = wa_eket-ebelp.
      if wa_eket1-eindt <> wa_eket-eindt.
      import c from memory id 'CID'.
      c = c + 1.
      clear p.
      p = c mod 2.
      if p is not initial.             " adding 0.01 to the characteristic value for p.o amt.
      e_cekko-GNETW = e_cekko-GNETW + '0.01'.
      else.
      e_cekko-GNETW = e_cekko-GNETW - '0.01'.
      export c to memory id 'CID'.
      endif.
      endif.
      endloop.
    The logic I tried using is since the relese gets reset incase of p.o amnt and hence indirectly po amnt so i changed the value of p.o value by 0.01 incase of change in delivery date. cekok-gnetw doesnt reflect anywhere in the p.o as amnt, I guess its for defing range for relese stragey's amont in ct04 characteristics.
    However anything better incase u know plz let me know, or do u think this can cause any problems later....new to exits.
    Rgds,
    Anu.

  • Exit for Material Master UPdate

    Hi Friends,
    could anyone let me know any user exit for Material Master UPdate.
    Thanks in Advance
    Regards

    hi
    good
    MGA00001            Material Master (Industry): Checks and Enhancements
    MGA00002            Material Master (Industry): Number Assignment
    MGA00003            Material Master (Industry and Retail): Number Display
    thanks
    mrutyun^

  • User exit for sale order material serial number change

    I am looking for User exit for changing the serial number for the saleorder material va01.

    Hey,
      Check the include program : MV45AFZZ. it will trigger at the of saving the sale order.
    IF SY-TCODE EQ 'VA02' OR SY-TCODE EQ 'VA01'.
    Endif.
    Note : Write your coding inside the IF clause to avoid affecting the other transaction codes.
    Regards,
    Saravanan M

Maybe you are looking for

  • Error while deploying an Agentry application on SMP 2.3 Server

    Hello Experts, I am trying to deploy a customized SAPWM application on the SMP 2.3 server. I am referring to the tutorial maintained at the following URL :http://scn.sap.com/docs/DOC-43353 I have zipped the contents of the application folder (under S

  • Mini Display Port to Dual Link DVI Does Not Work Right

    Somebody said here that this was an isolated problem. Well, I just got my new MacBook Pro 15", used the adapter to hook to the 30" Dell monitor, and it works a few minutes, then the screen distorts. Count me among the isolated problems- it is beginni

  • After Effects CC 2014 Crashing with Magic Bullet Looks on Mac

    Hi, I recently installed the upgrade to the latest After Effects CC 2014 v13.0 and found the Magic Bullet Looks now causes After Effects to crash. I'm using MBL v2.5.2 I opened the Activity Monitor and noticed that whenever the crash occurs the Adobe

  • Transaction/Movement type on the vendor line item

    When we post to a vendor using F-43 (or FB01) using posting key 31. We want the field Transaction type to be available for input in the vendor line item. But this is not happening. note: In the FSG of vendor recon account and Posting key 31 this fiel

  • Attachement linked to purchase order

    I want to know where the attachements linked to purchase order are getting stored in SAP.Since the attachement are linked to purchase order(header level) ,is it possible to link those attachements at item level so when we select a particular item  an