Sage 300 ERP – Tips, Tricks and Components

In Sage 300, you can restrict posting of OE Order Entry, OE Shipment Entry and OE Invoice Entry for particular customer by keeping the status ‘Inactive’ in Customer Master Screen. But, it will also restrict posting of Order Entry.

For one of our client, we required to restrict only posting of OE Shipment and OE Invoice. And for this purpose, we did customization on OE Shipment and OE Invoice Screen.

Now, we will see how to restrict Shipment entry and Invoice Entry from being posted (Refer the below Screen)

Steps that we need to follow –

User will create an Optional field “RESTRICT” and its type will be Yes/No. This will be applicable for both OE Shipment and OE Invoice.

User needs to map this optional field to customers from customer master screen to whom the user wants to restrict, as shown in the below Screenshot:

At the time of posting OE Shipment Entry or Invoice Entry, if the system found Optional field’s value “YES” from customer master screen then posting of OE shipment or OE Invoice will get restricted and error message will be displayed that ‘Customer is restricted for Posting’ and if system found Optional field’s value “No” then OE shipment or OE Invoice will get posted successfully.

Hence with the help of this customization, User can add a restriction on posting of OE Shipment Entry and OE Invoice Entry.

Sage 300 ERP comes with various factors and features to maintain the data and integrity of the organization. We are now almost aware about the customization that can be done in Sage 300 ERP that makes it easier and organization oriented. One such customization we have already seen is a customization done on Order Entry and Shipment Screen which has a ‘Ship Commit All’ button. In our previous blog ‘Ship Commit All in OE Shipment’ we have seen the working and functionality of the button. It gets the quantity from Quantity committed to Quantity shipped column and ships only the committed quantity irrespective of the quantity ordered.

We have further customized this screen as per one of our client’s requirement to restrict and allow some features based on the template codes. In this customization, we define a template that decides the detail line items. For e.g.: if we have a Template code defined as ‘SPTEMP’, then entering a miscellaneous charge in the detail line is mandatory. We have restricted our screen in such a way that it does not allow to post unless a Miscellaneous charge is entered in the detail line if desired template code is present. You can refer the screenshot below:

Here, we have entered an Order number on Shipment screen with our required Template code ‘SPTEMP’. Now as per customization when we click on Post button, the functionality will prompt the user to enter valid template code or to enter a misc. charge on the detail line. This will also restrict the user to post the entry without the entering the required data.

The prompt Error screen will be as follows:

Also, we have further small customization on the screen, to display the total quantity shipped on the OE Shipment entry. This can be useful for display purpose of total quantity irrespective of item and locations.

In Sage 300, user can have ability to change the password on the login page from Web version as well as from Classic desktop version.

Sage 300 Login Screen

As per the existing process of change password, Sage 300 user need to click on these options to change password from Login window. Once user clicked on change password button, another window will populate to get all the information regarding old and new password with USER ID.

In Classic desktop version, Sage 300 user can see the option below to insert the information in order to change password from login window.

Same screen is getting populated in cloud version of Sage 300c

Login Screen populated in cloud version of Sage 300c

All the details have been compulsory and user need to provide the same in order to change the password from login window.

USER ID: These values have been populated automatically based on USER ID which has been present in background.
Old Password:
- User need to enter existing Sage 300 password of that USERID for which they want to change password.
- Validation has been present on this field if old password is wrong then it won’t allow you to change the same.
New Password: User need to enter new password in this text box.
Confirm New Password: User need to re-enter the new password in the confirm new password field.

About Us

Greytrix a globally recognized Premier Sage Gold Development Partner is a one stop solution provider for Sage ERP and Sage CRM needs. Being recognized and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third party add-on development and implementation expertise.

