USER EXIT/ BADI (The price should not be changed in the billing document)

Hi all,
We have given manual entry provision for pricing in Sales order level. But as per the company requirement, the price should not be changed in the billing document. Also the point to be considered is, it is a delivery based billing.
Kindly help me for finding USER EXIT/ BADI to achieve my requirement.
Thanks.

Hi,
Please refer to OSS notes:
105621 - Authorization check for the condition screen - you can use following user-exit includes for changing the condition tab to display only:
    USEREXIT_FIELD_MODIFICATION
    USEREXIT_PRICING_CHECK
    USEREXIT_FIELD_MODIFIC_LEER
    USEREXIT_FIELD_MODIFIC_KZWI
    USEREXIT_FIELD_MODIFIC_KOPF
1165078 - Authorization check for conditions or subtotals - from ECC6.0 EHP4 there is a dedicated BAdI for authorization check, however if the user is not aurhorized to change the conditions, the conditions are not visible for the user as well.
Regards,
Marcin

Similar Messages

User exit/ badi needed for planned order create/change,collective ATP check

Dear All,
I'm looking for a user exit/ badi which can be used for planned orders at the stage of
mass collective availability check (COMAC tcode) update; or at some other relevant stages of mass update of planned orders.
I need after collective availability check to perform the following:
1) to copy date from "total comitment" field on header tab of planned order and paste it (replace old date) to order finish date on header screen
then
2) to start a scheduling.
Very appreciate your help.
Best Regards,
Andrey
Edited by: Andrey Kruglov on Apr 15, 2010 3:06 PM
Edited by: Andrey Kruglov on Apr 15, 2010 3:07 PM

Dear,
Use the BAPI : BAPI_PLANNEDORDER_CHANGE
Or use the function module MD_SET_ACTION_PLAF for Schedule planned order.
and the transaction MDAC Execute action for planned order
This function module includes the following actions:
Explode BOM
Explode BOM, check availability
Check availability, only explode BOM in the case of a requirement
Check availability, do not explode BOM
Reset availability
Change planned order data
Schedule planned order
Delete planned order
Assign the key for the respective action control to the materials in the material master (MRP 4 view).
Please refer this thread,
Re: MDVP for collective orders
Regards,
R.Brahmankar

Adopted Info record price should not be changed in PO

Dear All
I do have a requirement that, my company wants to maintain info records for each vendor price combination, and wants user should not change adopted prices/conditions etc in PO while creating the PO.
Can this be possible without doing any ABAP coding using BADI?
Thank you

HI,
Its possible by MM configuration in Condition type ( PBXX or PB00).
What u want to do is In the conition type T.Code :M/06
Under the Changes wich can be made tab, thaer is
Manual entries , Plz give' D' in the tab , that means manual entries not possible.
Hope it clear,
Regards,
Andra

User Exit/BADI for Sales Order Line Partner Change

I am looking for a user exit or BADI which gets triggered when partner function of a sales order line is changed.
My detailed requirement is-We have created a new Partner Function - END CUSTOMER(EC). Requirement is to trigger a business logic whenever the End Customer partner function is changed from its default value to anything else.
If you have any suggestions please let me know.

Hi
have a look at function module EXIT_SAPLV09A_004 .
Cheers

Price should not be in changable during billing

Dear All,
During sales order user enters the price manually since condtion type is manual. And during billing
the user can change the price because it is in display mode. Please suggest how to restrict price changes in billing.
Regards,
ramesh

Hai,
For this, you can ask your Abaper to make the Pricing conditions in a display mode.
Alng with that make the Insert Row, Delete Row and UPDATE icons also as Display.
Since you mentioned you gave the price as a Manual entry, I want to share SAP standard functionalities.
If you don't make it as Display,
1. An User can change the sales order price and at the time of Billing he can Update all the price as per the Sales order.
2. As per Standard SAP an manual entry can be included in the pricing any number of times.
3. If any discount is given then by mistake discount can be given twice.
General advice, maintain price in the condition record and let it flow only from master.
Regards,
Mani

INFORECORD PRICES SHOULD NOT BE CHANGED IN PO

Sir,
INFORECORD PRICES SHIOULD NOT BE ABLE TO CHANGE IN PO.
REGARDS
AMEY

Hi,
I think you need to check on all possibilities here.
1. Is your requirement for all kind of PO's (direct spend, indirect spend, STO's....). If it is for all, then when you have new material to be purchased how does it pull in the price (if in case no inforecord exists)...check this.
2. If your requirement is only for few kind of purchases, then you need to limit it with the document type.
Your requirement could be achieved through function authorization for buyers and maintaining the parameter id for the buyers to restrict them with the access. Check if you have used parameter id for any other purpose.
Please clarify your business requirement elaborately.
Sk.

Pricing should not be changed in billing document?

HI,
We have given manual entry provision for pricing in Sales order level . But as per the company requirement, the price should not be changed in the billing document. Also the point to be considered is, it is a delivery based billing. What is the configuration required to ensure that , System should not allow pricing to be changed in billing document when it is getting created.
I have checked the forum and found no threads linked to it. Kindly help me in this regard.
Thanks in advance
Rgds,
Sivarajesh. J

