SAP OSS Notes: 2/20/11

26.2.11

SAP Note 23759 - Field overflow in SOP - transfer to Demand Management

Symptom:

When data is transferred from SOP to master production scheduling, terminations can occur if large key figures are to be transferred. These terminations occur in the area indicated k004125 below of Include LMCP2U01. In release 3.0, it is in includes LMCP2U40 and LMCP2U41 instead.
This program code rounds off places after the decimal point according to the specifications in the unit table (field: T006-ANDEC).
Transactions concerned: MC74 and MC75.
If the field overflows, rounding errors may occur in the transferred data.

Cause and prerequisites

1. The auxiliary fields were defined too small.
2. The value in field T006-ANDEC of table T006 is too large (for example, 99).

Solution
1. Korrektur P22K007632:
*k004125***********************Rundung der Übergabewerte
DATA: PT_HLP_MENGE_MIN_REST(16) TYPE P, "change
PT_HLP_MENGE_RUNDUNG(16) TYPE P DECIMALS 0, "change
PT_HLP_MENGE_GERUND(16) TYPE P, "change
PT_HLP_FAKTOR TYPE I,
PT_HLP_REST(16) TYPE P, "change
...
2. Change the unit table

SAP Note 23758 - Docu error: Obj. type 'ORH' only for PP order header

Symptom:

When allocating a status profile defined by the user to the object types of the general status management (transactions OIBS and BS13), it is not clear whether the object type ORI = 'Maintenance order' or the object type ORH = 'PP, PM: Order header' is to be used for the maintenance order.

Cause and prerequisites

Documentation error

Solution
Object type ORH only applies to the PP order. Thus, ORI is to be used for the maintenance order/plant maintenance order.

SAP Note 23754 - Exclusive lockwaits for table display SE16

Symptom:

If several users in the SAP system want to display the contents of a table (for example BSEG) via transaction SE16, exclusive lockwaits can occur on table D010LINF, with the result that one user has to wait for another. This can also occur if two users want to display different tables at the same time.

Cause and prerequisites

When you execute transaction SE16, an update lock is set up in table D010LINF on the generic ABAP/4 programs 'RSLOCK01', 'RSLOCK02' and so on. Due to an index access to table D010LINF that is not fully classified when executing transaction SE16, wait situations (exclusive lockwaits) can occur, so that one session must wait until the other one releases the update lock again.

Solution
Download the newest version of the script 'D010LINF.SH.23754' from sapservX.

This script is stored on sapservX in the directory '/general/3rdparty/informix/ddic', with the name 'D010LINF.SH.23754'.

Stop the R/3 System (stopsap r3) and execute the script; An informix specific index is created on table D010LINF.

SAP Note 23753 - Copy plan versions without orders for the project

Symptom:

In Project system, when you perform the functions
"Copy plan version--> costs" (CJ9B) and
"Copy plan version--> revenues" (CJ9C)
only the values planned directly on the WBS elements are copied.
The planning values of orders or networks for the project are not taken into account when copying.

Cause and prerequisites

Function not supported in R/3-3.0.

Solution
This function is planned for a later release.
If only CO orders are allocated to the project, the corresponding copy function in the CO orders application can be used in R/3-3.0.

SAP Note 23751 - GEN_STRUCTURE_STACK_OVERFLOW for posting

Symptom:

1. The runtime error GEN_STRUCTURE_STACK_OVERFLOW occurs in the case of a posting.

2. When you maintain a validation, a substitution or rule, the error GB018 ('Boolean statement not complete') is generated. Cause and prerequisites

1. The name of the program that caused the runtime error is:

a) up to Release 3.0: FGBB2mmm and FGBB3mmm where mmm stands for the client.

b) as of Release 3.0: GBTmmaa0 where mm stands for a two-digit encryption of the client and aa for the respective component (for example, FI, CO, AM, PC, GS, GL). To identify the client, use Transaction SE37. Enter 'G_CLIENT_DECODE' as function module and press the 'Sngl.test' pushbutton. In the following screen, enter the two-digit encryption of the client in input field 'MM' and choose 'Execute' (F8). In the following screen, the system displays the unencrypted client in export parameter 'MMM'.

Too many conditions linked by logical operators (AND, OR, --> or <-->) were used in a substitution, validation or rule. The generated source code thus has a too deep IF ... ENDIF nesting.

2. The condition, which you try to maintain is too long. There is a defined limit which is about 33 lines. The program disregards everything which exceeds this limit. Solution
Try to group several conditions together to a rule since this reduces the nesting depth of the IF ... ENDIF structures.

Example:

original rule: OR OR AND AND AND
( ... are placeholders for simple conditions)

This can be split into two or morel rules:

splited rule : &SR1 AND &SR2
where : SR1 = OR OR
SR2 = AND AND

Rules SR1 and SR2 are maintained with Transaction GCVZ.

If the complex condition contains field literal comparisons like those the following, it can be simplified by using sets:

$Field = 'Constant_1' or

$Field = 'Constant_2' or

$Field = 'Constant_3' or ... (Release < 4.0A)

Table-Field = 'Constant_1' or
Table-Field = 'Constant_2' or
Table-Field = 'Constant_3' or ... (Release >= 4.0A)

In this case, you can create a set in Transaction GS01 for the field 'Table field' that contains the values 'Constant_1', 'Constant_2', 'Constant_3' and so on. The sequence can then be replaced by an easy set validation - this also improves the performance.

If runtime error GEN_STRUCTURE_STACK_OVERFLOW occurs after you replace or split all complex conditions, execute program RGUGBR00. Check all parameters except for 'Gen.substn routns in all clnts'.

Additional key words

FB01, GGB0, GGB1, GBT

SAP Note 23743 - Negat. list decl. bal. of asset acct det. grp asset

Symptom:

The group asset became available with Release 3.0.
At present, the depreciation determined on the group asset cannot be distributed onto the allocated individual assets.

Solution
A solution within reporting is planned with Release 3.0.

SAP Note 23741 - Quantity management negative list in fixed assets

Symptom:

In Asset Accounting, the following functions are not possible with reference to a quantity management:

Settlement of orders or projects with quantity for investment measure with line item settlement. As of Release 4.5, a quantity settlement is possible for summary settlement (see Note 337476)

Asset balance update from Materials Management

Quantity grid

For negative assets, the quantity is not updated during the first acquisition posting in the asset master record.

Solution
Use transaction AS02 to maintain the quantity manually in the fixed asset.

SAP Note 23740 - Negative list: Variable lease payments

Symptom:

You cannot manage non-periodic lease payments (such as special payments) or changes to lease payments during the life of the leasing agreement.

Further negative points include:

No flexible installments.

Down payments/final settlements are not taken into account.

Posting to vendor account occurs for area 01 only.

Opening entries with affiliated company are not possible.

Posting the interest paid occurs for area 01 only.

Tax is not taken into account when the posting to vendor account is created.

The installment allocation to interest and repayment portions is executed using the depreciation key.

No different capitalization amounts (capitalization with the present value).

The useful life and contract duration must correspond. Changes during the life of the leasing agreement are not possible.

The contract start date, depreciation start date and interest start date must correspond and must not be in a future fiscal year.

The purchase price option is taken into account for the calculation of the present value.

The scrap value is not taken into account for the calculation of the present value.

Shutdown periods are not taken into account.

The "new depreciation calculation" is not used in combination with the leasing function. If the present value is determined in the asset master record, the logic of the old depreciation calculation is used.

The leasing start date must be at the start of the month. The system calculates from the start of the month even if another leasing start date is selected.

Partial transfer of a leased asset

In general, no value adjustment is determined for interest for intracompany transfers. For the issuing fixed asset, this means that interest on the retirement is determined from the relationship of the transfer posting amount to the entire APC. No prior year acquisitions are determined for interest.

However, the proportion of interest for target assets is newly determined according to the settings of the depreciation key. In almost all cases, there may therefore be differences when comparing the interest for the issuing transfer with the interest for the acquiring transfer.

SAP does not recommend partial transfers, but instead canceling the original acquisition, and activating the individual assets separately.

Other terms

Leasing, LEAS, negative list, LZINS

Reason and Prerequisites

Solution
You can use a new fixed asset for changes to regular payments during the life of the leasing agreement. In the case of fixed assets with the capital lease method, you must perform a retirement on the previous fixed asset beforehand (this procedure is described in the user guide).
Important: There may be differences between the cash value calculations and the display on a fixed asset (which is not possible).

SAP Note 23736 - Negative list : Indexing during the fiscal year

Symptom:

The indexing within Asset Accounting presently only works on an annual basis, that is, a monthly or quarterly indexing is not possible.

Solution
Up to now, this indexing was only implemented for the Argentinian version. The indexing was determined with a specific table in an additional program and reported as manual revaluation to Asset Accounting.
At this time no plans exist for additional coutry-specific versions.

SAP Note 23735 - WBS proposal from header, no profit center

Symptom:

If a WBS element is entered in the order header in account assignment, this is taken into account during the account assignment of items entered afterwards. However, the profit center is not extended. The profit center is only updated if you "access" the WBS number in the individual items.

Cause and prerequisites

Missing proposal

Solution
The following advance correction can be made as of 2.2B:
Program fv45pfap, form vbap_fuellen:

...
* Bedarfsdaten ermitteln
PERFORM VBAP_FUELLEN_T459K.
* Daten aus der Hauptposition, auch Kontierung
PERFORM VBAP_FUELLEN_HVBAP.

