LC2 calculated by default

All,
we are parking a document with the following amounts Local currency GBP 200, and group currency (LC2) - 400 USD.
But for some reason, the system always overrides the LC2 that we entered and recalculates its based on the exchange rate to 360 USD.
The same entry works fine on our QA system but the issue is only happening in production.
Any help would be appreciated!
Thanks,
Tz

Hi
Get into FBV4 and remove the checkbox in "doc curr" field.
This mark cause to post only the doc curr amounts and recalculate the LC2 amounts according to the new exchange rates in the system.
Ofer

Similar Messages

Make calculated fields default to blank - format with currency when filled

Hi!
I'm creating a standard invoice. quantity x price = subtotal...
I don't want a column of zeros strewn across my page, so I found a simple bit of javascript online render the fields blank when valued at zero:
if (event.value == 0) {
event.value = ''
My 'working' knowledge of javascript is limited at best... but that seems to do the job nicely. The next problem arises when I then try to format these fields as currency.
The simplest way to do this is through the format tab in the field properties, but doing so seems to remove the formatting applied through scripts since that would be a different formatting option.
So it would seem if I'm going to use a script to render the feilds blank, I'll also need to use a script to format the feilds as currency?
Any suggestions?
Thanks

Ah ha! Always nice when the solution is simpler than expected.
Working perfectly now, thanks!

Want to replace default calculator with third party calculator

I have a Z22. I like the calculator in Ultrasoft Money, specifically the ability to "X" out of the calculator and remain in the program. Is there a way to make the Money calculator the default calculator? I have set the hot sync button to access calculator. It pulls up the Money calc while in Money, but the Palm calc in all other aps.
Post relates to: Palm Z22

Ok, then this cannot be done. You can get a calculator program installed by itself but not have one inside of another program take over the one that is provided on the OS.
My recommendation is to find a Calculator program the same as or as similar you can get it to be that like the one inside Ultrasoft Money.
Post relates to: Treo 800w (Sprint)

What is the Default data format for calculations???

When we create a calculation based on data points(dp) like :
SUM(dp1 + dp2)
then what Number format is applied to the calculation by default, especially the number of digits that it can show.
Is there any rule related to that in Oracle?

ok Guys, i finally found the answer. By default a calculation can show up to 10 digits of number with 2 decimal points & this issue has discovered a new Bug in all the versions of Discoverer. Oracle is going to create a bug on this issue soon.
Thanks

Default value at Account Object Field setup

Hi,
How to give default value as ‘On Demand’ for the Source field at the time of Account creation and also we need to bypass this default value if the channel is web service and data import. This default should only effect if it is being done from OD UI.
I added below expression in DefaultValue
([<IndexedPick5>] = LookupValue("OCC_INDEX_CUST_LOV_ACCOUNT_5","On Demand")) AND (ExcludeChannel(‘Web Services’)) AND (ExcludeChannel(‘Import’))
but it giving an error as below when clicking New button in Account Object:
1] An error occurred calculating the default value for field 'Indexed Pick 5' in business component
'Account'.(SBL-DAT-00412) [2] Could not evaluate expression 'Expr: 'LookupValue([<IndexedPick5>],"On Demand") OR (ExcludeChannel(‘Web Services’))'' for field 'Indexed Pick 5' in business component 'Account'.(SBL-DAT-00394) [3] CSSString doesn't support operator 'OR'(SBL-DAT-00479)
Thanks
Bob

Try the following.
IIf(ExcludeChannel(‘Web Services’) or ExcludeChannel(‘Import’), 'On Demand', '')
Cheers!
Shilei G

Prompt date value with default max from table1.column1

Hi all,
How do I prompt user for date of report with default date = max(table1.column1) ? Give me some example of syntax pls.
Thanks ahead.

hi,
Default Date for the Date Prompt can be Static but not dynamic in WEBI.
Because we can't specify any object/calculation as default value for the prompt.
I think it's not possible in WEBI.
Regards,
Vamsee

Selection on Global Calculated Key Figure problem

