Steps for BDC before program

Can anyone just tell me the steps which one follows before going for a BDC Program. i mean right frm the starting if any Company want to implement SAP.

HI,
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.
Regards
Sudheer
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

Similar Messages

Steps For Creating Module programming ?

hi..
if u have any documentation for creating module programming means please send to me .
Thanks in advance
Deepa

Hi,
Go through This Link:--[http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm]
[http://abaplovers.blogspot.com/2008/03/sap-abap-module-pool-programming.html]
[http://abaplovers.blogspot.com/2008/03/sap-abap-tutorial-module-pool.html]
[http://abaplovers.blogspot.com/2008/03/sap-abap-tutorial-module-pool_17.html]
Regards
Sandipan

Steps for debugging the ABAP program

Hi
Im a SAP-BW Consultant. I have a program in R/3-Side. I want to debugg that program.
Please give me the steps for debugging that program .
Kumar

Hi Ravi,
Check this link
http://help.sap.com/saphelp_nw2004s/helpdata/en/b3/d322540c3beb4ba53795784eebb680/content.htm
I give you some usefull Tips.
Type /h in command Bar.
Then press F8 then system will automatically goes to debugging mode.
Then press F5. Then it shows the Each and every line of your program.
or type break-point in your SE38 program. Then press F8. it will goes to the Debugging mode.
Thanks.
Reward If Helpful.
Message was edited by:
Viji

Adding steps for a background job

Hello All,
I am creating a background job through a program and submitting another program for running in the background.
I would like to add steps for the backgound job which I created trough my program.
So background job will have different steps for the same program which I submitted.
Could any one of you help me on how to add steps for background job which is already running.
Thanks and Regards,
Vijay

Hi Naimesh,
Thanks for the Reply.
Sorry for replying late.
The problem I am facing is we need only one job with multiple step .
for example if we have job named BCKGRD.
Under this job we need to create Step 1, Step 2, Step 3..
Regards,
Vijay

Creating a Step for Background Job from within ABAP Program

Step-1: I have a Report in ECC, which is scheduled as Background Job, which writes the file to the Application Server(UNIX)
Step-2: Trigger a Unix Command to ftp the file to other server.
Both Step-1 & Step-2 can be done from SM36.
Another Scenario:
Users can run the report in background from SE38 or using the transaction code for the report, In this case we want to call the external command.
Instead of calling the External Command as below in the report, I want to create a Step from within the program when it is scheduled in background mode.
CALL 'SYSTEM' ID 'COMMAND' FIELD lc_unixcom. [ Here lc_unixcom has the External Command ].
Any ideas??? Appreciate help.

Hi,
For submitting a report step, you may use either SUBMIT ... VIA JOB ... or JOB_SUBMIT function module.
For external commands, this should be done only by calling JOB_SUBMIT function module.
Sandra

It's one small step for mankind, but one giant leap for me (DSP program)

Hi guys,I don´t know if it is a off-topic here or if someone is interested.
I was developing a DSP program i Java. All I told that I was developing this software
said it was impossible. The JVM is very heavy, is an interpreted language etc. But it is working
and with a good performance. Is a SDR (software defined radio) software, it is not finished but if anybody
want to see some documentation, give me a few days and look for it at
http:\\gvillamayor.angelfire.com
If anyone is interested mail me [email protected]

I have uploaded some details about the solution and how to integrate it into your own application.
http://inside-apex.blogspot.com/2007/01/one-small-step-for-man-one-giant-leap.html
As I have written in the blog posting, I'm really new to JavaScript, just started 1 1/2 month ago and I'm currently on page 351 (total 994) of the JavaScript - The Definitive Guilde. So if you look at my code and think, man are you crazy, why you write that much code to do that, it's a simple regular expression and you are done! Please let me know!
The JavaScript stuff was more work as I thought (especially if it should work with Firefox and IE), you really appreciate the build in TO_DATE and TO_NUMBER and it's flexibility when you have to implement that by yourself. :-)
At least I haven't found a JavaScript validation toolbox which is compatible with the format mask settings of Oracle.
Call for testing:
-) I want know if the format mask checks I implemented work for all the combinations out there. The weird American ones with AM/PM and the month at be beginning should also work ;-)
-) If the inline error display also works with other themes and userdefined label templates.
So please plug it into your application and do a test drive of the new Ferrari! ;-)
Thanks a lot
Patrick
Check out my APEX-blog: http://inside-apex.blogspot.com

