SAP OSS Notes: 1/16/11

22.1.11

SAP Note 18593 - FI-SL: Program terms with more than 53 periods

Symptom:

In FI-SL, program terminations occur if you use more than 53 periods (for example by using daily ledgers with 365 or 366 periods).

1) In Releases 2.x and 3.x:
ABAP/4 runtime error TSV_TNEW_ENTRY_TOO_LARGE

2) In releases prior to 4.70:
ABAP/4 runtime error GEN_TOO_MANY_DATA (allocation)
ABAP/4 runtime error GEN_LINE_BUFFER_OVERFLOW (rollup)

Other terms

TSV_TNEW_ENTRY_TOO_LARGE
GEN_TOO_MANY_DATA
GEN_LINE_BUFFER_OVERFLOW

Reason and Prerequisites

1) In Releases 2.x und 3.x:
The error can only occur in the planning, allocation and rollup application areas.
The reason for the ABAP/4 runtime error is the size of internal table GLU2; the ABAP Basis imposes a limitation of 8K. Normally if, for example, you use a monthly ledger (including four special periods), this is not a problem; around 765 bytes are required in GLU2 for 5 dimensions: 5 dimensions * 17 periods * 9 bytes. 366 periods require 3294 bytes for each dimension (= 366 * 9 bytes).
In addition, there is the problem that the GLU2 structure with 366 periods contains too many fields for each field group (TSL, HSL, KSL, MSL and ASL), which will also lead to a runtime error.
2) In Release 4.x:
The error can only occur in the allocation and rollup application areas.
The reason for the runtime error is that program ALxxxxxx (allocation) generates data statements that become too large, or the generated program RGLXxxxx (rollup) becomes too large.

Solution

1) In Release 2.x and 3.x:
At the moment, the problem can be solved if, when generating the GLU2 structure using the RGICGLU2 program, you leave out the field group additional quantity (ASL). This has the disadvantage that the additional quantity can no longer be processed when working with the above mentioned functions. Since the additional quantity is used relatively rarely, this is not all that significant.

---------------------

1. Make the following corrections:

Program RGICGLU2, approximately line 970:

FORM FILL_FIELDGROUPS.
FIELDGROUPS-FG = 'TSL'.
APPEND FIELDGROUPS.
FIELDGROUPS-FG = 'HSL'.
APPEND FIELDGROUPS.
FIELDGROUPS-FG = 'KSL'.
APPEND FIELDGROUPS.
FIELDGROUPS-FG = 'MSL'.
APPEND FIELDGROUPS.
* FIELDGROUPS-FG = 'ASL'. <-- (*)
* APPEND FIELDGROUPS. <-- (*)
ENDFORM.

-------------------------

2. If you want to use the assessment or distribution, you must modify the following programs.

Program RGALLOC0, approximately line 4760:

IF T800A-ATQNT = 'X'.
LOOP AT VALUE_L WHERE TABLE = I_TABLE-NAME
AND FIELD = 'ASL01'.
EXIT.
ENDLOOP.
STRING = 'CALC_OFF2 = CALC_OFF1 * x. '.
REPLACE 'x' WITH VALUE_L-LENGTH INTO STRING.
PERFORM APPEND-C USING 0 STRING 0 0.
STRING = 'CALC_PER2 = CALC_PER1 * x. '.
REPLACE 'x' WITH L_GLU2-ASL INTO STRING.
PERFORM APPEND-C USING 0 STRING 0 0.
STRING = 'ASSIGN x '.
REPLACE 'x' WITH I_TABLE-NAME INTO STRING.
REPLACE ' ' WITH
'-ASLVT+CALC_OFF2(x) TO TYPE ''P''. '
INTO STRING.
REPLACE 'x' WITH VALUE_L-LENGTH INTO STRING.
PERFORM APPEND-C USING 0 STRING 0 0.
* STRING = 'ASSIGN GLU2-ASL000+CALC_PER2(x) TO TYPE '<-- (*)
* REPLACE 'x' WITH L_GLU2-ASL INTO STRING. <-- (*)
* PERFORM APPEND-C USING 0 STRING 0 0. <-- (*)
* PERFORM APPEND-C USING 0 'ADD TO .' 0 0. <-- (*)
ENDIF.

Program RGALLOC1, approximately line 3480:

PERFORM APPEND-C USING:
0 'FORM BOOK_GLU2. ' 0 2,
0 ' ' 0 0,
0 'DATA: PERCL LIKE PERIOD, ' 0 0,
0 ' PERIO LIKE PERIOD, ' 0 0,
0 ' I LIKE SY-TABIX, ' 0 0,
0 ' TSL LIKE GLU2-TSL001, ' 0 0,
0 ' HSL LIKE GLU2-HSL001, ' 0 0,
0 ' KSL LIKE GLU2-KSL001, ' 0 0,
0 ' MSL LIKE GLU2-MSL001, ' 0 0,
0 ' ASL LIKE GLU2-MSL001, ' 0 0, <---
0 ' OFSET(2) TYPE P. ' 0 0,
0 'FIELD-SYMBOLS: . ' 0 0,

approximately line 4300:

PERFORM APPEND-C USING:
0 'DO PERIO_TO TIMES ' 0 2,
0 'VARYING TSL FROM GLU2-TSL001 NEXT GLU2-TSL002 ' 0 0,
0 'VARYING HSL FROM GLU2-HSL001 NEXT GLU2-HSL002 ' 0 0,
0 'VARYING KSL FROM GLU2-KSL001 NEXT GLU2-KSL002 ' 0 0,
0 'VARYING MSL FROM GLU2-MSL001 NEXT GLU2-MSL002.' 0 0, <-(.)
* 0 'VARYING ASL FROM GLU2-ASL001 NEXT GLU2-ASL002.' 0 0, <-(*)
0 ' ' 0 0,
0 'ADD 1 TO PERIO. ' 0 0,
0 'IF PERIO >= PERIO_FROM. ' 0 2,
0 'ADD 1 TO I. ' 0 0,

Caution:
You should not allocate or distribute more than 20-30 periods at one time when using allocations, because this may also cause a runtime
error.
-------------------------

3. You can edit 366 periods in planning only if NO MORE than two field groups (for example, transaction currency and local currency) are used.

For this reason, check your planning parameters and your currency settings for the ledger that is to be planned.
If you must plan with more than two field groups, you have the following possibilities:

b) Instead of using a rollup, you can create parallel reports for both ledgers in the Report Writer

-------------------------

4. When using rollups, you must make sure that the sender and the receiver ledgers do not store any additional quantities. Furthermore, you can simultaneously roll a maximum of around 100 periods.

----------------------

IMPORTANT NOTE:
To activate all of the program changes in FI-SL, you must start the following programs:

5. RGICGLU2 (with 366 periods)

6. RGBCFL00 with all parameters
You should not do so in a productive system.

2) In Release 4.x
Start the rollup or the allocation for a maximum of 70 periods in one run.
If you want to assess, distribute or summarize a whole year's data, you must start the relevant allocation or rollup several times in succession for different period intervals.

SAP Note 18580 - SAPcomm: Integrating a logo into fax documents

Symptom:

How can you integrate a graphic (company logo, etc.) in outbound fax documents?

Cause and prerequisites
Solution

Whether such a functionality is provided and how it can be implemented depends on the fax device used.
The decisive factors here are

1. whether and in which form the fax system accepts instructions to integrate from graphics.

2. which output format the system uses, that is, which device type is specified in the spool administration (see also Note 19302):

a) ASCII-Text, device types SAPCOMF, TOPCALL, GAMMAFAX

In the R/3 System, SAPcomm, or the fax system, the following four procedures are supported:

Add one or more statements in the SAPscript form assigned to the outbound fax document, which are performed by the fax device (the file with the logo graphics is stored in the fax system).

To do so, change the form (Transaction SE71) as follows:

a) Define a new window (for example, LOGO) of type CONST.

b) Create a new page window LOGO. Place this at the desired location with "Left margin" and "Right margin."

4. Logo in R/3
As of Release 3.0, it is only possible with printer format device types and not with ASCII text device types (see above).
Integrate the graphic files used as logos into the forms used for fax (SAPscript statement Include; read the details for this in the SAPscript documentation).

Additional key words

SAPcomm

SAP Note 18578 - Search fct./PCH report finds nothing

Symptom:

In den Transactions PP01, PP02, PO01, ..., P015, the search function finds nothing. However, if you enter the object ID directly, these objects are displayed.
In addition, evaluations via the PCH logical database do not produce any output.
These actions were executed in a newly created client. Only the file PLOG was copied to the new client and the report SAPMACO was started.

Cause and prerequisites

The user entered "*" as the search term. In this situation, the search function reads the PLOGI table which was not copied when the client was created. For evaluations via the logical database PCH,
the PLOGI table is also read.

Solution
Create the missing entries in the PLOGI table by starting report RHPLOGI0 with the following parameters:
Plan variant: *
Object type: *
Rebuild index: X

SAP Note 18575 - Withdrawing consignee stock for production order

Symptom:

Up to and including Release 3.1I, planned goods withdrawal with reference to a production order and consignee stock is not possible (Transaction MB1A).
As of Release 4.0A, planned goods withdrawal for the order can be executed from consignee stock via stock determination, even though the special stock indicator is not set in the reservation. Due to the complexity of this function, an advance correction for earlier releases cannot be provided.

Cause and prerequisites

