Sunday, December 06, 2015

Complement your Oracle ERP conversion with CRM File Based Data Import

On a customer Fusion ERP implementing project and on our own Fusion ERP Cloud implementation, I had the privilege of creating and running the conversion of suppliers to Fusion ERP. Fusion provides to necessary File Based Data Import to load Suppliers, Supplier Addresses, Sites, Assignments and Bank Accounts.
To be able to load the Supplier Bank Accounts, the bank and bank branches need to be converted to Cash Managent first, for this the RapidImplementionForCashManagement sheet can be utilised.
Because these implementations have CGI validation enabled for SEPA payment files, it is enforced to have an address for the bank branches, al least a country code and this is where it's getting exciting.

As said, you are able to load banks and bank branches, but at the moment there is no ability to load addresses for bank branches through ERP FBDI (currently an enhancement request).

Above screenshot is an example on how to create a bank and branch prior to creating supplier bank accounts.
Result of loading this sheet in Fusion ERP Cloud:

As you can see the Address section is not populated, but will be mandatory when creating SEPA payments.

Fortunately bank branches are stored as parties in the Trading Community Architecture (TCA) model and like many other entities shared across modules. Unlike Fusion ERP, that has predefined FBDI's, CRM provides you the ability to create your own defined data structure for loading using task Manage File Import Activities.

Before loading data, you will need to create a mapping of the source data to the target import objects and attributes, this can be done by task Manage File Import Mappings.

The first two lines of the mapping reference the source system and source reference of the object you want to load. If you would like to update this object in any time of the future you can use this source reference again. In this case I will use the Party ID of the bank branch as the source reference.
Lines 3 and 4 are references of the location link between a bank branch and the address.
Line 5 is the actual Party Id of the bank branch.
Line 6 is the bank branch name, which is in fact not necessary in this mapping, but will make the import file more readable.
Lines 7 through 16 are the actual address line attributes that will be loaded.

Key question here is, how do you obtain the Fusion internal Party Id for a bank branch?
You can use the CRM task Manage File Export Activities and export all parties or a subset or simply query the required bank branches, using the Fusion BI layer.

Now that we have the Party Id, we can start working on the update sheet. An upload sheet template can be dowloaded using the Download Template button in the Edit Mapping page as shown on the first screenshot of this post.

Now you can fill and upload this template using the task Manage File Import Activities.

Create a file import activity using your custom mapping.

Acknowledge the mapping lines.

See the result, the impossible has been made possible.

For more information on the File Import feature, please visit Oracle Support and see note:
Oracle Sales Cloud File Import Mapping Reference and Supporting Instructions (Doc ID 1596128.1)

No comments:

Post a Comment