Skip user exit call at BDC run.

Hi All,
1) I have a BDC program that updates email addresses for existing sales orders & contracts in T-code VA02 & VA42.
2) In include MV45AFZZ i have added a piece of code that raises a pop-up message for those items whose profit centre is not maintained.
It's a genuine case that my BDC won't execute successfully for those sales orders where profit centre is not maintained for its items. The reason the pop-up message is displayed and BDC won't skip that.
Note : I could have used warning/information message but due to some constraints i used the pop up message. I wanted a message to be displayed with all the line items missing their respective profit centres. The message was displayed but the screen was greyed out i.e. in display mode. So i used pop up message and handled the screen accordingly.
The main issue now is:
My BDC won't work as the pop-up message cannot be skipped by the BDC . Can you suggest something
1) So that the code in the user exit won't be trigerred at the BDC call or BDC run?
OR
2) Pop-up should only be displayed when user works with T-code VA02 or VA42 and not at BDC run
~Arya.

Hi,
Please check for the system parameter sy-binpt.
for eg:
IF SY-BINPT NE 'X'
CODe.....
ENDIF.
Thanks & Regards
Suresh Krishnan
Edited by: Suresh Krishnan on Jan 30, 2012 12:06 PM
Edited by: Suresh Krishnan on Jan 30, 2012 12:06 PM
Edited by: Suresh Krishnan on Jan 30, 2012 12:06 PM
Edited by: Suresh Krishnan on Jan 30, 2012 12:07 PM
Edited by: Suresh Krishnan on Jan 30, 2012 12:07 PM

Similar Messages

User exit call customer function 002 is not getting trigerred

Hi
I am using the user exit call customer function 002 in the function module idoc_input_proact to trigger and idoc.my problem is that the user exit is not geting triggered.
please help me gurus as this the last day for finishing thw work.
regards,
Asish dash

it means tthat, u are applying a wrong exit in the pgm.
try to once again search for the suitable exits for your program.
try this:
how to find the customer exits for a particular transaction
check out the pgm in this thread:
Re: Find User Exits
regards,
padma

Dumb question about E messages generated in user exits called from dialogs

After a user enters goods receipt info in MIGO and hits POST, there is a user exit (EXIT_SAPLIE01_007) which receives a copy of the goods receipt table (xmseg) from MIGO and lets you do whatever you want before the MIGO update task is called. In other words, you're still in the MIGO dialog process.
I have successfully used this exit before to pop an editable ALV that lets the user enter custom data per line item, and then store this data in memory so it can be accessed in MB_DOCUMENT_BADI or in the equivalent XMBC exit (enhancement MB_CF001).
But here's my question.
Suppose I generate an "E" message in EXIT_SAPLIE01_007.
Will this stop the MIGO "POST" so that the update task isn't called?
And will the text of the "E" message be displayed at the bottom of the main MIGO screen (the one you hit "POST" from) ????
Edited by: David Halitsky on Feb 21, 2008 9:03 PM
Edited by: David Halitsky on Feb 21, 2008 9:04 PM

Hi David,
it seems that you will get it:
E in Status bar
+behaviour: +
PAI processing is terminated, and control returns to the current screen. All of the screen fields for which there is a FIELD or CHAIN statement are ready for input. The user must enter a new value. The system then restarts PAI processing for the screen using the new values. Error messages are not possible in POH or POV processing. Instead, a runtime error occurs.
according to help [http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm|http://help.sap.com/saphelp_nw70/helpdata/en/9f/dbaabc35c111d1829f0000e829fbfe/frameset.htm]
best regards,
Wojciech

R/3 User Exit Call from ITS

Hi ,
In an user exit i want to find out if a call has been made from ITS ..
is there any FM or system variable set.. based on which I could find out ?

call function 'ITS_PING'
       exceptions
            its_not_available = 1
            others            = 2.
if sy-subrc eq 0 .
******* called from ITS
else .
**** not called from ITS
endif .
Raja

User Exit call

Hello friends,
how to call a client proxy from a user Exit.

Satya,
You can also refer these blogs for more info on creating and sending the data from outbound proxy to XI.
Have a look:
OutBound Proxy (Client Proxy)
/people/sravya.talanki2/blog/2006/07/28/smarter-approach-for-coding-abap-proxies
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
In your case you will write your code (data extraction logic) inside the exit rather than creating a Z progarm as mentioned in the above blogs. )
Regards,
Sarvesh

