When is the CO Validation / Substitution NOT called ?

When is the CO substitution NOT called?

• For negative postings that is, reversals that do not consist of an inverse posting but of an inversion of the CO document to be reversed. In negative postings the system only considers the posting information from the document to be reversed, a 'derivation' via substitution is not defined. For example, negative postings are carried out in the context of manual actual postings (KBXXN), CATS transfers, confirmations or billing documents.
• For all planning transactions.

The exception is the planned settlement for which it will run as part of the master record check for the settlement receivers. However, only the information required for the master record checks is available there (no posting details).

• For balance sheet accounts
• For postings to balance sheet accounts without cost elements in CO
• For posting IDocs (CODCMT) via ALE
• For goods receipt or invoice receipt for the goods receipt/invoice receipt clearing account (account key = WRX/WRY)
• For reposting line items (KB61) for the old line item

 

When is CO validation (OKC7) NOT called?

 

• In all cases in which the substitution is NOT called
• In the follow-up posting mode of the CO account assignment
• For the allocations (assessment, distribution, periodic reposting, indirect activity allocation), validation is not called at point 2

FZ003 : Company codes &/& do not appear in proposal & &; correct

Reasons :

- no line items
- config miss
- There will be no dues as of that run date..now post an invoice today and run payment tomorrow date provided payment terms should be payment immediately..

if u really want to run then change the payment terms and check wheter it is due for payment then run APP.

- This is normal issue for this issue delete the all uncompleted proposals,
check the run date dropdown button,there uncompleted proposal(yet to be payment completed)available May be those invoice stored in that proposals

Path:Menu>Edit>Proposal>Delete

After selecting the RUN DATE and IDENTIFICATION.

Please go to EDIT TAB
STEP 1) EDIT-->PAYMENTS-->DELETE OUTPUT.
STEP2) EDIT-->PROPOSAL-->DELETE.
STEP3) EDIT-->PARAMETERS-->DELETE. If this option is active.

- First check whether the Vendor is blocked in any other incomplete Payment run - proposal is created but it is not completed.

Further, in transaction code FBZP in the tab Bank Selection check the ranking order. Also check the Bank accounts.

The best to analyze the problem is to read the log as it will give the details where exactly it is failing. So in the parametrs select the log check boxes.

- The proposal run date and the next date are to be checked for each of the earlier APP Runs that are not posted. Ensure that there are no duplications.

The second most important point is that as long as the proposal is pending the items are locked for further processing. Hence delete all the earlier payment runs which are not posted and pending. The parameters and the proposal are to be deleted for each of the pending payment runs.

This shall solve the problem.

-  You can check in table REGUS with the company code and/ or vendor to easily find such incomplete proposals.

- The issue was my due date. I changed the baseline date to an earlier date so that my payment became due

- Normally the error FZ003 appears if you create a payment proposal
for some payment ID, date; then leave it as is; then create another
payment ID, date and execute payment proposal generation. Vendors/
customers are blocked in the first payment proposal.so pls.check whether you have several other proposals which are outstanding. if yes, then you
could delete these payment proposals or execute the payment runs to
the end. This action will allow to execute subsequent payment runs as
company code will be unblocked for the subsequent payment runs by
the system. Don't forget to delete unsuccessful payment proposals
(with error FZ003) and run proposal generation again.

Addition, if you selected the payment method C in free selection tab, the
field name is LFB1-ZWELS , not BSEG-ZLSCH.

Please also check the due date of the posted invoices of the vendor,
the payment run parameters especially the fields 'docs entered up
to' and 'customer items due by' fields.

SAP-COPA: Source and Target Fields

Source and Target Fields:

 

Use: You enter the source and target fields for derivation in a derivation step.

 

Source fields:

 

You can use the following operating concern fields as source fields:

 

• All fixed characteristics
• All user-defined characteristics
• All characteristics copied from SAP tables or from the field catalog
• All characteristics copied from customer hierarchies (CO-PA HIE01 to HIE10)
• All quantity unit fields (CO-PA *_ME)

 

Target fields:

 

You can use the following fields as target fields for derivation:

 

