Source List Determination

A source list identifies sources of supply for the certain materials and the period of time in which the material can be ordered from the source.

If the source list contains neither a vendor nor an outline agreement item, the SAP system then tries to find a contract or a scheduling agreement for the material. The SAP system also looks for suitable info records and suggests these for the material.

Source List Overview

A source list specifies the possible supply sources for a material over a given period of time. In the SAP system, a source for material supply can be a vendor or an outline agreement. A source list shows the time period in which a material may be ordered from a given vendor, or details of long-term purchase agreements.

The source list can be used to define the preferred or allowed sources of a material. Source list records are used in source determination, which involves automatically assigning sources to purchase requisitions.

Source List Maintenance

Source list records are maintained either manually, or via the outline agreement, purchasing information record or automatic generation. Once the source list is maintained, the system will suggest the source list in requisition via the source determination facility. The purchase order (PO) and purchase requisition (PR) will then be checked to determine whether the source is allowed.

These costs will be maintained in the pricing conditions of the outline agreement or if no outline agreement exists, it will be in the purchasing info record.

Each condition (the transportation costs, for example) can have a different vendor from the main vendor supplying the goods. At the time of purchase order creation with reference to the contract or info record, the pricing conditions will be copied into purchase order’s pricing conditions and may be maintained there.

At the time of invoice posting, the SAP system will use the conditions in the purchase order to calculate the due amount and compare it with the received invoice from the service vendors.

If a mismatch exists between the service supplier invoice and the condition in the purchase order, and this variance is deemed significant, the respective condition in the info record and PO will be updated.

If the variance is small and not significant, the invoice will be posted, where the difference will go to price difference account.

What is cause of this problem? I am searching the solution in SAP forum then I have got the solution now. To solve this issue, I checked the following steps:

1. Check the validity dates for the routing and production version. Rate Routing Valid from 15.07.2012, whereas you may be defining valid from of Production Version from 15.06.2012, in this case you may get 2 messages during the consistency check of production version, system will display message tasklist exists and next “No valid Task List” for period 15.06.2012. (For my case, valid date of production version and rate routing is matched.. What next?)

2. I re-checked my rate routing again and found the cause of this inconsistencies. It is because I have updated unit of measure of lot size as “PC” but unit of measure of lot size in production version is “CS”. So that means lot size is not matched.

I have updated UoM in rate routing to “CS” and consistency check this production version again. The green light is coming.

inconsistencies for production version+sap – This solution should be helpful any one who find this issue. I also welcome any comments and sharing.

Read more: Production Version

Yes.. to do that variant has be to create for this transaction. Go to FBL1N transactions and click on save icon (to save your variant). In variant attributes, select required field indicator at company code line, design your variant name and save as default variant.

This problem might be caused by component scrap value in material master of material A. If assembly material master is updated the component scrap in percent field on MRP4 view. Thus this scrap percentage will be used to be calculated and it makes the cost estimate increased.

Component scrap (%) parameter is also used in material requirement planning (MRP) to determine the quantities of component required. When exploding the bill of material (BOM), the SAP system will increase the required quantities of the components by calculated scrap quantity.

For example, If material A is required quantity 500 pieces and component scrap in percent is maintained as 10%. Then scrap quantity will be 50 pieces. Therefore, 556 ( 555.555.. ) pieces are required.

Read more information: Component Scrap BOM in SAP

For this case, I have checked my output type by using MN06 transaction. Key Combination (Purchasing Doc. Type and Company Code) is maintained properly and some purchase order that are using this output group can work correctly ( output is created automatically in message ).

I have investigated deeply and found that only purchase orders which created with one purchasing group (for example this case is T10) has this problem.

If you find the situation like this. More setting need to be checked is whether an output device has been assigned to the purchasing groups used in your purchase order or not.

• SPRO • Materials Management • Purchasing • Messages • Assign Output Devices to Purchasing Groups

For my case, this missing configuraiton is cause of output not triggering automatically for any purchase orders created with this purchasing group. Then I restored the configuration. I refreshed purchase order by using ME22N transaction and click the message button then output was assigned to my PO automatically again. So the problem is solved.

Hope this solution is useful for anyone who is encountering same issue. Any mistake, please share..

What is dispatch time?

1 – Send with periodically scheduled job
2 – Send with job, with additional time specification
3 – Send with application own transaction
4 – Send immediately (when saving the application)

