Skip to main content

xSuite Cube Installation Guide

Overview of steps when configuring a Vendor Portal

Step

Further information on the

1

Creating Portal users

To create a Portal user, use the transaction /WMD/XF_USR_ADMIN.

Specify the the following:

  • Activate tab Password → Option xSuite Portal user

  • Tab Attributes → Create attribute BSP_FPAYMENT_ENABLED. Value: X

This allows the user to create payment requests.

  • Tab Attributes → Create attribute VENDOR_INVOICE. Value: X

This allows the user to upload documents.

  • Tab Attributes → Create attribute VENDOR_INVOICE. Value: Vendor number

The value must consist of 10 digits. A shorter vendor number must be filled with leading zeros.

2

Creating public announcements

The start page shows a list of invoices from the current period in the standard target system. In addition, public and personal messages are displayed.

To create these notifications, use transaction /WMD/XF_VP_ANNOUNCE. In addition to normal texts, any HTML5 code and CSS3 code can also be entered. The code will be embedded directly into the Vendor Portal. Therefore, test it in advance in an HTML file.

3

Define possible target systems

The target systems are the multi-back-end systems, which are also used for the multi-back-end invoice monitor in xSuite Interface and for the payment requests.

For information on defining target systems, see "Define Targets for Multibackend" activity.

4

Defining target company codes with description

Each combination of target system and the company code available there represents a potential target for the vendor portal.

For information on defining target company codes, see "Target Descriptions" activity (Invoice).

5

Assign vendor number for target system

A Portal user must be assigned a vendor number for each target system.

For information on assigning target company codes, see "Assign Vendors" activity (Invoice).

6

Assign payment requests

Payment requests must be defined and assigned to a vendor.

For information on assigning payment requests, see "Record Types and Payment Requests" activity.