Wednesday, 12 January 2022

Workday Business Objects (Simple Terminology)

Workday Business Objects (Simple Terminology)



Workday architecture is Object based. Workday stores the data in business objects (BO).
A business object is like a spreadsheet, where each row is an instance of the object. Each column represents an attribute, or field, of the object.

For Example : A supplier is associated with supplier invoices, the invoice is associated with a supplier invoice payment and the payment is associated with a bank account. 

Below Snapshot shows how Business Objects are automatically connected. In the Workday Finance, the Supplier Business Object is linked to Contracts, Purchase Order, Parent/Child and Invoice. Here all of them are BO's.





Workday links related business objects together through single instance or multi-instance fields. Related Business Objects (RBO) enable you to access fields in a report that don’t belong to the Primary Business Object. (PBO)

Example: The Worker business object has a multi-instance field called Dependents. Dependents has a related business object of Dependent. In a report with a primary business object of Worker, you can use the Dependents field to access the fields belonging to the Dependent business object.

A report by name Business Object Details can be used to view:

-Custom and standard reports that use the business object.
-Data sources using the business object as the primary business object.
-Fields associated with the business object.
-Related business objects.

If you want to relate the workday terms with Database Management Systems like Oracle and SQL Server, see below:




1 comment:

How many types of EIB integrations in workday

How many types of EIB integrations in workday Basically there are 2 types of EIB integrations in workday, they are: 1. INBOUND Integration 2...