ABAP Demo Programs with standards for coding

Hello,
Like ABAPDOCU is there any transaction/program provided by SAP where general standards for coding are given.
Regards,
Mayank

I guess thats the tcode for going through examples in SAP.
Otherwise you may go through standard reports.
I can suggest you two links where you can get lots of programming examples of good quality.
<a href="http://www.sap-img.com">http://www.sap-img.com</a>
<a href="http://www.sapdevelopment.co.uk">http://www.sapdevelopment.co.uk</a>
Regards,
Amit
Reward all helpful replies.

Similar Messages

Can i development program with EDK for uploading file to server?

Can I development program with EDK for uploading file to server?How to avoid same name of files?
Thanks!

Hi ,
thanks for the quick response.
but the problem is supppose i have a excel sheet with 16 rows and 13 columns(so data).
i am placing this file contents to appserver USING ABOVE fm.
after that i am reading the file from appserver to create SO(idoc),i need 1row-3column data and 2row-2c data.like that.
in unix we will get row data(after uploading to app server) as #mprn#2345# like this so easy to separate when reading.but in MS NT OS 1row data getting stored in different rows in Appserver.so difficult to read.
so the above mentioned FM is OS dependent or is there any way (any other FM) to get same kind of data in different OS.
PLEASE SUGGEST OTHER WISE I NEED TO CODE BASED ON OS.
REGARDS
SARATH

I need standard for coding and desiging in 9ids

well me is new to oralce soo can any one help me to privide me the document or link or any reference material regarding the standard that is provided by the oracle co-operation for the its developer suite product development
i will also appricatie that plz guide me for the standard develoment in this package so that it help me in making new projects in oracle according to its standard that been given thanks

Tariq,
as far as Forms is concerned there are no design patterns or design guidelines that I am aware of. For JDeveloper, which also is part of the Oracle9iDS you can follow any Java programming design guidlelines you want.
Forms information can be found at
otn.oracle.com/products/forms
Reports
otn.oracle.com/products/reports
JDeveloper
otn.oracle.com/products/jdev
Frank

Programming with Kinect for Windows V2

I am a PhD student using Kinect V2 for data collection and I am actually new to it. I will like help with a code in C#, which measures body joints and calculates the joint angles during skeletal tracking. Please I urgently need help on this.
Thanks.

Hello Chy1234,
the demos provided by the SDK browser are a good start. Fire up the browser and filter for C# demos. Take a look at the
BodyBasics example. There you can see how you read bodies. In the kinect context, a body has
25 Joints. These joints have a X,Y,Z coordinate. You will need these information for your calculation. Also consider watching some
Jump Start videos as start.
What exactly do you mean with "measures body joints"?
Best regards,
Alex

Programming with Clusters for HR-Payroll

Hi
I have a requirement to make a report using payroll result.
Can anyone in the forum suggest me some good links for the same ?
Thanks in Advance,
Mayank

*& Report ZREAD_RT                                                    *
REPORT ZREAD_RT                                .
NODES : PERNR.
DATA: result type pay99_result.
DATA: my_rt like table of pc207 with header line.
DATA: LTX_RGDIR LIKE PC261 OCCURS 0 WITH HEADER LINE.
DATA : seq_no(5) type n.
START-OF-SELECTION.
GET PERNR.
CALL FUNCTION 'CU_READ_RGDIR_NEW'
EXPORTING
    persnr                      = PERNR-PERNR
    CHECK_READ_AUTHORITY        = SPACE
tables
    in_rgdir                    = LTX_RGDIR
EXCEPTIONS
   NO_RECORD_FOUND             = 1
   IMPORT_MISMATCH_ERROR       = 2
   NO_READ_AUTHORITY           = 3
   OTHERS                      = 4
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE LTX_RGDIR WITH KEY FPBEG(6) = PNPBEGDA(6).
IF SY-SUBRC = 0.
seq_no = LTX_RGDIR-SEQNR.
ENDIF.
   call function 'PYXX_READ_PAYROLL_RESULT'
        exporting
             clusterid                    = 'RX'
             employeenumber               = PERNR-PERNR
             sequencenumber               = seq_no
             READ_ONLY_INTERNATIONAL      = 'X'
        changing
             payroll_result               = result
my_rt[] = result-inter-rt[].
LOOP AT MY_RT.
WRITE : /10 MY_RT-ABART,
            MY_RT-LGART,
            MY_RT-APZNR,
            MY_RT-CNTR1,
            MY_RT-CNTR2,
            MY_RT-CNTR3,
            MY_RT-ALZNR,
            MY_RT-C1ZNR,
            MY_RT-BTZNR,
            MY_RT-ABZNR,
            MY_RT-V0TYP,
            MY_RT-V0ZNR,
            MY_RT-ZEINH,
            MY_RT-BETPE,
            MY_RT-ANZHL,
            MY_RT-BETRG,
            MY_RT-RTE_CURR,
            MY_RT-AMT_CURR.
ENDLOOP.

Abap-OOPS Help with standard class Cl_RSPLFC_COPY

Please help me out in expanding the functionality of an existing class cl_rsplfc_copy .As i want 2 copy some data from one cube 2 an another cube taking some characters common in both the cubes.

