Extract document data from sap-plm (sap database) to windchill

Hi,
Can i extract document data from sap-plm (sap database) to windchill using draw_extract fm??? if yes how to proceed....
Thanks and regards,
santhosh

Hi Santhosh,
You can refer the below links:
/people/harrison.holland5/blog/2006/11/27/mdm-syndication
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
Hope it helps.
Thanks,
Priti.

Similar Messages

HOw to connect and extract the data from MS ACCESS SOURCE(Database) system

Hi experts ,
I have to extract the data from MS access database system using JDBC adapter will it work if Yes HOW?

Hi Sushma,
how to configure sendor JDBC adapter ..
Select adapter type is JDBC..
Give the Transport Protocol:.JDBC 2.0 (Example)............
Message Protocol:...JDBC...........
IAdapter Engine : Integration Server
Processing Parameters..
Quality of service.....(Example)..Exactly once
Poll Interval .... Example ..10
Query Sql statement..Example ..select * from XXXXX
Document Name.....
Update Sql stetement.....
Thanks,
Satya
Reward points if it id useful...

Extraction of data from SAP R/3 Bapi into SAP BW

hi,
i am extracting data from sap r/3 bapi into sap bw. can u please send me the link and documents of how to extract the data from bapi to sap bw.
Answers will be rewarded
Thanks
sd shahid

Hi Swapnali,
In your case you have to send process order to XI and you have a bapi that satisfies your requirement.
Here the solution depends what is the triggerring point of the Interface.
If you want that from SAP side Interface should be triggered, then Use ABAP proxy program
You have to craete a Abap proxy class using outbound message interafce defined in IR of XI.This can be done by transaction SPROXY.
Then create a program that call sync/async method that is created by Sproxy t.code.
In this way , when u will execute the proxy program in R/3 , then call will be made to BAPI in Sap from XI server and u will get output back to your proxy program.
If your requirement is to not to trigger from SAP then nothing is required in R/3 side.
In XI , Bapi will be added in imported objects in Integration repository and bapi will be called.
Hope this will help u.
Please revert in case of queries.
Regards,
Monica

How to extract Inventory data from SAP R/3 system

Hi friends How to extract Inventory data from SAP R/3 system? What are report we may expect from the Inventory?

Hi,
Inventory management
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how%20to%20handle%20inventory%20management%20scenarios.pdf
How to Handle Inventory Management Scenarios in BW (NW2004)
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328
Loading of Cube
ref.to page 18 in "Upgrade and Migration Aspects for BI in SAP NetWeaver 2004s" paper
http://www.sapfinug.fi/downloads/2007/bi02/BI_upgrade_migration.pdf
Non-Cumulative Values / Stock Handling
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
Non-Cumulatives
http://help.sap.com/saphelp_nw2004s/helpdata/en/8f/da1640dc88e769e10000000a155106/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62ebe07211d2acb80000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a62f8e07211d2acb80000e829fbfe/frameset.htm
Here you will find all the Inventory Management BI Contents:
http://help.sap.com/saphelp_nw70/helpdata/en/fb/64073c52619459e10000000a114084/frameset.htm
2LIS_03_BX- Initial Stock/Material stock
2LIS_03_BF - Material movements
2LIS_03_UM - Revaluations/Find the price of the stock
The first DataSource (2LIS_03_BX) is used to extract an opening stock balance on a
detailed level (material, plant, storage location and so on). At this moment, the opening
stock is the operative stock in the source system. "At this moment" is the point in time at
which the statistical setup ran for DataSource 2LIS_03_BX. (This is because no
documents are to be posted during this run and so the stock does not change during this
run, as we will see below). It is not possible to choose a key date freely.
The second DataSource (2LIS_03_BF) is used to extract the material movements into
the BW system. This DataSource provides the data as material documents (MCMSEG
structure).
The third of the above DataSources (2LIS_03_UM) contains data from valuated
revaluations in Financial Accounting (document BSEG). This data is required to update
valuated stock changes for the calculated stock balance in the BW. This information is
not required in many situations as it is often only the quantities that are of importance.
This DataSource only describes financial accounting processes, not logistical ones. In
other words, only the stock value is changed here, no changes are made to the
quantities. Everything that is subsequently mentioned here about the upload sequence
and compression regarding DataSource 2LIS_03_BF also applies to this DataSource.
This means a detailed description is not required for the revaluation DataSource.
http://help.sap.com/saphelp_bw32/helpdata/en/05/c69480c357354a8846cc61f7b6e085/content.htm
http://help.sap.com/saphelp_bw33/helpdata/en/ed/16c29a27db6e4d81a015be8673eb80/content.htm
These are the standard data sources used for Inventory extraction.
Hope this helps.
Thanks,
JituK

