Functionality
The BAPI_DANGEROUSGOOD_SAVEREPMUL method is used by a system toreplicate or modify the business object dangerous goods in anothersystem. Distribution is carried out asynchronously.
In the source system, the BAPI_DANGEROUSGOOD_REPLICATE method is used toprovide the relevant data records.
The corresponding IDoc of type DANGEROUSGOOD is filled with the data.
The IDoc is sent to the target system defined in ALE Customizing.
The data from the IDoc is posted in the target system using theBAPI_DANGEROUSGOOD_SAVEREPMUL methods.

Prerequisites

• The relevant material master records must be entered in the source and
target system.

• The Customizing tables (see the section on Customizing) must be edited
for the dangerous goods master in the target system.

• ALE Customizing must be edited in the source and target system.


• If you use engineering change management, the relevant change numbers
you used to edit dangerous goods master records must be entered in thetarget system.

Notes
Messages are returned in the RETURN parameter. The return values andtheir meaning are explained in the documentation for this parameter.

Customizing
The following tables must be edited in the target system:
Table,,Table Name
Client,,T000
Units,,T006
ISO codes for units of measurement,,T006I
Change number,,AENR
Validity area,,TCG91/92
DG transport type,,THM003/004
DG class,,THM009/010
Classification code,,THM011/012
Danger label number,,THM017/018
Hazard identification number,,THM031/032
Dangerous goods regulation,,THM063/064
Packaging code,,THM073/074
Packing instruction numer,,THM075/076
Aggregate state,,T646A/B
Water pollution class,,TDG15/16
Hazard note,,TDG27/28
Label,,TDG29/30
Hazard-inducing substance,,TDG33/34
VbF class,,TDG35/36
Storage hazard class,,TDG37/38
Processing status,,TDG39/40
UN number,,TDG67/68

Further information
For more information, see Help -> SAP Library -> CA Cross-Application components -> CA The IDoc Interface -> Overview of the IDocInterface -> Monitoring.

Description
Normally, no message is output via the return parameter, as thefunction module is triggered asynchronously (without reference to thesource system). This means that no message can be returned to thesource system. However, a log is written to the subsequent functionmodules and can be displayed in the target system.

Description
For information on the meaning of the sender, see the correspondingdocumentation Logical system of the sender.

Value range
None

Default
None

Description
For information on the meaning of the individual parameter fields, seethe corresponding data element documentation in the ABAP dictionary.
Mandatory fields:
The material, regulation, valid-from and valid-to fields must be filed.If not, the corresponding data record is rejected. If a data record hasa data record split (with engineering change management), the changenumber is then mandatory.
Dependencies:
None

Description
For information on the meaning of the individual parameter fields, seethe corresponding data element documentation in the ABAP dictionary.
Mandatory fields:
The material, regulation, valid-from and valid-to fields must be filed.If not, the corresponding data record is rejected. If a data record hasa data record split (with engineering change management), the changenumber is then mandatory.
Dependencies:
None

Description
For information on the meaning of the individual parameter fields, seethe corresponding data element documentation in the ABAP dictionary.
Mandatory fields:
The material, regulation, valid-from and valid-to fields must be filed.If not, the corresponding data record is rejected. If a data record hasa data record split (with engineering change management), the changenumber is then mandatory.
Dependencies:
None

Description
For information on the meaning of the individual parameter fields, seethe corresponding data element documentation in the ABAP dictionary.
Mandatory fields:
The material, regulation, valid-from and valid-to fields must be filed.If not, the corresponding data record is rejected. If a data record hasa data record split (with engineering change management), the changenumber is then mandatory.
Dependencies:
None

Description
For information on the meaning of the individual parameter fields, seethe corresponding data element documentation in the ABAP dictionary.
Mandatory fields:
The material, regulation, valid-from and valid-to fields must be filed.If not, the corresponding data record is rejected. If a data record hasa data record split (with engineering change management), the changenumber is then mandatory.
Dependencies:
None

Description
This is the extension parameter for the implementation of thecustomer-specific enhancement of dangerous goods fields.
Fields appended to the dangerous goods table DGTM2 by customers usingAPPEND are transferred in this untyped container during distribution.
For a more detailed description of the procedure for appendingcustomer-specific fields in the dangerous goods master, see theapplication help.

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
INCLUDE BAPI_DATAELEMENT OBJECT DOKU ID TX

Description
BAPI Ref. Structure for Referring Object to Superord. UPS

Value range
Table: UPSLINK
This table is located in the function module interface only to ensurecompatibility with the business object definition. In the IDocinterface, its structure corresponds to the identification segment thatbelongs to the uniform packaging service. This table is optional andshould not be transferred.