Created several DART extracts in Production System - OSS Notes

We have created several DART extracts in Production System and we are getting some error messages
Below Views are missing
view 0sap_BKPF is not existing
view 0sap_BSEG is not existing
view 0sap_BSET is not existing
view 0sap_Ekko is not existing
view 0sap_MKPF is not existing
view 0sap_MSEG is not existing
view 0sap_T003 is not exisiting
view 0sap_VBRK is not existing
Below Fields are missing
Field A001-A002AFABE is unknown in 2 below views
0sap_AMMST and 0sap_AMTRN
Edited by: TheGaurav on Jul 16, 2010 11:10 AM

Hi,
the note 611648 should help.
Br
Attila

Similar Messages

How to make JOB CONTROL setting for delta extraction in Production system .

Hello All,
We are in the process to transport our development to PD server in BI . We have transported the data sources to ECC production and now we are filling the setup table for " SD BILLING BW " . After filling Setup table data in full mode through infoPackage we have to load data in delta mode .
How we can set our Update mode(LBWE setting) in PD server ?
Is LBWE T.Code authorisation required in ECC PD server to make the setting of Update mode or We have to set all Job Control Paramater in Dev System at the time of transport the datasource request to ECC production . Is our time which is set in job control of ECC development will be reflected in ECC production ?
can any body tell me about how to make setting for delta extraction in Production system .
Thanks ...

Hi,
How do you load the data in the development system?
- you set up the update mode in the infopackage. There you must customize "Initialization"
- you have to filled the setup table in the production system without laoding the data in the BW? then this step was for nothing. Filling the setup table and do the INIT in the BW, this must be together - during no changing will be done in your R/3 SD.
Sven

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Transaction Launcher: Logical System in Production System does not change

Hi,
I created a transaction launcher in the CRM development system (CRD) to launch the transaction IL02 in the ECC 6.0 system (ECD). Then I transported the changes from CRD to the CRM production system CRP. I also transported the changes from ECD to ECC production system ECP.
However, when I see the transaction launcher in CRP system, it is still configured for the URL of ECD. I want the transaction launcher to connect to ECP. One option I have is to change the class name in the CRP system. However, I am not allowed to create a new ABAP class in the production system. Is there any other way to change the target system automatically in production system?
Thanks,
Rohan.

Thanks Piyush. Could you be a bit more specific? I followed these steps:
1. In transaction CRMS_IC_CROSS_SYS, created a logical system URL for production system
2. In customizing setting Copy/Delete Launch Transactions, deleted the transaction launcher id.
3. In customizing setting Configure Transaction Launcher, created the same transaction launcher id newly.
I still am not able to change the logical system. However, I can do it if I change the class name.
While deleting the transaction launcher id, should I be deleting all dependencies?
Regards,
Rohan.

PO created in the SRM 7.0 system is not replicated to the Backend-ECCEHP4

PO is created in the SRM 7.0 system and the PO number also generated for the backend system but could not find the PO number in the backend system

Hi
In RZ20 i am getting the message :Error in local purchase order; no update of references in EXEC system.

DART extract file

We have DART extract files from different SAP system, and wanting to import into our current SAP system for viewing purpose. We transfered the file to directory path,and be able to view via AL11. We've tried to use tcode FTWF to import but kept receiving error, that it could not retrieve the file. Does anyone have any idea or know how to import this file to SAP? Thanks. TC

If the dup records are actually in the DART View versus the DART Extract, you could try OSS Note 1139619 DART: Eliminate duplicate records from DART view.
Additional Note - 1332571 FTWH/FTWY - Performance for "Eliminate duplicate records
Colleen
Edited by: Colleen Geraghty on May 28, 2009 6:07 PM

How to remove the duplicate record in DART Extract

