Systems in Seconds

INPUT INVENTORY COUNT IN SAP MM MODULE

2010-08-02T04:56:00.000-07:00

PHYSICAL STOCK CALCULATION IN SAP IS CALLED INVENTORY COUNT IN SAP MM.

Using menu:

Logistics -> Materials Management -> Physical Inventory -> Inventory Count

Using tcode: MI04

JFKJKHGK

Explore User Exits (Enhancement) For Any Module Of SAP

2010-08-02T00:05:00.000-07:00

aHTC Hero Android Phone (Sprint)1) ENTER TCODE SE81 IN COMMAND FIELD. NOW PRESS ENTER.

2) NOW DOUBLE CLICK ON THE SD HIERARCHY , CLICK ON EDIT MENU AND NOW CLICK ON SELECT SUBTREE +/- .

3) NOW CLICK ON INFORMATION SYATEM OR PRESS SHIFT + F4 .

4) NOW FOLLOW THE PATH
Repository Information System ---> Enhancements -----> Customer Exits ----> (Double Click) enhancement .

5) NOW YOU CAN SEE THE COMPLETE LIST OF EXITS AND ITS DESCRIPTION ,IN THE SCREEN.

TCODES FOR EXCISE , TAX AND REGISTERS ( CIN and CENVAT )

2010-07-28T05:11:00.000-07:00

Transaction codes for Tax and Excise Registers (CIN & CENVAT)

J1I2 - Prepare a sales tax register

J1I3 - Create outgoing excise invoices in batches

J1I5 - Update the RG 1 and Part I registers

J1IEX - Incoming Excise Invoices (central transaction)

J1IEX_C - Capture an incoming excise invoice (excise clerk)

J1IEX_P - Post an incoming excise invoice (excise supervisor)

J1IF01 - Create a subcontracting challana

J1IF11 - Change a subcontracting challan

J1IF12 - Display a subcontracting challan

J1IF13 - Complete, reverse, or recredit a subcontracting challan

J1IFQ - Reconcile quantities for subcontracting challans

J1IFR - List subcontracting challans

J1IH - Make a CENVAT adjustment posting

J1IIN - Create an outgoing excise invoice

J1IJ - Assign excise invoices to a delivery for sales from depots

J1INJV - Adjust withholding tax Item

J1INREP - Reprint a withholding tax certificate for a vendor

J1IQ - Year-End Income Tax Depreciation Report

J1IR - Download register data

J1IS - Process an excise invoice (outgoing) for other movements

J1IU - Process exemption forms

J1IW - Verify and post an incoming excise invoice

J1IX - Create an incoming excise invoice (without reference to purchase order)

J2I8 - Transfer excise duty to CENVAT account

J2IU - Remit excise duty fortnightly

J2I9 - Monthly CENVAT return

J1IG - Excise invoice entry at depot

J1IGA - Create additional excise entry at depot

J2I5 - Extract data for excise registers

J2I6 - Print excise registers

CREATE APPEND STRUCTURE IN ABAP DATA DICTIONARY

2010-07-27T04:50:00.000-07:00

APPEND STRUCTRURES :

APPEND STRUCTURES ARE USED ONLY TO ENHANCE STANDARD TABLES. STANDARD TABLES MAY HAVE INCLUDE STRUCTURES ALREADY CREATED , BUT IF WE WANT TO ADD SOME MORE FIELDS TO THE STANDARD TABLES, WE NEED TO GO FOR APPEND STRUCTURES.

APPEND STRUCTURES SHOULD BE ADDED AT THE END OF A STANDARD TABLE. THIS IS A MUST. BECAUSE WE SHOULD NOT CHANGE THE ORIGINAL STANDARD TABLE IN THE MIDDLE.

ONE THING YOU SHOULD KEEP IN MIND THAT IT MUST BE CREATED IN CUSTOMER NAMESPACE.
AND THE OTHETHING IS THAT NAME OF APPEND STRUCTURE MUST BE STARTS WITH ZZ OR YY
Let's starts with BKPF (Account Document Header) Table .

1) On EASY ACCESS Screen use TCODE SE11 . Now display the table BKPF . And click on append structure.

