Hi Experts/Friends,

  This is my first document in SNC and I am gonna share my rich experience with SNC,and I had done some end to end Implementations by Integrating SNC with PI and also I had gone through SDN threads and many of the peoples asked about SNC – PI Integration and still they didn’t got clarified in that.So I am taking the privilege to focus on the that particular area of Data Integration by managing the Master and Transactional data. In this document I am going to focus on the Basic settings to be done in the SNC side for Master Data  and I hope it will be useful for SNC Beginners. And Experts plz excuse me and also I will continue with the SNC – PI Integration with an another blog shortly .

Please replace and read “à” character as  (——–>>) as I cant to do that …  Ex : Settings à profiles (as)  Settings —-> Profiles.

.

  1. Within SAP application components à Supply Network Collaboration à Master Data à Model and Planning Version à Create Model 000 and Planning Version 000

/wp-content/uploads/2014/05/1_459078.jpg

The first basic step for customization in SNC begins by creation of Model and planning version. This is a one time activity done at the beginning.

  1. Within SAP application components à SAP Business Partner à Business Partner à Basic settings à Number ranges and groupings à Define Number Ranges

/wp-content/uploads/2014/05/2_459079.jpg

Define Number Ranges

In this activity, you define number ranges for business partners.

The defined number ranges are assigned to groupings in the Define groupings and assign number ranges activity.

Number ranges for business partners are valid throughout a client.

Standard settings

The standard SAP system contains number ranges for the groupings provided.

Custom settings

MD is a custom range; 01 is external number range and AB is internal number range which is maintained here. These number ranges are invoked while creation of Business Partner.

  1. Within SAP Application componentsà SCM Basisà Master Dataà Productà Specify Output Format of Product Number

/wp-content/uploads/2014/05/3_459128.jpg

Specify Output Format of Product Number

In this work step, you determine the following:

• Maximum input and output length of the product number; the length can be up to a maximum of 40 places.

• Template for displaying the product number (on-line or printing) you must type an underscore at every place in the product number that should not contain template characters.

• Display with or without leading zeros

• Storage type of the product number

You can make these product number settings for the entire system.

Activities

  1. 1. Determine the maximum length of the product number.
  2. 2. Determine a product number template.
  3. 3. Determine if the product number should be displayed with or without leading zeros.
  4. 4. Determine the storage type of the product number.

Dependencies:

Effects on ERP systems via Core Interface (CIF):

The settings made here are independent of the ERP system and only influence the conversion of the internal SAP APO display to external SAP APO display.

As with conversion of SAP APO data, there is also a similar conversion of the internal SCM display to external SCM display. So that the numbers also appear immediately on the interface, it is recommended that you use a corresponding conversion in SCM and in ERP.

If SCM is planning for several ERP systems, it may be necessary to make the identical numbers from different ERP systems unique in SCM. It is usual to use a prefix or suffix to do this. In this case, the internal ERP display and the internal SCM display are different. The conversion between the internal and external SCM display thus also differs from the conversion in ERP.

Custom settings

Here the lexicographical indicator is also maintained because of which the “0” is not added to the system auto proposed product ID

  1. Within SAP application componentsà Supply Network Collaborationà Basic settingsà Processing Inbound and Outbound Messagesà Processing Types of Outbound Messages à Assign Outbound XML Messages to Default Process Types

/wp-content/uploads/2014/05/4_459129.jpg

Assign Outbound XML Messages to Default Process Types

Use:

In this IMG activity, you define a default process type for an outbound XML message; in other words, you assign the XML message to the process type for which you want to use the XML message by default. Possible process types are Collaboration with Suppliers, Responsive Replenishment, and Returns Collaboration with Customers. The assignment of an XML message to a process type is relevant for outbound message processing. Depending on the process type, SAP Supply Network Collaboration (SAP SNC) writes data such as business partner numbers to different fields in the XML message: this can be InternalID, BuyerID, or VendorID. If you want to define a process type for an outbound XML message dependent on which system sends the XML message and which business partner sends the message, use the IMG activity Assign Sender-Dependent Process Types (Outbound).

Standard settings

The standard system comes delivered with a default assignment.

Activities

Check the default assignment and, if required, assign an XML message to a different process type

  1. Within SAP application componentsà Supply Network Collaborationà Basic settingsà Processing Inbound and Outbound Messagesà Processing Types of Inbound Messages à Assign inbound XML Messages to Default Process Types

/wp-content/uploads/2014/05/5_459130.jpg

Assign Inbound XML Messages to Default Process Types

Use

In this IMG activity, you create a default process type for an inbound XML message, that is, you assign the XML message to the process type for which you wish to use the XML message by default.

Note that:

