Transaction WDBM with IDOC WBBDLD for Assortment List

[carlostol]

Hello,

I want to send the Assortment List to our PI system through the WDBM transaction that generates an outbound IDOC WBBDLD. I'v already did all the necesary configuration (assortment list profile, WE21, WE20, etc) and the IDOC's are created. But it seems to be a restriction for the IDOC to be sended only to a type KU partner profile. Since we have more than 20 stores (and will continue to grow) it doesn't seem feasible to create 20 or more type KU parter profiles for maintenance reason.

Is there a way to configure the Assortment List Profile to make the IDOC to be sended to a single type LS (logical system) profile that would be pointed to our PI system?

I've debugged tx. WDBM and I've found a FM WDLD_IDOC_REDUCT_STRUCTURE_GET with the following source code:

...line:81:

   i_rec_edk13-mandt  = sy-mandt.       " 99A

   i_rec_edk13-rcvprn = locnr.          " 99A

   i_rec_edk13-rcvprt = 'KU'.           " 99A    Partnerart Kunde

   i_rec_edk13-mestyp = pi_mestyp.      " 99A

   CALL FUNCTION 'EDI_AGREE_OUT_MESSTYPE_READ'               "99A

        EXPORTING

            rec_edk13       = i_rec_edk13

       IMPORTING

            rec_edd13       = i_rec_edd13

       EXCEPTIONS

            db_error        = 1

            entry_not_exist = 2

            OTHERS          = 3.

...

The partner type of receiver is hardcoded to 'KU'. Our server is on SAP ECC 6.0 NW 731 with component EA-RETAIL v600.

Please help.

Regards...

[Former Member · Accepted solution]

Hi Carlos,

This is the way to do it.

No need to worry about the creation of your stores Partner Profiles. You don't have to do this operation manually. Thru the "Customizing for Plant" menu entry (tx WB01/WB02), you can enable the automatic Partner Profile creation:

You just have to:

- Set once the message types / IDocs, you want to send, on your reference site

- Add the EDI Partner profile in your relevant copy rule

And then the EDI partner profile will be automatically created for your "real" sites as expected...

[former_member189773]

Hi Carlos,

It is not possible to maintain one common profile for all sites, the objective to maintain partner profile is to enable store specific data maintenance i.e: Price, assortments etc. It is not possible, and even if do it functionally you might face lot of problems going forward. If u want to do it without partner profiles try integrating your systems through SOA.

Regards,

Vikram

[Former Member]

Hi Carlos,

WBBDLD is a Retail IDOC and works with the KU partner profile. The reason is WBBDLD IDocs are supposed to communicate only the store listed articles and store specific article info to each store ( ie each KU partner).

It is advisable to create KU partners for each of the stores in We19. It can also be mass maintained through a small program and also copied easily. Meanwhile for any new site creation process, you can add this step of creating a partner profile for the site as an activity.

Regards

Sudip Deb

[ramesh_kajuru]

Hi Carlos,

As rightly mentioned by Deb that "WBBDLD is a Retail IDOC and works with the KU partner profile".

Understand in your case you require to create Multiple Profiles for multiple Stores.

Suggest you to initially create profile at customer level and then under each customer you can create number of profiles for Stores.

In our case we have 4 brands and for each brand have more than 1000 stores. For 4 brands created profiles and underneath each of this brands configured for each of the stores.

Hope this gave a high level idea.

Ramesh

[Former Member]

Hi Carlos,

For all retail site (Store) you have to use KU partner type only. For new stores you can use the Create Copy function to copy the partner profile from other store and rename it to new store. This activity will hardly take couple of seconds.

Thanks,

Vikas