BDC overview details step by step

Can any one give BDC overview details step by step.
thanks,
krishna

Hi
Check the Database tables of that Transaction, whether the correct number of records equal to your file were updated or not.
Process the Session in SM35 for the error records till all the records were completely uploaded into database.
see the BDC doc:
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.
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 ?
Reward points if useful
Regards
Anji

Similar Messages

BDC Step by Step Process

Hi Experts,
I'm new to BDC.
If you have any material which shows step by step process of BDC
with screen shots please forwards to the following mail id...
[email protected]
Kindly help me!!!!
I would be very grateful for your help..
thanks & regards,
shilpa

BDC or Batch Input Program Tips and Tricks
Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.
The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.
Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.
Learning BDC Programming
I want to learn how to upload data using BDC. If I have a excel data file how will upload it using BDC. I don't know the full process of doing it, if someone help me in this. I want it using BDC session process and processing that session. I was trying to upload material master other day. But could not follow the process of uploading using BDC though I know LSMW. Please explain me the BDC process in details with examples.
For a BDC upload you need to write a program which created BDC sessions.
Steps:
1. Work out the transaction you would use to create the data manually.
2. Use transaction SHDB to record the creation of one material master data.
Click the New recording button or the Menu - Recording - Create
3. Save the recording, and then go back a screen and go to the overview.
4. Select the recording and click on Edit - Create Program. Give the program a Z name, and select transfer from recording.
5. Edit the program. You will see that all the data you entered is hard-coded into the program. You need to make the following changes:
5.1 After the start-of-selection, Call ws_upload to upload the file (the excel file needs to be saved as TAB separated).
5.2 After the open-group, Loop on the uploaded data. For each line, perform validation checks on the data, then modify the perform bdc_field commands to use the file data.
5.3. After perform bdc_transaction, add the endloop.
Execute the program. It will have options to create a batch session or to process directly.
These are all my finds . Might be it will be useful to you.
Direct call of transactions, session handling:
/nxxxx This terminates the current transaction, and starts transaction xxxx
/n This terminates the transaction. This generally corresponds to pressing F15 to go back.
/nend This termiantes all separate sessions and logs off (corresponds to System - Logoff).
/nex This terminates all separate sessions and logs off immediately (without any warning!).
/oxxxx This opens a new session and starts transaction xxxx in This session.
/o This lists existing sessions and allows deletion or opening of a new session.
/i This terminates the current session (corresponds to System End
/i1, /i2,... This terminates the session with the number given.
.xyzw Fast path: 'xyzw' refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).
Batch
The following commands can be entered in correction mode ('Process in foreground' or 'Display errors only') when processing a batch input session:
/n This terminates the current batch input transaction and characterizes it as
/bdel This deletes the current batch input transaction.
/bend This terminates batch input processing and sets the session to Failed
/bda This switches from Display errors only to Process in foreground
/bde This switches from Process in foreground to Display errors only
ABAP/4
/h This switches into debugging mode.
/hs This switches into debugging mode and activates the debugging of system functions.
Buffer
WARNING: Resetting buffers can significantly change the performance of the entire system for a long time.
It should therefore only be used where there is a good reason tdso. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log.
/$SYNC This resets all buffers of the application server
/$CUA This resets the CUA buffer of the application server
/$TAB This resets the TABLE buffers of the application server
/$NAM This resets the nametab buffer of the application server
/$DYNP This resets the screen buffer of the application server
and also see these following links.
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.sap-img.com/abap/learning-bdc-
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Regards.

BDC step-by-step

Hi Experts,
I am new to R/3 can any one explain the BDC in detail step-by-step.
You have any detail documents related to this topic pls send it to this mail id
[email protected]
Regards
Krishna.

