Configure Mapping Types

This section contains the following topics:

• Transaction - Basic
• Transaction - Header Detail
• Transaction - Block Types for Looping
• Transaction - Types of Loops
• BAPI/RFM - Basic
• BAPI/RFM - Header Detail
• GUI Script - Basic
• GUI Script - Header Detail
• Data Extractor - Basic

Transaction - Basic

This topic describes the different mapping types for Transaction technology that deal with single-line records. The mapping types allows you to customize the recording based on the Excel data file.

• Excel to SAP: Tells Process Runner to get the value from the Excel column.
• SAP to Excel: Tells Process Runner to place the value received from SAP in the specified Excel column.
• Fix Single Value: Tells Process Runner to use the value provided in the Map Value column.
• System Value: Tells Process Runner to use dynamically calculated value as provided in the Map Value column.
• Excel Cell Value: Tells Process Runner to place the value received from SAP in the specified Excel cell.

Transaction - Header Detail

This topic describes the block types that deal with multi-line (Header detail) documents by using loops. There are six ways to tell Process Runner how your Excel data is organized for a multi-line document.

• Fix Block: Where you know that number of detail rows is always fixed. Sometimes, you may want to run a loop for the same set of fields multiple times, defining the number of times you want to reprocess the loop. You can achieve this behavior using the Fix Block type for the block type and having a fixed value.

  

  To run a loop multiple times,

  1. In the Mapper, select the Start Loop and End Loop for the fields that you want to include in the loop.
  2. In the Block Type column, select Fix Block and define the number of times you want to run loop in the Block Value column. For example, 2.

     

  3. For the fields within the loop, select the Fix Single Value, System Value, or Excel Cell Value as mapping type.
  4. Save the Process file and select Run.
• On Change:Process Runner automatically determines a new transaction when the value changes. For example, you have document number repeated for each line in column F, you can use this block type and when there is new document number, Process Runner starts a new Header-Detail transaction automatically.

  

• On Change Ignore Blanks: Is the same as the On Change option, but instead of repeating the document number, you have blanks between the document numbers. Because a blank is a change, you want to tell Process Runner to ignore blank for considering them as a change. Process Runner ignores the blank and repeats the new Header-Detail transaction when it encounters new document number in column F.

  

• On Blank Cell In Column: For example, you are separating Header-Detail block by placing a blank line between each block of Header-Detail transaction. When Process Runner encounters a blank cell in mapped column, it automatically starts new Header-Detail transaction.

  

• On Value Ignore Blank: Because a blank is a change, you want to tell Process Runner to ignore blank for considering them as a change. Process Runner ignores the blank and starts a new loop when it encounters a value in column A.

  

• Legacy Loop: (Available only Transaction technology only) You can also specify which rows must be used as header and which rows must be used as a detail in a separate column. As shown in the following screenshot, headers are named as H and detail as D. You can give any user-defined names to header-detail items instead of just H and D.

  

  In the following screenshot of the mapper, L indicates that the legacy loop column contains the header and detail items.

  

Note: The two fields to map for Header-Detail looping are Block Type and Block Value. These fields are to tell Process Runnerhow data in Excel file is arranged. Also, you must update the Block Type and Block Value in the same row as the Start Loop.

When you set loops to upload multiple line items information, you can map Excel Column Index (column name) or Excel Column Header text (Excel header cell) in the Block Value column. For information about mapping Excel header Cell, see Map Excel Header. Note that this feature does not support to loop when Block Type is set to Fix Block.

Transaction - Block Types for Looping

Below is the sample excel data of a multi-line header detail transaction.

There are three types of Block Types for Header-Detail items in a loop.

• Start Value = Header line value
• Loop Value = Line item value
• Start + Loop Value = Header + Line item value

Start Value

In rare cases you have a field inside the loop that should always take value from header row. In that case, you would map "Start Value" for this field inside the loop. For example, in the above data file (Fig. 1), if we do not want to write “V0” in every detail item. We can write it only once as shown in Fig. 2 & map it as Start Loop (Fig. 3). It will consider “V0” as the block type for all subsequent detail items. (Fig. 4).

Figure 2

Figure 3

Figure 4

Loop Value

