Issue with using call transaction CJ9F and F.M BAPI_PROJECT_MAINTAIN

Hello All,
In my custom program for a given project in selection screen we are getting all the related data as shown in CJ20N, in this screen I first created the WBS element and during save we used F.M BAPI_PROJECT_MAINTAIN to update the data, and next called transaction CJ9F to update BLC, after this we are comming back to selection screen 1000.
Now from selection screen if i enter again into that project details screen and try to create a new WBS it is showing below information msg.
Changing the contents of the field is not permitted
Message no. CJ727
If i remove the call transaction CJ9F part during save i am not getting the above error msg.
I think i am getting this error when we call the function module BAPI_PROJECT_MAINTAIN twice in the program.
Please help me to resolve this issue, as this msg is not allowing to save or create anything.
But i found that if i come totally out of my custom transaction and enter once again into that Z transaction it is working fine with out that message
Please help me to resolve this issue.

Hi,
Not sure, but if it is possible, complete your project update using the custom transaction and do the CJ9F afterwards seperately.
Regards
Sreekanth

Similar Messages

Are there any issues with using OS X Mavericks and Premiere CC?

Are there any issues with using OS X Mavericks and Premiere CC?

Official statement: http://blogs.adobe.com/premierepro/2013/10/premiere-pro-and-mac-os-x-10-9-mavericks.html
Peter Garaway
Adobe
Premiere Pro

Issue with using crystal 8.5 and crystal 13 simultanously in dependent apps

Hello All,
I am facing some issue with different crystal versions used in applications. My application(let's say X13) is using crystal 13.0.10.1385 dotnet API and another application (let's say Y85) is using crystal 8.5 dotnet API version. My application X13 has a module which is dependent on application Y85 module and exchange information between them.
As both applications use crystal, CRPE32.dll is loaded in memory once for both the applications. The issue derives from the fact that the application X13 brings the crpe32.dll (version 13.0.10.1385) located in folder “C:\Program Files (x86)\SAP BusinessObjects\Crystal Reports for .NET Framework 4.0\Common\SAP BusinessObjects Enterprise XI 4.0\win32_x86” into memory. If the application X13 is not loaded into memory first then the version of crpe32.dll (i.e. 8.5.0.461) located in the application Y85 install folder will be used.
As we know that CR 13 and CR 8.5 are two entirely different API's now without any compatibility with each other. Now if my application X13 is initialized first and crpe32.dll (version 13.0.10.1385) is loaded in memory, on accessing the module dependent on application Y85, Y85 tries to make crystal calls.
It tries to call to PEOpenEngine, PEOpenPrintJob, PEGetNTables, PEGetNthTableLocation, crPEGetNthTableLogOnInfo and PEGetNDatabaseFields which executes fine but It is only the call to PEGetNthDatabaseFieldInfo that fails, with a return value of 0. Below is the sequence order of calls:
A 2013 .NET Crystal Engine is initialized first using ReportDocument.Load method or CrystalEngine.CRPE.InitCrpe.Also note that calling CrystalEngine.CRPE.CloseCrpe has no positive effect of eliminating the issue.
Subsequent calls to PEOpenEngine, PEOpenPrintJob, PEGetNTables, PEGetNthTableLocation, crPEGetNthTableLogOnInfo and PEGetNDatabaseFields all execute just fine.
It is only the call to PEGetNthDatabaseFieldInfo that fails, with a return value of 0.
Question arises here is how to get PEGetNthDatabaseFieldInfo working when the .NET Crystal Engine has already been initialized.
Is there a separate declare we can add to our VB6 code that will be compatible with crpe32.dll version 13.0.10.1385?
Or can we load both crpe32.dll (version 13.0.10.1385 and 8.5.0.461) in parallel and instruct .NET crystal to use version 13 and other one to use version 8.5 dll?
I have attached a sample code demonstrating same too. It will be great if anyone can help me on this.
Crystal versions involved : 13.0.10.1385 and 8.5.0.461
Visual Studio 2012
VB.net
WIN APP
Thanks
Saurabh

Hi Saurabh,
CR 8.5 never was side-by-side compatible with any other version of CR runtime.
And as of CR 9 you no longer are licensed to be able to use crpe32 as the reporting engine. R&D can change it at anytime so absolutely no support for it in that respect either. After CR 9 crpe32 was completely rewritten and a lot of parts were removed into their own dll's. The major parts were the DB drivers were renamed and the Parameter API's were also updated and old one's are no longer recognized, or may not work the same way.
So why not simply completely drop 8.5 since it is over 12 years old now... There is no reason you need to still be supporting it. We dropped support for it a long long time ago.
Don

Skip first screen of BD87 using call transaction with BDC_DATA option

hello all,
i am using call transaction with BDC_DATA option and i want to skip first screen, so can anyone please tell me how can i skip first screen of BD87 and get second screen that is output screen?
regards.

