Controlling The Statistical Data Setup in INVCO: Symptom
Controlling The Statistical Data Setup in INVCO: Symptom
Controlling The Statistical Data Setup in INVCO: Symptom
Symptom
This note contains the instructions for installing program RMCBNEWD and its documentation.
RMCBNEWD is an auxiliary program for simplifying the control of the statistical data setup in the Inventory Controlling (INVCO).
For the statistical data setup, you require an "update-free" period during which the users logged on in the client must not edit any
material and accounting documents.This update-free period is necessary, not because of the program design but because of theoretical
reasons and is thus unavoidable.
RMCBNEWD was developed as a tool for the administrator and serves to keep the "update-free" period as short as possible in order to
help avoid operating errors by improving user guidance.
************************************************************************
It is necessary to import notes 554046 and 582168 after you install this note !!!
************************************************************************
Other Terms
RMCBNEUA, RMCBNEUB, RMCBNERP, INVCO, RMCBNEWD, info structure, statistical setup Inventory Controlling, S031, S032, S033, S034, S035,
oli1, oli2.
Solution
1. Installation
(only necessary when the R/3 Support Package status of your system is lower
than the R/3 Support Package specified for RMCBNEWD in the above list.)
a) Load the transport for note 518876 stored on the SAPSERV server pool onto your system. The name and the access path
are:
Release 3.1I:
/general/R3server/abap/note.0518876/rel_31i
K900679.U3I und R900679.U3I
Release 4.0B:
/general/R3server/abap/note.0518876/rel_40b
K901673.U4B und R901673.U4B
Release 4.5B:
/general/R3server/abap/note.0518876/rel_45b
K901284.U4D und R901284.U4D
Release 4.6B:
/general/R3server/abap/note.0518876/rel_46b
K902151.U9B und R902151.U9B
Release 4.6C:
/general/R3server/abap/note.0518876/rel_46c
K904364.U9C und R904364.U9C
Take into account the specifications in note 13719. The transport contains the following objects:ABAP program (including
text symbols and selection texts)
German
Reports RMCBNEWD and LMCB1F60 cannot yet be generated successfully after you have imported the transport.A generation error for these
objects in the transport log is therefore not an error. Only the import of the objects must be error-free.
b) Create function modules MCB_REBUILD_MM and MCB_REBUILD_FI in function group MCB1 (report SAPLMCB1). The short texts for
this are
Statistical data setup Material documents (for MCB_REBUILD_MM) and
Statistical data setup accounting documents (for MCB_REBUILD_FI).
Create the respective import/export parameter according to the declaration section in the correction instructions
mentioned below.
Remember that the functions are created in the named sequence (therefore MCB_REBUILD_MM first and then MCB_REBUILD_FI).It
is important that you store the functions in Includes LMCB1U10 and LMCB1U11.
To ensure this, you must implement the following repair in Releases 3.1I to 4.6B:
Start the Function Builder (transaction SE37) and select menu option "Utilities / Repair func.group".Enter MCB1 as the
function group and press Enter.Missing TFDIR entries are displayed in the following screen for the following 4 function
modules:
MCB_FILL_ALE_BCO,
MCB_UPDATE_BCO_FROM_IDOC,
MCB_UPD_V1_REVALUATION,
MCB_UPD_V2_REVALUATION.
Choose "Repair" and then "Delete" in the following screen.You can now display these function modules using transaction
SE37.Afterwards delete the listed function modules (also using transaction SE37). They are no longer needed.
If difficulties arise when you create the new functions, for example due to error message FL707 ("Function module name is
reserved for SAP"), you must generate the new modules by copying one of the functions that already exist in function group
MCB1, for example, MCB_UPDATE_S039.
c) Add field FLG_INI to structure RMCSNEUA by calling up transaction SE11 and by adding a field with the following
attributes to RMCSNEUA:
Component FLG_INI
Component type FLG_INI
Afterwards choose 'Save', check and activate the structure.
d) Insert the changes attached (except for ______________________ LMCB1F60 that is already contained in the SAPSERV
transport) into your system and activate all the newly created objects.In this case, it may be necessary to activate the
includes LMCB1TOP and LMCB1F60 first.Activate these objects also when (apparent) errors are displayed.
Afterwards, the activation of the function modules and report RMCBNEWD must then run with no errors.If the activation of
the function modules is error-free, you must carry out another attempt to activate includes LMCB1TOP and LMCB1F60 without
any error message ( <= mutually dependent).
You can start program RMCBNEWD interactively or schedule it as a batch job for background processing.In interactive operation,
instructions on use are supported by dialog boxes with detailed information on the progress of processing and the measures
required.Because of the required runtimes, interactive use of the program is normally limited however to test cases or the setup
of smaller datasets. Therefore, scheduling for background processing should be preferred in most cases for use in the production
system.
The program is intended exclusively for setting up version '000'.It corresponds to the procedure known as the "Procedure with
reduced update-free period" as described in note 79083. The programs described there should be used for partial set up or for
particular procedures that require work versions.
Interactive operation
2. In the "Info Structure Stocks" field, enter the names of all the info structures of type C (stock information structures, cf.
note 79083) that you want to set up.
3. In the "Info Structure Movements" field, enter the names of all the info structures of type "Standard" (movement info
structures) that you want to set up.
Take into account that in performance terms, it is generally better to combine all the info structures of applications 03 and 40
in one run of RMCBNEWD than in each case to execute the program separately for different info structures.
4. Select the "Delete version '000'" option for the first run of RMCBNEWD in any case so that the statistical data is not
distorted by data records left in version '000'.The option must then not be set under any circumstances if you want to execute
RMCBNEWD again to add to the data of other company codes.Otherwise the data of preceding runs would be lost.
5. Only use the "Delete / Create Indices" option in exceptions (cf. F1 help), however, it must not be set, if you are executing
several runs of RMCBNEWD in parallel.
6. The "Extraction structures BW" option is only used in systems with the plug-in for the Business Information Warehouse (BW).It
must be deactivated in all other systems.
7. In the subwindow "Movement Data Restriction", specify the company code whose data you want to set up.You can only specify a
single company code.If you want to analyze several company codes, you must call program RMCBNEWD several times.The program
independently determines the plants which belong to the specified company code.
8. The number of documents that are taken into account in the set up can be restricted via the posting date.It is possible here
to specify a single value or an area.
9. Now execute program RMCBNEWD (function key F8).Deal with the corresponding dialog boxes for the following steps.Confirm
warning messages M2221 "You are writing in the actual data" and M2336 "Data already exists in the version" that may be displayed
in the "Statistical setup from Stocks" window by pressing Enter.
2. In the "Info Structure Stocks" field, enter the names of all the info structures of type C (stock information structures, cf.
note 79083) that you want to set up.
3. In the "Info Structure Movements" field, enter the names of all the info structures of type "Standard" (movement info
structures) that you want to set up.
Take into account that in performance terms, it is generally better to combine all the info structures of applications 03 and 40
in one run of RMCBNEWD than in each case to schedule the program separately for different info structures.
4. Select the "Delete version '000'" option in any case for the batch job started first, so that the statistical data is not
distorted by data records left in version '000'.You must not set the option under any circumstances if you want to schedule
RMCBNEWD more than once to enhance the data of other company codes.Otherwise the data of preceding runs would be lost.
5. The "Delete / Create Indices" option should only be used in exceptions (cf. F1 help), it should not be set, however, if you
are scheduling several runs of RMCBNEWD in parallel.
6. The "Extraction structures BW" option is only used in systems with the plug-in for the Business Information Warehouse (BW).It
must be deactivated in all other systems.
7. Select the menu option "Program / Execute in Background" and schedule the program run for the time you require.
It is of course also possible for you to create variants for program RMCBNEWD and to use RMCBNEWD with these variants for the
definition of batch jobs.This way it is possible for you to ensure that several schedulings of RMCBNEWD are started one after
the other at the required interval for different company codes.
******************************************************************
IMPORTANT
Consecutive schedulings of RMCBNEWD may only be started if progress message M5710 "End of update-free period" has been generated
in each case in the job log of the preceding job.During the update-free period, RMCBNEWD locks tables MKPF and BKPF.Only one of
the parallel runs receives access authorization in ease case.The other runs are then cancelled if necessary with error message
M5714 "Processing terminated. Document tables could not be locked". canceled.
*******************************************************************
Manual Activities
Attributes
Key Value
Software Components
Software Component And subsequent
SAP_APPL
SAP_APPL
SAP_APPL
SAP_APPL
SAP_APPL
SAP_APPL
SAP_HR
Correction Instructions
Software Component Number of Correction Instructions
SAP_APPL 8
Support Package
Software Component Version Support Package