No log Display - AFAB - Repeat Run - Test mode

Hi mates,
I am unable to view any log while executing the AFAB for repeat run option.  however, if I run in background, the system provides a spool containing the assets with values.
Could someone please let me know the reason?
Regards,
Surya

Symptom
You want to reverse a depreciation posting run.
Additional key words
Depreciation posting, RABUCH00, depreciation posting run, reverse depreciation posting, reversal
Cause and prerequisites
In most cases, you might wish to reverse the depreciation posting run for one of the following reasons:
Incorrect depreciation terms
Solution
Reversing a depreciation posting run is not possible for safety and consistency reasons.Instead of carrying out a reversal, proceed as follows:
Process completely the batch input session  (which is incorrect from your point of view) from the depreciation posting run.
Correct the incorrect fixed assets (for example, set the correct depreciation keys in the fixed assets)
If you change the definition of depreciation keys in Customizing, start program RAAFAR00 for recalculating the depreciation on the fixed assets.
Restart the depreciation posting run for the same period, this time using the option "Repeated run". For this option, a batch input session is generated that posts only the differences which result compared to the preceding regular run.
Process the batch input session generated here.
For the introduction phase you find a program "Reset posted depreciation" in the IMG. You must never use this program in a production system.If you use this program in a test system, note that this program resets the posted depreciations only from the point of view of Asset Accounting.Documents posted into Financial Accounting or into cost accounting are not reversed automatically.
Courtesy: SAP Note 82499

