BDC

Former Member · ‎2008 Feb 03

HI,

In BDC , wat is the difference between a call transaction method and a session method.?

Former Member · ‎2008 Feb 03

Hi,

BDC allows you to perform database updates in the background using standard SAP transactions.

The resultant entries will be as if the user had manually entered the data via SAP. This means

that you do not bypass any of the standard SAP consistency checks, authorisations etc.

There are two main methods of ABAP BDC, these are Call Transaction and Batch Input.

Difference between batch input and call transaction in BDC

Session method.

1) synchronous processing.

2) can tranfer large amount of data.

3) processing is slower.

4) error log is created

5) data is not updated until session is processed.

Call transaction.

1) asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) errors need to be handled explicitly

5) data is updated automatically

Hope this helps.

Reward if helpful.

Regards,

Former Member · ‎2008 Feb 03

Session Method

1) Session method supports both small amount of data aswell as large amount of data

2) data processing is asynchronus and data updation is synchronus.

3) it process multiple apllication while perfomaning validations.

4) in session method data will be updated in data base only after processing session only.

5) system provide by default logfile for handling error records.

6) it supports both foreground aswell as background process

in bdc we use FM ...

bdc_open_group " for creating Session

bdc_insert " adding transaction and bdcdata table for updating database

bdc_close_group " for closing Session

Call Transaction

1) Call transaction exclusively for small amout of data

2) it supports only one apllication while perfoming validations

3) there is no default logfile, We can explicitly provide logic for creating logfile for handling error records.

we can create logfile by using structure....BDCMSGCOLL

4) it doesn't support background processing.

5) data processing is synchronous and Data updation is Synchronous( default), in

this method also supports daya updation in asynchronus process also.

syntax:

Call transaction <transaction-name> using BDCDATA

mode <A/N/E>

update <L/A/S>

messages into BDCMSGCOLL.

Session

The most important aspects of the batch SESSION interface are: - Asynchronous processing - Transfers data for multiple transactions - Synchronous database update During processing, no transaction is started until the previous transaction has been written to the database. - A batch input processing log is generated for each session - Sessions cannot be generated in parallel

Call Transcation

The most important aspects of the CALL TRANSACTION USING interface are: - Synchronous processing - Transfers data for a single transaction - Synchronous and asynchronous database updating both possible The program specifies which kind of updating is desired. - Separate LUW for the transaction The system performs a database commit immediately before and after the CALL TRANSACTION USING statement. - No batch input processing log is generated.

Former Member · ‎2008 Feb 03

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 you’ll 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

EDIT BATCH INPUT  SERVICES SYSTEM

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

Define jobs Jobs  Administration Tools

Or

Jobs services System

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 don’t pass any record but some indication to system telling it to proceed further. For example: The following screen

To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.

Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.

BDC_CURSOR is also used to place cursor on particular field.

AN EXAMPLE WITH SESSION METHOD

Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.

The transaction is TFBA (to change customer).

A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.

Prerequisite to write this BDC interface as indicated earlier is:

1. To find screen number

2. To find screen field names, type of the field and length of the field.

3. To find BDC_OKCODE for each screen

4. Create flat file.

Flat file can be created in your hard disk as follows:

1 Vinod Krishna Hyderabad

2 Kavitha Secunderabad

3 Kishore Hyderabad

(Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)

To transfer this data to database table SCUSTOM following interface can be used.

REPORT DEMO1.

Following internal table is to upload flat file.

DATA: BEGIN OF ITAB OCCURS 0,

ID(10),

NAME(25),

CITY(25),

END OF ITAB.

*Following internal table BDCDATA is to pass date from internal table to session.

DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.

Variables

DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. “ This is for Hold Date

To upload flat file to internal table.

CALL FUNCTION UPLOAD

EXPORTING

FILE NAME = ‘C:\FF.TXT’

FILE TYPE = ‘ASC”

TABLES

DATA_TAB = ITAB

EXCEPTIONS

CONVERSION_ERROR = 1

INVALID_TABLE_WIDTH = 2

INVALID_TYPE = 3

NO_BATCH = 4

UNKNOWN_ERROR = 5

OTHERS = 6.

