21.7.11

SAP Note 26797 - ME6C - RM06LC00 Selecting main criteria

Symptom:

1. The selection functions in transaction ME6C for choosing the main criteria did not work:

- In the case of the function 'Select all', the last main criterion was not selected. Instead, the last header line was selected.
- The function 'Deselect all' did not reverse the selections but deleted the left frame border.

2. The CUA menu contained some superfluous entries.
The function 'Select all' was defined for the F2 key, which is generally reserved for the pick-up function.

Cause and prerequisites

Wrong positioning in program.

Solution
See below.

SAP Note 26792 - Allocation: Problems with several cycles, segments

Symptom:

If an allocation with several segments or cycles is carried out (collective execution), this might result in incorrect results.
The following list displays an overview of all problems already discovered in this context:

    1. The first segment contains a dimension which does not occur at all in the second segment. Nevertheless, the data is updated in the second segment for this dimension although, by definition, the data is to be summarized via this dimension.
    Example:
    1. Segment contains the sender dimensions RBUSA, RACCT and RCNTR and the receiver dimension RBUSA.
    2. Segment only contains the sender dimensions RBUSA and RACCT and the receiver dimension RBUSA. Although the data is to be summarized via the cost center, the cost center is updated in the 2nd segment (inheritance problem)
    This error does not only occur in connection with several segments within a cycle but also with the collective execution of several separate cycles. The reason for this is that an allocation run is regarded as a unit from a programming point of view.
    2. With the distribution, the values are redistributed from one account to another account although the account should remain unchanged. This 'incorrect posting' can also occur with any other field.
    This error occurs when two or more cycles are started with the allocation collective execution, where one cycle is to process less or other dimensions than another cycle (see above example).
Cause and prerequisites
Solution
Generally, only segments which process the same dimensions should be defined in one cycle. For the collective execution of several cycles, this requirement should also be met for all the cycles.
If errors occur anyway, these can actually only be corrected by distributing the cycles in question, which contain several segments, between several cycles with only one segment.
Since the errors also occur with the collective execution of several cycles, these cycles must then also be started individually.

Additional key words

Assessment distribution Allocation Segment Cycle GA15 GA2B GA35 GA4B

SAP Note 26791 - ME6C - RM06LC00 - processing according to main criteria

Symptom:

Vendor evaluation: transaction ME6C.
During selection of not-yet-evaluated vendors with regard to certain
main criteria, message I008 'All vendors already evaluated' was issued.
This message was wrong.

Cause and prerequisites
Solution
The above system message has been replaced by a new one that reads:
'The selected vendors have never been evaluated'.

SAP Note 26790 - Partner maintenance: No matchcode for vendors

Symptom:

On the detail screen for partner maintenance in purchasing documents (SAPLEKPA, screen 101), the F4 help on the field 'vendor' only lists all vendors. It would be more helpful here to carry out a search by standard matchcode.

Cause and prerequisites
Solution
Corrected in 3.0B. In advance of this release, you can activate the search by matchcode by entering matchcode object KRED in the 'Matchcode' field under the attributes of the field EKPA-LIFN2 on screen 101 of program SAPLEKPA. Then generate the screen.

Additional key words

Partner Partner function Purchase order Contract Request for quotation Scheduling agreement

SAP Note 26789 - Pricing error during batch split

Symptom:

For deliveries with a batch split, in pricing the error message: 'Pricing error in item &' occurs.

Cause and prerequisites

Missing entry in Customizing.

Solution
If a batch split is performed in the delivery, then both the main items and the subitems have a delivery item category.

Check whether the item category of the batch split items is a different item category than in the main item.
If this is the case, then the entry for the item category determination may be missing in table T184L (transaction 0184).

Example:
Sales order with an item free of charge (TANN)
Delivery with batch split:
Main item TANN - subitems TAN

Since the item category TAN is relevant for pricing, the pricing error occurs in the billing document.

The following entry must then be made in table T184L:
Del.type Item cat. Usage ItCat ItCat
LF NORM CHSP TANN TANN

Additional key words

VL02, batch, VF01, VF04, delivery free of charge, TANN, VF073

SAP Note 26788 - More than one generated rule in ledger selection

Symptom:


When using more than one generated rule within a line in the ledger selection, unexpected results occur. This causes an incorrect update of the ledgers.

Cause and prerequisites


When using generated rules, only the last rule in the line is valuated. Consequently, no logical operations with several rules are possible.

Solution

Only use one rule for each line of the ledger selection. If you want to link several rules through logical operations (for example, AND, OR and so on), use a generated rule in the ledger selection. In this rule, you can then use the rules you require as sub-rules.

Additional key words


Ledger selection, direct posting, generated rules

SAP Note 26784 - Display open purchase order quantity (currency) RM07MKBS

Symptom:

Display consignment stocks. (RM07MKBS) transaction MB54
Open purchase order quantities are not displayed correctly.
Currencies were not displayed.

Cause and prerequisites

The material number and the unit of measure were not transferred correctly.
The currency unit was not transferred correctly.

Solution
see repair.

SAP Note 26781 - Planning fields not copied from MRP profile

Symptom:

The fields for the planning material are maintained in the MRP profile. The content of these fields is then not copied into the material masters of those materials to which this MRP profile is assigned.

Cause and prerequisites

Program error

Solution
The error is corrected in 2.2G and 3.0B.

Additional key words

Transaction MMD1, MM02; Fields: RM03M-VPMAT, RM03M-VPWRK, RM03M-VPREF

SAP Note 26779 - Costs reports PS Info. Syst.: no data selection

Symptom:

When you call up PS Information System costs reports, message OK792 is issued. Data is then not selected.

Cause and prerequisites

The version key range of the LDB PSJ requires special processing for costs reports. It is incorrectly preassigned in case only original data should be read.

Solution
Please change program DBPSJSOS in FORM routine CHECK_INPUT as follows.
Old coding:
cn_stufe-high = 99.
cn_aktdt = con_no.
if cn_vsnmr[] is initial.
cn_vsnmr-sign = con_incl.
cn_vsnmr-option = con_equal.
cn_vsnmr-low = space.
append cn_vsnmr.
endif.
endif.
if lines is initial and

New coding:
cn_stufe-high = 99.
if cn_vsnmr-low is initial.
refresh cn_vsnmr.
cn_aktdt = con_yes.
else.
cn_aktdt = con_no.
endif.
endif.
if lines is initial and
Please replace FORM routine CHECK_VSNMR by the following program code in DBPSJSOS:
form check_vsnmr.
data: loc_tfill like sy-tfill.
* IntTabs
data: itab_ap_ord_pre like ap_ord_pre occurs 0 with header line.
* SelektionsTabs fuer ' .. All Entries '
data: begin of sel_tab occurs 0,
vsnmr like vskopf-vsnmr,
end of sel_tab.
data: begin of itab_vs_erdat occurs 0,
vsnmr like vskopf-vsnmr,
vserdat like vskopf-vserdat,
end of itab_vs_erdat.

