SCM Planning Solutions IBP APO Ariba: Note 487261 - Blocking R/3 data transfer during SNP, CTM, PP/DS planning

Note 487261 - Blocking R/3 data transfer during SNP, CTM, PP/DS planning

Summary

Symptom

Orders are omitted during the CTM planning run. This is caused by lock conflicts between the transfer of changes in R/3 via the CIF interface and the planning in APO.

Problems of the PP/DS planning run during the specification of the order sequence, if confirmations for orders are transferred from R/3 to APO during the planning run.

Other terms

CTM planning run, locks, stop queues

Reason and Prerequisites

The respective "peg areas", usually a product/location combination, are locked during the CTM planning when purchase requisitions or planned orders are changed. If a posting is made for the same product in the same location in R/3 (e.g. inventory posting, create delivery) and transferred to APO a lock conflict may occur.

Solution

Depending on whether you are using outbound or inbound queues to transfer the data to the APO system, there are various different solutions.
In the R/3 system you can see in transaction CFC1 which queue category is set for the APO target system.

1. Outbound Queues

Before the start of the SNP or CTM planning the queues are locked in the R/3 system. This can take place by scheduling the report /SAPAPO/CIFSTOPQUEUES in the APO system.

The planning takes place in the next step of the background processing.

Finally the queues are unblocked in R/3 by scheduling the report /SAPAPO/CIFSTARTQUEUES.

The queues can also be manually locked and unlocked in transaction SMQ1 in the detail view. (Process Menu -> Generic Queue -> Lock).
To shorten the runtime when activating the many locked queues, we recommend you to import the latest qRFC version (at least 045) and to use the outbound scheduler (see related notes 481278, 442478, 400330).

2. Inbound Queues

Before the scheduling, lock the inbound queues in APO by scheduling the report RSTRFCI1.

Now the planning takes place in SNP/CTM.

After the planning unlock the inbound queues in APO by scheduling the report RSTRFCI3.

Affected queues

You can deliberately block the transfer of certain transaction data. Here are some examples:

CFSTK* Stocks

CFSLS* Sales orders and deliveries

CFPO* Purchase requisitions and purchase orders

CFPLO* Planned and production orders

You can halt all CIF queues that are sent to APO by locking the generic queue

Then neither master nor transaction data is transferred to the APO system. That is, master data changes are also NOT transferred to the APO system.
It is also possible to only block the transfer of data changes for certain master data.

You will find further documentation for the programs RSTRFCI1 and RSTRFCI3 in note 717244.

It is also possible to block the transfer of data changes for only certain master data.

1. Notes on installing the correction instructions
1.1 Create data elements
Short description: "CIF: No activation when unlocking the queues" Development class: /SAPAPO/CIF
Domain: XFELD
Field label: 10 No file
17 No activation
28 No activation of the queues
28 No activation of the queues
Documentation: none
-> The maintenance of the data element /SAPAPO/CIFNOACT is finished when you save and activate.

1.2 Create data element /SAPAPO/CIFQUEUENAME
Short description: "Name of the CIF outbound queue"
Development class: /SAPAPO/CIF
Domain: TRFCQNAM
Field label: 10 queue
15 queue name
40 queue name of a queue to be locked
40 queue name of a queue to be locked

Maintain documentation:
You reach there in the data element via the menu Goto ->
Documentation -> Change
DEFINITION -> Smart Forms Format "U1"
Queue name of a queue to be locked/started
USE -> Smart Forms format "U1"
You can generically select the names of the queues.
DEPENDICIES -> Smart Forms format "U1"

EXAMPLE -> Smart Forms Format "U1"
If you only want to lock/start the transfer of transaction data, you can select the following queues
CFSTK* Stocks -> Smart Forms Format "B1"
CFSLS* Sales orders and deliveries -> Smart Forms Format "B1"
CFPO* Purchase requisitions and orders ->Sm Froms Format "B1"
CFPLO* Planned and production orders -> Smart Forms Format "B1"
Master data changes will then continue to be transferred.

-> With all lines of the documentation without format assignment you should use the standard format.
Save the documentation in the active status.
-> The maintenance of the data element /SAPAPO/CIFQUEUENAME is concluded when you save and activate.

2. Creating programs
Use transaction SE38 in your APO system to create the programs.

2.1 Create the program /SAPAPO/CIFSTOPQUEUES
2.1.1 Entries on the initial screen
Title: "Locks of the CIF outbound queues in the related SAP R/3 System"
Category: Executable program
Application: Basis (system)
Development class: /SAPAPO/CIF

2.1.2 Copying source code from the correction instructions
Select the source code with CTRL + Y in the correction instructions.
You can then copy it to your system by pressing CTRL + C and CTRL + V.
Save the program.

2.1.3 Adding the text symbols
In the program's source text processing, select the path Goto -> Text elements -> Text symbols.
Add the following text symbols using the procedure described under 2.1.2:
SYM Text mLen
001 Queue name: 35
002 RFC destination of the queues: 35
003 R/3 System: 35
004 Queues were successfully locked 40
005 Incorrect queue name 40
ATH S_ADMI_FCD / NADM 17

Save the text elements and then activate them.

2.1.4 Activate program
First, generate the program and save it before activating it. The selection texts are created with the generation.

2.1.5 Create texts for the selection texts
In the menu of the source text processing, select the path Goto -> Text elements -> Selection texts.
Add the text to the existing name using the procedure described under 2.1.2:
Name Text
P_DEST RFC destination of APO in R/3
P_QNAME Queue name
P_R3DEST Logical R/3 system

Save the selection texts and then activate them.

Note: Finally, carry out an extended program check.
You can do this using the menu program -> Check -> Extended Check in the initial screen of the ABAP Editor.

2.2 Create the program /SAPAPO/CIFSTARTQUEUES
You create this similar to program /SAPAPO/CIFSTOPQUEUES with the following values:

For the initial screen
Title: "Unlocking the CIF outbound queues in related SAP R/3 System"
Category: Executable program
Application: Basis (system)
Development class: /SAPAPO/CIF

For the text symbols
SYM Text mLen
001 Queue name: 35
002 RFC destination of the queues: 35
003 RFC destination of the R/3 System: 35
004 Number of activated LUWs 40
005 LUW status 40
006 System error 20
007 Communication error 20
008 Invalid. Queue name 20
009 Queues were successfully unlocked 40
ATH S_ADMI_FCD / NADM 17

For the selection texts
Name Text
P_DEST RFC destination of APO in R/3
P_NOACT No activation of the queue
P_QNAME Queue name
P_R3DEST Logical R/3 system

Header Data


Release Status:	Released for Customer
Released on:	22.03.2004 10:28:22
Master Language:	German
Priority:	Correction with high priority
Category:	Program error
Primary Component:	SCM-APO-INT-SNP Please use Component from area APO-SNP* or APO-INT*
Secondary Components:	SCM-APO-SNP Supply Network Planning (SNP)
	SCM-APO-INT-PPS PP-DS / Production and Process Order
	SCM-APO-SDM Multi-Level Supply & Demand Matching
	SCM-APO-SDM-CTM Capable-to-Match