Processing of a BDC in background which internally triggers user exits

Hi experts,
I have a req. where in a BDC program would internally trigger a user exit to update values.The program is running well in the foreground and in display with errors.But in background it throws a "System error when creating a control".Can you please let me know the exact reason for this.
Thanks and Regards,
Anitha

i think there is one option 'After Job' in SM36
this might be helpful to you
regards
if you are creating your jobs via SM36, you should be able to to create the second job using
'After Job' option with the 'Start Status Dependent' checkbox switched on. This way the
second job will not start unless the first job finishes successfully.
Message was edited by: Surpreet Singh Bal

Similar Messages

BDC session -session qid value-inside user exit

hai,
when we process a BDC session from SM35,can we know the unique queue id for that particular session..i need that value to update a ztable in a user exit..this user exit is hit during the processing of that session..is their some system like variables storing the session id?
Edited by: kumar gaurav on Jan 26, 2012 1:13 AM

Hi Gaurav,
Check in table APQI .
with key combination we will get the queue id from this table, and here you will get the info like whether the session is craeted or in process or with error......

Stoping process of saving purchase order(ME21/ME21N) in the user exit.

Hi,
I am using user exit "EXIT_SAPMM06E_016" of purchase order. While creating PO and after user enters 1st line item or more items and presses save button, then this user exit will be called.
Now my requirement is I have to check "item delivery date" , if it is more than 300 days from creation date then I have to show popup for warning the user for the same and if user want to make the changes then this user exit should stops the process of saving the PO and returns and allows to change the PO.
Please help me in this.
how I can stop the saving process.
Thanks,
Deepak

Hi Deepak,
You can do it in IM_ITEM method
DATA: ls_mepoitem TYPE mepoitem.
ls_mepoitem = im_item->get_data( ).
if you check ls_mepoitem-quantity field it will give your required value....pls Go through the documentation below for the method
Documentation for the method
Processing of Item Data
Functionality
The PROCESS_ITEM method enables you to change the item data and check it
for correctness.
Parameters
The following parameters are available:
o IM_ITEM - Document item
The interface reference is of the category
IF_PURCHASE_ORDER_ITEM_MM. You can use all methods defined there.
Note
Please note the general hints on Error Handling.
If you wish to mark the document item as invalid, use the
INVALIDATE() method of the IF_PURCHASE_ORDER_ITEM_MM interface.
Regards
Byju

How to find which are the user exits that updating z table.

There was a question posted by someone else which said:
I have a z table. my requirement is to find the user exits that update the value to this table?
but my requirement is to get only those user exits that update my z table.
Before that question was rejected, it got 5 replies which made me think that this tip is worth sharing.
So the steps are:
Do a where-used list search from SE11
Click on Search Range button at bottom
Type UPDATE (you can also add Insert, Delete etc to select-option) to ABAP Key Words field
Say No to the popup that asks whether to include Fields of the Table
Result will show relevant programs with code snippets doing static Update on that custom table.

EWK1 would be too performance heavy in this case. It scans the source code to get the result.
You can however, download the list of programs given in where-used list, and give that as limiting condition in EWK1 or some other code scanning utility.
Using my method, where-used list of table is taken from database tables, and then code scanning is done only on the that list, not on entire Z* programs.
Try it yourself to notice the speed difference.

T-codes in HR in which we write User-exit

Please tell me the T-codes in HR-Module for which we can use User-exit or Badi .
Regards : Rajneesh

hi,
when u append the extract structure then u should see that the appended field is checked as 'field only' and not as hidden.
otherwise the user exit will not be trigrred.
also see that u have use appropriate exit depending on wheter it is transactional ,master,text or hierachy.
regards.
pls assign points if helpful.

Error attempting to process LSMW generated BDC in background via SM35

In our CRM 4.0 system, I used LSMW to create a recording of the Contact Person load transaction (BP). If I process the subsequent Batch Input Session via SM35 in either 'Foreground' or 'Display errors only' mode, everything works okay. If I try to process in 'Background' mode, The job fails with error DC006 - "Control Framework: Fatal error - GUI cannot be reached". My Basis resource feels that this LSMW program can not run in background.
Since I will be loading >100,000 records, I would prefer to run in Background. Does anyone know how to get around this error?
Thanks,
Tony

Hi Anthony..
I am running into the exact problem..cannot run the recording in background....it works fine in foreground....well i dont have more than 20000 records, so i guess i can still do it in foreground..
I had the idea of using IDOCS..but its a little too complicated and its not worth all the mapping and conversion for just 15 fields that i have recorded and want to load..
I beleive that you have used some BAPI's to load data...
I would appreciate if you can help me with those BAPI's. I need to get done with this loads early next week.. So it wud be great if you share the BAPI's that you have used..
Thanks in advance..
Binoy

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

Is it possible to trigger user exit in BDC?

Hi experts,
I am having issue as follows.
when i am successfully creating rework code & UD code through tcode QA11 manually.
If i am doing manually some user exits will be called and there rework code will be generated successfully.
But i have used QA11 in my program using call transaction QA11 in back ground mode.
It is creaing UD code successfully.But rework code also has to be generated in back ground through user exit.
But that is not happening.
But internally my user exits are not calling when i run my program in back ground or fore ground.
Is there any problem of triggering user exists when running BDC in back ground or foreground?
Now i am unable to create rework code through QA11 why because user exists were not calling internally.
Thanks & Regards,
LOKESH GOUD

why dont you keep a break point and debug??