Hi all,
I've got a Calculated key figure, made up of 2 key figures and 2 restricted key figures, saved to a homogenous multiprovider (Customer Sales). this works fine as is.
However, when you create a selection in BEx QD, that limits the CKF further by Distribution channel, and view the result, the result seems to be multiplied by a value to the effect of 2.8???
If you view the CKF by itself its fine (though not limited to what it needs to be).
As an example.
Say sales for a distribution channel was 1 million dollars. Sales overall was 2 million dollars. If i drag in my CKF (and have NO characteristics), it comes up with 2 million dollars.
If i limit it to 1 sales office, no issues, I get that sales office's value. However, if i limit it to a distribution channel, i get roughly 2.8 million dollars.
Any ideas? I can't see the logic in this. Perhaps someone knows of the issue/has seen a note or something regarding this, cos its got me scratchin my head?
Cheers

Hi Pierre,
I appreciate the fast reply. This thing is driving me nuts!
Ok so when you refer to the CKF are you referring to the global CKF on the multiprovider or the CKF i have on the report that is restricted (basically a local RKF)?
I've had a look through there and have found the calculation tab, but can't really say i've found "Calculate according to current formula".
What i see are:
a dropdown list headed "calculate results as..." (nothing defined)
another dropdown list called "calculate Single Values as..." (nothing defined)
a tick box called cumulated (unticked)
another tickbox called "also apply to results" (unticked)
another dropdown listbox called "calculation direction" (default setting)
Underneath all that is a tickbox called "use precalculated value" (unticked).
is it something under all that that i need to change?
Do i change the global CKF or the local RKF?
Thanks for the assist.

Product Variance Calculation

Gurus,
How do we calculate Product variance?
What is the procedure / process?
Where can the effect be seen?
Edited by: Bhatia on Oct 15, 2008 6:44 PM

