SAP E Books » sap

What does configuration/customization mean in SAP?

admin — Sat, 26 Sep 2009 05:10:20 +0000

During the Realization phase of a SAP implementation the project team will configure the SAP environment to meet the requirements defined during Blueprint. Configuration can take many forms and many of them from SAP’s perspective are not considered “modifications” though the line is somewhat gray on occasion. The various types of configuration include:

Types of Configuration

Table Maintenance

Many of the transactional fields in SAP are populated from drop-down lists, maintenance of these lists is a standard activity on any project and is not considered a modification.

Examples of Table Maintenance:

Payment Terms – Most if not all clients attach payment terms to their Sales Orders. SAP comes loaded with a set of default terms, which can be hidden or others can be added, to fit a particular client’s needs.

Material Groups – In the material master SAP provides Material Groups so that clients can group their materials by product line, product family, etc. The values in this table can be changed as needed. The values themselves are used in things like pricing, but changing the values does not change how SAP works.

No standard code or functionality is affected by adding values to these tables.

Z Conditions and Z Document types

These objects are table entries or views of several tables which are merely containers for sets of instructions SAP uses in its’ standard code to perform tasks.

Example of Z Configuration:

SAP comes with a variety of preloaded “standard” configuration, for example out-of-the-box SAP provides a standard Sales Order called OR in the system, This OR has default settings that trigger certain functions within SAP. The settings take the form of fields populated by drop down lists, check boxes, and free form text fields. All of these settings can be changed without any development time. SAP realizes that the Standard Sales Order may not meet a client’s needs. The standard policy is to use the copy function, make a duplicate of the OR and rename it by putting a “Z” in front of it. So the custom order type would be called ZOR. The character Z lets anyone working on the system know that this is a copy of standard configuration and has been changed for the customers needs. Making a copy of the “OR” rather than changing the “OR” provides a baseline model incase the implementation team needs a point of reference. This does not require development time, though the new configuration does have to be tested. This is not considered a modification by SAP.

Formulas, Requirements and Data Transfer Routines

SAP provides “holes” in its’ code where instruction sets can be “included”. Sample sets are included with SAP but they intend for customers to create their own as required to custom, ”configure” the system to meet business needs. SAP does provide standard formulas, which are listed and defined in a separate document in the ASAP Implementation Assistant. However when new formulas, requirements, or data transfer routines are needed a development resource and time must be set aside, because they are written in ABAP or Java code. These types of code are typically not complex and do not require significant time to produce.

Example of a Formula:

In many cases rounding routinely is an issue during implementations depending on the customers pricing model. Standard SAP rounding will round to two decimal places, however if requirements dictate that rounding should be done to the nearest nickel, dime, dollar etc., a formula could be written to satisfy this requirement.

User Exits

See Formulas, Requirements, and Data Transfer Routines.

Where Formulas, Requirements and Data transfer Routines are usually no more than a few lines of code, User Exits can be quite complex and perform a variety of functions throughout the SAP system. But since they reside in the “holes” in Standard SAP code that SAP provides they are not considered modifications to CORE SAP.
SAPScripts/SAPSmartForms

A SAPScript is a printing program. These programs process the outputs from SAP, Order Acknowledgements, Purchase Orders, Invoices, etc. The SAPScripts contain the layouts for the outputs and hence SAP expects every customer to customize the layouts of their documents. This functionality is being phased out by SAP Smart Forms which are object oriented and easier to maintain.

OSS Notes

Changes (Bug Fixes) and/or corrections to SAP code which can be initiated and implemented by SAP and/or SAP customers which are properly documented and identified in such a manner as too easily allow migration to future releases with little or no intervention.

Whenever bugs are reported to SAP, the fixes they put out are call OSS notes. By entering transaction OSS1 in SAP and assuming you have a connection to SAP, you will be linked to their OSS System, which gives you access to all of the notes, which are sorted by release and module. If you are on ECC Release 5.0 none of the notes for prior releases should be important to you since a fix created for 4.6c would have been incorporated as standard in 5.0. So when searching the Database you would look for notes for release ECC 5.0 or higher.

OSS Notes document the problem and the resolution. They require that an ABAP developer apply them, since it more often than not requires inserting and changing lines of Code in SAP.

