BackGround code for any transaction

Hi Experts,
I want to see the back ground code for transaction "LISTCUBE".
Please guide me how can i do that.
Thanks in advance.

HI,
When you enter the t-code above you will find sytem.
Go to system, then there you will find status, click on it.
A new window will open, there under SAP data you will find program(screen) double click on it, it will display the program.
Hope this helps.
Thanks,
Rahul

Similar Messages

Blocking a company code for all transactions.

A compnay code is having two plants assigned. No open documents in that company code.
How to block the company code for any transactions including purchase document creation?
However all the past data to be available for viewing and reference.
Thanks in advance.
Narasimharao

Dear Narasimharao ,
You can remove authorization from user profile to use this company code.
And when someone try to save any documents , error message will be send.
hope this could help you.
best regards,
Carlos Moçatto

How to create a background job for call transaction

hi gurus
can any one suggest me
how to create the background job for call transaction.
thank you
regards
kals.

Hi,
Refer
https://forums.sdn.sap.com/click.jspa?searchID=10926107&messageID=889652
Regards
Kiran Sure

Need BDC code for Call Transaction of VL31N, which creates Inbound del.s,

Hi Experts,
Is any body does have the BDC (CALL TRANSACTION) code for VL31N transaction, where we can crete INBOUND deliveries from Purc Orders.
Actually, currently am doing by using FM - GN_DELIVERY_CREATE, but, its not given me a chance to incorporate BATCH SPLIT functionality. So, decided to go with BDC
1 - Is this VL31N is Okay for BDC, bcoz, some where I red that, since its a ENJOY tx, its NOT recommended?
2 - Is there any other FM, BAPI to create INBOUND deliveries from POs, which can take care of BATCH SPLIT functionality?
3 - BDC code for VL31N tx.
thanq
Edited by: Srinivas on Jul 29, 2008 1:47 PM

1 - Is this VL31N is Okay for BDC, bcoz, some where I red that, since its a ENJOY tx, its NOT recommended?
yes you can do that .
2 - Is there any other FM, BAPI to create INBOUND deliveries from POs, which can take care of BATCH SPLIT functionality?
using BDC we can achieve the Barch split functionality.
3 - BDC code for VL31N tx.
Record using SHDB it will give you.

Hi guys please give me sample code for call transaction that handles error

hi guys, please give me sample code for call transaction that handles error,
please send me the sample code in which there should be all decleration part and everything, based on the sample code i will develop my code.
please do help me as it is urgent.
thanks and regards.
prasadnn.

Hi Prasad,
Check this code.
Source Code for BDC using Call Transaction
*Code used to create BDC
*& Report ZBDC_EXAMPLE                                                *
*& Example BDC program, which updates net price of item 00010 of a     *
*& particular Purchase order(EBELN).                                   *
REPORT ZBDC_EXAMPLE NO STANDARD PAGE HEADING
                      LINE-SIZE 132.
Data declaration
TABLES: ekko, ekpo.
TYPES: BEGIN OF t_ekko,
    ebeln TYPE ekko-ebeln,
    waers TYPE ekko-waers,
    netpr TYPE ekpo-netpr,
    err_msg(73) TYPE c,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko,
      it_error TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_error TYPE t_ekko,
      it_success TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_success TYPE t_ekko.
DATA: w_textout            LIKE t100-text.
DATA: gd_update TYPE i,
      gd_lines TYPE i.
*Used to store BDC data
DATA: BEGIN OF bdc_tab OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA: END OF bdc_tab.
*Used to stores error information from CALL TRANSACTION Function Module
DATA: BEGIN OF messtab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
*Screen declaration
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME
                                    TITLE text-001. "Purchase order Num
SELECT-OPTIONS: so_ebeln FOR ekko-ebeln OBLIGATORY.
SELECTION-SCREEN END OF BLOCK block1.
SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME
                                    TITLE text-002. "New NETPR value
PARAMETERS: p_newpr(14)   TYPE c obligatory. "LIKE ekpo-netpr.
SELECTION-SCREEN END OF BLOCK block2.
*START-OF-SELECTION
START-OF-SELECTION.
Retrieve data from Purchase order table(EKKO)
SELECT ekkoebeln ekkowaers ekpo~netpr
    INTO TABLE it_ekko
    FROM ekko AS ekko INNER JOIN ekpo AS ekpo
      ON ekpoebeln EQ ekkoebeln
   WHERE ekko~ebeln IN so_ebeln AND
         ekpo~ebelp EQ '10'.