Restore old PowerBook G4 before/for Apple Recycle Program.

I have an old PowerBook G4 I need to send to Apple for its recycling program. But it's still got all of my stuff inside it I've just transferred it to my new MacBook. I need to wipe everything out before I can send it like erase the disk and restore its orginal settings. I know I should own the Lion dvd to be able to do this BUT thing is I have NO cd/dvd in the box. There's everything else as I purchased my MacBook in an Apple Store BUT there is NO such thing as a cd/dvd. Can I do the process in some other way or am I forced to bring the old computer to an Apple Store? Thank you.

You can hook up your Powerbook in target disk mode to your MacBook Pro, and erase the hard drive from there. You'll need a firewire cable to attach the two systems. Boot the Powerbook while holding the T key down. A firewire symbol will be moving around the screen, hook up the firewire cable between the two system, and your Powerbook will now appear as another disk drive to your MBP. Bring up Disk Utility on the MBP and erase the Powerbook hard drive, recommend a secure erase which writes zero's to the hard drive. If it's going to be recycled, I don't know why you need do anything else but clear the hard drive.

Please provide me material for bdc

Hi everyone,
can you please provide me some stuff for bdc, actually i am working on bdc for mm01 , so plz send me study materials and if you have any scenario then please forward me.
Thanks & Regards,
Vimarsh B.

Hi
Hope it will help you.
Reward if help.
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:
u2022 The first is when application data to be replaced is transferred at once, and only once.
u2022 The second situation is to transfer data periodically from external systems to SAP and vice versa.
u2022 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 u201Cbatch inputu201D or u201Cbatch data communicationu201D.
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 u201Cdata transferu201D 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:
u2022 To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
u2022 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:
u2022 The transaction code, if you do not already know it.
u2022 Which fields require input i.e., mandatory.
u2022 Which fields can you allow to default to standard values.
u2022 The names, types, and lengths of the fields that are used by a transaction.
u2022 Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
u2022 Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System u2013 Status.)
u2022 Step through the transaction, entering the data will be required for processing your batch input data.
u2022 On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
u2022 Display these by choosing System u2013 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.
u2022 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 youu2019ll 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.
u2022 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:
u2022 Create a BDCDATA structure
u2022 Write the structure out to a session or process it with CALL TRANSACTION USING; and then
u2022 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:
u2022 Data that is entered into screen fields.
u2022 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:
u2022 PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
u2022 DYNPRO: Screen Number. Set this field only in the first record for the screen.
u2022 DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to u2018 u2018 (blank) for all other records.)
u2022 FNAM: Field Name. The FNAM field is not case-sensitive.
u2022 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:
u2022 User Name: User name
u2022 Group: Name of the session
u2022 Lock Date: The date on which you want to process the session.
u2022 Keep: This parameter is passed as u2018Xu2019 when you want to retain session after
processing it or u2018 u2018 to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
u2022 Tcode: Transaction Name
u2022 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 u2013 1 is transaction code.
Parameter u2013 2 is name of BDCTAB table.
Parameter u2013 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 u2013 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 u2013 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.
u2022 Click Get Transaction.
u2022 Return to BI.
u2022 Click overview.
u2022 Position the cursor on the just recorded entry and click generate program.
u2022 Enter program name.
u2022 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.
u2022 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.
u2022 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.
u2022 Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
u2022 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.
u2022 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 donu2019t 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 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. u201C This is for Hold Date
To upload flat file to internal table.
CALL FUNCTION UPLOAD
EXPORTING
FILE NAME = u2018C:\FF.TXTu2019
FILE TYPE = u2018ASCu201D
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 u2018BDC_OPEN_GROUPu2019
EXPORTING
CLIENT = SY-MANDT
GROUP = u2018POTHURIu2019
HOLDDATE = DATE1
KEEP = u2018Xu2019
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. u201C Populating BDCDATA Table
CALL FUNCTION u2018BDC_INSERTu2019
EXPORTING
TCODE = u2018TFBAu2019
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 u2018BDC_CLOSE_GROUPu2019
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 = u2018SAPMTFBAu2019.
BDCTAX-DYNPRO = 100.
BDCTAP-DYNBEGIN = u2018Xu2019.
APPEND BCDTAB.CLEAR BDCTAB.
Passing field information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-IDu2019
BDCTAB-FVAL = ITAB-ID.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018/5u2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information for next screen to BDCDATA
BDCTAB-PROGRAM = u2018SAPMTFBAu2019.
BDCTAB-DYNPRO = 200.
BDCTAB-DYNBEGIN = u2018Xu2019.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-NAMEu2019.
BDCTAB-FVAL = ITAB-NAME.
APPEND BDCTAB.CLEAR BDCTAB.
Passing screen information to BDCDATA
BDCTAB-FNAM = u2018SCUSTOM-CITYu2019.
BDCTAB-FVAL = ITAB-CITY.
APPEND BDCTAB.CLEAR BDCTAB.
Passing BDC_OKCODE to BDCDATA
BDCTAB-FNAM = u2018BDC_OKCODEu2019.
BDCTAB-FVAL = u2018SAVEu2019.
APPEND BDCTAB.CLEAR BDCTAB.
ENDFORM. u201CGENERATE_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, u201CPopulating BDCDATA Table
Call transaction u2018TFBAu2019 using BCDDATA Mode u2018Au2019 Update u2018Su2019.
REFRESH BDCTAB
ENDLOOP.

