Related topics
The entries in this panel are used to define how to transfer the G/L postings and invoices from different pre-systems to the G/L, A/R and A/P in DC1 Financials. An interface type is set up for each group of transactions that shall be transferred together with the same voucher type, using the same voucher number series. You must, however, create different interface types for invoices and pure G/L postings respectively that originate from the same pre-system, as it is done when transferring transactions from DC1 Distribution via transfer groups.
You use a project control system that generates employee salaries and A/R invoices based on the number of hours that are debited. The salaries and invoices shall be transferred to DC1 Financials. Salaries, which are pure G/L postings, must be transferred separately from the A/R invoices. The salary postings only concern the G/L, while the invoices shall update both the A/R and the G/L, whereby two interface types must be established:
| Field | Salaries | Invoices |
|---|---|---|
| Interface type | SAL | INV |
| Voucher type | GL | AR |
| Voucher break level | 1 | 2 |
| Summary code | Y | N |
| Document type | N/A | ___ |
| Identity | N/A | IN |
| System identity | G/L | A/R |
Three different transfer files are used when retrieving the invoices and the G/L postings:
| Code | Description |
|---|---|
| SROIBT | Transfer file with G/L postings, both pure ones and postings belonging to invoices, which update the G/L. |
| SROKBA | Transfer file with A/R invoices which update the A/R. |
| SROLBA | Transfer file with A/P invoices which update the A/P. |
The system will search in all three of these files, and transfer all invoices and postings that meet the requirements of the selected interface type(s). No cross-reference between the files is done to ensure that, for example, the cost posting for an A/P invoice will automatically be transferred from SROIBT when the invoice is transferred from SROLBA. It is therefore very important that all the information for the transactions in the files is correct and complete.
Note that transactions to be transferred from DC1 Distribution shall not be handled in this routine. Those transactions are transferred via transfer groups in the Transfer group table, which are already defined in DC1 Distribution.
Options
Selection fields
- Interface type
- This column lists the existing interface types.
- Description
- This column lists the descriptions of the existing interface types.
- Voucher type
- Displays the voucher type that the postings for the transactions in the corresponding interface type should receive in the G/L.
- Break level
- Displays the voucher break level code of the corresponding interface type. The break level code decides how the voucher numbers will be set.
- Summary code
- Indicates if the postings of the corresponding interface type should be summarised before transfer.
- Document type
- Displays the document type used to identify the transactions that will be transferred to the A/R or A/P, when the corresponding interface type is selected for transfer.
- Identity
- Displays the identity for the pre-system from which transactions with the corresponding interface type are transferred.
- System id
- Displays the system identity to define from which file the transactions should be retrieved when the corresponding interface type is used for transfer.
Work with interface types (GDMD13404)
On this panel you enter or maintain an interface type.
Function keys
- Interface type
-
The type code is connected to the G/L postings in the SROIBT transfer file. When running the batch program for transfer to the G/L, you make your selection on which interface type(s) to transfer, and only the G/L postings with the same interface type will be transferred.
- Description
-
When postings are summarised, this text will be displayed as the transaction text.
- Voucher type
- Enter the voucher type from the Voucher type table that the postings for the transactions in this interface type shall receive in the G/L. The voucher type controls the voucher numbering from the voucher number series defined for the type. This field must be completed.
- Voucher break level
- Mandatory entry. Enter the voucher break level code that will correspond to this interface type, thereby deciding how the voucher numbers will be set.
Level code Description Voucher date handling 1 Break level 1 means that all postings within the same interface type, year and journal number will receive the same voucher number upon the transfer to DC1 Financials. This level is typically used when pure G/L postings are transferred. For level 1 the system uses the actual system date (today’s date) as voucher date for all postings. Note: The voucher date can be overridden when the actual transfer is done. 2 Break level 2 means that voucher number is set on transaction level, i.e. all the postings for a transaction will receive the same voucher number upon the transfer to DC1 Financials. The voucher number will be the same as the invoice number. This level is used when transferring already numbered transactions, e.g. invoices. Note: Level 2 is only valid for the IN01 transfer group. If this level is used, then the voucher number series and the invoice number series must overlap. The Document type and Identity fields must also be completed if the system shall find the transactions, if break level 2 is used.
It is important that the voucher number series for the voucher type is set up correctly with a valid number range if using break level 2. Automatic numbering is in this case mandatory, which means number handling code 2. The voucher type used must also be valid for the GIT routine in the Routine table. If you want to allocate a voucher type for the transfer of A/R or A/P invoices only, a voucher type which is valid only for the BARI or BAPI routines can be used. Such a voucher type will not be valid when transferring pure G/L postings.
For level 2 the system uses the document date per document as voucher date. Note: The voucher date can be overridden when the actual transfer is done.
- Summary code
- Set this field to YES if the postings of this interface type shall be summarised before transfer. Individual postings with the same accounting period, account combination, VAT handling code, transaction currency and quantity code will be added up and transferred as one posting. If each individual posting shall be transferred separately, you set this field to NO.
If the transactions to transfer are invoices or credit notes, no summation will normally be performed, since each of these transactions receive a reference number in the transfer file over which no summation can be done. Summation will, however, be done if several postings for the same invoice have the same values for the summation parameters. Invoice postings can also be summarised when they have been transferred, if account summation is used, which is defined per main account in the Account file, and voucher break level 1 was used when transferring the invoices.
- Document type
- This field is only used when transferring invoices and credit notes from the A/R transfer file SROKBA or the A/P transfer file SROLBA, and must in that case be completed. It can be used to separate different invoice types that are transferred from the same pre-system, e.g. invoices and credit notes from an invoicing system. You can let invoices respectively credit notes use different voucher types and voucher number series to separate them in the G/L.
If a document type from the Document type table is entered, only transactions with this document type will be transferred to the A/R or A/P, when this interface type is selected for transfer. If all transactions are valid, you complete the field with underscores (___).
- Identity
- This field is only used when transferring invoices and credit notes from the A/R transfer file SROKBA or the A/P transfer file SROLBA, and must in that case be completed. Enter an identity for the pre-system from which transactions with this interface type are transferred. The identity code must exist as invoice information in the transfer file if the invoice shall be selected when this interface type is transferred.
- System identity
- This field is used to define from which file the transactions shall be retrieved. Enter the code for G/L for pure G/L postings, and enter the codes for A/R or A/P for invoices. The codes are defined in the Language table. The system identity G/L is only valid if the Document type and Identity fields are blank, which they must be if only G/L postings shall be transferred.
System identities A/R and A/P are only valid if the Document type and Identity fields are completed, which they must be if invoices shall be transferred. If A/R is entered, the invoices will be retrieved from SROKBA, and if A/P is entered, invoices from SROLBA are retrieved.
Work with interface types, Copy (GDMD13405)
- Interface type
- Displays the interface type you selected to copy.
- New interface type
- Enter the new interface type that you are creating.