APO CIF queues in CCR

[agam_jain3]

Hello Experts,

We are running SAP_PP_002 heurisitc in PPDS and creating purchase requisitions everyday. There are a lot of master data issues in system and we are rectifying it. We have activated cif error handing.

We expect faulty Preqs to not move as per standard system, but a lot of not faulty preqs also do not move to ECC.

They show up in CCR and CPP1 in morning and pushing them manually clears them.

Is the faulty queue in one block stopping other queues to reach? We have not specified any block size for external procurement in /sapapo/c3. I think its taking 100 as default.

Please help as how we can handle this, is this due to default size that 1 faulty queue blocking other good queues as well and they are logged in CPP1?

Regards

Agam

[rupesh_brahmankar · Accepted solution]

Hello,

Please check settings of /N/SAPAPO/C2.

In transaction /SAPAPO/C2 the value for the field Error Handling is set to 'Postprocessing of Errors, No splitting of LUWs'. Read the F1 help of Error Handling.

For CIF transfers using queued remote function call (qRFC), several objects (for example, orders) are sometimes transferred to the target system in one logical unit of work (LUW). The No splitting of LUWs setting means that none of the objects transferred are updated in the target system if an error occurs in the same LUW when an object is being processed.

Best Regards,

R.Brahmankar