OBJECTS_OBJREF_NOT_ASSIGNED error in posting run

We are testing prior to upgrading to ERP6.0 and I get the error "You attempted to use a null object reference (points to nothing) access a component (variable: " ").
Program CL_HR_PM_PW_PARCEL============CP
Include   CL_HR_PM_PW_PARCEL============CM009
METHOD get_parcel.
I have checked the notes system and can't find anything. Has anyone come across this before?

Thanks for your reply Afrasyab. It didn't fix the problem as the data had already been converted during upgrade.
The issue appears to be with the variants we were using for testing. We were using variants copied from our 4.7 system and because the screen has changed slightly this was causing the problem. Setting up variants from scratch and running the report again appears to have solved the problem.

Similar Messages

  • Error "Last posting run terminated"

    Hi Experts,
    When I tried to run the depreciation for Nov, I encounter the error "Last posting run terminated.  Restart in period 2009 010",
    But when I tried to restart the depreciation for October, I encounter the error Account 'Expense account for ordinary depreciat.' could not be found for area 01.  When I checked the assets, I can see in AW01N, that it has already posted a depreciation for October.  Why then would it ask for an expense account for period 10 when it has already posted a depreciation last October.
    Thanks to advise.
    Regards,
    Thess

    Dear,
    Just check account assignment in AO90 if G/L for 'Expense account for ordinary depreciat.' has not been changed. And also see the change document for more clarity.
    Regards,
    Chintan Joshi.

  • Error in posting run

    dear gurus
    I am settling the travel expenses in t code PRFI, while creating the posting run i am getting the following error.
        Posting Run 3
                 Non-Postable Trips
                     Personnel No. 99087571 raju surya narayana
                         Trip Number 0000000001
                        No entry in table T030 for argument ET01 HRP 1RR
                        No entry in table T030 for argument ET01 HRT 120
                        No entry in table T030B for argument HRP
                        No entry in table T030B for argument HRT
                        Tax code in procedure TAXUAE is invalid
                        Trip could not be included in posting run
    Can some help me out.
    Regards
    Arjun

    1. Accounting determination is missing in T Code PRT3 for both transactions keys (HRP - Customer/vendor trip costs postings and HRT - Trip costs postings, expense accounts).
    2. Looks like the company code in which you are trying to make postings is in country AE (Utd.Arab.Emir.) which is assigned to tax calculation procedure TAXUAE, and the tax code is not defined.  Define the missing tax code using T Code FTXP in country AE and assign GL account to the tax code.
    Good luck!
    Assign pts. if it helps!!!

  • Error Depreciation Posting Run

    Dear All,
    I have a trouble about depreciation posting run, there is an error message when I tried AFAB.
    Right now, I already  maintain the validation (OKC7) in order to change the error [E] message become warning only [W], so atleast the depreciation could be posted (depreciation can be posted, althought there is still error on it).
    The trouble already occured for 2 periods (Apr-May), and I've just found the error---there was incorrect posting for the asset class.
    Should I use F-92 (asset retire), ABAON, or there is any other solution for this?
    Please advise...
    Thanks & regards,
    Vanda

    hi,
    try transaction  <b>afar</b>
    (read the documentation of tht report RAAFAR00)
    A.

  • Depreciation error - Unplanned posting run allow for future period

    Dear ,
    Need urgent advice for depreciation error happen in our production system.
    FYI, our fiscal year variant 2013 = Feb 2012 - Jan 2013 ( We are now at month-end close for Pr 1 2013 ).And fiscal year close 2012 AJAB and Carry forward ARJW have successfully run for new FY 2013.
    In short, in our asset accounting user was accidentally run unplannned depreciation for future period 12/2013 of one particular asset, while we are now in Pr 1/2013. And, Pr12/2013 is open for asset posting.However, no FI posting posted into the system.
    Just a curiosity as to why system allow user to run unplanned depreciation for future posting without giving an error message to follow the posting cycle.
    The impact/error of above unplanned depreciation run:
    User is not allowed to execute AFAB depreciation run for Pr 1/2013. Even worst, in the AFAB program shows from Pr 1/2013 - 12/2013 is already posted when we do depreciation test run. We can't perform any planned,repeat,restart  for Pr1/2013.
    Because of only one asset had accidentally run for Pr12/2013, all of our asset (96,773 asset) cannot proceed with depreciation run for Pr 1/2013 in the new fiscal year.
    This is high priority as it will impact the entire depreciation run for 12 month of our company.
    Your early reply on this issue is greatly appreciated.
    Thank you,
    Regards,
    Latifah

    Thank you for the response.
    FYI, the asset posting actually has been executed but no document was posted as there's no value.
    I've check the 2 tables below:
    ANLC - No numbers of run for any period in FY2013
    ANLP - No depreciation run was posted in FY13 (all periods).
    Is there anyway for us to do normal planned run for Pr 1/2013? As i understand SAP has no function to perform reversal depreciation run in AFAB. How
    With regard to the posting period 12/2013 that is open for user, I already highlighted this to the respective custodian.
    Thanks.

  • Can't Run AFAB - Posting run requested for future period

    Hi,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    Diagnosis
    There was a check of your entries in the company code and posting period fields for the current system date. The result of this check is that you requested a posting run for company code xxxx for a future fiscal period.
    Please help me, cause I must close the period.
    Thanks

    Hi
    Check Table TABA, whats your last posted period for depreciation
    If you are executing depreciation for last period + 1, then this error is not justified
    If you are doing it for last period + 2, then its justified
    Br, Ajay M

  • Posting run for future period requested (check entry)

    Hi,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    I checked in OB52 postings periods are open for 2009(all periods)
    SAP note 1150235 (all corrections) and 1153718 are completely implemented.
    Still the problem is not resolved.
    Regards,
    Sankar

    Hi Sankar,
    I would like to refer you to the already implemented note 1153718 which states :
    After you implement the changes, the system issues error message AA 697      
    "Posting run for future period requested (check entry)" immediately when     
    you use a fiscal year that is in the future.  In principle, you can          
    customize this message. However, in this case, no settings are taken         
    into account; the system always issues an error message.                     
    Regards Bernhard

  • Posting run for future period requested

    Dear Team,
    While taking depreciation run for company code in AFAB system is generating the error message "Posting run for future period requested (check entry)" SAP error AA697
    please help to reslove the issue.
    Regards,
    MAhendra

    Hi,
    look into the Threads,
    Can't Run AFAB - Posting run requested for future period
    Regards
    Andi

  • Depreciation Run -"Last Posting run terminated Restart in period 03 2010"

    Hello Friends,
    Please help me for this. I am trying to run depreciation for a CoCd 2002 in
    production. When I do AFAB
    for FY 2010 Period 04. It gives a error message "Last Posting run
    terminated, restart in period 2010 003"
    Diagnosis*
    The last posting run in period 003 2010 was terminated by an error.
    Before any more posting runs are performed, you must restart the
    posting run for period 003 2010.
    Procedure
    Start the posting run for period 003 2010 again using the restart
    parameter.
    After this I run AFAB (03 2010) using the Restart radio tab, it runs ok in
    Test and w/o Test (i.e in backgrond),
    when I check SM37 - it shows a program RAPOST2000 is finished. Then I am
    able to run AFAB for (04 2010)
    in test and background also. Again a program is there in SM37.
    But when I try to run for period 05 2010 - it again shows the earlier error
    " "Last Posting run terminated, restart in period 2010 003""
    You see the error message comes again.
    Can someone suggest me a solution. Do I need to go sm35 and process the
    Batch I/P session . Why this error is
    coming up?
    Regards,
    George

    Hi George,
    please look at table-field TABA-XBUKZ.
    If there is a  "1" it means "Restart" necessary.
    If you have the restart sign you have to solve the error and after the restart the TABA-XBUKZ shoudl change to "X".
    regards Bernhard

  • Last posting run terminated (Restart in period 2011 010) _ Depre posting

    Hi
    I am trying post depreciation for the month of October 2011 for an asset.
    I am getting the following error:
    Last posting run terminated (Restart in period 2011 010)
    Message no. AA730
    Diagnosis
    The last posting run in period 010 2011 was terminated by an error. Before any more posting runs are performed, you must restart the posting run for period 010 2011.
    Procedure
    Start the posting run for period 010 2011 again using the restart parameter.
    I checked OB52 and the settings look ok.
    Any idea what might be the reason for the error?
    Thank you in advance
    Regards
    Vedavatee

    i checked in TABA
    and found:
    Client         Co Code    Fiscal year     Posted up to  No. of posting runs FROM Doc.No.     To doc.no.     Document posted
    123     ABCD     2011     008     01          0000000001     0000000001              N
    123     ABCD     2011     009     01          0000000001     0000000001              N
    123     ABCD     2011     009     02          0000000001     0000000001              N
    123     ABCD     2011     009     03          0000000001     0000000001              N
    123     ABCD     2011     010     01          0000000001     0000000001              1

  • ERROR - Status of posting run could not be read - TV

    Hi,
    I've a problem at PR05 transaction. When I select a down payment line I receve the message below:
         Status of posting run 0000054529 could not be read
         Message no. 56820
         Diagnosis
         The trip is assigned to a posting run (significant for transfer to accounting) for which the current accounting status could 
         not be read.
         System Response
         For security reasons, the system does not allow changing or canceling of trips with undefined accounting status.
         Procedure
         Try to repeat the action later or inform your system administrator.
    The FI Document was generated. I believe that something happend to SAP after PRRW generated the FI/CO Documents.
    The question is how can I Create a Travel Expense Report (TRIP) in order to clear the dow payment with this problem happening?
    PS: SAP ECC 6.0
    tks

    Answered my own question. After I thought I had tried everything, it occurred to me to Verify Disk. Doing so revealed a minor bitmap error. So, using my trusty install disk, I booted my machine to the disk and repaired it.
    After the repair, I started iTunes and was able to download my songs. Unfortunately, my original library file was permanently damaged, so I had to start with a clean one. However, if the worst thing to happen to me in all this is that I have to redefine my playlists, then I'm better off.
    I hope this thread helps someone in the future.

  • AFAB - Depreciation Posting Run Error

    When I tried to execute the Depreciation Posting Run, I get the error message "Internal error with background job scheduling RAPOST2000"
    Hv anyone face this problem before? Pls help!
    Thanks.

    Thanks~ I checked with my colleague, he told me that the user is lost few objects in the role. This included the User Authority and the program objects.
    After he added the objects to the user's role. The issue is settle.
    Thanks~!

  • Travel Expense - Posting run error - Error during creation of posting run

    Hi Guru's,
    Look forward for your insights. Here you go with my question.
    We are implementing Expense Mgt with Portal with out scope for payroll in SAP.  I have set up Expense type, WT, Symbolic A/c to G/L Accounts. Im performing Unit testing currently.
    Created Expense trip in ESS, from R/3 tcode PRAP, have approved trip, and settled through Tcode - PREC.
    When I try to create posting run under transfer to accounting, I get following error
    Error during creation of posting run number (->PR1
    Message no. 56840
    I'm not sure why this error was popping up. Appreciate your suggestion.
    Regards
    Praveen.N

    Hi,
    Since you are trying to make payment through FI, you need to maintain ur employee as Vendor. You can do it through PRAA.
    So while creating posting run for this trip, it checks if the respective Vendor for this employee is maintained or not.
    Pls maintain it as vendor and see if the errors are still coming.
    Rakesh

  • Error when run Depreciation Posting Run AFAB

    Hi,
    I found error when run Depreciation Posting Run for period 7 2007.
    FYI. I had run Unplanned Depreciation (TCode: ABAA) with document date 31.10.2007 and posting date 31.10.2007, trans. type 640. After that, i want to run Depreciation Posting Run (TCode: AFAB) with fiscal year: 2008, posting period: 7, reason for posting run: repeat. Select on Test Run. Then i found error message as below. 
    Error Message:
    Documents manually posted within dep.doc.number range
    Message no. AA728
    Diagnosis
    In the number range interval for the document type for posting depreciation, a document  has been posted which was not created within the framework of depreciation posting. The last document posted by depreciation posting was assigned the number .
    Procedure
    Contact your Systems Specialist. When changing the number range interval for the document type in depreciation posting, you have to specify a new interval in which no documents exist. Using organizational measures, you can guarantee that there are no documents apart from those created by depreciation posting in this number range.
    Can any one help how to solve this issue?

    Hi Paul,
    Now I go to TCode: FBN1 - Accounting Document Number Ranges, then i want to change the range for year 2008.
    No Year  From No          To No           Current No          Ext
    03  2001   0300000000   0399999999   -                          /
    03  2002   0300000000   0399999999   -                          /
    03  2003   0300000000   0399999999   -                          /
    03  2004   0300000000   0399999999   -                          /
    03  2005   0300000000   0399999999   -                          /
    03  2006   0300000000   0399999999   -                          /
    03  2007   0300000000   0399999999   -                          /
    03  2008   0300000000   0399999999   -                          /
    03  2009   0300000000   0399999999   -                          /
    Referring back to Asset Accounting, the Reference Document: 19.
    Do it mean that my FI doc. no is 0300000019 ? I bit confuse on this..
    Can you guide me more details on it?
    Thanks in advance.
    Edited by: Nur Aman Abdul Manap on Apr 15, 2009 2:09 AM

  • Error AAPO191 in AFAB: depreciation posting run

    Hi,
    I created a new depreciation area and customized the account determination on AO90. When running the AFAB (dep. posting run) the system issues the error AAPO 191 "Internal error in item 0000000000: asset row is not complete"
    I checked the note 859617 which says the accumulated depreciation account must not be set as fixed asset reconciliation account.
    As far as I know, these accounts have to be set as reconciliation accounts otherwise it will be open for manual postings leading to inconsistencies between FI-AA and FI-GL.
    I checked transaction OAMK and it has some accounts in it (but not the ones with errors). Nevertheless, it has no option to include new accounts.
    Can anyone help me out with this error?
    Thanks in advance,
    Paulo Siqueira

    Hi Paulo,
    this error is nearly always about wrong or missing  account control in your account determination. Please check closely     
    note 7595 and verify if any account has been erroneously defined or  is missing.                                                                               
    As per note  7595:                                                                               
    1. Areas to be posted in dialog   > T093-BUHBKT = 1                                                                               
    The balance sheet accounts and the accumulated depreciation accounts must be characterized as reconciliation accounts of account type   'A'. Down payment account KTANZA must also be a reconciliation                                                                               
    2.  Areas to be posted periodically or areas only relevant to  depreciation  -> T093-BUHBKT = 2                                                                               
    Create the accounts of these areas as ordinary G/L accounts.  They may not be reconciliation accounts.   
    Regards Bernhard

Maybe you are looking for