*END-OF-SELECTION
END-OF-SELECTION.
Check data has been retrieved ready for processing
DESCRIBE TABLE it_ekko LINES gd_lines.
IF gd_lines LE 0.
Display message if no data has been retrieved
    MESSAGE i003(zp) WITH 'No Records Found'(001).
    LEAVE TO SCREEN 0.
ELSE.
Update Customer master data (instalment text)
    LOOP AT it_ekko INTO wa_ekko.
      PERFORM bdc_update.
    ENDLOOP.
Display message confirming number of records updated
    IF gd_update GT 1.
      MESSAGE i003(zp) WITH gd_update 'Records updated'(002).
    ELSE.
      MESSAGE i003(zp) WITH gd_update 'Record updated'(003).
    ENDIF.
Display Success Report
Check Success table
    DESCRIBE TABLE it_success LINES gd_lines.
    IF gd_lines GT 0.
    Display result report column headings
      PERFORM display_column_headings.
    Display result report
      PERFORM display_report.
    ENDIF.
Display Error Report
Check errors table
    DESCRIBE TABLE it_error LINES gd_lines.
If errors exist then display errors report
    IF gd_lines GT 0.
    Display errors report
      PERFORM display_error_headings.
      PERFORM display_error_report.
    ENDIF.
ENDIF.
*&      Form DISPLAY_COLUMN_HEADINGS
      Display column headings
FORM display_column_headings.
WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.
SKIP.
WRITE:2 'The following records updated successfully:'(013).
WRITE:/ sy-uline(42).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(004), sy-vline,
          (11) 'Old Netpr'(005), sy-vline,
          (11) 'New Netpr'(006), sy-vline.
WRITE:/ sy-uline(42).
ENDFORM.                    " DISPLAY_COLUMN_HEADINGS
*&      Form BDC_UPDATE
      Populate BDC table and call transaction ME22
FORM bdc_update.
PERFORM dynpro USING:
      'X'   'SAPMM06E'        '0105',
      ' '   'BDC_CURSOR'      'RM06E-BSTNR',
      ' '   'RM06E-BSTNR'     wa_ekko-ebeln,
      ' '   'BDC_OKCODE'      '/00',                      "OK code
      'X'   'SAPMM06E'        '0120',
      ' '   'BDC_CURSOR'      'EKPO-NETPR(01)',
      ' '   'EKPO-NETPR(01)' p_newpr,
      ' '   'BDC_OKCODE'      '=BU'.                      "OK code
Call transaction to update customer instalment text
CALL TRANSACTION 'ME22' USING bdc_tab MODE 'N' UPDATE 'S'
         MESSAGES INTO messtab.
Check if update was succesful
IF sy-subrc EQ 0.
    ADD 1 TO gd_update.
    APPEND wa_ekko TO it_success.
ELSE.
Retrieve error messages displayed during BDC update
    LOOP AT messtab WHERE msgtyp = 'E'.
    Builds actual message based on info returned from Call transaction
      CALL FUNCTION 'MESSAGE_TEXT_BUILD'
           EXPORTING
                msgid               = messtab-msgid
                msgnr               = messtab-msgnr
                msgv1               = messtab-msgv1
                msgv2               = messtab-msgv2
                msgv3               = messtab-msgv3
                msgv4               = messtab-msgv4
           IMPORTING
                message_text_output = w_textout.
    ENDLOOP.
Build error table ready for output
    wa_error = wa_ekko.
    wa_error-err_msg = w_textout.
    APPEND wa_error TO it_error.
    CLEAR: wa_error.
ENDIF.
Clear bdc date table
CLEAR: bdc_tab.
REFRESH: bdc_tab.
ENDFORM.                    " BDC_UPDATE
      FORM DYNPRO                                                   *
      stores values to bdc table                                    *
--> DYNBEGIN                                                      *
--> NAME                                                          *
--> VALUE                                                         *
FORM dynpro USING    dynbegin name value.
IF dynbegin = 'X'.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-program,
           value TO bdc_tab-dynpro,
           'X' TO bdc_tab-dynbegin.
    APPEND bdc_tab.
ELSE.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-fnam,
           value TO bdc_tab-fval.
    APPEND bdc_tab.
ENDIF.
ENDFORM.                               " DYNPRO
*&      Form DISPLAY_REPORT
      Display Report