During Upgrades an evaluation must be done of all the OSS notes that have been applied to see which ones are covered by the upgrade. Any notes not covered by the new release need to be reapplied after SAP has been upgraded.

IPC aka Internet Pricing Configurator

For pricing in SAP CRM, all pricing must be loaded into the IPC a java based application. This requires that any custom pricing requirements or formulas, which were created in SAP’s ABAP programming language must be recreated in Java and loaded onto the IPC in order to do comparable pricing.

To accomplish this a java developer is required as well as extensive testing. Pricing is very complicated in standard SAP, let alone replicating that model in another programming language and setting up communication between the two.

MAS aka Mobile Application Studio

The Mobile Application studio allows you to customize the screens in the SAP CRM Mobile client. This is an object oriented programming tool that can be used to change layouts and remove or add fields to screens in SAP. These screen changes do not carry over into CRM Online or SAP R/3.

Effective use of this tool requires a developer familiar with Visual Basic and object oriented programming methodologies.

MODs aka Modifications

Changes to SAP code which are initiated and developed by SAP customers. When Properly documented and identified these can be readily recognized and retrofitted during migration to future releases.

SAP discourages MODs without their involvement and approval. In all cases MODs are not support under service agreements and SAP will not support any problems they cause with the system.

If a customer works with SAP on the MOD then SAP may incorporate it in future releases at which point it becomes part of standard.

The following OSS note should be considered before any modifications are built.

170183: What to consider when applying modifications

*SAP may support MODs if they are involved in the custom development process and support the change.
** SAP will support work in these areas only so far as it does not impact standard SAP/CRM Functionality.

SAP Tables and Relation

admin — Mon, 13 Jul 2009 17:46:46 +0000

SAP Tables and Relation

This document list of all the major tables and their relationship.

This document covers tables from following modules,

1. FI Financial Accounting Tables
2. CO Controlling Tables
3. MM Material Management Tables
4. SD Sales and Distribution Table
5. PS SAP Project System tables
6. PP – Project Planning tables

This document is very useful for the entire SAP consultants who have to work on table level.

This document will also help you to write functional specification for development. This will be specifically useful for all the ABAP consultants who need to work on developments in SAP.

This document is available for immediate download, click here to know more and Buy Now!

SAP Tables and Relation

SAP Self Learning Materials

admin — Fri, 10 Jul 2009 18:25:37 +0000

All these documents are available for instant download. For any help contact us at admin@sapebooks.com

How to Analysie workflow problems

admin — Thu, 11 Jun 2009 15:39:58 +0000

This article contains transactions and techniques that will help you nderstand and analyze your workflow problems.

Transaction SWUD

SWUD is the diagnosis transaction. This will guide you through the fault finding process. The check-list order is determined dynamically
according to:

a) your workflow definition and

b) the statistics of the most common mistakes made when

creating/activating a workflow.

The testbed, provides a launchpad for tests to ensure that your workflow definition is rugged enough for the production environment. It also allows you to access the tasks, subflows, object types, delegated object types and agent assignments directly, without going through the workflow builder first. (Foreground tasks with no agent assignment are marked in red from release 4.5 onwards). This list is also useful as a catalogue of the components of workflow for documentation or transport purposes.

     Click on the “info” icon to read a description of the test being performed.
     Any workflow accessed through this transaction is added to the last-used
     list. The workflow can be recalled at a later date by clicking on the
     reuse icon in the left-hand column of the last-used list.
     The next section describes the transactions called from SWUD. Experts
     may find it easier calling them directly.