Hi,
Go thru this doc.
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 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.
AN EXAMPLE WITH SESSION METHOD
Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
The transaction is TFBA (to change customer).
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.
Flat file can be created in your hard disk as follows:
1     Vinod Krishna     Hyderabad
2     Kavitha     Secunderabad
3     Kishore     Hyderabad
(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
To transfer this data to database table SCUSTOM following interface can be used.
REPORT DEMO1.
Following internal table is to upload flat file.
DATA: BEGIN OF ITAB OCCURS 0,
               ID(10),
               NAME(25),
               CITY(25),
             END OF ITAB.
*Following internal table BDCDATA is to pass date from internal table to session.
DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
Variables
DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME                    = C:\FF.TXT
FILE TYPE                    = ASC
TABLES
DATA_TAB                    = ITAB
EXCEPTIONS
CONVERSION_ERROR          = 1
INVALID_TABLE_WIDTH          = 2
INVALID_TYPE               = 3
NO_BATCH                    = 4
UNKNOWN_ERROR          = 5
OTHERS                    = 6.
If sy-subrc = 0.
Calling Function to Create a Session
CALL FUNCTION BDC_OPEN_GROUP
EXPORTING
CLIENT                    = SY-MANDT
GROUP                    = POTHURI
HOLDDATE                    = DATE1
KEEP                         = X
USER                         = SY-UNAME
EXCEPTIONS
CLIENT_INVALID               = 1
DESTINATION_INVALID          = 2
GROUP_INVALID               = 3
GROUP_IS_LOCKED          = 4
HOLDDATE_INVALID          = 5
INTERNAL_ERROR               = 6
QUEUE_ERROR               = 7
RUNNING                    = 8
SYSTEM_LOCK_ERROR          = 9
USER_INVALID               = 10
OTHERS                    = 11.
If sy-subrc = 0.
*-- MAIN Logic--
LOOP AT ITAB
PERFORM GENERATE_DATA. Populating BDCDATA Table
CALL FUNCTION BDC_INSERT
     EXPORTING
TCODE               = TFBA
TABLES
DYNPROTAB          = BDCTAB
EXCEPTIONS
INTERNAL_ERROR          = 1
NOT_OPEN               = 2
QUEUE_ERROR          = 3
TCODE_INVALID          = 4
PRINTING_INVALID     = 5
POSTING_INVALID     = 6
OTHERS               = 7.
REFRESH BDCTAB
ENDLOOP.
Calling function to close the session
CALL FUNCTION BDC_CLOSE_GROUP
EXCEPTIONS
NOT_OPEN          = 1
QUEUE_ERROR     = 2
OTHERS          = 3.
Endif.
Endif.
*& Form GENERATE_DATA
   Create BDC Data
FORM GENERATE_DATA
Passing information for 1st screen on BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = X.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = SCUSTOM-ID
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = /5.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = SAPMTFBA.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = X.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-NAME.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = SCUSTOM-CITY.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = BDC_OKCODE.
BDCTAB-FVAL = SAVE.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM.                              GENERATE_DATA
AN EXAMPLE WITH CALL TRANSACTION
Same steps to be repeated for CALL TRANSACTION
The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
REPORT DEMO1.
Follow above Code till MAIN Logic. Even the Subroutine should be copied
LOOP AT ITAB
PERFORM GENERATE_DATA, Populating BDCDATA Table
Call transaction TFBA using BCDDATA Mode A Update S.
REFRESH BDCTAB
ENDLOOP.
Thanks
Sunil

LSMW, ALE, BCD step by step details

can any one give the details of LSMW, ALE, BCD - forum to discuss various Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs
Regards & thanks,
k.s.krishna

Hi,
LSMW
http://www.sap-img.com/sap-data-migration.htm
/people/hema.rao/blog/2006/09/14/lsmw--step-by-step
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/dataTransfers-LSMW,ALE,+BDC&
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/lsmw&
http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
http://myweb.dal.ca/hchinni/sap/lsmw_home.htm
http://esnips.com/doc/8e732760-5548-44cc-a0bb-5982c9424f17/lsmw_sp.ppt
http://esnips.com/doc/f55fef40-fb82-4e89-9000-88316699c323/Data-Transfer-Using-LSMW.zip
http://esnips.com/doc/1cd73c19-4263-42a4-9d6f-ac5487b0ebcb/LSMW-with-Idocs.ppt
http://esnips.com/doc/ef04c89f-f3a2-473c-beee-6db5bb3dbb0e/LSMW-with-BAPI.ppt
http://esnips.com/doc/7582d072-6663-4388-803b-4b2b94d7f85e/LSMW.pdf
http://****************/Tutorials/LSMW/LSMWMainPage.htm
**********Check the following link:
http://www.sapbrain.com/TOOLS/LSMW/SAP_LSMW_steps_introduction.html
BDC............Creation..........
http://help.sap.com/saphelp_erp2005/helpdata/en/fa/097119543b11d1898e0000e8322d00/frameset.htm
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
Please refer to the details mentioned in the hyper-links beow.
You will get the details how to go about it.
To see the IDOC & status check it in WE02/WE05
You will get step by step process.
ABAP Development
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.geocities.com/xplosion78/customised_ALE_IDOC_BY_SACHIN_DABHADE.zip
http://help.sap.com/saphelp_45b/helpdata/en/35/b0ea5187a62488e10000009b38f9b7/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/c4/6bc368fef411d28d0900104b56737d/frameset.htm
ABAP Development
Follow below steps to create custom IDOC.
1.Create segments through transaction WE31.
2.Create IDoc Type through transaction WE30 by attaching created segments.
3.Message type through transaction WE81.
4.Link Idoc and message type in WE82 transaction.
Check the transaction WEDI for ALE settings
Check these links for more details on IDoc's:
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.intelligententerprise.com/channels/applications/feature/archive/kasturi.jhtml
Hope this will help.
Regards,
Priyanka.

HT4972 I have an Ipod touch version 4.2.1 and the instructions do not detail how to update to iOS 5. Can you help with me step by step instructions.

I have an Ipod touch version 4.2.1 and the instructions do not detail how to update to iOS 5. Can you help me with step by step instructions.

iOS 4.2.1 suggests that you may have 2nd generation Touch, which cannot be updated past iOS 4.2.1
Check http://support.apple.com/kb/HT1353 for help in identifying your model. A quicker method may be to check the back casing. If your iPod has Model No.A 1288 etched into it, then it's a 2nd gen Touch.
Assuming that you are using the latest version of iTunes (today, that is 10.6.3), to check if your iPod can be updated, connect it to your iTunes and look on the Device/Summary pane. Select Check for Updates. If there is one, you will see a message telling you that and how to install it. However, if you see a message saying that your iPod is up-to-date, then it cannot be updated.

ABAP/4 u0096 Step by Step Main Concept details

can any one give the details of ABAP/4 Step by Step Main Concept details and Links.

Hi
Start with this.Refer this
http://www.sapbrain.com/FAQs/TECHNICAL/SAP_ABAP_DATADICTIONARY_FAQ.html
http://www.****************/InterviewQ/interviewQ.htm
http://help.sap.com/saphelp_46c/helpdata/en/35/2cd77bd7705394e10000009b387c12/frameset.htm
Reports
http://www.sapgenie.com/abap/reports.htm
http://www.allsaplinks.com/material.html
http://www.sapdevelopment.co.uk/reporting/reportinghome.htm
http://www.sapfans.com/forums/viewtopic.php?t=58286
http://www.sapfans.com/forums/viewtopic.php?t=76490
http://www.sapfans.com/forums/viewtopic.php?t=20591
http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
Check these step-by-step links
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
for Smartforms material
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
http://www.sap-img.com/smartforms/smartform-tutorial.htm
http://www.sapgenie.com/abap/smartforms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
http://www.sap-img.com/smartforms/smart-006.htm
http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
Re: Need FAQ's
check most imp link
http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
step by step good ex link is....
http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
SAPScripts
http://esnips.com/doc/1ff9f8e8-0a4c-42a7-8819-6e3ff9e7ab44/sapscripts.pdf
http://esnips.com/doc/1e487f0c-8009-4ae1-9f9c-c07bd953dbfa/script-command.pdf
http://esnips.com/doc/64d4eccb-e09b-48e1-9be9-e2818d73f074/faqss.pdf
http://esnips.com/doc/cb7e39b4-3161-437f-bfc6-21e6a50e1b39/sscript.pdf
http://esnips.com/doc/fced4d36-ba52-4df9-ab35-b3d194830bbf/symbols-in-scripts.pdf
http://esnips.com/doc/b57e8989-ccf0-40d0-8992-8183be831030/sapscript-how-to-calculate-totals-and-subtotals.htm
SAP SCRIPT FIELDS
http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/8033ea454211d189710000e8322d00/content.htm
scripts easy material
http://www.allsaplinks.com/sap_script_made_easy.html
Debugging Document.
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
Reward points if useful
Regards
Anji

Step by Step details on how to load data from a flat file

hi can anyone explain how to load data from a flat file. Pls giv me step by step details. thnx

hi sonam.
it is very easy to load data from flat file. whn compared with other extrations methods...
here r the step to load transation data from a flat file.......
step:1 create a Flat File.
step:2 log on to sap bw (t.code : rsa1 or rsa13).
and observe the flat file source system icon. i.e pc icon.
step:3 create required info objects.
3.1: create infoarea
     (infoObjects Under Modeling > infoObjects (root node)-> context menu -
> create infoarea).
3.2: create char /keyfig infoObject Catalog.(select infoArea ---.context menu --->create infoObject catalog).
3.3:   create char.. infoObj and keyFig infoObjects accourding to ur requirement and activate them.
step:4 create infoSource for transaction data and create transfer structure and maintain communication structure...
    4.1: first create a application component.(select InfoSources Under modeling-->infosources<root node>>context menu-->create applic...component)
   4.2: create infoSource for transation data(select appl..comp--.context menu-->create infosource)
>select O flexible update and give info source name..
>continue..
4.4: *IMp* ASSIGN DATASOURCE..
(EXPAND APPLIC ..COMP..>EXPAND YOUR INFOSOURCE>CONTEXT MENU>ASSIGN DATASOURCE.)
>* DATASOURCE *
>O SOURCE SYSTEM: <BROWSE AND CHOOSE YOUR FLAT FILE SOURCE SYSTEM>.(EX:PC ICON).
>CONTINUE.
4.5: DEFINE DATASOURCE/TRANSFER STRUCTURE FOR IN FOSOURCE..
> SELECT TRANSFER STRUCTURE TAB.
>FILL THE INFOOBJECT FILLED WITH THE NECESSARY INFOOBJ IN THE ORDER OR SEQUENCE OF FLAT FILE STRUCTURE.
4.6: ASSIGN TRANSFER RULES.
---> NOW SELECT TRANSFER RULES TAB. AND SELECT PROPOSE TRANSFER RULES SPINDLE LIKE ICON.
(IF DATA TARGET IS ODS -
INCLUDE 0RECORDMODE IN COMMUNICATION STRUCTURE.)
--->ACTIVATE...
STEP:5 CREATE DATATARGET.(INFOCUBE/ODS OBJECT).
5.1: CREATE INFO CUBE.
-->SELECT YOUR INFOAREA>CONTEXT MENU>CREATE INFOCUBE.
5.2: CREATE INFOCUBE STRUCTURE.
---> FILL THE STRUCTURE PANE WILL REQUIRE INFOOBJECTS...(SELECT INFOSOURCE ICON>FIND UR INFOSOURCE >DOUBLE CLICK > SELECT "YES" FOR INFOOBJECT ASSIGNMENT ).
>MAINTAIN ATLEAST ON TIME CHAR.......(EX; 0CALDAY).
5.3:DEFINE AND ASSIGN DIMENSIONS FOR YOUR CHARACTERISTICS..
>ACTIVATE..
STEP:6 CREATE UPDATE RULES FOR INFOCUDE USING INFOSOURCE .
>SELECT UR INFOCUBE >CONTEXT MENU> CREATE UPDATE RULES.
> DATASOURCE
> O INFOSOURCE : _________(U R INFOSOURCE). AND PRESS ENTER KEY.......
>ACTIVATE.....UR UPDATE RULES....
>>>>SEE THE DATA FLOW <<<<<<<<----
STEP:7 SCHEDULE / LOAD DATA..
7.1 CREATE INFOPACKAGE.
--->SELECT INFOSOURCE UNDER MODELING> EXPAND UR APPLIC.. COMP..> EXPAND UR INFOSOURCE..> SELECT UR DATASOURCE ASSIGN MENT ICON....>CONTEXT MENU> CREAE INFOPACKAGE..
>GIVE INFOPACKAGE DISCREPTION............_________
>SELECT YOUR DATA SOURCE.-------> AND PRESS CONTINUE .....
>SELECT EXTERNAL DATA TAB...
> SELECT *CLIENT WORKSTATION oR APPLI SERVER >GIVE FILE NAME > FILE TYPE> DATA SAPARATER>
>SELECT PROCESSING TAB
> PSA AND THEN INTO DATATARGETS....
>DATATARGET TAB.
>O SELECT DATA TARGETS
[ ] UPDATE DATATARGET CHECK BOX.....
--->UPDATE TAB.
O FULL UPDATE...
>SCHEDULE TAB..
>SELECT O START DATA LOAD IMMEDIATELY...
AND SELECT "START" BUTTON........
>>>>>>>>>>
STEP:8 MONITOR DATA
> CHECK DATA IN PSA
CHECK DATA IN DATA TARGETS.....
>>>>>>>>>>> <<<<<<<<<----
I HOPE THIS LL HELP YOU.....

Need detailed step by step procedure to hire an employee

Hi all,
can anyone give me the detailed step by step procedure to hire an employee?
Thanks
pabi

Before you hire try to configure infogroups and actions check all the integrations in T77s0
and go to PA40 and click on Hiring action and execute

Step-by-step BDC upload

can u send me the step by step process for a BDC program
i had given a excel sheet with field names and length .....that is to be uploaded
it is material master(MM01)
thanks in advance

Hi,
for the bdc upload
step1. go to the Transaction SHDb and create a new recording for the transaction MM01 and save the recording.
step 2: from the same transaction select the recording and go the program.
Note: if you have ur file in presentation server insted of open dataset use gui_upload.
make the needed necessary changes in the coding.
i've attached the sample coding, keep that as reference and do according to your need.
REPORT zmm01_bdc
       NO STANDARD PAGE HEADING LINE-SIZE 255.
INCLUDE bdcrecx1.
DATA: dataset(132) TYPE c.
   DO NOT CHANGE - the generated data section - DO NOT CHANGE    ***
If it is nessesary to change the data section use the rules:
1.) Each definition of a field exists of two lines
2.) The first line shows exactly the comment
      '* data element: ' followed with the data element
      which describes the field.
      If you don't have a data element use the
      comment without a data element name
