Like Demand Planning (DP), Supply Network Planning (SNP) is based on a planning object structure that is used to manage the planning objects.However, planning object structures for DP and SNP are technically very different.As DP is not bound to APO master data (except in the DP-BOM scenario), it can be much more flexible compared with SNP.Therefore, an APO InfoCube is used internally to manage the planning objects.This allows the use of certain InfoCube functions such as navigation attributes.
As a result of direct linkage to business objects that are modelled by APO master data, SNP is much less flexible.Therefore, no InfoCube is used to manage these planning objects;Due to this design, no InfoCube functions such as navigation attributes can be used in SNP.The navigation attributes shipped by SAP (such as the navigation attributes '9ALOCFROM', '9ALOCTO', '9ATTYPE' for the characteristic '9ATRNAME') are an exception.You cannot modify the characteristics used in SNP, so this may prevent you from using SNP.In particular, no navigation attributes may be added to the characteristics used in SNP (for example '9AMATNR'). As of APO 3.0 Support Package 17 or note 434922, the invalid enhancement of navigation attributes is checked when an SNP planning object structure is checked or activated.
Source: Note 453644 - No use of navigation attributes in SNP
Thursday, March 25, 2010
Sunday, March 7, 2010
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.
CTM planning run, locks, stop queues
Reason and PrerequisitesThe 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.
SolutionDepending 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.
- 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).
- 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.
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
- CF*
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.
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 |
Affected Releases
|
Correction delivered in Support Package
|
Corrections Instructions
|
Related Notes
Saturday, February 27, 2010
SNC Periodic Tasks
Periodic Tasks
| Program Name / Task | Recommended Frequency | Detailed Description | ||||
| Report /SCMB/ODM_TRACKING_DATA_DELETE | Monthly or as needed | Deletion of ODM tracking data (history) This report deletes the ODM audit trail (tracking data). | ||||
| Report /SCA/ASN_PASTDUE_ALERTWRITE Transaction /SCA/DELVALERTSWRITE | Daily | This report creates the following inventory alerts: #31: ASNs in the past This means that the ASN is overdue. The report regards an ASN as overdue if the ASN fulfills the following conditions: �� Its delivery date is before a user-defined date. �� The supplier has not delivered all items. ASNs or ASN items with the status Closed, however, are regarded as delivered in full. | ||||
| Report /SCMB/ALEN_ALERT_DELETE Transaction /SCMB/ALEN_ALERT_DEL | Monthly or as needed. We recommend that you delete ASNs and alerts on a regular basis to avoid filling up your database. | Delete Current Alerts You can use the report /SCMB/ALEN_ALERT_DEL to delete alerts from the database online or in the background. If you use this report to delete an alert, for which SAP SNC records an alert history, SAP SNC generates a data record in the alert history. | ||||
| Report /SCMB/ALERTHOUSECLEAR Transaction /SCMB/ALERT_HIST_DEL | As needed | Deletes alert history | ||||
| Report /SCA/WO_DELETION Report /SCA/WO_ARC_DELETE | As needed | You can use the report /SCA/WO_DELETION to delete work orders. You can use the report /SCA/WO_ARC_DELETION to delete archived work orders | ||||
| Report /SCA/INVOICE_DELETE | As needed | You can use this report to delete invoices. | ||||
| Report /SCA/DLV_DELETE | As needed | You can use this report to delete ASNs. | ||||
| Report /SCA/PO_DELETE | Monthly or as needed | You can use this report to delete purchase orders, replenishment orders and TLB shipments. | ||||
| Report /SCA/DM_DELETEINV | As needed | You can use this report to delete inventory data. For removal of historical data from Logistics Inventory Management Engine (LIME), inventory data needs to be archived and deleted. For more information, see SAP Notes 934089 and 873400. | ||||
| SMI | ||||||
| Transaction /SCA/DLV_Close Report /SCA/DM_BOL_DLV_CLOSE | Monthly or as needed | Closing ASN Items If you do not expect any more changes to an ASN item for which you have possibly only received one partial delivery until now, and you regard the delivery as complete, you can close the ASN item in SAP SNC. The consequences of this are as follows: The ASN item acquires the delivery status Closed. SAP SNC takes the undelivered item quantity from the stock in transit. If all items in an ASN in SAP SNC have the status Closed, SAP SNC also automatically sets the status Closed for the ASN header. | ||||
| Transaction /SCA/DLV_Delete Report /SCA/DM_BOL_DLV_DELETE | Monthly or as needed. We recommend that you delete ASNs and alerts on a regular basis to avoid filling up your database. | Deletes closed or completely delivered ASNs. | ||||
| Transaction /SCA/INVALERTSWRITE Report /SCA/INVALERTSWRITE | Daily | Creates the following inventory alerts: #11: No inventory #12: Inventory above maximum #13: Inventory below minimum | ||||
|
|
|
|
|
|
|
|
| Release Processing | ||
| Transaction /SCA/BOL_REL_DELETE Report /SCA/DM_BOL_REL_DELETE | Monthly or as needed. | Deletes scheduling agreement releases |
| Transaction /SCA/RELUAALERTWRITE Report /SCA/RELUNACKNALERTWRITE | Daily | Generates alerts for releases with past due acknowledgement if the supplier has not acknowledged the release at least five days after the release creation date. |
| Transaction /SCA/RELDEMAND_ALERT Report /SCA/REL_DEMAND_ALERT_WRITE | Daily | You can use this report to generate alerts if the release contains schedule lines that the supplier cannot cover within the agreed lead time. |
Re Required Manual Periodic Tasks
| Task or Transaction | Description | Recommended frequency |
| Transaction /SCMB/ALERT_HIST_DEL | Delete Alert History Any change to an alert (owner changes, response, and so on) creates a new version, and the prior version of the report is placed into a tracking file. This file should be emptied periodically. The alert history can be deleted by alert type, minimum alert age in days, application or application | Monthly or as required |
| Transaction /SCA/TSDM_TS_DELETE | Deletes the current time series data that can be viewed on the SAP SNC application in screens such as the Inventory Monitor | Monthly or as required |
| Transaction /SCA/TSDM_TSHIST_DEL | Delete time series tracking data Users can delete time series history data by either specifying a Date From and Date To, or by specifying how many days in the past (from the current day) they want the data deleted. | Monthly or as required |
Friday, February 26, 2010
System Requirements for SAP Best Practices for SCM 5.0 Scenarios
Use
The objective of this document is to help system administrators to prepare an SAP SCM system for the installation of one or more SAP Best Practices scenarios and to ensure the system setup meets the requirements for the installation.
This document does not provide information on how to set up the entire SAP SCM system, itself, but provides you with useful additional information and troubleshooting tips.
System Landscape
To install one or more of the SAP Best Practices for SCM scenarios from this CD, you should refer to the system landscape described below and compare it with your own existing system landscape as an installation prerequisite.
Please note that the support package levels indicate the minimum support package level your system landscape should have. If higher support packages exist, we recommend that you install the highest available support package.
To install and use any SAP Best Practices scenario, you must have installed an SAP R/3 and an SAP SCM system.
SCM 5.0: Complete Version
SAP SCM 5.0 contains the following business application components on one system platform:
· SAP
· SAP EM 5.0
· SAP SNC 5.0
· SAP SCM 5.0 Add-On TM
The following table provides an overview of the software component details of the SAP SCM system:
| Software Component | Release | Level | Highest Support Package | Short description of Software Component |
| 700 | 0011 | SAPKB700011 | SAP Basis Component | |
| SAP_ABA | 700 | 0011 | SAPKA700011 | Cross-Application Component |
| ST-PI | 2005_1_700 | 0001 | SAPKITLQI1 | SAP Solution Tools Plug-In |
| PI_BASIS | 2005_1_700 | 0011 | SAPKIPYJ7B | Basis Plug-In (PI_BASIS) 2005_1_700 |
| SAP_BW | 700 | 0012 | SAPKW70012 | SAP NetWeaver BI 7.0 |
| SAP_AP | 700 | 0008 | SAPKNA7008 | SAP Application Platform 7.00 |
| LCAPPS | 2005_700 | 0004 | SAPKIBHD04 | LCAPPS 2005_700 : Add-On Installation |
| EA-IPPE | 400 | 0007 | SAPKGPID07 | SAP iPPE (EA-IPPE) 400 |
| SCM | 500 | 0008 | SAPKY50008 | Supply Chain Management 5.0 |
| SCM_BASIS | 500 | 0008 | SAPK-50008INSCMBASIS | SCM Basis 5.0 |
| QIE | 200 | 0004 | SAPK-20004INQIE | Quality Inspection Engine 2.00 |
| BI_CONT | 702 | 0004 | SAPKIBIHP4 | Business Intelligence Content |
| TPVS | 100 | 0002 | SAPK-10002INTPVS | TPVS 100 : Add-on |
Optimization Server Version:
| Identifier | Version |
| CTM01 | 5.0_REL SP08, 368812 |
| DPS01 | 5.0_REL SP08, 368812 |
| CS01 | 5.0_REL SP08, 368812 |
| SEQ01 | 5.0_REL SP08, 368812 |
| SNP01 | 5.0_REL SP08, 368812 |
| VSR01 | 5.0_REL SP08, 368812 |
Live Cache SP05 (LCA50.09, LC 7.6.01.09)
DBM server version: DBMServer 7.6.01 Build 009-123-141-487
Operating system: SunOS
LCA version: Module 50 Build 09
SAP
We recommend that you install the SAP APO specific SAPGUI add-on, which is required for certain business transactions.
SAP ECC System
SAP ECC Enterprise with Extension Set 1 (for the SAP Best Practices scenario Fulfillment Visibility we used an SAP R/3 Enterprise system with Extension Set 2)
| Software Component | Release | Level | Highest Support Package | Short description of Software Component |
| SAP_ABA | 700 | 0012 | SAPKA70012 | Cross-Application Component |
| SAP_BASIS | 700 | 0012 | SAPKB70012 | SAP Basis Component |
| ST-PI | 2005_1_700 | 0004 | SAPKITLQI4 | SAP Solution Tools Plug-In |
| PI_BASIS | 2005_1_700 | 0012 | SAPKIPYJ7C | PI_BASIS 2005_1_700 |
| SAP_AP | 700 | 0009 | SAPKNA7009 | SAP Application Platform |
| SAP_APPL | 600 | 0010 | SAPKH60010 | Logistics and Accounting |
| EA-IPPE | 400 | 0010 | SAPKGPID10 | SAP iPPE |
| EA-APPL | 600 | 0010 | SAPKGPAD10 | SAP R/3 |
| FINBASIS | 600 | 0010 | SAPK-60010INFINBASIS | Fin. Basis |
| BP-ERP05 | 600V1 | 0000 | | SAP Best Practices All-in-One based on ERP 2005 (ECC 600) |
SAP XI System
If you want to install the SAP Best Practices scenario Supplier Managed Inventory, Release Processing, Responsive Replenishment, Contract Manufacturing Procurement & Supply Network Inventory, Kanban-based Replenishment, you also need to implement an SAP XI system.
| Software Component / PI Content | Release | Level | Highest Support Package | Short description of Software Component / PI Content |
| SAP_BASIS | 700 | 0011 | SAPKB70011 | SAP Basis Component |
| Content for SAP BASIS | 700 | 0011 | | XI content for SAP BASIS 7.0 |
| Content for SCM | 500 | 0008 | | XI content for SCM 5.0 |
| Content for SCM BASIS | 500 | 0008 | | XI content for SCM BASIS 5.0 |
Non-ABAP components, such as the Integration Builder and the Integration Repository, must also be installed and have the respective support package levels.
For uploading the content in the XI System, refer to SAP note 836200.
Checklist after the System Setup
· SCM Menu
After you have installed the SCM System, you may have to set up the menu that you want to use.
To do this, access transaction SE38 and run the report /SCMB/SM_VERS.
Choose Full Version and then, choose Execute.
· Check Planning Version 000
In your SAP SCM system, use the following path:
SAP Menu ® Advanced Planning and Optimization ® Master Data ® Planning Version Management ® Model and Version Management
Make sure that the planning version 000 – Active Version is available.
If this planning version is not available, this means that the LiveCache has not been initialized. Proceed with the LiveCache initialization before you start with the installation of any SAP Best Practices scenario.
· Check that PSE services have been activated
Use transaction “strust” in your SCM system. All services should have a green light. If it is red, activate all of them. There is no need to reboot the system afterwards.
OPTIMIZER
1. Checking that the Optimizer has been installed
Transaction SM59 ® RFC Destination ® OPTSERVER_CTM01 ® Test Connection
If the connection cannot be established, this may be due to the following reasons:
· the Optimizer has not been installed
· an error occurred during the installation of the Optimizer
2. Checking that the Optimizer SP’s have been installed
Open transaction /SAPAPO/OPT09. The Optimizer Support Packages should be identical to the Support Packages of the SCM system.
· Ensuring that the
You have to make sure that the business transaction events are active in the SAP ECC system. Only if these events are active for the SAP APO integration, will changes to the transaction data be transferred from the SAP ECC system to the SAP APO system. This setting should have already been performed; this is just a reminder in order to avoid possible problems later on. Use the following procedure:
In your SAP ECC system, open the transaction BF11.
Confirm the message The table is cross client.
On the Change View: Application Indicator”: Overview screen, check that the applications ND-APO, PI-EM and NDI are active, i.e. selected. If they are inactive, select the check box to activate them.
Choose Save and go back.
Web Communication Layer (WCL)
Ensure that the WCL is installed correctly: Usually the WCL should be connected to the client 001 of the SCM system. Use transaction /saptrx/wcl_search in the SCM system to open the WCL. If a logon pop-up appears, then the WCL is set up correctly. If the message “WCL is not installed...” appears, the respective set up settings should be checked and corrected, if necessary.
Additional Information
For additional information on issues such as architecture, sizing, platforms, and upgrades, refer to following page on the Service Marketplace:
alias /SCM ® SCM Technology
For information on system monitoring, system administration, volume testing etc., check SAP note 572003. You can also refer to the Service Marketplace, using the alias /SCM ® SCM Technology ® Table of Contents ® Solution Management ® Best Practices for SAP SCM Solution Management.
Subscribe to:
Posts (Atom)