Material on Outline Agreements

Hi all,
Is there any tutorial available on sales outline agreements?
Please respond.
Best Regards,
AI.

Hi
Check thse links
http://homepages.wmich.edu/~c3chadde/project_3.html
http://www.sapdb.info/scheduling-agreement/
http://www.sapdb.info/wp-content/uploads/2008/12/scheduling-agreement-procedure.pdf
regards
Edited by: rithvika on May 21, 2009 2:19 PM

Similar Messages

  • SPRO config field for Material Master & Outline agreement Contracts

    Dear Gurus,
    I want the Field AUTO PO should be mandatory field - for creating New materials - Can you please suggest me in SPRO configuration?
    For outline Agreement ( contracts) - i want to make the Plant field as mandatiry - Can you please suggest me in SPRO configuration?
    Please advice
    Regards
    RS

    Hi,
    Transaction MEKB is for maintaining Condition records, in you PRD server ask concerned to maintain condition record using MEKB for contract and its line item.
    Procedure is
    1. Input in the intial screen is Purchase org, Contract number and relevant line item number and execute
    2. In the following screen highlight the line item and click on create (F6) button in the tool bar (First one from left)
    3. In the following screen inside grid maintain price in amount column agains the condition type
    If you have done the above steps then AUTO should work
    Check on it as eill:-
    Re: pr mandatory for po
    Re: Auto PO in ME59N
    pherasath

  • How to reflect variable price in outline agreement

    We procure many very complex tools that have options which significantly affect the price of that tool.  We would like to be able to reflect those price differences in the outline agreement by option within the following boundary conditions.
    1. Do not want to create a new material master for each option
    2. Do not want to utilize BOM
    3. We are buying the tool so sales order solutions won't work for us
    I have looked at configurable materials where I set up characteristics to reflect the options but I have not been able to figure out a way to price those individual options.  I do see how I could create multiple line items on the outline agreement for the same material and put unique combinations of the option characteristics in individual lines but that means I have to create a line item per option combination permutation which is much more painful than simply pricing individual options.  I also haven't seen any way to get SAP to select the correct line item based on these characteristics when doing source selection on the PR or PO.   I have started looking at variant pricing but that is completely new to me and I am not sure if that is going to go in the direction I want.  My fear is that this just allows me to price a combination of characteristics vs. pricing individual characteristics then combining the prices at the time of purchase (no different that having to create an OA line item per option combination permutation).  My apologies in advance for the convoluted message but it is difficult to ask about solutions when you are not sure what functionality potentially exists.
    Thanks,
    Ben

    Hi
    Try to check with variant Configuraqtion may be upto some extent helpful
    Check the link
    http://help.sap.com/saphelp_erp2004/helpdata/EN/92/58d455417011d189ec0000e81ddfac/frameset.htm

  • Outline Agreements - min order qty and regular vendor flag

    As a part of E Source Integration with ECC we are planning to leverageusing Outline Agreement(Contract Type MK) to store
    Price and other Business Terms for Material / Vendor combinations. Currently we are
    using Purchase Information Record with minimum order quantity and
    regular vendor flag functionalities, and these are maintained manually.
    We intend to use Minimum Order qty and Regular Vendor Flag
    indicator in Outline Agreement as well, however noticed that these fields are
    not available in the screens. Does anyone know if these fields can be enabled in an outline agreement?

    Guys
    thanks for reply..
    But I thnik my question was not fully clear as the aswers didn't make sense to me...
    As a logistics consultant .I know that I can maintain Min Order qty for a material + vendor at PIR level..
    My question ..if I buy 10 items in a PO from a sinle vendor..is there any option to restrict Min qrder qty for these combination of materials..
    or in other words vendor says he dont care about number of items ,but the lot lot should be min..10 cartons only..
    appropriate points will be rewarded.
    thanks in advance.

  • Outline agreement or automatic schedule from scheduling agreement

    Hello Master's,
    Plz find the below workflow which will brief u abt the complete process;-
    1.User raises indent(me51n) and then releases(me54n) else as per our MRP, indent/PR gets generated automatically.
    2. Standard Practice is that we invite offers, negotiate and place order (me21n) else f we have rate contract for any item we go for direct ordering (me21n) and then get it released (me29n)
    For around 20-30k material codes we have rate contract finalized with various suppliers for a period of time.
    When we find any indent/pr falling into this category, we dont invite offer but go for ordering as per the finalized price. The price is maintained in excel or pdf format.
    Problem is we want to map material codes with vendor and rates associated with the contract.
    For this either we have to go for outline agreement(me31k) of scheduling agreement(me31l) so that whenever any indent/PR gets generated in this category, order/delivery schedule will be generated automatically in SAP.
    Points in which i need help from you:-
    1. How to generate automatic po from outline agreement or automatic schedule from scheduling agreement.
    2. complete understanding of the difference between outline agreement and scheduling agreement.

    Hi Nilson,
    The data contained within the global outline agreement is distributed as purchasing contracts or scheduling agreements to the backend systems of the release-authorized purchasing organizations of the relevant corporate group. These purchasing organizations can then use the purchasing contracts or scheduling agreements according to the terms agreed centrally within the global outline agreement.
    For more details.
    http://help.sap.com/saphelp_srm50/helpdata/en/42/f93dfd975f3ee6e10000000a1553f7/frameset.htm
    Nishant

  • Problems in Global Outline Agreement

    Hi friends,
                          We are using SRM 5.0 and R/3 4.7.I want to replicate contract to SRM 5.0 to R/3. For that I have to configure Global Outline Agreement. After creating and distributing GOA i am facing 2 errors. I got those errors from Transaction RZ20 -> SAP Enterprise Buyer Monitors - > Contract Management.
    Errors are
    Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution     
    Date - 21.06.2008     Time - 14:37:45     
    System - SRD     
    Context - Business to Business Procurement (500)     
    Object Name - Contract Management     
    Short Name - Contract Distribution     
    Status - ACTIVE     
    Value - 3     
    Severity - 50          
    Status Set by - BBP     
    Status Set on - 21.06.2008     
    Status Set at - 09:07:45     
    Msg Class - SAP-T100     
    Msg Id - 000     
    Alert Text - Different processing times defined for BLAORD and CONDA          
    Var1 - 5600000014     
    Var2 - K77CLNT801       (backend Logical System)
    Var3 - 0000000000000000     
    Var4 - 5600000014K77CLNT8010000000003          01
    Node name - SRD\Business to Business Procurement (500)\...\Contract Management\Contract Distribution     
    Date 21.06.2008     
    14:37:45     
    System - SRD     
    Context - Business to Business Procurement (500)     
    Object Name - Contract Management     
    Short Name - Contract Distribution     
    Status - ACTIVE     
    Value - 3     
    Severity - 50          
    Status Set by - BBP     
    Status Set on - 21.06.2008     
    Status Set at - 09:07:45     
    Msg Class - SAP-T100     
    Msg Id - BBP_ADMIN 028     
    Alert Text - Application error in backend system K77CLNT801 (SRM outline agreement 5600000014)     
    Var1 - K77CLNT801      (backend Logical System)
    Var2 - 5600000014     
    Var3 - 0000000000000000     
    Var4 - 5600000014K77CLNT8010000000003          01
    I have done replication process of Purchase order from SRM to R/3.It is working fine.
    I have done this configuration for GOA.
    1.     Define GCTR transaction type in SRM.
    2.     Define internal number range in SRM for the GOA that is the same as the external number range in the back end system for GCTR.
    3.     Implement the badi BBP_CTR_BE_CREATE.
    4.     Store, Plant, Material, Material group has been replicated from R/3.
    I am getting those mentioned system message from Header Data -> Status 
    System Status
    Complete
    Created
    Released
    Distribution Incorrect
    Document Completed
    I am not using any conditions in item level.
    How can I configure IDocs BLAREL for SRM and MM? I donu2019t have any idea?
    Please help me to correct error .
    Thanks in advance.

    Hello,
    check out notes 1053985 and 646903, that should solve your problem (especially the sections Mapping master data and Customizing data of note 646903).
    Regards,
    Andreas

  • Outline Agreement of FS Contarcts

    Dear experts,
    I'm struggling to try to understand how CRM Outline Agreements works.
    Basically I can see that the standard solution privides two kinds of OA:
    1. Promo Agreement: trans type DP, item categ DPI
    2. Master Agreement: trans type MA, item categ MAF.
    II succeeded in understand Promo Agreement, with which I can add third party subvention going to automatically add a Third Party Relationship on the FS contract, according to the access sequences defined in customizing.
    Regarding Master Agreement, I already noticed that the determination on contract is customized differently in of respect DP, but is not such a problem.
    I'm facing great difficulties in managing price agreements, payment structure and in reporting the results on the FS contract.
    Do anyone has a "Best practice documentation" on how to manage and customize an Outline Agreement MA?
    - Price agreements: It often gives errors (i.e.: when you try to maintain condition records pricing agreement the condition record is disappears from display during creation.).
    I currently assigned a cond function group to the item category MAF to which is assigned a condition type with an access sequence containing the following accesses:
    10     SAP00090
    20     SAP00099
    30     SAP00089
    - Payment structure: I cannot insert flow categories in the payment structure of the OA item because the system gives the following error:
    tem 1000: Payt struc.: You must enter a flow category before the first program run
    Diagnosis
    You have not entered a flow category for a step in the payment structure. You must enter a flow category before the first program run, otherwise you must change the flow category later. However, you are not then permitted to change the flow category group.
    Procedure
    Delete this row and insert a new row in the payment structure. Enter a flow category before the first program run.
    When I create an FS Contract and the OA is determined in it, I cannot see any result such as, for example, the price agreement.
    Do anyone knows how the outline agreement MA affects the FS contract?
    Do anyone knows how to insert the payment structure on the outline agreement's item?
    Thanks and regards
    Dario

    Hello,
    Item category 'W' in a contract is not meant for automatic creation of a purchase order. It does not have a net price, where do you expect the system to pick this price from? Tax code only comes in later. Your error also talks about that.
    The material group contracts can be used to keep track of orders so that they do not exceed a value limit.
    In case, you do not know the material at the time of contract/ or have many similar type of materials use item category 'M' Material instead. In this you can specify price as well as tax code and use for auto POs.
    Item Category/Account Assgt. Category in Contracts - Purchasing (MM-PUR) - SAP Library

  • Delivery date for outline agreement requisition

    Hi all,
    When I create a purchase requisition (ME51N) for a non stock material, for example, using req type NB or FO, the delivery date defaults to the current date. If I create a req with the same information but using type RV (outline agreement) the delivery date defaults to blank. I found out that in the IMG, under the req doc type config, the type RV is associated with the "Control indicator for purchasing document type" = R (Purchase requisition for outline agreement). If I clear this field, the delivery date starts defaulting to the current date. I created 2 reqs side by side (one with the indicator "R" and the other without) and I did not find any difference except for the delivery date. Does anyone know what the impact is to clear field V_T161-BSAKZ for doc type RV?
    Thanks.

    Hi
    The control indicator "R" determines Filed selection. ie Which requires mandatory or optional. For Doc types RV field selection groups is RVB , in that Delivery date is not a Required/optional/Dsiplay field., this works in conjunction with control indicator "R".
    Hence when you try to create with Doc type RV and control indiactor "R" it is not propsoding the current date. When you remove Control indicator "R" the field selcetion groups becomes NBB , in that Delviery date is Required filed, so the system proposes the current date .
    The impact of removal of control indicator "R" is nothing.
    Regards
    DRN
    Give points if ok

  • To change the text of outline-agreement

    Hi Experts,
    Im using BAPI_CONTRACT_CHANGE function module to change outline agreement.When im executing this im getting the dump.Will you explain me how to use this fm to change the item text of outline-agreement.Will you please give the list of mandatory fields for this function-module.

    IMPORTING
    *"     VALUE(PURCHASINGDOCUMENT) TYPE  BAPIMEOUTHEADER-NUMBER
    *"     VALUE(HEADER) TYPE  BAPIMEOUTHEADER OPTIONAL
    *"     VALUE(HEADERX) TYPE  BAPIMEOUTHEADERX OPTIONAL
    *"     VALUE(VENDOR_ADDRESS) TYPE  BAPIMEOUTADDRVENDOR OPTIONAL
    *"     VALUE(TESTRUN) TYPE  BAPIFLAG-BAPIFLAG OPTIONAL
    *"     VALUE(TECHNICAL_DATA) TYPE  BAPIMEOUTTECH OPTIONAL
    *"  EXPORTING
    *"     VALUE(EXP_HEADER) TYPE  BAPIMEOUTHEADER
    *"  TABLES
    *"      ITEM STRUCTURE  BAPIMEOUTITEM OPTIONAL
    *"      ITEMX STRUCTURE  BAPIMEOUTITEMX OPTIONAL
    *"      ACCOUNT STRUCTURE  BAPIMEOUTACCOUNT OPTIONAL
    *"      ACCOUNTPROFITSEGMENT STRUCTURE  BAPIMEOUTPROFITSEGMENT OPTIONAL
    *"      ACCOUNTX STRUCTURE  BAPIMEOUTACCOUNTX OPTIONAL
    *"      DELIVERY_ADDRESS STRUCTURE  BAPIMEOUTADDRDELIVERY OPTIONAL
    *"      ITEM_COND_VALIDITY STRUCTURE  BAPIMEOUTVALIDITY OPTIONAL
    *"      ITEM_COND_VALIDITYX STRUCTURE  BAPIMEOUTVALIDITYX OPTIONAL
    *"      ITEM_CONDITION STRUCTURE  BAPIMEOUTCONDITION OPTIONAL
    *"      ITEM_CONDITIONX STRUCTURE  BAPIMEOUTCONDITIONX OPTIONAL
    *"      ITEM_COND_SCALE_VALUE STRUCTURE  BAPIMEOUTITEMSCALEVAL OPTIONAL
    *"      ITEM_COND_SCALE_QUAN STRUCTURE  BAPIMEOUTITEMSCALEQUAN OPTIONAL
    *"      ITEM_TEXT STRUCTURE  BAPIMEOUTITEMTEXT OPTIONAL
    *"      HEADER_TEXT STRUCTURE  BAPIMEOUTTEXT OPTIONAL
    *"      HEAD_COND_VALIDITY STRUCTURE  BAPIMEOUTHEADVALIDITY OPTIONAL
    *"      HEAD_COND_VALIDITYX STRUCTURE  BAPIMEOUTHEADVALIDITYX OPTIONAL
    *"      HEAD_CONDITION STRUCTURE  BAPIMEOUTHEADERCOND OPTIONAL
    *"      HEAD_CONDITIONX STRUCTURE  BAPIMEOUTHEADERCONDX OPTIONAL
    *"      HEAD_COND_SCALE_VAL STRUCTURE  BAPIMEOUTSCALEVALUE OPTIONAL
    *"      HEAD_COND_SCALE_QUAN STRUCTURE  BAPIMEOUTSCALE OPTIONAL
    *"      PARTNER STRUCTURE  BAPIMEOUTPARTNER OPTIONAL
    *"      PARTNERX STRUCTURE  BAPIMEOUTPARTNERX OPTIONAL
    *"      RELEASE_DOCU STRUCTURE  BAPIMEOUTRELEASEINFO OPTIONAL
    *"      EXTENSIONIN STRUCTURE  BAPIPAREX OPTIONAL
    *"      EXTENSIONOUT STRUCTURE  BAPIPAREX OPTIONAL
    *"      RETURN STRUCTURE  BAPIRET2 OPTIONAL
    FU BAPI_CONTRACT_CHANGE
    Short Text
    BAPI to Change a Purchase Contract
    Functionality
    BAPI for changing a purchase contract.
    Notes
    Master conditions
    When creating outline agreements, you can specify only one period per variable key. This means that just one period can be specified for the document header (i.e. condition table A019). The same applies to each item (i.e. condition table A016) and to each item/plant combination (i.e. condition table A068).
    You can use any periods. However they must not overlap for a variable key.
    When conditions are changed, new condition records are nevertheless written.
    Because volume rebate conditions are not taken into account in outline agreements, they are not processed.
    No subitems (e.g. inclusive/exclusive bonus quantities, display, etc.) are taken into account.
    The control key for quality management in procurement (EKPO-SSQSS) and the certificate category (EKPO-ZGTYP) are only taken into account to a certain extent. These two items of information are copied from the reference contract or material master, but cannot be changed; neither are any checks carried out for these two fields.
    The revision level (EKPO-REVLV) cannot be changed because various quality management routines were not implemented.
    Version management (Document Change Management) is not supported.
    External services (planned or unplanned) are not supported.
    The creation or changing of configurations is not supported.
    Further information
    When a purchase contract is changed (activity 02), the following authorization objects are checked:
    M_RAHM_BSA Document type in contract
    M_RAHM_EKG Purchasing group in contract
    M_RAHM_EKO Purchasing organization in contract
    M_RAHM_WRK Plant in contract
    Parameters
    PURCHASINGDOCUMENT
    HEADER
    HEADERX
    VENDOR_ADDRESS
    TESTRUN
    TECHNICAL_DATA
    EXP_HEADER
    ITEM
    ITEMX
    ACCOUNT
    ACCOUNTPROFITSEGMENT
    ACCOUNTX
    DELIVERY_ADDRESS
    ITEM_COND_VALIDITY
    ITEM_COND_VALIDITYX
    ITEM_CONDITION
    ITEM_CONDITIONX
    ITEM_COND_SCALE_VALUE
    ITEM_COND_SCALE_QUAN
    ITEM_TEXT
    HEADER_TEXT
    HEAD_COND_VALIDITY
    HEAD_COND_VALIDITYX
    HEAD_CONDITION
    HEAD_CONDITIONX
    HEAD_COND_SCALE_VAL
    HEAD_COND_SCALE_QUAN
    PARTNER
    PARTNERX
    RELEASE_DOCU
    EXTENSIONIN
    EXTENSIONOUT
    RETURN
    Exceptions
    Function Group
    <b>rewards point for helpful answer.</b>

  • Outline agreement with different item prices

    Hi,
    I have some outline agreements with different prices. The prices is based on the quantity purchased on the period of the contract:
    Example: for the first 100000 items the price is 4u20AC, beetwen 100001 and 200000 it is 3,9u20AC and after it is 3,85u20AC.
    1st purchase order 50000pc, price 4u20AC*50000 = 2000000u20AC
    2nd purchase order 60000pc, price 500004u20AC + 100003,9u20AC = 239000u20AC
    how to do this for one division and for several division (the contract can be used by all the divisions)?
    Thanks for your help.

    Hi,
    Do either quantity contract or value contract and maintain scales in that for your requirement. Whenever you raise purchase order with respect to contract, it will take the value according to the quantity you maintained in the scales.
    or
    Maintain info record for that material,plant,vendor combination. In that, maintain scales according to your requirement. Then whenever you raise purchase order with reference to that contract, according to that scales maintained in info record, it will take the value.
    Regards,
    Prasath

  • Issue with outline agreement

    Hi all,
    I need to find the outline agreement price for a material. I have retrieved that material from ekpo based on bstyp = k (contract) and displaying the price.
    But for some materials the price i see in ekpo differs from that i see on me33k for the same contract and same item
    The reason for this bacause of validity periods
    i have 2 validity periods
    01/01/2007   04/30/2007
    05/01/2007   12/31/9999
    The contract iam looking at has a creation date of 04/25/2007 and the price is $200 but since  the sy-datum falls under second interval it shows me a price of $202 but the ekpo stores $200 . Can anyone tell me how to retrieve the latest price i.e $202- This is Gross price Condition PB00
    Thanks
    Venki

    Hi
    Any thoughts
    Thanks
    Venki

  • Automatic po from outline agreement

    Eventhough i have maintained outline agreement against material codes, as well as checked auto po and source in material master and auto po in vendor master, and the PR is even release. while running me59n it says, message no.ME261 ( No suitable purchase requisitions found).
    P.s: Even the source determination in the PR has been checked.

    Please check if the PR is subjected to any release strategy, if yes - check if it is released or not.
    If released then check the Source of supply tab in the PR, is it assigned with the outline agreement or not.
    If yes then the check if you manually enter the PR all the details are pulled into the PO or not and correct based on the error.
    If no error then pass it thorugh ME59N and recheck.

  • Difference B/w Framework & Outline Agreement

    Hi Gurus
    I am new to SAP MM, can anyone please tell me the difference b/w framework orders and outline orders/ agreement.
    General examples of this regard will be very helpful.
    Regards
    Imran

    Dear,
    A Frame work order is :
    Purchasing document used for the procurement of materials or external services. Instead of stipulating a specific delivery date, this type of purchase order has an extended validity period. Goods or services can be supplied or performed against it over this period without the need for any further written instruction to be issued by the buying entity.
    Framework orders are defined with document type FO. They are used in accelerated procurement processes in connection with preventive maintenance (servicing) plans or invoicing plans, and for blanket purchase orders (purchase orders with specified limits).
    A framework order covers multiple procurement transactions over a longer period in cases where the administrative costs of processing discrete POs would be disproportionately high.
    An Outline agreement is :
    Outline agreement also referred as Contract in SAP.
    Outline Agreement can be of 2 types:- Contract and SA. 
    Contract is where you have a contract with the vendor,may be a for a predetermined quantity or predefined value. So everytime you need the material,  you need to make PO ref the contract asking for the delivery of the material. In such instance when PO is ref with contract its called contract release orders or call off orders. 
    Scheduling agreement is a long term purchase agreement, where you will keep issuing the delivery schedules whenever there is a change in requirement or at predetermined time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will contain different zones viz. firm/tradeoff/Forecast.  Firm zone schedules are confirmed requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the raw materails and ordering party is liable to pay raw material cost, in case of requirement cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
    SA is also an agreement with the vendor for the supply of matl, may be a quanity or value. The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.So you can maintain the delivery schedule and communicate the vendor on Forecase basis or JIT basis. And when you need some more matl then will only create SA deliveries using ME38. SA could be of 2 types:- without release documentation-system will transmit the delivery info to the vendor once you save the document. 
    With release documentation- after creating the delivery schedules you need to create SA release using ME84.
    The main difference between contract and SA is volume of docs generated would be higher in contract since everytime you need to make a PO ref the contract and its time consuming, whereas SA can be integrated with MRP such that it automatically creates delivery schedules during MRP run provided if there is a requirement to the matl. 
    Regards,
    Syed Hussain.

  • Global outline agreement and Delivery schedule

    Hi experts.
    I am in SRM 5.5, ECC 5.0 as backend in ECS.
    I would like to have some information about relation between Global outline agreement and Delivery schedule of ECC.
    Can I create GOAs and replicate to ECC as Delivery schedule for automatic generation of schedule lines?
    The schedule lines generated afted MRP run goes to SRM or only goes to SUS if required?
    Thanks
    Nilson

    Hi Nilson,
    The data contained within the global outline agreement is distributed as purchasing contracts or scheduling agreements to the backend systems of the release-authorized purchasing organizations of the relevant corporate group. These purchasing organizations can then use the purchasing contracts or scheduling agreements according to the terms agreed centrally within the global outline agreement.
    For more details.
    http://help.sap.com/saphelp_srm50/helpdata/en/42/f93dfd975f3ee6e10000000a1553f7/frameset.htm
    Nishant

  • Function Module for outline agreement

    Dear Sir,
    I want to know the function module for contract/outline agreement from where I can fetch the details of release orders against the given contract.
    Regards
    Amit Agarwal

    Hi
    Go to SE37 enter the Outline agreement and press F4
    you can see the function module
    (or) Post the same message in  SAP ABAP forum
    G.Ganesh Kumar

