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

Similar Messages

IPC 5.0 API doc is not getting generated -: Note 809820

Hello friends,
I have setup development environment for IPC 5.0 on my machine.I used the information provided in PricingUserexitManualV102.pdf which is attached with SAP Note 809820. Everything looks set except for the fact that when i try to generate API documenation (*** <b>Activate the context menu (right mouse click) on
build_api_doc.xml and select Run As -> Ant Build</b> ***), then its not getting generated and i get the IOException. Please can some one guide me how to generate API docs?
Many Thanks,
Dipender Singh (Dips)

I have been able to resolve it. I just configured by path and java_home. ( it was done to setup installation of J2EE server slim edition). While doing this when i again tried to generate the docs it happened like .. as if using winzip.
Regards,
Dipender

A/C doc is not getting Generated for Excise while MIGO_GR

Hi
In import Purchase order scenario I am unable to capture part 2 for excise materials
First I have created import PO. Then I did miro where I posted BED,AED,ECS,SECss
After that I did migo and captured part 1
After that while I was Posting part 2 with ref to vendor invoice I m getting an error message as
NO CENVAT AMOUNT TO BE POSTED
NO CENVAT AMOUNT TO BE REVERSED
We are using taxinj
Can u please help me out in solving this issue?
Rahul

Hi,
In IMPORT PO, first step while creating PO, deselect the GR based IV.
and for CVD(JCV1), give the custom as vender and save.
2. Go to MIRO, selct the planned delivery cost and do the MIRO.
3. go to J1IEX, capture Excise Invoice....here give the commercial Invoice Number i.e. your MIRO document number.
4. Go to MIGO, as soon as u gave the PO number, system will ask for commercial Invoice Numer.
5. After posting Part1 in MIGO, go to J1iex now to post cenvat amount.
Regards,
Pardeep Malik

FI Doc not getting generated at the time of Asset GRN

Hi,
We have created Asset Purchase Order.
At the time of GRN, FI Doc is not getting generated.
What changes need to be required from MM side (in OBYC)
Regards,

HI PK,
whether your PO Item have Single Account Assignment or it is Multiple Account assignment.
Check Distribution in Accoun Assignment Tab at PO item level.
If it is Single account Assignment, then Accounting Document will be generated at GR where if it is Distributed then, no Accounting Document will be generated.
In your case, Probably it would be distributed. and as a result of this your PO Item is marked as 'GR non valuated'.
Check its Delivery Tab. If it is the case, then need not worry as it is std practise. system will treated it as multiple account assignment and its valuation will only be carried out Invoice Verification level.
Later on check the Material document also.
Pls Note:
If flag 'GR non-valuated' is set in the purchase order, the valuation is only executed through the invoice verification. This flag must be set if the purchase order has multiple account assignment.
A valuated goods receipt for a purchase order with account assignment generates a posting line for the consumption account 'Account-assigned purchase order' (KBS) and for the GR/IR clearing account WRX.
hope it address your issue.
Regards,
S Anand

Regarding updattion of record...in BDC call transaction and session method.

Hi all,
I am uploading 10 records in to sap . By using call transaction method . But after insertion of 5 record server suddenly shutdown. Then what happens . What we have to do
and what about the updated 5 recs as well as remaining 5 recs.
And if it happens in case of BDC-SESSION then what is the status what we have to do..
PLEZ GIVe reply soon...its urgent
regards,
anilreddy...

Hi,
If you are using call transaction , you will not get error messages for balance 5 records that not updated. you need to cross check with the transaction and rerun again.
Session method is concerned no session will be created. system shutdown happened before the close_group,
a®

Is BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE(manual) creation?

Hi Experts,
Ours is IS-Oil.
If the user do not enters/inputs OIC_MOT (Mode Of Transport) at ITEM level on the External Details popup, SAP will get it from Customar Master-KNA1 and populates on it, because its a mandatory field (OIC_MOT), but, do not throws an Error message and interupts the sales order creation process.
We have a inbound IDOC posting function module for sales order (VA01), which posts the sales oreders by using BDC (CALL TRANSACTION 'VA01') in the system. In this function module, we are not populating the OIC_MOT field contained segment by hoping SAP will populate/default it while it hits CALL TRANSACTION 'VA01' of my BDC of my FM of IB IDOC. But, SAP is not defaulting/populating and throwing error message (saying 'OIC_MOT field is a mandatory input field' data is missing) and IDOC is failing, pls. let me know Wht its so? is the BDC's CALL TRANSACTION 'VA01' is not equals to ONLINE (manual ) creation of sales order?
Thank you

