venerdì 26 marzo 2010

SAP TABLES

Customizing

General settings

Countries

T005 Countries

Currency

TCURC Currency codes
TCURR Wisselkoersen
TCURT Currency name
TCURX Decimal places for currencies.

Unit of measure

T006 Units of measure

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

Enterprise structure

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

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

Financial accounting

Company code

T004 Chart of accounts
T077S Account group (g/l accounts)
T009 Fiscal year variants
T880 Global company data
T014 Credit control area

Fi document

T010O Posting period variant
T010P Posting Period Variant Names
T001B Permitted Posting Periods
T003 Document types
          T012 House banks

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


Basic data / administration

Workbench related tables

Data dictionary tables

DD02L Tables in SAP
DD02T Tables description
DD03L Field names in SAP
DD03T Field description in SAP

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

Administration

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

Batch input queue

APQD DATA DEFINITION Queue
         APQI Queue info definition

Job processing

TBTCO Job status overview table
TBTCP Batch job step overview

Spool

TSP02 Spool: Print requests

Runtime errors

SNAP Runtime errors

Message control

TNAPR Processing programs for output
NAST Message status
NACH Printer determination

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

Change documents

CDHDR Change document header
CDPOS Change document positionen
JCDS Change Documents for System/User Statuses (Table JEST)

Reporting tree table

SERPTREE Reporting: tree structure

LIS structure/control tables

TMC4 Global Control Elements: LIS Info Structure

MASTER DATA :

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

Basic data text (sap script)

STXB SAPscript: Texts in non-SAPscript format
STXH STXD SAPscript text file header
STXL STXD SAPscript text file lines

Batches

MCHA Batches
MCH1 Batches
MCHB Stock : batches

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

Vendor

LFA1 Vendor master
LFB1 Vendor per company code
LFB5 Vendor dunning data
LFM1 Purchasing organisation data
LFM2 Purchasing data
LFBK Bank details

Customer – material info record

KNMT Customer material info record

Bank data

BNKA Master bank data

Characteristics :

Characteristics :

CABN Characteristics ( o.a. batch/vendor)
CABNT Characteristics description
CAWN Characteristics ( o.a. material)
CAWNT Characteristics description
AUSP Characteristic Values

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

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)

FI/CO :

FI :

Master data

SKA1 Accounts
BNKA Bank master record

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)

Payment run

REGUH Settlement data from payment program

REGUP Processed items from payment program

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

Cost center master data

CSKS Cost Center Master Data
CSKT Cost center texts
CRCO Assignment of Work Center to Cost Center

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


Sales and Distribution (SD) :


VBFA Document flow (alg.)
VTFA Flow shipping documents

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

Billing document :

VBRK header data
VBRP Item data

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)

Delivery :

LIKP Delivery header
LIPS Delivery item

Pricing :

KONH Conditions header
KONP Conditions items
KONV Procedure ( billing doc or sales order)
KOND

contracts :

VEDA Contract data


Material Management (MM) :

Material document

MKPF material document
MSEG material document (item level)

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

Warehouse Management (WM) :

Transfer requirement

LTBK Transfer requirement - header
LTBP Transfer requirement - item

Transfer order

LTAK Transfer order - header
LTAP Transfer order - item

Master data - stock positions

LQUA Quants

Inventory documents in WM

LINK Inventory document header
LINP Inventory document item
LINV Inventory data per quant


Quality Management (QM) :


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

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

Certificate profile

QCVMT Certificate profile characteristic level: texts
QCVM Certificate profile characteristic level
QCVK Certificate profile header

Production Planning (PP)

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

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

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

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

Planned orders

PLAF Planned orders

KANBAN

PKPS Kanban identification, control cycle
PKHD Kanban control cycle (header data)
PKER Error log for Kanban containers

Reservations

RESB Material reservations
RKPF header

Capacity planning

KBKO Header record for capacity requirements
KBED Capacity requirements records
KBEZ Add. data for table KBED (for indiv. capacities/splits)

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.

Project system (PS)

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

Equipment

EQUI Equipment master data
EQKT Equipment short text
EQUZ Equipment time segment



Plant maintenance (PM)

IHPA Plant Maintenance: Partners
OBJK Plant Maintenance Object List
ILOA PM Object Location and Account Assignment
AFIH Maintenance order header

Human resources

Settings

T582A Infotypes: Customer-Specific Settings

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

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

martedì 23 marzo 2010

Esempio di specifica controlli in LQUA con chiave LQNUM e utilizzo FM HU_CREATE_GOODS_MOVEMENT


la seguente modifica coinvolge le 3 transazioni di precarico (zwrf_1ot01 / 02 / 03) tenendo presente che nella 01 la lettura del singolo SSCC e la contestuale digitazione del tasto "enter" provoca la registrazione immediata ad ogni lettura di SSCC (1 to 1) e quindi l'elaborazione della funzione da integrare se viene rispettata la condizione di seguito descritta mentre nella 02 e 03 la lettura dell'SSCC prevede l'inserimento in una tabellina interna in attesa della conferma definitiva di + sscc alla digitazione del tasto funzione SALVA.