>>>> Begin of correction, insert the following lines:
* Bei Projektkontierung wird das Profitcenter aus dem PSP vorgeschlagen
if vbap-kzvbr = kzvbr_p and
not vbap-ps_psp_pnr is initial.

call function 'CJPN_PROJECT_ACCOUNT'
exporting
int_num = vbap-ps_psp_pnr
importing
e_prctr = vbap-prctr
exceptions
others = 1.
endif.
>>>> not changed: <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

* Bei Bedarfserfassung kommt die Mengeneinheit aus MT61D(MAEPV),
* weil MAAPV nicht genutzt wird.
PERFORM VBAP-UMZIZ_ERMITTELN.
PERFORM VBAP-UMVKZ_ERMITTELN.
...
...

SAP Note 23734 - Negative list : Subdivision of acquisition costs

Symptom:

A subdivision of acquisition and production costs (APC), for example, according to acquisition years or original costs is not possible.

Solution
You can use subnumbers in the system for the subdivision according acquisition years.
In this case, you can use a depreciation key for the fixed assets in question which does not allow an acquisition according to the acquisition year.

SAP Note 23732 - Negative list : Different period versions

Symptom:

Can a fiscal year variant (other than the one in the General Ledger) be used in one or more depreciation areas?

Cause and prerequisites

The reasons for this might include:

The company is a member of a corporate group: the group has a different fisal year.

Fixed tax year: the tax year is the calendar year (for example) and is different from the fiscal year of the company code.

Solution

The fundamental rule is, you specify the fiscal year variant for the company code centrally in the FI General Ledger. In Asset Accounting, you can define an alternative fiscal year variant (version) for all depreciation areas. However, the first and last day of the fiscal year for this fiscal year variant must be the same as the first and last day of the fiscal year variant in the General Ledger.
You can define and use your own fiscal year variant in depreciation areas starting in maintenance level 3.0C, but the first and last day of your fiscal year variant must agree with the General Ledger variant.
Reports for a specific date (for example, an asset list) are possible with this functionality, but not reports on a period of time (for example, an asset history sheet).
There are two possible workaround solutions. Use the follwing as an example: Assume that the fiscal year in depreciation area 01 goes from January 1 to December 31. The desired fiscal year for reporting goes from October 1 of year X to September 30 of year X+1.

1. Solution using additional reports:

a) Run a report for September 30 of year X (for example, 1997).

b) Run a report for December 31 of year X (for example, 1997).

c) Run a report for September 30 of year X+1 (for example, 1998).

d) Load all of these reports into EXCEL or a similar tool and calculate the differences using that tool.

Additional key words

Period version

SAPNote 23731 - CJ40: Only one WBS element in cost element planning

Symptom:

When you access cost element planning (primary costs KPP2 and activity input KPR2) via the work breakdown structure (CJ40/CJ41), and after executing function 'Swap dimensions...', only one element is displayed the 'Dimension WBS elements' screen, even though you selected several WBS elements in the structure.

Cause and prerequisites

The branch from the WBS to cost element planning always refers to the
first of the selected WBS elements, since groups of WBS elements cannot
be set up. Consequently, only the one WBS element is displayed when you execute 'Swap dimensions...'.

Solution
You need to plan the WBS elements of a WBS separately.

SAP Note 23729 - FB01/FBZ1/FB05: Mess. KI235, e.g. for bank charges

Symptom:

The message KI235 appears for incoming payment with bank charges (account does not contain a cost center-relevant account assignment).
Key words: FBZ1 KI235 SAPLRKIP K_COBL_CHECK

Cause and prerequisites

No default account assignments maintained in tables TKA3A, TKA3B.

Solution
Configuration menu Controlling - Cost center accounting - actual postings - Autom. account assignment (transaction OKB9): Define default account assignments.

SAP Note 23727 - Incomplete transfer of default values T159B

Symptom:

When creating batch input sessions BTCI, the default value 'Including inventoried batches' from table T159B is not transferred for the following transactions/reports:

MI31 / RM07II31
MIK1 / RM07IK31
MIE1 / RM07IE31
MIO1 / RM07IO31
MIV1 / RM07IV31 -> RM07IVW1
MIW1 / RM07IW31 -> RM07IVW1
MIQ1 / RM07IQ31 (only > 2.1)
MIM1 / RM07IM31 (only > 2.1)

Cause and prerequisites

The transfer of field T159B-XICHA is missing in module RM07IBDC.

Solution
Editor SE38 -> MODUL RM07Ixxx -> for Release 2.1* where xxx stands for the respective program under 'Sysmtom'.
Editor SE38 -> MODUL RM07IBDC -> approx. line 2190 for Release 2.2*/3.0*

SAP Note 23723 - Creating WBS from a ref. does not copy plan.values

Symptom:

When you create a work breakdown structure (WBS) from a reference (CJ01), in other words by copying a WBS, the cost/revenue plan values of the reference are not copied.

Cause and prerequisites

This function is not available in R/3-3.0.

Solution
The created WBS must be planned again.

SAP Note 23718 - Generation of an incorrect matchcode

Symptom:

After an information structure generation, the required matchcode is not created on the selection screen of the respective standard analysis. Instead, a different matchcode is generated. For example, in some cases, the matchcode for quotations is processed instead of the matchcode for orders, if the sales order number is a characteristic of the information structure.

Other terms

Matchcode, info structure, F4, input help, search help, standard analysis

Reason and Prerequisites

The matchcode object is not always unique, a dialog to choose the required matchcode object is not supported.

Solution
You can force the required matchcode object by the following modification in the module for determining the matchcode object. Please note that this matchcode object then becomes effective for all information structure fields with this check table (in the above example VBAK). That is, in the example, the matchcode is also processed for orders, if quotations are meant.
Insert an entry in the include LV12BU02 in the CASE query:
CONDENSE TAB_FELD NO-GAPS.
CASE TAB_FELD.
WHEN 'XXXXYYYYY'. "<------ new
MATCHCODE_FOUND = 'X'. "<------ new
MCD_MATCHCODE = 'ZZZZ'. "<------ new
WHEN 'MARAMATNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MAT1'.
WHEN 'KNA1KUNNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'DEBI'.
WHEN 'MCHACHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'MCH1CHARG'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'MCH1'.
WHEN 'LFA1LIFNR'.
MATCHCODE_FOUND = 'X'.
MCD_MATCHCODE = 'KRED'.
WHEN OTHERS.
* MC-Datei finden
SELECT * FROM DD27S
Where: 'XXXX' is the name of the check table (example: VBAK)
'YYYYY' is the name of the check table field against which the checks are run (example: VBELN)
'ZZZZ' is the name of the matchcode object which should be forced (example: VMVA)
Generate program SAPLV12B.
Regenerate the standard analyses and planning screens using the report RMCSISGE (or RMCSISGN).

SAP Note 23716 - Missing fields in transfer structure BALTD

Symptom:

Depending on the Release, asset table fields (for example, the tax jurisdiction TXJCD) are missing in the internal structure BALTD.
Key words: Transfer structure, RAALTD01, RAALTD11

Cause and prerequisites

Incorrect delivery.

Solution
How can these fields be included in the structure?
Program RAALTD01 or RAALTD11 (as of Release 2.2) can generally process enhancements or reductions in the interface structure.
The customer can therefore insert a missing field at any appropriate position without requiring a program change.
You cannot tranfer the fields of ANLU.

SAP Note 23704 - No standard F4 help on 'Reason of movement'

Symptom:

There is no standard F4 help available for field 'Reason of movement'.

Cause and prerequisites

There is still an old help function module implement for the event .

Solution
Make the following changes to the flow logic of screens SAPMM07M 0210, 0310 and 0410 with SE51 and regenerate the screens:
PROCESS ON VALUE-REQUEST.
FIELD MSEG-GRUND MODULE GRUND_HILFE. 'OLD
* FIELD MSEG-GRUND MODULE GRUND_HILFE. 'NEW
*eject
As a result, MODUL GRUND_HILFE is no longer called and the standard F4 help is available.

SAP Note 23697 - Problem with ABAP/4 statement "call system"

Symptom:

ABAP/4 statement "call 'SYSTEM'" supplied in version 2.2D+ Status -1 in SYST-SUBRC.

Cause and prerequisites

Oracle libraries use 'SIGCHLD'.

Solution

In some Oracle releases, the runtime environment supports the signal 'SIGCHLD' and clears the exit status of all scheduled processes.
On the other hand, the pclose called by the kernel for the ABAP/4 statement "call 'SYSTEM'" expects the process to deliver its exit code. Pclose provides an error (-1) which is returned by the kernel to ABAP/4. Errno ECHILD occurs internally. The problem appears in different versions on different platforms. It also depends on the access mode in the database (in one system, it can sometimes occur only on a couple of application servers).

A general solution is not possible. "call system" should not be used and is not released by SAP for customer applications.

The following implementation approaches are possible:

1. Avoid supported and documented calls, as, for example, CPIC, RFC and external batch.

2. Furthermore, if "call system" should be used: Do not call up the return code and document the successful exit in the standard output.

3. Since the problem occurs only when connections to BEQUEATH are made, doing the work in TWO_TASK mode (TCP/IP) creates the possibility of limiting the creation of 'ZOMBIE' processes.

SAP Note 23694 - RFVBER00: Termination CONNE_IMPORT_WRONG_COMP_LENG

Symptom:

RFVBER00 terminates with runtime error CONNE_IMPORT_WRONG_COMP_LENG.

Cause and prerequisites

