Functionality
This Business Application Programming Interface (BAPI) creates serviceorders based on the order codes entered in table ORDERDATA.
You can also use this BAPI to create maintenance orders for theUtilities industry.
Please note the following for this BAPI:
A COMMIT WORK command is triggered during each call.
You may not use this BAPI if you use a configurable task list ora configurable technical reference object to create the orders.
The service orders can have different commercial characteristics.

Example
Orders for

• Replacing a device


• Disconnecting one or more devices of a customer with outstanding
payments

• Repairing a defective transformer after a power failure.

Notes
Messages are returned in the parameter RETURN. The documentation forthis parameter lists the return codes and explains their meanings.

Further information
During execution of this BAPI the system generates an application logthat contains the following:


• Creation data


• Error messages


• Numbers of the orders generated.

To evaluate this log, proceed as follows:
Call transaction SLG1.
Select object IUWMORD and sub-object BAPI_CREATE_MULTIPLE.

Description
This table contains long text lines for a service order.
The fields are explained below:


• ORDERINDEX: For information about the order index, see the

data element documentation:
Order index

• FORMAT_COL: For information about the tab column, see the

data element documentation:
Tag column

• TEXT_LINE: For information about the text line, see the data

element documentation:
Text line

Description
This table contains an object list entry for a service order for eachline.
The fields are explained below:


• ORDERINDEX: For information about the order index, see the data

element documentation:
Order index

• OBJECTID: For information about the object type for object

lists, see the data element documentation:
Object type

• FUNCT_LOC: For information about the functional location, see

the data element documentation:
Functional location

• EQUIPMENT: For information about the equipment number, see the

data element documentation:
Equipment number

• MATERIAL : For information about the material number, see the

data element documentation:
Material number

• SERIALNO: For information about the serial number, see the

data element documentation:
Serial number

• ASSEMBLY: For information about the assembly, see the

data element documentation:
Assembly

• NOTIF_NO: For information about the notification number, see

the data element documentation:
Notification number

Value range
The fixed values for the parameters are listed below:


• OBJECTID: Fixed values of the object type for object lists

01 = functional location
02 = piece of equipment
03 = serial number
04 = assembly
05 = Notification

Description
This table contains object links for a service order.
The fields in the table are explained below:


• ORDERINDEX: For information about the order index, see the data

element documentation:
Order index

• OBJKEY: For information about the object key, see the data

element documentation:
Object key

• OBJTYPE: For information about the object type, see the

data element documentation:
Object type

• RELTYPE: Binary relationship type

Value range
The fixed values for the parameters are listed below:


• RELTYPE: Binary relationship type

"EXE1" = Disconnection/reconnection
"EXE2" = Replacement
"EXE3" = Inspection
"EXE5" = Check sample devices
"EXEC" = Meter reading
"EXEC" = Deregulated reference point
"EXEC" = Device information record

Description
This table contains the data for creating a service order.
The fields of the table are explained below:


• ORDER_CODE: For information about the order code, see the

data element documentation:
Order code

• PLANPLANT: For information about the maintenance planning

plant, see the data element documentation:
Planning plant
If the maintenance planning plant is not transfered, then it is
determined with the main work center.

• REGIOGROUP: If you did not enter the maintenance planning plant

using the parameter PLANPLANT, then the maintenance
planning plant is determined from the order code and the
regional structure group. For information about the
regional structure group, see the data element
documentation:
Regional structure grouping

• LANGU: For information about the ISO language key, see the

data element documentation:
Language key

• LANGU_ISO: Language according to ISO 639


• ORDER_TYPE: For information about the order type, see the data

element documentation:
Order type

• INT_OBJ_NO: For information about configuration, see the data

element documentation:
Configuration

• START_DATE: Order start date


• FINISHDATE: Order finish date


• S_ORD_ITEM: Do not use.


• OBJECTTYPE: For information about the technical reference object

type, see the data element documentation:
Technical reference object type

• REF_OBJECT: For information about the technical reference

object, see the data element documentation:
Technical reference object

• SERIALNO: For information about the serial number, see the

data element documentation:
Serial number

• CUSTOMER: For information about the customer number, see the

data element documentation:
Customer number

• ORDERID: For information about the order number, see the data

element documentation:
Order number
Here the number of the order generated is returned.

• WORKCENTER: For information about the main work center,

see the data element documentation:
Main work center

• START_TIME: For information about the basic start date (time),

see the data element documentation:
Basic start date (time)

• FINISH_TIME:For information on the basic finish date (time),

see the data element documentation:
Basic finish date (time)

• PLANTWORKC: For information on the plant associated with main

work center, see the data element documentation:
Plant associated with main work center

Value range
The fixed values for the parameters are listed below:


• OBJECTTYPE: Fixed values for the technical reference object type

'01' = functional location
'02' = equipment
'03' = serial number
'04' = assembly

Description
This table contains permits for a service order.
The fields of the table are explained below:


• ORDERINDEX: For information about the order index, see the data

element documentation:
Order index

• PERMIT: For information about the permit, see the data

element documentation:
Permit key

• OVERRIDE: For information about the indicator for overriding

the settings for permits, see the data element
documentation:
Override default values for permits

• KEYRELEASE: For information about the key for order release,

see the data element documentation:
Valid for order release

• KEYCOMPLET: For information about the key for order completion,

see the data element documentation:
Valid for order completion

• KEYPRINT: For information about the indicator for printing

permits, see the data element documentation:
Indicator: Permit should be printed

Value range
The fixed values for the parameters are listed below:


• OVERRIDE: Indicator: Override default values for permits

' ' = Do not override default values
'X' = Override default values

• KEYRELEASE: Key relevance for order release

' ' = Permit must not be issued
'1' = Permit to be issued after WARNING
'2' = Permit must be issued; otherwise ERROR

• KEYCOMPLET: Key relevance for order completion

' ' = Permit must not be issued
'1' = Permit to be issued after WARNING
'2' = Permit must be issued; otherwise ERROR

• KEYPRINT : Indicator: Permit should be printed

' ' = Do not print permit
'X' = Print permit

Description
Error messages for the method.

Value range
If an error occurs, the following messages are returned:
Type ID Number Message
E E9 878 Entry of tables ... required in FM ...
E E9 100 You are not authorized to create service
orders.
E EEWMSERVICE 010 No service object exists for order code &1
E EEWMSERVICE 084 No entry for plant &1, service object &2 &3
in table T399A