How to suppress a warning message in BDC call transaction

Hi,
I was calling a BDC using CALL Transaction in mode N. But due to some warning messages the background job was not success. Please tell me how to overcome the warning messages in BDC.
Regards,
Satish

Hi tyr this way:
PERFORM bdc_dynpro      USING 'SAPMM07M' '0210'. " into the screen
      PERFORM bdc_field       USING 'BDC_CURSOR'           "cursor on the filed to update
                                    'DM07M-HSDAT_INPUT'.
      PERFORM bdc_field       USING 'DM07M-HSDAT_INPUT'   "assign values
                                     v_date.                                     "might get an warning so three enters...
      PERFORM bdc_field       USING 'BDC_OKCODE' " first enter
                                   '/00'.
      PERFORM bdc_field       USING 'BDC_OKCODE' "second enter
                                    '/00'.
      PERFORM bdc_field       USING 'BDC_OKCODE' "third enter
                                    '/00'.

Similar Messages

How to do the job scheduling in BDC Call transaction

Hi Experts,
I've a Query like how to do the job scheduling in BDC Call transaction
If anybody knows the answer please send me the reply.
Thanks.
Regards,
Rekha

Hi ,
any progarm can be scheduled, wether it may be BDC or report thru SM36 Tcode.
But do rememeber that if ur BDC is using GUI_UPLOAD function module, then it wont work , coz the function Gui_upload or GUI_DOWNLOAd wont work in back ground.
If u r going to use OPEN_DATASET , READ dataset ....then it can be scheduled. i.e BDC can work if ur program retrievesz the data from Application server.
Rvert back if any issues,
Reward with poinst if helpful.
Regards,
Naveen

How to Suppress a warning message in Reports

Hi All,
I am getting REP-32751: Warning: Some text segments are missing warning message when ever i open a report and also while run the report in the browser. I am not able to find the missing text segments. Is there any way to suppress this warning message in oracle reports 10g?. Please let me know.
Regards,
Prasad.

Just was curious and was in Metalink anyways and looked up your Error:
>
Another workaround: open the report under the desired NLS_LANG, and OK all the warning messages. Once the report is opened, save it (under a different name). This will fill out missing text segments with blanks,which is OK because these strings never appear in the report anyway (theyshould have been deleted...)

How to supress a warning message in BDC for ME11 Tcode

Hi Expert,
I am doing a BDC report for ME11 Tcode and some of warning is ignorable for this transaction code,how can we suppress these warning through BDC program, is it possible or will have to make some changes changes in TCODE(ME11) itself.

hi,
if the warning message coming in a pop-up window then it can be supressed in the following way.
1. comment the lines of the code of bdc recording of that pop-up screen along with the perform of bdc ok code '=ENTE".
2. use the structure ctu_params and fill the correspondings fiels, particularly the field nobinpt = 'X' and then use this structure in the call transcation statement as
call transcation 'ME11'
using bdcdata
options from opt ( structure of ctu_params )
3. At the time of recording use the option of check box " no batch input session ".
regards,
Alok

How to suppress the Warning messages while doing GR(MIGO)

Hi ALL,
I have a requirement while posting goods GR/GI using T-code MIGO.
Trying to do GR against PO using MIGO.After selecting the line item quantity and entering BATCH Number for line item Material when I click on 'CHECK' Pushbutton i am Getting the below Warning msg
'For batch RAB001 of material 1522582, no class could be determined'. Message no M7207.
How to suppress this above warning message, I want to Post the goods by suppressing the above warning message .
Like similarly while issuing the goods to the to the Production order using MIGO i am getting warning message when I click on 'CHECK' Pushbutton.
I do want to issue the goods by suppressing warning message in this case also.
I know this could be solved by customization but we are dealing with batch managed materials.
How to suppress the the above warning messages in MIGO through ABAP coding ...
Looking forward the helpfull answer.
Regards,
venky

