01-31-2008 9:03 AM
Can u explain me about below objects i.e what tables , t.codes used , etc.....
Developed a report to display vendor details on basic list and Purchasing Header details for the selected vendor in the next secondary list and display the purchasing items for the selected purchase document in next list and display the material details for the selected material in next list.
Developed a complex report to display Customer wise sales order report, selection screen criteria were customer number range and order number range.
Developed a BDC program for uploading the data of sales orders using transaction VA01.
Developed a BDC program for uploading the material master data from the legacy system to SAP system through the transaction code MM02.
01-31-2008 9:11 AM
hi Mujeeb,
why did you include these into your resume, if you have no idea how to do it? Better to be honest...
ec
01-31-2008 9:42 AM
Transaction SE38.
>Classical Reporting
>>A classic report is a program that generates a single list, >>which must contain all of the required detail information.
>>
>>1) This procedure may result in extensive lists from which >>the user has to pick the relevant data.
>>
>>
>>2) For background processing, this is the only possible >>method. After starting a background job, there is no way of >>influencing the program.
>>
>>3) The desired selections must be made beforehand and >>the list must provide detailed information.
>>
>>4) For dialog sessions, there are no such restrictions.
>>
>>5) The user is present during the execution of the program >>and can control and manipulate the program flow directly.
>>
>>6) To be able to use all advantages of the online >>environment, classical reporting was developed into >>interactive reporting.
>*Interactive Reporting.
>>
>>As the name suggests, the user can Interact with the >>report. We can have a drill down into the report data. For >>example, Column one of the report displays the material >>numbers, and the user feels that he needs some more >>specific data about the vendor for that material, he can >>HIDE that data under those material numbers. And when >>the user clicks the material number, another report >>(actually sub report/secondary list) which displays the >>vendor details will be displayed.
>>
>>We can have a basic list (number starts from 0) and 20 >>secondary lists (1 to 21). Events associated with >>Interactive Reports are: 1. AT LINE-SELECTION 2. AT >>USER-COMMAND 3. AT PF<key> 4. TOP-OF-PAGE >>DURING LINE-SELECTION. HIDE statement holds the >>data to be displayed in the secondary list. sy-lisel : >>contains data of the selected line. sy-lsind : contains the >>level of report (from 0 to 21)
>>
>>Interactive Report Events:
>>
>>AT LINE-SELECTION : This Event triggers when we >>double click a line on the list, when the event is triggered a >>new sublist is going to be generated. Under this event >>what ever the statements that are been return will be >>displayed on newly generated sublist.
>>AT PFn: For predefined function keys...
>>AT USER-COMMAND : It provides user functions keys.
01-31-2008 9:47 AM
HI
SD tables
http://www.erpgenie.com/abap/tables_sd.htm
MM tables
MARA - Material master
MARC - material master plant level
MVKE - Material master sales org details
EKKO - Purchasing document header
EKPO - Purchasing document line item
EKET - Purchasing document schedule lines
EKES - Purchasing document confirmations
EKBE - Purchasing document history
EBAN - Purchase requisition
EINE - purchase info record
MKPF - Material document movement header
MSEG - Material document movement line item
RBKP - Invoice document header
RSEG - invoice document line item
Also:
http://www.erpgenie.com/abap/tables_mm.htm
SD Tables:
1. VA is the package where we can find
SD tables.
2.
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
The above two are the main tables.
PVINX Index of New Sales Documents for Product Proposal
T176T Sales Documents: Customer Order Types: Texts
T661T Difference Tolerances for External and Internal Conditions
TERRF Erroneous Data for First Data Transfer
TVDC Delivery Times:Categories
TVDCT Delivery Times: Texts
TVRMAVK Repair Procedure: Actions
TVRMAVT Repair Procedure: Action Texts
TVSTAT Display/Maintain Status in Sales Overview
TVVFS Variant Matching Procedure: Procedures
TVVFT Variant Determination Procedure: Texts
TVVFZ Variant Matching Procedure: Time Control
VAKGU Sales Index: Quotation Validity
VAKPA Sales Index: Orders by Partner Function
VAPMA Sales Index: Order Items by Material
VBAG Sales Document: Release Data by Schedule Line in Sch.Agrmt.
VBAK Sales Document: Header Data
VBAP Sales Document: Item Data
VBEH Schedule line history
VBEP Sales Document: Schedule Line Data
VBKD Sales Document: Business Data
VBKFZ Cumulative Quantity Corrections
VBLB Sales document: Release order data
VBMUE Sales Document: Characteristic Overview
VBMUET Sales Document: Characteristic Overview Description
VBMUEZ Sales Document: Characteristic Overview Assignments
VBPK Sales Document: Product Proposal Header
VBPV Sales Document: Product Proposal
VBREF SD Object Link to Item References
VBSN Change status relating to scheduling agreements
VBSP SD Document Item for Models of Material Structures
VBUV Sales Document: Incompletion Log
VCRSELA Cross Selling Analysis
VCRSELA_RES Cross Selling Analysis: Results
VEDA Contract Data
VEPVG Delivery Due Index
VKDFS SD Index: Billing Initiator
VLPKM Scheduling agreements by customer material
refer this link for table and relation b/w them
http://www.erpgenie.com/abap/tables_sd.htm
FI tables
http://www.erpgenie.com/abap/tables_fi.htm
PS tables
http://www.erpgenie.com/abap/tables_ps.htm
PP tables
http://www.erpgenie.com/abap/tables_pp.htm
http://www.erpgenie.com/abap/tables.htm
Here is the list of SD transactions. One can create BDCs for all the TCs:
VA11 / 12/ 13 - Sales Quatation Creation / Change / Display
VA01 / 02/ 03 - Sales Order Creation / Change / Display.
VL01 / 02/ 03 - Delivery Creation / Change / Display.
ST01 / 02/ 03 - Shipment Creation / Change / Display
VF01 / 02/ 03 - Invoice Creation / Change / Display
W1SAP MM T CODES
All transaction is stored in table TSTC.
Transaction for MM module start with M.
IH09 - Display Material
MM01 - Create Material
MM02 - Change Material
MM03 - Display Material
MM50 - List Extendable Materials
MMBE - Stock Overview
MMI1 - Create Operating Supplies
MMN1 - Create Non-Stock Material
MMS1 - Create Service
MMU1 - Create Non-Valuated Material
Purchase Requisition:-
ME51N - Create Purchase Requisition
ME52N - Change Purchase Requisition
ME53N - Display Purchase Requisition
ME5A - Purchase Requisitions: List Display
ME5J - Purchase Requisitions for Project
ME5K - Requisitions by Account Assignment
MELB - Purch. Transactions by Tracking No.
ME56 - Assign Source to Purch. Requisition
ME57 - Assign and Process Requisitions
ME58 - Ordering: Assigned Requisitions
ME59 - Automatic Generation of POs
ME54 - Release Purchase Requisition
ME55 - Collective Release of Purchase Reqs.
ME5F - Release Reminder: Purch. Requisition
Reservation:-
MB21 - Create Reservation
MB22 - Change Reservation
MB23 - Display Reservation
MB24 - Reservations by Material
MB25 - Reservations by Account Assignment
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MBRL - Return Delivery per Mat. Document
MB1C - Other Goods Receipts
MB90 - Output Processing for Mat. Documents
MB1B - Transfer Posting
MIBC - ABC Analysis for Cycle Counting
MI01 - Create Physical Inventory Document
MI02 - Change Physical Inventory Document
MI03 - Display Physical Inventory Document
MI31 - Batch Input: Create Phys. Inv. Doc.
MI32 - Batch Input: Block Material
MI33 - Batch Input: Freeze Book Inv.Balance
MICN - Btch Inpt:Ph.Inv.Docs.for Cycle Ctng
MIK1 - Batch Input: Ph.Inv.Doc.Vendor Cons.
MIQ1 - Batch Input: PhInvDoc. Project Stock
MI21 - Print physical inventory document
MI04 - Enter Inventory Count with Document
MI05 - Change Inventory Count
MI06 - Display Inventory Count
MI09 - Enter Inventory Count w/o Document
MI34 - Batch Input: Enter Count
MI35 - Batch Input: Post Zero Stock Balance
MI38 - Batch Input: Count and Differences
MI39 - Batch Input: Document and Count
MI40 - Batch Input: Doc., Count and Diff.
MI08 - Create List of Differences with Doc.
MI10 - Create List of Differences w/o Doc.
MI20 - Print List of Differences
MI11 - Physical Inventory Document Recount
MI07 - Process List of Differences
MI37 - Batch Input: Post Differences
CT01 - Create Characteristic
CT02 - Change Characteristic
CT03 - Display Characteristic
CL01 - Create Class
CL02 - Classes
CL03 - Display Class
CL04 - Delete Class
CL2B - Class Types
ME01 - Maintain Source List
ME03 - Display Source List
ME04 - Changes to Source List
ME05 - Generate Source List
ME06 - Analyze Source List
ME07 - Reorganize Source List
ME08 - Send Source List
ME0M - Source List for Material
ME11 - Create Purchasing Info Record
ME12 - Change Purchasing Info Record
ME13 - Display Purchasing Info Record
ME14 - Changes to Purchasing Info Record
ME15 - Flag Purch. Info Rec. for Deletion
ME16 - Purchasing Info Recs. for Deletion
ME17 - Archive Info Records
ME18 - Send Purchasing Info Record
ME1A Archived Purchasing Info Records
ME1B Redetermine Info Record Price
ME1E Quotation Price History
ME1L Info Records Per Vendor
ME1M Info Records per Material
ME1P Purchase Order Price History
ME1W Info Records Per Material Group
ME1X Buyer's Negotiation Sheet for Vendor
ME1Y Buyer's Negotiat. Sheet for Material
ME21 Create Purchase Order
ME21N Create Purchase rder
ME22 Change Purchase Order
ME22N Change Purchase Order
ME23 Display Purchase Order
ME23N Display Purchase Order
ME24 Maintain Purchase Order Supplement
ME25 Create PO with Source Determination
ME26 Display PO Supplement (IR)
ME27 Create Stock Transport Order
ME28 Release Purchase Order
ME29N Release purchase order
ME2A Monitor Confirmations
ME2B POs by Requirement Tracking Number
ME2C Purchase Orders by Material Group
ME2J Purchase Orders for Project
ME2K Purch. Orders by Account Assignment
ME2L Purchase Orders by Vendor
ME2M Purchase Orders by Material
ME2N Purchase Orders by PO Number
ME2O SC Stock Monitoring (Vendor)
ME2S Services per Purchase Order
ME2V Goods Receipt Forecast
ME2W Purchase Orders for Supplying Plant
ME308 Send Contracts with Conditions
ME31 Create Outline Agreement
ME31K Create Contract
ME31L Create Scheduling Agreement
ME32 Change Outline Agreement
ME32K Change Contract
ME32L Change Scheduling Agreement
ME33 Display Outline Agreement
ME33K Display Contract
ME33L Display Scheduling Agreement
ME34 Maintain Outl. Agreement Supplement
ME34K Maintain Contract Supplement
ME34L Maintain Sched. Agreement Supplement
ME35 Release Outline Agreement
ME35K Release Contract
ME35L Release Scheduling Agreement
ME36 Display Agreement Supplement (IR)
ME37 Create Transport Scheduling Agmt.
ME38 Maintain Sched. Agreement Schedule
ME39 Display Sched. Agmt. Schedule (TEST)
ME3A Transm. Release Documentation Record
ME3B Outl. Agreements per Requirement No.
ME3C Outline Agreements by Material Group
ME3J Outline Agreements per Project
ME3K Outl. Agreements by Acct. Assignment
ME3L Outline Agreements per Vendor
ME3M Outline Agreements by Material
ME3N Outline Agreements by Agreement No.
ME3P Recalculate Contract Price
ME3R Recalculate Sched. Agreement Price
ME3S Service List for Contract
ME41 Create Request For Quotation
ME42 Change Request For Quotation
ME43 Display Request For Quotation
ME44 Maintain RFQ Supplement
ME45 Release RFQ
ME47 Create Quotation
ME48 Display Quotation
ME49 Price Comparison List
ME4B RFQs by Requirement Tracking Number
ME4C RFQs by Material Group
ME4L RFQs by Vendor
ME4M RFQs by Material
ME4N RFQs by RFQ Number
ME4S RFQs by Collective Number
ME51 Create Purchase Requisition
ME51N Create Purchase Requisition
ME52 Change Purchase Requisition
ME52N Change Purchase Requisition
ME52NB Buyer Approval: Purchase Requisition
ME53 Display Purchase Requisition
ME53N Display Purchase Requisition
ME54 Release Purchase Requisition
ME54N Release Purchase Requisition
ME55 Collective Release of Purchase Reqs.
ME56 Assign Source to Purch. Requisition
ME57 Assign and Process Requisitions
ME58 Ordering: Assigned Requisitions
ME59 Automatic Generation of POs
ME59N Automatic generation of POs
ME5A Purchase Requisitions: List Display
ME5F Release Reminder: Purch. Requisition
ME5J Purchase Requisitions for Project
ME5K Requisitions by Account Assignment
ME5R Archived Purchase Requisitions
ME5W Resubmission of Purch. Requisitions
ME61 Maintain Vendor Evaluation
ME62 Display Vendor Evaluation
ME63 Evaluation of Automatic Subcriteria
ME64 Evaluation Comparison
ME65 Evaluation Lists
ME6A Changes to Vendor Evaluation
ME6B Display Vendor Evaln. for Material
ME6C Vendors Without Evaluation
ME6D Vendors Not Evaluated Since...
ME6E Evaluation Records Without Weighting
ME6F Print
ME6G Vendor Evaluation in the Background
ME6H Standard Analysis: Vendor Evaluation
ME6Z Transport Vendor Evaluation Tables
ME80 Purchasing Reporting
ME80A Purchasing Reporting: RFQs
ME80AN General Analyses (A)
ME80F Purchasing Reporting: POs
ME80FN General Analyses (F)
ME80R Purchasing Reporting: Outline Agmts.
ME80RN General Analyses (L,K)
ME81 Analysis of Order Values
ME81N Analysis of Order Values
ME82 Archived Purchasing Documents
ME84 Generation of Sched. Agmt. Releases
ME84A Individual Display of SA Release
ME85 Renumber Schedule Lines
ME86 Aggregate Schedule Lines
ME87 Aggregate PO History
ME88 Set Agr. Cum. Qty./Reconcil. Date
ME91 Purchasing Docs.: Urging/Reminding
ME91A Urge Submission of Quotations
ME91E Sch. Agmt. Schedules: Urging/Remind.
ME91F Purchase Orders: Urging/Reminders
ME92 Monitor Order Acknowledgment
ME92F Monitor Order Acknowledgment
ME92K Monitor Order Acknowledgment
ME92L Monitor Order Acknowledgment
ME97 Archive Purchase Requisitions
ME98 Archive Purchasing Documents
ME99 Messages from Purchase Orders
ME9A Message Output: RFQs
ME9E Message Output: Sch. Agmt. Schedules
ME9F Message Output: Purchase Orders
ME9K Message Output: Contracts
ME9L Message Output: Sched. Agreements
MEAN Delivery Addresses
MEB0 Reversal of Settlement Runs
MEB1 Create Reb. Arrangs. (Subseq. Sett.)
MEB2 Change Reb. Arrangs. (Subseq. Sett.)
MEB3 Displ. Reb. Arrangs. (Subseq. Sett.)
MEB4 Settlement re Vendor Rebate Arrs.
MEB5 List of Vendor Rebate Arrangements
MEB6 Busn. Vol. Data, Vendor Rebate Arrs.
MEB7 Extend Vendor Rebate Arrangements
MEB8 Det. Statement, Vendor Rebate Arrs.
MEB9 Stat. Statement, Vendor Rebate Arrs.
MEBA Comp. Suppl. BV, Vendor Rebate Arr.
MEBB Check Open Docs., Vendor Reb. Arrs.
MEBC Check Customizing: Subsequent Sett.
MEBE Workflow Sett. re Vendor Reb. Arrs.
MEBF Updating of External Busn. Volumes
MEBG Chg. Curr. (Euro), Vend. Reb. Arrs.
MEBH Generate Work Items (Man. Extension)
MEBI Message, Subs.Settlem. - Settlem.Run
MEBJ Recompile Income, Vendor Reb. Arrs.
MEBK Message., Subs. Settlem.- Arrangment
MEBM List of settlement runs for arrngmts
MEBR Archive Rebate Arrangements
MEBS Stmnt. Sett. Docs., Vend. Reb. Arrs.
MEBT Test Data: External Business Volumes
MEBV Extend Rebate Arrangements (Dialog)
MECCP_ME2K For Requisition Account Assignment
MEDL Price Change: Contract
MEI1 Automatic Purchasing Document Change
MEI2 Automatic Document Change
MEI3 Recompilation of Document Index
MEI4 Compile Worklist for Document Index
MEI5 Delete Worklist for Document Index
MEI6 Delete purchasing document index
MEI7 Change sales prices in purch. orders
MEI8 Recomp. doc. index settlement req.
MEI9 Recomp. doc. index vendor bill. doc.
MEIA New Structure Doc.Ind. Cust. Sett.
MEIS Data Selection: Arrivals
MEK1 Create Conditions (Purchasing)
MEK2 Change Conditions (Purchasing)
MEK3 Display Conditions (Purchasing)
MEK31 Condition Maintenance: Change
MEK32 Condition Maintenance: Change
MEK33 Condition Maintenance: Change
MEK4 Create Conditions (Purchasing)
MEKA Conditions: General Overview
MEKB Conditions by Contract
MEKC Conditions by Info Record
MEKD Conditions for Material Group
MEKE Conditions for Vendor
MEKF Conditions for Material Type
MEKG Conditions for Condition Group
MEKH Market Price
MEKI Conditions for Incoterms
MEKJ Conditions for Invoicing Party
MEKK Conditions for Vendor Sub-Range
MEKL Price Change: Scheduling Agreements
MEKLE Currency Change: Sched. Agreements
MEKP Price Change: Info Records
MEKPE Currency Change: Info Records
MEKR Price Change: Contracts
MEKRE Currency Change: Contracts
MEKX Transport Condition Types Purchasing
MEKY Trnsp. Calc. Schema: Mkt. Pr. (Pur.)
MEKZ Trnsp. Calculation Schemas (Purch.)
MELB Purch. Transactions by Tracking No.
MEMASSIN Mass-Changing of Purch. Info Records
MEMASSPO Mass Change of Purchase Orders
MEMASSRQ Mass-Changing of Purch. Requisitions
MENU_MIGRATION Menu Migration into New Hierarchy
MEPA Order Price Simulation/Price Info
MEPB Price Info/Vendor Negotiations
MEPO Purchase Order
MEQ1 Maintain Quota Arrangement
MEQ3 Display Quota Arrangement
MEQ4 Changes to Quota Arrangement
MEQ6 Analyze Quota Arrangement
MEQ7 Reorganize Quota Arrangement
MEQ8 Monitor Quota Arrangements
MEQB Revise Quota Arrangement
MEQM Quota Arrangement for Material
MER4 Settlement re Customer Rebate Arrs.
MER5 List of Customer Rebate Arrangements
MER6 Busn. Vols., Cust. Reb. Arrangements
MER7 Extension of Cust. Reb. Arrangements
MER8 Det. Statement: Cust. Rebate Arrs.
MER9 Statement: Customer Reb. Arr. Stats.
MERA Comp. Suppl. BV, Cust. Rebate Arrs.
MERB Check re Open Docs. Cust. Reb. Arr.
MERE Workflow: Sett. Cust. Rebate Arrs.
MEREP_EX_REPLIC SAP Mobile: Execute Replicator
MEREP_GROUP SAP Mobile: Mobile Group
MEREP_LOG SAP Mobile: Activity Log
MEREP_MIG SAP Mobile: Migration
MEREP_MON SAP Mobile: Mobile Monitor
MEREP_PD SAP Mobile: Profile Dialog
MEREP_PURGE SAP Mobile: Purge Tool
MEREP_SBUILDER SAP Mobile: SyncBO Builder
MEREP_SCENGEN SAP Mobile: SyncBO Generator
MERF Updating of External Busn. Volumes
MERG Change Curr. (Euro) Cust. Reb. Arrs.
MERH Generate Work Items (Man. Extension)
MERJ Recomp. of Income, Cust. Reb. Arrs.
MERS Stmnt. Sett. Docs. Cust. Reb. Arrs.
MEU0 Assign User to User Group
MEU2 Perform Busn. Volume Comp.: Rebate
MEU3 Display Busn. Volume Comp.: Rebate
MEU4 Display Busn. Volume Comp.: Rebate
MEU5 Display Busn. Volume Comp.: Rebate
MEW0 Procurement Transaction
MEW1 Create Requirement Request
MEW10 Service Entry in Web
MEW2 Status Display: Requirement Requests
MEW3 Collective Release of Purchase Reqs.
MEW5 Collective Release of Purchase Order
MEW6 Assign Purchase Orders WEB
MEW7 Release of Service Entry Sheets
MEW8 Release of Service Entry Sheet
MEW9 mew9
MEWP Web based PO
MEWS Service Entry (Component)
ME_SWP_ALERT Display MRP Alerts (Web)
ME_SWP_CO Display Purchasing Pricing (Web)
ME_SWP_IV Display Settlement Status (Web)
ME_SWP_PDI Display Purchase Document Info (Web)
ME_SWP_PH Display Purchasing History (Web)
ME_SWP_SRI Display Schedule Releases (Web)
ME_WIZARD ME: Registration and Generation
PURCHASING TABLES
A501 Plant/Material
EBAN Purchase Requisition
EBKN Purchase Requisition Account Assignment
EKAB Release Documentation
EKBE History per Purchasing Document
EKET Scheduling Agreement Schedule Lines
EKKN Account Assignment in Purchasing Document
EKKO Purchasing Document Header
EKPO Purchasing Document Item
IKPF Header- Physical Inventory Document
ISEG Physical Inventory Document Items
LFA1 Vendor Master (General section)
LFB1 Vendor Master (Company Code)
NRIV Number range intervals
RESB Reservation/dependent requirements
T161T Texts for Purchasing Document Types
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.
01-31-2008 9:47 AM
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 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
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 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 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.
*--
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.
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.
Differences between Call Transaction and Sessions Method:
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.
6) generally used for back ground jobs.
7) at atime 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 atime we can update to a single screen.
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/