Apple ID for the Deployment Program and VPP is the same

I created an Apple ID for the Deployment Program and authorized the same ID for VPP. Now I learned these should be different. Is this a problem and if so, how can the VPP ID be changed?

You should be able to. The only hiccup will be that any apps that you have purchased with the older ID you will have to repurchase with the newer ID to be able to keep using them.
Though of course this actually depends on how you plan to use the IDs. For example, I had an Apple ID through iTunes a few years before I opened a .Mac/MobileMe account (what iCloud is now in case you are new to Apple). Thus, my iPhone and iPad actually have two IDs on them, one for iTunes/App Store, and one for anything associated with iCloud. I've never really had any problems assoctiated with having two IDs on one device. Usually just an extra step when I get a new device or have to restore either of them for some reason. Though I understand that this is probably not what you plan on doing, I thought I would use it as an example of what the IDs are really associted with on the devices.

How to debug BDC , Dialog program and Script

Hi all,
Please let me know, how to debug BDC , Dialog program and Script
Thanks&Regards
Devi

SCRIPT DEBUGGING
When we want to debug the SAPSCRIPT, we need to first activate the debugger, we have 2 ways to activate the Debugger.
1) Execute the program RSTXDBUG
2) Go to SE71, from the initial screen enter the form name and press Utilities --> Activate Debugger
When we are in the Debug screen,
3.1) F5 will be debug filed by field, that means if a single line is having 5 fields, if we press the F5 this will do field by field,
3.2) F6 will be line by line, that means when we press the F6, it will debug the line and it will go to the next line. F7 also do the same way
3.3) F8 will be very useful when we have any include statement in the SCRIPT, if any include is there and we press the F5 or F6 then this will go that Include (normally SO10 or any transaction text), then if we want line by line debugging then we can press the F5 or F6, or if you want to execute that in a single shot then press the F8, then the debugger will be executed that include and come back to the Script debugging.
Some times in the script, we may right lengthy lines, if we want to debug that whole line, we have an option called Left/Right, this we will find the Debug screen of the script, there is a Push button, we can make use this button to debug.
We can put the breakpoints in the SCRIPT DEBUGGER also, just press the BREAKPOINT Pushbutton from the debugging screen or press EDIT --> Breakpoint
If we want to debug the print program from the SCRIPT DEBUGGER, just press SHIFT+F7 or EDIT --> ABAP Debugging
If we want to see the Windows which are defined in the forms, just press the Go to --> Form --> Windows .if we want to see the pages go to --> Form --> pages. Here we have an option to see the page wise window also go to --> Form --> page Windows
If we want to see the paragraphs which are defined in that script, press go to --> Styles --> paragraphs.
If we want to see the Character formats which are defined in that script, press go to --> Styles --> Character Strings.
If we want to see the Page formats which are defined in that script, press go to --> OTF --> Page.
If we want to see the Elements which are used in the Script, then press go to --> Text Elements --> Form Elements.
If we want to see the commands which are used in the script, press go to --> Commands --> List
Finally, if we want to exit from the SCRIPT DEBUGING, simply press Debugger --> Exit
DEBUG BDC
ust go into debugging mode and do the BDC step by step, when it comes to the Call Transaction line, check the mode which will be 'N'....Now, overwrite this with 'A' and execute the BDC...It will run in All Screens Mode....
As suggested above the MODE 'A' will do the trick as it takes you to all screens.
Normally MODE N will be defaulted as it will be used for background processing,
Here is a simple tip,
This will be the call transaction part of the program,
CALL TRANSACTION 'IW32' USING BDCDATA MODE 'N'
MESSAGES INTO MESSTAB.
I would suggest you to make it like this,
DATA: V_MODE TYPE C VALUE 'N'.
*<In debug mode set V_MODE = 'A' for debugging>
CALL TRANSACTION 'IW32' USING BDCDATA MODE V_MODE
MESSAGES INTO MESSTAB.
This will be very useful because you just need to change the value of the V_MODE at runtime as A for debugging besides it has N which is the default to be used. (i.e. you need not change the code again and again).
This will be very useful when you have to debug some program in QA or PRD servers.
regards,
srinivas
*reward for useful answers*