If sy-subrc = 0.

Calling Function to Create a Session

CALL FUNCTION ‘BDC_OPEN_GROUP’

EXPORTING

CLIENT = SY-MANDT

GROUP = ‘POTHURI’

HOLDDATE = DATE1

KEEP = ‘X’

USER = SY-UNAME

EXCEPTIONS

CLIENT_INVALID = 1

DESTINATION_INVALID = 2

GROUP_INVALID = 3

GROUP_IS_LOCKED = 4

HOLDDATE_INVALID = 5

INTERNAL_ERROR = 6

QUEUE_ERROR = 7

RUNNING = 8

SYSTEM_LOCK_ERROR = 9

USER_INVALID = 10

OTHERS = 11.

If sy-subrc = 0.

*--

MAIN Logic--

LOOP AT ITAB

PERFORM GENERATE_DATA. “ Populating BDCDATA Table

CALL FUNCTION ‘BDC_INSERT’

EXPORTING

TCODE = ‘TFBA’

TABLES

DYNPROTAB = BDCTAB

EXCEPTIONS

INTERNAL_ERROR = 1

NOT_OPEN = 2

QUEUE_ERROR = 3

TCODE_INVALID = 4

PRINTING_INVALID = 5

POSTING_INVALID = 6

OTHERS = 7.

REFRESH BDCTAB

ENDLOOP.

Calling function to close the session

CALL FUNCTION ‘BDC_CLOSE_GROUP’

EXCEPTIONS

NOT_OPEN = 1

QUEUE_ERROR = 2

OTHERS = 3.

Endif.

&----

*& 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.

Former Member · ‎2008 Feb 03

hi Suresh, this will guide u.

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

BATCH INPUT METHOD:

This method is also called as ‘CLASSICAL METHOD’.

Features:

Asynchronous processing.

Synchronous Processing in database update.

Transfer data for more than one transaction.

Batch input processing log will be generated.

During processing, no transaction is started until the previous transaction has been written to the database.

CALL TRANSACTION METHOD :

This is another method to transfer data from the legacy system.

Features:

Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.

Updating the database can be either synchronous or asynchronous. The program specifies the update type.

Transfer data for a single transaction.

Transfers data for a sequence of dialog screens.

No batch input processing log is generated.

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

Among the two methods call transaction is better compared to session bcoz data transfer is faster in it.

Differences between call transaction and session.

Session Method:

1) Data is not updated in the database table until the session is processed.

2) No sy-subrc is returned.

3) Error log is created for error records.

4) Updation is always synchronous.

Call Transaction Method:

1) Immediate updation in the database table.

2) sy-subrc is returned.

3)Error need to be handled explicitly.

4) updation can be synchronous as well as asynchronous.

2) ya u can use using the N mode no screen.

3)u can't handle multiple transaction in call transaction.

4) u can handle multiple transaction in session using the BDC_INSERT fm.

5)When u go to SM35 u can able to see the error records.

Which is best?

That depends on your requirement. Both of them have there advantages.

According to the situation u can choose any one of these.

difference between batch input and call transaction in BDC Session method.

1) synchronous processing.

2) can tranfer large amount of data.

3) processing is slower.

4) error log is created

5) data is not updated until session is processed.

Call transaction.

1) asynchronous processing

2) can transfer small amount of data

3) processing is faster.

4) errors need to be handled explicitly

5) data is updated automatically

For session method,these are the function modules to b used.

BDC_OPEN_GROUP

BDC_INSERT

BDC_CLOSE_GROUP

For call transaction,this is the syntax.

CALL TRANSACTION TCODE USING BDCDATA

MODE A or E or N

UPDATE A or S

MESSAGES INTO MESSTAB.

Take a scenario where we need to post documents in FB01 and the input file has say 2000 records (2000 documents, not line items in FB01 but 2000 records)

In the BDC call transaction method

We call the transaction FB01 2000 times (once for each record posting) and if the processing fails in record no 3 it can be captured and start with reocord 4.

Eg: Loop at itab.

call transaction FB01

capture errors

endloop.

In the session method.