Similar Messages

  • AFAB - Repeat Run & Restart Run

    Hello Sap Experts
    Can anyone kindly explain the situation we need to use "Repeat Run" & "Restart Run" available in AFAB.
    Kindly expain.
    Thanks & Regards
    Deepak Garg

    Hi Deepak,
    Repeat run is used to post the depreiciation for assets in a period, for which the planned depreciation has been posted.
    Ex: You have run the dep for 01-2010, then in the same period you might have added some more assets and need to be posted depreciation for the same period again. In this case repeat run would be useful.
    Note: this repeat run can be done for the last posted period only.
    Restart option is to continue the depreciation posting run from a last dep run, which is stopped due to some errors casused at the system level.
    Thanks,
    Srinu

  • AJAB-Error AFAB-Not allowing repeat run

    Dear Friends
    User executed AFAB in 12-2008 and since period was still open, asset retirement was posted in period 12-2008. As a result of this, the asset net book value is open by the amount of depreciation which was posted for the period 12-2008. We tried all options such as- Recalculate depreciation from asset master data, activated asset again, opened period 12-2008 and trying to run AFAB -Repeat run for period 12- 2008 in test mode for such retired assets only and system does not show any asset values in AFAB and no error log is also created. What could be the reason for this? AJAB gives an error due to these retired asset as planned depreciation -dep which was posted for 12- 2008 is shown in AS03 also as planned depreciation to be reversed for such assets is not completely posted. Tried posting with AFAB in period 13 and planned posting run also, but nothing happens with AFAB. I have following questions
    What could be reason for these assets not being depreciated by repeat run of AFAB.
    What is the solution for resolving the error -Planned depreciation not completely posted- in AJAB
    If AJAB is not run, can we still post depreciation for period 1- 2009
    Thanks and regards

    Hi Kylie and AP,
    Many thanks for the quick response. I reversed the retirement document and it corrects the situation and now no error in AJAB. But if I still run AFAB in test mode for repeating the run, I don't get any values for the asset. This is because, depreciation was already posted in period 12, 2008 and now there is nothing to post for depreciation. I am not sure if we can do repeat run of AFAB in 12,2008 and retire the asset again in period 12, 2008.
    Just to clarify the following part: Did you mean to do this in 2008? Pl. clarify how do I do the following? This is because AFAB is not going to post anything for repeat run in 2008 as I described below and if we repeat retirement in 2008, then the same error will appear in AJAB.
    You'll need to reverse the retirements and then run the depreciation program in repeat mode.
    You should be able to then retire the assets, and perform year-end close.
    Thanks and regards.

  • AFAB program strange performance in TEST mode

    Hi colleagues,
    We are experiencing a strange performance in AFAB program.
    We have uploaded several assets in a particular company code. When executing AFAB transaction in TEST mode, the new assets are not considered, whereas, when performing a REAL execution yes they are.
    We think that when reconciliating assets at the end of the year, this issue which is not harmful (but strange indeed) may be solved, but we are not sure at all.
    Can anybody provide a clue on what is happening.
    Thanks and my best regards

    Hi When you run this report online in test it will only show +/- the first 1.000 assets and the new asset are later in the data base and you don't see them.
    You have to run it in test mode in back ground and look in the spool to the result (default the spool shows arround 20 page's but this you can change or go to the next 20 pages)

  • WDA - Application in Test Mode is displayed in Disabled mode

    Hi,
    I have developed a component in SE80 and created an Application. Now if I run the same component in Test mode, It is displaying the page and elements(Ex: Input Fields & Buttons) in Non-Editable mode.  Is there any setting for the same. Please help me in this case.
    Thanks.
    Sekhar.J

    In version 10.7.4 the screen background of the fullscreen is the same login background. I like. I used the Loginox 1.0.6b5.

  • Run in test mode call transaction

    I have written a bdc program using call transaction method. I am giving the option in the
    selection screen like run in test mode.so i want to display the error mess
    without actually updating the tables,
    if there is a way to do this
    please tell me how to run in test mode.
    thank you so much for all the replies.

    have written a bdc program using call transaction method. I am giving the option in the
    selection screen like run in test mode.so i want to display the error mess
    without actually updating the tables,
    if there is a way to do this
    please tell me how to run in test mode.
    thank you so much for all the replies.
    Hi
    it is not possible, once u run call tranation the data is updated in table.
    for ur requirement, put the option in test mode in selection screen, in this mode flat file data check with master data (flat file validations
    ) , if any errors it disaly errors in a report.
    i provide some code, this is for fb60 check this code
          FORM validate                                                 *
    FORM validate.
      delete t_record index 1.
      loop at t_record.
        delete t_record where accnt = ' '.
        translate t_record-bukrs to upper case.
        translate t_record-accnt to upper case.
        translate t_record-waers to upper case.
        translate t_record-xblnr to upper case.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  INPUT  = t_record-accnt
             IMPORTING
                  OUTPUT = t_record-accnt.
        move-corresponding t_record to n_record.
        append n_record.
        clear n_record.
      endloop.
      loop at t_record.
        clear flag.
        delete t_record where accnt = ' '.
    vendor  and company code checking.
        translate t_record-accnt to upper case.
        translate t_record-bukrs to upper case.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  INPUT  = t_record-accnt
             IMPORTING
                  OUTPUT = t_record-accnt.
        select single * from lfb1 where bukrs = t_record-bukrs
                                      and  lifnr = t_record-accnt.
        if sy-subrc <> 0.
          flag = 'X'.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
          error_record-text1 = 'The Vendor not Under this company Code'.
        endif.
    With holding liability.
        select single * from lfbw where bukrs = t_record-bukrs
                                        and  lifnr = t_record-accnt
                                      and  WT_SUBJCT = 'X'.
        if sy-subrc <> 0.
          flag = 'X'.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
    error_record-text2 = 'The Vendor doesnt have Withholding Tax Liability'.
        endif.
    G/L account check with company code*
        select single * from skb1 where bukrs = t_record-bukrs
                                      and saknr = t_record-hkont.
        if sy-subrc <> 0.
          flag = 'X'.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
        error_record-text3 = 'The G/L acc not under the given company code'.
        endif.
    *cost centre checking
    this FM for leading zeros
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  INPUT  = t_record-kostl
             IMPORTING
                  OUTPUT = v_kostl.
    select single kostl from csks into v_kostl where bukrs = t_record-bukrs
                                             and kostl = v_kostl.
        if sy-subrc <> 0.
          flag = 'X'.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
    error_record-text4 = 'The costcentre not under the given company code'.
        endif.
    it check the invioce alredy posted or not.
        translate t_record-waers to upper case.
        translate t_record-xblnr to upper case.
    select single belnr into v_belnr1 from bsip where bukrs = t_record-bukrs
                                              and   lifnr  = t_record-accnt
                                              and   waers  = t_record-waers
                                                  and   bldat  = p_invdat
                                              and   xblnr  = t_record-xblnr.
        if sy-subrc = 0.
          day   =  p_invdat+6(2).
          month =  p_invdat+4(2).
          year  =  p_invdat+0(4).
          concatenate day month year into date1 SEPARATED BY '.'.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
    concatenate 'This document under number' v_belnr1 'already posted on '
          date1 into fld2  separated by space.
          error_record-text5 = fld2.
          flag = 'X'.
        endif.
    *zero balance
        on change of t_record-accnt or t_record-xblnr.
          amount = 0.
          totalamount = 0.
          amount = t_record-wrbtr1.
          loop at n_record where bukrs = t_record-bukrs
                               and  accnt = t_record-accnt
                               and xblnr = t_record-xblnr
                               and wrbtr1 = t_record-wrbtr1
                               and waers = t_record-waers.
            totalamount = totalamount  + n_record-wrbtr2.
          endloop.
        endon.
        if amount ne totalamount.
          error_record-rowno = sy-tabix + 1.
          move-corresponding t_record to error_record.
          error_record-text6 = 'Posting only possible with zero balance'.
          flag = 'X'.
        endif.
        if flag = 'X'.
          error_record-flag = 'X'.
          append error_record.
        endif.
        if flag <> 'X'.
          move-corresponding t_record to f_record.
          append f_record.
        endif.
        clear f_record.
        clear error_record.
      endloop.
    endform.
    *&  Form  Table Control
    FORM head_item .
      clear t_record.
      LOOP AT t_record.
        delete t_record where accnt = ' '.
        translate t_record-bukrs to upper case.
        translate t_record-accnt to upper case.
        translate t_record-waers to upper case.
        translate t_record-xblnr to upper case.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
             EXPORTING
                  INPUT  = t_record-accnt
             IMPORTING
                  OUTPUT = t_record-accnt.
        on change of t_record-accnt or t_record-xblnr or t_record-wrbtr1.
          MOVE-CORRESPONDING t_record TO t_head.
          APPEND t_head.
        endon.
        MOVE-CORRESPONDING t_record TO t_item.
        APPEND t_item.
        clear : t_item,t_head.
      ENDLOOP.
    ENDFORM.
    form disperrortestrun.
      loop at error_record.
        format color 2 intensified on.
        set left scroll-boundary column 70.
        write :   /'|',
                 (6) error_record-rowno,         '|' no-gap,
                 (14) error_record-bukrs,        '|' no-gap,
                 (12) error_record-accnt,        '|' no-gap,
                 (16) error_record-xblnr,        '|' no-gap,
                 (16) error_record-wrbtr1,       '|' no-gap,
                 (8)  error_record-waers,        '|' no-gap,
                 (13) error_record-secco,        '|' no-gap,
                 (20) error_record-sgtxt,        '|' no-gap,
                 (14) error_record-hkont,        '|' no-gap,
                 (15) error_record-wrbtr2,       '|' no-gap,
                 (10) error_record-mwskz,        '|' no-gap,
                 (20) error_record-gsber,        '|' no-gap,
                 (12) error_record-kostl,        '|' no-gap,
                 (5)  error_record-flag,         '|' no-gap,
                 (50) error_record-text1,        '|' no-gap,
                 (53) error_record-text2,        '|' no-gap,
                 (50) error_record-text3,        '|' no-gap,
                 (50) error_record-text4,        '|' no-gap,
                 (67) error_record-text5,        '|' no-gap,
                 (45) error_record-text6,        '|'  .
      endloop.
      uline at /1(538).
      format color off.
    endform.
    Report Header for Test Run                                          *
    form header.
      set left scroll-boundary column 70.
      format color 5 .
      write: 'REPORT :', sy-repid,
    38 'ERROR RECORDS DETAILS OF TEST RUN OF FB60(VENDOR INVIOCE POSTING)'
      ,123 'DATE :', sy-datum .
      format color off.
      skip 3.
      format color 1 intensified on.
      uline at 1(538).
      write : /'|',
              (6) 'Row No',                             '|' no-gap,
             (14) 'Company Code',                       '|' no-gap,
             (12) 'Vendor No',                          '|' no-gap,
             (16) 'Reference',                          '|' no-gap,
             (16) 'Invioce Amount',                     '|' no-gap,
             (8) 'Currency',                            '|' no-gap,
             (13) 'Section Code',                       '|' no-gap,
             (20) 'text',                               '|' no-gap,
             (14) 'G/L Account',                        '|' no-gap,
             (15) 'Item Amount',                        '|' no-gap,
             (10) 'Tax Code',                           '|' no-gap,
             (20) 'Business Area',                      '|' no-gap,
             (12) 'Cost Centre',                        '|' no-gap,
             (5)  'Error record Status',                '|' no-gap,
             (50) 'Company Code/Vendor',                '|' no-gap,
             (53) 'Vendor/With holding tax Liability',  '|' no-gap,
             (50) 'Company Code/ G/L Account',          '|' no-gap,
             (50) 'Company Code / Cost Centre',         '|' no-gap,
             (67) 'Invioce Status',                     '|' no-gap,
             (45) 'Invalid Balance',
            '|'.
      uline at /1(538).
      format color off.
    endform.
    thanks
    sitaram.

  • MD01- MRP run in test mode.......

    Hi Expets,
    My client wants to see the Material and quantity going to be generated by MRP run, so how can I run the MD01 in test mode, in order to view which materials are planned and with what quantity PR is going to be generated before MRP run, Same like in the single level planning MD03 with "Display results before they are saved ".
    Regards,
    Sri.....

    Hi Afshad Irani ,
    My question was is there any way to see the test results in PRD only like in MD03 T-Code.Every time we can not copy the PRD to Quality.
    Regards,
    Sri.......

  • Running a file in test mode

    hi iam doing a bdc recording in which there is an option to runthe file in test mode i.e if that button is checked then only will the validations will be done and the program should stop executingand save the succesful records at the end of it and should not post even if it doesnot contain ny error.and for the validations display a log file containing the no. of records and details.
    some of the validations are like komg-hland and country of origin of article komg-herkl has to be checked from T005 TABLE.
    The rate unit(currency or percentage)konp-konwa has to be checked from TCURC TABLE.THE CONDITION UNIT KONP-KMEIN HAS TO BE CHECKED FROM T006 TABLE.

    Hi Sushant,
    Just add a Check box in your program and check it by default.
    Perform all the validations expect inserting to the table if the chk param is checked. else insert the value.
    parameter : ip_tstrn as checkbox default 'X'.
      if ip_tstrn ne 'X'.
        perform create_data.
      endif.
    Guess i hav answerd ur q.Is this you have asked ?
    Rgds,
    Jothi.P
    *let me know the outcome.

  • Erroneous GP successfully run in test mode.

    Hi,
    We have some GP's which are in erroneous status. The same erroneous GP's gets processed when re-run in the test mode.
    1)Could you please let us know the steps to re-run GP's  in the test mode
    2)Is this something related to framework
    Rgrds,
    Saket

    Hello Saket,
    If a GP process instance goes into error, it is not poissible to rerun it. You must initiate the process again. Please see the following Knowledge Based Article on this:
    #1649701 Guided Procedures Erroneous Process Instances
    Thanks and best regards,
    Carl Connolly
    Senior Support Consultant - Netweaver Web Application Server
    AGS Primary Support, Global Support Centre Ireland
    Guided Procedures trouble shooting guide:
    https://
    www.sdn.sap.com/irj/scn/wiki?path=/display/jstsg/%2528gp%2529home

  • Repeat run depreciation in AFAB

    Important and urgent
    The issue is related to depreciation, I have changed the depreciation key in the asset class and depreciation was posted this resulted in very high value of depreciation for the period. As standard SAP I understand that  when we change the depreciation key in asset class this will recalculate the depreciation values.
    What I now done is I have put back the depreciation key again and run AFAR (Depreciation planned run) and trying to do repeat run using AFAB for posted values in the period.
    But the posted values are not making any change, when I done the same in Quality this took affect. Any suggestions please...
    Thanks
    Srinath

    Hi Srinath,
    if you change the depreciation key in the asset class (OAYZ) it has definitely no effect on already created assets.
    This could only has an impact on assets that you create up to now.
    Please check (in AS02) which depreciation key you have on the asset itself.
    If this is the wrong key, please change it and make a recalculation of values.
    regards Bernhard

  • Run in test mode the transaction FB01, FB08 and FBR2

    HI,
    I would like to know if its possible to run the transaction fb01,fb08 and fbr2 in test mode.
    thanks

    Hi,
    You can run in simulation mode which is nothing but the test mode in finance. Every posting can be seen in simulation mode before posting the document.
    Regards,
    Sreekanth

  • Run BAPI_MATERIAL_SAVEDATA in Test Mode

    Hi ABAPers,
    I am trying to run BAPI_MATERIAL_SAVEDATA. When I run, the details are being changed without using 'COMMIT WORK'.
    However, if I use ROLLBACK WORK before the end of the program, the database table does not get updated.
    Is there any other way I can run BAPI_MATERIAL_SAVEDATA in test mode without updating the Database table?
    Help is highly appreciated.
    Thanks!

    Do not call bapi commit function module in test moode, instead call bapi rollback FM, after u call the material save data bapi
    *(or)     *
    I understand that you are using the BAPI, but if you were to use LSMW direct input program instead, you would be able to run in TST mode, and make sure that all of the errors are taken care of before you actually update the system.
    *******************Reward points,if found useful

  • Field test mode signal display

    Hi all,
    Back in March I posted that I was having garbled and dropped calls. I still have them but my cell extender has helped some. I'm still waiting on the femtocell for a final fix in this area...
    Anyway a person here suggested that I make the field test call, tap on the bars to change it to the dBm display then quit using a soft reset to leave it in that mode.
    Did that and monitored signal in lots of places. I'd like to go back to the bars because in general, even though I understand dBm a picture is easier to quickly digest.
    So I did field test mode, tapped to get bars then quit again using soft reset. It seems though to go back to bars then at some point it switches back over to dBm again... A soft reset will take it back to bars but then at some point dBm will appear again...
    How do I get back to bar display permanently?

    I am sorry but, we do no have the steps to enable the Field Test Mode on your Iphone, which relates to the technical details and signal strength on the mobile phone and network. 
    To ensure you have the best signal on your phone and in your area, you may benefit from a free update of your wireless phone's roaming software once a month. As Verizon Wireless continues to expand our network, it is important to update your software to receive optimal coverage when traveling.
    To update your phone, please follow the simple instructions below while on the Verizon Wireless network and receiving a digital signal:
    1. Power on your Verizon Wireless phone.
    2. Dial *228 followed by the "Send" key.
    3. When prompted, press option "2" to update your roaming capabilities.
    Within two minutes, a voice recording will advise you that programming is complete. Remain on the line, as the call will disconnect automatically. I recommend you perform this update monthly or before leaving for a trip, as this will give you the ability to pick up newly acquired service areas while roaming.
    If you experience any difficulty with the free software upgrade, please call us at 800-922-0204 from a landline phone, and have your wireless phone charged and available when calling. 
    KinquanaH_VZW

  • Repeated Nvidia error on Vaio Z1 laptop: "Display driver NVIDIA Windows Kernel Mode Driver, Version 188.80 stopped responding and successfully recovered." Any thoughts?

    I keep having my screen go black and then Win 7 pro gives me this error:
    "Display driver NVIDIA Windows Kernel Mode Driver, Version 188.80 stopped responding and successfully recovered."
    everything is fine after that.
    happens 3 or 4 times a day.
    '''doesn't '''seem to be on graphics or flash heavy sites.
    driver is up to date and tried reloading driver.

    I keep having my screen go black and then Win 7 pro gives me this error:
    "Display driver NVIDIA Windows Kernel Mode Driver, Version 188.80 stopped responding and successfully recovered."
    everything is fine after that.
    happens 3 or 4 times a day.
    '''doesn't '''seem to be on graphics or flash heavy sites.
    driver is up to date and tried reloading driver.

  • Validation before running test script?

    Hello Gurus,
    I am getting started to learn eCATT and with different posts availabe I was sucessfully able to create and execute simple scripts. Thanks for posting all this and I am now able to create all four objects in eCATT. A special thanks to Sapna Modi for her step wise information.
    However, I have certain conditions to check before running test script. Like I want to check a table entry and if the entry exists then the test script should be executed. I tried with ABAP  ...ENDABAP and TCD recording.  I wasnt able to do it.
    Could anyone of you please let me know how we can accomplish this? Also when the entry isnt there in the table the test script should fail and appropriate message should be displayed in the log.
    Also, please let me know if we can use TCD and SAPGUI commands within ABAP ENDABAP commands.
    Your help is highly appreciated...
    Regards,
    GS...

    Hi,
    For your negative testing,if your entry is not listed in the table.Eventually CHETAB command wil fail and you see a Red log.
    For not executing the script,if your check fails.Please add some condition..
    In CHETAB/GETTAB table commands,Say you passed a value and it is found in the table.Then the return value for the CHETAB/GETTAB would be zero.If it is failed it return Non-zero values.This values can be captured by using the command &SUBRC.
    So please apply a condition for your next script to execute..
    If &SUBRC = 0
    give the script name
    else
    log(condition failed)
    endif.
    just add this code in between your code..and place the script you wanna execute after your check is successful.
    Hope it answers your doubts.
    Regards,
    Venky

Maybe you are looking for