FORM display_report.
FORMAT COLOR COL_NORMAL.
Loop at data table
LOOP AT it_success INTO wa_success.
    WRITE:/      sy-vline,
            (10) wa_success-ebeln, sy-vline,
            (11) wa_success-netpr CURRENCY wa_success-waers, sy-vline,
            (11) p_newpr, sy-vline.
    CLEAR: wa_success.
ENDLOOP.
WRITE:/ sy-uline(42).
REFRESH: it_success.
FORMAT COLOR COL_BACKGROUND.
ENDFORM.                    " DISPLAY_REPORT
*&      Form DISPLAY_ERROR_REPORT
      Display error report data
FORM display_error_report.
LOOP AT it_error INTO wa_error.
    WRITE:/      sy-vline,
            (10) wa_error-ebeln, sy-vline,
            (11) wa_error-netpr CURRENCY wa_error-waers, sy-vline,
            (73) wa_error-err_msg, sy-vline.
ENDLOOP.
WRITE:/ sy-uline(104).
REFRESH: it_error.
ENDFORM.                    " DISPLAY_ERROR_REPORT
*&      Form DISPLAY_ERROR_HEADINGS
      Display error report headings
FORM display_error_headings.
SKIP.
WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.
SKIP.
WRITE:2 'The following records failed during update:'(008).
WRITE:/ sy-uline(104).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(009), sy-vline,
          (11) 'Netpr'(010), sy-vline,
          (73) 'Error Message'(012), sy-vline.
WRITE:/ sy-uline(104).
FORMAT COLOR COL_NORMAL.
ENDFORM.                    " DISPLAY_ERROR_HEADINGS
Hope this resolves your query.
Reward all the helpful answers.
Regards

OTL: Timecard Audit Template require reason code for all transaction.

We are currently using OTL with CLA template with interface time entry from external system.
When monthly time entry interfaced into OTL each employee have to review and update their time and submit to manager, but when process to audit template they has been forced to update reason code for all transactions.
We suppose to update the reason code only for the modified transactions. Please help me.
Nonny.

nondhasid,
If you are not modifying those records which are asking for a reason field to be filled, then it should be coming from the Late setup. Check the CLA setup.
--Shiv

Shortcut for any transaction

Hi All,
can any body tell me how to create a shortcut on the desktop for any transaction.
Ex-i am having a TCode BP when ever i click on the shortcut i should get the BP screen directly without going through the logon pad- BP .
Regards,
SAP.

Thank you for your quick reply.My problem is that i am having a SA38 query which is created based on Quick viewer, for that query i need a shortcut on the desktop. exp-
What i am doing-
1. I have created SA 38 query and i will execute in SA38 when i execute that query i will get one more screen based on my selection screen.
What i want-
when i execute SA38 query the screen which i get i want that screen as shortcut on my desktopI
Regards,
VRS.
Edited by: rajasekhar on Jan 19, 2010 7:59 AM
Edited by: rajasekhar on Jan 19, 2010 8:05 AM

BDC code for MM01 Transaction

Hi All,,
 Please give Entire BDC code for MM01 Transaction.
i will change as per my requirement.
I think this is already done by some ABAP Consultants.
plz dont give answers like do recording for that transaction MM01. I know recording...
For time constraiint, I have to complete soon.....
Thanks in Advance
BestRegards,
Anil

Hi,
The below code is using the Session Method
report ZDS_BDC_MM01
 no standard page heading line-size 255.
include bdcrecx1.
*parameters: dataset(132) lower case.
*** DO NOT CHANGE - the generated data section - DO NOT CHANGE ***
* If it is nessesary to change the data section use the rules:
* 1.) Each definition of a field exists of two lines
* 2.) The first line shows exactly the comment
* '* data element: ' followed with the data element
* which describes the field.
* If you don't have a data element use the
* comment without a data element name
* 3.) The second line shows the fieldname of the
* structure, the fieldname must consist of
* a fieldname and optional the character '_' and
* three numbers and the field length in brackets
* 4.) Each field must be type C.
*** Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record OCCURS 0,
* data element: MATNR
 MATNR_001(018),
* data element: MBRSH
 MBRSH_002(001),
* data element: MTART
 MTART_003(004),
* data element: XFELD
 KZSEL_01_004(001),
* data element: XFELD
 KZSEL_02_005(001),
* data element: MAKTX
 MAKTX_006(040),
