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!
MAS90 Error 47 - Journal List Entry
- Thread starter Lori4pets
- Start date
LouieGrandie
Technical User
Could you please post the entire error message. Need at least the program name and line number. Also need to know what version of MAS you are on and if this is MAS90 or MAS200. Need to know which journal. Right now there is not enough information to go on.
- Thread starter
- #3
Error #47: Substring reference out of string
Program GLWDAC - Line 10080
File GL3CAP.SOA - GL3 G/L Journal Posting Detail File
Channel 2
Key-N/A
Application - General Ledger (3.71)
L/M Level - 3.71
I have an un-posted journal entry that I can not access to edit or delete. I’ve tried creating a new JE and use the arrows to back into this entry, but it only gives me the error. I’ve tried to post the entry and again, I just get the error. I’ve Goggled the error and posted it in a chat room – so far, no solutions. (There is a lot of info regarding this error on the web – but not many solutions without a “rebuild”).
The problem is I can’t get any other JEs to post – it blocks all entries behind it.
My audit is next week and I need to record some entries - YIKES!
Appreciate your assistance!
Program GLWDAC - Line 10080
File GL3CAP.SOA - GL3 G/L Journal Posting Detail File
Channel 2
Key-N/A
Application - General Ledger (3.71)
L/M Level - 3.71
I have an un-posted journal entry that I can not access to edit or delete. I’ve tried creating a new JE and use the arrows to back into this entry, but it only gives me the error. I’ve tried to post the entry and again, I just get the error. I’ve Goggled the error and posted it in a chat room – so far, no solutions. (There is a lot of info regarding this error on the web – but not many solutions without a “rebuild”).
The problem is I can’t get any other JEs to post – it blocks all entries behind it.
My audit is next week and I need to record some entries - YIKES!
Appreciate your assistance!
I found this:
TITLE :
Error 47 GLWDAC 10080 in General Journal Entry
DETAILS :
Error 47 GLWDAC 10080 in General Journal Entry
Entry Type: Informational
Product: Sage MAS 90 and Sage MAS 200 ERP
Application: General Ledger
Version Reported: 3.4
Subject:
Error 47 GLWDAC 10080 file = GL3xxx.soa, in General Journal Entry
Possible Resolution:
1. In Library Master / Repair / Rebuild Application Key Files
2. Click 'OK' on the warning and Enter in General Ledger for
the Application and the Company Code
3. The system will load files
4. Select GL2xxx, xxx=company code, the G/L Journal Posting
Header File then double click to turn the 'NO' to a 'YES'
on the right side of the screen
5. Click on 'Proceed' at the bottom of the screen
6. Answer 'Yes' to scan files first and 'Yes' to save original
files (Note: If there is a difference in the amount of record
recoverable print the error log, however, if the number of
records are the same then the error log does not need to be
printed)
7. In Repair / Analyze and Relink Line Files
8. Click 'OK' on the warning and select General Ledger as the
module and the Company Code
9. Select GL3xxx , xxx=company code G/L Journal Posting Detail
File then double click to turn the 'NO' to a 'YES' on the
right side of the screen
10. Click on 'Proceed'
11. Answer 'Yes' to save original files
12. This utility will let you know if there are any errors. If
there were errors then you would print the error log.
13. In Library Master / Repair / Rebuild Application Sort Files
14. Select General Ledger and the Company Code and click
on 'Rebuild'
Note: If there were errors during Analyze and Relink Line Files then go back into General Journal entry and check the lines on the transactions, lines that were removed may need to fixed.
If the above does not fix the error then rename and manually reinitialize the GL2xxx.soa and GL3xxx.soa files. This should only be done by individuals with experience in the Sage MAS 90 utilities or with assistance from a Customer Support Specialist.
Repair Disclaimer:
Note: Caution should be taken whenever File Analysis and Repair utilities are used. Always make a backup first. If necessary, seek the assistance of a qualified Sage Software business partner or Customer Support analyst.
TITLE :
Error 47 GLWDAC 10080 in General Journal Entry
DETAILS :
Error 47 GLWDAC 10080 in General Journal Entry
Entry Type: Informational
Product: Sage MAS 90 and Sage MAS 200 ERP
Application: General Ledger
Version Reported: 3.4
Subject:
Error 47 GLWDAC 10080 file = GL3xxx.soa, in General Journal Entry
Possible Resolution:
1. In Library Master / Repair / Rebuild Application Key Files
2. Click 'OK' on the warning and Enter in General Ledger for
the Application and the Company Code
3. The system will load files
4. Select GL2xxx, xxx=company code, the G/L Journal Posting
Header File then double click to turn the 'NO' to a 'YES'
on the right side of the screen
5. Click on 'Proceed' at the bottom of the screen
6. Answer 'Yes' to scan files first and 'Yes' to save original
files (Note: If there is a difference in the amount of record
recoverable print the error log, however, if the number of
records are the same then the error log does not need to be
printed)
7. In Repair / Analyze and Relink Line Files
8. Click 'OK' on the warning and select General Ledger as the
module and the Company Code
9. Select GL3xxx , xxx=company code G/L Journal Posting Detail
File then double click to turn the 'NO' to a 'YES' on the
right side of the screen
10. Click on 'Proceed'
11. Answer 'Yes' to save original files
12. This utility will let you know if there are any errors. If
there were errors then you would print the error log.
13. In Library Master / Repair / Rebuild Application Sort Files
14. Select General Ledger and the Company Code and click
on 'Rebuild'
Note: If there were errors during Analyze and Relink Line Files then go back into General Journal entry and check the lines on the transactions, lines that were removed may need to fixed.
If the above does not fix the error then rename and manually reinitialize the GL2xxx.soa and GL3xxx.soa files. This should only be done by individuals with experience in the Sage MAS 90 utilities or with assistance from a Customer Support Specialist.
Repair Disclaimer:
Note: Caution should be taken whenever File Analysis and Repair utilities are used. Always make a backup first. If necessary, seek the assistance of a qualified Sage Software business partner or Customer Support analyst.
- Status
Similar threads