Automate

Hi Automate Community!

This week I have a quick tip on using cell based mapping instead of the default column mapping in Transaction. Typically, column mapping is used to mass upload data to SAP, but there might be certain use cases or scenarios when a mass upload isn't necessary and you have an Excel form you want to use instead. The use case I'll cover today is for a sales order form, but this can apply to any transaction code or SAP use case. For example, you might want to upload one journal entry at a time or you might get the data in an Excel form and you prefer to load it into SAP using that format instead of reformatting it to column based.

Here is an example of an Excel form that would need cell based mapping:

Here is another example showing a Journal Entry:

There are a few differences to note when using cell based mapping instead of column mapping. 

1. When you map the script, you will switch the mapping type to "Cell Based Mapping" in the ribbon on the Map tab before you start mapping:
2. If the script needs a loop, you will have two options for the line items. The first option is to use identifiers. This will require "D" or whatever you specify to indicate a line item row. The second option is to use a row range where you specify the start and end of the line items in the spreadsheet. For my sales order example, the line items start on row 11. Here are screenshots for both:
3. When you map the script, everything will be mapped to a cell unless you have a loop. If you have a loop then the validate log and SAP fields in the loop will be mapped to columns. Here is an example from the sales order script:

I hope this gives you ideas on different ways to do your data uploads into SAP. If you've used cell based mapping for a use case, let us know! I'm sure the Community would love to hear about other use cases for this. 

Thanks!