3.) The second line shows the fieldname of the
      structure, the fieldname must consist of
      a fieldname and optional the character '_' and
      three numbers and the field length in brackets
4.) Each field must be type C.
Generated data section with specific formatting - DO NOT CHANGE ***
DATA: BEGIN OF record,
data element: MATNR
        matnr_001(018),
data element: MBRSH
        mbrsh_002(001),
data element: MTART
        mtart_003(004),
data element: XFELD
        kzsel_01_004(001),
data element: XFELD
        kzsel_02_005(001),
data element: MATNR
        matnr_006(018),
data element: MBRSH
        mbrsh_007(001),
data element: MTART
        mtart_008(004),
data element: XFELD
        kzsel_01_009(001),
data element: XFELD
        kzsel_02_010(001),
data element: MAKTX
        maktx_011(040),
data element: MEINS
        meins_012(003),
data element: MATKL
        matkl_013(009),
data element: MTPOS_MARA
        mtpos_mara_014(004),
data element: MAKTX
        maktx_015(040),
      END OF record.
DATA l_lines TYPE i .
DATA it_record LIKE TABLE OF record WITH HEADER LINE .
DATA wa_record LIKE record .
End generated data section ***
START-OF-SELECTION.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                      ='C:\MM01_FILE.TXT'
     filetype                      = 'ASC'
     has_field_separator           = '#'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
    TABLES
      data_tab                      = it_record
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
PERFORM open_dataset USING dataset.
PERFORM open_group.
DO.
    READ DATASET dataset INTO record.
    IF sy-subrc <> 0. EXIT. ENDIF.
    LOOP AT it_record INTO wa_record.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '0060'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'RMMG1-MTART'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'RMMG1-MATNR'
                                    record-matnr_001.
      PERFORM bdc_field       USING 'RMMG1-MBRSH'
                                    record-mbrsh_002.
      PERFORM bdc_field       USING 'RMMG1-MTART'
                                    record-mtart_003.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'MSICHTAUSW-DYTXT(02)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=ENTR'.
      PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(01)'
                                    record-kzsel_01_004.
      PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(02)'
                                    record-kzsel_02_005.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '0060'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'RMMG1-MATNR'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'RMMG1-MATNR'
                                    record-matnr_006.
      PERFORM bdc_field       USING 'RMMG1-MBRSH'
                                    record-mbrsh_007.
      PERFORM bdc_field       USING 'RMMG1-MTART'
                                    record-mtart_008.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '0070'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'MSICHTAUSW-DYTXT(02)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=ENTR'.
      PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(01)'
                                    record-kzsel_01_009.
      PERFORM bdc_field       USING 'MSICHTAUSW-KZSEL(02)'
                                    record-kzsel_02_010.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'MAKT-MAKTX'
                                    record-maktx_011.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'MARA-MATKL'.
      PERFORM bdc_field       USING 'MARA-MEINS'
                                    record-meins_012.
      PERFORM bdc_field       USING 'MARA-MATKL'
                                    record-matkl_013.
      PERFORM bdc_field       USING 'MARA-MTPOS_MARA'
                                    record-mtpos_mara_014.
      PERFORM bdc_dynpro      USING 'SAPLMGMM' '4004'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '/00'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'MAKT-MAKTX'.
      PERFORM bdc_field       USING 'MAKT-MAKTX'
                                    record-maktx_015.
      PERFORM bdc_dynpro      USING 'SAPLSPO1' '0300'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=YES'.
      PERFORM bdc_transaction USING 'MM01'.
