Reg Organisational Structure Creation

Hi,
When Iam trying to create root Org Unit in Org Mgmnt Module it is giving the error as "No valid interval found (internal number assignment)".
I also tried to maintain the number ranges entries( internal) in spro .
I guess I might not be maintained for the correct subgroup.
So Kindly let me know the subgroup of Root org unit to maintain the number range.
Regards,

Hi Aruna,
The entry $$$$ in the field subgroup represents all number ranges not listed explicitly. You should not delete this entry.
and coming to the other two
Number assignment for plan version 10 / object type S: Subgroup 10S
so i think the other two r not default groups.
Regards,
Kitchlu

Similar Messages

Reg: Organisation structure

Hi,
my business have two company codes.each have 4 regional offices and 50 branch office and have 8 plants in 8 plants and 4 regional distribution centers. every B.o, R.O and RDC's have some storage capblity.here every dealer sales is happened through B.o"s
How to define the Org structure for SD. Here MM people all RDC's, R.O's, B.O's are considered plants. Because if u treated sloc, no documents is generated for Plant to Sloc material transfer
Regards

Hi Rao
This will vary from client to client depending upon their requirements. However, you can capture as follows:-
1) Each company code can have one sales organisation
2) Each Sales Organisation can have 4 regional offices
3) Each Regional Office can have 50 branch offices
4) Each branch office can have regional distribution centers
5) 8 plants can be created under one Sales organisation and extended to another
Thanks
G. Lakshmipathi

Reg organisational structure

hi
i would like to whether sales organisation in delhi can sell a material from plant in chennai.what i would like to know is suppose if i have five plants in five states,is it necessary to have five sales organisation.
regarding indian scenarios

>
Raj Kumar wrote:
> hi
> i would like to whether sales organisation in delhi can sell a material from plant in chennai.what i would like to know is suppose if i have five plants in five states,is it necessary to have five sales organisation.
> regarding indian scenarios
Hi,
it's not required u have 5 plants un need not req 5 sales org sales org basically it negotiating terms and condition in the market plant is basically manufacturing one.as per sap recommendation one sale sorg is sufficient if require u can have no of sales org depend on business req not depend on plant.
i hope it;s usefull for u.
Best regards,
venkataswamy.y
Edited by: yanamadala venkataswamy on Nov 25, 2008 6:41 PM

Organizational structure creation

