User Exit To Change Posting Date In T-Code: F110
Hi,
I need to change the posting date while doing payment run from T-Code: F110.
Kindly advice me how to go forward with it.
Regards,
Rohini.
Hi Rohini ,
I have used BTE 1120 (Business Transaction Event) to change the value date for line items (BSEG-VALUT) for F110.
May be this can help u ..... try once ....
Regards,
AKS
Similar Messages
-
USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT
Hi,
Pls advise any USER EXIT FOR CHANGING POSTING DATE IN THE MATERIAL DOCUMENT.
Regards,Hi,
There is another user exit for updating material document data Upon posting is MB_CF001
I hope this will fullfill you.
Prem -
Inbound IDOC User Exit ZXVEDU04 change IDoc Data
Hi all,
We have to develop an user exit for changing the Plant, Shipping Point and Storage location
We have identified the exit ZXVEDU04 . Is there some other exit for this ??
But which internal table we are supposed to change this to change the data .
If possible send me a sample code
Thanks in Advance .
Vivek K ..Hi all,
I have done this for a single line item IDoc .
How do i go for IDocs with more than one line item ???
I have hardcoded VBAP-WERKS(1) etc for Plant, Strg Loc and shp pt .
How to identify how many line items are there in the IDocs ??
Thanks in Advance .
Vivek K .. -
User exit to change sort on ME57 t-code in SAP MM
Do we have any user exit to change the sort on ME57 output screen, I have to sort ME57 by Storage bin, we dont have storage bin on ME57 output, so i have add storage bin and sort.
Can any body help me to solve this problem?
thanks,Hi Rohini ,
I have used BTE 1120 (Business Transaction Event) to change the value date for line items (BSEG-VALUT) for F110.
May be this can help u ..... try once ....
Regards,
AKS -
User-exit for changing pricing date in condition record while creating SO?
Hi all,
I am creating sales order based on PO using ALE-idoc . Here i got one problem i.e the system taking the pricing date as system date.
But i want the pricing date equal to PO document date.
Please specify where and how to set this pricing date?
Thanks,
Vamshi.hi Vamshi,
Could you poste your solution for our information?
I ran into a situation sort of related to yours.
Our customers use ALE change their Purchase Order(PO) to us. Then, by means of ALE, our Sales Order(SO) changed accordingly.
According to system standard, our Sales Order(SO) pricing date modified to present date. But in our industry scenario, pricing date is unchangable once the Sales Order(SO) has been created.
Which user exit I can utilize to made those pricing date of SO header and body item stay the same? -
User exit for MIGO Posting Date
Dear all,
My Client want requirement is : Posting date of GRN should be after last posting date of goods issue
i.e. GI 261 1st june
GI Reverse 262 2nd june
again GI 261 28 may ( as 2 posting perod are open )
then user should be able to do GRN on or after 28th may
For this user exit please suggest me any FM or logic
my current logic is allowing to post GRN after 1st june i.e. latest GI date but that is not matching client requirement
Please suggest
Regards,
IshwarHi,
Enhancement for MIGO ,you can try these user exit
MB_CF001--> Customer Function Exit in the Case of Updating a Mat. Doc.
MBCF0002 --> Customer function exit: Segment text in material doc. item
MBCF0005 --> Material document item for goods receipt/issue slip
MBCF0007 -->Customer function exit: Updating a reservation
In BADI,you can refer these
MB_CIN_LMBMBU04--> posting of gr
.In MKPF table having data (posting date of goods issue) BUDAT-field name,tell the conditions as per your requirement to ABAPer,they can implement the enhancement as per your requirement...
I hope,it will help you
<=<< Sharing Knowledge is a way to Innovative >>=>
By,
Yoga -
User exit to change Release date for ME54N
Dear Folks,
I need and user exit / BADI to update EBAN-FRGDT (Release date) based on the value in EBAN-FRGKX (Release indicator).
For example : If the PR release indicator changed to "F", I need to change the EBAN-FRGDT (Release date) to sy-datum and then save. Please help me.
Thanks,
Kishore. PHi Rohini ,
I have used BTE 1120 (Business Transaction Event) to change the value date for line items (BSEG-VALUT) for F110.
May be this can help u ..... try once ....
Regards,
AKS -
Purchase requisition , ME51N, user exit for change Release date
Hello.
Purchase Requisition ( transaction ME51N).
I want to change the value of u201ERelease dateu201C using user-exit EXIT_SAPLMEREQ_005.
CALL METHOD im_req_item->get_data
RECEIVING
re_data = get.
set = get.
set-frgdt = u2026..
CALL METHOD im_req_item->set_data
EXPORTING
im_data = set.
Next, in dynpro is visible the right value from EXIT_SAPLMEREQ_005, but when saving the system uses another value, not the value from user exit.
Do you anybody have some experiences with this problem?
LumirHi
The USer Exit you can use for the ME51n Tcode is by using Badi's.The Badi you can use is ME_PROCESS_REQ_CUST BADI.
Method to be used: PROCESS_ITEM
This link gives you a brief idea.Hope it helps you.
BADI for ME51N
Thanking you. -
User Exit for changing RBKP-BVTYP in t-Code MRRL
Hi ,
We have to change Partner bank type field (RBKP-BVTYP) while creating invoice through t-code MRRL. i tried to find out the user exit or BADI for this
purpose, but i could not.
i found below user exits and badi but here i was unable to change the value. there were other exits but there also it was not possible to change the value.
Enhancement MRMH0001 - component - EXIT_SAPLMRMH_001 and EXIT_SAPLMRMH_002
here only limited change to RBKP is permitted.
I tried with BADI INVOICE_UPDATE but it is not allowed there also.
Can we do it with some configuration or substitution rule ? if yes then how?
thnaks in advance
rajpalHi Emir,
BADI BADI_SD_SALES_ITEM now changed to enhancement spot.
In SE18: enter Enhancement spot - BADI_SD_SALES_ITEM.
Inside enhancement spot BADI_SD_SALES_ITEM four BADI definition were exist.
I think BADI definition MSR_SD_SALES is use full for you (This BADI definition is not reserver for SAP intrnal use.
And above enhancement spot also not reserverd for sap internal use.
Just try to implementation BADI definition MSR_SD_SALES and use method CHANGE_BILLING_BLOCK_ITEM.
BR,
Vijay -
How to change posting date in J1IH Code
i posted the posting date wrongy for current date, in J1IH t code. how to change that into last march month date in table. what is the table name? how to do?
Hi hi,
Posting date is system date you shoudnt change it.
What is your perticular requirement , why you want to change it?
If you have already post the document then it is not possibe the change the posting date..
Rgds,
Kareena -
User exit to change material availability date
Hi Gurus,
my requirement is like I need to change the material availability date based on some conditions.
Is there any User Exit to change the availability date so that I can dump my code in the user exit .
If not is there any alternative process to get the solution.
Thanks,
Sudhaa.............Hi Sudha,
Can you tell me your requirement clearly please.
Regards,
Dhanunjaya Reddy -
User exit to change item level data in purchase order
Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirment is
For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in itemlevel data.
Regards,
RahulHi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar -
Help - User exit to change item level data in Purchase Order
Hi,
Can anyone let me know the user exit to change item level data in purchase order . there is a badi ME_PROCESS_PO_CUST for this but the issue is its method process_item gets triggered only when the item is changed. My requirement is For purchase order document types u201CZSOu201D and u201CZCOu201D, where the purchase order is a u201CLimits Orderu201D only i.e. no materials or services on the purchase order, the print price indicator field should be set to u201Cblanku201D (unchecked). now i cant use ME_PROCESS_PO_CUST because process_item wont get triggered if there is no change in item level data.
Thanks,
RahulHi Rahul,
Probably EXIT_SAPLMEKO_002.
hope it helps,
Edgar -
User exit for changing Sales order lines.
Hello experts ,
I want to delete the field "ROUTE" from all of the orders lines in sales orders, I have been using "USEREXIT_SAVE_DOCUMENT_PREPARE" but it does not seems to do the job.
What is the name of user exit that i have to use for this task and which structure should be used, is it xvbap ? is it vbap ?
Thanks for the help.
Avi.Hi,
find the user exit u required.
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
Best regards,
venkatawamy.y -
User exit for change PO (me22n) for save header and item text.
Hi Experts,
I have a requirement to read the header texts/item text at run time .
please tell me is there any save user exit for tc me22n .
Thanks in Advance.
PareshTransaction Code - ME21N Create Purchase Order
Exit Name Description
LMEDR001 Enhancements to print program
LMELA002 Adopt batch no. from shipping notification when posting a GR
LMELA010 Inbound shipping notification: Transfer item data from IDOC
LMEQR001 User exit for source determination
LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
LWSUS001 Customer-Specific Source Determination in Retail
M06B0001 Role determination for purchase requisition release
M06B0002 Changes to comm. structure for purchase requisition release
M06B0003 Number range and document number
M06B0004 Number range and document number
M06B0005 Changes to comm. structure for overall release of requisn.
M06E0004 Changes to communication structure for release purch. doc.
M06E0005 Role determination for release of purchasing documents
ME590001 Grouping of requsitions for PO split in ME59
MEETA001 Define schedule line type (backlog, immed. req., preview)
MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
MEQUERY1 Enhancement to Document Overview ME21N/ME51N
MEVME001 WE default quantity calc. and over/ underdelivery tolerance
MM06E001 User exits for EDI inbound and outbound purchasing documents
MM06E003 Number range and document number
MM06E004 Control import data screens in purchase order
MM06E005 Customer fields in purchasing document
MM06E007 Change document for requisitions upon conversion into PO
MM06E008 Monitoring of contr. target value in case of release orders
MM06E009 Relevant texts for "Texts exist" indicator
MM06E010 Field selection for vendor address
MMAL0001 ALE source list distribution: Outbound processing
MMAL0002 ALE source list distribution: Inbound processing
MMAL0003 ALE purcasing info record distribution: Outbound processing
MMAL0004 ALE purchasing info record distribution: Inbound processing
MMDA0001 Default delivery addresses
MMFAB001 User exit for generation of release order
MRFLB001 Control Items for Contract Release Order
AMPL0001 User subscreen for additional data on AMPL
No of Exits: 35
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal
Maybe you are looking for
-
Upload + Download in Bid invitation
Hi, What i understand from upload and download feature in SRM is that the purchaser can download the bid invitation & make changes & upload it back again. When I download I can see all database fields like - BBP_PDS_HEADER-GUID, BBP_PDS_PARTNER-PAR
-
I just received a new ipod 16gb, which has a new charger. How can I use this in my car, which has ipod connectivity using the old plug? How can I use it in my skullcandy speakers, which use the old plug?
-
Will nokia c5-00 be updated to symbian belle ?
will nokia release any new update for c5 to improve browser and time changing bug. Are we going to get anything above 71.005 . It is said that nokia is changing its phones from symbian to 'nokia belle' tag line. Can c5 expect the same or has the comp
-
Remote Communication Error(Trex).
Dear Friends, We have configuresd Trex for Full Text Search in DMS. But the Issue is we are not able to Index Documents. When I check the connections under "Trex_admin--->TREX ABAP Customizing" by giving Host Name or IP Address and Trex Index Server
-
When I "clear recent history" it hangs and "script:chrome://browser/content/sanitize.js:136" comes up and I have to stop the script to continue. This started within the last week.