There are certain tasks or times while in Sage 300 ERP you will come across something that doesn’t make sense or you think that it is an error or that you’ve done something wrong. However, sometimes what you think is an issue actually could be by design of the program.
For this week’s blog post, we want to take a look at some tasks that actually are meant to behave that way while in Sage 300 ERP:
• Cannot change the bank entry type when creating a new bank entry
So you are in Bank Entry in Bank Services and you want to change the bank entry type when creating a new bank entry but find that option is not available. You then try to change the bank entry type by going through Reconcile Statements and then clicking the Bank Entry button but the same occurs.
The reason why you are unable to change the bank entry type is because if you have assigned a Default G/L Account in Bank Option, the Bank Services inserts a default record for the bank entry and the Entry Type cannot be changed.
If you don’t assign a default G/L Account in Bank Options, the Entry Type will not insert a default record when you create a bank entry thereby you are able to change the Entry Type:
You will need to delete the default detail line created, this will allow you to select the Entry Type and insert a new blank detail line. Note that you won’t see this issue if you have two or more banks created.
• Unable to create multiple lots for one master item
In Inventory Control, users have found that when creating an assembly, the option to select “Lotted Items” is greyed out for a Master Item.
The reason why is because Sage 300 ERP is not designed to allow multiple lots to be assigned to a single master item so that option is greyed out to prevent anyone from doing so. The workaroudn is to create multiple assemblies.
• Performance is slow when printing OE Picking Slips
If you are printing Order Entry Picking Slips, you may have noticed that the performance is slow. The slowness is actually by design. You see, when the “Include Picking Slips Already Printed” option is selected, Sage 300 ERP will go through every order in the database to read what the printed status is. It will then write back to the database table for each order if it is printed or not. This can take a lot of time, especially if you have thousands of orders that already exist.
The only workaround is to select a range when printing.
• Entering multiple return entries for the same purchase order receipt
While in the P/O Return Entry screen, you discover that the screen allows you post multiple returns for the same purchase order receipt. What ends up happening is that more items end up being returned than purchased. This is by design. When you click on “Return All” in the P/O Return Entry (as indicated in the image below), Sage 300 ERP will update the Quantity Returned field automatically:
Now if:
• All items have already been returned and you click Return All, the value in the Quantity Returned field will default to 0.
• The items were partially returned and you click Return All, the value in the Quantity Returned field will default to the quantity remaining to be returned. However, you can still reenter another value into this field and post the return.
• FOB and Ship-Via information are not transferred to PO
When you are creating Purchase Orders from Order Entry, you fill discover that the FOB Point and Ship-Via fields will not be auto-populated. The reason is that FOB and Ship-Via belong to Purchase Order Detail as part of the drop-ship. These two fields (FOB and Ship-Via) only are part of Purchase Orders header. Clicking on “Create P/O from O/E” will only carry over the OE Header Ship-to info to the PO detail drop-ship, which does not include the FOB or Ship-Via.
• Optional field is removed after changing Ship to Location
When changing the ship to location on an invoice, any Optional field(s) previously added are removed. This is seen in A/R where a customer has a ship-to location. This happens because once the Ship-to location information is updated the screen is refreshed and the data is not saved.
If you like our team here to review any of the designs listed, let us know via our Sage 300 ERP Feedback page.