[Organizational Structure creation using HRMD_ABA;
Appologies if you saw this message on Friday, because I did originally post it under the general area. I was hoping that if I re-posted it under this area I might get a few more responses. I have included the one response I got, plus my reponse, which does contain more detail about how I ran PFAL - program RHALEINI, and re poses the question about what needs to be created in SRM re an organisational structure, prior to doing an initial load using transaction PFAL.
Many Thanks
Claire
I am trying to set up the organizational structure in our SRM 7.0 system using our ECC 6 organizational structure. I have created all the required distribution models for SRM and ECC 6, and have set up the switch settings in SRM. The number range settings have been set to external.
As per OSS Note 36317, which concentrates on the initial distribution, and I am working through, I have run PFAL in ECC 6 only for object type O. The HRMD_ABA idocs have been successfully transferred to our SRM system, but all are at status 52.
The message for all the idoc segments is:
'You tried to create a relationship from object 01O 50000333 to object 01S 50000846. However, object 01S 50000846 does not exist or is not active in the period from 19000101 to 99991231'.
One thing I haven't done, which might be incorrect, is create an Organizational Plan in SRM. I specifically haven't done this because I am wanting to use external numbering, and therefore thought the organizational plan would get automatically created as part of the initial distribution.
Does any one have any idea how to resolve my problem?
Many Thanks
Claire
Re: Organizational Structure creation using HRMD_ABA
Posted: Aug 21, 2009 6:03 PM    in response to: Claire Crosby-C...           Reply
Hello Claire,
It looks like you are replicating "S". After the "O" replication you should run the "S".
Please refer to the OSS note 934372 u201CSRM/CRM: HR integration for business partner u2013 new featuresu201D & SAP Note # 550055 EBP/SRM: New integration for business partner as well.
Hope this is helpful.
Thanks
Ashutosh
Claire Crosby-C...
Posts: 45
Registered: 3/22/04
Forum Points: 0
   Re: Organizational Structure creation using HRMD_ABA
Posted: Aug 21, 2009 6:53 PM    in response to: ASHUTOSH TRIPATHI     Edit          Reply
Hi Ashutosh
I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
I have also read the other 2 notes you mention.
Note 363187 stated:
'Perform the following steps in the sequence given if the target system is a
mySAP.com system (SEM, CRM, BBP/EBP):
1. If you want to use the change pointers for later changes, activate
them at once. During initial transport, you should not maintain the
data in parallel in HR because the distribution takes the blocking
mechanism into account, which can cause an incomplete initial
transport.
2. All objects of object type O are distributed with program RHALEINI. As
a transfer mode, the update mode with infotype 1000 selection should
be used.
This way you make sure that all objects of object type O are created
in the target system for existence checks.
3. As previous step but for object type C.
4. As previous step but for object type S.
So far all I have tried to do is up to step 2.
When running RHALEINI I have entered the following:
Objects - Object Type = 'O'
Reporting Period - Today is selected
Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
Any thoughts would be really helpful.
Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
Thanks
Claire

Hi Ashutosh
I intend to replicate 'S', as described in the note, but nothing has been created with my initial replication of 'O'. As per the note 363187 you are supposed to distribute type 'O' first before moving on to 'S'. Is there anything really fundamental I have missed that you are supposed to do in SRM either before or after the initial set of idocs for type 'O' are brought in?
I have also read the other 2 notes you mention.
Note 363187 stated:
'Perform the following steps in the sequence given if the target system is a
mySAP.com system (SEM, CRM, BBP/EBP):
1. If you want to use the change pointers for later changes, activate
them at once. During initial transport, you should not maintain the
data in parallel in HR because the distribution takes the blocking
mechanism into account, which can cause an incomplete initial
transport.
2. All objects of object type O are distributed with program RHALEINI. As
a transfer mode, the update mode with infotype 1000 selection should
be used.
This way you make sure that all objects of object type O are created
in the target system for existence checks.
3. As previous step but for object type C.
4. As previous step but for object type S.
So far all I have tried to do is up to step 2.
When running RHALEINI I have entered the following:
Objects - Object Type = 'O'
Reporting Period - Today is selected
Transfer Mode - Insert is selected, with the Update Mode infotype set to 1000
I did think making a setting under the Update Mode Infotype seemed a little odd, as I was doing an insert, but is this not what point 2 from the OSS Note is telling me to do?
Any thoughts would be really helpful.
Am I supposed to create a skeleton Org structure before pulling in the ECC 6 structure when I am using external numbering?
Thanks
Claire

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.

How do we transport organisation structure

i want to know how to transport organisation structure from Devlopment sysytem to Quality system and then to production sysytem

Hi naresh,
First to transfer an organistion
u need to create the organistation if possible with positions, jobs users assigned to it.
create logical systems similar to any other idoc transfer, with messafe type hrmd_a for systems <=4.6 and hrmd_aba for systems >4.6
u need to mention all the infotypes in the filter of the model view controller, if u miss any one type the data related to that type will not be transfered for an employee
u need to transfer organisation with appropriate plan , object type, and its id, when u transfer an organisation if it has postions jobs and users assigned to it all the data is not transfered except the structure of organisation. if u need to fill these details u need to transfer postions , employees in the sequence u followed while creation
reward if useful
thanks & regards

Transport Request for creating Organisation structure in DEV and Quality.

Dear Gurus,
I have a issue regarding transport request creation for creating organisation structure.
My client has their own basis team, Iam doing the customization in Dev server, when iam creating organsiation structure in dev server ( Easy Access) iam unable to generate transport request, Their basis team is saying that no transport request is created in easy access.
My question is weather transport request is to be generated in Dev (Gloden client) for creating organsiation structure or not. Please guide me.

Hi Ravi,
You can try report RHMOVE00.
It is up to you to either maintain the org structure in dev server and tranport to quality or maintain it directly in quality.
Regards,
Dilek

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

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

Change of Position in Organisational structure

Hi all,
The position of an employee has changed in the organisational structure and the
new position is displayed. But the underlying workflows containing
SWX_GET_MANAGER function module, are not working properly and no agent is determined .
The above function module works properly for all other employee values.
Is there any other place where we have to determine the new position ?
Please treat it as urgent.
Thanks in advance,
Garima

You can create a small program for that. Please find a sample below:
https://wiki.sdn.sap.com/wiki/display/SRM/CodeSample3UpdatingExtendedAttributes(Storage+Location)
Regards
Kathirvel

What is apple's organisational structure as in the CEO and stuff?

Apples organisational structure such as ceo then senior vice pres. then vice pres. and stuff

I don't know that anyone here has any specific knowledge on that. We are just non-Apple-employee users.
Does this help?
http://investor.apple.com/governance.cfm

A possible guide to organisational structure in Aperture

My take is that one should first think of an ‘exclusive’ organisational structure, ie, a structure that is unambiguous, that says this picture should be here and not anywhere else, and implement that structure using projects and blue folders. Such a structure could be based on, eg, holiday locations, type of events and the events themselves, or customers.
Secondly, one should think about how else one wants to access ones images and use albums for that (and group with folders when necessary). This often can be done via topical criteria (eg., people vs landscapes). Using keywords and other metadata in conjunction with search and smart albums falls into the same category. To a certain extent this topical structure can and will be identical with the 'exclusive' one.
A lot of people choose the date as an unambiguous criteria. That is a somewhat lazy and unimaginative way (but it naturally works). But I think it is worth to make the effort to create a more descriptive structure

And then there's "The DAM Book", which a lot of photographers adhere to. This book's whole reason for being is to present an organization for storing digital assets.
However, I suspect a lot of us have developed a "modified" version of that gospel.

Reg Organisational Structure Creation

Similar Messages

Maybe you are looking for