ENDDO.
PERFORM close_group.
PERFORM close_dataset USING dataset.

Detailed step-by-step technicals - INFOPACK & PC

Hi SDNers,
*POINTS GURANTEED
I am working with process chains in my proj. Theres an ODS - ZODSA, for which no load is scheduled for the past few months. Now it is needed to load this infopack & that too creating a PC for this & attaching it to the main PC.
Could you pls give me a detailed step-by-step technicals in carrying out the following?
1) Migrate existing infopackage for ZODSA from dev to quality
2) (LEG) create new subchain to execute, then activate this load - start condition should be immediate, no server name
3) Attach this new chain to Z_TRANS_ALL, after the master data loads, in parallel with ZSALES_PC in dev and test
4) Migrate and test PC changes,
5) Migrate IP and chain to Production and schedule chain for daily full load.
POINTS GURANTEED

1) Migrate existing infopackage from dev to quality.
RSA1 - Transport Connection - Grouping - Only Necessary - Collection - Manual
Infopackages - Search for the Infopackage - Transfer Selection - Package - Select - Assign Transportable Package - Assign Request.
2) In dev, a new subchain is to be created to execute, then activate this load - start condition should be immediate
How to keep the start variant as changable in Qual?
Usually, start variants will be open in Qual for changing scheduling timings or others.
3) In dev, Attach this new chain to the main chain
If you know where to add the new chain to the main chain - RSPC - Edit Mode - Processing Types - Local Chain - Read the new chain - Connect to pre and succesor - Activate
In the start variant of this local chain - Select " Start Using API........."
4) Then to transport BOTH THE CHAINS from Dev to Qual and test there also
Click on the truck icon from RSPC itself and foll above steps.
You can just select process types and infoapackages if all others have already been transported.
Pls give me a detailed transport steps.
5) Finally the infopackage + BOTH THE CHAINS are to be moved to prodn, right?
Yes