2) Now click on Create Append .

3) Now Give append name startting with ZZ or YY and press enter.

4) Now define field and components for build the append structure .
now save and activate it.

LSMW - Legacy System Migration Workbench

2010-07-26T04:44:00.000-07:00

The Legacy system migration workbench ( LSMW ) is an R/3-based tool that supports single or periodic data transfer from your non-SAP system to R/3 .It is a component of the R/3 System and, therefore, is independent from the platform.

The data is loaded via the standard interfaces of the applications.This will include all checks that are run for online transactions. Invalid data will be rejected.

Core Functions of LSMW

Importing legacy data from PC spreadsheet tables or sequential files.
Converting data from its original ( legacy system ) format to the target (R\3) format.
Importing the data using standard interfaces of R\3 ( IDOC inbound processing , batch input , direct input )

Which data can be migrated using LSMW ?

By means of standard transfer programs: a wide range of master data (e.g G/L accounts , customer master , vendor master , material master) and transaction data (e.g financial documents , sales order )
By means of recording of transactions: further data objects (if the transaction can be run in batch input mode)

The main advantages of the LSMW:

Part of R/3 and thus independent of individual platforms
A variety of technical possibilities of data conversion:
Data consistency due to standard import techniques:

                          Batch input

                         Direct input

                         BAPIs (Business Application Programming Interfaces)

                         IDocs (Intermediate Documents)

Generation of the conversion program on the basis of defined rules
Clear interactive process guide
Interface for data in spreadsheet format
Creation of data migration objects on the basis of recorded transactions
Charge-free for SAP customers and SAP partners

Prior to using LSMW, it is recommended to perform some

conceptual tasks.

Process Flow:

The following should be taken into account:

Make sure that the R/3 Customizing has been completed.

Analyze the data that exists in your legacy system (LS) and which of it (from a business point of view) will be required in the future as well.
Identify the transaction(s) in the R/3 System that you want to use to transfer the data to this system.
Process the respective transaction in R/3 manually using test data of the
legacy system and note which fields must be filled. Maybe there are required fields that do not correspond to a data field in the legacy system. In this case, assigning a fixed value or constant or setting up a field as an optional field perhaps is useful for the data transfer .
Carry out mapping on paper, that is, allocate the source fields and R/3 fields to each other. You can do this by using the object overview after you defined the object.
Determine the conversion rule according to which the field contents of the source fields are to be converted into R/3 fields.
Define the way in which the data is to be extracted from the non-SAP system. (The LSMW does not extract any data itself) .
Which format does the legacy data have? Decide which standard import technique you want to use, or if you should define an extra "object class” by means of recording.
In case only a part of your legacy system is to be replaced with the R/3 System, you have to determine the functions that are to be covered by the R/3 System and those to be covered by the legacy system. If necessary,a concept of the data flows and interface architecture has to be created.

Objects of LSMW

Project
Sub-project
Object
Structure Relationship
Field - Assignment

Project

Definition

All the data of an application system that is to be transferred to the SAP R/3 System.

Use

In the LSMW, the project serves as an organizational unit used to combine mapping and field assignments.

Structure

The project consists of:

Sub project
Business object (object)
Structure relationships
Field assignments

Integration

A project can have any number of sub projects assigned to it.

Sub-Project

Definition

An organizational unit subordinated to the project.

Integration

A sub project can have any number of objects.

Example

Data migration in a company with several plants in which data is organized in different ways. In this case, the complete migration of data would be the project. The sub projects would comprise the data in the individual plants.

Object

Definition

An object is a unit combined from the business point of view, which is used to transfer the data of a project to the SAP R/3 System.

Structure

An object consists of the following elements:

Tables involved in the project and in the SAP R/3 System
Structure(s) for transfer of data
Relationship between data at the table and field level
Field assignments for conversion of data.

Integration

                 An object is assigned to a sub project. For example, customer master,material master, or financial documents are objects.

Structure Relationship

Definition

Structure relationships are mappings between structured trees.