We do not explicity call the transaction 2000 times, but all the records are appeneded into a session and this session is stored. The processinf of the session is done wwhenever the user wants it to be done. Hence the errors cannot be captured in the program itself

Check these link:

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

Batch Input Session method is asynchronous as told by others here. But the advantage of this is that you have all the error messages and the data for each transaction held persistantly. You don't have to code anything for processing them or writing the logs.

But at the same time, the same feature can be disadvantageous if you need to react to an error or if there are too many errors to manually correct in a session. Since the session are created in the program and its execution is done seperately, you loose the trackability of such transactions.

With a call transaction, what was a disadvantage above will become an advantage. Call transaction immediately gives you messages back and you can react to it in your program. But the disadvantage is that, if you have several hundreds of transactions to run, running them from within the program can be resource crunching affair. It will hamper the system performance and you cannot really distribute the load. Of course, you have some mechanisms with which you can overcome this, but you will have to code for it. Also, storing the messages and storing the errored transaction data etc will have to be handled by you in the program. Whereas, in batch input session, your program's job is to just create the session, after that everything is standard SAP system's responsibility.

Ideally, you should do a call transaction if the resources are not a problem and if it fails, put the errored transaction into a session.

You can decide based on the data volume that your BDC is processing. If data volume is high go for session else call transaction will do.The call transaction updates will be instantaneous where as session needs to be processed explictly after creation.

Session Method

1) Session method supports both small amount of data aswell as large amount of data

2) data processing is asynchronus and data updation is synchronus.

3) it process multiple apllication while perfomaning validations.

4) in session method data will be updated in data base only after processing session only.

5) system provide by default logfile for handling error records.

6) it supports both foreground aswell as background process

in bdc we use FM ...

bdc_open_group " for creating Session

bdc_insert " adding transaction and bdcdata table for updating database

bdc_close_group " for closing Session

Call Transaction

1) Call transaction exclusively for small amout of data

2) it supports only one apllication while perfoming validations

3) there is no default logfile, We can explicitly provide logic for creating logfile for handling error records.

we can create logfile by using structure....BDCMSGCOLL

4) it doesn't support background processing.

5) data processing is synchronous and Data updation is Synchronous( default), in

this method also supports daya updation in asynchronus process also.

syntax:

Call transaction <transaction-name> using BDCDATA

mode <A/N/E>

update <L/A/S>

messages into BDCMSGCOLL.

BDC:

Batch Data Communication (BDC) is the process of transferring data from one SAP System to another SAP system or from a non-SAP system to SAP System.

Features :

BDC is an automatic procedure.

This method is used to transfer large amount of data that is available in electronic medium.

BDC can be used primarily when installing the SAP system and when transferring data from a legacy system (external system).

BDC uses normal transaction codes to transfer data.

Types of BDC :

CLASSICAL BATCH INPUT (Session Method)

CALL TRANSACTION

BATCH INPUT METHOD:

This method is also called as ‘CLASSICAL METHOD’.

Features:

Asynchronous processing.

Synchronous Processing in database update.

Transfer data for more than one transaction.

Batch input processing log will be generated.

During processing, no transaction is started until the previous transaction has been written to the database.

CALL TRANSACTION METHOD :

This is another method to transfer data from the legacy system.

Features:

Synchronous processing. The system performs a database commit immediately before and after the CALL TRANSACTION USING statement.

Updating the database can be either synchronous or asynchronous. The program specifies the update type.

Transfer data for a single transaction.

Transfers data for a sequence of dialog screens.

No batch input processing log is generated.

For BDC:

http://myweb.dal.ca/hchinni/sap/bdc_home.htm

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&;

http://www.sap-img.com/abap/learning-bdc-programming.htm

http://www.sapdevelopment.co.uk/bdc/bdchome.htm

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm

http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html

Check these link:

http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm

http://www.sap-img.com/abap/question-about-bdc-program.htm

http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/

http://www.planetsap.com/bdc_main_page.htm

Check the following links:

http://www.sap-img.com/bdc.htm

See below example code :

Call three FM : BDC_OPEN_GROUP,BDC_INSERT and BDC_CLOSE_GROUP.

Once you execute the program and it creates the session at SM35 Transaction.

