SAM Integration with Oracle Procurement

The SAM integration in Oracle U.S. Federal Financials creates or updates Procurement objects with data from SAM.

The SAM integration creates or updates these Procurement objects:

• Unique Entity Identifier (UEI) in the Supplier Sites window

• Taxpayer identifier in the Suppliers window

• Country and address fields and bank account information in the Supplier Sites window

• Bank branch number and branch type in the Banks window

• Account number, account type, and supplier assignment in the Bank Accounts window

Supplier header and site-level global descriptive flexfields are used to populate the SAM details.

Users can’t modify the information in the SAM fields.

Payables also checks the supplier site controls at certain points during the invoicing and payment processes.

The following table describes how the SAM Trading Partner Registration status impacts the Payables functionality:

Trading Partner's SAM Registration	Third-Party Agent's SAM Registration	Invoice Creation (AP)	Invoice Validation (AP)	Payments (AP)
Active	None used	An invoice can be created.	An invoice can be validated.	A payment can be processed.
Expired or Inactive	None used	An invoice can be created for an obligation.	An invoice can’t be validated. An expired registration hold is applied.	A previously validated invoice can’t be paid for selected payment.
Active	Active	An invoice can be created for the SAM trading partner.	An invoice can be validated for the SAM trading partner.	A payment can be processed for the third-party agent.
Expired or Inactive	Active	An invoice can be created.	An invoice can’t be validated. An expired registration hold is applied.	A previously validated invoice can’t be paid for selected payment.
Active	Expired or Inactive	An invoice can be created for the SAM trading partner.	An invoice can be validated for the SAM trading partner.	A payment can’t be processed for the third-party agent.