What sap fi org structure . and co org structure .

what sap fi org structure . and co org structure .

hi subhash....
FI structure is
Client->Controlling Area>Company Code-->Business area...
The Co organization structure is

Operating concern [/b>- Controlling area > Comapny code--> Cost center

Thanks & Regards
ranjit
null

Similar Messages

Org management and an Org model

Hello,
What is the difference between an Org management and an Org model

Hi Iris,
Organization Management is the complete process of creating org model, setting up organizational data determination and assigning organizational data determination in the transaction.
so creating Org model is part of Organizational Management.
Regards,
Deepak

Message mapping---1 source structure and n target structures

I would like to know how many message mappings we need if we are mapping one source structure to 3 different target structures of a single receiver. I am assuming its just one message mapping.
Depending on the above answer how many interface mappings do we need.

Kalyan,
you need multi-mapping that maps one source structure to multiple target structures. Just search multi mapping in SDN and you will find many good posts.
Basically, in MM editor, go to signature tab and in the target messages add additional message types. Simple. --> Only one MM and one IM
Jayson

Usage of both salary scale structure and pay scale structure

Hi,
Background
In most of Western Europe, normally the salary ranges are set by the union agreements. At the same time, if Job Pricing using data from salary survey companies are used, the salary range (depending on what is requested from the survey companies) might not be the same with the union salary ranges.
Questions:
1. Is it possible to have 2 salary ranges stored in the system:
a. Salary range from the union for day to day and legal purposes
b. Salary range from the survey data for comparison purposes
I cannot find the solution in standard SAP because you have the choice of either checking the salary scale structure or the pay scale structure.
If I use salary scale structure, I can record minimum and maximum but not reference salary. That would affect my 'Salary Data' iView in MSS. However, if I use pay scale structure, I can record minimum, maximum and reference pay and the display in 'Salary Data' iView and the compa-ratio calculation would be accurate.
And in ECM, it is pay scale structure that is used all the time. Is there any way to have both scales recorded at the same time?
Any help or pointers would be grateful (and points rewarded, of course).
Thanks,
MJ Sherdill

Hi,
Talk to the client about their future plans.
Think about requirements that are going to arise in the Future:
Depending on the Area /s- create PS Area/s
Depending on the companies/ - Create new PS Types
Also Create PS Groups as per the employee Grades.
If you have got time then it is better to create a proper structure Ese you can go for ONE PS Area, PSA Type & PS Group.
Thanks & Regards,
Param

Same source structure and different target structure without BPM

Hi Experts,
I am using PI 7.11.My requirement is at sender side the source structure is same.Basically invoice data coming from ECC to PI as a proxy message.
Receiver side adapter is JMS.At target side ,PI has to send the invoice data to 2 receiver systems.Payment node is coming in source XML,which always comes from ECC.For one of the business system ,Payment node should be sent.For the other BS,this node should be supressed.how to achieve this with single mapping?Payload based routing is not possible in my case as i dont have any field which differentiate the receiving system name.
Regards,
Karthiga

Hi,
In receiver determination, just input the two receivers (no conditions). In message mapping, you can use the constant function called receiver to suppress or create the node. You can only test it by editing the parameters in test tab e.g
At runtime, this value (receiver) will be filled out by the entries in receiver determination. So only one mapping is needed.
Hope this helps,
Mark

What is the basic difference between MM and SRM org structure

Hi
All,
What is the difference between MM org structure and SRM org structure?
to my understanding SRM org structure deals with BP concepts where as MM don't, please correct me if I am wrong
please give your inputs
Regards,
Srinivas

Hello Srinivas,
what do you call MM organizational structure? Which ECC transaction do you launch to access it?
Regards.
Laurent.

What is Structure and Exception Cell?

What is Structure and Exception Cell?

Structure:
lets assume u have a query with 'Plant' in rows and 'revenue' in columns.
This report shows all plants values and corresponding revenue values..
if create a sturucture in rows>from context menu>new selection-->drag and drop plant and provide description as 'plant'.
now you have two structures one is kf structure and one characteristic structure(Plant).
this report shows aggragated 'revenue' for all plants.i.e. you will not see individual plants in rows.Just one row 'plant' and aggregated value of revenue of all plants.
Exception:
In exception reporting you select and highlight objects that are in some way different or critical. Results that fall outside a set of predetermined threshold values (exceptions) are highlighted in color. This enables you to identify immediately any results that deviate from the expected results.

Overall Enterprise and MM enterprise structure ??

hii experts
Can some body explain me about the overall enterprise structure and MM enterprise structure in SAP.
Explain me with some enterprise structure example in SAP.
Explanation without link will be appreciable.
Thanks

Hi,
SAP enterprise structure is organizational structure that represents an enterprise in SAP R/3 system. It consists of some organizational units which, for legal reasons or for other specific business-related reasons or purposes, are grouped together. Organizational units include legal company entities, sales offices, profit centers, etc. Organizational units handle specific business functions.
Organizational units may be assigned to a single module (such as a sales organization assigned to Sales and Distribution (SD) module, or to several modules (such as a plant assigned to Materials Management (MM) and Production Planning (PP) module).
SAP R/3 system can represent a complex enterprise structure. Its flexibility can integrate the structure of an enterprise by linking its organizational unit. Enterprise structure design is a fundamental process in a SAP implementation project. The design is mainly determined by the business scenarios performed in an enterprise. Once the design is determined, it will affect many things such as how to perform a transaction and generate reports on SAP system. Although itu2019s possible, it requires great effort to change the enterprise structure. So , we must ensure that the enterprise structure designed in the SAP implementation project can accommodate all business scenarios and enterpriseu2019s requirements for current and future situation.
A Client is the highest-level element of all organizational units in SAP R/3 system. The client can be an enterprise group with several subsidiaries. An SAP client has its own master data (Data which is used long-term in the R/3 System for several business processes such as customers, materials, and vendors master data). In SAP, a client is represented by a unique 3-digit number.
A Company Code is a unit included in the balance sheet of a legally-independent enterprise. Balance sheets and Profit and Loss statements, required by law, are created at company code level. The Company Code is the smallest organizational unit for which we can have an independent accounting department within external accounting, for example, a company within a corporate group (client). In SAP, a company code is represented by a unique 4-digit alpha-numeric for a specific client. It is the central organizational element of Financial Accounting. At least there is one company code in a client. We can set up several company codes in one client in order to manage various separate legal entities simultaneously, each with their own balanced set of financial books. Besides company code, in FICO module there is also another important organizational unit which is Controlling Area. The Controlling Area is the business unit where Cost Accounting is carried out. Usually there is a 1:1 relationship between the controlling area and the company code. For the purpose of company-wide cost accounting, one controlling area can handle cost accounting for several company codes in one enterprise.
A plant is the place of production or simply a collection of several locations of material stocks in close physical proximity. A plant is represented by a unique 4-digit alpha-numeric for a specific client. Plant is used in Material Management (MM), Production Planning (PP), and Plant Maintenance (PM) module. A plant is assigned to one company code.
A Storage Location is a storage area comprising warehouses in close proximity. A Storage Location is represented by a unique 4-digit alpha-numeric for a specific plant. Material stocks can be differentiated within one plant according to storage location (inventory management). Storage locations are always created for a plant.
pherasath

Integrate the Org structure and employees SAP HR system to CRM via ALE

Hi All,
We want to integrate the organization structure and employees from mySAP HR system to mySAP CRM system. We are also aware that the same can be achieved through ALE Interface between both these systems.
In addition to the HR Organization Structure from HR system, can we also bring over the Sales Organization Structure from R/3 using transaction CRMC_R3_ORG_GENERATE?
1) Can someone , please let us the possible challenges which might occur when we download HR Org structure from SAP HR to SAP CRM.?
2) What is the implication of maintaining an HR org structure and CRM Sales Org structure within the SAP CRM 52 system?
3) Any _precautions) should we take before doing the download via ALE??
Please get back, suitable points will be awarded.
Regards
Ritvij