User Exit called when online ATP check with GATP

Hi Guys,
I got requirement as below,
Manipulate the GR time defined in the unloading point when the ATP confirmation of sales order is done with GATP online.
I noticed that the online GATP check from R/3 to APO is not going via normal CIF way of communication or at least even i de-registered CIF queue monitoring, the data transfer can still go through properly.
There are two questions popped up:
1. Any body knows the background routine how the data are transferred between R/3 and APO when online GATP is done, and how to debug this process?
2. Which functional module or exit user is called when online GATP check is done from R/3 sales order?
If anyone knows something you are also welcome to share your expertise!
Thanks!
Tony

hi! Tony
These are the Exits in online GATP
EXIT_/SAPAPO/SAPLATPT_001      APO ATP: Set ATP Segment
EXIT_/SAPAPO/SAPLATPT_002      APO ATP: Select Substitutions
EXIT_/SAPAPO/SAPLATPT_003      APO ATP: Initialize ATP Controller
EXIT_/SAPAPO/SAPLATPT_004      APO ATP: Check for the Existence of a Location Alias
EXIT_/SAPAPO/SAPLATPT_005      APO-ATP: Handling of Data at End of Check
Regards
Vaibhav Sareen

User exit called many times

Hello Friends,
I am writing a particular code in a user exit of the FM IDOC_INPUT_MATMAS01 , the problem is that the user exit is called some 4 times in the program and my logic gets repeated 4 times . Is there any way to over come this ?
Comradely ,
K.Sibi

Hi Sibi,
You can put a check based on sales/purchasing organization (VKORG) for which IDOCs are processed.
Or, you can put a validation check on
1) partner type & partner number,
2) message type,
3) idoc basic type & extension,
before executing your user exit code.
Also Check the link below:
Creating Idoc filter for MATMAS
Regards,
Nisha Vengal.

How to find the user exits called at the time of posting the IDOC?

Hi,
Could anyone please how to find the user exits while posting a idoc?

Hi,
One way to ahive this is by, be ready with IDOC postiong,
then go to ST05 transaction and activate the trace after checking Table Buffer Trace.
Now post the IDOC then deactivate the trace.
Now come back to ST05 and display trace and search for calls starts with EXIT_.
Regards,
Manoj Kumar P

Is there a user exit called when a module pool program is launch ?

Hello,
I know the exit 'EXIT_SAPLSABE_010' and it's very usefull for adding code before a report is launch.
But this exit is not called when a program is a "Module pool" type.
Is there a way to add my own code before this kind of program is launch ?
Thanks in advance,
Simon
Edited by: Simon Desbonnets on Mar 9, 2010 2:23 PM

Thanks for your answer.
No it's not for initializing values. It's for logging statistics into a specific table (program name, date ...).
The event "load-of-program" can be use for one program, it's not what I'm looking for.
I would like to know if there is an exit that is called each time a module pool program is executed.

Forms User Exit calls

Hi,
I am trying to make a user_exit call in Forms9i. I have created a Pro*Cobol file as specified and created a form with user_exit calls. Everything has compiled.
My platform is win2k. The place where I am stuck is I don't know how to create an environment so that the forms can run and make a call to the procobol procedure. Can somebody tell me where to find a documents which lists which config files to change, and where to place the procobol files etc so that my forms can run?
Please help.
Wriju

Any particular reason why you are looking into user_exit and not into the ORA_FFI functionality?
check the online help for information on ORA_FFI

Calling a BDC program in side a user-exit

Hi all,
I need to call a BDC program in side a user-exit of sales order change
. i want to make user by calling this BDC program that it wont effect any of my other code's on that and that the customer wont be noticed with any inconvenience.
i know to use
CALL TRANSACTION 'zprogram'.
but i want to make sure that till will not do any harm for any of other parts.
Regards Nafran.

Hi
Make sure you dont change any values of standard SAP variables,structures and internal table values inside the user exit.This is the only way where the other functionality gets affected(unless it is the requirement).
Reward if helpful.
Thanks & regards,
Ramya

Help with BDC, user exits and BAPI