If selected “3″, output will be printed later by using ME9F transaction (not print immediately)

Other configuration need to be checked: Partner Function Determination

No message generated for output of purchasing document
Message no. 06261

Diagnosis
The system was not able to find a message record via the message determination schema. Therefore it was not possible for such a record to be generated for this purchasing document. In consequence, the purchasing document cannot be outputted (printed or transmitted).

Then you cannot deselect this indicator by using MM02 transaction anymore. In technically, Batch Management indicator can be removed but there are so many prerequisite steps need to be done.

Sometime the way to create new materials may be easier than going thru all complex steps need to be done to remove batch managment.

The following are the steps to remove Batch Management indicator in material master:

How to deactivate batch management in SAP

1. Zero stock in present and previous period – Movement type 562 by using MIGO transaction or Peform Physical Inventory postings using MI10 transaction; Movement type 702.
2. No purchase orders – You need to delete all purchase orders lines (for open and closed POs) – List all POs by using ME2M transaction then PO line items have to be deleted by using ME22N transaction. If you have POs with GRs posted but invoices not posted, then post their invoices first, also any delivery costs should be settled. For POs with some GR done, order quantity should be reduced to match GR qty. After this only, you will be able to delete PO lines. Else, you will be hindered.
3. No open physical inventory documents – List all physical inventory documents by using MI22 transaction, If at all any documents are open, you will have to complete them by posting the differences or deleting them. There are chances of having open documents only if counting is being carried out presently.
4. All batches to be deleted at plant level and batch stock level by MSC2N transaction.
5. Batches to be archived.
6. Remove Batch Management indicator in material master.
7. Stock to be reloaded – Movement type 561 by using MIGO transaction or Peform Physical Inventory postings using MI10 transaction; Movement type 701.

More information:

Note 533383 – Deselecting the batch management requirement indicator
and Note 30656 – Change base unit of measure/batch mngt requirement

Below points should be concerns if you need to deactivate batch management indicator.

• Check the Status of Material in MMBE transaction for total batches of the material.
• There should not be any open Purchase Order Use SE16 & Table EKPO to find the Open POs
• There should not be any Sales Order. Use SE16 & Table VBAP to find the Open Sales Orders
• There should not be any Purchase Requisition. Use SE16 & Table EBAN to find the Open PRs
• There should be no Stock in Transit – MB5T transaction
• There should be no Plant availability Stock – MB53 transaction
• There should be no Reservation – MB25 transaction
• Previous Period Stock should be zero. Use MM43 with Plant Stock & Storage Loc. View. If Stock Exists follow the Procedure:

1. If previous period stocks exist, we can make a withdrawal posting as follows. Post the same amount to current period stock (for example, using movement type 561) so that previous period stock and current period stock are identical.
2. Make a withdrawal posting in the previous period for the stock together with posting date (for example, using movement type 562).

• Stock requirement should be zero – MD04 transaction
• There should be no open Delivery Use SE16 & Table LIPS
• There should be no open Warehouse Transfer Request Use SE16 & Table LTBP or LTAP
• The Batch Corresponding to the plant for the article has to be set for deletion indicator, MSC2N transaction. Once the batch deletion indicator is set, Archive all batches for the material
• If any of the above Stock Exists it has to be closed; If Any of the stock exists we cannot uncheck the batch management indicator.
• After closing all the open items; the related business documents such as Purchase Orders, Delivery, etc.. have to be archived.

So how to delete those demand (SNP:DepDmd elements) from system since this subcontractor will not be used anymore?

SNP:DepDmd elements in subcontractor location happened due to the planned order for finished goods at this subcontractor location (vendor).

To find what the finished goods of this product are, we can use CS15 transaction in SAP R/3.. As Material Where-Used list below, there are 3 finished goods using this material.

As checking, there are planned orders (SNP:PL-ORD elements) in finished goods product: 1534192 at vendor location. To delete that planned orders you need to run SNP heuristic at vendor location then SNP:DepDmd elements will be get deleted if there is no requirement.

If the orders are not deleted after run SNP heuristic. Why?

The planned orders are selected the PP-Firmed indicator hence when you are trying to delete those it does not. So that is the reason it is not able to delete that planned orders. Thus to remove PP-Firmed indicator, go inside that planned order then remove the tick on output firmed and pressed enter and automatically the tick on PP-firmed gets removed. Run SNP heuristic again, the orders will be deleted by running heuristic on the product location combination using /SAPAPO/SNP01 transaction.

