organizational assignment table name

• HRWPC_S_P0001 - Organizational Assignment (Infotype 0001 Fields)

SAP Table HRWPC_S_P0001

Organizational assignment (infotype 0001 fields).

HRWPC_S_P0001 (Organizational Assignment (Infotype 0001 Fields)) is a standard table in SAP R\3 ERP systems. Below you can find the technical details of the fields that make up this table. Key fields are marked in blue.

Additionally we provide an overview of foreign key relationships, if any, that link HRWPC_S_P0001 to other SAP tables.

HRWPC_S_P0001 table fields

Hrwpc_s_p0001 foreign key relationships.

3098249 - Infotype 0001 organizational fields (Position, Job, Organizational Unit and Cost Center) are not updated correctly

When replicating an employee, you may face the following symptoms:

• Despite Organizational Object, Employee Master Data and Employee Organizational Assignment replications executing successfully, Infotype 0001 still has inconsistent values for the organizational fields (ORGEH, PLANS, STELL and KOSTL);
• On the other hand, Infotype 1001 has the correct relationships between Employee, Position, Organizational Unit, Job and Cost Center;
• In this scenario, when running the Organizational Assignment replication again, it ends successfully with the message "Employee <EMPLOYEE_ID> : No relevant changes found in EC, no update needed in ERP" (SFIOM_PROCESSING165) in the Application Logs (transaction SLG1), however no update is done to Infotype 0001;

Environment

• Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP ERP HCM
• Replicating Employee Master Data and Organizational Assignments from Employee Central to SAP S/4HANA On Premise

position, org, unit, pa, pd, orga, 99999999, 00000000, PLANS, ORGEH, assignment , KBA , LOD-EC-INT-ORG , Org Integration EC to ERP On Premise , Problem

About this page

Search for additional results.

Visit SAP Support Portal's SAP Notes and KBA Search .

Privacy | Terms of use | Legal Disclosure | Copyright | Trademark

Blog about all things SAP

ERProof » SAP HR » SAP HR Training » SAP HCM Organizational Structure

SAP HCM Organizational Structure

There are 3 fundamental structures in SAP HCM :

• Enterprise structure
• Personnel structure
• Organizational structure

Enterprise and Personnel structures are part of the Personnel Management and Organization structure is part of Organizational Management (OM) submodule of SAP HCM.

The assignment to those 3 structures must allow to precisely locate any employee in the organization. Those structures are used to:

• Group together employees who share common rules and policies in terms of personnel administration, time management or payroll
• Generate default values
• Provide structures selection criteria
• Structure authorizations on master data

Overview of SAP HCM Organizational Structure

Now, let’s discuss SAP HCM organizational structure in more details. The organizational unit is a box in the pyramid of the organizational chart: a business unit, a department, a team, etc.

The position can be seen as a chair, on which will seat an employee, or a person.

Those objects are far from being the only ones existing in Organizational Management (OM) and will be detailed later on in this presentation.

Objects and Relationships

OM uses the concept of object and relationship . The following rules apply:

• An object has a type and is useless if not linked to at least one another object
• A relationship is always both ways (A and B relationships)
• A relationship has a type, which has a functional meaning (for example, 008, 012, etc.)
• All relationships are not allowed between two defined object types

Positions and Jobs

For various purposes, positions that share common characteristics may need to be grouped. This is done using the notion of job . It is used for instance to make easier maintenance of required qualifications, creation of requisitions for recruitment, or simply for reporting.

All these objects are linked in an organizational structure with so called ‘relationships’. These assignments between objects intend to cover the following business issues in the system:

Hierarchical structures

Define assignments between objects to describe their hierarchical relationship to each other. For example, you assign organizational units to each other hierarchically to represent the organizational structure of your enterprise or your organization and assign the individual organizational units to the positions that belong to them. You also use assignments to state which employee staffs which position.

Object characteristics

It is possible to use assignments to define object characteristics if own object types are planned to represent these characteristics in the system in the data model for the component Personnel & Organization . You can use the assignment of jobs to positions to describe the characteristics.

Relationships to objects of other components

It is possible to use assignments to represent relationships between objects of the component Personnel & Organization and objects of other components in the system. You can thus assign organizational units or positions to cost centers to represent the relationship between the organizational structure and the cost center structure.

When assigning an employee to a position in the infotype 0001 (Organizational Assignment), a link is created between the employee and the position in OM.

The relationship between a position and a person holds a notion of staffing percentage . This percentage needs to be correctly set to reflect the real situation. Mostly this will be set to 100%, but it may be otherwise. This is typically the case of “double hats” (people that occupy two or more positions at the same time):

This represents employees splitting their time between two (or more) positions.