Hi
Build a BDCDATA with following code..
                                                      T     BD87
RBDMON00     1100     X
BDC_CURSOR     SX_DOCNU-LOW
                                                            BDC_OKCODE     =CRET
                                                            SX_DOCNU-LOW
SX_CRETI-LOW     00:00:00
                                                            SX_CRETI-HIGH     00:00:00
                                                            SX_UPDDA-LOW     05.02.2010
                                                            SX_UPDDA-HIGH     05.02.2010
                                                            SX_UPDTI-LOW     00:00:00
                                                            SX_UPDTI-HIGH     00:00:00
RBDMON00     0100     X
BDC_OKCODE     =BACK
RBDMON00     1100     X
BDC_OKCODE     /ECBAC
                                                            BDC_CURSOR     SX_DOCNU-LOW

Open Transaction MM01/MM02 with multiple views using CALL TRANSACTION

Hi All,
I want to open MM01/MM02 with multiple views using call transaction but in the parameter ID for Views (MMX) I can pass status of only one View.
SET PARAMETER ID 'MAT' FIELD v_mat.
SET PARAMETER ID 'VKO' FIELD ' '.
SET PARAMETER ID 'MTA' FIELD IT_MOFF-MTART.
SET PARAMETER ID 'MTP' FIELD IT_MOFF-MBRSH.
SET PARAMETER ID 'VTW' FIELD ' '.
SET PARAMETER ID 'BWT' FIELD ' '.
SET PARAMETER ID 'LGT' FIELD ' '.
SET PARAMETER ID 'MXX' FIELD 'K'. "Sales View
SET PARAMETER ID 'MM5' FIELD ' '.
CALL TRANSACTION 'MM02' AND SKIP FIRST SCREEN
Please suggest.
Regards,
Divya

I do not exactly understand what you mean, but what i already did:
- I checked that the fields are from the same type.
- KUNNR is initialized! I already had a look to the debugger, that's why i'm posting this in this forum.
any more comments on this ?
maybe i have to change anything in the z-transaction. Btw, this is what the parameter looks like in the transaction:
SELECTION-SCREEN BEGIN OF BLOCK Debitoren WITH FRAME TITLE text-001.
PARAMETERS pkunnr type kna1-kunnr OBLIGATORY.
SELECTION-SCREEN END OF BLOCK Debitoren.
Edited by: Sven Delangle on Sep 3, 2010 2:42 PM

Uploading XL file using call Transaction and running in back ground

Hi all,
I am updating the T-code VA01 using call TRansaction method ....
i am uploading the file is XL file for that i m using the FM ALSM_EXCEL_TO_INTERNAL_TABLE.
But if execute my program in the back ground This FM is giving Dump because it can not Execute in Back GRound...
Plz let me know any FM to upload data from Excel file Both from foreground and back ground....
Plz let me know ASAP..
Thanks,
Suresh

HI...,,
When u run any program in Background, it will not have any contacts with the presentation server.... You cannot upload a presentation server file..
But u can use the Application server file...
SO first store this excel file's data in Application server using the transaction CG3Z and then use the Open data set and read dataset to upload the application server file !!!
reward all helpful answers !!
regards,
sai ramesh

When we use call transaction and session method?

cud anyone tell me the exact difference between session and call transaction ? when we have to use ?

hi,
BATCH INPUT METHOD
Asynchronous processing
Transfer data for multiple transactions.
Synchronous database update.
A batch input process log is generated for each session.
Session cannot be generated in parallel.
CALL TRANSACTION METHOD:
Using CALL TRANSACTION USING statement
Faster processing of data
Synchronous processing
Transfer data for a single transaction.
No batch input processing log is generated.

Can we use Call transaction and session method in same program ?

Hi experts,
Is it suggested to use call Transaction and session method in the same Program ?
i have a doubt , why cant we use multiple call transactions in same program instead of session method if we have multiple transaction updations ?

Hi Dengyong Zhang,
we can use the call transation and session method in same program.
However for better performance it's benificial to use call trasaction method of BDC. but if u want to upload very large amount of data then Session method is more preferable to use.
Session method is one of the method of BDC.
U can also use BAPI to upload the data in SAP but it's a different concept than BDC. Performance wise BAPI is more advantageous than BDC.

Creating PO with me21 using call transaction

hi,
I need some help regarding the application:
i have to build a custom screen having fields for creating PO using me21 transaction using call transaction.
would anybdy please guide me how to do it.
i wd appreciate ur help

Hi Harpreet
For creating a custom screen you will ve to use a screen exit. For purchase order 'MM06E005' will be useful. Explore it in XN SMOD.
Regards
PRAFUL

BDC using call transaction

