Hierarchy

⤷

⤷

Basic Data
Data Element | EDI_REF |
Short Description | Reference Ship-to Party for IDoc Copy Management |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | EDI_RCVPRN | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | EDPO1 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Reference |
Medium | 17 | Ref. STP |
Long | 20 | Ref. STP |
Heading | 17 | Ref. STP |
Documentation
Definition
Reference ship-to party
Use
The IDoc Copy Management tool allows you to copy outbound IDocs to different ship-to parties (customers) and to send them to a file port. The references and customers are maintained using the view V_TWPCOPY.
The reference ship-to party is a customer that represents a group of customers for whom the outbound documents are created. The IDocs that are created can then be copied using the tool (report RWDLCOPY_MANAGE or transaction WDL_COPY) to additional customers (ship-to parties).
You must enter and assign a PSS port for the reference ship-to party. For the actual ship-to party (customer) to whom the IDocs from the reference should be copied, you must maintain and assign a file port.
It is important that all the customers have one and the same reference ship-to party and the same file port.
Note that the reference ship-to party can also be a customer and in this case, should be maintained both as reference and as customer (ship-to-party) in the view. In this case, the reference IDoc is also sent to the reference ship-to party as customer. The IDoc is is sent to the port of the customers assigned to it.
Dependencies
Example
History
Last changed by/on | SAP | 20030430 |
SAP Release Created in | 200 |