ECC Pur Req number
seem to have ended up in a strange problem area. The issue is that when executing /sapapo/rrp3, and create a standard pur requisition, for transferring goods from one plant to another. The object is created with a PPDS application identifier and is provided with the SAP APO internal order number. when the order is saved this is CIF'd to ECC and obtains and ECC pur requisition number. The SAP standard process is that this ECC order number replaces the internal APO order number in /SAPAPO/RRP3. The problem is currently in our system this does not occur. This is only a problem for Pur Reqs. Other order types such as planned orders or deployment confirmed orders all behave as SAP standard.
We have ran the usual jobs
Livecache consistency check - no errors
LCM_con-shk - no errors
There are no queues in blocked or waiting status.
If anyone has any ideas I would appreciate it.