Update terminations from former releases are still in the system, the document structures have been extended in the meantime (BSEG was extended) so that the IMPORT of the old data no longer fits to the new structures.

Solution
None.
In RFVBER00, only select the data from the current release in RFVBER00.
Generally, update terminations should be checked, updated and deleted on a daily basis using transaction SM13.

SAP Note 23690 - Special characters in keys (names)

Symptom:

When you use unsuited special characters in keys, problems can occur during the database access or matchcode search. This particularly applies to the project numbers of the work breakdown structure (WBS), project definition and WBS element. However, you should also avoid the special characters in other keys, for example, network (during external number assignment) or PS text.

Cause and prerequisites

The special characters are interpreted by the database system or basis system and have a special meaning there (see "Solution")

Solution

Please avoid the following special characters in keys:

. Period is used as a field separation character during the matchcode search.

* Asterisk is in certain cases interpreted as a mask (wildcard).

? Question mark is in certain cases interpreted as a mask (wildcard).

% Percent is interpreted as a mask (wildcard) by the DB system for as many characters as desired.

_ Underscore is interpreted as a mask (wildcard) by the DB system for an individual character.

SAP Note 23688 - PA-TRV: customer enhancement screen, user data

Symptom:

In PR01 (Maintain trip data) a customer wants to use the user data
screen. However, there is no documentation on this.

Cause and prerequisites

In 2.1 and 2.2, the documentation can be called up using 'Extended
help'. As of 3.0, you should read CHAP.REIS9999 in RPDSYS00.

Solution
The documentation reads as follows:

Customer enhancement screen
-------------------------
In HR-TRV, it is easy to create an individual screen which meets the
specific requirements of your company.

The internal table USER can be used for this purpose. This table is
written to the database by the standard SAP programs and read there.
This table can be modified by users: it has been specially devised for
applications particular to individual customers.

To do this, you will need to have basic knowledge of the SAP
development environment. This includes knowledge of ABAP/4, DDIC,
Screenpainter.
In this way, you can enter information which can be used again and again (ranging from the reports of sales reps. in the pharmaceutical and insurance industries) to facts determined with regard to customer- specific subsequent systems.

Example: services that can be billed to customers.

SAP Note 23687 - MMBE: GR blocked stock

Symptom:

The stock overview (transaction MMBE) displays the GR blocked stock. This stock is calculated from the total of all goods receipts for purchase orders into GR blocked stock of this material (movement types 103 and 106) for which the transfer into the own stock or the return delivery to the vendor (movement types 105 and 104) was not yet entered. In this case, only those order items are considered whose goods receipt to the stock is to be posted to the material master. No special stocks are considered except for the vendor consignment stock.

Cause and prerequisites

This function is defined this way. The GR blocked stock should contain the stock quantity which can be used without restrictions after its release.

Solution
If the GR blocked stock is to be calculated differently, a modification is required.

SAPNote 23676 - Terms of payment in billing document: Output your own texts

Symptom:

With this modification, it is possible to output your own texts instead of the terms of payment texts generated from table T052.

Cause and prerequisites

Modification
Consider attached Note 170183.

Solution

1. Entering your own text:

Transaction SO10

Text name z.B. ZB01 (Text name should be 'TermsOfPaymentKey')

Text ID SDTP

Language, for example D

Create function key

Enter and save text

2. Form for billing document printout (standard: RVINVOICE01) change:

Transaction SE71

Form, for example, RVINVOICE01

Language, for example D

Change function key

Goto - Window

Choose TERMS

Edit - Text elements

CN requirements /: IF NE 'O'. (*)
AS
/
/
/: ELSE. "neu
/: INCLUDE OBJECT TEXT ID SDTP PARAGRAPH AS "neu
/: ENDIF.
AS ,,

--> The IF Statement in line (*) must be adjusted in such a way that the program reaches the ELSE statement and consequently prints the term of payment you entered.

SAP Note 23667 - Account no. print wrong with summarization 3

Symptom:

When summarization level 3 is used in the balance interest calculation for G/L accounts, only one account number is displayed per page.

Cause and prerequisites

Program error

Solution
Insert the lines marked with "S11KQQQQ below in progrma RFSZIS00
.
.
.
AT NEW SKA1-SAKNR.
*---------------------------------------------------------------------*
* Gruppenanfangsverarbeitung: Konto *
* Initialisierungen pro Konto *
*---------------------------------------------------------------------*
CHECK GUELTIGER-BUKR-FLAG = 'X'.
CHECK GUELTIGES-VZSKZ-FLAG = 'X'.
FORMAT RESET.
IF VD-STUFE < '3'.
NEW-PAGE.
BLATTNRP = 0.
ELSE. "S11KQQQQ
FORMAT COLOR COL_NORMAL INTENSIFIED. "S11KQQQQ
WRITE: / SY-VLINE, 2 SKB1-BUKRS, "S11KQQQQ
7 WAVZSKZ, "S11KQQQQ
18 WAWAERS, "S11KQQQQ
24 SKA1-SAKNR, "S11KQQQQ
36 SKAT-TXT20, 81 SY-VLINE. "S11KQQQQ
WRITE: / SY-VLINE, TEXT-036, PRINTVZUNTER DD/MM/YYYY, "S11KQQQQ

TEXT-002, PRINTVZOBER DD/MM/YYYY, 81 SY-VLINE. "S11KQQQQ
SKIP 1. "S11KQQQQ
WRITE: / SY-VLINE, 81 SY-VLINE."S11KQQQQ
"S11KQQQQ

ENDIF.

PERFORM DEBUGGING-CHECK1. "pruefen ob Konto zu debuggen ist
PERFORM DEBUGGING-MODE USING '0490'. "Konto wird bearbeitet
.
.
.
Insert the lines marked with "S11KQQQQ below in program RFSZIS01, subroutine UEBERSCHRIFT_FZ
FORM UEBERSCHRIFT_FZ.
.
.
.
CASE PRINT_STATUS.
WHEN '1'. " POSTENUEBERSCHRIFTEN
FORMAT COLOR COL_HEADING INTENSIFIED.
WRITE: / TEXT-100.
ULINE.
IF VD-STUFE < '3'. "S11KQQQQ
FORMAT COLOR COL_NORMAL INTENSIFIED.
WRITE: / SY-VLINE, 2 SKB1-BUKRS,
7 WAVZSKZ,
18 WAWAERS,
24 SKA1-SAKNR,
36 SKAT-TXT20, 81 SY-VLINE.
WRITE: / SY-VLINE, TEXT-036, PRINTVZUNTER DD/MM/YYYY,
TEXT-002, PRINTVZOBER DD/MM/YYYY, 81 SY-VLINE.
SKIP 1.
WRITE: / SY-VLINE, 81 SY-VLINE.
ULINE.
ENDIF. "S11KQQQQ
FORMAT COLOR COL_HEADING INTENSIFIED OFF.
.
.
.

25.2.11

SAP Note 23666 - Negative list: Asset types/classification

Symptom:

Fixed assets are currently classified in asset classes from a business point-of-view. Classification from a technical point-of-view (for example, according to types of objects) or an interface to the SAP classification is not provided.

Additional key words

Class, asset, material class

Cause and prerequisites

Solution
*

SAP Note 23663 - Negative list: Takeover of historical transactions

Symptom:

During old assets data takeover into Asset Accounting, no historical transactions can be entered.

Cause and prerequisites
Solution

There are no current development plans for this.

Additional key words

AS91, RAALTD01, RAALTD11, negative list

SAP Note 23656 - No transport connection for condition records

Symptom:

The transactions for condition record maintainance have no transport connection although they are called from some Customizing applications.

Cause and prerequisites

The condition records have the characteristics from the administration master data or message master data rather than the characteristics from the customizing data.

Solution
Manually unite condition records in the target system.

SAP Note 23649 - Cost comp. on main and lower lvl in costing reports

Symptom:

The cost elements of the main level and lower level are 'incorrectly' displayed in the costing reports 7EOE_002 and 7EOE_003. The lower level displays the total of the raw materials from the lower level and main level, however, the display of the raw materials is completely missing on the main level.

Cause and prerequisites

This is defined that way.

Solution
According to logic in R/3, only those costs are added to the main level which result directly from the value added (for example, indirect costs and external costs). Therefore, the entire raw material costs are displayed on the lower level.
If you require a distinction between the raw materials and the semi-finished products/assemblies, you can recognize the distinction via the cost element report in itemization (7U0E_004).

SAP Note 23642 - Description of pxanew and pxastat

Symptom:

There are two files are in the directory /usr/sap//D*/work with the names "pxanew" and "pxastat". The names of ABAP/4 programs which are loaded into the program buffer (the so-called PXA buffer) when the system is next started are listed in these files.
The programs listed in "pxastat" are loaded first, then those in "pxanew". "pxanew" is then copied to "pxastat" and "pxanew" is deleted. When shutting down the system normally, the names of all programs in the buffer are entered in the file "pxanew".
Thus, the programs listed in "pxanew" are those that were used in the last system instance. The files listed in "pxastat" are from the previous instance. This prevents the PXA statistics being lost if the system is started and then immediately stopped again.

Cause and prerequisites

Without this "preload" process, system response time would be initially very slow until the relevant programs were loaded back into the buffer.

Solution
*

SAP Note 23635 - T510J: values of Value column 100 times too small

Symptom:

After importing the FCS 3.0, the values of the column Value in table T510J are 100 times too small.
This applies to all clients except client 0.

