Technical Details for SNC

Implementation

Applies to:
SNC7.0

Summary
The Tutorial helps SNC beginner with no prior SNC knowledge to configure SNC for handling integration
data like master data from CIF and troubleshooting transactional data from PI. This would also be a good to
know document for Functional team who would like to have more control on technical aspects of SNC
proxies.
Author:

Dipali Rajput

Company: IBM
st

Created on: 1 October 2010

Author Bio
Dipali Rajput is a Senior Consultant in Netweaver development and Integration division of IBM .
She has 5 years of SNC PI integration experience. She has experience in ICH5.0, SNC5.1 and
SNC 7.0 integration. She has been involved in both SAP and Non SAP integration with PI for
SNC. She has Overall 8 years of Integration experience in SAP integration with PI, ALE, ABAP,
Java, XSLT, xCBL, SNC, SRM.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

1

Technical Details for SNC Implementation

Table of Contents
Introduction: ........................................................................................................................................................ 3
Pre-requisite in SNC: ...................................................................................................................................... 3
In ICH5.0 : Following BAdis were implemented ............................................................................................. 4
In SNC5.1 ........................................................................................................................................................ 4
In SNC7.0: ....................................................................................................................................................... 4
Implementation Procedure: ............................................................................................................................. 5
StandAlone Proxy Testing in SNC: ............................................................................................................... 11
Related Content ................................................................................................................................................ 17
Disclaimer and Liability Notice .......................................................................................................................... 18

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

2

Technical Details for SNC Implementation

Introduction:
The Sub-Contracting SAP Solution leverages the SAP SNC (previously known as ICH) application to
collaborate with suppliers on Purchase Orders. As part of this solution certain interfaces between the ECC
and SCM server are required to be activated. These interfaces are for both Master Data and Transactional
Data.
For Sub-Contracting we need to sync the following Master Data objects:
Vendor Masters
Material Masters
Plants (locations)
Purchasing Info Records
Schedule Agreements

In order to leverage the SAP SNC processes master data need to be replicated onto the SCM server so the
SNC application can provide the information to the Suppliers.

Although, this data does not change often, it should be sync near real time. SAP provide a way to configure
the ECC to transmit this data upon updates using the CIF process. The CIF depend on Integration Models to
identify the data content (which rows) to CIF over. The CIF process can be used to send over various
master data elements based on the selections.
When using SAP SNC XML-interfaces, an external application must handle the internal format of the master
data keys (location, product and partner) in the SCM system. In absence of doing so the system fails the
message with following error location ID key missing or product location key missing.

Pre-requisite in SNC:
To enable any scenario in SNC we need to implement few BAdis for Data conversion. These Badis can be
used to manipulate data coming in SNC.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

3

Technical Details for SNC Implementation

In ICH5.0 : Following BAdis were implemented

/SCMB/BIF_ME_LOCID
/SCMB/BIF_ME_PARTYID
/SCMB/BIF_MI_ITMBPRT
/SCMB/BIF_MI_LOCID
/SCMB/BIF_MI_PARTYID
/SCMB/BIF_MI_PRODID

In SNC5.1
You can implement these BAdis in compatible mode
Following are the list of BAdis to be implemented in SNC before initiating data transfer in and out of the
system.
- /SCA/BIF_ME_LOCID
- /SCA/BIF_ME_PARTYID
- /SCA/BIF_ME_PROD_ID
- /SCA/BIF_MI_ITMBPRT
- /SCA/BIF_MI_LOCID
- /SCA/BIF_MI_PARTYID
- /SCA/BIF_MI_PRODID

In SNC7.0:
General Master Data Integration is done using Enhancement spot

Note: You need a developer key to perform this task

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

4

Technical Details for SNC Implementation

Implementation Procedure:
To implement Enhancement spot: Lets look at /SCA/BIF_ME_LOCID
Go to SE19

Select New BAdi Enhancement Spot : provide the name of Enhancement Spot to be implementated
/SCA/BIF_ME_LOCID for Location ID.
Click create Implementation

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

5

Technical Details for SNC Implementation

Provide Implemetatio name as per naming convention guidelines. Here I have given
ZSCABIF_ME_LOCID
Provide short text for description .
You will be asked for package and request number to create transport.

After assigning Package and Request to the implementation to need to provide names for BADI
implementation and Implementation class.
Then select BADI definition from the drop down.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

6

Technical Details for SNC Implementation

Then an option is provided whether you want to use standard sample code or you want to create empty class
for custom modification. Based on your requirement you can select either Empty Class or Copy Sample
class. In standard SNC implementation Copy Sample class is used.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

7

Technical Details for SNC Implementation

After this step Implementation class is created.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

8

Technical Details for SNC Implementation

To view and activate implementation code

Double click on implementation class :

Click on Code

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

9

Technical Details for SNC Implementation

Activate.
Any custom changes to master data can be added here if required like length and leading zeros. You can
implement complex master data manipulation scenarios also.
Once all the master data is uploaded in the system. You need to activate proxies in SNC to enable data
integration with PI.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

10

Technical Details for SNC Implementation

StandAlone Proxy Testing in SNC:

During all my SNC implementation I had a common question asked by SNC Functional team how do we
know what is wrong with the message posting in SNC. Is there anyway to test the SNC proxy offline rather
than end to end test for transactional data? Since sending data for testing needs co-ordination between ECC
/ PI and SNC team. There were always queries to simply SNC testing.
Transactional data in SNC can be tested without connecting PI. In cases where PI system or configuration is
still in completion process SNC configuration can be tested for external data using following method. This
approach is also helpful if there are any custom proxies to be built in SNC for Non-standard impelementation.
For our understanding we will use ReplenishmentOrderNotification_In.
In SNC check if SLD Connection is working fine using SLCHECK t-code
If there are any errors like this screenshot please contact Basis team

When Connectivity is good SLDCHECK all the checks in the screen will be green.
Next Go to t-code SPROXY
Select namespace : http://sap.com/xi/SNC/Global

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

11

Technical Details for SNC Implementation

Select ReplenishmentOrderNotification_In for testing inbound messages coming from PI.

Click test button

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

12

Technical Details for SNC Implementation

If you want the entire Template for ReplenishmentOrderNotification_In select Generate Template Data. In
case you just want to know only the mandatory fields for testing then you can use Generate Initial Template

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

13

Technical Details for SNC Implementation

Click Execute or F8.

To Edit default message click on XML Editor

Here you can either manually edit each line or upload an existing xml data from a file using load file. To
download this file use Save File option.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

14

Technical Details for SNC Implementation

Once all needed data is provided in the Editor . Execute or F8

In case you have any errors it will be shown as below

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

15

Technical Details for SNC Implementation

Or

Click on log for details.

Else you should see Call Successfully at the bottom.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

16

Technical Details for SNC Implementation

Related Content
BADI implementations SAP ICH 5.0 <--> SAP ERP integration
SAP Community Network Forums SAP Solutions SCM APO Master Data and General
SAP Community Network Forums SAP NetWeaver Process Integration

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

17

Technical Details for SNC Implementation

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not
supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.
SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,
and anyone using these methods does so at his/her own risk.
SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or
code sample, including any liability resulting from incompatibility between the content within this document and the materials and
services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this
document.

SAP COMMUNITY NETWORK

2010 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com

18