Transactions for SAP HCM Organizational Structure

Below is the list of common transactions to display, create or change the organizational structure in SAP:

PP01 – Maintain Plan Data

PPOME – Change Organization and Staffing

PP02 – Maintain Plan Data

PPOSE – Display organization and Staffing Basis – Organizational Management

PPOCE – Create Organization and Staffing Basis – Organizational Management

PO10 – Maintain organizational units

PO13 – Maintain positions

PPOSE/PPOME are very complete transactions which give many display possibilities:

• Many search tools are available
• Display of structure area is adaptable to add or remove columns
• Display is time-dependent and shows movements
• Various structure views are available: with or without staff, reversed, etc.
• Infotype data shown in bottom part of the screen have been adapted to best suit our needs.

With these transactions you can

• Change the display dates to show the organizational structure on a desired date in the past or in the future

• Search in various ways on various object types

Organizational units and positions should be modified only using transaction PP01 , PO10 (organizational units only) or PO13 (positions only). They are more expert oriented and give you the full control over what you’re modifying and access to all the infotypes.

Whichever transaction is used, it is important to correctly manage dates. Indeed, the date on which data is starting in the SAP system must reflect the reality. For instance, if you decide to change an organizational unit title, then you would want to keep the historical name and date before changing to the new name before the real start date.

PP01 is an expert transaction which allows accessing all the infotypes available for a particular object. It handles the following situations:

• A position changes its title on the 1 st  of March.
• A cost center associated with the position you created has to be changed from a particular date.
• The job associated with the position you created has to be changed from a particular date.
• Move a position to another organizational unit.
• Change your organizational unit manager.

Did you like this tutorial? Have any questions or comments? We would love to hear your feedback in the comments section below. It’d be a big help for us, and hopefully it’s something we can address for you in improvement of our free SAP HR tutorials.

Navigation Links

Go to next lesson:  Structures in SAP HR

Go to previous lesson:  SAP HR Basics and Navigation

Go to overview of the course: SAP HR Training

4 thoughts on “SAP HCM Organizational Structure”

what do u need to become a SAP certified professional in HR

Can two people occupy one position?

I think position is not unique here, so two people can assign to same position

Sir, What is the tcode to view the Example SAP HCM Organizational Structure in this page. In ppome we are able to see this reporting structure. Is there a tcode to view this reporting structure comprising of all objects. This is exactly what I was looking for.

Leave a Reply Cancel reply

Do you have a question and want it to be answered ASAP? Post it on our FORUM here --> SAP FORUM !

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

• ABAP Snippets
• Top SAP Courses
• Top SAP Books

SAP and ABAP Free Tutorials

Sap Sales Organization Overview (Tables, Definition, Tcodes and SAP SD Sales Org)

This post will give you a deep technical overview of Sap Sales Organization. First we will start with some definition, then SAP Sales Organization Tables and Tcodes.

Finally, you will find some interesting tips for Sales Organization in SAP.

Table of Contents

SAP Sales Organization Definition

What is a sales organization.

Let’s start for the beginning and try to answer the following question What is a sales organization?

“Sales organization is a structured framework, specifying the formal authority and responsibility among persons working in the organization.

It consists of a group of individuals working to achieve selling objectives to increase sales, maximizing profits, expanding market share etc.” ( source )

Sales Organization in SAP

• Legally, a sales organization is included in exactly one company code.
• You assign sales offices and your own employees to a sales organization.
• All items in a sales & distribution document, that is, all items of an order, delivery or a billing document belong to a sales organization.

Definition of SAP Sales Group

The definition of sales groups is optional. You can use the SD system without creating sales groups. ⇾ You can assign a sales group to one or more sales offices. ( source )

SAP Sales Office

The definition of sales offices is optional. You can use the SD System without creating sales offices. ⇾ You assign a sales office to one or more sales areas.

If you want to go deeper of how to customize Sales Organization in SAP, check this link .

SAP Sales Organization Tcodes and Tables

Sap sales organization tcodes.

Some of the most important Tcodes for SAP Sales Organization are:

• OVX3 Company code ⇾ sales organization SD
• OVXA Division ⇾ sales organization SD
• OVB1 Sales organizations – Rebate SD
• OVX3N Company code ⇾ sales organization SD
• OVXAN Division ⇾ sales organization SD

SAP Sales Organization Tables

Here the list of main SAP Sales Organization Tables

• T001W Plant / sales organization
• TVKO Sales organization / company code
• TVKOV Distribution channel / sales organization
• TVKOS Division to sales organization
• TVKWZ Plants to sales organization

Useful Tips for SAP Sales Organization

How to find the mapping between r/3 sales org and crm org unit.

