- FI-ES

Package/Miscellanies Settings (HQ Admin)
Item code Autogeneration
If item code Autogeneration is enabled, then system will create item code automatically
while creating an item. Once item code autogeneration is activated, we cannot deactivate this
feature.
Supplier code Autogeneration
If Supplier code Autogeneration is enabled, then system will create Supplier code
automatically while creating a Supplier. Once Supplier code autogeneration is activated, we
cannot deactivate this feature.
Customer code Autogeneration
If Customer code Autogeneration is enabled, then system will create Customer code
automatically while creating a Customer. Once Customer code autogeneration is activated, we
cannot deactivate this feature.
Alias
This setting is used to provide alternative names for shop and godown. There is an
interface in HQ admin to enter alias name for shop and godown.
Allow Integer Quantity
If this setting is enabled, we cannot enter decimal quantity in whole system.
Allow Duplicate Item code
In item maser, while creating an item, check whether the itemcode can duplicate. It is
applicable, if item code autogeneration is not set.
Allow Zero cost price
If this setting is enabled itemrare can be entered as 0 in Item master
Block adding new item to all shop and godowns
Normally while creating an item, it will automatically added to shop/godown in which that
particular item category is already added. If this setting is enabled, the items will not add to
shop/godown automatically
Reorder Level/Quantity Mandatory
We can set Reorder Level/Quantity in item master. If “Reorder Level/Quantity Mandatory”,
is enabled, then these fields will be mandatory.
Default Search field in Item fetching
Using this setting we can set default search field in item fetch interfaces in P&C.
Default Vendor in Purchase request
The vendor we set here will list as default in Purchase request.
Enable multiple Quotations from Request
If this setting is enabled, we can create multiple Quotations from a request. If this setting is
enabled “Close Purchase Request” checkbox will enable in purchase request. If we close this
purchase request, then it will not come in Quotation pending list.
Allow PO reference in other shipment detail
If this setting is enabled, in Purchase bill adding new item interface, “Pending PO items”
button will enable. If we press this button another interface will come. This interface contains the
PO items which are not done in a purchase bill. We can do the Purchase bill for this item
through this interface.
Allow to set Item price below cost price
If this setting is enabled, we can fix the selling price below cost price.
Back Date Process
If this is enabled, then we cannot change the package date to a back date.
Back no of days
Cannot modify the HQ transactions before this date.
HQ Confirmation on local purchase
This setting is used for the HQ authentication on local purchase. If this setting is enabled,
local purchase order needs to confirm by HQ. Otherwise local purchase bill cannot do. There is
one interface local purchase confirmation is available in P and C.
P and C DefaultsLocal Purchase confirmation
Auto confirm Account transaction
If this setting is enabled, the confirm check box will not visible in account transactions
interfaces and will automatically confirm the account transactions while saving itself.
Account Freeze date
We cannot add, edit or delete account entries on or before this date.
Active Directory Login
If this setting is enabled, the user who is in that network domain only can login to Magnolia.
Disable Data filters for customers in Reports
This setting is used to avoid customer data filters in reports
Disable Data filters for vendors in Reports
This setting is used to avoid vendor data filters in reports
Enable Itemwise Accounting in In-house Consumption
If this setting is enabled separate account can set for in-house consumption items. So the
amount will post on this account. So we can track In-house consumption amount. If In-house
account is set in item master it will take at in-house consumption if not account set at item
category will take. If account is not set in item category, then account will take from package
settings.
Shop Should Enter SL No in special Invoice
Normally for Serial No enabled items, Serial No will select at the time of special
Despatch(Godown). If this setting is enabled, serial no should select at the time of special
invoice(Shop) itself.
POS SHOP SETTINGS
1) Doratecheck
This shopsetting helps to decide whether to do sales (Cash /Credit/Godown Dispatch
Invoice) with the Item Selling Price below Cost Price.
For Doratecheck we can give the values 0 and 1.
 If doratecheck: =0, then the User will be able to sell an Item at any price greater than
zero.
 If doratecheck: =1, then the User will not be able to sell an item with price below Cost
price.
2) Getsalesperson
This Shopsetting helps the user to enable the Sales Person combo in POS Cash Sales,
Credit Invoice and Godown Dispatch Invoice cash and Credit.
For getsalesperson we can give the values 0 and 1.
 If get salesperson : =0, then the Sales Person Combo will be disabled in POS Cash
Sales, Credit Invoice and Godown Dispatch Invoice cash and Credit.
 If get salesperson : =1, then the Sales Person Combo will get enabled in the POS Cash