Hi,
Variance Calculation
As long the production order is not fully delivered or flagged Technical Complete the remaining order balance is treated as WIP. Otherwise the order balance shows up in variance calculation.
If a lot-based product-controlling WIP, is valuated at actual costs. The WIP is calculated as the difference between the debit and credit of an order as long as the order does not have the status DLV (delivered).
In lot-based product controlling the variances are not calculated until the order has the status DLV (finally delivered) or TECO (technically completed). This means that at the time the order has reached this status, the system no longer interprets the difference between the debit and the credit as work in process but as a variance. In lot-based product controlling orders never have work in process and variances at the same time.
Variance calculation compares the actual costs incurred for the production/process order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
In this way you can find out which variances occurred between the value of the delivery and the actual costs and you can find the reason for the posting to the price difference account for materials with standard price control.
Variances from production (target version 1)
Variance calculation compares the actual costs incurred for the production order with the target costs for the production order and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variances occurred between the time the production order was created and the end of the production process.
Variances from planning (target version 2):
Variance calculation compares the planned costs for the production order with the target costs according to the standard cost estimate for the finished material, and assigns the individual variances to variance categories. The target costs are calculated using the quantity delivered for the order.
This enables variance calculation to find out which variance occurred between the time the standard cost estimate was created and the time the production order was created.
Variance categories:
The system assigns every variance to a variance category. The variance category indicates the cause of the variance (such as price change, lot-size variance). Variances are updated to the information system and passed on to Profitability Analysis according to variance category.
You differentiate between variance categories on the input side and on the output side:
u2022     Variances that occur because of goods issues, internal activity allocations, overhead and G/L account postings are displayed on the input side. Price variances, quantity variances, resource-usage variances and input variances are displayed on the input side.
u2022     Variances that occur because too little or too much of the planned order quantity were delivered, or because the delivered quantity was valuated differently are displayed on the output side.
Variances on the output side occur when you deliver using a price that differs from that found by dividing the target costs and the delivered quantity. If you deliver using the standard price, a variance can occur when the order lot size differs from the costing lot size. This is displayed as a lot-size variance.
For config
3.1.4.2     Variances & Settlement
Variance Calculation determines differences between the actual costs incurred on a production order and the standard costs of the material produced. Variances are calculated not at once, but for different variance categories. The variances computed are then transferred to CO-PA.
3.1.4.2.1     Define Default Variance Keys for Plants
Use
The Variance Key is part of the order header and controls variance calculation. The system selects the value set by this step as default value when a material master is created. From the material master the variance key then is transferred to the order when an order for the material is created.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKVW
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation -> Define Default Variance Keys for Plants
2.     Make the following entries:
Plant     Variance Key
BP01     000001
BP02     000001
BP03     000001
BP0X     000001
3.1.4.2.2     Define Target Cost Versions
Use
The target cost version controls various parameters related to calculation of target costs in variance calculation. In variance calculation, target costs are needed as a comparison to the actual costs incurred.
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     OKV6
IMG Menu     Controlling Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period End Closing  Variance Calculation  Define Target Cost Versions
2.     Choose New entries and enter the following values or copy from default settings of CoArea 0001 to BP01:
CoArea     TgtCostVsn     Text     Variance Variant     Control Cost     Target Cost
BP01     0     Target Costs for Total Variances     001     Actual Costs     Current Std cost Est
BP01     1     Target costs for production variances     001     Actual Costs     Plan Costs / Preliminary Cost Estimate
BP01     2     Target costs for planning variances     001     Plan Costs     Current Std cost Est
3.1.4.2.3     Create Settlement Profile
Use
The settlement profile controls various parameters related to settlement.
Prerequisites
Allocation Structure
Procedure
1.     Access the activity using one of the following navigation options:
Transaction Code     SPRO
IMG Menu     Controlling  Product Cost Controlling  Cost Object Controlling  Product Cost by Order  Period-End Closing  Settlement  Create Settlement Profile
2.     Choose New Entries and enter header data. Then for each new entry choose Details and enter remaining data.
3.     Overview of data records:
Profile     Text
YGPI00      BP Process Order w/o CO-PA
YGPP00     BP Production Order w/o CO-PA
YGPI00     YGPP00
Actual costs/costs of sales
To be settled in full     X     X
Can be settled
Not for settlement
Default Values
Allocation Structure     A1     A1
Source Structure
PA Transfer Struct.
Default object Type
Indicators
100% Validation     X     X
%-Settlement     X     X
Equivalence Nou2019s     X     X
Amount Settlement
Var. to co. bsd. PA
Valid receivers
G/L account     N     N
Cost center     O     O
Order     O     O
WBS Element     O     O
Fixed asset     N     N
Material     O     O
Network     N     N
Profit. Segment     N     N
Sales order     O     O
Cost objects     O     O
Order item     O     O
Business proc.     N     N
Real est. object     N     N
Other parameters
Document type      SA     SA
Max.no.dist.rls     3     3
Residence time     3     3
You have to assign Variance Key in material master for semi-finished and Finished goods in costing 1 tab also.
To Execute
KKS1-Collective Variance calculation
KKS2-Individual Variance calculation
CO88-Collective settlement
KO88-Individual settlement
Thanks,
Rau

Teerms of payment

Dear SAPpians.
by customizing the terms of payment we should check on the Account type Tab the buttons customer and vendor. My 1st question is why should we check Vendor although we are dealing ith terms of pyment only for the customer. The 2nd question is why is the meaning of fixed days and additional months? what is the purpose of iving datas in those boxes?
Thanks for replying

Dear Yves
In normal circumstances, it is not necessary to check both the boxes. It is enough if you check the box for Customer.
In some companies, one payment term will be used both in sale order and PO which means, it is applicable both to customer and vendor. So in such cases, the payment term should have been checked for vendor also.
With regard to Baseline date calculation, by default, FI people will select "Document date" which means, the payment term will be effective from billing date. Alternatively, if you want to calculate differently and if you maintain some day here, the system overwrites the day of the baseline date for payment of the line item.
thanks
G. Lakshmipathi

Enhancement in ME22N

Hi All,
         There is requirement to enhancement in Release strategy (ME22N). If user increase the OP price the release strategy being changed but he decrease the OP the price release strategy not being changed. The reauirement is there if they make any change in OP price either incrase or decrease, release strategy should be change. therefore there is any User-Exit or BADI which change the release strategies related informantion. I have aslo tried some user exit and BADI but in these exit and BADI the OP header information not in export parameters (this information is import parameters) so I can not make change it. there is any other user exit or BADI for do that.
Thanks in Advance
Jitendra Singh

