Deletion of ORGANISATION STRUCTURE in CRM

Dear Friends,
I am working with CRM 5.0. Can anybody help in stating that from where ORGANISATION STRUCTURE in CRM can be deleted.On deleting the assignment by right click to org unit only assignments gets deleted the entry remains in table.
With regards,
SACHIN

hi,
I have a query regarding the ORG structure.
Can a sales & marketing organization be created in same organization structure in CRM 5.0.
My requirement is to create a Sales & marketing Department in a company say 'SK Co.'
Once these are defined then the respective sales hierarchy can be created like for 'sales' ; Sales organization, Sales office , Sales group.
Thanks In advance.

Similar Messages

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

Bapi for org structure in crm

Hi Experts !
Pls tell me the BAPI for the ORGANIZATIONAL structure in CRM.
Thanks in advance.
Regds
Navneet

Hi Navneet,
Goto SE80 -> package : CRM_ORGMAN.
Here you will get all the FM used for Organisation structure in CRM.
I doubt if CRM as any BAPI in general for Organisation
Regards,
Anand.

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

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

Mass Delete of BDocs in SAP CRM system

Dear SDC team,
We like to hard delete some BDocs which are hanging in the txn SMW01 in CRM 5.2 system.
As of now we do not see a option to delete these unnecessary BDocs, as they are in Intermediate state (I04) .
Please tell us if there any standard report which can be used to do Mass Delete of BDocs in SAP CRM system.
Or Is there any Tables which need to be emptied .
Please help ..Points would be rewarded .
Regards
Ritvij

hi
Concerning the BDOCs without error, there is a job that you can schedule to run daily that cleans the BDocs processed without errors from the database.
The details of this job are:
Job name: SMO6_REORG
Job program: SMO6_REORG
Variants: SAP_MW_REORG
Trace data (days to hold): 7 (recomended by SAP)
Trace log (days to hold): 7 (recomended by SAP)
Period: daily.
Besides i should tell you I looked through Help and there are no best practices that I could find.We went through this process at one of my clients. They had 40,000 pluserror'd BDOCs and thousands of processed ones. The Middleware guycreated a program to delete the BDOCs that were over 2 months old andhad completed successfully to prevent the further build up of theseBDOCs. SAP Help says they are marked for deletion after they areprocessed, but it doesn't look like they get removed as wanted..
From SAP Help:
Deleting Processed BDoc Messages
1. Processed BDoc messages cannot be archived.
2. BDoc messages that have been processed successfully are marked fordeletion.
Procedure
To delete processed BDoc messages choose Architecture and Technology >Middleware > Message Flow > Delete Processed BDoc Messages
The messages you selected will be deleted.
and regarding deletion of non errant Bdocs
Usually there are two schools of thought on this issue:
1) Make the hard decision to go back to the beginning and startcorrectly all the things that caused these to error out (bank codes, taxcodes, config on R/3 side but not on CRM side, etc.). Then these can bereprocessed and everything will be brought up to date in the system.This takes time and may neccesistate hiring a Middleware resource for ashort term to help go through the process. The big part of this isidentifying those config items that are out of synch between R/3 andCRM.
2) The other way to handle these is to go through the errors quickly,gain an insight into the cause of the errors, and correct the bigthings. Delete all the old error'd BDOCs and then bring down all the bigitems again - BPs, Sales orders, products, and so forth. This is muchfaster process, but has it's own risks and problems vs Option 1 above.As these items come in, if you haven't fixed the config problems, theywill error out again. It's a fix and move - fix and move process. In theend you may have some missing data still, but the time commitment ismuch lower. You just need to get leadership's buy-in to this process.
Those error'd BDOCs are a problem and point out all the datainconsistencies that exist in the system. They are also a drag onperformance and need to be processed one way or another. After that,keeping them under a "1000" number is imperative. If you don't, theproblem will get away from you again.
finally Some Transaction Codes that people might find useful for working withBDOCs:
SMW01 Display BDocs
SMW02 Display BDoc Summary
SMW02A BDoc Messages: Show Top N Errors
SMW03 Show stats of unproc. BDoc messages
SMW10 Bdoc structure chekker
SMW19 Copy BDoc and process
SMW20 Process BDocs
SMW3EX1 Flow Carrier Example
SMW3FDBDOC Maintain Bdoctype dep. Flows
SMW3FDCUST Maintain Customer Flows
SMW3FDIF Maintain Bdoctype dep. Attributes
SMW3FDSTD Maintain Standard Flows
SMW3RBM Convert BDoc Messages to XML
SMW3RC BDoc Message Error Recovery
SMW3RCW BDoc Message Error Processor
SMW3STOP1 General Stop Configuration
SMW3STOP2 BDoc Type Stop Configuration
SMW3WD Watchdog for failed BDoc Messages
SMW3_00 BDoc Type Settings
SMW3_GSB Generic Bridge Activation
SMW3_GSB2 Generic Synch. Bridge Configuration
SMW3_GSB_SHOW Display Generic Synch Bridge Config
SMWMBSTATDISP BDoc statistics
hope info will help your cause,i told all this coz before deleting the Bdocs complete understanding of the errant and non errant Bdocs is necessary,
best regards
ashish

