Error 47 @ Line 2320 in Program SOWUAC (please help) 1

[busyb284]

When I go to Sales Order and try to click on Daily Sales Reports/Updates and hit preview, it says "Update interrupted. Do you want to restart?"

When I press yes, it gives me a "Error 47 in program SOWUAC at line 2320"

Here is the info:

Stack:
09020M:\MAS90\so\SOWUAC
02010M:\MAS90\soa\SWERRM
07072M:\MAS90\Home\lib\_winproc
02100M:\MAS90\soa\swerrm

Dump:
! Level=1
! PGN="M:\MAS90\soa\SWERRM"
! Statement......2010
BTN_CLICKED=1002
BTN_COL=9
BTN_ROW=3
COL=117
coSession=100001
CTL_CHAN=32727
E0=47
E3=2320
E5=33
E6=100
PIC=1
ROW=38
SAV_LFA=1
SAV_LFO=21
WIN=1
WIN_COLS=40
WIN_ROWS=5
APP$="S/O"
BRANCH$="ERROR47"
CMD$="RE"
LINE1$="Error 47 in program SOWUAC at line 2320"
msg$="Error #47: Substring reference out of string"
PIC$="!Stop95"
TMP$="&Retry"
X$="lS/O9X3LSO1 Sales Order 4.00 ?40227Y 4143.70N "

Please help me, I am trying to resolve this without having to go through the hassle of calling my reseller.

Thanks ahead of time to all you smart people.

 

[dfeller]

You really don't need to post the "stack" and "dump". What's typically needed is the program number, program name, line number, file and key info.

Why is calling your reseller a hassle?

This error is on Sage's KB under Resolution ID 663 and says it was fixed on version 4.05. Just go to the knowledgebase, pull up that entry, and it will tell you exactly how to fix it.

Dawn

 

[busyb284]

Dawn,

I won't be able to get a immediate resolution because we were just bought out and account info will be hard to resolve.

Could you please post the the Resolution on here so I can fix it?

Thank you so much.

 

[BigLouie]

Error 47 SOWUAC 2320, when posting Sales Order Invoices. This error occurs when line items on an invoice are pointing to invalid or nonexistent line items on a sales order. In other words, if the Invoice Data Entry Detail File (SO6) contains an invalid or missing Order Line Index from the Sales Order Entry Detail file (SO2), this error will occur.

Possible Resolution:

The value in the 'Order Line Index' field in SO6 may be incorrect or does not match the value in SO2 (Sales Order Line Index file). Remove the 'Order Line Index' within SO6 (Invoice Data Entry Detail File), so that the invoice no longer attempts to update the sales order line. This will allow the update to complete.

Note: Use caution when working with repair utilities. Always make a backup first. If necessary, seek the assistance of a qualified Sage Software business partner or Customer Support analyst.

1. Click 'Info' on the error window and then click 'Debug' (recreate the error if necessary)
2. In the debug screen, type "?a$(1,7)" (no quotes) and press 'Enter' This will return the invoice number, write this down.
3. Type "bye" to close the debug window
4. Open LM / Repair / Data File Display and Maintenance (DFDM), type SO5xxx (xxx = company code) and press 'Enter'
5. Click the 'Keyscan' button and select the invoice number returned above
6. Looking at the screen, write down the value next to field 02 (for example, 123.00) This is the starting index number.
7. In the File Name field, type SO6xxx and press 'Enter'
8. Enter the starting index number (from step 6) into the Index field and press 'Enter'
9. Click 'Edit' and enter the following (Order Line Index record):
a) Field number: 04
b) Starting position: 64
c) Length: 05
10. Remove the value that appears in the 'Change Data' field. Click 'Ok' to close the edit window
11. Note the value in Field 03 for the same record and write the number down. This is the next index number (next item on this invoice). Type this number into the Index field and press 'Enter'
12. Repeat steps 8 thru 11 until Field 03 is ".00". This indicates the last index record (last line on the invoice)
13. Try updating the Sales Journal again. If the error reoccurs, repeat the above steps starting at the beginning. The error may be occurring on multiple invoice numbers.

Note: After resolving the error, check the modules being updated for correct postings. In other words, check Accounts Receivable and confirm the invoices are on the customer's account and that they are in invoice history. Check Inventory Management to see if the items were relieved for stock correctly. Check the General Ledger for the correct postings. Check the sales order that were being shipped, make sure they were purged (if shipped complete) or backordered (if partially shipped)

 

[busyb284]

Thanks BigLouie!

I had to that with many invoices and now that I am trying to update sales journal, its giving me a different error.

Error 47 in program SOWUAD at line 12255.