Use

                     The mappings between the trees have to make sense. This means, the structures of the data to be migrated (referred to as "source structures" ) have to be created within the hierarchy in a way that they can be allocated to the structures in the R/3 System (referred to as target structures" ).

Field Assignment :

Definition

                                     A collection of rules that define how the field contents are to be onverted during data migration from the legacy system to the SAP R/3 System.

Use

                                 The field assignments use placeholders and conversion rules in order to ensure both flexibility and consistency of data. In migration customizing, you assign values to the placeholders and select the processing types for the conversion rules.

Structure

The field assignments are distinguished by the different levels of reference:

At the highest level, there is the domain, which is defined by the field type, field length, and value tables, or by means of fixed values.
At the second level, there are the data elements, which are defined by the domain as well as by language-dependent texts.
At the lowest level, there are the fields, which are defined by field names and data elements. The field-related rules refer to them.

The placeholders and conversion rules defined by the field assignments are either linked to the target field directly or through the domain.

Example for Batch Upload :

Material master data transfer using LSMW for transaction mm01.

Enter the Name for the project, subproject and object and press create button.

As soon as you have create the project, you have to record the transaction,

(ctrl + F2) in this case its going to be mm01.

Once you are through with the recording, maintain the field properties, by double clicking on the 3rd column of any field. This needs to be done for all the fields for which you made an entry during recording. Then go to LSMW, press ctrl + f8 for the corresponding project.

When you are done with maintaining the Object attributes( you have to mention the

name of the recording in Batch Input Recording ), now the next step is to maintain source attributes.

Select No.2 Radio option and Press F8 and in the next screen you have to mention the source structure by clicking create button and then save it.

Go back and by default No.3 Radio option must have been selected, if not select No.3

Radio option “Maintain source field”. In the source field screen, create the field, by pressing ctrl + F3 for all the fields that you made an entry during recording.

Go back and select No.5, “Maintain Field Mapping and conversion rules” and press ctrl F8.
Click Assign Source Field for each field in a structure and map it to the Project structure.

Go back and select No: 7 Radio option “Specify files” , press CTRL F8 , then create entry for Legacy Data, specify the file name and then save it.

Go back and select No:8 radio option “Assign files” and press CTRL F8 , then go to No.9

“Read Data”, execute it and enter the value for no.of transaction(say 1-999999), execute it.

Then Select No:10 “Display read data” to check whether value from .txt file is properly

assigned to the corresponding fields in the structure.

Follow the previous procedure for Step 10-12. Create the Batch Input

Session and Run the Batch input session.

The Legacy System Migration Workbench (LSMW) is a tool that supports data migration from non-SAP systems to the SAP R/3 System. It is a component of the R/3 System.

The LSMW supports a one-time transfer of data (initial data load) and also offers a restricted support of permanent interfaces. Thus, a periodic transfer of data is possible. The LSMW, however, does not include any functions for monitoring of permanent interfaces. The tool does not support any data export interfaces (outbound interfaces).

DIFFERENCE BETWEEN ELEMENATRY & COLLECTILE SEARCH HELP

2010-07-26T02:48:00.000-07:00

1) Elementary search helps describe a search path. The elementary search help must define where the data of the hit list should be read from (selection method), how the exchange of values between the screen template and selection method is implemented (interface of the search help) and how the online input help should be defined (online behavior of the search help).

2) Collective search helps combine several elementary search helps. Collective search help thus can offer several alternative search paths.

3) An elementary search help defines the standard flow of an input help.

4) A collective search help combines several elementary search helps. The user can thus choose one of several alternative search paths with collective search help.

5) A collective search help comprises several elementary search helps. It combines all the search paths that are meaningful for a field.

6) Both elementary search helps and other search helps can be included in a collective search help. If other collective search helps are contained in collective search help, they are expanded to the level of the elementary search helps when the input help is called.

ABAP SYSTEM VARIABLE

2010-07-21T03:25:00.000-07:00

SYSTEM VARIABLES HAVE BEEN PREDEFINED BY SAP . IT IS ALSO USED TO PASS INFORMATION TO FUNCTION MODULES OR THE ABAP SYSTEM FIELDS ARE ACTIVE IN ALL ABAP PROGRAMS. THEY ARE FILLED BY THE RUNTIME ENVIRONMENT AND YOU CAN QUERY THEIR VALUES IN A PROGRAM TO FIND OUT PARTICULAR STATE OF THE SYSTEM. ALTHOUGHT THEY ARE VARIABLE,

