Multiple currencies in master agreement

All,
Any ideas on how a master agreement can handle multiple currencies?
Even the subagreement carries over the master agreement currency and a script would not change it.
Regards,
Subhasini

Hi Subhasini,
Master agreement doesn't support multiple currencies in CLM till date. Only RFx does. You may have model your scenarios working around this limitation. One solution could be to use MA instead of subagreements and tie them with document links...
Guess In newer releses (wave 8) contract heirarchies are supported, where you can have multiple MAs linked and each of them can have their own currencies.
Thanks,
Baski

Similar Messages

Different currencies in Master Agreement and it;s Sub-Agreement

Hi Experts,
I see that the Sub-Agreement(SA) by default have the same currency as that of the Master Agreement(MA). However, by using importer, we can create a SA which can have a different currency from it’s MA.
If SAP allows the SA to have alternate currency using importer, why do it restricts from UI. We may have a business scenario where SA may be created for different countries and may have alternate currency.
Please share your thoughts on this .
Regards
Praveen

Hi Praveen,
Currency field becomes read only as soon you add a line item to both Master Agreement and Sub-Agreement.
If you want to make Sub-Agreement a different currency, you need to make to sure that there are no line items added until the intended currency is selected.
I hope this helps.
Regards,
Parankush

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

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);

PO multiple line items -multiple currency

Hi,
I had one issue.
Can I create PO with multiple line items ,with multiple currency ?
E.g 2 line items one line item with INR and second with USD.
I tried I am not able to create PO , But its allowing to create the same for Scheduling agreement and Contracts.
E.g I create a Contract with two line items.
one line item with INR and second with USD.
But the Header Currency is fix either INR or USD whatever u select before creating the contract remanins same and cannot be changed later.
Q :Is this correct ?
Q: what will contract vaule in this case in USD or INR .
Please see if u can add some in puts.
Thank you
Regards
Amar

Amar,
You can create a PO with multiple line item, but you can not create the PO with multiple currency.
Regards,
Manish

Can DRM support multiple currency ?

Can DRM support multiple currency ?

Hi,
DRM is a master data management tool - so if you have a currency dimension, then yes it would be easy to manage multiple currencies.
Can you expand on your question a bit?

Multiple currencies for one minisite

We have a requirement so the different users can place orders in two different currency. Some of the customers are set up with USD and some of the customers are setup with CAD. So, when they login to istore, based on their customer Master - order management tab price list value - that currency code should default.
I added both currencies with their default price list on minisite set up under pricing menu on left. Users are able to checkout and place an order in USD. But RMAs are not working - getting error "Please contact yor sales representative".
My question is: is this possible to have two currencies work for one minisite based on customer master setup?
If yes, How can I resolve RMA issue?
Thanks.

Hi,
iStore supports multi-currencies and allows a user to switch currencies using the Global Bin.
Please details below on using the Global Bin.
Thank You,
Deborah Bourgeois, Oracle Customer Support
Excerpt details below are from Chapter 6 'Implementing Initial Customer Application Pages'
Oracle® iStore Implementation and Administration Guide
11i Part No. B13549-01
12.0 Part No. B31536-03
12.1 Part No. E13575-02
Global Bin
The Global Bin displays by default on the right side of the Site Home Page and other
section pages, if the current site has multiple currencies enabled. The bin allows
customers to select other currencies; when customers select a new currency, item prices
are displayed with the newly selected currency.
Important: In order for prices to display in additional currencies, the items must be set
up on a price list in those currencies. See the chapter, Implementing Pricing, page 10-1
, for details.
To enable the Global Bin, set the profile option, IBE: Use Global Bin, to Yes. See the
appendix, Profile Options, page A-1, for more details on the profile options settings.
Just as with the Browse Bin, this profile works only if you use Fixed Layout when
creating a section. If sections are associated to Configurable Layout, then you should
map the bin using Configurable Layout for bins.
By default, the Global Bin template (STORE_GLOBAL_STORE_BIN) is mapped to the
JSP, ibeCAcdGlobal.jsp.
Guidelines:
• In order to view the bin, the user's active responsibility must not be iStore Sales
Representative (IBE_SALESREP).
• In order to display, the site where the bin will display must have multiple
currencies enabled.
• In order for the Global Bin to display on the shopping cart page, the current site
must have multiple currencies enabled.
• When the Global Bin is mapped to the shopping cart page, changing currency in the
shopping cart page causes cart items to be re-priced in the newly selected currency.

Multiple currencies? Multiple languages?

hi,
Does SAP handle multiple currencies? Multiple languages? What is a currency factoring technique?
Thank you
Ashok kumar