Secondary Diagnosis Transactions

         o Transaction SWU3: Verify Workflow Customizing.
            In this transaction the most important basic customizing for
            workflow is checked. If you find any errors here, read the
            documentation for the error. If your system is BBP or CRM, see
            note 60801.

         o Transaction SWEL: Event Log.
            Note: Before you can use the event log, you must make sure it is
            activated. You check this in transaction SWELS. If you are not
            sure whether or not it is active, just deactivate and activate
            the event log once.
            WARNING: An activated event log can lead to bad performance, and
            must not be activated constantly in a productive system.

         o Transaction SWE2: Event type linkage
            A workflow is usually started or triggered by an EVENT so it is
            important to make sure that an event occurrs. In the event log
            you can see the event and its business object type.
            If an event has been successfully created, it is important to
            check if there is a receiver type for this event. The receiver
            type is the workflow that has been triggered by the event.
            The coupling between an event and the receiver can be maintained
            in trans. SWE2.

         o Transaction SWU0: Event simulation
            If you have found NO receiver type in the event log, then you
            should check transaction SWU0, Simulate Events.
            In this transaction you can simulate an event. The system will
            check all workflows that could be triggered by the event and
            tells you whether or not they were triggered. Information is
            displayed for the workflows that were not triggered successfully.

         o Transaction SWI1: Work item list
            If a workflow was been correctly triggered and started at least
            one WORK ITEM should be created. You can view the work items in
            transaction SWI1, Work Item Selection.
            The easiest way for the selection is just to go into this
            transaction after you have checked the event log. By default all
            the work items of the last hour will be displayed.
            You will find in this transaction the work item number, the
            status of the work item and the workflow task that has created
            the work item. Furthermore, (in the technical workitem display)
            you can have a look at the container by selecting a work item and
            using the menu GOTO -> CONTAINER. To display the work item
            details double click on the item. From the details you can see
            the selected/ possible/excluded agents for this work item by
            using the menu GOTO -> AGENT -> SELECTED/POSSIBLE/EXCLUDED
            AGENTS.
            When the status of the work item shows an error you should have a
            look at the workflow log using the menu EDIT -> DISPLAY WORKFLOW
            LOG. Here you can see errors that have occurred.

         o Transaction PFTC/SWDD: Task editor/Workflow Builder
            If you want to have a look at the definition of the workflow you
            can use transaction PFTC, Maintain Tasks.
            The button WORKFLOW BUILDER brings you to a graphical display of
            the workflow structure which is fairly easy to read and
            understand. On the tabstrip TRIGGERING EVENTS you can check if
            the triggering is activated or not and deactivate/activate it by
            clicking on the icon in front of the event.

         o Transaction OOCU: Customizing overview
            To check if the relevant tasks are activated and users are

            assigned, you can use transaction OOCU; Task Customizing
            Overview.
            In this transaction all the tasks are sorted by the application
            components and are thus easy to find. Note that if you have
            almost no entries in this transaction, you should execute the
            report RS_APPL_REFRESH in transaction SE38.

         o Transaction SWUE/SWUS: Event/workflow trigger
            If you have activated a user exit, e.g. for the role
            determination, and you have problems with that, you most probably
            have to debug the workflow. This can be done using the
            transaction SWUS or SWUE.
            With SWUE you can create an event. After you entered object type
            and event you have to fill the event parameters and the key for a
            specific object. If you want to debug the workflow you have to
            set the flag TRIGGER RECIEVER FM SYNCHR. If you have set a break
            point in your user exit or in any other function module of the
            workflow the system will stop at this break point and you can
            start analyzing.
            The second possibility to debug a workflow is to use the
            transaction SWUS, the workflow test environment. In this
            transaction you have to enter the workflow task and fill the
            input data. Please use the F4-help to fill the input data. Here
            again you have to set a break point in your user exit or in any
            other function module of the workflow and then the system will
            stop there.
     Summary of the manual alternative to SWUD
     Now that you have a better understanding of how to use these
     transactions, you can follow the steps below to quickly analyze your
     workflow problems:

1. Go to transaction SWU3 and check if everything is okay. If it is
not, please fix it before you proceed.

2. Go to transaction SWEL and check if an event is created. If not,
check in transaction SWELS if the event log is activated.

o If you see an event but no workflow is triggered, proceed with
step 3.

o If you see an event and a workflow is triggered, but the status
of the triggering shows an error, proceed with step 3.

o If you see an event and a workflow is triggered and there is no
error, proceed with step 4.

         o If the event log is activated and you do not get any event, open
            up a message using the component of the application to which the
            business object type belongs. From release 20C for creation of
            shopping carts
            the architecture of workflows changed and no events are visible!

3. Go to transaction SWU0 and simulate the event. Is the workflow that
you expect to be triggered visible in the simulation?

         o If it is not, then check the workflow definition in PFTC. The
            event must be defined as triggering event.

o If it is, but the event linkage is not activated, go to
transaction OOCU and activated it.

o If it is visible, but it is not activated, go to transaction PFTC
and activate it.

