SAP ABAP Data Element VALUETYP (Type of field to be transferred to catalog)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ SRM-EBP-CUS (Application Component) Customizing
     ⤷ BBP_PU_C (Package) Business-to-Business Procurement - Purchasing - Customizing
Basic Data
Data Element VALUETYP
Short Description Type of field to be transferred to catalog  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type VALUETYP    
Data Type CHAR   Character String 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name QUALIFIER   
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Type 
Medium 15 Type 
Long 20 Type 
Heading 30 Type 
Documentation

Use

  • Type 0 (URL)

    Uniform Resource Locator (URL), under which the catalog can be reached.

    Example for the URL of the requisite catalog in IDES:

    http://idesreq35.wdf.sap.corp:1080/BugsEye/servlet/BugsEye_800

  • Type 1 (SAP field)

    Individual parameters when the catalog is called up can also be SAP fields. If, for example, a user name has to be passed on, you can enter SY-UNAME in the Content field. The system then automatically fills the parameter with the user name.

    Note: the requisite catalog in this example is supplied with a fixed value.

  • Type 2 (fixed value)

    If the parameter always has a fixed value, enter type 2.

    Example:

    In this example USERNAME and PASSWORD.

  • Type 3 (field from service)

    Special fixed value parameter within a service of the catalog application. This type is treated in the same way as type 2 when the catalog call is generated.

  • Type 4 (return URL)

    The name of the return URL depends on the catalog. You may not fill the Content field, because this field is determined and passed on dynamically at the time of the call.

    Example:

    For the requisite catalog, the name is HOOK_URL; for the SAP product catalog it is MM_HOOK_URL.

Caution

You must maintain all catalog-specific call parameters before the entry with type 4. The three SAP-internal parameters named must follow after the entry with type 4:

Name    Content    Type

HOOK_URL        4

~OkCode    ADDI    2

~Target    _top    2

~ForceTarge    Yes    2

Example: complete call of requisite catalog:

http://idesreq35.wdf.sap.corp:1080/BugsEye/servlet/BugsEye_800?username=guest&password=ides&HOOK_URL=SAPEVENT:POST

The return URL is passed on in encrypted form.

History
Last changed by/on SAP  20010216 
SAP Release Created in