HI,
Yes.
SAP handles Multiple Currencies and Languages
see the table TCURR, TCURC for different currencies
Currency Factoring Technique:
Currencies in Planning
In Profit Center Accounting, three currencies can be stored at once:
Transaction Currency
The transaction currency is the currency used for a specific transaction. You can choose a different currency from the list of valid currencies for each new transaction. The transaction currency is stored in the transaction data for Profit Center Accounting as the so-called "first currency".
Local Currency (Company Code Currency)
The controlling area currency is stored in Profit Center Accounting as the second currency.
Profit Center Local Currency
You need to set a special currency for Profit Center Accounting in Customizing for each controlling area. This currency is used in the standard reports, among other things. You can find more information about this currency in Customizing. The profit center currency is the third currency updated in the transaction data.
How Do I Plan Currencies in Profit Center Accounting?
You first plan a profit center in USD. Then you later plan the same profit center in DEM in a second planning session. This may be necessary if:
the planned costs for the profit center in a certain cost element consist of external invoices in the local currency and external invoices from abroad and
the external invoice from abroad was billed and paid abroad
The currencies which can be planned manually are defined in the Layout.
If the corresponding key figures are defined and ready for input in the planning layout, you can plan in any permissible transaction currency, the company code currency or the profit center currency. The planned amount is then immediately and automatically translated into the other currencies. Note, however, that the system can only translate into a transaction currency if you have explicitly specified a transaction currency.
If you want to want to plan data using different transaction currencies, you need to use a planning layout that contains the characteristic "Transaction currency".
Note that data can only be saved in the transaction currency if a transaction currency has been specified. Otherwise the data will only be saved in the other currencies without the transaction currency.
If you want to want to summarize data in the transaction currency, you need to use a planning layout that does not contain the characteristic "Transaction currency". You can then:
change the summarized values, in which case the changes are not updated in the transaction currency, and
add any combinations of objects that have not already been planned.
If you
enter one transaction currency, the system only displays the amounts planned in that currency. You can
change these amounts
plan in the currency specified
enter a number sign (#) to represent the value " " (no value), the system only displays those values that were planned without the transaction currency. You can
change these amounts
plan amounts without a transaction currency
specify more than one currency or all currencies (*), the system displays all the planned values. You can
change these amounts
can plan as yet unplanned combinations of your planning objects in any valid currency.
Planned currency amounts are translated using
the value date you entered in the planner profile for your area
a translation factor entered in the currency table for the exchange rate type entered in the planner profile
You will find further information about the currency table and currency translation in the documentation FI Configuration and Organization.
Transfer Pricing Using the Conditions Technique
The term "transfer pricing" is used to describe the calculation of prices for internal exchanges of goods between profit centers. Conditions are the individual steps carried out during price calculation. When a goods movement takes place between two plants, the price can depend on a number of factors, such as the material involved, the sender plant, the profit center, the partner profit center, and so on. The information on these variable factors is stored as master data in the form of condition records. There the transfer price can be defined as a fixed price or a percentage increase or reduction.
This section describes the steps necessary to define transfer prices. You define these transfer prices in Customizing. There you will also find a detailed description of how to proceed.
Define condition tables, which you use to store condition records for each condition type.
Here you define the price dependencies for transfer prices. You can make the transfer price found dependent upon a combination of fields. For example, if you want your transfer prices to be defined for a combination of material and partner profit center, you need to define a condition table that contains these key fields. The condition records then contain the individual prices for each combination of material and profit center. You maintain the condition records when you define the individual condition types.
Define access sequences that the system should use to search for valid condition records.
An access sequence is a search strategy that the system uses to find valid data for certain condition tables. Each access sequence consists of one or more steps, which the system processes in the order specified. The order determines where the system should look first for a valid condition record. You can specify an access sequence for any condition type for which you create condition records.
Define condition types for all the pricing elements (fixed amounts, markups and markdowns) that occur in your daily business operations.
In Profit Center Accounting, a condition type represents a component of a transfer price. You can define condition types for every type of fixed price, markup or markdown that occurs in your internal goods movements. If you define a percentage markup or markdown as a condition type, you also need to define another condition type to serve as the basis for this percentage. This can be a price stored in the material ledger. The relationship between these two condition types is then defined in the pricing procedure.
In some condition types you need to specify an access sequence. In this way you determine which fields the system should use to search for a valid condition record.
Define condition records that determine the amount or percentage to be applied for each set of values in the condition table (such as "fixed price of USD 100.00 for material 01, profit center ABC, and plant 0001").
You can maintain condition records directly from within the definition of the condition type. Or you can define them from the application menu by choosing Master data ® Transfer prices ® Conditions. It is also possible to copy existing condition records to create new ones. This is especially useful if you want to change the currency of the condition record. You can maintain condition records either in Customizing or in the application menu, under Master data ® Transfer prices.
Define a pricing procedure to group together condition types and determine how they relate to one another.
In addition to the selection and order of condition types, a pricing procedure determines
which subtotals should be calculated
what base value the system should use for calculating percentage markups or markdowns
what conditions must be met in order for a certain condition type to be calculated
The base value for markups and markdowns can be either a fixed price or a value from the material ledger. Using a routine supplied in the standard R/3 System, you can have the system read the legal, group, or profit center price from the material ledger and calculate the markup or markdown on this basis.
Define condition exclusions, which let you determine which condition type should be used in a given situation.
In transfer pricing for goods movements, it often happens that a number of different condition records are valid. Using condition exclusions, you can compare conditions with one another and use, for example, the most favorable price for the partner profit center.
For different condition exclusion methods are available:
· The most favorable condition in an exclusion group
· The most favorable condition record for a condition type
· The most favorable condition among different exclusion groups
· Exclusion of those conditions in an exclusion group when a condition type that belongs to another exclusion group appears
Define transfer price variants, which let you specify which pricing procedures are relevant for actual data and which for plan data.
To valuate different datasets, such as plan and actual data, using different conditions, you can define variants with an assignment to a specific pricing procedure. The system processes the specified procedures in order until it finds a valid transfer price.
In transfer pricing for goods movements, only actual data is valuated (variant 000). However, you can also create additional variants if you want to calculate plan prices on the basis of pricing data.
Define pricing reports, which determine the structure of lists of conditions.
A pricing report lets you analyze condition records according to certain criteria and define the structure of these lists. You can define pricing reports either in Customizing for Profit Center Accounting or in the application menu, under Master data ® Transfer prices ® Pricing reports.
Regards,
Padmam.

Multiple currency planning and budgeting?

Hi all
We are having a requirement of planning and budgeting in same WBS with multiple currencies and also seeing reports in different currencies on single screen.
Now has anybody explored this area and has anything to suggest.
Thanks in anticipation
Raman

Hi Raman
The following is the literature from SAP on the subject. You may find it useful.
Planning and Budgeting in Any Currency
Use
International groups often use one uniform company code currency (group currency) in CO. However, it may be necessary to plan and budget in the respective local currency as the majority of costs will be incurred in the local currency. The local currency is usually the corresponding company code currency.
Previously only budgeting of jobs (orders and projects) was possible in the local currency.
From Release 4.70, you can also budget investement programs in the local currency. In addition, it is possible to plan investment programs, appropriation requests and jobs directly in the local currency.
As was previously the case for orders and projects, plan and budget values for investment programs and appropriation requests are also saved in both the controlling area and local currencies defined in the master record of each object. If you change or re-specify the exchanged rates used, it is now possible to recalculate the values in the local currency using the values in the controlling area currency, and vice-versa.
In reporting for IM, it is even possible to calculate evaluations in any report currency (plan, budget and assigned values). If the values are available in the specified report currency, they are issued unchanged. If they are not available, they are converted from the controlling area currency into the report currency.
Effects on Existing Data
Before Release 4.70, the plan values for appropriation requirements, were only saved in the controlling area currency. This was also the case if a local object currency was specified in the master record for the appropriation requirement. From Release 4.70, the plan values for appropriation requirements are always saved in the controlling area and local currencies. Therefore, you must adjust appropriation requests that were created in an earlier release and use a local currency that varies from the local object currency. The easiest way to do this is to use the program RAIMCRC2 to recalculate the plan values in the local object currency for appropriation requests whose plan values are in the controlling area currency (transaction IMCRC2, menu path: Financial Accounting -> Investment Management -> Appropriation Requests -> Tools -> Recalculate Currency Plan for Appropriation Requests). Before you run the program, select the relevant option in the Process Control section of the initial screen.
Effects on Customizing
Adjustment of Planning and Budget Profiles
To enable the planning of investment programs, appropriation requests and jobs in a transaction currency different to the controlling area currency, you must adjust the relevant planning profiles.
To enable the budgeting of investment programs in a transaction currency different to the controlling area currency, you must adjust the relevant budget profiles.
In the planning currency (or budgeting currency) section of the planning (or budget) profile, you must define the transaction currency in which planning (or budgeting) is to be executed:
Only in the controlling area currency (default),
Only in the object currency
(= local currency defined in object master record ) or
In a transaction currency chosen at the start of planning/budgeting
(this option is not possible for appropriation requests).
In the planning or budget profiles, you must also define the exchange rate types to be used for the conversion of total values that are not dependent on the fiscal year.
To adjust the planning profiles, use the process steps:
Maintain Planning Profiles (investment programs)
Maintain Planning Profile for Cost Planning (appropiation requests)
To adjust the budgeting profiles, use the process steps:
Define Budget Profiles for Investment Programs (investment programs)
Exchange Rate Types
In the fiscal-year-dependent data of the CO planning versions, you must also define the exchange rate types to be used for conversion of plan values that are not dependent on the fiscal year.
For conversion of fiscal-year-dependent budget values and fiscal-year-dependent plan values of appropriation request variants not yet assigned to a plan version, each exchange rate type is taken from the fiscal-year-dependent data of the CO planning versions 0.
As the plan or budget values are stored in the transaction, controlling area, and local currencies, the exchange rates used must enable the conversion of the transaction currency into the controlling area and local currencies. Where necessary, the exchange rates used must be extended.
To enter the exchange rate types, use the process step:
Define Versions (investment programs)
Change Planning or Budget Currency
If you always planned or budgeted existing investment programs/measures in the controlling area currency, it is not subsequently possible to change the planning or budget currency to the object currency in the planning or budget profiles. This conversion is not prevented in Customizing, but leads to an error when you next plan or budget existing investment programs/measures. Alternatively, you can convert the planning or budget currency into the transaction currency in the planning or budget profiles, and set the object currency indicator as default.
A similar restriction does not exist for appropriation requests. You can change the planning currency in the planning profile at any time.
Use the process step under "Adjust the Planning and Budgeting Profiles".
Detailed Planning
When you call up detailed planning from structure-based cost planning or revenue planning, the standard SAP planning profiles are used, to which the standard SAP planning layouts are assigned. These planning profiles cannot be changed in the planning transactions. Import the standard SAP planning layouts 1-401-IM, 1-402-IM, 1-403-IM, 1-701-IM, 1-702-IM and 1-703-IM using the transaction OKBF from client 000 in your client.
To execute the import, choose the process step:
Import Standard Planning Layouts.
Reporting Currency for IM Reporting
In IM reporting, if you want to be able to specify a reporting currency that is different to the controlling area and object currencies used in the investment program items or subordinate appropriation requests and measures, another exchange rate type is required for the due conversion of plan, budget, or values into the reporting currency. You define this exchange rate type in Customizing for the program type for the investment program to be reported ( Group Reporting).
To enter additional reporting currencies, use the process step:
Define Program Types (investment programs)
you may also refer the following link in SAP help on the subject
[http://help.sap.com/saphelp_47x200/helpdata/en/86/98853478616434e10000009b38f83b/frameset.htm]
Venu

Multiple currencies in basic pay

Hi all,
our client keeps uses the basic pay infotype only as information (no payroll). They want to be able to use multiple currencies in the different wage types (e.g. one in USD, the other in EUR).
Is this possible ?
thanks in advance !

I too agree with our friend.
It is not possible to use two different currencies in Basic Pay.
I think it not possible in SAP standard.
i assume your client is using IT0008 for reporting purpose to solve this You can create 'Z' table pass IT 0008 values to that table. Write reports based on that table.

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.

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

Multiple Currency Payroll Payments for one Employee

Hello,
We have a requirement of paying one employee in multiple currencies (i.e in Local currency and USD). This means that such employee has two bank accounts, i.e. Local Currency Account and USD Account.
The costing of payroll costs is done in the local currency. Does anyone know any standard procedure for this?
P.S we are using Global Legislation
Regards,
Salman

Hi Salman,
Have you tried this from Element Define window. There is functionality for Input and Output currency.
Hope it could meet your requirement.
Thanks
AshokP

Multiple currency in PO/MIRO

Hi Friends,
In the PO, the vendor is from Japan, so the document currency is in Japan. But the freight condition currency is in MYR which we dont want to convert into JPY. Here the system converts all the condition type currencies into document corrency i.e. JPY in this case. After Goods Receipt, when I see the FI document in MIGO T-Code, all the posting
comes in JPY and when i change the postings into local currency i.e. into MYR, there is a difference of RM0.02(2 sens) in the posting. As the freight condition value is in MYR, we dont want system to change it to JPY as freight charge not relevant for PO printout. Because os the conversion factor, a podting having difference of 2 sens is done.
At the time of Invoice Posting through MIRO T-Code, all the charges are converted into JPY irrespective of their actual currency mentioned in the PO. Inside "Simulation" tab I can see the delivery/material cost in only 2 currencies i.e. JPY and MYR. I cant see the currency in USD as one of my delivery charge in PO is in USD. My invoice comes in respective urrencies as per PO. Please advise how to post invoice in multiple currencies as per the currency mentioned in PO.
Thanks & Regards
Satya

Hi,
Document currency of PO will be single and all the condition type values are converted to the document currency.
For condition types where currency conversion is required, please goto config (T code M/06), select the condition type and under Control data 2 tab, tick currency conversion. This will remove rounding of errors in case of multiple currecies.
Hope this info helps
Priyadarshi

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

Multiple currencies in master agreement

Similar Messages

Maybe you are looking for