Hello all:
1) I posted a question before about BDC documentation and people sent me lot of helpful material. Thanks to all of them. I am very new to ABAP coming from VB background and wondering if someone can tell me how to practice one simple BDC program starting from scratch. What do I first need to do to get started? I have Mini WAS 6.20 test version and like to practice BDC programming.
2) What are user exits and BADI and can anyone provide some documentation and sample code if possible.
Thanks everyone in advance.
--Mithun.

Hai Mithun Dha
Go through the following Documentation & Example Code
Just check these links.
Diff. between LSMW & BDC?
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
E BDC_OPEN_GROUP : Opens a session group
E BDC_CLOSE_GROUP : Closes a session
E BDC_INSERT : Insert a BDC scenario in the session
E The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code ? 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purposec
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
check with this code
include bdcrecx1.
tables : mara.
data : begin of it_mara occurs 0,
matnr like mara-matnr,
mbrsh like mara-mbrsh,
mtart like mara-mtart,
maktx like makt-maktx,
meins like mara-meins,
end of it_mara.
start-of-selection.
perform upload_data.
perform open_group.
loop at it_mara.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
'RMMG1-MATNR'.
perform bdc_field using 'BDC_OKCODE'
'/00'.
perform bdc_field using 'RMMG1-MATNR'
it_mara-matnr.
perform bdc_field using 'RMMG1-MBRSH'
it_mara-mbrsh.
perform bdc_field using 'RMMG1-MTART'
it_mara-mtart.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
'MSICHTAUSW-DYTXT(02)'.
perform bdc_field using 'BDC_OKCODE'
'=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
'X'.
perform bdc_field using 'MSICHTAUSW-KZSEL(02)'
'X'.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
'=BU'.
perform bdc_field using 'MAKT-MAKTX'
it_mara-maktx.
perform bdc_field using 'BDC_CURSOR'
'MARA-MEINS'.
perform bdc_field using 'MARA-MEINS'
it_mara-meins.
perform bdc_field using 'MARA-MTPOS_MARA'
'NORM'.
perform bdc_transaction using 'MM01'.
endloop.
perform close_group.
*& Form upload_data
text
--> p1 text
<-- p2 text
FORM upload_data .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
FILENAME = 'c:\mat_bdc.txt'
FILETYPE = 'ASC'
TABLES
DATA_TAB = it_mara.
IF SY-SUBRC = 0.
SORT IT_MARA BY MATNR.
ENDIF.
ENDFORM. " upload_data
flat file structure is
PRANIT_011 CCOUP This is Testing material kg
PRANIT_012 CCOUP This is Testing material kg
PRANIT_013 CCOUP This is Testing material kg
PRANIT_014 CCOUP This is Testing material kg
PRANIT_015 CCOUP This is Testing material kg
when your selecting views
this particular material will belongs to Po/Sales or some other areas .
when you select basic 1 --it gives description
select basic 2 -- it gives tax ,amount, base unit of measurement
BDC TO BAPI
The steps to be followed are :
1. Find out the relevant BAPI (BAPI_SALESORDER_CHANGE for VA02).
[for VA01 use BAPI_SALESORDER_CREATEFROMDAT2]
2. Create a Z program and call the BAPi (same as a Funtion module call).
2. Now, if you see this BAPi, it has
-> Importing structures.
eg: SALESDOCUMENT: this will take the Sales order header data as input.
-> Tables parameters:
eg: ORDER_ITEM_IN: this will take the line item data as input.
Note :
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data
Possible UPDATEFLAGS:
U = change
D = delete
I = add
Example
1. Delete the whole order
2. Delete order items
3. Change the order
4. Change the configuration
Notes
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.
For further details... refer to the Function Module documentation for the BAPi.
For User Exits
User Exits
Screen exits are exits that allow you to use a reserved part of the screen (A subscreen) to display or input data.
It is determined be SAP where the sub screen will be displayed.
The syntax is: CALL CUSTOMER-SUBSCREEN
The screen exit is not processed untill the corresponding subscreen has been created in an enhancement project,
and the project has been activated.
Note:
Function codes are only processed in the main screens flow logic
You are not allowed to enter a name for the subscreens command field
You are not allowed to define GUI stauses
You are not allowed to enter a value for Next screen
The global data of the program is not available for the subscreen. Data for the subscreen is provided by function modules.
These function modules belongs to the same function group as the subscreen Subscreens are edited with transaction CMOD.
When you activate a project containg subscreens, the calling screen is regenerated and the subscreen is displayed next
time you display the calling screen
The developer must create the subscreen and the corresponding PBO and PAI modules
How to identify screen exits
Look after CALL CUSTOMER-SUBSCREEN in the screenprogram of the screen you want to modify.
Use transaction CMOD menu Utillities -> SAP enhancements to search for screen exits
MENU EXITS
Menu exits allow you to add your own functionallity to menus. Menu exits are implemented by SAP, and are reserved menu
entries in the GUI interface. The developer can add his/her own text and logic for the menu.
Function codes for menu exits all start with "+"
Example
We want to create a new menu item in the Office menu. The text for the menu should be "Run ZTEST", and the menu will
run report ZTEST.
Goto transaction SE43 Area Menu Maintenance
In Area Menu Paramenter type 'S000' (S triple Zero)
Select Change and ignore all the warning screens
Expand the office menu. In the buttom of the office tree you will find a menu named "Customer function"
Double click on the text. In the pop-up screen change the text to "Run ZTEST". Note that the trsnaction code is +C01
Goto transaction SE93 and create transaction +C01 that calls report ZTEST.
Now you will se the menu displayed in the office tree. If you delete transaction +C01 again, the new menu will dissapear.
USER EXITS
User exits (Function module exits) are exits developed by SAP. The exit is implementerd as a call to a functionmodule.
The code for the function module is writeen 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>
Example:
The program for transaction VA01 Create salesorder is SAPMV45A
If you search for CALL CUSTOMER-FUNCTION i program SAPMV45A you will find ( Among other user exits):
CALL CUSTOMER-FUNCTION '003'
exporting
xvbak = vbak
xvbuk = vbuk
xkomk = tkomk
importing
lvf_subrc = lvf_subrc
tables
xvbfa = xvbfa
xvbap = xvbap
xvbup = xvbup.
The exit calls function module EXIT_SAPMV45A_003
2. How to find user exits
Display the program where you are searching for and exit and search for CALL CUSTOMER-EXIT
If you know the Exit name, go to transaction CMOD. Choose menu Utillities->SAP Enhancements.
Enter the exit name and press enter.
You will now come to a screen that shows the function module exits for the exit.
3. Using Project management of SAP Enhancements
We want to create a project to enahance trasnaction VA01
Go to transaction CMOD
Create a project called ZVA01
Choose the Enhancement assign radio button and press the Change button
In the first column enter V45A0002 Predefine sold-to party in sales document . Note that an enhancement can only
be used i 1 project. If the enhancement is allready in use, and error message will be displayed
Press Save
Press Components. You can now see that enhancement uses user exit EXIT_SAPMV45A_002. Double click on the exit.
Now the function module is displayed. Double click on include ZXVVAU04 in the function module
Insert the following code into the include: E_KUNNR = '2155'.
Activate the include program. Go back to CMOD and activate the project.
Goto transaction VA01 and craete a salesorder. Note that Sold-to-party now automatically is "2155"
Have look at this links
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
http://www.sapgenie.com/abap/ole.htm
http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIOFFI/BCCIOFFI.pdf
Creation of Field Exits
Step by step procedure for creating Field Exits
There are eight steps to creating a field exit:
Step 1: Determine Data Element
Step 2: Go To Field Exit Transaction
Step 3: Create Field Exit
Step 4: Create Function Module
Step 5: Code Function Module
Step 6: Activate Function Module
Step 7: Assign Program/Screen
Step 8: Activate Field Exit
Step 1: Determine Data Element
- Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
- An easy way to determine the data element associated to a particular screen field is to:
Go the appropriate screen.
Position the cursor in the appropriate field.
Press eF1f for field-level help.
Click on the eTechnical infof pushbutton (or press eF9f) on the help dialog box.
On this Technical Information dialog box, the data element will be specified if the field is 'painted' from the ABAP/4 Dictionary.
Step 2: Go To Field Exit Transaction
- The transaction to create field exits is CMOD.
- You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
- From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
- After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
Step 3: Create Field Exit
- From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
- After choosing this menu path, a dialog box will prompt you for the appropriate data element .
- Enter the data element name and click the eContinuef pushbutton.
- Now, you will be able to create the function module associated to the data elementfs field exit.
Step 4: Create Function Module
- You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the eContinuef pushbutton.
- In the eFunction modulef field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
FIELD_EXIT_<data element>
- You can add an identifier (an underscore followed by a single character ).
- The first function module for a data elementfs field exit must be created without an identifier.
- To create the function module, click on the eCreatef pushbutton, choose menu path Function module -> Create, or press eF5f.
- After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing eEnterf, you will be able to go ahead and create the function module.
- Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
Step 5: Code Function Module
- From the function modulefs attributes screen, click on the eSource codef pushbutton or choose the Goto -> Function module menu path to the code of the function module.
- Here you will add your desired functionality for the field exit.
- Remember that field exitfs function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
- You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
Step 6: Activate Function Module
- After coding the function module, you must remember to activate it.
- Use the Function module -> Activate menu path to activate the function module.
- At this point, you can return to the field exit transaction.
- You should be able to 'green arrow' back to this transaction.
- When you return to the field exit transaction, you will see an entry for the newly created field exit.
- At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
- Also, the field exit will not be triggered yet because it is inactive.
Step 7: Assign Program/Screen
- This step is only needed if you want to make a field exit local.
- To make a field exit local, select the field exit and click on the eAssign prog./screenf pushbutton.
- In the dialog box , indicate the appropriate program name and screen number.
This information indicates that the field exit is local to the specified screen in the specified program.
- In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the eFld. Exitf field.
- If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
- If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
Step 8: Activate Field Exit
- The field exit must be active for it to be triggered by the system.
- Activate the field exit by choosing the Field exit -> Activate menu path.
- After assigning the field exit to a change request, its status will change to eActivef and it will be triggered automatically on the appropriate screen(s).
NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
Thanks & regards
Sreenivasulu P

