Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
ME0C (Package) Customizing R/3 Purchasing
IMG Activity
| ID | SIMG_CFMENUOLMEOMHK | Implement Data Transfer: Purchase Requisition |
| Transaction Code | S_ALR_87002057 | IMG Activity: SIMG_CFMENUOLMEOMHK |
| Created on | 19981222 | |
| Customizing Attributes | SIMG_CFMENUOLMEOMHK | Implement Data Transfer: Purchase Requisition |
| Customizing Activity | SIMG_CFMENUOLMEOMHK | Implement Data Transfer: Purchase Requisition |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | SIMG_CFMENUOLMEOMHK |
In this step, you generate batch input sessions for purchase requisitions.
The batch input sessions must then be run in the system in a second step.
If you set the indicator Check file only, no session will be created. The system will only check whether the sequential file has been compiled correctly.
Preconditions
You must provide the report with the data to be processed.
Using a program external to the SAP System, you must store the production data to be transferred in a sequential file in a directory at operating system level.
Standard settings
In the standard SAP R/3 System, the following file in the following directory is suggested for the purposes of importing the data:
Logical file name: MM_PURCHASING_REQUISITIONS
Physical file name: /usr/sap/trans/data/mmrequisitions
Actions
- Enter the name of the sequential file into which you have imported your data from the old system.
- Generate a batch input session.
- Run this batch input session.
- Test the transferred data.
For further information, refer to the report documentation.
Note
When running report RM06BBI0, you can specify two parameters:
- the maximum number of items that a purchase requisition is to contain
- the maximum number of transactions that a batch input session is to contain
For example: you can distribute 1000 items that are to be transferred as follows:
Each requisition is to contain 10 items (that is, 100 requisitions will be generated). A batch input session should contain not more than 20 functions (that is, purchase requisitions). You thus obtain 5 batch input sessions.
Business Attributes
| ASAP Roadmap ID | 254 | Transfer Data |
| 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 | SIMG_CFMENUOLMEOMHK | 1 | HLA0006039 | Purchase Requisitions |
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 | OMHK | 255 | Batch Input, Purchase Requisitions |
History
| Last changed by/on | SAP | 19981222 |
| SAP Release Created in |
