FAQ: Data transfer (Batch Input) in Purchasing
Ques: Where can you find detailed information about batch input?
Answer:You can find the corresponding documentation in the SAP Library under: Cross-Application Components -> CA Data Transfer -> Data Transfer Workbench -> Data Transfer Objects after Application -> MM - Material Management.
More information is available in the IMG documentation: Purchasing (Transaction OLME) -> Data Transfer, and also in the program documentation for the reports specified there.
Also see the following notes:
502213 - Additional infos for data transfer of purchase orders.
554139 - FAQ 2: Batch input
638362 - FAQ: Data transfer in the service
Ques: Why may the system display an error message telling you to fill all required fields when you process a batch input session even though all the fields in the session are filled?
Answer: See Note 301968.
Ques: Why can you not use Transactions ME21N and ME51N for batch input?
Answer: This is not possible due to technical reasons. Use Transactions ME21 and ME51 or the corresponding BAPIs. For further information, see also Notes 381630 and 217437.
Ques: During batch input for purchasing transactions (ME21, ME22, ME27, ...), the system does not transfer data correctly (only in background processing) for item detail screens or the data is transferred to an incorrect item. How can you avoid this?
Answer: See Note 9966.
Ques: When you process a batch input session for purchase orders, the system issues error message 00 344 "No batch input data for screen SAPLSPO1 300". How can you avoid this?
Answer: See Note 69382.
Ques: You are using the INFREC IDoc (function module IDOC_INPUT_INFREC) and not the RM06IBI0 report to transfer purchasing info records. Why does this lead to problems that do not occur when you are using batch input?
Answer: For the restrictions regarding the data transfer using the INFREC IDoc, see Note 327083.
Ques: An error occurs each time you process a CATT for changing an outline agreement a second time because the program accesses the item detail screen instead of the item overview. How can you avoid this?
Answer: See Note 481268.
Ques: During batch input of the purchasing info records, the system issues error message VK 024: "Table 017 is not defined for use with condition type RA01". How can you avoid this?
Answer:See Note 41127.
Ques: When you execute the RM06IBI0 report, the system issues error message 06 312: "Purchasing info record & & & & already exists". How can you avoid this?
Answer:See Note 206905.
Ques: When using the reports RM06EEEX and RM06EEI0Is to transfer purchase orders, can you also transfer the foreign trade data?
Answer:There are restrictions regarding the transfer of foreign trade data. Refer to the MBEPOH and MBEPOI transfer structures to find out which fields you can transfer.
Ques: When you use Transaction ME21 to create a purchase order in batch input, the address check may issue an error message (R5 510). How can you create the purchase order despite this?
Answer: You can use the EXIT_SAPLSZAR_001 user exit to deactivate the address check in certain situations. If you never want to carry out an address check during batch input, you can call up the 'sy-binpt' field, which is always set to 'X' for the batch input.
Ques: Why may online processing of a batch input session differ from background processing?
Answer: See Note 33319.
Ques: How can you supply a confirmation dialog box in batch input?
Answer: See Note 13882.
Ques: How can you continue processing a session with the status "In process"?
Answer: See Note 12222.
Ques: Which special features are there for custom tariff preference data in the purchasing info record?
Answer: You can transfer plant-specific purchasing info records by batch input to a limited extent only. The same occurs for the online transaction (ME11/ME12: Create/Change info record). If the info record is plant-specific, the Plant (LFEI-WERKS) and Preference zone (LFEI-GZOLX) fields in Transactions ME11/ME12 (screen SAPLLFEI-0100) are not ready for input and error message 00 347 appears when you import the folder:
"Field ... is not an input field"
You can create examples for correct BTCI data (customs preference) using the BTCI recorder (SHDB).
Ques: Does the RM06EEI1 report transfer delivery costs?
Answer: The RM06EEI1 report does not transfer delivery costs (table EKBZ).
If you want to transfer delivery costs, you must create a new purchase order using the remaining open quantity.
The original purchase order should then be closed in the legacy system (by posting the remaining goods movements,..).
Ques: Can you transfer purchase order histories if the material ledger is active?
Answer: You cannot transfer purchase order histories to target systems in which the material ledger is activated. If required, contact Development Support for material ledgers (component CO-PC-ACT).