************************************************************************

Report : ZMPPC011

Type : Data upload

Author : Chetan Shah

Date : 05/05/2005

Transport : DV3K919557

Transaction: ??

Description: This ABAP/4 Program creates new Production Versions

(C223). It accepts tab-delimited spreadsheet input and

creates BDC sessions.

*

************************************************************************

Modification Log

Date Programmer Request # Description

************************************************************************

06/10/2005 Chetan Shah DV3K919557 Initial coding

************************************************************************

report zmppc011 no standard page heading line-size 120 line-count 55

message-id zz.

pool of form routines

include zmppn001.

Define BDC Table Structure

data: begin of itab_bdc_tab occurs 0.

include structure bdcdata.

data: end of itab_bdc_tab.

Input record layout of Leagcy File

data: begin of itab_xcel occurs 0,

matnr(18) type c,

werks(4) type c,

alnag(2) type c,

verid(4) type c,

text1(40) type c,

bstmi like mkal-bstmi,

bstma like mkal-bstma,

adatu(10) type c,

bdatu(10) type c,

stlal(2) type c,

stlan(1) type c,

serkz(1) type c,

mdv01(8) type c,

elpro(4) type c,

alort(4) type c,

end of itab_xcel.

data: begin of lt_pp04_cache occurs 0,

matnr like itab_xcel-matnr,

werks like itab_xcel-werks,

alnag like itab_xcel-alnag,

plnnr like mapl-plnnr,

arbpl like crhd-arbpl,

ktext like crtx-ktext,

end of lt_pp04_cache.

data: v_ssnnr(4) type n,

v_lines_in_xcel like sy-tabix,

v_ssnname like apqi-groupid,

v_trans_in_ssn type i,

wa_xcel LIKE itab_xcel,

l_tabix like sy-tabix,

v_matnr like rc27m-matnr,

v_plnnr like mapl-plnnr,

v_plnal like mapl-plnal,

v_tcode like sy-tcode value 'C223',

v_plnty like plas-plnty value 'R',

v_objty like crhd-objty value 'A',

v_plpo_steus like plpo-steus value 'PP04',

v_verwe like crhd-verwe value '0007'.

Parameters

selection-screen: skip 3.

selection-screen: begin of block 1 with frame.

*

parameters: p_name like rlgrap-filename

default 'C:\My Documents\InputFile.txt'

obligatory,

bdc session name prefix

p_bdcpfx(6) default 'ZPVCRT'

obligatory,

number for transction per BDC session

p_trnssn type i

default 2000 obligatory,

retain the BDC session after successfull execution

p_keep like apqi-qerase

default 'X',

user who will be executing BDC session

p_uname like apqi-userid

default sy-uname

obligatory.

*

selection-screen: end of block 1.

*

********************************************************

*

possible entry list (F4 dropdown) for input file name

at selection-screen on value-request for p_name.

*-SELECT FILE FROM USERS LOCAL PC

call function 'WS_FILENAME_GET'

exporting

DEF_FILENAME = ' '

def_path = 'C:\Temp\'

mask = ',.,..'

mode = 'O'

title = 'Select File '(007)

importing

filename = p_name

RC =

exceptions

inv_winsys = 1

no_batch = 2

selection_cancel = 3

selection_error = 4

others = 5.

if sy-subrc 0.

MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.

endif.

*

********************************************************

*

begin the show

*

start-of-selection.

read data from input file

perform transfer_xcel_to_itab.

*

loop at itab_xcel.

hang on to xcel line num

l_tabix = sy-tabix.

each line in the xcel file marks begining of new prod.version defn

if num-of-trnas-in-session = 0, create new BDC session

if v_trans_in_ssn is initial.

perform bdc_session_open.

endif.

begin new bdc script for rtg create trans

fill in bdc-data for prod.version maintenance screens

perform bdc_build_script.

insert the bdc script as a BDC transaction

perform bdc_submit_transaction.

keep track of how many BDC transactions were inserted in the BDC

session

add 1 to v_trans_in_ssn.

if the user-specified num of trans in BDC session is reached OR

if end of input file is reached, close the BDC session

if v_trans_in_ssn = p_trnssn or

