> For the complete documentation index, see [llms.txt](https://docs.fairmarkit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fairmarkit.com/buyers/integrations/sap-ariba-integration/purchase-requisition-sync/import-configurations.md).

# Import configurations

When importing requisitions from SAP Ariba, you have control over how the following information is available in Fairmarkit.

### Attachments <a href="#attachments" id="attachments"></a>

If your SAP Ariba requisition has attachments at the header or line item level, you can select to make them visible to suppliers.

| Attachments              | Header                        | Line item                                                             |
| ------------------------ | ----------------------------- | --------------------------------------------------------------------- |
| Visible to suppliers     | Imported in the Files section | Imported under Files Section (renamed as “Line{number}\_{filename}”)  |
| Not visible to suppliers | Imported under Internal notes | Imported under Internal notes (renamed as “Line{number}\_{filename}”) |

### Comments <a href="#attachments" id="attachments"></a>

If your SAP Ariba requisition has comments at the header or line item level, you can select to make them visible to suppliers. However, the “visible to suppliers” status is not exposed in the API. To be safe, we treat all comments as internal and import them as follows:

| Comment                  | Header                                                                                                                         | Line item                                                                                                                               |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| Visible to suppliers     | <p>Imported under Internal notes</p><p>Ariba Imported Comment:<br>George Jetson 2021-08-09 18:27:04: Comment from Ariba</p>    | <p>Imported under Internal notes</p><p>Ariba Imported Comment:</p><p>Line 1 - George Jetson 2021-08-09 18:27:04: Comment from Ariba</p> |
| Not visible to suppliers | <p>Imported under Internal notes</p><p>Ariba Imported Comment:</p><p>George Jetson 2021-08-09 18:27:04: Comment from Ariba</p> | <p>Imported under Internal notes</p><p>Ariba Imported Comment:</p><p>Line 1 - George Jetson 2021-08-09 18:27:04: Comment from Ariba</p> |

### Buyer assignments <a href="#buyerassignments" id="buyerassignments"></a>

Because SAP Ariba doesn't expose any email that can be used to directly assign request for quote events in Fairmarkit, all imported events are assigned to a default buyer. You can request custom logic for buyer assignment.

### Line Item Kinds <a href="#lineitemkinds" id="lineitemkinds"></a>

With SAP Ariba, you could have one of the following types of line items on your requisition:

* Non-Service Line Item
* Parent Service Line Item
* Child Service Line Item

Additionally, each item could have hidden items associated to it that are only exposed in the API. In particular, each item will have a hidden tax item (e.g. if there are 3 items in the UI, there will be 6 Line Items in the API).

All of these aren’t explicitly distinguished in the API, but we can determine the type a combination of fields. Here are the relevant ones:

* **NumberInCollection**: The main identifying field for an item. Starts at 1, and increments based on the ordering of the items. Hidden items will start at 10001, and tax items are ordered according to the associated Line Item (e.g. the tax item of the second line item will have *NumberInCollection* 10002).
* **ParentLineNumber**: Used to associate Line Items. Non-Service and Parent Service Line Items will have *ParentLineNumber* = 0. Any Child Service Line Items or Tax Items will have *ParentLineNumber* equal to the *NumberInCollection* of the Non-Service or Parent Service Line Item.
* **LineType**: This field on any regular Line Item will be null. This field on any hidden line item will specify the type of item (e.g. SalesTax).
* **ServiceDetails.RequiresServiceEntry**: True for Parent Service Line Items, False for all other

For Non-Service and Parent Line Items, hidden items are filtered out based on Linetype, and Child Service Items will be imported as subitems of a group service:

|                                                    | Has Child Line Items   | No Child Line Items |
| -------------------------------------------------- | ---------------------- | ------------------- |
| *ServiceDetails.RequiresServiceEntry* is **True**  | Service                | Group Service       |
| *ServiceDetails.RequiresServiceEntry* is **False** | Doesn’t exist in Ariba | Item                |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.fairmarkit.com/buyers/integrations/sap-ariba-integration/purchase-requisition-sync/import-configurations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.