Hi
Several transactions can ba a different behavior between online and bdc process, but if you simulate the trx by SM35 you should find out these gaps
I don't know OIL vertical, but the main transactions have a bapi can be used insted of BDC program (BAPI_SALESORDER_CREATEFROMDAT2, but perhaps there's a particular BAPI for OIL).
Max

Profit Center Document not getting generated when direct FI doc is posted

Dear Experts,
Profit Center Document not getting generated when direct FI doc is posted. However CO Document is generated for Line Item 1 mentioned below.
Accounting Entry
Line 1 -Debit Expense ( Cost Center) 1000
Line 2 - Credit Bank 1000
Advance Thanks
Sanjai

Hi,
Pls check profit center configuration.... Some config might have missed.....
Use the t.code 1KE1 For analysing the profit center configuration.
Regards,
RAM
Edited by: Ram000 on Oct 7, 2011 10:45 AM

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

Dif betwen BDC call transaction and session method

Hi to all,
           This is my problem. I want to know, what is the difference between BDC call Transaction method and Session method. where the situation we can use these methods.
I will be thankfull to all.

Session Method :
   Asynchronous Processing.
   Transfers Data for Multiple Transactions
Synchronous Database Update
During Processing, No Transaction is started until the previous transction has been written to the database.
A Batch Input Processing log is generated for each session
Sessions can not be generated in Parallel.
The Batch Input Porgram must not open a Session until it has closed the preceding Session.
Call Transaction :
   Synchronous Processing.
   Transfers Data for a single transaction.
   Synchronous and Asynchronous Database updating both Possible.
   The Program Specifies which kind of updating is desired.
Seperate LUW for the transaction.
The System Performs a database commit immediately before and after the CALL TRANSACTION Using Statement.
No Batch Input Processing Log is generated.
These are the differences between session and call transaction method.
Call transaction is faster then session method. But usually we use session method in real time...because we can transfer large amount of data from internal table to database and if any errors in a session. Process will not complete until session get correct.

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

BDC Call Transaction : FS00(Create G/L Account)

Hi,
BDC of FS00 is running properly in Forground (A) Mode, with success messages and G/L account being created in SKB1 table.
But when I run it in Background (N) Mode, it is not creating the G/L account. Although I am getting the success messages in the end of the execution but in the table, there is no G/L account.
FORM fill_bdcdata .
loop at i_output.
clear i_bdcdata.
refresh i_bdcdata.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ACC_CRE'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_KEY-BUKRS'.
perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-SAKNR'
                               i_output-SAKNR.                               "gl ac number
perform bdc_field       using 'GLACCOUNT_SCREEN_KEY-BUKRS'
                               i_output-BUKRS.                               "company code
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=2102_GROUP'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-KTOKS'.                  "ac grp
*perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              i_output-cc.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                               i_output-xplacct.                             "pl account
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XBILK'
                               i_output-xbilk.                               "balance sheet
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TAB02'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-KTOKS'
                              i_output-ktoks.                                 "ac grp
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-XPLACCT'
                              i_output-xplacct.                               "pl account
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_COA-TXT50_ML'.
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT20_ML'
                              i_output-txt20_ml.                               "short text
perform bdc_field       using 'GLACCOUNT_SCREEN_COA-TXT50_ML'
                              i_output-txt50_ml.                               "long text
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=TAB03'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-MITKZ'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XSALH'
                              i_output-xsalh.                                "Only Balance in Local Currency
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MWSKZ'
                              i_output-mwskz.                                "Tax Category
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XMWNO'
                              i_output-xmwno.                                "Posting without tax
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-MITKZ'
                              i_output-mitkz.                                "Reccon A/C
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XOPVW'
                              i_output-xopvw.                                     "Open Item Management
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XKRES'
                              i_output-xkres.                                     "Line Item Display
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-ZUAWA'
                              i_output-zuawa.                                     "Sort Key
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTER'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                              i_output-fstag.                                     "Field Stauts
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XINTB'
                              i_output-xintb.                                     "post automatically
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-XGKON'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XGKON'
                              i_output-xgkon.                                     "relevent to cash A/c
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-ZUAWA'.
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SAVE'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-FSTAG'.
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-FSTAG'
                              i_output-fstag.                                       "Field Stauts
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XINTB'
                              i_output-xintb.                                       "post automatically
perform bdc_field       using 'GLACCOUNT_SCREEN_CCODE-XGKON'
                              i_output-xgkon.                                        "relevent to cash A/c
