ABZO Posting with T Type 100 By LSMW ( with Dep areas restriction)

Hi Gurus
I have few hundreds of Assets that are created before the Activation of New dep Areas. Now i have to updated the Acquisition costs to those 10 and 11 Dep areas only. I am able to do the update the acquisition costs to Asset master by ABZO tcode with restricted T type 100 for 10 and 11 Dep areas manually But i have to do it by LSMW process with BAPI  method,  But ended up in the following error message.
Posting with transaction type 100 is not possible here, see long text
Message no. AAPO177
Diagnosis
Transaction type 100 has a depreciation area limitation, although posting is not mandatory in all of the depreciation areas entered. However, it is not possible to select depreciation areas in the current transaction.
Procedure
Check the specifications for transaction type 100 or use transaction LSMW to enter the transaction.
Please guide me the procedure to fix this issue.
Meenakshi.N
Edited by: Meenakshi.Nakshatrula on Jun 21, 2010 4:35 AM

ABZO - Tcode,
100 - Transaction type
Assets - Non AUC assets
Mistake is when i am recording the Session i haven't correctly determined the Depreciation areas. That lead me into error message.
I was able to do it successfully by Batch input recording method instead of BAPI.
Thanks
Meenakshi.N

Similar Messages

  • Transfer posting with Mov Type 311E in MIGO with reference to SC-PO

    Hi,
    I am working with MTO scenario.
    I want to carry out transfer posting of material with movement type 311E against subcontracting Purchase Order which is sale order specific.
    However, system does not allow me to do the same. whenever transfer posting, PO & movement type is selected in transaction MIGO, item details entry tabs are displayed blank.
    Below steps are being follow:
    Scenario is MTO ( special stock subcontracting)
    1. Subcontracting PO no. 4500000147 against Sale Order no 61 created.
    2. RM code - 61, available stock 100 TO & batch no.0000000127
    3. Transfer material to vendor for processing through MIGO ( since it is a special sales order stock, transferring happens from SL 0001- Main Stores to SL VLSC -Virtual storage location) using movement type 311 E
    5. Item Data details tabs are blank.---This is the issue / error.
    Note: I am restricted to post transfer posting through MIGO-Transfer Posting (will not use MB1B) due to some enhancement of MIGO and interfaces with legacy system.
    Please have a look on attachment for SAP screen issue.
    Regards
    Mohit Jaiswal

    Hi Mohit ,
    please check below link , you need to perform steps as given
    http://help.sap.com/saphelp_470/helpdata/en/4d/2b90b043ad11d189410000e829fbbd/content.htm
    also see the sales order subcontracting using the business addon
    http://help.sap.com/erp2005_ehp_04/helpdata/en/c7/2587b8dad94c52854ccd28015dceb0/frameset.htm

  • Mac synch warning POST/marketeer error type 100 in console log

    I see many notices and warnings in the console log sent by dotmacsynchclient saying POST/marketeer (FAILED) httpStatus Code:503, errorType:100. How do I get rid of these. Everything else is looking fine. These are annoying. I've synched several times after getting all the settings just right. Just recently started over with a new erase and install of Leopard, updated it to 10.5.8 and most things look fine. Anyone else have this issue with .Mac and synching issues with Leopard?

    Reset BusySync solved it for me
    A few weeks ago the Console started reporting errors with mobileme syncing. The following kind of errors happened anytime a sync was attempted
    6/22/10 1:01:16 PM mobilemesyncclient[14564] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:C6830B61-C17B-467A-99A5-15BE3BEB45EC, auto-retries=0, manual-retries=0
    6/22/10 1:01:59 PM mobilemesyncclient[14615] [244ef0] |Dataref|Warning| Attempt to save data wrapper <ISDDataWrapper[0503A63F-4027-4072-89A1-59035C44118F.com.apple.DotMacSync.data] signature=<48257585 b8aa0e46 ccec4d8f 5a281167 4b0129c4>> that already exists. Proceeding.
    6/22/10 1:01:59 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:01:59.212 mobilemesyncclient[14615:320f] [244ef0] |Dataref|Warning| Attempt to save data wrapper <ISDDataWrapper[0503A63F-4027-4072-89A1-59035C44118F.com.apple.DotMacSync.data] signature=<48257585 b8aa0e46 ccec4d8f 5a281167 4b0129c4>> that already exists. Proceeding.
    6/22/10 1:01:59 PM mobilemesyncclient[14615] [244ef0] |Dataref|Error| The data wrapper <ISDDataWrapper[590A07DB-D6F3-4B89-BEDD-99A07AE6961D.com.apple.DotMacSync.data] signature=<a5579fb9 52ec0383 9d892c02 111f00cc dc456ba5>> has never been saved before and it has no associated data!
    6/22/10 1:01:59 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:01:59.225 mobilemesyncclient[14615:320f] [244ef0] |Dataref|Error| The data wrapper <ISDDataWrapper[590A07DB-D6F3-4B89-BEDD-99A07AE6961D.com.apple.DotMacSync.data] signature=<a5579fb9 52ec0383 9d892c02 111f00cc dc456ba5>> has never been saved before and it has no associated data!
    6/22/10 1:01:59 PM mobilemesyncclient[14615] [244ef0] |ISDRecordStore|Error| Failed to save data reference Error Domain=ISyncDataWrapperError Code=2 "The operation couldn’t be completed. (ISyncDataWrapperError error 2.)"
    6/22/10 1:01:59 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:01:59.226 mobilemesyncclient[14615:320f] [244ef0] |ISDRecordStore|Error| Failed to save data reference Error Domain=ISyncDataWrapperError Code=2 "The operation couldn’t be completed. (ISyncDataWrapperError error 2.)"
    6/22/10 1:01:59 PM mobilemesyncclient[14615] [244ef0] |ISyncSession|Warning| Exception (because Unable to fault in data reference Data with length 2897) while attempting to commit accepted changes. Cancelling sync.
    6/22/10 1:01:59 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:01:59.227 mobilemesyncclient[14615:320f] [244ef0] |ISyncSession|Warning| Exception (because Unable to fault in data reference Data with length 2897) while attempting to commit accepted changes. Cancelling sync.
    6/22/10 1:02:01 PM mobilemesyncclient[14615] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:27294D3E-392C-42AB-8615-3E5637C60C5E, auto-retries=0, manual-retries=0
    6/22/10 1:02:01 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:02:01.316 mobilemesyncclient[14615:3883] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:27294D3E-392C-42AB-8615-3E5637C60C5E, auto-retries=0, manual-retries=0
    6/22/10 1:02:49 PM mobilemesyncclient[14657] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:D9E9D43E-F38F-4B34-B546-DF7D4934D34C, auto-retries=0, manual-retries=0
    6/22/10 1:02:49 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:02:49.092 mobilemesyncclient[14657:3d87] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:D9E9D43E-F38F-4B34-B546-DF7D4934D34C, auto-retries=0, manual-retries=0
    6/22/10 1:04:32 PM mobilemesyncclient[14723] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:0140C9E1-C874-44D5-9B8D-B5B69FAD6666, auto-retries=0, manual-retries=0
    6/22/10 1:04:32 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:04:32.870 mobilemesyncclient[14723:3d87] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:0140C9E1-C874-44D5-9B8D-B5B69FAD6666, auto-retries=0, manual-retries=0
    6/22/10 1:05:11 PM mobilemesyncclient[14751] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:7F91D33F-844E-4D95-A801-E7A233C184F3, auto-retries=0, manual-retries=0
    6/22/10 1:05:11 PM com.apple.syncservices.SyncServer[14529] 2010-06-22 13:05:11.762 mobilemesyncclient[14751:388b] POST /marketeer (FAILED), httpStatusCode:503, errorType:100, transactionState:5, txnId:7F91D33F-844E-4D95-A801-E7A233C184F3, auto-retries=0, manual-retries=0
    I tried forcing a resync from my Mac to the cloud but the errors persisted. The errors started under 10.6.3 and continued under 10.6.4.
    I happen to use BusySync. I simply reset BusySync's Sync History and the errors went away. Haven't had any more errors now for hours.
    I recognize that doesn't exactly help if you don't use BusySync, but perhaps it offers a clue. For instance there might be a cache file that needs refreshed or deleted in order for things to line up properly again.
    As long as you have good backups it might be worth disabling Sync, deleting the
    ~/Library/Application Support/MobileMeSyncClient
    ~/Library/Application Support/MobileSync
    folders, reenabling sync, and forcing a sync from your Mac to the cloud. If that doesn't work then restore the folders and try something else.
    Good luck!

  • .Mac/Synching: dotmacsynchclient warnings for POST/marketeer error type 100

    I see many notices and warnings in the console log sent by dotmacsynchclient saying POST/marketeer (FAILED) httpStatus Code:503, errorType:100. How do I get rid of these. Everything else is looking fine. These are annoying. I've synched several times after getting all the settings just right. Just recently started over with a new erase and install of Leopard, updated it to 10.5.8 and most things look fine. Anyone else have this issue with .Mac and synching issues with Leopard?

    Try the MobileMe forum.

  • Movement type 313 and 315 with special stock K.

    Hi,
    I would like to post a movement type 313 and 315 with special stock k (consignment) but it is not possible. Also i have tried to create a new movement type (OMJJ) coping 313 and trying to set stock special k in somewhere but I couldn't.
    it is possible a movement type 313 K or 315 K?
    Thanks in advance.
    Anna

    Hi Anna Barnils ,
    Not possible.
    Read the below help:
    SproMMInventory Management and Physical InventoryMovement TypesClick on the help infront of Copy, Change Movement Types and check movement types 313 / 315
    Regards
    Ramesh Ch

  • How to create table with row type in smart forms

    How to create table with row type in smart forms with out line type
    please explain me the procedure

    HI,
    A table type describes the structure and functional attributes of an internal table in ABAP. In ABAP programs you can reference a table type TTYP defined in the ABAP Dictionary with the command DATA <inttab> TYPE TTYP. An internal table <inttab> is created in the program with the attributes defined for TTYP in the ABAP Dictionary.
    A table type is defined by:
    its line type, that defines the structure and data type attributes of a line of the internal table
    the options for managing and accessing the data ( access mode) in the internal table
    the key ( key definition and key category) of the internal table
    The row type is defined by directly entering the data type, length and number of decimal places or by referencing a data element, structured type ( structure, table or view) or other table type. Or the row type can be a reference type.
    <b>for more info :</b> http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb366d358411d1829f0000e829fbfe/content.htm
    Internal table
    Regards
    Sudheer

  • Transaction type 100 not possible (posting to affiliated company)

    Hi All SAP Guru's
    I am trying to post asset acquisition through F-90
    Asset Dr Transcation Type 100
    To, Vendor Cr
    while saving the above document  i am getting an error Transcation type 100 is not possible (Posting to Affiliated Company)
    to explain further my client are using Trading Partner Concept, may be that is the reason document is not getting posted
    In Transcation Type I tried to change Post to affiliated Company then system allowing to post the document, but in real sense we should not give post to affiliated company at Transcation Type
    can anybody help, is there any alternative to go ahead
    Regards
    Sreenivasulu
    Edited by: sreenivasulu VAS on Feb 26, 2009 1:57 PM

    Hi,
    When there's a trading partner in the document, you need to use a different transaction type for external acquisition.
    Have you tried this? (I've used this one. without chaging document type setting)
    150     Acquisition from an affiliated company
    Difference from Transaction type 100 is posting type. 150 has a posting type of 'Post to affiliated company' whereas 100 has not.
    Check with IMG (T-code: AO73)
    Heeseon.

  • Transaction type 100 not posible (posting to affiliated company)

    Hil
    While asset acquistion posting in f-90 ia geting error message "Transaction type 100 not posible (posting to affiliated company)"
    can you please give solution for this one

    Hi
    pl check following settings in spro Img->Financial Accounting-Asset Accouning----Transctions--Acquisitions-Define Transaction Types for Acquisitions-in choose activity window -dbl clk on "Define Transaction Types for Acquisitions"
    select transaction type 100--click on details--check posting type.  if  " Do not post to affiliated company." is selected then choose another transaction type which allows acquisition with option "Post to affiliated company"
    regards
    Vishwas
    Edited by: Vishwas_bapat on Mar 24, 2011 1:24 PM

  • Error posting with trans.type 159 not possible (no aquisition posted)

    Hello All,
    A user has created an PO for asset with GR non valuated  in 2007 and has performed a MIGO/GR in the same year 2007. Now in 2008 the user has received an invoice against the said asset and wants to post it thru Trans MIRO.
    At the time of posting the invoice the user gets the error "posting with trans.type 159 not possible (no aquisition posted)" . Since this is a completely new asset and GR non valuated asset process is a standard in SAP why is the system recognising the transation type as 159 i/o trans type 100 ie new asset aquisition.
    If i post a dummy value to the same asset using FB01 the system accepts the value but the same process if i intend to follow usin MIRO system does not allow.
    Can you guys help me
    Thanks
    Nelson

    Thanks Paul for your reply, I checked the depreciation key. inthe key the "Aqu only allowed in capitalization year is marked as NO"
    Therefore the problem is not the depreciation key
    Thanks
    Nelson

  • Posting with trans.type 300 not possible (No acquisition posted)

    Dear Gurus,
    When I execute the T-code ABUMN, i've got the following message:
    Posting with trans.type 300 not possible (No acquisition posted)
    Message no. AA324
    Diagnosis
    Transaction type 300 belongs to a transaction type group, which can only
    be used to post to assets to which posting has already been performed.
    However, no postings have been made to this asset.
    Procedure
    Use a transaction type from a transaction type group, which can be used
    for the first acquisition to an asset.
      Regards

    Hi sapraj ,
        Transaction type 300 is "transfer of retire. old assets data from cap. asset" ,which means before you transfer this asset, it has to be first capitalized , for asset capitalization, you may use transaction type 100
    Mu

  • Posting with trans.type 300 not possible (No acquisition posted)   Message

    Dear Gurus,
    When I execute the T-code ABUMN, i've got the following message:
    Posting with trans.type 300 not possible (No acquisition posted)
         Message no. AA324
    Diagnosis
         Transaction type 300 belongs to a transaction type group, which can only
         be used to post to assets to which posting has already been performed.
         However, no postings have been made to this asset.
    Procedure
         Use a transaction type from a transaction type group, which can be used
         for the first acquisition to an asset.
    I don't know why I've got this problem. I did those tries:
    Asset Accounting => transaction => inter-company asset transfers => define transfer variants => define transfer variant:
    I don't know which transaction type to use? (Of course, if the problem can be solve here, i juste suppose it ).
    And I tried also to use an other asset (they said that there isn't any acquisition in this asset so I tried with others, that has got acquisitions).
    Thanks for replying,
    With regards,
    Gül'

    Thanks for helping,
    But the problem occures again...
    After transfert variant, I choose the variant 4 'transfert within a company code", then I enter 100 like you said it to me in the 2 cases:
    -  Transaction type in selling company code
    -  Transaction type for receiving company code
    but i've got a new message:
    Transfer variant 4 02 *: Method 1 retmt TTY not allowed
         Message no. AC636
    Diagnosis
         Transfer method 1 is specified for depreciation area *. A retirement
         transaction type must therefore be assigned.
    Procedure
         Assign a retirement transaction type.
    Then I tried others tranfers methods but it doesn't work! And I tried others transaction type too (always the same error message)

  • Posting with transaction type 160 is not possible at MR8M

    MODERATOR:  Do not post (or request) email address or links to copyrighted or confidential information on these forums.  If you do, the thread will be LOCKED and all points UNASSIGNED.  If you have some information, please consider posting it to the [Wiki|https://wiki.sdn.sap.com/wiki/display/ERPFI/Home] rather than sharing via email.  Thank you for your assistance.
    Hi All,
    We raised  a PO w.r.t CWIP asset and posted GRN (MIGO - Transaction typr:100) and Invoice (MIRO).
    Here, Invoice posted wrongly, So we are trying to reverse the invoice with MR8M (which is posted thru MIRO).
    But system populating one message as per the following:
    Posting with transaction type 160 is not possible here, see long text
    Message no. AAPO 177
    Diagnosis:
    Transaction type 160 has a depreciation limitation, although posting is not mandatory in all of the depreciation areas entered However, it is not possible to select depreciation areas in the current transactions.
    Procedure:
    Check the specification of transaction type 160 or use transaction MR8M to enter the transaction
    Please help
    Sairavi
    kumarfi9gmailcom

    Welcome to the forum.
    As a newbie you should understand the forum rules where you are not suppose to post any basic or repeated question.  To avoid this, you should make a search here
    [Forum Search|http://forums.sdn.sap.com/search!default.jspa?objID=f327]
    Type the same error text in Search Terms so that you will find the solution.
    thanks
    G. Lakshmipathi

  • LSMW with IDOC Message type COND_A and Basic type COND_A01

    Hi Sap All.
    in my project we using the LSMW with IDOC Message type COND_A and Basic type COND_A01 and now the requirement is to know the list of the tables which will be updated when i do the LSMW Migration with this IDOC Basic type.
    i have tried to know the list of the tables updated by entering into the transaction we30 and looking at the segments E1KOMG,E1KONH, E1KONP,E1KONM,E1KONW  and i found that the following below are the list of tables which gets updated when i populate the data into IDOC Message type COND_A and Basic type COND_A01.
    KOMG,KONH,KONP,KONM,KONW.
    please correct me if iam wrong.
    regards.
    Varma

    Hi Varma,
    The tables mentioned by you definitely get updated, i guess you can add KONV to the list too, but to be a 100% sure, enable SQL trace and process an IDOC. Then you can look for Insert/Modify/Update statements to get a list of the tables that get updated.
    Regards,
    Chen

  • While  F-92 posting with T type 210 not possible  (No acquisition posted)

    Hi
    Asset Retirement Not Possible
    We have uploded legacy data in our Production server on 01.04.2010.. after that we have to sale one of them asset .
    I am using T.code :- F-92 .. but i couldn't sale that and system gives me error
    Posting with trans.type 210 not possible (No acquisition posted)
    Message no. AA324
    Diagnosis
    Transaction type 210 belongs to a transaction type group, which can only be used to post to assets to which posting has already been performed. However, no postings have been made to this asset.
    Procedure
    Use a transaction type from a transaction type group, which can be used for the first acquisition to an asset.
    Ajay
    yes we are using Group Assets for income tax depreciation
    when checked at AS83 no values found under taken over value for the group asset
    ***. aquistion val  - 0
    and all other values are zero
    Edited by: johnrambo on Oct 4, 2010 12:09 PM
    Moderator: Don't repost threads which were locked by moderator

    Hi
    As I said, go to AS82 and upload the Income tax values for this group asset....
    Unless you do that, system wont allow you to proceed.. May be you can enter a nominal value if it is important to sell the asset now and later on correct it
    Regards
    Ajay M

  • Error : Posting with trans.type 200 not possible (No acquisition posted)

    Dear All,
      Iam getting error while doing asset retirement thru ABAVN. Error is mentioned below. Pls do the needful.
    Posting with trans.type 200 not possible (No acquisition posted)
        Message no. AA324

    Dear Bird,
      Already asset has been posted , but then also it shows the same error.
    pls help on this.
    regards
    Ranjit..

Maybe you are looking for