edoc invoice cockpit Administration Guide
edoc invoice cockpit Administration Guide
Breadcrumbs

Configure field mappings for SAP Cloud ERP

You can make additional field mappings in edoc invoice cockpit to transfer additional invoice data to your destination system.

Before you begin

You configure the edoc invoice cockpit application via REST-API. For details about using the REST API and the API documentation see: Using the REST API of edoc invoice cockpit

To use the REST API, you must authenticate yourself as an administrative user with the REST API: Authenticate the administrative user to the edoc invoice cockpit REST API

Here's how

  1. Create a REST query according to the OpenAPI documentation to create a field mapping.

  2. Under description, enter a meaningful description for the field mapping and its purpose.

  3. Under source_invoice_section, enter the invoice data section of an invoice from the invoice processing workflow. The data for the mapping is taken from the specified section. You can use one of the following options in the REST API for the mapping:

    1. transfer_status: Indicates that the data is taken from a field from the status transfer metadata.

    2. transfer_headvalue: Indicates that the data is taken from a field in the invoice header.

    3. transfer_positionvalue: Specifies that the data is taken from one field from each invoice line.

  4. Under destination_invoice_section, enter the section of the invoice data for an invoice from the destination system. The data for the mapping is transferred in the specified section. You can use one of the following options in the REST API for the mapping:

    1. null: Indicates that the data is transferred to a field in the invoice header.

    2. to_SupplierInvoiceItemGLAcct: Specifies that the data is transferred to a field in the G/L account lines.

    3. to_SuplrInvcItemPurOrdRef: Specifies that the data is transferred to a field in the purchasing document references.

  5. Specify the mapping type for this field mapping under mapping_type. You can use one of the following options in the REST API for the mapping:

    1. Field_Mapping: Specifies that data is taken from the specified source section of the specified source field and transferred to the specified destination section of the specified destination field.

    2. Static_Function: Specifies that an edoc invoice cockpit internal function is used to determine the value for the specified destination field.

    3. Static_Text: Specifies that a static text is always written to the specified destination field.

  6. For the Field_Mapping mapping type, enter the source field in the specified source section from which invoice data is to be taken for the transfer under source_field.

  7. Under destination_field, enter the destination field in the specified destination section to which the mapped data is to be transferred.

  8. Specify the data type of the destination field in the destination system under destination_field_datatype. You can use one of the following options in the REST-API for the mapping:

    1. boolean: Indicates that this is a Boolean field.

    2. datetime: Indicates that this is a field with date and time.

    3. string: Indicates that this is a field with numbers, letters and special characters.

  9. Optionally, enter the length of the field in your destination system under destination_field_size. If you do not specify a field length, the value from the mapped field is transferred without validating the field length.

  10. For the Static_Text mapping type, enter the static value to be written to the destination field under destination_static_value.

  11. Under active, use a Boolean value to specify whether the mapping should be used.

  12. Send the REST request.

With the field mapping, the corresponding invoice data is now transferred to your SAP Cloud ERP system.