If a goods issue is posted with reference to a production order, you cannot set the special stock indicator manually, as it is always copied from the reservation.
It is only possible to post a goods issue from consignee stock with reference to a production order in R/3 if the special stock indicator 'Consignment' is already set for the reservation in the order. In Release 3.0, the indicator can only be set manually. It is not possible to do this automatically. If the special stock indicator is not set in the order, only an unplanned withdrawal can be made using movement type 261 and the special stock indicator 'K'.
As of Release 4.0A, stock determination can be triggered by entering * in the storage location field.

Solution
Post the consignee stock to the available stock and then withdraw it from the production order or make prior arrangements for the consignment in the production order.

SAP Note 18566 - SPELL - Digits 30, 40-49 wrong in English

Symptom:

Key words: F110, RFFOD__S, RFFOUS_C, SPELL.
The digits in words for values 30 and 40 through 49 have been translated incorrectly in English (thrity instead of thirty and fourty instead of forty).

Cause and prerequisites

Incorrect table entries in table T015Z.

Solution
The error has been corrected for all new installations, but the upgrade/release procedure cannot correct the error in existing installations. You must therefore correct the table entry in the customer system:

Transaction SM31 Maintain table T015Z (press to confirm view screen).Set argument to Language E, Unit 3.
Now change the entry 30 from THRITY to THIRTY and
for the range 40 through 49, change FOURTY to FORTY.
Then press F11 in the view maintenance to save.

SAP Note 18551 - How can you save the database with an autochanger ?

Symptom:

How can you save the database with an autochanger without operator ?

Cause and prerequisites

Autochanger in BRBACKUP

Solution
BRBACKUP supports devices with automatic tape changer (e.g. autochanger, tape stacker). These devices can be accessed both locally and remotely.
Change the
init.sap profiles
parameter backup_dev_type:

local: backup_dev_type = tape_auto
remote: backup_dev_type = pipe_auto

BRBACKUP switches automatically to the next tape when a tape is filled (dependent on tape_size).

Caution:
--------
Many of these devices require additional time for the tape change. This additional time can be catered for by means of appropriate definition of parameter rewind_offline in the profile init.sap (operating-system-specific).

For example:
rewind_offline = "mt -f $ offline && sleep 30"

The time must be set even higher for certain devices, e.g.:

rewind_offline = "mt -f $ offline && sleep 200"

Caution:
--------
On the IBM AIX platform, tctl or tapeutil commands can be used in place of the mt command.

SAP Note 18533 - PC004: Error no. xx in graphic / file transfer

Symptom:

Termination with error message PC004.

Long text of the error message is not in the delivery due to transport problems.

Reason and Prerequisites

An error was detected in the SAPGUI (list of frequent errors)
01 : Operating system error message (not an SAP error)
02 : No memory available for starting further programs
03 : General error in the started program
05 : Error in download data with WK1 or DBF (see note 13531)
(too many columns, field width too large)
07 : Error writing file
(write protect, insufficient space, medium defect)
09 : Record too long.
(possibly binary data sent in ASCII mode)
11 : "invalid Child ID"
12 : "duplicate Child ID"
16 : "no window handle for instance"

Since these error were not masked in the calling program, the transaction is terminated.

Solution
Remarks on specific errors:
05 : Data structure for download needs to be adjusted.
11 : Program error in the application causing a program in the front end which was not yet started or which was already terminated to be supplied with data. The error is to be solved in the application.
12 : Program error in the application brings about that a program in the front end is to be started under an ID which was assigned to an already started graphics program. The error is to be solved in the application.
16 : Typical lack of resources in the system (Windows 3.x).
For more information refer to related notes.

SAP Note 18529 - Which authorization objects are checked ?

Symptom:

The authorization administrator often does not know which authorization objects are checked in predefined functions (business transactions).

Cause and prerequisites

This question cannot be answered with technical means.

Solution
A)
Please refer to the Customizing Implementation Guide. In the system, choose:

Rel. 2.1 or 2.2
---------------
Tools -> Customizing -> Implementation guide -> Complete version. Select the SAP application you are interested in with F2 (or double-click).
Example in SD: F2 on Environment -> Authorizations -> Define profiles
Example in MM Purchasing: F2 on Materials management -> Purchasing -> Environment data -> Maintain users -> Maintain authorizations
Example in FI Accounting: F2 on Financial accounting -> Financial Accounting -> Environment -> Employees -> Maintain user master records -> Maintain authorizations

Rel. 3.0
--------
Tools -> Customizing -> Implem. projects -> Display complete IMG.
Select the SAP application you are interested in with F2 (or double-click) and proceed as described under Rel. 2.1.
In newer Versions of 3.0:
Tools -> Business Engineering -> Customizing -> Enter -> F2 on the application in question -> ... Subchapter 'Maintain authorizations' Example: F2 on 'Initial Project Accounting (FI/AM/CO)' -> click on 'Financial Accounting' -> click on 'Basic settings in FI' -> click on 'Authorization management' -> Double-click on 'Maintain Authorizations'.
========================================================================

B)
As of Release 3.1G the so-called profile generator exists.
The administrator defines a so-called "position" or "plan position" and, in the process, chooses a set of application components which the system uses to determine the affected transactions. At the same time, an authorization profile is generated for that type of (work center) position that contains the authorization needed for the transaction chosen. When the administrator allocates this position to a user, the system automatically writes the newly generated authorization profile to the user master data.
========================================================================
C)
For individual cases, you can use the trace function to determine which objects are validated within a transaction.

Release 2.1 and 2.2
-------------------
Transaction SE30 -> enter the transaction to be traced -> Execute. Then carry out the transaction and return to SE30. Analyze -> Group hit list and scroll all the way to the end to DIVERSE. There you can find the authority checks and determine the name of the authorization object with double click on the relevant line. This trace determines checks only within a transaction without validating TSTCA, and displays only the names of the authorization objects.

Release 3.0
-----------
The authorization trace is done within the system trace.
Transaction ST01 -> Switch, edit -> click on check box Authorization check. Then click on the arrow next to General filters and enter your user name -> Back. Choose Write options and select To disk -> Back. Choose Trace switch -> Save -> in active system.
Now you can carry out any number of transactions.
To analyze the trace, go back into transaction ST01 and choose Stop.
Then choose Trace files -> Standard options. There, select only Trace for authorization checks and enter your user name in field User.
Choose Accept -> Trace files -> Analyze standard. Double click on the trace file to display a list with all authorization objects that were checked and their values.
=======================================================================

D)
When a user runs into a message, such as "You have no authorization...", he or she can call up transaction SU53 to display the authorization object and values.
In releases 2.1 and 2.2 this requires setting the system parameter
auth_check_value_write_on =1. Please note that this may affect system performance.
In Release 3.0 the parameter
login/auth_check_value_write_on
is no longer needed and the tracing does not affect performance.
========================================================================

E)
Table TSTCA contains only those authorization checks that are carried out by the dynpro processor directly at the start of a transaction.
In most cases, however, additional authorization checks are done in the ABAP/4 coding. These are not contained in table TSTCA.
There will possibly be another table in 3.0 which will contain all authorization objects directly checked by each transaction.

SAP Note 18523 - Using INDX in the Report Writer

Symptom:

There are problems with table INDX.
Stichwort: Report Writer

Cause and prerequisites

The Report Writer stores data in table INDX. Since INDX is also used by other applications, it is possible that the table is full.

Solution

The Report Writer stores the following data in table INDX:

1. If you generate a report group, all data relevant for the report definition is stored in INDX. This guarantees a fast access on the report definition when executing a report group. This data is deleted automatically if the report group is deleted.

