ADVANCED PLANNING AND OPTIMIZATION Contents

ADVANCED PLANNING AND OPTIMIZATION ................................................................................................ 1 Advantages of APO. .................................................................................................................................. 1 Additional advantages of APO .................................................................................................................. 1 Core Interface ........................................................................................................................................... 2 Basic settings of CIF............................................................................................................................... 3 Business system Group ............................................................................................................................. 7 Master Data integration ........................................................................................................................... 7 Important question. .............................................................................................................................. 9 Master data for Transferring Data changes. ............................................................................................. 9 SCM Master Data in CIF .......................................................................................................................... 10 Transfer of Master Data from ECC to APO .......................................................................................... 11 Master data and its uses in CIF ........................................................................................................... 12

Advantages of APO.
High Performance Live cache is available i.e. Memory residency power. Exact time of MRP run is calculated in APO (i.e. Hrs, mins ,sec) Detailed scheduling :Quantity and capacity can be calculated at a time in APO but not in ECC ATP check: Multilevel material and capacity available check for sales order is done. Multilevel forward scheduling. Optimization of algorithm with the limit of detail scheduling, minimal setup time, setup cost, date delays, alternative resources etc. Alerts are configured in APO.

Additional advantages of APO

 You can execute detailed scheduling with PP/DS as simultaneously .material and capacity planning To the minute requirement planning can be done .order and secondary requirements are created with time specification (that corresponds to ECC time) You can define resource as finite in resource master. Order operation are only created in such resources if there is sufficient capacity for the order quantity on the corresponding date. If the available capacity is insufficient the system fetches for a new data taking capacity situations in account. The fetching method is profile controlled (i.e. based on strategy) Optimizing order sequence/machine commitment Bi-directional propagation of order change It is automatic and immediate planning

Core Interface
Data transfer is done from SAP ECC to APO and APO to ECC i.e. bi-directional. And Non-sap can be done using BAPIs Sales orders, planned orders, purchased orders, stock will go to APO from ECC. BAPI ->Business application programming Interface. Mainly PP related master data(Routing, Capacity, resources, work center, BOM etc.) will go to APO CIF menu path. SAP logon->Logistics->Central functions->Supply chain planning interface->core interface APO>integration model->Create CFM1/Activate/display/Delete.

Basic settings of CIF

Creation of logical system and assign to Target system by creating RC destinations. 1. Description: Creation of Logical system. Menu path: SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Define logical system. ( BD54)

1. Description: Once the Logical system is created we need to assign the logical system to client. SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Assign logical system to client (SCC4)

2.

Description: Specify the APO resource after assigning logical systems to client.

SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Specify the APO resource(NDV2)

3. Description: Setup RFC destinations. SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Set up RFC destinations.(SM59) APO consultant will work in TCP/IP connections and in internal connections.

4. Description: Assign RFC to different application cases. SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Assign RFC to different application cases.(CFC7) i.e here we assign logical system to RFC . 5. Description: Setting up the target system and queue type. SPRO->IMG->integration with other SAP component->APO->Basic settings for setting up system landscape->Setting up the target system and queue type(CFC1)

Business system Group

Business system group is basically Assigning number. If data from different logical systems is to reference the same objects in the SCM system (for example, because you work with multiple ERP systems and one SCM system), then we need to define BSG0. Menu Path: Basic Settings for Creating the System Landscape Maintain Business System Group. If you create master data in the SCM system, we recommend that you assign this system to the same BSG as that used for the logical systems that contain the master data server. Only then can preliminary maintenance of the master data be carried out in the SCM system. Once you have transferred data, it can be problematic to subsequently change the BSG assignment. It should prevent the contradictory nature of 2 objects.

Master Data integration

Customer, Plant, material master, routing, BOM, master recipe will be interfaced with APO as Product. CIF is real Time interface. Additional master data is created in APO. In master data integration we select the data object and APO target system for data transfer. Creation, Change, Display, Deletion possible

Recommendations for Master data integration models. Customizing for APT setup groups and product allocation. Plant and distribution centers are grouped. Change master records. Characteristics and classes. Material master (includes (+) classes and characteristic). Batches integration. MRP areas and material master for MRP areas. Planning Product Material for which ATP should takes place in APO. Planning Product. Customer and vendor. Work center. Product data structures (PDS) and Process models. Purchasing info records and scheduling arguments and contracts (date ,Quantity will carry).

3 steps for master data integration (Logical system) Target system Which Master data objects to transfer? Selection area. Integration Model Initial Data Transfer1. 1. Generate integration model: Determine name and APO ,Plant and target system . 2. Activate integration model Integration model is active and Master data will be transferred Integration Model Generation Integration Model = Name + Application Target System = APO System (it should be a logical system having active RFC connection) Specify data objects to transfer - Filtering criteria available {Examples: -Plant, MRP Type (X0 or X1), MRP Controller} Execute system compiles the selected data objects (report available tocheck compiled objects) Generate (save the model)

