Copy Organisational Structure to Destination System

Hello Expert,
could anyone please let me know how I can copy the assigend OM - Structure to the personal no?
My settings in the step: "Transfer selection criteria"
Objecttype: P
Objectid: 123456
Evalutation Path:P-S-C-O
Additiona evaluation path:
P-S-O-O
Rootoptions:
Without new root.
Could anyone please give me a helping hand?
The Data Transfer works fine, but I could not find any org unit in my destination system.
The personal no is assigned to the org - unit ID 6000000 in the sender system.
If I run transaktion ppose i am not able to find the org unit.
The OM in my destination system is completely empty.
Is it necessary to create a new root object initialy????
Thanks a lot
Marco

Hello Marco,
In activity 'Transfer Selection Criteria' for PD selection, what are delete options and target options you have selected?
In Target Options, if you select Transfer 1:1 without change( must be in range), then all the object would be transferred correctly.
OR
If you don't follow the above selection, then you should take care that all the objects are transferred by involving the required infotypes or objects for transfer.
Also you can select 'Delete selected tables for given objects' in the Delete options to take care of it.
Regards,
Prasanth

Similar Messages

Define sd organisational structure?

define sd organisational structure?

SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
Pricing Procedure
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful.

Organisational structure --- Mapping

Hello dear Experts ...... This is venkat charan a new commer to SAP SD .
My question is..... how to MAP organisation structure in REAL TIME? What r the steps involved in this ? please help me ?