Hi Guys,
We are getting duplicate record when we do validate the DART extract file through DATA VIEWS for FI General Ledger Account Balances. If any one have experance on this, pls help us.
Following are the steps we done to Validate the DART EXTRACT File for FI General Ledger Account Balances.
1. We have run the DART extract program to extract the data from table to directory file by period vice in T.code FTW1A.
2. When we do validate the data from DART extract file through DATA VIWE for FI General Ledger Account Balances in T.code FTWH, getting duplicate record.
We unable to find out from where the duplicate records are coming out. will be great if any one can help us immediately.
Thanks & Records,
Boobalan,v

If the dup records are actually in the DART View versus the DART Extract, you could try OSS Note 1139619 DART: Eliminate duplicate records from DART view.
Additional Note - 1332571 FTWH/FTWY - Performance for "Eliminate duplicate records
Colleen
Edited by: Colleen Geraghty on May 28, 2009 6:07 PM

Will Queries will be created in the Production system?

Hi all,
Is it possible to create queries directly in the Production System. And if there is an issue in the query in production systems can it be fixed in the production system itself nor it should be moved to development and then to qa and then to production???
can anyone guide me on this???
thanxs
haritha

Hi,
I am creating all my queries directly in the production system; it all depends on your strategy.
Of course, when you'll have an issue, you'll have to fix it directly in PROD since your query doesn't exists neither in DEV nor in QA.
Based on our authorization concepts where users are allowed to see only some queries we create new queries in PROD with a certain name so that users cannot see that query. We test it with live data and when it's ready we save it as under another name; the query is now released to authorized users in order to test it. When the query is assessed "valid" for the requester, when save it as again this time "LIVE" which is the final version of it. If they're changes, we go trhough the same cycle.
We also use our DEV (we have chosen not to have a QA) to test special scenarios and variable exits....
hope this helps...
Olivier.

Error message while transporting SapScript to productive system

Hi,
I have tried to transport an order sapscript form (modified Medruck) into the productive system. But I got errors in transaction stms.
The error message is displayed like this:
R3TRFORMZMEDRUCKN was repaired in this system
Message no. TW 104
Diagnosis
Object R3TRFORMZMEDRUCKN is in repair status. Therefore, it cannot be imported.
System Response
The object is not imported.
Procedure
If you still want to import the object, release the relevant repair andrepeat the import.
Does anybody know something about that problem?
Cheers

Hi,
maybe somebody has already create your form in the productive system. Now you would like to create something already created.
Maybe, you have to check in the TADIR table (key R3TR / FORM / name of the form) if the form already exist. What is the system source for the form. (in the PROD)
And finaly, you can go to the SE03, select the first line and execute (to find object R3TR FORM ..) in all the request order. That will show you who has play with this form, and if a request was lost between DEV & PROD. (in the DEV)
Rgd
Frédric
Message was edited by: Frédéric Girod

Support message and change requests only for production system

Hi guys,
I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
Kind regards
Rayko

Hi Rayko,
We do not have this option.
Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
Best Regards,
Fernando

ADHOC Query in Production System

Can I create a ADHOC query in Production system?Coz I can able to do that.
Thanks
Sriram

This is the practice:
1. The project team will build all the reports defined in the project plan, test and transport to production. These queries usually will be set not to be changed.
2. SUper users will be granted authorization to create their own queries, modify their own queries and delete their own queries. For this the auth object S_RS_COMP1 is used.
3. All the other users will be granted to access reports.
Ravi Thothadri

One BW - One R/3 Development - Multiple R/3 Productive Systems

Dear experts,
we are at the moment having a classical 3-tier system environment.
1) R/3 Development --> BW Development
2) R/3 Consolidation --> BW Consolidation
3) R/3 Production --> BW Production
Due to increased system load on R/3 Production it is planned to create an additional R/3 Production System which also needs to be connected to the existing BW Production system...BUT there will be no additional R/3 Development or Consolidation systems. The new Production system will be feeded parallel with transports fro mthe existing development system.
Question:
On BW side we will need to create Source system-dependent objects (Transfer Structures, InfoPackages, etc), etc. which are connected to the new R/3 system. But we cannot do that as we do not have a corresponding R/3 Development system connected to our BW development system.
Anyone has an idea how to approach this issue?
Thanks a lot!
Regards.
Joachim