Step by step details to deploy jsp in weblogic

Hi,
can any one give me a step by step details to deploy jsp in weblogic 7..
i am abs new to EJBs and weblogic...
thnx
sai.

sai krishna wrote:
Hi,
can any one give me a step by step details to deploy jsp in weblogic 7..
i am abs new to EJBs and weblogic...
thnx
sai.Sai if you are completely new to this on WLS I would recommend reading:
http://edocs.bea.com/wls/docs70/programming/index.html
Then Possibly:
http://edocs.bea.com/wls/docs70/webapp/index.html &&
http://edocs.bea.com/wls/docs70/jsp/index.html
You can also find more programming information here:
http://edocs.bea.com/wls/docs70/programming.html
HTH
~Ryan

Need step by step in details about upgrade 11.5.3 to 12.1.1

Hi every one !
i' m trying to upgrade our ebs 11i from 11.5.3 on win NT4 To R12.1.1 on RHEL Linux 5.5 with another hardware. so can any one help me to get what i need in details with step by step instructions .
and what patchs must be downloaded. and any thing else do i need for this purpose .
i appreciate your help.
we're on :
ebs 11.5.3 with DB 8.1.6 On Win NT4 , Tow Nodes .
going to :
ebs 12.1.1 with DB 11g on RHEL Linux 5.5 , Tow Nodes.
thanks
Hani
Edited by: user2987179 on Feb 5, 2012 2:58 AM

