Screen Exists for crmd_order

Hi,
Any one tell me the screen exists for crmd_order t-code. I want to make the priority field mandotary in Create Change Request screen
Regards,
Priya.
Edited by: abap4kirti on May 20, 2010 2:54 PM

Hey,
in order to make sure a field is mandatory you should use badi crm_order_save called when a ticket is saved and raise a cancel save in case the field is empty ! This way you ll fore people to fill priority field for example
In order to make the errors appear on ticket as the standard errors you can check documentation of SPRO Customizing point : 'Business Add-In for Activities: Header Data'
You ll there find a very explicit explanation on how to handle messages buffer in tickets
That should be OK for your requirement !
Regards
Khalil
PS: Another simple way to do it is a screen variant and set field to mandatory (transaction SHD0)
-> Screen values 7153 Program SAPLCRM_SERVICE_UI Subscreen SUBSCR02

Similar Messages

Screen exit for CRMD_ORDER

Hi ABAPERs,
we need to add a custom field in the GENERAL tab in the TXN CRMD_ORDER...is there any screen exit / enhancement for the same.
BR,
Anubhav Jain.

Hi,
Have a look
https://forums.sdn.sap.com/click.jspa?searchID=11604451&messageID=3708512
Regards
Kiran Sure

'No detailed information exists for this person' while adding new reviewer

