In this article

Table of Contents

minLevel	1
maxLevel	2
absoluteUrl	true

Overview

You can use this Snap to expand the Teamcenter BoM structure to one level.

...

Snap Type

The <Snap name> Teamcenter BOM Structure Get Snap is a Read/Write/Parse/Transform/Flow/Format-type Snap that reads/fetches/writes/parses/executes/transforms/calls/creates… expands the Teamcenter BoM structure with one level.

Prerequisites

Valid client ID.
A valid account with the required permissions.

None.

Support for Ultra Pipelines

Works in Ultra Pipelines.
Works in Ultra Pipelines if....
Does not support Ultra Pipelines.

Limitations

...

None.

and Known Issues

None.

Snap Views

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input

Document

Binary

Binary or Document

Min: 1
Max: 1

Mapper
Copy
..

Requires the EDI data and internal ID as a JSON document

JSON Generator
Teamcenter BOM Structure Create

The Revision Rule, Mode and Object ID that needs to be fetched from the Teamcenter.

Output

Document

Binary

Binary or Document

Min: 1
Max:

..
..

The EDI transaction ID and order confirmation

1

Teamcenter Classification Detailed Info
Teamcenter BOM Structure Get Recursive

The expanded level of BOM Structure.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter when running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

Stop Pipeline Execution: Stops the current Pipeline execution if the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

...

{"features":["title","icon","rounded","collapsible","border"],"title":"Documenting Fields Based On Data Type/UI Element","titleColor":"#000000","titleColorBG":"#ff5c30","titleSize":"14","titleBold":true,"titleItalic":false,"titleUnderline":false,"lozenge":"Hot stuff","lozengeColor":"#172B4D","lozengeColorBG":"#fff0b3","height":200,"panelPadding":12,"panelColor":"#172B4D","panelColorBG":"#FFFFFF","borderColor":"#ff5c30","borderRadius":3,"borderStyle":"solid","borderWidth":1,"icon":"editor/info","iconPrimary":"#FFFFFF","iconSecondary":"#0052CC","newMacro":false}
Delete Before Publishing
Choose from the following sentences to document specific field types.
Drop-down lists/Option Buttons (radio buttons):
You must list the LoV and describe them if their meaning isn't apparent. In this case, format the LoV in italics, regular font for the LoV's description. In either case, list the LoVs as a bullet list.
<State what the option should do in this field>. The available options are: <bullet list of LoVs>
Specify the Salesforce API to be used. The available options are:...
Select the <category> that you want to use. Available options are...
* Option 1<italicized>. <third person singular form of the verb>
* Option 2<italicized>. <third person singular form of the verb>
Select the API that you want to use. Available options are:
Bulk API. Sends the Snap execution request details as a bulk API call.
REST API. ...
OR
Select one of the three following modes in which the Snap executes:
* Validate & Execute. Performs limited execution of the Snap and generates a data preview during Pipeline validation, then performs full execution of the Snap (unlimited records) during Pipeline runtime.
* Execute only. Performs full execution of the Snap during Pipeline execution without generating preview data.
* Disabled. Disables the Snap and all Snaps downstream from it.
Check boxes:
If selected, <Snap behavior>.
If selected, an empty file is written when the incoming document has no data.
If selected, <behavior>. If not selected/Otherwise, <behavior>
Use "If not selected" if the first sentence is long.
If selected, the Snap uses the file path value as is. Otherwise, the Snap uses the file path value in the URL.
If selected, an empty file is written when the incoming document has empty data. If there is no incoming document at the input view of the Snap, no file is written regardless of the value of the property.
Select to <action>
Use this if the behavior is binary. Either this or that, where the converse behavior is apparent/obvious.
Select to execute the Pipeline during validation.
Text Fields
Describe what the user shall specify in this field. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc.
Enter the name for new account.
Specify the account ID to use to log in to the endpoint.
Required if IAM Role is selected.
Do not use this field if you are using batch processing.
Numeric Text Fields
Describe what the field represents/contains. Additional details, as applicable, in a separate sentence. Include caveats such as the field being conditionally mandatory, limitations, etc. Include special values that impact the field's behavior as a bullet list.
The number of records in a batch.
The number of seconds for which you want the Snap to wait between retries.
The number of seconds for which the Snap waits between retries.
Use the following special values:
* 0: Disables batching.
* 1: Includes all documents in a single request.
Notes in field descriptions
Confluence’s new editor does not allow nesting of most macros inside another macro, especially the Note/Alert/Warning/Info (Panel) macros inside a table macro and Excerpt macros inside Expand or Panel Macro+ macros. So, as a workaround use the Footnotes approach as mentioned below:
Assign numbers at the Note locations in the form of follow through phrases like See Note 2 below this table. or such.
Add your Notes---an appropriate Note/Alert/Warning/Info (Panel) macro---immediately below the macro (for example, Table macro) beginning the content with the corresponding number assigned.
Info
Asterisk ( * ): Indicates a mandatory field.
Suggestion icon (): Indicates a list that is dynamically populated based on the configuration.
Expression icon ( ): Indicates the value is an expression (if enabled) or a static value (if disabled). Learn more about Using Expressions in SnapLogic.
Add icon ( ): Indicates that you can add fields in the fieldset.
Remove icon ( ): Indicates that you can remove fields from the fieldset.
Upload icon ( ): Indicates that you can upload files.
Specify advanced parameters that you want to include in the request.
Field Name
Field Type
Field Dependency
Description
Label*
Default Value: ELT Database Account TC Structure Get
Example: ELT RS AccountTC Structure Get
String
None.
The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.
Number of recordsRevision Rule*
Default Value: N/A
Example: 3<1
String/Expression
Sampling Type is Number of records.
Enter the number of records to output.
fieldset Name
Field 1*
Default Value: <value> or None.
Example: <value>
String
Debug mode check box is not selected.
Field 2
Default Value: <value> or None.
Example: <value>
String
NoneSpecify the revision rule that you want the Snap to use for the structure expansion.
Mode*
Default Value: Inline
Example: collect
Dropdown
Select the mode in which you want to showcase the results. The options available are:
each
inline
collect
Object ID*
Dropdown
Select the UID (unique identifier) or the Teamcenter adapter ID of the object.
Type