2. If you execute a report group, you can select the indicator 'Save data permanently' on the selection screen. The report then stores the currently read movement data with which the report is created. However, this is only useful if the report for this data is to be output several times. You can list the stored data via transaction GR55 (Execute Report Group). To do this, choose the function 'Saved data...' (from the 'Utilities' menu. On the selection screen, you can enter intervals, if required. You receive a list of all saved data. You can either delete or output the data.

SAP Note 18506 - Infty P0025 Per. reviews, features duplicated

Symptom:

When overwriting field "number" or "correction" in Infotype 0025 "Personnel reviews", the corresponding entry is duplicated.

Cause and prerequisites

'0' is entered in the "Weighting" field of the corresponding entry.
A personnel review feature may not be assigned '0', because:

An entry with weighting '0' is interpreted by the program as if a manual entry were made and the entry were appended to an internal table with weighting = '0'. All entries for this internal table are displayed on the screen.

Solution

There are two reasons why an entry can have a weighting of '0'.

The 'Weighting' field in Table T513H (as of 3.0A view V_T513H) is not completed.

Solution: maintain table entry.

In the maintain screen for Infotype 0025, the "Weighting" fields are switched off via screen modification. As a result, the weighting is set to '0'.

Solution: Switch on the "Weighting" fields again.

Additional key words

Personal reviews, MP002500, P0025, I0025

SAP Note 18487 - Displaying fields ready for input in lists

Symptom:

When setting up a list, fields ready for input (FORMAT INPUT) are displayed that are empty at the time of the output. The lines with these fields are not displayed in the list.

Cause and prerequisites

All fields that are displayed in this line are "empty" (contents SPACE) As a result, these lines are automatically suppressed (standard setting: SET BLANK LINES OFF = Suppress blank lines).

Solution
SET BLANK LINES ON in the ABAP/4 program changes the setting: blank lines are no longer suppressed.

SAP Note 18472 - Unassigned plan or actual values

Symptom:

Yo carry out a results analysis or a WIP calculation. In the single processing of results analysis, unassigned plan or actual values are displayed. In WIP calculation, the displayed work in process is lower or higher than expected. Costs or credits are not taken into account under some cost elements.

Other terms

Transactions KKA1, KKA2, KKA3, KKAI, KKAJ, KKAK, KKAO, KKAX, KKAS, KKAV, OKG5, OKGB, plan data, actual data, message KJ 161, masking

Reason and Prerequisites

Customizing setting

Solution

1. Check in the results analysis version's customizing whether the assignment of cost elements to line IDs is made with or without selection key.

2. Make sure that in the customizing of the assignment the Valid-from period includes all periods in which costs and revenues were posted.

3. Check whether all cost elements are assigned to a line ID explicitly or in masked form in the customizing of the assignment. Please take into account that numeric cost elements should be padded with zeros from the left and alphanumeric cost elements should be padded with blanks from the right.

Example: Numeric cost element 400000 is to be assigned.
Entry in field cost element: "0000400000" <= correct
Entry in field cost element: "400000 " <= incorrect

Example: Alphanumeric cost element ABC is to be assigned.
Entry in field cost element: "ABC " <= correct
Entry in field cost element: " ABC" <= incorrect

4. All fields whose contents are not to be used for the assignment of a line ID are to be masked with "+" characters. Make sure that all positions are masked with "+".

Example: The assignment to a line ID is to be made independent of the business process. In this case, fill the relevant field with "++++++++++++".

5. You check in particular whether in primary cost assignment all material origin groups are assigned. Field Origin should be filled with "+" characters, if the material origin groups are not to be assigned as a criterion for the assignment.

Information relevant to results analysis only:

7. Cost element-related overall plan values from unit costing are assigned to the opening period of the object to be selected. With this period, the plan costs are assigned to a line ID. Cost element-related annual plan values from unit costing are updated in the first period of the year. Results analysis does not assign any other period to these values.

8. Overall values and annual values (i.e. plan values without cost element relation) are assigned to the valuation method of a line ID in the Customizing expert mode. Overall values and annual values can occur with projects and internal orders.

All plan or actual values so far not assigned for the reasons given are listed under line ID $01 in the long log of the single processing of the results analysis. Line ID $01 is assigned internally in the program.

As of Release 4.5, you can display the unassigned cost elements in the long log of the single processing of the results analysis. Set the ID "Long log" before you carry out the results analysis. In the overview screen with the selection data, select "Logs -> Parameter list" from the menu. The program displays a list. At the end of the list, you find a collection of a unassigned values. Values assigned to a line ID of category N are not included. The values of these line IDs are, howerver, displayed as not considered in the overview screen with the selection data.

SAP Note 18446 - HR connection to various subsystems

Symptom:

Can you install various subsystems (such as Interflex) in parallel?

Cause and prerequisites

This is a consultant's question.

Solution
Basically, yes. There is no negative impact on the HR system if the time events are recorded and confirmed on different subsystems. It is useful to assign a person from the plant data collection group to one of the closed subsystems.
You can combine subsystems and plant data collection groups, so that the mini master records that are processed by the subsystem can be transferred to all or to assigned subsystems.
Because the subsystems cannot communicate with each other, the plant data collection groups must evaluate which employees should be allowed to record times in which subsystems.
You should determine the answers to these questions before you make the group assignments and transfer the master data to the subsystems.
It is also helpful to download the master data for several days in the future, if the access control is not going to take place for several days.
Table T555I controls the master record information (time types, remaining leave, etc) should be transferred to the subsystem.
Because HR itself generates time pairs (together with the day programs) based on the times that the subsystem confirms, it does not make sense to carry out a status check in a subsystem (that is, check whether the recorded time is a clock-in or clock-out). This status checking can be turned off in the INIT file of the subsystem.

SAP Note 18420 - Taking over old asset data - accumulated values cannot be en

Symptom:

You cannot enter accumlated values when taking over old asset data.
Key words: AS91 AS94 Taking over old data

Cause and prerequisites

You have flagged the asset class as a class for line-item settlement.

Solution
In asset classes for line-item settlement, you must enter accumulated values as transactions in the transaction screen. Press the pushbutton "Transactions" to do this".
If you do not require this, you must change the asset class or use a different one.

SAP Note 18416 - PA40 - Batch input data not found

Symptom:

PA40
A batch input session that is processed in the background is handled differently by the system than a batch input session that is processed in the foreground. Data for a different screen sequence is expected.

Cause and prerequisites

The events menu for PA40 and the Info groups of the events can be defined on the basis of user groups. The user group is determined at run time from the user parameter "UGR".
If no menu and/or info group is found for the user group, the data is determined with the reference user group.
For background processing, no user parameters are read, which means that the reference user group is always used.
If the reference user group differs from the user group in the user master, data in the session is not passed to the screens that were actually called.

Solution
The screens in the batch input session must always correspond to either the menu and/or the Info group that belongs to the reference user group.
Furthermore, we suggest that you do not program any batch input to PA40, because the events sequence must be intrepreted to the menu. Batch inputs should be carried out to PA30.

Set the following fields:
RP50G-CHOIC = '0000' (Events)
RP50G-SUBTY = '10' (Current event type, e.g., hiring)
RP50G-BEGDA = entry date
FCODE = 'INS'/'COP' (insert, copy)

SAP Note 18410 - Withholding tax field not present in credit memo

Symptom:

No withholding tax amounts (withholding tax base amount) can be entered when you enter a credit memo. Can also occur when entering an invoice (general transaction MR01).

Cause and prerequisites

The field status selection does not display the fields for the involved posting keys 21 (credit memo) and 31 (invoice).

Solution
Call transaction OB41 and change the field status (see button) for posting keys 21 and 31 for taxes: set the withholding tax fields to "Ready for input".

SAP Note 18397 - Quantity-specific delivery costs for goods receipt

Symptom:

If a goods receipt takes place for a purchase order and a varying quantity is entered in the order price unit, this quantity is ignored when calculating the quantity-specific delivery costs.

Cause and prerequisites

Quantity-specific delivery costs are always posted in proportion to the order quantity. If 50% of the ordered quantity is delivered, then 50% of the planned delivery costs are posted upon goods receipt.
If the delivery costs are defined in a varying unit of measure, the conversion factor of quantity to purchase order unit defined in the condition is applied to the goods receipt. This also applies when the unit of measure in the condition is the same as the purchase order unit.

Reason:
It is possible to define units of measure with separate conversion factors in the condition. These always refer to the quantity in the order unit. Even when the unit of measure of the condition is the same as the order price unit, the conversion factor in the condition may still differ from the conversion factor for the order units.

Example: Order unit: ,, pc
Order price unit: ,, kg (1 pc = 90 kg)
UoM of the condition: ,, kg (1 pc = 100 kg)
For this reason, the conditions are always posted proportionally to the order quantity.

Solution
Plan your provisions for delivery costs in the order as precisely as possible. If necessary, you can manually change the planned delivery costs in the purchase order again before posting the goods receipt.
The actual delivery costs are adjusted upon invoice receipt.

SAP Note 18391 - Reports with authorization groups in jobs

Symptom:

When you schedule a report (that has been assigned an authorization group in the report attributes) in a job using transaction SM36, function module JOB_SUBMIT, or ABAP language element SUBMIT VIA JOB, the system issues an error message that states that the user is not authorized to schedule the report as a job. This message also appears in Syslog with the designation "EG1".

Other terms

P_ACTION, P_GROUP.

Reason and Prerequisites

There is an authorization problem.

Solution
When you assign an authorization group to a report, the user, who wants to perform the report in the background, must have the following authorizations for authorization object "ABAP program flow checks" (S_PROGRAM):

- User action = BTCSUBMIT
- Authorization group = Name of the authorization group that was specified in the report attributes

SAP Note 18389 - Pricing variant: Condition is generated twice

Symptom:

1.) A variant-dependent condition determined per action is generated twice.
2.) A variant-dependent condition drags twice during new pricing.

Cause and prerequisites

1.) The access sequence is set incorrectly.
2.) Program error.

Solution
1.) If several accesses are defined in access sequence VA00, one of these accesses should be indicated as exclusive.

Usually one single access with the following reference or source fields is sufficient:

Access 10 Table 57 Sales organization = Sales organization
Distribution channel = Distribution channel
Material = Pricing refer. material
Variant = Variant
2.) Correction to 3.0D.

Additional key words

VA00 Configuration configure configured KMAT

SAP Note 18388 - Pricing variant: Only one condition is generated

Symptom:

Although several values or keys are to be found per action(s) for condition records of condition type VA00, only one condition record is found each time.

Cause and prerequisites

The object characteristic with allocation to DDIC field KOMG-VARCOND was not defined as multiple-value characteristic.

Solution
Delete the reference object and create it again in two steps:

1. Maintain the basis data, especially 'Several valuations' = X
(input control block)
2. Maintain additional data and the allocation to DDIC field KOMG-VARCOND
CAUTION: All relationships to which the reference object was cross-
referenced must be regenerated/updated from the editor
after the recreation.

SAP Note 18380 - Error message: 777 -Sequence key OC0001 not defined

Symptom:

In maintenance orders, error message 777 occurs: 'Sequence key OC0001 for operation validation is not defined'.
IW31, IW32 - SAPLCOKO, SAPLCOIH ( OC0002 ).

Cause and prerequisites

Entries missing from tables TCO60 or TCO62.

Solution
Please make the following entries in table TCO60:
(with transaction SM31)