l_tabix = v_lines_in_xcel.

perform bdc_session_close.

clear v_trans_in_ssn.

endif.

endloop.

top-of-page.

call function 'Z_HEADER'

EXPORTING

FLEX_TEXT1 =

FLEX_TEXT2 =

FLEX_TEXT3 =

.

FORM TRANSFER_XCEL_TO_ITAB *

Transfer Xcel Spreadsheet to SAP Internal Table * form transfer_xcel_to_itab.

*

Read the tab-delimited file into itab

call function 'WS_UPLOAD'

exporting

filename = p_name

filetype = 'DAT'

IMPORTING

filelength = flength

tables

data_tab = itab_xcel

exceptions

conversion_error = 1

file_open_error = 2

file_read_error = 3

invalid_table_width = 4

invalid_type = 5

no_batch = 6

unknown_error = 7

others = 8.

*

if sy-subrc = 0.

sort the data

sort itab_xcel by matnr werks.

clear v_lines_in_xcel.

if no data in the file - error out

describe table itab_xcel lines v_lines_in_xcel.

if v_lines_in_xcel is initial.

write: / 'No data in input file'.

stop.

endif.

else.

if file upload failed - error out

write: / 'Error reading input file'.

stop.

endif.

endform.

FORM BDC_SESSION_OPEN *

Open BDC Session * form bdc_session_open.

create bdc session name = prefix-from-selectn-screen + nnnn

add 1 to v_ssnnr.

concatenate p_bdcpfx v_ssnnr into v_ssnname.

open new bdc session

call function 'BDC_OPEN_GROUP'

exporting

client = sy-mandt

group = v_ssnname

keep = p_keep

user = p_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.

endform.

FORM BDC_BUILD_SCRIPT *

Build BDC * form bdc_build_script.

data: l_arbpl like crhd-arbpl,

l_text1 like mkal-text1,

l_mdv01 like mkal-mdv01,

l_mapl like mapl.

clear bdc-data itab - begin of new bdc transaction

clear itab_bdc_tab.

refresh itab_bdc_tab.

*

read material cross reference tables to determine sap part#

clear : v_matnr, v_plnnr, v_plnal.

perform read_matnr_cross_ref using itab_xcel-matnr

itab_xcel-werks

changing v_matnr.

*

determine the version description to use

if itab_xcel-text1 is initial.

l_text1 = itab_xcel-verid.

else.

l_text1 = itab_xcel-text1.

endif.

determine the routing group# and group ctr# to use

perform read_routing .

*

determine the production line to use

if itab_xcel-mdv01 is initial.

if not provided in the file then:

prod line = work ctr on the last PP04 op of the rtg determined above

perform read_wc_on_last_pp04 using v_plnnr v_plnal

changing l_mdv01.

NOTE: when executing the above form\routine, if v_plnnr is initial

or v_plnal is initial, THEN l_mdv01 will automatically be

returned blank (ie initial)

else.

l_mdv01 = itab_xcel-mdv01.

endif.

*

build bdc script

perform bdc_build_script_record

*

fill in initial screen

using: 'X' 'SAPLCMFV' '1000',

' ' 'BDC_OKCODE' '=ENTE',

' ' 'MKAL-WERKS' itab_xcel-werks,

' ' 'MKAL-MATNR' v_matnr,

' ' 'MKAL_ADMIN-DISPO' space,

' ' 'MKAL-PLNNR' space,

' ' 'MKAL_ADMIN-STTAG' space,

' ' 'MKAL-PLNNG' space,

' ' 'MKAL-MDV01' space,

' ' 'MKAL-PLNNM' space,

click create button on initial screen and go to detail screen

'X' 'SAPLCMFV' '1000',

' ' 'BDC_OKCODE' '=CREA',

fill in the detail screen and go back to initial screen

'X' 'SAPLCMFV' '2000',

' ' 'BDC_OKCODE' '=CLOS',

' ' 'MKAL_EXPAND-MATNR' v_matnr,

' ' 'MKAL_EXPAND-VERID' itab_xcel-verid,

' ' 'MKAL_EXPAND-TEXT1' l_text1,

