Business objects are self-contained components of SYSPRO business logic that can be used to build custom solutions. They communicate using XML and are accessible through the SYSPRO program folder via the e.net load balancer.
Explore the core of SYSPRO’s flexibility through its Business Object Library, a crucial toolset for developers aiming to customize and extend the functionality of SYSPRO software. Business objects are components of SYSPRO’s business logic, encapsulated independently from the user interface. These objects enable developers to use them as standalone building blocks or integrate them into larger systems without being tied to a specific user interface.
This design ensures that business objects are both flexible and powerful, suitable for creating sophisticated solutions tailored to specific business needs.
The individual business objects are grouped together into mini-modules called functional areas, for licensing purposes.
A module can have one or more functional areas (e.g. the Inventory module has seven functional areas. This enables you to license only the functionality that you require.
To license a functional area you must already have the matching SYSPRO module installed.
Some functional areas (e.g. e.net System Query Functional Area, e.net System Posting Functional Area and the e.net System Setup Functional Area) are licensed automatically with the e.net System Manager.
Classes
Utilities – used for logging on/off, retrieving preferences and calling standalone programs.
Query – these do not update or change the underlying database. They simply retrieve data, often applying business rules to the returned information. Business objects that are part of the query class only require one XML string.
Setup – used to create semi-static items such as stock codes and customers. Business objects that are part of the setup class require two XML strings, the parameter string and the document string.
Transaction – used to post transactional data line inventory movements, sales orders and producing invoices. Business objects that are part of the transaction class require two XML strings, the parameter string and the document string.
Methods
Each class contains several methods.
Utilities class:
Logon – to logon to e.net Solutions
Logoff – to logoff from e.net Solutions
GetLogonProfile – to retrieve information about the currently logged on session
Run – to run a NetExpress program
Query class:
Browse – to generically browse columns from a table
Fetch – to generically return all rows from a specified column in a table
Query – to access query-type business objects
NextKey – to generically retrieve a key alphabetically higher than an existing key
PreviousKey – to generically retrieve a key alphabetically lower than an existing key
Setup class:
Add – to add single or multiple items with a single call
Update – to change single or multiple items with a single call
Delete – to delete single or multiple items with a single call
Transaction class:
Build – to retrieve information helpful during the post
Post – to post transactions
Like SYSPRO programs, business objects have a six character program name.
The first three characters consist of a module code (e.g. INV is the module code for the Inventory control module). If the business object is not related to a specific module, then the first three characters will be COM.
The fourth character contains one of the following:
Q – Query business object
S – Setup business object
T – Transaction Posting business object
R – Retrieve/Build business object
U – Utility business object
The remaining two characters are a short mnemonic indicating the business object function. Note that the primary query in each module contains the three character suffix QRY.
For example:
| Program name | Method | Notes about program function |
|---|---|---|
| INVQRY | Query.Query | Inventory Query business object |
| INVQAT | Query.Query | Inventory ATP Query business object |
| ARSSCS | Setup.Add | A/R Customer maintenance Setup business object |
| INVTSC | Transaction.Post | Inventory Stock Take Transaction Posting business object |
| SORRSH | Transaction.Build | Sales Order Header Retrieve/Build business object |
Below are the available business objects, grouped by module.
Each row contains the business object name, short description, class, method and functional area.
At the beginning of each row is an icon. When you click on the icon a screen is displayed that as multiple tabs. Each tab containing information about the business object. The Object Details tab contains information about the class, method, module, etc., and links to the sample XML and schema files. Another tab contains the Object overview, which describes what the business object does. The Input XML and Output XML tabs supply detailed information about restriction in what can be supplied, and what will be returned, including setup options that affect these.
Security
The integrity and security of data are paramount within the SYSPRO ecosystem. Consistent with SYSPRO’s core products, business objects adhere to the same security model. This means if a user is restricted from accessing certain data within SYSPRO, the business object will similarly restrict this data in its XML outputs. Thus, compliance and security are maintained seamlessly across all platforms and tools.