* data element: MEINS
 MEINS_007(003),
* data element: MAKTX
 MAKTX_008(040),
 end of record.
*** End generated data section ***
start-of-selection.
*perform open_dataset using dataset.
perform open_group.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME ='C:\DHRUV.TXT'
 FILETYPE = 'DAT'
* HAS_FIELD_SEPARATOR = ' '
* HEADER_LENGTH = 0
* READ_BY_LINE = 'X'
* DAT_MODE = ' '
* CODEPAGE = ' '
* IGNORE_CERR = ABAP_TRUE
* REPLACEMENT = '#'
* CHECK_BOM = ' '
* VIRUS_SCAN_PROFILE =
* NO_AUTH_CHECK = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
 DATA_TAB = RECORD
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*do.
LOOP AT record.
*read dataset dataset into record.
if sy-subrc <> 0. exit. endif.
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'
 record-MATNR_001.
perform bdc_field using 'RMMG1-MBRSH'
 record-MBRSH_002.
perform bdc_field using 'RMMG1-MTART'
 record-MTART_003.
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)'
 record-KZSEL_01_004.
perform bdc_field using 'MSICHTAUSW-KZSEL(02)'
 record-KZSEL_02_005.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'MAKT-MAKTX'
 record-MAKTX_006.
perform bdc_field using 'BDC_CURSOR'
 'MARA-MEINS'.
perform bdc_field using 'MARA-MEINS'
 record-MEINS_007.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'BDC_CURSOR'
 'MAKT-MAKTX'.
perform bdc_field using 'MAKT-MAKTX'
 record-MAKTX_008.
perform bdc_dynpro using 'SAPLSPO1' '0300'.
perform bdc_field using 'BDC_OKCODE'
 '=YES'.
perform bdc_transaction using 'MM01'.
*enddo.
ENDLOOP.
perform close_group.
*perform close_dataset using dataset.
*Text elements
* E00 Error opening dataset, return code:
* I01 Session name
* I02 Open session
* I03 Insert transaction
* I04 Close Session
* I05 Return code =
* I06 Error session created
* S01 Session name
* S02 User
* S03 Keep session
* S04 Lock date
* S05 Processing Mode
* S06 Update Mode
* S07 Generate session
* S08 Call transaction
* S09 Error sessn
* S10 Nodata indicator
* S11 Short log
*Messages
* Message class: MS
*613 Please enter a session name and user name
The Below is the coding for the Call Transaction...
report ZDS_BDC_MM01_2
 no standard page heading line-size 255.
*include bdcrecx1.
*parameters: dataset(132) lower case.
*** DO NOT CHANGE - the generated data section - DO NOT CHANGE ***
* If it is nessesary to change the data section use the rules:
* 1.) Each definition of a field exists of two lines
* 2.) The first line shows exactly the comment
* '* data element: ' followed with the data element
* which describes the field.
* If you don't have a data element use the
* comment without a data element name
* 3.) The second line shows the fieldname of the
* structure, the fieldname must consist of
* a fieldname and optional the character '_' and
* three numbers and the field length in brackets
* 4.) Each field must be type C.
*** Generated data section with specific formatting - DO NOT CHANGE ***
data: begin of record OCCURS 0,
* data element: MATNR
 MATNR_001(018),
* data element: MBRSH
 MBRSH_002(001),
* data element: MTART
 MTART_003(004),
* data element: XFELD
 KZSEL_01_004(001),
* data element: MAKTX
 MAKTX_005(040),
* data element: MEINS
 MEINS_006(003),
* data element: MTPOS_MARA
 MTPOS_MARA_007(004),
 end of record.
DATA: FLNAME TYPE STRING.
*** End generated data section ***
DATA: BDCDATA LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
*** MESSAGE******
DATA: BEGIN OF MESSTAB OCCURS 0.
 INCLUDE STRUCTURE BDCMSGCOLL.
 DATA: MATNR TYPE MARA-MATNR,
 END OF MESSTAB.
****END OF MESSAGE****
PARAMETERS: FILENAME TYPE RLGRAP-FILENAME.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILENAME.
CALL FUNCTION 'F4_FILENAME'
 IMPORTING
 FILE_NAME = FILENAME.
start-of-selection.
*perform open_dataset using dataset.
perform open_group.
FLNAME = FILENAME.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
 FILENAME = FLNAME
 FILETYPE = 'DAT'
