/PACG/ECM_CUST_ORG - Maintain Organization

The ‘Our organization’ node is not reflected in SAP FSM, it’s an artificial informational entity.

Table of contents

1. Create a new organization

Organization exists with an FSM company and serves as its sub-unit/sub-company. To create a new organization below an existing entity, select a chosen entry and click the ‘Add organization’ button, as shown below.

Enter the organization’s ID, and then its name and description. Make sure the Organization’s status is set to ‘ENABLED’ and its validation dates are maintained.

Company data

Each company is an organization but not all the organizations are companies, therefore the ‘Company data’ block can be edited only for actual company entries. Currently, this block serves the same function as transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953211.

Transfer to SAP FSM

New or changed organizations should be transferred to SAP FSM with transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/611516424. To transfer all the sub-organizations being part of a given company (which is always the top-level organization), fill the ‘Company ID’ and check the ‘Include child Organization IDs’ field.

After transfer, all the organizations can be found in the SAP FSM Admin module of a given company, tab ‘Organizational Levels’.

Deletion

Deleting an organization results in deletion of all its sub-organizations. This is communicated by a message box displayed after clicking the ‘Delete organization’ button.

Transport organization structure (S4)PACG 200 SP12

Option Selected organization hierarchy can be transport to another systems. The option ‘Transport’ under Report menu allows to open window with request:

Additionally, user can easily select properly structure for transport by right-clicking on the single organization level. The option ‘Select hierarchy’ automatically mark a whole structure within parent company.

2. Assign members

Organization members must first of all be added as FSM users relevant for a given FSM company - see transaction /PACG/ECM_MAINT_USER - FSM users. After creating entries on account and company level for a given user, use the tab ‘Organization level allocation' to assign a user to a specific organization unit. Saving the transaction should trigger automatic transfer of Person objects as well as ORGLEVELALLOCATION which serves as a link between a user and an organization unit.

User allocation is visible in FSM Admin module on company level → Organizational Levels:

3. Assign objects/areas

Objects meant to be handled within an organizational structure unit (and by users assigned to a specific organization) should be assigned to a plant, sales area or personnel area (depending on an object) using the organization’s ID as Company ID.

See:

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952576

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565

https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952587

The example below shows the CUSTOMER object and specified sales area assigned to organization 1400 - a sub-organization of company 1 (transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952565).

Transfer a relevant customer to SAP FSM by using transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38175125 and filling the ‘Company ID’ field with Organization ID (1400). Since organization 1400 is not top-level, its ID will be put only in the ‘ORGLEVEL’ field of the outbound idoc’s control record. The ID of the company to which the organization belongs will be stored in the ‘COMPID’ field.

Organization assignment of the transferred object can be additionally checked in Query API, field orgLevel.

4. Adjust policy groups in FSM

User Policy Groups permissions in SAP FSM should be customized to apply to objects in the same organization level (or objects in the same and child organization levels). It should be done for each relevant CRUD action of each relevant object type.