Hi All,
This is an extremely urgent issue.
We are getting the following message in SRM while adding a new approver to the Shopping cart once the - 'No detailed information exists for this person'
We have implemented the following OSS Notes in the SRM 5.5 system, Release 700 after rasing a call with SAP.
SAP Pilot OSS note - 1002957
Other OSS Notes -
999528 Adding Ad Hoc Approver fails due to comit erro...
722357 Ad hoc: Commit control with ad hoc enhancement...
990467 Commit Problem with AdHoc Agents...
984582 Problems with Posting Container Data (ad Hoc
 agent...
947296 Inserted/changed approver is not transferred...
910925 SRM Workflow: Ad-hoc agent not found...
803628 BADI workflow: You cannot add an approver
Here are the details
 Cannot add additional approver
 We are now on SRM 5.5 and a document attached shows the
 patch levels
 from SPAM.
 In shop transaction, it is possible to change the
 default approvers,
 but not possible to Add.
 When we add, the system shows the list of available
 approvers, allows
 selection, but "transfer" button does not actually
 transfer.
 When the cart is saved, the added approval shows as "no
 approval
 available".
 We are using the standard workflows for 2 step approval.
 A document is attached to show what happens and the
 results of checks
 we have performed.
 BUS2121 also shows as ok when checked.
Any pointers what could be possible reasons.
Points for sure. !!
Regards
- Atul

Hi Atul,
Here is the list.
 |----- 0000702787 EBP 4.0: Message "Enter a country"
 |----- 0000732828 E-mail messages for work items with incorrect line break
 |----- 0000735026 Memory problems at BBP_GETLIST_INDEX_FILL
 |----- 0000804317 SRM40/SUS/PO: PO inbound with error BBP_PD 147
 |----- 0000862851 PO not ordered due to different locations error
 |----- 0000902956 Changing Account assignment category BE Limit service PO
 |----- 0000911446 No reservation is created
 |----- 0000917869 SRM 5.0: PPOMV_BBP - Vendor address tab page
 |----- 0000919553 SRM 5.0: Termination of output preview for invalid partner
 |----- 0000920363 Shopping cart transfer: Sourcing indicator is not set
 |----- 0000924218 SRM 5.0: wrong error message for non existant auth. PurchOrg
 |----- 0000924811 SRM5.0: Javascript error on document screen
 |----- 0000926750 Shopping cart: Unit of measure is not restored
 |----- 0000926878 Link for expanding details in the shopping cart too small
 |----- 0000927142 SRM5.0: Browser hangs up during attachment upload
 |----- 0000938168 SRM50: Message "No default value from vendor master"
 |----- 0000938296 JavaScript runtime error in the bid invitation
 |----- 0000940805 BBPS_SC_APP_SOS cannot be enhanced
 |----- 0000941935 External requirements displayed as a reference
 |----- 0000942742 Update is cancelled if new source of supply is found
 |----- 0000944592 No location when vendor has changed
 |----- 0000944918 ECS: Find back end purchasing group as a responsible group
 |----- 0000945601 Termination when you display purchase order item detail
 |----- 0000948425 Shopping basket changeable although already approved
 |----- 0000953238 Shopping cart history in the sourcing cockpit
 |----- 0000954066 Follow-On Documents Tab does not get Highlighted
 |----- 0000954409 Error message during approval of a confirmation
 |----- 0000955377 Long runtimes for workflows with blocks
 |----- 0000956108 Empty worklist after clicking button 'Find'
 |----- 0000956723 BBPMAININT:Bus. partner display switches to maintenance mode
 |----- 0000956797 RUSRM50: Limit Purchase Order Functional Area Error Message
 |----- 0000957884 Category Management: Data disappears after program SAVE
 |----- 0000958045 BBPSC04: Delete icon not hidden despite screen variant
 |----- 0000958349 Final delivery with quantity 0
 |----- 0000959528 During PO creation wrong error message BBP_PD 428
 |----- 0000960169 Favorites not saved for 'Purchase for'
 |----- 0000961422 BBP_MON_SC: No search help for 'Created By'
 |----- 0000962093 BBP_VENDOR_CREATE: Refresh BP data
 |----- 0000962252 BBP_GETLIST_INDEX_FILL: Incorrect processing statistics
 |----- 0000962474 Error after changing partner data
 |----- 0000964132 Approval Preview for Rejected Items: Wrong User's Inbox
 |----- 0000964361 Cannot find employee of vendor
 |----- 0000964455 Country for the PO box is initial
 |----- 0000964911 Kopieren von Alertkategorien: Containerelemente verschwinden
 |----- 0000966072 Download of material fails - set type COMM_PR_UNIT
 |----- 0000966323 Service Item: Not able to create PO in ERP backend
 |----- 0000967429 Approval buttons not updated after release
 |----- 0000967615 Performance of BBP_PD_PO_GETDETAIL may be poor
 |----- 0000968110 Transfer canceled, account assignment acc. to value/quantity
 |----- 0000968251 BBPSC02:In source of supply preferred vendor not validated
 |----- 0000969091 SRM does not support passwords longer than 8 characters
 |----- 0000982293 Ext requirements: Purchasing group data not transferred
 |----- 0000982448 Impossibility to delete an item in PO
 |----- 0000982674 Change PO quantity does not update account assign quantity
 |----- 0000983130 Search for back-end purchase orders using the requester name
 |----- 0000984184 BADI BBP_ALERTING active but its implementation isn't called
 |----- 0000985179 Delete button active for backend service entry sheets
 |----- 0000990264 Multiple confirmations cannot be posted for service & limit
 |----- 0000996104 No catalog when confirming back-end blanket purchase orders
 |----- 0001003408 BBPCF: Cannot Add Catalog Item to Confirmation for Limit PO
 0001010791 Flag Confirmation based Invoice Verification set erroneous
Kind regards,
Yann

No Active Nametab exist for - while deleting master data

Hi,
We are deleting a master data record in production and while saving the master data we are getting an error like "No Active Nametab exist for". And while going back the screen it is giving an error as "Table /BIC/YZEMPLOYEE does not exist". How do we resolve this and is there any program to delete the master datAny help is greatly appreciated.
Regards
Vijay

Hi,
Check this OSS Note 211492.
Hope this will resolve the issue..
Best Regards,
VVenkat..

Would love Steve Jobs to contact me for in setting screen tinting orange for seizures as OK WE HAVE DONE IT AN ORANGE PROTECTIVE SCREEN OVERLAY FOR IPOD AND IPAD STOPPING JOHN'S photosensitivity SEIZURES AND STOPPING EYE PROBLEMS WITH USAGE

OK WE HAVE DONE IT AN ORANGE PROTECTIVE SCREEN OVERLAY FOR IPOD AND IPAD STOPPING JOHN'S SEIZURES AND STOPPING EYE PROBLEMS WITH USAGE ABLE TO CUT ANY SIZE FOR PHONES EG
Contact me Steve the idea is great and the pictures are reveal a better depth perception of colour call me a Mum that created a diffence for her son and kept him communicating on his ipod and his ipad proffessors were amazed at childrens hospital and would love to show you my ideas in making it built in to your ipod and ipads or any computer for that matter everyone i show is blown away not only that but a wider customer level will be reached from a Mum that made a difference for her son that was unable to communicate and then had seizures so developed my own cover that allows him to chat all day without having any eye problems.
So we now sell the covers on ebay to help others access technology that they need in order to survive and live happily as without his ipod or ipad and him telling us what was wrong he would of died he had respritory lung disease photosensitive epilepsy a metabolic condition that could of killed him anytime from stroke or seizure battled with using all types of technology but now is a dream come true.
Would love for this to be enabled in the setup of all computers alike to protect eyes and allow more users to speak and communicate a big thankyou to the creators and designers fabulous but please can you call me as this could make you even better i mean will and also give me more time.
From one praying God fearing Mum
Nadine
Call me i do have better pics they were too big to upload orange covering on right hand side

Going through the feedback and support pages will be a waste of your time. Apple won't respond to feedback, and support can't do anything regarding product suggestions, particularly not from a company with an existing product they wish to sell. The only attention you might get from Apple would be possible interest in selling your product through the Apple Stores, and I don't know how Apple chooses the third-party products they sell. All I could suggest would be writing to Apple's corporate headquarters:
Apple
1 Infinite Loop
Cupertino, CA 95014
with perhaps "Attention: Retail Sales Division" and telling them about your product and your interest in it being sold through the Apple Stores.
Regards.

Screen-exit for profit center creation - transaction KE51.

Hi All,
Background: The client has the requirement of importing profit centre master data from legacy system into SAP ECC system. Few of the legacy data could not be filled into existing sap fields, hence the requirement has been to populate the data into custom fields.
The client also has the requirement, that the same fields are required during online entry. For this we need to enhance the profit centre creation screen (transaction code KE51) with two additional custom fields.
Requirement: To enhance profit centre creation screen with custom fields. Screen-exit for KE51 transaction.
Pre-work: Program SAPLRKPM in SAP ECC system is the main program. It does not have any screen or sub screen area for custom fields addition. Debugged the program to check for screen-exits, found none.
Below user-exits are not either screen-exits or cannot be used for enhancing profit center screen.
PCA00001 EC-PCA: Document changes for data transfer
PCA00002 Profit Center Accounting: derivation of representative mat.
PCA00003 Derive Partner Profit Center for External Deliveries
PCA00004 Check valuation for invoice verification with transfer price
PCA00005 Check valuation for invoice verification with transfer price
PCASELEK EC-PCA: Selection criteria for data transfer
Solution required for: Could anyone please let me know if it is possible to enhance the profit center creation screen. If yes, please provide the names of the screen-exit/ badi exit.
(Just a thought, modifying the standard seems to be the only solution, this should be the last option and i agree, please provide your inputs.)
Thanks in advance.
Warm Regards,
Goutham.

Thank you Manohar for the response.
The requirement is to display custom fields on standard sap screen and there are no screen-exits. So, i suppose the standard screen has to be modified.
Could you please provide brief explanation on
May be you should consider maintaining custom mapping table instead of going for chaning standard.
With Regards,
Goutham.

User Exist for MM - Purchase Order

Hi ABAP expert,
is there any user exist for Purchase order, actually i'm want to prevent the user from do the deletion on PO items, as per my understanding we can use user exit.
can anyone help and how to do the process ?

Hi,
1. Just copy and paste this code and execute it.
2. Give the Tcode "ME21" and you will see the lot of user exits.
TABLES : tstc,     "SAP Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
* Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
* Find Repository Objects for transaction code
IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
       WHERE pgmid    = 'R3TR'
         AND object   = 'PROG'
         AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
      SELECT SINGLE * FROM trdir
         WHERE name = tstc-pgmna.
      IF trdir-subc EQ 'F'.
        SELECT SINGLE * FROM tfdir
          WHERE pname = tstc-pgmna.
        SELECT SINGLE * FROM enlfdir
          WHERE funcname = tfdir-funcname.
        SELECT SINGLE * FROM tadir
          WHERE pgmid    = 'R3TR'
            AND object   = 'FUGR'
            AND obj_name = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
* Find SAP Modifactions
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
      WHERE sprsl EQ sy-langu
        AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
      WRITE:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
* Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
Thanks,
Reward If Helpful.

Find screen number for enhancement.

How to identify screen number for a particular standard SAP transaction for enhancement. Suppose I want to enhance any screen of any transaction how to search/identify customer screen number and enhance them, I want to add some fields or tab or anything else.

Hi Avirat,
You can get the screen number for screen enhancement using the following methods:
1) Googling on the Tcode or by reading OSS notes .
2) Go to SPRO transaction . Navigate to the application component and see whether any section on Enhancement exists.
3) Other ways of finding it are -
i) CMOD based screen exits -
Here the 4 digits 0101,0111,0201,0211,0301,0311 are the screen numbers where enhancement can be done .
In case project is already implemented, get the project name from MODACT table.
ii) For BADI based screen exit - Do a look up on SXS_SCRN table
Regards,
DPM

