SAP MII 14.0 - Calling Transactions using SOAP Runner fails

Hello All,
We are calling transactions in SAP MII 14.0 from external apps using SOAP Runner and we are passing the login info in the payload. But we are getting the following error.
We are passing the following in the payload.
<xmii:LoginName>Username</xmii:LoginName>
<xmii:LoginPassword>Password</xmii:LoginPassword>
We are getting 401 unauthorized as the user name and password is not propagated to the MII.
It works if we supply the info explicitly when we invoke the URL.
Thanks,
Kiran

Hello Rajesh,
I don't think that will be allowed. We usually pass the credentials in the payload and it has always worked for us in MII 12.1. But in MII 14.0 it does not seem to be working.
Thanks,
Kiran

Similar Messages

Message type in BDCMSGCOLL Structure in Call transaction using BDCDATA

Hi,
We are facing issue while capturing message in BDCMSGCOLL structure in Call transaction using bdcdata. The message which are like
Message 'Message Text' Type 'S' Display LIke 'E' .
This message is captured as Success on the Message structure instead of error & user are asking to update it as Error as it is looking like Error message to the end user.
Please provide resolution to the issue.
Regards,
Kapil

Hi Venkat,
I am not doing any upload, i am just doing a replay of the transaction ME21 & in that there are many error message which encounter while creating a PO but when i have check the logic , they are basically a success message which are display like Error so when i have called ME21 transaction using below statement
call transaction ME21 using BDCDATA
into messages bdcmsgcoll.
I am getting the message as success only since the message are of type success but as they are display like E , so user want that in msgcoll structure these messages must be shown as Error.
Regards,
Kapil.

URL format to call transaction using WinGUI