Block mail notification of moving employee in the organisation structure

Hello all,
When you move an employee in the organisation structure, this employee gets a mail notification of this action. How can i disable these mail notifications?
Regards
Jordi

You can change the Event Scehma in the Alert Management as explained below:
IMG Path:
SAP Implementation Guide ->
Supplier Relationship Management ->
SRM Server ->
Cross-Application Basic Settings ->
Event and Event Schema for Alert Management ->
Define Event Schema ->
-> Select BUS1006003 (Employee) in the table and double click Event Schema
-> Select MA (Employee) in the table and double click Event Control
Here delete the event DEPARTMENT_CHANGED.
This will solve your problem.
Note: If this is needed it can be added again at a later point of time and there will not be any issues.
Regards
Kathirvel

How to Delete the condition record in CRM

HI,
Can you please help me how to delete the condition record from condition table in CRM.
Please explain the usage of FM CRMXIF_CONDITION_SEL_DELETE with examples.
I have also read the documention of the function module. How to use this FM for custom defined condition table.
(this is the code given in Documentation)
DATA-OBJECT_REPRESENTATION         = 'E'
DATA-SEL_OPT-CT_APPLICATION              = 'CRM'
DATA-SEL_OPT-OBJECT_TASK                    = 'D'
DATA-SEL_OPT-RANGE-FIELDNAME        = 'PRODUCT_ID'
DATA-SEL_OPT-RANGE-R_SIGN                  = 'I'    (Including)
DATA-SEL_OPT-RANGE-R_OPTION           = 'EQ'
DATA-SEL_OPT-RANGE-R_VALUE_LOW = 'PROD_1'
Thanks
Shankar

Hi Shankar,
I am using the same CRMXIF_CONDITION_SEL_DELETE function module to delete condition record present in CRM.
But it is giving me below error in the return table of the FM after i run the program. Can you please correct me if I am doing any thing wrong?
Error in lt_return: SMW3     CND_MAST_SEL_DEL_EXT_VALIDATE     CND_M_SD
code:
ls_range-fieldname = 'PRODUCT_ID''.
ls_range-R_SIGN = 'I'.
ls_range-R_OPTION = 'EQ'.
ls_range-R_VALUE_LOW = '123456'.
APPEND ls_range TO lt_range.
MOVE lt_range TO ls_entry-SEL_OPT-range.
ls_data-SEL_OPT-object_task = 'D'.
ls_data-SEL_OPT-ct_application = 'CRM'.
ls_data-object_representation = 'E'.
CALL FUNCTION 'CRMXIF_CONDITION_SEL_DELETE'
EXPORTING
    DATA          = ls_date
IMPORTING
   RETURN        = lt_return
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
IMPORTING
    return = lt_ret.
Edited by: Saravanaprasad Nadar on Jul 7, 2010 1:27 AM

Regarding Evaluation path used in Organisation structure.

Dear All,
How would i be able to get to know the evaluation path used by organisational structure to display the structure. What i found in tcode : ppome is that it is showing evaluation but not path name. I want to know the reference path name which it is using.
Thanks,
Raj

Hi
Check the Report:
RHINFAW0 - Infotype reporting.
Regards,
Sreeram

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

Relation between Organisation Structure and Business Partner