Screen Exit for Notification Header

Hie Experts.
I would like to implement the BADI BADI_EAM_SINGLELEVEL_LIST but when i search for it under t-code SE18 it doesn't exist. Is the BADI BADI_EAM_SINGLELEVEL_LIST found in SAP ECC 6.0 version?
Regards,
Joseph.

Hi ,
Please go to Se80 as per below screen shot and choose repositiry Information system .
Now click on Enhancement and choose BADi as below Screen shot for Enhancement spot mention by Archer
This will display 5213 result and then Serach with
Many Thanks

Screen exit for me32k for header and for items

hi experts,
i need a screen exit from me32k to add subscreen in :
1. items
2. header
thanks in advanced,
dana.

Hi,
Just some information on screen exits:
Screen Exit:
How to implement screen exit for a SAP standard transaction
Introduction
SAP provides standard transactions to enter data into database. But a client may want to maintain some additional information in SAP other than what is provided.
To make provisions for this, additional screens have to be provided and additional fields must be added into appropriate database table.
To pave way for this, SAP has provided the option for screen exits. Usually, SAP provides the following:
An append structure in the database table with the new fields.
A subscreen area into the standard screen where the programmer can attach his subscreen of his own program with the new fields.
A function group under which the new subscreen has to be created with the new fields.
Function exits to synchronize the PBO and PAI of the standard SAP program with the PBO and PAI of the subscreen so that data can flow back and forth between the standard SAP program and the program written by the developer for the subscreen. These function modules also exist in the same function group under which the subscreen will have to be developed.
Finally, a linkage has to be done between the subscreen area of standard SAP screen with the custom subscreen constructed by the developer.
Typically, SAP provides an enhancement in which the developer can create an append structure, use the function exits to synchronize the PBO and PAI of the standard SAP program and the custom subscreen program, and make the necessary linking( as mentioned above in step 4. But, again, this is not a hard and fast rule. Linking in some case, is also done by configurations.) SAP also usually provides the name of the function group under which the subscreen has to be developed.
Necessary guidance about implementing a screen exit development is usually available in the Documentation section of the enhancement ( can be availed by transaction SMOD).
Pre-Requisites
The developer to work on screen exit should have essential knowledge on the following:
DDIC concepts, including the knowledge of append structure.
Concept of SAP Enhancements and implementing them using Projects.
Concept of function exits.
Knowledge on Module Pool including subscreens, Tabstrip controls etc.
Steps
Guidelines
So, a developer can follow the guidelines mentioned below to implement a screen exit to a standard SAP transaction, as and when required:
Find out the Required Enhancements
Go to SMOD. Press F4 in the Enhancement field. In the next popup window, click pushbutton SAP Applications. A list will appear that contains information on all the enhancements, categorized under functional areas. Developer must search for the enhancements relevant to his functional area of interest for e.g., Purchasing, Asset Accounting, etc.
Note down the enhancements. Then, come to the initial screen of SMOD and view the documentation of each enhancement to find out which one is required for your development.
Utilize the Enhancement in a Project
After you have found one, do as directed in the documentation. Generally, the steps are as follows:
Create a project using CMOD including your enhancement.
Create the append structure with new fields.
Go to the desired function group and create a subscreen with the new fields. Write PBO and PAI for the subscreen, if required.
Use the function exits in the enhancement to link the PBO and PAI of the subscreen with that of the main SAP program supporting the SAP transaction.
Maintain necessary linkage between the subscreen area of standard SAP program with the custom subscreen developed along with the custom program name. This can be done in the project (developed by CMOD including the enhancement) or outside as a part of configuration.
Activate the project.
Test to ensure that required functionality are met.
Case Study 1
Add three new custom fields for Asset master and maintain information for them
Requirement
Three fields in the legacy system have to be maintained in Asset master. These fields are:
Original Asset number 20 characters
Location 2 15 Characters.
Model no 20 characters
Location 2 should start with L.
Pre-Analysis
Finding out the Enhancement
As described above, the enhancement is determined. It was found, that enhancement AIST0002 will serve the purpose. It contains the following components (can be viewed by transaction SMOD):
Exit Type Description EXIT_SAPL1022_001 Function Exit Check of User-Defined Fields when Using Create and Change BAPI EXIT_SAPLAIST_002 Function Exit Transfer Data for User Subscreens in PBO. EXIT_SAPLAIST_003 Function Exit Transfer of User-Defined Fields to SAP Master Data Transactions CI_ANLU Customizing Include Include structure to add new fields
Studying the Function Exits
The function module level documentation for the function exits are then viewed from transaction SE37. The documentation clearly laid out for the purpose for their use:
EXIT_SAPLAIST_002
Function module Level Documentation
This function module is called by asset master data maintenance at the start of the dialog. (When changing, it is called after reading of the data from the database; when creating it is called after the transfer of the default values from the asset class and reference asset.) The purpose of the function module is to enable this function group to recognize the master data. For interpreting or controlling master data fields that are important for user fields, it is possible to transfer to global variables at this point, so that they can be recognized when the user subscreens are processed.
Import Parameters
Understanding
This function module is called at the PBO to pass the information retrieved from the database to pass them to the custom subscreen and its underlying program. Import parameter : I_ANLU will be populated with the values for user-defined fields which will be passed to the subscreen program. So, there must be some sort of variable assignment from I_ANLU.
EXIT_SAPLAIST_003
Function module Documentation: This function module is called by SAP asset master data maintenance after the screens are processed, but before saving. The purpose of the function module is to transfer fields entered on user sub-screens of SAP asset data maintenance to the database for updating. The export parameter for this function module is:
Understanding
This function module will be used to transfer the user entered data in the subscreen fields to the main SAP program, which will then be saved into the database.
Studying the Documentation of the Enhancement
The enhancement documentation (as is viewed from the initial screen of SMOD] also supports the idea. Moreover, it informs that we need to develop a subscreen under function group XAIS. This is the function group under which the two function exit modules also exist. So, if the custom subscreen refers to the global data of the function group XAIS, then those values will also be available to these function exits as well.
Going to SE80 and viewing the function group XAIS helps us to inform that there are three DDIC tables declared for it:
Deciding the Final course of Action
After making all the investigations, the final course of action was determined.
SrlNo Step Justification
A project has to be created using transaction CMOD where the enhancement AIST0002 will be included.
Customizing include CI_ANLU has to be created with the custom fields demanded When CI_ANLU will be developed, the custom fields will get appended to the database table ANLU. Also, these fields will be used to create screen fields in the new subscreen.
A custom subscreen, say, 9000 will be developed under function group XAIS. The screen group for the screen will be CUST (or any name). The three custom fields added to table ANLU (by creating CI_ANLU) will be used to create new fields in the screen.
In the PAI of the subscreen, validation for Location to start with L will be added. The subscreen with three new fields has to be developed so that it can be attached to a subscreen area of the asset master screens.
In the custom include of the function exit module EXIT_SAPLAIST_002, the following code will be written:-
ANLU = I_ANLU. I_ANLU is the import parameter of this FM. The value is assigned to the global variable ANLU, referring which the three new subscreen fields are developed. So, data retrieved from database table ANLU will be passed to this FM as I_ANLU by the standard SAP main program. The value will be taken and passed to the global variable of the function group XAIS, so that the three custom fields (referring to ANLU of XAIS) get populated.
In the custom include of the function exit module EXIT_SAPLAIST_003, the following code will be written:-
E_ANLU = ANLU. The changed values in the subscreen fields exist in global variable ANLU for the function group XAIS. This function exit module will pass the data back to the SAP main program as E_ANLU.
Proper linkage/configuration has to be done so that the new subscreens get linked to the appropriate subscreen area of the Asset master screen. This has to be done otherwise, the new custom subscreen will not be displayed in the Asset master screens.
Development
Creating a Project to include the enhancement
Go to transaction CMOD and create a project.
Enter a description for the project. Then, click on the pushbutton Enhancement Assignments in the Application Toolbar.
Enter the name of the enhancement and Save.
Go to Components.
Creating Custom Include for ANLU
The screen shown below will appear, showing all the enhancement components under the assignment AIST0002. Double-click on the name of the Include Structure to create it.
Create the include structure with three new fields, as required. Then, save and activate it.
Develop the subscreen and the program
Go to transaction SE80. For the function group XAIS, create a new subscreen 9000.
Create it as subscreen.
Then, go to the Layout of the screen and create three new fields from Database table ANLU.
Drag the fields in the screen body and place them.
Then, save and activate the screen and come back to screen flow editor.
Create the PAI module to add validation for field Location 2, as required .
Activate the whole function group and come out.
Write code in the Function Exits to synchronize the programs
Now, code has to be written in the function modules EXIT_SAPLAIST_002 and EXIT_SAPLAIST_003 so that data flows to and fro between the main SAP program and custom subscreen program. For that, go back to transaction CMOD and change the function exits.
Write code in the function module EXIT_SAPLAIST_002 called once at the beginning of the transaction:
Write code in EXIT_SAPLAIST_003 to pass the data from the subscreen to SAP main program.
Then, activate everything the whole project and come out.
Complete the configuration to link the subscreen
The development portion is complete. Now, linking of the subscreen has to be done with the subscreen area of the main program. In most of the cases, this linking can be done in the enhancement itself. But, here, requirement is a bit different. It is done by configuration using SPRO.
Assets are created under Asset class. And for each asset class, there is a layout assigned to it. For a layout, there are multiple tab pages assigned to it. And, for each tab page, there are multiple screen groups/field groups assigned.
Here, the requirement is to create these three custom fields in the tab page General of asset master screen ( AS01/AS02/AS03/AS91).
Determine the Layout
To achieve this, first of all, we need to find out which layout is assigned to asset class 1000.For that, go to transaction AOLK( information has to be obtained from functional consultant).Select the Asset Class 1000 and click on folder General Assignment of Layout.
Here, for Asset class 1000, for all the user groups, tab layout SAP is assigned. Since layout SAP cannot be changed, it has to be copied and manipulated to include our screen group. Later, the new layout has to be assigned over here.
Create new tab layout
Go to transaction AOLA. Copy the tab layout SAP to create another layout, say, YSUB.
System will copy all the settings and will inform you about that.
Select your newly created layout and double-click on the folder Tab page titles.
You want to put your custom fields in the tab page General. So, select this tab page entry and double-click on the folder "Position of Groups".
Here, all the field groups currently residing in the tab-page General are shown. Add an entry for your newly created fields.
Select the group box from the list. An entry will come with U padded with the custom subscreen prepared by you.
Then, save and come out.
Assign the new Layout to Asset Class
Now, go to tcode AOLK and assign tab layout YSUB for asset class 1000.
Save and come out.
Test the Exit
Everything is over. Now, go to transaction code AS01/02/03 or AS91 to deal with an asset of asset class 1000. You will see your new fields added to the screen. Add values to themsave. Then, enter into the tcodes again to see whether the values entered by you are being displayed or not.
Original Source: ittoolbox.com
User Exits:
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a function module. The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the include that is implemented in the function module.
The naming standard of function modules for functionmodule exits is:
EXIT_<program name><3 digit suffix>
The call to a functionmodule exit is implemented as:
CALL CUSTOMER.-FUNCTION <3 digit suffix>
To find a Exit.
Goto Transaction -- Find The Package
SMOD >f4>Use the Package here to Find the Exits In the Package.
Else if you Want to search by Application Area wise ,
There is one more tab to find the Exits in the Respective Application Area.
Implementing the Exit-- CMOD Create ProjectsAssgn your Component .
Now Run ur Transaction to Check if it Triggers.
Thats it..
Suppose you need to find out all the user exits related to a tcode.
1. Execute the Tcode.
2. Open the SAP program.
3. Get the Development Class.
4. Execute Tcode SE84.
5. Open the Node 'Envir. -> Exit Techniques -> 'Customer Exits -> Enhancements'
6. Enter the Development class and execute.
Check out this thread..
The specified item was not found.
1. Type the transaction : system->status-> <PROG. NAME>
2 open SE37 , type EXIT<PROG NAME> and press F4 to get the list of function exits available.
3. Open CMOD utilities->SAP enhancements
EDIT->All selections
4.type the function module name obtained in step 2, in fields 'component name' in 'additional selections' block. and execute.
5. The displayed list contains the enhancements names for the transaction You were looking for.
6. Create a project in CMOD and the code in default include->activate.
http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec079f5db911d295ae0000e82de14a/frameset.htm
For information on Exits, check these links
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.planetsap.com/userexit_main_page.htm
User-Exits
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/ab038.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.sap-basis-abap.com/sapab013.htm
http://sap.ittoolbox.com/documents/popular-q-and-a/user-exits-for-the-transaction-code-migo-3283
These links will help you to learn more on user exits.
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm
http://www.planetsap.com/userexit_main_page.htm
http://www.allsaplinks.com/user_exit.html
www.sap-img.com/abap/what-is-user-exits.htm
Also please check these threads for more details about user exits.
Re: Screen exit
user exit and customer exit
user exit
1. Document on UserExits in FI/CO
http://www.ficoexpertonline.com/downloads/User%20ExitsWPedit.doc
2. Finding User Exits...
http://sap.ionelburlacu.ro/abap/sap2/Other_Useful_Tips.html#Finding_User_Exits
3. List of all User Exits...
http://www.planetsap.com/userexit_main_page.htm
Reward if found helpfull,
Cheers,
Chaitanya.