Hi ,
In SPRO -> S&D-> Billing Documents ->Maintain copying Control for Billing documents. Here select for copying control for ( based on your case) delivery type to Invoice type (Eg: Invoice type F2: Delivery type : LF) and then go to Item and select Item Category.
And then go to Item Category details (Eg: TAN) . Here you find Pricing type and based on your requirement you can select. If not satisfying your need then you can modify the copying requirement.
Thanks,
Veerendra

Need the user exit/BADI name for Reverese order MIGo- ME21N(changing item)

Hi
I have the below requirement.
I am changing the item details in the transaction MIGO transaction,the value of MSEG entries
are got changed.and also it should change in the Purchase order level also(in the table EKKO).
Can anybody tell me the User Exit /BADI name which is triggered in the Reverse order
i.e MIGO -> ME21N.So that i can implement my code in the reverse order in the User Exit/BADI.

hi I did not find any paramater type EKPO in the Exporting or changing of any methods in the BADI's given by you...........

User Exit / BAdI to update the pricing conditions of the Purchase Order

Hello SAPients,
This is my requirement:
"Copy the Pricing Conditions from the Shipment Cost Document (VI01 / VI02) to the automatically generated Purchase Order".
I'm using the enhancement V54U0002 (Function Module EXIT_SAPLV54U_002) to EXPORT the values of the Pricing Conditions to memory and I have used the enhancement MM06E005 ( FM EXIT_SAPMM06E_006, 007, 012, 013, 014, 016, and 017) to IMPORT the values from memory and store them in TKOMV. But, when the PO is generated the values don't stay, they are always changed with the standard PBXX pricing conditions.
My question is: Does anyone know the User Exit / BAdI that I can use to change the Pricing Conditions of the Purchase Order?
<<removed_by_moderator>>
Thanks!
Edited by: Vijay Babu Dudla on Jan 14, 2009 11:08 PM

>
kartik tarla wrote:
> check this badi
> ME_PROCESS_PO_CUST
>
> and the following user exit
> Goto-> include RV61AFZA then search for
> USEREXIT_PRICING_RULE see if its helpful to u.
Hello Kartik / SAPients,
I tried with ME_PROCESS_PO_CUST but didn't work. The system doesn't execute that code. Any other idea would be greatly appreciated.
Thanks.

User Exit/ BADI to validate input in LT06

Dear Gurus,
I would like to ask what user exit/BADI i could use to validate or check the input value before creating the material document in LT06?
I have tried MWMTO001 and put break point inside FM EXIT_SAPLL03T_001, but the break point is not called.
Thanks a lot.

Hi Shirley,
If you get the proper place where you need to add your code then best option is, you can findout implicit enhancement for this and add your code in inside implicit part.
every screen having PBO and PAI part , you can try to add your code in PAI part.
Note: for this BAdI definition WM_ENHANCMENT implementation, need to sap access key and remove tick from BADI definition but I don't think this is right option.
Regards,
Prasenjit

User Exit/ Badi for Changing Quant parameters during TO Creation

Hi Gurus,
Could you please guide me to advice the User Exit/Badi which can be used for changing Quant Data during TO Creation.
User Requirement: Using "Recepient Field" in MIGO as a Key Value for FIFO in WM during goods issue. Receipient is copied into TR and TO (Standard SAP Functionality). For the purpose of Stock Removal based on Receipient Value, we need to copy this value into Quant Data field named Certificate Number ("LQUA-ZEUGN").
I will highly appreciate reply from Gurus.
Regards,
Gupta M

Hi manish,
Use the Exit MWMTO001 for this purpose and modify the table accordingly. This will solve your problem.
Thanks,
Shibashis

In Billing doc Base price should not change where as in SO system allow

Hi
I have one requirenment the Base price (ZPR0) should pick automatically from condition records and system should allow to change ZPR0 in Sales Order item level , where as it should be Grey mode in billing document item level.
1. In the condition type ZPR0 i had maintainted as NO LIMITATION and in copy controls of VTFL the pricing type as" D"
so system is allowing to change the base price at both Sales order & billing doc level.
my requirement is System should allow to change the price manually in Sales order and at billing document it should be in grey mode, so that no user cannot change the price at billing level.
Regards,
Satya

Hi ,
Create transaction varient for vf01 and vf02 in SHD0 and assign it to Users.
Regards,
Suresh

Change in Useful life of asset in mid year, but the previous posted depreciation should not be changed