Hi
Answer is pure assumption.
Pls check the following OSS notes
Note 319094 - Warning message during batch classification in IM
Note 122937 - UD: Error message M7207 when you save
Note 399416 - Message M7207 not analyzed in background
Note 786755 - You cannot suppress message M7 207
Note 201196 - MIGO: Error M7207 for goods receipt for batch
Pls take opinion from SAP / Basis before implementing the OSS note
Regards
Madhan D

How to remove browser warning message in HTML 5 Cap 8 projects?

How to remove browser warning message in HTML 5 Cap 8 projects?

My conclusion after a morning struggling with this, is that there's no point in suppressing the message if your html5 content then goes on to misbehave in Firefox (like mine does). I've chosen to keep the popup, but change the wording to refer Firefox users to a completely separate Flash version. The wording of the popup is also in CPM.js.
Before you all shout at me, no I can't use the multiscreen.html approach, because my Flash version will have to be non-rescaleable, because web objects don't rescale in Flash.

Suppressing a warning message in reports 10g

Hi All,
I am getting REP-32751: Warning: Some text segments are missing warning message when ever i open a report and also while run the report in the browser. I am not able to find the missing text segments. Is there any way to suppress this warning message in oracle reports 10g?. Please let me know.
Regards,
Prasad.

probably best to post this in the reports forum

How to Convert the Warning Message to Error Message in Standard Transaction

Hi,
I face one problem in Standard Transaction Code CS02. In that by entering the material Number, Plant, bomstatus press enter. it gives a warning message. How to convert the Warning message to Error. In abap how to do that. Please help me.

Mohan,
It appears that there is some configuration you can do for BOM Message types to change the message type. The IMG link for this function is:
Production->Basic Data->Bill of Material->General Data->Change Message Type
However you need to read the IMG documentation to see if this will work for you. There are only certain messages that can be changed with this configuration step.
Also, please do not double post questions in the forums.
Best Regards,
Chris H.

How can I disappear warning message~?

I'm using R12.
And I don't want to see warning message.
like that
!Warning
The search could not be completed because data is not staged or this match rule is not compiled: HZ_ORG_SIMPLE_SEARCH_RULE. Plese contact your sys admin...
I inserted data using by API.
And I'm staging by concurrunt manager per 1 min...
When I inserted some data using by API, that message is occured.
but it would be disappeared later in 1 minute.
How can I disappear warning message~?
I think there is a something what I can setting . somewhere....but I don't know where it is...
like warning, error, critical....
plz let me know~

You will need to set appropriate profile options - pl see MOS Doc 565905.1 (FAQ on the setup/usage of DQM Profile Options for OCO and Receivables)
HTH
Srini

How to clear the Warning Messages

Hi Friends,
How to clear the warning messages, The requirement is I am preparing some warning messages in page1 , and based on some button user will be navigated to page2. In page2 If user clicks on Save button I am displaying the warning messages which are preared in first page(Code snippet shown below) when user trying to navigate to first page .
addWarningMessage("",new Object[]{});
Thanks in Advance

Hi Frank,
Yes you are right, The warning message is being displayed on Page2 when user clicked on 'Save' button on Page2. The Code snippet is being executed in ServiceImpl class when user clicks on the Save button.
Basically, I am validating the Page1 data and Page2 data on Page2 when User clicks on the Save button on page2.
Thank you !!

BDC Call Transaction - Doc.No not getting generated in Message Internal tab

Dear All,
I am using BDC Call Transaction method for uploading data for transaction, Iam able to successfully capture the Error messages, sucess messages and the transaction number is also displayed for the bdc run in Mode A, but in case of scheduling the job in background, the Error messages are displayed but the transaction number is not captured in the message Internal table( BDCMSGCOLL).
Kindly look into the matter and revert back for any further info.
Regards
Naresh

Hi,
Please try using the following kind of code in 'CALL TRANSACTION'
    opt-dismode = 'E'.     " Exclusive mode
    opt-defsize = 'X'.
    opt-updmode = 'S'.
    opt-nobinpt = ' '.
    CALL TRANSACTION transaction_code USING ft OPTIONS FROM opt
                                                                         MESSAGES INTO t_bdcmsgcoll .
