SE16 - Output SAP Table Content

Component Name and System Landscape

• Name: FCA_SAP_Tablecontent_List
• Description: SAP - BC: Tran SE16 - output SAP Table content
• Application: FCA_SAP_Transactions
• Type: RedwoodScript
• Other Info: SAP Manual - Transaction SE16

Brief Description

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

Parameter Mapping - Generic Tabs

There are several tabs under this section. Some will be generic, and others are specific to the component. The generic tabs usually are:

• Target: Requires SAP and Client information. You can also hard code the SAP username.
• Infrastructure: Used for Action rules. See the Redwood Finance Automation Reference.
• Recipient parameters: Generally left to default values.
• Job output parameters: Defines the format of the required output. Defaults to RTX and Text. See Porgam Handling for more information.

note

Most of the time these tabs will be shown, but there are components where these differ and either do not appear at all, or they are specific tabs.

Parameter Mapping - Specific Tabs

This guide shows the minimum parameter values required for the component to run. Please refer to the Redwood Automation Engineering Training course for submission and monitoring activities.

Tab	Technical Name	Description	Format	Mandatory Field	Example
Parameters	Delimiter	Delimiter		Yes	| or, or;
Parameters	Table	Table	<TableName>	Yes	SKB1
Parameters	Fields	Fields	<ColumName>		BUKRS, SAKNR
Parameters	Selection	Selection Criteria	See Defining the Where Clause section		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_1_LOGIC	Operation IN - Logic - 1	See Defining the Where Clause section	Yes	AND, OR
Operation - IN	OP_IN_1_FIELD	Operation IN - Field - 1	<ColumnName>		BUKRS
Operation - IN	OP_IN_1_VALUE	Operation IN - Value - 1	<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 examples when 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 <FieldName> 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).

• Operation IN – Logic – 1 → AND
• Operation IN – Field – 1 → VBELN
• Operation IN – Value – 1 → 0000004969

See example below using table VBAP and POSNR (Item).

• Operation IN – Logic – 2 → AND
• Operation IN – Field – 2 → POSNR
• Operation IN – Value – 2 → 000010

Troubleshooting

• Ensure the RFC user or the component user running the component have the required SAP authorization.
• It often happens that the component is configured ‘correctly’ but the output is empty because of SAP field formatting issues for example 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.
• The where clause is limited to 72 characters. However, it is possible to have a where clause with more than 72 characters. In order to achieve this, split up the clause in chunks of no more than 72 characters, separated by a semicolon.

See Also

Redwood Finance Automation Reference

financeTopic