Dear Experts,
I have a requirement in one of my client, We need to extend the useful life of asset in mid of an asset fiscal year and the depreciation which was posted in the previous should not be changed.
Requirement:
Useful life of asset is to be extended after completing depreciation for 4 years and in-between the current asset fiscal year. Provided the present asset value has to be taken as the new book value of the asset and the depreciation posted henceforth to be posted based on the new asset value till the remaining useful life.
Previously posted depreciation should be unchanged.
Analysis:
1.      The fiscal Year followed - October to September.
2.      The useful life of asset will be changed, and the depreciated value posted till 31/mar 2014 will have the old depreciation value ( based on the original acquisition value)
3.      The Depreciation key used in of type LINR (linear), depreciation value will be calculated based on the Book value till the asset value becomes ZERO at the end of useful life of the asset.
4.      We can change the useful life of the asset at the end of a Asset fiscal year say FY- 2014, if this is done the existing configuration will take the Book value of the asset at the end of the Fiscal as the asset value and the new depreciation will be calculated based on the new useful life of the asset. The asset value will become ZERO at the end of the newly changed Useful Life.
5.      But the requirement is that the useful life of the asset will be changed exactly half way in between existing Asset fiscal (i.e., 31/03/2014), if this is done system will change the depreciation value based on the new useful life ( since the Dep Key is LINR), but the depreciation value will change from the fiscal start say October 2013 to September 2014 ), which will not satisfy the requirement of the client. Since the depreciation which is already posted from October 2013 to March 2014 should not be changed.
Note:
1. We are not willing to retire the asset and create a new asset with the remaining book value as asset value and start depreciation.
Kindly let me know if the requirement can be fulfilled without retiring the asset.

