CIF Customisation

Shriram Pistons & Rings Limited
SAP Project
mySAP IMPLEMENTATION PROJECT

SCM 5.0
CUSTOMIZATION DOCUMENT
Core Interface
Customization Document Page 1 of 89 Confidential Document

Customization Document
Core Interface Advance

Planner and Optimizer
Prepared by:
Siemens Information Systems Ltd RAJAN SAGOO

PPDS Consultant SISL
Project Team
Date of Preparation:
____________ __________________________ ________________________
Sign Off Date Signature: Project Team Signature: Consultant(s)

Shriram Pistons & Rings Ltd Siemens Information Systems Ltd.

Module SCM Core Interface
Process/ Sub Overview
Process
Table of Contents
1. Introduction________________________________________________________________5
2. Business Configuration_______________________________________________________6
3. Configuration_______________________________________________________________7
3.1 Core Interface Basic settings_______________________________________________7
3.1.1 Setting up Client__________________________________________________________7
3.1.2 Assign Logical system to Client_______________________________________________9
3.1.3 Specify SAP APO Release__________________________________________________11
3.1.4 Set up RFC Definition_____________________________________________________13
3.1.5 Set Target system and queue Type____________________________________________17
4. Basic setting for the Data Transfer_____________________________________________19
4.1 Set User Parameter_________________________________________________________19
4.2 Change Transfers__________________________________________________________21
4.2.1 Change Transfer for Master Data____________________________________________21
4.2.2 Activate ALE Change pointers generally______________________________________23
4.2.3 Activate online Transfer Using BTE_________________________________________25
4.3 Activating the CIF Application Log____________________________________________27
5. Configuring APO___________________________________________________________29
5.1 Basic setting for creating the System Landscape_________________________________29
5.1.1 Name of the Logical System________________________________________________29
5.1.2 Assign Logical System to a Client____________________________________________30
5.1.3 Set up RFC Destination____________________________________________________32
5.1.4 Maintain Business system Group____________________________________________36
5.1.5 Assign Logical system and Queue Type_______________________________________38
5.2 Basic setting for Data Transfer_______________________________________________40

5.2.1 Set User Parameter_______________________________________________________40
5.2.2 Publication______________________________________________________________42
5.3 Preliminary steps__________________________________________________________44
5.3.1 Activating the customizing Import from SAP R/3 (SAP SCM)_____________________44
5.3.2 Maintaining Units of Measurement__________________________________________46
5.3.3 Defining the Transportation group___________________________________________48
5.3.4 User setting and activating the CIF Application Log_____________________________50
6. Integration In SAP SCM (Master Data And Transactional Data)_____________________52
6.1 Generation and Activation of Integration Models_________________________________52
6.2 Checking result and creating Variants__________________________________________55
6.3 Details of Configuration/changes: Activating the Integration Model_________________58
6.4 Changing Integration Model_________________________________________________61
6.5 Activating the changed Integration Model______________________________________63
7. Master Data________________________________________________________________64
7.1 Master Data Plant__________________________________________________________64
7.2 Master Data (Material Master)_______________________________________________67
8. Transaction Data___________________________________________________________72
8.1 Transactional Data Purchase Requisition_______________________________________72
8.2 Transaction Data for Planned Order___________________________________________74
8.3 Transactional Data for Stocks________________________________________________76
8.4 Transaction Data for In-Transit Stock_________________________________________78
8.5 Transactional Data for Production Order_______________________________________80
8.6 Transactional Data for Sales Order____________________________________________82

Module Supply Chain Management
Process/ Sub
Process 1. Introduction
Sr. Topics
No
1.1 Scope of the Document
This document contains the configuration details maintained for Shriram Piston &
Rings Ltd. for logistics ad business working of the Core Interface Module in SAP APO
5.0
1.2 Document Objectives

The objective of this document is to provide important configuration details of the
Core Interface Module to enable the application system administrator(s) / authorized
users in maintaining the system. Neither this documentation nor any part of it may be
copied or reproduced in any form or by any means or translated into another language,
without the prior consent of Siemens Information Systems Limited.
1.3 Document Structure

This document is broadly about the configuration details.
1.4 Target Audience

This document is meant for the application system administrators, who are responsible
for maintaining the Supply Chain Planning Interface. It may be noted that the
document is consistent with the system settings on the date of document (date on the
title page). It is the responsibility of the application system administrators to keep this
document updated and consistent with any further configuration done.

Process/ Sub
Process 2. Business Configuration
Sr. Topics
No
2.1 Document Objectives
This section describes:
The configuration settings that you need to make in SAP ECC and SAP SCM systems.

Mas
3. Configuration
3.1 Core Interface Basic settings
3.1.1 Setting up Client

Sr. No Topics
3.1.1.1 Explanation
To enable the transfer of data via APO Core Interface (CIF), you need to name both the
ERP system in which you are working and the SAP APO system to which you want to
transfer data as logical systems.
Note that you also have to carry out these steps in SAP APO. The names of the logical
systems need to correspond in the ERP system and in SAP APO (that is, the name that
is defined for SAP APO in SAP APO must be specified as the logical target system in
the ERP system, and the name defined for ERP in the ERP system must be specified as
the logical target system in SAP APO).
3.1.1.2 Customization Path

