fig1 depicts a system 100 including a processor 105 and a server 190 , which are coupled by a network 150 . the processor 105 further includes a user interface 110 . server 190 further includes a code list provider 160 ( labeled practical code list provider ) and a code list buffer 162 . the processor 105 may be implemented as any processor capable of executing an application , such as user interface 110 , and the like . for example , the processor 105 may include at least one processor , such as a central processing unit , and at least one memory ( which may include code and / or data ). examples of processor 105 include a computer , a computing device , a tablet computer , a mobile wireless device , a blade server , or any other suitable processing device . the user interface 110 may be implemented as any type of interface that enables interaction with aspects of system 100 , including server 190 , code list provider 160 , and code list buffer 162 . for example , user interface 110 may be implemented as a web browser ( which may include one or more plug - ins ), a client application , a thin client , and any other interface mechanism . the network 150 may be any type of wired and / or wireless mechanism and may include , alone or in any suitable combination , the internet , a telephony - based network , a local area network ( lan ), a wide area network ( wan ), a dedicated intranets , wireless lan , an intranet , a public land mobile network , a wireless network , a bus , and / or any other communication path . the server 190 may include at least one processor and at least one memory ( which may include code and / or data ). the at least one memory may be implemented as any type of storage mechanism including random access memory , read only memory , flash memory , and / or any other mechanism for storing data . the server 190 may be implemented as one or more of the following : a computing device , a computer , a processor , a blade server , or any other suitable processing device . the server 190 may execute one or more applications , such as code list provider 160 . code list provider 160 may generate a code list ( e . g ., a list of code ) and provide the code list to a user interface , such as user interface 110 . moreover , the code list provider 160 may provide the code list as part of a value help function at user interface 110 . for example , a user may move an indicator over an element of user interface 110 , and value help may present , either autonomously or when selected ( e . g ., selecting f4 ), a code list as value help for that element of user interface 110 . the code list buffer 162 may provide code list information to enable the code list provider 160 to provide value help including the code list . in some implementations , the code list buffer 162 stores the code list ( s ) in a database and / or table . furthermore , the stored code lists may be buffered in memory , such as readily accessible random access memory , dynamic ram , and the like , rather than store the code list in slower , longer - term , persistent storage , such as a hard drive and the like . in some implementations , the stored code lists are stored using tables specific to a client ( e . g ., a tenant ) and in tables that are common to a plurality of clients . fig2 a depicts an example implementation of a page presented at user interface 110 . specifically , fig2 a depicts an indicator 210 pointing at an input element 215 , and value help including a code list 220 being presented . the code list 220 includes a code header , code values , and code description . the code header refers to a description of the type of code . the code values refer to code values of the code lists and contexts in the code type table . the code description refers to a general description of the code . examples of the code header , code value , and code description are provided below with respect to fig5 . to further illustrate the code header , code values , and code description , suppose there is a “ document status code ,” which can have the values 1 , 2 , and 3 with the semantics of 1 being equated to new , 2 being equated to released , and 3 being equated to obsolete . then , the code header would include a code type value to represent these codes . for example , a code type 42 may be configured to correspond to a code value table having 3 entries for this code type : 42 1 ; 42 2 ; and 42 3 . the semantics for these 3 entries are as follows : 42 1 “ document status code new ;” 42 2 “ document status code — released ;” and 42 3 “ document status code — obsolete .” the code descriptions may be language dependent and implemented as follows : 42 1 en new ; 42 1 de neu ; 42 2 en released ; 42 2 de freigegeben ; 42 3 en obsolete ; and 42 3 de obsolete , wherein “ en ” corresponds to english and “ de ” corresponds to german . in some implementations , a duplicate , second set of tables ( which have similar semantics ) may be used to add an additional key column to allow client - specific codes or code variations . referring again to fig2 a , code 1 and / or code 2 may be selected by the user ( e . g ., a developer ) to enable the user to use the selected code at input element 215 . for example , the user may be configuring a system , such as a database , application , enterprise resource planning system , and the like . in this example , the user may be customizing the configuration of the system by selecting one or more pieces of data or code , such as with code 1 and / or code 2 . thus , the code list 220 is provided to the user when completing that task . for example , the above - noted example for code type 42 may be implemented as a drop down box to allow a user to select the status of a document . fig2 b depicts another example of a code list in a drop down box 298 including code - based help for the sales phase . fig3 depicts a system 300 for providing a code list as part of , for example , value help function . the system 300 is similar to system 100 in some respects but includes a content reader 315 , which provides direct access to most of the code list information stored in buffer 162 and , for the content not stored in buffer 162 , accesses so - called “ inactive ” storage 360 which includes the code lists information not stored in buffer 162 . when an operation at the user interface causes a request for value help to be sent from the user interface 110 to the code list provider 160 , the code list provider 160 forwards the request to a content reader 315 . the content reader 315 reads the request for a code list and then determines whether the request corresponds to code list information stored in buffer 162 or code list information which is determined from business configuration data , such as business objects . for example , the content reader 315 may read a flag in the request indicating that the code list information is stored in buffer 162 , the content reader 315 may include information , such as for example , a table , indicating what code list information is stored in buffer 162 . if stored in buffer 162 , the content reader 315 accesses buffer 162 via a data access class 340 . the buffer 162 includes the code list store as described above with respect to fig1 . in some implementations , the data access is performed during runtime . moreover , the buffer 162 may , in some implementations , keep the code list in memory , such as random access memory ( ram ), dynamic ram , flash memory , rather than in persistent storage , such as disk - based drives . furthermore , the system 300 may be implemented to include about at least 70 % of the code list information likely to be used and separated by type in buffer 162 . although the system 300 may also be implemented to include about at least 80 %, 85 %, and / or 90 % of the code list information likely to be used and separated by type in buffer 162 . in some implementations , storing in buffer 162 at least about 70 %, 80 %, 85 %, and / or 90 % of the code list information likely to be used at user interface 110 enhances the performance ( e . g ., access times , responsiveness , etc .) of system 300 , when compared to storing all of the code list information in buffer 162 ( although system 300 may instead be implemented with 100 % of the code list information stored in buffer 162 ). if content reader 315 determines that the request for a code list corresponds to business configuration data , such as business objects , the content reader 315 may access a buffer 310 to retrieve such data which is ready for use ( e . g ., pre - configured business objects , pre - delivered business objects , etc .). the content reader 315 then retrieves the code list information from the data contained in the business objects retrieved from buffer 310 . however , if the buffer 310 does not have the data required by content reader 315 , the content reader 315 may access a transport infrastructure 320 to search for the business configuration data , such as for example business objects . the transport infrastructure 320 may access a dispatcher 325 which forms a request for the business configuration data , such as business objects , and then dispatches the request to a data access class for inactive content 335 . the data access class for inactive content 335 then retrieves the business configuration data , such as business objects , from an inactive store , which may be implemented as a persistent storage , such as for example a disk - drive and the like . the retrieved business configuration data , such as business objects , may be provided to content reader 315 , which may extract the code list information from business configuration data , such as business objects . the content reader 315 may then provide the code list information to code list provider 160 and user interface 110 for presentation in a code list . in some implementations , inactive store 360 may also include code which may take up a large amount of memory , such as code lists that are too long , code lists having a long key value , and / or and code lists having a long description . fig4 depicts a process 400 for providing value help including a code list . at 405 , a value help request is received for a code list . for example , code list provider 160 may receive a request for value help including a code list ( also referred to herein as “ code list value help ”). the request may be received as a message indicating which of the plurality of elements at user interface requires the code list value help . for example , a first element at the user interface may have a first code list value help , and a second element at the user interface may have a second code list value help . consequently , the request includes an indication of whether the value help is for the first element or the second element . at 410 , a determination is made whether to access cache for the code list information . for example , content reader 315 may determine whether to directly access code list information stored in cache , such as buffer 162 which may store most of the code list information . the content reader 315 may determine that the code list information need for the request received at 405 is not stored in cache , such as buffer 162 , but instead stored in inactive store 360 . for example , the code list information may be contained in business configuration information , such as business objects , in which case the code list information is obtained from inactive store 360 . when the code list information is accessible from cache , such as buffer 162 , the cache is accessed , at 415 , to obtain the code list value help . for example , the content reader 315 may access runtime data access class for active content 340 and cache , such as buffer 162 , to obtain the code list information . as noted , the buffer 162 may be implemented in memory to enable rapid retrieval of code list information , when compared to retrieval from other mechanisms , such as persistent storage . at 420 , the code list is provided to a user interface , so that the code list is presented as value help at the user interface . for example , the content reader 315 provides the code list information ( including the code list ) to the code list provider 160 , which in turn sends the code list to user interface 110 , where the code list is presented as value help for an element of the user interface 110 as depicted at fig2 a - b . when the code list information is not accessible from buffer 162 , secondary storage mechanisms may be accessed at 425 . for example , the content reader 315 may access a first secondary store , such as buffer 310 , to retrieve data which may include pre - configured business objects , pre - delivered business objects , and the like . the content reader 315 may then retrieve the code list information from the data contained in the business objects retrieved from buffer 310 , but if the buffer 310 does not have the data required by content reader 315 , the content reader 315 may access a transport infrastructure 320 to search for the business objects . the transport infrastructure 320 may access a dispatcher 325 which forms a request for the business objects . the dispatcher 325 sends the request to a data access class for inactive content 335 , which retrieves the business objects , from another secondary storage mechanism , such as inactive store 360 . at 430 , the code list information obtained from secondary storage is provided to a user interface , so that the code list is presented as value help at the user interface . for example , the business objects obtained from secondary storage , such as inactive store 360 , may be provided to content reader 315 , which may extract the code list information from business configuration data , such as business objects . the content reader 315 may then provide the code list information to code list provider 160 and user interface 110 for presentation in a code list . the secondary store , such as inactive store 360 , may also provide code lists that are relatively large and thus take up a relatively large amount of memory ( such as code that is too long , code list having a long key value , and code lists having a long description ). fig5 depicts an example implementation of the code list information stored by type in buffer 162 . specifically , the code list information is stored in tables based on code type 510 a . the code_type table 510 a may include a list of all supported code types and code lists . the key to table 510 a may be an internal , short name of the code list , and the table 510 a may be buffered in memory at code list buffer 162 . the excluded flag indicates if a code is to be excluded from the code list value help mechanism of buffer 162 , although the default is typically to include the code in the code list value help mechanisms described herein . in some implementations , the code list provider 160 may include a mechanism for programmatically adding or deleting code from the code list at code list buffer 162 . for example , if the tables in buffer 162 become full , or approach a threshold , a code may be excluded using the exclude flag at table 510 a from the code list stored at buffer 162 . in this example , the excluded code may be stored in secondary storage , such as inactive store 360 . the code value table 510 b includes all code values of all code lists and contexts in the code type table . the table 510 b may be buffered at 162 with one or more key fields . the disabled field ( which is included in table 510 b ) indicates that a code value is disabled ( e . g ., the code value may be still be used for presentation and query purposes but not enabled for entry at the user interface for a new task or document ). to illustrate by an example , suppose it is germany in the year 1990 and the local currency is the “ deutsche mark ” but in 2010 , the local currency is the euro . in this example , the respective code values are dem and eur . however , suppose an old invoice from 1990 is presented at a user interface , the currency code will be dem and its description would be in the system to enable presentation and query of the dem currency but the dem currency is not to be entered in 2010 as a new value for any new tasks / documents . the code description table 510 c includes descriptions of some , if not all , of the code values . the table 510 may be buffered at 162 with one or more key fields ( e . g ., three key fields ). the code description table 510 c contains the disabled field to avoid retrieval of that field from the value table 510 b . the code description table 510 c also includes a language field , which is the first key field . using the language field as a key field may be realized as the language filed is very stable during a user session , and the language filed does not typically change among users ( e . g ., most users will log in to a given system using a common language ). hence , the language field was placed before the key list to ensure that the language field will be subject to the buffer 162 . in some implementations , the tables 510 a - c are replicated with an additional key field for tenant specific settings . tenant specific settings are specific to a given client or user while common settings are shared among most , if not all , tenants of a system . for example , tenant code header tables may have the form of table 512 a , tenant code value tables may have the form of table 512 b , and tenant code description tables may have the form of table 518 c . for example , code list provider 160 may lookup whether the extension code type table 512 a at buffer 162 includes an entry for a desired code for a code list . if so , the tenant specific tables are accessed , otherwise the generic tables 510 a - c are accessed to find the desired code . in some implementations , the extensibility of code lists may be controlled using a switch table framework . this approach would include a lookup to determine whether a corresponding switch for a code is active and then using the “ active ” information to determine where to retrieve the codes . for example , active code list information may be retrieved from buffer 162 , while inactive code may be retrieved from inactive store 360 . the code list data may be replicated from a persistent repository into memory at code list buffer 162 . if there are any changes to the underlying code list information , the changes may be replicated to buffer 162 . thus , any changes to the data are replicate when a change is made ( e . g ., upgrades , transports , deployment , etc ). for example , the transport infrastructure may include a code list replicator 370 , which may track underlying code list information caused by a change . in some implementations , the code list replicator 370 detects whether code lists are not suitable for replication and excludes them from replication . for example , a code list having too many entries or too much content ( which exceeds a predefined limit in buffer 162 ) might be excluded from replication into the buffer 162 . if a code list was previously replicated and then requires exclusion , the code list provider 160 may delete the obsolete code list entries in buffer 162 . in some implementations , tenant specific tables and common tables ( which are independent of any given client ) are selected during replication by code list replicator 370 in accordance with the switches noted above . for example , a client dependent view , t1 , is generated , such as table 1 below , by way of a client independent table , t2 , containing all code values , such as table 2 below and a client dependent table , switch table , ts , may contain the active switches per client , such as table 3 below . these tables are used to determine whether a code value is provided in a given client , such as client 001 . in the examples of tables t1 , t2 , and ts , switch a is active only for client 003 . thus , client 001 and client 002 would be provided with code 1 and code 2 , and client 003 would be provided with code 1 , 2 , and 3 . the switch table , ts , enables client specific filtering . referring again to the above example using the code type 42 , suppose a customer wants to include an additional code , the codes would be as depicted at table 4 . the new tenant specific code , 42 4 “ document status code — ready for review ,” is not be visible to other tenants ( or customers ), so a tenant specific extension is used to isolate the client specific code , 42 4 , to a given client . the use of a switch table , such as table 3 , may also save memory when compared to replicating the codes at each client table . various implementations of the subject matter described herein may be realized in digital electronic circuitry , integrated circuitry , specially designed asics ( application specific integrated circuits ), computer hardware , firmware , software , and / or combinations thereof . these various implementations may include implementation in one or more computer programs that are executable and / or interpretable on a programmable system including at least one programmable processor , which may be special or general purpose , coupled to receive data and instructions from , and to transmit data and instructions to , a storage system , at least one input device , and at least one output device . these computer programs ( also known as programs , software , software applications , or code ) include machine instructions for a programmable processor , and may be implemented in a high - level procedural and / or object - oriented programming language , and / or in assembly / machine language . as used herein , the term “ machine - readable medium ” refers to any computer program product , apparatus and / or device ( e . g ., magnetic discs , optical disks , memory , programmable logic devices ( plds )) used to provide machine instructions and / or data to a programmable processor , including a machine - readable medium that receives machine instructions . to provide for interaction with a user , the subject matter described herein may be implemented on a computer having a display device ( e . g ., a crt ( cathode ray tube ) or lcd ( liquid crystal display ) monitor ) for displaying information to the user and a keyboard and a pointing device ( e . g ., a mouse or a trackball ) by which the user may provide input to the computer . other kinds of devices may be used to provide for interaction with a user as well ; for example , feedback provided to the user may be any form of sensory feedback ( e . g ., visual feedback , auditory feedback , or tactile feedback ); and input from the user may be received in any form , including acoustic , speech , or tactile input . the subject matter described herein may be implemented in a computing system that includes a back - end component ( e . g ., as a data server ), or that includes a middleware component ( e . g ., an application server ), or that includes a front - end component ( e . g ., a client computer having a graphical user interface or a web browser through which a user may interact with an implementation of the subject matter described herein ), or any combination of such back - end , middleware , or front - end components . the components of the system may be interconnected by any form or medium of digital data communication ( e . g ., a communication network ). examples of communication networks include a local area network (“ lan ”), a wide area network (“ wan ”), and the internet . although a few variations have been described in detail above , other modifications are possible . for example , while the descriptions of specific implementations of the current subject matter discuss analytic applications , the current subject matter is applicable to other types of software and data services access as well . furthermore , the phrases “ based on ” and “ based on at least ” are used interchangeably herein as both phrases are equivalent . moreover , although the above description refers to specific products , other products may be used as well . in addition , the logic flows depicted in the accompanying figures and described herein do not require the particular order shown , or sequential order , to achieve desirable results . other embodiments may be within the scope of the following claims .