Which user-exit or BAPI triggered when a schedule line is changed

Dear All,
Does anyone know which user-exit, enhancement or BAPI is triggered when we do change on schedule line item?
Let's say, I have two line schedule line item, then I do change for delivery date. After triggered "Item Availability" button, system will accumulate confirmed Qty on first line and second line into first line. And then the second line will remain zero.
I need to know, which enhancement or user exit or any standard FM do this process.
I searched, but not found any user exit or enhancement that will go through.
Best regards,
Dinivian.

Hi,
For MFBF there are sollowing user-exits....
XMRM0001 - Backflushing in Repetitive Manufacturing.
PTRM0001 - For lead column in REM planning Table.
SAPLRMPU - Customer Exit for Article Staging.
Reward points if useful....
Regards
AK

Need to schedule a report in background from an user exit

Hi Experts,
I have a requirement to execute a report in background from an user exit. Please advise.
Thanks in advance,
Vivenchandar R

Use the submit statement.
For example
SUBMIT zipr_trans_details "VIA SELECTION-SCREEN
 WITH so_trdt IN lr_tr_period
 WITH so_empno IN lr_emp
 AND RETURN.
Where zipr_trans_details is the report name.
Message was edited by:
 Naren Someneni

Which user exit belongs to which project

hello,
1) imagine I have got the user exit name
   EXIT_SAPMV45A_003 and now I want to find out
   to which project this user exit belongs.
   How can I obtain this information
2) Is it possible to deactivate only one
   or designated user exit instaed of the
   whole project
Ilhan

Hi,
Herewith i am sending the sample coding for the report which will help to u can find through whatever transaction codes are having how many user exits are there and through that u can run that user exits and u can go to any transaction code.
*& Report YMS_USEREXITTEST                                            *
REPORT YMS_USEREXITTEST 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.
-End of Program-
Thanks,
Shankar

Find out queries which contain user-exit variable

Hello.
I want to get a list of BEX queries, which contain my user-exit variable, defined in ZXRSRU01. Could anybody tell me how I can achieve this?

Hello, Konstantin.
You can use differnet methods to do this.
Method №1.
You can open one (any) query, that uses your variable in Metadata repository (active objects). If you don't know such query - you can create it.
In the description of your query you can find which variable is used by this query.
Open your variable.
There you can find all queries, that uses you variable.
Method №2.
Open SE11. Choose table RSZELTDIR.
Determine ELTUID of your variable (OBJVERS='A',MAPNAME=Variable ID).
Open SE11. Choose table RSZELTXREF.
Select ALL SELTUID with OBJVERS='A', TELTUID=ELTUID (see above), LAYTP=VAR
Open SE11. Choose table RSZELTDIR.
Select all MAPNAME with OBJVERS='A', ELTUID=lists of SELTUID (see above)
You can take texts from table RSZELTTXT.
Best regards,
Alexander Kuzmich

In FCP x backup process is constantly running in background even though its done which results into slow working of FCP x. any idea to resolve the issue. I am using 10.1.3 and facing the problem ever since i have updated my FCP x to 10.1.3

in FCP x backup process is constantly running in background even though its done which results into slow working of FCP x. any idea to resolve the issue? I am using 10.1.3 and facing the problem ever since i have updated my FCP x to 10.1.3

Go into preferences and under playback turn off background render. That helped speed things for me when working with large files.

No batch input data for screen SAPMSSY0 0120 when running BDC in background

Hi Experts,
I am facing an issue "No batch input data for screen SAPMSSY0 0120" when running a BDC for VA01 in background.
The scenario is like we have EDI orders coming into SAP in the form Idocs. These EDI orders are processed by Function module
IDOC_INPUT_ORDERS. This FM module internally calls VA01 (Call Transaction) to create Sales Orders in SAP.
Now we have a scenario in which we want a popup screen to come up & ask for selection of record from list of records displayed on popup screen. In background since we can not show up a screen, we are programatically selecting the record we want & going ahead.
Now what is happening is during foerground the functionality is working abosultely fine, that is incoming idoc is getting posted successfully in SAP with status of 53. Incase of back ground processing of the same we are getting an error
No batch input data for screen SAPMSSY0 0120
I have checked this screen through screen painer(SE51) & i did not find any element on this screen but Element list
shows one field Syst-Xcode.
Kindly guide me how to fix the issue so that the same can work as expected in background.
Regards,
Chetan.

Hi Chetan,
List screens utilize SAPMSSY0/0120. Please check within your ABAP coding if you have any customer exit that tries to issue WRITE statements. If so, either remove them or add logic to not issue them in background (e.g. SY-BATCH = 'X'). Another culprit might be a SUBMIT statement in a user exit, which triggers a report with list output. I'm not completely sure, but I think the screen is also used for some value helps (do you have any coding forcing a value help popup?).
Hope this helps, harald

Document not posting through F-02 BDC in background.

Hi,
While trying to post park documents for a company code through F-02 using BDC in background mode N, when any single document is having any error then all the documents for that company code are going in error state and not getting posted.When checked in debug mode for the error document, it is showing the Profit center field is not present on screen at BDC whereas the profit center field is actually passed and is present.Please advise.
Edited by: rohan.das on Dec 20, 2011 2:40 PM

There is a POP-Up window in the process, that is not coming in background. identify that screen no and not pass any data, another option is pass OK_CODE for that particular screen.
Hope it's might be useful for you.
Thanks,
Prarthan

Processing of a BDC in background which internally triggers user exits

Similar Messages

Maybe you are looking for