Implementation Guide for R/3 Customizing Integration with other mySAP
Component Advance Planning and Optimization Basic settings for setting Up the
system Landscape Name Logical System
Transaction code for above menu path: SPRO
3.1.1.3 Details of Configuration/changes:

In this step, you can define the logical systems in your distributed system.

Mas
3. Configuration
3.1.2 Assign Logical system to Client

Sr. No Topics
3.1.2.1 Explanation
These settings cannot be transported. When a new system is being set up, these settings
must be made after the system installation has been completed.
You also have to carry out these steps in SAP APO. The names of the logical systems
need to correspond in the ERP system and in SAP APO (that is, the name that is
defined for SAP APO in SAP APO must be specified as the logical target system in the
ERP system, and the name defined for ERP in the ERP system must be specified as the
logical target system in SAP APO).

system Landscape Assign Logical system to Client

In this work step, you assign a client to each logical system.

Mas
3. Configuration
3.1.3 Specify SAP APO Release

Sr. No Topics
3.1.3.1 Explanation
The setting(s) that you make in this IMG activity are dependent upon the target system
concerned. For this reason, there is no transport to the production system. As a result,
you need to also make the settings for the relevant target system in the production
system.

system Landscape Specify SAP APO Release

In this IMG activity, you specify the release level of the SAP APO system that is
defined as the target system.

2.1.3 Maintain Settings at Plant Level

Mas
3. Configuration
3.1.4 Set up RFC Definition

Sr. No Topics
3.1.4.1 Explanation
Before two or more systems can communicate with each other, the technical coupling
between them must be set up. The target address for the data transfer is determined
during the set-up of an RFC destination in SAP R/3. The name of the corresponding
RFC destination must be identical to the name of the logical target system (SAP APO).
One RFC destination is required for each target client (for example, 001).

system Landscape Setup RFC Definition
Transaction code for above menu path: SM59

In this IMG activity, you create the connection to SAP APO. The name of the RFC
destination has to match exactly the name of the logical target system that was already
specified.
1. Open the ABAP Connection node.

2. Choose Create. The RFC Destination screen is displayed
3. Enter the following:
a) RFC Destination: Enter the name of the logical target sys specified in the IMG
activity Name Logical Systems.
b) Connection Type: Use the input help to choose the relevant connection type. In
most cases, choose connection type 3.
c) Enter a description.
4. Enter the following information on the Logon/Security tab page:
a) Under Logon, define the security options.
b) Language: Optional.
c) Client: Use the input help to select the relevant client. The client to be
configured depends on the current authorization profile of the user
d) User: User-defined. The user entered here must also be created in the target
system (SAP APO) with the corresponding authorization profile. If you want
to perform cross-system debugging, the relevant user must be created in the
target system as a dialog user with debugging authorization.
e) Password: User-defined: Default setting at delivery: initial.

2.2.1.2 Define Keys for Certificate Processing
IMG transaction Menu path:

Mas
3. Configuration
3.1.5 Set Target system and queue Type

Sr. No Topics
3.1.5.1 Explanation
To enable communication between SAP R/3 and SAP APO, the relevant target system
for this connection must be installed in addition to the definition of the RFC
destination. You install a valid operation mode at the same time.
You assign a queue type to the connection to the selected system. The queue type
Outbound Queue is set by default.

system Landscape Set Target System and Queue type

In this IMG activity, you add the target system that you have already defined to the
definition of the RFC destination for the Transfer. The data transfer using the APO core
interface is made with Queued remote function call (qRFC) technology. This means
that the data is stored temporarily in queues. The Queue type (Inbound and Outbound)
determine whether queue Processing is controlled by sending or receiving system. In
this step you can set the queue type for the target system specified

Mas
4. Basic setting for the Data Transfer
4.1 Set User Parameter

Sr. Topics
No
4.1.1 Explanation
Enter the user name specified in the user master. Use input help to make the relevant
settings for this user.
4.1.2 Customization Path

Component Advance Planning and Optimization Basic Setting for Data transfer
Set User parameter
4.1.3 Details of Configuration/changes:

In this IMG activity, you can make user-specific
Entries for the following parameter.
RFC Mode (Activate/Deactivate transfer on a User Specific basis)
Logging (Configure application Log on a user specific basis)
Debug (Activate/Deactivate debugging on User-Specific basis)

Mas
4.2 Change Transfers
4.2.1 Change Transfer for Master Data

Sr. No Topics
4.2.1.1 Explanation
The change transfer for master data is concerned with:
Creating new master data whose selection criteria match those of an active integration
model and the subsequent transfer to SAP APO.
Making changes to master data and transferring these to SAP APO

Component Advance Planning and Optimization Basic Setting for the Data
transfer Change Transfer Change transfer for master Data Configure change
transfer for master Data
Transaction code for above menu path: CFC9

In this IMG activity, you set how changes to the master data are transferred to SAP
APO. If you do not make setting here, Master data changes are not transferred to SAP
APO.
You have three options:
The System dose not transfer changes
The system Transfers the changes Periodically using ALE Change Pointers
The System Transfers the changes to SAPAPO Immediately (Online Transfer)
Using Business transaction events (BTE)

Mas
4.2.2 Activate ALE Change pointers generally