Greytrix offers unique GUMU integrated solutions of Sage 300 with Sage CRM, Salesforce.com and Magento eCommerce along with Sage 300 Migration from Sage 50 US, Sage 50 CA, Sage PRO, QuickBooks, Sage Business Vision and Sage Business Works. We also offer best-in-class Sage 300 customization and development services and integration service for applications such as POS | WMS | Payroll | Shipping System | Business Intelligence | eCommerce for Sage 300 ERP and in Sage 300c development services we offer services such as upgrades of older codes and screens to new web screens, newer integrations using sdata and web services to Sage business partners, end users and Sage PSG worldwide. Greytrix offers over 20+ Sage 300 productivity enhancing utilities that we can help you with such as GreyMatrix, Document Attachment, Document Numbering, Auto-Bank Reconciliation, Purchase Approval System, Three way PO matching, Bill of Lading and VAT for Middle East.

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

There was a very unique but interesting requirement from one of our clients. The requirement was to provide filter on Item description column on the detail level order entry grid to modify only those records which are getting matched with item description filter. Once we remove the filter, all the records should be display into the detail grid with modified records as well.

New Stuff:- Change password from Login page in Sage 300

We have incorporated these requirements on the standard Order entry page of Sage 300c version. Please find the screen shot below of Order entry page.

We have filtered the Order Entry standard grid based upon the Item description criteria. Also, the user will be able to update the Items in the grid. In the item description textbox control, the user can specify/set the filter criteria. When user will check ‘Show All Item’ checkbox and clicks on the ‘Filter’ button then all details lines are getting displayed in the single page and filters the records against the filter criteria supplied. When the user clicks on the clear button all filter conditions are getting removed and it display all details lines.

The same customization can be possible for other transaction screens like IC, AR, AP, PO etc.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

Sage 300 web screens support multiple regional languages. It is utilizing the resource files (Resx files) to maintain localize setting like strings, text, captions, messages etc. These resource files (Resx files) are supported by Microsoft’s Resource manager class which is present in the Sage 300 web screen.

New Stuff:- Sage 300C Grid filtration for Transaction Screens

We have described below the supported language of the Sage 300 web screen:

English (en-US) (i.e. MenuResx.resx)
Chinese Simplified (zh-Hans) (i.e. MenuResx.zh-Hans.resx)
Chinese Traditional (zh-Hant) (i.e. MenuResx.zh-Hant.resx)
Spanish (es) (i.e. MenuResx.es.resx)
French (fr-CA) (i.e. MenuResx.fr-CA.resx)

In which, English language is default language and local extension of Sage 300 web screen are to be considered the English Resx files.

In Sage 300c every module has their own resource files which is present into the resource DLL file.

User can select the language while creating the solution and project of Sage 300c web screen. Below is the wizard screen by using developer can decide in which language resource file need to be generate while creating a solution project for Sage 300 web screen

About Us:-

Greytrix – a globally recognized Premier Sage Gold Development Partner is a one-stop solution provider for Sage ERP and Sage CRM needs. Being recognized and rewarded for multi-man years of experience, we bring complete end-to-end assistance for your technical consultations, product customizations, data migration, system integrations, third-party add-on development and implementation expertise.

Greytrix caters to a wide range of Sage Enterprise Management (Sage X3) offerings – a Sage Business Cloud Solution. Our unique GUMU integrations include Sage Enterprise Management (Sage X3) for Sage CRM, Salesforce.com and Magento eCommerce along with Implementation and Technical Support worldwide for Sage Enterprise Management (Sage X3). Currently we are Sage Enterprise Management Implementation Partner in East Africa, Middles East, Australia, Asia. We also offer best-in-class Sage X3 customization and development services, integrated applications such as POS | WMS | Payment Gateway | Shipping System | Business Intelligence | eCommerce and have developed add-ons such as Catch – Weight and Letter of Credit for Sage Enterprise Management to Sage business partners, end users and Sage PSG worldwide.

Greytrix is a recognized Sage Rockstar ISV Partner for GUMU Sage Enterprise Management – Sage CRM integration also listed on Sage Marketplace; GUMU integration for Sage Enterprise Management – Salesforce is a 5-star app listed on Salesforce AppExchange.