Is there any specific reason you want to use exit, when there is a standard copy planning function which does the copy without any customization? Why not use a multiplanning area and copy its simple to implement and maintain.

Bdc program with out coding

Hi All,
I want to know how to write a bdc program with out coding...
Thank you,
Gopi....

Hai.
check this.
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 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.
regards.
sowjanya.b.

Which one is better EP with ABAP or EP with Java

Hi Experts,
Please tell me Which one is better EP with ABAP or EP with Java for learning and useful in USA?
Regards
Jana

What programming background do you already have? You should match up the flavor of Web Dynpro that matches the skill sets you already have? Do you have ERP or other Business Suite experience already? If so you will find that WDA is often used in conjunction with the Business Suite and WDJ used for composites. So consider where your business domain experience and knowledge lies and support that as well.

How to create a job thru ABAP program for calling a program with variant???

Hello experts,
can u give me step wise procedure to create jobs for a program with a variant name thru ABAP???
Also, can a transaction can be scheduled as a job to run in background with a variant name???
Edited by: SAP USER on Jul 22, 2008 6:08 AM

Hi,
To create a job through ABAP program you can do the following.
Go to Menu bar.
In there, go to SYTSTEM> SERVICES> JOBS--> DEFINE JOB.
Then give the JOB NAME and CLASS in the screen that comes up.
This is how we schedule a program.
Now, to create a variant for a program -
First activate your program in SE38. Then execute it .
Now, click on SAVE button. It will open up the variant creation screen. Give the details there like variant name and value for the fields. Save and come back.
Hope this helps.
Regards,
Hari Kiran

Hello friends , I have started with writing c code on mac using xcode .....but one of my friend told me to use gcc for coding. He started with terminal And used a text editor to compil the c program on his mac.. So please tell me how to do the same

Hello friends , I have started with writing c code on mac using xcode .....but one of my friend told me to use gcc for coding. He started with terminal And used a text editor to compil the c program on his mac.. So please tell me how to do the same and is there any pre stalled text editor on mac if yes then where and if no then which text editor to install and how to install gcc...please help me out thanks in advance !!!

I have started with writing c code on mac using xcode .....but one of my friend told me to use gcc for coding.
Why? If you are developing and writing code on a Mac why would you not use the tools Apple has given you? And Xcode, once you get use to it, is a very nice development environment that will make you life a whole lot easier.
If you insist on using an editor and the terminal I would recommend Emacs but it has a long learning curve so something like TextWrangler will work too.
As for the compiler if you have Xcode installed install the command line tools and you will be able to compile from the terminal.
good luck

SAP standard example to get start with Webdynpro for ABAP

Hi,
I just started learning Webdynpro for ABAP.
I'm looking for SAP standard buit in applilcation example which explains all the the view controls, properties and Layout desining.
please let me know the standard applications of SAP for learning.
Many Thanks,
Gupta

hi..
just go to package SWDP_DEMO, it has all sample webdynpro applications using all UI elements.
By the way...question is posted in wrong forum
Regards
Manas Dua

Need help with a activation code for Adobe Acrobat X Standard for my PC,, Don't have older version serial numbers, threw programs away, only have Adobe Acrobat X Standard, need a code to unlock program?

Need help with a activation code for Adobe Acrobat X Standard for my PC, Don't have older Version of Adobe Acrobat 9, 8 or 7.

You don't need to install the older version, you only need the serial number from your original purchase. If you don't have them to hand, did you register? If so, they should be in your Adobe account. If not you really need to contact Adobe, though it isn't clear they will be able to do anything without some proof of purchase etc.

Integrating WebDynpro ABAP applications with UWL for workflow in Portal

Dear
We want to integrate an abap webdynpro application as task in the workflow with UWL.
More information was found in /people/ginger.gatling/blog/2005/12/14/create-new-uis-for-existing-workflow-tasks-with-abap-web-dynpro-and-universal-worklist
But no answer on the following issue:
We use the transaction SWFVISU to prepare standard setting for our task. This defines how a task is executed, once you select the task subject line on the worklist.
Task                           TS91700001
Visualization Type             ABAP Web Dynpro
APPLICATION     z_wd_pas
DYNPARAM     IV_WIID=${item.externalId}&period=${item.PERIOD}
NAMESPACE     SAP
SYSTEM_ALIAS     SAP_BSP_EREC
But we want to start the abap webdynpro application with a dynamic parameter: period 07.2010 or 08.2010 or MM.YYYY. This parameter is a container element of the task, filled when the task is created. Also other parameters are available in the abap webdynpro application.
Component       Z_WD_PAS
Interface View PAS
Plug Name       DEFAULT
Help Menu Text
Help Link
                                                                                Package         Z_PAS
