MM month end periods error..?

Dear all
Can anybody expalin me how to clear this error message,
"Posting only possible in periods 2008/03 and 2008/02 in company code LML"
Thanks
sap-mm

Hi,
Hope New Period ( July month,04) not open in FI side
Check in T.code: MMRV and see which period is open for ur Co.Code LML and back posting is allowed or not.In MMPV close the period last period ( may be 03) and automatically system open the new one.
Now use t.code: OB52(FI side) and open the 04, 2008 period in Account Types A, K, D,M, S and specially Account Type u201C+u201D which stands for valid for all accounts type and save. Better consult FICO consultant for OB52 step.
Regards,
Biju K

Similar Messages

Posting Run Month end accruals error

Hi Guys,
after running the payroll driver on test mode for period 26 2009...when I look at the log file...I get an error that the employee has been rejected...and the maximum number of search runs exceeded under Month end accruals...
looking fwd to your comments and suggestions

Hello Shiloh S,
The error message "Maximum number of search runs exceeded" occurs in
function UACGF, which is for the Month End Accruals calculations.
Below, I've updated information which explains the Month End Accruals
process, calculations and required table entries:
1. Tables T549S and T51A1:
The T549S table needs 3 dates specified for each pay id. Those 3
dates and their respective Date IDs are:
01 = pay date
04 = posting run
05 = ACC: Earliest Doc. creation date
To check if these entries have been made, please go to sm31 and view
if the entries have been made for the year for example: 2002
(you should also check consistency of future entries as well!)
You can create the entries via the IMG paths specified below for the
respective Date IDs (if you have not already done so).
NOTE: The tables are only changed if a flag has been set for the field
'Carry out table change'. If no flag is set, a test run is performed.
01 = pay date
    IMG -> Payroll US -> Basic Settings -> Payroll Organization
        -> Generate Payroll Period
           You can view the documenation on this step by doubleclicking
           the title of the step. (NOTE: first change your Text Display
           by going to 'Utilities - Text Display - SAPscript)
           For further explanation - click 'Report Documentation'
04 = posting run
    IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation -> Maintain Posting Date
         -Create      ('Info' icon provides explanation of how to run.)
05 = ACC: Earliest Doc. creation date
    IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation -> Set latest earliest document creation
         date
For T51A1 - Final date for HR Postings (Accruals):
This date determines the final date on which postings may be effected
from HR for each posting period. I would advise you to set this up
for each company code and each accounting period of 2001. For more
info, please select F1 in the fields that you are unsure of.
You can maintain these dates via the path:
   IMG -> Payroll US -> Month end accruals -> Triggering Month End
        Accrual computation ->
2. Explanation of Month End Accruals:
First of all there is a switch to say in general if accruals are to be
computed for an employee or not. This switch is called ACCMO and
is set to 'ON' (1) in rule UAC0. Unfortuately this rule is deactivated
in your development system so that accruals are not calculated.
If this switch is set to 'ON', the system first tries to find out if it
has to calculate accruals and for which periods this is to be done.
If you have a payroll period which overlaps two posting periods, you
will have accruals for this period.
Generally the system can calculate accruals according to exact/current
values and or the system can estimate the accruals. The system always
tries to be as exact as possible which means it always tries to use
current values.
So: How does the system decide if for one period current values can be
taken or if an estimation has to be done?
If you need to post accruals for a payroll period because it overlaps
two posting periods, you have to post to both posting periods. So you
have to make sure, that you are still able to post to both posting
periods when the posting for the payroll period is done. This means the
system has to check that the LDCD (Latest earliest document creation
date) of the payroll period is earlier than the closing date of both
posting periods concerned. Often one posting period is already closed
which means that it is no longer possible to post accruals to this
posting period when the overlapping payroll period is calculated. This
means the system has to estimate values for this overlapping payroll
period before. In other words, the system calculates accruals for a
payroll period in the last payroll period with a LDCD which is is
earlier than the closing date of the overlapped posting periods.
Thus during payroll, the system checks for the current and for the
following payroll periods if things have already been done (because now
it is too late), if things have to be done now (because when the next
payroll period is calculated it will be too late) or if it will be
possible to post accruals after the next payroll period.
Hoping the above information are helpful.
Kind regards,
Graziela

Error with month end payroll Accruals

We have an error when posting month end payroll accruals for our weekly payroll, though the bi-weekly payroll works fine!
I have checked tables T549S and T51A1 and all of the dates are correct and set as I would expect, however the system did not create a month end accrual for the weekly payroll into the following months posting period. For the biweekly payroll this worked exactly as expected.
We had no issues with this for the last calendar year, however for 2009 we have changed our month end closing dates, though I do not see that this would prevent this from happening. I have checked various things in the IMG and have not been able to resolve this, does anyone have any ideas what might be causing this.
HELP!!!

Michelle :
Month-end accrual determination is based on T51A1, T549S (date type '04' and '05'), and T549Q (field Begda and Endda). Pay extra attention on these dates, as if one is incorrect (e.g. miss-type the year in the future entry with an earlier year) would definitely cause month-end accrual to stop working.
Rgds.

Strange Oracle Behaviour - only month end or high load periods

Hi SAP Gurus
In one of our systems I am expreriencing a strange behaviour from Oracle, in that it seems to be in reconnect, but yet it is not, it resets and carries on but do produce Dump and SM21 log messages, the dump is not really helpfull as it is the same dump but with different program everytime.
I have looked in oracle alert log and found no event tying back to the SM21 log message or dump.
The following is what I found in the developer trace of one of these insident, but there are many, about 125 - 200 for the day during high load:
Fri Nov 28 10:05:55 2008
C *** ERROR => Failed to register application info: orc=3113
[dboci.c      3042]
C *** ERROR => Error 3114 in stmt_fetch()
[dbsloci.c    13001]
C *** ERROR => ORA-3114 occurred when executing SQL statement (parse error offset=0)
[dbsloci.c    13002]
C sc_p=045B18B4,no=29,idc_p=00000000,con=0,act=1,slen=1291,smax=1536,#vars=4,stmt=34DA78C8,table=CATSDB
C SELECT "MANDT" , "COUNTER" , "PERNR" , "WORKDATE" , "SKOSTL" , "LSTAR" , "SEBELN" , "SEBELP" , "SPRZ\
C NR" , "LSTNR" , "RKOSTL" , "RPROJ" , "RAUFNR" , "RNPLNR" , "RAUFPL" , "RAPLZL" , "RKDAUF" , "RKDPOS"\
C   , "RKSTR" , "RPRZNR" , "PAOBJNR" , "FUND" , "FUNC_AREA" , "GRANT_NBR" , "S_FUND" , "S_FUNC_AREA" , \
C "S_GRANT_NBR" , "AWART" , "LGART" , "KAPID" , "SPLIT" , "REINR" , "WABLNR" , "VERSL" , "WTART" , "BW\
C GRL" , "WAERS" , "AUFKZ" , "TRFGR" , "TRFST" , "PRAKN" , "PRAKZ" , "OTYPE" , "PLANS" , "KOKRS" , "ME\
C INH" , "TCURR" , "PRICE" , "ARBID" , "WERKS" , "AUTYP" , "HRCOSTASG" , "HRKOSTL" , "HRLSTAR" , "HRFU\
C ND" , "HRFUNC_AREA" , "HRGRANT_NBR" , "BEMOT" , "UNIT" , "STATKEYFIG" , "TASKTYPE" , "TASKLEVEL" , "\
C TASKCOMPONENT" , "BUKRS" , "ERSDA" , "ERSTM" , "ERNAM" , "LAEDA" , "LAETM" , "AENAM" , "APNAM" , "AP\
C DAT" , "WORKITEMID" , "LOGSYS" , "STATUS" , "REFCOUNTER" , "REASON" , "BELNR" , "EXTSYSTEM" , "EXTAP\
C PLICATION" , "EXTDOCUMENTNO" , "TASKCOUNTER" , "CATSHOURS" , "BEGUZ" , "ENDUZ" , "VTKEN" , "ALLDF" ,\
C   "OFMNW" , "PEDD" , "AUERU" , "LTXA1" , "LONGTEXT" , "ERUZU" , "CATSAMOUNT" , "CATSQUANTITY" , "ZCAT\
C SPLAN" , "ROUTE" , "KUNNR" , "MVGR1" , "GSBER" , "SNAME" , "MAKTX" , "ZAVGHRS" , "ZQANT" , "ZPERNR" \
C FROM "CATSDB" WHERE "MANDT" = :A0 AND "WORKDATE" = :A1 AND "WERKS" = :A2 AND "STATUS" < :A3;
C sc_p=045B18B4,no=29,idc_p=00000000,con=0,act=1,slen=1291,smax=1536,#vars=4,stmt=34DA78C8,table=CATSDB
C prep=0,lit=0,nsql=0,lobret=0,#exec=1,dbcnt=0,upsh_p=00000000,ocistmth_p=345E20EC
C IN : cols=4,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=-1,rsize=17,vmax=32,bound=1,iobuf_p=045DFFA8,vda_p=3470A8D8
C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
C OUT: cols=105,rmax=58,xcnt=58,rpc=1,rowi=0,rtot=1,upto=-1,rsize=895,vmax=128,bound=1,iobuf_p=0E0A4EC8,vda_p=34F8F7E8
C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
C SELECT "MANDT" , "COUNTER" , "PERNR" , "WORKDATE" , "SKOSTL" , "LSTAR" , "SEBELN" , "SEBELP" , "SPRZ\
C NR" , "LSTNR" , "RKOSTL" , "RPROJ" , "RAUFNR" , "RNPLNR" , "RAUFPL" , "RAPLZL" , "RKDAUF" , "RKDPOS"\
C   , "RKSTR" , "RPRZNR" , "PAOBJNR" , "FUND" , "FUNC_AREA" , "GRANT_NBR" , "S_FUND" , "S_FUNC_AREA" , \
C "S_GRANT_NBR" , "AWART" , "LGART" , "KAPID" , "SPLIT" , "REINR" , "WABLNR" , "VERSL" , "WTART" , "BW\
C GRL" , "WAERS" , "AUFKZ" , "TRFGR" , "TRFST" , "PRAKN" , "PRAKZ" , "OTYPE" , "PLANS" , "KOKRS" , "ME\
C INH" , "TCURR" , "PRICE" , "ARBID" , "WERKS" , "AUTYP" , "HRCOSTASG" , "HRKOSTL" , "HRLSTAR" , "HRFU\
C ND" , "HRFUNC_AREA" , "HRGRANT_NBR" , "BEMOT" , "UNIT" , "STATKEYFIG" , "TASKTYPE" , "TASKLEVEL" , "\
C TASKCOMPONENT" , "BUKRS" , "ERSDA" , "ERSTM" , "ERNAM" , "LAEDA" , "LAETM" , "AENAM" , "APNAM" , "AP\
C DAT" , "WORKITEMID" , "LOGSYS" , "STATUS" , "REFCOUNTER" , "REASON" , "BELNR" , "EXTSYSTEM" , "EXTAP\
C PLICATION" , "EXTDOCUMENTNO" , "TASKCOUNTER" , "CATSHOURS" , "BEGUZ" , "ENDUZ" , "VTKEN" , "ALLDF" ,\
C   "OFMNW" , "PEDD" , "AUERU" , "LTXA1" , "LONGTEXT" , "ERUZU" , "CATSAMOUNT" , "CATSQUANTITY" , "ZCAT\
C SPLAN" , "ROUTE" , "KUNNR" , "MVGR1" , "GSBER" , "SNAME" , "MAKTX" , "ZAVGHRS" , "ZQANT" , "ZPERNR" \
C FROM "CATSDB" WHERE "MANDT" = :A0 AND "WORKDATE" = :A1 AND "WERKS" = :A2 AND "STATUS" < :A3;
B ***LOG BYM=> severe DB error 3114      ; work process in reconnect status [dbsh#3 @ 1123] [dbsh    1123 ]
B ***LOG BY4=> sql error 3114   performing FET on table CATSDB     [dbtran#10 @ 7292] [dbtran 7292 ]
B ***LOG BY0=> ORA-03114: not connected to ORACLE [dbtran#10 @ 7292] [dbtran 7292 ]
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'FET'
B   RSLT: {dbsl=99, tran=1}
B   FHDR: {tab='CATSDB', fcode=225, mode=2, bpb=0, dbcnt=0, crsr=1,
B          hold=0, keep=1, xfer=0, pkg=0, upto=0, init:b=0,
B          init:p=00000000, init:#=871, wa:p=0XA000DC88, wa:#=871}
B dbtran ERROR LOG (hdl_dbsl_error): DbSl 'FET'
B   STMT:
B   CRSR: {tab='CATSDB', id=1, hold=0, prop=0x1000, max.in@0=1, fae:blk=1,
B          con:id=0, con:vndr=5, val=2,
B          key:#=4, xfer=0, xin:#=0, row:#=0, upto=0, wa:p=0XA000DC88}
C *** ERROR => Error 3114 in stmt_fetch()
[dbsloci.c    13001]
C *** ERROR => ORA-3114 occurred when executing SQL statement (parse error offset=0)
[dbsloci.c    13002]
C sc_p=045B52E4,no=225,idc_p=045C400C,con=0,act=1,slen=184,smax=2048,#vars=3,stmt=35BBB778,table=REPOLOAD
C SELECT "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJO\
C R_VERS" FROM "REPOLOAD" WHERE "PROGNAME" = :A0 AND "R3STATE" = :A1 AND "MACH" = :A2 ;
C sc_p=045B52E4,no=225,idc_p=045C400C,con=0,act=1,slen=184,smax=2048,#vars=3,stmt=35BBB778,table=REPOLOAD
C prep=0,lit=0,nsql=0,lobret=0,#exec=29,dbcnt=0,upsh_p=00000000,ocistmth_p=34B9ADD4
C IN : cols=3,rmax=1,xcnt=0,rpc=0,rowi=0,rtot=0,upto=-1,rsize=45,vmax=32,bound=1,iobuf_p=0E0A4EC8,vda_p=31361B18
C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
C OUT: cols=9,rmax=1,xcnt=1,rpc=1,rowi=0,rtot=1,upto=-1,rsize=56,vmax=32,bound=1,iobuf_p=045DFFA8,vda_p=345C39B8
C       lobs=0,lmax=0,lpcnt=0,larr=00000000,lcurr_p=00000000,rret=0
C SELECT "UNAM" , "UDAT" , "UTIME" , "L_DATALG" , "Q_DATALG" , "SDAT" , "STIME" , "MINOR_VERS" , "MAJO\
C R_VERS" FROM "REPOLOAD" WHERE "PROGNAME" = :A0 AND "R3STATE" = :A1 AND "MACH" = :A2 ;
B ***LOG BYM=> severe DB error 3114      ; work process in reconnect status [dbsh#3 @ 1123] [dbsh    1123 ]
B ***LOG BY4=> sql error 3114   performing SEL on table REPOLOAD   [dbrepo#6 @ 2657] [dbrepo 2657 ]
B ***LOG BY0=> ORA-03114: not connected to ORACLE [dbrepo#6 @ 2657] [dbrepo 2657 ]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_VMIT_CLEANUP entered.
A ** RABAX: level LEV_RX_VMIT_CLEANUP completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
C *** ERROR => OCI-call 'OCITransRollback' failed: rc = 3114
[dboci.c      3127]
B ***LOG BYM=> severe DB error 3114      ; work process in reconnect status [dbsh#3 @ 1123] [dbsh    1123 ]
B Reconnect state is entered by connection:
B 0: name = R/3, con_id = 000000000 state = ACTIVE      , perm = YES, reco = YES, timeout = 000, con_max = 255, con_opt = 255, occ = NO
B hdl_error_on_commit_rollback: DB-ROLLBACK detected RECONNECT state
M ThShortCommit: db unusable
B db_con_reconnect disconnecting connection:
B 0: name = R/3, con_id = 000000000 state = INACTIVE    , perm = YES, reco = YES, timeout = 000, con_max = 255, con_opt = 255, occ = NO
C Disconnecting from connection 0 ...
C Close user session (con_hdl=0,svchp=045D7FA4,usrhp=345E67A0)
C Detaching from DB Server (con_hdl=0,svchp=045D7FA4,srvhp=045D0174)
C Now I'm disconnected from ORACLE
B db_con_reconnect performing the reconnect for con:
B 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = YES, timeout = 000, con_max = 255, con_opt = 255, occ = NO
C got NLS_LANG='AMERICAN_AMERICA.US7ASCII' from environment
C Client NLS settings:
C Logon as OPS$-user to get SAPR3's password
C Connecting as /@PRD on connection 0 (nls_hdl 0) ... (dbsl 640 250407)
C Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
C    0 US7ASCII                                                  1   045CBB38   0E0A4648   0E0A40B0
C Attaching to DB Server PRD (con_hdl=0,svchp=045
SM51 log entries:
     09:00:32     MS                         Q0I     Operating system call recv failed (error no. 10054)
     09:00:32     DP                         Q0K     Connection to message server (on FCMSPROD) established
     09:00:32     DIA     004     040     181JOLENES     VA02     BYM     SQL error 3114 . Work processes in reconnect status
     09:00:32     DP                         Q1C     MsgServer Hardware ID Was Determined
     09:00:32     DIA     001     040     181ANNELINEJ     VA42     BYY     Work process has left reconnect status
     09:00:32     DIA     001     040     181ANNELINEJ     VA42     AB0     Run-time error "DBIF_REPO_SQL_ERROR" occurred
     09:00:32     DIA     014     040     161ADRIV     VA02     BYY     Work process has left reconnect status
     09:00:32     DIA     013     040     140ELECIA          BYY     Work process has left reconnect status
     09:00:32     DIA     003     040     133MIRANDAV     KO88     BYY     Work process has left reconnect status
     09:00:32     DIA     003     040     133MIRANDAV     KO88     AB0     Run-time error "DBIF_REPO_SQL_ERROR" occurred
     09:00:32     DIA     001     040     181ANNELINEJ     VA42     AB1     > Short dump "081128 090032 FCMSPROD 181ANNELINEJ" generated
     09:00:32     DIA     003     040     133MIRANDAV     KO88     AB1     > Short dump "081128 090032 FCMSPROD 133MIRANDAV " generated
     09:00:32     DIA     009     040     120ELIZEP     FB01     BYY     Work process has left reconnect status
     09:00:33     DIA     009     040     120ELIZEP     FB01     AB0     Run-time error "DBIF_REPO_SQL_ERROR" occurred
     09:00:33     DIA     004     040     181JOLENES     VA02     BYY     Work process has left reconnect status
     09:00:33     DIA     002     040     133KOEKIEJ          BYY     Work process has left reconnect status
     09:00:33     DIA     002     040     133KOEKIEJ          AB0     Run-time error "DBIF_REPO_SQL_ERROR" occurred
     09:00:33     DIA     004     040     181JOLENES     VA02     AB0     Run-time error "DBIF_REPO_SQL_ERROR" occurred
     09:00:33     DIA     009     040     120ELIZEP     FB01     AB1     > Short dump "081128 090033 FCMSPROD 120ELIZEP " generated
     09:00:33     DIA     005     040     181CLIVEB     VA02     BYY     Work process has left reconnect status
     09:00:33     DIA     003                    R0Z     The update dispatch info was reset
     09:00:33     DIA     003                    R0Z     The update dispatch info was reset
Please can you assist in maybe you have seen this before.
Regards
Pieter

Hi
Yes I have gone through the Oracle Alert log several time, It is huge, but I am pasting an extract for the entire day this was happening into this reply. Oracle version is 9.2.0.8.0 with the only intrim path I can see being installed : 6130293.
Following is the extract from Alert Log for the day this occurred, again I must stress that this happens only on high system load days like month end:
Fri Nov 28 03:43:33 2008
ALTER TABLESPACE "PSAPBTABI" END BACKUP
Fri Nov 28 03:43:33 2008
Completed: ALTER TABLESPACE "PSAPBTABI" END BACKUP
Fri Nov 28 03:43:37 2008
ALTER TABLESPACE "PSAPCLUD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPCLUD" BEGIN BACKUP
Fri Nov 28 03:53:38 2008
ALTER TABLESPACE "PSAPCLUD" END BACKUP
Fri Nov 28 03:53:38 2008
Completed: ALTER TABLESPACE "PSAPCLUD" END BACKUP
Fri Nov 28 03:53:42 2008
ALTER TABLESPACE "PSAPCLUI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPCLUI" BEGIN BACKUP
Fri Nov 28 03:54:36 2008
ALTER TABLESPACE "PSAPCLUI" END BACKUP
Fri Nov 28 03:54:36 2008
Completed: ALTER TABLESPACE "PSAPCLUI" END BACKUP
Fri Nov 28 03:54:38 2008
ALTER TABLESPACE "PSAPDDICD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPDDICD" BEGIN BACKUP
Fri Nov 28 03:55:47 2008
ALTER TABLESPACE "PSAPDDICD" END BACKUP
Fri Nov 28 03:55:47 2008
Completed: ALTER TABLESPACE "PSAPDDICD" END BACKUP
Fri Nov 28 03:55:50 2008
ALTER TABLESPACE "PSAPDDICI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPDDICI" BEGIN BACKUP
Fri Nov 28 03:56:41 2008
ALTER TABLESPACE "PSAPDDICI" END BACKUP
Fri Nov 28 03:56:41 2008
Completed: ALTER TABLESPACE "PSAPDDICI" END BACKUP
Fri Nov 28 03:56:45 2008
ALTER TABLESPACE "PSAPDOCUD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPDOCUD" BEGIN BACKUP
Fri Nov 28 03:56:49 2008
ALTER TABLESPACE "PSAPDOCUD" END BACKUP
Completed: ALTER TABLESPACE "PSAPDOCUD" END BACKUP
Fri Nov 28 03:56:52 2008
ALTER TABLESPACE "PSAPDOCUI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPDOCUI" BEGIN BACKUP
Fri Nov 28 03:56:55 2008
ALTER TABLESPACE "PSAPDOCUI" END BACKUP
Completed: ALTER TABLESPACE "PSAPDOCUI" END BACKUP
Fri Nov 28 03:56:59 2008
ALTER TABLESPACE "PSAPEL640D" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPEL640D" BEGIN BACKUP
Fri Nov 28 04:03:46 2008
ALTER TABLESPACE "PSAPEL640D" END BACKUP
Fri Nov 28 04:03:46 2008
Completed: ALTER TABLESPACE "PSAPEL640D" END BACKUP
Fri Nov 28 04:03:50 2008
ALTER TABLESPACE "PSAPEL640I" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPEL640I" BEGIN BACKUP
Fri Nov 28 04:04:37 2008
ALTER TABLESPACE "PSAPEL640I" END BACKUP
Fri Nov 28 04:04:37 2008
Completed: ALTER TABLESPACE "PSAPEL640I" END BACKUP
Fri Nov 28 04:04:40 2008
ALTER TABLESPACE "PSAPES640D" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPES640D" BEGIN BACKUP
Fri Nov 28 04:20:17 2008
ALTER TABLESPACE "PSAPES640D" END BACKUP
Fri Nov 28 04:20:17 2008
Completed: ALTER TABLESPACE "PSAPES640D" END BACKUP
Fri Nov 28 04:20:20 2008
ALTER TABLESPACE "PSAPES640I" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPES640I" BEGIN BACKUP
Fri Nov 28 04:36:26 2008
ALTER TABLESPACE "PSAPES640I" END BACKUP
Fri Nov 28 04:36:26 2008
Completed: ALTER TABLESPACE "PSAPES640I" END BACKUP
Fri Nov 28 04:36:29 2008
ALTER TABLESPACE "PSAPLOADD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPLOADD" BEGIN BACKUP
Fri Nov 28 04:36:40 2008
ALTER TABLESPACE "PSAPLOADD" END BACKUP
Fri Nov 28 04:36:40 2008
Completed: ALTER TABLESPACE "PSAPLOADD" END BACKUP
Fri Nov 28 04:36:43 2008
ALTER TABLESPACE "PSAPLOADI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPLOADI" BEGIN BACKUP
Fri Nov 28 04:36:53 2008
ALTER TABLESPACE "PSAPLOADI" END BACKUP
Completed: ALTER TABLESPACE "PSAPLOADI" END BACKUP
Fri Nov 28 04:36:56 2008
ALTER TABLESPACE "PSAPPOOLD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPPOOLD" BEGIN BACKUP
Fri Nov 28 04:41:04 2008
ALTER TABLESPACE "PSAPPOOLD" END BACKUP
Fri Nov 28 04:41:04 2008
Completed: ALTER TABLESPACE "PSAPPOOLD" END BACKUP
Fri Nov 28 04:41:08 2008
ALTER TABLESPACE "PSAPPOOLI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPPOOLI" BEGIN BACKUP
Fri Nov 28 04:45:17 2008
ALTER TABLESPACE "PSAPPOOLI" END BACKUP
Fri Nov 28 04:45:17 2008
Completed: ALTER TABLESPACE "PSAPPOOLI" END BACKUP
Fri Nov 28 04:45:21 2008
ALTER TABLESPACE "PSAPPROTD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPPROTD" BEGIN BACKUP
Fri Nov 28 04:47:25 2008
ALTER TABLESPACE "PSAPPROTD" END BACKUP
Fri Nov 28 04:47:25 2008
Completed: ALTER TABLESPACE "PSAPPROTD" END BACKUP
Fri Nov 28 04:47:29 2008
ALTER TABLESPACE "PSAPPROTI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPPROTI" BEGIN BACKUP
Fri Nov 28 04:48:09 2008
ALTER TABLESPACE "PSAPPROTI" END BACKUP
Fri Nov 28 04:48:09 2008
Completed: ALTER TABLESPACE "PSAPPROTI" END BACKUP
Fri Nov 28 04:48:13 2008
ALTER TABLESPACE "PSAPSOURCED" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPSOURCED" BEGIN BACKUP
Fri Nov 28 04:48:46 2008
ALTER TABLESPACE "PSAPSOURCED" END BACKUP
Fri Nov 28 04:48:46 2008
Completed: ALTER TABLESPACE "PSAPSOURCED" END BACKUP
Fri Nov 28 04:48:49 2008
ALTER TABLESPACE "PSAPSOURCEI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPSOURCEI" BEGIN BACKUP
Fri Nov 28 04:49:29 2008
ALTER TABLESPACE "PSAPSOURCEI" END BACKUP
Fri Nov 28 04:49:29 2008
Completed: ALTER TABLESPACE "PSAPSOURCEI" END BACKUP
Fri Nov 28 04:49:34 2008
ALTER TABLESPACE "PSAPSTABD" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPSTABD" BEGIN BACKUP
Fri Nov 28 05:05:16 2008
ALTER TABLESPACE "PSAPSTABD" END BACKUP
Fri Nov 28 05:05:16 2008
Completed: ALTER TABLESPACE "PSAPSTABD" END BACKUP
Fri Nov 28 05:05:23 2008
ALTER TABLESPACE "PSAPSTABI" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPSTABI" BEGIN BACKUP
Fri Nov 28 05:21:15 2008
ALTER TABLESPACE "PSAPSTABI" END BACKUP
Fri Nov 28 05:21:15 2008
Completed: ALTER TABLESPACE "PSAPSTABI" END BACKUP
Fri Nov 28 05:21:19 2008
ALTER TABLESPACE "PSAPUSER1D" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPUSER1D" BEGIN BACKUP
Fri Nov 28 05:21:42 2008
ALTER TABLESPACE "PSAPUSER1D" END BACKUP
Fri Nov 28 05:21:42 2008
Completed: ALTER TABLESPACE "PSAPUSER1D" END BACKUP
Fri Nov 28 05:21:46 2008
ALTER TABLESPACE "PSAPUSER1I" BEGIN BACKUP
Completed: ALTER TABLESPACE "PSAPUSER1I" BEGIN BACKUP
Fri Nov 28 05:23:03 2008
ALTER TABLESPACE "PSAPUSER1I" END BACKUP
Fri Nov 28 05:23:03 2008
Completed: ALTER TABLESPACE "PSAPUSER1I" END BACKUP
Fri Nov 28 05:23:06 2008
ALTER TABLESPACE "SYSTEM" BEGIN BACKUP
Completed: ALTER TABLESPACE "SYSTEM" BEGIN BACKUP
Fri Nov 28 05:24:03 2008
ALTER TABLESPACE "SYSTEM" END BACKUP
Fri Nov 28 05:24:03 2008
Completed: ALTER TABLESPACE "SYSTEM" END BACKUP
Fri Nov 28 05:24:07 2008
ALTER TABLESPACE "UNDOTBS1" BEGIN BACKUP
Completed: ALTER TABLESPACE "UNDOTBS1" BEGIN BACKUP
Fri Nov 28 05:42:06 2008
ALTER TABLESPACE "UNDOTBS1" END BACKUP
Fri Nov 28 05:42:06 2008
Completed: ALTER TABLESPACE "UNDOTBS1" END BACKUP
Fri Nov 28 05:42:07 2008
ALTER DATABASE BACKUP CONTROLFILE TO 'C:\Program Files\CA\BrightStor ARCserve Backup Enterprise Option for SAP R3 for Oracle\CONTROL.PRD' REUSE
Completed: ALTER DATABASE BACKUP CONTROLFILE TO 'C:\Program F
Fri Nov 28 05:42:14 2008
Beginning log switch checkpoint up to RBA [0x77f2.2.10], SCN: 0x0000.3c0ae436
Thread 1 advanced to log sequence 30706
Current log# 2 seq# 30706 mem# 0: C:\ORACLE\PRD\ORIGLOGB\LOGPRD02_M1.ORA
Current log# 2 seq# 30706 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOGPRD02_M2.ORA
Fri Nov 28 05:42:14 2008
ARC0: Evaluating archive   log 3 thread 1 sequence 30705
ARC0: Beginning to archive log 3 thread 1 sequence 30705
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30705.001'
Fri Nov 28 05:42:27 2008
ARC1: Evaluating archive   log 3 thread 1 sequence 30705
ARC1: Unable to archive log 3 thread 1 sequence 30705
      Log actively being archived by another process
Fri Nov 28 05:42:29 2008
ARC0: Completed archiving log 3 thread 1 sequence 30705
Fri Nov 28 06:11:26 2008
Completed checkpoint up to RBA [0x77f2.2.10], SCN: 0x0000.3c0ae436
Fri Nov 28 09:20:59 2008
Beginning log switch checkpoint up to RBA [0x77f3.2.10], SCN: 0x0000.3c0b739c
Thread 1 advanced to log sequence 30707
Current log# 1 seq# 30707 mem# 0: C:\ORACLE\PRD\ORIGLOGA\LOGPRD01_M1.ORA
Current log# 1 seq# 30707 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOGPRD01_M2.ORA
Fri Nov 28 09:20:59 2008
ARC0: Evaluating archive   log 2 thread 1 sequence 30706
ARC0: Beginning to archive log 2 thread 1 sequence 30706
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30706.001'
Fri Nov 28 09:21:18 2008
ARC0: Completed archiving log 2 thread 1 sequence 30706
Fri Nov 28 09:51:06 2008
Completed checkpoint up to RBA [0x77f3.2.10], SCN: 0x0000.3c0b739c
Fri Nov 28 10:44:43 2008
Beginning log switch checkpoint up to RBA [0x77f4.2.10], SCN: 0x0000.3c0bb876
Thread 1 advanced to log sequence 30708
Current log# 4 seq# 30708 mem# 0: C:\ORACLE\PRD\ORIGLOGB\LOGPRD04_M1.ORA
Current log# 4 seq# 30708 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOGPRD04_M2.ORA
Fri Nov 28 10:44:43 2008
ARC0: Evaluating archive   log 1 thread 1 sequence 30707
ARC0: Beginning to archive log 1 thread 1 sequence 30707
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30707.001'
Fri Nov 28 10:45:07 2008
ARC1: Evaluating archive   log 1 thread 1 sequence 30707
ARC1: Unable to archive log 1 thread 1 sequence 30707
      Log actively being archived by another process
Fri Nov 28 10:45:09 2008
ARC0: Completed archiving log 1 thread 1 sequence 30707
Fri Nov 28 11:13:20 2008
Completed checkpoint up to RBA [0x77f4.2.10], SCN: 0x0000.3c0bb876
Fri Nov 28 11:45:09 2008
Beginning log switch checkpoint up to RBA [0x77f5.2.10], SCN: 0x0000.3c0bfc29
Thread 1 advanced to log sequence 30709
Current log# 3 seq# 30709 mem# 0: C:\ORACLE\PRD\ORIGLOGA\LOGPRD03_M1.ORA
Current log# 3 seq# 30709 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOGPRD03_M2.ORA
Fri Nov 28 11:45:09 2008
ARC0: Evaluating archive   log 4 thread 1 sequence 30708
ARC0: Beginning to archive log 4 thread 1 sequence 30708
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30708.001'
Fri Nov 28 11:45:13 2008
ARC1: Evaluating archive   log 4 thread 1 sequence 30708
ARC1: Unable to archive log 4 thread 1 sequence 30708
      Log actively being archived by another process
Fri Nov 28 11:45:29 2008
ARC0: Completed archiving log 4 thread 1 sequence 30708
Fri Nov 28 12:15:17 2008
Completed checkpoint up to RBA [0x77f5.2.10], SCN: 0x0000.3c0bfc29
Fri Nov 28 12:50:23 2008
Beginning log switch checkpoint up to RBA [0x77f6.2.10], SCN: 0x0000.3c0c3298
Thread 1 advanced to log sequence 30710
Current log# 2 seq# 30710 mem# 0: C:\ORACLE\PRD\ORIGLOGB\LOGPRD02_M1.ORA
Current log# 2 seq# 30710 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOGPRD02_M2.ORA
Fri Nov 28 12:50:24 2008
ARC0: Evaluating archive   log 3 thread 1 sequence 30709
ARC0: Beginning to archive log 3 thread 1 sequence 30709
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30709.001'
Fri Nov 28 12:50:40 2008
ARC0: Completed archiving log 3 thread 1 sequence 30709
Fri Nov 28 13:20:29 2008
Completed checkpoint up to RBA [0x77f6.2.10], SCN: 0x0000.3c0c3298
Fri Nov 28 14:27:01 2008
Beginning log switch checkpoint up to RBA [0x77f7.2.10], SCN: 0x0000.3c0c75c1
Thread 1 advanced to log sequence 30711
Current log# 1 seq# 30711 mem# 0: C:\ORACLE\PRD\ORIGLOGA\LOGPRD01_M1.ORA
Current log# 1 seq# 30711 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOGPRD01_M2.ORA
Fri Nov 28 14:27:01 2008
ARC0: Evaluating archive   log 2 thread 1 sequence 30710
ARC0: Beginning to archive log 2 thread 1 sequence 30710
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30710.001'
Fri Nov 28 14:27:25 2008
ARC0: Completed archiving log 2 thread 1 sequence 30710
Fri Nov 28 14:57:08 2008
Completed checkpoint up to RBA [0x77f7.2.10], SCN: 0x0000.3c0c75c1
Fri Nov 28 15:57:26 2008
Beginning log switch checkpoint up to RBA [0x77f8.2.10], SCN: 0x0000.3c0cb34a
Thread 1 advanced to log sequence 30712
Current log# 4 seq# 30712 mem# 0: C:\ORACLE\PRD\ORIGLOGB\LOGPRD04_M1.ORA
Current log# 4 seq# 30712 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOGPRD04_M2.ORA
Fri Nov 28 15:57:26 2008
ARC0: Evaluating archive   log 1 thread 1 sequence 30711
ARC0: Beginning to archive log 1 thread 1 sequence 30711
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30711.001'
Fri Nov 28 15:57:40 2008
ARC1: Evaluating archive   log 1 thread 1 sequence 30711
ARC1: Unable to archive log 1 thread 1 sequence 30711
      Log actively being archived by another process
Fri Nov 28 15:57:40 2008
ARC0: Completed archiving log 1 thread 1 sequence 30711
Fri Nov 28 16:27:31 2008
Completed checkpoint up to RBA [0x77f8.2.10], SCN: 0x0000.3c0cb34a
Fri Nov 28 17:02:12 2008
Beginning log switch checkpoint up to RBA [0x77f9.2.10], SCN: 0x0000.3c0cc245
Thread 1 advanced to log sequence 30713
Current log# 3 seq# 30713 mem# 0: C:\ORACLE\PRD\ORIGLOGA\LOGPRD03_M1.ORA
Current log# 3 seq# 30713 mem# 1: F:\ORACLE\PRD\MIRRLOGA\LOGPRD03_M2.ORA
Fri Nov 28 17:02:12 2008
ARC0: Evaluating archive   log 4 thread 1 sequence 30712
ARC0: Beginning to archive log 4 thread 1 sequence 30712
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30712.001'
Fri Nov 28 17:02:25 2008
ARC0: Completed archiving log 4 thread 1 sequence 30712
Fri Nov 28 17:32:17 2008
Completed checkpoint up to RBA [0x77f9.2.10], SCN: 0x0000.3c0cc245
Fri Nov 28 18:00:19 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPBTABD" COALESCE
Fri Nov 28 18:00:19 2008
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPBTABD" COALE
Fri Nov 28 18:00:19 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPBTABI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPBTABI" COALE
Fri Nov 28 18:00:19 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPCLUD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPCLUD" COALES
Fri Nov 28 18:00:20 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPCLUI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPCLUI" COALES
Fri Nov 28 18:00:21 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDDICD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDDICD" COALE
Fri Nov 28 18:00:23 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDDICI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDDICI" COALE
Fri Nov 28 18:00:23 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUD" COALE
Fri Nov 28 18:00:23 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUI" COALE
Fri Nov 28 18:00:24 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPEL640D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPEL640D" COAL
Fri Nov 28 18:00:26 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPEL640I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPEL640I" COAL
Fri Nov 28 18:00:27 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPES640D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPES640D" COAL
Fri Nov 28 18:00:27 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPES640I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPES640I" COAL
Fri Nov 28 18:00:27 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPLOADD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPLOADD" COALE
Fri Nov 28 18:00:27 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPLOADI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPLOADI" COALE
Fri Nov 28 18:00:27 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLD" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLI" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPROTD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPROTD" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPROTI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPROTI" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCED" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCED" COA
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCEI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCEI" COA
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSTABD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSTABD" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSTABI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSTABI" COALE
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1D" COAL
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1I" COAL
Fri Nov 28 18:00:28 2008
/* BRCONNECT */ ALTER TABLESPACE "SYSTEM" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "SYSTEM" COALESCE
Fri Nov 28 20:00:17 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPBTABD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPBTABD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPBTABI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPBTABI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPCLUD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPCLUD" COALES
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPCLUI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPCLUI" COALES
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDDICD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDDICD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDDICI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDDICI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPDOCUI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPEL640D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPEL640D" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPEL640I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPEL640I" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPES640D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPES640D" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPES640I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPES640I" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPLOADD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPLOADD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPLOADI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPLOADI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPOOLI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPROTD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPROTD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPPROTI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPPROTI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCED" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCED" COA
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCEI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSOURCEI" COA
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSTABD" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSTABD" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPSTABI" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPSTABI" COALE
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1D" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1D" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1I" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "PSAPUSER1I" COAL
Fri Nov 28 20:00:18 2008
/* BRCONNECT */ ALTER TABLESPACE "SYSTEM" COALESCE
Completed: /* BRCONNECT */ ALTER TABLESPACE "SYSTEM" COALESCE
Fri Nov 28 20:00:36 2008
Beginning log switch checkpoint up to RBA [0x77fa.2.10], SCN: 0x0000.3c0cf8e3
Thread 1 advanced to log sequence 30714
Current log# 2 seq# 30714 mem# 0: C:\ORACLE\PRD\ORIGLOGB\LOGPRD02_M1.ORA
Current log# 2 seq# 30714 mem# 1: F:\ORACLE\PRD\MIRRLOGB\LOGPRD02_M2.ORA
Fri Nov 28 20:00:36 2008
ARC0: Evaluating archive   log 3 thread 1 sequence 30713
ARC0: Beginning to archive log 3 thread 1 sequence 30713
Creating archive destination LOG_ARCHIVE_DEST_1: 'F:\ORACLE\PRD\SAPARCH\ARC30713.001'
Fri Nov 28 20:00:44 2008
ARC1: Evaluating archive   log 3 thread 1 sequence 30713
ARC1: Unable to archive log 3 thread 1 sequence 30713
      Log actively being archived by another process
Fri Nov 28 20:00:47 2008
ARC0: Completed archiving log 3 thread 1 sequence 30713
Dump file f:\oracle\prd\saptrace\background\alert_prd.log
Mon Dec 01 09:03:16 2008
ORACLE V9.2.0.8.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Mon Dec 01 09:03:16 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.8.0.
System parameters with non-default values:
processes                = 120
sessions                 = 150
timed_statistics         = TRUE
shared_pool_size         = 822083584
large_pool_size          = 8388608
java_pool_size           = 8388608
enqueue_resources        = 8000
filesystemio_options     = SETALL
control_files            = C:\oracle\PRD\origlogA\ctrlPRD.ctl, F:\oracle\PRD\saparch\ctrlPRD.ctl, E:\oracle\PRD\sapdata1\ctrlPRD.ctl
db_block_checksum        = FALSE
db_block_size            = 8192
db_cache_size            = 1073741824
compatible               = 9.2.0
log_archive_start        = TRUE
log_archive_dest         = F:\oracle\PRD\saparch
log_buffer               = 4194304
log_checkpoint_interval = 0
db_files                 = 254
db_file_multiblock_read_count= 8
log_checkpoints_to_alert = TRUE
control_file_record_keep_time= 30
dml_locks                = 2500
row_locking              = always
replication_dependency_tracking= FALSE
transactions_per_rollback_segment= 20
transaction_auditing     = FALSE
undo_management          = AUTO
undo_tablespace          = UNDOTBS1
undo_retention           = 43200
remote_os_authent        = TRUE
db_domain                = world
service_names            = PRD.world, PRD.WORLD
hash_join_enabled        = FALSE
background_dump_dest     = F:\Oracle\PRD\saptrace\background
user_dump_dest           = F:\Oracle\PRD\saptrace\usertrace
max_dump_file_size       = 1240
core_dump_dest           = F:\Oracle\PRD\saptrace\background
optimizer_features_enable= 9.2.0
sort_area_size           = 0
sort_area_retained_size = 0
db_name                  = PRD
open_cursors             = 800
optimizer_mode           = CHOOSE
sortelimination_cost_ratio= 10
btree_bitmap_plans     = FALSE
eliminatecommon_subexpr= FALSE
pushjoin_predicate     = FALSE
optimizerjoin_sel_sanity_check= TRUE
parallel_threads_per_cpu = 4
optimizer_index_cost_adj = 10
optimizer_index_caching = 50
optimpeek_user_binds   = FALSE
pga_aggregate_target     = 536870912
optimizeror_expansion = DEPTH
PMON started with pid=2, OS id=17336
DBW0 started with pid=3, OS id=16972
LGWR started with pid=4, OS id=16900
CKPT started with pid=5, OS id=17236
SMON started with pid=6, OS id=17436
Regards
Pieter

Getting Error while doing month end provisions using FS00

Hi Guru,
please suggest.
while making month end provisions for salraies by using t code FS00 geeting error that Account XXXXX does not exist in company code level
please help me on reslove this.
Rgds..Suresh

Hello Suresh,
The GL Account does not exist for that Company code. Hence extend the GL Account to the Company Code by using Copy with template in FS00.
Regards
Kalpana

Asset Under Construction(AUC),During month end settlement run(via KO8G)

Hi Guys ,
please hlep on this AUC :
During month end settlement run (via tcode KO8G), if there are -ve (credit) values to be settled to an Asset Under Construction (AUC) asset which does not have sufficient +ve value in the current FY, the settlement run will prompt an error message "Balance for transaction type group 10 negative for the area 01". The TT posted via the settlement run is TT115. To get around, user has to raise a manual journal (via doc type AT) to post the -ve value to the same AUC asset via TT101. TT 115 and 101 are configured differently (see attached).
Since the Fixed Assets system does accept credit posting to AUC via a journal, is there a solution to make posting go through via the settlement run?
Regards,
Narra

You can settle the AUC value in one period and posting can be made in another period. in the same you can give the different asset value date in KO88 screen. The only limitation is this possible only if the fiscal year is same.
Give the asset value date as 15.07.2007 in KO88
Hope this will work
Radha

Project Accounting Month end Closing Process

Dear Experts,
Any one can help me by explaining Project Accounting Month End Closing Process
Thanks & Regards
Bharath

Bharath
1. Clear all the transactions from Interface tables
2. Import them
3. Run all the Expenditures (PRC, Interface processes) make sure none of the expenditures are not accounted
4. Run Borrow and Lent process if any, Transfer to GL
5. Run Revenue Process, make sure revenue is generated, accounted
6. Review the revenue draft versions created, make sure all revenue draft versions are released
7. INterface revenue to GL, then later Tie back process
8. Run the Invoicing process
9. Make sure to Approve, release all the Invoices in draft version
10. Interface to AR ( ensure that none of the records are in error)
11. Auto Invoice Import in AR
12. Tieback process in PA
13. run Exc: Transaction Exception details by GL Period/ PA period , Exc: Transaction Exception summary by GL Period/ PA Period
14. Make sure the report output on step 13 are blank, if yes try to clear all the transactions and re run the reports
15. Now try closing the period
Thanks
Krishna

Reversal is only possible after CO month end closing

I am getting the error Reversal is only possible after CO month end closing while doing partial or full confirmation. I had already checked the OKP1 the period is open. Also in MMRV it is fine. Please suggest what could be the reason for this error.
With Regards
Tarun

HI
Yes u are right it is a custom message starting with Z. The message is as below:
Msg.typ Application Area     MsgNo Name of Area of Responsibility Spec.ResAr Number   Numer.
Order        Seq.   OpAc
Message Text
E       Z1                   025                                                  1        1
Reversal is only possible after CO-month end closing !
In detail analysis the only details are
Reversal is only possible after CO-month end closing !
Message no. Z1025
Also when i do the back button the message i am getting is
Error in determining actual costs for order. The detail analysis for the same is
Error in determining actual costs for order 70076492
Message no. RU085
Diagnosis
The actual costs could not be determined correctly due to incorrect or missing data.
System Response
The determination of actual costs is terminated.
However, the confirmation itself can be saved. Error records are written for a subsequent determination of actual costs. Using these error records, the determination of actual costs can be repeated once the original causes of the errors have been removed.
The transaction COFC for reprocessing the determination of actual costs can be found, for example, using the menu options "Logistics -> Production -> Production Control -> Confirmation -> Reprocessing -> Actual Costs."
However, it is not possible to write error records for run schedule headers, QM orders or header confirmations. In this case, the confirmation transaction must be terminated because a subsequent determination of actual costs is not possible.
Procedure
You can find the exact cause of the termination of the determination of actual costs in the error log for actual cost determination.
You can switch the error log on and off using the variable parameters.
With Regards
Tarun
With Regards
Tarun

Someone can help me here with posting period error in doing GR post in SAP

Hi Seniors,
I've been getting below error while doing GR post. could someone help me to step on further with this error.
"Check table T001B for record type "0", the selected company code, account type S and G/L account 191*** If required, make sure that an entry is made in the table or an interval is changed."
i'm using test system as am a student of SAP MM.
Thank you very much..
Shivakumar

Open and Close Posting Periods
In this activity, you can specify which periods are open for posting for each variant. You have two time intervals (time period 1 and time period 2). In each interval, specify a period lower limit, a period upper limit, and the fiscal year.
You close a period by selecting the period specifications so that the period to be closed does not fall within them.
You can also assign authorization groups for permitted posting periods. This means that in month-end or year-end closing for example, you can open some posting periods for specific users only. The authorization group only has an effect on time period 1. The authorization object is F_BKPF_BUP (Accounting document: Authorizations for posting periods). For more information about assigning authorizations, see the corresponding section for User Maintenance.
Note
Specify G/L account numbers for your specifications. You define the permitted posting periods for the subledger accounting accounts using the relevant reconciliation accounts. To do this, specify the account type for the subledger accounting, such as D or K, and the relevant reconciliation account.
Caution
There must be a minimum entry for each variant. This entry must have + in column K, and the columns From Account and To Account must not contain entries. In the columns for the posting periods, specify the periods you want to always be open in this variant. With further entries, you define more specifically which periods are to be open for which accounts.
Activities
1. Specify the periods permitted for posting.
2. First enter the periods permitted for posting for all variants (minimum entry).
3. Then add entries for account types or account areas if the periods are to be further restricted for specific accounts.
4. In addition, enter an authorization group for each time period 1 in order to limit user access.

Sales doc items with the status CLSD ARE being selected for month-end

We are working to improve month-end processing time for Sales Orders We use SAPKKA12 to set CLSD status on line items
SAP Help states: be sure that the status CLSD (closed) is set for all sales document items that you do not want to include in the period-end closing process. The sales document items with the status CLSD are then not selected for processing in the period-end closing process. Use report program SAPKKA12 to set the status.
This use to work (in 4.0). I have been on other projects and just brought back to this after several years (now in 5.0). Testing today shows that orders with CLSD status are being selected for month-end process.
Any ideas why this is so? System is selceting over 300,000 orders when well over half of them are set to CLSD. I do get a message that the order is not relevant to processing, but selecting the order and logging the message take time. and the logs are VERY long.
thanks

Does any one else have this issue that Sales documents with status CLSD are selected by RA (KKAK)?
In just one of our jobs, i get this Basic List
Perform actual results analysis      31273
Not relevant                                                 103894
Error                                                        2306
Objects Selected                                    137,473
75% of the orders are CLSD. and the system is still counting them. (we do not out put information messages)
I do understand that the orders are not analyzed, but all documentaion states that CLSD status is not selected, and in our 5.0 system, they are selected. In our 4.0 system, they were not selected.
Does this truely work for anyone in a 5.0 system?
Thanks
Althea

Navigation for Month End Closings & Some inputs on Monthly closing issues

Hi Experts
Some inputs on Month End Closing and
what type of issues will be come accross during the closing( Mention any ).
Navigation for the Month End Closings

In the case of Inventory: Monthly Accounting Period closure, you need to ensure that there are no unprocessed shipping transactions, uncosted material transactions, pending WIP costing transactionsm etc.. The number of these kinds of transactions should be Zero. For example, if there are any unprocessed shipping transactions which might be stuck/errored out during Interface Trip Stop program run, then you can NOT close the period for that month until you clear these transactions. Check the metalink note, 262979.1 for the same.
Navigation is Inventory > Accounting Close Cycle > Inventory Accounting Periods. Click on the Pending button to see the pending transactions. If there are NO requried resolutions to be done, you can close the INV period for that month.
Regards,
Hemanth

Month-end

Hi friends,
I have some knowledge of month end acivities.
here i mentioned ....
1)Open and close posting periods in FI.OB52
2)Close MM period..MMPV
3) Collect and post all outstanding vendor InvoicesF-43
4) Collect and post all customer InvoicesF-22
5) Post accruals/deferrals FBS1
6) Generate Recurring entries.F.14
7) Run the interest calculation..F.52
8) Maintaining Exchange Rates OB08
9) Run the foreign currency valuation.F.05
10) Run depreciation run..AFAB
11) GR/IR clearing account .F.13
12) Complete Bank ReconciliationFF67
Please any mistakes rectify and any another acivities mentioned the with T.codes.
pls let me know.
Regards,
Chandra.