' ' 'MKAL_EXPAND-BSTMI' itab_xcel-bstmi,

' ' 'MKAL_EXPAND-BSTMA' itab_xcel-bstma,

' ' 'MKAL_EXPAND-ADATU' itab_xcel-adatu,

' ' 'MKAL_EXPAND-BDATU' itab_xcel-bdatu,

' ' 'MKAL_EXPAND-PLTYG' v_plnty,

' ' 'MKAL_EXPAND-PLNNG' v_plnnr,

' ' 'MKAL_EXPAND-ALNAG' v_plnal,

' ' 'MKAL_EXPAND-STLAL' itab_xcel-stlal,

' ' 'MKAL_EXPAND-STLAN' itab_xcel-stlan,

' ' 'MKAL_EXPAND-SERKZ' itab_xcel-serkz,

' ' 'MKAL_EXPAND-MDV01' l_mdv01,

' ' 'MKAL_EXPAND-ELPRO' itab_xcel-elpro,

' ' 'MKAL_EXPAND-ALORT' itab_xcel-alort,

save the production version from initial screen

'X' 'SAPLCMFV' '1000',

' ' 'BDC_OKCODE' '=SAVE'.

endform.

FORM BDC_SUBMIT_TRANSACTION *

Submit BDC Session * form bdc_submit_transaction.

Load BDC script as a trqansction in BDC session

call function 'BDC_INSERT'

exporting

tcode = v_tcode

tables

dynprotab = itab_bdc_tab

exceptions

internal_error = 01

not_open = 02

queue_error = 03

tcode_invalid = 04.

endform.

FORM BDC_BUILD_SCRIPT_RECORD * form bdc_build_script_record using dynbegin name value.

clear itab_bdc_tab.

if dynbegin = 'X'.

move: name to itab_bdc_tab-program,

value to itab_bdc_tab-dynpro,

'X' to itab_bdc_tab-dynbegin.

else.

move: name to itab_bdc_tab-fnam,

value to itab_bdc_tab-fval.

shift itab_bdc_tab-fval left deleting leading space.

endif.

append itab_bdc_tab.

endform.

FORM BDC_SESSION_CLOSE *

Close BDC Session * form bdc_session_close.

close the session

call function 'BDC_CLOSE_GROUP'

exceptions

not_open = 1

queue_error = 2

others = 3.

skip 2.

if sy-subrc ne 0.

write: / 'Error Closing BDC Session ' , 'RETURN CODE: ', sy-subrc.

else.

write : / 'Session created:', v_ssnname,

50 '# of transactions:', v_trans_in_ssn.

endif.

endform.

&----

*& Form read_routing_cache

&----

*FORM read_routing_cache USING pi_matnr

pi_werks

pi_alnag

pi_verid

pi_mdv01.

*

DATA: BEGIN OF lt_plpo OCCURS 0,

vornr LIKE plpo-vornr,

objty LIKE crhd-objty,

objid LIKE crhd-objid,

arbpl LIKE crhd-arbpl,

END OF lt_plpo,

l_mapl_plnnr LIKE mapl-plnnr.

*

determine the routing group#

CLEAR lt_pp04_cache.

chk if its in the cache first, if not then get it from MAPL table

and put it in the cache

READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr

werks = pi_werks

alnag = pi_alnag.

IF sy-subrc = 0.

do nothing - lt_pp04_cache header line has rtg#

ELSE.

get the routing group # from MAPL

SELECT plnnr INTO l_mapl_plnnr

FROM mapl UP TO 1 ROWS

WHERE matnr = pi_matnr AND

werks = pi_werks AND

plnty = 'R' AND

plnal = pi_alnag AND

loekz = space.

ENDSELECT.

put it in the cache internal table

IF NOT l_mapl_plnnr IS INITIAL.

lt_pp04_cache-matnr = pi_matnr.

lt_pp04_cache-werks = pi_werks.

lt_pp04_cache-alnag = pi_alnag.

lt_pp04_cache-plnnr = l_mapl_plnnr.

APPEND lt_pp04_cache.

ENDIF.

*

if the rtg# was determined AND

*

o the work center was not determined yet AND

