cancel
Showing results for 
Search instead for 
Did you mean: 

WBS Element deletion

Former Member
0 Kudos

Hello All,

I need to delete WBS elements which don't have status Asset Under Construction. If I delete WBS on the above condition, can u tell me which all tables will get affected? If I don't use a BAPI and code manually to delete all dependency entries, then what all dependent table I must consider?

Thanks in advance

Sugata Basu

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Sugata Basu,

Reward me, since I am giving the complete cycle of Archiving and deletion.

For checking the effect of tables effected by any Object in SAP for deletion or Archiving, follow the following steps.

Go to Trs. AOBJ

Select the appropriate Archiving object (In your case PS_PROJECT)

Then go to Trs. SARA.

Insert the selected object in Object name (In your case PS_PROJECT) and select Database tables.

In your case the following tables will be affected:

AFAB Network - Relationships

AFFH PRT assignment data for the work order

AFFL Work order sequence

AFFT Order - Process Instructions

AFFV Order - Process Instruction Values

AFFW Goods Movements with Errors from Confirmations

AFIH Maintenance order header

AFKO Order header data PP orders

AFPO Order item

AFRU Order Confirmations

AFSPOPR Split Operations in an Order Split

AFSPREL Relation Between Orders in an Order Split

AFVC Operation within an order

AFVU DB structure of the user fields of the operation

AFVV DB structure of the quantities/dates/values in the operation

AFWI Subsequently posted goods movements for confirmations

ANLI Link table for investment measure -> AuC

AUAI Settlement Amounts per Depreciation Area

AUAK Document Header for Settlement

AUFK Order master data

AUFM Goods movements for order

AUSP Characteristic Values

BPBK Doc.Header Controlling Obj.

BPEG Line Item Overall 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.

BPHI Cross-hierarchy Data Controlling obj.

BPIG Budget Object Index (Overall Budget)

BPIJ Budget Object Index (Annual Budget)

BPJA Totals Record for Annual Total Controlling Obj.

BPPE Totals Record for Period Values Controlling Obj.

BPTR Object Data Controlling Obj.

CABN Characteristic

CABNT Characteristic Descriptions

CAWNT Value Texts

CDCLS Cluster structure for change documents

CDHDR Change document header

CDPOS_UID Additional Table for Inclusion of TABKEY>70 Characters

CKHS Header: Unit Costing (Control + Totals)

CKHT Texts for CKHS

CKIP Unit Costing: Period Costs Line Item

CKIS Items Unit Costing/Itemization Product Costing

CKIT Texts for CKIS

COANZ Index of Objects With Down Payments/Requests

COBK CO Object: Document Header

COBK_INDX Index in COBK for ORGVG

COBRA Settlement Rule for Order Settlement

COBRB Distribution Rules Settlement Rule Order Settlement

COCH Process Management: Control Recipe Header

COCHP PI sheet: Control Recipe Header

COCOA Process Management: Operation Assignment Table

COEJ CO Object: Line Items (by Fiscal Year)

COEJL CO Object: Line Items for Activity Types (by Fiscal Year)

COEJR CO Object: Line Items for Stat. Key Figures (by Fiscal Year)

COEJT CO Object: Line Items for Prices (by Fiscal Year)

COEP CO Object: Line Items (by Period)

COEPB CO Object: Line Items Variance/Period-Based Results Analysis

COEPBR CO Object: Valuated Line Item Settlement

COEPD CO Object: Line Item Settlement, Not Valuated, With Status

COEPL CO Object: Line Items for Activity Types (by Period)

COEPR CO Object: Line Items for Stat. Key Figs (by Period)

COEPT CO Object: Line Items for Prices (by Period)

COER Sales Order Value Revenue

COES CO Object: Sales Order Value Line Items

COFIV PI Sheet: Signature for Deviation

COFMA PI Sheet: Message Assignment to Process Instruction

COFP Document Lines (project cash management)

COFT Process Management: Process Instructions in Control Recipe

COFTP PI Sheet: Process Instructions

COFV Process Management: Process Instr. Charact. in Ctrl Recipe

COFVP PI Sheet: Process Instruction Characteristics

COKA CO Object: Control Data for Cost Elements

COKL CO Object: Control Data for Activity Types

