User exit ZXRSRU02 to get user's entry

Hi,
Will this code work to get get the user's entry and start processing it from program ZXRSRU02:
Data: L_S_CHANM TYPE RRKE_S_CHANM.
CASE I_S_RKB1D_INFOCUBE.
WHEN 'DEMOCUBE'.
L_S_CHANM-CHANM = 'PRODUCT'.
L_S_CHANM-MODE = RRKE_C_MODE-READ.
APPEND L_S_CHANM TO E_T_CHANM.
L_S_CHANM-CHANM = 'PRICE_TP'.
L_S_CHANM-MODE = RRKE_C_MODE-NO-SELECTION.
APPEND L_S_CHANM TO E_T_CHANM.
APPEND 'ACT_PRICE' TO E_T_KYFNM.
APPEND 'QUANTITY' TO E_T_KYFNM.
ENDCASE.
Will this code allow me to get the user's entry from the selection screen?
Tahnks,
RT

Hi,
Yes your'e correct about the requirement.
Here are the links to what I have completed so far but I would get the value with 6 numbers similar to 736,278, for example. I am asking for more time to resolve this 6 number results but was told to use the program ZXRSRU02 and make use of virtual char. I would think to make use of Virtual Char is more complicated and more coding is require.
Re: How to create cutsomer exit variable to a replacement path variable
Re: Compute number of days using user's entry date as an operand
Re: Check the user's entry from query selection screen
Thanks,
RT
Message was edited by: Rob Thomas

Similar Messages

User-Exit / Badi for ML81n (create service entry sheet)

Dear experts,
I am looking for a User-Exit / Badi for ML81n (create service entry sheet), which will enable me to compare its date with the referenced PO's item's delivery-date, befor saving , and send an error message (with no update) if the check is not OK.
Remark : I have tried MB_DOCUMENT_BADI but with no success because you can't send an error message from it.
Thank you
Yaacov

hi check below thread
User-Exit for Service Entry Sheet via ML81N?
regards
vijay

User exit when saving the user profile

Hi All,
Is there any user exit exist which get triggered whenever any SAP user profile is saved.
Thanks in advance,
Harkamal

Hi harkamal,
I dont think that any user exit is present for the code :SU01.
If you want to check the user exit. please find the below code and execute in SE38 you will get the Userexit related to the TCode.
*& Report Z7CC_USEREXIT_TRANSACTION_CODE
report zuserexit no standard page heading.
tables : tstc, tadir, modsapt, modact, trdir, tfdir, enlfdir.
 tables : tstct.
data : jtab like tadir occurs 0 with header line.
data : field1(30).
data : v_devclass like tadir-devclass.
parameters : p_tcode like tstc-tcode obligatory.
select single * from tstc where tcode eq p_tcode.
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 eq enlfdir-area.
 move : tadir-devclass to v_devclass.
 endif.
 endif.
 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.
at line-selection.
 get cursor field field1.
 check field1(4) eq 'JTAB'.
 set parameter id 'MON' field sy-lisel+1(10).
 call transaction 'SMOD' and skip first screen.

User Exit or BADI for MIGO on entry of inbound delivery number

Hi all,
I want a user exit or BADI for MIGO, my requirement is that whenever a user enters an inbound delivery number and presses enter in MIGO the exit should get fired.
Please help, if someone knows.
Thanks and Regards,
Mohammed.

hi
you can try out various BADI'S-
MB_MIGO_BADI
MB_MIGO_ITEM_BADI
Helpful function modules:-
MIGO_BADI_EXAMPLE
MIGO_BADI_EXAMPLE_GET_DATA
MIGO_BADI_EXAMPLE_GET_HEADER
MIGO_BADI_EXAMPLE_PUT_DATA
MIGO_BADI_EXAMPLE_PUT_HEADER
MIGO_BADI_EXAMPLE_UPATE_DATA
MIGO_BADI_EXAMPLE_UPDATE_HEAD
I hope at least one of these helps.
regards
Aakash

LT09 - Transfer Order User Exit is not getting trigerred though its active

Hi,
I am trying to assign the enhancement : MWMTO001
( Enhancements for end of transfer order generation )
which contains the user exit component : EXIT_SAPLL03T_001
I have created a project in CMOD and assigned the enhancement.
When I execute the TCode LT09 for transfer order, I noticed that this exit is not getting trigerred ...
I need to call a smartform whenever we save the data in the T-code LT09.
Am i using a wrong Exit ? Please help me to find out why this exit is not getting triggered though its activated ....
Thanking you in advance..
Nagasubramanyam.