For more information on Sage X3 Integration and Services, please contact us at x3@greytrix.com. We will be glad to assist you.

Sage has introduced a new feature on the web version of Sage 300c where user can get all the information about the organizations as it is working like a central location or Dashboard where user can monitor and analyze the performance of the business.

In that situation, Organizations has their own User authorization policy in which they want to hide or display the information to the User.

Sage 300c widget also working based on the standard User authorization of Sage 300 in which User can able to see only those widget information which is assigned by Organization in Sage 300 .

All widgets of Sage 300c has been working based on security access “Dashboard”. This security access currently present for three (3) modules of Sage 300 i.e. AP (Account Payable), AR (Account Receivable) and GL (General ledger).

->Each widget has been displayed summarize information based on the Sage 300 module.

For example:

1- Account Balances widget getting summarize information from General Ledger module that because all the account related information has been stored in General ledger module of Sage 300 ERP.

2- Top Vendor widget getting all top vendor names from Account Payable module so that Top vendor widget belonged to Account Payable module.

->In Sage 300 or Sage 300c, Sage has introduced security access name “Dashboard” by using Admin user can assign rights to user for enabling or disabling widget for Sage 300c.

->We have described below Sage 300c widget lists with included Sage 300 module lists so that reader can understand which module has been belongs to which widget of Sage 300c.

Admin user has a rights to use above User security access code “Dashboard” from Security Group screen to provide widget access to the users as per Sage 300 module wise.

Firstly, you need to create a security group id with grant security access code “Dashboard” or assign access to existing security group id. For example, we have created new security group id “WIDGET” for AP module and have checked the grant access code “Dashboard” only.

Then, assign this security group id to any particular user by using User authorization screen.

On the below screen, we have assigned “widget” group id to User id “TEST1” and Click to Save button.

Then, we have looked the rights for the userid “TEST1” by login into the Sage 300 cloud.

After logging with “TEST1” user, we only have access of AP module widget lists on the web screen of Sage 300c.

So using these simple steps you can do the administrative setting in Sage 300c.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

GUMU for Sage 100 ERP to Sage 300 ERP is a Sage certified Migration solution. Greytrix is a pioneer in providing migration services at its Sage Migration Centre and catering end-users business requirements. Data migration is always a challenging task to perform. We migrate data with the help of our Sage certified migration utility in accordance to our well defined migration process.

Here, in this post will discuss about some scenarios which we encounter while migration the data from Sage 50 US (Peachtree) to Sage 300 ERP.

Sage 50 US allows making payment against credit note. But as per the Sage 300 standard functionality, it will not allow making payment against credit note (-ve amount). So in our migration process, we handle this scenario as we apply debit note against payment applied on –ve amount in Sage 50.

In the below screen we can see that the payment is applied on credit note (refer below screenshot)

And in the below screenshot you can see that we have applied Debit note against –ve payment.

Like this way we migrate payment applied on credit note in sage 50 to Sage 300 ERP.

About Us

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

While migrating the data we come-up with multiple scenarios. So while migrating the data few scenarios we need to handle manually here we are sharing an example:

In the below screen screenshot you can see that an invoice entry without having any detail information. It has only sales tax amount.

While migrating the data such kind of scenarios we need to handle manually. Just because as per the Sage 300 functionality it will not allow us to enter the transactions without any detail information. So, for such kind of transactions we create an invoice entry in Sage 300 ERP as shown below:

Like this way we migrate above mentioned transaction from sage 50 to Sage 300 ERP.

About Us

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we will be discussing about opening and composing the OE Order Entry View using Sage 300 Advantage API method.

Below are the steps which will guide through opening and composing the OE Order Entry View.

New Stuff: Validate Sage 300 user Credentials

Step 1:

Include the Sage 300 Advantage DLL in the project.

Step 2:

Once the Advantage DLL is included, create the object of the Session.

Session _session = new Session();

