Program execution during RIMODAC2..will it always reach to cif user exit

Question

Hello ,
We are implementing cif user exit for Purchase Order at R3 side to capture additional date field. So logic to capture additional date field is put in user exit CIFPUR01. We have  RIMODAC2  background job for Purchase order running on daily basis.
if there is no change in standard Purchase Order objects. When RIMODAC2 is executed  for purchase order Integration models ..will  program execution still always reach to R3  user exit part of the program irrespective of if  any change in standard purchase order object has happened or not.
Will appreciate your answer.
Thank you
Best Regards
Nilesh Patil

Answer 1

Nilesh,
I am no longer sure I understand the question.
RIMODAC2 activates the model.  Once a model is activated, if someone changes certain specific fields in an R/3 object, then these changes are sent to SCM, either immediately or via change pointers.  All this happens irrespective of IM userexits.
If this same field in this same object is changed in R/3, and a userexit also has been implemented, the  userexit will execute according to its design,  performing whatever task it has been programmed to do.
If you create and implement a userexit, it begins working at that moment in time that it is installed.  Data that flowed across 'yesterday' to SCM is not affected.  Data that flows across 'tomorrow' will be affected.  Data in R/3 will usually only flow across to SCM if there is some kind of triggering event, usually a database 'change' transaction (e.g., ME22N for POs) The mere act of installing a userexit will not generally affect existing data on either side.  The userexit only affects data that flows across the IM. Unchanged records in the R/3 database will generally not be sent to SCM by the IM, and will not be subject to userexit processing.
It is not generally the responsibility of a functional consultant to explain the workings of a userexit to a technical consultant.  It is enough that the functional identifies the userexit, and specifies the business requirement in as much detail as possible.  The developer is then responsible for carrying out the coding.  Technicals are generally expected to be competent enough to determine from the userexit docs, and from the surrounding code, how a userexit works.  They can also raise a message to SAP.  In the end, it is all just ABAP, although userexit implementations can be quite challenging. SAP seldom provides enough details in their documentation.   Once the Technical has finalized the code, Functional and Technical together then perform unit testing, before passing the mods to users for integration testing.
If your client's coders are unable to manage the task, perhaps they should engage your company to provide technical expertise, as well as functional expertise.
Best Regards,
DB49