Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MSB919, MSB900 etc.. - external cost records

Status
Not open for further replies.

Petbul

MIS
Jun 20, 2001
56
CZ
Hi, please, is anybody familiar with using external cost records accounting - records from MSF903 (processed by MSB919) ->into MSF900 (processed by MSB900)-> costs posted onto WO.(We are using just costs not revenue...)...

We have processed 4 months (2 months sucesfully - through both MSB919, MSB900 - 2 months not).One month = in our case is one batch_id.
At the end of running MSB919 remains some records (about 100 records from tousends) from those two batch_id's in MSF903 and MSF903_M_903 (MSF903_A_903 - was deleted first)..
Records posted to MSF900 are not proccessed by MSB900 (No transaction proceseed - I can't find any errors).
What would yould you supposed to do now?


1.With the records in MSF903 etc. (to run it again under another batch_id_)
2.With non processed records in MSF900 (system looks like don't know about them]
3. Is somwhere stored batch_id ? I think that we can't use the same batch number again - bat don't know where is this information stored.
4.What rules schould I check in MSF903...and MSF900

Please, if posible, answer ASAP ;)
Many thanks
Petr







Best regards
Petr
 
We had to write a custom msb903 program. in our process we run the custom msb903 program which creates an out put file that is fed to the msb904 program.
The msb904 creates the batch number and journal entry transactions. If there are errors from the msb904, run the msr908.
Errors are fixed via mso919. There are also options to delete batches, verify batches, etc. If there are too many errors to correct, it may be easier to delete the batch(es) in error and re-run msb904.
To re-run msb904, there will be a mst903.txt file from the most recent run, which is input into the whole process. Just execute msb904 after deleting the batches.

After errors are corrected via mso919 or re-running msb904, then execute msb919. This program processes batches that are error-free and creates the journals. If one batch has errors and a second one doesn’t, msb919 will only process the second batch. The program also deletes from msf903 the processed transactions.
Finaly, Execute msb900 to post the journals to the GL.

I hope this will help you out.
 
Yes. You can use the same Batch No. again once entries are in MSF900
 
For specific problem : Records posted to MSF900 are not proccessed by MSB900

We can check in msf001_jp_run (this file is a control file for MSB900):
- first find max msf001_jp_run.control_rec_no
- then find msf001_jp_run.first_tran_nxtrun
- Compare it with minimum transaction_id that is not posted by MSB900 (this should not earlier than first_tran_nxtrun)
- Change first_tran_nxtrun with first/minumum transaction_id that is not posted by MSB900

FYI we're still using 3.13NY
:(


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top