Ctg SeqKey
----------
30 FCHECK
30 OC0001
30 OC0002

Please include the following entries in table TCO62:
(with transaction SM31)

Ctg SeqKey Description VerifNo Program
Grp. Panel
------------------------------------------------------------------------
30 FCHECK Validation PRT allocation PM order 1 SAPLCOFD
ED 0100
30 FCHECK Validation PRT allocation PM order 2 SAPLCOFD
ED 0120
30 FCHECK Validation PRT allocation PM order 3 SAPLCOFD
ED 0140
30 OC0001 1 SAPLCOIH
VD 3100
30 OC0002 1 SAPLCOIH
VD 3110

Additional key words

CT777

SAP Note 18379 - Balance carried forward: carry forward account in company...

Symptom:

UKSymptom
When running the balance carry forward program (SAPFGVTR) in the Special
Purpose Ledger, the following error message is issued for global ledgers:
Balance carry forward account not created in global company.

Cause and prerequisites

This can have several reasons:

- The retained earnings account for global data has not been correctly maintained

- The global company in question has not been allocated to a master record company code

Solution

First check the retained earnings account:

Special Purpose Ledger Configuration menu: Periodic processing -> Balance carr.forward -> Retnd earning acct -> Global.
Here you must define a valid account for the chart of accounts (as assigned to ledger/global company level) and the income statement type (defined in the account master), into which the balance from the income statement accounts is carried forward.

If this setting has been made correctly, then check the how your global company is defined. If no master record company code has been assigned to it, you have two options:

You can enter a company code with the same chart of accounts such as at the ledger/global company level.

You can write your own master record exit for this global company table, which validates the accounts with the chart of accounts (Program SAPLGUMD), and enter this new exit in your table, starting from the Special Purpose Ledger Configuration menu: Environment -> Master data -> Integr.master data.

Additional key words

Balance carry forward, SAPFGVTR, RGVTRnnn, GVTR, global ledger

SAP Note 18370 - ABAP/4 query: Use of credit/debit fields

Symptom:

If a total is calculated using a credit/debit field in a query, the field contents were added, regardless of the credit/debit indicator (e.g. positive values were always added). This resulted in incorrect totals, since the credit amounts must be subtracted from the total.

Cause and prerequisites

Credit/debit fields always have (positive) amounts. The +/- sign required for calculating the total can only be derived from the corresponding credit/debit indicator.
The relationship between the credit/debit field and the credit/debit indicator is not stored in the SAP System, which means that 1) the system cannot determine which fields are credit/debit fields, and 2) the system cannot determine which field is to be used as credit/ debit indicator for a credit/debit field. The query is therefore not capable of totaling credit/debit fields based on the corresponding credit/debit indicators.

Solution
If you need to calculate using credit/debit fields in queries, you must define the functional area as follows:
The credit/debit field of the logical bank is not included in the functional area. Instead, an additional field is defined with the same characteristics as the credit/debit field (use LIKE). The coding for the additional field consists of the assignment of the value of the credit/debit field, and and +/- sign is reversed, when necessary, based on the corresponding credit/debit indicator.
The additional field must be added to the functional area in place of the credit/debit indicator. The additional field enables you to calculate the correct totals in the queries.

SAP Note 18369 - Profit center not transferred from SD to FI

Symptom:

Profit center is not transferred from the billing document to FI.

Cause and prerequisites

Standard procedure

Solution
In the standard system, the transfer of the profit center from the billing document is not performed using the SD/FI interface in the standard system but rather using the LIS interface (Table S007) to Profit Center Accounting. Thus, the profit center is not to be found in the FI document.
A possible modifcation is described in note 25686.

SAP Note 18356 - Value update for non-valuated material

Symptom:

A value update is carried out for material with material type UNBW (non-valuated).

Reason and Prerequisites

Incorrect Customizing.

Solution
In Transaction OMS2 in Table T134M, you have to deactivate the value update button. In Table T156S, no value string may be entered for the movement type.

SAP Note 18348 - Field overflow in MD01 / MD02 / MD03 / MD04 / MD05

Symptom:

Field overflow in the materials planning transactions, for example, MD04.

Cause and prerequisites

QUAN15 fields from the SD system are copied in QUAN13 fields.

Solution
The error can occur in program "SAPLM61X" in FORM routine "PRUEFEN_VBBS". Statement: MOVE VBBS-OMENG TO MDPSX-MNG01.
Here, a field overflow could occur theoretically. This, however, can always be avoided in everyday work, if the unit of measurement in Sales and Distribution and the base units of measure are set usefully.
If, for example, a material is sold in tons and scheduled in grams, the sales unit may at most be 9999 t. For 10000 t, a field overflow occurs. You should then schedule the material at least with the base unit of measure kilograms.

SAP Note 18331 - IS-H Check digits calculation procedure

Symptom:

The check digit calculated appears to be incorrect.

Cause and prerequisites

Possible differing procedures in several systems.
In IS-H, the check digits are calculated exclusively according to "DIN ISO 7064, MOD 11, 10". Another way of calculating them is not provided.
For purely numeric keys, the leading zeros are always also transferred. This leads (automatically) to the number of digits corresponding to the field for the calculation. Be sure to take this into account during tests. Checks of individual check digits or of check digits in programs must ensure the correct field length with leading zeros.

Solution
In IS-H, the check digits are calculated according to "DIN ISO 7064, MOD 11, 10". The exact documentation must be obtained from BEUTH Verlag in Berlin (Tel. +49-30/26010) (Sole vendor).

Here, only the recursive calculation procedure (for control purposes):

Character string processed from left to right;
N => Number of digits in the string including check digits;
J = 1, 2, ..., N => Index;
a(J) =>character value of the Jth position (a(1)=check digit at right!);
P(1) = 10 => initial value.
Calculate:
S(J) = P(J)|11 + a(N-J+1)
P(J+1) = S(J)||10 x 2
Here,
||10 => remainder of division by 10; if this equals zero, insert 10
instead;
|11 => remainder of division by 11 (never equal to zero).
String is correct is S(N) = 1 (mod 10).
Check digit a(1) is created so that:
P(N)|11 + a(1) = 1 (mod 10).

Additional key words

ISH_TEST_DIGIT, module, check digit procedure, consulting

SAP Note 18330 - Partner: Sales employee in the sales document (VA01)

Symptom:

In the order, the partner selection dialog box for sales employees displays the wrong names, or the document is incomplete because the address is missing.
Furthermore, error message VP250 'HR master record does not exist' is displayed in sales documents and in the customer master if the sales contact is not authorized to display HR master data.
In addition, the private address and not the business address is displayed in sales documents.

Cause and prerequisites

Infotype 0006 in HR has not been maintained or the sales contact is not authorized to display address data of the sales employees. Both cases were not covered by the program.

Solution
Program change in the following programs:

1. LV05ETOP und LVADRTOP:

TABLES: P0001, T001W. "<-- new line

2. LV05EFAD:

Change WHEN 'PE' branch as follows:

WHEN 'PE'.
PERFORM READ_INFOTYPE(SAPFP50P)
USING VTCOM-PERNR '0001' SPACE SPACE SPACE
SY-DATUM SY-DATUM '1' 'NOP' P0001.
IF SY-SUBRC = 4.
Personalnummer nicht da
IF VTCOM-MSGKZ NE 'U'.
MESSAGE E250 WITH VTCOM-PERNR RAISING NO_PERNR.
ENDIF.
ELSE.
IF T001W-WERKS NE P0001-WERKS.
SELECT SINGLE * FROM T001W WHERE WERKS = P0001-WERKS.
ENDIF.
IF T001W-WERKS = P0001-WERKS.
MOVE-CORRESPONDING T001W TO LKUPAV.
LKUPAV-NAME3 = T001W-NAME1.
LKUPAV-NAME4 = T001W-NAME2.
ENDIF.
LKUPAV-NAME_LIST = P0001-ENAME.
LKUPAV-NAME1 = P0001-ENAME.
* keine Berechtigung zur Anzeige
* RAISE NO_AUTHORIZATION.
ENDIF.
RP-READ-INFOTYPE VTCOM-PERNR 0002 P0002 SY-DATUM SY-DATUM.
LOOP AT P0002.
MOVE-CORRESPONDING P0002 TO LKUPAV.
LKUPAV-SPRAS = P0002-SPRSL.
SELECT SINGLE * FROM T522T WHERE SPRSL = SY-LANGU
AND ANRED = P0002-ANRED.
LKUPAV-ANRED = T522T-ATEXT.
EXIT.
ENDLOOP.
WHEN OTHERS.
IF TPAR-NRART(1) = 'Y' OR TPAR-NRART(1) = 'Z'.
CALL FUNCTION 'RV_PARTNER_EXIT'

3. LVADRU01:

Change WHEN 'PE' branch as follows:

