Show TOC

Function documentationUsing Business Object BCONT_UMC

 

The business object type BCONT_UMC is used to trigger the Workflow for processing the Internet Service Request (ISR) using a customer contact, that is, changing the business partner's first name and last name. It is inherited from the standard Customer Contact business object of type BCONTACT.

Features

The new BO Event RequestReceived is introduced to trigger the workflow when an ISR is received. This event contains the following input parameters:

Parameters

DDIC Type

Description

BusinessPartner

BUT000-PARTNER

Business Partner Number

NumOfInputVariables

SYST-INDEX

Total Number of Input Variables

InputVariables

ISUS_UMC_CONTAINER_VAR

Input Variables table (Name/Value pair)

The new method AppendText is also added into the BCONT_UMC business object. This allows you to add a new text line into the Customer Contact.

The following table describes the input parameters for the BCONT_UMC business object:

Input Parameter

Description

Lang

Language key (optional)

NewTextLine

Text line to append (optional)

MsgClass

Message class if a message is appended (optional)

MsgNo

Message number if a message is appended (optional)

MsgV1

Variable 1 for the message to append (optional)

MsgV2

Variable 2 for the message to append (optional)

MsgV3

Variable 3 for the message to append (optional)

MsgV4

Variable 4 for the message to append (optional)

The following table describes the export parameter for the BCONT_UMC business object:

Export Parameter

Description

Return

Return parameters in the table of BAPIRET2

The following table describes the exceptions for the BCONT_UMC business object:

Exception Code

Description

1000

TD/602 (The Text object is not available)

1001

TD/603 (The Text ID for the text object does not exist)

1002

TD/604 (Language is not allowed)

1003

TD/605 (Name & is invalid)