Generic transfer configuration

With the option “generic”, that can be configured in the AdminClient, any RFC module on SAP side can be used to specify the transfer mapping, which is used to update values originating from SAP in ImageMaster. However, the update option can only be used with a valid license for ImageMaster MetadataSync for ERP.

Figure 444: ImageMaster generic transfer configuration – settings

Figure 445: ImageMaster generic transfer configuration – mapping

With the option “Generic” any RFC module on SAP side can be used. A transfer can be specified from the perspective of the SAP system:

  • Import (into SAP)

  • Export (from SAP)

  • Changing (a combination of import and export)

  • Tables (support for multiple rows in the context of multi-value attributes)

Generic elements of an RFC module

Import

Parameters (single or structures) that can be handed over to the RFC module

Mandatory parameters are marked with an asterisk (*).

These can be filled with fixed values, custom attributes, system attributes, SAP attributes, content properties or binary object properties (see Data location identifier).

Export

Parameters (single or structures) that are handed over from SAP via the RFC module

It is possible to define custom attributes which should be updated with the provided value (single value only!).

Changing

Parameters (single or structures) that can be handed over to the RFC module, which will receive a changed value in a response from the call

Mandatory Parameters are marked with an asterisk (*).

These can be filled with fixed values, custom attributes, system attributes, SAP attributes, content properties or binary object properties (see Data location identifier).

If system attributes are provided optionally, the update flag can be set so the custom attributes will be updated with the provided value (single value only!).

Tables

Tables are treated in a special way. They can have either the characteristics of import parameters or export parameters – just with multiple rows.

Each cell of a table can be filled and for all cells the same rules apply: These can be filled with fixed values, custom attributes, system attributes, SAP attributes, content properties or binary object properties (see Data location identifier).

Multi-value attributes are supported. For details see the sections on the handling of multi-value attributes beneath this table.

Table 256: Generic transfer configuration settings

Handling of multiple multi-value attributes in tables

Let’s assume:

  • Attribute A has 5 values.

  • Attribute B has 3 values.

  • Attribute C has 1 value.

    Column 1

    Column 2

    Column 3

    A1

    B1

    C

    A2

    B2

    C

    A3

    B3

    C

    A4

    N/A

    N/A

    A5

    N/A

    N/A

The following rules apply:

  • Single value attributes are repeated for all rows.

  • If multiple multi-value attributes are in a table (like A and B above), the maximum number is limited by the multi-value attribute with the lowest number of multiple values. This is attribute B in the example above with 3 values.

Handling of multi-value attribute updates in tables

Each column of a table can be marked as update. Enabling the update flag for the first cell of a column (which must be a custom attribute), every cell in that column will be considered to be updated. However, as it is not predictable how many rows in a table will be provided by the RFC module, the following rule applies:

Let’s assume:

  • Attributes A and B are multi-value attributes and C is a single value.

  • Attribute A has the values 1,3,5.

  • Attribute B has the values 7, 9, 11.

  • Attribute C has the value 2.

    Column 1

    Column 2

    Column 3

    A (update=true)

    B (update=true)

    C (update=true)

  • SAP will return values for each cell for each row:

    Column 1

    Column 2

    Column 3

    1

    7

    2

    3

    9

    2

    5

    11

    2

The following rule applies:

  • If SAP provides different values for a single value attribute, the first value will be used for updating the attribute in ImageMaster.

For a proper configuration it is mandatory to understand what the RFC module is intended for. You need some documentation on your specific use case describing the characteristics and behavior of the RFC module.

Extension points exist for internal customizations that can be provided by T-Systems.