WHEN 'PE'.
PERFORM READ_INFOTYPE(SAPFP50P)
USING VBPA-PERNR '0001' SPACE SPACE SPACE
SY-DATUM SY-DATUM '1' 'NOP' P0001.
IF SY-SUBRC = 4.
IF MESSAGE = 'X'.
* Personalnummer nicht da
MESSAGE E250 WITH VBPA-PERNR.
ENDIF.
ELSE.
IF T001W-WERKS NE P0001-WERKS.
SELECT SINGLE * FROM T001W WHERE WERKS = P0001-WERKS.
ENDIF.
IF T001W-WERKS = P0001-WERKS.
MOVE-CORRESPONDING T001W TO VBADR.
VBADR-NAME3 = T001W-NAME1.
VBADR-NAME4 = T001W-NAME2.
ENDIF.
VBADR-NAME_LIST = P0001-ENAME.
VBADR-NAME1 = P0001-ENAME.
* keine Berechtigung zur Anzeige
* RAISE NO_AUTHORIZATION.
ENDIF.
RP-READ-INFOTYPE VBPA-PERNR 0002 P0002 SY-DATUM SY-DATUM.
* RP-READ-INFOTYPE VTCOM-PERNR 0006 P0006 SY-DATUM SY-DATUM.
LOOP AT P0002.
MOVE-CORRESPONDING P0002 TO VBADR.
VBADR-SPRAS = P0002-SPRSL.
SELECT SINGLE * FROM T522T WHERE SPRSL = SY-LANGU
AND ANRED = P0002-ANRED.
VBADR-ANRED = T522T-ATEXT.
VBADR-PARGE = P0002-GESCH.
EXIT.
ENDLOOP.
ENDCASE.
ENDIF.

SUBRC_PRIVATADRESSE = 0.

20.1.11

SAP Note 18319 - Difficulties with the batch input log file

Symptom:

Difficulties occur when accessing the batch input log file.
Up to now we are aware of the following:

btccllog0592
> Function BtcClFindPart btccllog0592
Job log file ID not found
Failed to open log partition
> Funktion BtcClWrEntry btccllog1574
> Transaction No: 0 Block No: 0
> Error creating batch input log
or
Error editing job log file
> Log file btccllog1703
> Function BtcClRmPart btccllog1703
Log partition does not exist

Cause and prerequisites

The log file is corrupt (end identifier is missing).

Solution

The log file or files are in the directory /usr/sap//SYS/global and have the name BI
for example: System K11 Server hs1033 Instance 00
File: /usr/sap/K11/SYS/global/BIhs103300
A reorganization file is created for reorganization.
Up to Release 2.2C it has the name /usr/sap/K11/SYS/global/BDCREORG.
As of Release 3.0D it has the name //BI
Example: /usr/sap/K11/D00/data/BIhs103300

Solution:

Find the corrupt log file (possibly RSBDCLOG and execute in debugging BREAK-POINT in FORM routine LOG_DIR, field LOGNAME).

Remove the corrupt log file (remove or rename on operating system level. The renamed file must not start with BI).

Find the reorganization file in the DATA directory ().

Copy the reorganization file under the old log name to precisely the same position.

If you cannot find a reorganization file, delete the corrupt log file nevertheless since otherwise no batch input will run any longer.

Caution:
Up to Release 3.0C!!!:
The reorganization of the logs must always run separately. No batch input may be processed in parallel. Take this into account.

All valid releases:
An overflow of the file system is the most frequent cause for a corrupt log file. In particular for large or a great number of batch input sessions, provide sufficient disk space in the global directory.

Additional key words

btccllog

SAP Note 18307 - Batch input logs and reorganization

Symptom:

Batch input logs.

Cause and prerequisites

Batch input: Log reorganization.

Solution

You call report RSBDCREO (or schedule it in the background) and reorganize your logs.
What does 'Reorganization' mean?

The report has the following functions:

2. It deletes logs without sessions.

Technical information for log reorganization:

The logs are in the GLOBAL directory of the SAP System path:
/usr/sap/C11/SYS/global "Where C11 is the system name
Name of the log file 'BI' e.g. BIserver00

The logs are reorganized
until Release 22D in the GLOBAL directory
as of Release 22E in /tmp (DIR_TMP)
Application Server Directory
as of Release 30D on DIR_DATA
Application Server Directory

Important:
In the directory (GLOBAL or DIR_TMP or DIR_DATA), there must be space available at the time of the reorganization. An approximate value is the size of the log file.

Example:
Log file BIserver00 with a size of 125 MB.
An additional 125 MB are needed to reorganize this file.

For a better understanding, the following section describes how the reorganization is carried out from a technical viewpoint.

4. The log file is copied into the reorganization directory (bdc/altlogfile). A semaphore locks the file.

5. The reorganization file is shrunk to it true size.

Plan your reorganization runs well in advance. Smaller files are processed more quickly.

Note: Release 2.1A - 3.0C
Report RSBDCREO must always run alone: that means, you must not run a batch input in parallel. Refer to Note 34427.

Additional key words

APQD APQI

19.1.11

SAP Note 18295 - Incorrect zip code or PO box in address

Symptom:

When printing the purchase order, the PO box or zip code is not printed correctly.

Cause and prerequisites

Error in SAPScript layout set MEDRUCK.

Solution
Correct layout set MEDRUCK as follows:
SE71 -> MEDRUCK -> Create/change -> Goto -> Windows -> Text elements Select ADDRESS -> Edit -> Text elements.
Make the changes and save and activate the layout set.
Then the text element should be as follows:
ADDRESS PARAGRAPH AS
TITLE &LFA1-ANRED&
NAME &LFA1-NAME1&, &LFA1-NAME2&, &LFA1-NAME3&, &LFA1-NAME4&
STREET &LFA1-STRAS&
POBOX &LFA1-PFACH& CODE &LFA1-PSTL2& (No comma before CODE)
CITY &LFA1-ORT01&, &LFA1-ORT02&
POSTCODE &LFA1-PSTLZ&
COUNTRY &LFA1-LAND1&
REGION &LFA1-REGIO&
FROMCOUNTRY &T001-LAND1&
ENDADDRESS

Note:
If the first line is ADDRESS DELIVERY PARAGRAPH AS, street and PO box are always printed, even if PO box and zip code are maintained in the vendor master.
If the first line is ADDRESS PARAGRAPH AS, PO box number and zip code are printed if they are maintained in the vendor master. If the PO box is not maintained in the vendor master, the street is printed.
The layout set can be generated from client 000 or the current client. You have to keep in mind that the correct key for the address setup is maintained in table T0005 and that the correct country key is maintained in table T0001-LAND1.

SAP Note 18289 - Output tax cannot be changed

Symptom:

If you change and store the output tax, the system does not actually store the value.

Cause and prerequisites

Data discrepancy caused by an incomplete transport between two systems.

Solution
With the following program, you can analyze and correct the conditions. The program analyzes and deletes incorrect conditions, if necessary. Be careful when using this program.

SAP Note 18281 - CCMS log display after recovery with "Reset logs"

Symptom:

Oracle redo logs are displayed as saved (already archived), although they have not been (in CCMS, DB12, status of most recent logs).

Cause and prerequisites

A recovery was run with "Reset logs"; in Oracle version 7 and later, the log sequence number is reset to 1 (that is, the same numbers are used again). In CCMS, however, the information that a given log file has been archived was not reset.

Solution
This short ABAP report will delete the CCMS (brarchive) history.
report fixsdbah.
SDBAH is the header table, SDBAD the detail table:
exec sql.
delete from sdbah where
funct in ('sve','cpy','ssv','svd','cpd','ssd','dsv','dcp','cps','cds',
'SVE','CPY','SSV','SVD','CPD','SSD','DSV','DCP','CPS','CDS')
and beg > '19910000000000'
and beg < 'Datum des Restores in YYYYMMDDHHMMSS- Format'
endexec.
exec sql.
delete from sdbad where
funct in ('sve','cpy','ssv','svd','cpd','ssd','dsv','dcp','cps','cds',
'SVE','CPY','SSV','SVD','CPD','SSD','DSV','DCP','CPS','CDS')
and beg > '19910000000000'
and beg < 'Datum des Restores in YYYYMMDDHHMMSS- Format'
endexec.

SAP Note 18273 - DELETE DATASET returns SY-SUBRC = 4

Symptom:

The ABAP/4 language element

DELETE DATASET .

sets SY-SUBRC to 4.

Cause and prerequisites

The specified file could not be deleted.

Solution
There are various possible causes:

1) The specified file does not exist
2) The specified file is a directory
3) The SAP system cannot search for a component of the specified
file name (search path)
4) The SAP system has no write access to the directory containing
the specified file.
5) A component of the search path is not a directory
6) The file is a symbolic link that cannot be expanded (loop?)
7) The specified file is a program that is currently running.

SAP Note 18254 - Material listing and exclusion with batch

Symptom:

The material listing and material exclusion are not checked for fields entered later.

Cause and prerequisites

The check is run only when the material is first entered.

Solution
Problem Note 19014 solves that special case of batch inputs entered later.

SAP Note 18236 - R3trans: Export to tape / Splitting the export

Symptom:

Customer wants to export data with R3trans. If there is not enough storage space on the hard disk, or if the export exceeds the maximum file length, the following possibilities are available:

Write the export directly onto the tape.

Split or compress the export with "R3chop" (as of 3.0B).

For a client transport you can also use a remote copy as of Release 4.0.

Attention: This note is valid only until and including Release 4.0B. Note 86535 is valid as of Release 4.5.

Cause and prerequisites

Lack of space, limited maximum file length

Solution

The following solution works only for UNIX operating systems.

The 'named pipe' concept allows the exchange of data between two processes (on one computer), where one process writes to the pipe and the other reads that data. The 'named pipe' itself can be regarded as a file with a maximum length which can be rewritten to only once the reading process has completely read the contents already written.
In the following case R3trans writes to such a 'named pipe'; it is then read from by "dd" and written to tape or split into various files with "R3chop".

Usage of R3trans directly:

The filesplit is slightly easier when working directly with R3trans, therefore this case is described first. Nevertheless, please notice that exports and imports are normally performed by using the transport control program tp (see below).

