hai

Former Member · ‎10-10-2007

hai,

can any body will provide me the configuration steps of idocs,BDC

Former Member · ‎10-11-2007

Hi Kamtah,

BDC(Batch Input Session):Batch Data Communication

1. Screens will be called programmatically.

2. First sessions will be created then we'll run the seesions in SM35 transaction.

3. Synchronous database update. After the processing the session only database update will occur.

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.

Differences between Call Transaction and Sessions Method:

Session method.

1) Synchronous processing.

2) Can transfer large amount of data.

3) Processing is slower.

4) Error log is created

5) data is not updated until session is processed.

6) Generally used for back ground jobs.

7) At a time we can update to more than one screens.

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

6) for background n fore ground jobs.

7) At a time we can update to a single screen.

Direct Input method:

Without calling the screens but all the validations should be done and only for master datas upload.

1. Only for error free datas and also master data updation.

2. It will directly updates the database table. No screens involved.

3. Transaction BMVO or Program RBMVSHOW has been used.

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

IDOC:-

IDOCS:

IDOCS are intermediary documents which are like CARRIERS of the data.

IDOCs are safe to transfer data, but less volume of data. User is not allowed to access (modify) the data like PSA. IDOCs have 3 parts.

1. Control Record - SOURCE & TARGET details,

2. Data Record - Here comes your query....

Info IDOC - It contains all the technical details related to the data load i.e. Request NO, No of Data Packages, USER, DATE, TIME, LOGICAL SYSTEM, etc. Info IDOC is also ONE segment, the 1 sr segment.

Here data will not be there.

Data IDOC - These are the ones which hold the data. The total no of records are made into Data IDOCs i.e. if 99 records are there then 99 Data IDOCs will be there and all these will be divided into 99 segments.

Hence the total number of Segments in IDOC is 100.

Info IDOC + Data IDOCs = Total no of Segments

1 + 99 = 100.

3. Status Record - Here the status of the data transfer will be available.

Please check this online document for ALE and IDoc.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

Also check this links for additional information.

http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm

http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc

http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419

http://www.netweaverguru.com/EDI/HTML/IDocBook.htm

http://www.sapgenie.com/sapedi/index.htm

IDOC Creation - Manual:

If a batch job is not running. First thing is go into to code of the batch job and find out what type of IDOC's it is processing.

Let's assume, it is creating / processing DELINS type IDOC's, then follow the below steps:

Go to T-code WE02, input DELINS in the logical message, give date range of say 10 days or so and Direction = 2 and execute it. You will get a list of IDOC's

Then select any one of those IDOC"s in status 53 and go to T-code WE19 and input the same and execute.

Later in the same T-code you can change the sender and receiver parameters including the plant.

In the header level you need to change the delivery schedule number and release number. Put the same PO number as in the scheduling agreement. Enter values of sold to, ship to, partner description and customer material along with the desired quantity.

Then on the application tool bar you will find "Standard Inbound", click on this and check for the green light against the partner profile and click OK / Enter.

You will be processing the IDOC manually. Then once you get the IDOC number, input the new number in WE02 and execute to check the status. If it is not 53 status, then go to T-code BD87 and input that number and execute. Inside select the last line of status and click on "Process" icon to finally get the IDOC in Status 53 "Successfully Processed"

This is the standard process followed for processing IDOC's manually.

IDOC'S CONFIGURATION FOR SD

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

Former Member · ‎10-11-2007

Dear kamtah shaik

A small search on SDN SD forum will help you to answer your query.

I will suggest you to visit http://sap-img.com. It will give you the overview of all modules of SAP.

Moreover there is a separate section of FAQs with answers which will help you in great deal.

Hope this helps you.

Do award points if you found them useful.

Regards,

Rakesh

Former Member · ‎10-11-2007

Hi

For a BDC upload you need to write a program which created BDC sessions.

Steps:

1. Work out the transaction you would use to create the data manually.

2. Use transaction SHDB to record the creation of one material master data.

Click the New recording button or the Menu - Recording - Create

3. Save the recording, and then go back a screen and go to the overview.

4. Select the recording and click on Edit - Create Program. Give the program a Z name, and select transfer from recording.

5. Edit the program. You will see that all the data you entered is hard-coded into the program. You need to make the following changes:

5.1 After the start-of-selection, Call ws_upload to upload the file (the excel file needs to be saved as TAB separated).

5.2 After the open-group, Loop on the uploaded data. For each line, perform validation checks on the data, then modify the perform bdc_field commands to use the file data.

5.3. After perform bdc_transaction, add the endloop.

Execute the program. It will have options to create a batch session or to process directly.

These are all my finds . Might be it will be useful to you.

Direct call of transactions, session handling:

/nxxxx This terminates the current transaction, and starts transaction xxxx

/n This terminates the transaction. This generally corresponds to pressing F15 to go back.

/nend This termiantes all separate sessions and logs off (corresponds to System - Logoff).

/nex This terminates all separate sessions and logs off immediately (without any warning!).

/oxxxx This opens a new session and starts transaction xxxx in This session.

/o This lists existing sessions and allows deletion or opening of a new session.

/i This terminates the current session (corresponds to System End

/i1, /i2,... This terminates the session with the number given.

.xyzw Fast path: 'xyzw' refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).

Batch

The following commands can be entered in correction mode ('Process in foreground' or 'Display errors only') when processing a batch input session:

/n This terminates the current batch input transaction and characterizes it as

/bdel This deletes the current batch input transaction.

/bend This terminates batch input processing and sets the session to Failed

/bda This switches from Display errors only to Process in foreground

/bde This switches from Process in foreground to Display errors only

ABAP/4

/h This switches into debugging mode.

/hs This switches into debugging mode and activates the debugging of system functions.

Buffer

WARNING: Resetting buffers can significantly change the performance of the entire system for a long time.

It should therefore only be used where there is a good reason tdso. As of release 3.0B system administator authorization is required (authorization object (S_ADMI_FCD). The action is noted in the system log.

/$SYNC This resets all buffers of the application server

/$CUA This resets the CUA buffer of the application server

/$TAB This resets the TABLE buffers of the application server

/$NAM This resets the nametab buffer of the application server

/$DYNP This resets the screen buffer of the application server

ABAP Tips by: Vijay K.

What is recording?

As the word record implies, it mean recording the keystroke of the user input of a SAP transaction screen.

Why it is used?

It is normally used for mass update or uploading of data to the system.

What is its need?

It help to save time for the users who need to mass change the system data. For e.g. tax rate change announce by the country government.

How it is related with bdc?

It is related to bdc because bdc programming allows recording of user inputs.

<a href="http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm">BDC Example</a>

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.

A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.

IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.

An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system.

<a href="https://secure.topxml.com/biztalkutilities/walkthroughs/SAP%20IDoc%20Configuration.pdf">SAP IDoc Configuration</a>