Importing Attachments for Master Agreements in CLM

I am attempting to load contract files (.doc/PDF) using the import tool and I am having issues.  What needs to be populated in the 'Attachment Order Code' field in the load file.
Can someone outline the steps to load an existing contract created outside of CLM to a master agreement?
I am using E-Sourcing 5.1/CLM 2.0.
Thanks in Advance,
Kyle

Jeff,
It does make sense to me what you are trying but it does not make sense in the logic of SAP Sourcing.  You don't want the suppliers to see the button to not confuse them but in the logic if you activate it on one side the possibility you are sharing a document is real so it should be visible on both sides or you will have confusion on the buyer side if someone chooses internal and external view while the supplier doesn't see even the attachment section.
On the buyer side the default is internal only so if this is not changed by the master agreement owner on the buyer side the attachment section will always be empty for the supplier causing no unnecessary confusion.
There is no way at present to hide this only on the supplier side as far as I see it.
Regards,
Erik

Similar Messages

  • Overiding Mandatory Fields for master Agreement Template

    Hello,
    In the standard creation of the master agreement template the CONTACT field is mandatory. To me, this does not make sense because a template would need to be created for every contact/supplier.  We want to make the CONTACT field optional for master agreement templates.  I am trying to create a page customization with the following properties to accomplish this:
    UI ID:contracts.contract.ui.buyside.default
    Name:Master AgreementParent
    Class: Master Agreement
    Field ID: Contact
    Property: required
    Value: no
    Dimension on parent set
    Dimension Field :  IS_TEMPLATE
    Dimension Field Type: Boolean
    Dimension Value: yes
    I can not seem to make it work.  Any suggestions?  Is this even possible?
    Thanks in advance,
    Kyle

    Thanks for the quick reply.  I was hoping to avoid a dummy vendor.  This is sure a strange piece of software.
    Kyle

  • Workflow for Master Agreement (Publish to ERP)

    What is the best practice for approval workflow before publishing a master agreement from eSource to ECC?
    In the interest in keeping the source-of-truth within a single application we do not want to keep approval workflow of Outline Agreements in ECC as it is currently when moving the creation of the master agreement functionality to eSource.  There is no inherent workflow functionality for master agreements in eSource.  Are there customizations and/or best practices for having workflow of master agreements such that the Publish to ERP would not be possible until approval has been done within the eSource application?

    Hi,
    As you rightly said, Work flow support is not available in MA and more specifically before sending it to ERP
    Here are some options you may want to consider:
    - Try to use ACL/Security rights to control who can publish to ERP. For instance only the "document owner" can publish and the document owners are responsible. You can put a message or ask the publisher to enter some values on extension fields on who all approved this document.
    - Try using approval functionality in ERP if that works. that may be the simplest..
    The following options require heavy customization & scripting:
    Leverage workflow support from other docs
    - Tie an User defined business document (UDO that supports workflow) with MA. Provide a custom action, which will create a UDO biz doc instance and trigger a workflow behind the scenes.  MA will have a reference to UDO and vice versa. Users will approve the UDO.  In your Pre Publish to ERP script check for the approval conditions of UDO and work with that.
    - if MA is created from Projects try using project workflow for the business process..
    Good luck!
    Thanks, Baski

  • Attachments Toolbar for Master Agreements

    On the sell side, when suppliers log on, we are trying to hide the Attachments toobar (button) when they are in Master Agreements. In Toolbar Customization I can Hide the toolbar but it does it on both the buy and the sell sides and we want to keep it available for the buy side. Has anyone wver come accross this issue and has a solution ?

    Jeff,
    It does make sense to me what you are trying but it does not make sense in the logic of SAP Sourcing.  You don't want the suppliers to see the button to not confuse them but in the logic if you activate it on one side the possibility you are sharing a document is real so it should be visible on both sides or you will have confusion on the buyer side if someone chooses internal and external view while the supplier doesn't see even the attachment section.
    On the buyer side the default is internal only so if this is not changed by the master agreement owner on the buyer side the attachment section will always be empty for the supplier causing no unnecessary confusion.
    There is no way at present to hide this only on the supplier side as far as I see it.
    Regards,
    Erik

  • Disabling the default search when searching for master Agreements

    Hello Experts
    I am relatively new to SAP e sourcing ,we are working on 5.1 system.
    We have a query , Contract management->Agreements->Search master agreements and Sub agreements.
    This query takes a lot of time for execution.
    When user selects this option , it runs this query and then displays a screen with all the filters and search results at the bottom.
    I want to ensure that this query is not run by default, so that when user selects this option , the page only displays the selection criteria , users can specify the filter values and hit on search.
    Can anyone please help me on how can we disable the default execution of query everytime "Search master agreements and Sub agreements " is selected from the dropdown.
    is there any option within the query itself or do we need any script for doing this.
    Regards
    Vikas

    Hello Vikas,
    This should be the general approach.
    1) Write a new query that has the functionality you desire. In your case you can duplicate the existing query and make one of the filters mandatory. This will ensure that the query does not get executed by default. Save this new query in the system.
    2) Identify the corresponding query group. In your case it is FCI-ContractBuyList.
    3) In this query group, find the entry for 'Search Master Agreements and Agreements' query and check 'Remove Query from Selection List'.
    4)Add your new query in this query group and check the 'Include in SRM Navigation' checkbox. Click Save.
    Let us know if this works.
    Thanks
    Devesh

  • INSPECTIONPLAN_CREATE  (Specify a valid data import mode for master inspec)

    BAPI_INSPECTIONPLAN_CREATE this is the bapi where i am updating INSPECTION LPAN ,,,i am getting this error if i update it with (MSTR_CHAR )master inspection char or else it is updating. Is there any key field to be given? Even i tried passing C,L, but its not working... Can any one help me for this,,

    If you try this it will work,,,but here i have the import mode as 'N'.
         LOOP  AT lt_insp_char_temp INTO wa_insp_char_temp.
          wa_insp_char-inspchar          =  wa_insp_char_temp-merknr.
          wa_insp_char-mstr_char        =  wa_insp_char_temp-verwmerkm.
          IF wa_insp_char-mstr_char IS NOT INITIAL.
            wa_insp_char-cha_master_import_modus = 'N'.
          ENDIF.
          READ TABLE lt_qpmk  INTO wa_qpmk WITH KEY mkmnr = wa_insp_char_temp-verwmerkm.
          IF sy-subrc = 0.
            MOVE wa_qpmk-steuerkz TO wa_qmkst.
            wa_insp_char-quantitative_ind                 = wa_qmkst-quantitat.
            wa_insp_char-meas_value_confirm_ind  = wa_qmkst-messwerte.
            wa_insp_char-attribute_required_ind       = wa_qmkst-pruefkat.
            wa_insp_char-up_tol_lmt_ind                   = wa_qmkst-toleroben.
            wa_insp_char-lw_tol_lmt_ind                   = wa_qmkst-tolerunten.
            wa_insp_char-scope_ind                         = wa_qmkst-pumfkz.
            wa_insp_char-result_recording_type      = wa_qmkst-estukz.
            wa_insp_char-docu_requ                        = wa_qmkst-dokukz.
            wa_insp_char-confirmation_category     = wa_qmkst-rzwang.
            wa_insp_char-sampling_procedure_ind  = wa_qmkst-stichpr.
            wa_insp_char-qscore_and_share_relevant = wa_qmkst-ausslos.
            wa_insp_char-defect_no_confirmation    = wa_qmkst-bewfhlzhl.
            wa_insp_char-target_val_check_ind       = wa_qmkst-sollpruef.
            wa_insp_char-long_term_insp_ind          = wa_qmkst-lzeitkz.
            wa_insp_char-add_sample_quantity       = wa_qmkst-addpro.
            wa_insp_char-destructive_insp_ind        = wa_qmkst-zerstprf.
          ENDIF.
          wa_insp_char-pmstr_char            = wa_insp_char_temp-qpmk_werks.
          wa_insp_char-activity                   = wa_insp_char_temp-inspec_opr_no.
          wa_insp_char-char_descr            = wa_insp_char_temp-kurztext.
          wa_insp_char-smpl_procedure     = wa_insp_char_temp-stichprver.
          wa_insp_char-smpl_unit                = wa_insp_char_temp-probemgeh.
          wa_insp_char-smpl_quant            = wa_insp_char_temp-bmsch.
          wa_insp_char-spc_criterion_key  = wa_insp_char_temp-spckrit.
          wa_insp_char-dec_places            = wa_insp_char_temp-stellen.
          wa_insp_char-lw_tol_lmt              = wa_insp_char_temp-toleranzun.
          wa_insp_char-up_tol_lmt              = wa_insp_char_temp-toleranzob.
          wa_insp_char-meas_unit              = wa_insp_char_temp-masseinhsw.
          wa_insp_char-sel_set1                = wa_insp_char_temp-auswmgwrk1.
          wa_insp_char-psel_set1              = wa_insp_char_temp-qpmk_werks.
          wa_insp_char-infofield1               = wa_insp_char_temp-dummy10.
          wa_insp_char-pmethod                = wa_insp_char_temp-qpmk_werks.
          IF wa_insp_char_temp-spckrit IS NOT INITIAL AND
             wa_insp_char_temp-stichprver IS NOT INITIAL.
            wa_insp_char-spc_ind  = 'X'.
          ENDIF.
          APPEND wa_insp_char TO lt_insp_char.
          CLEAR:wa_insp_char.
        ENDLOOP.

  • Master Agreement Import Failed

    Hi experts,
    An error was encountered during Data Import of Master Agreement in CLM system.  Logs shown below.  
    Details of the errors:
    Failed: object 1: metadata exception
    Exception: method not found
    MessageId: exception.common.db.metadata.reflection
    Info: target method = getObjectId [STANDARD_ATTRIBUTE_ID].
    found in fpa logs:
    metadata exception, Exception: method not found, AttributeId: SAPPORG_OBJECT_ID, MessageId: exception.common.db.metadata.reflection
    When checking in Setup --> Extension Definition List --> Master Agreement Extensions, SAPPORG is existing in the Attributes tab
    Regards,
    Lester

    Hi Lester,
    In setup>extension defnition, you can define different extensions for an object type (e.g. MA) for different contexts. In case of MA, you can define different set of extensions in enterpirse context and in subcontext(s).
    e.g. for enterprise context you can have EXT1 for MA
          for subcontext1 you can have EXT2 for MA
          for subcontext2 you can have EXT3 for MA
    When a user logs-in he will be associated with a context based on his company. Say with subcontext 2. In that case the user can see only extension EXT2.
    I was suspecting extensions are defined in a different context than from the user is importing... Please check.
    1. Check 1: user used for importing, the associated company & determine the respective context
    2. go to setup>ext def and look for this MA under this context and see the extension.
    Thanks,
    Baski

  • Transfering Between CLM Master Agreement Folder Types

    Hello,
    How do I transfer a CLM master agreement to another CLM master agreement folder type?  For example, an existing CLM Legal master agreement will need to be transferred to a CLM HR master agreement (using the new HR master agreement type numbering table).
    Thanks,
    Adrian

    Hi Adrian,
    If I understand your requirement correct, you would like to convert Master Agreement created from Legal Master Agreement type to a new HR Master Agreement.
    CLM does not allow to change the Master Agreement Type i.e. the Document type, once the MA is created.
    You will need to create a new MA using the HR Master Agreement type, if it has been already defined/configured in the MA Types.
    I hope this helps.
    Regards,
    Parankush

  • What is the XML format for Sub Agreements?

    Hi,
    We have requirement to automate loading Master Agreements and Sub Agreements into CLM from a non-SAP system. 
    Currently the data is loaded using CSV files, but Double Byte Char. is not supported in CSV file format.
    I am trying to load using XML format and have be successful to load  Master Agreement.
    I need help with Sub Agreement XML Structure or a better alternative to load Sub Agreement metadata containing Double Byte Char. 
    Provided below is the Sub Agreement XML Structure. Please provide suggestions or guidance on this issue.
    We are on 7.0 SP8 .
    Thanks
    Sai

    Hi Prasad,
    Thanks for your quick response.
    I am able to load successfully Project and Master Agreement in XML format with metadata containing multibyte char.
    Multibyte char is displayed on Project and Master Agreement Screen.
    English , German, Chinese, Japanese, Korean, Spanish, French and Italian language packs are installed in Sourcing.
    I am getting below error while importing XML for Sub Agreement.
    Record 1. Warning: XML import could not process field: CONTRACT_UNIQUE_DOC_NAME
    Facility=local4;sessionid=bR6bHsKNs_s_sA8ihHdOSyOASPCvRgEP3icA_SAP;tenantid=#ebay#;username=sguntaka;exception=java.lang.IllegalArgumentException: unsupported null bind parameter no. 0 found in statement SELECT OBJECTID, CONTEXTID, REVISION_COUNT, UNIQUE_DOC_NAME, DISPLAY_NAME, COLLN_METADATA, RESERVATION_LOCK, DOCUMENT_DESCRIPTION, CREATED_BY_USER_OBJECT_ID, CREATED_BY_USER_CLASS_ID, CREATED_BY_USER_OBJECT_NAME, MODIFIED_BY_USER_OBJECT_ID, MODIFIED_BY_USER_CLASS_ID, MODIFIED_BY_USER_OBJECT_NAME, EDIT_BY_USER_OBJECT_ID, EDIT_BY_USER_CLASS_ID, EDIT_BY_USER_OBJECT_NAME, CREATED_AT, MODIFIED_AT, EDIT_AT_DATETIME, INACTIVE, TRACK_CHANGES, COLLABORATION_POLICY, HAS_PUBLIC_DISC, IS_TEMPLATE, CANCELED_BY_USER_OBJECT_ID, CANCELED_BY_USER_CLASS_ID, CANCELED_BY_USER_OBJECT_NAME, DOC_OWNER_USER_OBJECT_ID, DOC_OWNER_USER_CLASS_ID, DOC_OWNER_USER_OBJECT_NAME, CLOSED_BY_USER_OBJECT_ID, CLOSED_BY_USER_CLASS_ID, CLOSED_BY_USER_OBJECT_NAME, CANCELED_AT, CLOSED_AT, TEMPLATE_OBJECT_ID, TEMPLATE_CLASS_ID, TEMPLATE_OBJECT_NAME, DOC_TYPE_OBJECT_ID, DOC_TYPE_CLASS_ID, DOC_TYPE_OBJECT_NAME, BASE_DATE_DATE, SCHEDULE_WORK_DAYS, BUSINESS_UNIT_OBJECT_ID, BUSINESS_UNIT_CLASS_ID, BUSINESS_UNIT_OBJECT_NAME, COMPANY_OBJECT_ID, COMPANY_CLASS_ID, COMPANY_OBJECT_NAME, ESTIMATED_CURRENCY, ESTIMATED_OBJECT_ID, ESTIMATED_PRICE, BUDGETED_CURRENCY, BUDGETED_OBJECT_ID, BUDGETED_PRICE, CURRENCY_OBJECT_ID, CURRENCY_CLASS_ID, CURRENCY_OBJECT_NAME, VENDOR_VISIBLE, DATE_TO_PUBLISH_DATE, LOCK_BASELINE, LI_PERIOD_TYPE_OBJECT_ID, LI_PERIOD_TYPE_CLASS_ID, LI_PERIOD_TYPE_OBJECT_NAME, CALC_METHOD, SPEC_ID_COUNT, ATTR_ID_COUNT, FORMULA_ID_COUNT, PURCHASING_ORG_OBJECT_ID, PURCHASING_ORG_CLASS_ID, PURCHASING_ORG_OBJECT_NAME, PURCHASING_GRP_OBJECT_ID, PURCHASING_GRP_CLASS_ID, PURCHASING_GRP_OBJECT_NAME, TRANSACTION_TYPE_OBJECT_ID, TRANSACTION_TYPE_CLASS_ID, TRANSACTION_TYPE_OBJECT_NAME, COMPANY_CODE_OBJECT_ID, COMPANY_CODE_CLASS_ID, COMPANY_CODE_OBJECT_NAME, INTEGRATED_TYPE, USE_ERP_VALIDATION, STORAGE_LOCATION, RECORD_SERIES, RETENTION_DATE_DATE, RETENTION_REMINDER_DATE_DATE, RETENTION_EVENT_OBJECT_ID, RETENTION_EVENT_CLASS_ID, RETENTION_EVENT_OBJECT_NAME, EFFECTIVE_DATE_DATE, EXPIRATION_DATE_DATE, TERMIN_NOTICE_LEAD_TIME, TERMIN_COMMU_DATE, PERPETUAL_TERM, AUTO_RENEWAL, EVENT_OBJECT_ID, EVENT_CLASS_ID, EVENT_OBJECT_NAME, RENEWAL_REMINDER_DATE, VENDOR_OBJECT_ID, VENDOR_CLASS_ID, VENDOR_OBJECT_NAME, CONTACT_OBJECT_ID, CONTACT_CLASS_ID, CONTACT_OBJECT_NAME, LOCATION_OBJECT_ID, LOCATION_CLASS_ID, LOCATION_OBJECT_NAME, PAYTERMS_OBJECT_ID, PAYTERMS_CLASS_ID, PAYTERMS_OBJECT_NAME, REPLENISHMENT_OBJECT_ID, REPLENISHMENT_CLASS_ID, REPLENISHMENT_OBJECT_NAME, VENDOR_ACCT_NUM, INT_CAT_OBJECT_ID, INT_CAT_CLASS_ID, INT_CAT_OBJECT_NAME, EXT_CAT_OBJECT_ID, EXT_CAT_CLASS_ID, EXT_CAT_OBJECT_NAME, EVALUATION_CRITERIA, NEXT_AUDIT_DATE, LAST_AUDIT_DATE, TOTAL_EXPECTED_CURRENCY, TOTAL_EXPECTED_OBJECT_ID, TOTAL_EXPECTED_PRICE, TOTAL_BUDGETED_CURRENCY, TOTAL_BUDGETED_OBJECT_ID, TOTAL_BUDGETED_PRICE, TOTAL_ACTUAL_CURRENCY, TOTAL_ACTUAL_OBJECT_ID, TOTAL_ACTUAL_PRICE, TOTAL_SAVINGS_CURRENCY, TOTAL_SAVINGS_OBJECT_ID, TOTAL_SAVINGS_PRICE, TOTAL_COST_SAVINGS_CURRENCY, TOTAL_COST_SAVINGS_OBJECT_ID, TOTAL_COST_SAVINGS_PRICE, TOTAL_COST_AVOIDANCE_CURRENCY, TOTAL_COST_AVOIDANCE_OBJECT_ID, TOTAL_COST_AVOIDANCE_PRICE, PERF_EVAL_CRITERIA, PERF_LAST_UPDATE_DATE, PERF_NEXT_UPDATE_DATE, BUYER_SEARCHABLE, VAL_PERIOD_TYPE_OBJECT_ID, VAL_PERIOD_TYPE_CLASS_ID, VAL_PERIOD_TYPE_OBJECT_NAME, INCLUDE_PART_NUMBER, TOTAL_ACTUAL_SPEND_CURRENCY, TOTAL_ACTUAL_SPEND_OBJECT_ID, TOTAL_ACTUAL_SPEND_PRICE, FORECAST_SPEND_CURRENCY, FORECAST_SPEND_OBJECT_ID, FORECAST_SPEND_PRICE, ACTUAL_LIMIT_PCT, FORECAST_LIMIT_PCT, LINEITEM_ID_CNT, LIMIT_VALUE_CURRENCY, LIMIT_VALUE_OBJECT_ID, LIMIT_VALUE_PRICE, MINIMUM_VALUE_CURRENCY, MINIMUM_VALUE_OBJECT_ID, MINIMUM_VALUE_PRICE, MINIMUM_DAYS_OFFSET, MARGIN_PRICING, DELETED_AT_DATETIME, DELETED_BY_OBJECT_ID, DELETED_BY_CLASS_ID, DELETED_BY_OBJECT_NAME, CTR_IS_DUET, HAS_DUET_ITEMS, WORD_ATTRIBUTES_TEXT_PREVIEW, WORD_ATTRIBUTES_TEXT_OBJECT_ID, WORD_ATTRIBUTES_TEXT_CLASS_ID, WORD_ATTRIBUTES_CHECKSUM, SENT_TO_ERP_DATETIME, STATUS_OBJECT_ID, STATUS_CLASS_ID, STATUS_OBJECT_NAME, LAST_SPEND_IMPORT_DATE, BUYER_SPECS_SUPPORT, VENDOR_SPECS_SUPPORT FROM clmuser.FCI_CONTRACT WHERE UNIQUE_DOC_NAME = ? AND CONTEXTID = ?;stacktrace=java.lang.IllegalArgumentException: unsupported null bind parameter no. 0 found in statement SELECT OBJECTID, CONTEXTID, REVISION_COUNT, UNIQUE_DOC_NAME, DISPLAY_NAME, COLLN_METADATA, RESERVATION_LOCK, DOCUMENT_DESCRIPTION, CREATED_BY_USER_OBJECT_ID, CREATED_BY_USER_CLASS_ID, CREATED_BY_USER_OBJECT_NAME, MODIFIED_BY_USER_OBJECT_ID, MODIFIED_BY_USER_CLASS_ID, MODIFIED_BY_USER_OBJECT_NAME, EDIT_BY_USER_OBJECT_ID, EDIT_BY_USER_CLASS_ID, EDIT_BY_USER_OBJECT_NAME, CREATED_AT, MODIFIED_AT, EDIT_AT_DATETIME, INACTIVE, TRACK_CHANGES, COLLABORATION_POLICY, HAS_PUBLIC_DISC, IS_TEMPLATE, CANCELED_BY_USER_OBJECT_ID, CANCELED_BY_USER_CLASS_ID, CANCELED_BY_USER_OBJECT_NAME, DOC_OWNER_USER_OBJECT_ID, DOC_OWNER_USER_CLASS_ID, DOC_OWNER_USER_OBJECT_NAME, CLOSED_BY_USER_OBJECT_ID, CLOSED_BY_USER_CLASS_ID, CLOSED_BY_USER_OBJECT_NAME, CANCELED_AT, CLOSED_AT, TEMPLATE_OBJECT_ID, TEMPLATE_CLASS_ID, TEMPLATE_OBJECT_NAME, DOC_TYPE_OBJECT_ID, DOC_TYPE_CLASS_ID, DOC_TYPE_OBJECT_NAME, BASE_DATE_DATE, SCHEDULE_WORK_DAYS, BUSINESS_UNIT_OBJECT_ID, BUSINESS_UNIT_CLASS_ID, BUSINESS_UNIT_OBJECT_NAME, COMPANY_OBJECT_ID, COMPANY_CLASS_ID, COMPANY_OBJECT_NAME, ESTIMATED_CURRENCY, ESTIMATED_OBJECT_ID, ESTIMATED_PRICE, BUDGETED_CURRENCY, BUDGETED_OBJECT_ID, BUDGETED_PRICE, CURRENCY_OBJECT_ID, CURRENCY_CLASS_ID, CURRENCY_OBJECT_NAME, VENDOR_VISIBLE, DATE_TO_PUBLISH_DATE, LOCK_BASELINE, LI_PERIOD_TYPE_OBJECT_ID, LI_PERIOD_TYPE_CLASS_ID, LI_PERIOD_TYPE_OBJECT_NAME, CALC_METHOD, SPEC_ID_COUNT, ATTR_ID_COUNT, FORMULA_ID_COUNT, PURCHASING_ORG_OBJECT_ID, PURCHASING_ORG_CLASS_ID, PURCHASING_ORG_OBJECT_NAME, PURCHASING_GRP_OBJECT_ID, PURCHASING_GRP_CLASS_ID, PURCHASING_GRP_OBJECT_NAME, TRANSACTION_TYPE_OBJECT_ID, TRANSACTION_TYPE_CLASS_ID, TRANSACTION_TYPE_OBJECT_NAME, COMPANY_CODE_OBJECT_ID, COMPANY_CODE_CLASS_ID, COMPANY_CODE_OBJECT_NAME, INTEGRATED_TYPE, USE_ERP_VALIDATION, STORAGE_LOCATION, RECORD_SERIES, RETENTION_DATE_DATE, RETENTION_REMINDER_DATE_DATE, RETENTION_EVENT_OBJECT_ID, RETENTION_EVENT_CLASS_ID, RETENTION_EVENT_OBJECT_NAME, EFFECTIVE_DATE_DATE, EXPIRATION_DATE_DATE, TERMIN_NOTICE_LEAD_TIME, TERMIN_COMMU_DATE, PERPETUAL_TERM, AUTO_RENEWAL, EVENT_OBJECT_ID, EVENT_CLASS_ID, EVENT_OBJECT_NAME, RENEWAL_REMINDER_DATE, VENDOR_OBJECT_ID, VENDOR_CLASS_ID, VENDOR_OBJECT_NAME, CONTACT_OBJECT_ID, CONTACT_CLASS_ID, CONTACT_OBJECT_NAME, LOCATION_OBJECT_ID, LOCATION_CLASS_ID, LOCATION_OBJECT_NAME, PAYTERMS_OBJECT_ID, PAYTERMS_CLASS_ID, PAYTERMS_OBJECT_NAME, REPLENISHMENT_OBJECT_ID, REPLENISHMENT_CLASS_ID, REPLENISHMENT_OBJECT_NAME, VENDOR_ACCT_NUM, INT_CAT_OBJECT_ID, INT_CAT_CLASS_ID, INT_CAT_OBJECT_NAME, EXT_CAT_OBJECT_ID, EXT_CAT_CLASS_ID, EXT_CAT_OBJECT_NAME, EVALUATION_CRITERIA, NEXT_AUDIT_DATE, LAST_AUDIT_DATE, TOTAL_EXPECTED_CURRENCY, TOTAL_EXPECTED_OBJECT_ID, TOTAL_EXPECTED_PRICE, TOTAL_BUDGETED_CURRENCY, TOTAL_BUDGETED_OBJECT_ID, TOTAL_BUDGETED_PRICE, TOTAL_ACTUAL_CURRENCY, TOTAL_ACTUAL_OBJECT_ID, TOTAL_ACTUAL_PRICE, TOTAL_SAVINGS_CURRENCY, TOTAL_SAVINGS_OBJECT_ID, TOTAL_SAVINGS_PRICE, TOTAL_COST_SAVINGS_CURRENCY, TOTAL_COST_SAVINGS_OBJECT_ID, TOTAL_COST_SAVINGS_PRICE, TOTAL_COST_AVOIDANCE_CURRENCY, TOTAL_COST_AVOIDANCE_OBJECT_ID, TOTAL_COST_AVOIDANCE_PRICE, PERF_EVAL_CRITERIA, PERF_LAST_UPDATE_DATE, PERF_NEXT_UPDATE_DATE, BUYER_SEARCHABLE, VAL_PERIOD_TYPE_OBJECT_ID, VAL_PERIOD_TYPE_CLASS_ID, VAL_PERIOD_TYPE_OBJECT_NAME, INCLUDE_PART_NUMBER, TOTAL_ACTUAL_SPEND_CURRENCY, TOTAL_ACTUAL_SPEND_OBJECT_ID, TOTAL_ACTUAL_SPEND_PRICE, FORECAST_SPEND_CURRENCY, FORECAST_SPEND_OBJECT_ID, FORECAST_SPEND_PRICE, ACTUAL_LIMIT_PCT, FORECAST_LIMIT_PCT, LINEITEM_ID_CNT, LIMIT_VALUE_CURRENCY, LIMIT_VALUE_OBJECT_ID, LIMIT_VALUE_PRICE, MINIMUM_VALUE_CURRENCY, MINIMUM_VALUE_OBJECT_ID, MINIMUM_VALUE_PRICE, MINIMUM_DAYS_OFFSET, MARGIN_PRICING, DELETED_AT_DATETIME, DELETED_BY_OBJECT_ID, DELETED_BY_CLASS_ID, DELETED_BY_OBJECT_NAME, CTR_IS_DUET, HAS_DUET_ITEMS, WORD_ATTRIBUTES_TEXT_PREVIEW, WORD_ATTRIBUTES_TEXT_OBJECT_ID, WORD_ATTRIBUTES_TEXT_CLASS_ID, WORD_ATTRIBUTES_CHECKSUM, SENT_TO_ERP_DATETIME, STATUS_OBJECT_ID, STATUS_CLASS_ID, STATUS_OBJECT_NAME, LAST_SPEND_IMPORT_DATE, BUYER_SPECS_SUPPORT, VENDOR_SPECS_SUPPORT FROM clmuser.FCI_CONTRACT WHERE UNIQUE_DOC_NAME = ? AND CONTEXTID = ?
    at com.sap.odp.common.db.AbstractDb.findWhere(AbstractDb.java:5823)
    at com.sap.odp.common.db.AbstractDb.findWhere(AbstractDb.java:5760)
    at com.sap.eso.contracts.ContractHome.findUniqueByDocName(ContractHome.java:96)
    at com.sap.eso.contracts.importer.processors.AgreementProcessor.createNewHook(AgreementProcessor.java:479)
    at com.sap.odp.doc.importer.AbsDocImportProcessor.processRow(AbsDocImportProcessor.java:165)
    at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processRowInternal(CsvFileProcessor.java:1370)
    at com.sap.odp.common.install.dataimport.csv.CsvFileProcessor.processFile(CsvFileProcessor.java:281)
    at com.sap.odp.common.install.dataimport.xml.XmlImporter.importXmlObject(XmlImporter.java:249)
    at com.sap.odp.common.install.dataimport.xml.XmlImportHandler.endElement(XmlImportHandler.java:155)
    at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
    at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
    at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
    at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
    at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
    at javax.xml.parsers.SAXParser.parse(SAXParser.java:176)
    at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.importObjects(ImportXmlReader.java:141)
    at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.parse(ImportXmlReader.java:84)
    at com.sap.odp.common.install.dataimport.xml.ImportXmlReader.parse(ImportXmlReader.java:73)
    at com.sap.odp.common.install.dataimport.xml.XmlImporter.go(XmlImporter.java:164)
    at com.sap.odp.install.actions.ProcessXmlImportFile.executeHook(ProcessXmlImportFile.java:170)
    at com.sap.odp.install.actions.InstallAction.execute(InstallAction.java:203)
    at com.sap.odp.install.engine.ScriptedImportEngine.runSingleItem(ScriptedImportEngine.java:319)
    at com.sap.odp.install.engine.XmlImportEngine.execute(XmlImportEngine.java:128)
    at com.sap.odp.install.imports.ImportController$ImportRunner.execute(ImportController.java:302)
    at com.sap.odp.install.imports.ImportController$ImportRunner.run(ImportController.java:212)
    at java.lang.Thread.run(Thread.java:708)
    Let me know if you need additional details.
    Regards
    Sai

  • Master Agreements fields carry over to child Agreement.

    Hi,
    How can I carry over the fields set in the master agreement module to a child agreement?
    I believe I need to have a script definition on the creation of child agreement. but how can I get the reference to the master agreement fields? Any sample code?
    Also if not for script definition is there any other way out?
    Edited by: patsy lobo on Sep 22, 2008 7:35 PM
    Edited by: patsy lobo on Sep 22, 2008 7:36 PM

    HI,
    Adding to what Sudipta has said, you can also use the workbook technique for accomplishing these type of changes. That way you can achieve all hover text changes in one shot across all MA tabs.
    The 2 main tabs in the wokbook to be changed are: 'Localized Resource' and 'UI overrides' tab.
    As an example, suppose you want to add the following text for Master Agreement External Category field:
    "This field is a classification hierarchy to describe the products or services of the event and/or agreement."
    So in the Localized resource tab, fill out the following:
    BUNDLE: custom
    RESOURCE_ID: xxx     
    RESOURCE_KIND: APP_TEXT     
    DEFAULT_VALUE: This field is a classification hierarchy to describe the products or services of the event and/or agreement.
    Then refer the same attributes in the UI Overrides tab:
    UI_ID: contracts.agreement.ui.buyside.default
    FIELD: EXT_CAT
    ATTRIBUTE: Description
    VALUE: Same as Resource ID used in localized resource (xxx above)
    Hope this helps,
    Vikram Shukla

  • CLM Importing Master Agreement: Is it possible to import custom collection

    Hello,
    We are looking to migrate some legacy data into CLM using the import master agreement (setup->Import and Export Tools).  This approach works fine for all standard data as well as extensions that are single entry fields (not collections).  We would like to load some data into extension field that are collections and are wondering what is the best, most efficient way to accomplish this.
    I can only think of the following method:
    Import all master agreement data standard fields and extension fields (not collections).  Once all are entered, we go into the master agreement and add the collection data manually or by importing csv files at that time.
    This method will be time consuming.  Is there a better way to accomplish this?
    Thanks in advance,
    Kyle

    Hi Kyle & Venkat,
    I am trying to import the contract through 'contract import workbook' present in RG.
    I have made & verified changes in field data values of the three worksheets in contracts.
    Now when i try importing, it gets failed giving me the error  - An error was encountered in column CONTACT/LOCATION.
    However, the same values do exist in Master Data.
    Can you please let me know if the same error occured with you folks & possible troubleshooting.
    Any pointers would be highly appreciated.
    Thanks,
    Tripti

  • CLM Company-Organization Unit in Master Agreement

    Hi guys
    In a CLM Master Agreement, after I select a company, I am able to select any organizational unit, even if it does not belong to that company. The system does not issue any error message. Is it standard behavior?
    Shouldnt the system validate that only the organizational units which are belonging to a particular company be displayed?
    Thanks and regards
    Ajay

    Hi,
    It looks it is standard behaviour.
    We have put in script to validate and added a query to query group so that user can search ORG UNIT by company code.
    //........................Gets company code
    getChildFieldByFieldId(parentFieldId,childFieldId){
            value=doc.getExtensionField(parentFieldId).get();
         if(hasValue(value)){
              parenthome=IBeanHomeLocator.lookup(session,value);
              parentbean=parenthome.find(value);
              childField=parentbean.getExtensionField(childFieldId).get();
              return childField;
         return null;
    validateCompanyCodes(parentfieldId,childFieldId){
            flag=false;
         maCompanyCode=doc.getExtensionField("SAPCCODE").get();
            companyCode=getChildFieldByFieldId(parentfieldId,childFieldId);
         if(companyCode==null @or !hasValue(maCompanyCode)){
              flag=false;
         }else if(maCompanyCode.equals(companyCode)){
              flag=true;
         return flag;
    purchasingOrgCompanyCodeMatch=validateCompanyCodes("SAPPORG","sapccode");

  • Script for setting Inco-terms in Master Agreement Setup

    Hi All,
    We have a requirement to create a follow-on child Master Agreement from a Parent MA. So we are writting a toolbar script to craete this follow-on Master Agreement. The problem we are facing is , we are not able to populate inco-terms (delivery terms) from the setup of Parent to Child Master Agreement.
    Although Master Agreement Setup has APIs but it seems there is no method which can allow us to get and set the values of inco-term in the collection (DEL_TERM_COLLN ) which is present in the setup of Master Agreement.
    Can you please throw some light on this issue, if it would be possible to set incoterms values in Master Agreement Setup.
    Thanks in Advance!
    Regards,

    Hello,
    If the IAPI doesnu2019t have the getter and setter, I would suggest raising a OSS message with SAP.
    Regards,
    Vikram

  • How to make extended field mandatory in Master Agreement

    Hello All,
    I am new to SAP CLM, and I have requirement where one extended field in master agreement needs to be made as mandatory field.
    I tried in extension definition but check box to make it required is disabled and I am unable to find other way to do it.
    Can some one help me and Please let me know how make extended fields mandatory in CLM.
    Regards,
    Prabhat

    Hi
    This could be achieved using Page Customization.Go to Setup-> User Interface-> Page Customization, open master agreement object (create new with UI ID:contracts.contract.ui.buyside.default if doesn't exist ) and add a new customization for extended field with Property set to Required.
    Regards
    Mudit Saini

  • How to change the standard query "Create a Master Agreement" by a custom one

    Hello Sourcing CLM experts,
    I would need to replace the standard query displayed when the user tries to create a Master Agreement by a custom query to filter the MA types according to some criteria:
    According to this post: Re: Create security profile for a document template in SAP Sourcing, I've tried to achieve it by doing the following steps:
    Create a new query as a copy of exsiting query FCI-ContractTypes
    Modify query group FCI-ContractTypesBP to include my custom query instead of the standard one to only list the MAType "Standard Master Agreement"
    Following you can see the change done into the query group FCI-ContractTypesBP:
    However, standard query has not been replaced and same set of MA Types are listed.
    Therefore, I would like to ask you:
    Is it possible to do this kind of modifications? If so, which query group need to be modified?
    If it is not possible, is there any other way to achieve that requirement?
    Thanks in advance for your time and support!
    Best regards,
    Isaac

    Hello again experts,
    If this query cannot be modified, is there any option to disable button below? Or at lease, to disable the query group to avoid the listing of MA Types when it is pressed?
    The reason is because we are going to set up the system in the way that only it will be possible to create Master Agreements from Template. However, if user keep on using that button he will be able to create MA from document types.
    Any ideas?
    Thanks again and best regards,
    Isaac

Maybe you are looking for