Hi ,
This is vijay...
can anyone help me plz
Hi,
Iam uploading data using call transaction.Tcode is ff67.In this TCode we have the begining balance(ssald) and ending balance(esald).The new record we are uploading will take the begining balance as the previous record ending balance, if we give the begining balance wrong then the record does not saved it will show error(the begining balance does not match with the prior ending balance).
while uploading the data using MODE A iam able to get the desired output but by using the MODE N iam not able to get the desired output i,e if there is any error in the begining balance also the record is being saved iam not getting the error message.
Iam attaching the code below..please help me
report Z_BRS_BDC no standard page heading line-size 255.
        INTERNAL TABLES DECLARATIONS
DATA : BEGIN OF bdcdata OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA : END OF bdcdata.
DATA: LV_OUT TYPE STRING.
DATA : iopt LIKE ctu_params.
DATA : wa_rec_err   TYPE i.
DATA : wa_rec_wri TYPE i.
DATA : wa_tot_rec TYPE i.
DATA : amt(16) type c.
DATA : BEGIN OF gu_upload OCCURS 0,
       hbkid LIKE febmka-hbkid,
       hktid LIKE febmka-hktid,
       aznum LIKE febmka-aznum,
       azdat LIKE febmka-azdat,
       ssald LIKE amt,
       esald LIKE amt,
       budtm LIKE febmka-budtm,
       mnam1 LIKE febmka-mnam1,
       jname LIKE febmka-jname,
       vgman LIKE febmka-vgman,
       valut LIKE febep-valut,
       kwbtr(13) TYPE c,
       chect_kf LIKE febmkk-chect_kf,
      END OF gu_upload.
DATA:GU_DOWNLOAD LIKE GU_UPLOAD OCCURS 0 WITH HEADER LINE.
kishi*********************************
DATA: BEGIN OF itab OCCURS 0,
     vgman LIKE febmka-vgman,
     valut LIKE febep-valut,
     kwbtr(13) TYPE c,
     chect_kf LIKE febmkk-chect_kf,
     END OF itab.