Hope this will work.
Thanks,
Leo

How to set the BDC Call transaction Program in Background

Hi All,
        I have a requirement. If i execute a BDC Call Transaction Program in Background it is showing 0 seconds means it is not executing. Normally it is working properly. If execute in background it is not executing. But my client wnats to execute in background. How can i overcome this could you please suggest me?
Thanks in Advance

hi
To schedule the processing of session in backgroud you can use report RSBDCSUB.
You can do in two ways -
Ist Method
Define a batch job in SM36 with two steps -
First Step - Your Custom Program ( with a variant )
Second Step - RSBDCSUB ( With a variant having
the session name ).
2nd Method
In your program after BDC_CLOSE_GROUP add a line.
SUBMIT RSBDCSUB WITH MAPPE EQ <SESSION_NAME>.
Scedule you program as a batch job in SM36 ( Single Step ). ( You can also test the program by running in online mode . After your programs executes , go and see in SM35. You will see that your session created in being processed or has been processed in background).
In Both ways the session created by BDC_OPEN_GROUP will be processed in background
You would have to create a job on the fly to do this. This example shows how to kick off a background job via an ABAP program.
report zrich_0004 .
data:   sdate type sy-datum,
        stime type sy-uzeit,
        l_valid,
        ls_params like pri_params,
        l_jobcount like tbtcjob-jobcount,
        l_jobname like tbtcjob-jobname.
start-of-selection.
Get Print Parameters
call function 'GET_PRINT_PARAMETERS'
       exporting
            no_dialog      = 'X'
       importing
            valid          = l_valid
            out_parameters = ls_params.
Open Job
l_jobname = 'ZRICH_0005'.
call function 'JOB_OPEN'
       exporting
            jobname = l_jobname
       importing
            jobcount = l_jobcount.
Submit report to job
submit zrich_0005
       via job     l_jobname
           number l_jobcount
       to sap-spool without spool dynpro
           spool parameters ls_params
              and return.
Schedule and close job.
call function 'JOB_CLOSE'
       exporting
            jobcount = l_jobcount
            jobname   = l_jobname
            strtimmed = 'X.
regards
Satish

Plz tell me BDC CALL TRANSACTION steps with simple example

hi,
plz tell me the steps
BDC CALL TRANSACTION steps with simple example

Hi,
BATCH DATA COMMUNICATION
About Data Transfer In R/3 System
When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
In the process of replacing current applications and transferring application data, two situations might occur:
? The first is when application data to be replaced is transferred at once, and only once.
? The second situation is to transfer data periodically from external systems to SAP and vice versa.
? There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called ?batch input? or ?batch data communication?.
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a ?data transfer? program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
? To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
? To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
? The transaction code, if you do not already know it.
? Which fields require input i.e., mandatory.
? Which fields can you allow to default to standard values.
? The names, types, and lengths of the fields that are used by a transaction.
? Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
? Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System ? Status.)
? Step through the transaction, entering the data will be required for processing your batch input data.
? On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
? Display these by choosing System ? Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
? For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which you?ll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
? Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
? Create a BDCDATA structure
? Write the structure out to a session or process it with CALL TRANSACTION USING; and then
? Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
? Data that is entered into screen fields.
? Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
? PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
? DYNPRO: Screen Number. Set this field only in the first record for the screen.
? DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ? ? (blank) for all other records.)
? FNAM: Field Name. The FNAM field is not case-sensitive.
? FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
? User Name: User name
? Group: Name of the session
? Lock Date: The date on which you want to process the session.
? Keep: This parameter is passed as ?X? when you want to retain session after
processing it or ? ? to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
? Tcode: Transaction Name
? Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter ? 1 is transaction code.
Parameter ? 2 is name of BDCTAB table.
Parameter ? 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter ? 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter ? 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
Thanks &regards,
Sravani

