|
Functionality
This method is used for reading planning data for costing-basedProfitability Analysis.
For this, the data source (summarization levels, the object level orline items) is selected automatically depending on which source isexpected to deliver the desired data most quickly. Summarization levelsare not locked against entry when data is read from them (this meansthat, if the summarization levels are updated at the same time as datais being read, inconsistencies can occur when the data is returned).
If data is read from line items, then the current structure is alwaystaken.
All characteristic values have an internal representation (for enteringthe selection criterion as well as in the table ResultData)!
The module is not suitable for reading mass data! If the selection isnot sufficiently reduced, the process can terminate due to longruntimes. If you need to read large amounts of data, you should choosethe appropriate selection criteria so that several callups areimplemented to read data on a package basis.
It is important that you watch for messages in the Return parameter. Example
From plan version "001", you wish to read the sales volume and therevenue for all products in division "01" and for the period "001.1999"through "012.1999". The planning data is posted to operating concern"S001" with record type "F" and currency type "B0" for costing-basedProfitability Analysis.
For this, the import parameters should be defined as follows:
OperatingConcern: S001
MaxRecords: 500 (for example)
Table SelectedFields:
FIELDNAME
PALEDGER
VRGAR
VERSI
PERIO
SPART
ARTNR
ABSMG_ME
ERLOS
ABSMG
Table Selection:
FIELDNAME|SIGN|OPTION|LOW |HIGH
PALEDGER |I |EQ |01 |
VRGAR |I |EQ |F |
VERSI |I |EQ |001 |
PERIO |I |BT |1999001 |1999012
SPART |I |EQ |01 |
Note: All values must be entered using internal representation. "01" isthe internal representation for currency type "B0", whereas "1999001"is the internal representation for period "001.1999".
Table ResultData is then filled with the planning data for twoproducts, for example, in the following way (if data were only found inthe period "001.1999"):
Table ResultData:
RECORD_ID|FIELDNAME|VALUE |CURRENCY
000001 |PALEDGER |01 |
000001 |VRGAR |F |
000001 |VERSI |001 |
000001 |PERIO |1999001 |
000001 |SPART |01 |
000001 |ARTNR |A1 |
000001 |ABSMG_ME |KG |
000001 |ERLOS |1000 |DEM
000001 |ABSMG |20 |
000002 |PALEDGER |01 |
000002 |VRGAR |F |
000002 |VERSI |001 |
000002 |PERIO |1999001 |
000002 |SPART |01 |
000002 |ARTNR |A2 |
000002 |ABSMG_ME |ST |
000002 |ERLOS |2000 |DEM
000002 |ABSMG |30 |
INCLUDE COPAQUERY_MAXRECORDS OBJECT DOKU ID TX Description
For information on the significance of the operating concern, see therelevant glossary definition:Operating concern.
INCLUDE COPAQUERY_FIELDLIST OBJECT DOKU ID TX
INCLUDE COPAQUERY_SELECTION OBJECT DOKU ID TX |