YOU SHOULD NOT ASSIGN YOUR OWN VALUES TO THEM, SINCE THEY MAY OVERWRITE INFORMATION IMPORTANT FOR THE NORMAL FOR THE PROGRAM.

1 ) FIRST ON EASY ACCESS SCREEN TCODE SE11 . THEN GO TO DATATYPES AND PRESS F4 . NOW CLICK ON SEARCH DATA STRUCTURE .

2) NOW CLICK ON INFORMATION SYSTEM BUTTON .

3) IN THE STRUCTURE NAME WRITE SYST AND EXECUTE .

4 ) NOW CLICK ON STRUCTURE NAME SYST AND ACCEPT .

5) NOW CLICK ON DISPLAY.

6) THE GIVEN BELOW IS TOTAL NO. OF SYS. FIELD OF SAP.

IF YOU DON'T WANT TO FOLLOW THE WHOLE PROCEDURE THEN ALSO JUST

GOTO TCODE SE11---> DATA TYPE ---> simply type there SYST ---> CLICK ON DISPLAY

THANK YOU .

CREATE SEARCH HELP - ABAP DATA DICTIONARY

2010-07-20T00:51:00.000-07:00

1) FIRST OF ALL IN EASY ACCESS SCREEN ENTER TCODE SE11 , AND CHOOSE SEARCH HELP AND GIVE ANY NAME NOW CLICK ON CREATE .

2) THERE ARE TWO TYPES OF SEARCH HELPS ONE IS COLLECTIVE SEARCH HELP AND THE OTHER IS ELEMENTARY SEARCH HELP.

ELEMENTARY SEARCH HELP : DEPENDS ON ONE TABLE

COLLECTIVE SEARCH HELP : DEPENDS ON MORE THAN ONE ELEMENTARY SEARCH HELP

NOW SELECT ELEMNATARY SEARCH HELP.

3 ) NOW GIVE A SHORT DISCRIPTION IN THE SCREEN AND CLICK ON SELECTION METHOD. CLICK ON SEARCH FOR TABLES.

4 ) GIVE THE TABLE NAME WHERE YOU WOULD LIKE TO ATTACH SEARCH HELP AND CLICK ENTER.

5 ) NOW ENTER SEARCH HELP PARAMETERS BY PRESSING FUNCTIN KEY F4 .

6 ) NOW SAVE , ACTIVATE AND TEST THE SEARCH HELP.

MAKING COLUMNS IN SMARTFORMS

2010-07-16T03:35:00.000-07:00

1 ) Now one of the important process of smartform is making column. So we are going to make column in our smartforms.

the process is quite simple, first let’s open your SmartForms, you can create a SmartForms using TCODE Smartforms and just create a new report there.

Before drawing the table columns, you must create the table first by right clicking the main window --> Create --> Table.

Next you have to click on the pencil button on the table tab.

Now you can draw the columns by clicking and dragging the pencil on the table boxes, this will create a table line that will be used to create the report columns.

Now to show the columns you just drew, right click the table, select TABLE -- > Create TABLE LINE. Thenin the output table select the linetype.

Now you see there are 4 columns from the table line we just drew earlier.

So Only few clicks and tricks can make columns in your SMARTFORMS.

CREATE PHYSICAL INVENTORY - MM

2010-07-16T02:54:00.000-07:00

TCODE : MI01

USING
MENU:-Logistic-->Material Management-->Physical Inventory-->Physical Inventory Document

Generally Create Physical inventory document is a process to create document for the physical inventory checking. (Stock up and down)

1. Plant: The plant where the stock checking is conducted.

2. Storage Location: Warehouse where the material is located.

3. Posting Block: The block utility so that the material can not be used for any transaction during the physical stock checking process.

4. Freeze book inventory: As a cut off for the stock checking. (The item that has the status “Freeze” still can be used for transaction)

