Problems with APO Integration Models

[Former Member]

Hi.

We have a job in our system running daily program RIMODAC2

to pass the changed information in SAP R/3 to our APO machine.

All the documentation says that the customer data to transfer is based in Change Pointers message CIFCUS.

Most of the times the job runs perfectly. But sometimes ALL the data about customers in R/3 is passed to APO generating severe performance problems when it reaches APO.

If I take a look at the pointers table for that particular day nothing strange appears and the number of pointers is similar to a common day.

Have you experienced something like this?

I really don't understand what is happening.

Thanks in advance.

Rui Pinto

[somnath_manna]

Hi Rui,

The program mentioned by you is to Activate Integration models in background. It is not just transfer of Changes. For transfer of changes the program is RCPTRAN4 or txn. code CFP1.

Now let me give you a scenario:

You have integration model CUS1 which is already active.

Tonight you generate new integration model CUS2. The next thing you do is run RIMODAC2 - it will activate integration model CUS2. But since CUS1 is already active it will do a delta transfer (only new customers that are in CUS2 integration model).

On the other hand if for some reason integration model CUS1 is inactive when you are activating CUS2 (report RIMODAC2) then it becomes an Initial Transfer. Bottomline all customers in integration model CUS2 are transferred to APO since there is no active integration model.

This can result in large number of queues to transfer.

Hope this explanation helps.

Please note change transfer pointers will move from R/3 to APO only for those customers (in this case) which are in an active integration model.

Typically first do change transfer, next generate new integration models and then activate the integration models. The last step can be to delete old integration models (after a gap of few days/weeks).

Thanks,

Somnath