perform import_from_memory using 'VERSION' con_mem_id_key_blank.
read table versionen with key vsnmr = space.
if not sy-subrc is initial and cn_aktdt = con_yes.
describe table versionen lines loc_tfill.
versionen-vsnmr = space.
versionen-version = loc_tfill.
append versionen.
endif.
if not cn_vsnmr[] is initial.
loop at cn_vsnmr.
sel_tab-vsnmr = cn_vsnmr-low.
append sel_tab.
endloop.
select vsnmr vserdat from vskopf
into table itab_vs_erdat
for all entries in sel_tab
where vsnmr = sel_tab-vsnmr
and vszhl = '00000001'.
loop at cn_vsnmr.
read table itab_vs_erdat with key vsnmr = cn_vsnmr-low.
if not sy-subrc is initial.
message i792(cn) with cn_vsnmr-low.
stop.
endif.
endloop.

* zuerst neueste Version selektieren
sort itab_vs_erdat by vserdat descending.

describe table versionen lines loc_tfill.
loop at itab_vs_erdat where vsnmr in cn_vsnmr.
read table versionen with key vsnmr = itab_vs_erdat-vsnmr.
if not sy-subrc is initial.
versionen-vsnmr = itab_vs_erdat-vsnmr.
versionen-version = loc_tfill.
add 1 to loc_tfill.
append versionen.
endif.
endloop.
endif.
perform export_to_memory using 'VERSION' con_mem_id_key_blank.
perform export_to_memory using 'VSKOPF' con_mem_id_key_blank.

endform.
Please change the selected places in the program code of include DBPSJGET
as of: *...die Objektnummer über die Projektdefinition holen
IF NOT CN_PROJN[] IS INITIAL.
SELECT OBJNR FROM VSPROJ_CN INTO TABLE OBJNR_TAB
WHERE VSNMR = CN_VSNMR-LOW
AND PSPID IN CN_PROJN.
* if objnr_tab[] is initial. " DELETE
* select objnr from proj into table objnr_tab " DELETE
* where pspid in cn_projn. " DELETE
* endif. " DELETE
ENDIF.

IF NOT OBJNR_TAB[] IS INITIAL.
SELECT * FROM VSSTEU INTO TABLE VSSTEU_TAB
FOR ALL ENTRIES IN OBJNR_TAB
WHERE VSNMR = CN_VSNMR-LOW
AND OBJNR EQ OBJNR_TAB-OBJNR.
ELSE.
SELECT OBJNR FROM PROJ INTO TABLE OBJNR_TAB " MODIFY
WHERE PSPID IN CN_PROJN. " MODIFY
IF NOT OBJNR_TAB[] IS INITIAL. " INSERT
SELECT OBJNR FROM VSSTEU INTO TABLE OBJNR_TAB " INSERT
WHERE VSNMR = CN_VSNMR-LOW. " INSERT
ENDIF. " INSERT
ENDIF.
*...Versionsnummer überprüfen, ob vorhanden.

IF OBJNR_TAB[] IS INITIAL. " MODIFY
MESSAGE I792(CN) WITH CN_VSNMR-LOW.
.....

*
*...wurde die Version aktionsgesteuert erstellt, muß keine
* Version der Projektdefinition vorhanden sein
* *
*...sollte die ITAB_PROJ initial sein, muß in der Steuertabelle
* nach PSP-Elementen gesucht werden
IF ITAB_PROJ[] IS INITIAL AND CN_PSPNR IS INITIAL.
SELECT * FROM VSKOPF INTO TABLE VSKOPF_TAB " INSERT
WHERE VSNMR IN CN_VSNMR. " INSERT
SELECT * FROM VSSTEU INTO TABLE VSSTEU_TAB
FOR ALL ENTRIES IN VSKOPF_TAB
WHERE VSNMR EQ VSKOPF_TAB-VSNMR.

SORT VSSTEU_TAB BY OBJNR.
LOOP AT VSSTEU_TAB.
*...Range-Tabelle für PSP-Elemente füllen
IF VSSTEU_TAB-OBJNR(2) EQ 'PR'.
*...aus Objektnummer PSP-Element bestimmen
MOVE VSSTEU_TAB-OBJNR+2 TO PSPNR_TMP.
*...den ersten Eintrag in 'LOW' und 'HIGH' ablegen
IF CN_PSPNR-LOW IS INITIAL. " MODIFY
WRITE PSPNR_TMP TO CN_PSPNR-LOW.


FORM SELECT_AUKOD_FOR_CN_VBELN.
CASE SELECTION_MODE.
WHEN CON_ACT_DATA.
SELECT * FROM M_AUKOD INTO TABLE ITAB_AUKOD
WHERE KDAUF IN CN_VBELN ORDER BY AUFNR.
WHEN CON_VER_DATA.
*...bei Versionen wird über die Originaltabelle gelesen (anstatt MCode)
SELECT * FROM VSAFPO_CN INTO TABLE VSAFPO_TAB
WHERE VSNMR = CN_VSNMR-LOW " MODIFY
AND KDAUF IN CN_VBELN ORDER BY AUFNR. " MODIFY

FORM SELECT_PRPOC_FOR_PSP_RNG.
CASE SELECTION_MODE.
WHEN CON_ACT_DATA.
SELECT * FROM M_PRPOC INTO TABLE ITAB_PRPOC
FOR ALL ENTRIES IN PSP_RNG
WHERE PROJN = PSP_RNG-LOW.
WHEN CON_VER_DATA.
SELECT * FROM VSAFPO_CN INTO TABLE VSAFPO_TAB
FOR ALL ENTRIES IN PSP_RNG
WHERE VSNMR = CN_VSNMR-LOW " MODIFY
AND PROJN = PSP_RNG-LOW. " MODIFY

FORM SELECT_AFVCP_FOR_PSP_RNG.
CASE SELECTION_MODE.
WHEN CON_ACT_DATA.
SELECT * FROM AFVCP INTO TABLE ITAB_AFVCP
FOR ALL ENTRIES IN PSP_RNG
WHERE PROJN = PSP_RNG-LOW.
WHEN CON_VER_DATA.
SELECT * FROM VSAFVC_CN INTO TABLE VSAFVC_TAB
FOR ALL ENTRIES IN PSP_RNG
WHERE VSNMR = CN_VSNMR-LOW " MODIFY
AND PROJN = PSP_RNG-LOW. " MODIFY

FORM GENERATE_SELECT_FOR_PRPS.
CLEAR GEN_SEL_WHERE. " INSERT
IF NOT LINES-PROJ IS INITIAL.
* Definitionen als Selektionskriterium eingegeben.
IF NOT ITAB_PROJ[] IS INITIAL.
APPEND ' FOR ALL ENTRIES IN GEN_PROJ' TO GEN_SELECT.
APPEND ' WHERE PSPHI = GEN_PROJ-PSPNR' TO GEN_SELECT.
IF SELECTION_MODE = CON_VER_DATA.
APPEND ' AND VSNMR = GEN_VSNMR' TO GEN_SELECT.
ENDIF.
GEN_SEL_WHERE = CON_OK.
ENDIF.
ENDIF. " INSERT
IF SELECTION_MODE = CON_VER_DATA AND GEN_SEL_WHERE IS INITIAL." INSERT
APPEND ' WHERE VSNMR = GEN_VSNMR' TO GEN_SELECT. " INSERT
GEN_SEL_WHERE = CON_OK.

Additional key words

Logical database PSJ, commercial analysis

SAP Note 26777 - tp returns the message: sapparam (1c): no profile used.

Symptom:

When calling tp, the following message appears on stdout (possibly repeatedly)
sapparam (1c): no profile used.

Cause and prerequisites

Working according to note 11677 with the event controlled RDDIMPDP. The program sapevt is used for generating events. In fact, it does not read (nor does it have to read) any profiles.
Thus, this message is NOT AN ERROR MESSAGE!

Solution
Ignore it!

Additional key words

sapparam(1c)

SAP Note 26776 - Pricing error in time-dependent conditions

Symptom:

Pricing error in the subtotals of time-dependent prices.

Additional key words
Cause and prerequisites

Program error.

Solution
Program change in LV61AF0X

SAP Note 26774 - Copy entries from table view V_T399X_QM

Symptom:

If a table comparison is carried out for view V_T399X_QM (T399X), entries for all order types will be proposed even though the view only supports the maintenance of order types with order category 06.
All of these order types are designated as 'not available in the current client' and can be copied using the copy functions. They cannot, however, be saved.

Cause and prerequisites

No limitation in the view for the order category

Solution
From the SAP standard, copy order types QL01, QL02 and QN01 only. Other order types are not supported in the view. The order category for the order type must be 06. Refer to table T003O.

Additional key words

Comparison

SAP Note 26773 - Overflow in field H-WERT

Symptom:

Program termination.

Cause and prerequisites

Entry of target quantities and prices that are too high (quantity x price > 9999999999999.99)

Solution
Rectified as of 2.2H and 3.0B.

Additional key words

Transaction: ME3N Module: SAPFM06L - FM06LFEK

SAP Note 26772 - ORACLE installation - VARIOUS OPTIONS

Symptom:

Which options does the customer receive with the SAP ORACLE installation?

Cause and prerequisites

see above

Solution

For Oracle releases as of 7.3* and Oracle 8:
Further options (distributed, parallel query, 64 K option) are in the meantime included in the standard installation.

EXCEPTION: Oracle 8.0.5 for Reliant Unix 32-bit
Therefore, after the Oracle 8.0.5 installation,
immediately apply the following fix:
~ftp/general/3rdparty/oracle/RELIANT_UX/8.0.5/bug805573

For Oracle releases up to and including 7.2.3:
Further options (distributed, parallel query, 64 K option) are NOT included in the standard installation.

The software is contained on the SAP ORACLE CD, but it is not active.

If these options are used, the licensing rights must be cleared up BEFORE activation. These options MUST be obtained separately.

You should get in contact with SAP or with the ORACLE branch office with regard to the license.

Activation of the software is carried out by Second Level ORACLE Support at SAP.

Additional key words

ORA2088

SAP Note 26767 - Loss of the short texts when transporting CO groups

Symptom:

After transporting a cost accounting group (for example, cost element group), the group has no short descriptions for nodes or values in the target system.

Cause and prerequisites

The error occurs when the transfer order contains an entry of the form
R3OB SETS STSD/0H/CCSS/... or
R3OB SETS STSD/0H/GLTPC/... or
R3OB SETS STSD/0H/GLPCT/...
(the decisive factor is the character string '0H' between the first two slashes.)
Such entries are created, for example, through the transaction OKE6 in CO Customizing.

Solution
Corrected in program FGUTRF20 (in the source system of the transport)

Additional key words

Set Group Hierarchy
T800Y T800X
SAPFGUTR FGUTRF20

SAP Note 26765 - Form F130_ERROR_01: Error in the English version

Symptom:

The English translation of form F130_ERROR_01 is incorrect.

Cause and prerequisite

Translation is incorrect

Solution
Change form F130_ERROR_01 as follows:

Transaction /NSE71
Form F130_ERROR_01 Language English
Choose Option window
Change form
Double-click on MAIN window
Choose Edit text elements
Change the following in the editor

/E 931
/E "<- Delete

Save and F3=Back
Check form
Save and activate form.

Additional key words

SAPF130D, SAPF130K

SAP Note 26763 - SD-COPA: Fields from PAPARTNER not supplied

Symptom:

When transferring billing documents from SD into Profitability Analysis CO-PA, characteristics, which were picked up from the structure PAPARTNER (for example, ship-to party, invoice recipient, and so on) are not updated in CO-PA, although the field assignment for the business transaction 'SD00' is entered correctly in the configuration menu of CO-PA under the menu option 'Copy characteristic'.

Cause and prerequisites

- the costing-based Profitability Analysis is exclusively active
- the sales order entry is not active
- no customer production order for customers exists
- on the sales order, the assignment to profitability segment was not made manually

If these requirements are met, the characteristics are not updated due to a program error.

Solution
The error is corrected in Release 3.0B. As advance correction, you can make the change mentioned below (indicated with '<--') in program SAPLV60A.

Additional key words

SD - CO-PA interface

SAP Note 26762 - Selection from a view returns invalid result set

Symptom:

After changing the selection criteria of a database view, the results of quotation requests do not change appropriately.

Cause and prerequisites

This involves an unknown problem in the R/3 environment in conjunction with the database Informix OnLine.
Every database statement from R/3 is passed to the Informix database via dynamic SQL. Information about these statements is stored locally for performance reasons for a certain time in the respective work process. If the view is now deleted in the database and recreated with the same external structure (that is, only the view selection was changed), further execution of the stored Informix database statement is handled correctly (that is, without an error message) -- unfortunately, however, the number of hits does not change as it of course should.

Solution
A currently required displacement of this statement from the work process storage is not explicitly controllable -- it occurs implicitly according to certain criteria. The only short-term solution at this point is to restart the system; or at least the work process in which the information was stored. Since this can often only be determined with difficulty, there is, as already stated, often only the option to restart the entire system. The problem was reported to Informix and will be corrected in a subsequent version that has not yet been named. From the viewpoint of SAP, there is currently no praktical program strategy to get round this problem.
For this reason, you should change the view definitions as rarely as possible and, if in doubt, restart the system after this. A corresponding development request was created, however we cannot currently make any statement about the general availability of a solution.

Additional key words

PTS PTS_BUG PTS_BUG_43132

SAP Note 26759 - RM07RVER selects automatic reservations

Symptom:

Management of reservations: if you neither enter a reservation number nor a baseline date in the selection screen, then automatic reservations are proposed as well to be managed.
This is an error because automatic reservations must not be reorganized manually. They only can be deleted with a reorganization run of the reference documents (for example, the production order).

Cause and prerequisites

Program error.

Solution
Change program RM07RVER.

Additional key words

Transaction MBVR

SAPNote 26758 - Special payment: No payment at end of waiting time

Symptom:

If the end of a retention period (specified by the waiting time in table T530C) coincides with the end of the compensation period, the quota is not paid.

Cause and prerequisites

Program error

Solution
Please change the following lines indicated with "<<<---" below in member "RPCSPA01" in FORM routine "SZVAR_10_F":

SAP Note 26755 - System cannot be started. Syslog FA6

Symptom:

System cannot be started. Error messages with 'gethostbyname'. Syslog FA6: Host ... is unknown. Which includes the individual name.

Cause and prerequisites

Different problems are conceivable.
1.
Name Server ("DNS") does not run.
2.
File etc/resolv.conf is read protected.

Solution
1.
Domain Name Servers are independent software packages which should be equipped with separate documentation.

2.
/etc/resolv.conf should belong to a UNIX system user and have the authorizations rw-r--r--.