• All user-defined characteristics
• All characteristics copied from SAP tables or from the field catalog
• All characteristics copied from customer hierarchies (CO-PA HIE01 to HIE10)
• Only the following fixed characteristics:
• Customer number (CO-PA KNDNR)
• Product number (CO-PA ARTNR)
• Business area (CO-PA GSBER)
• Profit center (CO-PA PRCTR)
• Sales organization (CO-PA VKORG)
• Distribution channel (CO-PA VTWEG)
• Division (CO-PA SPART)
• Plant (CO-PA WERKS)
• All quantity unit fields (CO-PA *_ME)
• Temporary fields (GLOBAL USERTEMP1 to GLOBAL USERTEMP8)

SAP CO: Statistical & Real Posting

WBS element/Cost Center/Internal Order is a real CO object where as Profit Center is a Statiscal Object. All the posting you make to the real object are real postings, paralelly statistical posting will be flown to your profit center.

Internal Orders are two types. 1. Real and 2. Statistical.
Real orders get real postings and statistical orders get statistical.
Statistical means information purpose only.
Statistical orders cannot be settled.
At the time of postings to cost elements you must have at least one real object.

If you give more than one real object, read the following:

When you two real objects like cost center and WBS element at the time of posting a journal voucher, the WBS element prevails as a real object and the two statistcal postings will be posted. One to cost center and the second one to the profit center assigned in the WBS element.

Differences : SAP FI & SAP CO

Deactivation & Retirement of Asset :

When asset is sold or scrapped with retirement posting, the asset value date is updated as deactivation date.
You can also plan deactivation of asset by entering future date in deactivation date field asset master data.

ABGF and AB08 :

AB08 is used to Reverse the amount posted to an asset - reverses the asset document.
ABGF is for passing a credit memo using an adjustment account(offsetting account) in the next year.

KO88 and KO8G :

KO88 is used for settling single order (more like day to day work) used settlement to final asset
KO8G is used periodical to select a group of internal orders used periodical posting for AUC

Asset History and Asset History Sheet:

the Asset History is a report which shows the complete history of an asset. All information such as master data, depreciation area definition, development over the years of useful life. Further more this report uses SAP Script.
The Asset History Sheet is a report which shows the value flow (= value history) for one year in the asset useful life.

Manual depreciation and Unplanned depreciation :

Manual depreciation is when you use in the asset a manual depreciation key.
Unplanned depreciation you use aditional on a Manual or an other depreciation rule.

GL Planning & Cost element planning:

GL Planning would be carried out in FI and can be done for all P&L and B/S GL accounts. In case controlling is active then you can try for Cost element planning for P&L accounts. The Cost element planning will also be made use of for activity type plan price calculation in product costing

BADI and USER-EXIT:

i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.

LIV and Normal Invoice document :

LIV is useful for verifying goods which related to MM. When goods purchased or when received verifying the invoice details like quantity, rate, invoice number etc., PO with the invoice. LIV is linked to FI and MM. But FI inovice is creating only in FI, it no where linked to any module.
Entries are different in both cases.

Consolidated Business Area and Cost Center Grouping :

Business consolidation is for more of consolidation purpose and cost center grouping is more for management reporting purpose for cost control purposes.Both the organizational units serve for different purposes. Consolidatied business will not have much meaning unless you go with EC-CS.Cost Center Groups are much for control purpose and help in managerial reporting.Business Units are part of FI Organizational Structure and Cost Centers are part of CO organizational structures.

COPA & PCA :

In Profit Center Accounting Costs and Revenue are matched to find the profitability of the Investment Center. The shared services expenses are allocated equitably in between the profit centers to find our the accurate ROI of the Investment Centers. Here you will get the Segmental Profit and loss account.

