Minimum required fields for data import
To properly process and manage data that is imported in Supply Chain Intelligence Suite, a minimal set of fields is required in the CSV files.
When objects are uploaded, make sure that you upload objects so that the data dependencies for an object exist before that object is uploaded. For example, because the products have a reference to a catalog, the catalog data must be uploaded first and then the product data can be uploaded after the catalog upload is completed.
Before you prepare CSV files for import, review the following minimum required fields.
- Contact
-
Defines contacts in your supplier organization. For more information, see Contact.
Field Description contactIdentifierUnique identifier for the contact. firstNameGiven name. lastNameSurname. emailAddressEmail address.
- Organization
- Defines your supplier's organization. For more information, see Organization.
Field Description organizationIdentifierA unique identifier for the organization orgTypeAn indication of the type of organization. Note: The value must be SUPPLIER.nameThe descriptive name of the organization. primaryContact.contactIdentifierThe ID for the primary contact for the organization.
- Source location
- Defines your supplier's location that ships to your organization. For more information, see
Location.
Field Description locationIdentifierA unique identifier for a location that your supplier owns. LocationNameThe descriptive name for the location. countryThe value must be the 3-digit country code of one of the 188 countries that Supply Chain Intelligence Suite supports. - Destination location
- Defines your organization's location that your supplier ships to. For more information, see
Location.
Field Description locationIdentifierA unique identifier for a location that your organization owns. LocationNameThe descriptive name for the location. secondaryIdentifierA unique identifier that must match a location ID in Envizi™ ESG Suite.
- Catalog
- Defines the categories of products that your organization receives from suppliers. Controls the
factor code that is used for a product. Each category has a factor code. For more information, see
Product catalog.
Field Description nameThe descriptive name of the catalog code.
levelTypeThe type of level. It is used for filtering and categorization.
Note: The value must be CATEGORY.codeA unique identifier for the category. catalogTypeThe category type.
Note: The value must be ITEM.emissionsFactorGroup.factorCodeA classification code that identifies the emission factor. For the list of valid values, see
Factor codes. - Product
- Defines a product that is shipped to your organization. For more information, see Product.
Field Description partNumberA unique identifier for the product.
valueThe value or price of the product or material.
valueCurrencyThe currency designation in ISO 4217 format.
Note: For use with the default EORA factor data, the value must be in USD.nameThe descriptive name of the product. productTypeThe type of product. The field is used for categorization or filtering.
Note: The value must be ITEM.category.codeA unique identifier for the product category.
Note: The value must match an existing code field in a catalog object. - Order
- Defines the order of goods that are inbound to your organization from a supplier. For more
information, see Order.
Field Description orderTypeSpecifies whether the order is inbound or outbound. Note: The value must be INBOUND.orderIdentifierThe unique identifier for an order. vendor.organizationIdentifierThe unique ID for the supplier. Note: The value must match theorganizationIdentifierof aSUPPLIERorganization object. - Order line
- Defines a shipment of one product that is inbound to your organization from a supplier for an
order. For more information, see Order line.
Field Description orderLineNumberSequential number of the order line. order.orderIdentifierA unique identifier for an order that the order line is fulfilling. Note: The value must match theorderIdentifierof an order object.order.orderTypeThe value must be INBOUND. product.partNumberThe unique identifier of the product in the order line. Note: The value must match thepartNumberof a product object.quantityThe quantity of products or materials in the order line.
quantityUnitsThe units of measure from the source system. Use standard UOM or ISO format. For example, EA. plannedShipDateThe date and time that fulfillment expects to ship the order line. The following format is expected for the date and time:YYYY-MM-DDThh:mm:ssZ
Where- YYYY
- The four-digit year.
- MM
- The two-digit month. For example,
01is January. - DD
- The two-digit day of the month. Valid values are 01 through 31.
- T
- Separator
- hh
- The two-digit hour. Valid values are 00 through 23. Do not include AMor PM.
- mm
- The two-digit minute. Valid values are 00 through 59.
- ss
- The two-digit second. Valid values are 00 through 59.
- Z
- The designator for the time zone. Valid values can be Z or +0000.
For example, 2023-06-28T14:30:36+0000.
shipFromInstructionLocation.locationIdentifierThe location that the order line is being shipped from. Note: The value must match thelocationIdentifierof aSUPPLIERlocation object.shipToLocation.locationIdentifierThe location that the order line is being shipped to. Note: The value must match thelocationIdentifierof a location object that is defined for one of your organization's locations.valueTotal value of products or materials in the order line. For example, 10850. valueCurrencyCurrency designation in ISO 4217 format. For example, USD.