Additional key words

DNS, Domain Name Server, YP, Yellow Pages

SAP Note 26754 - Plant conditions overview: No F4 help for plant

Symptom:

On the overview screen for the plant conditions in the contract (SAPMM06E, screen 230), the F4 help is missing fieldfor 'Plant'. The same applies to the popup for copying plant conditions (SAPMM06E, screen 518).

Cause and prerequisites

Missing foreign key

Solution
Corrected in 3.0B. You can make the following advance correction: Maintain the foreign keys for fields
RM06E-KOWRK and RM06E-KPWRK in the ABAP/4 Dictionary as follows:
RM06E-KOWRK:

Inspection table field Foreign key field T001W MANDT SYST MANDT
T001W WERKS RM06E KOWRK

RM06E-KPWRK:

Inspection table field Foreign key field T001W MANDT SYST MANDT
T001W WERKS RM06E KPWRK

Then activate structure RM06E.

Additional key words

ME31, ME32, ME33

SAP Note 26750 - ANLC is not updated during KO88/CJ88 reversal

Symptom:

When you reverse an order settlement or a project settlement to a fixed asset (not during the settlement of capital investment measures), the asset values in ANLC are not updated. Asset line items are created.

Cause and prerequisites

Program error

Solution
Please execute the function "Recalculate val." in transaction AS02 (Change Asset) for the fixed asset in question and make the following correction.

Additional key words

KO88, CJ88, settlement

SAP Note 26748 - Create primary cost element: Error KS045

Symptom:

Error KS045 occurs when creating primary cost elements.

Cause and prerequisites
Solution
See repair.

Additional key words

Key word: Master data, create cost elements, program SAPMKMA4
Transaction: KA01

SAP Note 26737 - Batch split: Rescheduling item generation

Symptom:

When you create batch split items, a rescheduling of the item date specifications and the delivery date is carried out.
Error message 6P365: '00.00.0000 date comes after end of valid factory calendar. (please correct)' may occur when you post a goods issue.

Cause and prerequisites

Program error

Solution
Change program.

SAP Note 26736 - Purchase requisition for KMAT materials

Symptom:

If a production order was created for a combinable assembly and the bill of material contained non-stock components, purchase requisitions were not created for these components.

Cause and prerequisites
Solution
Correction

Additional key words

CO01, KMAT

20.7.11

SAP Note 26726 - Maintenance order: Costing indicator / scheduling

Symptom:

What effect have the characteristics of the 'external processing' flag to scheduling and costing in the control key?

Cause and prerequisites

No error

Solution


Charact. external processing indicator ! ' ' ! 'X' ! '+' ----------------------------------------------------------------------
! ! !Scheduling ! 1. ! 2. ! 3. ! ! !Costing ! 4. ! 5. ! 6.


1.) Duration
2.) Duration
3.) Planned delivery time

4.) Work
5.) Release 2.2: Work
Release 3.X: Work. If no work center is maintained, costing is
carried out using the price of the external
activity screen
6.) Price


Note: Consider that no purchase requisition is generated with external processing indicator 'X'
since it is
an internally processed operation.

Additional key words

ß418-Lief, control key

SAP Note 26725 - Empty list during determination of lowest value

Symptom:

The list created by one of the programs to determine the lowest value is empty.

Cause and prerequisites

Changes in program SAPDBMSM by which the material number and other material master fields were no longer filled.

Solution
Corrected in programs RMNIWE00, RMNIWE10 and RMNIWE20.

Additional key words

RMNIWE00, RMNIWE10, RMNIWE20, MRN0, MRN1, MRN2, movement rate, range of coverage

SAP Note 26724 - VL01/VL02 SAPMV50A Error Message VL222

Symptom:

1. When you want to delete a batch in order to call up the batch split, after having created this batch on the picking screen (VL01/VL02) and posted it, you receive Error message VL222:
Valuation type in Item & already specified for Material &
When you change a batch, after having created it on the picking screen (VL01, VL02) and posted it, the field BWTAR (valuation type) is not redetermined from the new batch.

Cause and prerequisites

The valuation type is neither reset nor redetermined.

Solution
P22K009477 in 2.2
P30K015844 in 3.0

SAP Note 26721 - No complete sender credit in assessment

Symptom:

Description:
the activity-dependent amounts planned or posted on the senders are not taken into account in the actual/planned assessment.
Transactions: KSU5, KSUB
Program names: SAPMKGA2, ALxxyyyR

Cause and prerequisites

Program error - KL sender cost-objects are indeed selected, but are nonetheless eliminated again later during the program run.

Preconditions:
This note is valid only for the assessment in CO-CCA or CO-ABC !!

Solution
Implement the following program correction.

Additional key words

Allocation.

SAP Note 26718 - MF41 Cancelling the LIS information

Symptom:

When you cancel the backflushing (repetitive manufacturing), the LIS information is not cancelled.

Cause and prerequisites

Program error

Solution
See the source code corrections

SAP Note 26716 - CK11: Illegal_temporary_objnr during update

Symptom:

Product costing, transaction CK11 or CK64, terminates with the RAISE_EXCEPTION 'Illegal_temporary_objnr' as soon as you attempt to store the costing with cost element itemization.

Cause and prerequisites

A negative splitting was calculated for one of the materials costed. In this case, the respective cost element cost object is (incorrectly) not deleted, and it also has no final cost element itemization number. When updating, an attempt is made to update the cost object with the temporary number and the program terminates.

Solution
Repaired in 3.0B. To correct the error immediately, a repair to the function module CK_F_ASSEMBLY_COSTING is necessary. Please insert the lines marked with <<<<

SAP Note 26715 - MD06: Qty data missing/incorrect in detailed header

Symptom:

1)
If you branch from the collective display of MRP lists (MD06) to an individual MRP list, then various quantity fields in the individual list are empty (for example, the maximum stock)

2)
In the detailed header and in the material overview of the MRP list (MD05 and MD06), the stock fields are displayed as zero although stocks do exist.

3)
In release 2.2, in the detailed header of the MRP list, the system includes safety stock in the available plant stock display. In release 3.0 (up to and including release 3.0E), this stock is no longer displayed in the detailed header of the MRP list.

Additional key words

MD04 MD07

Cause and prerequisites

1)
Program error. This problem has been solved for 3.0B. It only occurs in release 3.0 to 3.0A.

2)
The MRP list displays the situation at the time of the last planning run. This is also true for the stocks. The stock levels at this time however, are not available.
Therefore, from release 3.0B, they are hidden and can no longer be seen.

3)
In release 2.2 and from release 3.0F, available plant stock including safety stock is saved in field, MDKP-SUM01. If you want to display this stock in the detailed header of the MRP list from 3.0F, then you must create your own include screen for the detailed header that contains this data.
In Customizing, this include screen can then be included in the detailed header's screen sequence. Note 36087 describes the procedure for creating an individual screen for the detailed header.
Up to and including release 3.0F, however, you first have to have implemented the correction specified under 3) below.
In the standard system, from release 3.0F, the field MDKP-SUM01 exists on screen SAPLM61K/0103.