Default Value: N/A
Example: Diameter
String/Expression
Specify the name of the Teamcenter type.
Expand Attributes
Specify the attributes you want the Snap to fetch from Teamcenter. Each atribute must be specified as a new row. Click to add a row.
Name*
Default Value: None.
Example: Item_response
String
Specify the name of the attribute.
Snap Execution
Default Value:
Example: Validate & Execute
Dropdown listN/A
Select one of the following three modes in which the Snap executes:
Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
Disabled: Disables the Snap and all Snaps that are downstream from it.

Troubleshooting

...

Error

...

Reason

...

Resolution

...

Account validation failed.

...

The Pipeline ended before the batch could complete execution due to a connection error.

...

Verify that the Refresh token field is configured to handle the inputs properly. If you are not sure when the input data is available, configure this field as zero to keep the connection always open.

...

Examples

Excluding Fields from the Input Data Stream

We can exclude the unrequired fields from the input data stream by omitting them in the Input schema fieldset. This example demonstrates how we can use the <Snap Name> to achieve this result:

Download this Pipeline.

Downloads

Info
Download and import the Pipeline into SnapLogic. Configure Snap accounts, as applicable. Provide Pipeline parameters, as applicable.

Attachments

patterns	.slp, .zip
sortBy	name

Snap Pack History

...

title	Click here to expand...

...

Versions Compared

Old Version 3

New Version 4

Key

Overview

Snap Type

Prerequisites

Support for Ultra Pipelines

Limitations

and Known Issues

Snap Views

Snap Settings

Troubleshooting

Examples

Excluding Fields from the Input Data Stream

Downloads

Snap Pack History

Related Content

Related Content

Field Name		Field Type	Field Dependency	Description
Label* Default Value: ELT Database Account TC Structure Get Example: ELT RS AccountTC Structure Get		String	None.	The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your Pipeline.
Number of recordsRevision Rule* Default Value: N/A Example: 3<1		String/Expression	Sampling Type is Number of records.	Enter the number of records to output.	fieldset Name	Field 1* Default Value: <value> or None. Example: <value>	String	Debug mode check box is not selected.	Field 2 Default Value: <value> or None. Example: <value>	String	NoneSpecify the revision rule that you want the Snap to use for the structure expansion.
Mode* Default Value: Inline Example: collect		Dropdown	Select the mode in which you want to showcase the results. The options available are: each inline collect
Object ID*		Dropdown	Select the UID (unique identifier) or the Teamcenter adapter ID of the object.
Type Default Value: N/A Example: Diameter		String/Expression	Specify the name of the Teamcenter type.
Expand Attributes	Specify the attributes you want the Snap to fetch from Teamcenter. Each atribute must be specified as a new row. Click to add a row.
Expand Attributes	Name* Default Value: None. Example: Item_response	String	Specify the name of the attribute.
Snap Execution Default Value: Example: Validate & Execute		Dropdown listN/A	Select one of the following three modes in which the Snap executes: Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime. Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data. Disabled: Disables the Snap and all Snaps that are downstream from it.

Page Comparison

Versions Compared

Old Version 3

New Version 4

Key

Overview

Snap Type

Prerequisites

Support for Ultra Pipelines

Limitations

and Known Issues

Snap Views

Snap Settings

Troubleshooting

Examples

Excluding Fields from the Input Data Stream

Downloads

Snap Pack History

Related Content

Related Content