Hi Ritvij,
Couple of things that spring to mind are:
1) When you do the initial data load (PFAL) try to ensure that no one is amending the Org structure as Objects can be locked and therefore not transferred. (on one of our test loads the top level was locked and therfore all subsequent levels were just transfered and we didn't have a top level)
2) Keep the 'forms of address' in CRM the same as the R/3 ones
3) Keep the same Employee and Org Unit IDs but prefix with (for exmaple) EM and OU in CRM. (Through the HR integration config in CRM). This may also (apparantley) aid you if set up something like an Employee interaction centre in the future.
I will update when other stuff springs to mind.
Cheers
Gaz

Transport of org.units and structure

Hi all
I know there is a possibility to transport org.units and its structure (PPOMA_BBP). There are some settings to do in table T77S0 (key = TRSP.CORR) and 2 reports RHMOVE30 and/or RHMOVE50 to be used depending on the setting done in T77S0.
It is also required to configure ALE distribution model with IDoc type HRMD_A.
My question is: what do I have to include in the filter? What are the relevant info types to be replicated via ALE?
We're on SRM 4.0 with SRM Server 5.0 SP08. We don't have HR module in SAP R/3 in use.
Thanks anyone for some help regarding this one!
Kind regards,
Renaud

Hi Renaud ,
Yr business card does not carry ID.
PL. mail me to have a detailed doc on yr question.
[email protected]
BR
Dinesh

