The setup for Analysis Codes is accessible from Administration > Setup > Eralis Job > Transaction Attributes > Job Analysis sub-menu.
The intention behind analysis codes is to provide the facility to add additional properties to the transactions recorded against a job. These analysis code properties can then be used in reporting, filtering and grouping transactions to further analyze jobs and subjobs. Each transaction, starting from a quote, can be assigned two analysis codes. UDFs (User Defined Fields) for analysis 1 and 2 codes have been added to SAP Business One marketing documents to allow values to be passed into Eralis Job, or for values to be passed to the marketing documents from Eralis Job.
Analysis 1 and 2 values can be created is such a way as to make them company wide, or they can be created so that they are only available for transactions linked to specific job. Analysis 2 values can also be created so that they are independent of analysis 1 values, or linked to an analysis 1 value. If analysis 2 values are linked to an analysis 1, values are filtered to only display the linked values when the specific analysis 1 value is selected. There are several uses for the analysis codes especially around reporting and filtering within the system. Another key area where they are used is in the grouping functions within quotes and the consolidated invoice functions in invoicing. With the grouping and consolidation functions, the system can effectively cater for additional levels of job structure below the standard master job and subjob structure.
On the Item Master screen, UDFs have been added to allow default analysis 1 and 2 codes to be assigned. When the item code is used on a job transaction, the system will automatically populate the analysis code fields with the default values. These can be altered if required. On the master job footer, a button Analysis Codes exist which allows the user to create analysis codes specifically for that job. Analysis codes created in this manner will not be available for selection on job transactions not linked to the specific job.
Article is closed for comments.