Network order integration - process overview

Network order integration has been designed with one of our customers in mind. In order to avoid misunderstandings or issues, we strongly recommend implementing it only with Proaxia’s Expert Support.

The below described processes serve as an overview of SAP PS ↔︎ FSM Cloud Connector integration scope. Please refer to the official SAP learning resources for more detailed information about project elements configuration.

You will learn about the following integration features:

  • Project network orders can be transferred to SAP FSM as service calls.

  • Project activities can be transferred to SAP FSM as activities.

  • Changes of activity/service call in SAP FSM are reflected in SAP PS.

  • Project materials can be transferred to SAP FSM as reserved materials.

 

Project creation

Projects can be created and maintained using the SAP standard transaction CJ20N. Create a new project by clicking ‘New’ → ‘Project’.

 

Enter the name (definition) and description of the project. Make sure to assign a proper Project Profile.

 

Basic project structure

WBS element

To create the main WBS element, right-click on the project definition → ‘Create’ → ‘WBS element’.

 

Name the WBS element and assign a category.

 

Network order


Integration feature: Project network orders can be transferred to SAP FSM as service calls.


To create a network order, right-click on the WBS element → ‘Create’ → ‘Network’.

 

Enter the network order’s description, profile and type (the type has to be maintained in transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1881342047).

 

Apart from transaction CJ20N, network orders can be displayed using transaction CN23 (which is similar to service order transaction IW33).

 

Activities


Integration feature: Project activities can be transferred to SAP FSM as activities.


To create an activity for a network order, right-click on the network order → ‘Create’ → ‘Activity’ (e.g. internal).

 

Enter the description of the activity.

 

Additional data regarding the activity can be customized in other tabs, such as ‘Dates’.

 

Service call transfer

After activity creation, a service call idoc is automatically transferred to SAP FSM. It is not required to release the network/activity for a service call to be sent to SAP FSM. Its status, however, will be empty (not ‘released’).

Notice that the customer (business partner) number was derived from customizing transaction https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/760250414 based on the network type and company.

 

The service call can be found in the SAP FSM Planning and Dispatching by using the number displayed in SAP PS.

 

Activity release and transfer

To transfer an activity to SAP FSM, it is required to release it first. Double-click on the activity and navigate to the ‘Edit’ menu option → ‘Status’ → ‘Release’.

 

After saving the project, Activity (and service call) idocs will be transferred to SAP FSM.

 

If we add a second activity and not release it, the system status of only the first activity will be ‘REL’, while the related network order’s status will be ‘PREL’ (pre-released).

 

The pre-released status of a network order is translated to the ‘released’ status of a service call.

 

The service call in SAP FSM will now have status ‘released’.

 

It will contain the new activity whose status is currently ‘draft’. The activity data corresponds to the data maintained in transaction CJ20N.

 

Inbound integration


Integration feature: Changes of activity/service call in SAP FSM are reflected in SAP PS.


Person assignment

Find the activity and assign it to a technician on the Planning Board.

 

Release the assignment.

 

An inbound activity idoc will be found. Its responsible person is filled with the name of the technician user.

 

Navigate to the corresponding activity in transaction CJ20N and notice that the person assignment has been updated.

 

Service call modification

Modify the test service call in SAP FSM, for example change its subject.

 

Navigate to transaction CJ20N and notice that the corresponding network order’s description has changed accordingly.

 

Activity created in FSM

To create a new activity on FSM side there is necessary to duplicate activity which was created in SAP before. Otherwise, the incoming activity will be processed with error status 51, inside logs will be information 'Order operation cannot be determined'.

 

Reserved materials


Integration feature: Project materials can be transferred to SAP FSM as reserved materials.


To create a material, right-click on an activity → ‘Create’ → ‘Material component’.

 

Specify the material, item category and quantity.

 

Save the project and notice that a reserved material idoc was transferred to SAP FSM.

 

Navigate to the activity in SAP FSM and find a new material under the ‘Reserved materias' tab.

 

Attachments

Activity attachment will be found under the ‘Attachment list’ option (GOS/BDS).

 

Time efforts

(S4)PACG 200 sp12

Time efforts created for network order activity-based FSM activities can be saved as CATS entries or network order confirmations, depending on setting ‘CATS active’ in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137707. The time postings have reference to the related network order and operation.

 

If you'd like to help us improve the documentation, please provide your feedback using the communication channels listed /wiki/spaces/PFCC/pages/1561427969. Learn about support possibilities here.