Managing Org units and Master Data in project structure

How are Org units and Master data managed at the project structure? What would be the appropriate place holders for them in the structure. Should we manage it at the top of the project structure or within the business scenarios/processes. On what basis should we decide this? How would this impact in case of a global template rollout?
Please share your experiences regarding this.
Thanks.
Mike

any talented guy do this way.
i think that ur working in E2E project work
before singoff ur business process u should give to ur users master data templets..they collect for masterdatas in before realization phase...that time u should know how many specifications is there and in spections how many in quantitative and how many qualitative u will indentify. if any query let me back.
Edited by: Lakshmiananda prasad on Oct 6, 2009 11:48 AM

Org Specific Purchasing Category Structure and Values

Hi
I have an instance with 2 separate organisations defined under 1 business group. Each organisation requires its own purchasing category structure and values.
I cant seem to be able to achieve setting each org with its own values using a different category set, even when I configure the category set to be controlled by organisation. Let alone each org having its own flexfield segment configuration i.e one has 3 segments 1 has 4.
Is there anyway to achieve this in my current org structure, or do i have to create a business group for each organisation and seperate them that way to achieve this?
Thanks
James

Hi Sandeep
I have setup 2 different category sets, each controlled at org level, and then assigned them as the default category set for purchasing. However when i set it for one org it overwrites whats configured for the other org?
Do you know why i cant seperate them?
Thanks
James

Difference between Structural and Org. Based Security

Hi
Could anyone please explain the difference between Structural and Org. based security
Also could anyone please point to relevant documents.
Thanks

Structural authorization:
ex: assigning roles to position and not to userids.. Listed below are some links that may help you to get started in understanding "Structural authorization".
http://www.sap-img.com/human/structural-authorization-vs-role-authorization.htm
http://www.sap-press.de/katalog/buecher/inhaltsverzeichnis/gp/titelID-1071
https://websmp205.sap-ag.de/~form/ehandler?_APP=00200682500000001337&_EVENT=DISPLAY&COURSE=ADM940
HB

HR Org Structures and MSS

Hello Everyone,
We've been testing various scenarios in our QA system regarding the 'relationships' between teams and supervisors with and without the chief's top hat in the org structure. Then, we were left with some questions.
How does MSS work? How can a senior manager in another organisational unit see the records of a manager from another unit?
Eg:- "X" is not a manager in his Org unit, is a supervisor of 8 employees who are all Manager's within their own org unit. Then, when we assigned the chief's top hat to "X" he can only see the employees without top hat's in the same org unit of "X".
So, do we need to amend to include supervisors of managers? i.e. not supervisors of employees just supervisors of managers!
How easy is it to do that? Without this senior managers will have less functionality than individual team managers.
Please let me know if you require any clarification.
Please help me in resolving this issue. I would appreciate your help.
Thanks a lot.
Regards,
PG.