Other way to delete SNP:PL-ORD elements

SNP:PL-ORD elements can be deleted by using /SAPAPO/RLCDEL transaction. You can specify selection parameters as below:

• Select Object: By Categories → Choose ES (What is ES mean?)
• Manual Selection: Specify Planning Version, Product Number, Location

If you find any questions, please feel free to share me… And also welcome any comments.

S_ALR_87012357 transaction can be used. Note 1687572 need to be implemented to update report RFUMSV00 to display the VAT Registration number of the company with 13 digits as maintained in the Company’s Master Data.

RFUMSV00 program creates the advance return for tax on sales/purchases (if required, a batch input session can be created) for automatic transfer posting of tax payable. It is used to report the month taxable sales and purchases. We use it as a basis for our VAT declaration to the Tax authorities in your country. With the RFUMSV00 report you can offset your input and output sales tax to a net payable or receivable account in your balance sheet.

More information: http://help.sap.com/saphelp_ish471/helpdata/EN/8e/051f2bc925d311b60f0060b03c2bff/content.htm

1. The length of VAT Registration Number of Company Code is changed from 10 digits to 13 digits.
2. The length of Tax Identification Number of vendor is changed from 10 digits to 13 digits.
3. The format of PND3 and PND53 forms is changed.
4. The personal ID field is removed from form IDWTREPT_TH_1

SAP provides solution that the VAT Registration (STCEG) field can be used to update the new VAT Registration number of the company in Mater Data of a company using OBY6 transaction (• Financial Accounting Global Settings • Company Code • Enter Global Parameters).

For customer and vendor master, tax Number 1 cannot be used because it is for personal ID and links to withholding tax form for personal withholding tax. VAT reg.no. also cannot be used due to we need this field to maintain tax number for company who has VAT registered (for company without VAT registration will leave it blank).

SAP release the solution as following:

Note 1687572 – Implement this note, report RFUMSV00 will display the VAT Registration number of the company with 13 digits as maintained in the Company’s Master Data.

Note 1686208 – Implement this note for Report RFIDYYWT

Note 1681250 – Implement this note to update tax no. in customer / vendor master to 13 digits. Activate Tax Number 3 field. It can be used to update the new tax number. Report would check and display tax data from tax number 2 (STCD2) in case tax number 3 (STCD3) is not updated in the corresponding vendor / customer master. This case is valid for those customers who have not received new TAX ID number from the government and existing Tax ID is valid.

Hope this information is useful .. Please share me if any information is missing.

How to maintain Thailand’s Tax ID of a company code in SAP system

SAP VAT registration number configuration – Maintaining of a VAT reg.no.is only possible for company codes in EC countries. The following are the steps to update company code’s tax ID in VAT Registration No. field in configuration (Enter Global Parameters (OBY6) – SAP company code VAT registration number)

1. In Customizing for SAP NetWeaver, choose • General Settings • Set Countries • Define Countries in mySAP.com Systems.
2. Select country “TH” for Thailand.
3. Select EU Country indicator.

4. Go back to the Implementation Guide (IMG) screen, then, in Customizing for Financial Accounting (FI), choose Financial Accounting Global Settings • Company Code • Enter Global Parameters.
5. Select your company code.
6. In the VAT Registration No. field, enter TH followed by your tax ID, for example, TH123456789123.
7. Go back in Customizing for SAP NetWeaver again, choose • General Settings • Set Countries • Define Countries in mySAP.com Systems. and deselect EU country indicator.
8. Save your settings.

Hence there is some discrepancy between 2 systems. However, if compare the demand numbers in weeks so I will find the match exactly.

So I need to understand more about planning calendar setting in SAP APO (MD27 transaction is used to maintain planning calendar in R/3).

The calendar data is maintained as part of the location master data. The Maintain Planning Calendar (Time Stream) is prerequisite step before maintaining calendar data. The time stream can be set up in weekly or monthly periods.

SPRO • Advanced Planning and Optimization • Master Data • Calendar • Maintain Planning Calendar (Time Stream)

The following fields are provided on the Calendar tab page of Location Master Data (/N/SAPAPO/LOC3):