Cause and prerequisites

It is possible that XPRA RPU30009 ran twice in the FCS System

Solution
You can partially restore the table entries using the following report:
Report chT510j.

tables: t510j.

select * from t510j
client specified
where mandt <> '000'
order by primary key.

t510j-wert1 = t510j-wert1 * 100.
update t510j client specified from t510j.

endselect.

Please remember that the previous division might have rounded values off, and that these cannot, therefore, be restored with the above report. This is always the case if the value is not a whole number. These fractions disappear after the two divisions by 100.
This means that you should check the table entries manually after running the report!

SAP Note 23633 - Carry Forward Budget for Projects/Orders Not Allowed

Symptom:

In Release 3.0, you cannot automatically transfer remaining budgets that were not used within the year-end closing into the new year.

Cause and prerequisites

This is caused by missing functions in Release 3.0.

Solution

If a budget is transferred into the following year for a few orders or WBS elements only, you can carry out the carry forward manually as return/supplement, original budget change or (only for WBS elements) as a transfer, if necessary.

In Release 3.1G, two new transactions in the standard R/3 System allow a carry forward budget for projects and orders:

1. Transaction KOCO: Carry Forward Order Budget

The carry forward budget is available for CO internal orders and maintenance orders.

Budgets of a closed fiscal year that are not used up can be transferred into the following year.

The carry forward budget can be executed repeatedly in succession and it can run in the test run and in the production run. The differences to the last run are posted in each case. A detail list is issued optionally.

Selecting the orders is carried out via selection variants.

The budget of an order that is not used up results from the annual budget minus the actual costs. Commitments and sales revenues are not considered. Credits from settlements are only considered if the order in question was settled to another order, WBS element, network or network activity (elimination of internal business volume).

If the calculated value is negative, the program checks whether a carry forward run has already occurred before and writes the possibly existing carry forward amounting to the calculated value back into the initial year. The budget already transferred is retrieved as a maximum in this case. It is not possible to transfer a newly assigned budget into a previous year. With this an "actual" negative carry forward budgets are not possible.

An error log is issued in the case of an error. No carry forward occurs for the order in question.

For reasons of performance, you should execute the program in the background if the used selection variant contains many orders.

No active availability control occurs.

2. Transaction CJCO: Project Carryover Funds

Budgets of a closed fiscal year that are not used up can be transferred into the following year.

The carry forward budget can be carried out repeatedly in succession and it can run in the test and in the production run. The differences to the last run are posted in each case. A detail list is issued optionally.

Selecting the projects is carried out via the logical database of the Project System. The selection criteria can be restricted as desired using dynamic selections. However, the database profile is predefined for technical reasons and it cannot be changed.

The budget of a WBS element that is not used up results as follows:

Budget not used up = Annual budget
- Distributed value
- Actual costs

The actual costs contain the costs of the WBS element with budget and the actual costs of all assigned orders, all networks and all network activities as well as the actual costs of the lower-level WBS elements without budget.

Sales revenues and commitments are not taken into account. In contrast to the availability control, planned costs of apportioned orders and networks are also not included in the calculation of the carry forward. Reductions from settlements are only taken into account if the WBS element in question (or order, network or network activity) was settled to a WBS element, an order, a network or network activity (elimination of internal business volume).

If the calculated value is negative, the program checks whether a carry forward run has already occurred previously and it transfers the possibly available carry forward that amounts to the calculated value back into the initial year, if necessary. The budget already transferred is retrieved as a maximum in this case. It is not possible to transfer a newly assigned budget into a previous year. With this an "actual" negativ carry forward budgets are not possible.

An error log is issued in the case of an error. No carry forward occurs for the affected WBS element.

If a carry forward budget is carried out on a WBS element of a lower level, the corresponding value is also transferred into the following year on the higher-level WBS elements to ensure that the distributed values of the higher-level WBS elements are not higher than the budget available there.

Since the balance of the carry forward (budget minus distributed value) resulting from it is equal to zero on the higher-level WBS elements, only the carry forward of the lower WBS element is displayed in the detail list. For the same reason, a status validation is also only carried out for the lower WBS element in this case: it is checked whether the activities "Carry forward budget sender (GJA)" and "Carry forward budget receiver (GJA)" are permitted.

If the projects for which a carry forward is carried out contain many WBS elements or if you want to edit a large number of projects, you should execute the program in the background, due to reasons of performance.

No active availability control occurs.

As of Release 3.0D, the function described above is available via SAPSERV3 as a preliminary delivery.
The required files for transport request P30K160981 (old: P30K160981) are available in the directory /general/R3server/abap/note.0023633. See Note 13719 on how to pick up the files.

In addition, execute the following actions in your system manually:

a) Create a message for message class BP with number 595 using Transaction SE91:

Short text: 'Live run only possible for closed financial years'

Long text:
Cause
You tried to close the current fiscal year, or a future one, in the production run.
As you cannot reverse the activity, you may only close a fiscal year which has elapsed.
System response
The system switches automatically to the test mode.
What to do
Start the transaction again, if required, for a fiscal year which has elapsed.

b) Call Transaction SE37 and choose 'Utilities -> Repair funct. group -> Compare funct. group'. Enter AIPA as function group. Select the two top items (AIPA_CHECK_MEAS_YRCHG and AIPA_CHECK_MEAS_YRCHG_PREREAD) and choose 'Repair'. (If your logon language is not German, you must maintain in the *original* language).

c) Activate the two function modules AIPA_CHECK_MEAS_YRCHG and AIPA_CHECK_MEAS_YRCHG_PREREAD. You must first change the source code of function module AIPA_CHECK_MEAS_YRCHG_PREREAD as specified under "Corrections" (see also the next point). If in doing so problems with the editor lock occur proceed according to related Note 112111.

d) Make the source code changes specified under "Corrections".

Insert the lines marked with "<=== INSERT and delete those marked with "<=== DELETE.

Note the specified Releases to which the corrections apply in each case.

Note that these corrections are modifications which may be overwriten by applying Hot Packages and have to be edited afterwards to avoid syntax errors.

If you work with releases and do not want to adjust them manually, you must implement Note 93841 (Release 3.0D - 3.0F, 3.1G - 3.1H, 4.0A) in addition, which ensures that releases of the old year are reduced according to the budget during carry forward budget. However, no carry forward of the releases to the new year takes place. The note is required to avoid error messages caused by too high releases in the old year within budgeting.

Additional key words

budget forwarded, fiscal year change, fiscal year end, budgeting, budget

SAP Note 23632 - Erstattungsantrag bei Arbeitsplatzwechsel

Symptom:

Falls Abwesenheiten durch einen Arbeitsplatzwechsel gesplittet werden, so wird für jeden Teil der Abwesenheit ein Erstattungsantrag ausgegeben.
Dies ist nicht korrekt.
Für die gesamte Abwesenheit darf nur ein einziger Antrag auf Erstattung erstellt werden.

Weitere Begriffe
Ursache und Voraussetzungen

Programmfehler.
Abwesenheiten, die durch den o.a. Sachverhalt geteilt wurden, müssen wieder zusammengefaßt werden.

Lösung
Bitte ändern Sie die mit "<<<=========" besonders gekennzeichneten Programmzeilen und fügen Sie die neuen Routinen am Ende des Members RPCEFCA0 ein.

Betroff. Member RPCEFZA0

...
...
CURRKY LIKE P0015-WAERS "Waehrung
VALUE 'ATS',
CNTR3_MAX LIKE AB-CNTR3 "Laender-Split Nr. 3 < <<========
VALUE 'FF',
...
...
DATM TYPE D, "Datum
DATE TYPE D. "Datum
...
...
DATA: BEGIN OF OLD_AB. "Kopfzeile von AB <<<========
INCLUDE STRUCTURE PC20I. "<<<========
DATA: END OF OLD_AB. "<<<========
Betroff. Member: RPCEFCA0
Routine : COMPUTE_ABSENCE

FORM COMPUTE_ABSENCE.

* vor der eigentlichen Verarbeitung muessen noch diverse Variablen
* pro Abrechnungsperiode initialisiert werden
PERFORM RESET_PER_PERIOD.

* unrechtmaessig geteilte Abwesenheiten muessen vorab wieder zu-
* sammengefuegt werden
PERFORM MARK_DUPL_AB. "<<<========

* pro Abwesenheit muss nun festgestellt werden, ob es sich um eine
* erstattungsfaehige Abwesenheit handelt
LOOP AT AB.
* sind ueberhaupt die entsprechenden Lohnarten vorhanden?
PERFORM CHECK_AMOUNT USING AB-ABZNR FOUND REF_BETRG.

* CHECK: FOUND = TRUE. "alles OK? <<<========
CHECK: NOT REF_BETRG IS INITIAL AND"Betrag vorhanden? <<<========
AB-CNTR3 <> CNTR3_MAX. "Abwesenheit? <<<========

* vor der eigentlichen Verarbeitung einer Abwesenheit muessen be-
...
...
ENDFORM.

Betroff. Member: RPCEFCA0
Routine : CHECK_AMOUNT

FORM CHECK_AMOUNT USING $ABZNR $FOUND $BETRG.

* assume - keine Lohnarten vorhanden
CLEAR: $FOUND. "<<<========
* $BETRG. "<<<========
* falls eine neue Abwesenheit vorliegt, soll Betrag initialisiert
* werden (d.h. ungerechtfertigt geteilte Abwesenheiten werden
* wieder kumuliert)
PERFORM COMP_AB_OLD_AB USING CHAR. "<<<========

