Monthly Archives: July 2011

#17 Advantage and Disadvantage of ERP

Date: 24 July 2011

Enterprise resource planning (ERP) integrates internal and external management information across an entire organization, embracing finance/accounting, manufacturing, sales and service, customer relationship management, etc. ERP systems automate this activity with an integrated software application. Its purpose is to facilitate the flow of information between all business functions inside the boundaries of the organization and manage the connections to outside stakeholders

Advantage and Disadvantage



Integration can be the highest benefit of them all. The only real project aim for implementing ERP is reducing data redundancy and redundant data entry. If this is set as a goal, to automate inventory posting to G/L, then it might be a successful project. Those companies where integration is not so important or even dangerous tend to have a hard time with ERP. ERP does not improve the individual efficiency of users, so if they expect it, it will be a big disappointment. ERP improves the cooperation of users.


Generally, ERP software focuses on integration and tends to not care about the daily needs of people. I think individual efficiency can suffer by implementing ERP. The big question with ERP is whether the benefit of integration and cooperation can make up for the loss in personal efficiency or not.

Cost reduction

It reduces cost only if the company took accounting and reporting seriously even before implementation and had put a lot of manual effort in it. If they didn’t care about it, if they just did some simple accounting to fill mandatory statements and if internal reporting did not exists of has not been financially-oriented, then no cost is reduced.

Fewer personnel

Same as above. Less reporting or accounting personnel, but more sales assistants etc.


No. People are accurate, not software. What ERP does is makes the lives of inaccurate people or organization a complete hell and maybe forces them to be accurate (which means hiring more people or distributing work better), or it falls.



This entails software, hardware, implementation, consultants, training, etc. Or you can hire a programmer or two as an employee and only buy business consulting from an outside source, do all customization and end-user training inside. That can be cost-effective.

Not very flexible

It depends. SAP can be configured to almost anything. In Navision one can develop almost anything in days. Other software may not be flexible.


Leave a comment

Posted by on July 24, 2011 in ERP


Tags: ,

#16 Accpac Finder

Date: 17 July 2011

The Finder is a pop-up window that displays records in a column format for a view. Records are displayed in one of two formats, selected by the user. The user can also select the order for record display. If desired, the caller can provide a filter to restrict the records displayed by the Finder.

Uses of the Finder
The Finder can be used for:

Inquiry In this case, the Finder provides a detailed list of items. The user can select the fields to be displayed by the Finder.
Searching In this case, the user chooses the Finder button to initiate the search for a specific item. The selection is placed in a buffer and the Finder is terminated. For this purpose, the Finder should be started modally by the calling program, so that no further work can be done by the caller until a selection has been made.
Selection In this case, the Finder selects an item to be operated on by another object. After the item has been selected, an object is started, and the selection is passed to it. After the object has been started, the Finder can either remain or terminate. If the Finder remains, the object started by the Finder is modeless. Subsequent Finder selections can be made and further instances of the object started. The objects started can be either peers or children of the Finder. If an object started is a peer, the user can terminate the Finder, but any other objects started by the Finder will not be terminated. If an object started is a child of the Finder, terminating the Finder causes all the Finder’s children to also be terminated.
If the Finder terminates after starting an object, the object obviously must have been started as a peer. The Finder provides the primary key for the selected item in the key area of the object that is started. It is also possible for the caller to provide a user area to be passed to the object started by the Finder.

Following is the code to call the finder that will show the item form ICITEM table in Accpac

Private Sub Cmditemfrm_Click()
Dim fnd As AccpacFinder.ViewFinder
Set fnd = New AccpacFinder.ViewFinder
fnd.Session = AccpacSession
fnd.ViewID = “IC0310”
fnd.DisplayFieldIDs = Array(7, 3, 5, 1, 8 )
fnd.ReturnFieldIDs = Array(7, 3)
fnd.Filter = “” ‘condition here
fnd.AutoTabAway = False
If fnd.Finder = True Then
‘Code here
End If
End Sub


1 Comment

Posted by on July 17, 2011 in Accpac Macro, Accpac Support, Sage Accpac


Tags: , , ,

#15 Accpac Views Protocol for INSERTING and UPDATING Data

Date: 10 July 2011

When we are using Accpac views to insert data into Accpac most of the validation it does by itself. This is one of the most important reasons, why we need to use Accpac views to insert or update data into Accpac Database.