o work center was really needed for this line in the input file

then

*

o read the work center from last PP04 operation on the routing

o update the cache accordingly

*

IF NOT lt_pp04_cache-plnnr IS INITIAL AND

lt_pp04_cache-arbpl IS INITIAL AND

( pi_verid IS INITIAL OR

pi_mdv01 IS INITIAL ).

*

read the last PP04 operation

CLEAR lt_plpo.

REFRESH lt_plpo.

SELECT vornr e_{objty e}objid e~arbpl

INTO CORRESPONDING FIELDS OF TABLE lt_plpo

FROM plas AS b

INNER JOIN plpo AS c

ON b_{plnty = c}plnty AND

b_{plnnr = c}plnnr AND

b_{zaehl = c}zaehl

INNER JOIN crhd AS e

ON c_{arbid = e}objid

WHERE b~plnty = v_plnty AND

b~plnnr = lt_pp04_cache-plnnr AND

b~plnal = lt_pp04_cache-alnag AND

c~loekz = space AND

c~steus = v_plpo_steus AND

e~objty = v_objty AND

e~werks = lt_pp04_cache-werks AND

e~verwe = v_verwe.

SORT lt_plpo BY vornr DESCENDING.

READ TABLE lt_plpo INDEX 1.

**

IF NOT lt_plpo-arbpl IS INITIAL.

lt_pp04_cache-arbpl = lt_plpo-arbpl.

read work center description

SELECT SINGLE ktext INTO lt_pp04_cache-ktext

FROM crtx WHERE objty = lt_plpo-objty AND

objid = lt_plpo-objid AND

spras = sy-langu.

the following read will get the index of the correct record to be

updated in the cache

READ TABLE lt_pp04_cache

WITH KEY matnr = pi_matnr

werks = pi_werks

alnag = pi_alnag.

MODIFY lt_pp04_cache

INDEX sy-tabix

TRANSPORTING arbpl ktext.

ENDIF.

*

*ENDFORM. " read_last_pp04_operation_cache

&----

*& Form read_routing

&----

form read_routing.

data: begin of lt_mapl occurs 0,

plnnr like mapl-plnnr,

plnal like mapl-plnal,

end of lt_mapl,

l_arbpl like crhd-arbpl.

get all the rtg# and grp ctr# from MAPL

select plnnr plnal

into corresponding fields of table lt_mapl

from mapl

where matnr = v_matnr and

werks = itab_xcel-werks and

plnty = v_plnty and "Rate Routing

loekz = space. "with del flag = OFF

sort lt_mapl by plnal.

if not itab_xcel-verid is initial.

if the verid=0001 then use the 1st good rtg-grp# and grp-ctr#

if itab_xcel-verid = '0001'.

read table lt_mapl index 1.

v_plnnr = lt_mapl-plnnr.

v_plnal = lt_mapl-plnal.

else.

if the verid0001 then use the rtg-grp# and grp-ctr# of the routing

whose work center on the last PP04 operation matches the given verid

loop at lt_mapl.

clear l_arbpl.

get the work center from the last PP04 operation

perform read_wc_on_last_pp04 using lt_mapl-plnnr

lt_mapl-plnal

changing l_arbpl.

*

if itab_xcel-verid = l_arbpl.

v_plnnr = lt_mapl-plnnr.

v_plnal = lt_mapl-plnal.

exit.

endif.

endloop.

endif.

else.

do nothing

endif.

For version IDs that are other then '0000' or 'ZWIP' :--

if itab_xcel-verid NE '0000' and

itab_xcel-verid NE 'ZWIP'.

if routing group# or group counter was not determined, make the

valid-to date 99/99/9999 so that the BDC, on execution, errors out.

if v_plnnr is initial or

v_plnal is initial.

itab_xcel-bdatu = '99/99/9999'.

endif.

determine the routing group#

CLEAR lt_pp04_cache.

chk if its in the cache first, if not then get it from MAPL table

and put it in the cache

READ TABLE lt_pp04_cache WITH KEY matnr = pi_matnr

werks = pi_werks

alnag = pi_alnag.

IF sy-subrc = 0.

do nothing - lt_pp04_cache header line has rtg#