Sr. No Topics
4.2.2.1 Explanation
If you change these master data objects in SAP R/3, the system will write a note. These
notes are called ALE change pointers (ALE = Application Link Enabling). Here,
message type CIFMAT stands for material, CIFCUS for customer, CIFVEN for vendor
and CIFSRC for source of supply.

transfer Change Transfer Change transfer for master Data Activate ALE
change Pointers generally

In this IMG activity. You fulfil the perquisite for transferring changes to master data
change Pointers.

Mas
4.2.3 Activate Online Transfer Using BTE

Sr. No Topics
4.2.3.1 Explanation
For transaction data, there is a smooth transition between the initial transfer (supply) of
data and the transfer of data changes. As soon as the integration model is activated, the
SAP R/3 system switches from the initial supply of data to the transfer of data changes.
If you create, change or delete a document relevant to SAP APO, the system
immediately transfers this change to SAP APO (online transfer).
To allow online transfer and enable the immediate transfer of changes to transaction
data from SAP R/3 to SAP APO, you have to activate generally the Business
Transaction Events (BTEs) in SAP R/3 for integration with SAP APO.
transfer Change Transfer Change transfer for Transaction Data Activate
online Transfer Using BTE

In this IMG activity, you activate BTE for the Integration with SAPAPO and so fulfil
the prerequisite for the on line transfer of both transaction data changes and In
exceptional cases- master data Changes.

Activities
Set the ND-APO (New Dimension Plug-In APO) and NDI (New Dimension
Integration) Application indicator to active.

Mas
4.3 Activating the CIF Application Log

Sr. No Topics
4.3.1 Explanation
Every transfer between SAP APO and SAP R/3 can be logged in a user-specific way.
You can choose between two different settings for logging:
No logging
Standard (only the number of transferred data records are logged)
Detailed (number and content of the transferred data records are logged)

Implementation Guide for APO Customizing Integration with SAP Component
Advance Planning and Optimization Basic setting for the Data transfer Set User
Parameters.
Transaction code for above menu path: CFC2

By activating the CIF application log, you can analyse the error that occur during the
data transfer. The log will provide you with the information such as who and when
transferred what data from R/3 to SCM

Mas
5. Configuration in APO
5.1 Basic setting for creating the System Landscape
5.1.1 Name of the Logical System

Sr. No Topics
5.1.1.1 Explanation
System in which applications run integrated on a shared data basis.
The distribution of data between systems requires that each system in the network have
a unique identification. The logical system is used for this purpose.
In the SAP System the client corresponds to a logical system. You can assign a logical
system to a client in the client maintenance (choose Goto -> Detail).
The logical system is relevant in the following SAP areas:

ALE general: two or more logical systems communicate with one another.
ALE - ALE business processes (for example, cost center accounting): definition of
a system where a specific application runs. Changes to master data can only be
made in this system, for example.
Workflow objects: the logical system in which the object is located is always
included in an object's key.
When maintaining the logical system, note the following:

The logical system must be unique company-wide. It must not be used by any
other system in the ALE integrated group. In a production system, the logical
system must not be changed. If the logical system of a document reference is not
set to initial and does not match your own, the system assumes the document is
located in a different system.

Intigration Via Core Interface (CIF) Basic Setting for Creating the system
Landscape Name of the Logical system

In this step, You define the logical system in your distributed system.

Mas
5. Configuring APO
5.1.2 Assign Logical System to a Client

Sr. No Topics
5.1.2.1 Explanation
CIF Customizing in SAP APO is used to set up the system infrastructure and to
configure the data transfer between SAP Advanced Planning and Optimization (SAP
APO) and the ERP system via SAP APO Core Interface (CIF). CIF Customizing also
covers application-specific settings and enhancements for CIF.
An Implementation Guide (IMG) is available for CIF Customizing. The IMG provides
you with a clear overview and explanation of all steps that are necessary for integration
via CIF. With the exception of organizational IMG activities that only contain a
description, you can go directly to the relevant transaction and execute the action.

Landscape Assign Logical System to a client


In this work step, you assign a Client to each logical system.

Mas
5. Configuring APO
5.1.3 Set up RFC Destination

Sr. No Topics
5.1.3.1 Explanation
Before two or more systems can communicate with each other, the technical coupling
between them must be set up. The target address for the data transfer is determined
during the set up of an RFC destination in SAP R/3. The name of the corresponding
RFC destination must be identical to the name of the logical target system (SAP APO).
One RFC destination is required for each target client.

Landscape Set Up RFC Destination

In this IMG activity, you create the connection to SAP APO. The name of the RFC
destination has to match exactly the name of the logical target system that was already
specified.
Activities
1. Open the ABAP Connection node
2. Choose Create. The RFC Destination screen is displayed.
3. Enter the following:
a) RFC Destination: Enter the name of the logical target sys specified in
the IMG activity Name Logical Systems.
b) Connection Type: Use the input help to choose the relevant connection
type. In most cases, choose connection type 3.
c) Enter a description.
4. Enter the following information on the Logon/Security tab page:
a) Under Logon, define the security options.
b) Language: Optional
c) Client: Use the input help to select the relevant client. The client to be
configured depends on the current authorization profile of the user.
d) User: User-defined. The user entered here must also be created in the
target system (SAP APO) with the corresponding authorization
profile. If you want to perform cross-system debugging, the relevant
user must be created in the target system as a dialog user with
debugging authorization.
e) Password: User-defined.

