Hierarchy

⤷

⤷

⤷

IMG Activity
ID | PPPI_MD_2611 | Maintain Transfer Structure |
Transaction Code | S_ALR_87006098 | IMG Activity: PPPI_MD_2611 |
Created on | 19981222 | |
Customizing Attributes | PPPI_MD_2611 | Maintain transfer structure |
Customizing Activity | PPPI_MD_2611 | Maintain transfer structure |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | PPPI_MD_2611 |
Step 1: Process transfer structure
In this step, you generate the transfer structures (source description of the table structures) that you can write to a sequential file. You can use this dataset for data declaration in the transfer program.
You use the transfer program to write the BOM data you require from your existing IT system to a sequential file.
The SAP system generates the transfer structure in one of the following programming languages:
- COBOL
- C
- PL/1
For the source description, see the documentation of the transfer program
Transfer BOM without long text (report RCSBI010).
Note:
Please note the following rules when you generate the sequential file:
- A session header can only be followed by BOM header data.
- Sub-item data can never follow BOM header data.
Activities
Generate source descriptions of any table structures you require for the transfer program.
Additional information
For further information on the structure of the sequential file, see step "Transfer data now".
Step 2: Process transfer file
Perform the following steps:
- Enter the logical file name under which the transfer file is stored.
- Select a storage location for the transfer file you want to import.
If you are reading the file from an external application server, enter the server name.Note:
For the source description, see the documentation of the transfer program
Transfer BOM without long text (report RCSBI010).
Step 3: Transfer data
Perform the following steps:
- Enter the logical file name under which the transfer file is stored.
- Select a storage location for the transfer file you want to import.
If you are reading the file from an external application server, enter the server name.Note:
For the source description, see the documentation of the transfer program
Transfer BOM with all long texts (report RCSBI040).
Notes on transport
There is no point in providing a transport connection for this function, because it does not change any Customizing data.
Business Attributes
ASAP Roadmap ID | 253 | Create Data Transfer Programs |
Mandatory / Optional | 2 | Optional activity |
Critical / Non-Critical | 2 | Non-critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | PPPI_MD_2611 | 0 | HLA0006271 | Master Recipe |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
IMGDUMMY | D - Dummy object | OS40 | PPPI_MD261 | Dummy object for transaction call from IMG |
History
Last changed by/on | SAP | 19981222 |
SAP Release Created in |