Hi Joachim,
I have a rough idea. Can you go to RSA1 of your BW production machine, in menu tools->conversion of source system names. Add a new line, and assign r/3 consolidation machine as "Original Source System" the second R/3 prod machine as target source system. Save and try transporting again.
I haven't such experience before and it's only my guess (your case is really special). Please validate it first
If not work, a stupid way is changing this table after the first importing for r/3 prod machine1, then import again for machine2...
Regards,
Frank

System should not allow to do the changes in PO once the ID created.

Hi All,
Once the Inbound Delivery is Created based on the Purchse Order, System should not allow to do the changes in the Purchase Order like Deletion of Item, etc..
Any Configuration Changes is avaliable. ?
Regards,
Sudhakar

Dear,
Please check the staus in order
Current order status xxxx does not allow goods receipt (Message no. C6009)? is this the message?
This will not allow you to do GR for production order when you activate status profile "SAT1" in the production order. After that when you confirm order it will automatically assign next user status i.e. "SAT2" (if not assign it manually in CO02) it will allow you to do GR for that production order.
Regards,
R.Brahmankar

Solman 7.1 LVSM Product system has no technical system assigned

Hi All,
As reference of blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1SAPNetworkWeblogs%2528SAPNetworkWeblogs%2529
I have created product instance from LSVM and now I have problem to add "product system" for Enterprise portal (using NW 7.3) to the landscape, as its throw me an error "Product system has no technical system assigned".
From the display help its mentioned:
*Diagnosis*
Product system is not assigned a technical system in the system landscape of the Solution Manager.
*System Response*
Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis.
*Procedure*
Assign one or more technical systems to your product system . SAP recommends that you use the corresponding wizard of the Landscape Verification Tool. To start the wizard, choose the button Change Technical System Assignments next to the message. The user interface of the wizard contains detailed information about its usage.
I'm not sure with sentence of Assign one or more technical systems to your product system and which wizard are this referring to ?
I have also checked from the wiki:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-EnterprisePortal
And its only supported for NW 7.0 not 7.3.
Is there anyone had this issues ?
It's feels like I'm the only one stuck in this.
Thanks in advanced.
Raff

Hi Sunny,
Many thanks for your reply.
I have followed the guide you mentioned, now I can see 2 EPD Error from LVSM.
1. Product system EPD has no technical system assigned (new)
2. Technical system EPD is not assigned to a product system
For number 1. if I clicked on Change Technical System Assignments I can see EPD there, but when I want to add the EPD by clicking > I've got this error message " Newly linked technical system EPD has already been locked by user" I've tried to remove the lock from sm12 but nothing happen.
For number 2. if I clicked on Change Product System Assignments, there is an error messages "Technical system EPD was updated in parallel session"
I believe the number 1. coming because I create it from SMSY, but the number 2. is still there in the first place.
Cheers,
Raff

COM_HIERARCHY_DELETE_ALL in Productive system

Hi CRM experts,
We need to run the report COM_HIERARCHY_DELETE_ALL in the Production CRM System, but when we try to execute this report, the system issues a message to archive the data first.
However we have executed the same report in the Quality Assurance and Development system sucessfully.
Does anybody know how to configure the Productive system to not issue this check / message?
Thanks in advance
Monalisa

Hi Monalisa,
As far as my knowledge goes, you can only be able to delete the product hierarchy in the same system in which you have created. Looks like you had transported the product hierarchy either from dev or test system.
Did you try to delete a single node using 'COM_HIERARCHY_DELETE_SINGLE' ? What was the outcome?
Reward if helps
Regards,
Paul Kondaveeti

Created several DART extracts in Production System - OSS Notes

Similar Messages

Maybe you are looking for