PDS -Integration and change transfer

[Former Member]

Dear Experts,

We have large number of product_location selection for PDS integration and change transfer which are periodically updated in regular intervals.

PDS integration does not take too much of time while executed in background.

But, lot of time is required to complete change transfer (CURTO_CREATE).

How can we reduce time required for change transfer and Obsolete PDS deletion ?

Pls suggest..

Regards,

Shoaib

[Former Member · Accepted solution]

Hi Rupesh,

We do same , we lock obsolete versions in C223.

System scenario :

We have in all 12K combis in our system, for 100-150 combis routine are changed after every 15 days and 100 combis(versions) are newly created.

It is difficult to figure out changed versions and new combis. So, we run full fletched CURTO_CREATE for all the combis which takes lot of time to complete.

RIMODINI is helpful for existing PDS integration, want to know if it does same for new PDS or CURTO_CREATE is mandatory for new PDS?

Thanks for your suggestion

Regards,

Shoaib

[rupesh_brahmankar3 · Accepted solution]

Hi Shoaib,

CURTO_CREATE is not required for new PDS also it will not work if there is no active integration model for new PDS.. For new PDS you should have active integration model

for that you can use CFM1 and CFM2/3. For change transfer you can use the RIMODINI and you can use CURTO_CREATE batch job weekly once in change transfer mode.

Regards,

R.Brahmankar

[Former Member]

Thanks Rupesh....this seems helpful clue for me to reduce activity time.

Regards,

Shoaib

[rupesh_brahmankar3]

Hi Shoaib,

You lock the production version which are Obsoleted in C223. That will reduce the selection data in CURTO_CREATE. Also not necessey to use the CURTO_CREATE For change transfer you run report RIMODINI via transaction SE38 for the integration model which contains the PDS.

Also refer OSS note 1126803 - CIF-PDS: Performance problem when reading MAPL

Regards,

R.Brahmankar