Transfer catalog text into new SRM text type ID ?

[yann_bouillut]

Hi,

We are trying to transfer some catalog text into a new text ID "ZPAI" that i have created in SRM.

For this, we are using IF_EX_BBP_CATALOG_TRANSFER~ENRICH_ITEM_DATA

In standard, only the vendor text is filled.

What we want is to transfer one of the catalog text into this ZPAI text type ID (not a CUF !).

Up to now, we didn't find any solution.

Did anybody succeed in transfering catalog text into Z text type ID ?

We already looked at wiki, SDN forum and OSS...

Kind regards,

Yann

[Former Member · Accepted solution]

We had the same requirement at my company, only a text should be transferred to the internal note text id and the vendor text (as well as a custom made text id).

So our problem is like the one you are describing. The way we solved this is as follows:

1. Put all the text into the long description OCI field, this is mapped to the vendor text id in the badi.

2. To make a distinction between vendor text and internal note we put an identifier in the line something like NOTE** (or in your case ZPAI**) in front of the actual text.

3. LOOP over all the CT_LONGTEXTS where the tdline contains the NOTE**. Use the SPLIT command to separate the text id and actual text into a structure of BBP_PDS_LONGTEXT (don't have the actual name here).

SPLIT ct_longtext-tdline AT '**' INTO ls_longtext-tdid ls_longtext-tdline.

4. Add a counter and language

5. ADD ls_longtext to the CT_LONGTEXTS table.

6. Delete the original line from the ct_longtexts table

Above solution is for the longer kinds of texts. If the text stays below 50 characters or so (check the length of CUST_FIELD5), you can put your catalog text in there and start from point 3b to 5.

I hope this gives you an idea what kind of things you could try out.

[yann_bouillut · Accepted solution]

Hi Robin,

We finally found another solution.

We have created 2 Z FM to fill in the correct Z TextID in bbp_doc_change badi

One of the FM is called in the catalog badi, the other one in bbp_doc_change badi.

This enable us to transfer the variable value.

Kind regards,

Yann

[laurent_touillaud]

Hi Yann,

Have you already followed these steps :

- look in structure BBP_OCI_ITEM for CUST_FIELD1 to CUST_FIELD5 if these can suite the transfer of texts.

- look in structure BBP_OCI_ITEM for appending exit structure CI_OCI_CUSTOMER_EXTENSION with your field

- look in the catalog form html if these fields are sent.

Regards,

Laurent.

[yann_bouillut]

Hi Laurent,

We already used CI_OCI_CUSTOMER_EXTENSION and data from catalogue are well transfered to SRM badi.

However, this is nthe next step that is causing us a problem as we have to fill in the SC or PO item text ID with the value we have received from the catalogue.

How do you do it ?

Kind regards,

Yann

[laurent_touillaud]

Hi,

Have you also :

- appended the item data structure BBP_PDS_SC_ITEM_D with the exit structure CI_BBP_ITEM_SC

and

- appended the item data structure BBP_PDS_PO_ITEM_D with the exit structure CI_BBP_ITEM_PO

Regards,

Laurent

[yann_bouillut]

Hi Laurent,

I was not clear...

I do not have any issue to transfer catalogue data to SRM SC or PO CUF field.

I do have issue to transfer catalogue data to SRM or PO item TEXT ID field

kind regards,

Yann

[laurent_touillaud]

Ok now i see.

Did you also take a look after the badi where longtexts are transferred :

program : LBBP_SC_APPF65

line identifier : **.. longtexts from catalog

PERFORM text_update

USING

ls_item-guid

c_ltxtid_itxt

lt_text

CHANGING

cs_document.

lt_text must be filled at this stage.

Best regards,

Laurent

[yann_bouillut]

Hi Laurent,

Yes this code validate the fact that it cannot work with another text than c_ltxtid_itxt

Kind regards,

Yann