During the immediate transfer of the SNP planned orders after the planning run, some orders are not moved immediately, they went to R3 during the next snp run in the background.
Did you check you settings for Configure transfer to OLTP systems under SPRO-Advanced Planning and Optimization-Supply Chain planning-Basic setting-Configure transfer to OLTP system?
As Sanjeev mentioned please check the transfer setting where you can set the transfer of orders in phased manner, so please check the block size for order transfer.
all the relavant settings are made in the system(like OLTP transferimmediately, publication type, distribution definition , etc.), it simply not transfering the purchase requisitions immediately and where can set the block size for transfer?
To answer your query in block size, the block size can be maintained in customizing settings. You can navigate with the following navigation path
SPRO --> Integration visa APO Core INterface --> Basic Settings for data transfer --> Publication --> Manitain Object Specific Settings
You can define an optimum block size for both external procurement and In house Production. But before you do that I would request first check if there any queue blcoks exisitng which are preventng the smooth flow of data from APO to ECC. You check this through /sapapo/cq transaction. Depending upon how you have queue set up (inbound/outbound), you can select the apprpriate drill down and see if any queue blcoks exist. If you can afford to delete the queue blocks, then please delete them and then run heursitcs again.
Also in your intial part of the query you have mentioned that the planned orders are not getting transferred. However in the latter part you are refering to purchase requistions. Are you facing problem with both the types of transaction data?
Yes, iam referring to both. first, SNP planned order donot go to r3 even though the OLTP transfer set to immediately, goes only after the next background job run and second the purchase requisitions generated are also not seen in R3 after the planning run.
any specific reason for this? note; all the settings are done.
has it got some thing to do we the material short text in the material master in the log on languge of the rfc user?
The SNP planned orders already existing in the system before making the setting in "configure transfer to OLTP" will not go. After this seeting is done you need to delete old orders and then take planning run. After this only newly created orders will flow to ECC.
If the CIF integration model is active for planned orders, then can you just create 1 order (planned order and purchase requistion) manually and see if it gets reflected immediately in ECC. By doing this atleast you will be sure about the sanctity of the integration models, distribution definition (publication settings), OLTP settings, etc. If the orders are not reflected immediately then you can start analysing everything sequnentially from integration models, to publication settings, OLTP settings, queue blocks, stuck queues (in smq1 and smq2).
Another thing which you can also try for the sake of it, if you have authorisation, create an order in ECC and see if it gets reflected in APO immediately and then delete the orders later on.
If nothing works, then you can switch on debugging.
There are umpteen number of posts on how to switch on CIF debugging.
do we have to delete the existing orders after every snp planning run inorder for the snp plnd orders transfer to r3. and the background job runs every week, so after this run does it automatically delete the snp plnd orders and creates new ones or? and there we no stuck queues.
how to set the material short text as asked in my previous reply, can you help.
You are right, when you execute full heurstics then the receipts are deleted and re generated again. however if you execute net chnage planning, then the heursitics runs on the products for which the master/transaction data has changed.
Coming to the 2nd query, are you refering to setting short text in DP or in SNP?
In SNP the description is always populated on the basis of CIF whilst in DP the description may be coming from the BW master data objects.
and the purchase requistions are by default reflected in the Distribution demand key figure unless any other order category is assigned to this info object in the SNP planing area.
We are using the network heuristic in the snp planning run, a background job runs evey week and in between the planner carry out the planning runs and make changes init..
even net change planning is also carried out with heuristics is n't it? then what is full heuristics and net chng plng(although only for changed mats) how they are executed differently?
incase of net chnage planning (net chnage heursitics), the planning engine generates chnage pointers for all the data for which there is any chnage in the master or transacation data. And then when net chnage planning is executed, then the system processes only those codes for which the change pointers exist.
As against in the full heursitics, receipts are planned for all demand irrespective of any chnage in the master or transcation data.
When heursitics is run interactively, then always full heursitics is executed. Net chnage planning can be executed only in the back ground. When you execute the transaction //sanp01, then you can find a selection for net chnage towards the bottom of the screen. Net change heursitics is run for performance reasons.
I hope the differences are clear between net chnage and full heuristics. For further clarification you can also refer to SAP note 654235.
Please award points if the information was helpful.
Can you check the "recording" column under transaction /SAPAPO/C4 and see if the setting is "Do not collect changes"? If it is not, change it to the same. By default SNP orders are not transferred immediately to R/3 unless you update change pointers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.