Sales, Credit Invoice and Godown Dispatch Invoice cash and Credit.
3) Default counter
By setting the Counter Login option in the Shop Master we can implement counter
Login in the shops created in Magnolia. If this option is set to true (i.e. ticked the Check box), we
need to assign the selling points i.e. POS Counters. For this purpose we need to create
Counters in Counter Master in HQ Admin.
After creating the counters we can assign the counter to a particular machine using the
Shopsetting file, which is available in each Shop (POS Folder in Magnolia Installation Path).
There is a parameter called Defaultcounter: =. Here we will set the integer values, which are
matching to the Counter Id. If we set 1 here means it is for the counter 1.
When the user login to POS, the system will pop up a small window for the counter selection.
Here the counter name and user name is written to the registry and the user is marked inside
the counter master table. This is done for preventing any another user login to the current
system and for preventing any other user in selecting the same counter from other systems. The
values are cleared when the user log off from the program.
If a shop is set to counter wise login, only the systems, which the counter is set, will be able to
login to POS. The HQ users will not be able to login to the POS because of this. In order to
avoid this difficulty if we set the Defaultcounter: = to 0, the system will allow to login from any
system to the POS.
4) SetFocusToQty
This shopsetting helps the continuous navigation of records in the List View.i.e for the
transactions like POS invoice etc if there is more than one Item in the List view from the Item
Details interface while navigating or clicking the OK button, instead of Item Details interface
getting closed will open the Item details interface of the next Item in the List view.
For SetFocusToQty we can give the values 0 and 1.
 If SetFocusToQty: =0, then the while navigating or clicking OK from one Item Details
interface, the Interface will get closed.
 If SetFocusToQty : =1, then the while navigating or clicking the OK button, instead of Item
Details interface getting closed will open the Item details interface of the next Item in the
List view.
5) GodownDesWithParentDep
This shopsetting helps the user to filter the godowns to be listed in the Godown
Dispatch cash / Credit.
For GodownDesWithParentDep we can give the values 0 and 1.
 If GodownDesWithParentDep: =0, then the while doing the Godown Dispatch Invoice
Cash /Credit , all the godowns in the Company having Item Stock will come in the List
view.
 If GodownDesWithParentDep: =1, then the while doing the Godown Dispatch Invoice
Cash /Credit , all the godowns coming under same Parent Department having Item
Stock will come in the List view.
6) AllowDiscandRateEditing
Normally the POS, Invoice and Godown Dispatch Invoice will not allow the user
to do both rate editing and giving Discount in sales. But using this shopsetting can enable that
feature.
For AllowDiscandRateEditing we can give the values 0 and 1.
 If AllowDiscandRateEditing: =0, then the System will allow the user to do only rate
Editing. The Rate editing will get enabled only if the rate editing option is enabled in the
Shop Master/Shop variables in HQ Admin for the particular Shop.
 If AllowDiscandRateEditing: =1, then the user will be able to do both rate editing and
giving Discount for an Item/ Sales.
7) LastPriceType
This Shopsetting helps the user to set the Selling Price for an Item while doing the POS
– Cash Sales, Credit Invoice and Godown Dispatch Invoice.
For LastPriceType we can give the values W and D.
Case 1:
Selling price should be greater than or equal to whole sales price.
doratecheck :=1 ,LastPriceType :=W
Case 2:
Selling price should be greater than or equal to discount price.
doratecheck :=1 ,LastPriceType :=D
Case 3:
Selling price can be any amount.
doratecheck: =0
Caution: But this case should be avoided as it enables the salesperson to enter any selling price
for any item.
Case 4:
Only a few items can be sold at any price.
Doratecheck: =1, LastPriceType: =W (or) LastPriceType: =D
Add those items which can be sold at any price as free items in a given shop.
8) BlockNegativeStock and NegativeStockpopup
This shopsetting is to decide whether to block the Item Stock getting negative or
not.
For BlockNegativeStock and NegativeStockpopup we can give the values 0 and 1.
Case 1:
BlockNegativeStock : =0 and NegativeStockpopup: =0
In this condition if we give a quantity more than the available Quantity, the system will allow the
user to continue.
Case 2:
BlockNegativeStock : =0 and NegativeStockpopup: =1
In this condition if we give a quantity more than the available Quantity, the system will allow to
continue the transaction.
Case 3:
BlockNegativeStock : =1 and NegativeStockpopup: =0
In this condition if we give a quantity more than the available Quantity, the system will block the
user to continue. Only when the transaction qty is less than or equal to the available quantity,
the user will be able to continue the transaction.
Case 4:
BlockNegativeStock: =1 and NegativeStockpopup: =1
In this condition if we give a quantity more than the available Quantity, the system will block
the user to continue and a popup message will appear.
In this message if we click yes, then the user can continue with the quantity
entered. And if the user Click NO then only when the transaction qty is less than or equal to the
available quantity, the user will be able to continue the transaction.
9) AllowMoreQtyInGoodsArrival
This shopsetting helps to decide whether to accept more Quantity than the Dispatched
quantity in Shop Goods arrival.
For AllowMoreQtyInGoodsArrival we can give the values 0 and 1.
 If AllowMoreQtyInGoodsArrival: =0, then the System will not allow the user to accept
