Professional Documents
Culture Documents
Sub Contract Inbound Delivery User Exit
Sub Contract Inbound Delivery User Exit
release level. Below is the standard documentation available for this class interface. You can view this
information and more if you enter the class name CL_SHP_LECOMP into the relevant SAP transaction such
as SE24 or SE80.
Contribute (Comments)
Within the comments section below there is also an opportunity for you to add useful hints, tips and
information specific to this SAP object. This means that you and other users will be able to find these details
quickly by simply searching on the object name CL_SHP_LECOMP or its description.
Class Methods
In some respects Class methods are similar to function modules in that they are a coding block that
performs certain ABAP functionality. Methods can be referenced using the following syntax: CALL METHOD
CL_SHP_LECOMP=>methodname EXPORTING/IMPORTING...
Class Attributes
Class attributes can be referenced using the following syntax CL_SHP_LECOMP=><attribute name>.
Although depending on where you are inserting the ABAP code you do need to check if the attribute is public
or private.
GC_BWART_COMP_GR -
GC_FCODE_COMP_VL32 -
GC_FCODE_COMP_VL60 -
GC_TRTYP_CHANGE -
GC_TRTYP_CREATE -
GC_TRTYP_DISPLAY -
GC_UPDKZ_DELETE -
GC_UPDKZ_INSERT -
GC_UPDKZ_OLD -
GC_UPDKZ_UPDATE -
GC_VBTYP_GI_REVERSE -
GC_VBTYP_LIAV -
GC_VBTYP_PO -
GC_XLBTYPE_COMP -
GC_XLBTYPE_PARENT -
GC_BWART_COMP_GI -
MF_CHANGED - Changed?
MF_LANGU - Language Key of Current Text Environment
MF_LIFNR - Account Number of Vendor or Creditor
MF_PROPOSED - Proposal (must be confirmed/ changed)?
MF_TRTYP - Transaction type
MT_ISSUE - Goods issue data
MT_ITEM - Inbound delivery items
MT_XCOMP - SC Components maintained
MT_YCOMP - SC Components on database
Class Events
Events are created within your class using special event handler methods. These must be registered at
runtime for the event and can then be triggered using the ABAP syntax: RAISE EVENT <event name>
EXPOTING...