Please send detail steps for uploading legacy data

Hi friends,
please send detail steps for uploading legacy data
Thanking u in advance,
Diwa.

HI U CAN USE LSMW TO UPLOAD LEGACY DATA
LSMW is used for migrating data from a legacy system to SAP system, or from one SAP system to another.
Apart from standard batch/direct input and recordings, BAPI and IDocs are available as additional import methods for processing the legacy data.
The LSMW comprises the following main steps:
Read data (legacy data in spreadsheet tables and/or sequential files).
Convert data (from the source into the target format).
Import data (to the database used by the R/3 application.
But, before these steps, you need to perform following steps :
Define source structure : structure of data in the source file.
Define target structure : structure of SAP that receives data.
Field mapping: Mapping between the source and target structure with conversions, if any.
Specify file: location of the source file
Of all the methods used for data migration like BDC, LSMW , Call Transaction which one is used most of the time?
How is the decision made which method should be followed? What is the procedure followed for this analysis?
All the 3 methods are used to migrate data. Selection of these methods depends on the scenario, amount of data need to transfer. LSMW is a ready tool provided by SAP and you have to follow some 17 steps to migrate master data. While in BDCs Session method is the better choice because of some advantages over call transaction. But call transaction is also very useful to do immediate updation of small amout of data. (In call transaction developer has to handle errors).
SO Bottom line is make choice of these methods based of real time requirements.
These methods are chosen completely based on situation you are in. Direct input method is not available for all scenario, else, they are the simplest ones. In batch input method ,you need to do recording for the transaction concerned. Similarly, IDoc, and BAPI are there, and use of these need to be decided based on the requirement.
Try to go through the some material on these four methods, and implement them. You will then have a fair idea about when to use which.
LSMW Steps For Data Migration
How to develop a lsmw for data migration for va01 or xk01 transaction?
You can create lsmw for data migration as follows (using session method):
Example for xk01 (create vendor)
Initially there will be 20 steps but after processing 1 step it will reduced to 14 for session method.
1. TCode : LSMW.
2. Enter Project name, sub project name and object name.
    Execute.
3. Maintain object attributes.
    Execute
    select Batch Input recording
    goto->Recording overview
    create
    recording name.
    enter transaction code.
    start recording
    do recording as per ur choice.
    save + back.
    enter recording name in lsmw screen.
    save + back
Now there will be 14 steps.
2. MAINTAIN SOURCE STRUCTURES.
    Here you have to enter the name of internal table.
    display change
    create
    save + back
3. MAINTAIN SOURCE FIELDS.
    display change
    select structure
    source_fields->copy fields.
    a dialogue window will come .
    select -> from data file
    apply source fields
    enter No. of fields
    length of fields
    attach file
    save + back
4. MAINTAIN STRUCTURE RELATIONS
    display change
    save + back
5. MAINTAN FIELD MAPPING & CONVERSION RULE
    display change
    click on source field, select exact field from structue and enter
    repeat these steps for all fields.
    save+back
6. MAINTAIN FIXED VALUES, TRANSACTION, USER DEFINED
    execute
    save + back
7. SPECIFY FILES.
    display change
    click on legacy data
    attah flat file
    give description
    select tabulatore
    enter
    save + back
8. ASSIGN FILE
    execute
    display change
    save + back
9. IMPORT DATA.
    execute
    display change
    save + back
10. DISPLAY IMPORTED DATA
      enter ok, it willl show records only.
      back
11. CONVERT DATA
      execute
      display change
      save + back
12. DISPLAY CONVERTED DATA
      execute
      display change
      save + back
13. CREATE BATCH INPUT SESSION
      tick keep batch input folder
      F8
      back
14. RUN BATCH INPUT SESSION.
      sm35 will come
      Object name will be shown here
      select object & process

Steps for creating a new BAPI function module

Hello experts,
Can any one send me steps for creating a new BAPI function module , I got a requirement to do like this,but I dont have any clue about how to create.
Please help !!!

BAPI stands for Business Application Programming Interface.
There are 5 different steps in BAPI.
- Create BAPI Structure
- Create BAPI Function Module or API Method.
- Create BAPI object
- Release BAPI Function Module.
- Release BAPI object.
Step1. Creating BAPI Structure:
- Go to <SE11>.
- Select Data Type & Enter a name.
- Click on Create.
- Note: Always BAPI should be in a development class with request number (Not Local Object).
- Select Structure & hit ENTER.
- Enter the fields from your database. Make sure that the first field is the Primary Key Field.
- Then SAVE & ACTIVATE.
Step 2. Creating BAPI module:
- Enter TR.CODE <SE37>.
- Before entering any thing, from the present screen that you are in, select the menu
 Goto -> Function Groups -> Create Group.
 Enter a name (Note: This name Must start with ZBAPI)
 Let this screen be as it is and open another window and there, enter TR.CODE <SE80).
 Click on the Third ICON that says Inactive Objects.
 Select the group that you just created and click on Activate.
 Notice that the group you created will disappear from the list of inactive objects.