Integration Model Activation Activate integration model This initiates data transfer from R3 to APO The integration models are created with time-stamps The active integration model is indicated by the icon (Green tick symbol)

Important question.
What effect does this MRP procedure have? The affect for planned order transfer from non-sap system to APO a BOM explosion is still performed so that dependent requirement can be covered. Which planning method is endorsed in additional selection parameters? Planning method 1.Planned with non-sap system.

Master data for Transferring Data changes.

The transfer of data changes is concerned with transferring data records that have been changed or recently created in SAP R/3 to SAP APO once the initial data transfer has already taken place. Changes to master data and the creation of new master data relevant to SAP APO In most cases, you make changes to master data in the ERP system because this is the superordinate system for master data. There are two different scenarios for this: Changes to master data fields that are already contained in an active integration model The ERP system marks these changes using change pointers .When the integration model is activated, the system automatically evaluates all change pointers and transfers the corresponding master data records to the target system. Only the master data records that have been changed are transferred, not all of the data records that are contained in the integration model. If you change these master data objects in the ERP system, the system writes a note for ALE change pointer.

As a prerequisite, change pointers must have been activated in CIF. In addition, you must specify for which message types changes pointers should be written. To do this, following settings are required. In the CIF IMG, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Activate ALE Change Pointers Generally, or call transaction BD61. Set the relevant indicator. Then, in the IMG for CIF, choose Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Activate ALE Change Pointers for Message Types, or call transaction BD50. Choose the relevant message types.

Schedule background jobs in which the integration model is activated regularly (for example, at night). The change pointers will then be evaluated each time. This ensures that your master data in the target system is always up-to-date. If you do not regularly activate the integration model and want to evaluate the change pointers, you can use report RCPTRAN4. Create a variant of this report containing the target system and the selection of master data objects. For the material, customer, vendor, and setup group master data (message types CIFMAT, CIFCUS, CIFVEN, and CIFSTG), you can also set the periodic transfer of change transfers by using transaction CFC9. In this case, change pointers must also be activated. In the IMG for CIF, Basic Settings for the Data Transfer Change Transfer Change Transfer for Master Data Configure the Change Transfer for Master Data, or call transaction CFC9. Changes to master data fields relevant to filtering These changes mean that certain master data entries now fulfill the selection criteria of an integration model that already exists. Fields relevant to filtering are those that are given in the General Selection Options for Materials section of the selection screen for the integration model (material type, plant-specific material status, MRP controller, MRP type, and ABC indicator).

SCM Master Data in CIF

It explains us: How the master data and CIF is combined? How the master data is taken from ECC to APO? How transfer of master data effects in APO? Master data from ECC to APO where it acts as an Active model. Any master data created in APO manually it will exclusively attached to active model. Several planning version can be created in APO. Default planning version of APO planning version is 000. In Version Mgmt., configurations are done based on how the planning versions are created.

Transfer of Master Data from ECC to APO

Initial transfer

Plant Customer Vendor Material Master Purchase info record Work center Capacity Routing and BOM Characteristics and classes Other objects

Location
Product External procurement reference Resource Production process model Characteristics and classes Other objects.

Apo will not require all the data from ECC BOM and routing will be transferred as Production process.

Master data and its uses in CIF

Table of master data in CIF Applications object Plant MRP areas Customer vendor Material master Batch classes Characterisitcis WC PDS BOM PPM iPPE Change master recoed Purchase info record Setip matrix Qoute Arrangement Shipping point Product allocations DP SNP x x x x x PP/DS x x x x x1 x x x x x3 x x4 x5 x x2 x2,6 x8 GATP x x TPVS x x x x x Service parts planning Event mgmt SPP IP(Maintain SNC and service EMplanning) EWM x x x x x x x x x x x x x x x10 x x x

x x9

x x x

x x

x x x

x x7

x x2,6 x8

x x

1 Batch is used in PPDs as a limited,relesas dependandnt and indusrty specific 2 Setip matrix is not a CIF objects 3 BOM is only used for transferring phantom assembilies 4 IPPE is only industry specific(automative) 5 Chane of master data can be included in planning with PDS 6 QouteArrangement can be included in the source determinations 7 BOM is exploded in Multilevel ATP 8 Production allocation is used only in forecasting. 9 Material master:no core interface is required for demand planning.A check is made when releasing the results of DP,for Ex to SN 10 Extended ware house mgmt: Specific data can be entered in ECC transferred via CIF