I need to make some fields output only at item level
> in transaction ME22N i.e. during PO change. Is there
> any exit or BADI available for that.
>
> Regards
This is mainly config.
Check in SPRO - IMG
Materials Management > Purchasing > Purchase Order > Define Screen Layout at Document Level
Also these BAdis are available:
ME_PROCESS_PO_CUST - For Custom logic in Enjoy transactions
ME_GUI_PO_CUST - For Additional Custom screens in ME2xn
Read the documentation, it will help.
Also, read the config section about enhancements in Purchasing using old enhancement technology. See below.
OSS is also a good place for documentation. OSS 496083.
Good luck!
Leonardo De Araujo
Develop Enhancements for Purchasing
     In this step, you develop enhancements for Purchasing.
     The following SAP enhancements are available for the Purchasing area:
     o   AMPL0001
         User subscreen for additional AMPL data (Manufacturer part number)
     o   LMELA002
         Adoption of batch number from shipping notification at time of
         posting of a goods receipt
     o   LMELA010
         Incoming shipping notification: adoption of item data from IDoc
     o   LMEQR001
         User exit for source determination
     o   M06B0001
         Role determination for release of requisitions
     o   M06B0001
         Changes to communication structure for release of requisitions
     o   M06B0003
         Number range and document number
     o   M06B0004
         Number range and document number
     o   M06B0005
         Changes to communication structure for overall release of purchase
         requisitions
     o   M06E0004
         Changes to communication structure for release of purchasing
         document
     o   M06E0005
         Role determination for release of purchasing documents
     o   ME590001
         Grouping of requisitions for PO split in transaction ME59
     o   MEETA001
         Determination of schedule line type (backlog, immediate requirement,
         forecast)
     o   MEFLD004
         Determination of earliest delivery date for checking at time of
         goods receipt (PO only)
     o   MELAB001
         Generation of forecast delivery schedule: realization via creation
         profile
     o   MEQUERY1
         Enhancement for document overview ME21N / ME51N
     o   MEVME001
         Calculation of default GR quantity and over/underdelivery tolerances
     o   MM06E001
         User exits for inbound EDI messages and outbound purchasing
         documents
     o   MM06E003
         Number range and document number
     o   MM06E004
         Control of import data screens in purchase orders
     o   MM06E005
         Customer fields in purchasing documents
     o   MEREQ001
         Customer's own data in purhcase requisitions
     o   MM06E007
         Change document for requisitions when converting into POs
     o   MM06E008
         Monitoring of contract target value in case of release orders
     o   MM06E009
         Relevant texts for "Texts exist" indicator
     o   MM06E010
         Field selection for vendor address
     o   MM06E011
         Activation of requisition block
     o   MM06L001
         Exits for determination of ratings in vendor evaluation
     o   MMAL0001
         ALE source list distribution: outbound processing
     o   MMAL0002
         ALE source list distribution: inbound processing
     o   MMAL0003
         ALE purchasing info record distribution: outbound processing
     o   MMAL0004
         ALE purchasing info record distribution: inbound processing
     o   MMDA0001
         Default values for delivery addresses
     o   MMFAB001
         User exit for generation of releases
     o   MRFLB001
         Control items during release creation
     o   LWBON001
         Enhancement of LIS update through extension of the communication
         structure MCKONA (business volumes and rebate income)
     o   LWBON003
         Change settlement data for end-of-period rebate settlement before
         creation of settlement documents
     o   LWSUS001
         Customer-specific source determination in Retail
     Activities
     1. Either create a new project or use an existing one and then enter
         the enhancement.
     2. Activate the project
         Your enhancement will only become effective after activation.
     Further notes
     In contrast to modifications, enhancements are basically
     release-insensitive since they are not implemented in the SAP original
     but in a name range that is reserved for the customer.
     The general procedure for creating enhancements can be found in the
     enhancement transaction at Help -> Application help.
     If you want to display the documentation for an enhancement, choose Goto
     -> Documentation in the enhancement transaction.
Return ->
     Application

Manually entering pixel dimensions

Having some measurement units confusion here.
Illy CS5
For the sake of a clean test: (and not how I normally work, but just to help rule out any file setting oddities) I create a new doc, using the New Document Profile: Print.
Select Rectangle Tool, click on artboard, type in 300px for width. ENTER.
In inches, it measures as 4.1667in. Why?
I expect it to be precisely 1in.
Also, if I punch in 300pt, it comes out to be 4.1667in as well.
I'm lost.

