These mapping types deal with multi-line (Header detail) documents.
Consider the data as below in which 1 part is header & the other is detail.
Both header details together constitute a Sales Document.
In column I there is a Sales Document column which will retrieve the sales document number once document is posted. We have mapped that field to SAP to Excel in Download from SAP

In order to execute the above date we need to configure loop in Process Runner.
You can assign loop to a field from Block Type & 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 & its consequent block value will automatically consider those fields in a loop.
Block Type and Block Value: Using this column will automatically include loop for your mapped data. In case of looping through Excel data, using this column 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 in Process Runner.
Where you know that number of detail rows is always fix, say 5 rows. Consider user data as below where one has a fix block of five records.

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

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

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

|
Same as 2, 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 block type column in Mapper (upload/download from SAP), we need to map all the input records to On Change ignore blank & Block value to column E.

|
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.

In block type column in Mapper (upload/download from SAP), we need to map all the input records to On Blank cell in column & Block value to column E (or any column that indicates the end of the document).

Note: If human eye can intelligently determine header and detail by looking at data, Process Runner will also be able to map that WITHOUT forcing you to change the data.
|
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. It will ignore those blank and will repeat new Header-Detail transaction when it encounters a Sold-to-party number.

In block type column in Mapper (upload/download from SAP), we need to map all the input records to On Value ignore blank & Block value to column E.

|
Next:
GUI Script - Basic
|