Screen exit for VL31N

Hi All,
I have a requirement to add a few custom fields in the standard transaction screen VL31N.Is there any screen exit i can make use of? How do i proceed once i get the Screen exit to add the fields in the screen.
Thanks in advance.
Karthik

HI,
There is no screen exit available for VL31N. the available user exists for this Tcode are :
V02V0001            Sales area determination for stock transport order
V02V0002            User exit for storage location determination
V02V0003            User exit for gate + matl staging area determination (headr)
V02V0004            User Exit for Staging Area Determination (Item)
V50PSTAT            Delivery: Item Status Calculation
V50Q0001            Delivery Monitor: User Exits for Filling Display Fields
V50R0001            Collective processing for delivery creation
V50R0002            Collective processing for delivery creation
V50R0004            Calculation of Stock for POs for Shipping Due Date List
V50S0001            User Exits for Delivery Processing
V53C0001            Rough workload calculation in time per item
V53C0002            W&S: RWE enhancement - shipping material type/time slot
V53W0001            User exits for creating picking waves
VMDE0001            Shipping Interface: Error Handling - Inbound IDoc
VMDE0002            Shipping Interface: Message PICKSD (Picking, Outbound)
VMDE0003            Shipping Interface: Message SDPICK (Picking, Inbound)
VMDE0004            Shipping Interface: Message SDPACK (Packing, Inbound)
Thanks,
Varna

