Accepted valuesPurchase requisition ID from your purchasing application
Data type: Text
Example: R1000
| | | Requisition Title | requisition\_title |Purchase requisition title. This title will display in Fairmarkit and defaults to the first line item title.
Data type: Text
Example: Req for FMKT
| | | Line Number | line\_number |Line number or order of the line item.
Data type: Text
Example: 1
| | \* | Item Title | item\_title |Item name.
Data type: Text
Example: coffee beans
| | | Item Identifier | item\_identifier |Unique identifier for the line item in your purchasing application, if it exists.
Data type: Text
Example: G123
Note: This data is preserved when exported from Fairmarkit.
| | | Buyer Email | buyer\_email |Buyer's email. Fairmarkit does not validate the email. This value is used to assign request for quote events in Fairmarkit.
Data type: Text
Example:
Buyer's ID in your purchasing application. The ID can be used as an alternative to the Buyer Email, but a mapping will need to be provided.
Data type: Text
Example: buyer.example
| | | Currency | currency |Purchase requisition currency. This should be the three letter currency code.
Default: USD
Data type: Text
Example: USD
| | \* | Quantity |quantity
|
Item quantity. This is assumed to be an integer.
Data type: Text
Example: 1
| | | UOM | uom |Unit of measure of the item.
Default: Each
Data type: Text
Example: Each
Accepted values: Fairmarkit defined values; For more information, see Available UOMs.
Note: Custom mapping is available. For more information, contact your technical architect.
| | | Benchmark Supplier ID | benchmark\_supplier\_id |Benchmark supplier ID.
Data type: Text
Example: S1002
| | | Benchmark Supplier Title | benchmark\_supplier\_title |Benchmark supplier name. This can be a name, title, entity, or description.
Data type: Text
Example: Charlie's Convenience Store
| | | Benchmark Price (Per Unit) | benchmark\_price\_per\_unit |Benchmark price per unit. This is internal to your company. Presumably in your currency and UOM for the item.
Data type: Text
Example: 10.00
| | | Internal Part Number | internal\_part\_number |Your organization's part number for the item. This value is entered at your discretion.
Data type: Text
Example: IPN100
| | | Manufacturer | manufacturer |Manufacturer of the line item.
Data type: Text
Example: Local Co
| | | Manufacturer Part Number | manufacturer\_part\_number |Manufacturer part number of the line item.
Data type: Text
Example: 900
| | | UNSPSC | unspsc |Standard 8 digit UNSPSC code for the item or requested service.
Data type: Text
Example: 50201706
| | | Start Date | start\_date |Start date for the line item. Typically used for services, leases, and software subscriptions and licenses.
Data type: Text
Example: 2022-07-20
| | | End Date | end\_date |End date for the line item. Typically used for services, leases, and software subscriptions and licenses.
Data type: Text
Example: 2022-07-27
| | | Buyer Line Comment | buyer\_line\_comment |Line item comments from you (buyer) to the suppliers.
Data type: Text
Example: We'll need your best coffee
| | | Item Kind | item\_kind |Line item type. For more information, see 3. Add items or services.
Default: Item
Data type: Text
Example: Item
| | | Group Item Title | group\_item\_title |When Item Kind is Group, the name of the group.
Data type: Text
Example: Coffee Supplies
| | | Group Item Id | group\_item\_id |When Item Kind is Group, an optional key.
Data type: Text
Example: 123
| | | Requester | requester |Name of requester. This could be an entity. This value is at discretion of buyer company.
Data type: Text
Example: John Smith
| | | Preferred Delivery Date | preferred\_delivery\_date |The date when the line items are needed. This date is the preference used when defining shipping time lines and scheduling services.
Data type: Text
Example: 2022-07-20
| | | Shipping Type | shipping\_type |Preferred shipping method. This value is selected from a list and does not default.
Data type: Text
Example: Ground
| | | Shipping Carrier | shipping\_carrier |Preferred shipping carrier. This value is selected from a list and does not default.
Data type: Text
Example: USPS
| | | Address1 | shipping\_address\_address1 |Shipping address - first line.
Data type: Text
Example: 27 School St
| | | Address2 | shipping\_address\_address2 |Shipping address - second line.
Data type: Text
Example: STE 400
| | | City | shipping\_address\_city |Shipping address city.
Data type: Text
Example: Boston
| | | State | shipping\_address\_state |Shipping address state.
Data type: Text
Example: MA
| | | Zip | shipping\_address\_zip |Shipping address zip code.
Data type: Text
Example: 02108
| | | Country | shipping\_address\_country |Shipping address country.
Data type: Text
Example: US
| | | Requisition Internal Comment | internal\_notes |Notes about the event. This is internal to your company. Multiple notes are concatenated into a long string. This correlates to the Internal Notes in the Fairmarkit user interface.
Data type: Text
Example: Get medium roast
| | | Requisition Note to Supplier | note\_to\_supplier |Add additional information and communication about the event with all invited suppliers. This correlates to the Notes to Suppliers in the Fairmarkit user interface.
Data type: Text
Example: Please leave on doorstep
| | | Urgency | urgency |Let suppliers know the urgency of the event.
Default: Normal
Data type: Text
Example: Normal
| | | Business Unit | business\_unit |Business unit.
Data type: Text
Example: Sales
| | | Client Company | client\_company |Client company.
Data type: Text
Example: Cameron's Consulting Agency
| | | Category | category |Category as defined in your purchasing application.
Data type: Text
Example: Supplies
| | | Category ID | category\_id |Category ID.
Data type: Text
Example: 1001
| | | Subcategory | subcategory |Subcategory.
Data type: Text
Example: Coffee
| | | Subcategory ID | subcategory\_id |Subcategory ID.
Data type: Text
Example: 23
| | | ERP System | erp\_system |Your purchasing application. When entered, it will override the system level settings.
Data type: Text
Example: SAP Ariba
| | | Requisition Import Status | requisition\_import\_status |Event status of your imported purchase requisition. This will override the initial event status. With Skip, the line will not be imported.
Default: Draft
Data type: Text
Example: Draft
| | | Requisition Tag XXX | requisition\_tag\_XXX |Requisition tag. Replace XXX with your value. For example, add plant for requisition\_tag\_plant. This adds a cosmetic item to the event in the user interface.
Data type: Text
Example: C08
| | | Line Item Meta Tag XXX | line\_item\_meta\_tag\_XXX |In the user interface, this value translates to Internal Tags. Replace XXX with your tag key. The row value is used as the tag value.
Data type: Text
Example: Account1000
| | | Additional Info XXX | additional\_info\_XXX |Additional information. Add any other data that is necessary to attach to the line item and send back to your purchasing application.
Data type: Text
Example: G776
| | | Closes At Date | closes\_at\_date |Closes at date. This date supersedes closes\_days.
Default: next business day
Data type: Text
Example: 2022-07-20
| | | Days until close | closes\_days |The number of business days until the event closes.
Data type: Int
Example: 2
| --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fairmarkit.com/buyers/integrations/flat-file-integration/import-data/import-purchase-requisitions.md?ask=