Setting up Field Mapping

The FFBC Field Mapping object contains mappings between object fields used in Billing Central processes. For example, several fields are mapped from an Opportunity object to a Billing Central Billing Contract object.

Note:

Mapping is one-to-one. This means that you cannot map a field on one object to two fields on another object.

The FFBC Field Mapping object specifies how the system maps different SObject types. You can change the default mappings, and add your own custom fields so that they are copied over automatically when Billing Central performs the mapping. Fields are then mapped from opportunities to Billing Central contracts as required. The mapping works for all types of contract: new, renewal, upsell, and replacement.

To set up mappings for your processes:

  1. Go to Setup | Custom Code | Custom Metadata Types. Using ClassicClosed Navigate to Setup | Develop | Custom Metadata Types.
  2. Scroll down the list to find FFBC Field Mapping then click Manage Records.
  3. You can choose whether or not to use existing mappings by selecting or deselecting the Active field. If an existing mapping contains a field that you want to use in a new mapping, deselect the existing mapping's Active field to avoid clashes.

    You cannot delete the packaged mappings, but you can make inactive the ones that you do not need.

  4. Create new mappings as required. Make sure you map from the Opportunity to a Billing Central Billing Contract.

Creating a New Mapping

  1. On the FFBC Field Mappings object click New.
  2. Enter a Label for the mapping. FFBC Field Mapping Name is automatically populated.
  3. Select a Process. The first process in the picklist is selected by default.
  4. The Active field is selected by default.
  5. Select Object From and Object To. Make sure that these are correct object types. For example, they must be an Opportunity that maps to a Billing Contract, or an Opportunity Line Item that maps to a Billing Contract Line Item.
  6. Select Field From and Field To. Make sure you select fields that have compatible data types.
  7. Click Save.
Notes:

Field mappings may fail if an object field contains a value which the target field cannot handle. For example, length of text field may be bigger in the Object From field.

An error will be reported if you run a process that tries to map a field to a field that can only be populated by Billing Central, such as Billed To and Total Billed.