perform bdc_dynpro      using 'SAPLGL_ACCOUNT_MASTER_MAINTAIN' '2001'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EEXIT'.
perform bdc_field       using 'BDC_CURSOR'
                              'GLACCOUNT_SCREEN_CCODE-XGKON'.
perform bdc_dynpro      using 'SAPLSPO1' '0100'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
perform f_elog.
endloop.
FORM f_elog .
data len type i.
clear i_msgtab.
call transaction 'FS00'
                      using i_bdcdata
                      mode g_v_mode              "N
                      messages into i_msgtab
                      update g_v_update .          "S
write: i_output-saknr.
I am not getting where I am going wrong in the code.
Regards,
Priyanka.

Hi,
Make the mode 'E' and see excatly, where the warning or errors or coming.
If you are having an currency or UOM ,related fields, see that the values should not be empty. If they are enpty. Put an if condition there and Quit filling such fields.
First keep in mode 'e' and debug. 100% you will see the warnings or errors, then tell me what is the error.
<b>call transaction 'FS00'
using i_bdcdata
mode g_v_mode "E
messages into i_msgtab</b>
Thansk'
Manju.

Improve performance of bdc call transaction

Hi all,
I am performing a batch update of tax codes in a BDC call transaction program. This particular code takes about 3 minutes to process 2,600 entries. I have tried almost everything but is there a way to improve / make it run faster?
I have a feeling it has something to do with the form "do_transaction", but I really don't know anymore.
Thank you in advance.
Attached is the code:
*& Report ZFI_CHANGEWTAX
*& Description: Change Doctors Withholding Tax Code (EI)
*& Using BDC Call Transaction Method
*& Created by : mpena
*& Created on : 07/15/2009
*& Modification History
*& Seq Changed on
*&       Changed by
*& 001   07/15/2009
*&        mpena         Initial Development
*& 002   07/20/2009
*&        mpena         Logic modification
*&                      Testing
*& 003   07/20/2009
*&        mpena         Call function parameter modification
*& 004   07/22/2009
*&        mpena         Report generation
*&                      Performance improvements
REPORT zfi_changewtax
       NO STANDARD PAGE HEADING
       MESSAGE-ID zfk02msg.
TYPES: BEGIN OF t_tax,
       lifnr LIKE lfa1-lifnr,                "account number
       wt_withcd LIKE lfbw-wt_withcd,        "current tax code
       wt_withcd_new LIKE lfbw-wt_withcd,    "new tax code (left blank at default)
       END OF t_tax.
DATA: wa_tax TYPE t_tax,
       i_tax TYPE STANDARD TABLE OF t_tax,
       it_bdcdata TYPE bdcdata OCCURS 0 WITH HEADER LINE,
       lin TYPE i.
-------Selection Screen Design -
SELECTION-SCREEN:
SKIP 1,
BEGIN OF BLOCK blk1 WITH FRAME TITLE aaa.
PARAMETERS: p_ktokk LIKE lfa1-ktokk DEFAULT 'DOCT' OBLIGATORY,
            p_bukrs LIKE lfbw-bukrs DEFAULT 'SL' OBLIGATORY,
            p_wtax LIKE lfbw-wt_withcd OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk1.
INITIALIZATION.
aaa = 'Change Tax Code to specified value'.
TOP-OF-PAGE.
WRITE:
/ 'Update of taxes successful on:', sy-datum, sy-uzeit,
/ 'Generated by:', sy-uname,
/ 'Company Code:', p_bukrs, 'Vendor Group:', p_ktokk.
SKIP 1.
ULINE.
WRITE:
/ 'Account Number', 20 'Old Withholding Tax Code', 50 'New Withholding Tax Code'.
ULINE.
START-OF-SELECTION.
SELECT lfa1~lifnr
         lfbw~wt_withcd
INTO TABLE i_tax
FROM lfa1 INNER JOIN lfbw
    ON lfa1lifnr = lfbwlifnr
    WHERE lfbw~bukrs EQ p_bukrs
    AND lfbw~witht EQ 'EI'.
IF sy-subrc EQ 0.
    DESCRIBE TABLE i_tax LINES lin.
ENDIF.
Update i_tax with new value of wt_witchd, then display for comparison.
After write: if old and new tax are the same, tax update was not successful for that specific account
or inputted tax type is the same as the old one.
LOOP AT i_tax INTO wa_tax.
    wa_tax-wt_withcd_new = p_wtax.
    MODIFY i_tax FROM wa_tax.
    WRITE:
    / wa_tax-lifnr,
    20 wa_tax-wt_withcd,
    50 wa_tax-wt_withcd_new.
    CLEAR wa_tax.