IF CHAR <> TRUE. "neue Abwesenheit? <<<========
CLEAR: $BETRG. "reset Betrag <<<========
ENDIF. "<<<========

OLD_AB = AB. "Daten uebernehmen <<<========

LOOP AT RT "Ergebnistabelle
WHERE ABZNR = $ABZNR. "AB-Split-Kennzeichen
...
...
ENDFORM.
Betroff. Member: RPCEFCA0
Routine : MARK_DUPL_AB (Gesamte Routine ist NEU!!!)

*---------------------------------------------------------------------*
* FORM MARK_DUPL_AB *
*---------------------------------------------------------------------*
* Geteilte Abwesenheiten muessen u.U. wieder zusammengefasst werden. *
*---------------------------------------------------------------------*
FORM MARK_DUPL_AB.

DESCRIBE TABLE AB LINES TABL_RECS. "Abwesenheiten vorhanden?

CHECK: TABL_RECS > 0. "Verarbeitung bei mindestens 1

TABL_INDX = 1. "erster Tabelleneintrag

READ TABLE AB INDEX TABL_INDX. "mit erstem Eintrag beginnen

OLD_AB = AB. "in OLD-Struktur und

WHILE TABL_INDX < TABL_RECS. "Vergleiche durchfuehren
TABL_INDX = TABL_INDX + 1. "Index erhoehen

READ TABLE AB INDEX TABL_INDX. "vorhergehender Eintrag

* unrechtmaessige Splittung der Abwesenheit feststellen
PERFORM COMP_AB_OLD_AB USING CHAR.

IF CHAR = TRUE. "sind Abwesenheiten gleich?
PERFORM CORRECT_AB USING TABL_INDX. "Beginn-Datum/Markierung
ENDIF.

OLD_AB = AB. "Daten uebernehmen (f. Vergl.)
ENDWHILE.

CLEAR: OLD_AB. "reset Kopfzeile
ENDFORM.
Betroff. Member: RPCEFCA0
Routine : COMP_AB_OLD_AB (Gesamte Routine ist NEU!!!)

*---------------------------------------------------------------------*
* FORM COMP_AB_OLD_AB *
*---------------------------------------------------------------------*
* Feststellen, ob Abwesenheit unrechtmaessig (wg. Arbeitsplatz- *
* wechsel) gesplittet wurde. *
*---------------------------------------------------------------------*
* $CHAR -- Output-Parameter *
* gibt an, ob zwei Abwesenheiten (eine in Tab. AB, *
* die andere in OLD_AB) gleich sind - d.h. Split er- *
* folgte wegen Arbeitsplatzwechsel *
* es gilt: TRUE -- Gleichheit der Abwesenheiten *
* FALSE -- sonst *
*---------------------------------------------------------------------*
FORM COMP_AB_OLD_AB USING $CHAR.

* assume Ungleichheit
$CHAR = FALSE.

CHECK: AB-OBEGD = OLD_AB-OBEGD AND "urspruengl. Beginn?
AB-OENDD = OLD_AB-OENDD AND "urspruengl. Ende?
AB-KLBEW = OLD_AB-KLBEW. "Bewertungsklasse?

$CHAR = TRUE. "Abwesenheiten sind gleich!
ENDFORM.
Betroff. Member: RPCEFCA0
Routine : CORRECT_AB (gesamte Routine ist NEU!!!!)

*---------------------------------------------------------------------*
* FORM CORRECT_AB *
*---------------------------------------------------------------------*
* Datumsangaben der Abwesenheit korrigieren, damit werden geteilte *
* Abwesenheiten besonders markiert und koennen somit entsprechend *
* verarbeitet werden. *
*---------------------------------------------------------------------*
* $INDX -- Input-Parameter *
* Tabellen-Index *
*---------------------------------------------------------------------*
FORM CORRECT_AB USING VALUE($INDX).

* aktuellen Tabelleneintrag bearbeiten
AB-BEGDA = OLD_AB-BEGDA. "Beginn der Abwesenheit
AB-APZNR = OLD_AB-APZNR. "WPBP-Zuordnung

MODIFY AB INDEX $INDX. "Aenderung durchfuehren

OLD_AB = AB. "Daten uebernehmen (Vergleich)
$INDX = $INDX - 1. "Index vermindern

* vorhergehenden Tabelleneintrag bearbeiten
READ TABLE AB INDEX $INDX. "vorhergehenden Eintrag bearb.

AB-CNTR3 = CNTR3_MAX. "Abwesenheit markieren

MODIFY AB INDEX $INDX. "Aenderungen uebernehmen

AB = OLD_AB. "reset Kopfzeile
ENDFORM.

SAP Note 23621 - Terms of payment with day limit - no printing

Symptom:

Terms of payment with day limits are not printed on the standard form RVORDER01 for quotations and sales orders.

Cause and prerequisites

The text cannot be determined explicitly since the date is unknown.

Solution
For all terms of payment with day limits which should be printed on the above-mentioned form, you must maintain a standard form via the following path:

Tools - Word processing - Standard text (transaction SO10)

Text name: XXXX (XXXX = terms of payment, which are to be included on the form)

Text ID: SDTP
Language: Language, in which a text is to be maintained for the
terms of payment.

Click on ´Create/Change´

Enter the text which is to appear on the form (maximum of 3 lines).

Save.

SAP Note 23617 - Resource-usage variance for materials

Symptom:

In variance calculation for orders, production cost collectors, or cost object IDs, a resource-usage variance for a material is expected because a different material was used than had originally been planned. What the system actually calculates, however, is a quantity variance, input variance, or remaining variance.
Transactions: KKS1, KKS2, KKS3, KKS5, KKS6, KKP5, KKPT

Cause and prerequisites

Costs are written to the above objects under the combination cost element, origin group, and material number. If planned costs but not actual costs (or vice-versa) exist for such a combination, a resource-usage variance is calculated in the amount of these costs.
The costs are always written under a cost element.
The origin group is only used if an origin group is assigned to the material in the material master. Otherwise the origin group remains on the object unused.
Costs are only written under the material number if this is defined for the material (i.e. when the "material origin" field is selected in the material master). This is only possible in Release 3.0. If the material is not selected in this way, the material number remains on the object unused. In Release 2.1/2.2 there is no material number in cost accounting objects, and no selection field in the material master.
If the material consumed has the same combination as was actually used for the planned material, no resource-usage variance is calculated. Instead, a quantity variance, input variance or remaining variance is calculated (see note 20217).
Examples: No. Planned mat. M1 Act. material M2 Resource-usage
Cost el./Orig/Mat. Cost el./Orig/Mat. variance
1. 400000/H001/M1 4000000/H001/M2 Yes
2. 400000/H001/- 4000000/H001/- No
3. 400000/- /M1 4000000/- /M2 Yes
4. 400000/- /- 4000000/- /- No
In examples 1 and 2, an origin group is assigned. In examples 1 and 3, the material origin has been chosen; this is only possible in Release 3.0.

Solution
If a resource-usage variance is desired, different origin groups should be used for different materials. In Release 3.0, the material origin can be chosen for selected materials. Note: The more detailed cost updating increases the amount of data and the runtime of the transactions, particularly during period-end closing. For this reason it should be restricted to important (valuable) materials.
A change to the material master will only affect cost estimates and material withdrawals that are created after the change. Existing data is not affected.
Remark:
With secondary cost elements, costs are always written under the combination of cost element and cost center/activity type. This cannot be influenced. The resource-usage variance is calculated for this combination similar to a material.

SAP Note 23614 - Address display in delivery header screen

Symptom:

In case of ship-to parties with manual addresses, the location that is displayed in the delivery header screen is still copied from the customer master.

Cause and prerequisites

Program error

Solution
Change program MV50AF0W as follows:

Additional key words

Partner, VL01, VL02, VL04, ship-to party

SAP Note 23611 - Collective Note: Security in SAP Products

Symptom:

Frequently asked questions concerning security in SAP products.

Other terms

security, network security, passwords, cryptography, authorizations

Reason and Prerequisites

Questions about security when using SAP products

Solution

This note provides an overview of security in SAP products and lists sources of additional information.

SAP Security Services
We offer a number of security services and mechanisms to support your security needs when using SAP Systems, to include:

Password rules, the SAP authorization concept, Central User Management, and auditing tools (Audit Info System and Security Audit Log) are some of the security services provided as standard measures in SAP Systems.

Features such as Single Sign-On, authentication outside of the SAP System, encryption and digital signatures are available using the SAP security interfaces SNC (Secure Network Communications) and SSF (Secure Store and Forward).

The SAP Security Guide provides a consolidated and detailed description of the security issues involved when using SAP Systems. Related guides provided by the Audit User's Group include FI and MM auditing guides and the Data Protection Guide (in german only).

The Security Consulting Team is also available for assisting you in meeting your individual security needs when using SAP Systems.

Additional Information
Visit the Security pages on the SAP Service Marketplace to find Fact Sheets, White Papers, presentations, technical documents, the SAP Security Guide, and links to the Security Consulting Team and the Audit User's Group. See http://service.sap.com/security.

SAP Note 23606 - Net price dependent on currency

Symptom:

If you are working in transaction CA02, external processing (screen 1040 in SAPLCPDO) and change the currency without changing the net price, the net price has been increased or reduced by a power of 10 the next time the screen is displayed.

Cause and prerequisites

Error in program SAPLCPDO

