Error in MIGO posting Assets

Hi  Friends ,
Following error i am geting in MIGO posting for assets....please help
Authorization missing for Company code 1000 Asset class IN4200
Message no. AA048
Diagnosis
Authorization for Company code 1000 with Asset class IN4200 is missing.
System Response
You cannot create, change or post data in this object.
Procedure
If you want to create or change, use an object for which you have authorization. The display transaction will indicate your missing authorization in the initial request screen.
If you need the authorization for this object, contact your Systems Specialist

Hie Balegar.
How did you resolve your error? My client is experiencing the same error AA048 but using t-code SU53 reports missing authorisations which are  maintained, have even went further to re-transport the role to no avail. Can you assist with possible solution.

Similar Messages

  • Account Determination error during MIGO Posting

    Dear All,
    Kindly help resolve error duirng MIGO posting  "ACCOUNT DETERMINATION FOR ENTRY GBB____ZOB TF01 not possible".  This is Message no. M8 147. 
    The error happens once the transaction is being saved.
    Hoping for your positive response.
    Thanks and regards,
    ching

    Hi,
    Goto OBYC Transaction.
    Select the Procedure as ' GBB" and enter the Chart of Accounts ( for Your Company code)
    Enter the Valuation modifier as assigned to others.
    Enter the General modifier as ZOB
    Enter the Valuation class  ( with respect ROH/SFG others)
    Enter the Debit/ Credit G/L account
    save then proceed your transaction MIGO.
    rgds
    Chidanand

  • Run Time error in MIGO Posting

    Dear Friends,
    While Posting MIGO against a import PO system throws run time error for a particular plant. I have created 2 plants for the same company code. But first plant does not have any problem. Pl help me and let me know what may be the cause and its solution. No conditions maintained for the Vendor. After PO directly user creating MIGO.
    Regards,
    Ashok

    Pl find the Run Time error of Exception while posting. Before posting Document was OK while checking.
    Runtime Errors         MESSAGE_TYPE_X
    Date and Time          11.01.2011 10:34:16
    Short text
         The current application triggered a termination with a short dump.
    What happened?
         The current application program detected a situation which really
         should not occur. Therefore, a termination with a short dump was
         triggered on purpose by the key word MESSAGE (type X).
    Error analysis
         Short text of error message:
         Operation QM14 not available for this lot
         Long text of error message:
          Diagnosis
              The desired operation does not fit the inspection lot (object
              type).
          System Response
              The operation is not permitted and can therefore not be carried
              out.
          Procedure
         Technical information about the message:
         Message class....... "QV"
         Number.............. 224
         Variable 1.......... "QM14"
         Variable 2.......... " "
         Variable 3.......... " "
         Variable 4.......... " "
    Trigger Location of Runtime Error
        Program                                 SAPLMBWL
        Include                                 LMBWLU21
        Row                                     62
        Module type                             (FUNCTION)
        Module Name                             MB_POST_GOODS_MOVEMENT
    Source Code Extract
    Line  SourceCde
       32 *    BKPF as well. There is no other way to forward XBLNR to FI as not
       33 *    every document is posted by MB_CREATE -> a new function module in
       34 *    MBWL for transferring the information, called by FI, meant to load
       35 *    the complete function group for all MBxx postings when this isn't
       36 *    required (Performance). Would be the better way to transport the
       37 *    information after switching off MBxx in later release.
       38 *    corresponding IMPORT ... FROM MEMORY ... can be found in
       39 *    AC_DOCUMENT_POST (FORM FI_DOCUMENT_PREPARE (LFACIF5D))
       40      l_mem_id = 'MKPF-XBLNR'.                                   " 641365
       41      EXPORT xblnr = xblnr_sd TO MEMORY ID l_mem_id.             " 641365
       42    ELSE.                                                        "1245374
       43      l_mem_id = 'MKPF-XBLNR'.                                   "1245374
       44      FREE MEMORY ID l_mem_id.                                   "1245374
       45    ENDIF.
       46    IF xmkpf-xabln IS INITIAL.                               "note 434093
       47        CALL FUNCTION 'MB_XAB_NUMBER_GET'.                   "note 434093
       48    ENDIF.                                                   "note 434093
       49
       50 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
    ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
       CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
            EXCEPTIONS
              error_message = 4.
    As soon as we have started to put things into UPDATE TASK, w
    ensure that errors definitely terminate the transaction.
    MESSAGE A is not sufficient because it can be catched from
    external callers which COMMIT WORK afterwards, resulting in
    incomplete updates. Read note 385830 for the full story.
       IF NOT sy-subrc IS INITIAL.
          MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH
                     sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        MESSAGE A263.
       ENDIF.
    Optische Archivierung
    Spaete Erfassung mit Barcode
    Redesign of barcode handling -> note 780365
      PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
                                             xmkpf-mjahr
                                             barcode.
      MOVE-CORRESPONDING xmkpf TO emkpf.
      CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
        EXCEPTIONS
          error_message = 4.
       MOVE-CORRESPONDING xmkpf TO emkpf.
       CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
            EXCEPTIONS
              error_message = 4.
       IF NOT sy-subrc IS INITIAL.
    Regards,
    Ashok

  • Error in MIGO posting against PO with account assignment category K

    Hi folks,
    I have craeted a P.O. Account assignment category K, while creating GR, I am getting following error message
    Account determination for entry SABB (chart of account) Z44 (Tra/event key) TE (act. grouping code) not possible
    Message no. M8147
    What could be the possibel cause.
    I have already did the G.R with same account assignment in the past.
    Regards

    Dear
    The system did not find an account for this transaction. This means that the account determination is not maintained in MM Customizing (Valuation). The key is made up of:
    Chart of account
    Transaction key (= Posting transaction)
    Valuation grouping code
    Account grouping code
    Valuation class
    System Response
    The system cannot update a G/L account for this transaction. You cannot post the transaction.
    Procedure
    Contact your system administrator.
    If you have the authorization, check the Account determination in Customizing forValuation.
    Regards

  • Error in migo posting with respect to sch agreement

    Hi
    I created a purchse requisition and also a sch agreement with respect to it and maintained delivery scheduled.
    PR item qty=10
    sch delivery=2  4   4   i.e.equal to 10
    but when i post GR with respect to this it gives error as follows
    PU Ordered quantity exceeded by 2 KG
    what can be possible reason.
    Thnx

    Hi,
    Please check the SA - Schedule lines & also the Purchase document history to confirm the total order as well as GR quantity.
    Also Please check the Purchase Order unit & Base unit of measure for the material.
    Thanks & Regards,

  • MIGO posting  for asset

    Hi
    During creation of MIGO for asset we got error " YOU CAN NOT POST TO ASSET IN COMPANY CODE BP01 FISCAL YEAR 2011"
    We have copied an existing one asset.Plz tell us the solution.

    Hi,
    Please refer to the following link
    You cannot post to asset in company code 1000,fiscal year 2011
    reverse asset -- You cannot post to this asset (Fiscal year already closed)
    You cannot post to this asset (Fiscal year already closed)
    You cannot post to asset in company code 0001 fiscal year 2009
    error msg: You cannot post to asset in company code xxxx fiscal year 2010
    You cannot post to asset in company code ITML fiscal year 2008
    Also for more clarity pls post in FI/AA or take help from  FI consultant.
    Thanks
    sBk
    Edited by: Sujithbk on Dec 17, 2011 8:12 AM

  • Error AU133 received while posting asset transfer

    Hi Friends,
    While posting asset transfer to affiliated co. (t.code ABT1N) got error message "Account 'Clear.revenue sale to affil.company' could not be found for area 01".
    We have already maintained GL A/c in Ao90 in tab 'Clear.revenue sale to affil.company' .The asset is a AUC asset.
    The GL is also existing in the co  code from which the transfer is made.
    Kindly help to solve the issue..
    Thanks & Regards
    Bhairavi

    Hi Bhairavi,
    1) the note is relevant for your release to check the transfer variants
    2) In fact, when the field in OABE is selected the system uses another posting schema than the standard one (used when the OABE is not set).
    3) Do you one or more depr areas which are derivied from area 01 ans use different accounts? For example:
    AFAPL  AFABER XSTORE ABVOR1 AFABE1 ABVOR2 AFABE2 VZANSW VZREST BUHBKT  
    ABCD   03            +      01     -      02     *      *      4       
    ABCD   05            +      01     -      04     *      *      4       
    Regars Bernhard

  • FA Retirement- 21151: error while posting asset document: '100000039'

    Hello Experts,
    I have a client who encountered this error during fixed asset retirement - scrapping.
    After selecting the asset to be retired, sap did not assign an account in the account column, but the user
    was able to save the document.  After saving it, the user needs to retire again another asset - scrapping, but the document would not be saved because of this error: 21151: error while posting asset document '100000039'.  The document number the systems is referring to is the last document saved but sap did not assign an account code.
    Please help. My client is using sap b1 8.81 patch5.
    Regards,
    Luz

    Hi Too Mui Hwee,
    What we did is to put letters on the number so the series will continue example there is already 100333, 100334, 100335 since the error is encountered from 100333. We add 100333A, 100334A, 100335A.
    Thanks

  • Error while posting asset in PY-ABZON

    Hi Expert,
    Im trying to post asset acquisition through T-code-ABZON and am facing the error that For the K4 Fiscal year Variant, no period is defined for XX period
    I've checked my fiscal year variant Its not K4 have checked the Posting period Variant its open for the said period,but still this error.
    Please help me with it
    Regards

    Check your configuration
    IMG->FA->AA->Valuation->Fiscal Year->Fiscal Year Vairants....
    Specify Other versions on company code level
    Specify Other versions on depreciation area level

  • Error while posting asset acquisition

    hai
    while posting asset acquisition in f-90 iam getting error that "asset is incomplete' when analysed using RAUNVA00 , it is asking to update field group-22 i.e scrap value, but this field is not found in asset master, pls help me.
    thank u
    shivaji.a

    In AS02 you go the Depreciation key and double click on the depreciation key. In the following screen "additional Specifications" you give Scrap value.

  • Error posting asset to company ''Specify payment period baseline date''

    Hi All,
    Please some can advise on the below error msg.
    While posting the asset in to company I will get error like ''Specify payment period baseline date'' and i cant go further.
    Please advise ASAP.
    Many Thanks
    Balaji A S

    Dear:
                   This error message normally appears if In the payment terms that you are using (can be seen in OBB8) there is no any default date assigned to the payment term. If it is then assign one like Posting Date or Document Date in OBB8 against the payment term you using. I am a bot confused in your case that why are you getting this error while acquiring the asset. Would you please elaborate the process you are using for asset acquisition.
    Regards

  • Posting period error in MIGO

    Hi Friends,
    I am getting the same error while doing posting a GR for PO as
    " Posting only possible in periods 1998/06 and 1998/05 in dev server. I checked in OB52 for opening periods. It starts from 1st month of 1998 to 12 2010. The fiscal year variant for CO Code is V3. I gave posting date as 15.6.1998 but still the same error comes.
    PL help to resolve this.
    Regards.
    Ram

    Hi,
    Use MMPV..
    Enter your company code-09
    Enter period you wanna open--1998
    Enter year--
    Press inside execute button
    System will show you message that the period is nt current period jus after taht press main execute button..
    Go on opening till you reach the current one...
    Can check the open periods in OMSY
    Regards,
    Priyanka.P
    AWARD IF HELPFULL
    Edited by: Priyanka Paltanwale on Aug 7, 2008 2:18 PM

  • Error during GR for asset PO

    while doing GR for asset PO system is giving error message of "Acct123 for trans/ev  key ANL, is not a control account
    some one plz explain me the reason for this error and how to resolve.

    Hi,
    You are posting asset through MIGO so GL acocunt being debited for asset has to be Asset Reconciliation Account.
    Use ME23N and check GL account for Account assginemnt category A whether GL is control one.
    Or you can also check in AO90 that the GL assgined to account determination for particular asset class for depreciation areas is reconciliation one or not.
    Check whether u had maintianed GL account for ANL transaction event key in OBYC t.code
    Regards,
    KK

  • Error in MIGO while doing Intracompnay plant to depot by STO

    Dear gurus,
    I am facing an error while posting MIGO during intra-company plant to plant STO.
    Settings for STO:
    SPRO >IMG > MM >Purchasing > Purchase Order>set up Stock Transport Order
    Define Shipping Data
    Define/assign Checking rule
    Assign Delivery Type
    Assign Doc type
    I have maintained the following pre-requisite master data
    1. Supplying/Receiving plants are created as customer/vendor master
    2. Excise details (customer/Vendor/Plant) data are maintained in J1ID
    3. Assessable value is entered in J1ID
    Process flow:
    1. ME21n - Create STO (PO type:UB)
    2. VL10B - Create Outbound Delivery
    3. VL02N - PGI
    4. VF01 - Create Pro-forma Invoice (Stock Transfer Invoice)
    5. J1IIN - Post Excise Invoice
    at the receiving Plant
    6. MIGO-Post Goods Receipt.
    After entering the excise invoice and clicking on CHECK button in MIGO, the following errors are appearing
    1. Excise Details are not maintained for Vendor .-Message no. 8I565
    2. Maintain Vendor for the excise invoice -Message no. 4F185
    3. Please check excise base for the item is zero ! -Message no. 4F121
    Please reply your valuable suggestions.
    Regards,
    Anbu

    Dear,
    1. Excise Details are not maintained for Vendor .-Message no. 8I565
       Kindly maintain Excise Indicator for Vendor in TCODE-J1ID
    2. Maintain Vendor for the excise invoice -Message no. 4F185
         Kindly maintain Excise Indicator for VENDOR in  J1ID
    3. Please check excise base for the item is zero ! -Message no. 4F121
         As excise in calculated on Base amount for Item so need to maintain Pricing for item then only it will be able to calculate
      or if u dont want to item not  to be relevent for pricing then make Excise condition type as manual an maintain it manually .
    Regards
    AJIT K SINGH
    HAPPY TO HELP U

  • Error in MIGO durng intra-company stock transfer by STO

    Dear gurus,
    I am facing an error while posting MIGO during intra-company plant to plant STO.
    Settings for STO:
    SPRO >IMG > MM >Purchasing > Purchase Order>set up Stock Transport Order
    Define Shipping Data
    Define/assign Checking rule
    Assign Delivery Type
    Assign Doc type
    I have maintained the following pre-requisite master data
    1. Supplying/Receiving plants are created as customer/vendor master
    2. Excise details (customer/Vendor/Plant) data are maintained in J1ID
    3. Assessable value is entered in J1ID
    Process flow:
    1. ME21n - Create STO (PO type:UB)
    2. VL10B - Create Outbound Delivery
    3. VL02N - PGI
    4. VF01 - Create Pro-forma Invoice (Stock Transfer Invoice)
    5. J1IIN - Post Excise Invoice
    at the receiving Plant
    6. MIGO-Post Goods Receipt.
    After entering the excise invoice and clicking on CHECK buttin in MIGO, the following errors are appearing
    1. Excise Details are not maintained for Vendor .-Message no. 8I565
    2. Maintain Vendor for the excise invoice -Message no. 4F185
    3. Please check excise base for the item is zero ! -Message no. 4F121
    Please reply your valuable suggestions.
    Regards,
    Anbu

    Hi Anbu..
    Post Migo without excise entry and try in J1IG to post the excise invoice.
    In J1iG..enter material doc of GR ,Excise invoice no from Manufac plant,check own plant and
    Click Details to get the excise values as in excise invoice.
    Hope this works !!
    Thanks
    R.Kannan,

Maybe you are looking for