ELSE.

get the routing group # from MAPL

put it in the cache internal table

IF NOT l_mapl_plnnr IS INITIAL.

lt_pp04_cache-matnr = pi_matnr.

lt_pp04_cache-werks = pi_werks.

lt_pp04_cache-alnag = pi_alnag.

lt_pp04_cache-plnnr = l_mapl_plnnr.

APPEND lt_pp04_cache.

ENDIF.

*

if the rtg# was determined AND

*

o the work center was not determined yet AND

o work center was really needed for this line in the input file

then

*

o read the work center from last PP04 operation on the routing

o update the cache accordingly

*

IF NOT lt_pp04_cache-plnnr IS INITIAL AND

lt_pp04_cache-arbpl IS INITIAL AND

( pi_verid IS INITIAL OR

pi_mdv01 IS INITIAL ).

*

read the last PP04 operation

CLEAR lt_plpo.

REFRESH lt_plpo.

SELECT vornr e_{objty e}objid e~arbpl

INTO CORRESPONDING FIELDS OF TABLE lt_plpo

FROM plas AS b

INNER JOIN plpo AS c

ON b_{plnty = c}plnty AND

b_{plnnr = c}plnnr AND

b_{zaehl = c}zaehl

INNER JOIN crhd AS e

ON c_{arbid = e}objid

WHERE b~plnty = v_plnty AND

b~plnnr = lt_pp04_cache-plnnr AND

b~plnal = lt_pp04_cache-alnag AND

c~loekz = space AND

c~steus = v_plpo_steus AND

e~objty = v_objty AND

e~werks = lt_pp04_cache-werks AND

e~verwe = v_verwe.

SORT lt_plpo BY vornr DESCENDING.

READ TABLE lt_plpo INDEX 1.

**

IF NOT lt_plpo-arbpl IS INITIAL.

lt_pp04_cache-arbpl = lt_plpo-arbpl.

read work center description

SELECT SINGLE ktext INTO lt_pp04_cache-ktext

FROM crtx WHERE objty = lt_plpo-objty AND

objid = lt_plpo-objid AND

spras = sy-langu.

the following read will get the index of the correct record to be

updated in the cache

READ TABLE lt_pp04_cache

WITH KEY matnr = pi_matnr

werks = pi_werks

alnag = pi_alnag.

MODIFY lt_pp04_cache

INDEX sy-tabix

TRANSPORTING arbpl ktext.

ENDIF.

endform. " read_last_pp04_operation_cache

&----

*& Form read_wc_on_last_pp04

&----

form read_wc_on_last_pp04 using pi_plnnr

pi_plnal

changing pe_arbpl.

data: begin of lt_plpo occurs 0,

vornr like plpo-vornr,

objty like crhd-objty,

objid like crhd-objid,

arbpl like crhd-arbpl,

end of lt_plpo.

get all the PP04 operations for the given rtg# & grp-ctr#

select vornr e_{objty e}objid e~arbpl

into corresponding fields of table lt_plpo

from plas as b

inner join plpo as c

on b_{plnty = c}plnty and

b_{plnnr = c}plnnr and

b_{zaehl = c}zaehl

inner join crhd as e

on c_{arbid = e}objid

where b~plnty = v_plnty and "Rate Routing

b~plnnr = pi_plnnr and

b~plnal = pi_plnal and

c~loekz = space and "Oper Del Flag = OFF

c~steus = v_plpo_steus and "PP04

e~objty = v_objty. "WC Obj Type = 'A'

read the last operation

sort lt_plpo by vornr descending.

read table lt_plpo index 1.

pe_arbpl = lt_plpo-arbpl.

endform. " read_wc_on_last_pp04

Goto LSMW-> Select Direct Input method in 1st step. These are the standard programs for data transfer.

Otherwise goto SPRO->SAP Reference IMG-> Under this you'll find standard data transfer programs module wise.

regs,

Hema.

By Category

Related Content

Activity Groups

Industry Groups

Influence and Feedback Groups

Interest Groups

Location Groups

Customer Only Groups

Forums

Related Resources

Products

Learning and Support

About

My Account

My Account

BDC