Hi Venkat Chanran,
Please find the details below.
Client:
Client is an environment where we are working. A client is an organisation term it is an independent unit in the system, each unit consist of own environment and there fore its has own master data or transaction data assigned ,user master records and chart of accounts.
Master data:
The data, which is the basis for all the SD processing.
Type of Master Data:
1.Organizational data: this is the structure of the company where by each business is represented by a hierarchical element.
2. Customer master data: the data where all data regarding customer and material are stored.
3. Documents: the business transaction is stored in the documents.
4. Global Settings: it is one in which we define country keys and currencies.
Company code:
Legal entity and an independent accounting unit at company code level, where we create balance sheet and profit and loss accounts.
Sales organization:
An organizational unit that sells and distributes products, negotiates terms of sale, and is responsible for these transactions.
Distribution channel:
Channel through which materials or services reach customers. Typical distribution channels include wholesale, retail and direct sales. You can assign a distribution channel to one or more sales organizations.
Division:
Product groups can be defined for a wide-ranging spectrum of products. For every division you can make customer-specific agreements on, for example, partial deliveries, pricing and terms of payment. Within a division you can carry out statistical analyses or set up separate marketing.
Sales area:
Combination of Sales organisation, Distribution Channel, and division.
Sales Office.
Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales office can be considered as a subsidiary.
Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a certain sales area, the sales office must be assigned to that area.
Sales Group.
The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions.
Salespersons.
Individual personnel master records are used to manage data about salespersons. You can assign a sales person to a sales group in the personnel master record.
Plant:
A plant is a place where either material are produced or goods and services provided.
Storage location:
Where we store the material.
Shipping point:
It is a physical location where we load the goods in order to deliver.
Loading point:
It is a point where we load and unload the material by means of equipments.
Business Area.
A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of developing unified business policy.
Financial Accounting (FI).
A business area is an organizational unit within financial accounting which represents a separate area of operations or responsibilities within an organization.
The system posts costs and revenue according to the business area.
The business area can be Assigned to the:
sales area (if the accounts are to be posted according to sales)
plant/division (if the accounts are to be posted according to products)
Financial accounting transactions can be allocated to a specific business area.
Credit control area.
Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control areas.
ENTERPRISE STRUCTURE
STEP 1: DEFINE COMPANY
MENU PATH: IMG u2013 ENTERPRICE STRUCTURE
FINANCIAL ACCOUNTING u2013 DEFINATION u2013 DEFINE COMPANY T.C: SPRO
Select the line 1000 and go for details and then click copy, enter the company details and save it. (ctrl s)
step 2: edit copy check delete company code
select the line 1000 go for details and then say copy , fill the details of company code. Then a address screen appears and fill the details .
then save it.
Now go for the next option
We will fine the below screen and click copy button
Press enter
Say yes
Say yes
for the remaining screen say yes to all , now the system will copy the table to your company code.
After copying below screen u will see and the say transport
In below screen u enter u r company code.
the above screen u will see is the transport request screen
Step 2: logistic general
We will get the below screen enter the details of the plant and also fill the address details of the plants and save it
then save it
DEFINE DIVISION:
HERE GO FOR NEW ENTRIES DIRECTLY BECAUSE NO DETAILS ICON IS THEIR.
SALES AND DISTRIBUTION
ENTER ALL THE DETAILS AND SAVE
2. DISTRIBUTION CHANNEL
GO FOR MENU PATH . DEFINE DISTRIBUTION CHANNEL
THEN SAVE IT
DEFINE SALES OFFICE:
MATERIAL MANAGEMENT
THIS IS NOT OUR CONFIGURATION; THIS IS THE PART OF MM CONSULTANT.
DEFINE STORAGE LOCATION
LOGISTIC EXECUTION:
DEFINE SHIPPING POINT
HERE ALSO THE SAME PROCEDURE ,
Select the line 1000 go for details and say copy. Enter the details of shipping point and save it.
The above are the definition part, now we have to link the organizational elements. The linking can be configured with the help of menu path: Img - enterprise structure - assignment
Note: what we have defined in respective module, the same we have to assign with respect to the module.
ASSIGNMENTS:
1. FINANICIAL ACCOUNTING:
ASSIGN COMPANY CODE TO COMPANY:
THEN SAVE IT.
LOGISTIC GENERAL
1. ASSIGN PLANT TO COMPANY CODE:
GO FOR THE COMPANY CODE AND HIGHLIGHT IT, NOW CLICK ASSIGN THEN SELECT THE PLANT IN THE POP UP SCEEN AND PRESS OK, WE HAVE TO GET THE BELOW SCREEN
NOTE : BUSINESS AREA CONCEPT IS VERY IMPORTANT.
SALES AND DISTRIBUTION ASSIGNMENTS
1. ASSIGN SALES ORGANISATION TO COMPANY CODE T.Code : OVX2
2. ASSIGN DISTRIBUTION CHANNEL TO SALES ORGANISATION
T.CODE: OVXK
3. ASSIGN DIVISION TO SALES ORGANISATION
T.CODE: OVXA
4. SET UP SALES AREA:
T.CODE : OVXG
5. ASSIGN SALES OFFICE TO SALES AREA
6.ASSIGN SALES ORGANISATION u2013 DISTRIBUTION CHANNEL u2013 PLANT
T.CODE : OVX6
NO MATERIAL MANAGEMENT ASSIGNMENT OF STORAGE LOCATION
WHY BECAUSE WE HAVE ALREADY MAINTAINED IN THE PLANT, SO IT IS AN ASSIGNMENT.
LOGISTIC EXECUTION
ASSIGN SHIPPING POINT TO PLANT:
NOW OUR ENTERPRISE STRUCTURE IS READY
Result :
Go for Img u2013 enterprise structure u2013 definition u2013 define company u2013 edit copy check delete company code u2013 structure u2013 navigation u2013 double click your created company code. T. code: EC01
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Error when creating transfer structure in source system

We have just had a copy of the ERP production system done and connected it to our existing QA system (done by our service providers) for a test go-live of our ERP upgrade.
Now I cannot activate the transfer rules as the transfer structure cannot be created in the source system.
I have checked the settings in table RSBASIDOC and they look okay, I can only assume that our wonderful basis people have done everything they should have but cannot be sure they've done it all correctly.
The sourcesystem is active, the RFC's are fine.
And help for a desperate man please. I've got to get this working in 1 day as basis need the system back to do an Oracle upgrade.

Hi Jonathan,
Try to replicate the DS once again and the run the program RS_TRANSTRU_ACTIVATE_ALL to activate your transfer structure. Hope it helps.
Thanks and Regards
Subray Hegde

