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

Similar Messages

CATT - vendor/customer master address field length over

Dear all,
when use CATT to record vendor/customer master,the address some fields length are over recorded field length(ex. ADDR1_DATA-NAME4,ADDR1_DATA-STR_SUPPL3...etc)
is there any config in CATT to solve this kind of problem?

When you are doing your LSMW batch input recording, on selection screen (where you specify the sales org, distribution channel, division, account group, etc) please put a flag on "Use central address management" checkbox (SAPMF02D 0100 > USE_ZAV).
In this case you should be able to see and fill the desired fields.

Unable to capture field values in Master agreement Line Items

I am trying to get the field values from master agreement line items page. I have written the following code to get the line item details which is working fine to capture part number and quantity->
agreementBean = doc.getRootParentIBean();
lineItemCollection = agreementBean.getLineItems();
collectionsize = lineItemCollection.size();
for(i=0;i<collectionsize;i++){
     collectionbean = lineItemCollection.get(i);
     partNum = ""+collectionbean.getPartNumber() ;
     Quantity = ""+collectionbean.getQuantity();
     throw doc.createApplicationException(null,partNum + " , " + Quantity );
Now, my problem is that I am unable to capture the following field item values in the master agreement > line items page.
1. Price Unit
2. Unit Price
3. Product Category
4. Plant
Please help me to find the values.
Thankx in Advance.
Su
Edited by: subrataindra on Aug 10, 2010 11:11 AM

This will return the name of the plant.
.getExtensionField("PLANT").get().getDisplayName(session);
Check if this returns the product category
collectionbean.getExtensionField("ITEM_CAT").get().getDisplayName();
This will Return the Price
collectionbean.getExtensionField("PRICE").get().getPrice();
(return type :BigDecimal)
This will return the currency
collectionbean.getExtensionField("PRICE").get().getCurrency;
(Return type:String)
Similarly to retrieve other fields for which there are no standard functions, use .getExtensionField("Field ID")
Hope this helps
Regards,
Immanuel

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

PO rel procedure carried over to Outline agreements

Hi Experts,
Release procedure created for Purchase order has become active for Contracts & Scheduling agreement also. Infact system doesn't allow to process (MIGO) scheduling agreements (agreement type: LP) without being released.
Is this valid? if yes how do I avoid this carry over.
Thanks,
Rajoo

Hi,
In the classification of the release strategy, create one caracteristik as Document category.
Maintain the value "F" for PO.
It will not pickup the outline agreement
Cheers,
Satish Purandare

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

A link to create master agreement in a user defined object

Hi guys,
We have a requirement wherein we need to put a toolbar link in a UDO to create a master agreement. Certain fields from the UDO needs to be carried over to the master agreement.
Any pointers would be extremely helpful..

hi reshma,
Here is the code for contract creation. Please Note: Other mandatory fields, depending on your MAster agreement document type has to be set before you save the Contract.
contractHome =IBeanHomeLocator.lookup(session, ContractIBeanHomeIfc.sHOME_NAME);
//Creates a contract bean. The input parameter is an Master Agreement type
contractBean = contractHome.create("master agreement typet");
/Set the Required fields in the contract/
//example to set few fields
valueTypeHome=IBeanHomeLocator.lookup(session,ValueListTypeIBeanHomeIfc.sHOME_NAME);
valueTypeBean=valueTypeHome.findByExternalId("master_agreement_status");
valueBean=valueTypeBean.getCollnValueListValue().get(0);
contractBean.setStatusRef(valueBean.getLocalizedObjectReference());
//set display name
contractBean.setDisplayName("Test"+doc.getDisplayName());
//Set currency
contractBean.setCurrency(doc.getCurrency());
//set effective date
contractBean.setEffectiveDate(TypeFactory.createSysDate(new java.util.Date()));
//set base date
contractBean.setBaseDate(doc.getBaseDate());
//set contact info
vendorCollection = doc.getCollnVendors();
vendorRef=vendorCollection.get(0);
contact=vendorRef.getContactObjRef();
contractBean.dbSetContactRef(contact);
contractBean.dbSetVendorRef(vendorRef.getVendorObjRef());
/Set other necessary information in the contract bean/
//Save the Contract
contractHome.save(contractBean);

Copy line items from Master Agreement to SubAgreement

Dear all,
As a requirement, we need to create a dummy line item at master agreement and subagreement level to be able to publish them to ERP without need
to complete line items (they are completed in ERP via a development).
We have created master agreement templates with a dummy line item but at subagreement level, templates are not available.
What we are trying to develop is a script on post_create at agreement level to copy line items from Master Agreement to SubAgreement. We are able to get Master Agreement line items and copy them to the SubAgreement, but the subagreement is not created. This is the code we are using:
import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListTypeIBeanHomeIfc;
import com.sap.odp.api.doccommon.masterdata.ValueListTypeIBeanIfc;
import com.sap.eso.api.contracts.ContractIBeanHomeIfc;
Mst_agreementBean = doc.getParentIBean();
lineItemCollectionSub = doc.getLineItems();
lineItemCollection = Mst_agreementBean.getLineItems();
collectionsize = lineItemCollection.size();
colln = Mst_agreementBean.getCollectionMetadata("MA_LINEITEMS").get(Mst_agreementBean);
colln2 = doc.getCollectionMetadata("MA_LINEITEMS").get(doc)
newProject = Mst_agreementBean.getIBeanHomeIfc().createFromAnother(Mst_agreementBean);
newMember = colln.get(1);
// Get Values Line Item
assCat = newMember.getAcctAssignCategory();
actLimP         = newMember.getActualLimitPercent();
delAdCity       = newMember.getDeliveryAddressCity();
delAdCount    = newMember.getDeliveryAddressCountryRef();
delAdDist       = newMember.getDeliveryAddressDistrict();
//... (all fields included in the script)
// Create Line
newMember2 = newMember;
AgreementHome = IBeanHomeLocator.lookup(session, doc.getObjectReference());
AgreementHome.upgradeToEdit(doc);
// Set Values
newMember2.setAcctAssignCategory(assCat);
newMember2.setActualLimitPercent(actLimP);
newMember2.setDeliveryAddressCity(delAdCity);
newMember2.setDeliveryAddressCountryRef(delAdCount);
newMember2.setDeliveryAddressDistrict(delAdDist);
//... (all fields included in the script)
try{
colln2.add(newMember2);
AgreementHome.save(doc);
AgreementHome.downgradeToView(doc);
collectionbean = colln2.get(0);
logInfo("Value of collectionbeanSub " + collectionbean );
}catch (ApplicationException e){
logInfo("Error " + e.getClass() + ". " + e.getMessage());
When we try to create an Agreement under a Master Agreement (clicking Add on Agreement tab), following error message is shown related to the line in blue:
Facility=local4;sessionid=4e73bb8e73304d6284816f93f4e04522a7c387b; tenantid=#tenant.ecb#;username=LUGUELL; exception=Sourced file: inline evaluation of: ``// **   import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : Method Invocation AgreementHome.save : at Line: 164 : in file: inline evaluation of: ``// **    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : AgreementHome .save ( doc )
Target exception: java.lang.NullPointerException: while trying to invoke the method com.sap.eso.contracts.ContractTypeBo.getVendorVisible()
of a null object returned from com.sap.eso.contracts.ContractCommonBo.getTypeBo()
;stacktrace=Sourced file: inline evaluation of: ``// *JLA*    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : Method Invocation AgreementHome.save : at Line: 164 : in file: inline evaluation of: ``// *JLA*    import com.sap.odp.api.doccommon.masterdata.ValueListValueIBeanHomeI ... '' : AgreementHome .save ( doc )
Target exception: java.lang.NullPointerException: while trying to invoke the method com.sap.eso.contracts.ContractTypeBo.getVendorVisible()
of a null object returned from com.sap.eso.contracts.ContractCommonBo.getTypeBo()
Any ideas what is causing the error? What are we missing on our code to copy line items?
Many thanks,
Marc Romagosa
Message was edited by: Marc Romagosa de Riba

We managed to create a line item at VALIDATE script, but not at POST_CREATE. Either it is a bug or it is not possible at POST_CREATE script.

Can we hide filter in Search Master agreements standard top level query?

Hi Experts,
I have a requirement to hide flter in standard Search Master Agreements top level query. See below screen shot
I have an idea how to delete filter in query but when i have added that query to top level navigation i don't have any idea.
So i want to hide Business Unit & Region filter in Search Master Agreement query when it is in top level navigation.
If anyone have idea please share with me how to hide.
Thanks,
Lava

Hi Lava,
It is not a filter but this a Standard field which is coming from the Master Agreement.
So, you cannot hide or even delete any field.
But if it is a custom field you can hide it by inactivating the respective field in Extension Defination.
Please let me know if you need any assistance.
Thanks,
Raj.

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

Can we duplicate standard query Search Master Agreements and Agreements.

Hi Experts,
I have a requirement to hide Agreement Manager and Business Unit & Region result fields in standard Search Master Agreements and Agreements query.
I have duplicated this standard query and deleted Agreement Manager and Business Unit & Region result fields. Try to run this query but it is giving error.
Execution Type is Java.
Query Executor Class: com.sap.eso.contracts.query.SearchAllMAandAgreements
Error: SQL Exception: Fail to convert to internal representation, ANSI-92 SQL State: 99999, Vendor Error Code: 17059. Fail to convert to internal
representation.
Does anyone have idea about this functionality or how this standard query can be modified.
Thanks,
Lava

Hi Lava,
There is the Standard Query ODP-ESO-MasterAgreementList
Duplicate the query and remove the fields from the Result fields whcih you dont want. I think you will get the result required.
Thanks
Kushagra A

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 get Organizational Unit of a Master Agreement?

HI,
I am trying to retrieve value of Organization Unit of a Master Agreement but I am getting some code: name.
ownerObj=doc.getDocumentOwnerUserReference();
ownerHome=IBeanHomeLocator.lookup(session,ownerObj);
ownerBean=ownerHome.find(ownerObj);
throw doc.createApplicationException("VENDOR_VISIBLE", "Supplier name is "+
ownerBean.getOrganization());
Please suggest.
Thanks,
Saloni

Hi Solani,
You were getting the error beacuse we don't have any field like org unit in the Contract Document and the method you used is not there in the API's.If you want to access the Master Agreement Org unit in Contract document then you have to get the MA bean and then you can fetch Org unit in your contract document.
Code as follows:-
masterBean = doc.getParentIBean();// to get the MA bean
orgunit = masterBean.getOrganizationalUnitRef(); //this wil give the orunit of the MA
businessUnitHome=IBeanHomeLocator.lookup(session,orgunit);
businessUnitBean=businessUnitHome.find(orgunit);
Hope this will work for you.
Thanks,
Ankur Goyal
Edited by: ankur_goyal03 on Oct 15, 2011 8:23 AM

Uploading two contract documents to the same master agreement

Hi:
I am uploading contracts into the SAP Sourcing 7.0 using the 'Contract Agreement and Document Uploader' in the Document Setup of the Setup.
For a particular scenario when I try to upload two different contract documents to the same master agreement I get this error.
I am using exactly the same row in the CSV file except for the field FILE_NAME.
The error that I get is-
The attempted phase change failed. Return to your document to see errors. [PHASE_ERROR].....Import failed for object number 3. The Master Agreement has been changed by Jon Stewart, and your changes cannot be saved. You must discard these changes and reload the document. [STANDARD_ATTRIBUTE_ID].
Thanks in advance
Raghav

Hi Raghav,
I am sorry, i could not understand your problem properly. but the error with STANDARD ATTRIBUTE ID is something i hope i can help you with.
I had got the same error while uploading RFP Questions (STANDARD ATTRIBUTE ID) for Group Name. The reason i found for this error was that the group name had exceeded the maximum number of allowed characters i.e 40. Could you please check whether your data in certain field has exceeded the maximum number of characters.
Can you please throw some light on other problem, would be more than happy to help.
Regards,
Anshuman

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

Master Agreements fields carry over to child Agreement.

Similar Messages

Maybe you are looking for