Error Records in BDC Call transaction

Hi.....
     I am new to BDC concept... Can any of u tell me how to collect error records in BDC Call transaction... I already collected error messages through BDCMSGCOL... but i dont know how to collect those error records... here i am using two different flat files for header and line item... and kindly tell me if there is an error in line item how to get it so with relevent header details...
thanks,

Hi,
      LOOP AT t_bdcmsgcoll INTO w_bdcmsgcoll.
        PERFORM f_format_msg USING w_bdcmsgcoll CHANGING w_return.
     ENDLOOP.
Form format_msg
DATA : l_mstring(480).
CALL FUNCTION 'FORMAT_MESSAGE'
    EXPORTING
      id        = w_bdcmsgcoll-msgid
      lang      = w_bdcmsgcoll-msgspra
      no        = w_bdcmsgcoll-msgnr
      v1        = w_bdcmsgcoll-msgv1
      v2        = w_bdcmsgcoll-msgv2
      v3        = w_bdcmsgcoll-msgv3
      v4        = w_bdcmsgcoll-msgv4
    IMPORTING
      msg       = l_mstring
    EXCEPTIONS
      not_found = 1
      OTHERS    = 2.
End format_msg
you can use the l_mstring to process further and pass to the bapiret2 table
Regards,
Vijaya

Holder(A008) is not maintaing in HRP1001 (BDC - Call Transaction Method)

Dear Friends,
Holder (A008) in HRP1001 is not maintained for some hiried persons through BDC - Call Transaction Method.
Except Holder update eveything is updated in the hrp1001.
When we hire a perosn through PA40, then its automatically maintaining Holder ( A008 ) in HRP1001. But for the same case through BDC program with Call Transaction method, its not maintaining Holder.
What can be reason behind not updating holder in HRP1001. How we can maintain Holder in this case.
Thanks
Rav
Edited by: Rav Jordan on Jan 10, 2012 8:03 AM

Hi Keshav,
Thanks for your response.
After running
   CALL TRANSACTION 'PA40' USING BDCDATA
                           MODE CTUMODE " 'A'
                         UPDATE 'A'
                       MESSAGES INTO MESSTAB.
if sy-subrc eq '0'.
i am selecting perner created from pa0002.
now to update holder i am using fucntion module.
     WA_HOLD-AEDTM = SY-DATUM.
      WA_HOLD-UNAME = SY-UNAME.
      WA_HOLD-OBJID = P_PLANS.
      WA_HOLD-BEGDA = DT.
      WA_HOLD-ENDDA = '99991231'.
      WA_HOLD-OTYPE = 'S'.
      WA_HOLD-PLVAR = '01'.
      WA_HOLD-RSIGN = 'A'.
      WA_HOLD-RELAT = '008'.
      WA_HOLD-SCLAS = 'P'.
      WA_HOLD-SOBID = GD_PERNR.
      CALL FUNCTION 'RH_INSERT_INFTY'
        EXPORTING
         FCODE                     = 'INSE'
         VTASK                     = 'A'
ORDER_FLG                 = 'X'
COMMIT_FLG                = 'X'
AUTHY                     = 'X'
PPPAR_IMP                 =
OLD_TABNR                 = ' '
REPID                     = ' '
FORM                      = ' '
KEEP_LUPD                 =
WORKF_ACTV                = 'X'
        TABLES
          INNNN                     = WA_HOLD
ILFCODE                   =
EXCEPTIONS
NO_AUTHORIZATION          = 1
ERROR_DURING_INSERT       = 2
REPID_FORM_INITIAL        = 3
CORR_EXIT                 = 4
BEGDA_GREATER_ENDDA       = 5
OTHERS                    = 6
      IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
endif.
This also not updating holder in the hrp1001 postion in the table.
May i know where to do change in the code so that holder can be maintained.
Thanks
Rav

How to suppress a warning message in BDC call transaction

Similar Messages

Maybe you are looking for