Organisation Structure and Other Modules

Hi
I would like to know if each and every sub-module has a structure for itself or do they use the structure we create in OM.
E.g
Organisation Structure gives me a structure of the Org Units. I want to know if the same structure would be used by SD/Financials/MM etc
Appriciate your valuable answer
Rgds
Aravind

Hi,
HR contains all data related to HR system, similarly SD MM contains data related to SD MM. All the modules are integrated in SAP. Now come to your question. Org Structure should be same for a client in different module.
Sandip

How to extract organisational structure ( PPOMA_BBP) in a document /excel.

Hi . in transaction PPOMA_BBP when i go to system -> List -> Save -> Reporting Tree , the reporting tree is greyed out.
1) Is there another way to extract the organisational structure? I need to save the hierarchy + attributes .
2) If possible, can we use the extract to maintain/ create an organisational structure ?
thx

Hello,
We got a requirement like.... Suppose X company is having 5 consultants including proj mngr and is doing projects for Y and Z. In Y project 3consultants r involved, n in Z also 3consultants r involved. Proj mngr is common 2 both. We configured reporting structure evrything. But it will display only when we click on the position. The client is asking that... after giving org unit numb in ppom_old, the whole structure has 2 display....ie., who involved in the projects, who is reporting to whom, blablabla.....even in graphical struc also it is not showing...can anybody guide me, whether there is such option in sap.
Thanks

SRM 5.0 organisational structure

Hi Gurus,
is there a restriction for the number of persons integrated in the SRM (SRM 5.0) org. structure (PPOMA_BBP)? Is there a sizing guideline? We plan to expand the number of buyers and approvers up to 90.000.
Many thanks in advance,
Dirk

Hi
Welcome to world of SRM !!!
Please go through the following links, which will definitely help ->
Re: Org Model Report
Re: I want to replicate organisation structure tree of pposa screen?
Re: USERS_GEN and the 200 Limitation
If an organizational structure with a large number of dependent nodes is displayed in the overview area, access to the transaction can take a very long time.
This type of large organizational structure can occur when the vendors are transferred from the back-end system.
Please refer to the following SAP OSS Notes ->
Note 503915 - PPOMA_BBP: performance improvement overview area
Note 389869 - Organizational unit with many employees
Note 405806 - Transaction PPOMA_BBP for new material group attributes
Note 864221 - EBP 4.0+: Performance location
Note 920158 - EBP 4.0+: Shopping cart performance
Note 1044096 - RSWUWFMLEC: Wrong Emails and/or Bad Performance
Also please see this SAP Consulting Note ->
Note 1095895 - Slow response times for several SRM transactions
Re: SRM Org Structure - Vendor Root
Hope this will definitely help. Do let me know, Hope this will answer all your queries.
Regards
- Atul

No organisational structure maintained for this item

I am trying to create a shopping cart in SRM 4.0 front end and i keep getting the error no organisational structure maintained for this item. the purchasing group is not being picked up.I will greatly appreciate your help in solving this issue.
thank you

Hi Guys,
Well... I think I have found the cause of the problem. But I dont know how to solve it.
In my Org Model, "Extended Attributes" tab, "Product Categories" option selected. In that place I need to assign my Backend as the Src. System, and then choose my Product Category.
The problem is that I dont have any category linked to my backend system.    Because If I choose my SRM as the Src. System, I can see all the product categories that I have created.
Somebody knows how can I link my Product Categories to my backend?
pd: my current categories were created manually in srm (not imported from r3)
THANKS FOR YOUR HELP GUYS !!!!!!
Regards,
Diego

Organisational structure should be alphanumerical or numerical.

Hi Team,
I have a client requirement where client has requested all organisational structure like company code, chart of accounts, credit control area, conrtolling area etc all should be alphanumerical or numerical.
If its alphanumerical, what are merits or demerits and if its numerical, its merits and dermertis.
Thanks in advance,
Sameer.

Hi,
There is no importance whether it's alphanumerical or not. I would just recommend to avoid leading zeros, if you define it as numerical (mainly, for potential interfaces to other systems)
Regards,
Eli