Note: available plant stock in release 2.2 and how it is saved in field MDKP-SUM01 is not identical to plant stock in the detailed header of the current stock/requirements list MD04 (field, MDSTA-SUM01). Up to and including release 3.0E, this plant stock represents the unrestricted-use stock in the plant. From release 3.0F, the system displays available stock in teh plant (depending on Customizing, use of QM). Up to release 3.0E, this can only be displayed via stock statistics. In all releases, however, the field also contains the stocks in the storage locations that are not included in MRP and is thus different from MDKP-SUM01.
Stock according to MDSTA-SUM01 us not saved in the MRP list. It can also not be determined later. Therefore, it can no longer be displayed with the correction specified under (2) below in the MRP list (MD05, MD06).

Solution
1)
Correction (see below)

2)
No general preliminary solution - from release 3.0B to 3.0D, the error only occurs if the field, MDSTA-SUM01 from screen SAPLM61K/0100 was copied to a detailed header to be displayed (see note 36087). See below for correction.

3)
Correction. Contained in the standard system from release 3.0F.
However, note that in all MRP lists created in releases previous to 3.0E before implementation of the correction, the field MDKP-SUM01 usually contains the incorrect value 0, that is also displayed incorrectly.

SAP Note 26714 - Workflow customizing prerequisites

Symptom:

The following symptons can occur when customizing has not been fully completed:

  • Popup to request the active plan variant is displayed every time a workflow maintenance transaction is called (PFWS, PFWF, PFTS, PFT)
  • No workflow templates available
  • Message OL:810 when an object method is carried out
  • Message SR:027 in the RFC queue (transaction SM58).

At the end of this note there is a description of how to collect a report that verifies the workflow customizing. If you are having problems with workflow in a new system it is a good idea to run this verification report before proceeding further.

Additional key words

..

Cause and prerequisites

Customizing has not been completed.

Solution
Sympton: Popup requesting the active plan variant is displayed every time the workflow maintenance transaction is called.

Reason: The active plan variant has not been defined.
Solution: Configure an active plan variant. This is done via workflow basic customizing. Route: General basis -> Workflow management -> basic data ->Set active plan version

Sympton: No workflow templates available.

Reason: The workflow templates have not been copied into your client or they have not been activated (automatic after 3.0B).
Solution: Execute the report RHWFACTI with the test flag on. If no entries exist you must copy the templates from client 0. If templates do exist but have not been activated you can activate them by switching the test flag off and executing the report again.

Sympton: Message OL:810 when an object method is carried out. This can lead to the workflow being created with no step-protocol.

Reason: No logical destination has been defined for this client.
Solution: Call transaction BD54 to create a logical system name and then use transaction OY25 to assign it to this client.

Sympton: Message SR:027 in the RFC queue (transaction SM58).

Reason: The WORKFLOW_LOCAL Logical Destination has not been configured.
Solution: Define a Logical Destination using customizing. Route: General basis -> Workflow management -> basic data -> Create local destination for tRFC.

Customizing verification report.
In 3.0B, the transaction SWU3 can be used to verify the workflow customizing. This is available on SAPSERV3 as pre-release functionality. Do not collect the patch if you have release 3.0B or higher!
To collect the program from sapserv3:
You will find the correction in the directory /dist/permanent/Note.0026714, transport request P30K034639 (you can find a description of the import procedure in note 13719).

SAP Note 26711 - Saving profile name/group in Screen SAPL0PSR 315

Symptom:

Changes to the fields 'group' or 'name' for the graphics profile (V_TCBP-PRF_GRUPPE, V_TCBP-PRF_NAME) cannot be saved.

Cause and prerequisites

In Project System Customizing use transaction OPT7 to call up
the 'Project planning board overview. Then maintain the field 'name' of the 'graphics profile' on a detail screen. After saving, the new value is not accepted by the system.

Solution
Use transaction 'SE51' to go into the flow logic of screen
'SAPL0PSR' '315', and include the two fields V_TCBP-PRF_GRUPPE V_TCBP-PRF_NAME in the chain statement as shown below.
Afterwards re-generate the screen !

SAP Note 26710 - GR quantity in operation is not updated

Symptom:

If goods receipt is carried out for an external operation in the maintenance order, the GR quantity is not updated on the external processing data screen of the operation when subsequently changing or displaying the order. It is equal to zero.

Cause and prerequisites

Program error

Solution
Correction P30K015816

Additional key words

Quantity of goods received

SAP Note 26709 - Court orders type 'M' - Maintenance arrestment Scot

Symptom:

Payroll rejects in function GCRTO when there is a court order type 'M'

Cause and prerequisites

Incorrect reading of Table T5G15

Solution
Change the code as follows.

SAP Note 26706 - MD06, 3.0FCS: Missing factory calendar

Symptom:

In transaction MD06 (Collective Display of MRP Lists), the error message "Missing factory calendar or error in factory calendar" is displayed on the initial screen.

Cause and prerequisites

The error occurs in 3.0FCS (First Customer Shipment).
It is corrected in release 3.0A.

Solution
Please make the following correction in Include LM61RSEL:

SAP Note 26703 - Creating batch input sessions and COMMIT WORK

Symptom:

You create one or more batch input sessions and have the following problems.
1. You have created very large session and the database returns errors.
ORACLE: ORA1562 "failed to extend rollback segment"
followed by ORA1556 ORA1547 ORA1631 ORA1628
INFORMIX: INF134 "ISAM error: no more locks"
caused by INF246 INF271
INF458 "long transaction aborted"

2. You create several sessions in one program and your program crashes. As a result, all preceeding sessions are lost.

Cause and prerequisites

1. The database transaction contained too many modifications.

2. Your data was not yet stored in the database.

The function modules
BDC_OPEN_GROUP,
BDC_INSERT
BDC_CLOSE_GROUP
do --- NOT --- perform a COMMIT WORK.

The background processing does not automatically perform a COMMIT WORK. The COMMIT WORK is only executed automatically after a dialog step in online processing.

Solution
Perform a COMMIT WORK after a certain number of transactions which you have defined in the session. This COMMIT WORK terminates the database transaction. The number of modified objects per transaction is reduced and made permanent in smaller packages.

Example: Perform COMMIT WORK after 100 transactions.

TRANS_COUNT = TRANS_COUNT + 1.

CALL FUNCTION 'BDC_INSERT' .....

IF TRANS_COUNT EQ 100.
COMMIT WORK.
ENDIF.

Additional key words

ORA1562 ORA1556 ORA1547 ORA1631 ORA1628
INF134 ISAM134 INF246 INF271 INF458

18.7.11

SAP Note 26699 - Missing memory entry at the event PUT AFKO

Symptom:

When you execute reports which use the logical database PSJ - for example, all structure reports and costs reports in the Project Information System - it can occur that a memory entry is not found for the event PUT AFKO. As a consequence, no data is found for the specified selections.

Cause and prerequisites

The error described above occurs if only the checkboxes 'WBS element', 'Incl. hierarchy' and 'Incl. network' are selected in the database profile (PF20 on the selection screen). In this case, the range NET_RNG in program FDBPSRST is changed and not restored although the original range is needed again later.

Solution
Please insert the line indicated below in Include DBPSJPUT in FORM routine PUT_AFKO:
form put_afko.
if rsthie-type = con_obt_netz.
check h_auth-netz = con_ok.
if first-neko is initial.
first-neko = con_ok.
if flg_do_db_selection = con_yes.
* INSERT the following line!
===========================================
perform import_from_memory using 'NET_RNG' con_mem_id_key_blank.
check not net_rng[] is initial.

