cancel
Showing results for 
Search instead for 
Did you mean: 

SNP Subcontracting PDS Transfer Issue

Former Member
0 Kudos

Hi,

Delta transfer is not working for below scenario

1. Production version is created for header material. Production version has BOM and Master recipe assigned to it

2. Cif Integration models are genrated and activated. integration model for subcontracting PDS is activated but there is no PDS created as there is no purchase info record as yet.

3. After Few days Subcontracting Purchase info record created and production version is assigned to purchase info record

4. Again regular  Delta transfer job(genrate and activate) executed for purchase info record as well as subcontracting PDS.

  

Still there is no PDS available at vendor location. If initial transfer is executed(Genrate, Deactivate and then activate) then PDS is getting created at vendor location

As PIR creation and production version creation is done by two diffrent department there will be always few days gap between these activities.

Is this standarad behaviour? What are options available apart from initial transfer as initial transfer is very performance intensive activity

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member189901
Contributor
0 Kudos

Hii Santosh,

For SNP subcontracting the standard process is,

1. First send the Info record, which will crate t lane as well as external procurement relationship in APO side. Without info record sending PDS is useless...

2. Send PDS for Subcontrating to APO, which will determine source of supply and BOM for the SKU.

Yes you are right for subcontracting some times we faces PDS not generated after generate and activate also.

So You can put a backgroung job for "RIMODINI" for PDS model, which will take care of initail transfer.

Otherwise you can do as willian said...but unflag the change transfer check box. otherwise it'll send only those PDS where change pointer exist....

Regards

Debashis

former_member197994
Active Contributor
0 Kudos

Hi Santosh,

When talking about 'change to PDS', I think bill of material, routing or recipe and production version are included while info records are not.

You can use t-cd:CURTO_CREATE instead.

Best regards,

Tiemin

wilian_segatto
Employee
Employee
0 Kudos

Exactly. The delta logic would work for BOM, Routing/Recipe and Production Version changes.

You can run /CURTO_CREATE without checking the "Send changes" flag. That will perform an initial load of PDS, creating it correctly in SCM.

Best regards,

Will