If you want to get the mapping between R/3 Sales Org Mapping with CRM Org Unit, check the following Tables:

Mapping between R/3 Sales Org and CRM Org Unit

If you prefer using SAP function modules, you may check the following SAP FM to find the mapping between ECC and CRM Sales Organization, Sales Group and Sales Office

SAP Table for sales org and plant assignment

The SAP Standard Tables TVKWZ ( or V_TVKWZ_ASSIGN ) stores the information for SAP Sales Org and Plant Assignment.

Actually, Plant is assign to Company code and not sales organization, but sales organization and distribution channel is assign to plant and the same you can get in

SPRO > Enterprise Structure > Assignment > Sales and Distribution > Assign sales org. Distribution channel plant .

Source: Table for sales org and plant assignment

Related Posts

The Most Important SAP Payment Terms Tables (ZTERM, Text…)

October 21, 2018 March 24, 2021

SAP Batch Management: User-exits and BAdIs

June 17, 2017 January 21, 2022

SAP Batch Management Tcodes, Tables and Customizing (SAP Batch Management)

June 16, 2017 January 21, 2022

• school Campus Bookshelves
• menu_book Bookshelves
• perm_media Learning Objects
• login Login
• how_to_reg Request Instructor Account
• hub Instructor Commons
• Download Page (PDF)
• Download Full Book (PDF)
• Periodic Table
• Physics Constants
• Scientific Calculator
• Reference & Cite
• Tools expand_more
• Readability

selected template will load here

This action is not available.

6.3: Assignment- Organizational Structures

• Last updated
• Save as PDF
• Page ID 47675
• Lumen Learning

Preparation

This module introduced common organizational structures, including the four classic organizational structures and various management and team organizational structures, including the situations where they are particularly well suited. This exercise is an opportunity to check your understanding of this material, matching structures with characteristics and identifying a company or industry example for each structure.

To prepare for your written assignment:

• Read the Organizational Structures module with a specific focus on the Common Organizational Structures and Factors Impacting Organization Design sections.
• Take notes on the companies and industries cited as examples of specific organizational/management structure. Some example answers will require supplemental Internet research.

Download one of the following formats:

• Organizational Structures assignment (.docx)
• Organizational Structures assignment (PDF)

Read the structure descriptions in the left column and the answer choices in the answer choices pool. Complete the table by inserting the correct answer choices in the two columns on the right. Each table entry has only one correct answer and answers are not duplicated. Submit your completed table for grading.

Your assignment will be graded on the basis of number of correct matches out of a total of 28.

Contributors and Attributions

• Assignment: Organizational Structures. Authored by : Nina Burokas. Provided by : Lumen Learning. License : CC BY: Attribution

Resources: Discussions and Assignments

Module 6 assignment: organizational structures, preparation.

This module introduced common organizational structures, including the four classic organizational structures and various management and team organizational structures, including the situations where they are particularly well suited. This exercise is an opportunity to check your understanding of this material, matching structures with characteristics and identifying a company or industry example for each structure.

To prepare for your written assignment:

• Read the Organizational Structures module with a specific focus on the Common Organizational Structures and Factors Impacting Organization Design sections.
• Take notes on the companies and industries cited as examples of specific organizational/management structure. Some example answers will require supplemental Internet research.

Download one of the following formats:

• Organizational Structures assignment (.docx)
• Organizational Structures assignment (PDF)

Read the structure descriptions in the left column and the answer choices in the answer choices pool. Complete the table by inserting the correct answer choices in the two columns on the right. Each table entry has only one correct answer and answers are not duplicated. Submit your completed table for grading.

Your assignment will be graded on the basis of number of correct matches out of a total of 28.

• Assignment: Organizational Structures. Authored by : Nina Burokas. Provided by : Lumen Learning. License : CC BY: Attribution

• Implementing Product Management

Example of Assigning Organizations Using Item Rules

You can define assignment rules that automatically assign items to one or more organizations when a condition is satisfied. The condition can be based on attribute values, another organization assignment, or a catalog assignment.

The following table summarizes an example of an item rule that:

Is defined in an assignment rule set.

Tests whether an item has a product type of In-house . If the result of the test is true, then assign the item to the organizations M2 and M3 .

Tests whether an item has a product type of Bought-outside . If the result of the test is true, then assign the item to the organization T1 .

Note that this rule has more than one THEN expression. You add THEN expressions by using the Add Row action. The expressions are evaluated in the sequence of the rows, and the execution is halted when the first THEN expression evaluates to True. You can add additional rows of Then Expressions by clicking Add Row .

Related Topics

• Rules and Rule Sets
• Define Rule Sets and Item Rules
• Item Rule Syntax