Mas
5. Configuring APO
5.1.4 Maintain Business system Group

Sr. No Topics
5.1.4.1 Explanation
If data from different logical systems is to reference the same objects in SAP APO (for
example, because you work with multiple ERP systems and one SAP APO), two
prerequisites must be met.
1. Define a business system group (BSG). This step is always necessary. The BSG

integrates different physical systems into a superordinate logical unit.
2. Set up mapping structures, in other words, maintain/activate user enhancements.
3.
Integration Via Core Interface (CIF) Basic Setting for Creating the system
Landscape Maintain Business System group

In this IMG activity, you determine the assignment to the business system group of
APO system and R/3 system to be connected. By doing this, you create areas with the
same Naming Conventions. These Guarantee that the same names are used for master
data, and also there Synchronization in distributed system landscape.

Mas
5. Configuring APO
5.1.5 Assign Logical system and Queue Type

Sr. No Topics
5.1.5.1 Explanation
To enable error-free communication with SAP APO, each source system (SAP R/3)
must be assigned to a business system group (BSG). A BSG can consist of one or more
source systems.

Integration Via Core Interface (CIF) Basic Setting for Creating the system
Landscape Assign Logical system and Queue Type

In this IMG activity assign logical, you assign a logical system to business system
group (BSG). Additionally, you assign a queue Type (Inbound queue or Outbound
queue) to the BSG.

Mas
5. Configuring APO
5.2 Basic setting for Data Transfer
5.2.1 Set User Parameter

Sr. No Topics
5.2.1.1 Explanation
Enter the user name as specified in the user master. Use the field and input help to
make the relevant settings for this user.

Integration Via Core Interface (CIF) Basic Setting for data Transfer Set User
Parameter

In this IMG Activity, you can make user Specific Entries for the following parameter:
Logging (Configure application Log on A user Specific basis)
Debugging (Activate/Deactivate, debugging On A user specific basis)
Recording (Control event recording, That is, publication of Planning result)

Mas
5. Configuring APO
5.2 Basic setting for Data Transfer
5.2.2 Publication
Sr. No Topics
5.2.2.1 Explanation
The data generated or changed by SAP APO in Supply Network Planning (SNP) or
Production Planning and Detailed Scheduling (PP/DS) is transferred to SAP R/3. This
operation is called the publication of planning results. There are two types or
publication in SAP APO: Direct publication and periodic publication.
For all objects that have been generated in SAP APO and are now to be transferred to
SAP R/3, the distribution definitions for the relevant publication type must have been
defined. Distribution definitions do not necessarily have to be defined for objects that
have only been changed in SAP APO.

Integration Via Core Interface (CIF) Basic Setting for data Transfer Publication
Maintain Distribution Definition

You use this IMG activity to define the distribution of SAP APO Planning result to the
relevant logical System.
You must define the distribution for the following Object.

External procurement
Schedule Lines for scheduling agreement item
In-House Production
Production campaign

Sales Order
Reservations
If you do not define a distribution definition, the system does not transfer any data.

Mas
5. Configuring APO
5.3 Preliminary steps
5.3.1 Activating the customizing Import from SAP

R/3 (SAP SCM)
Sr. No Topics
5.3.1.1 Explanation
In this IMG activity, you maintain the global settings for the availability check. These
include:
Import Customizing data using the CIF integration model in the
connected OLTP system: allowed/not allowed.
Define bucket parameters

Implementation Guide for APO Customizing Advance Planning and optimisation
Global Available-to-Promise (Global ATP) General Settings Maintain Global
setting for Availability Check

The purpose of this activity is to activate the setting in SAP SCM that allow
customizing to be imported from SAP R/3 to SAP SCM.
The Customizing import from R/3 to SAP SCM is selected in the integration
Model in the section material independent Object.

Mas
5. Configuring APO
5.3.2 Maintaining Units of Measurement

Sr. No Topics
5.3.2.1 Explanation
In applications you often have to make calculations with quantities and physical units.
Units of measurement are needed for their screen display and for internal conversions
(such as kilogram <-> gram, but also centimetre <-> inch). The international system of
units (SI) is used for this.
The international system of units is based on seven basic units of measurement. All
other units are derived from these basic units. Units of measurement that measure the
same quantity (and can therefore be converted into each other) are included in a
dimension.
Units of measurement are held centrally in the SAP System for all applications. The
conversion factors are stored in the system with a unique internal key. The external
display specifications are maintained for each unit of measurement language-
dependently. A business key (3 characters) and a technical key (6 characters) should be
maintained for each language.

Implementation Guide for APO Customizing General Setting Check Unit of

Measurement.
Transaction code for above menu path: CUNI

Carry out this activity only if the SAP R/3 data, which has to be transferred to SAP
SCM, requires additional unit of measure that are not included in SAP standard. If you
have defined additional unit of measure in your SAP R/3 System you need to define
these in SAP SCM as well.

Mas
5. Configuring APO
5.3.3 Defining the Transportation group