4. Go to transaction SWI1. Search for the work item that belongs to the
workflow. Check the status of the work item.

         o If it shows an error, look at the workflow log. Do you see any
            errors? If yes, you can probably find a solution in the SAPNet
            Frontend. (Tips and tricks on how to search for information and
            solutions in the SAPNet Frontend can be found in note 192194.) If
            you do not find any help in the SAPNet Frontend, please open up a
            message with the component BC-BMT-WFM and tell us the number of
            the error message and the name of the workflow.

SAP Table List

admin — Wed, 10 Jun 2009 12:50:07 +0000

1 Customising

1.1 General settings

1.1.1 Countries

T005 Countries

1.1.2 Currency

TCURC Currency codes

TCURR Wisselkoersen

TCURT Currency name

TCURX Decimal places for currencies.

1.1.3 Unit of measure

T006 Units of measure

1.1.4 Calendar functions

T247 Month names

TFACD Factory calendar definition

T015M Month names

TTZZ Time zones

TTZD Summer time rules

TTZDF Summer time rules (fixed annual dates)

TTZDV Summer time rules (variable dates)

TTZDT Summer time rules texts

TTZ5 Assign Time Tones to Countries

TTZ5S Assign time zones to regions

1.2 Enterprise structure

1.2.1 Definition

FI T880 Company

T001 Company code

CO TKA01 Controlling area

LO T001W Plant / sales organisation

T499S Locations

TSPA Division

SD TVKO Sales organisation / company code

TVTW Distribution channel

TVBUR Sales office

TVKBT Sales office text

TVKGR Sales group

TVGRT Sales group text

T171T Sales district text

MM T001L Storage locations

T024E Purchasing organization

T3001 Warehouse number

TVST Shipping point

TVLA Loading point

TTDS Transportation

1.2.2 Assignment

CO TKA02 Assign company code to controlling area

LO T001K Assign plant (valuation area) to company code

SD TVKO Sales organisation / company code

TVKOV Distribution channel / sales organisation

TVKOS Division to sales organization

TVTA Sales aria

TVKBZ Sales office to sales area

TVBVK Sales group to sales office

TVKWZ Plants to sales organization

MM T024E Purchasing organization / company code

T024W Plant to Purchase organization

T001K Link plant ( = valuation area) / company code

TVSWZ Shipping point to plant

T320 Assignment MM Storage Location to WM Warehouse

1.3 Financial accounting

1.3.1 Company code

T004 Chart of accounts

T077S Account group (g/l accounts)

T009 Fiscal year variants

T880 Global company data

T014 Credit control area

1.3.2 Fi document

T010O Posting period variant

T010P Posting Period Variant Names

T001B Permitted Posting Periods

T003 Document types

T012 House banks

1.4 Not categorized

T007a Tax keys

T134 Material types

T179 Materials: Product Hierarchies

T179T Materials: Product hierarchies: Texts

TJ02T Status text

TINC Customer incoterms

TVFK Billing doc types

T390 PM: Shop papers for print control

2 Basic data / administration

2.1 Workbench related tables

2.1.1 Data dictionary tables

DD02L Tables in SAP

DD02T Tables description

DD03L Field names in SAP

DD03T Field description in SAP

2.1.2 Workbench

TADIR Directory of R/3 Repository Objects

TRDIR System table TRDIR

TFDIR Function Module

TLIBG Person responsible for function class

TLIBT Function Group Short Texts

TFTIT Function Module Short Text

TSTC Transaction codes in SAP

TSTCT Transaction codes texts

T100 Message text (vb e000)

VARID Variant data

D020T Screen texts

TDEVC Development class

TDEVCT Texts for development classes

2.2 Administration

2.2.1 User administration

USR01 User master

USR02 Logon data

USR03 User address data

USR04 User master authorizations

USR11 User Master Texts for Profiles (USR10)

UST12 User master: Authorizations

USR12 User master authorization values

USR13 Short Texts for Authorizations

USR40 Prohibited passwords

TOBJ Objects

TOBC Authorization Object Classes

TPRPROF Profile Name for Activity Group

DEVACCESS Table for development user

2.2.2 Batch input queue

APQD DATA DEFINITION Queue

APQI Queue info definition

2.2.3 Job processing

TBTCO Job status overview table

TBTCP Batch job step overview

2.2.4 Spool

TSP02 Spool: Print requests

2.2.5 Runtime errors

SNAP Runtime errors

2.2.6 Message control