In Include FDBPSRST, you also have to insert one line:
* Aufbauen SUB_NET_RNG
refresh sub_net_rng. <===== INSERT
sub_net_rng-option = con_equal.

Additional key words

Error message OK012

SAP Note 26693 - ME21 entries disappear on screen 124

Symptom:

Summary

Symptom

If you create a release order, field contents disappear on screen 124 (release order item overview) in the following cases:

    1. On the initial screen, a date is set as a default value; on screen 124, you first of all choose function 'Select all'. The date disappears.
    2. You make an entry in one of the fields 'Plant', 'Delivery date', 'Material' (for example for contract items with item category M), but not 'PO quantity' or 'PReq', and then press ENTER. The entries you have made disappear.
    3. In addition, default values from the initial screen, for example account assignment category and plant, are not transferred into the release order items.
Cause and prerequisites

Program error.

Solution

Corrected as of Releases 2.2G/3.0C. Advance correction possible as follows:

Header Data



Release Status:Released for Customer
Released on:13.05.1996 22:00:00
Master Language:German
Priority:
Category:
Primary Component:MM-PUR-PO Purchase Orders

Affected Releases

Software
Component
Release
From
Release
To
Release
And
subsequent
SAP_APPL
22
22A
22F
SAP_APPL
30
300
30B

Attributes

Attribute
Value
old release
00121A R3STD 0026693
old release
00121B R3STD 0026693
old release
00121C R3STD 0026693
old release
00121D R3STD 0026693
old release
00121E R3STD 0026693
old release
00121F R3STD 0026693
old release
00121G R3STD 0026693
old release
00121H R3STD 0026693
old release
00121I R3STD 0026693
old release
00121J R3STD 0026693
old release
00121K R3STD 0026693
old release
00121L R3STD 0026693
old release
00121M R3STD 0026693
old release
00121N R3STD 0026693

SAP Note 26690 - No conf. quantity after changing unit of measure

Symptom:

After changing the unit of measure of an order item, the confirmed quantity is missing.
Or:
After changing the conversion factors of an item, the confirmed quantity is calculated from the old required quantity and not the required quantity from the confirmed quantity.

Cause and prerequisites

The availability check is not active.

Solution
As a workaround, it is possible to avoid the error by temporarily changing the order quantity and resetting it again.

SAP Note 26688 - Incorr. display Book val. for reval. w. depreciat.

Symptom:

If the depreciation of the past has also appreciated on a fixed asset (backlog), an incorrect book value was displayed when displaying the asset values.

Cause and prerequisites

Program error

Solution
Advance correction in the module MA03WF05, syntax check only in main program SAPMA03W.

Additional key words

AW01 SAPMA03W AUFNP

SAP Note 26687 - Integration HR - PM / PS : Procedure

Symptom:

The concept of the integration between Logistics and HR is explained in note 29178.
This note describes the procedure for setting up and administering the interface between Logistics and HR.

Cause and prerequisites
Solution

Make customizing settings:
Call the R/3 implementation guide (IMG).

  • The two switches for Logistics integration must be set via Human resources administration and payroll --> Incentive wages --> Settings --> Maintain incentive wage parameters.
  • The Integration Logistics switch must be set for time ticket type '01' via Human resources administration and payroll --> Incentive wages --> Time ticket types --> Create time ticket types.
  • The assignment of activities to times must be defined in the HR system via Production --> Basic data --> Work center --> General data --> Standard value --> Define standard value key.

Recording confirmations:

  • The confirmation is recorded using the confirmation transaction in the respective application (PPP/PM/PS). The personnel number must be specified. The system writes a record to the interface file AFRUHR.

Updating confirmations in HR:

  • Report RPWI1000 generates a batch input session on the basis of the information in the interface file. Logistics confirmations can thus be updated in HR in the form of time tickets.

Updating individual confirmations in HR:

  • The HR transaction is called via the menu path Human resources --> Time management --> Incentive wages --> Maintain. You can use the function Action --> Retrieve confirmations to transfer selected confirmations to the HR system.

Processing time tickets in HR:

  • Time tickets can be maintained via the menu path Human resources --> Time management --> Incentive wages -- > Maintain. Data entered in Logistics is not affected.
  • The time tickets can be accessed for time leveling and payroll accounting.

SAP Note 26686 - Batch input WBS: Leave to Transaction not permitted

Symptom:

A batch input for the work breakdown structure, which does not change any data, terminates with the following error message when saving:
Leave to Transaction not permitted

Cause and prerequisites

Leave to Transaction Sy-Tcode is not supported (by the SAP basis department) during the batch input in Rel.2.1. and 2.2.

Solution
Correction

Additional key words

Transaction CJ02, CJ07, CJ12

SAP Note 26685 - Object list and scheduling agreement

Symptom:

In a sales document, there are main items with subitems. In the main items, several schedule lines are generated with the same date. Then the schedule lines of the main item are changed. The changes are incorrectly transferred into the schedule lines of the subitems.

Cause and prerequisites

The date and arrival time must be unique so that the schedule lines of the subitems can be identified when transferring the data.

Solution
The following repair ensures that the date and arrival time of a schedule line are unique. If necessary, an arrival time must then only be entered in the first schedule line before the entry of the second schedule line for the same date.

Additional key words

Rebate in kind, V1336.

SAP Note 26681 - Leasing: Posting date for interest/depreciation

Symptom:

The periodic posting of depreciation is distributed incorrectly when leased assets are valuated using method 'L' = 'depreciation and interest for the present value, determined from the payments to be made'.
Similarly, the proportional accumulated depreciation is calculated incorrectly for a transfer retirement or simple retirement.

Cause and prerequisites

The problem only occurs when the payment cycle is quarterly, semi-annual or annual, instead of monthly.

Solution
This problem is actually not an error, but a distribution option that cannot be set up. Determining interest and depreciation according to the present value method affects amounts, but not the date when they are posted.
At present, the posting date is set to the end of the period. For a payment of 12, for example, the interest and depreciation falling due on a payment is posted after 12 months have elapsed (including the payment period).
The following program modification enables you to change the posting date to the start of the period, so that the payments and the posting of interest or depreciation fall within the same period.
There is not yet a programming solution to the problem of evenly distributing the interest and depreciation to the individual periods between two payments.

Additional key words

Transfer SAPLAFAR RABUCH00 Capital Lease

SAP Note 26679 - RPCLPCG0 Absence Calendar SSP/SMP - week missing

Symptom:

The absence calendar for SSP/SMP does not show the week 23/10 - 29/10/95

Cause and prerequisites
Solution
The problem has been corrected by a source code change.

SAP Note 26676 - Dump in program RVDVVL11 if more than 255 docs.

Symptom:

If more than 255 deliveries are transferred from R/2 to R/3, a dump can occur

Cause and prerequisites

This is caused by a program error.

Solution
Implement the correction in program RVDVVL11
Caution:
The note was changed on October 28th, 1997, since the old version contained an error in the source code.

SAP Note 26671 - Termination of RSCLICOP with DBIF_RSQL_NO_MEMORY

Symptom:

