Structure of vendor data

Oracle vendor data consists of a vendor header at the system level and one or more vendor sites are at the operating unit level, which is the equivalent of the Maximo® Manage site level.

The following diagram shows the vendor structure in Oracle E-Business Suite:
Figure 1. Oracle E-Business Suite vendor structure
Diagram depicting how vendor data is structured in the Oracle E-Business Suite

Maximo Manage vendor data consists of a vendor master at the set level and one or more vendor records at the organization level. An organization has only one vendor set, but a vendor set can belong to more than one organization.

Maximo Manage refers to vendors as companies. The following diagram shows the company structure in Maximo Manage:
Figure 2. Maximo Manage vendor structure
Diagram depicting how company data is structured in Maximo Manage

The integration framework passes the Oracle E-Business Suite vendor site records to Maximo Manage organization level. The integration framework determines Maximo Manage set identifier from the organization information about the inbound vendor record.

Before you use the integration framework, you must configure the relationship between company master sets and Maximo Manage organizations in the Sets application.

The company identifier in Maximo Manage is a concatenation of the Oracle E-Business Suite operating unit, vendor ID (SEGMENT1), and vendor site code.

The following diagram shows the mapping of the Oracle vendor and site identifiers to Maximo Manage:
Figure 3. Oracle to Maximo Manage vendor and site identifier mapping
Diagram depicting how the Oracle vendor and site identifiers map to Maximo Manage

The integration framework does not create the company masters. To direct Maximo Manage to create a company master for each inbound vendor it creates, select the Automatically Add Companies to Company Master checkbox in the Sets application. If you do not, errors occur.

Although Maximo Manage allows a one‐to‐many relationship between company masters and company record, a one‐to‐one relationship for vendors exists that is added by using the vendor integration.

Effectivity of vendors

The value in the Inactive Date field in the Oracle E-Business Suite Suppliers window determines whether an Oracle vendor is active or not active. If a vendor header is not active, its vendor sites are all not active. If a vendor header is active, the Inactive On date determines the status of each vendor site. If the system date is earlier than the Inactive On date, the vendor is active.

The integration framework passes the following fields to the PL/SQL user exit. If necessary, you can write a user exit procedure to include these fields in the interface table.
  • AP_SUPPLIERS.START_DATE_ACTIVE
  • AP_SUPPLIERS.END_DATE_ACTIVE
  • AP_SUPPLIER_SITES_ALL.INACTIVE_DATE

The SYNCVND synchronization script sends active and nonactive vendors to Maximo Manage. If a vendor is active, the Disqualified Vendor checkbox in Maximo Manage Company Master and Companies windows is not selected.

The integration framework uses the following logic to evaluate the INACTIVE_DATE and END_DATE_ACTIVE fields in the Oracle E-Business Suite and set the value of the Disqualified Vendor checkbox in Maximo Manage.

Table 1. integration framework date evaluation logic
Oracle E-Business Suite Maximo Manage
End date Inactive date Disqualified vendor value
Null Null Not checked (vendor header)
Null > system date Not checked (vendor site)
Null < or = system date Checked (vendor site)
> system date   Not checked (vendor header)
> system date > system date Not checked (vendor site)
> system date < or = system date Checked (vendor site)
< or = system date any value Checked (vendor header and vendor site)

The vendor integration does not update Maximo Manage vendors when the status of an Oracle vendor changes to active or nonactive based on the system date. To ensure that Maximo Manage uses only active vendors, run the SYNCVND synchronization script frequently.

Vendor filter

The integration framework transfers vendors from the Oracle E-Business Suite to Maximo Manage when the following conditions are met:

  • The value of the Oracle integration control COMIN is 1.
  • The vendor is designated a purchasing site, a pay site, or both in Oracle E-Business Suite.

Effectivity of vendor site contacts

The Inactive Date on the Oracle E-Business Suite Suppliers Contact Directory field determines whether the contact is active or not. If the inactive date is less than the current system date, the contact is nonactive for all associated sites in the Oracle E-Business Suite.

During the execution of the vendor sync script, Maximo Connector for Oracle Applications sends only active contacts that are associated with sites (addresses). If the inactive date is updated in the Oracle E-Business Suite Suppliers Contact Directory window, the adapter deletes the contacts in Maximo Manage.

Follow these guidelines for contact deletion:

Table 2. Contact deletion guidelines
Oracle E-Business Suite Maximo Manage
Inactive Date < system date Contact deleted.
Inactive Date > = system date Contact is not deleted.

The vendor integration does not update vendor site contacts when the status of an Oracle vendor site contact changes to active or nonactive based on the system date. To ensure that Maximo Manage uses only active vendor site contacts, you must run the SYNCVND synchronization script frequently.

Vendor contact filter

The integration framework transfers vendor contacts from Oracle E-Business Suite to Maximo Manage when the value of the Oracle integration control COMIN is 1.

Integration controls

The vendor integration uses the following Maximo Manage and Oracle integration controls.

Table 3. Vendor integration controls
Control Description System
COMIN Send the Oracle E-Business Suite vendor data to Maximo Manage. Oracle E-Business Suite
GENUSR Dummy identifier for masking user ID in outbound transactions. Maximo Manage
ORGXREF Cross‐reference Maximo Manage organization and the Oracle E-Business Suite ledger ID. Maximo Manage