Comparision Between Oracle Simplified and Detailed Customer FBDI Template

 There are many ways to import/Integrate customers in Oracle .

 1).  Manually from UI

 2).  Using web services

 3).  Using FBDI templates- Simplified and Detailed  template

In this article we will see the comparison between Simplified and detailed FBDI templates to import Customers in Oracle.

For common use cases we will see the capabilities and limitations of these two templates one by one.

Note:- Using simplified template we can create customer as organization only but with detailed template we can create customer as organization as well as person.

Let us first see the Simplified template:

 Simplified Template

Use Case	Insert	Update	Delete/Inactivate	Comment/Observation
Customer- Party	Yes	Yes	No	Insert and update are possible
Customer- Account	Yes	Yes	No	Insert and update are possible
Customer- Sites	Yes	Yes	No	Insert and update are possible
Customer- Site Use	Yes	Yes	No	Insert and update are possible
Customer- Site Location	Yes	Yes	No	Insert and update are possible
Contact	Yes	Yes	No	Insert and update are possible, No option to end date, not in UI either
Contact Point	Yes	No	No	Email and Phone can't be updated,since the orig system reference has the email or phone if we use simplified template. It is generated by system. The format will be like: Pary Number-CP-Contact Point Type-Value for contact point Example : 10040006-CP-Email-test@test.com
Reference Account	Yes	Yes	Yes, with workaround	We can reset the account by providing null values for BU instead of end date
Customer Profile Assignment	Partially	Partially	No	Support at Account level and not at Site level. However requirement is at the account level only.
Receipt Method	Yes	No (Treated as a new Record)	No	We can create receipt method assignments. No option to end date, and changes to Receipt Method is treated as a new record
Bank Accounts	Yes	No (Treated as a new Record)	No	We can create bank account. No option to end date, and changes to Bank Account number treats as a new record

Now let us see the detailed template.

Detailed Template

Use Case	Insert	Update	Delete/Inactivate	Comment/Observation
Customer- Party	Yes	Yes	No	No option to end date a party
Customer- Account	Yes	Yes	Yes	Invoice is gets created through AutoInvoice even though customer account, site and site uses are end dated. However if we create invoice manually from UI then it restricts. This is because validation for manual invoice is different from Autoinvoice.
Customer- Sites	Yes	Yes	Yes	Invoice is gets created through AutoInvoice even though customer account, site and site uses are end dated. However if we create invoice manually from UI then it restricts. This is because validation for manual invoice is different from Autoinvoice.
Customer- Site Use	Yes	Yes	Yes	Invoice is gets created through AutoInvoice even though customer account, site and site uses are end dated. However if we create invoice manually from UI then it restricts. This is because validation for manual invoice is different from Autoinvoice.
Customer- Site Location	Yes	Yes	Yes	Location Insert and update is possible for all fields
Contact	Yes	Yes	No	No option to end date, not in UI either
Contact Point	Yes	Yes	Yes	Contact Point Inert and update Working. End Date also possible however need to have party tab as well populated.
Reference Account	No	No	No	Not supported by Detailed Template. However webservice available to create the reference account. Sample Payload To Create Reference Accounts To The Bill-To Site Via Web Service. (Doc ID 2579569.1)
Customer Profile Assignment	Yes	Yes	No	Support at both Account and Site level, and can update the indvidual attributes as well
Receipt Method	Yes	No	No	Update and endate not working through template since no Inser/update indicator
Bank Accounts	Yes	No	No	Update and endate not working through detailed template