Sr. No Topics
5.3.3.1 Explanation
Groups products with the same transportation requirements.
Example
You sell foodstuffs. If you want to transport food that spoils easily and that must be
kept cool during transportation, you create a transportation group for products that have
to be transported in a refrigerated truck.

Implementation Guide for APO Customizing Advance Planning and Optimization
transportation Planning and Vehicle scheduling basic setting Maintain
Transportation Group.

The assignment of a transportation group to a material is transferred to SAP SCM via

CIF with the material master. The customizing for defining the transportation groups,
however, is not transferred. Therefore, you need to create all relevant transportation
groups in SAP SCM customizing before starting data replication.

Mas
5. Configuring APO
5.3.4 User setting and activating the CIF Application

Log
Sr. No Topics
5.3.4.1 Explanation
Enter the user name specified in the user master. Use input help to make the relevant
settings for this user. Every transfer between SAP APO and SAP R/3 can be logged in a
user-specific way. You can choose between two different settings for logging:
No logging
Standard (only the number of transferred data records are logged)
Detailed (number and content of the transferred data records are logged)

Advanced Planning and Optimization APO Administration Integration
Settings User Settings.

Transaction code for above menu path: /N/SAPAPO/C4

With this step, you maintain some global parameters for the SAP SCM users. In
addition, you activate the CIF application log for these users. This enables you to
analyze errors occurring during data transfer, because error messages are stored in the
destination systems application log. You have already activated the CIF application log
in the R/3 system in the previous step.

Mas
6. Integration in SAP SCM (Master Data and
Transactional Data)
6.1 Generation and Activation of Integration Models

Sr. Topics
No
6.1.1 Explanation
The integration model controls the transfer of master data and transaction data. It is
generated in the SAP R/3 system and contains all data that is to be transferred from SAP
R/3 to SAP APO. It is uniquely identified by name and application.
All available master data and transaction data in SAP R/3 is not generally needed for
planning in SAP APO. When you generate an integration model, you specify which data
objects are to be selected from the total dataset in SAP R/3 for the transfer to SAP APO.
To create the integration model, first mark the object types (for example, material
masters) to be selected on the Create Integration Model selection screen. Next, you select
specific selection criteria (usually a material-plant combination) that further restrict the
object types you have already selected. If you have already selected Material Masters,
for example, you could now enter an MRP controller. In this way, you define what are
referred to as filter objects. Filter objects are used to select which data objects are
transferred to a specified SAP APO system. In the example, all material masters for a
particular MRP controller are selected.

Logistics Central Functions Supply Chain Planning Interface Core Interface
Advanced Planner and Optimizer Integration Model Create
Transaction code for above menu path: CFM1

In this activity, you define the range of master and transaction data to be transferred. We
recommend that you create different integration models for master and transaction this
does not only improve the performance, but also helps to identify any errors that may
occur during data transfer.
For each integration model, carry out all steps of the following two activities before you
create the next integration model:

Creating Integration Models
Saving Results and Creating Variants
As each scenario needs different integration models, the following section provides a
generic description of how to create integration models
Activities to be performed:
a) Access the activity using the transaction Code CFM1
b) The create Integration Model screen appears. It contain the three major section
Material dependent object
General Selection options for the material
Material Independent object
c) Specify the following Information
Model Name: Specify a unique name for integration Model
Logical System: specify the target logical system
APO Application: Specify the name of the SAP SCM application
d) Select all Material Dependent Objects as specified for the model in the scenario
installation guide. If there are no material-dependent objects for an integration
model, proceed with step f (material-independent objects).
e) In the General Selection Options for Materials screen area, you specify or define
ranges for the material dependent objects by using criteria, which are applicable
to all material dependent objects.
f) You can further restrict the selected material dependent objects by choosing the
yellow arrow button next to the object. The selection criteria will be applied in
addition to those defined in General Selection Option for Materials.
g) Specify or define ranges for the material independent objects by choosing the
yellow arrow button next to the objects. A dialog box is displayed. You can define
value ranges and selection criteria for the material independent objects you have
already selected.
Note: By definition, the section General Selection Option for Materials does
not apply to the material independent object.
If you make no restrictions to the material independent objects selected for the
integration model, the system automatically selects all objects for this object
type, for example, all customers in the system. This can lead to significant
performance problems during data transfer.
h) Do not save your entries for this integration model but go to the next activity to
check the consistency of the model and to create a variant.

Mas
Transactional Data)
6.2 Checking result and creating Variants

Sr. Topics
No
6.2.1 Explanation
The consistency check can be carried out at two different points in time:
The model to be generated is analysed when the integration model is generated
The check is carried out on active integration models when integration models are
activated. This includes integration models that are to be activated, but not those
integration models that are to be deactivated.
As a result of the check, a dialog box appears that displays a corresponding message.
Since the system does not save the selection options you make when creating an
integration model, you have to save the settings as a variant on the selection screen. By
working with variants you are able to reuse the settings you have saved whenever you
want. If you want to recreate an integration model at a later point in time, you can call up
the required variant by choosing the Select Variant symbol on the toolbar at the top of the
selection screen.