Dear All ,
My Requirement is to pass any child node to get the corresponding parent node in the organisation structure created by T.Code : PPOMA_CRM.
I found in HRP1001 table if you pass the BP in SOBID field you will get the Parent field at OBJID in the same record . again you have to pass the OBJID as SOBID to get the next parent . Here my problem is the Business partner (SOBID) assigned in to two Org .Structure , So it is giving two records in the HRP1001 table . But i want to get the parent node comes under a particular Org Stucture .
how it is related .
Can any one help me on this,pls ?

Hello,
I don't know what your problem is, but try some of these fm. to help you to understand how hrp1001 table works. To find related objects you need to
pass sobid into objid changing otype, ralat and sclas fields depending of what you are looking for.
CRM_CENTRALPERSON_GET
CRM_BUPA_GET_HROBJECT
CRM_ORGUNIT_GETEMPLOYEES
CRM_ORGUNIT_GETBUPA
CRM_EMPLOYEE_GETORGUNIT
CRM_CP_GET_POSITION
CRM_IS_ORGUNIT_CONSISTENT
Regards, Robert

Help required on Organisation Structure

Dear All,
I wanted to prepare a Organisation Structure for one of our Client.
The Business process is like this , there is one Head office , 25 Branches & 50 Service centres .
The Head Office & Branches have similar function, i.e of booking the orders , checking the stock ( branches also stock the material ) ,if avialable than despatch, if the stock is not avilable than the stock is replenished from the main warehouse.
The service centre recieves complaints & defective goods under warranty from the customer , checks for availabilty of material , issues fresh material in place of defective material & sends it to the customer ,incase of material is not available than the requistion for the same is sent to the main warehouse & on reciept from warehouse the material given to the client.
In such scenario, how should I map my Organisation structure.
Secondly what factors decide whether a unit is to be treated as a plant or a storage location.
Thanks

Hello,
My suggestion is to have
1 company code
25 purchasing organizations (or maybe less if you are able to put some of them together)
50 plants
but I would need to know much more about how the company works.
A purchasing organization is defined as:
A purchasing organization is an organizational unit within logistics subdividing an enterprise according to the requirements of Purchasing. It procures materials and services, negotiates conditions of purchase with vendors, and bears responsibility for such transactions.
The definition for plant:
An organizational unit serving to subdivide an enterprise according to production, procurement, maintenance, and materials planning aspects. It is a place where either materials are produced or goods and services provided.
The defnition for storage location is:
An organizational unit allowing the differentiation of material stocks within a plant. All data referring to a particular storage location is stored at storage location level. This applies mainly to storage location stocks.
So deciding if you create a plant with only one storage location assigned or with more than one, it depends if you need to divide your goods in different locations. if they are all grouped in the same location, you can decide to have only one storage location per plant.
For more information about this you can checl the online help:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/dd/af9fec708b11d194da00a0c930e0da/frameset.htm
Best Regards,
Arminda Jack

Deletion of Reference customer in CRM

Hi all,
How do i delete a reference Customer in CRM?
the Reference customer numbers in R/3 and CRM are different.
We are basically up loading the master data from R/3 to CRM so that the number ranges should be identical.
can any help in this regard?
thanks in advance.
R,
mdvsapcrm.

Hello R,
Once a reference customer is assigned, it cannot be changed or deleted via the Function Module BUP_BUPA_DELETE or via transaction CRMC_BUPA_CONSUM.
If you do not have any consumers assigned, it is possible to directly delete the reference business partner from the table CRMC_BUPA_CONSUM.
If there were consumers assigned, you could change the attributes of original business partner as opposed to changing the reference customer and assigning a new business partner.
Note that a reference business partner is also mainatained in ERP (transaction VD07).
Rather test this carefully.
Good luck, Sascha

Inactive employees not showing in the organisational structure

We have employees who are in positions but may be on extended unpaid leaves of absence which means they have an inactive employment status. In the organisational structure their position is there, but their name is not displayed. Does anyone know how we can show inactive employees in the structure?
Thanks Tanya

Hi, this is fine for HR if they are looking in the backend, but when the managers see their employees on the MSS portal, for those inactive employees, they do not see the name, because the view is current.
Thanks Tanya

Deletion of ORGANISATION STRUCTURE in CRM

Similar Messages

Maybe you are looking for