Notes on customizing record types by xSuite product
Customizing record types for Invoice
Depending on the application type, the input dialog on the left side of the screen will change. Following is a list of record types commonly set up for xSuite Invoice.
Record type | Description | Comment |
|---|---|---|
XX | xSuite scan documents | This record type is often used in conjunction with xSuite Capture. It contains all scanned documents for which the data extraction process has not yet been completed. After data extraction has been completed, the data record is updated. The record type changes to FI or MM. |
FI | FI invoices | This record type is used for FI invoices. |
MM | MM invoices | This record type is used for MM invoices. |
DP | Down payment requests | Set up this record type if the customer uses down payment requests (target transaction F-47). |
AN | Complex postings | In some cases, it is necessary to use a record type for "complex postings." They might be for transactions such as asset invoices, i.e., ones which often cannot be processed using transaction FV60, but require FBV1 instead. |
TM | Transportation Management | This record type is used for TM documents (e.g., freight orders). |
The record types can be adapted to the needs of the customer and/or the project. However, we recommend that you use the record types described above.
It may be useful to set up additional record types. For example, it makes sense to use separate record types for EDI invoices and intercompany invoices.
Customizing record types for ArchiveLink
Following is a list of record types commonly set up for ArchiveLink.
Record type | Description | Comment |
|---|---|---|
XX | xSuite scan documents | This record type is often used in conjunction with xSuite Capture. It contains all scanned documents for which the data extraction process has not yet been completed. After data extraction has been completed, the data record is updated. The record type is changed. |
BC | Barcode scenario | This record type is used for the ArchiveLink barcode scenario. A barcode can be used to assign an attachment document to an SAP document. |
AS | Assign and store | This record type is used for the "Assign and store" scenario. |
WF | Workflow scenario | This record type is used for the workflow scenario. In this scenario, a workflow is started for the attached document. The object type is permanently set to the value |
Customizing record types for Orders
Following is a list of record types commonly set up for xSuite Orders.
Record type | Description | Comment |
|---|---|---|
XX | xSuite scan documents | This record type is often used in conjunction with xSuite Capture. It contains all scanned documents for which the data extraction process has not yet been completed. After data extraction has been completed, the data record is updated. The record type changes to SD. |
SD | Sales orders | This record type is used for SD orders such as "Business object VBAK". |
There is a large number of possible order types that are controlled by different SAP business objects. During project implementation, you may have to create several record types for sales orders.
Customizing record types for Order Confirmation
Following is a list of record types commonly set up for xSuite Order Confirmation.
Record type | Description | Comment |
|---|---|---|
XX | xSuite scan documents | This record type is often used in conjunction with xSuite Capture. It contains all scanned documents for which the data extraction process has not yet been completed. After data extraction has been completed, the data record is updated. The record type changes to AB. |
AB | Order confirmation | This record type is used for incoming order confirmations. |
For record types in the Order Confirmation area, it is important that you specify the correct document type. The record type corresponds to the confirmation category that has been stored in SAP customizing.
SAP Customizing is located in the SAP Customizing Implementation Guide under Materials Management → Purchasing → Confirmations → Configure Confirmation Control. The sequence in which confirmations are written to the respective order item is also defined here. As an example, it is not possible to post a shipping notification if an order confirmation has not been posted beforehand. If a user wants to do so anyway, she must use a different confirmation control key for this item, namely one that explicitly allows posting in the absence of an order confirmation.
Customizing record types for Interface SAP
No additional record types are required for Interface SAP, since it uses existing Invoice record types.
Customizing record types for Procurement
Since xSuite Procurement is an internal procurement process, the process is not started by incoming documents, but by internally created Feeders or requests, SAP purchase requisitions, or SAP purchase orders.
In this case, incoming documents will generally tend to be documents which are scanned in and accompany a procurement process that has already started. For this, Interface ArchiveLink can be used to feed documents to an existing transaction.
How to set up ArchiveLink scenarios (early and late archiving) is not covered in this publication. For examples of installation scenarios, please refer to the documentation for xSuite Interface.
Customizing record types for Delivery Notes
Following is a list of record types commonly set up for xSuite Delivery Notes.
Record type | Description | Comment |
|---|---|---|
XX | xSuite scan documents | This record type is often used in conjunction with xSuite Capture. It contains all scanned documents for which the data extraction process has not yet been completed. After data extraction has been completed, the data record is updated. The record type changes to DN. |
DN | Delivery notes | This record type is used for incoming delivery notes. |