la modifica consiste in:

condizione principale:
solo e soltanto se l'OT (v_tanum - input iniziale delle 3 transazioni da modificare) è dedicato ad uno stock speciale (ltap-sonum diverso da zero accedendo in ltap con ltap-tanum = v_tanum_input - se trovi una pos con sonum diverso da 0 anche le altre idem) andSSCC1 letto in input alla transazione - v_sscc1_input - non ha il medesimo stock speciale della pos del v_tanum_input, ovvero LTAP-SONUM (accedendo con v_tanum) diverso da LQUA-SONUM (accedendo con LQNUM = v_ltap_NLQNR la procedura è descritta di seguito) mentre i campi matnr - charg - vlpla delle medesime tab LTAP ed LQUA corrispondono. questo controllo dovrebbe già essere implementato ma bisogna integrare la modifica in caso di sonum diversi. attualmente le transazioni bloccano il procedimento per incoerenza con il fabbisogno richiesto a monte del processo di vendita. questa seconda condizione la verifichiamo domani perchè la modfica dipende da come è stata implementata (se scatenata da una funzione std o custom).

solo se viene soddisfatta la condizione principale procedere con il seguente:
ogni qualvolta viene inserito il codice SSCC (v_sscc1_input) e digitato l'invio di tastiera bisogna avviare il controllo, di seguito descritto, preceduto dalla seguente lettura della qtà dell'SSCC letto in input alle transazioni:

estrazione della qta disponibile dell'SSCC letto in input:
accedere nella tab LEIN per LEIN-LENUM = v_sscc1_input per estrarre il valore del campo LEIN-BTANR (v_lein_btanr).
accedere in LTAP con LTAP-TANUM =v_lein_btanr and LTAP-NLENR = v_sscc1_input per estrarre LTAP-NLQNR (= v_ltap_NLQNR).
accedere in LQUA con LQUA-LQNUM = v_ltap_NLQNR per estrarre il valore del campo lqua-gesme = lqua-verme (devono essere uguali i due valori dei due campi qtà per essere ritenuta qtà disponibile) da assegnare alla variabile v_qta_sscc1_input (usata nel check successivo).

verifica condizione per avviare il trasferimento SSCC tra due contratti a parità di materiale/partita/ubicazione/qtà disponibile:
accedere nella tab. LQUA per ogni (lqua-lqnum diverso da v_ltap_nlqnr) and (lqua-lgnum = v_lgnum) and (lqua-bestq = space) and (lqua-sonum diverso da space and diverso da lqua-sonum relativo al record lqua-lqnum = v_ltap_nlqnr) per verificare se esiste un SSCC1_output che ha le stesse caratteristiche dell'SSCC1 e che quindi rispetta la seguente condizione:

lqua-charg = ltap-charg (stessa partita)
lqua-matnr = ltap-matnr (stesso materiale)
lqua-lgpla = ltap-vlpla (stessa ubicazione)
lqua-gesme = lqua-verme = v_qta_sscc1_input (stessa qtà)