* HAS_FIELD_SEPARATOR = ' '
* HEADER_LENGTH = 0
* READ_BY_LINE = 'X'
* DAT_MODE = ' '
* CODEPAGE = ' '
* IGNORE_CERR = ABAP_TRUE
* REPLACEMENT = '#'
* CHECK_BOM = ' '
* VIRUS_SCAN_PROFILE =
* NO_AUTH_CHECK = ' '
* IMPORTING
* FILELENGTH =
* HEADER =
TABLES
 DATA_TAB = record
EXCEPTIONS
 FILE_OPEN_ERROR = 1
 FILE_READ_ERROR = 2
 NO_BATCH = 3
 GUI_REFUSE_FILETRANSFER = 4
 INVALID_TYPE = 5
 NO_AUTHORITY = 6
 UNKNOWN_ERROR = 7
 BAD_DATA_FORMAT = 8
 HEADER_NOT_ALLOWED = 9
 SEPARATOR_NOT_ALLOWED = 10
 HEADER_TOO_LONG = 11
 UNKNOWN_DP_ERROR = 12
 ACCESS_DENIED = 13
 DP_OUT_OF_MEMORY = 14
 DISK_FULL = 15
 DP_TIMEOUT = 16
 OTHERS = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
LOOP AT record.
DATA:
 CNT TYPE I.
 CNT = CNT + 1.
 REFRESH BDCDATA.
perform bdc_dynpro using 'SAPLMGMM' '0060'.
perform bdc_field using 'BDC_CURSOR'
 'RMMG1-MTART'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'RMMG1-MATNR'
 record-MATNR_001.
perform bdc_field using 'RMMG1-MBRSH'
 record-MBRSH_002.
perform bdc_field using 'RMMG1-MTART'
 record-MTART_003.
perform bdc_dynpro using 'SAPLMGMM' '0070'.
perform bdc_field using 'BDC_CURSOR'
 'MSICHTAUSW-DYTXT(01)'.
perform bdc_field using 'BDC_OKCODE'
 '=ENTR'.
perform bdc_field using 'MSICHTAUSW-KZSEL(01)'
 record-KZSEL_01_004.
perform bdc_dynpro using 'SAPLMGMM' '4004'.
perform bdc_field using 'BDC_OKCODE'
 '/00'.
perform bdc_field using 'MAKT-MAKTX'
 record-MAKTX_005.
perform bdc_field using 'BDC_CURSOR'
 'MARA-MEINS'.
perform bdc_field using 'MARA-MEINS'
 record-MEINS_006.
perform bdc_field using 'MARA-MTPOS_MARA'
 record-MTPOS_MARA_007.
perform bdc_dynpro using 'SAPLSPO1' '0300'.
perform bdc_field using 'BDC_OKCODE'
 '=YES'.
*perform bdc_transaction using 'MM01'.
CALL TRANSACTION 'MM01' USING BDCDATA
 MODE 'N'
 UPDATE 'A'
 MESSAGES INTO MESSTAB.
READ TABLE MESSTAB INTO MESSTAB INDEX CNT.
 IF MESSTAB-MSGTYP = 'E'.
 MESSTAB-MATNR = RECORD-MATNR_001.
 MODIFY MESSTAB INDEX CNT FROM MESSTAB. " TRANSPORTING MATNR.
 ENDIF.
ENDLOOP.
FORM OPEN_GROUP.
CALL FUNCTION 'BDC_OPEN_GROUP'
 EXPORTING CLIENT = SY-MANDT
 GROUP = 'MM01'
 USER = SY-UNAME
 KEEP = 'X'.
ENDFORM.
FORM BDC_INSERT.
CALL FUNCTION 'BDC_INSERT'
 EXPORTING
 TCODE = 'MM01'
* POST_LOCAL = NOVBLOCAL
* PRINTING = NOPRINT
* SIMUBATCH = ' '
* CTUPARAMS = ' '
 TABLES
 DYNPROTAB = BDCDATA
 EXCEPTIONS
 INTERNAL_ERROR = 1
 NOT_OPEN = 2
 QUEUE_ERROR = 3
 TCODE_INVALID = 4
 PRINTING_INVALID = 5
 POSTING_INVALID = 6
 OTHERS = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.
END-OF-SELECTION.
LOOP AT MESSTAB.
 IF MESSTAB-MSGTYP = 'E'.
 WRITE:/ 'ERROR OCCURED ON MATNR = ',MESSTAB-MATNR , 'MESSAGE : MATNR ALREADY EXISTS IN MARA!!!'.
 ENDIF.