ENDLOOP.
PERFORM do_transaction USING p_bukrs p_wtax.
*&      Form do_transaction
     Extracted from ZFKO2 recording accessible in shdb.
FORM do_transaction USING v_bukrs v_wtax.
MESSAGE i000 WITH lin.
LOOP AT i_tax INTO wa_tax.
    REFRESH it_bdcdata.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0106'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'RF02K-D0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'RF02K-LIFNR'
                                  wa_tax-lifnr.
    PERFORM bdc_field       USING 'RF02K-BUKRS'
                                  v_bukrs.
    PERFORM bdc_field       USING 'RF02K-D0610'
                                  'X'.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '/00'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFBW-WT_WITHCD(01)'.
    PERFORM bdc_field       USING 'LFB1-QLAND'
                                  'PH'.
    PERFORM bdc_field       USING 'LFBW-WT_WITHCD(01)'
                                  v_wtax.
    PERFORM bdc_dynpro      USING 'SAPMF02K' '0610'.
    PERFORM bdc_field       USING 'BDC_OKCODE'
                                  '=UPDA'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                  'LFB1-QLAND'.
    PERFORM bdc_field       USING 'LFB1-QLAND'
                                  'PH'.
    CALL TRANSACTION 'FK02' USING it_bdcdata
                            MODE   'N'
                            UPDATE 'A'.
ENDLOOP.
MESSAGE i001.
ENDFORM.                    "do_transaction
       form for bdc dynpro
FORM bdc_dynpro USING program
                      dynpro.
it_bdcdata-program = program.
it_bdcdata-dynpro = dynpro.
it_bdcdata-dynbegin = 'X'.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM.                    "bdc_dynpro
       form for bdc field
FORM bdc_field USING fnam
                      fval.
it_bdcdata-fnam = fnam.
it_bdcdata-fval = fval.
APPEND it_bdcdata.
CLEAR it_bdcdata.
ENDFORM.                    "bdc_field

You might want to try using a BAPI instead of a call transaction.   I believe "BAPI_VENDOR_SAVECHARVALREPLICA" will work for you. Calling a BAPI is just like calling a function module.   After you call the bapi remember to commit it with the function module "BAPI_TRANSACTION_COMMIT".

CRMXIF_ORDER_SAVE IDOC not getting generated for BUS_TRANS_MSG BDOC

Hello Experts,
In our project, we have a requirement to send custom fields in the BUS_TRANS_MSG to external system through XIF. The model of BDOC BUS_TRANS_MSG triggering IDOC CRMXIF_ORDER_SAVE_M02 perfectly worked in the development system. We wanted to try the custom field extension in the Sandbox. So as per OSS note 916093, we have extended E101_CRMXIF_CUSTOMER_H segments with custom fields and tried generating the interfaces in BDFG transaction. While generation with IDOC CRMXIF_ORDER_SAVE_M we got an error message "Incompatible change to complex data type
type E101CRMXIF_ISU_PRA1_X". So went about creating a custom IDOC ZZ_CRMXIF_ORDER_SAVE_M02 for message CRMXIF_ORDER_SAVE. Even for this config, the IDOC is not getting generated for the BDOCs. Lastly, configured the IDOC ZZ_CRMXIF_ORDER_SAVE_M02 to a custom function module ZZ_BDFG_IDOC_TEST_FM. The FM got generated and activated, even then the IDOC is not generated for the BDOC.
SMOEAC config in Sandbox looks the same as the Development system. We do not the reason why IDOC is not getting generated and also the reason for error in BDFG while generating the interfaces after adding custom fields to CUSTOMER_H segment.
Any help would be appreciated.
Thanks,
Partha

Hi Partha,
Kindly check the following thread.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/406efa7e-388a-2910-f9b8-81913b0ca57f?QuickLink=index&overridelayout=true
XIF adapter
Hope it answers your Query
Regards,
Srikanth.Naga

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

Reg Vendor master upload using BDC Call Transaction Method

Hi All,
Thanks in advance.
I am uploading vendor master data using bdc call transaction method for XK01. In that i am getting an error message that the fields " smtp_addr" ( for email) and "time_zone" (for time zone) doesnot exist on the screen '0110' ( this is the second screen) . the field timezone will be displayed on the screen only when we go for communications button and select the URL field .
Do anybody have the solution for this problem. if possible can you give me the code for that screen.

Create a recording via SM35 (menu go to=>recording), this will generate automatically the code for filling your bdcdata-table...

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

Similar Messages

Maybe you are looking for