RSCLICOP terminates with DBIF_RSQL_NO_MEMORY. The table which it wants to copy is a logical cluster table (e.g. BSEG or CDHDR).
The error is reported from dbrclu2.c line 36?? (in the C-coding in the function c2_write_to_db()).
If an ABAP short dump can be generated, it shows the following code selection:
LSCCRF01, line 38970
038910 SELECT * PACKAGE SIZE 512 INTO TABLE IS FROM (TABLE)
038920 CLIENT SPECIFIED WHERE (CTAB).
038930 IF SY-SUBRC = 0.
038940 READ TABLE IS INDEX 1.
038950 DEL_ENTRY = SY-TFILL + DEL_ENTRY.
038960 * delete the table
> DELETE (TABLE) FROM TABLE IS.
038980 IF SY-SUBRC <> 0.
038990 PERFORM LOG_MSG
039000 USING 2 '143'
039010 SY-MANDT 'del' TABLE SPACE.
039020 ENDIF.
039030 ENDIF.
039040 ENDSELECT.
Thus packages of 512 (BSEG) keys are always collected and then deleted.
(2)
The termination occurs when inserting the new records.
The physical cluster table is not defined in the Dictionary as client-
dependent (for example, in EDIDOC the client field MANDT was in
the Dictionary MANDT CHAR 3 instead of MANDT CLNT 3).

Additional key words

Client copy, CDCLS, CDHDR, RFBLG, BSEG, EDIDOC, EDIDD, cluster,
cluster table

Cause and prerequisites

The cause of the termination is the programming of the cluster
interface.
An internal storage area which is required if records of a cluster
table are written to the database while reading cursor (selections) are
still open for this cluster table has to be extended.
However, the storage requirements cannot be fulfilled.

Solution
(1)
Corrected in release 3.0C

Workarounds:
Increase the SHORT storage area of the R/3 system for the duration
of the client copy (profile parameter "ztta/short_area")
or
change LSCCRF01 so that 20 is used instead of 512 as the package size
(has a negative influence on the total duration of the copy).
(2)
Define the physical cluster table in the Dictionary as client-dependent.

SAP Note 26669 - Material number display in computation of quantity

Symptom:

The material number display during the computation of quantities of a master recipe only has 15 characters.
The text of a phantom material is not displayed in the materials list.

Cause and prerequisites

This applies to Releases 3.00 (FCS) and 3.0A.

Solution
Correction in P30: P30K013289

The files "R013289.P30" and "K013289.P30" for the above correction can be found on SAPSERV3 in the directory "/dist/permanent".

Please import the files according to the procedure described in note 13719.

Additional key words

COR1, COR2, COR3, material computation of quantities, phantom material, MATNR
Process order.

SAP Note 26667 - MMIM: Repet. manufacturing - Document cancellation

Symptom:

The cancellation of material documents that were created with reference to a reservation in repetitive manufacturing is possibly terminated with the following message:
Document $ does not contain any selectable items (M7064) and traceable in P22.

Long text of the error message:
(Only for reservations): No movements are yet allowed for the reservation items.

Cause and prerequisites

Program error.

Solution
Please change Include MM07MFB0.

Additional key words

MF41

SAP Note 26666 - RABUCH00/RAPOST2000 inexplicable amnts for depreciatn pstngs

Symptom:

Inexplicable amounts are posted during the depreciation posting, for example, after a release upgrade or other changes.

The same problem occurs when displaying the monthly development in the Asset Explorer AW01.

Other terms

RABUCH00, RAPOST2000, AFAB, AFABN

Reason and Prerequisites

Depreciation parameters were probably changed in the depreciation keys or the depreciation calculation keys or the depreciation areas.
An example would be the indicator for the calculation after the end of the planned life or below zero.
During the depreciation posting, the depreciation of every fixed asset is recalculated internally according to the new parameters.

However, the recalculated depreciation is only used to determine the amount to be posted. The old planned depreciation remains in the fixed asset and is also displayed as a planned amount in the log of the depreciation run (RABUCH00 or RAPOST2000).

Solution
Check the changed depreciation parameters in Customizing. If you want the changes of the depreciation parameters in Customizing to apply to all fixed assets, you have to carry out a depreciation recalculation with the program RAAFAR00.

SAP Note 26662 - Consignment and returnable packaging - GI

Symptom:

Problems occurred in goods issue for the order types KB and KR, and for returnable packaging. An entry is missing in table T156S.

Cause and prerequisites

COPA is active

Solution
The following repair is possible

SAP Note 26660 - Composite note: 3.0B corrections for packing

Symptom:

Packing error in 3.0A

Cause and prerequisites

Program error

Solution
Program change

SAP Note 26659 - Download / upload default path

Symptom:

Default path for file transfer (upload/download) should be set

Cause and prerequisites

The installation directory is often entered as the working directory of the SAPGUI icon. This directory can be preallocated dependently from the work station or user.
This preallocation is only possible if the preallocated file names are addressed before the function module UPLOAD or DOWNLOAD OHNE!! is used. (??)

Solution
    1. The working directory for SAPGUI can be changed in the program manager (attributes) to any directory for which write authorization is available (also see note 9174)
    2. In the file FRONT.INI, a section "Filetransfer" can be created as of R/3 Releases 3.0, 2.2D, 2.1J, in which the key "Path" is maintained. If this entry has no effect, the file front.ini must be copied into the work directory of the SAPGUI (also see Note 130047).
    3. Alternative to 2) the user parameters GR8 (download path) or GR9 (upload path) can be preset with (System -> User profile -> User parameters). These values are then not taken from the file Front.ini.
Sequence of steps for determining the path
=========================================
FILENAME set -> No adjustment
otherwise: Is parameter GR8/GR9 set ?
otherwise: Front.Ini, [FILETRANSFER] (PATH=xx) ?
otherwise: Front.Ini, [FILETRANSFER] (PATHUPLOAD=xx / PATHDOWNLOAD=xx)?
otherwise: Adjust working directory according to the installation of SAPGUI

Example for file Front.ini

[Filetransfer]
Path=C:\DOWNLOAD

Additional key words

File transfer front SAPGUI UPLOAD DOWNLOAD WINDOWS WIN95 NT

SAP Note 26656 - Customizing for cond type/tables: agreements (3.0A)

Symptom:

