# Owning Package Configuration

## Overview

The Owning Package field is applicable to MBSE connectors. It enables users to explicitly define the target project and package where synchronized data will be written. This field provides greater control over data placement by allowing users to override the project selected at the integration level.

## Behavior and Functionality

### Purpose

1. Displays a lookup of available Project Display Names / Package Qualified Names.
2. Allows users to specify the exact project and package where OIM should write the data.
3. Overrides the default project selected during integration configuration.

In other words, even if a project is selected at the integration level, the Owning Package selection determines the final destination for the synchronized artifact.

### Behavior at Mapping Level

1. When a specific project is selected at the mapping level:

   (a)The Owning Package field displays all available packages within the selected project.

   (b)Users can select the appropriate package where the data should reside.

   <div align="center"><img src="/files/LQTJoBsnLUOUJuxO6poy" alt="Package Selection Criteria Configuration" height="436" width="418"></div>
2. When a workspace is selected as the project, the Owning Package field displays the complete hierarchical paths of:

   (a) All projects within the workspace

   (b) All packages under each project

   (c) This allows selection of any valid package across the entire workspace structure.

   <div align="center"><img src="/files/oyFjYCWfGgbvoxaoGi69" alt="Package Selection Criteria Configuration" height="436" width="418"></div>


---

# 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://opstech.gitbook.io/opstech-docs/mbse-connector-sdk-index/oim-configuration-for-mbse/owning-package-lookup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.