Fields in SROKBPP

This code is meant to identify the origin (external source) of the given transaction. It is assumed that this code will be common for all the transactions imported from the same source, independent of its sub-ledger and type. In the import process, it is this value that will determine, if the given not imported yet (i.e., still having a zero Batch no value) interface record should be loaded by the system loader or not. The origin code(s) of the transactions to be loaded in a single loading process are passed to the loader as a parameter value.

Currently, there is no dedicated standard table to define the origin codes. They are considered the same way as the Idenntity codes in the contemporary payments’ interface solution (SROKBP).

This value can be used to separate transactions even having the same accounting period into separate open batches.

In the single loading process the loader will load all the interface transactions with the selected origin code(s) and zero batch no value into batches created according to the Accounting year +Accounting period + Transaction group no key value.

This is the accounting period of the transaction in which it is to be booked, written in the standard CCYYPP DC1 accounting period format.

In the single loading process the loader will load all the interface transactions with the selected origin code(s) and zero batch no value into batches created according to the Accounting year + Accounting period + Transaction group no key value.

This number will be assigned by loader. It must be zero on input. If for a given record Batch no value is not zero, the record is considered as already loaded.

This is the Voucher type code to be applied for the document. It must be a valid voucher type for the given accounting period of the transaction.

This field is used for both: the voucher number assignment and the transaction grouping.

If the Voucher type is associated with a Voucher no series defined with the Handling code “2” or “3”, the value entered here should be the actual voucher number for the document.The entered voucher number will be validated against the voucher number series associated with the voucher type.

If the Voucher type is associated with a Voucher no series defined with the Handling code “1” or “2” and the field is left zero it will be completed with the next number retrieved from the assigned Voucher number series.

All the transactions transferred in one portion that have the same number entered into this field will always share the same voucher number in the end. A zero number in this field will be handled the same way as any other eligible number. This means that if the voucher number field will be left zero all the interface transactions in the loading portion will be given the same common next voucher number, retrieved from the number series, identically as it is today for one of the interface types options. For grouping purposes, you can enter a temporary voucher number and if automatic voucher number handling is defined for the voucher type entered for the payment, (i.e. Handling code “1” is defined for the voucher number series), the temporary voucher number will be replaced by the number retrieved from the voucher number series upon transfer. Note: If a voucher number series is defined with handling code “2”, the entered voucher number will be used rather than replaced by the system.

This field is used to pass the voucher date value for the voucher. This value should be the same for all the document merged into one voucher, but this assumption will not be validated. The voucher date will be retrieved to the voucher header from the first document found belonging to this voucher. The date must be written in the CCYYMMDD date format.

This field is ignored if for the given transaction Voucher type the Check voucher amount flag is set to NO. If it is set to YES, then this field should contain a unique reference number to the SROKBVH file record that should contain control amounts for the given voucher.

Leaving this value equal to zero, overrides the Check voucher amount value to No for the voucher, independent of the Voucher.

It is assumed that the External voucher header reference number and the External reference number entered for the payment are retrieved from the same External reference number series.

This is the reference number that together with the External reference number series value uniquely identifies the assigned record with the Cash book entry header description.

The payment having an assigned Cash book entry header description must be a Cash book payment. It means the Liquid entry panel is set to 8 for the document in the Document type table.

It is assumed that the External liquid entry ref number and the External reference number entered for the payment are retrieved from the same External reference number series.

This code is meant to identify the external number series that is used to uniquely identify interface transaction within each of the number series in an interface file. Practically the following situations can occur:

• The unique transaction number is assigned by an external system and is imported together with the rest of the entry description. In this case the External reference number series code will identify the transaction origin and its number series which is used by the external system.
• Transactions come to the interface file without any unique identification number. In this case the application that writes records to the interface (the Integrator or similar) needs to have series dedicated from which the numbers are retrieved and used to “sign” the added entries. In this case the External reference number series code will identify the number series from which the numbers to numerate the added transactions are retrieved.

This is the reference number that together with the External reference number series value uniquely identifies each transaction in the interface file. It is assumed that the external number series code + the external reference number is a unique key for each record in the interface file at any time instance. This means that as soon as the batch in which a transaction with the given external number is updated and the record of this transaction is removed from the interface file, the external number can be reused within the number series, if needed.

The Document type must be defined as a payment document type in the Document type table.

If for the entered document type a Cash book entry panel is defined, the External liquid entry reference number must not be zero. The SROKBCB record linked with this number must indicate the same Document type as the one entered here.

The number entered into this field will be validated against the Document number series. If the field is left zero the number will be retrieved automatically from the associated Document number series.

This field is used to pass the document date value for the transaction. The date must be written in the CCYYMMDD date format.

This field is used to pass the debtor number value for the transaction. It must be a valid debtor number defined inf the Business partner file. If for the applied template the Init from existing field is set to YES, the field may be left blank to be completed by the system with the Debtor number of the document, which should be settled.

If the debtor with the given number is defined as a sundry business partner in the Business partner file, the additional address information can be passed to the system in the SROKBSN file. The link between the master record in the SROKBPP and the secondary record in the SROKBSN file will be the full payment identification key, meaning:

External reference number series + External reference number

Note: The sundry address information is mandatory only if the document remains open in the batch.

This field is used to pass the cost centre account segment name for the transaction. If left blank, it will be completed by the system in the following sequence:

1. The field will be initialized based on the template indicated the import.

2. The field will be defaulted with the cost centre defined in the Business partner file for the payment’s debtor.

This field is used to pass the value of the transaction amount in transaction currency.The amount decimals must be valid for the given Transaction currency.The amount sign should reflect the DC1 rule for transaction registration.

The sign of the transaction amount loaded in the file should be the sign of the amount booked on the debtor’s control account. It means that a customer payment must be loaded in the file with the negative sign and the customer pay-back amount must be loaded with the positive sign.

Note: If a negative amount is loaded in the file it may be displayed on the detail transaction entry panel with the reversed sign, if for the applied Document type the Reverse sign field value is set to YES in the Document types table.

This field is used to pass the code of the transaction currency. If blank, it may be completed by the system in the following sequence:

1. the field will be initialized based on the template indicated the import

2. the field will be defaulted with the primary currency defined in the Business partner file for the payment’s debtor.

This field is used to pass the transaction amount calculated in system currency. The amount decimals must be valid for the system currency. The amount sign must be the same as that for the Transaction amount, unless the value is zero. In the latter case the system currency amount will be calculated from the Transaction amount, based on the exchange rate valid for the transaction.

This field is used to pass a short text that describes the transaction. If the field will be left blank the text for the transaction will be the text retrieved from the Document types table for the given Document type.

Note: In addition to this short text description the transaction may have attached a longer text passed via a SROKBTX file record. The link between the master record in the SROKBPP and the secondary record in the SROKBTX file is the full payment identification. key, i.e. the External reference number series + External reference number value. The record will be attached to the ultimate transaction record as a Text editor attachment. This attachment is optional.

This field is used to give the exchange rate system time interval from which the transaction exchange should be retrieved. The format required for this value is dependent on the Exchange rate period type code (PATYPC) value:

• a. For 1: CCYYMMDD (day)
• b. For 2: CCYYWW (week)
• c. For 3: CCYYMM (month)
• d. For 4: CCYY (year)
• e. For 5: *zero (fixed)

If zero the interval will be calculated from the Document date for the given Exchange rate period type (PATYPC) and level (PACLVL).

This value determines the format of the current record Exchange rate period value (see above). The following values are allowed:

• 1: day
• 2: week
• 3: month
• 4: year
• 5: fixed rate used

The following codes are valid:

H = High
M = Medium
L = Low