MSB919, MSB900 problems again (documentation request)

Hi all,
I have again some troubles with (cost) transaction posting in MIMS (Using exernal cost records MSF903, MSB919 and MSB900).

issue
1/- By running MSB919 - always only cca 200 of records where processed (inserted into MSF900) and then failed. By other run of MSB919 the same situation etc...(this way I have "sent" all MSF903 records into MSF900 table...).Below you can find the MSB919 log file...
2/ - When running MSB900 only few record from MSF900 where processed (I have checked the jnl_interface_ind -which caused similar issue below and its spaces, so OK) and MSB900 "succesfully" finished without any warings/errors in log - not processed cca 8 tousends of records with posted status='N' or 'U' . Do you have an idea why and what to do? (I was told that there is a possibility to reset msf900 start transaction id - but I have no idea how and for what situation is that suitable...)
3/ - Maybe related question - currently we have transaction type's records (BPJ,MPJ) and posted status (N,U) for this full_period and MJV trx, could you help me please to understand how to handle especialy trx with 'U' and 'N' in posted_status (is there some special way how to process that records?) - why they can be ignored and how to "move" system to process them.
4/ - Is there some detailed documentation available describing the whole process of posting records onto work orders (with all possible exceptions, problem solving etc...). Could you please send me a reference to infopack or the document by email.


Its urgent for us, I would appriciate any help of you.
Thank you and nice day.
Petr


PS. There is 7518 unprocessed records in msf900 for current period...

select count(*) from msf900 where posted_status='N' and full_period='200401'

****logs fo MSB919 and MSB900***********************


MSB919 Program Version = 010C Revision = 1.3
SPECS : REQUEST___MSB919__200408160000007995918384867001
SEARCHING FOR A REQUEST RECORD FOR SPECIFIED KEY:MSB919 200408160000007995918384867001
--> Timeslot checking switched off!
ACCOUNTING TRANSACTIONS IMBALANCE :
BATCH NUMBER :
WX-TRAN-BALANCE = 137402,660000
WX-SEC-BALANCE = 0,000000
WX-CASH-BALANCE = 0,000000

*--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**-



*** A FATAL ERROR HAS OCCURRED ***

*** PROGRAM
MSB919
MSS904

*** PROGRAM-VERSION
005

LINE ACCESS RESULT FILE KEY
2647 LOCK-HA NOT FOUND MSF906 0001M0059200401
2233 STARTGE FOUND MSF006A 0001M0059
2233 READNXT FOUND MSF006A 0001M0059 TESTTESTTEST
2244 ENDBR-F MSF006A 0001M0059 TESTTESTTEST
2215 READ-NO FOUND MSF966 0001TESTTESTTEST
1935 STARTGE FOUND MSF907 0001MLCZK 0059
1935 READNXT FOUND MSF907 0001MLCZK 0059
2003 ENDBR-F MSF907 0001MLCZK 0059
1231 READ-NO MSF000 0001PC0401
1231 OTHER S/R Call MSSERM
LAST SQL ERROR WAS: +1403 SQL WARNING FLAGS:<********> SQL MESSAGE:
Not found
A FATAL ERROR HAS OCCURRED____________
OS Ret. Code (EIBACODE) is 1403 (DEC.)
TP Condition (EIBRCODE) IS 3 (DEC.)
ERROR : NOT-FND, $UNDEFINED$

*--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**-



*** A FATAL ERROR HAS OCCURRED ***

*** PROGRAM
MSB919
MSS901

*** PROGRAM-VERSION
017

LINE ACCESS RESULT FILE KEY
241 OTHER S/R Call MSSHEX
241 OTHER S/R Return MSSHEX
6324 LOCK-HA FOUND MSF900 0001899454857668M
4574 READ-HA FOUND MSF010 TR MPJ
4505 READ-HA FOUND MSF010 TG M
5380 STARTGE FOUND MSF006 0001TESTTESTTEST M
5380 READNXT FOUND MSF006 0001TESTTESTTEST M0059
5388 ENDBR-F MSF006 0001TESTTESTTEST M0059
5481 OTHER S/R Call MSS904
1360 OTHER S/R Call MSSERM
A FATAL ERROR HAS OCCURRED____________
OS Ret. Code (EIBACODE) is 1403 (DEC.)
TP Condition (EIBRCODE) IS 6 (DEC.)
ERROR : OTHER.., $UNDEFINED$

*--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**-



*** A FATAL ERROR HAS OCCURRED ***

*** PROGRAM
MSB919
MSS902

*** PROGRAM-VERSION
017

LINE ACCESS RESULT FILE KEY
2264 READ-NO FOUND MSF900 0001899454857668M
A FATAL ERROR HAS OCCURRED____________
OS Ret. Code (EIBACODE) is 1403 (DEC.)
TP Condition (EIBRCODE) IS 6 (DEC.)
ERROR : OTHER.., $UNDEFINED$

*--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**-



*** A FATAL ERROR HAS OCCURRED ***

*** PROGRAM
MSB919
MSS907

*** PROGRAM-VERSION
010

