Import of Merchandise Hierarchy changes from other system

[former_member1207844]

Good day for everyone!

Can you please help me in this situation:

1. We have two system - SAP and system for master data maintenance (call it MD).

2. Merchandise Hierarchy structure creates in SAP and migrates to  MD system.

3. All changes we want to make in MD system (creating/changing/deleting  hierarchy nodes, hierarchy reorganization, creating/changing/deleting attributes for hierarchy nodes) and then pass it in SAP.

Are there any standard instruments in SAP that can allow to transfer all making changes for Merchandise Hierarchy in MD system to SAP (reports, FM and so on)? Maybe anyone have experience with similar situation? I hope for help! Thank you for answers!

[paul_gendreau · Accepted solution]

Hi Olga:

The sceanrio is distribution from the sending system.  Standard transactions and ALE support transfer of Merchandise Category Hierarchy (MCH) and dependant objects (characteristics and values, for example).

There are four message types that will be sent: W_WGRP, CHRMAS, CLFMAS, and CLSMAS.  MCH objects have dependencies and therefore the sequence of these messages must be controlled, which requires the addition of a fifth message type: SERDAT.

It is important to understand that IDoc Serialization using message types is used when several different message types are dependent on each other, as is the case here.  For example, if a merchandise category is assigned to a merchandise category hierarchy level,  the merchandise category hierarchy level must first exist.

For this reason, the message types are grouped together in a serialization group, in which the processing sequence is defined.  There is a standard serialization group for this purpose: GRP_W_WGRP. 

Use the following path to configure inbound processing:

SALE > Modeling and Implementing Business Processes > Master Data Distribution > Serialization for Sending and Receiving Data > Serialization Using Message Types > Define Inbound Processing

Here is an outline of the steps:

1. SALE - Configuration of Serialization of IDoc processing

2. SM59 – Create RFC destination

3. WE21 – Create an RFC Port

4. BD64 – Create Distribution Model

5. WE20 – Create Outbound Partner Profile

6. WE20 – Create Inbound Partner Profile

7. WGSE – ALE MCH Objects

Please also take note of the following standard reports:

RBDSER01 creates the IDocs for a serialization group.

RBDSER02  dispatches the IDocs belonging to a serialization group.

RBDSER03  checks whether all the IDocs have been successfully sent to the receiving system. If they have, a control message of message type SERDAT is sent to the receiving system and posts the serialization group there.

RBDSER04 is for processing of inbound IDocs of a serialization group can be directly started by the Report RBDSER04.

You will want to also consider maintaining Reference Articles in the sending system and distribution of Reference Articles using ALE too.  This is because Reference Articles are assigned to the Merchandise Category.  The standard transaction for this is BD10.

In addition to the manual transactions and reports, change pointers can also be used to distribute the master data.

- Paul

------------------------------

Paul Gendreau, Jr.

SAP Retail

[former_member1207844]

Thank you so much for helpful answer, Paul!