Illustrator assumes 72 ppi when converting units of measure on the rulers and transform controls and this it is the same for raster images and raster effects regardless of their native resolution which will be used when printing, exporting, and for displayed detail on the monitor like when zooming in. So, you can have a raster image with 1 x 1 inch with native resolution of 300 or any other ppi but illustrator will always show it as 72 ppi on its ruler and transform controls. The native ppi of raster images is displayed on the control bar and the raster effects settings can be checked under the Effects menu. Illustrator also uses the 72 ppi assumption for calculating the default image size when you use Save for web and devices and also when you use 100% zoom - for display purposes it rasterizes on the fly the vector on screen at 72 ppi in the same way if you choose Pixel Preview from the View menu and it fits one pixel from the document to one monitor pixel. If you happen to have a monitor from the last century with monitor pixel density of 72 ppi you will also have that 1 x 1 inch image or object as large as one real size inch. My monitor has 109 ppi and this makes the Illustrator inches at 100% zoom (Actual Size from View menu) very tiny for me.

PLEASE HELP REGARING VBOF A S AP

Hi,
     I have to update the rebate agreement for a particular customer from 01.01.2007 to tilldate.I tried to do it in VBOF ,But I am getting a message after entering everything and executing "list contains no data".I have no cule how to go about it.Please let me know what to do in the screen and where to see the output.I have never done it before.Please help me.Please advice me what to enter in each field.What I am entering now is ,Rebate agreement Number,Rebate Recipient,Valid to date(Do we have to give todays date or the rebate agreement valid to date?),Posting date(Do we have to give todays date ? or actual billing document posting date?) and in error tab do we have to select drilldown option?Please advice me.This is very urgent.
Regards
Ram

dear aram
pleaes gothrough this
REBATES
Rebates are special kind of discounts that area paid to the customer on certain sales volume. Rebates are paid after rebate agreement period.
ex : one year the customer should purchase specified if he purchased that specified sales value then only to be rebates are going to be paid by raising credit memo.
Configuration Settings:
     Activate three controls
Check the rebate processing active at the time of defining sales organization
Activate check result at customer master pair
Activate check relevant for rebate whole defining to billing document type Ex : F2
Including Condition Type, BO02 with, subtotal =7, requirement = 24 and accounting key = ERB, Accrual Key = ERU, in V/08 B/N, Discount or after total discount value we have to put after discount value if we use rebate basis.
(Requirement 24 excludes rebate condition type during sales order processing and including during the billing process)
Create Rebate Agreements (VB01):
Path: Logistic S&D  Master Data  Rebate Agreement  Rebate Arrangement  VB01 Create
Specify Rebate Agreement   ex: 0002 Material Rebate
Inter, Specify the description, Rebate Recipient (Customer Payer), Currency Validity Period
Agreement Status: Open & Verification levels
F- Do play totals by payer material
*Click on Conditions maintain Sales Trees, Customer number, Material Number, Validity Period, Amount.
*Select Condition line item, 40 to Scales maintain scales, save it.
*note down the Rebate Agreement Number.
 Define Rebate Agreement Type:
Path: Img  S&D  Billing  Rebate Processing  Rebate Agreement  Define Agreement type  Define Agreement types
Choose Rebate agreement 0002 go to Details icon and maintain data as below
*Default Values
 Proposed Valid from: Specify the beginning validity date which system automatically proposes. Ex: to days date
 Proposed valid to: the value of this field proposes how long this rebate condition record should remain in force. Ex-2
 Payment method: The value of this field determined how the payment going to be made ex: Cheque or cash etc.
->Default Status: It specifies Default status of the rebate agreement. The system automatically proposes when you create a rebate agreement. Ex: Open
Control Data:
 Verification level: ex F Display total by payer/material
It how the information should be displayed or printed out for a Rebate Agreement.
 Check different Validity periods
It specifies whether condition Records within Rebate Agreement must have exactly the same validity period as an agreement itself.
Manual Accruals order type R4 (B4):
     Specify the sale doc type R4 when we perform manual posting of accruals for agreement.
