Understanding Field Names in the Sample Sales Account Import Template



Steps:

  1. Hello, my name is John and today I will talk about importing sales account information from a file.

    Step 1

  2. In this demo, I will talk about fields and field names in the sample import template.

    Step 2

  3. This is the third in a series of demos that show how to use the template to import sales accounts from a file.

    Step 3

  4. Let's go back to the page where you map the fields in your file to the fields in the application and look at the field names.

     

    Some field names are similar to what you see in the interface. Sometimes they just have a different capitalization or have the spaces taken out.

    Step 4

  5. Others are different.

     

    For example, a phone number is split into a country code, an area code, and the number itself.

    Step 5

  6. There is a field called Primary flag that takes a value of either Y or N and indicates the phone is the primary phone.

    Step 6

  7. Notice multiple attributes that have the term OrigSystem in the name. This abbreviation stands for original system. 

     

    Step 7

  8. All of these attributes have the same value. In this sample template, the letters CSV.

    You must complete the Manage Trading Community Source Systems setup task to create the value in your environment before you import the template. This is a one-time setup that is covered in a related demonstration.

    Step 8

  9. The file also includes many attributes with OrigSystemRef in the name. This abbreviation stands for Original System Reference.

    Step 9

  10. These attributes hold IDs that identify the objects you are importing.

    If your legacy data does not include these IDs, you can easily generate them in your file using Excel.  The sample template already includes these IDs for you.

    Step 10

  11. The original system code paired up with the ID ensures the uniqueness of each record.

    Oracle permits you to import data from multiple systems and so there is a slight chance that you could have duplicates if you didn't have an original system code.

    You can use these pairs to identify records in many import objects including customer, contact, and consumer.

    Including these pairs in your file is one alternative for identifying records so you can update them later or import related information.

    After you import an  object for the first time, you can reference it using an internal ID  such as PartyID or LocationID, but you'll have to do more work to get these.

    Step 11

  12. When you examine the template, you will notice many system and ID pairs. Each pair identifies an object that's being created when you import.

     

    Using this template, you are actually  importing only four bits of customer information.

     

     

    Step 12

  13. Customer name

    Step 13

  14. Customer address

    Step 14

  15. Customer URL

    Step 15

  16. Customer phone

    Step 16

  17. In this demo, you learned about the fields and field names in the sample template for importing sales accounts.

    You can find additional learning resources in your Oracle Fusion Help application, as well as in the Oracle Learning Library, and at Oracle University. Thank you.

    Step 17

Table of Contents  Start Topic