Category Archives: BDC

BDC
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 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.
Posted in BDC Leave a Comment

BDC
MAR 4

Posted by Manoj Kanwar Rathore

The early versions of R/3, SAP has been providing batch interfacing techniques. Among these techniques, Batch Data Communication (BDC) is the oldest one. BDC is not bi-directional; it is an integration tool in its typical form. It can only be used for uploading data into RJ3. BDC works through an ABAP program and works on the principle of simulating user input for transactional screen. The purpose of the Batch Data Communication is to transfer data. The BDC can transfer data from one SAP System to another SAP System or can transfer data from non-SAP System to SAP System too. To transfer data BDC uses normal transaction codes. Two methods are provided to BDC to do this work. SAP has provided two different types of methods for BDC to do its work. Among these, the first one is called the classical method or session method. Through this method the data can be read by the BDC program from a sequential dataset file. This sequential dataset file is stored in batchinput session. In order to .run the transaction in this session, what one needs is to execute the session. For this, follow these few steps: you can start and subsequently monitor the session firstly from System Services Batch Input or have the session run in the background. In this method to generate the required session, you have to use the function module BDC _ NSERT and BDC _CLOSE. In the second method the BDC has to use the ABAP statement CALL TRANSACTION USING statement to run a transaction. In the second method, unlike in the first type, you do not need BDC to create a session.