Workflow history

This view shows the 5 most recent entries. The complete workflow log is available from the 'Document Activity' menu item.

Apr 23, 2026	Actor	Type	Activity
Lead Approval	TILBEE-ext, Amanda	Comment	commented 2:38 pm This document should cover validation of agreements against ICertis contracts so we have end to end alignment on legal contracts and purchase contracts. We need rules for when an OA / SA is created and how the ICertis contract references is included.
Comment	commented 2:36 pm Shouldnt this be part of validation rules?
Comment	commented 2:36 pm What does this mean? 'your SAP Solution"??
Comment	commented 2:36 pm Shouldn't this be covered in inclusions?
Comment	commented 2:31 pm This doesnt contain any rules.
Comment	commented 2:29 pm Shouldnt we know what this is?
Comment	commented 2:20 pm Rewrite as a conversion spec. there should be no 'make sure' but a clear rule set of field mapping - legacy to target; transformation - legacy to target; relevancy rules; conditional logic
Comment	commented 2:17 pm This is missing conditional importance / logic.
Comment	commented 2:16 pm This is very hard to read. Please restructure the table. Is this source based on only the inclusions? Why are we ending up with the same number in target? Where are the mapping or transformation rules?
Comment	commented 2:12 pm Are these exclusions in use? Include additional info on this so impacts are understood.
Comment	commented 2:11 pm Why are these being excluded?
Comment	commented 2:09 pm This needs a mapping activity as both are likely to be changing.
Comment	commented 2:08 pm This should be a mapping activity from legacy to new, not filter criteria to exclude details.
	ROWLINSON-ext, Kerry	Comment	commented 1:04 pm As part of R2 ECC developments implemented are fields: EKKO-ZZICMAGREEMENTCODE which will hold the Icertis agreement number filled by the user on new OA creation or in change OA post R2 go live. EKKO-ZZOAVERIFICATION which is a verification status which can be set by the user post R2 go live. If Icertis number is filled above, leave this blank - expect OA needs to be migrated. 01 - Verified without ICM contract (is required to be migrated, but there is no ICM agreement currently to map to) 02 - Do not migrate Ideally, every OA to migrate would have one or the other of these fields set, plus any other 'rules' met - validity date, open target value, target qty etc.
Comment	commented 12:07 pm As above, the diagrams need to be drawn in confluence for everyone to be able to see them.
Comment	commented 12:03 pm Clarify which specific blocking statuses, for both this client level check and the plant level below.
Comment	commented 12:01 pm If the valid to date is in the past, then the OA is expired. Can just be excluded. But the types of invalid dates which should be reported for cleansing are 31.12.9999 31.12.nn99 - anything more than nn(to be defined) years in the future.
Comment	commented 11:57 am Clarify what we are trying to achieve with this report. If the header is marked for deletion, the OA is not valid. Considering the account assignment data is not relevant. Same as below for the items marked for deletion. No cleansing is required for the account assignment data.
Comment	commented 11:55 am This is not possible in SAP. The header deletion is set automatically only when all items are marked for deletion. There will never be any entries in this report.
Comment	commented 11:47 am In SAP the can be OA items with blank account assignment category meaning the item is coming into stock - there will be no EKKN data. If an account assignment category is selected that requires account assignment data it has to be entered, an OA cannot exist without it. It is also feasible for account assignment to be 'unknown' on the OA, SAP will force it to be entered on the purchase order or requisition. So can we clarify what problem we are looking for with this report?
Comment	commented 11:43 am This is not possible in SAP and there will be no entries found
Comment	commented 11:41 am Unable to see or open the diagram. In confluence, the diagrams need to be drawn in the tool so that everyone can see them. I can help you with that, if required.
Comment	commented 11:39 am Typo
Comment	commented 11:39 am Can this be explained further? If there is an OA for a material it is going to have a price? Is this saying always to take the price from the info record instead?
Comment	commented 11:35 am Can this be clarified exactly which date? Valid from? Would you use the source list to determine which one they are actually using? Or look at the release history? Or ask Syensqo to confirm? The dates might not enough to make an automated choice.
Comment	commented 11:30 am Can this also exclude OAs where there is no remaining target value or no remaining quantity. This may not be exactly zero, but if only a small percentage of the total remains the contract is no longer useable in terms of raising further POs. Exclude any OAs which are not released.
Comment	commented 11:28 am This is not possible in SAP
	TILBEE-ext, Amanda	Comment	commented 7:00 am Please clarify what this means 'verified with the one year consumption'
Comment	commented 6:59 am The attribute design has been provided previously, please advise what is needed.
Comment	commented 6:59 am Please specify the source of this when using the word 'contract'
Apr 16, 2026
	JAIN-ext, Gaurav	State	changed expiry date to '23 Apr, 2026 02:11 pm' at 2:11 pm
State	changed state to Lead Approval at 2:11 pm	v36
Tech Review of Updates	JAIN-ext, Gaurav	State	gave Minor change approval at 2:11 pm

Apr 23, 2026

Actor

Type

Activity

Version

Lead Approval

TILBEE-ext, Amanda

Comment

commented 2:38 pm

This document should cover validation of agreements against ICertis contracts so we have end to end alignment on legal contracts and purchase contracts. We need rules for when an OA / SA is created and how the ICertis contract references is included.

Comment

commented 2:36 pm

Shouldnt this be part of validation rules?

Comment

commented 2:36 pm

What does this mean? 'your SAP Solution"??

Comment

commented 2:36 pm

Shouldn't this be covered in inclusions?

Comment

commented 2:31 pm