COKP CO Object: Control Data for Primary Planning

COKR CO Object: Control Data for Statistical Key Figures

COKS CO Object: Control Data for Secondary Planning

COMEP PI Sheet: Message Characteristics

COMER Process Message Record: Message Characteristics

COMHP PI Sheet: Message Header

COMHR Process Message Record: Message Header Data

COMQ Temporary Storage for Material Production Messages for QM

COOI Commitments Management: Line Items

COSB CO Object: Total Variances/Results Analyses

COSBD CO Object: Total of variances/accruals, of which settled

COSL CO Object: Activity Type Totals

COSLD CO Object: Activity Type Totals - of Which Settled

COSP CO Object: Cost Totals for External Postings

COSPD CO Object: Settled Primary Cost Totals

COSPP Transfer of the Order in the COSP Table to the Project

COSR CO Object: Statistical Key Figure Totals

COSS CO Object: Cost Totals for Internal Postings

COSSD CO Object: Settled Secondary Cost Totals

COSSP Transfer of the Order COSS Table to the Project

COST CO Object: Price Totals

COTRP PI Sheet: Process Parameter Texts (Versions)

COVLP PI Sheet: Current Variable Values

CUCO Additional Data for Configurable Objects

CUVT Variant Table

DJEST Individual Status per Object: Key Date Based Management

DRAD Document-Object Link

DRAD_PORDER Attributes for Links: Document to Production Order

EBAN Purchase Requisition

EBII CO/SD document flow: billed portions of expense items

EBKN Purchase Requisition Account Assignment

ESKL Account Assignment Specification: Service Line

ESLH Service Package Header Data

ESLL Lines of Service Package

ESUC Ext. Services Management: Unplanned Limits on Contract Item

ESUH Ext. Services Management: Unpl. Service Limits: Header Data

EVFG CNE5: Percentage of completion

EVOF CNE5: Object parameter PS earned value analysis

EVOP Object parameters

EVPOC Percentage of completion

FMSP Copy FMSU table order to project

FMSU FI-FM Totals Records

IBIB IB: Installed Base/IBase

IBIBOBS IB: IBase observer

IBIBT IB: Installed base short texts

IBIN IB: Component/instance

IBINDOMAINS IB: Redundant design object <Char. domains for instance>

IBINOBS IB: Observer of an IBase instance

IBINOWN IB: Owner of an IBase instance

IBINT IB: Component short texts

IBINVALUES IB: Characteristic values and restrictions for instance

IBSP IB: Specialization

IBST IB: Structure

IBSTREF IB: Reference to master data structure

IBSYMBOL IB: Symbol

IHPA Plant Maintenance: Partners

ILOA PM Object Location and Account Assignment

INOB Link between Internal Number and Object

JCDO Change Documents for Status Object (Table JSTO)

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

JEST Individual Object Status

JSTO Status object information

KALC Material Quantity Calculation - Formulas

KALT Material Quantity Calculation: Header

KOCLU Cluster for conditions in purchasing and sales

KONH Conditions (Header)

KONM Conditions (1-Dimensional Quantity Scale)

KONP Conditions (Item)

KONW Conditions (1-Dimensional Value Scale)

KSSK Allocation Table: Object to Class

LFINF Delivery information Project System

LFINFX Assignment delivery information to Project System objects

MCAFKOV Versions: Order Header Data - PP Orders

MCAFPOV Versions: Order Item

MCAFVGV Versions: Order Procedure

MCKALKW Versions: Cost Itemization

MLST Milestone

MLTX Milestone Description

ONR00 General Object Number

ONROF Object number index for production resource order

ONROK Object number index for material component/reservation

ONROR Object Number Index, Order

ONROS Object number index for order sequence

ONROV Object number index for order process

ONRPD Object number index for project

ONRPR Object number index for project structure element

PRHI Work Breakdown Structure, Edges (Hierarchy Pointer)

PROJ Project definition

PRPS WBS (Work Breakdown Structure) Element Master Data

PRTE Scheduling Data for Project Item

PRTP Subprojects

PRTX PS Texts (WBS)

PSERB Inheritance data, Project System

PSERBV Inheritance administration, Project System

PSERBZ Inheritance run: Object assignments, Project System

PSLI Reference: Delivery from project