The Following Activities are to be performed for the Mentioned above
a) After you have defined the entire object that you want to include in the
integration model choose the execute button in the create integration Model
screen to Display the result list. On the Create Integration Model screen to display
the result list.
b) Navigate the detailed view for each filter object by clicking on it and choosing the
details. A list of information of the data object you have selected with the name of
your Model and the target system is displayed
c) Verify that only the required object are included in the integration Model and go
back
d) Choose the Consistency check to conduct a Consistency check of the integration

Model
As a result of the consistency check of the integration models for

transaction you may receive warning messages such as material is not included
in the integration model. You can ignore these messages if the material master
data has already been included in a previous model.
e) Save the selection

f) Confirm the Information Message Integration Model< Name of your
Model>generated for target system <Logical system name > and Application
<name of the Application>
g) Choose go back twice
h) In, should your Option Be saved as a Variant? Dialog Box, Choose Yes. It is
recommended that you create Variants because the system dose not saves the
selection Option you have made when creating an integration model. By working
with variant you are able to reuse the setting or change the Original integration
model at the late Point in time.
i) On The ABAP Variant Attributes screen, Enter a name and a description for
the variant and choose Save
j) Go back to the pervious activity (Create integration Model) to create the next
Integration Model if it is necessary.

Mas
Transactional Data)
6.3 Activating the Integration Model

Sr. Topics
No
6.3.1 Explanation
The activation of an integration model leads to an initial transfer of master data and
transaction data from SAP R/3 to SAP APO. Online transfer is released for transaction
data. As standard, the integration models to be activated are compared with the
integration models that are already active. In this way, the transfer restricts itself to
difference, in other words; only data for filter objects that are not contained in any active
integration models is transferred.
To retransfer all data records, you have to deactivate and then reactivate all active
integration models.
You can generate multiple integration models. However, only one version can be
activated for each model. You can activate and deactivate several integration models
simultaneously.

Integration models for master data and transaction data must remain active to enable
online transfer.

Advanced Planner and Optimizer Integration Model Activate

The Following Activities are to be performed for the Mentioned above
a) Access The Activity using one of the following Tcode CFM2

b) On The Activate and Deactivate Integration Model Screen, Make the Following
Entries
Enter the name of the integration Model Or Press F4
Logical And target System
APO Application
c) Choose Execute
d) To activate an integration model, double-click the creation date of the model you
want to activate. As an alternative, you can click the date and choose Set to
active/inactive from the application toolbar. A green checkmark before the
creation date of the model indicates that the integration model is active. To
deactivate an active model, double-click the date of the model or choose Set.
A red cross before the model indicates that the model is inactive.
e) To trigger the Data replication to the target system (SAP SCM) Choose
f) If the CIF Load Prompts appears asking you Should the interval Be created,
Choose Yes
g) If the Following Application Log Prompts appears, Choose
No, if You Do not want to Branch to the Application log
Yes, to Display the CIF Application log Including a list of the Object that

were transferred appears
h) Confirm the Information Message Activation or the deactivation of the selected

Models is Complete.

Mas
Transactional Data)
6.4 Changing Integration Model

Sr. Topics
No
6.4.1 Explanation
We recommend that you change an existing variant of the integration model, generate a
new version using transaction CFM1, and then delete the variant.


This activity describes how to change existing, already activated integration models.
Changes to integration models may be necessary, if you intend to plan additional
products or locations in SAP SCM
Activities to be performed for changing the Integration Model
a) Access the activity using the Transaction Code CFM1

b) On the Create integration Model Screen, choose Go to Variants Get Variant
from the Menu bar
c) Select the variants which corresponds to the integration model you want to
Change the setting for the integration models are displayed
d) Proceed with making the required changes or enhancement to the integration

model
e) Choose execute. A new Integration model is generated
f) Choose Save and go back.

g) On the ABAP: Save as Variant screen, decide if you want to overwrite the
existing variant or create a new one
h) Go Back

Mas
Transactional Data)
6.5 Activating the changed Integration Model

Sr. Topics
No
6.5.1 Explanation
To retransfer all data records, you have to deactivate and then reactivate all active
integration models.

Advanced Planner and Optimizer Integration Model Activate

The Following Activities have to be completed
a) Access the activity using the Above Mentioned T-Code

b) Enter a model name, a logical system and an APO application and choose
Execute
c) On the Activate or Deactivate Integration Model screen, a green check symbol

indicates the currently active integration model. The changed integration model
with the time and date of the change is displayed in the first row and is not active.
d) Double click the changed integration model. A green check symbol appears on its

left. At the same time, a red cross appears to the left of the old integration model
e) Choose Start. The changed integration model is activated and the old version of
this integration model is deactivated at the same time.
f) Go back.

Mas
7. Master Data
7.1 Master Data Plant

Sr. Topics
No
7.1.1 Explanation
You normally create and maintain master data in the execution system. In order that this
master data is available in the planning functions of SAP Advanced Planning and
Optimization (SAP APO), you must transfer the master data and any master data changes
to SAP APO. The data is transferred via the Core Interface (CIF). You can also use the
master data that is transferred in other SCM components such as Inventory Collaboration
Hub (ICH).
You transfer the data before starting to work with SAP APO so that the same planning
situation exists in both systems.

SAP Implementation guide Production Distribution Resource Planning (DRP)
Basic Setting Maintain assignment of the Node Type.

