> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/tcap/receiving-component-portion.md).

# Receiving component portion

The **transaction component received** (event) message is used by [TCAP](/telecom-references/ss7-and-signalling/tcap.md) to notify and send received component to TCAP service user.

If TCAP detects any syntax or semantic error in the received component (for example, unexpected component type), then it builds and queues a reject component and it generates a local reject indication to the TCAP service user. Then, the TCAP service user can send a **transaction component add** (reject component) message and **transaction data send** messages to the peer TCAP/service user. Previous statements are not valid when an erroneous component was received in a unidirectional, end (ITU TCAP), or response (ANSI TCAP) message. When this occurs, the rejected component is not queued.

The **component portion** contains the following parameters:

* TCAP userpart handle
* TCAP transaction identifier
* Component parameters
* Component reject source indicator
* Component specific parameters buffer


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/tcap/receiving-component-portion.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.