Mapping FSM to OneSource

Batch level

Use this table to map FSM data to OneSource.

Element name Type Required Infor table/field
<USERNAME> Alpha (60) Yes, if OneSourceVersionType=Generic TaxConfiguratioVersion/

UserName

<PASSWORD> Alpha (16) Yes, if OneSourceVersionType=Generic TaxConfigVersion/

OneSourcePassword

<INVOICE> Structural Yes n/a

Invoice level

Use this table to map FSM data to OneSource.

Element name Type Required Infor table/field
<HOST_SYSTEM> Alpha (100) Yes TaxEntity/

HostSystem

<EXTERNAL_COMPANY_ID> Alpha (100) Yes TaxEntity/

ExternalCompanyId

<COMPANY_NAME> Alpha (100) Yes TaxEntity/

ExternalCompanyIdName

<COMPANY_ROLE> Alpha (20) Yes TaxEntity/

CompanyRole

<FILTER_GROUP_NAME Alpha (50) No TaxEntity/

FilterGroupName

<FILTER_GROUP_OWNER> Alpha (40) No TaxEntity/

FilterGroupOwner

<PRODUCT_MAPPING_GROUP_OWNER> Alpha (40) No TaxEntity/

ProductMappingGroupOwner

<PRODUCT_MAPPING_GROUP_NAME> Alpha (40) No TaxEntity/

ProductMappingGroupName

<CURRENCY_CODE> Alpha (3) Yes <calling system>/

Currency

<IS_AUDITED> Boolean No n/a
<INVOICE_DATE> Date Yes <calling system>/

InvoiceDate

<FISCAL_DATE> Date No <calling system>/

PostDate

<DOCUMENT_TYPE> Alpha (50) No <calling system>/

DocumentType

<INVOICE_NUMBER> Alpha (200) Yes <calling system>/

InvoiceNumber

<VENDOR_NUMBER> Alpha (100) Yes <calling system>/

Vendor

<VENDOR_NAME> Alpha (100) Yes <calling system>/

VendorName

<CUSTOMER_NUMBER> Alpha (100) Yes, for Recievables <calling system>/

Customer

<CUSTOMER_NAME> Alpha (100) Yes, for Recievables <calling system>/

CustomerName

<END_USER_NAME> Alpha (100) No <calling system>/

Actor

<TRANSACTION_TYPE> Alpha (2) Yes Hard Coded “GS”/

n/a

Line level

Use this table to map FSM data to OneSource.

Element name Type Required Infor table/field
<LINE_ID="N"> Structural Yes <calling system>/

LineNumber

<PRODUCT_CODE> Alpha 15 Yes <calling system>/

ProductTaxCategory, ICN Code, or TaxUsageCode

<GROSS_AMOUNT> Number Yes <calling system>/

TaxableAmount

<COMMODITY_CODE> Alpha 5 Yes <calling system>/

CommodityCode

<DELIVERY_TERMS> Alpha Upper 3 Yes <calling system>/

DeliveryTerms/ShipTerms

<PART_NUMBER> AlphaUpper 32 Yes <calling system>/

Item

<SHIP_TO> Structural Yes <calling system>/

Ship To Address

<COUNTRY> Alpha (50) Yes <calling system>/

Ship To Address Country

<PROVINCE> Alpha (50) Yes, Canada <calling system>/

Ship To Address Province

<STATE> Alpha (50) Yes <calling system>/

Ship To Address State

<COUNTY> Alpha (50) No <calling system>/

Ship To Address County

<CITY> Alpha (50) No <calling system>/

Ship To Address City

<POSTCODE> Alpha (50) Yes <calling system>/

Ship To Address Postal Code

<GEOCODE> Alpha (50) Yes <calling system>/

Ship To Address Postal Code last 4 digits

<SHIP_FROM> Structural Yes n/a
<COUNTRY> Alpha (50) Yes <calling system>/Ship From Address Country
<PROVINCE> Alpha (50) Yes, Canada <calling system>/Ship From Address Province
<STATE> Alpha (50) Yes <calling system>/Ship From Address State
<COUNTY> Alpha (50) No <calling system>/Ship From Address County
<CITY> Alpha (50) No <calling system>/Ship From Address City
<POSTCODE> Alpha (50) No <calling system>/Ship From Address Postal Code
<GEOCODE> Alpha (50) No <calling system>/Ship From Address Zip last 4 digits
<QUANTITIES> Structural No n/a
<QUANTITY> Structural No n/a/

Quantity

<AMOUNT> Number No <calling system>/

Quantity Amount

<UOM> Alpha (25) No <calling system>/

Unit of Measure

<USER_ELEMENT> Structural Yes n/a
<NAME> Alpha (200) Yes, if Attribute is passed <calling system>/

ATTRIBUTE1-50

<VALUE> Alpha (200) Yes, if Attribute is passed n/a/

Attribute value

Element name explanations are located in the OneSource programmers guide.

If the OneSource user guide already has a mapping, then just add the missing fields.