LINE ACCESS RESULT FILE KEY
6555 READ-NO FOUND MSF900 0001899454857668M
5611 READ-HA NOT FOUND MSF918 0001M000000033
5794 READ-NO FOUND MSF900 0001899454857668M
5811 OTHER S/R Call MSS902
1360 OTHER S/R Call MSSERM
A FATAL ERROR HAS OCCURRED____________
OS Ret. Code (EIBACODE) is 1403 (DEC.)
TP Condition (EIBRCODE) IS 6 (DEC.)
ERROR : OTHER.., $UNDEFINED$

*--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**--**-



*** A FATAL ERROR HAS OCCURRED ***

*** PROGRAM
MSB919

*** PROGRAM-VERSION
010

LINE ACCESS RESULT FILE KEY
1643 OTHER S/R Return MSS907
1643 OTHER S/R Call MSSDTM
362 OTHER S/R Return MSSDTM
362 LOCK-HA FOUND MSF080 MSB919 200408160000007995918384867001
362 REWRITE MSF080 MSB919 200408160000007995918384867001
1928 STARTGE FOUND MSF006A 0001M0059
1928 READNXT FOUND MSF006A 0001M0059 TESTTESTTEST
1928 ENDBR-F MSF006A 0001M0059 TESTTESTTEST
1396 OTHER S/R Call MSS907
1360 OTHER S/R Call MSSERM
A FATAL ERROR HAS OCCURRED____________
OS Ret. Code (EIBACODE) is 1403 (DEC.)
TP Condition (EIBRCODE) IS 6 (DEC.)
ERROR : OTHER.., $UNDEFINED$

*********MSF900 log*********************************
MSB900A01 LOGICA5 20040817090514000120040817MSB900 F 00 00 00 00 00 00 00 00 00 0
CURRENT RUN NUMBER 0178
CONTROL TOTALS
FIRST TRANSACTION ID POSTED: 858950284444M
LAST TRANSACTION ID POSTED: 896253103661M
TOTAL NUMBER OF TRANSACTION PROCESSED THIS RUN 9
NUMBER OF TRANSACTIONS POSTED 0
NUMBER OF TRANSACTIONS WITH ERRORS 0
NUMBER OF TRANSACTIONS WITHOUT ERRORS 0
NUMBER OF TRANSACTIONS WITH ERRORS AND NOT POSTED 0
NUMBER OF POSTING RECORDS CREATED ON G/L ACTUAL BALANCES FILE (MSF960) 0
NUMBER OF SUMMARY RECORDS CREATED ON G/L ACTUAL BALANCES FILE (MSF960) 0
NUMBER OF POSTING RECORDS CREATED ON G/L ACCOUNT STATISTICS FILE(MSF962) 0
NUMBER OF SUMMARY RECORDS CREATED ON G/L ACCOUNT STATISTICS FILE(MSF962) 0
NUMBER OF EQUIPMENT COSTING SUMMARY RECORDS CREATED (MSF630) 0
NUMBER OF PROJECT COSTING SUMMARY RECORDS CREATED (MSF665) 0
NUMBER OF GROUP CODE COSTING RECORDS CREATED (MSF760) 0
TRANSACTION VALUES POSTED
PERIOD DEBITS CREDITS
----------------------------------------------
TOTAL 0,00 0,00
TRAN-TYPE DEBITS CREDITS
0,00 0,00

Report Summary:
Total Number of Records Read: 0
----------------------------------------------------------- End of Report ----------------------------------------------------------

 

[lmel]

From waht you've stated, I'm not too sure which of the two failed. If it is the MSB900 then a solution could be easy. But for MSB919, then you could be required to check if your MSB904 or ???904 and MSR908 report and check what errors were reportd.

Kindly do the following to confirm the errors.

Run the SQL sript

select * from msf909

This will confirm the unposted transction by a failed MSB900

From here we can then check what re-start parameters have to be put i.e duping the MSB900 to start prior to the failed MSB900.

lmel

 

[kelana]

Dear Petr,
1. As Imel answer, if MSB919 failed, check error report MSR908

2a. Posted status of 'U' - unapproved journal must be
changed to Approved via online journal maintenance
menu, otherwise they won't be posted by MSB900 forever.
2b. In case of some transactions left behind by MSB900, we
must change MSB900 run control, in our MIMS3.13
msf000_jp_run.
2b1. First find minimum unposted transaction id
(process_date+transaction_no+rec900_type),
eg. '889262138900M'. Unposted status in MSF900 :
second digit in stats_type field equal to N, U,
V, O - just remember NUVO
2b2. Then we must find latest MSB900 or max
(control_rec_no) within district code, eg. 3431
query :
select max(control_rec_no) from msf000_jp_run
where dstrct_code = 'XXXX'
2b3. Review whole data from 2b2, then we change first
transaction to be posted by next MSB900 run,
query :
update msf001_jp_run set first_tran_nxtrun
= ‘889262138900M’
where dstrct_code = 'XXXX'
and ctl_rec_type = 'JP'
and control_rec_no = '3431'
2b4. Run MSB900 - check result

3. See explanation in point 2


Good luck.. and do the test in development first.