In some cases, you can have Header on row 2 and all the line items will be from row 3 as shown in Fig (5). In that case, you would map only "Loop value" for the fields inside the loop. So if we assign loop value (Fig. 6) for the detail items, Process Runner will pickup the detail items from the second row below the header item.

Figure 5

Figure 6

Start + Loop Value

In some cases, you can have Header is on row 2 and all the line items will be from row 3 as shown in the following screenshot. In that case, you would map "only Loop value" for the fields inside the loop. So if we assign loop value (Fig. 6) for the detail items, Process Runner picks up the detail items from the second row below the header item.

In some cases, you can have Header is on row 2 and also line starts from row 2. In that case, you would map "Start+Loop value" for the fields inside the loop.

Transaction - Types of Loops

To insert header and detail records, loop setting is necessary. Process runner supports multiple types of loops:

• Single Loop
• Loop inside another loop (Nested Loop)
• Parallel Loop (Multiple Loop)

Single Loop

Loop inside another loop (Nested Loop)

Parallel Loop (Multiple Loop)

BAPI/RFM - Basic

BAPI mapping types are different from that of transaction in the sense of UI. They are sensibly placed in their respective sections according to the Mapping action they perform.

For BAPI, Mapper is divided into 3 subsections:

• Upload to SAP
• Download from SAP
• Upload/Download from SAP

These mapping types deal with single-line records.

• Upload to SAP

  Fields that are input to SAP.

  

  • None: Removes any mapping previously assigned.
  • Excel to SAP: Indicates that the data will be uploaded from Excel to SAP. When mapping type is Excel to SAP, you can map the SAP field with Excel Column Index (column name) or Excel Column Header text (Excel header cell). For information about mapping Excel header Cell, see Map Excel Header.
  • Fix Single Value: Indicates that the value provided in the Map Value column is passed to SAP.
  • System Value: Indicates that the dynamically calculated value provided in Map Value column is used.
  • Excel Cell Value: Indicates that the value received from SAP will be fetched in the Excel cell specified in the Map Value column.

• Download from SAP

  Fields that are output from SAP.

  

  • SAP to Excel: Tells Process Runner to place value received from SAP to given Excel column.

• Upload/Download from SAP

  Fields that can act as both input or output to or from SAP.

  

BAPI/RFM - Header Detail

These mapping types deal with multi-line (Header detail) documents.

Consider the data as below in which one part is header and the other is detail. Both header details together constitute a Sales Document.

In column I there is a Sales Document column that will retrieve the sales document number when the document is posted. We have mapped that field to SAP to Excel in Download from SAP.

To execute the above date we need to configure loop in Process Runner. You can assign loop to a field from Block Type and Block value from Mapper. It will only be visible if you have enabled Advance view from Mapper toolbar.

Unlike Transaction, here there is no Start loop or End loop indicators. Inserting a Block Type and its consequent block value will automatically consider those fields in a loop.

You can tell Process Runner how it should loop through your Excel data. You can tell that Excel data is grouped in "Fix Block" or certain rows or grouped by similar values i.e. "On Change" or grouped by blank row in between them i.e. "Blank Row".

Following are the Block types supported.

• Fix Block

  Where you know that number of detail rows is always fixed, say 5 rows. Consider data where you have a fixed block of five records.

  

  In the Block Type column in Mapper (upload/download from SAP), map all the input records to Fix Block and update the Block value to 5 as the block length is 5 in our case.

  

• On Change

  In this type, Process Runner automatically determines new transaction when value changes. For example, if you have 2200 for each line in the column Sold to party column in E, you can use this mapping type and when there is a new number in column E, Process Runner starts a new Header-Detail transaction automatically.

  

  In Block Type column in Mapper (upload/download from SAP), map all the input records to On Change value to column E.

  

• On Change Ignore Blank

  Same as the On Change Ignore Blank option, but instead of repeating number, you have blanks between Sold-to-party numbers. It will ignore those blank and will repeat new Header-Detail transaction when it encounters new Sold-to-party number.

  

  In the Block Type column in Mapper (upload/download from SAP), map all the input records to On Change Ignore Blank and Block Value to column E.

  