Hi
Other few activities given below:
FI
1. Depreciation Run - AFAB
2. F.5D Balance sheet adjustment calculation
3. F.5E Balance sheet adjustment Post
4. F.05 Foreigh Currency Valuation.
CO
1. CO43 Overhead calculation
2. KKAO - WIP Calculation
3. KKS1 - Variance Calculation
4. CO88 - Settlement
If you think it helpful kindly assign the points
Thanks & Regards
Mahesh

GR/IR at the month end

Hello,
What we have to do with GR IR account for clearing at the month end.
Regards
Ravi

Hi Ravi,
GR/IR clearing is the month end activity. To do this first you should maintain gl accounts under open item managment.
the GR/IR Clearing account is used to account for Goods Receipt and Invoice entry for the vendor invoices. The GR/IR clearing account program reclassifies the entries in GR/IR account as either assets or liabilities for reporting purpose. At the period end which goods receipt has been done and for which Invoice has not been recd or goods for which invoice has been done and GR has not been done. During the time between invoice being created and delivered the goods. To accommodate this timing difference a gr/ir clearing account is maintain temporarily to record the flow
hope it will useful and pl assign points
thanks
venkat

Delivery Block at PGI level based on GI date and Month end date

Business need a check on delivery processing based on the Planned GI date, Month end date and transit period. This transit period is a custom field and dependent on customer. Also it is not maintained anywhere in system. Business store it in some excel format.
The logic needed is: For any given month, the delivery order MUST be goods issued in the same month, i.e. once the order is delivered, the Post goods issue should ONLY be allowed if and only if , the PLANNED GI date ( as maintained in delivery ) + transit time ( at customer level ), falls within the month end date. If not, a block should be applied at PGI and only authorized personnel should be able to release that block.
Also, there will be no check at invoicing VF01 level. Once the PGI blocked is removed, there will be no check on invoicing. The month end date may vary month to month and need to in combination of Sales Org / Plant as mentioned
In addition, the business need an exception report where the information of releasing the block should appear for release date, user id of the responsible person, time sales order no etc. and it should be downloadable.
We can have a custom table to maintain the month end day in given combination.
But I need your expert inputs as-
1-     Can we add this transit period in at customer master data as it is dependent on customer and there are huge no of customers for the sales unit? If not, then how to maintain it; may be a z table?
2-     Based on this logic, what should the code/logic to be written for block at PGI.
3-     How to control the authority check for removing the block.
4-     The source fields for exception report.
Pls revert accordingly.
Many thanks in advance.

