supplier site assignment fbdi

• Using Procurement

Supplier Sites and Supplier Site Assignments

The site represents a business relationship between a procurement business unit (BU) and the supplier.

Create Site

Sites are created in a procurement BU. A procurement BU represents a specific purchasing or sourcing organization that's responsible for establishing and maintaining supplier relationships. The site allows a specific procurement BU to set terms, controls, and policies which govern how procure to pay transactions are executed between its client BUs and the supplier. Many of these site attributes are optional must be set only when there is a need to deviate from a BU level policy. For example, the supplier might require more restrictive receipt and invoice tolerances. Procurement policy terms and controls that are defined for a supplier are maintained at the supplier site level.

These details are available for a site:

Procurement BU

Site address

Site purposes: Purchasing, Pay, Procurement Card, Primary Pay, and Sourcing Only.

When a new site is created, the site purposes are set by default, based on the address purposes. The address purposes reflect the sales functions that the supplier claims to perform at their location, whereas the site purpose indicates the equivalent procurement functions the buying organization transacts with the location, which can be a subset of the address purposes.

Sites also feature an Additional Details region to capture additional information that can be defined by the buying organization. This information is referred to as descriptive flexfield information.

Use the subtabs on the Sites page to configure the controls that determine how purchasing, receiving and invoicing transactions are executed with the supplier.

Subtabs on the Sites page include:

General: User can provide additional identifier information including a customer number, which is the internal number the supplier uses to identify the buying organization, alternate site name, and a tax reporting indicator.

Purchasing: User can define purchasing terms for this site including communication details, self-billing information, freight, and hold controls.

Receiving: Provide information relating to receiving controls such as over-receipt tolerance, early receipt tolerance, receipt routing and so on

Invoicing: Define invoicing controls and terms such as invoice currency, payment currency, invoice-related holds, match approval levels, payment terms, pay date basis, third-party payment relationships, and so on.

Payments: Define supplier bank accounts, preferred payment methods, and other payment processing attributes for the site. Bank account information is used for paying supplier invoices by electronic funds transfer (EFT).

Site Assignments: Maintain the set of client BUs that can use the site for purchasing and invoicing purposes.

Qualifications: View the assessments and qualification outcomes for supplier.

Site Assignments

Site assignments control which client BUs can transact with the site. In addition, the bill-to BU associated with the client BU is defined. Bill-to BU represents the organization that assumes the liability for the purchases made on behalf of the client BU. In most cases, the client BU and the bill-to BU are the same. However, users can set up a different bill-to BU for a specific client if required.

The premise of the site assignment model is to leverage the centralized procurement organization which negotiates terms and sets policy controls. These terms and controls established for a supplier site are used by the client BUs as a result of being assigned to the site. Without the site assignment model each client BU would be forced to establish its own relationship with the supplier. The service provider relationship between the client BU and procurement BU is defined in the business unit setup.

Creating a Site Assignment

There are two ways to create site assignments. You can manually create one assignment at a time by selecting the specific client BU, or you can use autocreate.

Every supplier site must have an active assignment to create transactions against the site, such as purchase orders or invoices. In other words, if a site assignment doesn't exist or is inactive, you can't create transactions for that supplier site.

In a site assignment, only Client BU and bill-to BU are required values. To create a site assignment for a client BU, provide these details:

Client BU: Select the appropriate BU from the list of all requisitioning and invoicing BUs that are serviced by the procurement BU.

Bill-to BU: The bill-to BU identifies the business unit responsible for processing invoices for the purchase order.. However, in certain instances due to tax or legal reasons the client BU may only perform requisitioning with the supplier and another BU assumes the liability for the purchases. In this case a different bill-to BU is selected. The list of bill-to BUs that can be selected for a given client BU is determined by the Intercompany Transaction Flow setup. In addition, when a separate bill-to BU acts as an agent to the client BU an assignment must be created for the bill-to BU in order for the BU to process invoices.

Ship-to Location: Identifies the default shipping location used on purchasing documents for the client BU.

Bill-to Location: Identifies the default billing location used on purchasing documents for the bill-to BU.

Inactive Date: Determines when the assignment record is no longer active.

Withholding tax information: Indicate whether withholding tax is enabled for the assignment and if yes, identify the tax group in which it's classified.

Liability Distribution: The liability distribution for new invoices.

Prepayment Distribution: The distribution for prepaid expenses.

Bill Payable Distribution: The distribution for future-dated payments.

Distribution Set: A predefined group of general ledger accounting codes that would determine the debit accounts for other receipt payments.

Related Topics

• Options to Merge Supplier Sites

• About TechSupper
• Achievements
• Testimonials
• Oracle Integration
• Oracle Visual Builder
• Oracle BI Publisher
• Visual Builder
• Oracle Process Cloud
• Oracle Cloud Infrastructure
• Oracle Service Bus
• Oracle Analytics Cloud
• Oracle APEX
• Oracle Business Intelligence (BI) & OTBI
• Oracle Cloud Infrastructure (OCI)
• Subscription

Enter your keyword

Import suppliers using fbdi in oracle integration.