Solution
Identical corrections in Release 2.1L (repair P21K005458) and Release 2.2F (repair P22K007483):
Screen 1040 in SAPLCPDO:
PROCESS AFTER INPUT.

*----------------------Verarbeitung nach der Eingabe--------------------
* Abbrechen:
*=======================================================================
MODULE PIC_EXIT AT EXIT-COMMAND.

* Dynpro-Felder aktualisieren
*======================================================================*
* Arbeitsplatzdaten nachlesen
CHAIN.
:::
:::
:::
* Fremdbearbeitungsdaten-Verprobung
*-----------------------------------------------------------------------
* Falls ein Fremddatum eingegeben wird, so muß der Steuerschlüssel
* auf Fremdbearbeitung hin untersucht werden
CHAIN.
FIELD:
PLPOD-INFNR,
PLPOD-EKORG,
PLPOD-SORTL,
PLPOD-LIFNR,
PLPOD-MATKL,
PLPOD-EKGRP,
PLPOD-PLIFZ,
PLPOD-PREIS, <=== delete
PLPOD-PEINH,
PLPOD-WAERS,
PLPOD-PREIS, <=== insert
PLPOD-SAKTO.
:::
:::
:::

Additional key words

external processing work_center refer_to

SAP Note 23604 - APC valuation for foreign currency

Symptom:

How are acquisition costs and production costs valuated if the asset acquisition was made in foreign currency?

Other terms

Acquisition costs, date of purchase, foreign currency, down payment, exchange rate change

Solution
Adler-Düring-Schmalz, Rechnungslegung und Prüfung der Unternehmen, §255 HGB, Tz.63:
'If acquisition costs are to be paid in foreign currency, they are determined by the amount actually paid in DM for down payments and when paying cash.' During the purchase on target, the acquisition costs are basically determined through the amount of the foreign currency payables to be posted ... exchange rate changes after the primary update of assets generally do not effect the acquisition costs ...'.

SAP Note 23603 - Sort by document age: RFKORD10, RDKORD11

Symptom:

Sorting by document age is not available in the reports RFKORD10 and RDKORD11.

Cause and prerequisites

Was not programmed yet.

Solution
In the standard system for Release 3.0A and later

Advance correction for releases in which the sorted list has already been installed in the reports RFKORD10 and RFKORD11:

Parameter RART-ALT is used to select sorting by document age
Parameter RBLDAT is used to select the document date (instead of the
posting date) for sorting.

The new and changed lines are marked below with "<".

Report RFKORI02:
<
UTAGE(3) TYPE P, <
*---- ATAGE = Tage fuer Belegalterrasterung ----------------------* <
ATAGE(3) TYPE P.

Report RFKORD10 (RFKORD11):

Text symbols:

104 Document date__;;
105 Document age sorting

Source code:

SELECTION-SCREEN BEGIN OF LINE. <
PARAMETERS RART-ALT AS CHECKBOX. <
SELECTION-SCREEN COMMENT 03(28) TEXT-105. <
SELECTION-SCREEN POSITION 51. <
PARAMETERS RBLDAT AS CHECKOX. <
SELECTION-SCREEN COMMENT 61(12) TEXT-104. <
SELECTION-SCREEN END OF LINE. <

OR NOT RART-UEB IS INITIAL <
OR NOT RART-ALT IS INITIAL. <
PERFORM RASTER_AUFBAU.
ENDIF.

OR NOT RART-UEB IS INITIAL
OR NOT RART-ALT IS INITIAL <
OR NOT RVZTAG IS INITIAL.
IF VSTID IS INITIAL

IF NOT RART-UEB IS INITIAL.
UTAGE = RF140-VSTID - HBSID-NETDT.
PERFORM FILL_WAEHRUNGSFELDER_BSIDK_2.
PERFORM RASTERN USING HBSID-BUKRS HBSID-BSTAT UTAGE '4'
RF140-WRSHB HBSID-WAERS.
ENDIF.
IF NOT RART-ALT IS INITIAL. <
IF RBLDAT IS INITIAL. <
ATAGE = RF140-VSTID - HBSID-BUDAT. <
ELSE. <
ATAGE = RF140-VSTID - HBSID-BLDAT. <
ENDIF. <
PERFORM FILL_WAEHRUNGSFELDER_BSIDK_2. <
PERFORM RASTERN USING HBSID-BUKRS HBSID-BSTAT ATAGE '5' <
RF140-WRSHB HBSID-WAERS. <
ENDIF. <

IF NOT RART-UEB IS INITIAL.
UTAGE = RF140-VSTID - HBSIK-NETDT.
PERFORM FILL_WAEHRUNGSFELDER_BSIDK_2.
PERFORM RASTERN USING HBSIK-BUKRS HBSIK-BSTAT UTAGE '4'
RF140-WRSHB HBSIK-WAERS.
ENDIF.
IF NOT RART-ALT IS INITIAL. <
IF RBLDAT IS INITIAL. <
ATAGE = RF140-VSTID - HBSIK-BUDAT. <
ELSE. <
ATAGE = RF140-VSTID - HBSIK-BLDAT. <
ENDIF. <
PERFORM FILL_WAEHRUNGSFELDER_BSIDK_2. <
PERFORM RASTERN USING HBSIK-BUKRS HBSIK-BSTAT ATAGE '5' <
RF140-WRSHB HBSIK-WAERS. <
ENDIF. <

IF NOT RART-UEB IS INITIAL.
UTAGE = RF140-VSTID - HBSAD-NETDT.
PERFORM FILL_WAEHRUNGSFELDER_BSADK_2.
PERFORM RASTERN USING HBSAD-BUKRS HBSAD-BSTAT UTAGE '4'
RF140-WRSHB HBSAD-WAERS.
ENDIF.
IF NOT RART-ALT IS INITIAL. <
IF RBLDAT IS INITIAL. <
ATAGE = RF140-VSTID - HBSAD-BUDAT. <
ELSE. <
ATAGE = RF140-VSTID - HBSAD-BLDAT. <
ENDIF. <
PERFORM FILL_WAEHRUNGSFELDER_BSADK_2. <
PERFORM RASTERN USING HBSAD-BUKRS HBSAD-BSTAT ATAGE '5' <
RF140-WRSHB HBSAD-WAERS. <
ENDIF. <

IF NOT RART-UEB IS INITIAL.
UTAGE = RF140-VSTID - HBSAK-NETDT.
PERFORM FILL_WAEHRUNGSFELDER_BSADK_2.
PERFORM RASTERN USING HBSAK-BUKRS HBSAK-BSTAT UTAGE '4'
RF140-WRSHB HBSAK-WAERS.
ENDIF.
IF NOT RART-ALT IS INITIAL. <
IF RBLDAT IS INITIAL. <
ATAGE = RF140-VSTID - HBSAK-BUDAT. <
ELSE. <
ATAGE = RF140-VSTID - HBSAK-BLDAT. <
ENDIF. <
PERFORM FILL_WAEHRUNGSFELDER_BSADK_2. <
PERFORM RASTERN USING HBSAK-BUKRS HBSAK-BSTAT ATAGE '5' <
RF140-WRSHB HBSAK-WAERS. <
ENDIF. <

Report RFKORI15 (RFKORI16)

CASE RTAB-RAART.
WHEN '1'.
EREIGNIS = '574'.
WHEN '2'.
EREIGNIS = '575'.
WHEN '3'.
EREIGNIS = '576'.
WHEN '4'.
EREIGNIS = '577'.
WHEN '5'. <
EREIGNIS = '578'. <
ENDCASE.

Layout sets F140_ACC_STAT_01, F140_CUS_STAT_01, and F140_CUS_STAT_02:

