Functionality
This BAPI is used for changing a shipping document (header and itemdata) or for deleting shipping document items.
Generally speaking, the following applies:

• You only have to enter the data to be changed.


• You must select this data with an X in the appropriate checkbox
structures.

• You should enter the value U in field UPDATEFLAG (in table ITEMDATAX)
(D if you want to delete and item).

• Always enter key fields when you make changes, also in the checkbox
structure.
Possible UPDATEFLAGS: U = Update/change
D = Delete

Notes
If the sender/recipient is of category network or project definintion,you must enter a network activity or WBS element for the projectdefinition in the HEADERDATA since the BAPI guidelines do not allowdialog.
If an equipment, which represents a package, is transferred into tableITEMDATA, this package is not exploded. The user is responsible forexploding and transfering the package items as part of the ITEMDATA.You can possibly use RFC function module/SAPCEM/HIER_PAKET_AUFLOESEN.
If an error is found (parameter RETURN contains entries of TYPE E or A)and the shipping documeent cannot therefore be changed, you must ensurethat all locks are released.
The BAPI does not involve a database commit. This means that thecalling application has to exit the commit so that changes can be madeon the database. BAPI BAPI_TRANSACTION_COMMIT is available forthis purpose.

Description
Detail Data for a Shipping Document Header Record

Value range
DOC_TYPE Document Type
SENDER Sender
RECIPIENT Recipient
INTER_RCPT Intermediate Recipient
EXTDOCNO External Document Number
DOC_DATE CEM Document Number
WBS_ELEMENT_SENDER WBS Element - Sender
WBS_ELEMENT_RECIPIENT WBS Element - Recipient

WBS_ELEMENT_INTER_RCPT WBS Element - Intermediate Recipient
ACTIVITY_SENDER Transaction Number - Sender
ACTIVITY_RECIPIENT Transaction Number - Recipient
COMMENT1 Commentary 1
COMMENT2 Commentary 2

Description
Checkbox structure: shipping document header
Only data from structure HEADERDATA for which the correspondingcheckbox in structure HEADERDATAX has been set is copied to theshipping document.

Description
Document number of the document to be changed

Description
If you set this indicator, updating does not take place.

Description
Structure with data from customer-specific fields (header record)
Only data from structure USERFIELDS for which the correspondingcheckbox in structure USERFIELDSX has been set is copied to theshipping document.

Description
Checkbox structure: customer-specific fields (header record)
Only data from structure USERFIELDS for which the correspondingcheckbox in structure USERFIELDSX has been set is copied to theshipping document.

Description
This table contains customer enhancements for tables J_3GBELK (shippingdocument header) and J_3GBELP (shipping document item)

Value range
/SAPCEM/BAPI_TE_J_3GBELK
/SAPCEM/BAPI_TE_J_3GBELP

Default
The documentation for structure BAPIPAREX for thisparameter contains further notes on how to use this parameter. You canfind further documentation under 'Customer Enhancement Concept forBAPIs'.

Description
Item table with values to be changed
Only data from table ITEMDATA for which the correspondingcheckbox in table ITEMDATAX has been set is copied to theshipping document.

Description
Checkbox structure: shipping document item
Only data from table ITEMDATA for which the correspondingcheckbox in table ITEMDATAX has been set is copied to theshipping document.

Description
Table of Messages
The messages are collected in this table.
TYPE Message type: S Success, E Error, W Warning, I Information
ID Message ID
NUMBER Message Number
MESSAGE Message text
LOG_NO Application log: log number
LOG_MSG_NO Application log: sequence number of message
MESSAGE_V1 Message variable
MESSAGE_V2 Message variable
MESSAGE_V3 Message variable
MESSAGE_V4 Message variable
PARAMETER Parameter name
ROW Line in parameter
FIELD Field in parameter
SYSTEM System (logical system) from which the message ensues