Dear All,
This requirement has been completed.
1. I created New Multi level valuation method with base 26 ( Net book value w/o Revaluation ).
2. New depreciation key was created and the above method was assigned to it. I never changed the Base method.
3. new interval was created in the depreciation area, with this created dep key and extended the useful life of the asset. The depreciation was calculated according to the requirement.
Originally the asset had useful life of 5 Years, I changed the asset useful life to 8 years now with new Depreciation key 2001.
Depreciation was already posted to the asset till 04- 2013 for an amount of 148.27 SAR.
Net Book value carried forward to 2013 = 1575.56 SAR
Depreciation already posted till 4th period =   148.27 SAR
Current Net book value after useful life extension           = 1427.29 SAR .
Now the new depreciation key 2001 with Multilevel method 201, will take this Net-book value as Asset value and will depreciate along the useful life of the asset till it becomes zero.
Planned depreciation of 2013 ( remaining 6 months) = 166.24 SAR
Planned depreciation of 2014 = 225.96 SAR
Planned depreciation of 2015 = 225.96 SAR
Planned depreciation of 2016 = 225.96 SAR
Planned depreciation of 2017 = 225.96 SAR
Planned depreciation of 2018 = 225.96 SAR
Planned depreciation of 2019 = 131.25 SAR
Total      = 1427.29 SAR ( the Asset value becomes zero at the end of its remaining useful life.
The previously posted depreciation from 01.01.2013 to 30.04.2013 was untouched.

To find out user exit/ badi for the VT01n transaction triggered in Save

Hi Friends,
I have the following requirement and for this appropriate user exit/ badi should be needed which will trigger during saving of the shipment.
Cass shipment type (VTTK-ADD03) field needs to be required and should be automatically populated upon creation of the shipment document. The rules for populating the value (SO, ST, PO and RA) are as follows:
If any of the orders on the shipment are customer order types, then the CASS shipment type should be a SO,
If all of the orders are STO orders, then the Cass shipment type should be "ST",
If all of the orders are PO orders, then the Cass shipment type should be "PO" , and
If all of the orders are customer return orders, then the Cass shipment type should be "RA".
I have tried with the 3 badi available and 7 to 8 user exit, but it won't work.
Thanking a lot in advance for giving the solution.
With Regards,
Ajit.

Hi,
This code will give you all the user-exits.
Code:
& Report ZPJA_PM002 (Ver4) &
& PJA Consultancy Services (www.pjas.com) &
& This report attmpts to find Enhancements, Program-Exits, BADIs &
& and Business Transaction Events in a particular program/tcode. &
& Other search options: &
& Program: RPR_ABAP_SOURCE_SCAN &
& FModule: &
& Text Elements: &
& P_DEVC Show user-exits from development class &
& P_LIMIT Limit submit program selection &
& P_FUNC Show function modules &
& P_SUBM Show submit programs &
& S01 Selection data (TCode takes precedence over program name) &
report zpja_pm002
no standard page heading
line-size 221.
data: tabix like sy-tabix,
w_linnum type i,
w_off type i,
w_index like sy-tabix,
w_include like trdir-name,
w_prog like trdir-name,
w_incl like trdir-name,
w_area like rs38l-area,
w_level,
w_fsel like sy-ucomm, " Determination of screen field
w_str(50) type c,
w_funcname like tfdir-funcname.
constants: c_fmod(40) type c value 'Function modules selected: ',
c_subm(40) type c value 'Submit programs selected: ',
c_col1(12) type c value 'Enhanmt Type',
c_col2(40) type c value 'Enhancement',
c_col3(30) type c value 'Program/Include',
c_col4(20) type c value 'Enhancement Name',
c_col5(40) type c value 'Enhancement Description',
c_col6(8) type c value 'Project',
c_col7(1) type c value 'S',
c_col8(12) type c value 'ChangeName',
c_col9(10) type c value 'ChangeDate'.
Work Areas: ABAP Workbench
data: begin of wa_d010inc.
data: master type d010inc-master.
data: end of wa_d010inc.
data: begin of wa_tfdir.
data: funcname type tfdir-funcname,
pname type tfdir-pname,
include type tfdir-include.
data: end of wa_tfdir.
data: begin of wa_tadir.
data: devclass type tadir-devclass.
data: end of wa_tadir.
data: begin of wa_tstc.
data: pgmna type tstc-pgmna.
data: end of wa_tstc.
data: begin of wa_tstcp.
data: param type tstcp-param.
data: end of wa_tstcp.
data: begin of wa_enlfdir.
data: area type enlfdir-area.
data: end of wa_enlfdir.
Work Areas: BADIs
data: begin of wa_sxs_attr.
data: exit_name type sxs_attr-exit_name.
data: end of wa_sxs_attr.
data: begin of wa_sxs_attrt.
data: text type sxs_attrt-text.
data: end of wa_sxs_attrt.
Work Areas: Enhancements
data: begin of wa_modsap.
data: member type modsap-member.
data: end of wa_modsap.
data: begin of wa_modsapa.
data: name type modsapa-name.
data: end of wa_modsapa.
data: begin of wa_modsapt.
data: modtext type modsapt-modtext.
data: end of wa_modsapt.
Work Areas: Business Transaction Events
data: begin of wa_tbe01t.
data: text1 type tbe01t-text1.
data: end of wa_tbe01t.
data: begin of wa_tps01t.
data: text1 type tps01t-text1.
data: end of wa_tps01t.
user-exits
types: begin of ty_mod,
member like modact-member,
name like modact-name,
status like modattr-status,
anam like modattr-anam,
adat like modattr-adat,
end of ty_mod.
data: w_mod type ty_mod.
types: begin of t_userexit,
type(12) type c,
pname like trdir-name,
txt(300),
level type c,
modname(30) type c,
modtext(60) type c,
modattr type ty_mod,
end of t_userexit.
data: i_userexit type standard table of t_userexit with header line.
Function module developmnet classes
types: begin of t_devclass,
clas like trdir-clas,
end of t_devclass.
data: i_devclass type standard table of t_devclass with header line.
types: begin of t_enlfdir,
area type enlfdir-area,
end of t_enlfdir.
data: i_enlfdir type standard table of t_enlfdir with header line.
Submit programs
types: begin of t_submit,
pname like trdir-name,
level,
done,
end of t_submit.
data: i_submit type standard table of t_submit with header line.
Source code
types: begin of t_sourcetab, "#EC * (SLIN lügt!)
line(200), "#EC * (SLIN lügt!)
end of t_sourcetab. "#EC * (SLIN lügt!)
data: sourcetab type standard table of t_sourcetab with header line.
data c_overflow(30000) type c.
Description of an ABAP/4 source analysis token
data: i_stoken type standard table of stokex with header line.
data wa_stoken like i_stoken.
Description of an ABAP/4 source analysis statement
data: i_sstmnt type standard table of sstmnt with header line."#EC NEEDED
keywords for searching ABAP code
types: begin of t_keywords,
word(30),
end of t_keywords.
data: keywords type standard table of t_keywords with header line.
function modules within program
types: begin of t_fmodule,
name like rs38l-name,
pname like trdir-name,
pname2 like trdir-name,
level,
bapi,
done,
end of t_fmodule.
data: i_fmodule type standard table of t_fmodule with header line.
& Selection Options &
selection-screen begin of block selscr1 with frame title text-s01.
parameter: p_pname like trdir-name memory id rid,
p_tcode like syst-tcode,
p_limit(4) type n default 100,
p_devc like rihea-dy_ofn default ' ',
p_func like rihea-dy_ofn default ' ',
p_subm like rihea-dy_ofn default ' '.
selection-screen end of block selscr1.
& START-OF-SELECTION &
start-of-selection.
if p_pname is initial and p_tcode is initial.
message e008(hrfpm). "Make entry on the selection screen
stop.
endif.
ensure P_LIMIT is not zero.
if p_limit = 0.
p_limit = 1.
endif.
perform data_select.
perform get_submit_data.
perform get_fm_data.
perform get_additional_data.
perform data_display.
& Form DATA_SELECT &
form data_select.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
destination 'SAPGUI'
keeping logical unit of work
exporting
text = 'Get programs/includes' "#EC NOTEXT
exceptions
system_failure
communication_failure
. "#EC *
determine search words
keywords-word = 'CALL'.
append keywords.
keywords-word = 'FORM'.
append keywords.
keywords-word = 'PERFORM'.
append keywords.
keywords-word = 'SUBMIT'.
append keywords.
keywords-word = 'INCLUDE'.
append keywords.
if not p_tcode is initial.
get program name from TCode
select single pgmna from tstc into wa_tstc-pgmna
where tcode eq p_tcode.
if not wa_tstc-pgmna is initial.
p_pname = wa_tstc-pgmna.
TCode does not include program name, but does have refereve TCode
else.
select single param from tstcp into wa_tstcp-param
where tcode eq p_tcode.
if sy-subrc = 0.
check wa_tstcp-param(1) = '/'.
check wa_tstcp-param+1(1) = '*'.
if wa_tstcp-param ca ' '.
endif.
w_off = sy-fdpos + 1.
subtract 2 from sy-fdpos.
if sy-fdpos gt 0.
p_tcode = wa_tstcp-param+2(sy-fdpos).
endif.
select single pgmna from tstc into wa_tstc-pgmna
where tcode eq p_tcode.
p_pname = wa_tstc-pgmna.
if sy-subrc <> 0.
message e110(/saptrx/asc) with 'No program found for: ' p_tcode."#EC NOTEXT
endif.
else.
message e110(/saptrx/asc) with 'No program found for: ' p_tcode."#EC NOTEXT
endif.
endif.
endif.
Call customer-function aus Program coding
read report p_pname into sourcetab.
if sy-subrc > 0.
message e017(enhancement) with p_pname raising no_program."#EC *
endif.
scan abap-source sourcetab tokens into i_stoken
statements into i_sstmnt
keywords from keywords
overflow into c_overflow
with includes.
if sy-subrc > 0. "keine/syntakt. falsche Ablauflog./Fehler im Skanner
message e130(enhancement) raising syntax_error. "#EC *
endif.
check I_STOKEN for entries
clear w_linnum.
describe table i_stoken lines w_linnum.
if w_linnum gt 0.
w_level = '0'.
w_prog = ''.
w_incl = ''.
perform data_search tables i_stoken using w_level w_prog w_incl.
endif.
endform. "DATA_SELECT
& Form GET_FM_DATA &
form get_fm_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
destination 'SAPGUI'
keeping logical unit of work
exporting
text = 'Get function module data' "#EC NOTEXT
exceptions
system_failure
communication_failure. "#EC *
Function module data
sort i_fmodule by name.
delete adjacent duplicates from i_fmodule comparing name.
loop at i_fmodule where done ne 'X'.
clear: i_stoken, i_sstmnt, sourcetab, wa_tfdir, w_include .
refresh: i_stoken, i_sstmnt, sourcetab.
store function groups
select single area from enlfdir into wa_enlfdir-area
where funcname = i_fmodule-name.
i_enlfdir-area = wa_enlfdir-area.
append i_enlfdir.
Store development classes
if not wa_enlfdir-area is initial.
select single devclass into wa_tadir-devclass
from tadir where pgmid = 'R3TR'
and object = 'FUGR'
and obj_name = wa_enlfdir-area.
check not wa_tadir-devclass is initial.
move wa_tadir-devclass to i_devclass-clas.
append i_devclass.
endif.
clear wa_tfdir.
select single funcname pname include from tfdir into wa_tfdir
where funcname = i_fmodule-name.
check sy-subrc = 0.
call function 'FUNCTION_INCLUDE_SPLIT'
exporting
program = wa_tfdir-pname
importing
group = w_area.
concatenate 'L' w_area 'U' wa_tfdir-include into w_include.
i_fmodule-pname = w_include.
i_fmodule-pname2 = wa_tfdir-pname.
modify i_fmodule.
read report i_fmodule-pname into sourcetab.
if sy-subrc = 0.
scan abap-source sourcetab tokens into i_stoken
statements into i_sstmnt
keywords from keywords
with includes.
if sy-subrc > 0.
message e130(enhancement) raising syntax_error.
endif.
check i_stoken for entries
clear w_linnum.
describe table i_stoken lines w_linnum.
if w_linnum gt 0.
w_level = '1'.
w_prog = i_fmodule-pname2.
w_incl = i_fmodule-pname.
perform data_search tables i_stoken using w_level w_prog w_incl.
endif.
endif.
endloop.
sort funtion groups
sort i_devclass.
delete adjacent duplicates from i_devclass.
sort i_enlfdir.
delete adjacent duplicates from i_enlfdir.
endform. "GET_FM_DATA
& Form GET_SUBMIT_DATA &
form get_submit_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
destination 'SAPGUI'
keeping logical unit of work
exporting
text = 'Get submit data' "#EC NOTEXT
exceptions
system_failure
communication_failure
. "#EC *
sort i_submit.
delete adjacent duplicates from i_submit comparing pname.
w_level = '0'.
loop at i_submit where done ne 'X'.
check i_submit-pname ne p_pname. " ensure not the same as origianl program
clear: i_stoken, i_sstmnt, sourcetab.
refresh: i_stoken, i_sstmnt, sourcetab.
read report i_submit-pname into sourcetab.
if sy-subrc <> 0.
delete i_submit.
continue.
else.
scan abap-source sourcetab tokens into i_stoken
statements into i_sstmnt
keywords from keywords
with includes.
if sy-subrc > 0.
continue.
endif.
check i_stoken for entries
clear w_linnum.
describe table i_stoken lines w_linnum.
if w_linnum gt 0.
w_prog = i_submit-pname.
w_incl = ''.
perform data_search tables i_stoken using w_level w_prog w_incl.
endif.
endif.
restrict number of submit program selected for processing
describe table i_submit lines w_linnum.
if w_linnum ge p_limit.
w_level = '1'.
endif.
i_submit-done = 'X'.
modify i_submit.
endloop.
sort i_submit.
delete adjacent duplicates from i_submit comparing pname.
endform. "GET_SUBMIT_DATA
& Form DATA_SEARCH &
form data_search tables p_stoken structure stoken
using p_level p_prog p_incl.
loop at p_stoken.
clear i_userexit.
tabix = sy-tabix + 1.
i_userexit-level = p_level.
if i_userexit-level = '0'.
if p_incl is initial.
i_userexit-pname = p_pname.
else.
concatenate p_pname '/' p_incl into i_userexit-pname.
endif.
else.
if p_incl is initial.
i_userexit-pname = p_prog.
else.
concatenate p_prog '/' p_incl into i_userexit-pname.
endif.
endif.
Include
if p_stoken-str eq 'INCLUDE'.
check p_level eq '0'. " do not perform for function modules (2nd pass)
w_index = sy-tabix + 1.
read table p_stoken index w_index into wa_stoken.
check not wa_stoken-str cs 'STRUCTURE'.
check not wa_stoken-str cs 'SYMBOL'.
read table i_submit with key pname = wa_stoken-str.
if sy-subrc <> 0.
i_submit-pname = wa_stoken-str.
i_submit-level = p_level.
append i_submit.
endif.
endif.
Enhancements
if p_stoken-str eq 'CUSTOMER-FUNCTION'.
clear w_funcname.
read table p_stoken index tabix.
translate p_stoken-str using ''' '.
condense p_stoken-str.
if p_prog is initial.
concatenate 'EXIT' p_pname p_stoken-str into w_funcname
separated by '_'.
else.
concatenate 'EXIT' p_prog p_stoken-str into w_funcname
separated by '_'.
endif.
select single member from modsap into wa_modsap-member
where member = w_funcname.
if sy-subrc = 0. " check for valid enhancement
i_userexit-type = 'Enhancement'.
i_userexit-txt = w_funcname.
append i_userexit.
else.
clear wa_d010inc.
select single master into wa_d010inc-master
from d010inc
where include = p_prog.
concatenate 'EXIT' wa_d010inc-master p_stoken-str into w_funcname
separated by '_'.
i_userexit-type = 'Enhancement'.
i_userexit-txt = w_funcname.
endif.
endif.
BADIs
if p_stoken-str cs 'cl_exithandler='.
w_index = sy-tabix + 4.
read table p_stoken index w_index into wa_stoken.
i_userexit-txt = wa_stoken-str.
replace all occurrences of '''' in i_userexit-txt with space.
i_userexit-type = 'BADI'.
append i_userexit.
endif.
Business transaction events
if p_stoken-str cs 'OPEN_FI_PERFORM'.
i_userexit-type = 'BusTrEvent'.
i_userexit-txt = p_stoken-str.
replace all occurrences of '''' in i_userexit-txt with space.
i_userexit-modname = i_userexit-txt+16(8).
case i_userexit-txt+25(1).
when 'E'.
clear wa_tbe01t.
select single text1 into wa_tbe01t-text1 from tbe01t
where event = i_userexit-txt+16(8)
and spras = sy-langu.
if wa_tbe01t-text1 is initial.
i_userexit-modtext = ''. "#EC NOTEXT
else.
i_userexit-modtext = wa_tbe01t-text1.
endif.
i_userexit-modname+8 = '/P&S'. "#EC NOTEXT
when 'P'.
clear wa_tps01t.
select single text1 into wa_tps01t-text1 from tps01t
where procs = i_userexit-txt+16(8)
and spras = sy-langu.
i_userexit-modtext = wa_tps01t-text1.
i_userexit-modname+8 = '/Process'.
endcase.
append i_userexit.
endif.
Program exits
if p_stoken-str cs 'USEREXIT_'.
i_userexit-type = 'Program Exit'.
i_userexit-txt = p_stoken-str.
replace all occurrences of '''' in i_userexit-txt with space.
append i_userexit.
endif.
Submit programs
if p_stoken-str cs 'SUBMIT'.
check p_level eq '0'. " do not perform for function modules (2nd pass)
check not p_stoken-str cs '_'. " ensure not SUBMIT_XXX
w_index = sy-tabix + 1.
read table p_stoken index w_index into wa_stoken.
check not wa_stoken-str cs '_'. " ensure not SUBMIT_XXX
replace all occurrences of '''' in wa_stoken-str with space.
read table i_submit with key pname = wa_stoken-str.
if sy-subrc <> 0.
i_submit-pname = wa_stoken-str.
i_submit-level = p_level.
append i_submit.
endif.
endif.
Perform routines (which reference external programs)
if p_stoken-str cs 'PERFORM'.
check p_level eq '0'. " do not perform for function modules (2nd pass)
w_index = sy-tabix + 1.
read table p_stoken index w_index into wa_stoken.
if not wa_stoken-ovfl is initial.
w_off = wa_stoken-off1 + 10.
w_str = c_overflow+w_off(30).
find ')' in w_str match offset w_off.
w_off = w_off + 1.
wa_stoken-str = w_str(w_off).
endif.
check wa_stoken-str cs '('.
w_off = 0.
while sy-subrc = 0.
if wa_stoken-str+w_off(1) eq '('.
replace section offset w_off length 1 of wa_stoken-str with ''.
replace all occurrences of ')' in wa_stoken-str with space.
read table i_submit with key pname = wa_stoken-str.
if sy-subrc <> 0.
i_submit-pname = wa_stoken-str.
append i_submit.
endif.
exit.
else.
replace section offset w_off length 1 of wa_stoken-str with ''.
shift wa_stoken-str left deleting leading space.
endif.
endwhile.
endif.
Function modules
if p_stoken-str cs 'FUNCTION'.
clear i_fmodule.
check p_level eq '0'. " do not perform for function modules (2nd pass)
w_index = sy-tabix + 1.
read table p_stoken index w_index into wa_stoken.
if wa_stoken-str cs 'WF_'.
if wa_stoken-str cs 'IDOC'.
break-point.
endif.
if wa_stoken-str cs 'BAPI'.
i_fmodule-bapi = 'X'.
endif.
replace first occurrence of '''' in wa_stoken-str with space.
replace first occurrence of '''' in wa_stoken-str with space.
if sy-subrc = 4. " didn't find 2nd quote (ie name truncated)
clear wa_tfdir.
concatenate wa_stoken-str '%' into wa_stoken-str.
select single funcname into wa_tfdir-funcname from tfdir
where funcname like wa_stoken-str.
if sy-subrc = 0.
i_fmodule-name = wa_tfdir-funcname.
else.
continue.
endif.
else.
i_fmodule-name = wa_stoken-str.
endif.
read table i_fmodule with key name = i_fmodule-name.
if sy-subrc <> 0.
i_fmodule-level = p_level.
append i_fmodule.
endif.
endif.
endloop.
endform. "DATA_SEARCH
& Form GET_ADDITIONAL_DATA &
form get_additional_data.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
destination 'SAPGUI'
keeping logical unit of work
exporting
text = 'Get additional data' "#EC NOTEXT
exceptions
system_failure
communication_failure
. "#EC *
loop at i_userexit.
Enhancement data
if i_userexit-type cs 'Enh'.
clear: wa_modsapa.
select single name into wa_modsapa-name from modsap
where member = i_userexit-txt.
check sy-subrc = 0.
i_userexit-modname = wa_modsapa-name.
clear wa_modsapt.
select single modtext into wa_modsapt-modtext from modsapt
where name = wa_modsapa-name
and sprsl = sy-langu.
i_userexit-modtext = wa_modsapt-modtext.
MOH - enhancement to get the project name
clear w_mod.
select single modactmember modactname modattr~status
modattranam modattradat
into w_mod
from modact
inner join modattr
on modattrname = modactname
where modact~member = wa_modsapa-name
and modact~typ = space.
i_userexit-modattr = w_mod.
MOH - eoe
endif.
BADI data
if i_userexit-type eq 'BADI'.
clear wa_sxs_attr.
select single exit_name into wa_sxs_attr-exit_name from sxs_attr
where exit_name = i_userexit-txt.
if sy-subrc = 0.
i_userexit-modname = i_userexit-txt.
else.
i_userexit-modname = 'Dynamic call'. "#EC NOTEXT
endif.
clear wa_sxs_attrt.
select single text into wa_sxs_attrt-text from sxs_attrt
where exit_name = wa_sxs_attr-exit_name
and sprsl = sy-langu.
i_userexit-modtext = wa_sxs_attrt-text.
endif.
modify i_userexit.
endloop.
get enhancements via program package
clear wa_tadir.
select single devclass into wa_tadir-devclass from tadir
where pgmid = 'R3TR'
and object = 'PROG'
and obj_name = p_pname.
if sy-subrc = 0.
clear: wa_modsapa, wa_modsapt.
select name from modsapa into wa_modsapa-name
where devclass = wa_tadir-devclass.
select single modtext from modsapt into wa_modsapt-modtext
where name = wa_modsapa-name
and sprsl = sy-langu.
read table i_userexit with key modname = wa_modsapa-name.
if sy-subrc <> 0.
i_userexit-modtext = wa_modsapt-modtext.
i_userexit-type = 'Enhancement'. "#EC NOTEXT
i_userexit-modname = wa_modsapa-name.
i_userexit-txt = 'Determined from program DevClass'."#EC NOTEXT
i_userexit-pname = 'Unknown'. "#EC NOTEXT
append i_userexit.
endif.
endselect.
endif.
Get IDOCs
loop at i_devclass.
endloop.
endform. "GET_ADDITIONAL_DATA
& Form DATA_DISPLAY &
form data_display.
data selection message to sap gui
call function 'SAPGUI_PROGRESS_INDICATOR'
destination 'SAPGUI'
keeping logical unit of work
exporting
text = 'Prepare screen for display' "#EC NOTEXT
exceptions
system_failure
communication_failure
. "#EC *
sort i_userexit by type txt modname.
delete adjacent duplicates from i_userexit comparing txt modname.
format headings
write: 'Enhancements from main program'. "#EC NOTEXT
write: /.
uline.
format color col_heading.
write: / sy-vline,
(12) c_col1, "Enhanmt Type
sy-vline,
(40) c_col2, "Enhancement
sy-vline,
(30) c_col3, "Program/Include
sy-vline,
(20) c_col4, "Enhancement name
sy-vline,
(60) c_col5, "Enhancement description
sy-vline,
(8) c_col6, "Project
sy-vline,
(1) c_col7, "S
sy-vline,
(12) c_col8, "ChangeName
sy-vline,
(10) c_col9, "ChangeDate
sy-vline.
format reset.
uline.
format lines
loop at i_userexit.
set line colour
case i_userexit-type.
when 'Enhancement'.
format color 3 intensified off.
when 'BADI'.
format color 4 intensified off.
when 'BusTrEvent'.
format color 5 intensified off.
when 'Program Exit'.
format color 6 intensified off.
when others.
format reset.
endcase.
write: / sy-vline,
i_userexit-type,
sy-vline,
i_userexit-txt(40),
sy-vline,
i_userexit-pname(30),
sy-vline,
i_userexit-modname(20),
sy-vline,
i_userexit-modtext(60),
sy-vline,
i_userexit-modattr-name,
sy-vline,
i_userexit-modattr-status,
sy-vline,
i_userexit-modattr-anam,
sy-vline,
i_userexit-modattr-adat no-zero,
sy-vline.
hide: i_userexit-type,
i_userexit-txt,
i_userexit-pname,
i_userexit-modname,
i_userexit-modtext.
endloop.
format reset.
uline.
user-exits from development class of function modules
if p_devc = 'X'.
write: /.
write: / 'User-exits from function module development class'."#EC NOTEXT
write: 157''.
uline (90).
write: 157''.
loop at i_devclass.
clear wa_modsapa.
select name from modsapa into wa_modsapa
where devclass = i_devclass-clas.
select single name modtext into corresponding fields of wa_modsapt
from modsapt
where name = wa_modsapa-name
and sprsl = sy-langu.
format color 3 intensified off.
write: / sy-vline,
(12) 'Enhancement',
sy-vline,
wa_modsapa-name,
sy-vline,
wa_modsapt-modtext,
sy-vline.
endselect.
endloop.
uline (90).
format reset.
endif.
describe table i_fmodule lines w_linnum.
write: / c_fmod , at 35 w_linnum. "#EC NOTEXT
write: 157''.
if p_func = 'X'.
display fuction modules used in program
uline (38).
write: 157''.
loop at i_fmodule.
write: sy-vline,
i_fmodule-name,
sy-vline,
i_fmodule-bapi,
sy-vline.
write: 157''.
endloop.
uline (38).
write: 157''.
endif.
describe table i_submit lines w_linnum.
write: / c_subm , at 35 w_linnum. "#EC NOTEXT
write: 157''.
if p_subm = 'X'.
display submit programs used in program
uline (44).
write: 157''.
loop at i_submit.
write: sy-vline,
i_submit-pname,
sy-vline.
write: 157''.
endloop.
uline (44).
endif.
issue message with number of user-exits displayed
describe table i_userexit lines w_linnum.
message s697(56) with w_linnum.
endform. "DATA_DISPLAY
& User Selection Processing &
at line-selection.
get cursor field w_fsel.
case w_fsel.
when 'I_USEREXIT-MODNAME'.
case i_userexit-type.
when 'Enhancement'.
set parameter id 'MON' field i_userexit-modname.
call transaction 'SMOD' and skip first screen.
when 'BADI'.
check i_userexit-modname ne 'Dynamic call'.
set parameter id 'EXN' field i_userexit-modname.
call transaction 'SE18' and skip first screen.
when 'BusTrEvent'.
submit rfopfi00 with attr_typey_selm = 'A'
with event = i_userexit-modname(8)
via selection-screen
and return.
when others.
endcase.
when 'I_USEREXIT-PNAME'.
check i_userexit-modname ne 'Unknown'.
w_off = 0.
find '/' in i_userexit-pname match offset w_off.
if w_off = 0.
set parameter id 'RID' field i_userexit-pname.
call transaction 'SE38' and skip first screen.
else.
w_off = w_off + 1.
w_prog = i_userexit-pname+w_off.
set parameter id 'RID' field w_prog.
call transaction 'SE38' and skip first screen.
endif.
when others.
endcase.
Feel free to revert back.
--Ragu

PO Net Price and Gross Price should not bechange once GR happen for the sam

Hi Friends,
For my client they need the below requiremet
As of now my client is able change a PO price(net price & Gross Price) after GR happen for the PO.
I maked the Net price field as Display mode under the below Path
Go to ->spro->mm->purchasing ->Purchse Order->define screen layout at document
level-> Choose NBF->select price and price unit and make it display
and i recieved the GR for the PO.
But still am able to change the Gross Price for the material under the Item Detail-> Condition Tab.
if am changing the Gross price means the same reflecting in netprice also.
So,User should not do any Price level changes in a PO once GR done for that.
Kindly suggest me how i can solve this issue.
How i can remove the option in the Purchase Order?.

Hi,
Standard SAP does not provide any setting to meet your req.
however, you can Use an user exit i.e. when the user is using T.code ME22N or ME29N the system should not allow to change the price if there is follow-on documents in the PO history.
Refer SAP Note- 457511.
OR
Create a variant for field price in ME22N & M329N using T code shd0.
http://wiki.sdn.sap.com/wiki/display/Snippets/TransactionVariant-AStepbyStepGuidefor+Creation
Regards,
Pravin
Avoid Changes in PO price after Gr has been done .

USER EXIT/ BADI (The price should not be changed in the billing document)

Similar Messages

Maybe you are looking for