Hello Celonis Team and community,
Im currently working on topics like planning adherence and schedule adherence.
The last one is basically an OTD (on time delivery) KPI, but only related to the plant performance.
Based on my company process, the GR date (goods receipt date) is the moment when the clock stops and the plant on time delivery is measured.
To my surprise, there are different GR types (see list below) and Ive asked internally the meaning and the original data fields in SAP. Unfortunately, it seems that these activities are standard Celonis content, whose definition/construct is not visible to us (not even in HANA - database level). Therefore, we are not able to determine the meaning nor the origin of them.
It is appreciated to receive a clarification of all possible GR tasks and the logic behind it (e.g. SAP original data fields).
Thank you in advance for your support.
With kindest regards,
Francesca
GR for Order
GR for sales ord.st.
GR f. sls.or.st. rev
GR for acc.assgt rev
GR for acct assgmnt
GR for order rev.
Page 1 / 1
Hi Francesca,
thanks for reaching out!
In general, we are building activities in the transformation phase after extracting the data. Depending on the deployment scenario, this can happen in the Event Collection of the Celonis Intelligent Business Cloud or on-premise.
The activities which are created differ from process to process because every process is somewhat unique. I guess you were referring to a Purchase-to-Pay process? Even though there is no standard script from Celonis, you assume correctly that certain activities for this process are created almost everytime, e.g. record goods receipt or cancel goods receipt. For those activities (case table is purchase order item in EKPO), we use SAP table EKBE:
WHEN EKBE.VGABE = 1 AND EKBE.SHKZG = S THEN Record Goods Receipt
WHEN EKBE.VGABE = 1 AND EKBE.SHKZG = H THEN Cancel Goods Receipt
WHEN EKBE.VGABE = 1 THEN Record Goods Receipt
The EKBE table displays the history per purchasing document. Field VGABE stores information about the transaction / event type, SHKZG is a debit / credit indicator (https://www.se80.co.uk/saptables/e/ekbe/ekbe.html).
The activities you have listed sound customized. Can you provide us with the full activity names of those and deeper insights into the process? Also, you or your inhouse data engineer / data scientist can look up the activity scripts in the event collection.
Cheers,
Max
thanks for reaching out!
In general, we are building activities in the transformation phase after extracting the data. Depending on the deployment scenario, this can happen in the Event Collection of the Celonis Intelligent Business Cloud or on-premise.
The activities which are created differ from process to process because every process is somewhat unique. I guess you were referring to a Purchase-to-Pay process? Even though there is no standard script from Celonis, you assume correctly that certain activities for this process are created almost everytime, e.g. record goods receipt or cancel goods receipt. For those activities (case table is purchase order item in EKPO), we use SAP table EKBE:
WHEN EKBE.VGABE = 1 AND EKBE.SHKZG = S THEN Record Goods Receipt
WHEN EKBE.VGABE = 1 AND EKBE.SHKZG = H THEN Cancel Goods Receipt
WHEN EKBE.VGABE = 1 THEN Record Goods Receipt
The EKBE table displays the history per purchasing document. Field VGABE stores information about the transaction / event type, SHKZG is a debit / credit indicator (https://www.se80.co.uk/saptables/e/ekbe/ekbe.html).
The activities you have listed sound customized. Can you provide us with the full activity names of those and deeper insights into the process? Also, you or your inhouse data engineer / data scientist can look up the activity scripts in the event collection.
Cheers,
Max
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.