Language        EN
URL             http://saperpd1.imec.be:8000/sap/bc/webdynpro/sap/z_wd_pas
with parameters
IV_WIID     000000000000     SWW_WIID
ORG_UNIT     00000000     ORGEH
PERIOD                              SPMON
PERNR     00000000     PERSNO
Can we set the dynamic parameter list DYNPARAM from the task
or should we read the container in our abap webdynpro application described in http://wiki.sdn.sap.com/wiki/display/WDABAP/IntegratingWebDynproABAPapplicationswithUWLforworkflowin+Portal?
More information: The task is a webservice
Standard task        91700001   Z_PAS_CC
Object Category      BOR Object Type
Object Type          WEBSERVICE   WebFlow Service
Method               PROCESSDIALOG                      Dialog Service
with the following standard program code for this method:
begin_method processdialog changing container.
DATA: l_wi_objkey TYPE swotobjid-objkey.
DATA: l_wiid TYPE swwwihead-wi_id.
                                                                                CALL FUNCTION 'SWE_WI_GET_FROM_REQUESTER'
IMPORTING
    requester_workitemid = l_wi_objkey.
l_wiid = l_wi_objkey.
                                                                                CALL FUNCTION 'SWF_WSC_START_LH_DIALOG'
EXPORTING
    i_wiid                 = l_wiid
EXCEPTIONS
    url_creation_failed    = 1
    browser_launch_failure = 2
    OTHERS                 = 3.
IF sy-subrc <> 0.
CASE sy-subrc.
    WHEN 1.
      exit_return '1000' space space space space.
    WHEN 2.
      exit_return '1001' space space space space.
    WHEN OTHERS.
      exit_return '1002' space space space space.
ENDCASE.
ENDIF.
end_method.
Before calling the function SWF_WSC_START_LH_DIALOG the parameters for the abap webdynpro should be defined. Is this possible ?
Thanks for your suggestions.
Best regards
Luc Marent

I added below sources .
>    <ItemType name="uwl.request.webflow.WS91000001" connector="WebFlowConnector" defaultView="WorkItemRequestsView" defaultAction="launchWebDynPro" executionMode="default">
>      <ItemTypeCriteria systemId="UWLSETXXX" externalType="WS91000001" connector="WebFlowConnector" />
>      <Actions>
>        <Action name="launchWebDynPro" groupAction="" handler="SAPWebDynproABAPLauncher" returnToDetailViewAllowed="yes" launchInNewWindow="yes" launchNewWindowFeatures="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no">
>          <Properties>
>            <Property name="WebDynproApplication" value="ZWD_WF_002" />
>            <Property name="newWindowFeatures" value="resizable=yes,scrollbars=yes,status=yes,toolbar=no,menubar=no,location=no,directories=no" />
>            <Property name="DynamicParameter" value="wi_id=${item.externalId}" />
>            <Property name="openInNewWindow" value="yes" />
>            <Property name="System" value="WDSETXXX" />
>            <Property name="WebDynproNamespace" value="sap" />
>            <Property name="display_order_priority" value="5" />
>          </Properties>
>          <Descriptions default="" />
>        </Action>
>      </Actions>
>    </ItemType>
>    <ItemType name="uwl.request.webflow.decision.WS91000001.UWLSETXXX" connector="WebFlowConnector" defaultView="WorkItemRequestsView " defaultAction="viewDetail" executionMode="default">
>      <ItemTypeCriteria systemId="UWLSETXXX" externalType="WS91000001" connector="WebFlowConnector" />
>    </ItemType>

Tools to upload data into SRM 7.0 with webdynpro for ABAP

Hi,
Webdynpro for abap is used in SRM70.
I need to load data in SRM70 (product category...).
ECATT is not working with web dynpro for abap.
What other tools can i use to load data in SRM70 ? LSMW ?
I would like to avoid to create a Z program to load data into SRM70...
Thanks,
Kind regards,
Yann

Hello Yann.
welcome . we read your wonderful threads and they are useful to coomunity forever.
I am not aware much.
Product category is a permanent data right . i think we may not frequently change the data right.
Does your business want very frequent update on product category?
I believe if we make frequent changes/modify of data we may use LSMW .
i think your zprogram is a best method to upload the product category.
As you aware we can not change the product category as per standard.For eg. If i create a local product category /hierarchy .Even i can not rename them.
category/hierarchy creation are one time activity in SRM.
please correct me.
regards
Muthu

Problem with the active version of the transfer rule ABAP program with sour

Hi,
I have a problem with the active version of the transfer rule ABAP program with source system EXCEL.
The system does not react to changes done in the transfer rule coding. For FISCPER I have hardcoded the result 'BABABA' and still the results delivered are those from the CSV.
Resetting the system buffers does not help. The problem is systematic in combination with source system EXCEL (i.e. not only 1 InfoSource). Checking the active program Extras->Display Program shows the coding (result='BABABA') being there, but
as stated, the system does not produce the result BABABA, but instead the result of the CSV.
It seems as if the original version from the very first activation of the transfer rule program remains somewhere and continues to be used. Does anybody know how to flush it out and get the system to actually use the coding appearing as the active program.
I have posted an OSS note, but SAP takes it time to answer and I am under time pressure so I figured that maybe one of you know who to solve it before SAP does.
Greetings and thanks,
Martin

Hi martin,
just try to go out the RSA1 and then return to your infopac. ...
sometimes there some "cache" trouble

ABAP Demo Programs with standards for coding

Similar Messages

Maybe you are looking for