Maybe you are looking for

  • Web Template Tech Comparison (including fastm)

    1. Preface In the Java Web Application, the Page Generation Part may be the most tedious and painful part. All other layers can be well structured. Only the Page Generation Part is mixed and bad structured. This article first introduces and compares

  • Windows XP Media Center Edition does not suport ipod nano...need programs

    I was just informed by Apple Service that Windows XP Media Center does not support ipod nano, but that there are online programs available that would allow me to use my ipod with Windows XP Media Center. Does anyone know of these porgrams?? If so, co

  • Adding Metadata to folders/ Searching Drive for Keywords not just one folder -  Bridge CC 2014

    Hello Adobe world, I'm trying to add Metadata to folders not the files. The files in the folders already have metadata and in one folder we have 360 images of the same thing. When I do a keyword search I don't want to go though 20+ sets of 360 duplic

  • Getting warning when trying to hide/show subforms

    hi, i have a pdf form with several subforms on it. I made the hide/show form option with the click event of some buttons. It worked fine. I then tried to do the same using the initialize method for the form. form1.page1.Subform1.presence = "hidden";

  • VDS didn't start: Could not load JDBC driver

    Hello, I want to start the VDS Tutorial, but I get an error: Exception: Data source 'Derby database' failed. Check your CLASSPATH! (in Tools -> Options) Could not load JDBC driver 'org.apache.derby.jdbc.EmbeddedDriver' Shutting down... Data source 'D