Organisational structure button in Z Reports

Hello everybody!
We have a problem with the 'Organisational structure' button in Z Reports.
There are some checkboxes that are used to make the selection but although we check only the organisational units we want in the report, the system shows all the subordinates of that unit.
Is there any way to capture only the selected org. units in some internal tables?
Thanks a lot.
Regards,
Rupesh

Unfortunately, as we don't know your programs, we can't answer!

Organisational structure in Workflow

Hi
I'm with a client that keeps organisational structure in a non-SAP system, but might be considering moving this structure into SAP. In either case, I need to have an organisational structure in Workflow for agent assignment. If they continue to keep the org. structure outside of SAP, I will have to create the structure from scratch in WF, correct? Can the two structures be kept in synch automtically?
If they decide to go with the SAP option, will I still need to create the org.structure from scratch in Workflow, or can I somehow use the already existing org.structure in SAP.. how?
I have been looking at help.sap.com and other sources for help, but I am unable to find a clear picture..
Any help is greatly appreciated.
Kind Regards,
Thomas Kjelsrud

Hello,
For workflow you dont need to build a decicated workflow org structure, but you can use an existing OM structure. The problem in most of the times is that the OM structure which represents the organization is not always suitable for use in workflow.
I dont know which options you have with migrating the HR Om structure from a NON sap environment to a SAP system.
/Peter

Short Dump while copying Org structure from ERP to CRM

Hello Experts:
We are trying to copy the Org structure from ECC to CRM.
We have a standard transaction 'CRMC_R3_ORG_GENERATE' to copy the the org structure from ECC or the IMG path:
SPRO->CRM->Master Data->Organization Management->Data Transfer->Coppy ECC Sales Structure
We have a multiple assignment scenario where each sales groups are assigned to multiple sales offices and likewise,each sales office is assigned to multiple sales org unit in ECC.
This can be achieved by turning on the enhanced version.
In our current business,even though the sales offices and groups are created,but are not having relavance in the business,hence while running in the sandbox system, we ran the program to copy the structures in the standard mode(default) and we could copy it without issues and create the org units for every entity in CRM based on how the number ranges are defined.
What happens when enhanced version switch is turned on ::
While we turn the mode to enhanced version, The system automatically::
- enhances the Function tab page in the ppoma_crm transaction to include a grid table, in which you maintain multiple assignments of organizational units
- generates an extra dialog box to the Organization tab page in business transactions for you to select the relevant assignment path for the organizational unit
- adapts the consistency check in business transactions to take into account organizational units that have been multiple assigned
Risk factor :
Once you have switched to the enhanced backend integration version of the organizational model you cannot return to the standard backend integration version. The system will also automatically make changes to the organizational model version in CRM Mobile Sales.
Also this structure will happen across all the clients in the system,so unfortunately cannot try in a sandbox client also of the new environment.
We are building our development box,so while running the above step in standard mode,the program gives a short dump due to long execution time even though we have the same amount of data as in our prototype system.
Also, we increased the idle time value to a very high value.
When I approached SAP OSS,I was told that it is due to the multiple assignment scenario,hence we need to switch to enhanced version in CRM before we run the copy program ( CRMC_ORG_R3_GENERATE )
I am not quite sure if the mismatch of the scenarios between CRM and ECC could be causing this short dump as we could run it in standard mode in our prototype/sandbox environment without issues even with the same data volume as in the new development system .
I am looking for help from all the experts if they have come across similar issue and your recommendations/feedback if this can be corrected.
Appreciate your guidance/recommendation on this issue.
thanks!!

In CRM Best Practices Building block C05 is the step by step description how to replicate Org. structure and some of employee's master data.
Follow link - http://help.sap.com/bp_crmv12007/CRM_DE/BBLibrary/html/C05_EN_DE.htm

Organisation Structure is not replicating completely from R/3 to CRM

