Purchasing Data 

Use

This function provides information on the integration of purchasing data. It covers the following objects in this transfer:

·        Purchase Requisitions and Stock Transfer Requisitions [from SAP Apparel and Footwear (SAP AFS) to SAP Advanced Planning and Optimizaton (SAP APO) and vice versa]

·        Purchase Orders and Stock Transfer Orders (from SAP AFS to SAP APO)

·        Confirmations (from SAP AFS to SAP APO)

The initial and online transfer of purchasing documents with SAP AFS triggers the transfer to SAP APO.

Prerequisites

·        You have transferred the SAP AFS material master data to SAP APO.

·        You have created the stock keeping unit (SKU) variants of AFS material that is transferred as separate location products in SAP APO. For more information, see AFS Material Variant.

·        You have maintained the necessary standard Customizing settings in both the systems.

Features

This function offers the following features:

·        The SAP AFS-specific schedule-line level purchasing data is first transferred to SAP SCM as Receipts; it is then used in SAP APO for planning in Supply Network Planning (SNP).

·        The purchasing data that exist for the SKU (only grid values are considered and not the categories to determine SKU) in SAP AFS is transferred for the location product that corresponds to the particular SKU, as every SKU in SAP AFS is represented by different location products in SAP APO.

·        In SAP SCM, when the planning is done at the header location product level, the system uses the location product hierarchy in SAP SCM to get all the location products that correspond to the SKU of that header location product.

·        When the results of the planning run (purchase requisition for external procurement) are disaggregated to individual location products that fall under that hierarchy, then multiple member orders are generated for each of these location products.

·        The system then performs the reverse functionality while transferring the disaggregated data back to SAP AFS.

This means, that the receipts from SAP APO are mapped to schedule lines in SAP AFS purchase requisition.

Activities

This function involves the following activities:

·        Create and activate the integration model to transfer the purchasing data between the two systems for the SAP AFS material.

·        Carry out Aggregation to collect the available receipts of a member or SKU location products while planning for the header or group location product.

·        Plan the location product corresponding to the AFS material in the ERP system using hierarchical planning functionality of SNP in APO.

If the purchasing data already exists as a result of aggregation, it is considered as Available Receipts before planning.

·        Carry out the Disaggregation functionality to distribute the planned receipts to individual SKU location products.

As a result of the transfer of these disaggregated receipts, observe these receipts as a purchase requisition that has AFS material in the ERP system. The generated SAP AFS purchase requisition appears as Group_No in SAP APO. The purchase requisition sent from SAP AFS to SAP APO should not be changed manually in the product view. If changes are made, then Group_No cannot be generated using the planning book (SNP).

·        If necessary, perform the post-planning functionality in SAP AFS.

This includes creating orders, deliveries or post goods receipts for the requisitions received from SAP APO.

For an outbound transfer (from SAP AFS to SAP APO), the system makes sure that the purchasing data is passed only at the SKU level, not at the material level. The schedule line information is mapped to individual location products in SAP APO.

For an inbound transfer (planning results from SAP APO to SAP AFS), the system maps the purchasing data of individual location products to SKUs (grid values) of AFS materials and generates the single purchasing document in which location products are represented by schedule lines in SAP AFS. For this, the system makes use of order grouping functionality passed from SAP APO.

Example

In the figure below you see how a purchase requisition in SAP SCM is transferred to SAP AFS.

There is a header order with header location product T-shirt and two member orders for two SKU location products T-shirt M and T-shirt L. These products carry the external procured information in SAP APO.

After the transfer, it creates one purchase requisition, where the item has AFS material T-shirt and schedule lines have grid values M and L. The quantity and delivery date is properly mapped to grid values in AFS purchase requisition. Also, if needed, you can manually add more items to the purchase requisition.