kishi)(_()00-8-09
DATA: BEGIN OF messtab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
DATA: BEGIN OF messtab1 OCCURS 0.
        INCLUDE STRUCTURE messtab.
DATA: END OF messtab1.
DATA : BEGIN OF int_count OCCURS 0.
        INCLUDE STRUCTURE alsmex_tabline.
DATA : END OF int_count.
DATA: c_tcode      LIKE sy-tcode              VALUE 'FF67',
      c_upd        LIKE ctu_params-updmode    VALUE 'S',
      c_def_size   LIKE ctu_params-defsize    VALUE 'X'.
*VALUES FOR STARTING COLUMNS AND ROWS IN THE EXCEL SHEET
DATA : c_begcol     TYPE i                     VALUE '1',
      c_begrow     TYPE i                     VALUE '1',
*DATA IS ENDED AT THE 13TH COLUMN IN THE EXCELSHEET
      c_endcol     TYPE i                     VALUE '13',
*LAST ROW IN THE EXCEL SHEET
      c_endrow     TYPE i                     VALUE '65536',
      c_path(3)    TYPE c                     VALUE 'C:\'.
*Field Symbols
FIELD-SYMBOLS: <fs>.
     SELECTION SCREEN PARAMETERS
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
PARAMETERS : p_file LIKE rlgrap-filename DEFAULT
'C:\ ',
*This is the path for downloading file
P_FNAME2 LIKE RLGRAP-FILENAME ,
c_mode LIKE ctu_params-dismode DEFAULT 'N'.
SELECTION-SCREEN END OF BLOCK b1.
AT SELECTION-SCREEN.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*F4 HELP FOR FILE SELECTION
PERFORM validate_input_file.
START-OF-SELECTION.
CLEAR gu_upload.
REFRESH gu_upload.
     UPLOAD THE DATA FROM FLAT FILE TO INTERNAL TABLE
PERFORM file_upload.
iopt-dismode = c_mode.
iopt-updmode = c_upd.
iopt-defsize = c_def_size.
     POPULATE THE DATA THROUGHSCREENS
PERFORM bdc_upload.
END-OF-SELECTION.
*DISPLY THE ERROR RECORDS
PERFORM DISPLAY-DATA.
      FORM file_upload                                              *
FORM file_upload.
CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
       EXPORTING
            filename                = p_file
            i_begin_col             = c_begcol
            i_begin_row             = c_begrow
            i_end_col               = c_endcol
            i_end_row               = c_endrow
       TABLES
            intern                  = int_count
       EXCEPTIONS
            inconsistent_parameters = 1
            upload_ole              = 2
            OTHERS                  = 3.
LOOP AT int_count.
    ASSIGN COMPONENT int_count-col OF STRUCTURE gu_upload TO <fs>.
    IF sy-subrc NE 0.
      EXIT.
    ENDIF.
    <fs> = int_count-value.
    AT END OF row.
      APPEND gu_upload.
      CLEAR gu_upload.
    ENDAT.
ENDLOOP.
*kishhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh
LOOP AT gu_upload.
    itab-vgman = gu_upload-vgman.
    itab-valut = gu_upload-valut.
    itab-kwbtr = gu_upload-kwbtr.
    itab-chect_kf = gu_upload-chect_kf.
    APPEND itab.
ENDLOOP.
*kishiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiiii
ENDFORM.                    "file_upload
*&      Form BDC_UPLOAD
FORM bdc_upload.
LOOP AT gu_upload.
    CLEAR bdcdata.
    REFRESH bdcdata.
*&      POPULATE THE DATA FOR FIRST SCREEN
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-JNAME'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'FEBMKA-BUKRS'
                              'IN14'.
perform bdc_field       using 'FEBMKA-HBKID'
                              gu_upload-hbkid.
perform bdc_field       using 'FEBMKA-HKTID'
                              gu_upload-hktid.
perform bdc_field       using 'FEBMKA-AZNUM'
                              gu_upload-aznum.
perform bdc_field       using 'FEBMKA-AZDAT'
                              gu_upload-azdat.
perform bdc_field       using 'FEBMKA-SSALD'
                              gu_upload-ssald.
perform bdc_field       using 'FEBMKA-ESALD'
                              gu_upload-esald.
perform bdc_field       using 'FEBMKA-BUDTM'
                              gu_upload-budtm.
perform bdc_field       using 'FEBMKA-MNAM1'
                              gu_upload-mnam1.
perform bdc_field       using 'FEBMKA-JNAME'
                              gu_upload-jname.
*&      POPULATE THE DATA FOR SECOND SCREEN
    DATA : fnam(20) TYPE c,
          idx      TYPE c.
    MOVE 1 TO idx.
    LOOP AT itab.
      PERFORM bdc_dynpro      USING 'SAPMF40K' '8000'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'FEBMKK-CHECT_KF(03)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      CONCATENATE 'FEBMKA-VGMAN(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam
                                    itab-vgman.
      CONCATENATE 'FEBEP-VALUT(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam itab-valut.
      CONCATENATE 'FEBMKA-KWBTR(' idx ')' INTO fnam.
      PERFORM bdc_field       USING fnam itab-kwbtr.
      CONCATENATE 'FEBMKK-CHECT_KF(' idx ')' INTO fnam.
      PERFORM bdc_field USING fnam itab-chect_kf.
      idx = idx + 1.
    ENDLOOP.
*perform bdc_dynpro      using 'SAPMF40K' '8000'.
*perform bdc_field       using 'BDC_CURSOR'
                             'FEBMKK-CHECT_KF(01)'.
*perform bdc_field       using 'BDC_OKCODE'
                             '/00'.
*perform bdc_field       using 'FEBMKA-VGMAN(01)'
                             'z001'.
*perform bdc_field       using 'FEBEP-VALUT(01)'
                             '2007/04/26'.
*perform bdc_field       using 'FEBMKA-KWBTR(01)'
                             '          5000-'.
*perform bdc_field       using 'FEBMKK-CHECT_KF(01)'
                             '1122'.
perform bdc_dynpro      using 'SAPMF40K' '8000'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKK-CHECT_KF(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SICH'.
*&      POPULATE THE DATA FOR FOURTH SCREEN
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-BUKRS'.
perform bdc_field       using 'BDC_OKCODE'
                              '=BUCH'.
perform bdc_field       using 'FEBMKA-BUKRS'
                              'IN14'.
perform bdc_field       using 'FEBMKA-HBKID'
                              gu_upload-hbkid.
perform bdc_field       using 'FEBMKA-HKTID'
                              gu_upload-hktid.
perform bdc_field       using 'FEBMKA-AZNUM'
                              gu_upload-aznum.
perform bdc_field       using 'FEBMKA-AZDAT'
                              gu_upload-azdat.
perform bdc_field       using 'FEBMKA-SSALD'
                              gu_upload-ssald.
perform bdc_field       using 'FEBMKA-ESALD'
                              gu_upload-esald.
perform bdc_field       using 'FEBMKA-BUDTM'
                              gu_upload-budtm.
perform bdc_field       using 'FEBMKA-MNAM1'
                              gu_upload-mnam1.
perform bdc_field       using 'FEBMKA-JNAME'
                              gu_upload-jname.
*perform bdc_dynpro      using 'SAPMF40K' '0101'.
*perform bdc_field       using 'BDC_OKCODE'
                             '/EENDE'.
*perform bdc_field       using 'BDC_CURSOR'
                             'FEBMKA-BUKRS'.
perform bdc_dynpro      using 'SAPMF40K' '0101'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EABBR'.
perform bdc_field       using 'BDC_CURSOR'
                              'FEBMKA-BUKRS'.
*&      USING THE CALL TRANSACTION
    PERFORM call_transaction.
   CLEAR BDCDATA.                      "<--- Add here
   REFRESH BDCDATA.                 "<--- Add here
ENDLOOP.
ENDFORM.                    " BDC_UPLOAD
*&      Form VALIDATE_INPUT_FILE
FORM validate_input_file.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_path         = ' c:\ '
            mask             = ',.txt,.*.'
            mode             = 'O'
            title            = 'Upload '
       IMPORTING
            filename         = p_file
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
IF sy-subrc <> 0.
IF sy-subrc <> 0 AND sy-subrc <> 3.
   MESSAGE e100(zm) WITH text-007.
ENDIF.
ENDFORM.                    " VALIDATE_INPUT_FILE
       Start new screen                                              *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "bdc_dynpro
       Insert field                                                  *
FORM bdc_field USING fnam fval.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
ENDFORM.                    "bdc_field
*&      Form CALL_TRANSACTION
FORM call_transaction.
DATA: l_index LIKE sy-tabix.
CALL TRANSACTION c_tcode USING bdcdata
                            MODE c_mode
                            MESSAGES INTO messtab.
*POPULATE THE ERROR RECORDS INTO INTERNAL TABLE
IF SY-SUBRC NE 0.
    GU_DOWNLOAD-HBKID = GU_UPLOAD-HBKID.
   GU_DOWNLOAD-HBKID = GU_UPLOAD-HBKID.
    GU_DOWNLOAD-HKTID = GU_UPLOAD-HKTID.
    GU_DOWNLOAD-AZNUM = GU_UPLOAD-AZNUM.
    GU_DOWNLOAD-AZDAT = GU_UPLOAD-AZDAT.
    GU_DOWNLOAD-ESALD = GU_UPLOAD-ESALD.
    GU_DOWNLOAD-SSALD = GU_UPLOAD-SSALD.
    GU_DOWNLOAD-BUDTM = GU_UPLOAD-BUDTM.
    GU_DOWNLOAD-MNAM1 = GU_UPLOAD-MNAM1.
    GU_DOWNLOAD-JNAME = GU_UPLOAD-JNAME.
    GU_DOWNLOAD-VGMAN = GU_UPLOAD-VGMAN.
    GU_DOWNLOAD-VALUT = GU_UPLOAD-VALUT.
    GU_DOWNLOAD-KWBTR = GU_UPLOAD-KWBTR.
    GU_DOWNLOAD-CHECT_KF = GU_UPLOAD-CHECT_KF.
    APPEND GU_DOWNLOAD.
*DISPLAY THE PROGRESS OF PROCESS
CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'
EXPORTING
   PERCENTAGE       = 0
   TEXT             = 'Downloading is in process'.
*DOWNLOADING THE ERROR RECORD
    LV_OUT = P_FNAME2.
    CALL FUNCTION 'GUI_DOWNLOAD'
      EXPORTING
        FILENAME               = LV_OUT
        WRITE_FIELD_SEPARATOR =      'X'
      TABLES
        DATA_TAB                = GU_DOWNLOAD.
ENDIF.
IF NOT messtab[] IS INITIAL.
    PERFORM format_message.
ENDIF.
ENDFORM.                    " CALL_TRANSACTION
*&      Form DISPLAY-DATA
FORM display-data.
SKIP.
WRITE: 'SY-SUBRC' , sy-subrc.
ENDFORM.                    " DISPLAY-DATA
      FORM FORMAT_MESSAGE                                           *
FORM format_message.
DATA: l_msg(100),
   l_index LIKE sy-tabix.
LOOP AT messtab.
    READ TABLE gu_upload INDEX l_index.
    CALL FUNCTION 'FORMAT_MESSAGE'
         EXPORTING
              id        = messtab-msgid
              lang      = sy-langu
              no        = messtab-msgnr
              v1        = messtab-msgv1
              v2        = messtab-msgv2
              v3        = messtab-msgv3
              v4        = messtab-msgv4
         IMPORTING
              msg       = l_msg
         EXCEPTIONS
              not_found = 1
              OTHERS    = 2.
    IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
   WRITE:/ l_msg.
ENDLOOP.
WRITE:/ l_msg.
ENDFORM.
Message was edited by:
        vijayd duvvada

Hi,
First , keep the mode "E" and check the debugger , you can exactly see where the error is and let me know, what error and where it is stoping.
By your coding, i suppose to think that, its proble in the amount (currency). When ever you are try to pass the value, and value is not there in upload file or data is mismatch, the call transaction will fail in mode 'A' and succesful in mode 'N'.
In that situation use this before the currecny field.
IF NOT FEBMKA-SSALD IS INTIAL.
   perform bdc_field using 'FEBMKA-ESALD'
                                  gu_upload-esald.
ENDIF.
tHANKS
Manju

CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .

Hi all,
i hope there is someone that can help me.
My problem is: in an ABAP custom report in a FORM user-command my code is
CASE ls_selfield-sel_tab_field.
    WHEN 'ITAB-BELNR'.
      IF NOT ls_selfield-value IS INITIAL.
        SET PARAMETER ID 'RBN' FIELD ls_selfield-value.
        CALL TRANSACTION 'MIR6' AND SKIP FIRST SCREEN .
ENDCASE.
When i click on output field of my report, not skip first screen but only call MIR6!!!
How can i solve this problem?
Regards.

Hi,
First of all Please don't use all Caps for Subject Line
Test Following Sample Code it will solve out your problem,
DATA: it_bdcdata TYPE TABLE OF bdcdata,
      wa_it_bdcdata LIKE LINE OF it_bdcdata,
      belnr(10).
belnr = '100'. " Give Document Number here
DATA opt TYPE ctu_params.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-program = 'SAPMM08N'.
wa_it_bdcdata-dynpro   = '100'.
wa_it_bdcdata-dynbegin = 'X'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_CURSOR'.
wa_it_bdcdata-fval = 'SO_BELNR-LOW'.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'SO_BELNR-LOW'.
wa_it_bdcdata-fval = BELNR.
APPEND wa_it_bdcdata TO it_bdcdata.
CLEAR wa_it_bdcdata.
wa_it_bdcdata-fnam = 'BDC_OKCODE'.
wa_it_bdcdata-fval = '=CRET'.
APPEND wa_it_bdcdata TO it_bdcdata.
opt-dismode = 'E'.
CALL TRANSACTION 'MIR6' USING it_bdcdata OPTIONS FROM opt.
Please Reply if any Issue,
Best Regards,
Faisal

HR ABAP: Issue with using 'nocommit' parameter on FM HR_INFOTYPE_OPERATION

Issue with using nocommit parameter on FM HR_INFOTYPE_OPERATION:
My client has a requirement to create the following 4 infotypes in sequence in a LUW, i.e either all are created or none is created.
9045 (custom infotype)
0045
0078
0015
I tried to use the nocommit parameter on FM HR_INFOTYPE_OPERATION to insert the 4 infotypes
in a nocoomit mode and then at the end I have issued
'Commit Work', but to my surprise only I/T 0015 is created in the database and the first three (9045, 0045 and 0078) did not make it to database.
I searched many threads on SDN but could not find a solution.
Please let me know if there could be any solution to implement the LUW.
YOur inputs will be appreciated.

Hi ,
i think u can also try with this FM HR_MAINTAIN_MASTERDATA , see its documentations.
no commit works like a simulation mode , what u can do is ,
call FM for all Infotypes and collect all error msgs if any , then finally call FM for all infotypes again without passing nocommit work ( i.e space).
regards
prabhu

Problems with a call transaction

Hi, I'm having some problems with a call transaction and I cannot understand why. I put A in the mode, and I am seeing the dynpros and I am pressing enter it works perfectly but when I use mode N it tells me that there is not information for one of the dynpros and it doesn't work. Does anybody know the problem and how to solve it??
Thanks in advance

Hi,
First of all thank you very much for your time.
I am using FB05 and the problem is in dynpro SAPLKACB 0002, and it says that batch input data doesn't exist. Here is the code, maybe you can see what is happening
LOOP AT t_resumen WHERE belnr = t_batch-belnr AND
                            ( contador = 3 OR contador = 4 or CONTADOR = 5 ).
      READ TABLE t_clave WITH KEY belnr = t_resumen-belnr.
      d_clave = t_clave-bschl.
      i = i + 1.
      CASE i.
        WHEN 1.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0700'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          PERFORM bdc_field   USING 'RF05A-NEWBS' t_resumen-bschl.
          PERFORM bdc_field   USING 'RF05A-NEWKO' t_resumen-hkont.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0300'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          j_wrbtr = t_resumen-wrbtr.
          REPLACE '.' WITH ',' INTO j_wrbtr.
          PERFORM bdc_field   USING 'BSEG-WRBTR' j_wrbtr.
          PERFORM bdc_dynpro USING 'SAPLKACB'    '0002'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
        WHEN t.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0300'.
          PERFORM bdc_field   USING 'RF05A-NEWBS' t_resumen-bschl.
          PERFORM bdc_field   USING 'RF05A-NEWKO' t_resumen-hkont.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          j_hkont = t_resumen-hkont.
          j_clave = t_resumen-bschl.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0300'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '=BU'.
          j_wrbtr = t_resumen-wrbtr.
          REPLACE '.' WITH ',' INTO j_wrbtr.
          PERFORM bdc_field   USING 'BSEG-WRBTR' j_wrbtr.
          PERFORM bdc_dynpro USING 'SAPLKACB'    '0002'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
        WHEN OTHERS.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0300'.
          PERFORM bdc_field   USING 'RF05A-NEWBS' t_resumen-bschl.
          PERFORM bdc_field   USING 'RF05A-NEWKO' t_resumen-hkont.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          j_hkont = t_resumen-hkont.
          j_clave = t_resumen-bschl.
          PERFORM bdc_dynpro USING 'SAPMF05A'    '0300'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
          j_wrbtr = t_resumen-wrbtr.
          REPLACE '.' WITH ',' INTO j_wrbtr.
          PERFORM bdc_field   USING 'BSEG-WRBTR' j_wrbtr.
          PERFORM bdc_dynpro USING 'SAPLKACB'    '0002'.
          PERFORM bdc_field   USING 'BDC_OKCODE' '/00'.
      ENDCASE.
        READ TABLE t_porcentajes WITH KEY gjahr = t_resumen-zzbad
                                       zzbtd = t_resumen-zzbtd.
        IF j_hkont = t_porcentajes-cfacpr.
          PERFORM bdc_field   USING 'COBL-PRCTR' t_porcentajes-prctrfac.
          PERFORM bdc_field   USING 'COBL-ZZBTD' t_resumen-zzbtd.
          PERFORM bdc_field   USING 'COBL-ZZBAD' t_resumen-zzbad.
        ELSEIF t_resumen-hkont = t_porcentajes-cadmin.
         PERFORM bdc_field   USING 'COBL-KOSTL' '20801'.
        ELSEIF t_resumen-hkont = t_porcentajes-creca.
         PERFORM bdc_field   USING 'COBL-KOSTL' '20401'.
        ELSE.
          IF d_clave = 01 OR d_clave = 04 OR d_clave = 40 OR d_clave = 09.
            IF j_hkont >= 424001 AND j_hkont <= 424005.
              PERFORM bdc_field   USING 'COBL-PRCTR' 'DUMMY'.
            ELSEIF j_hkont >= 424601 AND j_hkont <= 424605.
              IF j_clave = 40.
                PERFORM bdc_field   USING 'COBL-PRCTR' 'DUMMY'.
              ENDIF.
            ENDIF.
          ELSEIF d_clave = 11 OR d_clave = 12 OR d_clave = 14 OR d_clave = 50.
            IF j_hkont >= 424001 AND j_hkont <= 424005.
              PERFORM bdc_field   USING 'COBL-PRCTR' 'DUMMY'.
            ELSEIF j_hkont >= 424601 AND j_hkont <= 424605.
              IF j_clave = 50.
                PERFORM bdc_field   USING 'COBL-PRCTR' 'DUMMY'.
              ENDIF.
            ENDIF.
          ENDIF.
*Fin modificacion marzo 2007.----
          PERFORM bdc_field   USING 'COBL-ZZBTD' t_resumen-zzbtd.
          PERFORM bdc_field   USING 'COBL-ZZBAD' t_resumen-zzbad.
          PERFORM bdc_field   USING 'COBL-ZZBTT' t_resumen-zzbtt.
          PERFORM bdc_field   USING 'COBL-ZZBTU' t_resumen-zzbtu.
          PERFORM bdc_field   USING 'COBL-ZZBTS' t_resumen-zzbts.
          PERFORM bdc_field   USING 'COBL-ZZBAG' t_resumen-zzbag.
          PERFORM bdc_field   USING 'COBL-ZZBRE' t_resumen-zzbre.
          PERFORM bdc_field   USING 'COBL-ZZBC8' t_resumen-zzbc8.
          PERFORM bdc_field   USING 'COBL-ZZBC9' t_resumen-zzbc9.
        ENDIF.
    ENDLOOP.

Issue with using GET n SET Parameter in module pool programming.

Hello Friends,
                     I am using SET n GET Parameter to access input values from a screen. But when I use it, the values are not transfered back n forth. Getting initial values.
Your expertise would be appreciated.
Cheers,
Senthil

Hi,
check this
Filling an Initial Screen using SPA/GPA Parameters
To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.
ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.
To fill one, use:
SET PARAMETER ID <pid> FIELD <f>.
This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID <pid> FIELD <f>.
This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.
To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.
The relevant fields must each be linked to an SPA/GPA parameter.
On a selection screen, you link fields to parameters using the MEMORY ID addition in the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID when you declare a parameter or selection option, the corresponding input field is linked to that input field.
On a screen, you link fields to parameters in the Screen Painter. When you define the field attributes of an input field, you can enter the name of an SPA/GPA parameter in the Parameter ID field in the screen attributes. The SET parameter and GET parameter checkboxes allow you to specify whether the field should be filled from the corresponding SPA/GPA parameter in the PBO event, and whether the SPA/GPA parameter should be filled with the value from the screen in the PAI event.
When an input field is linked to an SPA/GPA parameter, it is initialized with the current value of the parameter each time the screen is displayed. This is the reason why fields on screens in the R/3 System often already contain values when you call them more than once.
When you call programs, you can use SPA/GPA parameters with no additional programming overhead if, for example, you need to fill obligatory fields on the initial screen of the called program. The system simply transfers the values from the parameters into the input fields of the called program.
However, you can control the contents of the parameters from your program by using the SET PARAMETER statement before the actual program call. This technique is particularly useful if you want to skip the initial screen of the called program and that screen contains obligatory fields.
If you want to set SPA/GPA parameters before a program call, you need to know which parameters are linked to which fields on the initial screen. A simple way of doing this is to start the program that you want to call, place the cursor on the input fields, and choose F1 followed by Technical info. The Parameter ID field contains the name of the corresponding SPA/GPA parameter. Alternatively, you can look at the screen definition in the Screen Painter.
The technical information for the first input field of the booking transaction TCG2 looks like this:
The SPA/GPA parameter for the input field Company has the ID CAR. Use this method to find the IDs CON, DAY, and BOK for the other input fields.
The following executable program is connected to the logical database F1S and calls an update transaction:
REPORT BOOKINGS NO STANDARD PAGE HEADING.
TABLES SBOOK.
START-OF-SELECTION.
WRITE: 'Select a booking',
SKIP.
GET SBOOK.
WRITE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
HIDE: SBOOK-CARRID, SBOOK-CONNID,
         SBOOK-FLDATE, SBOOK-BOOKID.
AT LINE-SELECTION.
SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,
                    'CON' FIELD SBOOK-CONNID,
                    'DAY' FIELD SBOOK-FLDATE,
                    'BOK' FIELD SBOOK-BOOKID.
CALL TRANSACTION 'BOOK'.
The basic list of the program shows fields from the database table SBOOK according to the user entries on the selection screen. These data are also stored in the HIDE areas of each line.
If the user selects a line of booking data by double-clicking, the system triggers the AT LINE-SELECTION event and takes the data stored in the HIDE area to fill them into the SPA/GPA parameters of the initial screen of the transaction. Then it calls the transaction. Since you do not suppress the initial screen using AND SKIP FIRST SCREEN, the initial screen may appear as follows:
If you would use the AND SKIP FIRST SCREEN option with the CALL TRANSACTION statement, the second screen would appear immediately, since all obligatory fields of the first screen are filled.
Regards
Edited by: K.P.N on Jan 9, 2008 5:21 AM

How to use call transaction stmt from webdynpro application

Hi Expers,
Can I use call transaction 'tcode' in my webdynpro application, I have tried in my application but i am getting short dump saying
Error analysis+
An exception occurred that is explained in detail below.The exception, which is assigned to class'CX_SY_SEND_DYNPRO_NO_RECEIVER', was not caught and therefore caused a runtime error. The reason for the exception is: During background processing, the system attempted to send a screen to a user. Current screen: "SAPLMGMM " 0060.
I haven't used any more statements in my application am sure from my application side everything perfect. but I have seen a screen shot
with SAP screen in webbrowser.
Please help me out if you are not clear abt my doubt please ask me for clear idea.
Thanks in advance
Phalani M

Hello,
Since you can't use the call transaction command in web dynpros components, I suggest you to create a report and fill a BDC table on this and use the call transaction in this report.
So, in your web dynpro component you can use a command SUBMIT to create a job in background.
DATA: number           TYPE tbtcjob-jobcount,
      name             TYPE tbtcjob-jobname VALUE 'JOB_TEST',
      print_parameters TYPE pri_params.
CALL FUNCTION 'JOB_OPEN'
EXPORTING
    jobname          = name
IMPORTING
    jobcount         = number
EXCEPTIONS
    cant_create_job = 1
    invalid_job_data = 2
    jobname_missing = 3
    OTHERS           = 4.
IF sy-subrc = 0.
SUBMIT submitable TO SAP-SPOOL
                    SPOOL PARAMETERS print_parameters
                    WITHOUT SPOOL DYNPRO
                    VIA JOB name NUMBER number
                    AND RETURN.
IF sy-subrc = 0.
    CALL FUNCTION 'JOB_CLOSE'
      EXPORTING
        jobcount             = number
        jobname              = name
        strtimmed            = 'X'
      EXCEPTIONS
        cant_start_immediate = 1
        invalid_startdate    = 2
        jobname_missing      = 3
        job_close_failed     = 4
        job_nosteps          = 5
        job_notex            = 6
        lock_failed          = 7
        OTHERS               = 8.
    IF sy-subrc <> 0.
    ENDIF.
ENDIF.
ENDIF.
Regards.

Issue with using call transaction CJ9F and F.M BAPI_PROJECT_MAINTAIN

Similar Messages

Maybe you are looking for