PSMERK Characteristics for summarization w/o class., Project System

PSTX PS Texts (Header)

RESB Reservation/dependent requirements

RKPF Document Header: Reservation

RPSCO Project info database: Costs, revenues, finances

RPSQT Project info database: quantities

RSADD Additional fields for reservation

RSDB Index of the RESB for the Direct Procurement Element

STPO BOM item

STXB SAPscript: Texts in non-SAPscript format

STXH STXD SAPscript text file header

STXL STXD SAPscript text file lines

SWOR Classification System: Keywords

TC71 Digital Signature

TC71D Signed Document for Signature

TC74 Digital Signature for PI Sheet

TCN01 Key Word Text for PS User Fields

TCNTM05 Assignment Components to Groups

TCNTM06 Dates for Components, Events and Date Type

TCNTM07 Status of a Date Type for a Component

TPI03 CO Objects: Date of Last Interest Run

TZIN1 Document Header Data from Source Document (PS Int.Calc.)

TZIN2 Interest Document:Segment Int.Indicator & Valuation Category

TZIN3 Interest Document: Currency Type Segment

TZIN4 Interest Document: "Objects Affected" Segment

VPKDLI Sales Pricing Dynamic Items

VPKHEAD Sales Pricing Header Data

VPKSDITEM Sales Pricing Header Data (Specific to SD)

VSAFAB_CN Version: Network relationships

VSAFFH_CN Version: PRT allocation to work order

VSAFFL_CN Version: Order sequences PP orders

VSAFIH_CN Version: Order header for plant maintenance

VSAFKO_CN Version: Order header data for PP orders

VSAFPO_CN Version: Order items in PP orders

VSAFVC_CN Version: Operation in order

VSAFVU_CN Version: User fields in operation in order

VSAFVV_CN Version: Quantities/Dates/Values in order operation

VSAUFK_CN Version: Order master data

VSEBAN_CN Version: Purchase requisition

VSEBKN_CN Version: Purchase requisition account assignment

VSFPLA_CN Version: Billing schedule

VSFPLT_CN Version: Billing schedule: Dates

VSJEST_CN Version: Individual status per object

VSJSTO_CN Version: Information on status object

VSKBED_CN Version: Capacity requirement records

VSKBEZ_CN Version: Additional data for table KBED (ind. capacities)

VSKOPF Version: Header - general data for a version -

VSMLST_CN Version: Milestone

VSNPTX_CN Version: PS texts (network)

VSPLAF_CN Version: Planned order

VSPRHI_CN Version: WBS, edges (hierarchy pointer)

VSPROJ_CN Version: Project definition

VSPRPS_CN Version: WBS Element (Work Breakdwn Struc. Elem.) Mast. Data

VSPRTE_CN Version: Scheduling data for project item

VSPRTX_CN Version: PS texts (WBS)

VSPSTX_CN Version: PS texts (header)

VSRESB_CN Version: Reservation/Dependent requirements

VSRPSCO_CN Version: Cumulation table for project reporting

VSRSDB_CN Version: Index of RESB for direct procurement elements

VSSTEU Version: Control table - one entry per version object -

VSVBAK_CN Version: Sales document: Header data

VSVBAP_CN Version: Sales document: Item data

VSVBEP_CN Version: Sales document: Schedule line data

VSVBKD_CN Version: Sales document - commercial data

Former Member
0 Kudos

Hi dude,

your answer is very much helpful to me, although it's not the complete solution. But still I shall give you some marks. My solution will be complete if you could answer the following,

1. How the parent child relation of WBS elements are maintained? In which table (I guess PRPS itself but question is how and through which field?) field and what is the convention (if any?)?

2. If I delete WBS elements manually means through custom report program, without any BAPI (using delete command of SQL), what all tables may get affected? In the other way, during deletion, what all table entries corresponding to that record need to be deleted so that there is no inconsistency remaining at the Database ? I am not asking for all the PS tables (and only PS tables).

Waiting for your reply.

Thanks in advance,

Sugata Basu

Answers (1)

Answers (1)

schneidertho
Advisor
Advisor
0 Kudos

I would not develop such a report. WBS elements are so highly integrated into other areas, that I would always use a BAPI. Best regards, Thorsten