cancel
Showing results for 
Search instead for 
Did you mean: 

Changing custom field appearance

Former Member
0 Kudos

Hi All,

I have added a custom text field to basic data section of Shopping cart. Is it possible to display it in Web as text area? If so, how do we manage the data flow from/to it?

Thanks in advance

Nandalal

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Nandalal,

no this is not possible.

Even if technically you could define a CUF with 400 char, and call a custom screen to handle it as a text area. But this is not a good solution to store text data in a table field.

In SRM 5.0, you can define some custom text types (added in header or item document tab).

In SRM 4.0, custom text types could be added, but with changes on standard code.

Rgds

Christophe

Former Member
0 Kudos

Hi Christophe,

Thanks for the reply. We are currently running 4.0 but may soon be upgrading to 5.0. So please let me know how can we define custom text types and use it in 5.0

Thanks

Nandalal

Former Member
0 Kudos

Hi Nandalal,

in SRM 5.0, we can define some text types & schema and assign them to document header or item.

SPRO -> SRM Server --> Cross-Application Basic Settings --> Text Schema:

- Define Text Types

- Define Text Schema

- Define Fixed Values for Texts

Here is the documentation for this customizing point:

Define Text Schema

Use

In this IMG activity, you define new text schemas, and assign text types to these text schemas.

Standard settings

Text schemas are shipped for all SRM documents.

Activities

1. To create a new schema, choose New Entries, and enter an ID and short text for the new schema.

2. To add text types to the schema, select the schema and choose Texts for Schema and then New Entries.

3. Use the input help to select a text type, and then enter a short description that will appear on the user interface (UI).

a) Specify whether this text should be displayed for the header only, for the item only, or for both.

b) Specify whether the text should be visible to all users, visible for internal or external users only, or hidden to all users.

c) You can also specify whether the text can be changed by all users, by internal or external users only, or not at all. If you select the option By Workflow User in Display Mode, it will be possible to change the text type in the approval process even if it is in display mode.

d) The 'Can Be Copied' field specifies whether the content of the text type is copied in the document flow. If you want to display the copied texts in the follow-on document, you must ensure that the text type for copying also exists in the follow-on document.

Note: The system can only copy the long texts for text types for which no fixed values have been defined in Customizing for the source text schema or for the text type in the follow-on document.

If you do not want this to happen, you can implement BAdI <DS:SIMG.BBP_LONGTEXT_BADI>BBP_LONGTEXT_BADI.

4. To assign a text schema to a transaction type (or business transaction), use the IMG activity Define Transaction Types.

Note:

You cannot configure header-level text schemas for shopping carts.

In shopping carts, you can only define default item settings for the text type NOTE. If you want to enter a text that applies to all items, make sure that the text type NOTE has been defined in Customizing. If this text type does not exist in the relevant text schema, the function is deactivated. In other words, you cannot enter any predefined long texts for shopping cart items.

If you want to run a check on a reason for rejection or return delivery when you approve invoice or confirmation documents, make sure that the text types RREJ (reason for rejecting invoice) and RRTN (return delivery reason for confirmation) exist in the relevant text schema of the documents. If these text types do not exist in the relevant text schema, the check is deactivated.

In a bid , all of the non-changeable text types that do not exist in the source document (bid invitation or auction) are hidden. The relevant description from the source document is used for non-changeable text types that exist both in the text schema of the bid and in the text schema of the source document (bid invitation or auction).

Rgds

Christophe

Former Member
0 Kudos

Thanks Christophe,

I shall try this while working with 5.0.

Thanks very much for the same.

Nandalal

Answers (0)