SAP Error "Trader does not exist for company code"

Good Day,
In SAP, we have multiple users in the role of trader. However, for one user, he keeps getting the message "Trade <name> does not exist for company code <code>" when he hits enter on the first screen of transaction TX01.
We have copied the profile of another user who is not getting that error, but still he keeps getting the error. What else should we check apart from the profile?
Thanks
VC

Thanks all, but i solved the problem.

Time constraint classes and screen number for absence type

Hi all,
What should be the Time constraint classes and screen number for absence type.
The different absence types are annual leave, sick leave , study leave , personal leave, maternity leave , juryduty leave nad leave without pay etc
Kindly help.
Regards,

The time constaint class depends on the client requirement.
eg.if they want that a error needs to be generated while overlapping absences or warning message is required.
Time contraints comprise the following:
Time constraint classes that determine which collisions in time data records are allowed
Time constraint table that contains the time-based collisions allowed in the time data records
Time constraint indicator that displays whether a new data record that collides with an existing time data record can be transferred to the system or whether the transfer is prohibited
For screen number you will have to see if the is quota based deduction or just an absence. Here is the documentation of screen number from SAP
In the standard system, the following numbers are allocated to the screens:
1. 2000 - General absence
This screen is used for all absences which do not require special processing (such as paid leave of absence for getting married).
2. 2001 - Quota deduction
This screen is used for entering data on leave or time in lieu of overtime.
3. 2002 - Work incapacity
Use this screen for all absence types where continued pay should be taken into account automatically by the system.
4. Special screens have been developed for the following absence types:
2003 - maternity protection, parental leave
2004 - military and non-military service
2005 - work incapacity (Netherlands)
Please go through the documentation of the configuration.
Shrikant Basarkar