When using transaction VB(4 to customize condition types/tables for agreements, the following error message occurs when using the "help" function (PF4) for condition tables:

"E: Entry E 029 does not exist (check your entry)".

Cause and prerequisites

Program errors.

Solution
Program corrections.

SAP Note 26655 - Assembly order with produc. plant <> planning plant

Symptom:

From a sales document, you create an assembly order for more than one BOM item or schedule line for the same material. The special procurement key in the material specifies that the production should take place in a plant other than the delivery (planning).
When you create a second or more assembly orders, it is possible that the routing is not found (the system searches in the delivery plant/planning plant).

Cause and prerequisites
Solution
Program correction

Additional key words

Production order, sales order

SAP Note 26653 - Performance improvement SD document update

Symptom:

Long validity periods when updating large documents.

Cause and prerequisites

Database operations with an effort for the update of indexes.

Solution

In programs LV05IFxI (x = 0, 1, 2, 3, ... , 8) in which sales and distribution document indexes are updated, you can activate the array insert for the insert mode. The corrections required to do this are described in the attachment.

In the following overview you can see which programs in your system can be used for a performance improvement:

Program Table Contents of the index table

LV05IF0I VAKPA Orders by partner function
LV05IF1I VAPMA Order items by material
LV05IF2I VAKGU Quotation validity
LV05IF3I VEPVG Delivery due index
LV05IF4I VLKPA Deliveries by partner functions
LV05IF5I VKDFS Billing initiator
LV05IF6I VLPMA Delivery items by material
LV05IF7I VRKPA Bills by partner functions
LV05IF8I VRPMA Billing items for each material

The highest performance improvement is achieved for programs LV05IF1I, LV05IF6I and LV05IF8I because here an item index is written.

This note will not be included in a Hot Package. Check whether you require the correction described in your system. When you apply a Hot Package, the system may overwrite parts of this correction. Therefore, when applying a Hot Package, make sure that you retain this correction (SPAM/SPAU) unchanged in your system.

Additional key words

Performance, VA01, VL01, VF01, VA02, VL02, VF02, VL04, VF04, index, indexes, validity period, update, update program, sales order, delivery, billing document

SAP Note 26648 - Shipping point - inc. display of poss. entries

Symptom:

The possible entries (F4) are incorrect on the field Shipping point in the overview screen Shipping of the Order Entry (SAPMV45A screen:403).
All created shipping points are displayed and not just the allowed ones.

Cause and prerequisites
Solution
Repair in the program code

SAP Note 26646 - Error during transfer to FI when using several taxes

Symptom:

During the tax calculation for Canada, billing documents were not transferred to Financial Accounting because the tax conditions MWST and UTX1 used different tax indicators.
The check carried out during the transfer to FI then comes to the conclusion that the transferred tax amounts are incorrect.

Cause and prerequisites

Initial situation in the example:

The tax table TAXCA in FI contains the following condition types: GST Taxes on sales/purchases
PST Sales tax

Two tax conditions are defined in SD Customizing: MWST Taxes on sales/purchases and
UTX1 Sales tax

Condition records are created in SD for both condition types. These condition records are read within pricing and supply the control indicator for accounting.

The tax calculation in FI is designed so that the tax percentage rates are found using the tax indicator. Example:

Tax indicator: SA ---> GST 7% - PST 12%
SB ---> GST 7% - PST 10%
SC ---> GST 7% - PST 11%

The above problem occurs because it is not ensured that the tax condition records found in SD provide the same tax indicator.

Solution

The calculation of the taxes is changed to the method that is already used for U.S. taxes with tax jurisdiction code.
In this case, the tax indicator is found in SD via an object condition UTXJ. This is then used to calculate the percentage rates from FI. The redundant maintenance of the percentage rates in SD and FI is then no longer applicable.

Carry out the following Customizing activities:

    1. In the country table, you must first find out which tax table is used for Canada (for example: TAXCA)
    2. In FI Customizing you must make a note of the tax conditions in the tax calculation schema (for example PST, GST).
    3. In SD Customizing you must then copy tax condition type JR1 into PST including condition category D and then copy group condition X PST into GST.
    4. Enter the following conditions in the SD pricing procedure (for example RVCA01) instead of the condition types MWST and UTX1 used up to now:

905 UTXJ with manual = BLANK

910 GST with manual = X

915 PST with manual = X

    5. In SD Customizing you must enter UTXJ as the only taxes used in the country in question and maintain the allowed tax classifications for customer and material
    6. Finally create the condition records for UTXJ.

Additional key words

SD-FI, CTX1, tax, FF747


SAP Note 26645 - Reporting ( especially Report portfolio )

Symptom:

1. In the graphic menu, incorrect sorting within the hierarchy can be displayed. Report classes, which lie within one level, are displayed in a sequence other than the one defined.
2. If you choose a report class in the graphic menu, you reach a graphic displaying all reports for the selected report class. Here an error can occur in the color display. The selected report class should basically have the same color on the two screens. On the 2nd screen, however, an incorrect color is sometimes displayed.
3. If you copy a definition report as a screen sequence from drill-down reporting to the report portfolio, the following functions are recorded incorrectly:
a) Display comment
b) Key figure information
c) Characteristics (individual characteristic)
4. In definition reports, errors can appear for the following functions
a) Switch off column
b) Delete column
c) Sort column
d) Column On/Off
e) Currency (for a specified column)
5. Termination "Type conflict at ASSIGN" in Program "SAPLKYP3"
The error can appear when calling function module RKD_VARIABLE_CHECK.
This function module in used in several places for interval validation
when entering variables.

Cause and prerequisites
Solution
The problems are corrected in Release 3.0B.

SAP Note 26641 - ISHCM locking transceiver files

Symptom:

Miscellaneous.The transceiver programs often remain hanging and can then no longer be stopped anymore by means of "kill -9".
On Windows NT, you may find that messages arrive incompletely in the NTISH.dat file (this in turn causes the additional error that SS_STAT.dat is not locked).
It is also advantageous for programming partner connections to the R/3 communication module if you are acquainted with the locking mechanism (see below).
Additional key words

File locks, locking, ISHCM, transceivers, put_tab, PUT_TAB, consulting
Cause and prerequisites

Diverse.Problems often occur in connection with the file systems mounted.Read the related notes for more information.
On Windows NT, the special feature still exists that a file lock without a size specification (which is actually common) only refers to the file in available length. That means appending is possible despite the lock.
Solution

Difficult.In order to determine the cause of the error it can be helpful to know the locking mechanism of the transceiver programs.

When transferring data out from within the R/3 System, SS_STAT.dat is used as the central lock object (see documentation "SAP R/3 communications module"). That is important. It is not the data file which is the lock object here but SS_STAT.dat. Therefore, the partner program need (only) lock SS_STAT.dat in the case of this communication direction. If only NTISH.dat is locked, it can create a diverse range of error symptoms.

When receiving data into the R/3 System, the corresponding files are always locked directly (not SS_STAT.dat).

Clarify C source code statements here which the locking mechanism creates when transferring data out of R/3:

1. .tmp (is called differently as of transceiver 1.42) and fill:
if (fp == NULL) {
if ((fp = fopen{NTXXXTEMP,"w+"))==NULL)
exit(1);
}
fputs(.....

2. lock SS_STAT.dat:
if ((sfd=LockFile(SS_STAT))==-1) goto ssstatfalse;

3. replace .dat by .tmp-Rename (or append in the append mode):
if (rename(NTXXXTEMP, NTXXXFILE)) goto renamefalse;

The routine used under 2) should look as follows:
int LockFile(fname)
char *fname;
{
int try;
int sfd;
time_t t;

try = 0;
while (1) {
#ifndef OS2
sfd = open(fname, O_RDWR|O_CREAT, 0666);
if (sfd==-1) return -1;
lck.l_type=F_WRLCK;
lck.l_whence = 0;
lck.l_start = 01;
lck.l_len = 01;
if (fcntl(sfd,F_SETLK, &lck) < 0) {
if (++try < MAXTRY) { close(sfd); sleep(2); }
else return -1;
} else return sfd;
#else
sfd = sopen(fname, O_RDWR|O_CREAT, SH_DENYRW, S_IREAD|S_IWRITE);
if (sfd==-1) {
if (++try < MAXTRY) {
t = time(01);
while (time(01)-t < 3) ;
} else return -1;
} else return sfd;
#endif
}
}