Production Calendar
The production calendar is used to schedule production activities. A production calendar valid for the entire production is assigned to a location.

Warehouse Calendar
The warehouse calendar is created for the scheduling of warehousing/storage activities. A warehouse calendar regulating the accessibility of a storage facility for stock putaway and removal purposes is assigned to a location.

Shipping Calendar
The shipping calendar is used to schedule shipping activities. A shipping calendar valid for the entire shipping function is assigned to a location.

Maintain Planning Calendar (Time Stream) Steps

1. Enter a unique name for the time stream (calendar), and choose Create. The Change Planning Calendar screen appears.

2. Enter a short description for the time stream.

3. Enter how many years into the past the calendar is to extend. This setting is optional.

4. Enter how many years into the future the calendar is to extend. If you do not make an entry in this field, the system considers the current year only.

5. Use the input help to select the time zone for the location to which this calendar is assigned.

6. Select one of the following calendar options, depending on the location or transportation lane associated with this calendar:

• Factory calendar (with gaps)
• Period calendar (without gaps)

7. Use the input help to select a pre-defined calendar.

8. Choose Periods to define the periods for this calendar.

9. Select the required time interval (week or month). The interval is displayed in weeks or months accordingly.

10. The information you enter in this step depends on whether you selected week or month for the time interval:

• If you selected week, assign numbers 1 – 7 (1 for Monday, 2 for Tuesday, and so on) to the periods and enter the required times.
• If you selected month, assign numbers 1 – 5 in the first column for the weeks in a month, and number 1 – 7 in the second column for the days of the week. Enter the required times.

11. Choose Periods to generate the periods. You always have to generate the periods again when you have changed the calculation rules.

12. Choose Save.

This indicator specifies whether a purchase order item is considered as completed and closed. This means that no more goods receipts are EXPECTED for this item. If this indicator is set, the open purchase order quantity becomes zero, even if the full quantity has not been delivered.

The fact that the system proposes the quantity that was ordered but has not yet been delivered is the standard system response. No program correction is available since this is standard system behavior. Setting the ‘delivery completed’ indicator has the following effects:

1. The purchase order item is considered as completed and can be deleted even if not the entire quantity was delivered.
2. A further delivery is not expected. This affects material requirements planning (materials planning) and purchase order commitment. However, another delivery up to the purchase order quantity (including overdelivery tolerance) is still possible.

3. During the next goods receipt, the system does not select the item as a proposal in the selection list in Transaction MB01. In Transaction MIGO, the system does not propose the ‘OK’ indicator even if it would normally be proposed due to the user settings.

According to solution in Note 856279 (MIGO: Proposed qty despite ‘delivery completed’ indicator)

To stop the system from proposing a quantity in Transactions MB01 or MIGO and to prevent a GR posting, you can proceed as follows:

1. Reduce the purchase order quantity to the previous GR quantity.

2. Block the purchase order item. (ME22N: Block pushbutton; ME22 Menu → Edit → Block)

3. Fill the date field for the ‘Latest Possible Goods Receipt’ (LEWED) in the purchase order item. If you do this and you enter a GR document after this date, the system issues message M7163, which you must set as an error message in Customizing.

4. Under “Purchasing – Environment Data – Define Attributes of System Messages” add Application Area 06 and Message Number 744 from warning to error.

Set “Delivery Completed” Indicator in Customizing

The “Delivery Completed” indicator can be specified as the system automatically suggests the inward delivery completed indicator for goods receipts if the delivered quantity lies within the under/overdelivery tolerance.

SPRO → Materials Management → Inventory Management and Physical Inventory → Goods Receipt → Set “Delivery Completed” Indicator

The “inward delivery completed” indicator has the following effects:

• The item is regarded as closed, even if the total quantity was not delivered.
• A further delivery is not expected, may, however, arrive.
• In the next goods receipt, the item appears on the selection list but has no selection indicator.
• The item can be reorganized even if the total quantity has not been delivered.

More information about delivery completed indicator can be find in SAP Note 1093582 – FAQ: Delivery complete indicator ELIKZ.

Time profile can be configured in Customizing of Detailed Scheduling or go to /SAPAPO/CDPSC4 transaction directly.

Period Type for Definition of Display and Planning Period can be defined in the following ways:

Relative

