Ansicht
Dokumentation

RWMBONF0 - Update Business Volume From Ext. Data File, Supplier Reb. Arrangements

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Description

The reports RWMBONF0 (Transfer External Data) and RWMBONF1 (Create Test Data) are suitable tools for transferring data on the volume of business done with suppliers and rebate income from external systems into the SAP system.

They enable you to use the programs for "subsequent settlement" (end-of-period rebate settlement) even if you do not (yet) process your purchase orders, goods receipts, or incoming invoices using the SAP system. In particular, they allow you to transfer your old (or existing) data from system to system simply and easily.

Once you have set up the necessary rebate arrangements, you can import the supplier business data and rebate income to the system. On the basis of certain price determination data such as supplier, material, material group, etc., the system automatically determines the relevant rebate arrangement and condition records and updates the supplier business volume data.

Report RWMBONF0 serves the purpose of transferring (i.e. checking and updating) a data file with external supplier business volume data.

Report RWMBONF1 enables you to create any necessary test data. From the sub-program SIMULATION, you can see how the external data records have to be created.

See also "Transferring data from other systems" documentation.

Description of selection parameters

Note that F1 help is available for each parameter.

• Import external supplier business volume data from
  
  

Choose whether you wish to have the test data imported from the application server or from your front end (e.g. PC). Enter the relevant path and file names. When specifying the path, note that, depending on your system configuration, you can work on a different application server when you log on again. Specify a complete path otherwise data may be written to the installation directory of the SAP system.

• Updating
  
  

• Test run, no update
  
  

If you set this indicator, no database changes involving the LIS structures will be made. You can thus check which errors occur during processing. Before you have the external data entered, it is essential that you first carry out a test run and then process and remedy any errors that may be reported via error messages.

• Save under version
  
  

Specify the version under which the external data is to be entered in the LIS structures.

The actual data is contained in version '000' (test run before updating). For test purposes, you can have the data inputted to one of the versions beginnning with the characters '&'). The third character is optional. Other versions are not allowed.

You can use report RMCVISCP or the LIS Copy Management Tool to copy data between versions or delete data.

• Cancel update
  
  

If you set this indicator, the update (entry of the external data) will be cancelled (reversed). If an error that is relevant to updating should occur during the process of updating (adding data to) version '000' (actual data), it is essential that you cancel the update. Otherwise you must individually repost the relevant data record (separate external data file).

• Delimitation of rebate arrangements selected
  
  

As with all the reports of the "subsequent settlement" (end-of-period rebate settlement) function, you can narrow down the selection of the rebate arrangements to be processed.

• Control of program run
  
  

Each program run is assigned a name. If the run is prematurely terminated due to a timeout, the system records which rebate arrangements have already been processed - and which have not - under this name. This allows you to resume the execution of the program at any time (do not set "New run" indicator, use variant if necessary - see below).

If, in addition to the rebate arrangement numbers, you have entered further delimiting selection criteria, it is essential that you store the latter in a variant, since the system only saves the numbers of the arrangements that have not yet been processed.

Enter a termination date and time. If these limits are exceeded, the report will be terminated. You can continue processing the remaining, unprocessed rebate arrangements at a more suitable date later on with reference to the run name.

You can stipulate that all rebate arrangements are blocked (data consistency). Of course, this may not be desirable during processing in dialog mode. In addition, all rebate arrangements in the system (including those on the sales side, etc.) are blocked in such case.

Requirements

Enter/maintain the rebate arrangements in the system.

Do not fail to carry out a test run. Examine any error messages that are issued, and remedy problem sources. Analyze the update data.

Output

You obtain a log of all processed rebate arrangements together with any messages issued.

The report is designed to be interactive. To view the long text of a message, for example, you need only click on the message. Similarly, just click on the external data record number to view the record that caused the message to be issued.

From within the log you can display the update data generated for each rebate arrangement or condition record.

You can request a list of the external data records (individual record, complete list).

In addition, you can create and display an update log (LIS) for individual rebate arrangements. This enables you to check which information structures have been updated. In particular, you can also monitor the updating progress at field level.

PERFORM Short Reference   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 6324 Date: 20240601 Time: 044132     sap01-206 ( 123 ms )