Below is the way to test:
1. Create two Org Units - A and B
2. Create employees in Org Unit A and Manager in Org Unit B
3. Make the Manager chief of Org Unit B
4. Create reporting relationship between the employee and the Manager
5. Also create relationship between the employees and the Org Unit
6. Maintain User IDs of all the employees and the Manager in IT0105 in PA30
Above steps are at ECC end
Portal steps:
1. Assign MSS role to Manager's User ID
2. Assign ESS role to employees' User ID
Assignment of roles will be done Portal Consultant.
Then login to portal as Manager and check the team Calendar whether you are able to view the employees
Regards,
Suhasini

Integrate HR org structure and CUA?

We are considering a new design for our authorization management on our production ECC 6.0 system.
There will be 2 productive ECC 6.0 systems; which system you use will depend on your global location. We currently utilize the HR org structure to assist us with provisioning and deprovisioning accounts on our durrent single ECC 6.0 instance, and we hang composite roles off of positions in the org structure, so that a fair amount of authorization management is automated.
If we were to put a CUA client over the two productive ECC 6.0 clients, how might that be integrated with the HR organizational model? Does CUA integrate well with an org structure? Any experiences with this would be helpful.

Hi Mary,
Firstly, are the org structures in the two ECC clients identical - in sync with each other?
If the org structures are different then it would limit the options that you would have:
- CUA client would simply be used for the provisioning of the user id
- The role to position allocation would still take place locally in each of the ECC clients
- You would have to maintain the 105 relationships locally in the ECC clients
- You would have to set the role maintenance option in SCUM to local maintenance
If the org structure is the same on both ECC clients, then it would provide you with some additional options:
Option 1 - use the approach described above to allow for local maintenance
Option 2 - ALE the org structure to the CUA client, then allocate the composite roles to the positions on the org structure and maintain the 105 relationship on the CUA client.
- the roles will then be distributed to the correct child system when the org recon is run
Option 3 - Use one of the ECC systems as the CUA client (Which we are busy implementing at the moment)
I'm using my ECC system as my central CUA for the production system, I know that many people would disagree with this due to upgrade requirements and all the rest. However in the Netweaver environment the ECC client is typically on the highest basis release, which caters for the CUA requirement and CUA is far more stable these days which reduces the risk. The other reason we have chosen this route is also the capacity of the ECC production system which is suitable.
Also the HRORG is maintained on the same system, therefore less ALE requirements to move the org structure between systems etc. In the landscape we currently have BI and Portal, future applications/modules include ESS, MSS, APO and SEM.
To achieve the solution I create all roles for all applications in the landscape, in the ECC client - for non-ECC roles the role definition is only role name and description (the correct authorisations are then maintained in the relevant child system). These are then distributed via RFC to the various child systems, it requires a couple of small changes but does work fine. All roles are then inlcuded into a composite role, regardless of which child system the role belongs to. The composite role is then allocated to the position in the HR org and once the HR recon is run, the role allocations are distributed to the correct child system. An example of a Line Manager Composite role would include:
- HR Line Manager (ECC Client)
- Cost Centre Manager (ECC Client)
- BW Line Manager Menu role (Portal)
- BW Line Manager Data role (BI client)
- Purchasing Approval (ECC Client)
I'm not sure if this has helped you, but in short the CUA integration with HRORG does work reasonably well and depending on the approach you choose it could affect the amount of maintenance that takes place. Just remember that the structural profile allocations would always take place locally on the ECC clients and only the role allocations can be managed from the CUA.
Regards
Sujeet

What sap fi org structure . and co org structure .

Similar Messages

Maybe you are looking for