User exit not work in bdc background mode

i have bdc program for creating sales order. I also use some user-exits. When i run the program in foreground, user-exit works fine, but in background, the program can't stop in user-exit. Do you have any idea about what kind of problem can cause to this?

Call transactions with bdc tables in Sales Orders execute the user exit code! I've never seen user exit code excluded, unless by program code. What do you mean by "stop" in background. Of course, you can't make it stop there in background.
Post relevant code and we'll see what we can tell you. What does the code do?

User exit for MRP run - MD01

Hi All,
Can i know the use of "User exit parameter" field in MD01. as i know it means if we only want to plan the materials of a certain MRP controller, for example, we can enter the key of the appropriate MRP controller as the parameter.
in my scenario, we have already incorporated a user exit for MD01 - MRP Run.
i have 3 MRP controllers, but want to plan for only 2 MRP controllers, then how to enter in that field?
Regards,
Ram

HI,
User exit are available for Md01 transaction. You can plan material by MRP Type, MRP Controller,MRP Type, Procurement type & so on....
Once you activate user exit, you can select the same by drill down option in user exit Key field.
Regards,
Milind.

Trigger a waiting ABAP program from a User Exit of CO01

Hi all,
   We would like to launch a ABAP program from a User Exit (EXIT_SAPLCOZV_001) of CO01, this ABAP program has a special characteristic: using Function Module RFC_PING_AND_WAIT, so this program will be existing until terminating event coming.
    Our purpose is terminate CO01 normally before finishing of ABAP program. We don't know if it's possible?
    Actually:
       1. when we use SUBMIT ..., the process will stop CO01 (stop not normally) and then launch ABAP program. => This is not suitable for our purpose.
       2. when we use SUBMIT ... and RETURN, CO01 will wait for finishing of ABAP program => This is not suitable for our purpose too, because we wish CO01 terminated normally when ABAP program is still existing and waiting for its terminating event.
Do you have a solution that is suitable for our purpose, could you please help us?
(The context is below:
Time: Begin-->CO finished> ABAP finished-->
   Launch CO01 --> Call User Exit --> Call ABAP program for waiting --> CO01 saved normally.
> ABAP program still waiting ---> waiting for terminating event
Thanks a lot,
Vinh Vo

Hi,
     Try with the function module BP_EVENT_RAISE, it takes eventid, and eventparm as import parameters in the User exit.
1) With Eventid, you create a background job of the ABAP program and schedule it. Eventparm can be the Production order number.
2) So when ever the Event is triggered the FM gets triggered and which in turn run the ABAP program, so the foreground the CO01 transaction runs without waiting for the ABAP program to complete.
Regards
Bala Krishna

Skip user exit call at BDC run.

Similar Messages

Maybe you are looking for