Step 3:

Take the DB Link object and assign link to that object.

DBLink dBLink = null;

dBLink = session.OpenDBLink(DBLinkType.Company, DBLinkFlags.ReadWrite);

Step 4:

Open the views.

View view = dBLink.OpenView(“OE0520”);

View view2 = dBLink.OpenView(“OE0500”);

View view3 = dBLink.OpenView(“OE0740”);

View view4 = dBLink.OpenView(“OE0180”);

View view5 = dBLink.OpenView(“OE0526”);

View view6 = dBLink.OpenView(“OE0522”);

View view7 = dBLink.OpenView(“OE0508”);

View view8 = dBLink.OpenView(“OE0507”);

View view9 = dBLink.OpenView(“OE0501”);

View view10 = dBLink.OpenView(“OE0502”);

View view11 = dBLink.OpenView(“OE0504”);

View view12 = dBLink.OpenView(“OE0506”);

View view13 = dBLink.OpenView(“OE0503”);

Step 5:

Compose the views.

view.Compose(new View[6] { view2, null, view4, view3, view5, view6 });

view2.Compose(new View[6] { view, view9, view13, view10, view7, view8 });

view3.Compose(new View[1] { view });

view4.Compose(new View[2] { view, view2 });

view5.Compose(new View[1] { view });

view6.Compose(new View[1] { view });

view7.Compose(new View[1] { view2 });

view8.Compose(new View[1] { view2 });

view9.Compose(new View[1] { view2 });

view10.Compose(new View[3] { view2, view11, view12 });

view11.Compose(new View[1] { view10 });

view12.Compose(new View[1] { view10 });

view13.Compose(new View[1] { view2 });

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

CSQRY

CSQRY is the View CS0120. It basically takes SQL Query as the parameter to its Browse method and then returns the records via calls to Fetch. CSQRY is easy to execute general SQL statements through the Sage 300 API. This way we don’t need additional database credentials and don’t need to use an alternate API like ODBC.

New Stuff: How to open OE Order Entry View using Advantage API

Step 1:

Include the Sage 300 Advantage DLL in the project.

Step 2:

Once the Advantage DLL is included, create the object of the DBLink and open the “CS0120” using DBLink object.

DBLink dBLink = session.OpenDBLink(DBLinkType.Company, DBLinkFlags.ReadWrite);

View view = dBLink.OpenView(“CS0120”);

Step 3:

Pass the SQL Query in Browse method as string parameter.

view.Cancel();

view.Browse(“SELECT OPTFIELD FROM CSOPTFH (NOLOCK) WHERE TYPE = ‘1’”, true);

view.InternalSet(256);

Step 4:

Now we call the Fetch method to return the records.

List<string> optionalFieldList = new List<string>;

while (view.Fetch() == true)