In the MAIN window, copy text /E 577 to /E 578 and change the text as follows:
/E 578
/* *- List line Doc. date Sort
T4 Document age
,,&RF140-WAERS&,,&RF140-RAST1(18)&,,&RF140-RAST2(18)&,,&RF140-RA >

SAP Note 23594 - First page is printed again at the end

Symptom:

When you print a Report Writer report, the first page of data is printed again at the end of the report.
Key words: Report Writer, Printer, Printing, Spool

Cause and prerequisites

Program error

Solution
Error corrected in Release 3.0A.

SAP Note 23588 - Calling reps for run schedule headers is impossible

Symptom:

In the cost analysis of repetitive planning (transaction MF20), it is not possible to call the reports stored in Customizing.
Cancellation with the error message: ´KN001: No suitable reports exist#´.

Cause and prerequisites

Reports do not exist or are not generated.

Solution
1. Transfer reports from client 000 into the respective clients: Transaction OKSP
2. Generate reports: Transaction OKS9

SAP Note 23575 - Lack of performance when creating production orders

Symptom:

If capacity planning is activated for a control-key, which is used in a production order, (transaction OP00, field V_T430-TERM ) then creating production orders is very slow. If this indicator is reset, then the order can be saved injust a few seconds.

Cause and prerequisites

The control-key in the operation requires capacity planning in the work center, however, the fields in the standard available capacity are not maintained.

Solution
Please check the capacity header in the scheduling screen in the work centers. If the fields in the standard available capacity are not maintained, the system will look at every day in the calendar and performance suffers as a result of this.
Path: TA CR02 - Scheduling - Capacity header

Additional key words

CO01 SAPLCRK1 SAPLSCAL Performance runtime work center

SAP Note 23567 - Missing amort.on goodwill/undiscl.res.for EQUITY

Symptom:

With the subsequent consolidation (RGCKAP00) of a company consolidated at-equity, neither amortizations of goodwill nor of the hidden reserves are displayed and posted. This applies although the goodwill and the eliminated hidden reserves are correctly contained in the corresponding financial reporting table T874 (Transaction GC33, function 'Eliminated hidden reserves').

Cause and prerequisites

Program RGCKAP00

Solution
Amortizations of goodwill or eliminated hidden reserves are only carried out if the change in profit and loss of the company consolidated at-equity (Transaction GC33) was also maintained for the same period.
For the exceptional case that there are no equity holdings adjustments to be maintained, install correction vhs116236 in program FF10CE92, (no longer necessary as of Release 3.1G) and maintain the equity holdings adjustments with zero values.

SAP Note 23566 - RFZALI10 - Incorrect accounting clerk

Symptom:

The accounting clerk for the exception list in payment transactions is displayed incorrectly (the accounting clerk from a different company code is displayed whereby an accounting clerk was not allocated for the current company code).

Cause and prerequisites

Program error.

Solution
Error has been corrected in Release 3.0E. An interim correction is possible.

Additional key words

RFZALI10

SAP Note 23562 - RFFOD__L - SCB ind. and supplying cntry are missing

Symptom:

1. With data medium exchange, payments cannot be made using DME in the DTAZV format, since the SCB indicator and supplying country are missing or are not valid (error messages FS265, FS266, FS267).

2. When posting, the SCB indicator and supplying country fields cannot be entered on the additional screen (Other data). Cause and prerequisites

In Customizing, the fields are hidden by means of the field selection.

Solution

>>>> Preparation <<<<

Additional key words

LZBKZ, LANDL, RFFOD__L, F110, FB01, FB10, F-43, F-47
BSEG-LZBKZ, BSEG-LANDL, regulatory reporting

SAP Note 23560 - PC entry: Printing on network printer

Symptom:

The printouts from the FI-LC PC entry are automatically routed to the LPT1 port. As a result, the printouts are not sent to the network printer.

Cause and prerequisites

See above

Solution
You can identify the printer for LPT1 in the batch file for calling PC entry in the following manner:

FILC.BAT:

SET CLIPPER=F45
del *.ntx
net use lpt1 \\p04711\hp4 <- network address of printer: Example!
fi.exe
del !*.*
net use lpt1 /D <- Statement cancelled again at the end
of the program

The assignment must be programmed for the individual network address of the corresponding printer for each installation.

SAP Note 23552 - CREATE costing

Symptom:

Transaction VKP0: The entry CREATE is missing in the costing menu. One can only change and display.

Cause and prerequisites

The change mode allows both "Create" and "Change". If you only want to "Create", you have to set the indicator "New costings only". For this reason, a transaction "Create costing" did not seem to be necessary. This, however, contradicts the ergonomics directives.

Solution
A new transaction "Create costing" was created which corresponds to the transaction "Change costing". Here, the indicator "New costings only" is no longer displayed on the selection screen and set in the background.

SAP Note 23551 - RPCSVBA0: Keine Gruppensummen bei Null-Summen

Symptom:

Summary

Symptom

Bei Rueckrechnungen werden Gruppensummen und Trennblätter ausgedruckt, auch wenn die Summe Null ist.

Weitere Begriffe
Ursache und Voraussetzungen

Design

Lösung

Mit dieser Modifikation können im Rückrechnungsfall die Ausgabe von Gruppensummen und Trennblättern bei Null-Summen unterdrückt werden.

Bitte ergänzen Sie im Member RPCSVBAI folgende
mit <---- gekennzeichneten Zeilen:

***********************************************************************
* Bei Gruppenwechsel die Summe der vorhergehenden Gruppe ausgeben. *
***********************************************************************
FORM GRUPPEN_SUMME USING EINS ZWEI DREI VIER FUENF SECHS.
DATA: DIFFERENZ1 LIKE AUSVA_2-DNDGP.
CHECK AUSVA_2-FUPER EQ PERIODEJ OR "Rueckrechnung und "<<<---
AUSVA_2-DNDGB NE 0. "Summe ist null "<<<---
REIHENFOLGE1 = REIHENFOLGE.
.
.
.
ENDFORM.

***********************************************************************
* Trennblatt ausgeben *
***********************************************************************
FORM TRENN_BLATT.
CHECK AUSVA_2-FUPER EQ PERIODEJ OR "Rueckrechnung und "<<<---
AUSVA_2-DNDGB NE 0. "Summe ist null "<<<---
SCHALTER = 'N'.
.
.
.
ENDFORM.

Header Data


Release Status:	Released for Customer
Released on:	01.12.1996 23:00:00
Master Language:	German
Priority:	Correction with low priority
Category:	Program error
Primary Component:	PY-AT Austria

Affected Releases

Software Component	Release	From Release	To Release	And subsequent
SAP_APPL	22	22A	22G
SAP_APPL	30	30A	30C

SAP Note 23547 - Movement type for goods movements w. ref. to reservations

Symptom:

In the process of transactions MB1A (goods issue), MB1B (transfer posting), MB1C (other goods receipt), and MB11 (goods movement), the user enters a movement type (e.g. 201) and presses the "Reservations..." pushbutton (or chooses Goods movement --> Create with reference --> To reservation... from the CUA menu). In the dialog box which then appears, a reservation is entered or selected that has been created with a different movement type (e.g. 261).
The system carries out the goods movement on the basis of the movement type used for creation of the reservation (in the above example: 261). The system ignores the specified movement type (in the example: 201).
The system proceeds in the same way for movements that are entered with reference to an order or material document.

Cause and prerequisites

This process has been designed this way, because it should not be possible to change the original purpose of a reservation (in the example, it was created for a production order) by specifying a different movement type (in the example, for a cost center).

Solution
1. When entering a goods movement for a reservation, specification of a movement type is not required.
2. If you wish to reverse a goods movement for a reservation, you can do so by selecting Goods movement --> Reverse with reference --> To reservation... from the CUA menu. In this case, the goods movement is carried out with the relevant reversal movement type (in the example: 262).

SAP Note 23538 - Problems due to inconsistent host name notation

Symptom:

:
*** ERROR sql 6108 performing con
*** ERROR ThSendErrMsg: db_connect ...

Other terms

host name, TCPIP, DB12, SM51, startsap, DNS, name resolution, hosts

Reason and Prerequisites

In general:
Windows (NT, 2000, 2003, XP) distinguishes between the 'computer name' (Control Panel -> Network) and the 'host name' (Control Panel -> Network -> TCP/IP Protocol -> DNS). The name specified during NT installation will only be used as a 'computer name' for addresses within the LAN manager, while the 'host name' is used for addresses in TCP/IP. The 'computer name' exists in UPPER CASE only , while the host name is automatically set in lower case during the network configuration.
The main part of R/3 network communication is implemented by TCP/IP on the basis of the 'host name'. Within the R/3 system (for example, CCMS), this TCP/IP name is treated as CaSe SeNsItIvE. The errors mentioned above may occur if, during the upgrade or in any form of the dialog with R/3, the TCP/IP 'host name' (hereafter simply called the 'host name') is used in a different uppercase and lowercase format in R/3 profiles.

Especially for phenomenon no. 2:
The aforementioned symptom is possibly a specific instance and is caused by the inconsistent notation of the SAPDBHOST and SAPLOCALHOST profile parameters compared with the host name from Windows NT:
The work processes read SAPDBHOST, determine that the name is different from the host name (command prompt: "hostname") and SAPLOCALHOST, and - by means of TWO_TASK in TCP/IP - attempt to make the connection to a host that does not exist.

Solution

ALL references to the host name in SAP R/3 profiles (for example, rdisp/btc_name, SAPDBHOST, SAPLOCALHOST) must contain the TCP/IP host names! Adjust the profiles accordingly. Then restart the R/3 system including SAP Services. You can use the command line command "hostname" to determine the TCP/IP host name. To check that your changes are effective, display the host name in transaction SM51.

Of course, you should also enter the TCP/IP host name in the HOSTS file. Alias entries in the hosts file are not sufficient for this and should - if possible - be avoided if the alias contains the same host name, but it is written in the other notation.
It is a good idea to create a HOSTS file (see below) that includes the addresses and TCP/IP host names of all application servers in a distributed R/3 system. Then copy this HOSTS file to all applications servers in the %windir%\system32\drivers\etc directory. By doing this,

you reduce unnecessary network traffic for host name resolution using DNS or WINS, and

you make a unique host name source available to each application server.

Since the message server maintains a host name cache, you must stop and restart the R/3 system after you change the HOSTS file (in order to activate the changes).

Multihomed computer
For computers with several network cards, a separate, unique TCP/IP HOSTNAME must be assigned to each network card. You cannot use one name for several network cards (IP addresses). In this case, you must add the addresses of the second adapter to the HOSTS file and specify a second host name there. This host name must be unique, in other words, it must not simply differ with regard to the upper case and lower case of the host name of the first network adapter.
Information about the second network adapter (NIC) should also be available to other applications servers. Therefore, you should add the HOSTS file to the other instances. The following example shows how the HOSTS could look on each application server in a distributed R/3 system:

127.0.0.1 localhost
111.111.111.1 centrl #central instance
222.222.222.1 centrl_A #2. NIC of central instance
111.111.111.2 apsrv1 #application server 1
222.222.222.2 apsrv1_A #2. NIC of application server 1
111.111.111.3 apsrv2 #application server 2
222.222.222.3 apsrv2_A #2. NIC of application server 2
...

If you encounter difficulties when assigning host names to the IP addresses of a computer, refer to Note 83200.

If the procedure mentioned above is not successful, the parameter SAPLOCALHOST may exist again in the user environment of the user who starts the R/3 kernel. The SAPLOCALHOST, which is set in the environment in this way, overwrites the TCP/IP host name that is determined by the R/3 system in the operating system. Use the "SET" command to scan the user environment, or the kernel environment in the registry (HKML\Software\SAP\\Environment), for the parameter SAPLOCALHOST and, if necessary, correct the notation. After you change the value, you also have to stop and restart the R/3 instance (including SAP Services) here.

Exception SAPGLOBALHOST:
The parameter SAPGLOBALHOST will be set in capitals due to reasons related to the technical installation, but it is NOT treated as case sensitive. Therefore, it does not matter whether SAPGLOBALHOST is in upper case or lower case.

SAP Note 23538 - Problems due to inconsistent host name notation

Symptom:

:
*** ERROR sql 6108 performing con
*** ERROR ThSendErrMsg: db_connect ...

Other terms

host name, TCPIP, DB12, SM51, startsap, DNS, name resolution, hosts

Reason and Prerequisites

Solution

ALL references to the host name in SAP R/3 profiles (for example, rdisp/btc_name, SAPDBHOST, SAPLOCALHOST) must contain the TCP/IP host names! Adjust the profiles accordingly. Then restart the R/3 system including SAP Services. You can use the command line command "hostname" to determine the TCP/IP host name. To check that your changes are effective, display the host name in transaction SM51.

Of course, you should also enter the TCP/IP host name in the HOSTS file. Alias entries in the hosts file are not sufficient for this and should - if possible - be avoided if the alias contains the same host name, but it is written in the other notation.
It is a good idea to create a HOSTS file (see below) that includes the addresses and TCP/IP host names of all application servers in a distributed R/3 system. Then copy this HOSTS file to all applications servers in the %windir%\system32\drivers\etc directory. By doing this,

you reduce unnecessary network traffic for host name resolution using DNS or WINS, and

you make a unique host name source available to each application server.

Since the message server maintains a host name cache, you must stop and restart the R/3 system after you change the HOSTS file (in order to activate the changes).

Multihomed computer
For computers with several network cards, a separate, unique TCP/IP HOSTNAME must be assigned to each network card. You cannot use one name for several network cards (IP addresses). In this case, you must add the addresses of the second adapter to the HOSTS file and specify a second host name there. This host name must be unique, in other words, it must not simply differ with regard to the upper case and lower case of the host name of the first network adapter.
Information about the second network adapter (NIC) should also be available to other applications servers. Therefore, you should add the HOSTS file to the other instances. The following example shows how the HOSTS could look on each application server in a distributed R/3 system:

127.0.0.1 localhost
111.111.111.1 centrl #central instance
222.222.222.1 centrl_A #2. NIC of central instance
111.111.111.2 apsrv1 #application server 1
222.222.222.2 apsrv1_A #2. NIC of application server 1
111.111.111.3 apsrv2 #application server 2
222.222.222.3 apsrv2_A #2. NIC of application server 2
...

If you encounter difficulties when assigning host names to the IP addresses of a computer, refer to Note 83200.

If the procedure mentioned above is not successful, the parameter SAPLOCALHOST may exist again in the user environment of the user who starts the R/3 kernel. The SAPLOCALHOST, which is set in the environment in this way, overwrites the TCP/IP host name that is determined by the R/3 system in the operating system. Use the "SET" command to scan the user environment, or the kernel environment in the registry (HKML\Software\SAP\\Environment), for the parameter SAPLOCALHOST and, if necessary, correct the notation. After you change the value, you also have to stop and restart the R/3 instance (including SAP Services) here.

SAP Note 23513 - No further restriction in business reporting

Symptom:

No further restrictions can be selected on the selection screen in Project System business reporting.

Cause and prerequisites

Missing functionality in Release 3.0.

Solution
The logical database (PSJ), which underlies all of PS reporting, offers the possibility of further restrictions (for example, by profit center or responsible persons). This is also offered in basic data and scheduling reporting.
For technical reasons, this functionality is not available in business reporting.
As of Release 3.0D, free restrictions are also available in business reporting in the standard system (please refer to Release Notes).
For Release 3.0C, you can activate the free restrictions for structure reports for costs, revenues and finances by making a few simple changes to the source code. This change is described in the following source code section.

Additional key words

Information system, project, structure report

SAP Note 23512 - SAPDBCNJ: Authorization check: work center for oper.

Symptom:

The authorization check "Work center for operation", C_AFVG_APL, does not work in logical database CNJ.

Cause and prerequisites

When function module CNAU_AUTHORITY_AFVG is called in FORM routines AUTHORITYCHECK_ACT01/..02/..03 in DBCNJAUT, field ARBPL (work center, external number) is not filled.

Solution
Program SAPDBCNJ, file DBCNJAUT

Form-Routine ARBEITSPLATZ_SETZEN hinzufügen:
... ENDFORM. "SET_VGTYP

FORM ARBEITSPLATZ_SETZEN USING ARBID
CHANGING ARBPL WERKS.
DATA: BEGIN OF CRHD.
INCLUDE STRUCTURE CRHD.
DATA: END OF CRHD.

CLEAR: ARBPL,
WERKS.

CHECK NOT ARBID IS INITIAL.

CALL FUNCTION 'CR_WORKSTATION_READ'
EXPORTING
ID = ARBID
IMPORTING
ARBPL = ARBPL
ECRHD = CRHD
WERKS = WERKS
EXCEPTIONS
NOT_FOUND = 1.
IF SY-SUBRC <> 0.
CLEAR: ARBPL.
EXIT.
MESSAGE S000 WITH 'Arbeitsplatz nicht gefunden'.
ENDIF.
ENDFORM. "ARBEITSPLATZ_SETZEN

Release 2.2:
In addition, in file DBCNJAUT, insert calls for FORM routine ARBEITSPLATZ_SETZEN in FORM routines AUTHORITYCHECK_ACT01, AUTHORITYCHECK_ACT02, and AUTHORITYCHECK_ACT03.
The corresponding code places are identical in all three form routines up to the lines marked with "!!": insert ACT01 in AUTHORITYCHECK_ACT01 insert ACT02 in AUTHORITYCHECK_ACT02, and insert ACT03 in AUTHORITYCHECK_ACT03.

... PERFORM SET_VGTYP USING ITAB-VNG-STEUS
CHANGING H_VGTYP.
PERFORM ARBEITSPLATZ_SETZEN USING ITAB-VNG-ARBID <=== INSERT
CHANGING ITAB-VNG-ARBPL <=== INSERT
ITAB-VNG-WERKS. <=== INSERT
ACT01-ARBPL = ITAB-VNG-ARBPL. <=== INSERT !!
ACT01-WERKS = ITAB-VNG-WERKS. <=== INSERT !!
CALL FUNCTION 'CNAU_AUTHORITY_AFVG'
EXPORTING
I_AFVGD = ITAB-VNG
...
PERFORM SET_VGTYP USING ITAB-ELM-STEUS
CHANGING H_VGTYP.
PERFORM ARBEITSPLATZ_SETZEN USING ITAB-ELM-ARBID <=== INSERT
CHANGING ITAB-ELM-ARBPL <=== INSERT
ITAB-ELM-WERKS. <=== INSERT
ACT01-ARBPL = ITAB-ELM-ARBPL. <=== INSERT !!
ACT01-WERKS = ITAB-ELM-WERKS. <=== INSERT !!
CALL FUNCTION 'CNAU_AUTHORITY_AFVG'
EXPORTING
I_AFVGD = ITAB-ELM
...
Release 3.0
In file DBCNJAUT, insert calls for FORM routine ARBEITSPLATZ_SETZEN in FORM routines AUTHORITYCHECK_ACT01, AUTHORITYCHECK_ACT02, and AUTHORITYCHECK_ACT03.
The corresponding code places are identical in all three form routines up to the lines marked with "!!": insert ACT01 in AUTHORITYCHECK_ACT01 insert ACT02 in AUTHORITYCHECK_ACT02, and insert ACT03 in AUTHORITYCHECK_ACT03.
... PERFORM SET_VGTYP USING ITAB_VNG-STEUS
CHANGING H_VGTYP.
PERFORM ARBEITSPLATZ_SETZEN USING ITAB_VNG-ARBID <=== INSERT
CHANGING ITAB_VNG-ARBPL <=== INSERT
ITAB_VNG-WERKS. <=== INSERT
ACT01-ARBPL = ITAB_VNG-ARBPL. <=== INSERT "!!"
ACT01-WERKS = ITAB_VNG-WERKS. <=== INSERT "!!"
CALL FUNCTION 'CNAU_AUTHORITY_AFVG'
EXPORTING
I_AFVGD = ITAB_VNG
...
PERFORM SET_VGTYP USING ITAB_ELM-STEUS
CHANGING H_VGTYP.
PERFORM ARBEITSPLATZ_SETZEN USING ITAB_ELM-ARBID <=== INSERT
CHANGING ITAB_ELM-ARBPL <=== INSERT
ITAB_ELM-WERKS. <=== INSERT
ACT01-ARBPL = ITAB_ELM-ARBPL. <=== INSERT "!!"
ACT01-WERKS = ITAB_ELM-WERKS. <=== INSERT "!!"
CALL FUNCTION 'CNAU_AUTHORITY_AFVG'
EXPORTING
I_AFVGD = ITAB_ELM
...