Note: You can’t used both (posting block and freeze book inventory) at the same time.

Click enter to continue.

1. Select the material number.

2. Input the batch/lot number (this data will be automatically filled after you’ve selected the material number)

CTRL+S to save.

Now a new physical inventory document has been created successfully.

HOW TO INSERT LOGO IN SMARTFORMS

2010-07-15T04:46:00.000-07:00

SMART FORM IS GENERALLY USED FOR TO CREATE AND MAINTAIN MASS PRINTING . AND ALSO IT IS USED FOR SIMPLE MODIFICATION TO THE FORM .

SAP SMART FORMS ALLOW THE FORM LOGIC BY USING SIMPLE GRAPHICAL TOOLS.

IN SAP we have a place to store all the images that we want to use in the form application, it’s called the Administration of Form Graphics.

Before you can add logo/graphic into your Smartforms, first you need to upload the file into the bitmap folder in SAP.

1. Execute SE78

Expand the Stored Document Server --> Graphics --> BMAP Bitmap Images.

Now you need to name your graphic first, in this tutorial I typed in CREATELOGO as my graphic name, this name also serves as graphic ID.

2. Now click on Graphic --> Import or just press F5 to browse your graphic file.

Click the browse button the filename box, and just find the image that you want to stored/upload. In this tutorial I want to keep the color of my image so I choose Color Bitmap Image.

Remember that your image/graphic should have a Bitmap filetype (.BMP). MIND IT ONLY .BMP FILE FORMATES ARE SUPPORTED . if you have other filetype then you need to convert it first before uploading the image.

After you done, just press enter or click the Ok button. You should see the message on the status bar “Graphic xxxxx was imported”. It means that now it’s stored and ready to use.

CLICK ON IMPORT BUTTON

3. Open you smartforms, right click the %PAGE section, select CREATE --> Graphic.

4. Now just type in the file name we created earlier in step 1. Choose “GRAPHICS” as the object, and “BMAP” as the ID.

Choose the Color Bitmap Image to maintain its color.

5. After that, just click SAVE and Activate the SmartForms, test the SmartForms (F8), and here’s the result.

GET PROGRAM NAME FROM TCODE

2010-07-13T03:57:00.000-07:00

1 FIRST GO TO THE SE93 TRANSACTION

2) THEN FIRST ENTER THE TCODE OF PROGRAM AND CLICK ON DISPLAY

3) nOW YOU CAN SEE

PROGRAM
PACKAGE
TCODE
DESCRIPTION
AUTORIZATION OBJECT
SELECTION SCREEN

SO ONE CAN EASILY CUSTOMIZE CODE USING PROPER AUTHORIZATION.

Display Table

2010-06-21T05:01:00.000-07:00

SD RELATED TCODES

2010-06-15T22:29:00.000-07:00