SAP R/3 does not differentiate between production plants and distribution centers. In
SAP SCM, however, the location type distinguishes these locations. Moreover, different
settings apply to them; for example, production is not possible in a distribution center.
For successful data transfer, you need to define which plants in SAP R/3 correspond to
production plants and which to distribution centers
The Following Activities have to be performed
a) Access the T-Code Using the Above Mentioned Path.

b) Choose The Activity Allocation of Node Type.
c) Assign the node type PL to Your production Plant and DC to Your

Distribution Centre
d) Choose save.
Integration Models For the Plant
MODEL LOGICAL APO VARIEN VARIENT

NAME SYS APPLI. T NAME DESC.
SPRL_PLNT APOCLNT800 PLANT PLANT PLANT

Mas
7. Master Data
7.2 Master Data (Material Master)

Sr. Topics
No
7.2.1 Explanation
Materials are created as products in SAP APO when they are transferred via APO Core
Interface (CIF). The following contains information about integrating product master
data.

Logistic Material Management Material Master Material Create
Immediately.
Transaction code for above menu path: MM01

In this important step, you define which of your materials are to be planned in the SAP
SCM system and not in SAP R/3, which means they are excluded from planning in the
SAP R/3 system. To achieve this, you need to change the MRP type of the materials you
want to plan in SAP SCM. The MRP type X0 excludes materials from the MRP run in
SAP R/3. It is also used as a selection criterion for the integration model and the data
transfer.

7.2.4 Integration models for Material plant combination

The Variant name for the Material plant Combination for the Transaction CFM1
MODEL LOGICAL APO VARIENT

NAME SYSTEM APPLI. NAME VARIENT DISCRIPTION
SPRL_MAT APOCLNT800 P1000 P1000 Manufacturing Plant 1000 Gzb
SPRL_MAT APOCLNT800 P1101 P1101 Manufacturing Plant 1101 Gurgaon
SPRL_MAT APOCLNT800 T1102 T1102 OE Trade Gurgaon 1102
SPRL_MAT APOCLNT800 T1103 T1103 Trade Gurgaon 1103
SPRL_MAT APOCLNT800 P1104 P1104 Manufacturing Plant 1104 Sahibabad
SPRL_MAT APOCLNT800 NE1105 NE1105 Non Excisable 1105 Sahibabad
SPRL_MAT APOCLNT800 T1106 T1106 Trade Delhi 1106
SPRL_MAT APOCLNT800 T1107 T1107 Trade Gzb 1107
SPRL_MAT APOCLNT800 T1108 T1108 Trade Jaipur 1108
SPRL_MAT APOCLNT800 T1109 T1109 Trade jalandhar 1109
SPRL_MAT APOCLNT800 T1110 T1110 Trade Chandigarh 1110
SPRL_MAT APOCLNT800 T1151 T1151 Trade Kolkata 1151
SPRL_MAT APOCLNT800 T1152 T1152 Trade Patna 1152
SPRL_MAT APOCLNT800 T1153 T1153 Trade Guwahati 1153
SPRL_MAT APOCLNT800 P1154 P1154 Manufacturing Plant 1154 Jshm
SPRL_MAT APOCLNT800 T1165 T1165 Trade Bangalore 1165
SPRL_MAT APOCLNT800 T1166 T1166 Trade Chennai 1166
SPRL_MAT APOCLNT800 T1167 T1167 Trade Hyderbad 1167
SPRL_MAT APOCLNT800 T1168 T1168 Trade Cochin 1168
SPRL_MAT APOCLNT800 P1169 P1169 Manufacturing Plant 1169 Hosur
SPRL_MAT APOCLNT800 T1181 T1181 Trade Ahemdabad 1181
SPRL_MAT APOCLNT800 T1182 T1182 Trade Bhopal 1182
SPRL_MAT APOCLNT800 P1183 P1183 Manufacturing Plant 1183 Pune
SPRL_MAT APOCLNT800 T1184 T1184 Trade Pune 1184
SPRL_MAT APOCLNT800 P2000 P2000 Manufacturing Plant 2000 Gzb
SPRL_MAT APOCLNT800 T8000 T8000 Trade Port 8000
Variants for the Activation of the Integration Models Transaction Code CFM2

NAME SYSTEM APPLICATION NAME VARIENT DISCRIPTION
SPRL_MAT APOCLNT800 P1000 A_P1000 Manufacturing Plant 1000 Gzb
SPRL_MAT APOCLNT800 P1101 A_P1101 Manufacturing Plant 1101 Gurgaon

Mas
8. Transaction Data
8.1 Transactional Data Purchase Requisition

The Variants for the Purchase Requisition of Transaction CFM1

SPRL_PRPO SEPCLNT800 PR-PO1000 PR-PO1000 PR-PO Plant 1000
Variants for the Transaction CFM2

SPRL_PRPO SEPCLNT800 PR-PO1000 A_PR-PO1000 PR-PO Plant 1000
SPRL_PRPO SEPCLNT800 PR-PO1101 A_PR-PO1101 PR-PO Plant 1101

Mas
8. Transaction Data
8.2 Transaction Data for Planned Order

The Variants for the transaction CFM1