This doesnt contain any rules.

Comment

commented 2:29 pm

Shouldnt we know what this is?

Comment

commented 2:20 pm

Rewrite as a conversion spec. there should be no 'make sure' but a clear rule set of field mapping - legacy to target; transformation - legacy to target; relevancy rules; conditional logic

Comment

commented 2:17 pm

This is missing conditional importance / logic.

Comment

commented 2:16 pm

This is very hard to read.
Please restructure the table. Is this source based on only the inclusions?
Why are we ending up with the same number in target?
Where are the mapping or transformation rules?

Comment

commented 2:12 pm

Are these exclusions in use? Include additional info on this so impacts are understood.

Comment

commented 2:11 pm

Why are these being excluded?

Comment

commented 2:09 pm

This needs a mapping activity as both are likely to be changing.

Comment

commented 2:08 pm

This should be a mapping activity from legacy to new, not filter criteria to exclude details.

ROWLINSON-ext, Kerry

Comment

commented 1:04 pm

As part of R2 ECC developments implemented are fields:
EKKO-ZZICMAGREEMENTCODE which will hold the Icertis agreement number filled by the user on new OA creation or in change OA post R2 go live.

EKKO-ZZOAVERIFICATION which is a verification status which can be set by the user post R2 go live.
If Icertis number is filled above, leave this blank - expect OA needs to be migrated.
01 - Verified without ICM contract (is required to be migrated, but there is no ICM agreement currently to map to)
02 - Do not migrate

Ideally, every OA to migrate would have one or the other of these fields set, plus any other 'rules' met - validity date, open target value, target qty etc.

Comment

commented 12:07 pm

As above, the diagrams need to be drawn in confluence for everyone to be able to see them.

Comment

commented 12:03 pm

Clarify which specific blocking statuses, for both this client level check and the plant level below.

Comment

commented 12:01 pm

If the valid to date is in the past, then the OA is expired. Can just be excluded.
But the types of invalid dates which should be reported for cleansing are 31.12.9999 31.12.nn99 - anything more than nn(to be defined) years in the future.

Comment

commented 11:57 am

Clarify what we are trying to achieve with this report. If the header is marked for deletion, the OA is not valid. Considering the account assignment data is not relevant.
Same as below for the items marked for deletion.
No cleansing is required for the account assignment data.

Comment

commented 11:55 am

This is not possible in SAP. The header deletion is set automatically only when all items are marked for deletion. There will never be any entries in this report.

Comment

commented 11:47 am

In SAP the can be OA items with blank account assignment category meaning the item is coming into stock - there will be no EKKN data.
If an account assignment category is selected that requires account assignment data it has to be entered, an OA cannot exist without it.
It is also feasible for account assignment to be 'unknown' on the OA, SAP will force it to be entered on the purchase order or requisition.
So can we clarify what problem we are looking for with this report?

Comment

commented 11:43 am

This is not possible in SAP and there will be no entries found

Comment

commented 11:41 am

Unable to see or open the diagram. In confluence, the diagrams need to be drawn in the tool so that everyone can see them. I can help you with that, if required.

Comment

commented 11:39 am

Typo

Comment

commented 11:39 am

Can this be explained further? If there is an OA for a material it is going to have a price? Is this saying always to take the price from the info record instead?

Comment

commented 11:35 am

Can this be clarified exactly which date? Valid from? Would you use the source list to determine which one they are actually using? Or look at the release history? Or ask Syensqo to confirm? The dates might not enough to make an automated choice.

Comment

commented 11:30 am

Can this also exclude OAs where there is no remaining target value or no remaining quantity. This may not be exactly zero, but if only a small percentage of the total remains the contract is no longer useable in terms of raising further POs.

Exclude any OAs which are not released.

Comment

commented 11:28 am

This is not possible in SAP

TILBEE-ext, Amanda

Comment

commented 7:00 am

Please clarify what this means 'verified with the one year consumption'

Comment

commented 6:59 am

The attribute design has been provided previously, please advise what is needed.

Comment

commented 6:59 am

Please specify the source of this when using the word 'contract'

Apr 16, 2026

JAIN-ext, Gaurav

State

changed expiry date to '23 Apr, 2026 02:11 pm' at 2:11 pm

State

changed state to Lead Approval at 2:11 pm

v36

Tech Review of Updates

JAIN-ext, Gaurav

State

gave Minor change approval at 2:11 pm

Page Information

Title:	CNV-9040 Purchase Contracts
Author:	SICONOLFI-ext, Michael	Jul 16, 2025
Last Changed by:	MADHOK-ext, Jasleen	Apr 16, 2026
Tiny Link: (useful for email)	https://wiki.syensqo.com/x/7OXZNw
Export As:	Word · PDF

Hierarchy

Parent Page
Page: Conversion Specifications

Labels

Global Labels (1)

conversion

Recent Changes

Time	Editor
Apr 16, 2026 13:21	MADHOK-ext, Jasleen	View Changes
Apr 15, 2026 15:16	BATTINI-ext, Srinivasarao	View Changes
Apr 15, 2026 12:56	BATTINI-ext, Srinivasarao	View Changes
Apr 02, 2026 08:33	BATTINI-ext, Srinivasarao	View Changes
Mar 24, 2026 13:14	BATTINI-ext, Srinivasarao

View Page History

Outgoing Links

External Links (2)

https://docs.google.com/spreadsheets/d/1ycO3yrVqQufSK-M9IhU…

https://docs.google.com/spreadsheets/d/1xVlnP690LwQdXiYbuCL…

Workflow history

Space shortcuts

Page tree