‎2007 Mar 29 1:26 PM
can anyone give me the answers for the below questions
1)what are the views u have used in developing a bdc program for MM01.
2)what was the requirement in material upload bdc program.
My question: who is supposed to do recording in real time? an abaper or a functional guy.
3) he asked me why u have used bdc session method, why not bapi or call transaction.
4)how many types of BDCs are there?
can anyone send the specs for enhancements.
i will be very thankful if anybody give the above answers ,
thanks
‎2007 Mar 29 10:47 PM
Hi Zareena,
1) These are the views used in MM01
MARU
MARCU
MARDU
2) You need to be specific when you say requirement.
Recording is done by a functional guy but if you need to code it then it is done by the ABAPER. (Well clearly it depends on the project you are and the requirement)
3) Inconsistent data could be one of the major reason why u use session. If the data fails in bapi or call transaction then you have to correct them and rerun the whole things but in case of errors in session you will be able to store these sessions.. (But personally BAPI's are more effective and easy to use)
4) Types of BDC's
Session
Call Transaction
Recording
LSMW (Not really a BDC but a part of it)
Direct Input
.. More
Let me know if you have further questions (prabap@gmail.com).
BR
Rakesh
PS: Please close the thread if your question is answered..
‎2007 Mar 30 3:49 AM
Hi zareen,
1. views in MM01.
basic data1.
basic data 2. etc..
2. Usually functional guy will ive u the recording.
Check this documentation 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.
regards,
keerthi