ENDLOOP.
perform close_group.
*perform close_dataset using dataset.
*& Form close_group
* text
* --> p1 text
* <-- p2 text
FORM close_group .
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
 NOT_OPEN = 1
 QUEUE_ERROR = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " close_group
*& Form bdc_dynpro
* text
* -->P_0270 text
* -->P_0271 text
FORM bdc_dynpro USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM. " bdc_dynpro
*& Form bdc_field
* text
* -->P_0275 text
* -->P_0276 text
FORM bdc_field USING FNAM FVAL.
IF FVAL <> ' '.
 CLEAR BDCDATA.
 BDCDATA-FNAM = FNAM.
 BDCDATA-FVAL = FVAL.
 APPEND BDCDATA.
ENDIF.
ENDFORM. " bdc_field
*Text elements
* E00 Error opening dataset, return code:
* I01 Session name
* I02 Open session
* I03 Insert transaction
* I04 Close Session
* I05 Return code =
* I06 Error session created
* S01 Session name
* S02 User
* S03 Keep session
* S04 Lock date
* S05 Processing Mode
* S06 Update Mode
* S07 Generate session
* S08 Call transaction
* S09 Error sessn
* S10 Nodata indicator
* S11 Short log
HTH
Regards,
Dhruv Shah

Part codes for any Cisco part

Hi,
Any one knows in single file/url where we can check Part codes for any Cisco part.
I need mostly for SPFs modules.
Thanks
Venkat

http://www.cisco.com/en/US/docs/interfaces_modules/transceiver_modules/compatibility/matrix/OL632702.html
http://www.cisco.com/en/US/docs/routers/7200/install_and_upgrade/gbic_sfp_modules_install/5067g.html
http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6578/product_data_sheet0900aecd801f931c_ps5000_Products_Data_Sheet.html
http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6576/product_data_sheet0900aecd80582763.html
http://www.cisco.com/en/US/prod/collateral/modules/ps5455/ps6577/product_data_sheet0900aecd8033f885.html
http://www.cisco.com/en/US/prod/collateral/modules/ps5455/data_sheet_c78-455693.html

Method (se24) to search badi's for any transaction code

hi,
is there any other way to search badi except se18 name? my friend told me that we can search badi by using one method(se24) also but he also don't know the name of that method. can any one tell me?

Hi
1) First go to any transaction->iN THE menu bar SYSTEM->STATUS->Get the program name ->double click->u will go to the program attached to the tcode.Now search term will be CALL CL_EXITHANDLER.Now u will get list of BADI'S available..
2) Goto SE24->Give class name as CL_EXITHANDLER->Display->double click on get_instance mathod->Now u will go inside the method->Now put break point on the cl_exithandler.Now go to any transaction code and pass dat..U will see that it will be stopped on the break point which u set on the cl_exithandler...In the exit name u can find list of badi's attached to the tcode..
or
1) Go to Maintain Transaction (TCODE- SE93).
Enter the Transaction Ex:- VD02 for which you want to find BADI.
Click on the Display push buttons.
Get the Package Name. (Package VS in this case)
Go to TCode: SE84->Enhancements->Business Add-inns->Definition
Enter the Package Name and Execute.
Here you get a list of all the Enhancement BADI?s for the given package MB.
Above replace VD02 by your Transaction for which you need BADIs.
Regards
Bala Krishna

Inplace viewer for any transaction code?

Hi all, have to say Im a beginner in the ABAP Field...
I would like to split the SAP-GUI screen in two parts for any SAP-transaction:
First screen : any transaction S000, SE80 whatever...
Second screen: a static document, to show for example a guideline for the even called transaction
Thanks a lot for any suggestion : )
@Gurus
I found this demo report:
OM_DEMO_OBJECTMANAGER_SINGLE
Do you think it could be possible to modify for my needs ?
Edited by: carmine dagostino on Feb 6, 2008 4:10 PM

You could try writing a program that works like the ABAPDOCU transaction..
On the left hand side have a Tree type structure and on the right have the documentation, or whatever.
Try debugging the ABAPDOCU transaction . The interesting bit from your point of view is expanding and executing the ABAP code that appears on the right of the screen.
I think the actual sap program is SAPMSABAPDEMOS_TREE.
Cheers
jimbo