Hello,
Please refere the answers to your questions:
1- Can we add this transit period in at customer master data as it is dependent on customer and there are huge no of customers for the sales unit? If not, then how to maintain it; may be a z table?
You can either use some un-used Feild in Customer Master or maintain a Z-Table. I believe maintaining a Z-Table would be easy as you have huge number of Customers. You can also write a dmall program to Pick the Customer-wise transit dates from a excel file & store in Z-Table.
2- Based on this logic, what should the code/logic to be written for block at PGI.
You have explained the requirement well in your thread, you need to explain the same to your ABAPer & Basis person & they would do the needful.
3- How to control the authority check for removing the block.
Basis person would create & assign a Z-Authorization object which the ABAPer would use in his program.
4- The source fields for exception report.
Once you do the above development, your ABAPer will easily pick the required feild in Report as he has already used all the feilds somewhere in his development.
Hope this helps,
Thanks,
Jignesh Mehta

Month end accrual posting date- Last day of the month

Hi Experts,
I have set up month end accruals for PY US by configuring posting dates, LDCD, WageType accrual processing class, Schema changes. I have also set the closing dates as the end of the month.
Now after I do the posting , there are three documents getting generated.
1. Accrual posting document with first day of the current month
2. Normal Payroll posting document with payroll period posting date
3. Accrual reversal document with first day of the following month.
My Question is: As per standard SAP configuration, the month end accrual will have first day of the month. Can we customize this to end of the month for doc#1 - accrual document?
Please do let me know your suggestion and ideas.
Thanks,
Amosha

Hello,
I have a similar question and I hope to have more details on how to change the posting date.
The point is that I have an amount of 1200 and I have to post 100 for each month.
Key Date for Accruals: 31.01.2011
I posted 100 with Document date: 31.01.2011 and Posting date 31.01.2011
Key Date for Accruals: 28.01.2011
I posted 200 with Document date: 28.02.2011 and Posting date 28.02.2011
Also I reversed the amount posted in the previous month (100) with Document date: 31.01.2011 Posting date 28.02.2011
And so on...
The problem are the dates because I need to post the amount at the end of each month (28/02) and to reverse the previous amount at the beginning of the next month (01/02).
How can I change these dates?
Thanks a lot in advance
Kind Regards,
E.

MM month end periods error..?

Similar Messages

Maybe you are looking for