SPRL_PLO SEPCLNT800 PLO_1000 PLO_1000 Planned Order Plant 1000
Variants For the Transaction CFM2

SPRL_PLO SEPCLNT800 PLO_1000 A_PLO_1000 Planned Order Plant 1000
SPRL_PLO SEPCLNT800 PLO_1101 A_PLO_1101 Planned Order Plant 1101

Supply Chain Management
Module
Mas
8. Transaction Data
8.3 Transactional Data for Stocks

Variants for the transaction CFM1
MODEL LOGICAL APO
NAME SYSTEM APPLICATION VARIENT NAME VARIENT DISCRIPTION
SPRL_SLSTK APOCLNT800 SLSTK_1000 SLSTK_1000 Storage L Stock Plant 1000
Variants for the Transaction CFM2

MODEL LOGICAL APO
SPRL_SLSTK APOCLNT800 SLSTK_1000 A_SLSTK_1000 Storage L Stock Plant 1000

Mas
8. Transaction Data
8.4 Transaction Data for In-Transit Stock

The Variants for the transaction CFM1
MODEL LOGICAL APO
SPRL_INSTK APOCLNT800 INSTK_1000 INSTK_1000 In Transit Stock Plant 1000
The Variant for the Transaction CFM2
MODEL LOGICAL APO

SPRL_INSTK SEPCLNT800 INSTK_1000 A_INSTK_1000 In Transit Stock Plant 1000

Mas
8. Transaction Data
8.5 Transactional Data for Production Order

The Varient for the transaction CFM1
MODEL LOGICAL APO

SPRL_PROD SEPCLNT800 PROD_1000 PROD_1000 PROD Plant 1000
The Varient For the Transaction CFM2
MODEL LOGICAL APO

SPRL_PROD SEPCLNT800 PROD_1000 A_PROD_1000 PROD Plant 1000
SPRL_PROD SEPCLNT800 PROD_1101 A_PROD_1101 PROD Plant 1001

Mas
8. Transaction Data
8.6 Transactional Data for Sales Order

The Varient for transaction CFM1
MODEL LOGICAL APO

SPRL_SO SEPCLNT800 SO_1000 SO_1000 SO Plant 1000
The Varient For Transaction CFM2
MODEL LOGICAL APO A_VARIENT

SPRL_SO SEPCLNT800 SO_1000 A_SO_1000 SO Plant 1000
SPRL_SO SEPCLNT800 SO_1101 A_SO_1101 SO Plant 1001


CIF Customisation

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CIF Customisation

Uploaded by

Copyright:

Available Formats

Shriram Pistons & Rings Limited

mySAP IMPLEMENTATION PROJECT

Customization Document Page 1 of 89 Confidential Document

Core Interface Advance

Siemens Information Systems Ltd RAJAN SAGOO

Shriram Pistons & Rings Limited

____________ __________________________ ________________________

Sign Off Date Signature: Project Team Signature: Consultant(s)

Customization Document Page 2 of 89 Confidential Document

Customization Document Page 3 of 89 Confidential Document

Customization Document Page 4 of 89 Confidential Document

1.2 Document Objectives

1.3 Document Structure

1.4 Target Audience

Customization Document Page 5 of 89 Confidential Document

Customization Document Page 6 of 89 Confidential Document

3.1 Core Interface Basic settings

3.1.1 Setting up Client

3.1.1.2 Customization Path

Transaction code for above menu path: SPRO

3.1.1.3 Details of Configuration/changes:

Customization Document Page 7 of 89 Confidential Document

3.1.2 Assign Logical system to Client

3.1.2.2 Customization Path

Transaction code for above menu path: SPRO

3.1.2.3 Details of Configuration/changes:

Customization Document Page 9 of 89 Confidential Document

3.1.3 Specify SAP APO Release

3.1.3.2 Customization Path

Transaction code for above menu path: SPRO

3.1.3.3 Details of Configuration/changes:

Customization Document Page 11 of 89 Confidential Document

Customization Document Page 12 of 89 Confidential Document

3.1.4 Set up RFC Definition

3.1.4.2 Customization Path

Transaction code for above menu path: SM59

3.1.4.3 Details of Configuration/changes:

Customization Document Page 13 of 89 Confidential Document

Customization Document Page 14 of 89 Confidential Document

Customization Document Page 16 of 89 Confidential Document

3.1.5 Set Target system and queue Type

3.1.5.2 Customization Path

Transaction code for above menu path: SPRO

Customization Document Page 17 of 89 Confidential Document

Customization Document Page 18 of 89 Confidential Document

4.1 Set User Parameter

4.1.2 Customization Path

Transaction code for above menu path: SPRO

4.1.3 Details of Configuration/changes:

Customization Document Page 20 of 89 Confidential Document

4.2 Change Transfers

4.2.1 Change Transfer for Master Data

4.2.1.2 Customization Path

Transaction code for above menu path: CFC9

4.2.1.3 Details of Configuration/changes:

Customization Document Page 22 of 89 Confidential Document

4.2 Change Transfers

4.2.2 Activate ALE Change pointers generally

4.2.2.2 Customization Path

Transaction code for above menu path: SPRO

4.2.2.3 Details of Configuration/changes:

Customization Document Page 24 of 89 Confidential Document

4.2 Change Transfers

__________