Hi
Thank you for reply.
According to 1st scenario prgm is activated & also activated enhancement in CMOD.
According to 2nd scenario, can u suggest how to find out the correct exit...
Actually I written a print prgm in include of EXIT_SAPLL03T_001 & designed SMARTFORM for that...
if I do process thru LT09 transaction & save that SMARTFORM should be triggered which is not happening...I put break points & tried but the exit is not triggering.
pls suggest how to find out the correct exit of LT09 .
Thanks&Regards
NagaSubramanyam.

Which user exit allows to get cost element derivation in CO-PA after F-op.?

Dear All,
According with business requirements we need to get cost elements used in Sales in CO-PA document after F-operations.
We've got the answer from SAP that it could not be done by standard way. Cause profit segment we define in Sales order before we had performed outbound delivery (vl01n )and billing (vf01).
However, we still need to get this cost elements after F-operation in CO-PA documents.
Could anyone name user exit which could be used for that purpose?
With best regards,
Kamila.

Hi,
Thanks for response. But the link doesn't work.
"System Error
Sorry, internal server error occurred (500 error).
What can you do?
Try selecting Refresh in your browser.
Check the URL in the browser address bar and make sure it was entered correctly.
Use our Search feature (in the top right hand section) to locate the correct URL for the page or document you are trying to access.
If all else fails:
Please take a screenshot of this page (usually Function + Print Screen), or copy the URL from the browser address bar along with the text of the error message and email it to [email protected] Please include your user ID in all correspondence.
<< Go to the Homepage."
Could you please, resend this link?
Thank you,
With best regards,
Kamila.

User Exit or BADI for ml81n - Service Entry Sheet

Hi all,
I would like to find a user exit or BADI or enhancement upon saving.
The requirement is posting to specific GL A/C from the Service No. given.
Please don't provide me a list of unnecessary user exit or BADI.
Urgently need for solution, Thanks.

Hi,
Check out the various exits for ml81n
INTERFAC            Interface for data transfer
SRVDET              User screen on tab strip of service detail screen
SRVEDIT             Service list control (maintenance/display)
SRVENTRY            Unplanned part of entry sheet (obsolete since Rel. 3.1G)
SRVESI              Data conversion entry sheet interface
SRVESKN             Set account assignment in service line
SRVESLL             Service line checks
SRVESSR             Set entry sheet header data
SRVEUSCR            User screen on entry sheet tabstrip
SRVKNTTP            Setting the account assgnmt category when reading in, if
SRVLIMIT            Limit check
SRVMAIL1            Processing of mail before generation of sheet
SRVMSTLV            Conversion of data during importing of standard service c
SRVPOWEB            Purchase order for service entry in Web
SRVQUOT             Service export/import for inquiry/quotations
SRVREL              Changes to comm. structure for release of entry sheet
SRVSEL              Service selection from non-SAP systems
SRV_FRM             SRV: Formula calculation (obsolete since 4.0A!)

USER EXIT MB_CF001 NOT GETTING TRIGGERED

Hi All,
I am using EXIT_SAPLMBMB_001(MB_CF001)
I want it to be triggered after the document has been saved but its not trigeering..
How can I find out the reason???
Regards
Shilpa

Hi,
have you checked documentation for that enhancement? That function module is not called after goods movement creation.
The user exit MB_CF001 includes a function module that is called up
immediately before the COMMIT WORK when a goods movement is posted.
How do you test that FM? Some function modules from user exits are called in UPDATE TASK so they just ignore break points. In this case you can use the following trick. You need to enter an infinite loop into your user exit. Then you can connect to this program via transaction SM50 (Program/Session -> Program -> Debugging).
Cheers

How to find the list of all user exits modified by the users

How to find the list of all user exits using by in R3

Hi Mohamed
You use Solution Manager to do the comparison for you. There are some nice features that will highlight all your customised coding. Have a look at the SolMan resources on the Support Portal e.g. using SolMan for upgrade comparisons.
Rgards
Carl.

User-Exit or BADI for USER FIELD in C201 or C202

Dear Experts,
SAP has made provision of USER FIELDs in C201 / C202 (Create/Change Master Recipe: Operation), which is saved in PLPO table.
By applying logic, for each operation I want to create a Phantom part and update values in this user fields at the time of SAVE.
Is there any BADIs, User-Exit or any standard way available which is called at the time of Recipe Create / Change?
Or Should i go through Implicit Enhancement for the same?
With Regards,
Kaushik Savaliya