Is there a possible resolution for that?

I really appreciate your help.

 

[busyb284]

I tried debugging and now am getting a different error when going to daily sales reports/updates...here is the error

Error 40 in program SOWUAE at line 12180

Please come through guys.

 

[BigLouie]

Error 40 SOWUAE 12180, during Sales Journal update after invoicing a sales order

Entry Type: Program Issue

Product: Sage MAS 90 ERP, Sage MAS 200 ERP, Sage MAS 200 ERP - SQL Server Edition

Application: Sales Order Processing

Version Reported: 3.71

Status:

Resolved with program fixes SO3106-T and RA3006-T for Sage MAS 90 or 200 versions 3.71 and 4.00.

Notes:

* The error may still occur if Sale Order Quote/History lines are out of sync with sales order lines from causes other than what is resolved by these program fixes. A utility is available in Sage MAS 90 and 200 4.10 to resync the lines. If an upgrade is not available, use the workaround below.

* Sage MAS 90 and 200 4.05 include the files from these program fixes.

* The program fixes affect only orders created after the fixes are installed.. Existing orders may continue to receive the error, use the workaround below to resolve it.

* SO3106-T prevents the issue only for transactions created in Sales Order. RA3006-T prevents the issue for transaction created in RMA.

Subject:

Error 40 SOWUAE 12180, during the sales journal update after invoicing a sales order that was created in Sales Order Entry or from RMA (through Cross Ship), and adding a comment to the order.
Steps to Duplicate:

In ABC company:

1. Enter an RMA return for any customer
* Customer action = Replace
* Add one comment line, and apply the comment to "All".
* Add one inventory item, and select "Repair" as the item action.
2. Generate the transactions. This creates a sales order.
3. Open Library Master / Repair / Data File Display and Maintenance (DFDM).
4. Select SO_04abc.soa.
5. Verify that both lines exist for the generated sales order.
* The comment line should be sequence number "0".
* The inventory item should be sequence number "1".
6. Open Sales Order / Main / Sales Order Data Entry, and select the sales order generated above.
7. Add another comment line below the inventory item, and click 'Accept'.
8. Open DFDM and select SO_04abc.soa again.
9. Note that only two lines exist for the order. Also, note that both are "Comment" lines. The inventory item in SO_04 is overwritten.

Expected Behavior:

Sales orders should append comments to the quote history files and not overwrite existing lines.
Possible Workaround:

Notes:

* Use caution when working with the following task. Always make a backup first. If necessary, seek the assistance of a qualified Sage Software Customer Support analyst.
* The error message should provide a key (for example, 00075860000000004). This key is from the Sales Order History Line Detail File (SO_04), and represents the order number and line sequence number. If the error did not provide a key, click 'Debug' on the error window and perform the following:
1. Type "? SO_04$(1,17)" (without quotes) and press ENTER.
2. Note the returned key from SO_04.
3. Type "BYE" (without quotes) and press ENTER to close 'Debug' window.

Sage MAS 90 and 200 (See below for Sage MAS 200 - SQL Server Edition):

1. Open Library Master / Repair / Data File Display and Maintenance (DFDM).
2. Select SO_04xxx (xxx = company code).
3. In the 'Key' field, type the 17 digit number from the error message or 'Debug' step above and press ENTER.
4. Click the 'Edit' button. Enter the Field number as "10" (without quotes) and press ENTER. In the 'Change' field, the number must be one or greater. This field is the sales unit of measure conversion factor which must be greater than zero. Enter "1" (without quotes) in the 'Change Data' field.
5. Perform the following steps only if the record is an inventory item. Skip the following steps if the key was a "/C" comment line.
6. Still in DFDM, select IM1xxx at the 'File Name' field (xxx = company code). Press ENTER.
7. Click 'Keyscan', and select the item number that was corrected above.
8. Click 'Edit'. In the 'Field number', type "5" (without quotes). Press ENTER.
9. In the 'Change' field, the number must be 1 or greater. This field is the sales unit of measure conversion factor which must be greater than zero. Enter a "1" (without quotes) in the 'Change Data' field, and click 'OK'.
10. Close DFDM, and start the update again.

Sage MAS 200 - SQL Server Edition:

From the debug window:

> ? SO_04[8]
Note: If this returns 0, this the problem line.

>LET SO_04[8]=1
Note: This changes the value from 0 to 1.

>? SO_04[8]
Note: This verifies what the value is now.

>GOTO 12180
>? 'POP';RUN

Repeat these steps for every record that errors, to complete the update. Should get the Sales Journal Update Register prompt next.

 

[busyb284]

thanks louie, you really came through.