TNAPR Processing programs for output

NAST Message status

NACH Printer determination

2.2.7 EDI

EDIDC Control record

EDIDD Data record

EDID2 Data record 3.0 Version

EDIDS EDI status record

EDPAR Convert External < > Internal Partner Number

EDPVW EDI partner types

EDPI1 EDI partner profile inbound

EDPO1/2/3 EDI partner profile outbound

2.2.8 Change documents

CDHDR Change document header

CDPOS Change document positionen

JCDS Change Documents for System/User Statuses (Table JEST)

2.2.9 Reporting tree table

SERPTREE Reporting: tree structure

2.2.10 LIS structure/control tables

TMC4 Global Control Elements: LIS Info Structure

3 MASTER DATA :

3.1 Material master :

MARA Material master

MAKT Material text

MARC Material per plant / stock

MVKE Material master, sales data

MARD Storage location / stock

MSKA Sales order stock

MSPR Project stock

MARM Units of measure

MEAN International article number

PGMI Planning material

PROP Forecast parameters

MAPR Link MARC <=> PROP

MBEW Material valuation

MVER Material consumption

MLGN Material / Warehouse number

MLGT Material / Storage type

MPRP Forecast profiles

MDTB MRP table

MDKP Header data for MRP document

MLAN Tax data material master

MTQSS Material master view: QM

3.1.1 Basic data text (sap script)

STXB SAPscript: Texts in non-SAPscript format

STXH STXD SAPscript text file header

STXL STXD SAPscript text file lines

3.1.2 Batches

MCHA Batches

MCH1 Batches

MCHB Stock : batches

3.2 Customer master data

KNA1 Customer master

KNB1 Customer / company

KNVV Customer sales data

KNBK Bank details

KNVH Customer hierarchy

KNVP Customer partners

KNVS Shipment data for customer

KNVK Contact persons

KNVI Customer master tax indicator

3.3 Vendor

LFA1 Vendor master

LFB1 Vendor per company code

LFB5 Vendor dunning data

LFM1 Purchasing organisation data

LFM2 Purchasing data

LFBK Bank details

3.4 Customer – material info record

KNMT Customer material info record

3.5 Bank data

BNKA Master bank data

4 Characteristics :

4.1 Characteristics :

CABN Characteristics ( o.a. batch/vendor)

CABNT Characteristics description

CAWN Characteristics ( o.a. material)

CAWNT Characteristics description

AUSP Characteristic Values

4.2 Class types and objects :

TCLAO Several class types for object

TCLA Class types ( vb. lfa1 => v10 en 010)

TCLAT Class type text

TCLT Classifiable objects

TCLC Classification status

4.3 Links :

INOB Link between Internal Number and Object

KLAH Class header data

KSSK Allocation Table: Object (vb.matnr) to Class

KSML Characteristics for a class (internal number)

5 FI/CO :

5.1 FI :

5.1.1 Master data

SKA1 Accounts

BNKA Bank master record

5.1.2 Accounting documents // indices

BKPF Accounting documents

BSEG item level

BSID Accounting: Secondary index for customers

BSIK Accounting: Secondary index for vendors

BSIM Secondary Index, Documents for Material

BSIP Index for vendor validation of double documents

BSIS Accounting: Secondary index for G/L accounts

BSAD Accounting: Index for customers (cleared items)

BSAK Accounting: Index for vendors (cleared items)

BSAS Accounting: Index for G/L accounts (cleared items)

5.1.3 Payment run

REGUH Settlement data from payment program

REGUP Processed items from payment program

5.2 CO :

TKA01 Controlling areas

TKA02 Controlling area assignment

KEKO Product-costing header

KEPH Cost components for cost of goods manuf.

KALO Costing objects

KANZ Sales order items – costing objects

5.2.1 Cost center master data

CSKS Cost Center Master Data

CSKT Cost center texts

CRCO Assignment of Work Center to Cost Center

5.2.2 Cost center accounting

COSP CO Object: Cost Totals for External Postings

COEP CO Object: Line Items (by Period)

. COBK CO Object: Document header

COST CO Object: Price Totals

6 Sales and Distribution (SD) :

VBFA Document flow (alg.)

VTFA Flow shipping documents

6.1 Sales order :

VBAK Header data

VBAP Item data

VBPA Partners in sales order