Here you define the start date and finish date in relation to the current date, for example, the start date lies 10 weeks in the past (-10) and 40 weeks in the future (40). You therefore enter a number of periods for the start and for the finish date.

Absolute

Here you enter the start date and the finish date as an absolute value in the set period type, for example, for the start date 011999 (calendar week 1 in year 1999) and for the finish date 501999 (calendar week 50 in year 1999).

For performance reasons, you should keep the display period as short as possible.

Information in recipient field defines Goods Recipient/Ship-To Party. It specifies the recipient for whom the material or the service is destined.

To list all pending POs which created by requester, go to table EKPO (item information) thru SE16 transaction, for example:

The parameters above list all pending purchase orders of company code:1000 which created by User: SAPID001 during 01 Jan 2009 to 21 March 2012. Exclude PO items which have been flagged for deletion (Deletion Ind.: L), and exclude item which flagged Deliv. Compl.

To find open GR and IR quantity, you can export PO numbers from table EKPO then go to ME2N transaction with those POs. Then you will get more information about your pending POs such as Still to be delivered Qty and Still to be invoiced Qty.

In addition, EKET table which contains purchase order schedule line wise schedule qty (EKET-MENGE) and delivered qty (EKET-WEMNG). MENGE – WEMNG = open qty.

Scheduled Quantity is quantity to be delivered by the vendor in respect of this schedule line.

Quantity of Goods Received specifies the quantity already delivered to date for this item or schedule line.

In case you need to find the pending PRs in SAP system instead.. see How to Check Open Purchase Requisition

The CDHDR and CDPOS table collect changes made to material masters (table MARA). You can see what changes are made by using these two tables CDHDR (header) and CDPOS (items).

You can select by specific the fields such as OBJECTCLAS, OBJECTID and CHANGE_IND to get CHANGENR. The date, time, user, and field changed are saved in CDPOS table, along with the the old value and the new value of the changed field.

For example, to see changes made to field MATERIAL on table MARA, read table CDHDR where

CDHDR-OBJECTCLAS = ‘MATERIAL’
CDHDR-OBJECTID = ‘your material number’
CDHDR-UDATE = SY-DATUM or your choice of date
CDHDR-TCODE = ‘MM02′
CDHDR-CHNGIND = ‘U’

Using values from CDHDR table, you can get the information from CDPOS table where, for example,

CDPOS-OBJECTCLAS = ‘MATERIAL’
CDPOS-TABNAME = ‘MARA’
CDPOS-OBJECTID = CDHDR-OBJECTID
CDPOS-CHANGENR = CDHDR-CHANGENR
CDPOS-FNAME = ‘your field name’ wanted
CDPOS-VALUE NEW
CDPOS-VALUE OLD

Or Try to run Program RSSCD100 with Object Class ‘MATERIAL’. It will give us more information in regard to old and new value.

Useful Material Master Tables:

MARA – Material Master (MATNR)
MARC – Material Master with Plant Data (MATNR, WERKS)
MARD – Material Master with Storage Location Data (MATNR, LGORT, WERKS)
MAKT – Material Master Material Descriptions (MATNR, MATKL)
MBEW – Material Valuation Data (MATNR, BWTAR)
MVKE – Material Master : Sales related Data
MDKP, MDTB – MRP related Data( Header, Item)
MCHA, MCHB – Material Batches (Header, Item) (MATNR, WERKS, LGORT, CHARG)

For configuration change log, you can find in this post..How to Check Change Log of Configuration

Detailed Scheduling Heuristics in APO can only reschedule or deallocate orders and operations that start within the planning period.

The system must schedule deallocated operations or orders to be newly created so that the start date is within the planning period.

• Reschedule activity is used to determine a new date or new resources for a scheduled operation, on which the operation should be processed.

With rescheduling, the operation still occupies the resources; after rescheduling it occupies either the previous resources or the new resources. Rescheduling an order means rescheduling the operations of an order.

• Deallocate activity in which an operation is removed from the resource schedule. With deallocation, an operation is given the status deallocated; the operation no longer occupies any resources.

• Schedule activity for newly created or deallocated operations, which is used to:

- determine the resources to be used to process an operation

- determine the date when the operation should be processed on the resource

With scheduling, the operation occupies the resource. Scheduling an order means scheduling all the operations of an order. 0800572600

For example scenario, this is related to finish goods material which will change the packaging design and still use current material number.

