Ansicht
Dokumentation

RM06EEI1 - Transfer of Purchase Order History

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Description

This direct input program supplements the purchase orders created by the program RM06EEI0 with the purchase order history and the necessary accounting documents for the GR/IR clearing account.

As input, the program needs the sequential file you specified before running program RM06EEI0.

On the basis of the data specified in this file, the previously created purchase orders are updated as follows:

• The processing status of the message record is updated ('not processed' -> 'successfully processed')

• If the PO history for a PO item is to be updated (field: MBEPOI-WEREF), the following is done:

• The "delivery completed" or "final invoice" indicator is set in the PO item if specified

• The quantity delivered is updated in the PO schedule lines

• The final invoice indicator is updated in the account assignment data if specified

• The PO history with regard to GRs and IRs relating to the PO item is compiled

• If a PO history was compiled and the GR/IR clearing account is to be posted for this PO item (no delivery free of charge, GR allowed, no non-valuated GR), accounting documents are generated, which then serve to create the required open items on the GR/IR clearing account. For further information on the calculation of the open item amounts, and the different characteristic values of field MBEPOI-WEREF, please refer to the Implementation Guide. If a business area can be derived from the account assignment data of the PO item or the material division, this business area is also noted in the posting lines of the GR/IR clearing account. The contra entry is generally effected without the business area in balance sheet transfer accounts. The accounting document number can be taken from the "material document" field in the relevant PO history record.

Program parameters

You can define the following parameters on the initial screen:

• File name: please enter the logical file name under which the sequential file can be accessed.

• Update or test run: with these parameters you specify whether or not the program is to be run in test mode only. If you specify the test mode, all the data transfer checks are carried out without the database being updated. Please note that in test mode it is not possible to carry out a check as to whether the accounting documents have been created correctly. If you decide on the update run, the POs and accounting documents will be added to the database if found to be satisfactory following checking.

• G/L accounts: via these parameters you specify the accounts for the generation of the accounting documents. Please note that all accounting documents generated will generally be posted to these accounts. For performance reasons, the program does not carry out an automatic account determination process for the GR/IR clearing account. Accordingly, you should first check whether the clearing account entered as a parameter agrees with the account that was determined within the framework of account determination in productive operation.

• Document types: with these parameters, you specify the document types for the generation of the accounting documents.

• Scope of log: with these parameters, you specify whether or not you wish to have a detailed output of error messages for each PO item with error identification and short error text.

Requirements

The purchase orders must have been transferred without errors via program RM06EEI0 using the same sequential file.

Output

The program log contains:

• Program statistics (start, end, number of records read etc.)

• A listing of the numbers of the updated POs

• A listing of the numbers of POs that were not updated (faulty POs)

• A listing of the numbers of POs already updated (in the event of a restart)

The detailed error log per PO item supplements this, provided you have activated the output of this log via the relevant program parameter.

This latter log contains:

• PO number

• PO item

• Message class

• Error category

• Error number

• Error short text

Check

The following checks are made:

• Does the PO to be updated exist in the system?

• Was it possible to determine a business area on the basis of the division to which the material was assigned?

• Was it possible to create the necessary accounting documents?

• Was it possible to successfully update the purchase order in the database?

The accounting documents are created and the PO updated when all PO items have been checked and found to be satisfactory (DB commit).

Technical information

The program allows restarting at the existing sequential file. A check is made as to whether the PO history (EKBE) already exists in the system. If so, the purchase order is not updated again.

A database commit is initiated after each error-free updating of a purchase order.

Depending on the number of PO items to be transferred and the associated run-time of program RM06EEI0, you are advised to carry out a database back-up between the running of program RM06EEI0 and the running of program RM06EEI1 in order to be able to recreate the status subsequent to the execution of program RM06EEI0 in the event that unforeseen problems should arise while RM06EEI1 is running.

Reset programs for automatically updated POs and the accounting documents created are currently not available.

By means of the appropriate organizational measures, please ensure that the POs created by program RM06EEI0 are not changed manually prior to the successful running of program RM06EEI1. Inconsistencies cannot otherwise be ruled out.

For performance reasons, no SAP blocking logic (ENQUEUE/DEQUEUE) has been implemented in the case of program RM06EEI1. Accordingly, you must take the appropriate organizational measures to ensure that no user is able to make changes to the already created POs while the program is running. Inconsistencies cannot otherwise be ruled out.

The program run-time depends largely on your installation, your organization structure, and the quantity structure of your master and transaction data.

As a rough estimate, however, it can be assumed that approx. 1000 PO items per hour can be handled.

CPI1466 during Backup   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7400 Date: 20240520 Time: 095254     sap01-206 ( 131 ms )