Hello,
We would like to display SAP transactions in the portal, however they are from the SAP APO sytem and require the the WinGUI setting as they contain graphics that the ITS cannot interpret. WinGUI does not use the ITS. An iView or External Service can be created to display the required transactions using the SAPApplication.Transaction but as the screens are made up of several windows we would like them to open up full screen. The standard iView can open in a new screen but the window opens in a different place depending on the user's internet settings. To solve this a java iView could be written to dictate the starting point and size of the window but I am having trouble with the URL of the transaction. Using WebGUI the following format can be used to call a transaction:
<System.Access.ITS.Protocol>://<System.Access.ITS.HostName><System.Access.ITS.Path>/webgui/!?transaction=<SAP_Dynp_AutoStart%><SAP_TCode>%20<SAP_Dynp_Params%>&client=<System.Client>&language=<Request.Language>&accessibility=<User.Accessibility>
Does anyone know the format of the URL to call a transaction using wingui (it doesn't work to substitute wingui for webgui in the format above)?
Thanks for your help,
Katie

HI,
You need to write the codition like below,
If Message = 'Successful'
If Button = 'SUBMIT'
Call Transaction 'ZABC'.
Endif.
Endif.
Regards
Sudheer

CAll transaction using Adobe

Hi
My Requirement is call to a transcation ex: VA01 using ADOBE thru webservice(Fn module input-> sales order no).
The transaction shld be called when user hit the SUBMIT button Adobe interactive form.
I can create the button in webdynpro and called the screen using the below method. Its working.
lo_window_manager->create_external_window(
exporting
url = url
receiving
window = lo_window ).
But the requirement is only to call transaction when the user hit the submit button in the Adobe form.
It would be helpful if get an idea regarding the same.
Thanks
Arun

Hi
Thanks for all your replies.
Sanoosh
I tried to code in the function module. when submit the button in Adobe Interactive form is calling the Fn module (webservice).
But I couldnt decalre the wd_comp_controller->wd_get_api( ).
wd_comp_controller is an interface. how to decalre this interface in the function module source code.
Here is the complete code I tried in Function Module.
DATA: url TYPE string,
        host type string,
        port type string.
*Call below method to get host and port
cl_http_server=>if_http_server~get_location(
     IMPORTING host = host
            port = port ).
*create URL
CONCATENATE 'http'
'://' host ':' port
'/sap/bc/gui/sap/its/webgui/?sap-client=&~transaction=' 'VA03'
   INTO url.
*get the window manager as we are opening t code in external window.
DATA lo_window_manager TYPE REF TO if_wd_window_manager.
DATA lo_api_component TYPE REF TO if_wd_component.
DATA lo_window TYPE REF TO if_wd_window.
lo_api_component = wd_comp_controller->wd_get_api( ).
lo_window_manager = lo_api_component->get_window_manager( ).
call the url which we created above
lo_window_manager->create_external_window(
exporting
url = url
receiving
window = lo_window ).
lo_window->open( ).
Thanks & Regards

Call transaction using bdc tab and also skip first screen??

Hi,
Please help.
I want to call transaction PA30 fill it with values which are determined only at runtime and then skip first screen.
The screen doesn't have parameter fields so i cannot use 'set parameter id'.
I also cannot create a transaction with parameters as I only have these at runtime.
Anyone done anything like this???

hi,
you might be populateing the itab bdc_tab with the corresponding values fronm the recording.
while doing the recording go until to the screen wher u want to finsih.
and populate the bdc_tab wit the ok code,screen number and the value.
this will do.
for eg see the code below.
METHOD analyze_log.
DATA : wrk_extid TYPE balhdr-extnumber.
DATA : wrk_date(10) TYPE c.
DATA : it_rspar TYPE TABLE OF rsparams .
DATA : wa_rspar TYPE rsparams.
DATA: it_bdcdata TYPE STANDARD TABLE OF bdcdata,
      wa_bdcdata TYPE bdcdata.
DATA: params TYPE ctu_params.
CONSTANTS : object TYPE balhdr-object VALUE 'ZKIV_LOG'.
IF wa_kopf-vertr_nr IS NOT INITIAL.
    CONCATENATE wa_kopf-vertr_nr '/' wa_kopf-nachtr_nr INTO wrk_extid.
    wrk_date = '01.09.2006'.
    SET PARAMETER ID 'BALOBJ' FIELD object .
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
    wa_rspar-selname = 'ALDATE'.
    wa_rspar-sign = 'I'.
    wa_rspar-kind = 'P'.
    wa_rspar-option = 'EQ'.
    wa_rspar-low = wrk_date.
    APPEND wa_rspar TO it_rspar.
ELSE.
    CLEAR wrk_extid.
    SET PARAMETER ID 'BALEXT' FIELD wrk_extid.
ENDIF.
Update BDC tab
--Call SLG1 using BDC--&
params-dismode = 'E'. "Show errors only
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_CURSOR'.
wa_bdcdata-fval = 'BALHDR-ALDATE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BALHDR-ALDATE'.
wa_bdcdata-fval = wrk_date.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=SELE'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-program = 'SAPLSLG3'.
wa_bdcdata-dynpro   = '0100'.
wa_bdcdata-dynbegin = 'X'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_OKCODE'.
wa_bdcdata-fval = '=&F03'.
APPEND wa_bdcdata TO it_bdcdata.
CLEAR wa_bdcdata.
wa_bdcdata-fnam = 'BDC_SUBSCR'.
wa_bdcdata-fval = 'SAPLSBAL_DISPLAY                        0101SUBSCREEN'.
APPEND wa_bdcdata TO it_bdcdata.
CALL TRANSACTION 'SLG1' USING it_bdcdata OPTIONS FROM params.
--End of BDC--&
ENDMETHOD.
here wat i m doing is that i dont want the subscreen 101 to be displayed..
Message was edited by:
        Sandeep S

CALL transaction using itab aswell as skip the first screen

Hi All,
I am doin BDC for some Ztransaction and i am that transaction using CALL TRANSACTION... but i want to skip the first screen of the Ztransaction as well as pass the Itab .. mode .. update and message table.... how can i do it...
CALL TRANSACTION Z... USING iTAB UPDATE DATE MODE A message bdcmsgcoll AND skip THE FIST SCREEN.. how to acheive it....

PERFORM BDC_DYNPRO      TABLES BDCDATA
                       USING 'SAPLBPT1' '0100'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BDC_CURSOR'
                             'BCONTD-BPCONTACT'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BDC_OKCODE'
                             '/00'.
*PERFORM BDC_FIELD       TABLES BDCDATA
                       USING 'BCONTD-BPCONTACT'
                              V_CONTRACT.
the above code /recording call the first screen 100 which i dont want...
below code / recording is for screen 200 which i want to appear directly when i call the transaction....
skipping the first screen 100..
PERFORM BDC_DYNPRO      TABLES BDCDATA
                        USING 'SAPLBPT1' '0200'.
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BDC_OKCODE'
                              '=SAVE'
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BCONTD-PARTNER'
                               V_GPART.
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BCONTD-ADDINFO'
                               V_ZONE.         "ZONE(S,N,E,E,NE)
PERFORM BDC_FIELD       TABLES BDCDATA
                        USING 'BDC_CURSOR'
                              'EENO_DYNP-ZEILE(01)'.
PERFORM BDC_FIELD       TABLES BDCDATA
                         USING 'EENO_DYNP-ZEILE(01)'
                               V_LOG.                 "MESSAGE
CALL TRANSACTION 'BCT1'    USING BDCDATA
                           MODE MODE UPDATE UPDATE
                           MESSAGES INTO IT_BDCMSGCOLL.

CALL transaction using generic user.

Hi experts,
I have a CALL TRANSACTION, which code is: 'ME54' USING BDC_TAB MODE 'E' UPDATE 'S'.
I have previosly defines the BDC_TAB. Is is a backgroud process executes with an event. The sy-uname there is the same as the user that has lauched the event. I want this to be executed with a generic user, example GENUSER instead of the one that really launches the event.
¿Is this possible?
Thank-you very much,
Artur.

Hi,
The only way I can think of at the moment is to extract your CALL TRANSACTION into a separate self-contained program (which it may already be looking at your post). Then use FM JOB_OPEN, JOB_SUBMIT (changing the parameter AUTHCKNAM to you generic user) and JOB_CLOSE (with STRTIMMED = abap_true).
This obviously gives rise to other problems such as knowing when the job finished etc but this depends on your overall design and if this is important or not.
Looking at your overall process this does not sound like a problem. Simply change the background job step for the event - have it call a new program to perform the JOB* FM steps instead which calls your original program that was registered against the event.
Thanks,
Pete

Problem in call transaction using FD33 t code

Hi all i'm developing a report in that in that i'm calling a tcode FD33.
I want to skip the initial screen.For that i need to pass Customer , Credit control area and status from my program to that tcode.
But my problem is that how to pass the value to check box.
i.m writing the following code
   "Set parameter ID for transaction screen field
        SET PARAMETER ID 'KUN' FIELD W_ALV-KUNNR.
        SET PARAMETER ID 'KKB' FIELD W_ALV-VKORG.
       "Execute transaction FD33, and skip initial data entry screen
        CALL TRANSACTION 'FD33' AND SKIP FIRST SCREEN.
So how to set the value of the STATUS check box.
thanks in advanced.
Dheeraj

use:
data: dynnr(40) value '/210'.    "or number of another dynpro you wish to go
SET PARAMETER ID 'CDY' FIELD dynnr.
A.

RE-FX:call transaction using bdc-tab:No bdc_okcode for swapping table-entry

Hello,
I am trying to call transaction RERAOP (module RE-FX) to make an accounting transaction. There is 1 debit posting and 1 credit posting in a grid. Selecting the debit posting, a details scrren is shown, consisting of 2 registers.
On the first register you have to fill different fields. At this point it isn't possible to select the second register. The second (credit) posting is diplayed when you hit the enter key. After the fields in the details screen of this (credit) postings have been filled, it is possible to swap back to the first (debit) posting with a double-click on the first entry of the postings-table.
Finally I come to the point ...
If I record these steps (batch-input recorder) and generate an report of this code there is no bdc_okcode for the above mentioned swap back to the debit posting. While executing this report I get a lot of error message because the swap back to the debit posting doesn't work (--> because of the missing bdc_okcode) and therefore the batch input tries to fill fields which are not on the active screen (because they are on the 2. register which is not displayed).
Hope that there is someone out there who:
1. Understands my miserable english and
2. has an advice for me.
Thanks in advance!!!
Stephan
Edited by: Stephan Scholze on Apr 22, 2008 1:34 PM
Edited by: Stephan Scholze on Apr 22, 2008 2:24 PM
Edited by: Stephan Scholze on Apr 22, 2008 3:19 PM

Not sure how much I can help as we don't run RE-FX (RERAOP - what's the program name btw?) at any sites I work at, but a couple of general BDC things you might try (based on problems I've had with BDCs to other Tcodes)...
When you are in that transaction normally do a right click to see what function codes are defined as there might be one there that allows you to switch between these debit & credit data entry places (how are they rendered, btw - are they ALV grids or what? If they are table controls then you should be able to position the cursor on row 1 and trigger an F2 double-click)... also look at the PF-STATUS carefully in case (once again) there is a function code that lets you swap from DR to CR & vice versa... and even browse the source code in the user-command for the screen might give a clue as to how to achieve this. Of course it may not be possible if the data entry is control based i.e. the input areas are provided in the SAPGui not the application server (such as the text editor & ALV grids)... in which case you start hunting for BAPIs and function modules and the like, or end up having to pass data into the transaction via something like an "export" and catch it inside a user exit or enhancement via an "import"... all rather messy, but quite possible.
Jonathan

SAP MII workbench - saving new transaction - role issue?

We are using MII 12.1.4 (build 53) and have copied the SAP java roles to our own groups (ABAP Roles) in the UME, including the defined actions of the SAP roles. We then assign the ABAP role in ABAP to the User, so that in the UME they now have the groups assigned.
We have run into an issue where when creating a new transaction in the MII workbench we are unable to save it. If we add the standard SAP UME role SAP_XMII_DEVELOPER, we are now able to create and save the transaction (or whatever work). The only difference we can see in the SAP_XMII_DEVELOPER role and our copied role is the name, all the actions in SAP_XMII_DEVELOPER are in our Group (ABAP role).
our ABAP role (UME Group) example is:
ZZZZ:Z_MII_DEVELOPER (has UME role AD_JU_MII_DEVELOPER assigned)
UME Roles:
Z_MII_DEVELOPER has the 3 actions below assigned:
     xappsxmiiumeactions     XMII_User
     xappsxmiiumeactions     XMII_Read_Only
     xappsxmiiumeactions     XMII_Developer
SAP_XMII_DEVELOPER has the same 3 actions as above, and the onluy difference is the description, and that it doesn't have any assigned groups.
Does the MII workbench use the hardcoded role names somewhere that would not allow us to use our the ABAP roles (JAVA groups) or is there something else we are missing in the group?
I have searched the best practices, forums, SAP help, OSS, etc. with no luck
Thanks for any help,
jake

Hi Jake,
I also faced the same problem recently.
As Mike said, you need to add your role in " Transaction -> Security". Here, you will find all the available roles. Put the required role in Reader and Writer Roles windows.
As far as your question is concerned, by default MII assigns XMII Administrators, XMII Developers and XMII Users roles (MII 12.0) as Reader to Transaction. Where as MII assigns XMII Administrators and XMII Developers roles as Writer to Transaction.
Hope this helps!
Best Regards,
Kedar

How to call webservices using soap in xi

Hello
I am tring to work on webserivces,bascially i am not having any knowledge on webservices,i have seen the documentation & i know how to configure soap adapter & how to define webservice in integration directory.can any one please help me out how to work with webservices & good documentation on webservices & soap.
Thanks
Rajesh

Hi Rajesh,
Use server(tomcat server) or plain html coding for defining webservices....
check sample webservice coding
Purchase Order Web Application
dispDate(0)
Purchase Order Input Parameters:
Document Type:
Standard PO
Vendor Number:
Purchase Order Date:
Purchasing Material:
Delivery Date:
Quantity:
NetPrice:
Unit of Measurement:
PCs
PriceUnit:
Results:
/code
And gothrough the following weblogs which will be useful...
/people/siva.maranani/blog/2005/03/01/testing-xi-exposed-web-services
/people/thomas.jung3/blog/2005/06/05/web-services-the-case-of-the-missing-soap-action-header
/people/siva.maranani/blog/2005/09/03/invoke-webservices-using-sapxi
Hope u get some idea...
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

Rollback a call transaction using CTU_PARAMS

Is there any combination of CTU_PARAMS and ROLLBACK that can be used to rollback a call txn. A BAPI is not available for me to use to perform the function I need.

Hi,
I dont think there would be any combination available for CTU_PARAMS and ROllback.
CTU_PARAMS is available only under the following FM`S :
BDC_RECORD_TRANSACTION
BDC_RUNNING
RS_HDBDC_CALL_TC_BATCH_INPUT
RS_HDBDC_CHANGE_TC_BATCH_INPUT
Rollback can be done using BAPI_TRANSACTION_ROLLBACK.
It would be good if you call the Roll back BAPI explicitly instead of doing rollback along with CTU_PARAMS. Make both of them as independent calls.
Best regards,
Prashant

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.

What are the parameters in Call transaction method?

Hi ABAPER'S,
Please give me what are the parameters in call transaction method?
Thanks,
Prakash

Processing batch input data with CALL TRANSACTION USING is the faster of the two recommended data transfer methods. In this method, legacy data is processed inline in your data transfer program.
Syntax:
CALL TRANSACTION <tcode>
USING <bdc_tab>
MODE <mode>
UPDATE <update>
<tcode> : Transaction code
<bdc_tab> : Internal table of structure BDCDATA.
<mode> : Display mode:
A
Display all
E
Display errors only
N
No display
<update> : Update mode:
S
Synchronous
A
Asynchronous
L
Local update
A program that uses CALL TRANSACTION USING to process legacy data should execute the following steps:
Prepare a BDCDATA structure for the transaction that you wish to run.
With a CALL TRANSACTION USING statement, call the transaction and prepare the BDCDATA structure. For example:
CALL TRANSACTION 'TFCA' USING BDCDATA
MODE 'A'
UPDATE 'S'.
MESSAGES INTO MESSTAB.
IF SY-SUBRC <> 0.
<Error_handling>.
ENDIF.
The MODE Parameter
You can use the MODE parameter to specify whether data transfer processing should be displayed as it happens. You can choose between three modes:
A Display all. All screens and the data that goes in them appear when you run your program.
N No display. All screens are processed invisibly, regardless of whether there are errors or not. Control returns to your program as soon as transaction processing is finished.
E Display errors only. The transaction goes into display mode as soon as an error in one of the screens is detected. You can then correct the error.
The display modes are the same as those that are available for processing batch input sessions.
The UPDATE Parameter
You use the UPDATE parameter to specify how updates produced by a transaction should be processed. You can select between these modes:
A Asynchronous updating. In this mode, the called transaction does not wait for any updates it produces to be completed. It simply passes the updates to the SAP update service. Asynchronous processing therefore usually results in faster execution of your data transfer program.
Asynchronous processing is NOT recommended for processing any larger amount of data. This is because the called transaction receives no completion message from the update module in asynchronous updating. The calling data transfer program, in turn, cannot determine whether a called transaction ended with a successful update of the database or not.
If you use asynchronous updating, then you will need to use the update management facility (Transaction SM12) to check whether updates have been terminated abnormally during session processing. Error analysis and recovery is less convenient than with synchronous updating.
S Synchronous updating. In this mode, the called transaction waits for any updates that it produces to be completed. Execution is slower than with asynchronous updating because called transactions wait for updating to be completed. However, the called transaction is able to return any update error message that occurs to your program. It is much easier for you to analyze and recover from errors.
L Local updating. If you update data locally, the update of the database will not be processed in a separate process, but in the process of the calling program. (See the ABAP keyword documentation on SET UPDATE TASK LOCAL for more information.)
The MESSAGES Parameter
The MESSAGES specification indicates that all system messages issued during a CALL TRANSACTION USING are written into the internal table <MESSTAB> . The internal table must have the structure BDCMSGCOLL .
You can record the messages issued by Transaction TFCA in table MESSTAB with the following coding:
(This example uses a flight connection that does not exist to trigger an error in the transaction.)
DATA: BEGIN OF BDCDATA OCCURS 100.
INCLUDE STRUCTURE BDCDATA.
DATA: END OF BDCDATA.
DATA: BEGIN OF MESSTAB OCCURS 10.
INCLUDE STRUCTURE BDCMSGCOLL.
DATA: END OF MESSTAB.
BDCDATA-PROGRAM = 'SAPMTFCA'.
BDCDATA-DYNPRO = '0100'.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
CLEAR BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CARRID'.
BDCDATA-FVAL = 'XX'.
APPEND BDCDATA.
BDCDATA-FNAM = 'SFLIGHT-CONNID'.
BDCDATA-FVAL = '0400'.
APPEND BDCDATA.
CALL TRANSACTION 'TFCA' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
LOOP AT MESSTAB.
WRITE: / MESSTAB-TCODE,
MESSTAB-DYNAME,
MESSTAB-DYNUMB,
MESSTAB-MSGTYP,
MESSTAB-MSGSPRA,
MESSTAB-MSGID,
MESSTAB-MSGNR.
ENDLOOP.
The following figures show the return codes from CALL TRANSACTION USING and the system fields that contain message information from the called transaction. As the return code chart shows, return codes above 1000 are reserved for data transfer. If you use the MESSAGES INTO <table> option, then you do not need to query the system fields shown below; their contents are automatically written into the message table. You can loop over the message table to write out any messages that were entered into it.
Return codes:
Value
Explanation
0
Successful
<=1000
Error in dialog program
> 1000
Batch input error
System fields:
Name:
Explanation:
SY-MSGID
Message-ID
SY-MSGTY
Message type (E,I,W,S,A,X)
SY-MSGNO
Message number
SY-MSGV1
Message variable 1
SY-MSGV2
Message variable 2
SY-MSGV3
Message variable 3
SY-MSGV4
Message variable 4
Error Analysis and Restart Capability
Unlike batch input methods using sessions, CALL TRANSACTION USING processing does not provide any special handling for incorrect transactions. There is no restart capability for transactions that contain errors or produce update failures.
You can handle incorrect transactions by using update mode S (synchronous updating) and checking the return code from CALL TRANSACTION USING. If the return code is anything other than 0, then you should do the following:
write out or save the message table
use the BDCDATA table that you generated for the CALL TRANSACTION USING to generate a batch input session for the faulty transaction. You can then analyze the faulty transaction and correct the error using the tools provided in the batch input management facility.

When we have to go for session method, when we have to go for call transact

when we have to go for session method, when we have to go for call transaction method if i have a 3000 records in flat file. which is better? why

Data Transfer
During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.
As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.
SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:
Direct Input:
In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.
Call Transaction:
In this method you can check the data consistency with the help of screen logic.
Batch Input Session:
In this method data consistency is checked with the help of screen logic.
Direct Input Method
Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.
There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.
Call Transaction Method
Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.
Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.
Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the abovementioned sequential file.
Batch Input Session Method
This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a "batch input session." The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.
As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:
System à Services à Batch input. Moreover, you can have the session run in the background processing.
Writing a Data Transfer Program
If you want to write a data transfer program, you have to follow the steps mentioned below.
Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.
Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.
Thirdly, you will have to initialize the SAP data structure.
Fourthly, fill the structure with data, performing any conversions and error checking that are required.
Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.
Batch Input Method
Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.
There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily..., and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.
The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.
The process flows for a batch input are discussed below.
Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.
Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).
Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.
Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.
Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need to be involved.
Error Handling in Batch Input Method
It is found that most problems usually fall into one of the following two categories discussed below.
In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.
This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non-interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.
Conclusion
I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.
Thanks,
Shankar

SAP MII 14.0 - Calling Transactions using SOAP Runner fails

Similar Messages

Maybe you are looking for