The protocol that Accpac follows while doing Insert is as follows:
1. If the next header number is generated by the view, Put zero in the header number field and use Init to generate the next available header number. If the header number is specified by the caller, use Init to initialize the fields of the header, then Put the header
number in the header view.
2. Put the fields in the header.
3. Init detail to initialize the fields.
4. Put zero into the detail number field to insert from the start.
5. Put values in the other detail fields.
6. Verify detail. (Optional.)
7. Insert detail.
8. Go to step 5 until no more detail.
9. Verify header. (Optional.)
10. Insert the header. (This will do a Post of the details.)

Protocol for updating the data in Accpac is as follows (Including deleting the details):
1. Put header key into header view.
2. Read or Browse/Fetch the header view to get to the header.
3. Put the fields to be updated in the header view. (Optional.)
4. Put detail key into the detail view.
5. Read or Browse/Fetch the detail view to get to the detail.
The header number in the detail view should have been set by the header (because of the explicit composition).
6. Put the fields to be updated in the detail view.(Optional.)
7. Verify the detail. (Optional.)
8. Update or delete the detail.
9. Go to step 4 to process another detail.
10. Verify the header. (Optional.)
11.Update the header. (This will do a Post of the details.)

Browse/Fetch is the functions that help us to navigate through the data. Browse property do not have the “Where” or “Having” clause so we can use if condition to filter our data.


Leave a comment

Posted by on July 10, 2011 in Accpac Macro, Sage Accpac


Tags: ,

#14 Filtering Optional Field Values on Crystal Report from Accpac Database

Date: 03 July 2011

Recently I came to know that some of my colleagues and crystal report writers are facing issues at the time of fetching the optional fields form the Accpac database and showing it on the reports. It is may be because the way Accpac keeping the entries in the Database. Ok, now lets see how Accpac maintaining the optional fields and how we can easily filter it into our reports.

When we create any optional field, Accpac create a new entry in the optional field table. Let’s take Inventory control there is the master table “ICITEM” where all items will be saved. Now if we want to attach optional fields with the inventory then first we have to create optional fields from the Common Services “Optional Fields” form. Optional fields and there values will be stored in the optional field table “CSOPTFH” and “CSOPTFD” table. Further when we link it to inventory control module this information save into “ICOFD” table. Now at the time of creating new item we attach already created optional field with the new item and assign optional field value to it. Then, Accpac will store optional field values for each item in “ICITEMO” table with respective item numbers. I will try to explain this by diagrammatic representation:

From the above structure we can figure it out that In “ICITEMO” table the Item and optional field are coming from “ICITEM” and “ICOFD” tables.

Now the problem comes when we are trying fetching this information on the crystal report table where we have to show Optional fields horizontally. If we are putting condition like where optional field is equal to OPT1 then it will not bring OPT2 value on the report and if we not give any condition then it will duplicate the record. To solve this dilemma use duplicate tables instead of trying to retrieve data from one table. Here I am talking about “ICITEMO” table.

For example we need crystal report as follows

Here we can see that optional value one and two for each item is coming in front of respective item. How to do this easily? Let’s see. We know that the optional values are coming from one table “ICITEMO”. So we need to attach this table on the report and link it with “ICITEM”. But as I stated earlier if we give the condition for the optional value then either some optional value will not come or it will duplicate the data. Now to solve this, make and link alias of “ICITEMO” table on crystal report. Take as many number of “ICITEMO” tables as optional fields are. Like, here two optional values are there so we will take the Alias of “ICITEMO” table two times. Further we put the condition for each optional field with separate table. Let’s see how. Following is the crystal report link screen:

Here we can see that the ICITEMO table is used twice and linked to the “itemno” column of “ICITEM” table. Now this is how we can create the alias of the same table with different alias names. Here it is “ICITEMO” and “ICITEMO_1”. We can also give the alias name as the name of the optional field to make it easy. Just note down here that each alias is going to give one optional field value. Now after making such kind of link we have to set the condition also to retrieving the right value. So we will put the condition for each alias.

Now see the fig above, we can see that we are putting the condition that opt1 value should match with “ICITEMO” table and OPT2 should match with “ICITEMO_1” table. After doing this report is ready only we need to put right field at right place.

Like this we can take Optional value one from table “ICITEMO” and optional value two from “ICITEMO_1”.

Hope that this post will help the people how to take optional fields and make the report right. Further to add every person has its own way of doing things and each of them thinks he is right. But I want to say the option that I am giving will solve your problem and this is the easiest way among the couple of other solutions that I have. Even thought if any of you have any better one please comment and share with us.


%d bloggers like this: