Setting name | Description | Submodule/ archive |
Default Character set for prints | Used to tell the default characther set to use for the current database. NODK means norwegian and danish charathers while SEFI means swedish / finish. Default if not set is other. PS: This setting is not in use (2018.07.02) | Defaults |
Default Customer as WebUser | Default customer to be used on Sales Order Request (CPO) when a web user add products to the shopchart, without beeing logget in. Format to be used: CUS/NNNNNN (N for numbers) | Defaults |
Default Service Customer as WebUser | Default Service customer to be used on Sales documents when a web user add products to the shopchart, without beeing logget in. Format to be used: CUS/NNNNNN (N for numbers) | Defaults |
DefaultWebPageDomain | Domain of the default webpage. Probably obsolete | Defaults |
Fax is used for company | If this setting is "ON" - Fax can be used for this company | Defaults |
Footer1 on prints | The value is this setting will show as a text at the bottom of most standard prints | Defaults |
Footer2 on prints | The value is this setting will show as a text at the bottom of most standard prints | Defaults |
Footer3 on prints | The value is this setting will show as a text at the bottom of most standard prints | Defaults |
Footer4 on prints | The value is this setting will show as a text at the bottom of most standard prints | Defaults |
Footer5 on prints | The value is this setting will show as a text at the bottom of most standard prints | Defaults |
From Email address to be used as default on Mailing (MAI) | The value in this setting must be the 'from Email address' that should be used as default when creating Mailing (MAI). Format to be used: LLLLLL@LLLL.LL (L for letters) | Defaults |
Hide Personell information on prints | If this setting is "ON" - Personell information - Personell ID (PID), name and mailadr from Rambase documents) will be hidden on prints. If the setting is "OFF" - Personell information will show on prints | Defaults |
Minutes inactivity before logged out when logged in using onetime password | The value in this setting must be number of minutes you can stay logged in in Rambase without any activity, before you get logged out. This is when you are logged in from insecure location using onetime password | Defaults |
Minutes inactivity before logget out when loggen in from secure location | The value in this setting must be a number of minutes you can stay logged in in Rambase without any activity, before you get logget out. This is when you are logged in from secure location | Defaults |
Output theme | Value in this setting is a reference for selected output theme for this company. Changes in Company logs (COS) application will also update the setting with a new reference as value, e.g. 102233. Setting can be updated by JHC or partner. | Defaults |
Output logo | This is the output logo for this company which will show on prints and emails. | Defaults |
Send email automatically from documents by forward | If this setting is "ON" - Emails will be sent automatically when documents are forwarded. If the setting is "OFF" - Emails will be sent, and copies can be sent | Defaults |
View All PDF Links | If setting is ON - users are be able to see/open all pdf links in the Correspondance popup. JHC employes are able to see/open all pdf links even if the setting is not activated. | Defaults |
Web Shop Database | Value in this setting should be the database name for the company there should be a link to. Format to be used is : LLL-LL (L for letters) | Defaults |
Deactivate Approval message - Agreement Expiration Date | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM) | DocumentMessages |
Deactivate Approval message - Approval of Amount | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Item (SPO-ITM), Purchase Order Response Item (SOA-ITM) and Supplier Invoice Item (SIN-ITM) | DocumentMessages |
Deactivate Approval message - Buffer Quantity | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM). There is a check against CSV/CusQuoteBufferQuantityApprovalLimitPct (Item buffer quantity / Item remaining quantity * 100) | DocumentMessages |
Deactivate Approval message - Cancellation limit | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Approval message - Cancellation limit for period exceeded for Person (PID) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Approval message - Check Gross Margin | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM), Sales Order Item (COA-ITM), Shipping Advice Item (CSA-ITM) and Sales Invoice Item (CIN-ITM) | DocumentMessages |
Deactivate Approval message - Credit Insurance Exceeded | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA) | DocumentMessages |
Deactivate Approval message - Credit Limit Exceeded | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA) | DocumentMessages |
Deactivate Approval message - Expiration date 'later than' on Sales Quote (CQU) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote (CQU) | DocumentMessages |
Deactivate Approval message - KIT version | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated on KITART, when you make new version on a Product (ART) with TYPE=K | DocumentMessages |
Deactivate Approval message - Minimum Resale Price | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM), Sales Order Item (COA-ITM), Shipping Advice Item (CSA-ITM) and Sales Order Request Item (CPO-ITM) | DocumentMessages |
Deactivate Approval message - Payments (PAY) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Payment (PAY) | DocumentMessages |
Deactivate Approval message - Picking blocked | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA) | DocumentMessages |
Deactivate Approval message - Punch List | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Approval message - Required Documentation | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA), Shipping Advice Item (CSA-ITM) and Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Approval message - Total Cancellation limit for Person (PID) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Info message - Assignment changed to another Product | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate Info message - Cancellation of Purchase Order Response (SOA) from Supplier via file upload | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Cancellation of Sales Forecast Item (CFC-ITM)) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Forecast Item (CFC-ITM) | DocumentMessages |
Deactivate Info message - Checking requested date on Purchase Order Change Request (SRC) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Confirmed Product has changed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Customer merged | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for most of the documents (CCN,CIN,COA,CPO,CSA,CQU,CRQ,SCN,SIN,SOA,SPO,SRC,SRT,SRQ,SSA,SQU) | DocumentMessages |
Deactivate Info message - Customer requested change | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order (COA), Sales Order Item (COA-ITM), Sales Order Change Request (CRC) and Sales Order Change Request (CRC-ITM) | DocumentMessages |
Deactivate Info message - Documentation is not required | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA), Production Work Order (PWO) and Goods Reception (SSA) | DocumentMessages |
Deactivate Info message - Documentation reminder | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception (SSA) and Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Info message - Free Text | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for all documents except Sales Forecast (CFC) | DocumentMessages |
Deactivate Info message - Goods In confirmed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Info message - Gross Price mismatch on Purchase Order Response (SOA) from Purchase Order (SPO) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Item linked to Goods Reception Item (SSA-ITM) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Info message - Location (LOC) changed when Purchase Order Response (SOA) received for another location | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) and Sales Quote Item (CQU-ITM) | DocumentMessages |
Deactivate Info message - Message from Customer/Supplier | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for all documents | DocumentMessages |
Deactivate Info message - New Version | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Item (SPO-ITM) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - No version upgrade from Product performed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Pick Completed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM), Shipping Advice Item (CSA-ITM) and Supplier Return Item (SRT-ITM) | DocumentMessages |
Deactivate Info message - Production cancelled | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Production completed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Item (SPO-ITM) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Production on Hold | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Production Split | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Production started | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Item (SPO-ITM) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Production Undo Release | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Production Work Order (PWO) has been delinked by | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Production Work Order (PWO) on hold off | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Purchase Order (SPO) not found | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Purchase Order Response (SOA) has been Gross Price protected | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) | DocumentMessages |
Deactivate Info message - Purchase Quote (SQU) received from Supplier | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote (CQU) | DocumentMessages |
Deactivate Info message - Purchase Quote Request (SRQ) is closed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Quote Request Item (SRQ-ITM) | DocumentMessages |
Deactivate Info message - Quantity mismatch with Purchase Order (SPO) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Received Confirmation from Production - Shipday: V or W | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate Info message - Received Confirmation from Production - Shipday:D | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate Info message - Received Confirmation from Supplier | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate Info message - Released for Production | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Scrapping Completed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order (PWO) | DocumentMessages |
Deactivate Info message - Scrapping process started | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Scrapping Undone | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Serialnumber could not be registrated | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice Item (CSA-ITM) and Supplier Return Item (SRT-ITM) | DocumentMessages |
Deactivate Info message - Set Operation (OPR) to Ready | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Stock assignment cancelled | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate Info message - Supplier Part does not match Part at source item | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Order Response (SOA) and Purchase Order Response Item (SOA-ITM) | DocumentMessages |
Deactivate Info message - Undo Operation | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Undo Picking | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Info message - Valid Purchase Quote (SQU) exist | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate message - Circuit control | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception (SSA) and Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate message - Item can't be transported to Shipping Advice (CSA) until payment is registrated | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactivate message - Remember LOT/HEAT number | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception (SSA) and Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate message - Visual control according to procedure | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception (SSA) and Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Stop message - A valid shippingservice is required | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote (CQU), Sales Order (COA), Shipping Advice (CSA), Supplier Return (SRT), Goods Transfer (STW), Purchase Order (SPO), Purchase Order Response (SOA) and Purchase Quote Request (SRQ) | DocumentMessages |
Deactivate Stop message - Missing information in fields (Weight, Contry of Origin Code and Customs Tariff Code in Product (ART) | If the setting is "ON" - Document message is not activated. If the setting is "OFF - The document message is activated for Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Stop message - Number of Serial numbers does not match Quantity in item | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception Item (SSA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Stop message - Product Blocking | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Invoice Item (CIN-ITM), Sales Order Item (COA-ITM), Purchase Order Item (SPO-ITM), Goods Reception Item (SSA-ITM) and Sales Quote Item (CQU-ITM) | DocumentMessages |
Deactivate Stop message - Purchase Quote (SQU) is expired, check Purchase quote item field (BREF) for new Purchase Quote | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM), Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Stop message - Purchase Quote (SQU) is not valid for this customer | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Quote Item (CQU-ITM), Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Stop message - Purchase Quote (SQU) is not valid for this document | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Invoice Item (CIN-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Stop message - Purchase Quote (SQU) needs to be activated | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Stop message - Sales Quote Request (CRQ) has been changed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Purchase Quote Request Item (SRQ-ITM) | DocumentMessages |
Deactivate Stop message - This Type (class) is not accepted in actual document type | If the setting is "ON" - Document message is not activated. If the setting is "OFF - The document message is activated for Sales Order Item (COA-ITM), Sales Quote Item (CQU-ITM) and Sales Quote Request (CRQ-ITM) | DocumentMessages |
Deactivate Stop message - Waiting for Tollpass | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Goods Reception (SSA) | DocumentMessages |
Deactivate Warning message - ASWM: Missing Quantity on | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) and Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Warning message - Customer Reference Number (Yourno) already exist | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Supplier Invoice (SIN) and Supplier Credit Note (SCN) | DocumentMessages |
Deactivate Warning message - Free text | f this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for all documents except Sales Forecast (CFC) | DocumentMessages |
Deactivate Warning message - Invalid KID | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Supplier Invoice (SIN) | DocumentMessages |
Deactivate Warning message - Location (LOC) mismatch | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Supplier Invoice (SIN) | DocumentMessages |
Deactivate Warning message - Member - on Sales Order (COA) or Sales Order Request (CPO) | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order (COA) and Sales Order Request (CPO) | DocumentMessages |
Deactivate Warning message - Message from Product | f this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated | DocumentMessages |
Deactivate Warning message - Message to Shipping Operator | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order (COA) and Shipping Advice (CSA) | DocumentMessages |
Deactivate Warning message - Missing country of origin code on material | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice Item (CSA-ITM) | DocumentMessages |
Deactivate Warning message - Missing quantity on | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice Item (CSA-ITM), Supplier Return Item (SRT-ITM) and Goods Transfer Item (STW-ITM) | DocumentMessages |
Deactivate Warning message - Next Service Date | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Recurring Invoice Plan Item (COP-ITM) | DocumentMessages |
Deactivate Warning message - Picking Blocked | If the setting is "ON" - Document message is not activated. If the setting is "OFF - The document message is activated for Goods Reception Item (SSA-ITM) | DocumentMessages |
Deactivate Warning message - Price Difference between Supplier Invoice (SIN) and Goods Reception (SSA) | If the setting is "ON" - Document message is not activated. If the setting is "OFF - The document message is activated for Supplier Invoice (SIN) | DocumentMessages |
Deactivate Warning message - Sales Order (COA) cancelled | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Warning message - Sales Order (COA) deleted | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Warning message - Service Order (CSO) cancelled | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM) | DocumentMessages |
Deactivate Warning message - Service overdue | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Recurring Invoice Plan Item (COP-ITM) | DocumentMessages |
Deactivate Warning message - Source quantity is less that quantity | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Sales Order Item (COA-ITM) | DocumentMessages |
Deactive Approval message - Overdue Exceeded | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Shipping Advice (CSA) | DocumentMessages |
Deactive Info message - Picking list printed | If this setting is "ON" - The document message is not activated. If the setting is "OFF" - The document message is activated for Production Work Order Item (PWO-ITM), Shipping Advice Item (CSA-ITM) and Supplier Return Item (SRT-ITM) | DocumentMessages |
DocumentMessageDeactivateInfoExpectedAndNetPriceMismatch | Shows if the document message is deactivated. ON = Document message is not active OFF = Document message is active <empty> = Document message is active | DocumentMessages |
DocumentMessageDeactivateInfoTargetAndNetPriceMismatch | Shows if the document message is deactivated. ON = Document message is not active OFF = Document message is active <empty> = Document message is active | DocumentMessages |
Report 1000 Separator | This is the default 1000-separator for report fields of type Number or Quantity. Possible values: Space, Comma or Point. If this setting is not used, the default will be no 1000 separator. This value will be overridden if the column is formatted in the Report Definition. NOTE: This functionallity will not work as described until further development is done | Reports |
Report Decimal Separator | This is the default decimal separator for report fields of type Number or Quantity. Possible values: Comma or Point. If this setting is not used, the default will be point. This value will be overridden if the column is formatted in the Report Definition. NOTE: This functionallity will not work as described until further development is done | Reports |
Access based subscription fee for RamBase users | If this setting is 'ON' - Used to toggle if the system is running access based subscription fee for RamBase users, where access points on duties are accumulated for each user giving a subscription price category (UPC) for each user. The price category for a user decides the RamBase subscription fee for that user. This setting should only be activated in JHC-NO, and only by JHC | Roles |
Calculate user subscription price category per company | If this setting is 'ON' - Users will get one subscription price category (UPC) for each database they have roles in. Access points will be accumulated by unique duties the user has on roles within a database. If a user has the same duty in two roles, it will be considered as one duty in the accumulation. If setting is 'OFF' - the access points are calculated across all companies in the system by unique duties the user has acrosss all databases in the systems. This setting should typically be on if the owner of this RamBase system has seperate contracts for each company in the system. This setting should only be activated in JHC-NO, and only by JHC | Roles |
Notify PIDs when system changes subscription price category for users | Comma list of users (PIDs) that should be notified if system changes subscription price category (UPC) for a user in company. E.g. if a system defined role is updated with a new duty by JHC. Should be set in the databases where notifications should be sent. If company has company group agreement for licensing, all PIDs set up in one or more of the databases will receive notifications of changes in all databases, as user price categories then are valid cross all databases | Roles |
Set Comment Mandatory In Role User Assignment | If this setting is "ON" - It is mandatory to add a information in the Comment field when adding a user to a Role | Roles |
Threshold value for price category Cross functional user | Setting must be set in JHC-NO. The minimum number of access points that will make a user be a in the price category "Cross functional user". These are users with more demanding roles and wide and varied use of the system. Full access to the entire system (limited, of course, by the company's own roles). | Roles |
Threshold value for price category Functional user | Setting must be set in JHC-NO. The minimum number of access points that will make a user be a in the price category "Functional user" (or higher). These are "operator level" users as sales assistants, purchasing assistants, warehouse staff, regular production operators. | Roles |
Threshold value for price category Selfservice user | Setting must be set in JHC-NO. The minimum number of access points that will make a user be a in the price category "Selfservice user" (or higher). These are the most basic users. Typically they only have a PID and a login to RamBase. They report their hours and can report quality deviations. | Roles |
Threshold value for price category Singletask user | Setting must be set in JHC-NO. The minimum number of access points that will make a user be a in the price category "Singletask user" (or higher). These are users with very simple tasks related to relocation and / or very simple, repetitive operations in production. | Roles |
Turn Off Sharp Drivers For This System | If this setting is "ON" in JHC-NO database in the system - All sharp drivers for this system is deactivated. This means that no print, email etc will be sent out from Rambase. In Production environments the setting should be "OFF". IMPORTANT!! Don't turn ON/OFF this setting if you are not 100% sure what it will affect | Settings |
Use Card Reader to create Work Hour Log (WHL) lines | If this setting is "ON" - the company is using a Card Reader (from an external system) to create Work Hour Log (WHL) lines. It this settin is "OFF" - the company use "TimeClocking software" to create Work Hour Log lines or create the lines manually. | Interfaces |
External Planning System | Decide if emails sent from documents should attach the attached files or not. If value is "ON" - Only selected attachment will be sent. If value is "OFF" - Send automatically all attached files. If settings has no value - Attachments will not be sent. | Improvements |
Attach files when sending documents by email | Decide if emails sent from documents should attach the attached files or not. If value is "ON" - Only selected attachment will be sent. If value is "OFF" - Send automatically all attached files. If settings has no value - Attachments will not be sent. | Improvements |
Department on Quality Assurance Event (QAR) | If this setting is "ON" - Default department on Quality Assurance Event (QAR) will be the same as Department from the Personell (PER) that creates the Quality Assurance Event | Improvements |
DueDate on Quality Assurance Event (QAR) | Value in this setting is a number of days that will be added to Quality Assurance Event (QAR) date, to find the DueDate (Deadline) on Quality Assurance Event. The DueDate (Deadline) is the date the Quality Assurance Event should be completed. Default number of days could be 30 | Improvements |
Next Casehandler on Quality Assurance Event (QAR) | Value in this setting is a Group (GRP) that contains Personell (PER) that is available to select as 'Next Casehandler' on Quality Assurance Event. Format to be used: GRP/NNNNNN (N for numbers) | Improvements |
Return Quality Assurance Event (QAR) | If this setting is "ON" - It is possible to add a Message to the previous responsible when select 'Return' on the Quality Assurance Event (QAR) | Improvements |
QualityShowHealthEnvironmentSafetyFields | Setting to show the HES (Health, Environment and Safety) fields. Value for JHC-NO= 11,HES ex value for other companies =21 | Processes |
Print Detail Info Product Declaration | If this setting in 'ON' - Detailed information on the Product Declaration print is turned on. PARTs without KITItem will show | Documentation |
Product File Import Default ManufacturerId | Value in this setting is a ManufacturerId. The ManufacturerId will be used if a file with Productstructure is loaded into Rambase, and the file doesn't contain ManufacturerId, - value from this setting will be used as default on the products. Format to be used: MFR/NNNN (N for numbers) | Manufactures |
Procurement By Intercompany on Forward | If this setting is 'ON - The company is allowed to forward purchase object into sales objects in another database and vice versa. To use this also functionality, - local DOV's (domain values)are required to specify method of sending | Interfaces |
Purchase Order Send By Intercompany on Forward | If setting is 'ON' - The company can forward a Purchase Order (SPO) to a Sales Order (COA) in another database. It also requires that a local DOV (domain values) is setup to specify method of sending | Interfaces |
Sales Order Send By Intercompany on Forward | If setting is 'ON' - The company can forward a Sales Order (COA) to a Purchase Order Response ( SOA) in another database. It also requires that a local DOV (domain values) is setup to specify method of sending | Interfaces |
Supplier Purchase Order (SPO) can be sent via EDI - Electronic Data Ingerchange | If this setting is "ON" - Supplier Purchase Order (SPO) can be sent via EDI - Electronic Data Interchange | Interfaces |
Use of EDI - Electronic Data Interchange from Procurement Module | If this setting is "ON" - The Company can use EDI - Electronic Data Interchange from Procurement Module. More informations on kind of messages that could be triggered, is explained under the child settings | Interfaces |
The Users (USERS) application displays all the users with access to the system. It is restricted to login and access to the system. It shows who you are as a user in the system, not as an employee.
Use the Users (USERS) application to:
Create new users.
Link existing PER/employee to a new user.
Grant access to a new system for existing users.
Allow admin users to grant access to test systems to anyone, including themselves.
Edit and configure a user.
Inspect statistics and logs.
To open the Users (USERS) application, find Admin in the RamBase menu and then User administration. Click Users to enter the USERS application.
Highlight a user in the Users area to view details about the selected user.
It is possible to add predefined filters for more efficient navigation. Click on the Predefined filters icon next to the Search field to see the predefined filters. The selected filters will be available below the Search field.
The Search field is a free text filter. Write name, user name, userid or email and press ENTER to use the Search field.
The User Details area displays details about the user. It is only possible to edit details about the user in the users home system.
If the user should be allowed to login from a remote location, click the check-box Allow login from remote location. Select if the user should receive password on SMS or EMAIL in the One time password field.
If you allow a user to login from a remote location, the user can login to Rambase from all networks, including unsecured networks. Use this option only if the users must work from remote locations than locations having access to a secure network. The Company must establish the policy for remote login. When logging in from a remote location, the user must use 2-factor (2FA) authentication. There is a Company setting in the CSV called Minutes inactivity before logged out when logged in using onetime password. This setting specifies the maximum number of minutes a logged in user can be idle for, before being automatically logged out, when they have logged in using a one-time password (OTP). You can set the inactivity time from between 10 to 60 minutes by dragging the slider or selecting the arrows icons.
The Search field in the folders is a free text filter.
Statistics - The Statistics folder provides login information as well as the possibility to unblock a user.
Sessions - The Sessions folder displays all sessions in this system from various IP addresses. It is also possible to make an IP address secure, click the Verify this IP address to disable two-factor authentication icon in the Actions column. Then the user does not need to use a one time password next time the user logs in from the selected IP address. The IP address will be put in the One time password administration (OTPADMIN) application as an exception.
Logs - Log history is stored in the Logs folder.
Systems - Inspect all systems that the user is associated with in the Systems folder. It is also possible to give the user access to new systems in the Systems folder and delete access to systems.
Roles - The Roles folder displays all roles that the user has been assigned to. It is also possible to give the user new roles in the Roles folder. A role assigned from the Users application is activated directly.
Temporary leave - Use this option if the user will be on temporary leave. This will set the selected user as inactive (status 7) and the users accesses will be inactive until the user is activated again. When the user is activated again all roles and system accesses will be activated for the user.
Resign user - Use this option to disable the selected user. This will delete all roles and system accesses. It is possible to activate the user again, but roles and system accesses must be added from scratch.
Portal access - Use this option to give the selected user access to https://portal.rambase.net. Click the Assign/Edit portal access and select which Customer (CUS) or Supplier (SUP) the user is representing. The user also need Customer portal user or Supplier portal user role added to be able to access the portal.
Activate user - Use this option to activate an inactive or disabled user.
Re-send invitation email - Use this option to re-send the invitation email to a user.
Write USERS in the program field and press ENTER to open the Users application.
Click the Create user button.
In the popup, choose between three options:
Create RamBase user.
Add RamBase consultant.
Add user(s) from other RamBase systems.
Create RamBase user
Click the Create RamBase user option in the popup.
Select an existing employee in the search field or leave the field empty to create a new user.
Click the Next button.
Fill in the fields. The Lastname/Name and Email fields are mandatory.
Use the Send email notification check box to alert the user by email.
Click the Create button to create the new user.
User(s) created have received an invite mail (if you opted to send an email) with a link to the activation page.
The new user will be prompted to create a new password. The password selected must be minimum 15 characters in length. No other requirements needed.
Users created, but not invited by email will be in status 1. Users created and invited by email will be in status 2. The user will remain in status 2 (invited) until the invitation procedures are followed.
Add RamBase consultant
Select the Add RamBase consultant to give a consultant access to the system.
Click the Add RamBase consultant option in the popup.
The available consultants can be found in the Consultants user field. Select the consultant in the Consultant user field.
Select which database the consultant will get access to, in the Company field.
Write the reason the consultant will get access in the Reason field.
Click the Invite button to send an invite to the consultant.
Add user(s) from other RamBase systems
Click the Add user(s) from other RamBase systems option in the popup.
Select the system the user is from in System field.
Select the user in the User field.
Select which database the user will get access to, in the Company field.
Write the reason the user will get access in the Reason field.
Click the Invite button to send an invite to the user.
The OTPADMIN application displays the IP addresses with exception for using one time password to login to RamBase.
The Search field is a free text filter.
To open the One time password administration (OTPADMIN) application, find Admin in the RamBase menu and then User administration. Click Trusted user networks to enter the OTPADMIN application.
It is possible to create OTP exception from the Users (USERS) application or directly in the OTPADMIN application.
Create OTP exception in the Users application
The user must have logged in from the IP address at least one time with a one time password.
Enter the USERS application.
In the Users area, find and highlight the user.
Click the Sessions folder.
Find the IP address and click the Verify this IP address to disable two-factor authentication icon in the Actions column to create an OTP exception for the selected IP address.
Create OTP exception in the OTPADMIN application
Click the Create OTP exception button.
Write the IP address in the IP address field.
Write a reason in the Description field.
Select system in the System lookup field.
Click the Create button to create an OTP exception.
Delete an OTP exception
Enter the OTPADMIN application.
Find the OTP exception you want to delete.
Click the Trash can icon in the Actions column to delete the OTP exception for the selected IP address.
Edit an OTP exception
Enter the OTPADMIN application.
Find the OTP exception you want to edit.
Click the Edit icon in the Actions column.
It is possible to change the IpAddress, Description and SystemName fields.
Click the check-mark icon in the Actions column to save the changes.
Use the Portal users (PORTALUSER) application to create users that will only have access to the portal. Write PORTALUSER in the program field and press ENTER to open the Portal users application.
Highlight a portal user in the Portal users area to view details about the selected portal user.
It is possible to add predefined filters for more efficient navigation. Click on the Predefined filters icon next to the Search field to see the predefined filters. The selected filters will be available below the Search field.
The Search field is a free text filter. Write name, user name, userid or email and press ENTER to use the Search field.
The Portal user details area displays details about the portal user. It is only possible to edit details about the portal user in the portal users home system.
If the user should be allowed to login from a remote location, click the check-box Allow login from remote location. Select if the user should receive password on SMS or EMAIL in the One time password field.
Click the Assign/Edit portal access button to give the selected portal user access to the portal.
The Search field in the folders is a free text filter.
Statistics - The Statistics folder provides login information as well as the possibility to unblock a portal user.
Sessions - The Sessions folder displays all sessions in this system from various IP addresses. It is also possible to make an IP address secure, click the Verify this IP address to disable two-factor authentication icon in the Actions column. Then the portal user does not need to use a one time password next time the portal user logs in from the IP address. The IP address will be put in the One time password administration (OTPADMIN) application as an exception.
Logs - Log history is stored in the Logs folder.
Roles - It is possible to give the portal user the Customer portal user or the Supplier portal user role in the Roles folder.
Write PORTALUSERS in the program field and press ENTER to open the Portal users application.
Click the Create user button.
In the popup, choose between two options:
Create RamBase user from customer.
Create RamBase user from supplier.
Select customer/supplier in the Customer/Supplier field.
Optional, select contact for the customer/supplier in the Contact field.
Fill in the rest of the fields. Last name / Name and Email is mandatory.
If you did not select a Contact in the Contact field, a new contact will be created and connected to the customer/supplier.
Click the Create button.
New portal user created in the Portal user application, will automatically have access to the portal.
All RamBase users must be assigned to a role in order to perform tasks in the system. RamBase provides a set of system defined roles. If the system defined roles do not fit your company, it is possible to create company defined roles.
Users with admittance to the relevant functionality in the system through assigned roles.
To protect RamBase from unauthorized access, functionality is protected by permissions. E.g. to view a sales order requires one permission, to create a sales order requires another permission.
All functionality in the system is grouped to enable the user to perform different work tasks e.g. to maintain the sales order backlog. In RamBase, a work task is defined as a duty. Permissions will be assigned to the relevant duties. These assignments are referred to as privileges. A duty can consist of one or more privileges that cover the permissions the user needs to perform this work task.
A role is a group of related duties. When a user is assigned to a role, this person will automatically have access to relevant functionality in RamBase.
Sales Assistant is one of the system defined roles provided by RamBase. This role contains duties that cover all the work tasks a sales assistant has to perform.
In order to use RamBase, the system requires all users to be assigned to at least one role.
View details about a role - Name, description, users, and duties added to the role.
Assign users to a role - All users must be assigned to a role.
Create company defined roles - If the standard roles do not meet your company's demand, it is possible to create a company defined role. This can be done by making a copy of a standard role and making changes, or by creating a new role.
Reactivate role - If a role is deactivated in your system, it is possible to reactivate it.
View details about a duty - Description, module, submodule, permissions and permission details.
RamBase provides a set of predefined roles. If new functionality is added to the system, the relevant system defined role will be updated with the necessary duties with permissions for using the new functionality.
The customers get new functionality with new, related permissions, automatically.
The system defined roles cover all roles needed to utilize RamBase in the best possible way. If they do not fit your company, it is possible to create company defined roles.
In a company defined role you can select between the provided duties, and add the duties that are needed to perform the work tasks this role is supposed to cover.
Duties added to a company defined role will be updated automatically.
Note that new duties that are automatically added to system defined roles, must be added to company defined roles manually.
The duties not currently used by your company will be listed in the Unused duties application.
A role can be deactivated if it is not relevant for your company. If a deactivated role is needed again, it can be reactivated.
In the RamBase menu, click Admin > User administration > Roles, or write ROLE in the program field and press ENTER to open the Role application.
Click on the relevant role in the list to view details.
Select the User folder to view the user assignments.
Select the Duties folder to view the duties added to this role.
In the Duties-tree, hover over a duty to view the duty description.
Click the Inspect icon next to the duty to view details.
In the RamBase menu, click Admin > User administration > Roles, or write ROLE in the program field and press ENTER to open the Role application.
Click on the relevant role in the list to view details.
Click on the Competency expectations tab to view the competency expectations for the selected role.
To view details about a competence, click the arrow icon next to the competence name. This will open the Competences (CMP) application.
In the RamBase menu, click HR > Qualifications administration > Competences, or write CMP in the program field and press ENTER to open the Competence application.
Select the competence in the Competence administration area.
Click the Add role expectation button.
Select the role you want to add the competence to in the Role field.
Select the expected score for the competence in the Expected score field.
Click the Create button to add the competence to the selected role.
In the RamBase menu, click Admin > User administration > Roles, or write ROLE in the program field and press ENTER to open the Role application.
Click on the relevant role in the list to view details.
Select the Users folder.
Click the Add user button.
Search for a user by name or user id.
Click on the relevant user.
Click on the confirm button in the User popup to assign the user. By default, the user will have the admittance from the current date.
Add a description. A company setting defines if this is mandatory or optional.
To assign the user to the role for a specified period, set the From-/To-date.
To activate the changes, click on the context menu item Activate admittance changes.
In the RamBase menu, click Admin > User administration > Roles, or write ROLE in the program field and press ENTER to open the Role application.
Click the Add role button under the list of roles.
Select New.
Add a name.
Click the Confirm button to create the role.
Add a detailed description.
Select the Duties folder.
To add duties, set the radio button to All duties.
The duties listed are based on which modules and sub-modules the company has activated.
Click on the duty name to view details.
Use the check boxes to select duties.
Set the radio button to Selected duties to view the duties added to the role.
When all duties are added, click on the context menu option Activate role.
If you add/remove duties or users from the role, you must click on the context action menu option Activate admittance changes to apply the changes.
In the RamBase menu, click Admin > User administration > Roles, or write ROLE in the program field and press ENTER to open the Role application.
Click on the relevant role in the list of roles.
Click on the context menu item Deactivate role for company to deactivate the role for this company.
RamBase provides a set of duties. Duties are work tasks that can be performed in RamBase. When new functionality will be added to the system, the relevant duties will be updated with the necessary permissions for using the new functionality. New duties will be automatically be added to system defined roles.
Duties not currently used by your company will be listed in the Unused duties application.
In the RamBase menu, click Admin > User administration > Duties, or write DUTY in the program field and press ENTER to open the Duty application.
Click on relevant duty in the list of duties.
A list of privileges, with permission names and descriptions, will be displayed.
To view more details about the privilege, click on the Item details button.
In the RamBase menu, click Admin > User administration > Unused duties, or write UNUSEDDUT in the program field and press ENTER to open the Unused duties application.A list of duties and descriptions appears.
Use the information from this list when you add duties to a company defined role in the Role application.
RamBase now supports SSO from the Azure AD. If you use Azure AD, you can set up SSO for your users to allow them to sign in to RamBase with the same credentials they use for Azure AD. Requirements such as Two Factor Authentication (2FA) is handled by Azure AD according to the policies set by your AD administrators.
To activate SSO, the CSV setting Enable users to use single sign on with Microsoft AD must be enabled.
When the setting is enabled, a new menu option Invite user to Microsoft AD login becomes available in the USERS application.
Select Invite user to Microsoft AD login to send an email to your user with instructions on setting up SSO. Select OK in the prompt that appears. This needs to be done for every user that you want to enable to sign in with Azure AD. After set up, users will be able to select Sign in with Microsoft in the RamBase sign in page. The pid/password sign in method is disabled for the user.
To disable the Azure AD sign in for your user, select Reset single-sign-on AD user and Move to invite status. This sends out a new email to the user allowing them to set up the pid/password authentication.
The first time a user enters the Opportunity application, the system will create six default opportunity stages. These stages can be edited, deleted or ordered in a different way.
Open the Opportunity Stages (OPPS) application, find Admin in the RamBase menu and then CRM. Click Opportunity stages to enter the OPPS application.
Click the Add new stage button in the lower left hand corner.
Add the necessary information:
Name: The name of the stage as it will be seen.
Probability: The default probability of a successful deal in percentage for this stage.
Process template: Here we can add a task template which will be triggered each time an opportunity is added to this stage. Task templates are maintained under Collaboration - Task Process Template.
Click the OK button when finished.
Note: If you need to change the order of the stages, click and drag the stage to its intended position.
Loading data is used when we want to create or update multiple documents.
Multiple documents are registered.
Multiple documents are updated.
Multiple documents are registered or updated.
Loading of data is done by using files in CSV format which are uploaded to RamBase, and processed asynchronously.
Create a load file - If multiple documents should be created or updated, a load file must be created.
Process the load file with a relevant load program - A load file has been created and must be processed by a load program so the documents can be created or updated.
Check the log for loading results - After the load program has been completed the log should be checked to see if any errors were reported.
If necessary, modify the entries that could be loaded and repeat - If the load program reported any errors, the rows that there were reported errors on must be modified and reloaded.
Files that are to be imported into RamBase must have comma separated value (CSV) format. The first row of the file is header information. These values must be in upper case letters. The rest of the file consists of records that will be imported. Semicolon (;) must be used as data separator in both the header row and in the data rows. There are no requirements regarding the order of the columns.
Example:
ACCOUNT;ST;NAME
100001;4;Hatteland Computer AS
100002;4;The Hatteland Group AS
See separate topics for each archive, where possible fields to be loaded are listed and explained.
The fields within a load file must be separated with semicolons.
Make sure that all dates are written in the format yyyy.mm.dd (Example: 2015.04.29)
Use full stop (.) as a decimal separator (Example: 3.14)
Do not use thousand separator (1000, not 1 000)
Phone numbers and fax numbers can only contain numbers, and +. (Example: +4712345678, not (+47) 123 45 678)
E-mail addresses must be valid.
EXTID (former identification) has to be unique within one archive.
If there is a text in a field that contains a semicolon, the text must be a quoted string (Example: "123test;101")
There must not be any blank spaces before or after a value in a field.
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 |
NAME | Y | Doe | Company name, or a person's surname. | |
POCODE | Y | 5578 | Postal Code. Will be validated against the POC archive in RamBase. Illegal values will be discarded. | |
CITY | Y | NEDRE VATS | City/town/village. | |
CCODE | Y | 2 | NO | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. Will be validated against the CON archive in RamBase. |
CUR | 3 | NOK, EUR | Currencies this customer buys in. May contain a comma list if several are used. Is validated against a subset of ISO 4217. | |
ST | Y | 1 | 4 | Status of the customer. 1:New, 2:Pending internal approvement, 4:Active, 9:Obsolete. Defaults to 2 if not provided. |
ACCOUNT | 10000 | Customer Id. Unique number created by RamBase. Provide this value if you want to update an existing customer. | ||
FIRSTNAME | John | A person's first name. | ||
ATTN | Jane Doe | Attention. | ||
ADDR1 | Mystery Lane 123 | First address line. | ||
ADDR2 | Post box 9077 | Second address line. | ||
STATE | Y* | CA | * Required if country (CCODE) is Canada or USA. | |
PHONE | +4752763390 | Customer's main phone number. Can not contain any letters or spaces, but + is OK as prefix. Must be four digits or more. | ||
john.doe@msn.com | Customer's main mail address. Will be validated. | |||
FAX | +34915300164 | Customer's main fax number. Can not contain any letters or spaces, but + is OK as prefix. Must be six digits or more. | ||
ENTERPRISE | NO924054832MVA | Legal entity, a unique enterprise/organization number. | ||
VATNO | PL669 248 43 58 | Value Added Tax (VAT) registration number. Unique number assigned by the relevant tax authority. | ||
LANGUAGE | 3 | eng | Preferred language. Value is stored as a three character code, according to ISO 639-2 standard. Will be used to produce output to customer in correct language. | |
SHIPBYNO | 100036 | Preferred shipping method for sales orders. Will typically be a carrier's product. Numbers are references to SHP archive. | ||
DELTERM | FCA, Incoterm 2010 | Delivery terms for shipments to customer. Valid options have to be set up by JHC personnel in advance. | ||
PAYTERM | NET,10 | Payment terms. Duedate on invoice documents are calculated based on Payterm. Valid options have to be set up by JHC personnel in advance. Valid options: ADVANCE - Payment in advance NET, X - Day(s) net COD - Cash on delivery COP - Cash on pick up EOCM, X - Net x day(s) EOM | ||
PAYBY | Credit card | Method of payment. Valid options have to be set up by JHC personnel in advance. | ||
PRICEAGR | 100-PR | Quantity Price Agreement. E.g 100-PR means that even if an order line is for less quantity than 100 pieces, it will pick of the volume price of 100 pieces from the product (ART). Valid options have to be set up by JHC personnel in advance. | ||
INDEXAGR | 80/1.5 | Exchange fluctuation rate agreement. When an order is issued, RamBase stores the current exchange rate and the currency the part normally is purchased in. The exchange rate might have changed when the invoice is issued. The exchange rate fluctuation agreement specifies how to handle these differences. The agreement has the format AAA/BBB, where AAA is a percentage of the total invoice, and BBB is the exchange rate fluctuation percentage. E.g. 80/3.0 means that if the rate of exchange on the date a customer order is transported to an invoice has changed more than +/- 3% from the rate of exchange, 80% of the invoice amount will be adjusted. | ||
ACCOUNTCL | C | Classification of customers. Valid options have to be set up by JHC personnel in advance. | ||
DISTRICT | South | A geographic district for which an individual sales person or a sales team hold responsibility. Valid options have to be set up by JHC personnel in advance. | ||
SEGMENT | Military | The market segment the customer operates within. Valid options have to be set up by JHC personnel in advance. | ||
SECTOR | Distributor | The sector the customer belongs to. Valid options have to be set up by JHC in advance. | ||
INCLVAT | NO | Specifies how value added tax (VAT) should be calculated. Either always include VAT, always exclude VAT or use standard/default VAT rules. Valid options are: YES = if the customer always should pay VAT NO = if the customer never should pay VAT ‘blank’ = Std VAT rules will be used. | ||
CREDITLIM | 20000 | Maximum limit for customer credit, in currency given by company currency. | ||
CREDITINS | 400000 | Credit amount insured for the customer, in company currency. | ||
INSCOMPANY | AIG | Insurance company used by the customer for credit insurance. | ||
DUEAPPROVE | NO | "YES" if approval before shipping orders are required when outstanding accounts are overdue. | ||
REMINDER | YES | Set to "NO" if dunning letters for outstanding amounts should not be created for the customer. | ||
INTFEE | 25 | Interest rate used when creating interest invoices for invoices that have past duedate. | ||
SHIPDAY | 2 | D3 | Specifies which day orders will be shipped. Valid options are: V1-V5 = E.g V1 means Monday in the week before orders requested/confirmed date. W1-W5 = E.g W2 means Monday in the week the order is requested confirmed. D0-D9 = E.g D2 means two days before the order is requested/confirmed. If no value is provided, this is understood as D0. If the shippingday is based on requested or confirmed date is depending on set up in SHIPONCONF. | |
SHIPONCONF | YES | If set to YES, orders should be shipped to meet the confirmed date rather than requested. Is used in combination with SHIPDAY. If no value is provided, this is understood as NO. | ||
SHIPCOMPLETEITM | YES | Decides whether the whole quantity in an order item always should be shipped together. If set to YES, the order item should never be splitted into several shipments. If no value is provided, this is understood as NO. | ||
SHIPCOMPLETEDOC | YES | Decides whether all items of an order should be shipped together. If set to YES, the items of an order should never be splitted into several shipments. If no value is provided, this is understood as NO. | ||
SHIPCONS | YES | Decides whether order items will be consolidated into shipping advices in automatic processes. If set to NO, each order will result in separate shipping advice. If set to YES, several orders will be consolidated in to one Shipping Advise. If no value is provided, this is understood as NO. | ||
SHIPGROUPBY | YOURNO | Field to group by if the value YES is set in the SHIPCONS field. | ||
SHIPSORTBY | PART | Field to sort by if the value YES is set in the SHIPCONS field. | ||
SHIPSUBFGT | YES | Decides whether freight should be charged on sub-shipments or not. If no value is provided, this is understood as NO. | ||
SHCODE | SHC/100007 | Refers to special shipping and handling code for orders from this customer. Valid options have to be set up in SHC archive prior to the load. | ||
INVCONS | 1 | M | Specifies whether or how often shipping advise items will be consolidated when creating invoices. Valid options are: N = No consolidation X = Excluded from automatic creation of invoice. D = Daily W = Weekly M = Monthly If no value is provided, this is understood as the value N (No consolidation), which means that the invoice is automatically created when the shipping advise is sent. | |
INVGROUPBY | YOURNO | Field to group by if the values D, W or M are set in the INVCONS field. | ||
INVSORTBY | PART | Field to sort by if the values D, W or M are set in the INVCONS field. | ||
FEEPCT | 5 | Percentage of financial charge to be added to orders. | ||
FEE | 50 | An amount in document currency that will be added to an order. | ||
QUOTEBLOCKED | YES | Sales quotes for this customer will be blocked for registering. | ||
ORDERBLOCKED | YES | Orders for this customer will be blocked for registering. | ||
INVOICEBLOCKED | YES | Invoices for this customer will be blocked for registering. | ||
SHIPPINGADVICEBLOCKED | YES | Shipping advices for this customer will be blocked for registering. | ||
MSG | Customer wants estimates in EURO. | Internal note/notice about the customer. | ||
MINGM | 20 | The minimum accepted gross margin in percentage (%). | ||
ICTDB | JHR-NO | Inter Company Trading DataBase. Used to identify internal customer/suppliers. | ||
PIDEXT | 902 | Account manager, refers to a PER. | ||
PIDINT | 8900 | Account sales assistant, refers to a PER. | ||
EXTID | External customer reference/identifier. | |||
EDIACCOUNT | 1234567 | Electronic data interchange account number. | ||
EDIPARTNER | STANDARDEHF | Electronic data interchange partner. | ||
SEMAIL | john.doe@msn.com | Email for the default shipping address for customer. Will be validated. | ||
SPHONE | 4752763390 | Phone for the default shipping address for customer. Can not contain any letters or spaces, but + is OK as prefix. Must be four digits or more. | ||
PLINO | 6 | 100000 | Identification number of Price list (PLI) the customer belongs to. |
You find it by typing the RamBase command: "INP/72500". By using this you may upload purchase orders (SPO) to the system.
Field | Required | Length | Example | Description |
|---|---|---|---|---|
SUPPLIERID | Y | Supplier account. | ||
CURRENCY | Y | Currency of the purchase order. | ||
SUPPLIERSREFERENCENUMBER | Suppliers reference number e.g. quote number. | |||
PRODUCTID | Product Id (IT). | |||
PRODUCTNAME | Product name. Either product id or product name must exist on a line. | |||
SUPPLIERSPRODUCTNAME | Suppliers product name. | |||
QUANTITY | Y | Quantity to purchase. | ||
REQUESTEDATE | Y | Requested date. | ||
NETPRICE | Purchase price. | |||
MPN | MPN, if MPN is provided also Manufacturer is required. | |||
MANUFACTURER | Manufacturer. | |||
NOTE | Note on the SPO item. |
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 * | 123456 | Customer Id. Unique number created by RamBase. * To identify the customer to be updated ACCOUNT or EXTID must be provided in the file. | |
EXTID | Y * | External system customer Id. * To identify the customer to be updated ACCOUNT or EXTID must be provided in the file. | ||
SFIRSTNAME | John | A person's first name in the shipping address. | ||
SNAME | Doe | Company name, or a person's surname in the shipping address. | ||
SATTN | Jane Doe | Attention in the shipping address. | ||
SADDR1 | Mystery Lane 123 | First address line in the shipping address. | ||
SADDR2 | Post Box 9077 | Second address line in the shipping address. | ||
SPOCODE | 5578 | Postal code in the shipping address. Will be validated against the POC archive in RamBase. Illigal values will be discarded. | ||
SCITY | NEDRE VATS | City/town/village in the shipping address. | ||
SSTATE | TN | A US state. | ||
SHIPCC | 2 | NO | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. Will be validated against the CON archive in RamBase. | |
SCODE | S12 | Unique shipping code, used if e.g. a customer has a special code to identify a special plant. | ||
SSHCODE | SHC/100007 | Refers to a special shipping and handling code for orders to this shipping address. Valid options have to be set up in the SHC archive prior to the load. | ||
SPHONE | +4752763390 | Phone number for this shipping address. | ||
SFAX | +34915300164 | Fax number for this shipping address. | ||
SEMAIL |
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 |
NAME | Y | Doe | Company name, or a person's surname. | |
POCODE | Y | 5578 | Postal Code. Will be validated against the POC archive in RamBase. Illegal values will be discarded. | |
CITY | Y | NEDRE VATS | City/town/village. | |
CCODE | Y | 2 | NO | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. Will be validated against CON archive in RamBase. |
CUR | 3 | NOK, EUR | Currencies this supplier sells in. May contain a comma list if several. Is validated against a subset of ISO 4217. | |
ST | Y | 1 | 4 | Status of the supplier. 1:New, 2:Pending internal approvement, 4:Active, 9:Obsolete. Defaults to 2 if not provided. |
ACCOUNT | 10000 | Supplier Id. Unique number created by RamBase. Provide this value if you want to update an existing supplier. | ||
FIRSTNAME | John | A person's first name. | ||
ATTN | Jane Doe | Attention. | ||
ADDR1 | Mystery Lane 123 | First address line. | ||
ADDR2 | Post box 9077 | Second address line. | ||
STATE | Y* | CA | * Required if country (CCODE) is Canada or USA. | |
PHONE | +4752763390 | Supplier's main phone number. Can not contain any letters or spaces, but + is OK as prefix. Must be four digits or more. | ||
john.doe@msn.com | Supplier's main email address. Will be validated. | |||
FAX | +34915300164 | Supplier's main fax number. Can not contain any letters or spaces, but + is OK as prefix. Must be six digits or more. | ||
ENTERPRISE | NO924054832MVA | Legal entity, a unique enterprise/organization number. | ||
VATNO | PL669 248 43 58 | Value Added Tax (VAT) registration number. Unique number assigned by the relevant tax authority. | ||
LANGUAGE | 3 | Eng | Preferred Language. Value is stored as a three character code, according to ISO 639-2 standard. Will be used to produce output to supplier in correct language. | |
SHIPBYNO | 100036 | Preferred shipping method for purchase orders. Will typically be a carrier's product. Numbers are references to SHP archive. | ||
OUTGOINGSHIPBYNO | 100012 | Preferred shipping method for sales orders. Will typically be a carrier's product. Valid options have to be set up by JHC personnel in advance. Numbers are references to SHP archive. | ||
DELTERM | FCA Oslo | Delivery terms for shipments from supplier. Valid options have to be set up by JHC personnel in advance. | ||
PAYTERM | NET,10 | Payment terms for this supplier. Valid options have to be set up by JHC personnel in advance. If duedate on invoice documents are not manually filled, this will be calculated based on PayTerm. Valid options: ADVANCE - Payment in advance NET, X - Day(s) net COD - Cash on delivery COP - Cash on pick up EOCM, X - Net x day(s) EOM | ||
PAYBY | SWIFT | Method of payment. Valid options have to be set up by JHC personnel in advance. | ||
ACCOUNTCL | C | Classification of suppliers. Valid options have to be set up by JHC personnel in advance. | ||
DISTRICT | South | A geographic district. Valid options have to be set up by JHC personnel in advance. | ||
SEGMENT | Electronics | The market segment the supplier operates within. Valid options have to be set up by JHC personnel in advance. | ||
SECTOR | Distribution | The sector the supplier operates within. Valid options have to be set up by JHC personnel in advance. | ||
PAYBLOCKED | 1 | If set to 1, the system will block for generating payments to supplier. 0 is default value -> no blocking | ||
PREFERRED | YES | Preferred supplier. If set to ‘YES’, this supplier will be highlighed and suggested in the purchase application (PUR). | ||
MSG | Duplicate registered, use SUP/12345 instead. | Internal note/notice about the supplier. | ||
PURCHGROUP | Used to define certain buyers/groups for specific articles. Allows filtering by this in the purchase program (PUR). Valid options have to be set up by JHC personnel in advance. | |||
ICTDB | JHR-NO | Inter Company Trading DataBase. Used to identify internal customer/suppliers | ||
EXTID | External supplier reference/identifier. |
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* | 100000 | Supplier Id. Unique number created by RamBase. Provide this value if you want to update an existing supplier. *ACCOUNT or EXTID must be present in the file. | |
EXTID | Y* | 12345 | External supplier reference/identifier. Can be used in external systems. *ACCOUNT or EXTID must be present in the file. | |
BANKCCODE | Y | DK | The bank's country code | |
BANKACC | Y | 3254.12.35675 | Bank account number | |
BANKSWIFT | dabano22 | The bank's international identification number | ||
BANKNAME | Danske bank | Bank name | ||
BANKCODE | 123002911 | Bank code | ||
BANKCUR | Y | DKK | Currency | |
IBAN | NO9386011117947 | International Bank Account Number |
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 |
CUR | Y | NOK | Currency. The value must valid for the given supplier. | |
PART | Y | EP1K50TC144-2 | Product name. Must exist in the article archive. PART and MFR are used to identify the correct product. | |
MFR | Y | ACME | Manufacturer. | |
PRICE | Y | 168.00 | Quoted price in given currency. | |
ACCOUNT | 10278 | Supplier Identifier. | ||
YOURNO | Supplier quote number. | |||
YOURREF | John Doe | Supplier reference, typically a person. | ||
VALIDFROM | 2003.03.17 | Date that the quote is valid from. Can be overruled on each item by value in EXPIRE. | ||
VALIDTO | 2004.03.05 | Date that the quote is valid to. | ||
ISSHIPANDDEBIT | 1 | 1 | Valid options are "0" and "1", should be set to "1" if it is a Ship & Debit quote. It is automatically set to "0" which means that the system will understand it as an ordinary quote. | |
QTY | 5040 | Quoted quantity. | ||
EXPIRE | 2015.06.30 | Date that a specific item in the quote is valid to. | ||
CUSTOMER | TEM-NO:CUS/10246 | Customer to be supplied if the supplier quote is valid for one customer only. |
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 | Customer identifier | ||
CUR | Y | NOK | Currency. The value must be valid for the given customer. | |
QTY | Y | 10 | Quoted quantity | |
PART | Y* | EP1K50TC144-1 | Product name. Must exist in the article archive. *PART/MFR or CUSPART is used to identify the correct product. | |
MFR | Y* | ACME | Manufacturer. *PART/MFR or CUSPART is used to identify the correct product. | |
PRICE | Y | 159 | Quoted price in given currency. | |
EXPIRE | Y** | YYYY.MM.DD | Date that a specific item in the quote is valid to. **VALIDFORM or EXPIRE must have a value. | |
VALIDFROM | Y** | YYYY.MM.DD | Date that a quote is valid from. **VALIDFORM or EXPIRE must have a value. | |
VALIDTO | YYYY.MM.DD | Date that the quote is valid to. If not defined, it will get a default value configured for the company. | ||
YOURNO | HLD/12345 | Customer quote number. | ||
YOURREF | John Doe | Customer quote reference, typically a person. | ||
SQUREF | ||||
CUSPART | Y* | EP1K50TC144-10 | Customer product name. Must exists as a customer product name associated with the customer on a product. *PART/MFR or CUSPART is used to identify the correct product. |
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.
Y if PrivacyPolicyAccepted should be set. Blank if not Y = Yes
Field | Required | Length | Example | Description |
NAME | Y* | Doe | Company name, or a person's surname. *Only required if creating a new Contact. | |
EXTID | 01018012345 | NO or EXTID must be specified if existing Contact should be updated. | ||
FIRSTNAME | John | |||
CATEGORY | See DOV CATEGORY for valid values. | |||
LEGALBASIS | See DOV LEGALBASIS for valid values. | |||
MARKETINGCONSENT | Y | Y if MarketingContent should be set. Blank if not. Y = Yes. | ||
NO | NO or EXTID must be specified if existing Contact should be updated. | |||
ST | 1 | 4 | Status. Legal values: 1:New, 2:Pending internal approvement, 4:Active, 9:Inactive. If not specified, new contacts will get st:4. | |
PRIVACYPOLICYACCEPTED | Y | Y if PrivacyPolicyAccepted should be set. Blank if not. Y = Yes | ||
SOURCE | See DOV SOURCE for valid values. | |||
TITLE | Sales manager | Title | ||
LANGUAGE | 3 | ENG | Language. ISO 639.2 |
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 |
|---|---|---|---|---|
EXTID | 01018012345 | NO or EXTID must be specified to find Contact. | ||
ADDR1 | Mystery Lane 123 | First address line. | ||
ADDR2 | Post box 9077 | Second address line. | ||
ADDRFIRSTNAME | Jane | |||
ADDRNAME | Doe | Company name, or a person's surname. | ||
ATTN | Jane Doe | Attention. | ||
CCODE | NO | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. Will be validated against the CON archive in RamBase. | ||
CITY | Nedre Vats | City/town/village. | ||
COMMDETAILS | doe@company.com | Phone number or email - depends on CommDescr. | ||
COMMTYPE | See DOV COMMTYPE for valid values. | |||
COUNTRY | Norway | |||
ISDEFAULT | Y if Email/Phone/address should be set as the default. Blank if not. Y = Yes. | |||
NO | NO or EXTID must be specified to find Contact. | |||
POCODE | 5578 | Postal Code. Will be validated against the POC archive in RamBase. Illegal values will be discarded. | ||
STATE | CA | US or Canadian state. |
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 |
|---|---|---|---|---|
EXTID | 01018012345 | NO or EXTID must be specified to find Contact. | ||
ISPORTALUSER | Y if reference should be set as PortalUser. Blank if not. Y = Yes | |||
NO | NO or EXTID must be specified to find Contact. | |||
REFNO | REFNO or REFNOEXTID must be specified to find Reference. ACCOUNT (CUS/SUP) or PID (PER). | |||
REFNOEXTID | REFNO or REFNOEXTID must be specified to find Reference. REFNOEXTID is only valid for REFTYPE: CUS or SUP. | |||
REFTYPE | CUS, SUP or PER. |
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 |
MFR | Y | JHC | Manufacturer's Short name | |
ST | Y | 4 | Status | |
NAME | Jakob Hatteland Computer | Manufacturer's Full name | ||
SEGMENT | Computers | What kind of segment this MFR produces goods for. | ||
URL | Reference to the manufacturer's web-page. | |||
PARTNER |
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 |
TARIC | Y | 8531.90.90.090 | Customs clarification code | |
CCODE | Y | PL | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. | |
DESCRIPTION | DISPLAY, PARTS | Description. | ||
DUTYPCT | 5.2 | Duty percent. Ordinary duty rate, but goods can be duty free if the goods have preferential origin status. | ||
UNITDUTY | 1.28 | Unit duty. | ||
WEIGHTDUTY | 32.29 | Weight duty. | ||
MEASURE | GRM | Measure. The unit that will be used for preparation of statistical data. Valid options: GRM = Gram MTK = m2 (square meters) MTQ = m3 (cubic meters) NMB = pieces NPR = pairs | ||
ENVIRONMENTTAX | 20.32 | Environment tax. Only some countries have this tax. | ||
THIRDCONLIMITPCT | 2.5 | Third country limit cost in percent. Used to calculate if goods produced in a certain country, with components from 3rd countries included, are obligated to preferential origin status. | ||
UNION | EU | Union. |
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 |
PARTEXTID | Y | External identifier to the product | ||
SERIALNO | Y | Serial number of the product | ||
NEXTSERVICE | Date of the next service in the format YYYY.MM.DD | |||
NO | 6 | 100000 | Number of the measuring tool document | |
LASTSERVICE | Date of the next service in the format YYYY.MM.DD | |||
METGROUP | Production group | |||
STATUS | Status | |||
STOCKLOC | Stock location | |||
EXTID | 10017812346 | The external identifier to the measuring tool | ||
INSTRUMENTNAME | The name of the instrument |
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.
It is recommended to use the Load article purchase prices to load Purchase prices. If you still decide to use this load for it, then you need to check Load article purchase prices to see which field are required.
To be able to identify and update an article at a later time, the initial load must contain values in the fields PART, MFR, and the field CREATE must be set to YES. It is also recommended to add a value to the field EXTID.
To identify the article to be updated, the load file must contain a value in the field IT or a combination of the fields PART+MFR.
Field | Required | Length | Example | Description |
CREATE | Y* | 3 | YES | If you want to create a new article you have to set this value to YES. If blank, the system will try to update existing articles. Existing article will be found by exact match on: a) IT (RamBase internal article ID) b) Part + MFR * Required if the article does not exist in the ART archive. |
IT | Y* | 7 | #100000 | Internal typenumber is a unique ID that identifies the article. This will be assigned by RamBase when a new article is created. * IT or PART+MFR must be present in the file. |
ST | Y | 1 | 4 | Status of the article. Legal values: 2 – new, 3 – For approval, 4 – Ordinary article, 5 – To be revised, 6 – On hold, 7 – Announced EOL (end of life), 9 – Obsolete / discontinued. |
PART | Y * | 35 | 190-489-A1 | Article name. * IT or PART+MFR must be present in the file. |
MFR | Y * | 20 | ACME | Manufacturer. The manufacturers have to be registered in the Manufacturer archive (MFR) in RamBase prior to the article load. * IT or PART+MFR must be present in the file. |
EXTID | External supplier reference/identifier. | |||
LOC | Y ** | 3 | AUT | Warehouse code for MINSTOCK quantity and REORDERQTY and STOCKLOC. LOC must match one of the values predifined in the LOC register. LOC must be active (St:4). **If LOC has a value, MINSTOCK or STOCKLOC must have a value too. |
MINSTOCK | Y ** | 8 | Minimum stock value for the given article connected to the given location (LOC). **If this field has a value, the field LOC must have a value too. | |
REORDERQTY | Y ** | 8 | Re-order quantity for given location (LOC). Must be an integer value. **If this field has a value, the fields LOC and MINSTOCK must have a value too. | |
STOCKLOC | Y** | Preferred inhouse stock location for given location (LOC). **If this field has a value, the field LOC must have a value too. | ||
TEXT | 110 | Cable 0,5 meters | Article description. | |
URL | 110 | Link to a page on the internet. (URL = Uniform Resource Locator) | ||
PURCHASELEADTIME | 8 | 12 | Standard Purchase lead time could be added in Purchase on Product (ART). Valueis delivery time from Supplier, in days. | |
SALESLEADTIME | 8 | 12 | Sales lead time could be added in Main Data on Product (ART). Value is number of days used when calculating assignment window. | |
SUPLEADTIME | 8 | 12 | Supplier lead time could be added in Part Supplier Info pop-up on product (ART). | |
PACK | 8 | Box | Package type. "Box", "Reel", ..... | |
GR1 | 20 | Cable | Field used to support local classification purposes. Free text. Inherited to orders, invoices etc. | |
GR2 | 20 | HDMI | Field used to support local classification purposes. Free text. Inherited to orders, invoices etc. | |
PACKQTY | 10 | 10 | Quantity per package. | |
SUBQTY | 10 | 5 | Sub-Quantity, inner pack. | |
ORIGIN | 2 | JP | Country of Origin. Stored as two-character code according to the ISO 3166 standard. | |
WEIGHT | 12 | 0.5 | Weight per component - in kilogram. | |
CLASS | 2 | P | Classification: See topic Define class on a new article in RamBase Knowledge center. | |
MSG | 55 | For Test Only ! | Message on the article. | |
MINGM | 10 | 90 | Minimum allowed gross margin in percent (%). | |
FRPCT | 2.5 | Freight percent (%) on products in the product structure cost table. | ||
REQUIRESERIALNOTOSHIP | 1 | Legal values: 1 / 0 1=YES, 0=NO If set to YES: Serial numbers have to be registered on CSA, SRT, and STW before shipping parts. | ||
REQUIRESERIALNOTORECEIVE | 0 | Legal values: 1 / 0 1=YES, 0=NO If set to YES: Serial numbers have to be registered on SSA before the goods can be received. | ||
INCLUDEINLCMPARTLIST | 1 | Legal values: 1 / 0 1=YES, 0=NO If set to YES: Serial numbers will be included in part list in LCM. | ||
AUTOCREATESERIALNOFORLCM | 0 | Legal values: 1 / 0 1=YES, 0=NO If set to YES: Serial numbers will automatically be created for LCM in a production. *According to setup in the fields SNOPREFIX and SNOCNT. | ||
AUTOCREATESERIALNOFORSPO | 1 | Legal values: 1 / 0 1=YES, 0=NO If set to YES: Serial numbers will automatically be created for LCM in a production. *According to setup in the fields SNOPREFIX and SNOCNT. | ||
TARIC | 20 | 49.01.9909 | Local custom taric code for non EU-countries. | |
EUTARIC | 20 | 8471.60.40.00 | Customs taric code for EU-countries. | |
EAN | 35 | 4030661359847 | European article numbering. US: UCC Uniform Code Council (barcode) | |
RANK | 1 | ABC ranking. Free text field. | ||
WARRANTY | 6 | Warranty time in months. | ||
PURCHCUR | SEK | Purchase currency. | ||
PURCHPRICE | 0.15 | Purchase price in purchase currency. | ||
PURCHCOL | STD | Purchase price type - STD, Contract, Special | ||
PURCHQTY | 10 | 1 | Purchase quantity. | |
PURCHSTATUS | 15 | Valid | Purchase status. Values: "Valid", "Preferred". | |
PURCHFROM | 2005.06.20 | Purchase price valid from date. | ||
PURCHTO | 2015.01.20 | Purchase price valid to date. | ||
SUPPART | 30 | SP 101963 | Supplier's internal part number. | |
SUP | SUP/123456 | RamBase supplier number. If SUPPART is filled, SUP or SUPEXTID must also have a value. | ||
SUPEXTID | Legacy system supplier identification. If SUPPART is filled, SUPEXTID or SUP must also have a value. | |||
SUPMINQTY | 15 | Minimum order quantity for this supplier. | ||
UNIT | pcs | Trade unit for the part. Values like "pcs", "mm", "kg".. The UNI archive must be defined before the ART load. All trading (purchase, stock, sales, ...) must follow the UNIT of the article. | ||
PRODLINE | A production line. Used for articles of Class = K* to control which internal production-"supplier" to use for work orders and which production line that is default for the product. | |||
PALLETQTY | 10 | Quantity per pallet. | ||
DESCR | Long description | Detailed description for the request. | ||
CODE | 1010011000 | Classification Code: Reference to the Classification Management Code (WGR). Value concatinated from values of Code0 – Code6. CODE is inherited to orders, invoices ... . | ||
CODE0 | 2 | 10 | ||
CODE1 | 4 | 1001 | ||
CODE2 | 4 | 1000 | ||
CODE3 | 4 | 1001 | ||
CODE4 | 4 | |||
CODE5 | 4 | |||
CODE6 | 4 | |||
AO | 8 | AO | Announced to become obsolete. | |
CO | 2 | CO | Commodity article. | |
PP | 2 | PP | Price protected article. | |
MIRROR | 3 | YES | If value = YES: Article will be created if not found even if field CREATE <> "YES". | |
PURCHGROUP | Used to define certain buyers/groups for specific articles. Allows filtering by this in the purchase program (PUR). Value must match predefined purchase group in GRP register. | |||
SERVICEID | ART/#101234 | ID to the main service article (Class = KM) for the product. | ||
SERVICEDELETE | 1 | Y | If "Y": Main service article will be deleted from the product. | |
SERVICEMAIN | 1 | Y | "Y" if the given SERVICEID shall be main service. | |
RENTAL | Y/YES | If value = "Y" or "YES" and CREATE = "YES": A rental "part" (Class = R) will be created for the article. | ||
RENTALPRICE | 25.00 | Rental price for the part, in currency given by RENTALCUR. | ||
RENTALCUR | NOK | Rental price currency. | ||
REVISION | 1 or A1 or.. | Article revision number. | ||
ISEXTERNALLYMANUFACTURED | 1 | Y | True if the article is manufactured externally. Only valid for articles with CLASS:K*. | |
BLOCKING | P,S, | One letter value for each Blocking that should be set on Article. Valid options can be seen when selecting the option in the Blocking field on ART. Field can be blanked by sending in the value (BLANK). |
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 |
PART | Y * | 35 | 190-489-A1 | Article name. |
MFR | Y * | ACME | Manufacturer. The manufacturers have to be registered in the Manufacturer archive (MFR) in RamBase prior to the article load. | |
CUSPART | Y ** | 24 | 290631 | Customer's internal part number. **If CUSPART has a value, CUS or CUSEXTID must have a value too. |
CUS | Y ** | CUS/123456 | RamBase customer number. **If CUSPART has a value, CUS or CUSEXTID must have a value too. | |
CUSEXTID | Y ** | Legacy system customer identification. **If CUSPART has a value, CUS or CUSEXTID must have a value too. | ||
CREATE | YES | If you want to create a new article you have to set this value to YES. If blank, the system will try to update existing articles. Existing article will be found by exact match on: a) IT (RamBase internal article ID) b) Part + MFR If you put YES in this field, a new PART will be created in St=0 with default settings for MFR and CLASS. This article will be updated with given CUSPART information. |
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 |
PART | Y * | 35 | 190-489-A1 | Article name. |
MFR | Y * | 20 | ACME | Manufacturer. The manufacturer has to be registered in the Manufacturer archive (MFR) in RamBase prior to the article load. |
SUPPART | Y ** | 30 | SP 101963 | Supplier's internal part number. **If SUPPART is filled, SUPEXTID or SUP must have a value too. |
SUP | Y ** | SUP/123456 | RamBase supplier number. **If SUPPART is filled, SUPEXTID or SUP must have a value too. | |
SUPEXTID | Y ** | Legacy system supplier identification. **If SUPPART is filled, SUPEXTID or SUP must have a value too. | ||
CREATE | YES | If you want to create a new article you have to set this value to YES. If blank, the system will try to update existing articles. Existing article will be found by exact match on: a) IT (RamBase internal article ID) b) Part + MFR | ||
SUPCUR | EUR | The supplier's selling currency for this article. | ||
SUPMINQTY | 15 | Minimum order quantity for this article/supplier. | ||
SUPMINVALUE | 500 | Minimum order value for this article/supplier, in the currency given in the SUPCUR field. | ||
SUPLEADTIME | 12 | This supplier's delivery time, in days. |
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 |
IT | Y * | 7 | #100000 | Internal typenumber is a unique ID that identifies the article. This will be assigned by the system when a new article is created. Format: #123456 * IT, PART or EXTID must be present in the file. |
PART | Y * | 35 | 190-489-A1 | Article name. * IT, PART or EXTID must be present in the file. |
EXTID | Y * | External ID to identify Articles from the customer's system. * IT, PART or EXTID must be present in the file. | ||
PURCHSUP | Y ** | Supplier's account number in RamBase. ** PURCHSUPEXTID or PURCHSUP must be present in the file. | ||
PURCHSUPEXTID | Y ** | External ID to identify the supplier from the legacy system. ** PURCHSUPEXTID or PURCHSUP must be present in the file. | ||
PURCHCUR | Y | EUR | Buying currency. | |
PURCHQTY | Y | 1 / 100 / ... | The quantity that the given PURCHPRICE is valid for. | |
PURCHFROM | Y | 2015.10.01 | Purchase price valid from date. | |
PURCHCOL | Y | STD | Price type: STD (Standard), CONTRACT (Contract price), SPECIAL (Special price). | |
PURCHSTATUS | Y | Valid | Valid price or Preferred price. If set to Preferred the default cost price of the article will be this one, even if lower loaded price for other supplier. | |
PURCHPRICE | Y *** | 10.20 | Purchase price for the given PURCHQTY. ***Do not load if PURCHCONVERT-fields are used. | |
PURCHCONVERTUNIT | Y *** | Kg | This is used if the purchase price is given in an other unit than the stock keeping unit. Example: Steel has often stock keeping unit mm, and the supplier gives the price in Kg. *** Do not load if PURCHPRICE is loaded. | |
PURCHCONVPRICE | Y *** | 1200.00 | The price per PurchConvertUnit, e.g. the price per kg of the material. *** Do not load if PURCHPRICE is loaded. | |
PURCHUNITFACTOR | Y *** | 0.012 | This is the factor used to convert Unit to PurchConvertUnit. E.g. How much does 1 mm of the material weigh? The price per stock keeping unit (PurchPrice) is then calculated based on these inputs. *** Do not load if PURCHPRICE is loaded. | |
PURCHTO | 2015.12.31 | Purchase price valid to date. | ||
PURCHREF | A12345 | Contract number if PURCHCOL = CONTRACT. |
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 |
IT | Y * | #100000 | Internal typenumber is a unique ID that identifies the article. This will be assigned by the system when a new article is created. Format: #123456 * IT, PART or EXTID must be present in the file. | |
PART | Y * | 35 | 190-489-A1 | Article name. * IT, PART or EXTID must be present in the file. |
EXTID | Y * | External ID to identify Articles from the Customer's system. * IT, PART or EXTID must be present in the file. | ||
MFR | 20 | ACME | Manufacturer. The manufacturers have to be registered in the Manufacturer archive (MFR) in RamBase prior to the Article load. | |
SALESCUR | Y | NOK | Selling currency. | |
SALESQTY | Y** | 5 | Quantity step for sales prices. ** Can not have a value if SALESPRICEGROUPAGREEMENT has a value. | |
SALESPRICEGROUPAGREEMENT | Y** | Price agreement for a group of customers. Valid options have to be set up by JHC personnel in advance. ** Can not have a value if SALESQTY has a value. | ||
SALESDB | Selling database. | |||
SALESPRICE | 8.6 | Salesprice in the currency defined in SALESCUR, and the quantity defined in SALESQTY. | ||
SALESGM | 80 | Sales gross margin in percent (%). Will be calculated if SALESPRICE is set. | ||
SALESFROM | 2005.06.200523 | Sales price valid from set date. Must be a value before SALESTO. | ||
SALESTO | 2015.01.201504 | Sales price valid until set date. Must be a value after SALESFROM. | ||
PLINO | 100000 |
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.
At least one of the fields PRODUCTID, PRODUCTNAME and EXTERNALPRODUCT must be provided to identify the article.
Field | Required | Length | Example | Description |
PRODUCTID | Y* | #100000 | The Product ID assigned by Rambase. *If PRODUCTNAME is not a unique value you must use PRODUCTID or EXTERNALPRODUCTID. | |
PRODUCTNAME | Y* | Mobile phone | The name of the product (Part). *If PRODUCTNAME is not a unique value you must use PRODUCTID or EXTERNALPRODUCTID. | |
EXTERNALPRODUCTID | Y* | 123456 | The product external ID. *If PRODUCTNAME is not a unique value you must use PRODUCTID or EXTERNALPRODUCTID. | |
ACCKEY | Y | HOMESALE | Account key. Valid options: HOMESALE, VATSALE, EUSALE, EXPSALE, XMSALE, HOMEPURC, VATPURCH, EUPURC, EXPPURC and XMPURC. Possible to specify multiple values using a commalist, e.g. "HOMESALE,VATSALE". Unique key for account record. | |
ACCCODE | Y** | 1030 | General Ledger (GL) account number. **ACCCODE, DEPNO, PRJNO or ASTNO must have a value. | |
DEPNO | Y** | 1000 | Department number. **ACCCODE, DEPNO, PRJNO or ASTNO must have a value. | |
PRJNO | Y** | 1001 | Project number. **ACCCODE, DEPNO, PRJNO or ASTNO must have a value. | |
ASTNO | Y** | 1003 | Asset number. **ACCCODE, DEPNO, PRJNO or ASTNO must have a value. | |
VATCODE | 00 | Value added tax code. | ||
DIM4 | Dimension 4 | |||
DIM5 | Dimension 5 | |||
DIM6 | Dimension 6 | |||
DIM7 | Dimension 7 | |||
DIM8 | Dimension 8 | |||
DIM9 | Dimension 9 | |||
DIM10 | Dimension 10 |
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.
The order of the loaded structure is given by the value in the field KITOPNO, and the order in the file. It is recommended to put operations first, and then articles (PART). The articles are loaded into the structure, for the corresponding KITOPNO, in the order they are given in the file (top to bottom). It is the value in the field KITOPNO that determines which operation the article belongs to. Operations and articles should be loaded in individual lines, which means that each occurrence in the structure should have a separate line in the file.
Field | Required | Example | Description |
PRODUCTID | Y * | #100752 | IT-number of the article you are building a structure on. *PRODUCTID, PRODUCT or PRODUCTEXTID must be present in the file. |
PRODUCT | Y * | 17,17x1,78 Stang | PART-number of the article your are building a structure on. *PRODUCTID, PRODUCT or PRODUCTEXTID must be present in the file. |
PRODUCTEXTID | Y * | 17,17x1,78 Stang | EXTID of the article you building a structure on. *PRODUCTID, PRODUCT or PRODUCTEXTID must be present in the file. |
KITOPNO | Y | 100 | KIT operation number |
OPERATIONID | Y ** | 100155 | RamBase operation number of operation in KIT. **OPERATIONID, OPERATION or OPERATIONEXTID must be present in the file if an operation is to be added to the structure. |
OPERATION | Y ** | 2037_Ekstern tilvirkning | Operation in the structure. **OPERATIONID, OPERATION or OPERATIONEXTID must be present in the file if an operation is to be added to the structure. |
OPERATIONEXTID | Y ** | 2037_Ekstern tilvirkning | EXTID of the operation. **OPERATIONID, OPERATION or OPERATIONEXTID must be present in the file if an operation is to be added to the structure. |
PARTID | Y *** | #100647 | IT-number for the PART in the structure. ***PARTID, PART or PARTEXTID must be present in the file if an article is to be loaded in the structure. |
PART | Y *** | 12.4962B 316 | PART-number of the PART in the structure. ***PARTID, PART or PARTEXTID must be present in the file if an article is to be loaded in the structure. |
PARTEXTID | Y *** | 12.4962B 316 | EXTID of the PART in the structure. ***PARTID, PART or PARTEXTID must be present in the file if an article is to be loaded in the structure. |
RESOURCEID | Y **** | 100043 | Resource number of the resource in the structure. ****RESOURCEID, RESOURCE or RESOURCEEXTID must be present in the file if a resource is to be added to the structure. |
RESOURCE | Y **** | Resource in the structure. ****RESOURCEID, RESOURCE or RESOURCEEXTID must be present in the file if a resource is to be added to the structure. | |
RESOURCEEXTID | Y **** | EXTID of the resource in the structure. ****RESOURCEID, RESOURCE or RESOURCEEXTID must be present in the file if a resource is to be added to the structure. | |
KITQTY | 2 | Quantity of a PART. If the field is empty in the file, the value will automatically be set to "1" | |
KITTIME | 1 | Time spent during operation/resource | |
KITPRETIME | 0.5 | Time spent prior to operation/resource | |
KITPOSTTIME | 0.1 | Time spent after the operation/resource | |
REVISION | Revision of the product | ||
VERSIONNAME | Baseline | Name of this version of the product | |
VERSIONNOTE | Note to this version of the product |
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 |
EXTID | Y* | 12345 | External reference/identifier. Unique reference to a goods reception. Can be used in external systems. | |
PARTEXTID | Y* | EP1K50TC144-2 | Product name. Must exist in the article archive. PART and MFR are used to identify the correct product. | |
SSAITEMID | Y* | SSA/102716-1 | *You must provide either SSAITEMID or both EXTID and PARTEXTID to identify the Shipping Advice line the serial number should be created on. | |
SERIALNO | Y | Serial number |
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 |
|---|---|---|---|---|
NO | Y | 2380 | Budget number. | |
NAME | Y | Sales | Name of the budget. | |
DEPNO | 2040 | Department number. | ||
PRJNO | 3879 | Project number. | ||
YEAR | Y | 2020 | Budget year. | |
JAN | 10000 | Period amount for January. | ||
FEB | 10000 | Period amount for February. | ||
MAR | 10000 | Period amount for March. | ||
APR | 10000 | Period amount for April. | ||
MAY | 10000 | Period amount for May. | ||
JUN | 10000 | Period amount for June. | ||
JUL | 10000 | Period amount for July. | ||
AUG | 10000 | Period amount for August. | ||
SEP | 10000 | Period amount for September. | ||
OCT | 10000 | Period amount for October. | ||
NOV | 10000 | Period amount for November. | ||
DEC | 10000 | Period amount for December. |
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.
This load may be used to update fields for an existing account (ACC). However, it is not possible to update status with this load.
Field | Required | Length | Example | Description |
ST | 1 | 4 | 1 = Open 4 = Activated 9 = Deactivated If not provided in file, status for the account will be set to 1. | |
ACCCODE | Y | 2380 | General ledger account number. | |
ACCOUNTGROUPCODE | One character for account group code. | |||
NAME | Y | VAT settlement account | Name of account. | |
CATEGORY | Bank | Bank, Fixedasset, Receivables, Payables or ''. | ||
ISCONTROLACCOUNT | Y | Y (Yes) | ||
PARENTACCCODE | Y | Y (Yes) | ||
TEXT | Round-off | Free text. | ||
BACNO | 2910 | Reference to budget linked to this account. | ||
DEPNO | 2001 | Default Department number. | ||
ACCTYPE | Y | B | Type of Account : R = Result B = Balance | |
VATCODE | Y | 2 | 00 | Default Vatcode |
INCLDEP | N | Should postings to this Account include ref. to Department. N = No Y = Yes X = Can be used If not provided in file, INCLDEP will be set to N. | ||
INCLPRJ | N | Should postings to this Account include ref. to Project. N = No Y = Yes X = Can be used If not provided in file, INCLPRJ will be set to N. | ||
INCLAST | N | Should postings to this Account include ref. to Asset. N = No Y = Yes X = Can be used If not provided in file, INCLAST will be set to N. | ||
INCLDIM4 | N | Should postings to this Account include ref. to Dim4. N = No Y = Yes X = Can be used If not provided in file, INCLDIM4 will be set to N. | ||
INCLDIM5 | N | Should postings to this Account include ref. to Dim5. N = No Y = Yes X = Can be used If not provided in file, INCLDIM5 will be set to N. | ||
INCLDIM6 | N | Should postings to this Account include ref. to Dim6. N = No Y = Yes X = Can be used If not provided in file, INCLDIM6 will be set to N. | ||
INCLDIM7 | N | Should postings to this Account include ref. to Dim7. N = No Y = Yes X = Can be used If not provided in file, INCLDIM7 will be set to N. | ||
INCLDIM8 | N | Should postings to this Account include ref. to Dim8. N = No Y = Yes X = Can be used If not provided in file, INCLDIM8 will be set to N. | ||
INCLDIM9 | N | Should postings to this Account include ref. to Dim9. N = No Y = Yes X = Can be used If not provided in file, INCLDIM9 will be set to N. | ||
INCLDIM10 | N | Should postings to this Account include ref. to Dim10. N = No Y = Yes X = Can be used If not provided in file, INCLDIM10 will be set to N. | ||
INCLLOC | N | Should postings to this Account include ref. to Location. N = No Y = Yes X = Can be used If not provided in file, INCLLOC will be set to N. | ||
INCLICTDB | N | Should postings to this Account include ref. To InterComapnyDataBase. N = No Y = Yes X = Can be used If not provided in file, INCLICTDB will be set to N. | ||
AGIO | Y | N | Agio should be set to Y for balance accounts that should be revaluated to periodic exchange rate (rate at last day of period) as part of period closure. Agio is often used on payables, receivables and bank accounts. If not provided in file, AGIO will be set to N. Y = Yes N = No | |
FROMPERIOD | Y | 201503 | Account is legal from this period. (Format: YYYMM) | |
TOPERIOD | 201512 | Account is legal to this period. (Format: YYYYMM) | ||
MANUALGLBLOCKED | Y | Y = Yes | ||
PAYMENTBLOCKED | Y | Y = Yes | ||
SALESCREDITNOTEBLOCKED | Y | Y = Yes | ||
SALESINVOICEBLOCKED | Y | Y = Yes | ||
SALESPOSTINGADJUSTMENTBLOCKED | Y | Y = Yes | ||
SUPPLIERCREDITNOTEBLOCKED | Y | Y = Yes | ||
SUPPLIERINVOICEBLOCKED | Y | Y = Yes | ||
SUPPLIERPOSTINGADJUSTMENTBLOCKED | Y | Y = Yes | ||
OLDACCNO | OLDACCNO is only used when converting from an old chart of account to a new one. The existing Account number will be displayed in the OLDACCNO-field, and the new Account number in the ACCNO-field. If the same chart of account will be used, this field should be empty. | |||
DEBITCREDITPOSTINGTYPE | BOTH | Possible values are: DEBIT, CREDIT or BOTH (as default). |
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 |
NAME | Y | New Car Volvo AB12345 | Name of Fixed Asset | |
INVESTMENT | Y | Invoice 123000 | Reference to investment / invoice | |
INVESTMENTPERIOD | Y | 6 | YYYYMM | Period the investment was done |
ACTIVATEDPERIOD | Y | 6 | YYYYMM | Period the investment was activated |
FIRSTDEPRECIATIONPERIOD | Y | 6 | YYYYMM | First depreciation period |
LASTDEPRECIATIONPERIOD | Y | 6 | YYYYMM | Last period the depreciation was done |
AMOUNT | Y | 300000 | Investment amount | |
INVESTMENTACCOUNT | Y | 9010 | GL Account the investment / invoice was posted to | |
DEPNO | 1000 | Department number for the investment | ||
PRJNO | 2000 | Project number for the investment | ||
ASTNO | 3000 | Asset number for the investment |
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 |
NO | 100000 | Asset number | ||
NAME | Y | Machine 12A | Asset name | |
TEXT | 50 | This is just a Note | Description or Note / Free text | |
FROMPERIOD | Y | 6 | YYYYMM | First period the Asset could be used |
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 |
EXTID | Document ID from legacy (old) system. | |||
TRANS | Y | 6 | PERWAG | Transaction Type. For example: CUSCIN for sales invoices, SUPSIN for supplier invoices. When period amounts are to be loaded, the value in this field must be set to ATRMAN (manual postings to the general ledger). CUSMAN (Manual postings to account receivables). PERWAG (Import of wages). PACMAN (Manual period adjustment). SUPMAN (Manual postings to account payables). VATMAN (Manual VAT postings). |
TYPE | Y | IMPORTED | This field says how the transactions have been created. When period amounts are to be loaded, the value in this field must be set to IMPORTED. Valid options: AUTO = Automatic postings from Invoices, Credits or payments. MANUAL = Manual postings. AGIO = Agio postings. IMPORTED = Postings imported from file | |
PERIOD | Y | 201509 | Fiscal period. | |
TRDATE | Y | 2015.09.30 | Transaction Date. When period amounts are to be loaded, set this value to the last day of the month. | |
TRQTY | 369 | Transaction Quantity. Number of documents like invoices, credits of payments etc. connected to one ATR document that forms the basis of the GL entry. When period amounts are to be loaded, set this value to 0. | ||
DATE | Y | 2015.09.03 | Date of posting. When period amounts are to be loaded, set this value to the last day of the month. | |
REM | Imported wages from… | Remark (Free text). | ||
MSG | Message (Free text). | |||
ACCCODE | Y | 1210 | Account number in the General ledger. | |
DEPNO | 2040 | Department number. | ||
PRJNO | 3879 | Project number. | ||
ASTNO | 1001 | Asset number. | ||
DIM4 | 2966 | Reference to Dimension register 4. Used in addition to the dimensions Department (DEP), Project (PRJ) and Assets (AST). | ||
DIM5 | Reference to Dimension register 5 | |||
DIM6 | Reference to Dimension register 6 | |||
DIM7 | Reference to Dimension register 7 | |||
DIM8 | Reference to Dimension register 8 | |||
DIM9 | Reference to Dimension register 9 | |||
DIM10 | Reference to Dimension register 10 | |||
TEXT | Free text | |||
CUR | Y | NOK | Currency | |
RATE | Y | 1.00 | Currency exchange rate. | |
VATCODE | Y | 2 | 00 | VAT Code. |
ICTDB | Inter Company Database. Refers to a company in a corporation where there are corporate transactions. | |||
LOC | OSL | Location. | ||
AMOUNT | -4500.00 | Amount in Transaction Currency. |
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 |
EXTID | Unique ID for the transaction from the legacy (old) system. It is recommended to use the same value as in the YOURNO field. | |||
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. | ||
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. | |
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. |
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. | |
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. | ||
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. | ||
CUR | Y | 3 | NOK | Document currency. An abbreviation of three letters which corresponds to the CUR register in RamBase. |
KID | 10124001029384 | KID. Norwegian transaction code for recognition of incoming payments. | ||
RATE | Y | 42041 | 1.0000 | Exchange rate. If document is issued in local currency the exchange rate is 1. |
AMOUNT | Y | 12 | 77490.00 | Amount = Qty * Price in transaction currency. |
CAMOUNT | 12 | 77490.00 | Net amount converted to home (local) currency. | |
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 |
REGDATE | Y | 10 | YYYY.MM.DD | The registration date of the document. Format: YYYY.MM.DD |
PERIOD | Y | YYYYMM | Account/fiscal period. | |
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. | |
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. | |
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 is mandatory if KID is not included. | |
RMRFLAG | 1 | Reminder Flag: "1" - If this is set to 1, it means that reminders should not be created for this post. | ||
INTFLAG | 9 | Interest Flag: "9" - If set to 9, it means that interests should not be created for this post. | ||
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. |
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 | ||
PAYBY | CLEARING | The method of payment (MANUAL, CLEARING, EDI etc). It's also a internal rambase reference and is usually not loaded when the converted system is non-Rambase | ||
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. |
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 | ||
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. | ||
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. | |
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. |
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 |
|---|---|---|---|---|
ACCCODE | 1000 | General ledger account id. | ||
ACCOUNT | Y | 100033 | Customer id. | |
CUR | SEK | Currency. If currency is not specified, the first currency selected on the Customer (CUS) in the CUS application will be set. | ||
DEPNO | 1001 | Department id. | ||
EXTID | 99 | Unique ID for the transaction from the legacy (old) system. It is recommended to use the same value as in the YOURNO field. | ||
IT | Y | 7 | #100486 | Product id. |
NOTE | Note. | |||
OURNO | Sellers reference number. | |||
PRICE | Net price. | |||
PRJNO | 1000 | Project id. | ||
QTY | Y | Quantity. | ||
SELLER | 149 | Seller. | ||
TEXT | Default Article for Service | Product description. | ||
YOURITM | Customers item reference number. | |||
YOURNO | Customers reference number. | |||
YOURREF | Customers reference, typically a person. |
Field | Required | Length | Example | Description |
ACCOUNT | Y* | The Supplier ID assigned by Rambase. *ACCOUNT or ACCOUNTEXTID must have a value | ||
EXTID | The external ID of the supplier shipping advice. | |||
DATE | Y | 2015.05.05 | Date | |
PERIOD | 201705 | Period | ||
LOC | Y | 3 | VAT | Location |
CUR | Y | NOK | Currency | |
QTY | Y | Quantity | ||
NETQTY | Y | Net quantity. Must be equal 0 or equal quantity | ||
STOCKQTY | Y | Stock quantity | ||
PARTIT | Y** | #100000 | Internal typenumber is a unique ID that identifies the article. This will be assigned by the system when a new article is created. Format: #123456 **PARTIT, PART or PARTEXTID must have a value | |
PARTEXTID | Y** | The external ID of the product. **PART or PARTEXTID must have a value | ||
PART | Y** | 190-489-A1 | The name of the product. **PART or PARTEXTID must have a value | |
MFR | ACME | Manufacturer. Used in combination with part if there are parts with the same name but different manufacturers. | ||
PRICE | Y | 20.98 | ||
LOT | ||||
QUALITY | ||||
STOCKLOCATION1 | The placement of the goods in stock | |||
QTYSTOCKLOCATION1 | Quantity of goods in stock | |||
STOCKLOCATION2 | ||||
QTYSTOCKLOCATION2 | ||||
STOCKLOCATION3 | ||||
QTYSTOCKLOCATION3 | ||||
STOCKLOCATION4 | ||||
QTYSTOCKLOCATION4 | ||||
STOCKLOCATION5 | ||||
QTYSTOCKLOCATION5 | ||||
NOTE | ||||
ACCOUNTEXTID | Y* | The supplier external ID. *ACCOUNT or ACCOUNTEXTID must have a value | ||
DEPNO | Department Number | |||
PRJNO | Project Number |
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* | Supplier account number. The number should match the RamBase supplier number. *Either ACCOUNT or ACCOUNTEXTID must be present in the file. | ||
EXTID | BO-Fantomet | ID for the stockreference in old system. | ||
DATE | Y | YYYY.MM.DD | ||
LOC | Y | 3 | VAT | Location: A three character Warehouse Code, identifying a warehouse. |
CUR | Y | NOK | ||
QTY | Y | |||
PARTIT | Y* | Part IT. * PARTIT, PARTEXTID or PART must have a value. | ||
PARTEXTID | Y* | Product/Part ID in old system (Unique). * PARTIT, PARTEXTID or PART must have a value. | ||
PART | Y* | Servicetime | Part name. * PARTIT, PARTEXTID or PART must have a value. | |
MFR | 16 | MISC | Manufacturer. | |
PRICE | Y | |||
LOT | ||||
QUALITY | Field for Quality information on article, will be copied to Quality field on respective documents. | |||
NOTE | ||||
ACCOUNTEXTID | Y* | The supplier's unique ID from the legacy (old) system. To identify the supplier the transaction is to be connected to. *Either ACCOUNT or ACCOUNTEXTID must be present in the file. | ||
DEPNP | Department Number. | |||
PRJNO | Project Number. | |||
BESTIFUSEDBYDATE | 2020.03.30 | This is the date this product is best before, but it may also be good enough after this date. | ||
ORIGIN | 2 | NO | Two-character code (ISO 3166) identifying the default country where the product is produced. |
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* | Supplier account number. The number should match the RamBase supplier number. *Either ACCOUNT or ACCOUNTEXTID must be present in the file. | ||
EXTID | BO-Fantomet | ID for the stockreference in old system. | ||
DATE | Y | YYYY.MM.DD | ||
DOCTYPE | For example CUSOWNED. | |||
LOC | Y | 3 | VAT | Location: A three character Warehouse Code, identifying a warehouse. |
CUR | Y | NOK | ||
QTY | Y | |||
PARTIT | Y* | Part IT. * PARTIT, PARTEXTID or PART must have a value. | ||
PARTEXTID | Y* | Product/Part ID in old system (Unique). * PARTIT, PARTEXTID or PART must have a value. | ||
PART | Y* | Servicetime | Part name. * PARTIT, PARTEXTID or PART must have a value. | |
MFR | 16 | MISC | Manufacturer. | |
PRICE | Y | |||
LOT | ||||
QUALITY | Field for Quality information on article, will be copied to Quality field on respective documents. | |||
STOCKLOCATION1 | The placement of the goods in stock. | |||
QTYSTOCKLOCATION1 | Quantity of goods in stock. | |||
STOCKLOCATION2 | ||||
QTYSTOCKLOCATION2 | ||||
STOCKLOCATION3 | ||||
QTYSTOCKLOCATION3 | ||||
STOCKLOCATION4 | ||||
QTYSTOCKLOCATION4 | ||||
STOCKLOCATION5 | ||||
QTYSTOCKLOCATION5 | ||||
NOTE | ||||
ACCOUNTEXTID | Y* | The supplier's unique ID from the legacy (old) system. To identify the supplier the transaction is to be connected to. *Either ACCOUNT or ACCOUNTEXTID must be present in the file. | ||
DEPNO | Department Number | |||
PRJNO | Project Number | |||
BESTIFUSEDBYDATE | 2020.03.30 | This is the date this product is best before, but it may also be good enough after this date. | ||
ORIGIN | 2 | NO | Two-character code (ISO 3166) identifying the default country where the product is produced. | |
HEATNO | A heat number is an identification coupon number that is stamped on a material plate after it is removed from the ladle and rolled at a steel mill |
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* | Customer identifier. Has to match a customer in ST>=2 and ST<9. *ACCOUNT or ACCOUNTEXTID must have a value. (If ACCOUNTEXTID is given in the file, and ACCOUNT is not given, the program will search for customer via the EXTID field in the Customer (CUS) application). | ||
ACCOUNTEXTID | Y* | The customer external ID. *ACCOUNT or ACCOUNTEXTID must have a value. (If ACCOUNTEXTID is given in the file, and ACCOUNT is not given, the program will search for customer via the EXTID field in the Customer (CUS) application). | ||
YOURNO | Y | Sales Order Request number. | ||
QTY | Y | 10 | Ordered quantity. | |
CUR | Y | 3 | EUR | Currency. |
YOURREF | John Doe | Sales Order Request reference, typically a person. | ||
DELTERM | Delivery terms. | |||
DELTERMPLACE | A place related to DELTERM. | |||
UDF | CustomerPartnerOrderId | User defined field, main level. | ||
SHIPBY | Preferred shipping method. | |||
CARRIER | BRING | Name of transporter. | ||
SADDRID | Shipping address. | |||
SNAME | Doe | Company name, or a person's surname in the shipping address. | ||
SADDR1 | Mystery Lane 123 | First address line in the shipping address. | ||
SADDR2 | Post Box 9077 | Second address line in the shipping address. | ||
SCITY | NEDRE VATS | City/town/village in the shipping address. | ||
SPOCODE | 5578 | Postal code in the shipping address. Will be validated against the POC archive in RamBase. Illigal values will be discarded. | ||
SSTATE | TN | A US state. | ||
SHIPCC | Country code is a two-character code identifying a country. The code follows the ISO 3166 standard. Will be validated against the CON archive in RamBase. | |||
SATTN | Attention in the shipping address | |||
SPHONE | +4752763390 | Phone number for this shipping address. | ||
SEMAIL | Email address for this shipping address. | |||
PART | The product in the order. (If PARTEXTID is given in the file, the program will first try to find the product (ART) based on PARTEXTID. If ART is not found, the program will search via CUSPART from file, and by PART from file as third priority. If no product is found, the program will set product based on the Company setting (CSV) Unknown product for sales order). | |||
PARTEXTID | The external ID of the product. (If PARTEXTID is given in the file, the program will first try to find the product (ART) based on PARTEXTID. If ART is not found, the program will search via CUSPART from file, and by PART from file as third priority. If no product is found, the program will set product based on the Company setting (CSV) Unknown product for sales order). | |||
MFR | The manufacturer for the product. | |||
CUSPART | The customers part number. (If PARTEXTID is given in the file, the program will first try to find the product (ART) based on PARTEXTID. If ART is not found, the program will search via CUSPART from file, and by PART from file as third priority. If no product is found, the program will set product based on the Company setting (CSV) Unknown product for sales order). | |||
PRICE | The price of the product. | |||
REQ | 2019.10.25 | Must have the format YYYY.MM.DD or YYWW. | ||
YOURITM | The customers reference number. | |||
NOTE | Note from the customer. | |||
INTERN | Info to be set in an DMS/I00 MSG. | |||
REVISION | Requested product revision. | |||
ISBLOCKEDFORPRODUCTION | If set to 1, the order will be blocked for production. | |||
UDF1 | Prefix | User defined field, item level. |
This load will not update existing Production operations (OPR).
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 |
OPERATION | Y | Name of the Production operation (OPR). | ||
OPCLASS | Y | Production operation class. | ||
OPTIME | Y* | 1.5 | Planned run time in hours for the Production operation (OPR). 1h 30min is given as 1.5. * Either OPTIME or OPPRETIME must be specified. | |
OPPRETIME | Y* | 1.5 | Planned setup time in hours for the Production operation (OPR). 1h 30min is given as 1.5. * Either OPTIME or OPPRETIME must be specified. | |
OPPOSTTIME | 1.5 | Planned cleanup time in hours for the Production operation (OPR). 1h 30min is given as 1.5. | ||
RESEXTID | Y** | Resource (RES) id in the external system. ** Either RESOURCENO (100000) or RESEXTID must be included. | ||
RESOURCENO | Y** | 100000 | Resource (RES) id in RamBase. ** Either RESOURCENO (100000) or RESEXTID must be included. | |
EXTID | The Production operation (OPR) external system id. | |||
DESCRIPTION | Description of the Production operation (OPR). | |||
PICKINGMUSTBECOMPLETED | 1 | Set value 1, if picking must be completed. Then all parts for this and previous operations must be picked before current operation can be completed. | ||
HASCHECKPOINT | 1 | Set value 1, if the Production operation (OPR) has a checkpoint set. | ||
CHECKPOINTDESCRIPTION | Checkpoint description. | |||
CHECKSERIALNOONPARTS | 1 | Set value 1, if it require serial number before completion. Then all items in the tracelist for all product units needs to have serial number assigned. |
This load will not update existing Production resources (RESCONFIG).
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 |
NAME | Y | Name of Production resource (RESCONFIG). | ||
ST | Y | 4 | Status. Must be 1 or 4. | |
CLASS | Y | V | Production resource (RESCONFIG) class. | |
CATEGORY | Y | SINGLE | Production resource (RESCONFIG) category. Legal values are SINGLE, MEMBER or GROUP. | |
SHORTNAME | Short name of Production resource (RESCONFIG). | |||
EXTID | Production resource (RESCONFIG) external system id. | |||
NOTE | Description of the Production resource (RESCONFIG). | |||
GROUPID | Production resource (RESCONFIG) group id. | |||
ASSIGNTORESTRICTEDSTOCKLOCATIONS | 1 | Set value 1, if the Production resource (RESCONFIG) should be assigned to restricted stock locations. | ||
ALLOWGROUPING | 1 | Set value 1, to allow resource to use work order operation grouping. | ||
ALLOWMANHOURS | 1 | Set value 1, if man hours can be added to the the work log of work order operations. | ||
ALLOWMULTIOPERATOR | 1 | Set value 1, if multiple operators can work with one work order operation. | ||
HOURRATEPRE | 100 | Rate per hour for operations setup step, given in system currency. | ||
HOURRATE | 100 | Rate per hour for operations step, given in system currency. | ||
HOURRATEPOST | 100 | Rate per hour for operations post step, given in system currency. | ||
CALCULATECOSTBYPLANNEDHOURS | 1 | Set value 1 = Operation cost is calculated based on planned operation hours. Blank (Default) Operation cost is calculated by logged hours. |
Create a file in csv format
The file should have the following fields included, with the fields as header.
Field name | Description |
|---|---|
ACCOUNT | The customer identifier from RamBase, e.g.: 100123. If the customer number is given, If the customer identifier is not given, RamBase checks if it exists in the database. The job logs an error if the customer is not found or is inactive in Status 9. |
PRODUCTID | The identification of the product, e.g.: #123456 If a productid is provided it will be checked against the database to see if it exists. The job will log an error if no products are found. |
PRODUCTNAME | The name of a product, You do not have to give a product id, a product name is enough. RamBase searches the product archive with the provided name. If the product can not be found the job logs an error. |
CUSTOMERSPRODUCTNAME | The customer's name of the product, If neither product id nor product name is provided, the customer can upload the customers product name. This requires an account to be also provided. RamBase searches the product archive based on the customer's product name and the customer account. An error is logged if no match is found. |
QUANTITY | The number of products, e.g.: 10. This field is required. |
REQUESTEDDATE | The requested delivery date for the product, such as 01.01.2021. Use the formats DD.MM.YYYY, DD-MM-YYYY, YYYY.MM.DD, YYYY-MM-DD. This field is required. |
SOURCE | The source of the sales forecast: Blank or any integer number. If value = 1, it will get the description from DOV saying “From customer”.But any number can be provided if for instance the forecast is generated from a numbered algorithm. If the customer sends in blank, it will be set to 1 in the code. |
LOC | Location of the forecast, e.g.: VAT. If LOC is not provided it will be set to LOC from the COM archive. The location will be validated against the database and an error is logged if no location is found.There is also a limitations that there can not be a mix of locations in the file – only one. |
PROBABILITY | The probability, in percentage, of receiving a firm order, e.g.: 65. |
CUSTOMERSREFERENCE | The customers reference, e.g.: SPO/12345 (any string). |
CUSTOMERSREFERENCENO | The customers reference number, e.g.: SFC/112233 (any string). |
SHIPPINGADDRESSID | Refers to a specific shipping address for the customer, e.g.: If the field is given, it is validated along with the provided account. If no shipping address with this identifier is located in the provided customer account, then an error is logged. |
Example of a CSV file
ACCOUNT;PRODUCTID;PRODUCTNAME;CUSTOMERSPRODUCTNAME;QUANTITY;REQUESTEDDATE;SOURCE;LOC;PROBABILITY;CUSTOMERSREFERENCE;CUSTOMERSREFERENCENO;SHIPPINGADDRESSID101147;101904;7309 VW Frontlykter;;7;06.01.2021;1;VAT;;FCS/1301;PO/2346;1
You will get an overview of all company settings in the application Company Setting Values (CSV).
The settings are filtered by modules and sub-modules. It is also possible to search by name and key name regardless of the modules and sub-modules.
Each setting is defined by JHC personnel in accordance with your company's demands.
Click on a module in the list of modules.
Click on the relevant sub-module. The names and descriptions of the settings connected to this sub-module will then be displayed.
Required settings are marked with a star icon.
You need the permission ViewCompanySettings to be able to see this list.
There are three types of settings. Some of the settings may not be turned off, this is because the setting has a default value.
On/off setting - The only option for this setting is to turn it on or off by use of the On/off-button.
Custom input value from user - Open text field where you can set the value.
Select value from list - Select an option listed in a drop-down menu.
Note that some of the settings may have child settings. There will be a dependency between them.
You need the permission UpdateCompanySettings to be allowed to edit the company set-up.
This application gives quick overview and access to applications for configuring new and existing companies.
All actions can be started from this menu. Hover the mouse pointer over the different tiles to see a description of the options. Some are linked directly to applications while others are menus.
The Domain values (DOV) application can be used to make local configurations of value lists, for specific databases or systems. Some value lists allow adding custom values, while others are restricted to activating or deactivating predefined values.
Choose the item line containing the value list you want to edit and press ENTER.
Here you are able to activate and deactivate the different values for the given value lists using the confirmation icons to the left of the status number.
The Value column contains the value (key) saved on the document, and needs to be a unique value.
The Prio column shows the priority sorting of the values, where the lowest number indicates higher priority.
Notice that most of the value lists are set up per system. If a value needs to be restricted to specific databases, this is done in the Restrict to be available for selected DB's column to the right. If a value is deactivated (using Deactivate, Disable for system or Delete (only available in ST:1)), it will not be available for any databases in the system. A value needs to be in ST:4 to be active.
The QAR classification application is used to create a classification tree. The application is available from the Domain Values (DOV) menu.
This application is used to set up the value lists for the QAR classification - Category, Type and SubType in a tree structure. You can only add SubTypes for the Categories 10, 11, 20, 21 and 30.
Note that the setup is performed per company. The company you are working in while opening the application will be the company the QAR will apply for.
A new company, or a company without local customization, will start with the default setup. To change this, click the Make local changes for company button.
Specify value and description for Category. Value and description is the same field for Type and SubType. The field to the right of the columns specifies the priority/sorting of the values when shown the dropdowns (in the QAR screen).
Note: If you need to delete a category, you will first have to delete all the Tpes for the given category. This also applies for Type and SubType.
Name and address
Currency (CUR)
Language - Will be used on print, email and reports. If another language is registrated on a Customer (CUS) or a Supplier (SUP), this will overwrite the information from Company. If no language is set on Company, Customer og Supplier - english is used as default
Enterprise - The format is different from country to country. In Norway we create the Enterprise number without 'NO' in the front and 'MVA' at the end, - example: 111 222 333
Vatno - The format is different from country to country. In Norway we create the Vatno with MVA at the end since this is a claim that it shows on documents. In Sweden there is always 'SE' in the front of the Vatno, and '01' at the end. All EU contries have their Countrycode (CCODE) in front of the Vatno, - example: DK 222 333 444
Location (LOC) - This is the main location for the Company. This will be used as default Location on documents, - if not another location is set on Personell (PER), then this location will overwrite the location set in Company. This Location must be created in the Location (LOC) archive
Phone - example: +47 11 22 33 44
Email - example: post@company.no
Url - example: www.company.no
ConfirmSend - Will automatically be filled with Email
CommonDBG - Will automatically be filled with a shortening of the Group the Company belongs to - example: ABC
GroupDBG - Will automatically be filled with a shortening of the Company - example: BCD
ADMDBG and ADMAliasDB - should not be filled
OwnerDB - Should be filled with the same shortening as the Company has - example: BCD-NO (NO is the CountryCode)
FinanceSys - If the Company shall use the finance module in Rambase, this field has to be filled with 'RB'. Admittance to update this field is given by ROLE/System Consultant - Finance
GmModel (Gross Margin model) - Stock and unrealized Stock are calculated based on historical value (exchange rate when the Goods Reception Item (SSA-ITM) was registered in stock) or at current value (current price) or at invoice rate value (rate on SIN is posted back on SSA meaning value on SSA item is changed according to the rate on the SIN item).
Gm (Gross Margin) - the Company will not sell below this percent of profit. If they will sell with lover profit, is has to be approved by dedicated Personell
Period - Must be filled with the earliest period the Company will load data into Rambase. If the Company wil not load data, the period can be set from January same year, or the same month the Company is set up
ClosedPeriod - Will be automatically updated with the latest period that is closed in the Period Account Register (PAR)
Interest % - Interest percent that is used when interest-invoices to customers are created from the Interest Menu (INT). If the percent is changed from CSV/Customer Interest invoice Percent, the Interest field in Company is updated (and vice versa)
CmCreditNo, Membership and TvinnNo - Should not be filled
Unit - Units that the Company will use have to be created in the UNI (Unit) archive before it can be added in Company. A unit for 'pcs' must always be created, and this unit must be added in this field in Company
F12 Scheduled Batchjobs for company - When the set up is done in a new Company, data is loaded and reconciled, - Batchjobs can be activated by using this F12 option
Use the Approval configuration (APC) application to configure approval rules and their approvers. In the Approval Rules area, the menu has a treelist, showing one line for each approval type on main level. It is possible to expand and see the approval rules as children of the corresponding approval type. The detail view in the Approval rule area, shows details of the approval rule and the Approver assignments area shows a list of its approvers.
It is possible to both add and edit approval rules from the APC application.
An approval type must have at least one approval rule to be active. Most approval types will only have one approval rule, but the Amount limit types will typically have more than one approval rule with for example intervals of amount ranges where different persons can approve.
The list of approvers for the approval rule will have possibility of adding and removing approvers. Approvers can be both employees and roles.
Some approval types support restrictions and limits. These will be configured in separate applications, via links in the APC application.
Enter the Approval configuration (APC) application.
Highlight an approval type.
Click the Add approval rule button.
Make sure the correct item is selected in the Item field.
Set the name of the approval rule in the Name field.
Click the OK button to create an approval rule in status 1.
Click the Manage restrictions button in the Approval rule area.
Select restriction type in the - Select restriction type field.
Click the plus icon and set a value if required.
In the Approver assignments area, click the Add user or Add role button.
Find user or role and click the OK button to add the user or role as an approver, for the selected approval rule.
Click the Activate approval rule in the context menu to activate it and set in status 4.
Click the Manage restrictions button in the Approval rule area to edit restrictions. The application APRCOND will open.
The applications show the restrictions that can be configured for the selected approval type. The restrictions define when the approvers assigned to this approval rule are allowed to approve this approval type. Restrictions can be set by different fields, and the different fields allow different restriction types. To add a restriction, select restriction type for the field, and press the plus icon. Assign a value if required.
Some approval rules might have restrictions that are not supported by this new approval configuration. If so, a link will show, and this will open a popup to show these restrictions.
For approval types that supports configuring limits, the menu option Configure limits will show in the context menu. This will open the APCLIMIT application. An amount limit can be assigned. Some of today's configurations have conditions. These will show in the condition column.
It is possible to add roles as approvers. It will still be a single personnel (PER) that is selected when requesting approval. You select the role you want to select users from, and the active user assignments from that role are listed for selection.
It is now possible to select a person for each approval rule that should be default approver. The default approver will be on top of the list of approvers to be selected, when requesting approval. It is also intended for approval requests done by a server, for example, when a document is imported to RamBase and requires approval. The approval request will then be automatically sent to the default approver by the server.
For an approval type to be active, there needs to exist an approval rule for the approval type in status 4. The approval type must also not be disabled by the company setting. The approval type status is displayed in the Status column in the Approval Rules area.
Approval rule not configured - Approval type is enabled, but no approval rule has been added.
Approval rule(s) pending registration - One or more approval rule exists, and one or more has status 1.
Approval type disabled for company - Company setting for disabling the approval type has been activated.
Active - One or more approval rule exists in status 4, none have status 1. But some could have status 9.
For an approval rule to be active, it must have status 4. The approval type must also not be disabled by the company setting.
Pending registration - The approval rule has status 1.
Active - Approval rule has status 4.
Discontinued - Approval rule has status 9.
When an approval rule is selected, the following context menu options can be available depending on the status of the approval rule:
Configure limits - Only available for some approval types. Opens the APCLIMIT application for configuring limits.
Activate approval rule - Approval rule is set to status 4. Only available in status 1.
Delete approval rule - Removes the approval rule. The approval rule will no longer show in the application. Only available in status 1.
Discontinue approval rule - Approval rule is set to status 9. Only available in status 4.
Copy approval rule - Copies the approval rule to a new approval rule. Restrictions are included, but the approvers are not copied by default. When selecting the menu option, a popup will show with possibility to enter name of the new approval rule. There is an option to copy the approvers.
Edit setting for disabling approval type - Most approval types have the possibility for disabling/enabling for company by a company setting. Most are by default enabled. This menu option opens the company settings (CSV) application for configuring setting for current approval type.
By default, all users will receive approval notifications. It is possible to turn this off in the Personnel (PER) application:
No IMS when requested for approval - Specifying that the user should not receive an IMS notification, when the user is requested to do an approval.
No IMS when request approved - Specifying that the user should not receive an IMS notification, when a document the user owns have approval requests approved by other persons.
