"In ABAP it is very convenient to run a report using a Variant. Basically a report can have several Variants linked to it. If you use a variant then the data entry time is reduced considerably and this also reduces data entry errors. The load on the ABAP processing is also reduced. To create a Variant you may need the necessary authorizations. Most of the times while testing programs you will need to run a report using a variant and hence having the authorization to create a Variant is necessary. To create a Variant go to the main reporting screen, enter the name of the report for which you want to create the variant and select goto Variants option from the menu. The system displays the initial screen for the Variants. For creating a Variant you need to enter all the mandatory fields. Also you need to give a unique name for the Variant. Follow the naming convention rules. You may have to create several Variants for a particular report. Once a Variant is created you ca also schedule to run the report in the background using this Variant. For each variant that you create you need to give a brief description which will help to explain the purpose of the variant and help to distinguish the various Variants that you have created. You may want to protect your Variant by selecting the Protect Variant option. This option enables only the person who has created the Variant to change or delete it. While Running a report directly from the menu you can use the Run with Variant option and then select the desired variant from the dropdown list. Remember that Variants are report dependant. So to create a Variant you need to first create an ABAP report (Executable Program with selection screen). Once you successfully create all the variants for an ABAP report, you will save considerable amount of time which would otherwise have been spent in entering the same data again and again."
"SAP has provided two different types of methods for BDC to do its work. Among these the first one is called the classical method. This method is also called as the 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 batch-input sessions. In order to run the transaction in this session, What you need is to execute the session. For this follow these few steps. YOu an start and subsequently monitor the sessions firstly from System----> Service---->Batch input or have the sessions run in the background."
SAP R/3 can be interfaced with other systems using various techniques. EDI is one of them. For interfacing SAP R/3 with its partners (Vendors/Customers) the best way is using EDI. Please find below some of the important transaction codes used for IDOCs (intermediate document).
IDOC Monitoring
Transaction Code
Description
WE02
IDOC Display
WE05
IDOC List
WE07
IDOC Statistics
WE20
Maintain Partner Profiles Manually
BD82
Generate Partner Profiles Automatically
WE21
Port Definitions
SM59
RFC Destination
BD64
Maintain Customer Model
Message Control
Transaction Code
Description
NACE
Maintain condition records for various applications
VOK2
Message Control components for Sales and Distribution
VOK3
Message Control components for Purchasing
VOFM
Maintain requirements for Message Control
V/86
Field Catalog for condition Tables
Important Menus
Transaction Code
Description
WEDI
Main Menu for EDI related activities
BALE
Main menu for ALE related activities
SWLD
Main menu for workflow related activities
SALE
ALE Configuration
NACE
Message Control Configuration
IDOCs
Transaction Code
Description
WE31
Segment Editor
WE30
IDoc Editor to create and extend IDoc type
BD53
Reduce IDoc Types for Master Data
WE60
IDoc documentation (IDoc structure and segment definition)
WE61
IDoc documentation (Control Record, data record, and Status Record)
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
No comments:
Post a Comment