Hi SAP Gurus,
Plaese help me out in this issue.
We are replicating organisation structure from R/3 to CRM. There is Org Structure in which there are some sub org units say 6, under main org unit with positions and jobs. When try to replicating by tcode PFAL with evaluation path OS-CP, it geneartes IDOC in R/3, all are succesfully processed and Green. IN CRM, these Idocs are red and yellow with staus 51 and 52. As a result of this partial, org structure is replicated to CRM. In CRM, the Idoc is failed and It shows following errors:-->
1. Resource key 4AFBD7B949F406E9E10000000B7404B7 is not known (Status 51)
2. HR: ALE inbound processing for HR master data (Status 52)
3. No Filter, No Conversion, No Field converted.
Plaese advice to resolve this issue.
Thanks a lot,
Kind Regards
Ash
Edited by: Raman Khatri on Nov 23, 2009 2:43 PM
Edited by: Raman Khatri on Nov 23, 2009 2:47 PM

You can copy exactly error ??..
For replication you need use tx PIDE in R3.
In folder CRM>R3 you assign "BP Classification: Consumer, Customer, Sales prospect, competitor" to account group in R3. The BP Classification is hard code in CRM and only are available 5 types of classification.
In folder R3> CRM you assing Account group R3 to CRM Classifcation and grouping. Grouping CRM is done in SPRO > Cross-Application Components >SAP Business Partner > Basic Settings > Number Ranges and Groupings > Define Groupings and Assign Number Ranges.
Then, you define filter for replication in tx R3AC1 and replicate with tx R3AS

The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the error 0x80042316

When using Microsoft Backup on a Windows Server 2008 SP2 (not R2 - [Microsoft version 6.0.6002]) I get the error "The creation of the shadow copy on the backup destination has failed. Detailed Error: The Volume Shadow Copy operation failed with the
error 0x80042316"
The odd thing is that when I start the backup manually, it works fine. When it runs automatically the error appears.
When doing a SFC /scannow I do get errors that can't be corrected.
Is there anything short of rebuilding this machine (It's a DC and the only one this office has) I can do to fix this?

Hi,
0x80042316 means "Another shadow copy creation is already in progress". This error could occur when another VSS instance is running.
Is there any third party backup application installed? Try to uninstall it to see the result. And please also check if there is another backup schedule which causes the conflict.
Meanwhile please provide the result of:
vssadmin list providers
vssadmin list writers
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Hi,
I do have Crashplan ProE running. It started at 1900 and the Windows Backup starts at 2000. I have modified Crashplan not to start until 2300 to see if that helps.
Also:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
AND:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {f0c7ee55-5885-4894-8dd3-14fffbdd4d2e}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {017a0133-7577-4322-b513-04f72404b70a}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {6b17d670-9ea8-4ff1-a59e-b474f4b893db}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {56aad1bf-9bf1-4fde-b2f4-a706577c632d}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {e942d09d-276e-450a-9bf4-b1d5abe6af8a}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {3737164b-61ac-454c-b1f7-42f2620f10db}
State: [1] Stable
Last error: No error
Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {39458257-aca4-481e-a302-994f3eb1e9a3}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {6a8ab4aa-760c-4102-a27f-58f570c9c572}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
Writer Instance Id: {53577013-8397-448e-9a25-c7cac08aa0a8}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {ee2c9173-92e7-455c-8f73-601647c0ddb2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {b1f60392-9dfd-4e3a-bda6-3dc2cb622ba4}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {a328aede-78f0-448e-9c36-e8379e9fe2a8}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {c39fa334-5c9d-4906-a3b5-33c3444948e6}
State: [1] Stable
Last error: No error
Writer name: 'NPS VSS Writer'
Writer Id: {35e81631-13e1-48db-97fc-d5bc721bb18a}
Writer Instance Id: {3c9c5584-b5fd-48cf-8541-0c8bfa585ca0}
State: [1] Stable
Last error: No error

Organisation structure in CRM standalone

Hi ,
I need to create Sales Org, Sales Office, Sales group, in CRM standalone system. COuld anyone guide me about the settings how to go abt the same.
Thanks,
Ambrish

Hi,
can u pls send me the configuration steps for organisational structure and Business partner as well product master
Thanks ,
venkat

Copy Organisational Structure to Destination System

Similar Messages

Maybe you are looking for