> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arc.cdata.com/llms.txt
> Use this file to discover all available pages before exploring further.
# SAP IDoc Send
> Configuration for sending IDoc files to SAP using the Arc SAP IDoc connector.
## Connector Configuration
The following settings are available when you are sending IDoc files to SAP.
#### Control Record Information Options
When you are receiving IDoc files from one SAP system and sending them to another SAP system you might want to change the control record information without changing the IDoc file data. See [Sending IDocs to SAP](#sending-idocs-to-sap) for more information.
To overwrite the control headers for IDoc files, check **Overwrite**, then make your changes to the following options.
| Setting | Description |
| -------------------------------------- | -------------------------------------------------------------------------- |
| **SAP Release (DOCREL)** | The SAP Release for IDOC. |
| **Test Flag (TEST)** | The flag which indicates whether the IDoc should be in test mode. |
| **Sender Port (SNDPOR)** | The sender port (SAP System or external subsystem). |
| **Sender Partner Number (SNDPRN)** | The sender's partner number. |
| **Sender Partner Type (SNDPRT)** | The sender's partner type. |
| **Sender Partner Function (SNDPFC)** | The sender's partner function. |
| **Sender Address (SNDSAD)** | The sender's address. |
| **Logical Address (SNDLAD)** | The sender's logical address. |
| **Receiver Port (RCVPOR)** | The receiver port. |
| **Receiver Partner Number (RCVPRN)** | The receiver's partner number. |
| **Receiver Partner Type (RCFPRT)** | The receiver's partner type. |
| **Receiver Partner Function (RCVPFC)** | The receiver's partner function. |
| **Recipient Address (RVCSAD)** | The receiver's address. |
| **Receiver Logical Address (RCVLAD)** | The receiver's logical address. |
| **Use System Date/Time** | Whether to include the system date/time in the control record information. |
#### Advanced Settings
*Settings not included in the previous categories.*
| Setting | Description |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Processing Delay** | The amount of time (in seconds) by which the processing of files placed in the **Transactions** tab is delayed. This is a legacy setting. Best practice is to [use a File connector](./Designing-a-Flow#interacting-with-the-local-file-system) to manage local file systems instead of this setting. |
| **Refresh Schema** | When enabled, the connector attempts to update the schema it uses for parsing when a parsing error occurs. The schema is updated by reaching out to the SAP system and querying for the appropriate schema. |
| **Local File Scheme** | A scheme for assigning filenames to messages that are output by the connector. You can use macros in your filenames dynamically to include information such as identifiers and timestamps. For more information, see [Macros](#macros). |
| **Upload Schema** | Use this to upload a schema and install it in the connector's Schema folder. If a schema already exists, you are asked if you want to overwrite it. |
#### Message
The **Save to Sent Folder** and **Sent Folder Scheme** settings are deprecated and hidden by default. They appear only on connectors where they were previously enabled or configured to a non-default value. To retain copies of successfully processed files, right-click the connector in the flow, choose **Show Success Path**, and connect the success path to a [File connector](../file).
| Setting | Description |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Save to Sent Folder** (Deprecated) | Copies files processed by the connector to the Sent folder. Disabled by default. Files saved to the Sent folder are not covered by [Encryption at Rest](/26.3/self-hosted/en/getting-started/administration/settings/encryption-at-rest). |
| **Sent Folder Scheme** (Deprecated) | Groups files in the **Sent** folder by the selected time interval. Only relevant when **Save to Sent Folder** is enabled. |
#### Logging
*Settings that govern the creation and storage of logs.*
| Setting | Description |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Log Level** | The verbosity of logs generated by the connector. When you request support, set this to **Debug**. |
| **Log Subfolder Scheme** | Instructs the connector to group files in the Logs folder according to the selected interval. The **Weekly** option (which is the default) instructs the connector to create a new subfolder each week and store all logs for the week in that folder. Leaving this setting blank tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance. |
| **Log Messages** | Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the **Transactions** tab. |
#### Miscellaneous
*Miscellaneous settings are for specific use cases.*
| Setting | Description |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Other Settings** | Enables you to configure hidden connector settings in a semicolon-separated list (for example, `setting1=value1;setting2=value2`). Normal connector use cases and functionality should not require the use of these settings. |
## Sending IDocs to SAP
Once you have configured the IDoc connector to connect to your SAP system, you can begin sending IDoc files to SAP. The IDoc connector can send files formatted in raw IDoc or XML IDoc.
You can configure the connector to automatically insert control record information into the IDoc being sent to SAP: the DOCREL, SNDPOR, SNDPRT, and so on. This makes it easier to process outgoing IDocs to the configured system. Configure these settings in the [Control Record Information Options](#control-record-information-options) section of the **Settings** tab.
Before sending an IDoc to your SAP system, make sure that you have properly configured a partner profile in SAP. If no partner profile in SAP matches the control record information in the IDoc you are sending, the data will not be processed by your SAP system. See [Test Sending an IDoc to SAP](#test-sending-an-idoc-to-sap) for more information on setting up a partner profile.
You can use transaction code WE60 to search for segment documentation for different IDoc types.
### Test Sending an IDoc to SAP
To test sending an IDoc to SAP, you first need to configure your SAP system to have a partner profile for Arc. The following steps describe how to do this with an ORDERS IDoc.
1. *Create a partner:* Go to transaction code WE20 and define a partner profile. Set **Partn Type** to **KU** for Customer and **Partner No** to a valid customer number.
2. *Add an inbound parameter for the ORDERS document:* The message type for this document is ORDERS. On the **Inbound Options** tab, set **Process code** to **ORDE** to tell SAP how to create a sales order when a purchase order ORDERS document is received by the SAP system.
3. *Assign the customer to a sales division:* The customer configured in step one must be assigned to a sales organization, distribution channel, and division. Go to transaction VOE2 to configure these settings in the EDSDC table.