VBKD Sales district data

VBEP Data related to line items, delivery lines

6.2 Billing document :

VBRK header data

VBRP Item data

6.3 Shipping :

VTTK Shipment header

VTTP Shipment item

VTTS Stage in transport

VTSP Stage in transport per shipment item

VTPA Shipment partners

VEKP Handling Unit – Header Table

VEPO Packing: Handling Unit Item (Contents)

6.4 Delivery :

LIKP Delivery header

LIPS Delivery item

6.5 Pricing :

KONH Conditions header

KONP Conditions items

KONV Procedure ( billing doc or sales order)

KOND

6.6 contracts :

VEDA Contract data

7 Material Management (MM) :

7.1 Material document

MKPF material document

MSEG material document (item level)

7.2 Purchasing

EKKO Purchase document

EKPO Purchase document (item level)

EKPV Shipping-Specific Data on Stock Tfr. for Purch. Doc. Item

EKET Delivery schedule

VETVG Delivery Due Index for Stock Transfer

EKES Order Acceptance/Fulfillment Confirmations

EKKN Account assignment in purchasing

EKAN Vendor address purchasing

EKPA Partner functions

EIPO Item export / import data

EINA Purchase info record (main data)

EINE Purchase info record (organisational data)

EORD Source list

EBAN Purchase requisition

EBKN Purchase Requisition Account Assignment

8 Warehouse Management (WM) :

8.1 Transfer requirement

LTBK Transfer requirement – header

LTBP Transfer requirement – item

8.2 Transfer order

LTAK Transfer order – header

LTAP Transfer order – item

8.3 Master data – stock positions

LQUA Quants

8.4 Inventory documents in WM

LINK Inventory document header

LINP Inventory document item

LINV Inventory data per quant

9 Quality Management (QM) :

9.1 Inspection lot / info record

QALS Inspection lot record

QAMB Link inspection lot – material document

QAVE Inspection usage decision

QDPS Inspection stages

QMAT Inspection type – material parameters

QINF Inspection info record (vendor – material)

QDQL Quality level

QDPS Inspection stages

9.2 Quality notification

TQ80 Notification types

QMEL Quality notification

QMFE Quality notification – items

QMUR Quality notification – causes

QMSM Quality notification – tasks

QMMA Quality notification – activities

QMIH Quality message – maintenance data excerpt

9.3 Certificate profile

QCVMT Certificate profile characteristic level: texts

QCVM Certificate profile characteristic level

QCVK Certificate profile header

10 Production Planning (PP)

10.1 Work center

CRHH Work center hierarchy

CRHS Hierarchy structure

CRHD Work center header

CRTX Text for the Work Center or Production Resource/Tool

CRCO Assignment of Work Center to Cost Center

KAKO Capacity Header Segment

CRCA Work Center Capacity Allocation

TC24 Person responsible for the workcenter

10.2 Routings/operations

MAPL Allocation of task lists to materials

PLAS Task list – selection of operations/activities

PLFH Task list – production resources/tools

PLFL Task list – sequences

PLKO Task list – header

PLKZ Task list: main header

PLPH Phases / suboperations

PLPO Task list operation / activity

PLPR Log collector for tasklists

PLMZ Allocation of BOM – items to operations

10.3 Bill of material

STKO BOM – header

STPO BOM – item

STAS BOMs – Item Selection

STPN BOMs – follow-up control

STPU BOM – sub-item

STZU Permanent BOM data

PLMZ Allocation of BOM – items to operations

MAST Material to BOM link

KDST Sales order to BOM link

10.4 Production orders

AUFK Production order headers

AFIH Maintenance order header

AUFM Goods movement for prod. order

AFKO Order header data PP orders

AFPO Order item

RESB Order componenten

AFVC Order operations

AFVV Quantities/dates/values in the operation

AFVU User fields of the operation

AFFL Work order sequence

AFFH PRT assignment data for the work order(routing)

JSTO Status profile

JEST Object status

AFRU Order completion confirmations

PRT’s voor production orders

AFFH PRT assignment data for the work order

CRVD_A Link of PRT to Document

DRAW Document Info Record

TDWA Document Types

TDWD Data Carrier/Network Nodes

TDWE Data Carrier Type

10.5 Planned orders

PLAF Planned orders

10.6 KANBAN

PKPS Kanban identification, control cycle