Extracting updated data from SAP R/3 to BOBJ DS

Hi all,
I have a doubt reg extracting updated data from SAP to BOBJ DS. For example i am extracting 50000 records from SAP table to BOBJ DS say its taking half an hour, after extracting data 10 more records have added in the same table. Do we need extract the whole record again or do we have some other way to extract only those 10 records from table.
Please help me. I have searched in forums but cudnt find the exact solution fyi.
Thanks,
Guna

Apart from stepd 1,2, you need to create a Target Data store and a table to load your MARA data.
3. Now the MARA data will be available in data store(DS_ERP), say table name as BO_MARA
Why do you want to change the table name? Are you planning to stage the data anywhere?
4. Create a dataflow source as BO_MARA, query transform and destination as a table
Data transport object is required if you are using R/3 Data Flow.
This would suffice just for a full load, if all your transformations can be incorporated inside the Query transform.
5. Do Transformation.
6. Transformed data will be available in target table.
Only after executing the job that the transformed "data" will be available in the target.
The above part mentions only about a Source, Query transform, Source Data Store and table.
Apart from these
You would require a Script object to write the condition, to SELECT the MAX timestamps. You would require Variables to be created in your job to redirect your job path and to restrict the data extracted.
Use your DataFlow in a Conditional object. If load type is first, in the then part use the dataflow which you might have already designed. Else part will have a replicated Data Flow with the above mentioned WHERE condtion in Query transform.
Suggest you to refer Desiger document and DI supplement for SAP as well. Inform if you are stuck.
Regards,
Suneer Mehmood.

Extract data from CRM to SAP R/3

Hi Experts,
I Facing Problem to Extract the data from database table BUT000 in CRM 2.0 System to SAP R/3 whether its possible to update the data directly in R/3 system from CRM. whether any functional module exists?
Plz Provide me details about it

Why do you need to copy it? The data is easily available from R/3 via RFC.
Rob

Extract data from AMPLA to SAP BW

Hi All,
My requirement is to extract data from a Non SAP system called AMPLA (SQL Server 2012) to SAP BI system (7.0). I need to consider possible ways for SAP BI to extract data from Non SAP Systems like DB Connect, UD Connect, Web services etc. Does anyone have experience extracting AMPLA data to SAP BI system successfully and what method is ideal to be used? Also in what form is data usually available in AMPLA source system(tables/views etc)?

Hi Udit
Before that could you refer this SAP Notes for database connection
128126: Database Connect for external tools
1601608: How to access an external SQL Server database
Regards
Sriram

How to extract PS data from sap r/3 to bw

Hi,
How to extract PS data from sap r/3 to bw
PS data like plans,budget,accurals&commitmnets
can any one help me regarding this..
Thanks in Advance,
Shankar.

HI sankar,
you can refer the belkow link to find the details on the relevant extractors and infoproviders
http://help.sap.com/erp2005_ehp_04/helpdata/EN/17/416d030524064cb2b8d58ffb306f3a/frameset.htm
Regards,
Sathya

How to Extract the data from Microsoft BI to SAP BI 7

Dear All,
We have a requirement to Extract the data from Microsoft BI to Sap BI 7. How can we achieve this??
Shall we use the DB connection for this??
If anyone knows about this please give me some suggestion.
Thanks in advance
Sathiya

Hi All,
How to include the DBMS name when I give the connection. We are using the Data base as MS-BI.
Please guide me
Thanks in advance.
Regards
Sathiya