SAP SD related transaction codesCustomerXD01 Create Customer (Centrally)XD02 Change Customer (Centrally)XD03 Display Customer (Centrally)XD04 Customer Changes (Centrally)XD05 Block customer (centrally)XD06 Mark customer for deletion (centr.)XD07 Change Customer Account GroupXD99 Customer master mass maintenanceXDN1 Maintain Number Ranges (Customer)VendorXEIP Number range maintenance: EXPIMPXK01 Create vendor (centrally)XK02 Change vendor (centrally)XK03 Display vendor (centrally)XK04 Vendor Changes (Centrally)XK05 Block Vendor (Centrally)XK06 Mark vendor for deletion (centrally)XK07 Change vendor account groupSales OrderVA00 Initial Sales MenuVA01 Create Sales OrderVA02 Change Sales OrderVA03 Display Sales OrderVA05 List of Sales OrdersVA07 Compare Sales - Purchasing (Order)VA08 Compare Sales - Purchasing (Org.Dt.)InquiryVA11 Create InquiryVA12 Change InquiryVA13 Display InquiryVA14L Sales Documents Blocked for DeliveryVA15 Inquiries ListQuotationVA21 Create QuotationVA22 Change QuotationVA23 Display QuotationVA25 Quotations ListVA26 Collective Processing for QuotationsContractVA41 Create ContractVA42 Change ContractVA42W Workflow for master contractVA43 Display ContractVA44 Actual Overhead: Sales OrderVA45 List of ContractsVA46 Coll.Subseq.Processing f.ContractsItem ProposalVA51 Create Item ProposalVA52 Change Item ProposalVA53 Display Item ProposalVA55 List of Item ProposalsVA88 Actual Settlement: Sales OrdersDelivery (Outbound)VL00 ShippingVL01 Create DeliveryVL01N Create Outbound Dlv. with Order Ref.VL01NO Create Outbound Dlv. w/o Order Ref.VL02 Change Outbound DeliveryVL02N Change Outbound DeliveryVL03 Display Outbound DeliveryVL03N Display Outbound DeliveryVL04 Process Delivery Due ListVL06 Delivery MonitorVL06C List Outbound Dlvs for ConfirmationVL06D Outbound Deliveries for DistributionVL06F General delivery list - Outb.deliv.VL06G List of Oubound Dlvs for Goods IssueVL06I Inbound Delivery MonitorVL06IC Confirmation of putaway inb. deliv.VL06ID Inbound Deliveries for DistributionVL06IF Selection inbound deliveriesVL06IG Inbound deliveries for goods receiptVL06IP Inbound deliveries for putawayVL06L Outbound Deliveries to be LoadedVL06O Outbound Delivery MonitorVL06P List of Outbound Dlvs for PickingVL06T List Outbound Dlvs (Trans. Planning)VL06U List of Uncheckd Outbound DeliveriesVL08 Confirmation of Picking RequestVL09 Cancel Goods Issue for Delivery NoteVL10 Edit User-specific Delivery ListVL10A Sales Orders Due for DeliveryVL10B Purchase Orders Due for DeliveryCustomer managementFD01 Create Customer (Accounting)FD02 Change Customer (Accounting)FD02CORE Maintain customerFD03 Display Customer (Accounting)FD04 Customer Changes (Accounting)FD05 Block Customer (Accounting)FD06 Mark Customer for Deletion (Acctng)FD08 Confirm Customer Individually(Actng)FD09 Confirm Customer List (Accounting)FD10 Customer Account BalanceFD10N Customer Balance DisplayFD10NA Customer Bal. Display with WorklistFD10NET Customer Balance DisplayFD11 Customer Account AnalysisFD15 Transfer customer changes: sendFD16 Transfer customer changes: receiveFD24 Credit Limit ChangesFD32 Change Customer Credit ManagementFD33 Display Customer Credit ManagementFD37 Credit Management Mass ChangePricingV/03 Create Condition Table (SD Price)V/04 Change Condition Table (Sales pr.)V/05 Display Condition Table: (Sales Pr.)V/06 Condition Categories: SD PricingV/07 Maintain Access (Sales Price)V/08 Conditions: Procedure for A VV/09 Condition Types: Account Determin.V/10 Account Determination: Access SeqncV/11 Conditions: Account Determin.Proced.V/12 Account Determination: Create TableV/13 Account Determination: Change TableV/14 Account Determination: Display TableBOMCS00 BOM MenuCS01 Create Material BOMCS02 Change Material BOMCS03 Display Material BOMCS05 Change Material BOM GroupCS06 Display Material BOM GroupCS07 Allocate Material BOM to PlantCS08 Change Material BOM - Plant Alloc.CS09 Display Allocations to PlantCS11 Display BOM Level by LevelCS12 Multilevel BOMCS13 Summarized BOMCS14 BOM ComparisonCS15 Single-Level Where-Used ListCS20 Mass Change: Initial ScreenCS21 Mass Material Change: Initial ScreenCS22 Mass Document Change: Initial ScreenCS23 Mass Class Change: Initial ScreenCS25 Archiving for BOMsCS26 BOM deletionCS27 Retrieval of BOMsCS28 Archiving for BOMsCS31 Create class BOMCS32 Change class BOMCS33 Display class BOMCS40 Create Link to Configurable MaterialCS41 Change Material Config. AllocationCS42 Display Material Config. AssignmentCS51 Create standard BOMCS52 Change standard BOMCS53 Display standard BOMCS61 Create Order BOMCS62 Change Order BOMCS63 Display Order BOMCS71 Create WBS BOMCS72 Change WBS BOMCS73 Display WBS BOMCS74 Create multi-level WBS BOMCS75 Change multi-level WBS BOMCS76 Display multi-level WBS BOMCS80 Change Documents for Material BOMCS81 Change Documents for Standard BOMCS82 Change documents for sales order BOMCS83 Change documents for WBS BOMCS84 Change documents for class BOMCS90 Material BOM Number RangesCS91 Number Ranges for Standard BOMsCS92 Number Ranges for Sales Order BOMs