• On Blank Cell In Column

  For example, you are separating Header-Detail block by placing a blank line between each block of Header-Detail transaction. You can use this mapping type and when Process Runner encounters a Blank Cell in mapped column, it automatically starts the new Header-Detail transaction.

  

  In the Block Type column in Mapper (upload/download from SAP), map all the input records to On Blank Cell In Column and Block Value to column E (or any column that indicates the end of the document).

  

• On Value Ignore Blank

  Since a blank is a change, you want to tell Process Runner to ignore blank for considering them as a change. For example you have blanks between Sold-to-party numbers. Process Runner ignores those blanks and repeats new Header-Detail transaction when it encounters a Sold-to-party number.

  

  In the Block Type column in Mapper (upload/download from SAP), map all the input records to On Value Ignore Blank and Block Value to column E.

  

When you set loops to upload multiple line items information, you can map Excel Column Index (column name) or Excel Column Header text (Excel header cell) in the Block Value column. For information about mapping Excel header Cell, see Map Excel Header. Note that this feature does not support to loop when Block Type is set to Fix Block.

GUI Script - Basic

Mapping types in GUI script are similar to those of Transaction. These mapping types deal with single-line records.

• Excel to SAP: Tells Process Runner to get the value from Excel column.
• Fix Single Value: Tells Process Runner to use the value provided in the Map Value column.
• System Value: Tells Process Runner to use dynamically calculated value as provided in the Map Value column. For example, in the below capacity planning download we want to assign the file name for the downloaded file consisting of year, month, day, hours and seconds. For that we use system value and assign it as shown in the following screenshot.

  

  

• You can see in the following screenshot how the file is created, after assigning system value as the mapping type.

  

• Fix Multi-line Value: Tells Process Runner to place a range of values as shown in the following screenshot.

  

• Excel Cell Value: Tells Process Runner to place value received from SAP to the given Excel cell.

GUI Script - Header Detail

Following are the various mapping types supported in GUI Scripting module:

• Fix Block

  Where you know that number of detail rows is always fix, say 4 rows.

  

  Mapping is as displayed in the following screenshot.

  

• On Change

  Process Runner automatically determines new transaction when value changes. For example, you have Document number repeated for each line in column E, You can use this mapping type and every time there is new Document number, Process Runner will start a new Header-Detail transaction automatically.

  

  Mapping is as displayed in the following screenshot.

  

• On Change Ignore Blanks

  This option is the same as the On Change option, but instead of repeating Document number, you have blanks between Document numbers. Since a blank is a change, you want to tell Process Runner to ignore blank for considering them as a change.  With this mapping type, Process Runner will ignore those blank and will repeated new Header-Detail transaction when it encounters new Document number in column E.

  

  Mapping is as displayed in the following screenshot.

  

• On Blank Cell In Column

  For example, you are separating Header-Detail block by placing a blank line between each block of Header-Detail transaction. You can use this mapping type and anytime Process Runner encounters a Blank Cell in mapped column, it will automatically start new Header-Detail transaction.

  

  Mapping is as displayed in the following screenshot.

  

• On Value Ignore Blank

  Same as the On Change Ignore Blank option, but instead of changing value, it always starts a new transaction when it finds a value in the column whether it’s same or different. It will ignore blank. In the following example it will consider line 6 as new header-detail transaction even though the document header text is similar to previous one.

  

  Mapping is as displayed in the following screenshot.

  

• Legacy Loop

  Additionally to above mentioned methods, you can also specify which rows to be used as header and which to use as a detail in a separate column. As shown below, Headers are named as H and detail as D. You can give any user defined names to header-detail items instead of just H and D.

  

  In the following screenshot of the mapper, K indicates the Legacy loop column H and D indicate Header and detail items.

  

Note: There are two fields to map for Header-Detail looping - one is Block Type and another is Block Value. These two fields are over and above regular mapping fields. These fields are used together to tell Process Runner how data in Excel file is arranged.

Note: You maintain Block Type and Block Value in the same row as the Start Loop.

When you set loops to upload multiple line items information, you can map Excel Column Index (column name) or Excel Column Header text (Excel header cell) in the Block Value column. For information about mapping Excel header Cell, see Map Excel Header. Note that this feature does not support to loop when Block Type is set to Fix Block.

Data Extractor - Basic

Data extractor only has one mapping type that is SAP To Excel. The SAP to Excel mapping type tells Process Runner to place value received from SAP to the given Excel column.