- Go back to <SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.
NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.
Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.
Then click on the second tab that says [IMPORT].
Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box Pa. All remotely enabled functional modules MUST be Pa enabled, where Pa means Passed by Value and if you dont select Pa, then that means it will be passed by reference..
Then click on tab that says [EXPORT].
Enter the following as is in the first three fields
RETURN TYPE BAPIRETURN (These 3 field values are always same)
Here also select Pa meaning Pass by value.
Note: BAPIRETURN contains structure with message fields.
Then SAVE and ACTIVATE.
Step 3. Creating BAPI object:
- Enter Tr.Code <SWO1> (Note. It is letter O and not Zero).
- Enter a name and then click on create. Enter details.
NOTE: Make sure that that Object Type and Program name are SAME.
- Enter Application M, if you are using standard table Mara. If you are using your own database then select Z at the bottom.
- Then hit <ENTER>.
- Now we have to add Methods. High light METHODS and then select the following from the menu:
Goto Utilities -> API Methods -> Add Methods.
- Enter function Module name and hit <ENTER>.
- Select the second FORWARD ARROW button (>)to go to next step.
- Check if every thing looks ok and again click on FORWARD ARROW button (>).
- Then select YES and click on <SAVE>.
- Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.
- Goback to TR.CODE <SWO1>.
Here select the menu combination shown below in the same order.
- Edit -> Change Release Status -> Object Type Component -> To Implemented.
- Edit -> Change Release Status -> Object Type Component -> To Released.
- Edit -> Change Release Status -> Object Type -> To Implemented.
- Edit -> Change Release Status -> Object Type -> To Released.
- Then click on <SAVE>.
- Then click on Generate Button (4th button from left hand side looks like spinning wheel).
- Then Click on the button that says PROGRAM to see the source code.
To check if this is present in work flow goto TR.CODE <BAPI>.
Here it shows business object repository.
- First click on the middle button and then select ALL and hit ENTER.
- Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully.
regards,
aswin

Why am I being charged for the Edge program