Passing data from JAVASCRIPT to SAP database

Hi Experts,
Is it possible to connect or access RFC function module through JAVASCRIPT? I want to send data from JAVASCRIPT to SAP database table.
Is it possible to pass data from JAVASCRIPT to SAP database table?
Thanks in advance.
Regards,
Arindam Samanta.

OData services can be one option to achieve this.
Another possibility can be use of Generic REST enablement with SAP NetWeaver Gateway.
If you are not considering Gateway at all, then A JSON adapter like the one mentioned in JSON Adapter for ABAP Function Modules can be handy.

CC 5.2 Alert Generation - Not extracting any data from SAP

Hi there,
We are trying to use the alert function for critical transactions in CC 5.2. We have set the relevant parameters in CC. The Alert_Log.txt is created successfully but it is not extracting any data from SAP. Is there any settings that I am missing here, both in R/3 and CC 5.2? I really appreciate your help. Below is the Alert_Log.txt for your review.
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
FINEST: Analysis Daemon started background Job ID:41 (Daemon ID D:\usr\sap\CC1\DVEBMGS00\j2ee\cluster\server0\. Thread ID 0)
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Scheduling Job =>41----
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob run
INFO: --- Starting Job ID:41 (GENERATE_ALERT) - AlertGeneration_Testing
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 41 Status: Running
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
1@@Msg is AlertGeneration_Testing started
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO:
Background Job History: job id=41, status=1, message=AlertGeneration_Testing started
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Alert Generation Started @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Conflict Risk Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Critical Risk Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@ Mitigation Monitor Control Input has 1 records @@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: @@@@@ Backend Access Interface execution has been started @@@@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: @@System=>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO:
No of Records Inserted in ALTCDLOG =>0 For System =>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface append_TcodeLogFile
INFO: *********SOD Tcode Size=>0**************
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface append_TcodeLogFile
INFO: *********Alert Tcode Log File=>D:\cc_alert_log\cc_alert_log1.txt is created**************
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO:
File Output Log File Size ==>0----
For System =>R3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: -
Conf Last Run Date=>2007-12-12--Conf Last Run Time=>12:45:11--
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface alertGenerate
INFO: ==$$$===Notif Current Date=>2007-12-20==$$$==Notif Current Time=>14:27:32===$$$===
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>1
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>CONFALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>2
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>CRITALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ****************** send Notification Alert Type=>3
Dec 20, 2007 2:27:32 PM com.virsa.cc.comp.BackendAccessInterface send_AlertNotification
INFO: ******Alert Notification=>MITALERTNOTIF==LastRunDate:=>2007-12-20==LastRunTime:=>00:00:00==Curr Date=>2007-12-20==Curr Time=>14:27:32*********
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: Start AlertStats.............
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: start:Sat Dec 01 14:27:32 CST 2007
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: now:Thu Dec 20 14:27:32 CST 2007
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: end: Tue Jan 01 14:27:32 CST 2008
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.mgmbground.dao.AlertStats execute
INFO: Month 2007/12
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob alertGen
INFO: @@@=== Alert Generation Completed Successfully!===@@@
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob setStatus
INFO: Job ID: 41 Status: Complete
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.BgJob updateJobHistory
FINEST: --- @@@@@@@@@@@ Updating the Job History -
0@@Msg is Job Completed successfully
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert
INFO:
Background Job History: job id=41, status=0, message=Job Completed successfully
Dec 20, 2007 2:27:32 PM com.virsa.cc.xsys.riskanalysis.AnalysisDaemonBgJob scheduleJob
INFO: -
Complted Job =>41----

Hi,
we have ran into similar issue of alert log being not displayed accurately in CC 4.0 version and we implemented the Note 1044393 - CC5.1 Alerts, it did work for us, as you are using CC5.2, I would recommend you to check the code and then try this note. But iam still skeptical whether this note will be helpful to you or not.
Thanks,
Kavitha

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
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 youll 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
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Regarding Migrating data from Legacy to SAP