more quantity than the Dispatched Qty in Shop Goods Arrival.
 If AllowMoreQtyInGoodsArrival: =1, then the System will allow the user to accept
more quantity than the Dispatched Qty in Shop Goods Arrival.
10) PosImage
This shopsetting helps the user to decide whether to show the Fi-es Image in the Pos
Cash Sales list view or not as shown below.
For PosImage we can give the values 0 and 1.
 If PosImage: =0, then the Cash Sales list view will not show the Fi-es Image.
 If PosImage: =1, then the Cash Sales list view will show the Fi-es Image.
11) CustomerCreditLimitCheck
To prevent raising a credit invoice if the credit sales amount exceeds the Credit
Limit of the customer that is set in the Customer Master.
For PosImage we can give the values 0, 1 and 2.
 CustomerCreditLimitCheck :=0
It should not check for customer credit limit. Invoice should get saved even if the credit
limit exceeds for that particular customer.
 CustomerCreditLimitCheck :=1
Customer Credit limit check should be there. An YES/NO message box "Credit limit
exceeded for this customer. Are you sure to continue anyway?" should pop up.
 CustomerCreditLimitCheck :=2
Should not allow saving the invoice. Should display a message “Credit Limit exceeded
for this customer"
12) DefaultGodowns
This setting is related with Godown Dispatch Invoice. Generally, items can be
dispatched from any of the godowns comes under same department. DefaultGodowns setting is
used to restrict the list of Godowns from where the items can be dispatched.
For instance, the setting [DefaultGodowns :=1,4,5] allows the shop to dispatch the item from
only the Godowns 1, 4, and/or 5.To avoid this checking set DefaultGodowns to 0.
13) CreditDoRateCheck and CreditLastPriceType
This shopsetting is for setting lower limit for Item Rate in Credit Invoice. Check the
option "Separate Item Rate Checking Rules for Credit Invoice" at HQ (In Shop Variables) then
only you will get
the setup i.e."Separate Item Rate Checking Rules for Credit Invoice" in Credit Invoice. Refer
the below flow chart for getting more details.
14) RateUptoShopDisc
This Shopsetting helps the user to block giving Discount for a bill only upto Shop
Discount which is given in the Shop Master in HQ Admin.
For RateUptoShopDisc we can give the values 0 and 1.
 If RateUptoShopDisc: =0 then the user will be able to give Discount based on the
setting given for doratecheck and LastPriceType.
 If RateUptoShopDisc: =1 then the system will allow the user give discount upto the
Shop discount given in the Shop Master in HQ Admin.
15) BlockWildcardItemFetch
This Shopsetting helps the user to hide the wildcard fetch in the POS cash sales or
not in the POS Module.
For BlockWildcardItemFetch we can give the values 0 and 1.
 If BlockWildcardItemFetch: =0 then the wildcard fetch frame in the POS Cash Sales
interface will be visible to the User.
 If BlockWildcardItemFetch: =1 then the wildcard fetch frame in the POS Cash Sales
interface will get hided.
16) Billamounthide
This Shopsetting helps the user to decide whether to hide the Bill Amount column in
the POS Cash Sales master grid.
For Billamounthide we can give the values 0 and 1.
 If Billamounthide: =0 then the bill amount column in the POS Cash Sales interface will
be visible to the user.
 If Billamounthide: =1 then the bill amount column in the POS Cash Sales interface will
be visible to the user
17) CashDrawer
This Shopsetting helps the user to specify the CashDrawer is available in the Shop or
not.
For CashDrawer we can give the values 0 and 1.
 If CashDrawer: =0 it means that the Cash Drawer is not available in the Shop.
 If CashDrawer: =1 it means that the Cash Drawer is available in the Shop.
18) ContinuousBilling
This shop setting is applicable in the POS Cash Sales for loading the Item Details
interface immediately after saving one sales.
For ContinuousBilling we can give the values 0 and 1.
 If ContinuousBilling: =0 then while saving a Cash Sales the POS Master Grid
 If ContinuousBilling: =1 it means that the Cash Drawer is available in the Shop.
19) Maxsaleqty
This Shopsetting helps the user to decide how much Quantity a Shop can sale per
cash sales.
For Maxsaleqty we can give the values any number greater than or equal to zero.
 If Maxsaleqty: =0 Can sale any no: of Quantity.
 If Maxsaleqty: =1 Can sales only one Quantity per Cash Sales.
 If Maxsaleqty: =5 Can sales 5 Quantity per Cash Sales.