Oracle ERP adapter allows you to import bulk data using File Based Data Import(FBDI) . FBDI is the best way to get mass conversions done in shortest time.

Oracle provides an FBDI tool to  Import bulk data  from External Source to the Oracle fusion. Before we upload, an FBDI template needs to be downloaded and create a structured FBDI file to import.

Each job(Supplier, AR, AP, etc.) has a different FBDI template. For example: To Import Suppliers , use the link to download the FBDI template.

The scheduled process to import suppliers into ERP

The below diagram shows the end-to-end process, used to build the scheduled process to import suppliers into Oracle ERP via Oracle Integration

Callback Integration Process

The callback integration in an App-driven orchestration process will be called automatically once the import job is completed in Oracle ERP. The following diagram depicts the callback integration process:

Job Property file structure

Along with the FBDI file, you also need to create the job property file in the process. The property file has a specific format that must follow. The file requires a job package and name including a list of job parameters when submitting the respective bulk import job.

The format of the property file must be as follows:

The name of the property file can be anything, but the extension must be .properties

For import suppliers, the property file needs to be created with the below data:

Refer to this blog to know how to fetch job package, name and list of job parameters.

Watch this complete video to know how to pick up the supplier files from SFTP, create FBDI, property file, and import into the Oracle ERP along with the callback integration:

This video will help you with an end-to-end process.

Also, please subscribe to our  YouTube  channel to get the latest updates.

Further Readings

FTP adapter in Oracle Integration Cloud(OIC)

ERP Integration using File Based Data Import: Oracle Integration

How to create a BIP report in Oracle SaaS

Form region to insert a record into a table in Oracle APEX

Master-Detail Page in Oracle APEX

Cascading List of Values in Oracle APEX

Oracle APEX Interactive Grid with CRUD operation

Call External REST API: Oracle Integration Cloud

• 17 Jul, 2019

How to invoke an Integration from another Integration: Oracle Integration Cloud

• 2 Jul, 2019

Subscribe EBS Business Event in Oracle Integration Cloud

• 22 Jun, 2019

Secure files PGP (Part-2-Decryption): Oracle Integration Cloud

• 14 Jun, 2019

Securing files using PGP encryption (Part-1-Encryption): OIC

Casdk-0004 : failed to authenticate against the application with the credentials provided login_must_use_security_token.

• 8 Jun, 2019

Leave a Reply Cancel reply

Your email address will not be published.

Save my name, email, and website in this browser for the next time I comment.

How to use Supplier Site on Payment Request FBDI?

We are trying to submit an invoice via Payment Request FBDI to offset a misapplied credit taken in the Expense module. We are entering the address on the FBDI that matches the Remit Site of the credit. When the invoice is created, it adds a different Party Site and not the Remit Site defined in the Supplier Module (that was used on the credit).

When we run the PPR, we are expecting the misapplied credit and recently created invoice to process together and off-set each other. However, this is not happening and believe that the Party Site is preventing this from happening.

• Category 332
• Create-Manage-Invoices

Howdy, Stranger!

To view full details, sign in.

Don't have an account? Click here to get started!

Supplier Contact Import Using FBDI – Oracle Fusion

This blog describes the step by step process of Supplier Contacts migration in Fusion Application using File Based Data Import. Using this process we can create Contact of Suppliers and Supplier Addresses.

FBDI Template: SupplierContactImportTemplate .xlsm

Interface Tables: POZ_SUP_CONTACTS_INT

POZ_SUP_CONTACT_ADDRESSES_INT

Base Table: POZ_SUPPLIER_CONTACTS

HZ_CONTACT_POINTS

HZ_ORG_CONTACTS

ESS Job for Import Process: Import Supplier Contacts

STEP 1: Download FBDI template from Oracle Enterprise Repository with the same version as per your application version.

STEP 2: Populate the data both POZ_SUP_CONTACTS and POZ_SUPP_CONTACT_ADDRESSES_INT sheet of template as shown below.

STEP 3: Generate PozSupContactsInt.zip file in local system using “Generate CSV File” option.

STEP 4: Login to application and upload the PozSupContactsInt.zip file to interface table using “Load Interface File for Import” process.

STEP 5: Run “Import Supplier Contacts” process to import the interfaced data.

STEP 6: Get the error details using below SQL Query

–** Supplier Contacts Error Query **–

SELECT REJ.reject_lookup_code

      ,REJ.ATTRIBUTE error_field

      ,REJ.VALUE error_value

      ,INTE.*

FROM POZ_SUP_CONTACTS_INT INTE

    ,poz_supplier_int_rejections REJ

WHERE REJ.parent_id = INTE.contact_interface_id

  AND PARENT_TABLE = ‘POZ_SUPPLIER_CONTACTS’

–** Supplier Addresses Contacts Error Query **–

FROM POZ_SUP_CONTACT_ADDRESSES_INT INTE

WHERE REJ.parent_id = INTE.CONTACT_ADDRESS_INTERFACE_ID

  AND PARENT_TABLE = ‘POZ_SUP_CONTACT_ADDRESSES_INT’

Start typing and press Enter to search