Proceed as follows:

1. For the export, you require an R3trans control file in which the file is specified, among other things:

export
file = '/usr/sap/trans/data/'

2. Create the named pipe:

mknod /usr/sap/trans/data/ p

3. Start the read process:

Export to tape:
dd if=/usr/sap/trans/data/ of= bs=16k &
or
Split and/or compress with "R3chop":
R3chop -ecf -p -l &
(For details on R3chop see Note 37626)

4. Now start R3trans. It will write to the 'named_pipe' from which the process started in 3) will read.

5. The import functions analogously:

Maintain the R3trans control file

import
file = '/usr/sap/trans/data/'

Create the 'named pipe' (if it does not already exist)

Start the process which writes to the pipe (dd or R3chop)

When you have split the export with R3chop into several files, then the corresponding command, would be, for example:

cat | R3chop -icsf /usr/sap/trans/data/

where are the files from the above parameter file of the R3chop (thus )

Start R3trans

Caution:
The processes 'dd' or 'R3chop' terminate as soon as R3tans has read in the named pipe once. Since R3 trans (or tp) could read in the named pipe more than once (namely if DD objects are contained in the transport), the write process ("dd" or "R3chop") might have to be started again.
This is done by entering the command "dd" or "R3chop" from step 5 as soon as R3trans is started a second time (can be seen from the message written after stdout).

Using tp:

In principle, the same steps are necessary as described already for the direct use of R3trans. In contrast to the direct use of R3trans, you cannot influence the following when using tp:

When R3trans is started.

Which data file R3trans uses.

The consequences should be described here.

not

2. Determine the name of the data file from the name of the transport request (example: 'C11KT00031').

a) Append a period ('.') to the name of the request (example: 'C11KT00031').

b) Remove the first three letters of the name and append these to the end (example: 'KT00031.C11').

c) Change the first letter from 'K' to 'R' (example: 'RT00031.C11').

3. Create the complete path of the data file from: your transport directory, the subdirectory 'data' and the name of the data file. Create a "named pipe' of this name:

mknod p

Example:

mknod /usr/sap/trans/data/RT00031.C11 p

of= bs=16k &
or splitting and/or compression with "R3chop":
R3chop -ecf -p -1 &
(For details on R3chop, refer to Note 37626)

5. Start tp for export, for example:

tp export c11kt00031 u1 -Dtestimport=0

Before

a) start up the process which writes to the 'named pipe' (dd oder R3chop) or

b) delete the 'named pipe', create an empty file with the name of the data file and recreate the 'named pipe' after the 'ADDTOBUFFER'. Example:

cd /usr/sap/trans/data

rm RT0031.C11

touch RT00031.C11

tp addtobuffer c11kt00031 p11 pf=/usr/sap/trans/bin/TPPARAM

rm RT00031.C11

mknod RT00031.C11 p

7. Start tp for import.

