Skip to main content

xSuite Cube Installation Guide

"Record type" tab → "General data" area

/WMD/BC_SPRO → xSuite Business Solutions → Interface → Define Record Types

The General Data area affects all record types and is therefore configured independent of xSuite application. Special application-specific features are pointed out.

Field

Description

Description

Freely selectable term such as "invoices" or "sales orders"

Program

The name of a program that processes the data after the import is specified here. This is required if you want to park or post automatically without performing prior manual validation in SAP.

The following programs are provided by xSuite Group GmbH as examples:

  • /WMD/FP_INVB for incoming invoices

  • /WMD/FP_SD_BATCH for sales orders

  • /WMD/FP_OCB for purchase order confirmations

  • /WMD/FP_AR_BATCH for ArchiveLink scenarios

  • /WMD/FP_DNMB for delivery notes

Primary table

Imported data is first written to an interface table, which is referred to below as the primary table for header data. Depending on the application type, the following primary tables are used:

  • /WMD/FP_IFIVH for invoices (application type 1)

  • /WMD/FP_IFSDH for sales orders (application type 2)

  • /WMD/FP_IFARH for ArchiveLink documents (application type 3)

  • /WMD/FP_IFOCH for purchase order confirmations (application type 5)

  • WMD/FP_DNIFHD for delivery notes (application type 6)

After manual or automated processing, the data is written to the following tables:

  • /WMD/FP_IVHD for invoices

  • /WMD/FP_SDHD for sales orders

  • /WMD/FP_OCHD for purchase order confirmations

  • /WMD/FP_ALDOC for ArchiveLink records

Secondary table

Imported item data is written to the secondary table. Depending on the application type, the following item tables will be available:

  • /WMD/FP_IFIVI for invoices

  • /WMD/FP_IFSDI for sales orders

  • /WMD/FP_IFOCI for order confirmations

  • /WMD/FP_IFARI for ArchiveLink documents

  • /WMD/FP_DNIFPO for delivery notes

After manual or automated processing, the data is written to the following tables:

  • /WMD/FP_IVGL for G/L account register (FI and MM invoices)

  • /WMD/FP_IVDP for down payment requests (FI invoices)

  • /WMD/FP_OCIT for purchase order confirmations

  • /WMD/FP_ARIT for ArchiveLink documents

A special feature for MM invoices is the option of using Interface Windows to control which item category is used. Which tables can be populated depends on the item category.

Header, purchase-order and item data transferred by a feeder system is stored in the table /WMD/FP_IVPO

Table /WMD/FP_IVPD is populated when SAP proposes purchase order data. When a document is parked, regardless of whether it is done manually or automatically, data is adopted to the table /WMD/FP_IVPO.

Table /WMD/FP_IFSDI is used for sales orders. When the order is entered, regardless of whether it is done manually or automatically, the data is transferred to table /WMD/FP_SDIT.

ArcLink table

Table to which ArchiveLink links are written

  • /WMD/FP_IVAL for invoices and orders

  • /WMD/FP_OCAL for purchase order confirmations

  • /WMD/FP_ARDOC for ArchiveLink documents

  • /WMD/FP_DNAL for delivery notes

RFC Multibackend

RFC connection to the end system where this record type is used. This setting is only relevant when using the multi-back-end.

Object type

Object type for linking to the image (for example, MM invoices = BUS2081, FI invoices = BKPF, SD orders = VBAK)

Document type

Document type according to ArchiveLink customizing (transaction OAC2). Any of the document types available for the object type can be selected.

Cont.Rep.ID

Archive selection according to ArchiveLink customizing (transaction OAC0). Any repository available for the object type and document type can be selected.

Doc.class

Selection of all available document types, e.g. PDF or FAX. Items available for selection is available depending on ArchiveLink Customizing (transaction OAC2).

Logging

If an entry is left blank, standard logging will take place. If detailed logging is required, enter the value D.

BDC mode

If an entry is left blank, the document will be processed in the background. If A is selected, processing will take place in bright mode (dialog), if possible. Running this in test mode will allow you to see which values are transferred, and in which order.

In some cases, it is necessary to transfer data from external sources that does not exist, for example, as a field in a standard SAP document. It is possible to add this information from an external source using additional fields (AddInf fields). Examples include contract numbers, license plates, telephone numbers, etc.

Separate tables such as Z_ADDINF_IVH must be provided if writing of external information to AddInf fields is to be enabled. When additional fields are transferred, use header or item data (not in the case of Interface ArchiveLink, though):

DDIC structures (general data)

Description

Primary table

A primary table is used to transfer header data. Header data only appears once in the document, for example, displaying details such as the designated scan workstation or a contract number.

Secondary table

A secondary table is used for transferring additional item data. Item data can occur more than once. Telephone numbers and license plate numbers are examples of this.