SAP FI / CO TABLES Finance Tables

2010-06-15T03:51:00.000-07:00

AGKO Cleared Accounts

ANAR Asset Types

ANAT Asset type text

ANEK Document Header Asset Posting

ANEP Asset Line Items

ANEV Asset downpymt settlement

ANKT Asset classes- Description

ANLA Asset Master Record Segment

ANLB Depreciation terms

ANLC Asset Value Fields

ANLH Main asset number

AT02T Transaction Activity Category- Description

AT02A Transaction Code for Menu

TIMNAT10 Transaction type

AT10T Name of Transaction Type

BKDF Document Header Supplement for Recurring Entry

BKORM Accounting Correspondence Requests

BKPF Accounting Document Header

BLPK Document log header

BLPP Document log item

BLPR Document Log Index and Planned Order (Backflush)

BNKA Bank master record

BP000 Business Partner Master (General Data)

BPBK Doc.Header Controlling Obj.

BPEG Line Item Total Values Controlling Obj.

BPEJ Line Item Annual Values Controlling Obj.

BPEP Line Item Period Values Controlling Obj.

BPGE Totals Record for Total Value Controlling obj.

BPJA Totals Record for Annual Total Controlling Obj.

BSAD Accounting- Secondary Index for Customers (Cleared Items)

BSAK Accounting- Secondary Index for Vendors (Cleared Items)

BSAS Accounting- Secondary Index for G/L Accounts (Cleared Items)

BSEC One-Time Account Data Document Segment

BSEG Accounting Document Segment

BSID Accounting- Secondary Index for Customers

BSIK Accounting- Secondary Index for Vendors

BSIM Secondary Index, Documents for Material

BSIS Accounting- Secondary Index for G/L Accounts

CEPC Profit Center Master Data Table

CEPCT Texts for Profit Center Master Data

COBRA Settlement Rule for Order Settlement

COBRB Distribution Rules Settlement Rule Order Settlement

COKA CO Object- Control Data for Cost Elements

COSP CO Object- Cost Totals for External Postings

COSS CO Object- Cost Totals for Internal Postings

CRCO Assignment of Work Center to Cost Center

CSKA Cost Elements (Data Dependent on Chart of Accounts)

CSKB Cost Elements (Data Dependent on Controlling Area)

CSLA Activity master

FEBEP Electronic Bank Statement Line Items

FPLA Billing Plan

FPLT Billing Plan- Dates

GLPCT EC-PCA- Totals Table

KNA1 General Data in Customer Master

KOMK Pricing Communication Header

MAHNV Management Records for the Dunning Program

REGUT TemSe - Administration Data

SKA1 G/L Account Master (Chart of Accounts)

SKAT G/L Account Master Record (Chart of Accounts- Description)

SKB1 G/L account master (company code)

T003T Document Type Texts

T007S Tax Code Names

T087J Text

TAPRFT Text tab. for investment profile

TKA01 Controlling Areas

TKA09 Basic Settings for Versions

TKVS CO Versions

TZB0T Flow types text table

TZPAT Financial Assets Management product type texts

VBSEGS Document Segment for G/L Accounts Document Parking

VTBFHA Transaction

VTBFHAPO Transaction Flow

VTBFHAZU Transaction Activity

VTBFINKO Transaction Condition

VTIDERI Master Data Listed Options and Futures

VTIFHA Underlying transaction

VTIFHAPO Underlying transaction flows

VTIFHAZU Underlying transaction status table

VTIOF Options Additional Data

VWPANLA Asset master for securities