se si verifica la condizione di cui sopra:
estrarre il valore di LQUA-LENUM da assegnare a v_sscc1_output e il corrispondente valore di lqua-sonum
avviare due volte in modo accoppiato (una per ogni SSCC1 letto in input e relativamente per l'SSCC1_output selezionato alla condizione precedente) la funzione HU_CREATE_GOODS_MOVEMENT già utilizzata nelle tcode ZWRF_TR02 e ZWWS_TR02. Per le strutture e i dati da alimentare nella funzione puoi prendere come riferimento le transazioni citate. ti segnalo di seguito solo le strutture alimentate se l'elaborazione viene avviata dalla HUMO:

se non si verifica la condizione inviare messaggio di errore "SSCC letto non è coerente con il contratto del cliente". Questo messaggio va bene nella zwrf_1ot01 mentre nelle restanti due è da adattare. domani vediamo come.

IT_MOVE_TO:
HUWBEVENT = 0016 (fisso)
SONUM = v_lqua_sonum (corrispondente la prima volta a lqua-sonum di v_sscc1_input e la seconda volta a lqua-sonum di v_sscc1_output)
IT_INTERNAL_ID:
VENUM = v_vekp_venum (corrispondente la prima volta a v_sscc1_input la seconda volta av_sscc1_output)

WM Available Check for Block Storage Type

È stato aggiunto questo paragrafo per descrivere la modalità di verifica in caso di incoerenza tra disponibilità dello stock di WM, visibile in LX03, e le seguenti casisitiche:

  • l’impossibilità di prelevare lo stock individuato attraverso le 3 transazioni di precarico.
  • registrare il cambio di stato con la HUMO, controllare le tabelle LQUA LQUAB per i tipi magazzini di stock AF1/SF1 - AI1/SI1.

In questi casi d’incoerenza verificare le seguenti tabelle LQUA e LQUAB:
Controllare la coerenza delle tabelle LQUA e LQUAB accedendo per i filtri indicati nella figura seguente:
I valori di quantità disponibile presenti nella tabella LQUA sono gli stessi di quelli visibili nel report LX03.
Se in LX03 (LQUAB) risulta disponibile la quantità per il prelievo ma in effetti la strategia di prelievo non trova tale quantità attesa bisogna verificare la tabella LQUAB con i seguenti filtri aggregati rispetto alla selezione in LQUA:

Il campo lquab-Aofta identifica le pos. OT aperte che impegnano le partite del materiale aggregate per materiale, tipo magazzino, partita e ubicazione (chiavi della tabella).
Se il campo lquab-Menge = 0 and aofta = 1 significa che le “quantità totali” sono IMPEGNATE in 1 posizione di un OT aperto che toglie dalla disponibilità, ai fini del prelievo, tali quantità.
Per allineare le quantità disponibili in LQUA e LQUAB, bisogna utilizzare il report LT24 per ricercare gli OT che impegnano le partite che il report LX03 si aspetta disponibili.
Dopo aver trovato gli OT che impegnano le partite, bisogna verificare gli OT e cancellarli per allineare la quantità della tabella LQUAB a quella della tabella LQUA. Dopo aver cancellato tali OT, la situazione della tabella LQUAB si modifica allineando la quantità con quella della tabella LQUA e il campo AOFTA si riporta a ‘0’.
Se lquab-menge diverso da ‘0’ and aofta = 0 significa che il quant totale corrisponde anche alle quantità disponibili in LQUA-VERME dato che non ci sono posizioni di OT aperte per le chiavi della tabella lquab. Questa condizione è quella in cui le tabelle LQUA e LQUAB risultano allineate in termini di quantità disponibili.
Il caso preso in esame si riferisce ad un’anomalia in cui, dopo aver creato l’OT di 1° livello, la consegna del gruppo è stato cancellato abortendo il processo. I dati analizzati sono visualizzabili alla data d’invio del presente documento.

domenica 21 marzo 2010

HUMO: Maintain Goods Movements for Handling Unit Stock-Posting

You can define the movement types that are used for HU-specific material postings. The Packing process defines the movement type with which the packed (or unpacked) material is transferred between HU-managed storage locations and non-HU storage locations. You can use the other processes during the posting process in the Handling Unit Monitor and in the Goods Movements for Handling Units and Materials transaction.

Standard settings

All the processes are delivered with the standard movement types.

Recommendation

The movement type standards should not be changed for the individual processes. If you try to change the packing/unpacking processes, it could result in stock inconsistencies. Changes in the other processes could cause some input fields for other movements to become inactive.

Further notes

The individual processes, with the exception of unpacking, may not contain reversal movement types.


Process that uniquely identifies an HU goods movement Description HU Stock category MM mvt Status transfer
from - to
4 Transfer to inspection stock S - blocked 349 S > Q
4 Transfer to inspection stock Space – available stock 322 Space > Q
5 Transfer posting to blocked stock Q – quality 350 Q > S
5 Transfer posting to blocked stock space - available stock 344 Space > S
22 Transfer posting blocked -> unrestr. Space - available stock 343 S > space
3 Transfer posting to released stock S – blocked 343 S > space
1 Pack (non-HU storage location to HU storage location) S – blocked 325 S > S


domenica 28 febbraio 2010

Warehouse Structure With WMS


When you implement the Warehouse Management System (WMS) in a plant, you define the individual warehouses (high-rack storage, block storage, picking area, and so on) as storage types within a warehouse complex and group them together under a warehouse number. As a rule, it is not necessary to define several storage locations for a plant since you assign the WMS warehouse number to a storage location from Inventory Management (IM).
It is appropriate to define further storage locations for a plant if other warehouses (storage types) exist within a plant that is not managed using WMS but with Lean WM, for example.

You can also manage stock for several plants in the same warehouse at the same time. In this case, the same warehouse number is assigned to the storage locations for these plants.

As a rule, it is a good idea to manage only the stocks of one storage location and the same plant within a warehouse number. However, you can also manage several storage locations of one and the same plant within a warehouse number.

The warehouse structure in Warehouse Management is hierarchical and consists of the following elements:
  • The Warehouse Number
You can define an entire physical warehouse complex in WM using a single warehouse number.
  • The Storage Type
Each of the warehouse facilities or areas that make up the warehouse complex can be defined as a type of storage area or ”storage type” on the basis of its spatial, technical, and organizational characteristics. Each storage type is divided into storage sections. A storage section generally includes all bins that have certain characteristics in common, such as bins for ”fast-moving items” near a goods issue area.
  • The Storage Bin
Each storage type and storage section consists of a row of storage spaces that are referred to in WMS as storage bins. The coordinates of the bins indicate the exact position in the warehouse where goods can be stored.
  • The Quant
The quant serves to perform inventory management of a material at the storage bin.