Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-MID-ALE (Application Component) ALE Integration Technology⤷
SED (Package) IDoc Interface (Processing, Administration, Definition)
Basic Data
| Data Element | EDI_PVROUT |
| Short Description | Name of function module |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | EDI_PVROUT | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table | EDIFM |
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 | 7 | Routine |
| Medium | 15 | Identification |
| Long | 17 | Function module |
| Heading | 27 | Name of function module |
Documentation
Use
In order to prevent unprocessed files being overwritten, you use function modules which generate file or directory names dynamically, that is to say, at runtime. SAP recommends the module
EDI_PATH_CREATE_CLIENT_DOCNUM,
which names every file differently (namely, with the number of the first IDoc contained in the file and of the client).
For the output value every function module must deliver a "complete file name", that is, a character string from directory and file names. The file system then operates with these complete names.
Dependencies
The function modules can derive the complete file names from your entries for the directory and for the file. Function modules delivered by SAP ignore the file specification, that is to say you can leave this field empty in the port definition.
If your SAP system runs on several operating systems it is recommended that you use a logical directory instead of an explicit ("physical") directory.
In this case SAP recommends the function module
EDI_LPATH_CREATE_CLIENT_DOCNUM,
which derives a physical directory from the logical directory and the respective operating system. The file name is derived as EDI_PATH_CREATE_CLIENT_DOCNUM.
You must notify the system of the function modules you have written via control -> generate file name (in the initial screen of the IDoc interface).
Example
IDoc Number 107238 would be sent to client 747.
- In the port definition for the outbound file the physical UNIX directory
/usr/sap/T70/SYS/global/idoc/
and the function module
EDI_PATH_CREATE_CLIENT_DOCNUM
are entered. Then the "complete file name" is called
/usr/sap/T70/SYS/global/idoc/O_747_0000000000107238
that is, the file O_747_0000000000107238 is generated in directory /usr/sap/T70/SYS/global/idoc/. The O at the start of the file name stands for "Outbound".
- In the transaction FILE, the physical directory
\\sapdevdb\sapmnt\T70\SYS\global\idoc\<FILENAME>
for Windows NT operating systems is assigned to the logical directory ("path")
EDI_GLOBAL_PATH
If the application server runs on a Windows NT operating system and the path EDI_GLOBAL_PATH and function module EDI_LPATH_CREATE_CLIENT_DOCNUM are assigned to the port definition then the "complete file name" is
\\sapdevdb\sapmnt\T70\SYS\global\idoc\O_747_0000000000107238
Supplementary Documentation - EDI_PVROUT0001
Use
This selection module comes from the application and converts an application document into an IDoc.
Procedure
Examples
IDOC_OUTPUT_ORDERS converts a purchase order from purchasing into IDoc ORDERS01.
Dependencies
Supplementary Documentation - EDI_PVROUT0002
Use
The use of a function module for inbound processing is not recommended. The external system should generate the file names and transfer them to the IDoc Interface during logon to the SAP System.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_PVROUT0003
Use
The use of a function module for processing the status report is not recommended. The external system should generate the file names and transfer them to the IDoc Interface during logon to the SAP System.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_PVROUT0008
Use
This selection module comes from the application and converts an application document into an IDoc.
Procedure
Examples
IDOC_OUTPUT_ORDERS converts a purchase order from purchasing into IDoc ORDERS01.
Dependencies
Supplementary Documentation - EDI_PVROUT0016
Use
The function module controls the display of status details for status records which were not created by the SAP System.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_PVROUT0020
Use
The function module reads the address data of the partner.
Procedure
Examples
READ_KNA1 reads the customer master record.
Dependencies
Supplementary Documentation - EDI_PVROUT0022
Use
The function module generates the name of the outbound file dynamically. The name of the function module must be known to the EDI subsystem.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_PVROUT0044
Use
The function module generates the name of the inbound file dynamically. The name of the function module must be known to the EDI subsystem.
Procedure
Examples
Dependencies
Supplementary Documentation - EDI_PVROUT0088
Use
The function module generates the name of the status file dynamically. The name of the function module must be known to the EDI subsystem.
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19990505 |
| SAP Release Created in |