Please see old threads for similar dicussion -- https://forums.oracle.com/forums/search.jspa?threadID=&q=Upgrade+11i+to+R12&objID=c3&dateRange=all&userID=&numResults=15&rankBy=10001
Thanks,
Hussein

Request for Step by step procedure to create SRM User in detail

Hi All,
Could you please provide Step by step procedure to create SRM User in detail.
I have completed the following:
1. I created SU01 User.
2. I created Root Organistaion with PPOCA_BBP.
3. I went into PPOMA_BBP Tr. code and added Organisation structure like Root Organisation -> Organisation for Company Code -> Organisation for Pur Org -> Organisation fro Pur Group -> Position.
4. I got struck at assigning BusinessPartner for each organisation and creating Cntral Person
Plase provide further steps to copmplete SRM USer creation.
Thanks in advance,
Regards,
Siva

Hi
Are you using USERS_GEN transaction in SRM to create users ? Please read the SAP documentation in this case associated with the transaction using SRM GUI logon..
Which option do you use in USERS_GEN : file upload ?
In your case where the "US" (User) link is missing: is the SU01 user created ? Wasn't is already created before USERS_GEN ?
If the system is not able to create the CP <-> US relation, you should get back an error message in USERS_GEN.
Please go through the related very helpful pointers ->
Central Person
Re: Error while assigning user to a position
Re: How to assign contact person user id to Vendor uploaded from ECC?
Re: Central Person already exists
Re: Correct relationships not being created from USERS_GEN
Business Partner(BP) and Central Person(CP) distribution
Contact person of vendors created inconsistently in my organizative structu
Please revert in the event of any query.
Regards
- Atul