PKHD Kanban control cycle (header data)

PKER Error log for Kanban containers

10.7 Reservations

RESB Material reservations

RKPF header

10.8 Capacity planning

KBKO Header record for capacity requirements

KBED Capacity requirements records

KBEZ Add. data for table KBED (for indiv. capacities/splits)

10.9 Planned independent requirements

PBIM Independent requirements for material

PBED Independent requirement data

PBHI Independent requirement history

PBIV Independent requirement index

PBIC Independent requirement index for customer req.

11 Project system (PS)

11.1 Basic data

PRHI Work Breakdown Structure, Edges (Hierarchy Pointer)

PROJ Project definition

PRPS WBS (Work Breakdown Structure) Element Master Data

RPSCO Project info database: Costs, revenues, finances

MSPR Project stock

11.2 Equipment

EQUI Equipment master data

EQKT Equipment short text

EQUZ Equipment time segment

12 Plant maintenance (PM)

IHPA Plant Maintenance: Partners

OBJK Plant Maintenance Object List
ILOA PM Object Location and Account Assignment

AFIH Maintenance order header

12.1 Human resources

12.2 Settings

T582A Infotypes: Customer-Specific Settings

12.3 Master data

T527X Organizational Units

T528T Position Texts

T554T Attendance and Absence Texts

T501 Employee group

T503 Employee group, subgroup

T503K Employee subgroup

T510N Pay Scales for Annual Salaries (NA)

T549A Payroll Accounting Areas

T750X Vacancy

12.4 Infotypes

PA0001 Org. Assignment

PA0002 Personal Data

PA0006 Addresses

PA0007 Planned Working Time

PA0016 Contract elements

PA0008 Basic pay

PA0105 Communications

PA1007 Vacancies

PA1035 Training

PA2001 Absences

What is SAP ERP

admin — Thu, 21 May 2009 08:49:32 +0000

The SAP ERP application is an integrated enterprise resource planning (ERP) software manufactured by SAP AG that targets business software requirements of midsize and large organizations in all industries and sectors. It allows for open communication within and between all company functions.

Overview

SAP stands for Systems, Applications and Products. It uses the concept of modules (“individual programs that can be purchased, installed, and run separately, but that all extract data from the common database”).SAP AG, the company that provides the enterprise resource planning solution has upgraded the package and lauched it as SAP ECC 6.0 in 2005. ECC stands for Enterprise Central Component. The purpose of positioning it as ECC is to enable SAP to build and develop an environment of other products that can function upon the foundation of the central component.

SAP’s ERP solution includes several modules that support key functional areas – some of them are -

* SAP ERP Financials
* SAP ERP Logistics
* SAP ERP Human Resource Management

The evolution of mySAP ERP

SAP R/3 through version 4.6c consisted of various applications on top of SAP Basis, SAP’s set of middleware programs and tools.

When SAP R/3 Enterprise was launched in 2002, all applications were built on top of the SAP Web Application Server. Extension sets were used to deliver new features and kept the core as stable as possible. The Web Application Server contained all the capabilities of SAP Basis.

As a result of marketing changes and changes in the industry, other versions of SAP have been released that address these changes. The first edition of mySAP ERP was launched in 2003 and bundled previously separate products, including SAP R/3 Enterprise, SAP Strategic Enterprise Management (SEM) and extension sets. The SAP Web Application Server was wrapped into NetWeaver, which was also introduced in 2003.

A complete architecture change took place with the introduction of mySAP ERP edition 2004. R/3 Enterprise was replaced with the introduction of ERP Central Component (SAP ECC). The SAP Business Warehouse, SAP Strategic Enterprise Management and Internet Transaction Server were also merged into SAP ECC, allowing users to run them under one instance. Architectural changes were also made to support an enterprise services architecture to transition customers to a services-oriented architecture.

More than 2,300 customers are using the latest version of mySAP ERP, since it was released in early 2005, according to SAP. SAP reported a 20% growth in new ERP license deals in the second quarter of 2005.

Benefits of SAP ERP

* ERP allows easier global integration (Barriers of currency exchange rates, language, and culture can be bridged automatically)
* Updates only need to be done once to be implemented company wide
* Provides real-time information, reducing the possibility of redundancy errors
* Creates a more efficient work environment making it easier for employees to do their job which leads to effectiveness