Purchase Reqs created in APO are not transferred to R/3 automatically

[Former Member]

Hello all,

Recently we have upgraded our D01 and Q01 R/3 environments from ECC5.0

to ECC6.0. And now as part of testing the APO to ECC we are facing the

below mentioned problem.

Created few Purchase requisitions in the APO system after running

the heuristics in the SNP planning book but the data is not getting

transferred to the R/3 system automatically.

The Purchase Reqs are created immediately (which I can see by looking

at the distribution receipt details) but these P.Reqs show up in the

SCM Queue manager (/SAPAPO/CQ) only after 15 mins and we can see that

the P.Req are stuck in the queue with a status "Ready to be

transferrred" but never get converted to the actual R/3 P.Reqs.

On the R/3 side we can see these reqs in the inbound queue SMQ2.

We can manually force the APO P.Reqs to be pushed into R/3 either from

APO system using /SAPAPO/CQ transaction by selecting and clicking the

activate icon or from R/3 system using transaction SMQ2 by selecting

and clicking the activate icon.

Once we manually activate the APO P.Req then these go to R/3 and

convert to a actual P.Req and then this new number is immediately

updated on the APO side. No issues in this process. In the planning

book we can see the actual P.Req number from R/3.

Are we missing any connections? As part of upgrade do we need to do any settings on the R/3 side? Your help would be greatly appreciated.

We have a golive coming up and are stuck with this issue.

Harry

[Former Member]

Guys,

Thanks a lot!

Looks like we found the issue. The issue is with the QIN scheduler, it is supposed to run every two mins but somehow wasnt running. The Basis team was able to fix the scheduler (TCode: SMQR) and now everything transfers real time.

Thanks a lot for replying.

Regards,

Harry

[Former Member]

Hi,

I think the changes are getting collected in APO as are being stored as change pointers. which are generally updated in R/3 sometime later, so you may not see the changes in R/3 immediately.

Please check your global setting in /SAPAPO/C4 and check if the recording tab for the RFC user is : "collect" or "do not collect". The Do not collect changes will transfer these changes immediately to R/3 .

Please check and inform

Regards,

Sireesh

[Former Member]

Hi Harry,

1) Carryout /sapapo/ccr for purchase requisitions and check any errors are captured

2) Check number ranges are defined correctly in both R/3 and APO in customisation for purchase requisitions/orders

3) Check application logs (under smg1/clg1/c3) and check any errors are captured in both R/3 and in APO.

Pls revert with your findings.

Regards

R. Senthil Mareeswaran.

[Former Member]

Hi Senthil,

Thanks for the reply. Please see below for my findings...

1. YES, the integration model is active.

2. BTEs are active.

3. YES the publications and distribution defintion are maintained in the config.

4. YES it is maintained.

5. Yes the settings were set to be immediate.

Everything looks fine on the APO side, I am not even sure if the issue is on the APO side or the R/3 side. I am guessing we might have missed something that we need to activate on the R/3. Any pointers or directions would greatly help.

Thanks and Regards,

Harry

[Former Member]

Hi Harry,

Please check on the following.

1) In R/3, check integration model is active for purchase requisition/purchase orders.

2) Check whether change transfer is activated as BTE or change pointer for your scenario. If your setting is via change pointers, then you need to transfer the change pointers to R/3 using transaction /sapapo/c3.

3) Check distribution definition is maintained under customisation of APO under the link spro > sap guide > int with sap components > cif > basic settings for data transfer > maintain dis defintion

4) Check publication definition under link spro > sap guide > int with sap components > cif > basic settings for data transfer > maintain object specific settings

5) Check ur setting under spro > sap guide > apo > supply chain plg > configure transfer to oltp systems.

Please confirm your observations.

Regards

R. Senthil Mareeswaran.