Purpose
This WIKI page is intended to provide list of tables that explains the storage of configuration values.
You can find the flow of how CUOBJ can be helpful while finding other important information related to VC
Overview
The configuration of an object in an application is stored is TABLE_APPLICATION-CUOBJ. CUOBJ can be
fetched from below list of tables.
Table | Discription |
|---|---|
AFPO | Production Order |
PLAF | Plan Order |
RESB | Reservation |
VBAP | Sales Order |
EKPO | Purchasing Document Item |
EBAN | Purchase Requisition |
EQUI | Equipment master data |
MARC | For cross-plant material variant |
|
|
Use CUOBJ and run transaction CUTABLEINFO
There you get all relevant configuration data stored in different tables on the data base on one screen.
TABLE | DESCRIPTION | IMPORTANT FIELDS |
IBIB | Basic data | Ibase, OBJNR |
IBIN | Instance | Instance (=ibase+1) |
In_recno (internal uni identif) | ||
Valfrom, valto, cuco (profile) | ||
IBINOWN | Owner of instance | Inttyp, (obtab), objkey |
IBINVALUES | Characteristic values of an instance | Sybmol_id, ataut |
IBSYMBOL | Char-value combinations | Atinn, atwrt, atflv |
Note :- For plant independent material variants (client specific ) configuration instance is created in CUOBF
instead of CUOBJ. This field is stored in table MARA.
You can then use this CUOBF in transaction CUTABLEINFO (same way as you would use CUOBJ) to view the
configuration data.
SAP Note: 1547034 - How are characteristic values updated in table AUSP?