Hi Kaushik,
Please check these Function exits.
EXIT_SAPLCPDO_001 -PS: User fields
EXIT_SAPLCPDO_002 -PS: Customer specific fields in process (standard net)
EXIT_SAPLCPDO_003 -PS: Customer specific fields in process (standard net)
Hope it helps.

Logon user exit EXIT_SAPLSUSF_001 - for which users is it called?

Hi!
I just wanted to make sure one thing. Is the logon user exit EXIT_SAPLSUSF_001 called ONLY for dialog users? It is not triggered for background users, or other similar processes bypassing the logon screen?
thanks!

It will be called for every logon, this can cause some problems if some gui functions are called outside of a gui context (popup, cl_gui class, etc. -> [Note 819750 - Short dump after logon|https://service.sap.com/sap/support/notes/819750]) - use of TRY/CATCH/ENDTRY is recommended.
Regards,
Raymond

User Exit not getting triggered

Dear all,
we are creating a workflow for PR Release which needed release strategy customization. so we are trying to set the release stratagy by changing the communciation structure CEBAN-USRC1 field.
for this, i had done the following things:
1. SMOD->M06B0005->components->EXIT_SAPLEBND_004->INCLUDE ZXM06U31 (double clicked) wrote few lines of code.
2. CMOD-> created a proj ZMM_PREL->assigned Enhancement M06B0005 under enhancements tab-> EXIT_SAPLEBND_004-> activated all
(User exit, project eveything).
Now my problem is when i create a PR, this user exit does not get triggered at all. I am working on ECC6.0 the same code which i did in Ecc5.0 for my previous client is still working fine.
Can anyone please guide me where i might have gone wrong?
Thank you,
Regards,
Lakshmi

Hi,
HAve u verifiyed that the user-exit u r using is triggered whenever u create ou PR.?
First of all u have to put breakpoints at each and every user-exits provided for that transaction, then check which user exit is getting triggered when u carete ur PR. and thenafter write ur code in this user-exit only.
Reward is useful.
Regards,
Harsha

User Exit not getting Triggered in Quality Server

Hi,
In FM 'IDOC_INPUT_DESADV' Iam using an User Exit 'EXIT_SAPLEINM_006' ,
which is getting triggered in Development server.But when I moved it to Quality,
The User Exit is not getting triggered.Thou the Exit is assigned to Enhancement
and that in turn is assigned to Project, still the problem persists.
Can any one suggest me what could be the problem.
Regards,
Kiran B.

Kiran,
Check the Project of that enhancement is active or not. not the enhancement.
<REMOVED BY MODERATOR>
Satish
Message was edited by:
Alvaro Tejada Galindo

Error raising exception in user-exit for idoc_output_delvry.

Hi All,
   When I try to raise an exception from the user exit (idoc_output_delvry),
I get an error message 'Assign Measurement unit to ISO code'.
    Can you help me solve this issue.
Thanks in avance,
Disney.

Michael,
       Thanks for the quick response,
I did check in IMG, an entry is already there, the 'primary field' is checked,
USD is assigned to the iso code USD.
Regards,
Disney.

User exit MB_CF001 in MIGO

Folks,
I am using the user exit MB_CF001 to get the data from XMSEG table and send it to an external system. I was asked to call an RFC function module in this user exit to send the XMSEG data to an external system but the user exit documentation clearly says not to use RFC function call in this user exit.
I also heard that I can do this by using the idocs that get posted after MIGO is done. Could anyone give me step by step procedure how to do this as I am new to IDOCS.
Points will be rewarded for best answers.
Thanks,
Alok

Dear Alok,
Below is a documentation about IDOCs. Hope it will be useful to you.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Important links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
>SAP ALE & IDOC
Steps to configuration(Basis)
>>1. Create Logical System (LS) for each applicable ALE-enabled client
>>2. Link client to Logical System on the respective servers
>>3. Create background user, to be used by ALE(with authorizaton for ALE postings)
>>4. Create RFC Destinations(SM59)
>>5. Ports in Idoc processing(WE21)
>>6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
>Steps to customize a new IDoc
>>1. Define IDoc Segment (WE31)
>>2. Convert Segments into an IDoc type (WE30)
>>3. Create a Message Type (WE81)
>>4. Create valid Combination of Message & IDoc type(WE82)
>>5. Define Processing Code(WE41 for OUT / WE42 for IN)
>>6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
Best Regards,
Rajesh.
Please reward points if found helpful.

User exit ZXRSRU02 to get user's entry

Similar Messages

Maybe you are looking for