!--a11y-->
This table is used if the log file for the external optimization system is sent back. The events in the SAP System are described in this log file.
CLOIMETLOG
Field |
Description |
Type |
Length |
INDX |
Index for each entry |
char |
10 |
LOGLEVEL |
Level for the log of executed methods |
char |
10 |
METHOD |
Methods are functions that can be carried out for only one object. Example: scheduling orders |
char |
1 |
OBJTYP |
Field specifying the object category for which the method is to be generated: orders planned orders order sequence operations in orders "operations in planned orders" |
char |
32 |
PLNUM |
Planned order number |
char |
10 |
EXTPLNUM |
Planned order number of the external system |
char |
10 |
PLNFL |
Sequence of operations within a task list |
char |
6 |
AUFNR |
Order number |
char |
12 |
EXTAUFNR |
Order number of the external system |
char |
12 |
APLFL |
Sequence number |
char |
6 |
VORNR |
Operation number |
char |
4 |
OBJIDEXT |
SAP external object key |
char |
90 |
SUCC_CODE |
Field specifying whether the method was successfully executed |
char |
10 |
WORST_S_C |
Worst success code |
char |
10 |
FIRST_MSGL |
First entry in the message log for the method (in char) |
char |
10 |

This table provides an overview of the executed methods. The entries in the table may look different for various object types.
Examples of these methods are "UPDATE", "CREATE", "DELETE", "READ".
This table is only returned if the parameter CLOI_IF_PAR-METLOG_REQ was set to X. In addition, you can control the content using parameter CLOI_IF_PAR-MET_FILTER.
OBJIDEXT: if the object type is a planned order, "planned order operation", production order/process order or production/process order operation, you must also enter a unique identification in the fields PLNUM, EXTPLNUM, PLNFL, AUFNR, EXTAUFNR, APLFL and VORNR.