{

for (int i = 0; i < _ view.Fields.Count; i++)

{

optionalFieldList.Add(view.Fields.FieldByIndex[i].Value);

}

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

As per the Business aspects sometimes it happens that you need to transfer the multiple stock from one location to the other location. Sage 300 has provision to record the stock transfers between physical inventory locations using I/C transfer screen.

I/C Transfer entry updates the item quantities status from another location without changing the total number of items in inventory.

We did the customization on IC transfer screen for one of our customers to make the transfer processed more simplified.

New Stuff:- How to use CSQRY using .NetAPI in C#

You can see the customized screen below. We have added From and To Location on user interface to simplified the selection.

You can see in above screen shot, we have mentioned From and To Location at header level so that, if user want to transfer multiple item between same locations then they can select the locations at header level only and can add item in detail level. Both the location from header level will get automatically applied on detail level. This will make user task easier.

This customization would be helpful when you want to transfer large number of items from one location to other.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

As we know Sage introduced new enhancements on old functionality with the release of new patches. Sage 300 recently released the product update 2 for the 2019 version of Sage 300. With this new features are introduced with web screen i.e. Job related document option in recurring Charges screen.

New Stuff:- Customization on Stock Transfer Location

To check the Job related document navigate to AR Customers -> Recurring Charges -> System will open AR recurring Charges Screen.

Once the screen get open user can click on “Create New” to create new document. Once user click on new button system will allow user to select the mandatory fields as well as allow to select the “Job Related” Document option”.

So, user can now perform the Job Related transactions from the web screen itself instead of going back to the desktop screen.

Note: If user installed Product Update 2, then user will need to re-configure the PORTAL database through Database Setup.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we will be looking on creating the Sage 300 ERP session using the Advantage API in C# .Net.

We will be looking into the steps to create the same.

New Stuff: Recurring Charges – Job Related Documents introduced in Sage 300 2019.2 Web Screens

Step 1:

Include the Sage 300 Advantage DLL in the project.

Step 2:

Once the Advantage DLL is included, create the object of the Session.

Session _session = new Session();

Step 3:

Create the session of Sage 300 by passing the valid credentials and Sage information.

_session.CreateSession(“”,”AS”,”AS3001″,”65″,”ADMIN”,”ADMIN”,”SAMLTD”, DateTime.Today);

The session is ready to be used for interaction with the Sage 300 ERP.T

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we will be looking on creating the Sage 300 ERP session using the COMAPI in C# .Net. Session is the basis to interact with Sage 300 which becomes tedious job for some developers when they do not have enough knowledge about the Sage 300 API. This will consume an one LanPak Users License per session.

We will be looking into the steps to create the same with a sample code.

New Stuff: Create New Session using Advantage API in C#

Step 1:

Include the Sage 300 COMAPI in the project.

Step 2:

Once the COMAPI is included, create the object of the Sage 300 session.

AccpacSession _accpacSession = new AccpacSession();

Step 3:

Initialize the session by passing the valid sage information.

_accpacSession.Init(“”, “AS”, “AS3001”, “65”);

Step 4:

Create the session of Sage 300 by using the Open function and passing the valid credentials.

_accpacSession.Open(“ADMIN”,”ADMIN”,”SAMLTD”, DateTime.Now, 0, “”);

The session is created and ready to be used for interaction with the Sage 300 ERP.T

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we will be looking on creating the Sage 300 ERP session using the XAPI in C# .Net. When creating the integration with other systems or using Import/Export Programs, session is the basis to interact with Sage 300 which becomes tedious job for some developers when they do not have enough knowledge about the Sage 300 API. This will consume one IAP User License per session.

We will be looking into the steps to create the same with a sample code.

New Stuff: Create New Session using COMAPI in C#

Step 1:

Include the Sage 300 XAPI Library in the project.

Step 2:

Once the XAPI Library is included, create the object of the Sage 300 XAPI session.

ACCPACXAPILib.xapiSession _xapiSession = new ACCPACXAPILib.xapiSession();

Step 3:

Create the session of Sage 300 by using the Open function and passing the valid credentials.

_xapiSession.Open(“ADMIN”,”ADMIN”,”SAMLTD”, DateTime.Today, 1);

The session is created and ready to be used for interaction with the Sage 300 ERP.T

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we are going to see how we can create the Sage 300 finder using the COMAPI in C# .Net.

This would be a useful to create a finder on custom projects.

Below are the steps which will guide through how we can create the Sage 300 finder.

New Stuff: Create New Session using XAPI in C#

Step 1:

Include the Sage 300 COMAPI and Sage 300 Finder DLLs in the project.

Step 2:

Once the DLLs are included, create the object of the ViewFinder.

ViewFinder afinder = new ViewFinder();

Step 3:

Now we will assign a value to “Session”, “ViewID”, “InitKeyValue”, “InitKeyType”, “ReturnFieldIDs”, “DisplayFieldIDs” and “SearchFieldIDs” properties.

int[] DispArr = new int[5] { 1, 10, 4, 3, 24 }; // the array of field IDs that will be displayed in the finder’s columns.

int[] SearchArr = new int[5] { 1, 10, 4, 3, 24}; //the array of field IDs that will be used to search in the finder records.

afinder.Session = accpacDBLink.Session;

afinder.ViewID = “AP0015”;

afinder.InitKeyValue = “1200”;

afinder.InitKeyType = 1;

afinder.ReturnFieldIDs = 1;

afinder.DisplayFieldIDs = DispArr;

afinder.SearchFieldIDs = SearchArr;

Step 4:

Open the Finder

afinder.Finder();

Step 5:

Now we call the ReturnFieldValues property to return the selected field.

MessageBox.Show(afinder.ReturnFieldValues.ToString());

So using this code we can create a Finder using COMAPI.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we are going to see use of an existing Sage 300 ERP session with Advantage API in C# .Net. We have already seen about “Create New Session using Advantage API in C#” in our earlier blog. Since we already know that session is must to interact with Sage 300 and for some developers when they do not have enough knowledge about the Sage 300 API it becomes tedious job to use the same. We will be looking into the steps for using it with C# .Net Code.

New Stuff:- How to Create the Finder using COMAPI in C#

Step 1:

Include the Sage 300 Advantage DLL in the project.

Step 2:

Once the Advantage DLL is included, create the object of the Session.

Session _session = new Session ();

Step 3:

Initialize the session object with Sage 300 ERP.

_session.INit(“”, “AS”, “AS3001”, “65”);

Step 4:

Check whether session is already open. Open the session only if currently not available.

if (!_session.IsOpened)

_session.Open(“ADMIN”,”ADMIN”,”SAMLTD”, DateTime.Today, 0);

The application will not open the new session and use the existing session. If there is no session available only then new session will get open to connect the object of Sage 300 ERP.

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In this blog, we are going to define the use of an existing Sage 300 ERP session with COMAPI in C# .Net. We have already seen about “Create New Session using COMAPI in C#” in our earlier blog. Since we already know that session is must to interact with Sage 300 and for some developers when they do not have enough knowledge about the Sage 300 API it becomes tedious job to use the same. This will be using an existing License and not consume an additional LanPak Users License per session. We will be looking into the steps for using it with C# .Net Code.

New Stuff: How to use existing session using Advantage API in C#

Step 1:

Include the Sage 300 COMAPI and Session Manager in the project.

Step 2:

Once the COMAPI is included, declare the variable for SingonID and Session. Create the object of Session Manager.

AccpacSession _accpacSession;

int lSignonID = 0;

AccpacSessionManager.AccpacSessionMgr accpacSessionMgr = new AccpacSessionManager.AccpacSessionMgr();

Step 3:

Pass the Sage 300 information and use the existing session to connect to Sage 300 ERP.

accpacSessionMgr.AppID = “AS”;

accpacSessionMgr.ProgramName = “AS3001”;

accpacSessionMgr.ServerName = “”;

accpacSessionMgr.AppVersion = “65”;

accpacSessionMgr.CreateSession(“”, ref lSignonID, out _accpacSession); The application has now connected to existing session of Sage 300 ERP and ready to be used for interaction

About US:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

As we all are aware that Sage 300 stores the Audit Date and Audit Time in the SQL tables. Many times there are necessity to check the audits for organizational purpose but user cannot identify the time stored in the table due to its structure. We will be discussing the conversion of the time and date to the format user requires in this blog.

New Stuff:- How to use existing session using COMAPI in C#

In Sage 300 AUDTTIME and AUDTDATE are the fields in which you will get the date and time where all transactions are posted/updated in Sage 300. The fields are only accessible from SQL tables and not available on the screens.

Audit Date/Time:

In the SQL Audit date is stores in the yyyyMMdd format. If a user wants to format the date into the date and time format, so we provided an example of date type conversion for Sage 300 date fields.

Sage 300 ERP SQL Date / Time Conversion:

SQL Server allows us to set up custom user-created queries. You can run the following query then you can get output like “30/07/2019 16:03:32”

SQL Query:

select

DATEADD(mi, DATEDIFF(mi, GETUTCDATE(), GETDATE()),

CONVERT(VARCHAR(10),CONVERT(Date,CONVERT(VARCHAR(8),AUDTDATE))) + ‘ ‘ +

LEFT(LEFT(Right(‘00000000’ + Convert(varchar(8),AUDTTIME),8),4),2) + ‘:’ +

RIGHT(LEFT(right(‘00000000’ + Convert(varchar(8),AUDTTIME),8),4),2)

+ ‘:’ + RIGHT(LEFT(right(‘00000000’ + Convert(varchar(8),AUDTTIME),8), 6) ,2)

)

from tablename

Audit Time:

GMT format of the Audit time:

In sage 300 AUDTIME is based on GMT format, if user wants to translate the AUDTIME in a different time zone, the user will need to revise the SQL statement. We have converted the GMT time format into the Central Time zone. Refer the below SQL query for the Central Time zone.

Example :

Standard AUDTIME format is : 10333254 (10:33:32 GMT)

After running the query below you get an output like : 16:03:32 IST

SQL stmt to format AUDTIME :

select

LEFT(CONVERT(time,DATEADD(HOUR,5,DATEADD(MINUTE,30,(LEFT(LEFT(Right(‘00000000’ + Convert(varchar(8),AUDTTIME),8),4),2) + ‘:’ + RIGHT(LEFT(right(‘00000000’ + Convert(varchar(8),AUDTTIME),8),4),2)))),103),5)

+’:’+

RIGHT(LEFT(right(‘00000000’ + Convert(varchar(8),AUDTTIME),8), 6) – 60000,2)

RECTIME

from tablename

About Us:-

For more details on Sage 300 and 300c Services, please contact us at accpac@greytrix.com. We will be glad to assist you.

In Sage 300, IC shipment Entry screen used to keep record of shipments of items out of inventory from the Respective Location with the details of the Item Number, Item Description, Quantity, unit price, etc. But as per standard functionality users can create IC Shipments transaction without selecting customer number. One of our client requested to restrict the IC shipment & Return posting if user fails to enter customer number.

So we did the customization as per request and had restricted the posting of IC shipment entry and IC Return Entry. So whenever user tries to post or save IC Shipment entry or IC Return entry, it gives a warning message that ‘Customer Number should not be blank’

Refer below screen shot for your reference

Note: – Validation will work for both Transaction type, IC shipment & IC return entry

Using this validation/customization user can print the transactions details along with Customer information
User can keep a record out of inventory transaction history done against the customer
Suppose the user has created shipment Entry transaction with customer number but at the time return entry transaction if the user done the transaction without customer then it will show the mismatch inventory report but using this validation it is Mandatory to put the customer details and avoid this type of issues.

Validation on OE Shipment Entry Screen and OE Invoice Entry Screen

Miscellaneous Charge/Template requirement on Ship Commit All Customization in OE Shipment

Change password from Login page in Sage 300

Sage 300C Grid filtration for Transaction Screens

Sage 300c Web Screen Supported Regional Language

Display Widget based on User authorization wise in Sage 300c

Payment applied against credit note in Sage 50 is migrated as Debit Note in migration process

Migrate invoice created with only sales tax amount in Sage 50 to Sage 300 ERP

How to open OE Order Entry View using Advantage API

How to use CSQRY using .NetAPI in C#

Customization on Stock Transfer Location

Recurring Charges – Job Related Documents introduced in Sage 300 2019.2 Web Screens

Create New Session using Advantage API in C#

Create New Session using COMAPI in C#

Create New Session using XAPI in C#

How to Create the Finder using COMAPI in C#

How to use existing session using Advantage API in C#

How to use existing session using COMAPI in C#

Date/Time type conversion for Sage 300 date fields

Restrict users for posting of IC shipment and IC Return Entry for blank customer number