Step by step BDC using session method

hello experts,
im loking for BDC by session method, but i couldnt find any tutorial on BDC- session method.
can anyone suggest any link ot tutorial wher i can find step by step tutorial on bdc by session method.
your suggestion will help me lot,
thank you,
regards,
nikhil

Hi Nikhil,
This is the basic program to learn BDC session .Run this program and change the file path.
Make a recording for MM01 In T-Code SHDB for creating material.
*& Report ZBDC_SESSION
REPORT ZBDC_SESSION no standard page heading line-size 255.
DATA : BEGIN OF BDC OCCURS 100 ,
        MBRSH TYPE RMMG1-MBRSH,
        MTART TYPE RMMG1-MTART,
        MAKTX TYPE MAKT-MAKTX,
        MEINS TYPE MARA-MEINS,
        END OF BDC.
       ITAB LIKE TABLE OF BDC WITH HEADER LINE,
       DATA : BDCDATA LIKE TABLE OF BDCDATA WITH HEADER LINE.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
    FILENAME                      ='D:\MM01.TXT'
   FILETYPE                      = 'ASC'
   HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
VIRUS_SCAN_PROFILE            =
NO_AUTH_CHECK                 = ' '
IMPORTING
FILELENGTH                    =
HEADER                        =
TABLES
    DATA_TAB                      = BDC
EXCEPTIONS
FILE_OPEN_ERROR               = 1
FILE_READ_ERROR               = 2
NO_BATCH                      = 3
GUI_REFUSE_FILETRANSFER       = 4
INVALID_TYPE                  = 5
NO_AUTHORITY                  = 6
UNKNOWN_ERROR                 = 7
BAD_DATA_FORMAT               = 8
HEADER_NOT_ALLOWED            = 9
SEPARATOR_NOT_ALLOWED         = 10
HEADER_TOO_LONG               = 11
UNKNOWN_DP_ERROR              = 12
ACCESS_DENIED                 = 13
DP_OUT_OF_MEMORY              = 14
DISK_FULL                     = 15
DP_TIMEOUT                    = 16
OTHERS                        = 17
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'BDC_OPEN_GROUP'
EXPORTING
   CLIENT                    = SY-MANDT
DEST                      = FILLER8
   GROUP                     = 'ZAK'
HOLDDATE                  = FILLER8
   KEEP                      = 'X'
   USER                      = SY-UNAME
RECORD                    = FILLER1
PROG                      = SY-CPROG
DCPFM                     = '%'
DATFM                     = '%'
IMPORTING
QID                       =
EXCEPTIONS
CLIENT_INVALID            = 1
DESTINATION_INVALID       = 2
GROUP_INVALID             = 3
GROUP_IS_LOCKED           = 4
HOLDDATE_INVALID          = 5
INTERNAL_ERROR            = 6
QUEUE_ERROR               = 7
RUNNING                   = 8
SYSTEM_LOCK_ERROR         = 9
USER_INVALID              = 10
OTHERS                    = 11
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*include bdcrecx1.
*start-of-selection.
*perform open_group.
LOOP AT BDC.
CLEAR BDCDATA[].
REFRESH BDCDATA[].
perform bdc_dynpro      using 'SAPLMGMM' '0060'.
perform bdc_field       using 'BDC_CURSOR'
                              'RMMG1-MTART'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