• SAP Supply Network Collaboration (SAP SNC) always assigns a Delivery Information in which the returns indicator has been set to the process type DMRP, for dealer-managed returns processing, irrespective of the setting in this IMG activity.

• If you wish to define the process type for an inbound XML message depending on which system sends the XML message and which business partner sends or receives it, use the IMG activity

• Define Sender- and Recipient-Dependent Process Types.

Standard settings

We deliver a standard assignment.

Activities

Check the standard assignment and, if necessary, assign an XML message to a different process type.

Assign Sender- and Recipient-Dependent Process Types (Inbound)

Use

By default, the system assigns an inbound XML message to the default process type you entered in the IMG activity Determine Default Process Types. This assignment is independent of which business partners are exchanging the XML message and which system is sending it.

In this IMG activity, you can set the process type for an inbound XML message depending on which system is sending it and which business partner is sending or receiving it. The assignment you make here overrides the default process type.

Note: If you have not entered a process type for an XML message in this IMG activity and no default process type has been defined for the XML message, the system terminates inbound processing of the message.

Activities

If you wish to assign an XML message with a certain combination of sending system, sender, and recipient to another process type, create an entry with the corresponding parameters. When maintaining an entry, note the following:

• If you do not enter a sending system, a sender, or a recipient, the process type of this entry applies, irrespective of the parameter not specified. In particular, a process type applies to all combinations of sending system, sender, and recipient if you enter none of these parameters. Such an entry determines the standard setting for the XML message. You can exclude an XML message with a certain parameter combination from the standard setting by creating an additional entry with this parameter combination and the desired process type.

• You must not enter a sender for XML messages from an SAP back-end system.

• SAP SNC always assigns a Delivery Information in which the returns indicator has been set to the process type DMRP, for dealer-managed returns processing, irrespective of the setting in this IMG activity.

  1. Within SAP Application componentsà Supply Network Collaborationà Basic Settingsà Processing inbound and outbound messagesà Display of External Exceptions and Logs àMaintain Settings for Master data completion

/wp-content/uploads/2014/05/6_459137.jpg

Maintain Settings for Master Data Completion

Use:

In this IMG activity, you configure the master data completion, which SAP Supply Network Collaboration (SAP SNC) uses to automatically complete missing master data in inbound XML messages. You use this IMG activity to define how SAP SNC uses input for business partners to determine locations. Since several locations can be assigned to every business partner, you have to specify in the system how the system is to determine the locations. To do this, you can create a master data completion profile for every XML inbound interface and for every process type, by entering data for the master data completion method. You can also maintain the settings on a partner-specific basis, by specifying a a sender or recipient. If you leave the sender or recipient blank, the system interprets the settings as being relevant for all senders or recipients. Note that you must always leave the sender field empty in the case of standard integration (standard XI mapping) with an SAP ERP system.

In addition, you can define the log settings for the master data completion.

In the master data completion profile, you can either choose a master data completion method, or specify a location that the system is to use as default for an XML inbound interface and process type.

You can choose between the following master data completion methods:

• No system action

The system does not execute master data completion.

• Specified location

The system selects the location that you have entered in the Location Number field.

• Use first location found

The system only determines whether a location has even been assigned to the business partner. If this is the case, the system copies the first location found.

• Use first location found depending on transportation lanes

The system determines whether a location or product has been assigned to the business partner and whether a transportation lane exists for this location or product. The system then copies data from the transportation lane to complete the missing locations.

• Use first location found depending on document reference

The system imports the document reference in the XML message, such as a reference to an advanced shipping notification or a delivery plan. The system copies the missing master data from the document.

You can use the sequence number to define in which sequence the system is to determine the locations, for example, first the customer location and then the ship-to location. If the system determines locations that are assigned high sequence numbers, it uses the results of the master data completion for lower sequence numbers again. Thus, which sequences and master data completion methods you choose for which sequence numbers have an impact on the results of master data completion.

Standard settings

The standard system comes delivered with default settings for all message interfaces that are delivered for standard integration (XI mapping) with an SAP ERP system. You can use the Business Add-In (BAdI) /SCA/DM_MD_COMP to complete or override these default settings. For more information, see the BAdI documentation under BAdI: Master Data Completion.

Hope this document helps on key views on Master data and Basic settings Maintenance in the SAP SNC system.

Also on the other end, I am preparing theblog on the  SNC – PI Integration for PO collaboration and will keep on posted once it done..

Thanks for your time…..

Karthick

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Selim Batur

    Hi Kathrick,

    This is a really good blog posting to support SNC implementations.

    Keep sharing for the community 🙂

    Regards,

    Selim Batur

    (0) 

Leave a Reply