Currently, If we maintain the end valid date for current version and then start new version after current version.

Example, Production version 0001, valid to date is 03.31.2012 and start new version 0002 on 04.01.2012 with new packaging design.

When there is any delayed in project timeline, planner will move graph in PPDS, then sometimes some plan order may move back and over the end valid date. Then the issue is happened as “Planned order XXXX version 0001 is not valid on finish date 04.02.2012″.

The solution may be to set overlap of current production version and new version per scenario below.
Project timeline is to start new packaging design on Apr 1. We will set end valid date of version 0001 (current version) on Apr 15 (instead of Mar 31) and set version 0002 (new version) start on Apr 1 per project timeline.

Only implication of this setting is that during that period of overlap the system will create the planned orders on the first production version and the planners will have to keep a control on it (adopt the correct source of supply ) for the planned orders in that period.

SAP system allows the purchasing group maintained in material master (purchasing view for that plant) is diffrent than the purchasing group which is maintained in info record.

Regarding OSS note 178306, the puchasing group you enter manually in a requisition is always overwritten with the purchasing group from material master.

Even after MRP run or manual purchase requistion creation process, purchasing group maintained in material master record will come as default , it overrides the entry of purchasing group maintained in info record.

Purchasing group represents for the person and/or a group of person(s) who is/are responsible for purchasing activitites of a certain group of material. Hence, it is more logical that the purchasing group from the material master shall be used so that once the purchase requisition is generated, responsible team (with related purchasing group) will then group their own purchase requisition (using purchasing group as part of the selection parameters) for further processing in ME57 transaction.

It would then be subject to this/these responsible team(s) to determine how the purchase requisition shall be processed and since they are the team(s) who process(es) these purchase requisitions, the purchasing group from the purchase requisition shall be copied over into purchase order then.

Anyway, the purchasing group in the purchasing master data record (such as in info record or material master) is not critical to the entire process of PR processing (into RFQ and/or PO). Ideally the purchasing group in material and info record should be the same. – Ha Tran

This error means you have to maintain Business Process Planning Quantities / Prices in Activity Based Costing first. (Path below)

Accounting → Controlling → Activity-Based Costing → Planning → Process Quantities/Prices → Change

The plan activity/output prices in Activity Based Costing (ABC) will be maintained by using CP26 transaction (Change Business Process Planning Quantities / Prices) whereas using KP26 transaction (Change Activity Type / Price Planning) instead in Cost Center Accounting (CCA).

What is Business process in Activity-Based Costing

Process in a company that uses resources and can involve the activities of different departments. A business process can consume the output of multiple cost centers in a controlling area.

Read more information:

• Planning Process Output (Quantities and Prices)
• Activity Based Costing Document

How to Exclude MRP Type ND from CIF Model

You can exclude materials from a cif model with the multiple selection function directly in the integration model what you use for transfer.

When you activate materials give ‘ND‘ in the ‘Exclude values‘ of MRP type field in selection at CFM1 transaction. So all materials with MRP type ‘ND’ will not be included in the model.

Note:

If there are more than one integration model activated for that material then if you remove from one Integration Model, it will not get deactivated. In that case go to CFM5 transaction select that material and plant then execute. You will find which all Integration Model are there for that. Then deactivate in those all Integration Model.

I will suggest that, instead of excluding MRP type ‘ND’ , we can send the PDS with selection as, MRP type ‘X0′ . Though I found some inactive BOM for material with MRP type ‘X0′ . It will definitely reduce the failure occurrence of job.

How to exclude specific materials from Integration Model Expert: Dogboy49

All materials corresponding to a particular MRP type are in an integration model and the model is active. To exlude a specific material from this integration model even if it is having the same MRP type.

Use CFM1 transaction. For each model affected, call up the affected variant. Go to the material field. Select Multiple selections (‘right arrow’). Select the ‘Exclude values’ tab (third tab). Enter the material or materials to be excluded. Copy (F10). The Save the variant. Execute the program to generate the (newly modified) model. Save the model.

Go to CFM2. Activate the newly generated model. Repeat for other affected models.

If the material previously been contained in active models, then the newly excluded master and transactional data will still exist in SCM. If you find it to be necessary to delete these data, then you need to go over to SCM and perform the necessary steps. Start with /SAPAPO/CCR to delete transactional data, then go to WUF to delete master data.