*perform bdc_field       using 'RMMG1-MATNR'
                             'ZRAW001'.
perform bdc_field       using 'RMMG1-MBRSH'
                             'M'.
BDC-MBRSH.
perform bdc_field       using 'RMMG1-MTART'
                             'FERT'.
BDC-MTART.
perform bdc_dynpro      using 'SAPLMGMM' '0070'.
perform bdc_field       using 'BDC_CURSOR'
                              'MSICHTAUSW-DYTXT(01)'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTR'.
perform bdc_field       using 'MSICHTAUSW-KZSEL(01)'
                              'X'.
perform bdc_dynpro      using 'SAPLMGMM' '4004'.
perform bdc_field       using 'BDC_OKCODE'
                              '/00'.
perform bdc_field       using 'MAKT-MAKTX'
                             'NUT'.
BDC-MAKTX.
perform bdc_field       using 'BDC_CURSOR'
                              'MARA-MEINS'.
perform bdc_field       using 'MARA-MEINS'
                             'PC'.
BDC-MEINS.
perform bdc_field       using 'MARA-MTPOS_MARA'
                              'NORM'.
perform bdc_dynpro      using 'SAPLSPO1' '0300'.
perform bdc_field       using 'BDC_OKCODE'
                              '=YES'.
*perform bdc_transaction using 'MM01'.
*perform close_group.
CALL FUNCTION 'BDC_INSERT'
EXPORTING
   TCODE                  = 'MM01'
POST_LOCAL             = NOVBLOCAL
PRINTING               = NOPRINT
SIMUBATCH              = ' '
CTUPARAMS              = ' '
TABLES
    DYNPROTAB              = BDCDATA
EXCEPTIONS
INTERNAL_ERROR         = 1
NOT_OPEN               = 2
QUEUE_ERROR            = 3
TCODE_INVALID          = 4
PRINTING_INVALID       = 5
POSTING_INVALID        = 6
OTHERS                 = 7
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
CALL FUNCTION 'BDC_CLOSE_GROUP'
EXCEPTIONS
NOT_OPEN          = 1
QUEUE_ERROR       = 2
OTHERS            = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
       Start new screen                                              *
FORM BDC_DYNPRO USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
ENDFORM.
       Insert field                                                  *
FORM BDC_FIELD USING FNAM FVAL.
IF FVAL IS NOT INITIAL.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
ENDIF.
ENDFORM.

Step by Step Guide Details for RFC to File and File to RFC scenario

Hi Guru's
Good day to you. I am tyring to develop some scenarios based on RFC adaptor. so i want to start up with basic scenarios like RFC to File scenario(Here i just want to pull some data from SAP using RFC and put it in destination folder as an text file) and FILE to RFC scenario (Here i just want to take some data from the file and update into SAP).
For doing these scenarios i would like to request you people to send me the step by step guide which explains me about the complete steps of configurations required to do the RFC to FILE scenario and FILE to RFC scenario.
I found some scenarios and i am in confused state. so i request you to please put your experience to help me out.
thanks in advance.
Regards
Raj

Hi Aaron,
I don't know your scenario and your ECC and PI versions but I learned how to use ABAP Proxy more than 1 year ago with the following tutorial:
Edit--> The forum doesn't allow me to post external link, just search "ABAP Proxy Communication Scenario" in google and visit the 1st result
The way to develop ABAP Proxys has changed a little if your PI is 7.1. In the ECC side, the transaction SPROXY looks much better too if you have a recent version of the ECC.
Edited by: Marshal on Oct 8, 2009 5:08 PM
I've found that SDN Document. Maybe the scenario is not the most simple to start with ABAP Proxy but is very well documented and is for PI 7.1. The document also handles the inbound and outbound proxys
[http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c00ca32e-f991-2b10-f5be-97114bd2b08f&overridelayout=true]
Edited by: Marshal on Oct 8, 2009 5:22 PM

BDC overview details step by step

Similar Messages

Maybe you are looking for