Ex: when the ;business wants to put worth of certain amount of product as a front of store display then business pays 10000 then business has to post this 10000 as accruals, system automatically creates credit memo request of this document type(R4).
 Check Manual Accruals: Accruals this field if you want to post manual accruals for this agreement.
Manual Payment:
Payment Procedure: A Payment allowed up to accruals valid.
Specify the value, if you want to allow manual payment for a Rebate Agreement To indicator specifies the amount which can be paid by using this indicator we can limit the manual payment to be the amount of accruals posted for each Rebate condition records when normal payment is carried out creation of credit memo. When system carried out final settlement all partial payments are taken into account.
 Partial Settlement: R3 (B3)
Specify order type that should be used when we perform costing settlement for the Rebate Agreement. Ex: Customer wants partial Settlement for the Rebate Agreement, and then system uses this document type to settle the partial payment.
Note: That request must be approved before creating the credit memo.
Prerequisite: Make sure that in VOV8 R3 (B3) the Billing type field contains appropriate partial settlement value B3
Check Reverse Accruals
     Check this field when we want accruals to be reversed when manual payment is made for Rebate Agreement.
Use: System reverses the Accruals for the amount for manual payment. If the Cumulative Accruals are not sufficient then the system Reverse the accrual amount to which that system.
Settlement: Final Settlement B1
Specify the Sales doc type that system uses as a default when final Settlement Takes places.
Correction: B2
     Specify doc type B2 the System automatically uses to convert the Value. Ex: Sales Volume on which Rebates is based. If the business has to create a condition record with staring date that is in the past, then the system needs to adjust the sales revenue of the customer, then system has to take the invoice that were processed but the retroactive starting date of the condition record and the actual date on which we enter the Rebate Agreement.
Minimum Status: B Agreement released for settlement
It specifies the minimum status that Rebate Agreement must have before the settlement an be calculated by default it B
 Save it, and Exit
Activate Rebate Procedure infrastructure: (S136):
To update daily sales orders with synchronize updating.
Path Img  Logistic general  LIS  Logistics date warehousing  Updating  updating Control  Activate updates  S&D  S136
Double click on S136 and select Synchronous updating in pop up box
 Save it
 Double Click SD60, Select Day & with Synchronous updating in pop up box
 Save it
Go to OVA2 Assign sales document types B, B1, B2, R3, R4 to sales Area
Go to VA01, VL01N, and VF01raise the sales order billing doc for 2 times and note down the document numbers.
VA01: Go to Price condition screen & check rebate condition type Boo2 has been activated or not.
Go to Change mode of the Rebate agreement (VB02). Note down the message as system unable to update sales volume in the Rebate agreement we have to run the program SDBONT06 in SE38 Transaction Code. Click on Execute(F8) maintain Selection screen like Rebate Agreement number Rebate Recipient number, Sales Area, & check to error, check drill out, uncheck test, check changed agreement, click on execute.
rewards pls
siva

Plant wise trail balance

Friends,
My client want to see the Plant Wise balancesheet.
Please suggest me how should i configure for this.
they want to see plant wise balancesheet like how we get in f.01.
I will assign full points to all of you.
Thank you.
Regards,
Reva Naik

hiii
In most of the cases SAP facilitates reporting as Business area wise , we have to define Business areas for plant wise , then u will get reports according to Business areas .
In most of the cases Bus. Area = Plant = Profit Segment
Hope ur problem will b solved
can u tell me the confg of TB in Financial Statement Vetrsion ( OB58 ) , i tried the confg of TB but system is calculating Profit defaultly , i didn't assign any GL Acct also... is there any provision to configure TB as per Client's grouping....
help me
regards
ramki

Batch number as po number

hello all,
i have a requirement like in place of batch number i need to print po number either while creating po or while shiipping so i need the exit for that .

