Fields in SROKBPS

This code is meant to identify the origin (external source) of the given transaction. It is assumed that this code is common for all the transactions imported from the same source, independent of its sub-ledger and type (i.e. independent of if they are A/R Payments, A/R Settlements, or in the future: G/L transaction and so on). 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.

There is no dedicated standard table to define the origin codes and they are considered the same way as the Identity codes used in the contemporary payments’ interface solution (SROKBP).

Payment related settlements should have the same origin code value as the referred payment loaded into SROKBPP file.

The field is prepared to group the standing alone settlements, the settlements not related to a payment which is being transferred, but related to a document already booked in the system.

This value is ignored for the settlements associated with a payment which is being imported as these settlements will be always preloaded to the same batch as the referenced payment.

This field is prepared to goup the standing alone settlements, the settlements that are not related to a transferred payment, but related to a document already booked in the system. This is the accounting period in which all the difference and the control account adjustment documents created in the settlement should be booked. It must have the format of CCYYPP. The accounting period value entered here is ignored for the settlements associated with a payment which is being transferred as these settlements are always preloaded to the same batch as the referenced payment.

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 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.

The same External reference number series and the External reference number, as for the associated payment record loaded into the SROKBPP file, should be used.

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.

The same External reference number series and the External reference number, as for the associated payment record loaded into the SROKBPP file, should be used.

This is a text that, if entered here, will be written into the settlement header SROKBSH. SHDESC field. Otherwise the main settlement document text string will be used.

This code identifies the external number series from which Payment external reference number for the associated payment is retrieved.

If the corresponding payment exist in SROKBPP the STPERS and STERNS field values should be the same.

This is the reference number that together with the Payment external reference number series code uniquely identifies a payment loaded to the SROKBPP file that will be the main document of the current settlement.

If the corresponding payment exist in SROKBPP then the STPERN and STERFS field values should be the same.

This is the document type of the main settlement document to settle. Note: this field is prepared to be used by standalone settlements to determine the main document of the settlement. If entered, the value can be directly copied to the corresponding SROKBSH and the SROKBSD record fields by the Settlement description creation procedure, defined for the settlement option used. It is not used by Settlement description Note: the field is not used by Settlement description procedures provided currently by the standard system.

This is prepared to hold the document number of the main settlement document to settle.

Note: this field may be used by standalone settlements to determine the main document of the settlement. If entered, the value can be directly copied to the corresponding SROKBSH and the SROKBSD record fields by the Settlement description creation procedure, defined for the settlement option used.

Note: The field is not used by Settlement description procedures provided currently by the standard system.

This is the bank reference number of the main settlement document to settle. Note: this field may be used by standalone settlements to determine the main document of the settlement. If entered, the value can be directly copied to the corresponding SROKBSH and the SROKBSD record fields by the Settlement description creation procedure, defined for the settlement option used.

This is the system reference number of the main settlement document to be found.

Note: This value can be used for settlements internally created in the system, to directly point the document that needs to be settled in the current settlement.

If the settlement is not of the dependent on existing type this value should be zero.

This is the code defined for the settlement option in the Settlement option table.

If this field is blank or its value is not a valid settlement option code the settlement loading will be interrupted with an error.

This is the document type of the document to settle.

This is the document number of the document to settle.

This is the bank reference number of the document to settle.

This is the sales order number of the invoice to settle. The field is foreseen for the customised settlement options.

Note: The field is foreseen for the customised settlement options. The invoice to settle is supposed to be created in the DIS system. Its REFX can be retrieved from the SR2ISH file based on the passed ORNO value.

This is the customer-defined purchase order number of the invoice to settle. The field is foreseen for the customised settlement options.

Note: The invoice to settle is supposed to be created in the DIS system. Its REFX can be retrieved in the following two steps:

” From the SR13SOH file the resolution COPE->ORNO is available, providing a certain order status is assumed (the status is the first key of the logical file used).

” From the SR2ISH file the resolution ORNO->REFX is available.

This is the customer order number (EDIFACT) of the invoice to settle. The field is foreseen for the customised settlement options.

Note: The invoice to settle is supposed to be created in the DISsystem. Its REFX can be retrieved in the following two steps:

” From the SR8SOH file the resolution CORN->ORNO is available, assuming the customer number is resolvable from the payment debtor information (the customer number is the first key of the logical file used).

” From the SR2ISH file the resolution ORNO->REFX is available.

This is the portfolio bank remittance number of the invoices to settle. The field is foreseen for the customised settlement options.

Note: This value would be even more appropriate for selecting invoices picked up for the portfolio proposal. To make this working a new logical file over the SROPFH file has to be added, as the PHRMNO fieldis not a leading key for any of its logical files. A general scheme for all the related REFX resolution would be the following:

” From the SROPFH the RMNO->REFL would be resolved.

” From the SR1DTAB the REFL->list of REFX would be resolved.

This is the system reference number of the document to directly settle. It is foreseen for the customized settlement options. This value can be used for settlements internally created in the system, to directly point the document that needs to be settled in the current settlement.