Load subledgers (CAT/SAT) - INP/62583
This load is handling both creation and updating of CAT/SAT transactions. Possible fields to be loaded into RamBase are listed in the Field-column in the following table. The other columns in this table provide additional information about each field.
Field | Required | Length | Example | Description |
|---|---|---|---|---|
ACCOUNT | Y** | 10000 | Customer/Supplier account number. The number should match the RamBase customer/supplier number. **Either ACCOUNT or ACCOUNTEXTID must be present in the file. | |
ACCOUNTEXTID | Y** | The customer's/supplier's unique ID from the legacy (old) system. To identify the customer/supplier the transaction is to be connected to. **Either ACCOUNT or ACCOUNTEXTID must be present in the file. | ||
AMOUNT | Y | 12 | 77490.00 | Amount = Qty * Price in transaction currency. |
CAMOUNT | 12 | 77490.00 | Net amount converted to home (local) currency. | |
CUR | Y | 3 | NOK | Document currency. An abbreviation of three letters which corresponds to the CUR register in RamBase. |
DATE | Y * | 12 | YYYY.MM.DD | Transaction date (the date the transaction was issued). *To ensure best possible operation of age distribution and payment statistics, DATE, DUEDATE and PAYDATE should be loaded as accurate as possible. Format: YYYY.MM.DD |
DOC | CIN/101456 | When loading open posts for conversions, please leave this field empty RamBase transaction Id. (Sales Invoice number, credit number, payment number etc.). The field is a reference to a RamBase transaction document. If the field is loaded as empty, a "dummy" document reference will be created by the load. | ||
DUEDATE | Y* | 10 | 1996.10.13 | DueDate. Last date which invoice has to be paid. Format: YYYY.MM.DD *To ensure best possible operation of age distribution and payment statistics, DATE, DUEDATE and PAYDATE should be loaded as accurate as possible. |
EXTID | Unique ID for the transaction from the legacy (old) system. It is recommended to use the same value as in the YOURNO field. | |||
ICTDB | JHA-NO | Inter Company Trading DataBase. Used to identify customers/suppliers which are companies within the same corporation. The value is a RamBase database reference and should not be used unless the database reference actually exists in the RamBase system. | ||
INTFLAG | 9 | Interest Flag: "9" - If set to 9, it means that interests should not be created for this post. | ||
INVCC | 2 | SE | Invoice Country Code. On customer postings this is the code of the country the invoice are issued TO. On supplier postings it is the country code the invoice are issued FROM. | |
KID | 10124001029384 | KID. Norwegian transaction code for recognition of incoming payments. | ||
NAME | HATTELAND DATA A/S | Company name (Account name). Drawn from the customer/supplier register in RamBase from the value in the account field, and is therefore usually not loaded. | ||
NOUPDATE | Must be set to Y or YES to prevent update on an existing document. | |||
PAYDATE | Y* | 14 | 1997.02.14 | Transactiondate of payments. Format: YYYY.MM.DD If status=9, and this field is empty, PAYDATE will be set to (if present): 1. DUEDATE 2. DATE 3. Date the file is loaded *To ensure best possible operation of age distribution and payment statistics, DATE, DUEDATE and PAYDATE should be loaded as accurate as possible. |
PAYDOC | PAY/100119-1 | Transaction id from payment received for transaction. If status=9, and this field is empty, PAYDOC is set to PAY/xxx. PAYDOC is a reference to a rambase document and is not loaded if the converted system is a non-rambase installation | ||
PAYPERIOD | 199702 | Period of payments received for transaction. If status=9, and this field is empty, PAYPERIOD will be calculated from (if present): 1. DUEDATE 2. DATE 3. Date the file is loaded To show a correct age distribution of historical closed posts, PAYDATE should be loaded as the actual date of payment. | ||
PAYREGDATE | 2005.10.14 | Registration date of payment received for transaction. Format: YYYY.MM.DD If status=9, and this field is empty, PAYREGDATE will be set to (if present): 1. DUEDATE 2. DATE 3. Date the file is loaded | ||
PERIOD | Y | YYYYMM | Account/fiscal period. | |
RATE | Y | 42041 | 1.0000 | Exchange rate. If document is issued in local currency the exchange rate is 1. |
REGDATE | Y | 10 | YYYY.MM.DD | The registration date of the document. Format: YYYY.MM.DD |
RMRFLAG | 1 | Reminder Flag: "1" - If this is set to 1, it means that reminders should not be created for this post. | ||
SHIPCC | 2 | NO | Shipping Country Code. On customer postings this is the code of the country the goods are shipped TO. On supplier postings it is the country code the goods are shipped FROM. | |
ST | Y | 1 | 9 | RamBase status code. The main purpose of the field is to differ between open (st:4) and closed (st:9) ledger postings. In addition, SAT documents can have status code 6 (marked for manual handling). Both CAT and SAT can have status code 8 (paid, but not confirmed). It is not advisable to have unconfirmed payments at the time of conversion, so st:8 is not recommended used in load. |
TEXT | 50 | Bank-fee | Description of the transaction in free text. It's recommended to use a similar value as in the yourno field (for instance an invoice number), with additional text to make a reference to the converted system. | |
TRANSTYPE | Y | C | "C" = Customer transaction "S" = Supplier Transaction Both CAT (receivables) and SAT (payables) can be created from the same file. Based on the value in the Type field, the conversion programme will create either a CAT or a SAT document. | |
VATAMT | 1415.04 | VAT Amount. | ||
YOURNO | Y ** | 20 | Customer's/supplier's order number. When it comes to conversion, the value in the YOURNO field should be set to a value that refers to a searchable ID in the legacy (old) system. YOURNO in combination with ACCOUNT must be unique. If YOURNO is not unique, the first CAT/SAT transaction with a specific YOURNO will be updated when an additional CAT/SAT transaction is loaded with the same YOURNO. ** YOURNO is mandatory if KID is not included. |