Hi All,
We are in Migration Project. We have to upload data from legacy to SAP, either using BDC or Cross-Applications in the following SD scenario's.
1. Customer Master
2. Inquiries
3. Quotations
4. Proposals
5. Sales Order
6. Goods Issue
I would like to know, which concept is better for each of the above scenario. Each option have advantages and disadvantages. So, I need suggestion regarding this.
Regards,
Sathya.

hi
LSMW and BDC are vastly different.
BDC (Batch Data Communication) is a technology used for data transfer. it is meant for transferring data thru SAP transactions itself. when u use BDC for data transfer, the sequence of steps is the same as when u use standard sap transaction screens for data upload. the only difference is that u can use different options for foreground/backgrou nd processing.
LSMW on the other hand is a tool that helps migrate data from a legacy system (non-sap system ) to SAP system. it offers u various options to use either batch input, direct input, BAPIs or idocs. it involves a series of some 17-18 steps to migrate data.
BDC:
Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.
Features :
BDC is an automatic procedure.
This method is used to transfer large amount of data that is available in electronic medium.
BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).
BDC uses normal transaction codes to transfer data.
Types of BDC :
CLASSICAL BATCH INPUT (Session Method)
CALL TRANSACTION
BATCH INPUT METHOD:
This method is also called as CLASSICAL METHOD.
Features:
Asynchronous processing.
Synchronous Processing in database update.
Transfer data for more than one transaction.
Batch input processing log will be generated.
During processing, no transaction is started until the previous transaction has been written to the database.
CALL TRANSACTION METHOD :
This is another method to transfer data from the legacy system.
Features:
Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.
Updating the database can be either synchronous or asynchronous. The program specifies the update type.
Transfer data for a single transaction.
Transfers data for a sequence of dialog screens.
No batch input processing log is generated.
LSMW:
The LSM Workbench is an R/3-based tool that supports You when transferring data from non-SAP systems ("Legacy Systems") to R/3 once or periodically.
The tool supports conversion of data of the legacy system in a convenient way. The data can then be imported into the R/3 system via batch input, direct input, BAPIs or IDocs.
Furthermore, the LSM Workbench provides a recording function that allows to generate a "data migration object" in an entry or change transaction.
The main advantages of the LSM Workbench:
Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:
Batch input
Direct input
BAPIs (Business Application Programming Interfaces)
IDocs (Intermediate Documents)
The import technique to be used in an individual case depends on the business object.
Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners
also check this link:
Diff. between LSMW & BDC
Re: bdc and lsmw
plz reward points if it helps
rgds.

How to push data from BW into SAP R/3 system???

Hello,
We have faced a problem. We need to push compressed sales data from BW to SAP R/3 system. But We don't know how to do it.
Does it exist the standard instruments for it (without ABAP development)?
How to integrate BW and SAP system?
We will be much obliged you for your recomendations and advices.

Hi Igor,
I'm not aware of any standard out of the box mechanisms for moving Sales data back into SAP ERP. There are some delivered "retractors" for business scenarios like financial planning and consolidations where updated data is sent back to SAP ERP in a closed loop scenario. These retractors have been written in ABAP.
I would suggest that you search the latest BI content to see if there is anything for sales data retraction. There might also be information in SAP note on how to do this in code.
To send data from BI, you can also use the 'open hub' feature to extract the BI data to a DB table or file for example. This could then be read by a program to load SAP ERP. The loading would have to be custom development.
Sorry I can't help you more - I fear you will most definitely have some custom development in this case.
Cheers,
Mike.

How can we post data from CRM to SAP using ABAP proxies???

Hi ,
Can anyone hep me to create interface for the following scenario How can we post data from CRM to SAP using ABAP proxies???, can I find any document ???????
Thanks in advance
Andy

Andy,
Please look at these weblogs.
/people/ravikumar.allampallam/blog/2005/03/14/abap-proxies-in-xiclient-proxy
/people/ravikumar.allampallam/blog/2005/03/03/creating-purchase-order-idoc-through-xi
/people/siva.maranani/blog/2005/04/03/abap-server-proxies
/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
These should give a good idea about implementing Proxies.
Regards,
Ravi

Extract document data from sap-plm (sap database) to windchill

Similar Messages

Maybe you are looking for