AFS Connectivity with SAP SCM and SAP CRM 1.

Integration with SAP SCM DOC An AFS material in SAP is different from a material in the standard ERP solution. You cannot just connect SAP AFS to supply Network Planning (SNP) in SAP SCM using the already existing SAP Advanced Planning and Optimization (SAP APO) Core interface (CIF). Therefore, connectivity in SAPAFS is needed to properly transfer material master data and transactional data The following software components are involved in the data transfer: SAP AFS 6.0 SAP SCM 5.0 and higher releases SAP CRM 5.0 and higher releases SP 73 of PI_BASIS 2005_1_700 To use SAP APO, do the following:

Go to transaction FIBF. Choose Settings >> Identification >> SAP Applications Select the Active indicator for the entry ND-APO. Save your settings.

2.

Integration

The SAP SCM portion (order group and hierarchical planning) is independent of other parts of the SAP AFS connection to SAP Business Suite. However, there are dependencies within SAP AFS, such as the connection between SAP AFS and SAP SCM for production planning. The mapping between an AFS material on ERP side and a product hierarchy on the SAP SCM side will have an impact on the mapping of planned orders or purchase requisitions between the two systems. Therefore, the integration logic inside SAP AFS considers all connections of SAP AFS to the SAP Business Suite, for a simple and consistent logic for all applications

3. Constraints or Restrictions 1. In the standard ERP system, a global available to promise (ATP) check can be carried out for standard materials in SAP SCM. However, this is not possible for AFS materials when in SAP AFS the ERP system is connected to SAP SCM 2.Materials with coverage strategy : When AFS materials with coverage strategy are transferred to SAP APO for supply network planning (SNP), the category information is lost as categories are not integrated with SAP SCM. We recommend that you do not use the functionality at the category level. For example, routing based on category, assignment of stock category according to requirement category, safety stock at the category level maintained in the material master, and PIR consumption based on requirement category of the sales order. 3..When a planned production receipt or distribution receipt is created by SAP APO in the AFS inbound, the default values for the categories will be picked up if they are maintained. Unlike the standard system, the demand planning data cannot be released directly for the AFS materials. 4..Integration of scheduling agreements with SAP APO. 5.Grid value group for pricing for SAP CRM. 6.Internet Pricing and Configurator (IPC) pricing in internet sales ERP edition. 7.The SAP CRM Data Integrity Manager (DiMa) to check for product variants in SAP CRM. 8.The online transfer of production data structure (PDS) and PDS hierarchies. 9.The online transfer of Stock Keeping Unit (SKU)-specific master data, such as weight, volume, safety stock, and others. 10.The transfer of SAP AFS production orders from SAP APO to SAP AFS is technically not supported. When the report for the comparison/reconciliation of transaction data (transaction /SAPAPO/CCR) detects an inconsistency in an SAP AFS production order and suggests the transfer of this order back to SAP AFS, the transfer is not supported. SAP AFS production orders can only be transferred from SAP AFS to SAP APO. 11.Standard planning areas in SNP cannot be used. 12.The activation of SAP AFS for Business Transaction Event (BTE) is not delivered. 13.For SAP SCM, the purchasing information records are not sent for the SKU variants. Hence, the transportation lanes would not be automatically created for these SKU product variants in SAP SCM.