8. Whenever you see on the screen that R3trans appears (maximum twice for an import), start the process which writes to the 'named pipe' (dd or

When you have split the export with R3chop into several files, then the corresponding command, for example, would be:

cat | R3chop -icsf /usr/sap/trans/data/

where are the files from the above parameter file of the R3chop (thus )

Problems:

2. The R3chop program is no longer delivered in Release 4.0A/B. To also enable the functions described in this note for Release 4.0A/B, the R3chop for Release 4.0 is made available on the sapservX in the directory ~ftp/general/R3server/patches/rel40B/UNIX/. Refer to Note 19466 for details on how to retreive this program.

SAP Note 18228 - AM reports without G/L account in totals line

Symptom:

In asset reports using valuation areas where reconciliation postings are not made in FI (e.g. cost-accounting depreciation) with sorting by G/L account (e.g. sort variant 0001), the totals for each G/L account are displayed, but the account numbers for some account assignments are not displayed. The error occurs both in the totals line in the individual list and in the totals report.
Reports e.g. RAHAFA01 RAGITT01 RABEST01

Cause and prerequisites

Table T095 contains an unnecessary entry for the affected account assignments and valuation areas with reconciliation account " " for acquisition and production costs (field KTANSW in T095).
This entry is only legal when stock values are posted for an area, either online or periodically (flag BUHBKT in T093). This flag may have been changed at some point.

Solution
Use transaction SM31 to delete the unnecessary entries from table T095.

SAP Note 18217 - Termination CO168 with number range object AUF_PLAN

Symptom:

Termination in CO01: Create production order

Cause and prerequisites

Number range interval 01 not maintained for object AUF_PLAN.

Solution
Use transaction SNRO to maintain the appropriate number range object - that means, define the group and assign a new internal to the group.

Check whether the table TC004 contains the entry for order category 10 and operation number range interval 01 - or else maintain it manually.

SAP Note 18206 - Valuation type during the goods receipt

Symptom:

1. If a valuation type is set in a purchase order (or production order) item that is not assigned to an account, the goods receipt is always posted to this valuation type. However, if you enter a batch during the goods receipt with a different valuation type, the goods receipt is rejected by the system.

2. If no valuation type is set in a purchase order (or production order) item that is not assigned to an account and if no goods-receipt based invoice verification is declared in the purchase order item, the valuation type the goods receipt is posted to is saved in the purchase order (or production order) item during the first goods receipt. As a result, all following goods receipts have the valuation type of the first goods receipt.

3. If no valuation type is set in a purchase order item that is not assigned to an account and if a goods-receipt based invoice verification is declared in the purchase order item, different goods receipts can be made for different valuation types. Other terms

M7043, split valuation, individual batch valuation, single valuation,
batch single valuation, valuation type, batch-specific unit of measure
with valuation, active ingredient value assignment,
MBEW-KALNR, MBEW-KALN1, BWTTYX, BWTTY X, EKPO-WEBRE

Reason and Prerequisites

The system is set this way so that the user, on the one hand, can determine the valuation type for which the goods receipt is to be made.
The invoice verification, on the other hand, that is not based on a goods receipt requires a unique valuation type for the purchase order item so that subsequent debits by the invoice verification can be debited to the correct valuation type.
During the goods-receipt based invoice verification, this allocation is made via the goods receipt document.
For the production order, a unique assignment to a valuation type and thus to a cost estimate number is required for a correct order settlement and cost estimate. For the order settlement as well as for invoice receipt it must be ensured that a possible subsequent debit is made to the correct valuation type. The valuation type is needed for the cost estimate to be able to assign the costs to the correct valuation segment and thus to calculate the price for each segment.

Solution
In case, you want to post different goods receipt for one purchase order item to different valuation types, do not enter a valuation type in the purchase order item and use the goods-receipt based invoice verification instead. This procedure is especially useful for the individual batch valuation.
In the area of production and process orders, there is no comparable solution with the invoice verification related to goods receipt. The solution is provided using co-products.

SAP Note 18185 - Balance sheet/profit and loss statement transport

Symptom:

Tranporting balance sheet/profit and loss statement versions fails with the error message: ' INDX-like tables cannot be edited'.

Cause and prerequisites

Report RSCLICOP cannot transport INDX-like structures.

Solution
Please use R3TRANS. The function of R3TRANS is described in note 1942.

SAP Note 18174 - CUA Release strategy

Symptom:

Purchasing -> Purchase requisition -> Create/Change/Display and then select "Release strategy" --> CUA: User interface missing.

Cause and prerequisites

Unknown

Solution
Use transaction SE41 to generate the interface of program SAPLEINH.

SAP Note 18173 - Minimum order value

Symptom:

This consultant note describes how you can implement the function of the minimum sales order value in R/3 pricing. For details on the use and work method of these functions, see the online documentation under:

Logistics -> Sales and Distribution -> Basic functions and master data in Sales and Distribution processing -> Basic functions in Sales and Distribution -> Conditions and pricing -> Special pricing functions -> Minimum sales order value

Cause and prerequisites

The problem is caused by the Customizing settings.

Solution
General settings
This function was implement via the new condition types
AMIW Minimum sales order value
AMIZ Proposed minimum value
and a new condition formula. As of Release 3.0X, value formula 013 is provided for this.

You can also set up the required conditions AMIW and AMIZ in prior releases.

The condition types have the following characteristic values:

AMIW Access sequence K007 (for example)
Condition class A surcharges or discounts
Calculation type B fixed amount
Item condition X
Group condition X
Manual entry D not manually

AMIZ Access sequence K007 (for example)
Condition class A surcharges or discounts
Calculation type B fixed amount
Item condition X
Group condition BLANK
Manual entry D not manually
RefCondType AMIW (Release 3.0 only)
RefApplication V (Release 3.0 only)

Special settings for Release 2.2:

Use Transaction VOFM to create a new condition value formula, for example, 699 which looks as follows:

FORM FRM_KONDI_WERT_699.
IF KOMP-KZWI5 > KOMP-NETWR.
XKWERT = KOMP-KZWI5 - KOMP-NETWR.
ELSE.
XKWERT = 0.
ENDIF.
ENDFORM.

Include the two condition types in your pricing procedure as follows after the net item value to be compared:

Condit. type Stat Print SubTl Cond CalTyp BasVal Acctkey
AMIW X 5 2 2
AMIZ 2 699 ERS

Settings as of Release 3.0X
Include the two condition types in your pricing procedure as follows after the net item value to be compared:

Condit. type Stat Print SubTl Cond CalTyp BasVal Acctkey
AMIW X D 2 2
AMIZ 2 013 ERS

Caution
You have to consider that base formula 002 must be assigned to tax condition MWST, because otherwise the statistical condition AMIW is included in the condition base value.

Additional key words

Minimum sales order value, proposed minimum value, AMIZ, AMIW

SAP Note 18169 - ME21 Copy item text from contract

Symptom:

If the "fixed" indicator in table T165P for copying the item text from the contract to the purchase order (target: F EKPO F01, source: K EKPO K01) is set to "*", the item text of the last contract item is copied to all items in the purchase order.

Cause and prerequisites

Program error

Solution
See the correction numbers listed in this note.
Advance correction possible:
Program MM06EFTE, FORM REFERENZ_KEY_SETZEN_POS:

*--- Referenzbeleg ist ein Kontrakt -----------------------------
CHECK EKPO-KONNR NE SPACE.
CHECK NOT EKPO-KTPNR IS INITIAL.
IF KEKKO-SPRAS NE EKKO-SPRAS.
MESSAGE S132.
ENDIF.
HTEXT-TDSPRAS = KEKKO-SPRAS.
HTEXT-TDNAME(10) = EKPO-KONNR. <--- changed
HTEXT-TDNAME+10(5) = EKPO-KTPNR. <--- changed

SAP Note 18163 - Error GG213: Table GLT2 not supported

Symptom:

During ledger maintenance, the system issues message 213, which states that the totals database used in the ledger (usually GLT2) does not exist.

Cause and prerequisites

Missing system configuration in preparations for extended general ledger.

Solution
Flag the use of the global ledgers (companies) in the Customizing menu of "Extended general ledger" with the function:
Environment --> Preparation (Release 2.1/2.2) and/or via the
implementation guide (IMG) --> Financial accounting -->
Spec. Purpose Ledger --> Global settings --> Carry out preparation
(Release 3.0).

SAP Note 18155 - Variants: TVARV variable / conversion exits

Symptom:

When starting a report with a variant, only the first line of an interval is correct. The other lines are (apparently) interpreted incorrectly or not at all. The problem does not occur if the continuation lines are displayed on the value set screen before the report is executed.
The values for the interval are in this case defined by a TVARV variable and the correponding Dictionary field has a conversion routine.

() ABAPNOTE ABAPRESERR selection screen variant TVARV

Cause and prerequisites

When copying the values from TVARV, the conversion exit is ignored and a simple MOVE is carried out. If the conversion exit places, for example, leading zeros in front of numeric entries, the entries, however, are stored in TVARV without leading zeros, the SELECT-OPTION entry is '8 ' instead of '00000008'. This results in an incorrect selection.

Solution
Up to Release 3.0:
The values in TVARV must be stored in their entire length (with leading zeros, if required).
From Release 3.0A the conversion exit will be taken into account when
the variable is copied.

SAP Note 18153 - Table T237A empty for operating concern

Symptom:

UKSymptom
Drill-down reporting, only COPA.
When working with an operating concern, one notices that no basic entries for the operating concern are included in the tables T237,T237A, T237T. Thus, the entries with the numbers starting at 9000 that can be used in all line structures of the operating concern.

Cause and prerequisites

cannot be reproduced

Solution
In releases 2.1 and 2.2:
Use the transaction KE02, menu option Details, Entry, Rework Conversion. This function creates the entries starting at number 9000.
In Release 3.0:
Use the transaction KEA0. Enter the operating concern and hit the data release button.
Then choose the menu option Edit, generate entry environment. This function creates the entries starting at 9000 again.
Please carry out this function outside of your production operation.

Additional key words

line structure

SAP Note 18129 - INTRASTAT defaults

Symptom:

Defaults for region of destination and nature of transaction are not used when creating a purchase order.

Cause and prerequisites

Missing Customizing. These indicators are not contained in the info record as described in the documentation.

Solution
Maintain the following Customizing tables:
Transaction OMG5 (Maintain Business Ttransaction)
Table T001W with SM31 (Maintain Region)

SAP Note 18128 - Create purchase order: pur. req. is not blocked

Symptom:

Key words: ME21, ME22, ME57, ME58, ME59
Create purchase order with reference to purchase requisition: several users can create purchase orders with reference to the same purchase requisition, but the purchase requisition is not blocked.

Cause and prerequisites

This is not an error!
The purchase requisition is intentionally not blocked.
Reason: before a purchase order with reference to a purchase requisition is created, a list of purchase requisitions is normally generated (for example, selection by material number or purchasing group - not usually selected directly with the requisition number). Based on this list, the user selects one or more purchase requisitions. However, the requisition cannot simply be blocked after selection; all the purchase requisitions appearing in the corresponding selection list would have to be blocked before display.
Because these lists can be quite long, block situations would quickly occur that would prevent "normal" work.
Because specific purchasers are usually assigned to specific purchasing groups (organizational arrangement), these purchasers normally only select purchase requisitions with an assigned purchasing group. In such cases, the above situation can almost never apply.

Solution
An organizational solution to the problem is required.

Additional key words

douple, twice, parallel, 06589, 06 589

SAP Note 18127 - Dunning notices: dunning level lower than expected

Symptom:

Key words: SAPF150S, F150, dunning, dunning level
An account is only dunned, for example, with level 3, although invoices exist that could initiate a 4th dunning notice due to their days in arrears.

Cause and prerequisites

Generally, credit memos that have not been allocated exist, whose amount is higher than the balance of the highest dunning level.
The following example shows the logic of the dunning program:
There are 6 invoices on an account:
Amount Days/arrears Poss. dunning level
3,000.- 5 1
10,000.- 10 1
5,000.- 25 2
1,500.- 27 2
1,000.- 35 3
500.- 50 4
Furthermore, there are 2 credit memos over 2,000.- where one has an invoice reference to an invoice over 5,000.-.
In a first run, all invoices are sorted by the possible dunning level. The result is a balance per dunning level which is as follows:
Level Saldo
1 13,000.- Debit
2 6,500.- Debit
3 1,000.- Debit
4 500.- Debit
As a next step, the invoice-referenced credit memos are assigned the dunning level of the corresponding invoice and are cleared with the corresponding balance. Table of dunning balances:
Level Balance
1 13,000.- Debit
2 4,500.- Debit
3 1,000.- Debit
4 500.- Debit
Finally, the credit memos without reference to invoices are cleared, namely starting with the highest dunning level:
Level Balance
1 13,000.- Debit
2 4,500.- Debit
3 1,000.- Debit
4 1,500.- Credit
In the example, the result in the 4th dunning level is a credit balance so that no 4th dunning notice can be created. Now the attempt is made to clear the next lower dunning level:
Level Balance
1 13,000.- Debit
2 4,500.- Debit
3 500.- Credit
The balance also does not suffice for the 3rd dunning level. Next try:
Level Balance
1 13,000.- Debit
2 4,000.- Debit
Therefore, a 2nd dunning notice is written in this example.

Solution
You must ensure that for all credit memos, that belong to an invoice, the corresponding invoice reference is set. If several invoices have to be assigned, you can use one of the invoices to initiate a respective dunning level of the credit memos. A credit memo might even have to be blocked for dunning if you want to avoid a clearing with the oldest items.

SAP Note 18126 - main storage destroyed

Symptom:

System reports "MAIN STORAGE DESTROYED" in Short Dump or System Log.

Cause and prerequisites

... has to be found.

Solution
Within ABAP/4 debugging there is the possibility to activate 'memory monitoring'.

Find out the program which caused the error.
Start that program in debugging mode (/h).
Activate 'memory monitoring' and let the program run.

'memory monitoring' checks all memory segments of the ABAP/4 program in every ABAP/4 statement.

As soon as the memory gets destroyed by an ill behaving part of the SAP system, the system writes a short dump and a system log entry.

In general the user mode is canceled then.
Login again and look for the corresponding short dump (ST22) and system log entry (SM21).

Send the short dump and the system log to SAP with your problem report.

SAP Note 18108 - RFFOCH_P - No foreign transfers possible?

Symptom:

No foreign transfers or transfers in foreign currency are allowed with the Swiss payment medium program for the SAD format (payment orders to the Swiss post office (PTT)).

Cause and prerequisites

Is not supported until Release 3.0D.

Solution
Foreign transfers or transfers in foreign currency can only be carried out before Release 3.0D using program RFFOCH_U (data medium exchange with banks).

Additional key words

RFFOCH_P

SAP Note 18083 - EXART (trans.type) not proposed in purchase order

Symptom:

Two questions in connection with the Intrastat reporting:
1. The transaction type of T161B is not proposed in the order screens.
2. The transaction type field is not shown in the purchase info record,
although this field should exist according the documentation.
Please reply before the 17th of Februari.

Cause and prerequisites

wrong entry in table T161b

Solution
replace positiontype ' ' (=blank) with '0'.

SAP Note 18081 - SUBMIT TO SAP-SPOOL in a background job

Symptom:

If the statement SUBMIT TO SAP-SPOOL is called up in a background program without the explicit specification of print parameters, then the current print parameters are not used for the SUBMIT call but the usual default print parameters are used.

Reason and Prerequisites

The statement SUBMIT TO SAP-SPOOL behaves in the same way as almost all ABAP/4 statements online and in the background. Print parameters other than the default ones are only used if they are explicitly specified.

Solution
Read the current print parameters using the following call and use this for the SUBMIT command:

CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
MODE = 'CURRENT'
NO_DIALOG = 'X'
IMPORTING
OUT_PARAMETERS = pripars
OUT_ARCHIVE_PARAMETERS = arcparams
VALID = valid
EXCEPTIONS
.....
SUBMIT ... TO SAP-SPOOL AND RETURN SPOOL PARAMETERS pripars
ARCHIVE PARAMETERS arcparams.

SAP Note 18079 - Rollup: SAPSQL_ARRAY_INSERT_DUPREC

Symptom:

When trying to carry out a rollup, the system terminates with a runtime error: 'SAPSQL_ARRAY_INSERT_DUPREC' (duplicate records).

Cause and prerequisites

There might be several causes:

If the system terminates when writing line items, it might be that the number intervals for rollups (number range object GL_ROLLUP) were reset.

Another cause (irregardless of whether line items are to be written or not) could be that rollup records which are created through summarization, only differ from one another with respect to the additional unit of measure. Since the additional quantity unit (AUNIT) is only available in the data part of the database, the above described error occurs.
Example:
Account Business area RUNIT AUNIT ASL
400000 M001 KG BAR 50
400000 B001 KG LITER 30

By leaving out the dimension 'Business area', the above case occurs.

Solution

The error with the reset number range interval can be eliminated by setting the rollup number interval (see table T889, transaction GL20) for the number range object GL_ROLLUP using the transaction SNRO back to its old status.

The error with the additional units can really only be solved by the customer because a standard SAP solution for the problem is not provided due to the DB design.
Possible solutions for the customer are, leaving out the additional units in the rollup ledger (see Customizing) or converting the different additional units of meaasure within a user exit.

sap Note 18074 - ABAP/4 runtime error GEN_SELECTION_SCREEN_ERROR

Symptom:

The above runtime error occurs when you start a report (SA38/SE38 or with the transaction code). The text of the runtime error refers to ABAP program RSDBGENA, which can be used for a more precise error analysis.

The analysis shows the following cause:

1. Internal memory for screen LOAD (xxxxx bytes) not available.

Cause and prerequisites

Ad. 1.

The selection screen contains too many objects (for example, more than 70 to 80 SELECT-OPTIONS). The limited memory available for the generated version of the screen is not sufficient.
A further possible cause is a value of the profile paramenter ztta/dynpro_area that is too low. This should have the maximum value of 64000.

Ad. 2.

The reference field of a select option or a parameter has a data type, (for example, FLTP: Floating Point), that is not supported on the screen. As of Release 3.0F, floating points cause a syntax error in the report, previously GEN_SELECTION_SCREEN_ERROR.

Solution
Ad. 1.
Set ztta/dynpro_area higher. If the error is not corrected with a value of 64000, it is possible to trim down the selection screen, for example by leaving out unimportant criteria or comments, or by adding several of the criteria to the logical database as free restrictions in the corresponding selection view.

Ad. 2.
Floating point parameters and floating point select options are not supported.

Additional key words

() ABAPNOTE ABAPMSGERR Selection screen RSDBGENA DS084

SAP Note 18072 - Percentages in pie chart do not corr. to data

Symptom:

A customer analysis was created and sorted in descending order by sales. Value display in percentages.
The printed percentage (performance figure = sales) from the list differs from the percentage of the corresponding graphic (display = pie chart, percentage display).

Cause and prerequisites

Data was passed as percentages to the frontend. This included around 50 customers in the ABAP, but only 10 were displayed in the graphic. The configured diagram type was a bar graph. The user switched to the pie chart within the graphics application. Furthermore, the "Display percentages" option was activated. The percentages in the graphic were calculated from the set of data that was passed on to the graphics application, which did not correspond to the data in the ABAP.
The above error occurred as a result.

Solution
The percentage display cannot be activated at this point. The pie chart is not recommended for such use.
A workaround would be to group the remaining items in the ABAP and pass them on to the graphics application as "Remainder". We can recommend the pie chart in this case.

SAP Note 18070 - MM-WM: Multiple storage unit doc. printing in WMS

Symptom:

If storage unit documents are printed multiply, the number of printouts is not always correct.

Cause and prerequisites

Program error.

Solution
REPORT RLVSDR10 NO STANDARD PAGE HEADING MESSAGE-ID L3. * Feb 95 T329P_LESEN korrigiert *----------------------------------------------------------------- .... *----------------------------------------------------------------- * Lesen der TA-Druck Spoolparameter *----------------------------------------------------------------- FORM T329P_LESEN USING P_LGNUM P_SPOOL. SY-SUBRC = 0. * CHECK P_LGNUM NE T329P-LGNUM OR "corr Feb * P_SPOOL NE T329P-SPOOL. "corr Feb SELECT SINGLE * FROM T329P WHERE LGNUM = P_LGNUM AND SPOOL = P_SPOOL. ENDFORM. ...

SAP Note 18068 - Display version in the stock overview

Symptom:

Program RMMMBEST; Field Display version (T136-VERNU); Parameter ID VNR

In the stock overview, display version 1 is always defaulted and displayed when the stock overview is called from a different application. This is also true, however, when the user has entered a different display version for parameter ID VNR in the user master record.

Cause and prerequisites

The program ignores the user-specific configuration of the display version.

Solution
If you want the display version stored in parameter ID VNR to be displayed in your company, you must deactivate three lines and insert one line in report RMMMBEST (applies to Release 2.2 and 3.0):

RMMMBEST

. . .

* Evtl wird vom aufrufenden Programm eine Anzeigeversion mitgegeben
* IF NOT SY-CALLD IS INITIAL. "<-- deactivate
GET PARAMETER ID VNR FIELD VERNU.
* SET PARAMETER ID VNR FIELD DEF_VERNU. "<-- deactivate
* ENDIF. "<-- deactivate
IF VERNU IS INITIAL. "kann passieren nach 'Neue Selektion'
VERNU = DEF_VERNU.
ENDIF.

. . .

* --- SPA/GPA für Lagerort und Charge übernehmen bei Aufruf aus -
* --- anderer Anwendung
IF NOT SY-CALLD IS INITIAL.
PERFORM GPA_LGORT_CHARGE.
ENDIF.
SET PARAMETER ID VNR FIELD VERNU. "<--- NEW
START-OF-SELECTION.
*--- Lesen Materialgrunddaten mit Kurztext -------------------

In Release 2.1, instead of deactivating the above 3 lines, you must add 5 additional new lines to RMMMBEST (in addition to the one above):

. . .
DATA: VNR(3) TYPE C VALUE 'VNR'. "<-- NEW !!
* ------ Hilfsfelder, Merker ----------------------------------
DATA: SAV-BUKRS LIKE MARCV-BUKRS, "Hilfsfeld Buchungskreis
SAV-TEXT1 LIKE T157B-FTEXT, "Hilfsfeld Text1
SAV-TEXT2 LIKE T157B-FTEXT, "Hilfsfeld Text2

. . .
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN.
IF SCREEN-NAME = '%_MS_MATNR-PUSH' OR
SCREEN-NAME = '%_MS_MATNR-MORE'.
SCREEN-ACTIVE = '0'.
MODIFY SCREEN.
ENDIF.
ENDLOOP.
GET PARAMETER ID VNR FIELD VERNU. "<-- NEW
IF VERNU IS INITIAL. "<-- NEW
VERNU = DEF_VERNU. "<-- NEW
ENDIF. "<-- NEW
. . .

SAP Note 18065 - MRP: SAPLM61U SAPSQL_ARRAY_INSERT_DUPREC

Symptom:

Consumption-based planning ( MD01 MD02 MD03 MS02 ) terminates with SAPSQL_ARRAY_INSERT_DUPREC. The termination occurs in LM61UF20 during insert in table MDTB.

Cause and prerequisites

Incorrect number range status for the MRP lists.

Solution

2. Check and change status.
Call OMI2 and then choose 'Number ranges' under MRP list. Write down the number of the number range for the planned plant and then go back.

Then call the intervals and set the status >= highest number (see above) for the interval belonging to this number.

Additional key words

INSERT_MDTB_MDTBX

SAP Note 18055 - Requirements in pricing are not taken into account

Symptom:

A field in KOMP is changed by a condition formula (KOMP-KZNEP).
This field is queried in a requirement for a subsequent condition.
The queries in the requirement do not work.
The queries for the values in KOMP do not work either.
( KOMP-NETWR KOMP-KZWI1 KOMP-KZWI2 and so on )

Cause and prerequisites

During the pricing, all condition records are read first. At this time, the requirements are checked. Then an evaluation is performed for all conditions determined this way. The formulas are implemented but not the requirements. The value fields in KOMP are not filled until this time.

Solution
You can define exclusions by using the condition base value formulas 014 (set KOMP-KZNEP) and 015 (query KOMP-KZNEP and deactivate condition).

SAP Note 18054 - MI21: wrong F4 help for storage location

Symptom:

When you display the F4 help for the Storage Location field in the transaction MI21 (Print Physical Inventory Document), the help displayed is wrong.

Cause and prerequisites

Program error

Solution
To correct the problem, change the following line in the report RM07IDRU:

REPORT RM07IDRU MESSAGE-ID M7.
...
SELECT-OPTIONS:
R_IBLNR FOR V_MMIM_IPO-IBLNR MEMORY ID IBN,
R_GJAHR FOR V_MMIM_IPO-GJAHR MEMORY ID GJA,
R_WERKS FOR V_MMIM_IPO-WERKS MEMORY ID WRK,
-> R_LGORT FOR V_MMIM_IPO-LGORT MEMORY ID LAG, "old -> delete
-> R_LGORT FOR IKPF-LGORT MEMORY ID LAG, "new -> add
R_GIDAT FOR IKPF-GIDAT,
R_XBLNI FOR IKPF-XBLNI.