11gr1 - Handling different screen resolutions for an enterprise app.

Hi,
We are developing an enterprise application that will be deployed at different clients with different hardware.
We are confused about how to handle different screen resolutions and wonder how others are handling this.
We have some fixed size areas in our screens and liquid areas for content that may expand. The problem is say that you have a table with 6 columns. This table will be rendered nicely at 1280X800 but not at 1650X1050 or 800X600.
At higher resolutions we will either end up having some blank space or expand one of the columns of the table , but can't expand every column proportionally and this will look ugly.
For lower resolutions same problem in a different way will come into picture, we will not able to resize the columns and end up with scroll bars etc ...
What is the best practice with handling different screen resolutions for components like table,panel splitter etc ?
Thanks

Hi Muhammed,
I don't think that any better solution exists, you already use liquid layouts and define widths & heights with percentages etc. In my opinion using blank column at the end of table columns makes table's looking better. Additionally creating custom skin for table and defining column heights & widths with % or em may help you to stretch columns?

Screen exits for XD01 at different levels of customer classification

Hi ,
Can anyone help me in getting screen exits for Tran XD01 at differnt levels like in general data , sales area where i need to add custom fields.

Hi,
Check the documentation in below :
Goto - SPRO - Financial Accounting - Accounts receivable and Accounts Payable - Customer Accounts - Master Data ->
1) Preparations for Creating Customer Master Data - Adoption of Customeru2019s Own Master Data Fields -Prepare Modification-Free Enhancement in Customer Master Record. Here you will find the BADI's for customer master screens. Check the individual documentation
2) Preparations for Creating Customer Master Data- Develop Enhancements for Customer Master Data
Please note as far as i know, you can create new buttons on the customer master tool bar and then assign your fields to that button on the transaction. Not sure if you can add fields in the existing screens.
Thanks
Shiva

Screen Exists for crmd_order

Similar Messages

Maybe you are looking for