SAP BLOG Change Record in S4HANA – A New Look to ECR/ECO in S4HANA

Hi Folks,

Benefits of Change Record​

Image Courtesy : SAP Image 1​

Key Features​

image Courtesy : SAP———–Image 2​

Fiori App Required​

1. Global Process route Workbench
2. Myinbox
3. Manage Change Record / engineering Changes,
4. Manage Team and Responsibilities

Required configuration​

1 . Define Number Range for the change Record​

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Number Range Interval for Change Record



Image 3

2. Define Object types​

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object types




Note : The object types are predefined

3. Define Object Categories​

Path : SPRO > Logistics General > PLM > Change Record > Basic Settings > Define Object Categories




Note : These are predefined Category

4, Define User Status​

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status

5. Define User Action​

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Action




The User Action Text Defined appear on the front end screen of the Change Record

6 Define User Action Profile​

Path : SPRO > Logistics General > PLM > Change Record > User status > Define User Status Profile













As seen in the above screenshot, conditions help to navigate to different status from the current status, as in this case the status is 10, so when the change record is in status 10, then it can be moved to either 10,30,15 manually or via background task.

7 Define Item Relevance​

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Item Relevance.




This item relevance is used for the Items mentioned in the change record as shown in the image below for each of the object types. The control whether the enable the display the field of change relevance is covered by the configuration Define Engineering Record Type Section in Image 18

8 Define Engineering Record types.​

Path : SPRO > Logistics General > PLM > Change Record > Setting for engineering Changes > Define Engineering Record Types




The change number and the status profile defined are assigned to the change record type Z01.

The check “ProcStatus” is used to control whether the item processing status is required or not as shown in the below image

image 16​

SAP recommends the use of Process route for the Engineering change’s so the Check box Proc Route is enable for the Change record type : Z01.

Para Check column is used to enable the check whether same Object is used parallelly in other change number which is open or in process

image 17​

The Reference Object that will be used for the change record type are updated. You can create Multiple change record type having different Reference Object

Image 18​

Mapping of the Item Relevance with Refence object category is done in this node. As per the mapping only the relevant item relevance will be shown.

Image 19​

The Configuration in this Node decide, control at which user status the Change number is created in SAP and at which user status the change number created in SAP is marked as completed. The Change number created in SAP is seen at the header of the change record also via the cc03 transaction.




It is also possible to control whether the change number should be created with released key or without release key. The below parameter defined in the creation attribute decides whether the change number creation attribute, if its blank its “without release key” and if its set to 1 its ” Release Key”

Image 21​

it is possible to define the digital based on the User action as defined in Section 6

9.User Assignment to Receive Task​

Transaction : PFTC




If you want to control the Work items from the change record to be displayed to specific set of People then assign the user by navigating to

Additional Data > Assignment > Maintain

Image 23​

if you want the workflow task to create workitem as per the user id mentioned in the task created for the process route then Change the attribute of the task to General task as shown above by clicking on the Attribute button.

10. Activate Event linkage​

Transaction : PFTC

Image 24​

11. Enabling Service for MyInbox​

This service is used to allow the processing of the work items generated, for the change Record.via the MyInbox App. if this service is not enabled you will be able to see the work items in the list of the Myinbox app but you cannot open / Process it

13. Define Activities for the Change Record Processing​

Path : SPRO > Net weaver > Application Server > Basis Service > Records Management > Customization for Process Route > Create or change Activities and Activity Functions

Image 26​

Here all the Activities for the case management are defined but to filter out the relevant activities for the change record the below configuration is required, only after which you can the activities in the change record.

Image 27​

the above activity is required to change the status of the change record automatically based on the rules defined in the BRF+ application.

Change Record Processing​

1. Create Change Record​

Image 26​

2. Fill the details in the Change Record​

Image 27​

Add Objects to be changed via the change record

Image 28​

Image 29​

Template Created via the Global Process Route Workbench. The Task / Activity shown below are just for demonstration in this example are not in sync as per the status of the change record.

BRF+ Application Creation and Assignment​

Image 32​

Define the Context: its a structure with binding to DDIC

Image 33​

the output is defined as Element and has a DDIC Binding

Image 34​

Create a Decision table as a Top Expression, the inputs fields to the Decision table is from the context and the output is from the Results Data object.

Assign the BRF Application in the configuration Path​

Path : SPRO > Logistics General > PLM > Change Record > Process Route > Define Template

Change Record Process Continuation.​

Start the workflow in the change record.


the work item will be received in the my inbox App or in the SO01 Transaction. Complete the Task to move the change record to the next task as per the process route.

Image 39​

Image 40​

Change the status of the Change record. The status of the change record are as per the Section 6 ( User Action Profile )

Image 41​

if the request it to Update the Change record status based on the previous task decision that can be done via the BRF + Application.

Image 42​

Now as per the above image the change number is not created yet for the change record, but if we see the configuration defined for the change Record Image 19,20, 21, We can see that the change number is created only once it reaches the status 40. Please refer the below image where the change record is updated with change number of attribute with release key.







Perform the changes via the change number and Release the change number. After the changes are performed, the change record is updated. Once the change reord reaches the status complete the change number created is also completed.

Refer the Configuration Section Engineering Record type : Image 19






Hope this is helpful for all the folks. Happy Learning

Okumaya devam et...