SAP – BC: Tran SE16 – Output SAP Table Content

Component Name and System Landscape

Name: FCA_SAP_Tablecontent_List
Description: SAP – BC: Tran SE16 – Output SAP Table An object used to store values; much like a table in a database or a spreadsheet in Microsoft Excel. content
Application An object used to group objects like process definitions and chains.: FCA_SAP_Transactions
Type: RedwoodScript
Other Information: SAP Manual – Transaction SE16

Prerequisites

Attendance of the Automation Engineering Training Course.

Intended Audience

This component is intended for use by Automation Engineers during the build phase of business processes within the Redwood Platform. The purpose of this guide is to provide a reference of the minimum 'bare bones' requirements needed to get the component started and produce a result. During Customer implementations, a version of this document can be enhanced to include any additional parameters that may need to be used for specific requirements.

Brief Description

This component allows for data retrieval from SAP Tables. Same concept as the SE16 SAP Program.

Accessing the Component

There are two main ways to access the component:

Definition > Chain (To configure and submit component as part of a wider Business Process A process is a Process Definition that is submitted into a queue. When users request the execution of a chain, a process server creates a record in the Job table, calculates the start time and sets the status to Assigned.). Refer to the reference guide.
Definition > Process (To configure and submit component in isolation)

Menu Path: Control Center > Definitions > Processes:

Type in the Search Process Definitions filter box any abbreviation of what you are looking for and click on search button within the box. For example: Enter search term TABLE and hit search. This will bring up the list of components associated with the name. Select one and do a right hand click on the mouse. From the drop-down menu click on submit.

Parameter Mapping – Generic tabs

There are several tabs under this section. Some will be generic whilst others are specific to the component.

The generic tabs usually are:

Target – Requires SAP and Client information. You can also hard code the SAP user name.
Infrastructure – Used for Action rules. See Reference Guide.
Recipient parameters – Generally left to default values.
Job output parameters – Defines the format of the required output. Defaulted to RTX and Text.

Parameter Mapping - Specific tabs

This guide is only meant to show the minimum parameter values required for component to run as a starting point. See the Conventions section above for the field formatting tips.

Refer to the Redwood Training course for submission and monitoring activities,

Tab	Technical Name	Description	Format A format can be assigned to a process definition. The format defines the type of output that the process generates or captures.	Mandaotry	Example
Parameters	Delimiter	Delimiter		Mandatory	`\|,` or `;`
Parameters	Table	Table	`<TableName>`	Mandatory	`SKB1`
Parameters	Fields	Fields	`<ColumName>`		`BUKRS, SAKNR`
Parameters	Selection	Selection Criteria	**See notes on Where clause SAKNR IN ('11000')
Parameters	OrderBy	Sorting Criteria	Comma sep list + `ASC` or `DESC`
Parameters	Limit	Limit of records to read `500`
Parameters	Rowskips	Number of records to skip `100`
Parameters	Error	Raise error on			Empty or Found
Operation - IN	`OP_IN_<n>_LOGIC`	Operation IN - Logic - `<n>`	**See notes on Where clause Mandatory `AND`, `OR`
Operation - IN	`OP_IN_<n>_FIELD`	Operation IN - Field - `<n>`	`<ColumnName>`		BUKRS
Operation - IN	`OP_IN_<n>_VALUE`	Operation IN - Value - `<n>`	`<value>`		1000

Defining the where clause

When configuring the component, it is important to define a Where clause to ensure we only query the necessary data from SAP. This can be achieved by either populating the Selection Criteria parameter or by using the parameters in the Operation IN tab.

See below for examples of using the Selection Criteria parameter.

BUKRS IN ('1000, 2000) This condition is true if the column Company Code does contain one of the values 1000 or 2000.

BUKRS NOT IN ('1000', '2000') This condition is true if the column Company Code does not contain the values 1000 or 2000.

BUKRS = '1000' This condition is true if the column Company Code has the contents 1000.

BUKRS NE '1000' This condition is true if the column Company Code does not contain the string 1000.

BUKRS NOT BETWEEN '1000' AND '2000' This condition is true if the column Company Code is one character long and its contents are not between 1000 and 2000.

BUKRS LIKE '%1000%' This condition is true if the column Company Code contains a string containing the pattern '1000'.

BUKRS NOT LIKE '1000%' This condition is true if the column Company Code does not contain a string containing the pattern '1000'.

The Operation IN tab allows you create a simple WHERE clause with the condition IN. All you need to do is populate the with the Column Name and the value(s). The tab contains 5 different options (parameter combinations) so you can add lookups on multiple columns. The Operation Logic parameter allows you to add some AND/OR logic to the Where clause. See example below using table VBAP and columns VBELN (Sales doc) and POSNR (Item).

Operation IN - Logic - 1 -> AND
				Operation IN - Field - 1 -> VBELN
				Operation IN - Value - 1 -> 0000004969
				Operation IN - Logic - 2 -> AND
				Operation IN - Field - 2 -> POSNR
				Operation IN - Value - 2 -> 000010

Troubleshooting tips

Mention any tips and tricks that would help in ensuring the process runs efficiently.

Tab	Technical Name	Description	Comment
N/A	N/A	N/A	Ensure the RFC user or the component user running the component have the required SAP authorization.
N/A	N/A	N/A	It often happens that the component is configured 'correctly' but the output is empty because of SAP field formatting issues e.g. `VBLEN(0000004969)`. In this case, it is best to test the component first with only a few records. Execute the component, specify a table name and set the Limit parameter to 100 records. The output will then show the necessary formatting and how much padding is needed in certain fields. You can then build your where clause appropriately.
Parameters	Selection	Selection Criteria	The where clause is limited to 72 characters. Split the clause in chunks of no more than 72 characters, separated by a semicolon.