How to Find implemented Enhancements impementations for any Transaction ?

Hi Folks,
We are having standard transactions to find User Exits, Customer Exits, Filed Exits, BAdis..
Accordingly, in any program, we can find out the enhancement code..
Similarly, If I implement any implicit enhancement , and if others run any transaction containing similar code in part of there application, how can these implementations can be traced out by others, with out debugging entire code..??
<<Text removed>>
Cheers..!!
Edited by: Matt on Feb 16, 2009 10:12 AM - Do not offer points

Goto CMOD
F4 for project,
information system
Yow can find the PLUS button on the pop up window.
Deselect inactive and partially active check box and press enter
You can find the projects activated.
Regards,
santosh reddy

Block company code for any usage

Hi
how to find the compnay code or Plant blocked for any usage like block for transactions like master data creation or any positing like good receiot etc. Please confirm.
Madhavan

You can also block all posting periods, trough OB52 but it would depend in the Posting Period Variant of the company
Regards
Jose

Added code for VA01 transaction ----in the include MV45AFZZ

Hi All,
I have added the code for pop-up
if the quantity is greter than 20000 then we need to give the confirm pop-up.
for that i have added code like this.
When we clik on YES it will save the order.
suppose if i clik on NO then i need to change the quantiy value.
Whats needs to be doing for this.
Please help me on this.
IF ( vbak-vkorg = 'CA01' OR vbak-vkorg = 'CA02' OR
 vbak-vkorg = 'CA03' ).
 IF vbak-netwr > '50000.00'. "Comparing quatity value
 w_txt = 'Order Quantity exceeded 50000 CAD. Please confirm'.
 w_txt1 = 'Order Quantity Check'.
 MESSAGE w901(zmsg1) WITH '50,000.00 CAD'.
 CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
 EXPORTING
 defaultoption = 'Y'
 textline1 = w_txt
 TEXTLINE2 = ' '
 titel = w_txt1
 START_COLUMN = 25
 START_ROW = 6
 cancel_display = ' '
 IMPORTING
 answer = w_ans.
 CASE w_ans.
 WHEN 'J'. "This is for COnfirm means Yes
 CONTINUE.
 WHEN 'N'. "This is for NO
 SET SCREEN 4008.
 CALL SCREEN 4008.
 LEAVE TO SCREEN 4008.
Thanks
Sriman.

Hi,
I assume that you are writing this code in "USEREXIT_SAVE_DOCUMENT_PREPARE". If not that first thing you do is move your code here.
The next thing is modify your code like this
IF ( vbak-vkorg = 'CA01' OR vbak-vkorg = 'CA02' OR
 vbak-vkorg = 'CA03' ).
DATA: lv_screenno TYPE syst-dynnr.
IF vbak-netwr > '50000.00'.
 w_txt = 'Order Quantity exceeded 50000 CAD. Please confirm'.
 w_txt1 = 'Order Quantity Check'.
 CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
 EXPORTING
 defaultoption = 'Y'
 textline1 = w_txt
 titel = w_txt1
 cancel_display = ' '
 IMPORTING
 answer = w_ans.
 CASE w_ans.
 WHEN 'J'. "This is for COnfirm means Yes
 WHEN 'N'. "This is for NO
* SET SCREEN 4008. "Remove this line
* LEAVE TO SCREEN 4008. "Remove this line
*" No need to define variable FCODE again,
*" it is alreay define in MV45ACOM
 fcode = 'ENT1'. "sy-ucomm. Add this line
 lv_screenno = sy-dynnr. "Add this line
 LEAVE TO SCREEN lv_screenno. "Add this line
 ENDCASE.
ENDIF.
ENDIF.
Let me know if you have any question.
Regards,
RS

Getting Common Error for any Transaction posting- Fund Management

Hi,
I have created Budget against Commitment Items and linked those commitment Items to GL.
When I am posting any Transaction in F-02, for the same Commitment Item for a less amount, I am getting an error message as shown in the screen shot
When I try posting with another Commitment Item unlike before, I get the same message and same amount.
Now I want to check why in case of both the transactions I am getting the same Budget exceeding message. Please advice how to check the budget.

Hi,
It depends... First of all, I'd suggest running FMAVCREINIT transaction in order to make sure that your AVC ledgers are in good shape.
If you still have the problem, please, revert back.
Regards,
Eli

BackGround code for any transaction

Similar Messages

Maybe you are looking for