I recently went into a Verizon Wireless store to get some questions answered about my account and upgrade eligibility. Both my husbands and my phone were having issues and we needed to upgrade or find some other options. We began to speak with an employee at the store and were told we could upgrade to the Edge program so we could receive new phones and not wait another 5 months to our upgrade date. My phone would make random calls, text people out of nowhere, and my husbands would randomly shut down or end calls, as well as his screen was cracked. The employee stated that we could upgrade to the edge program and all we needed to do was send in an iPhone (the phone brand we were using). He said we would either need to get the screen replaced on my husbands phone as well as take my phone to apple to get it diagnosed and get that problem fixed. It sounded like an excellent deal and we asked if we could just buy a good used phone from a used website and send those phones in instead of going through the trouble of getting our current phones fixed to send in. The employee stated that as long as the screens weren't cracked and they were an iPhone 4 or higher then we would be fine. So we bought two used iPhone 4's that were in excellent condition and had no mechanical issues. We sold the phones we had to offset the cost to purchase the two used ones. We got signed up for our new edge program and sent in the two used iPhones. After a few months we received our Verizon bill and it was over $900! We called customer service and they began to tell us that our phones were broke and didn't pass the mechanical performance test so we were charged a fee. So we not only had to pay for those two used phones to send in and pay for our new phones, we are now being charged a $750 fee for these phone being so called broke? We were told that because we broke the edge contract there is no way to get a refund for this fee and have to pay it! This is the most RIDICULOUS thing I have ever heard of and is about to cause a huge appeal to this situation. I will be getting an attorney and am looking for any others who have had issues with the Edge program or similar problems. I will be filing suit against Verizon Wireless for this issue and if we get enough people with similar problems with the Edge program, then we will file a Class Action Lawsuit against Verizon Wireless to get the money back that they have stolen from us, the customers. We will also file for Verizon Wireless to pay for personal loss and harm these fee's have caused. Please reply to this thread and if you have the same problems then we will add you onto the Class Action Lawsuit so you can get back what you have lost or are losing. Thank you. Verizon Wireless Customer Support

Sounds like you Early Edged before finishing your contract. So Verizon told you you could turn in just any iPhone for the Edge program? I always thought you had to turn in the phone that you had not finished paying for yet, the one under contract.

How can I book an employee for a training program from PD?

HI One and All,
Hope all of you Doing well...
I configured Personal Development and Training Event Management.
When I go for Profile Match-up, I found that One employee is lack-off some skills. I have a training program to fill those skills. How can I book that employee for training program from Pofile match-up screen?
Or is there any other way to book an employee for a training program from PD?
Thnaks,
Potru,

Hi Priya,
Thanks for your response, I check the option Generate training Praposals before running the profile match-up. I have created one training Event type (D) and i assigned qualification through A-028 relation.
Here one employee is lack of MS Office excellent skills for Assistant Manager position, I created Training Event (D) called MS Office training and assigned the qualification for this training program.
when I run profile match-up I got an Icon Training praposal (Tree symbol).
and also I have a column called Training , but it is blank.
I want to book that employee for that training progam (MS offcie training program), from Profile match-up screen.
I have selected the employee and I click on the Icon called Further Training. But the message is like Choose a valid line.
How can I send employee for MS Office training from profile match-up screen?
Please guide me...
Thanks,
Potru.

Problem during recording of CJ01 transaction for BDC

Hello All,
I am facing a problem during the recording of CJ01(Creation of projects) for creation of BDC program.
The problem is during recoding after entering the the first WBS element with level 1 and i press the '+' button to create one more WBS element with Level 2,the first WBS element with level 1 goes to the bottom of the line item table and now if try to create the WBS element with Level 2 in the first line it wont allow because of the fact that the first WBS element with level 1 is below it.
But if i enter the first WBS elemnt with level 1 in the first line and come to the next line and enter the second WBS element with level 2 it will create since Level 2 WBS is below the Level 1.But this approach cannot be used for doing a recording for BDC.
Can anyone help in this regard
Thanks in Advance
Ashish

Hi Ashish,
NW is right. It is not proper to use BDC for CJ01. You can get more control and better if you use the following function module,
1. Use BAPI_PROJECT_MAINTAIN to create project definition and WBS Structure in one go. see the documentation in the BAPI on how to use this. Post the resut in this forum if you face any problem
Ravi

Steps for BDC before program

Similar Messages

Maybe you are looking for