© 2009 Wipro Ltd - Confidential1

ObjectiveSAP APO CIF Training

By Veeram Satish Reddy

© 2009 Wipro Ltd - Confidential2

Today’s Session

• CIF Overview• Integration Model Setup• Overview of Master Data• Overview of Transactional data• Transferring of Master Data and Transactional Data• Internal and External Data Inconsistencies in APO• Debug CIF and CIF logs• Error Handling While Transfer from both ways from APO to

R/3 and R/3 to APO

3

CIF Overview

44

Integrating APO With SAP R/3: Overview

55

R/3 Plug-In Details

66

R/3 - APO Integration Is Enabled by the Core Interface (CIF)

77

Integrating APO with R/3 – The Big Picture

8

Integration Model Setup

99

CIF Integration Model

1010

Key Steps to Configure the CIF

1111

Technical Integration Settings in R/3 and APO

1212

Configuring the Integration Between APO and R/3

1313

Integration Model

1414

Creation of Integration Model(CFM1 transaction)

1515

Creation of Integration Model (cont.)

To create

1616

Integration Models: Activation

1717

Activation of Integration Model

1818

Activation of Integration Model (CFM 2)

1919

Broad Classification of Data Objects Transferred via CIF

20

Overview of Master Data

2121

Master data changes

2222

• Location - /SAPAPO/LOC3 • Plants (Manufacturing / DC), Vendors, Customers, MRP Areas

in R/3 all map to Location master in APO differentiated by Location Type (1001, 1002, 1011, 1010, 1007)

• Product - /SAPAPO/MAT1 • Material in R/3 is mapped to Product in APO. Has multiple tabs

similar to that in R/3. Many field values come from R/3 while APO-specific field values are either manually populated or automatically during CIF transfer from R/3 to APO

• Resource - /SAPAPO/RES01 • Work Center (or Capacity) in R/3 defines the machine or

equipment used for Production, Storage or Transportation

About Master data

2323

• PDS - /SAPAPO/CURTO_SIMU • Combination of Bill-of-Material and Routing in R/3

(Production Version). Used for In-house Produced Products to determine components and resource (capacity and time) requirements

• Transportation Lane - /SAPAPO/SCC_TL3 • Purchasing Info records and Contracts in R/3 map to

Transportation Lanes in APO that define from where - to where products can be moved and the transportation duration

• Procurement Relationship - /SAPAPO/PWBSRC1 • Displays Contracts, Purchasing Info records and Scheduling

Agreements coming from R/3

Continue…

2424

Locations with location types

2525

New Material transfer

2626

Lot sizing procedure

2727

Lot sizing procedure

2828

Period lot size

2929

Resource

3030

Resources

3131

Resource capacity

3232

Production Process Model

3333

Scheduling time

3434

Activity relationships

3535

Production Process Model (PPM) – BOM and Routing

3636

External procurement relationships

37

Overview of Transactional data

3838

Transfer of transactional data

39

Internal and External Data Inconsistencies in APO

4040

Two Types of Inconsistencies in APO

4141

How to Identify and Fix Consistency Errors

4242

• Planned Order Manufacturing Order created in APO resulting from Production

Planning run for In-house Produced Product.• Production Order Planned Order is converted to a Production Order in R/3 which is

then executed up (actual production carried out).• Purchase Requisition / STR Planned requisition resulting from Production Planning run for an

Externally Procured Product .• Purchase Order / STO Requisition is converted to a firmed Order in R/3 for subsequent

execution.• Independent Requirement / Demand Requirement for a finished product coming from customer. This

may not be the firm demand but just a plan.

Transactional data

4343

• Sales Order Firm demand from customer with a confirmed requirement

date and quantity.• Stock Quantity of product available at a location either after

production or procurement.

Continue…

44

 Debug CIF and CIF logs

4545

CIF Debugging for STO’s from APO posted to the R3 SOS as PO

• Activate CIF debugging for all outbound queues in APO. • Go to transaction /SAPAPO/C4 and make an entry for your

user. Make sure your logon carries all relevant authorizations. This ensures that every queue object created gets blocked in the outbound port.

4646

Continue…

• STO is created in APO. To send it to R/3, click on “send to OLTP” directly. • Go to APO queue manager (/SAPAPO/CQ) and notice that an outbound queue is waiting to be processed.

4747

Continue…

Click on the “SMQ1/SMQ2” button and it takes you to R/3 SOS (RD7) inbound queue.

4848

Continue…

Double click on the queue; you go to the details of the function module called.

4949

Continue…

Select the function module and click on debug. You will taken to the debugger on R/3 side. From there, you need to debug till the creation of PO in R/3.

5050

Continue..

5151

The following modules/routines are called in the below sequence :

• CIF_PO_INBOUND • ME_APO_GENERATE_REQ_PO • Perform po_create • ME_CREATE_PO_ITEM • PERFORM neue_pos_bestellung(sapmm06e) • PERFORM ptv_fuellen_allgemein USING space. • PERFORM ptv_fuellen USING im_activity

Continue…

52

Error Handling While Transfer from both ways from APO to R/3 and R/3 to APO

5353

Error Handling

5454

• Communication errors: This includes network problems, a non-existing RFC

destination, and so on. Since the data transfer is repeated after certain periods, most of these communication errors should disappear once the network connection is available again.

• Application error: This includes program errors, non-posting of data in the

target system etc. Application errors cannot be solved by the system independently and must be processed by the system administrator.

Error Handling cont…

5555

QRFC error detection

5656

SCM Queue manager

5757

Reconciliation of transactional data (/SAPAPO/CCR report)

© 2009 Wipro Ltd - Confidential

Thank You