Whereas in the case of COPA, we get Product profitability upto Net income before Corporate tax. The Cost of Sales is matched with the revenue to get the gross margin per each product as well as marketing segment. Then selling overhead and Corporate expenses are allocated to the products on the basis of revenue and we get EBITDA(Earnings before Interest, Debenture interest and tax. The Longterm Interest and debenture interest shall also be allocated to the products equitably. Consequently, it is able to know the profitability of the products before payment of tax.

TAXINJ & TAXINN :

The only difference between TAXINJ & TAXINN is that TAXINJ is formula
based tax procedure which is dependant to a large extent on routines
to calculate taxes at each level.

TAXINN on the other hand is condition based tax procedure which is very
similar to the standard pricing procedure & is not dependant on routines
and other programs to fetch taxes. It is simply dependant on condition
records maintained for each of the tax conditions.

Prior to R/3 Enterprise we had only formula-based and from R/3 Enterpri
version you will have the option of Formula-based or Condition-based.
If you select TAXINN, it will support only condition- based excise
determination. And if select TAXINJ, you will have the option of Formula
-based and Condition-based (in SD not MM).

If you have future plans for extending your organisation to our new
dimension product such as CRM....then using TAXINJ would mean that the
formulas would need to be copied/rewritten to the CRM IPC. Where as you
would not be required to do that in TAXINN....

So if you do not have any plans for extending SAP solutions in your
organisation then you can use TAXINJ, else it is recommended that you
use TAXINN only.

Controlling and enterprise contrilling :

In controlling module you define the cost centres and in enterprise controlling you define the profit centres.
SAP cannot generate the profit and loss acoount and balance sheet for every cost centre but can generate P&L and balance sheet for each and every profit centre.
Enterprise Controlling is a separate module altogrther and consists of Consolidation and PCA as well. Whereas Controlling is a module which consists of CCA ,PA,Product Costing ,IO etc

Activity Types & SKFs :

Stat key figures are just that they have no financial impact in Controlling but may be used for reporting
and allocation purposes etc.Activity type are associated with a sender (usually cost centre with a
specific rate). Activity type wil always carry rate against it where as SKF wont have any rate.. It means activity type
is used for both allocation and absorption where as SKF can only be used for allocation.

Example -

Activity types in production cost centers are machine hours or finished units.

Stat key figures are just that they have no financial impact in
Controlling but may be used for reporting and allocation purposes etc.
Activity type are associated with a sender (usually cost centre with a specific rate). When an activity posting is made with either CATS or KB21 a transfer posting is made for the quantity * rate . This creats a CO posting between 2 different objects (sender and receiver)
SKF is not a real cost object , it carries statistical posting only =so it solely for reporting and analysis. Hoewev activity type is use for cost allocation from one cost object to another. Activity type for example No of Employee, Production hr whcih we can use to charge production over head to production order.

CK91 and CK86 :

CK91 is creating a Procurement Alternative where you define that source of procurement for a said material / plant whether it would be stock transfer / production etc..
Where CK86 costing a material based on a Procurement alternative.

Production Order and Product Cost :

Transaction for product cost collector is KKF6n. the product cost collector for that particular material,plant for repetetive manufacturing, production version it is used. As cost is collect and settle on period base.
While the production order costing done on order bsae and settelment also carried for order.
In REM settlement is against a period. Because production is not dependent by order. So to settle the cost for all the orders in certain period ex. for a month product cost collector is required. In this product cost collector, cost will store for all the orders.
In Production order or process order, settlement against each order. So no need to create product cost collector.
In production orders can can be used as a Cost object. Since production order is a cost object the costs can be settled to the cost centers or Sales orders using the process order as a cost carrying object.
In REM there is no Production order. Hence Product Cost Collectors are used. The cost can be sttles period or quantity wise.

Useful Programs List :

Program name	Report title
BPCARRT0	Delete Budget Structure
BUPA_TEST_DELETE	Delete Business Partners
BUSDELE0	Delete Program
BWFS_TIMESTAMPS_DELETE_ALL_IS	Deletes Time Stamp for InfoSource
CACS_RESET_USERPARM	Change/Delete a User Parameter
CACSLOSF03	Delete Records
CKECP_DELETE_CE	Delete from Cost Estimate
CKML_RUN_DELETE	Delete Costing Run in Actual Costing
CN_CDHDR_PROJ	Change Document Header, Deleted Project: U -> D
CO_ALEITEM_DEL	Archiving of CO Line Items Distributed with ALE: Delete Program
CO_CCMAST_DEL	Archiving Cost Center Master Data: Delete Program
CO_TOTAL_DEL	Archiving CO Totals Records: Delete Program
EC_PCA_ITM_DEL	Profit Center Accounting: Delete Archived Line Items (AO EC_PCA_ITM)
EC_PCA_SUM_DEL	PCA: Delete Archived Summary Records (AO: EC_PCA_SUM)
FICDLR00	Delete Totals Records
FICICA60	Delete Docs and Totals Records Updated in Realtime
FICSGN10	Delete Generated Sets (Units/Items)
GM_BUDGET_DATA_DELETE	Delete Budget Documents in GM
HTWUTXM0	Delete tax reported data
J_3RF_TAX_DELDATA	FI-SL Delete Program
KPP0REKL	CO Planning: Delete Program Catalog
KPP2DYKL	CO-PA Planning: Delete Screen Catalog
KPP7UT03	CO Planning: Delete Template
LBOKSU04	Delete cost center object number
LBONPU03	Delete network object number
LBOORU04	Delete order object number
LBOPDU04	Delete project object number
LBOPRU04	Delete WBS element object number
LBOPSU03	Delete standard project object number
LBOPTU03	Delete std WBS element object number
LCACTMU04	Delete dependencies for characteristic
LCKKKEKU04	Delete the cost estimate cache
LCMDIU17	Delete a Component Allocation to Operation
LCNT4U10	Deletes all nodes of the tree
LCNT4U49	Deletes one node of the tree
LCUKOU51	Deletes a BOM item
LCY04U52	Delete planned orders
LCY04U57	Delete planned orders
LECOPF22	Delete entries from the database
LEDIJU09	Delete IDoc segment definition
LEDIJU15	Delete segment without ensuring consistency
LEPSFU15	Delete File
LF005U14	Delete payment orders
LF110U20	Delete payment orders
LFR02U26	Delete Change Documents for G/L Accounts
LFWTDU01	Delete w/tax information (parallel to deletion of FI line item)
LFWTDU09	Delete w/tax information (parallel to deletion of FI line item)
LFWTHU06	Deletes the KONTAB_WITH, resets the clearing information
LFWTHU23	Delete WITH_ITEM entries belonging to a parked document
LFWTSU01	Delete withholding tax master data following archiving
LGRWIU13	Delete Report Painter Report
LGRWIU14	Delete Report Painter Report
LGRWTU36	Delete All Extracts from a Report Group
LGRWTU38	Delete Report-Dependent Sets and Dataset Entries
LGRWXU08	Delete All Unused Dataset Entries in a Report
LHFPVU03	Delete Table RPSCO
LHFPVU04	Delete Table RPSCO
LHFPVU06	Delete table RPSCO
LIPARU27	Deletes all entries from internal tables with specified OBJNR
LKADLU05	Delete CO data for an object number
LKAE3U04	Delete Global Data
LKEA4U04	Delete External Data Transfer for Operating Concern
LKEA7U03	Deletes a Range of Characteristic Values for a Characteristic
LKED4U10	Delete double entries in selection conditions
LKEDAU13	Delete One Summarization Level (Data and Definition)
LKEDEF20	Delete objects
LKEDEF50	Delete Authorization Objects
LKEDEF60	Delete Customizing
LKEDEU28	Delete Customizing - Client-Specific
LKEDEU29	Delete Summarization Levels
LKEDEU30	Delete Environment for Interface Between SD and CO-PA
LKEDRCOPAU04	Delete Derivation Strategy
LKEDRU05	Characteristic Derivation: Delete Strategy
LKEDRU08	Characteristic Derivation: Delete INDX
LKEDRU12	Characteristic Derivation: Delete Strategy
LKEETU04	Deletes buffer of text read module
LKENDU06	CO-PA Realignments: Delete Realignment Runs
LKEPCU09	Delete Posting Tables from global Memory
LKEV1U04	Delete LKEV1U01
LKEV2U04	Delete LKEV1U01
LKKBLU08	Delete a complete hierarchy
LKKERF01	Delete long text
LKMA1U05	Delete Cost Center
LKMA1U09	Delete Cost Centers: Group Processing
LKMA4U07	Delete Cost Element
LKMA4U08	Delete Cost Elements: Group Processing
LKMA6U07	Delete Activity Type
LKMA6U08	Delete Activity Types: Group Processing
LKMS0U08	Delete Buffer and Release Memory Space
LKMS2U04	Delete Buffer and Release Memory Space
LKPFPU06	Delete entries in BPPE, BPJA, RPSCO with value type 62 and 6A
LKWM3U07	Delete business process
LKWM3U10	Delete Business Processes: Group Processing
LMEWQU06	Delete/Close Purchase Requisition
LMG20U02	Checks Whether a Unit of Measure for a Material May Be Deleted
LMLSRU10	Delete entry sheet
LMRMEU11	Delete an invoice
LMRMEU12	Log. Inv. Verif. - Create/Change/Delete Taxes for Incoming Invoice
LMRP1U10	Deletes a material from buffer (View MT61D)
LMRPCU04	Delete total requirements
LPBNKU07	Delete Bank Details
LPBNKU08	Delete Bank Details
LREPPU11	CO-OM Reporting: Delete User-Specific Parameters
LRMRTU26	Deletes the general internal table with posting records for file CPZP
MASSDLOG	Delete Logs for Mass Changes
MFKM8F02	Delete Chart of Accounts
MFKM8I02	Delete Chart of Accounts
MFKM8O02	Delete Chart of Accounts
MGCU3TOP	FI-SL: Delete Transaction Data
MKEA3F80	CO-PA: Delete Operating Concern
MP50JF19	Delete Infotype
RACLSDEL	Delete Asset Classes
RACORR07	Delete ANEK/ANEP/ANEA with certain current numbers
RACORR07_ALL_DOC	Deletes All Line Items for Document for Purpose of Recreating
RAIDJP_TAX_TCO	Delete Old Property Tax Report Data
RAIMDELE	Completely Delete Capital Investment Programs
RAIMZODL	Delete illogical entries in IMZO
RATAMLAY2	Copy/Change/Delete Tab Layout Definitions
RATSTDEL	Delete Data From a Company Code in Asset Accounting
RCLEANFRET	Delete Distribution
RCRARDL1	Delete Work Centers
RCRARWR1	Archive and Delete Work Centers
RDELALOG	Delete Application Log Entries
RFBKABSD	Bank Statement Archiving: Delete Program
RFBKACFD	Balance Carry Forward Archiving: Delete Program
RFBKAGLD	BCA General Ledger Data: Delete Program
RFBKDEL1	Delete Account Master Data
RFBKDEL1_EXT	Delete Account Master Data via External Account Number
RFBKDEL1_INT	Delete Account Master Data via Internal Account Number
RFBKDEL3	Delete GL Update Data
RFCASH10	Cash Journal: Deleted Documents
RFCCDLOG	Payment Cards: Delete Old Log Information
RFCHKD00	Delete Check Information on Payment Run
RFCHKD10	Delete Check Information on Voided Checks
RFCHKD20	Delete Information on Checks Created Manually
RFCMDECV	Delete A/R Summary Data
RFDELPLN	Delete FI Planning Data
RFEBKAD0	Delete Bank Statements and Check Deposit Lists from Bank Buffer
RFEWUD0P	FI Reconciliation Phase <-> Delete Table EWUFI_SOP
RFFM_DEL_RELID_RFDT	Delete entries from table RFDT for certain RELIDs
RFFMAR46	Delete Unused Budget Texts in FM
RFFMAR54	Delete Archived Budget Entry Document in FM
RFFMAR64	Delete Archived Budget Totals Records in FM
RFFMARC4	Archiving Line Items in FM: Delete Data
RFFMARD4	Archiving of Totals in FM: Delete Data
RFFMDL02	Line Item Data Records to Delete
RFFMDL16	Delete Line Items in Project Cash Management
RFFMDL51	Delete Old Line Items from Cash Budget Management
RFFMDL52	Delete Actual Data for an FM Area in Cash Budget Management
RFFMDL53	Delete Plan Data for an FM Area in Cash Budget Management
RFFMDL82	Delete Actual Data for an FM Area in PS Cash Management
RFFMDL91_ISPS	Delete budget data
RFFMDLBL	Delete c/fwd Fund balances
RFFMDLCL	Delete Cash Budget Management Clearing Information
RFFMDLCU	Delete Controlling Data from  FM (Ledger 9C)
RFFMDLFMIT	Delete records from table FMIT
RFFMDLFMIT_QUICK	Delete FMIT
RFFMKU_DEL_DATA	Delete Budget Data
RFFMKWO1	Delete customer/object/revenue type assignments to bank data
RFFMKWO2	Master Data Objects: Delete Test Data
RFFMKWO3	Delete assignment of customer/revenue type to bank data
RFFMKWO4	Delete Execution Data from Customers, Vendors and Documents
RFFMPLAN_DEL	Delete Financial Budget
RFFMPSO1	Create/Change/Dispay/Delete/Approve/Reverse Request
RGUREP03	FI-SL: Delete Line Items and Correct Totals Records
RGUUMS02	Delete Summary Table Sets
RGUUMS03	Delete the Transaction Data of a Summary Table
RHU_INV_DISPLAY	Displays of Inventory Documents (incl. Deleted Items)
RKAKALDE	Reconciliation Ledger: Delete Data
RKCDELET	Delete transaction data
RKCDLALL	Delete transaction data
RKCDLMD0	Display / Delete master data
RKEDEL01	Delete Settings for Operating Concern
RKEPLDKL	CO-PA Planning: Delete Screen Catalog
RKKRMERK	Create and Delete Characteristics
RKMASDEL	Delete Master Data
RKODEL01	Delete CO orders
RKPLNC17	Correction: Delete Object and Transaction Currency for a Currency
RKPLNC18	Delete COKA Entries for Cost Center and Cost Center/Activity Type
RKPLNC19	ABAP correction: Delete undetermined credit records with PAROB "OR"
RKPLNC25	Delete COKA entries for one cost element
RKPLNC29	Delete CSSL record for a cost center / activity type
RKPLNC31	Delete COSL record without COKL
RKPLNC36	Delete CCtr/acty type
RKPLNC39	Delete COKP records without COKA
RKPLNC41	Delete COSS with Business Transaction RKPL if no COKL Record Exists
RKPLNC42	Delete RKP6 Records With Cost Center Object
RKPLNC45	Delete COKA Entries for CCtr or CCtr Acty Types (Not Released)
RKPLNC47	Delete TARKZ_I "001", "002", "003"
RKPLNC50	Delete Cst Ctr Actvy Type Itm w/Val.Type 10 in COSS, COSL, COEJ, COEJL
RKPLNC51	Delete RKP8 Records with Complete USPOB from COSS and COEJ
RKPLNC52	Delete CCtr ATyp without WBS Element Debit in COSS, COEJ
RKPLNC53	Delete CCAT/CC Records with Value Type 10 in CO*S, CO*P, COEJ
RKPLNC55	Delete KOAM/KOAP Line Items for Restart KP96 prior to 4.5
RKPLNC56	Delete Plan Data
RKSCUS01	Delete Transaction Data
RKSCUS02	Delete Cost Centers
RKSCUS03	Delete Cost Elements
RKSCUS04	Delete Activity Types
RKSCUS06	Delete Business Processes
RKSODEL1	Delete CO Line Items in Target Cost Calculation
RKSRULE6	Settlement rule: Delete KOAP rules with non PLINT objects
RKTCSKBU	Deletes Default Account Assignments from CSKB if KATYP = Revenue
RM07XFLA	Set Delete Status in Phys. Inv. Doc. Header
RMFIFO50	Delete FIFO Valuation Data
RMLIFO50	Delete LIFO Valuation Data
RMMDKP01	Delete MRP Lists
RPCA_DEL_DOC	Delete PCA Document (Using Local Document Number)
RPCA_DEL_REFDOC	Delete PCA Document Using Reference Document Number
RPCADEL0	EC-PCA: Delete Transaction Data (Mass Data Version)
RSAO0009	Delete InfoObjects
RSAQDELETE_BLANK_FA	Deletes InfoSets without names from the database
RSBDCDEL	Delete recordings
RSBTCDEL	Delete batch jobs
RSCATDEL	CATT - Delete Log Data If Expiration Date Is Reached
RSCATDELETE	CATT - Delete test cases
RSCDOK91	Delete change documents
RSCDOK98	Delete Planned Changes
RSCDOK99	Delete Change Documents
RSPO0036	Delete Large Spool Request
RSPO0041	Delete Old Spool Requests
RV14ADMP	Delete Material Price
RWVKP01D	Delete Pricing Documents
SAPF040R	Delete Reference Documents
SAPF053R	Delete Sample Account
SAPF123S	Delete Blocked Entries from the Automatic Clearing Program
SAPF140D	Delete Correspondence Requests
SAPLKEDE	Delete Operating Concern
SAPMF261	Delete held document from file
SAPMFKM8	Copy / Delete Chart of Accounts (FI)
SAPMGCU3	FI-SL: Delete Transaction Data
SAPMPCA3	EC-PCA: Delete Transaction Data
SAPRCK44	Delete Costing Run
SAPRCKDL	Deletes KALO Entries for Which no KALA Record Exists
SDLIKPDL	Delete Sales Documents
SDVBAKDL	Delete Sales Documents
SDVBRKDL	Delete Sales Documents
SDVFKKDL	Delete shipment costs
SDVTTKDL	Delete Shipments
UGRWDU02	Delete Report
UGRWDU10	Delete Report Group(s)

Note: Use this programs only in testing environment and don't try this in production environment.