Hi,
Please search for the correct Exit below and use.
I am sure using an EXIT we can do this.
Develop Enhancements for Purchasing
In this step, you develop enhancements for Purchasing.
The following SAP enhancements are available for the Purchasing area:
AMPL0001
User subscreen for additional AMPL data (manufacturer part number)
LMELA002
Adoption of batch number from shipping notification at time of posting of a goods receipt
LMELA010
Incoming shipping notification: adoption of item data from IDoc
LMEQR001
User exit for source determination
M06B0001
Role determination for release of requisitions
M06B0001
Changes to communication structure for release of requisitions
M06B0003
Number range and document number
M06B0004
Number range and document number
M06B0005
Changes to communication structure for overall release of purchase requisitions
M06E0004
Changes to communication structure for release of purchasing document
M06E0005
Role determination for release of purchasing documents
ME590001
Grouping of requisitions for PO split in transaction ME59
MEETA001
Determination of schedule line type (backlog, immediate requirement, forecast)
MEFLD004
Determination of earliest delivery date for checking at time of goods receipt (PO only)
MELAB001
Generation of forecast delivery schedule: realization via creation profile
MEQUERY1
Enhancement for document overview ME21N / ME51N
MEVME001
Calculation of default GR quantity and over/underdelivery tolerances
MM06E001
User exits for inbound EDI messages and outbound purchasing documents
MM06E003
Number range and document number
MM06E004
Control of import data screens in purchase orders
MM06E005
Customer fields in purchasing documents
MEREQ001
Customer's own data in purchase requisitions
MM06E007
Change document for requisitions when converting into POs
MM06E008
Monitoring of contract target value in case of release orders
MM06E009
Relevant texts for "Texts exist" indicator
MM06E010
Field selection for vendor address
MM06E011
Activation of requisition block
MM06L001
Exits for determination of ratings in vendor evaluation
MMAL0001
ALE source list distribution: outbound processing
MMAL0002
ALE source list distribution: inbound processing
MMAL0003
ALE purchasing info record distribution: outbound processing
MMAL0004
ALE purchasing info record distribution: inbound processing
MMDA0001
Default values for delivery addresses
MMFAB001
User exit for generation of releases
MRFLB001
Control items during release creation
LWBON001
Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)
LWBON003
Change settlement data for end-of-period rebate settlement before creation of settlement documents
LWSUS001
Customer-specific source determination in Retail
LMEXF001
Conditions in purchasing documents without invoice receipt
LMEKO002
Enhance communication structure KOMP for price determination
If you need BADI's search for them in SPRO
MM-> Purchasing->Business Add-Ins' for Purchasing.
Regards,
Anji

PO title change by using user exit

Hello friends,
I would like to change the Purchase order title depends on some conditions in one user exit .
Could you please suggest me any user exit or tell me the procedure to do that change.
Thanks in advance.
Arvind.

Hi,
check the following exits
M06B0005
Changes to communication structure for overall release of purchase requisitions
M06E0004
Changes to communication structure for release of purchasing document
M06E0005
Role determination for release of purchasing documents
ME590001
Grouping of requisitions for PO split in transaction ME59
MEETA001
Determination of schedule line type (backlog, immediate requirement, forecast)
MEFLD004
Determination of earliest delivery date for checking at time of goods receipt (PO only)
MELAB001
Generation of forecast delivery schedule: realization via creation profile
MEQUERY1
Enhancement for document overview ME21N / ME51N
MEVME001
Calculation of default GR quantity and over/underdelivery tolerances
MM06E001
User exits for inbound EDI messages and outbound purchasing documents
MM06E003
Number range and document number
MM06E004
Control of import data screens in purchase orders
MM06E005
Customer fields in purchasing documents
MEREQ001
Customer's own data in purchase requisitions
MM06E007
Change document for requisitions when converting into POs
MM06E008
Monitoring of contract target value in case of release orders
MM06E009
Relevant texts for "Texts exist" indicator
MM06E010
Field selection for vendor address
MM06E011
Activation of requisition block
MM06L001
Exits for determination of ratings in vendor evaluation
MMAL0001
ALE source list distribution: outbound processing
MMAL0002
ALE source list distribution: inbound processing
MMAL0003
ALE purchasing info record distribution: outbound processing
MMAL0004
ALE purchasing info record distribution: inbound processing
MMDA0001
Default values for delivery addresses
MMFAB001
User exit for generation of releases
MRFLB001
Control items during release creation
Regards,
Padmam.

LC2 calculated by default

Similar Messages

Maybe you are looking for