SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
PI sheet is not completed.
Cause and prerequisitesPI sheet, complete, status
An item of a subcontractor order contains a component with negative quantity (which is not provided to the subcontractor but which is returned by him). The component is still posted as a withdrawal with movement type 543 during the goods receipt of the item.
Cause and prerequisitesProgram error
SolutionSubcontracting, MB01
If you press F15 (Exit) in the capacity requirements list, you do not exit the list.
Cause and prerequisitesCapacity adjustment, capacity requirement list, PF15, Exit
When generating a functional area, a type difference is found for a field. The type originally determined from the ABAP/4 Dictionary no longer matches the type currently listed in the ABAP/4 Dictionary. This points to changes in the ABAP/4 Dictionary since the last generation of the functional area.
In the following two cases, this error is mistakenly reported, for every generation.
1. The field f has the type C in the DDIC
In the Dictionary, the field has the DDIC type VARC, LRAW, LCHR or RAW with a length of more than 999 characters.
2. The field f has the type I in the DDIC
In the Dictionary, the field has the DDIC type INT1 or INT2.
Case 1:
Fields with a length of more than 999 characters cannot be included directly as fields in a functional group. As of Release 3.0, it is no longer possible to include such a field in a functional group when maintaining a functional area. An error message is returned.
Case 2:
The table to which the field belongs was added to a functional area as an additional table. In this case, the DDIC type INT1 or INT2 is not represented correctly on the ABAP type I.
Query, functional area, generation
If you create a general costs activity without cost element, the costs of this activity are not taken into account during costing.
Cause and prerequisitesIt is not checked whether a cost element exists.
SolutionNetwork;
There are fields in a condition table for listing/exclusion for which no check is made against the check table. The name is also not displayed from the corresponding text table.
The check has only been implemented for the fields contained in the standard system.
Note 12905 only applies to pricing and output conditions.
In a later release, this check and the procurement of the text will be carried out automatically. Until then, you need to make the following modification.
A new check routine must be programmed for the new field.
To complete this check routine, follow the steps of the example that follow.
Example : Field ZZPRO5 is chosen as a new field, of which the first 5 positions represent a product hierarchy.
* FORM KOMGG-ZZPRO5 *
*---------------------------------------------------------------------*
* Prüfen der Produkthierarchie (stelle 1 - 5 ) *
*---------------------------------------------------------------------*
* --> KV_ERROR : Fehlermeldung falls Prod.Hiera. nicht vorhanden *
* --> KV_SUBRC : Returncode, falls keine Fehlermeldung angefordert *
*---------------------------------------------------------------------*
FORM KOMGG-ZZPRO5 USING KP_ERROR KP_SUBRC.
* Reset Returncode
CLEAR KP_SUBRC.
* Löschen aktiv ?
PERFORM DELETE_INDICATOR_SET.
* Keine Prüfung beim Löschen
CHECK DELETE_INDICATOR = NO.
* Produkthierarchie gerade gelesen ?
IF KOMGG-ZZPRO5 = T179-PRODH(5) AND
T179-PRODH+5 = SPACE.
EXIT.
ENDIF.
* Initialisieren der Workarea
IF KOMGG-ZZPRO5 EQ SPACE.
CLEAR: T179, T179T.
EXIT.
ENDIF.
* Lesen der Kundengruppen-Tabelle
SELECT SINGLE * FROM T179 WHERE PRODH EQ KOMGG-ZZPRO5.
IF SY-SUBRC NE 0.
CLEAR: T179, T179T.
* Ausgabe einer Fehlermeldung ?
IF KP_ERROR = YES.
MESSAGE E033 WITH KOMGG-ZZPRO5.
ELSE.
KP_SUBRC = SY-SUBRC.
EXIT.
ENDIF.
ENDIF.
* Lesen der Bezeichnung
SELECT SINGLE * FROM T179T WHERE SPRAS EQ SY-LANGU
AND PRODH EQ KOMGG-ZZPRO5.
IF SY-SUBRC <> 0.
CLEAR T179T.
ENDIF.
ENDFORM.
Insert the following code in include MV130F0x in the routine FELD_PRUEFUNG at the end of the CASE statement.
CASE VK_FIELDNAME.
...
...
WHEN 'ZZPRO5'. PERFORM KOMGG-ZZPRO5 USING FP_ERROR FP_SUBRC.
ENDCASE.
Insert the following code in include MV130F0x in the routine FILL_DEFAULT at the end of the CASE statement.
CASE FD_FIELD.
...
...
WHEN 'ZZPRO5'. MOVE T179T-VTEXT TO TEXT_DEFAULT-TEXT.
ENDCASE.
Insert the following program code in Include MV130F0x in the routine GET_TEXT at the end of the CASE statement
CASE TEXT_ERFASSUNG.
...
...
WHEN 'ZZPRO5'. MOVE TEXT_DEFAULT-TEXT TO T179T-VTEXT.
ENDCASE.
Material listing
Material exclusion
In Profitability Analysis, valuation is not possible in planning with condition records on the basis of the plan version (VERSI field).
Cause and prerequisitesThe VERSI field is not contained in the tables KOMG/K and SAPLKEAB and is also not taken into account in program SAPLKEAB.
SolutionValuation
When you call the planning table from the material view, the quantities of all planned orders are doubled when you go back.
Cause and prerequisitesProgram error
SolutionIf you call the planning table with MF50 without first showing capacity data, the new dates are not copied when you return to the planning table
Cause and prerequisitesThe KBKO record is not read because the query on whether production rate planning or detailed planning should be performed is missing. Up to now, this query was only carried out when showing the capacity data.
SolutionFor 'document_handling_remote', object assignments are not taken over correctly for CV02. Links are partially deleted although they were also transferred again.
Cause and prerequisitesError in 'SAPLCV00' FORM 'BUCHEN_DOKUMENT'.
For 'document_handling_remote', object assignments are not taken over correctly for CV02. Links are partially deleted although they were also transferred again.
Cause and prerequisitesError in 'SAPLCV00' FORM 'BUCHEN_DOKUMENT'.
If you parked cross-company code documents in preliminary posting and different local currencies have been defined for the company codes involved, then the system outputs a warning that the difference is too large when you enter * in the amount field.
Program error
SolutionFBV1, FBV2, FBV0, F5212
Some (or all) material components are displayed several times in the schedule information system. This applies to networks with many material components (>200).
Cause and prerequisitesProgram error (the RANGE was split incorrectly during the read operation)
SolutionWhen posting goods received (trans. MR01) an incorrect SL summary record is updated, namely a record with the GR/IR clearing account and the cost center which is allocated to the corresponding consumption account. (this second line is also updated.) Thus, the cost center is debited too much.
Cause and prerequisitesThe consumption cost center is placed into the line with the GR/IR account by MM so that CO has a link to the invoice. However, it was forgotten here that the SL therefore receives incorrect values.
SolutionRMWE, GR/IR
When creating a cost center or a cost element, the error KC028 occurs: You are not in the home system of controlling area &
Creating is not possible.
In distributed systems, cost centers or cost elements can be created only in the logical system assigned to the controlling area. However, the controlling area is obviously assigned to a logical system other than the client that you are working in.
SolutionTransaction KS01, KA01, KA06
A screen should be generated in the Screenpainter. The screen contains a subscreen area (INCLUDE screen area).
The error message "several copies of subscreen ... exists" is issued during generation and prevents the screen from being generated.
()EUNOTE, EUSCREENPAINTER, EUDYNPRO
The effect only occurs in customer systems with an early 3.00 Release.
SolutionRuntime error when executing reports after a release upgrade.
Cause and prerequisitesAfter a release upgrade, the function 'convert reports' must first be performed either manually or automatically.
This leads to a runtime error, caused by a RAISE statement specified explicitly in the program.
Key word: Conversion, RAISE, UMSETZEN_06, UMSETZEN_05, drill-down report
Runtime error
The error message E629 'The balance of transaction type group & is negative for area &.' or E628 'The balance of transaction type group & is positive for area &.' appears without cause during the value recalculation from the asset value display AW01 or with report RAAFAR00.
The error message can also be output during depreciation posting with report RABUCH00 or for an evaluation during the fiscal year, since a recalculation of the values is also carried out in these cases.
The error only occurs if there are reversed line items on the fixed asset.
SolutionRABEST01 RAGITT01 RAZUGA01 RAABGA01 RAHAFA01 SAPDBADA
When trying to delete or deactivate tax codes, occasional update terminations can occur or the change is not made.
It can also happen that data apparently has not been changed, but after a short time is nevertheless up-to-date.
Blocking problems / commit work / update online and in update task
SolutionFTXP SAPMF82T T007A A003 A053 KONP KONH
Via the list control/transactions (TCode OPK8), it is set that individual lists should be output in several copies.
When printing the original, not only the first one, but also all the following copies are output as originals.
Program error
SolutionPPPROBJU, PPPRSTEU, PPPRLAUF, PPPRMBRL, PPPRWARS, PPPRLOHN, PPPRRUEC
From 3.0 PPPRZUGL, PPPRSPLT
When calling a transaction data report for a derived depreciation area, no transactions are displayed.
Cause and prerequisitesThe depreciation areas which form the derived depreciation area do not all exist for the fixed asset.
This is mainly the case for investment support.
RAGITT01 RAZUGA01 RAABGA01 RAUMBU01
Not all selection views exist in the system. This can cause different errors, for example, when calling up change transports by choosing Logistics -> Sales and distribution -> Transports -> Change transports, the following error message is issued when you use F4 help for the transport number
VW 055: no transports could be found for the selection criteria.
The error only occurs in FCS systems.
The contents of table RSDSQOBJ were not transported to the customer because of an incorrect delivery class.
Treasury
for Transaction FF73 (bank account clearing) ->EM:->A: A: syntax error in screen. SAPMF40C 0210 message number 00041 -> transaction is terminated.
Screen generation
Language element LOOP AT xyz CURSOR x is used in the flow logic of a screen. As long as there is not a database table with the name 'xyz', the screen is correct. If someone now creates a table with this name, the screen becomes incorrect although no changes were made to module pool and screen. If a table actually exists in the database, the loop has priority via it. However the additional specification CURSOR is not allowed for this LOOP AT database table.
As of Release 4.5A the visibility rule is changed to the effect that for the addition CURSOR the table is always taken from the program.
A document parked in invoice verification cannot be posted. The message M8252 'Parked document & cannot be posted (see Extras -> Messages)' appears. If this function is called, you get the message M8107 'No messages exist'.
The invoice document has reference to a purchase order assigned to an account. The account assignment of the purchase order was changed during the preliminary entry.
Program error.
SolutionMR44, preliminary entry, message M8138.
You run program RMMMBIM0 within a background job. This can result in a termination message if, for example, the specified file does not contain any records. This causes the entire background job to be terminated and the subsequent steps to no longer be executed.
Cause and prerequisitesWhile running report RMMMBIM0, a situation occurs that prevents a session or a complete session from being created.
SolutionTermination message: MG 099
When calling up the planning table in the serial planning table (MF50) for the second time, the message 'No work centers found' appears.
Cause and prerequisitesIncorrect filling of the interface to capacity requirements planning
SolutionAfter the installation, the system cannot be started with "startsap". R3trans -d
It terminates with an error message. The error message can differ depending on the kernel release. For example:
2EETW000 "I have some problems during TADIR access"
2EETW150 "SAP_DEXT called with msgnr 900:
Internal Error in DB Interface.
or
2EETW169 no connect possible: "DBMS = DB2/6000DB2DBDFT = 'D3E'
--- SYSTEM = '???'."
R3trans finished (0012).
The attempt to log on to the database via command line processor (CLP) as user
db2 " connect to
fails with the following SQL error message.
SQL1116N A connection to or activation of database
cannot be made because of BACKUP PENDING. SQLSTATE=57019
After the database was converted to logretain mode, an offline backup as described in the installation guide was not carried out.
The intial screens of transactions CK11, CK71 and KKPA abend if the user parameter 'KKL' is set.
Cause and prerequisitesThe transactions affected attempt to load the lot size directly into the intial screen. The format for the parameter "lot size" is QUAN which is not supported by the set/get parameters.
SolutionThe lot size will no longer be found using the user parameters. To avoid the abend, change program SAPMC64S screens 0111 and 0141 as follows:
Unit costing; manual cost estimate
The program for primary cost planning for depreciation and interest has already incorrectly calculated costs for periods for the planned investments from depreciation and interest, that are contained in the planned acquisition year but before the planned start-up date.
or
all the costs were incorrectly added to the last period and not distributed over the periods to be planned.
Program error.
SolutionPeriodic processing RAKOPL AR13
When function module MESSAGE_STORE is called, which is used for issuing error messages in CO from the buffer, mode COLLECT_AND_SEND = 'X' is not completed.
The function module calls function module CM_F_MESSAGE which, in turn, calls MESSAGE_STORE recursively with the same parameters. This chain terminates when the stack overflows (STACK_PARM_NO_ROLL_MEMORY or STACK_VALUE_TOO_LARGE).
The message handler must first have been initialized with function module MESSAGES_INITIALIZE in mode COLLECT_AND_SEND = 'X'.
SolutionExcerpt from the dump: =====================
ABAP/4 runtime error RAISE_EXCEPTION
occurred on August 31st, 1995 at 08:43:30
Exception "NOT_FOUND" initialized
User, transaction...
--------------------
Client............. 019
User............ "DPD_3"
Language key... "D"
Transaction......... "SB01"
Program............ "SAPLSF04"
Screen.............. "SAPMSSY01000"
Screen line......... 6
---------------------------------------
Information on the point of termination
---------------------------------------
The termination occurred in "BM_NAVIGATE" in the ABAP/4 program "SAPLSF04".
The main program was "SBMHV000".
In the source code, the point of termination is in line 263 (for selecting using the editor: 2630) the ABAP/4 source "LSF04U06".
----------------------
Section of source code
----------------------
002330 PERFORM CALL_GRAPHIC
002340 USING NAV_MODEL
002350 GRAPHIC_ACTIVE.
002360 ENDIF.
002550
002560 WHEN C_NAV_IN_OUT. " input-output assign
002570 SELECT SINGLE * FROM DF40D
002580 WHERE PARENT_TYP = NAVTYP
002590 AND PARENT_OBJ = NAVOBJ
002600 AND AS4LOCAL = C_AS4_ACTIVE
002610 AND MODEL_TYP = C_MTYP_FUN_ASS_DIA.
002620 IF SY-SUBRC <> 0.
-----> RAISE NOT_FOUND.
002640 ELSE.
002650 CALL FUNCTION 'BM_FA_DIAGRAM'
002660 EXPORTING
002670 FA_OBJ = NAVOBJ
002680 TYPE = 'I'.
002690 ENDIF.
002700
002710 WHEN C_NAV_ORG_ASS. " sysorg assign
002720 SELECT SINGLE * FROM DF40D
002730 WHERE PARENT_TYP = NAVTYP
002740 AND PARENT_OBJ = NAVOBJ
002750 AND AS4LOCAL = C_AS4_ACTIVE
002760 AND MODEL_TYP = C_MTYP_FUN_ASS_DIA.
002770 IF SY-SUBRC <> 0.
002780 RAISE NOT_FOUND.
002790 ELSE.
002800 CALL FUNCTION 'BM_FA_DIAGRAM'
002810 EXPORTING
002820 FA_OBJ = NAVOBJ
Transaction SB01, selection of the input output assignment for a function which has no input output assignment.
SolutionNo assignment (transaction KVD0) of statistical key figures to activity type if it is of the category 2 (indirect calculation, indirect allocation). System reports error KW752: Activity type & does not exist on cost center & in fiscal year &.
Cause and prerequisitesActivity types can only be provided with statistical key figures after previous ( activity planning ) planning.
However, it can also be useful for activity category 2 without previous planning to have statistical key figures (for example, for indirect activity allocation with retrograde quantity determination).
statistical key figure, activity type, CO-ABC, ABC, allocation, LIS
Single-item plaing with "Display results" (MD02,MD03,MD43,...): when starting the single-item planning run - single-level - (MD03) and clicking on the "Display results" the system issues the message:
A: the value of the field is too long. Display not possible (message number 00020)
The same error may occur in the current stock/requirements list (MD04) or in the MRP list (MD05).
This occurs when the resulting list is so long that it takes up more than 99 pages (2.2G-2.2H or MD04/05: 999).
On several screens of programs SAPMM61X and SAPMM61R, the fields, 'RM61X-PANEW' and 'RM61X-PASUM' have only 3 character spaces (2.2G-2.2H or MD04/05: 4).
Solutiontermination, A00020
During transaction VA43 Display contract, values are lost in the deadlines of billing plans. This also causes the net value in the order item and in the order header to be changed incorrectly.
Cause and prerequisitesProgram error
SolutionVA03, billing plan
When creating a billing document, reference documents are proposed which have already been fully billed.
This affects transactions VF01 and VF11.
Program error
SolutionWhen you use standard form QC02, no certificate is printed.
Cause and prerequisitesFor reasons of naming conventions, layout set QC02 was renamed in QM_QCERT_01 in Release 3.0A.
The included standard texts QCERT* were also renamed:
old new
QCERT_GENERAL_TEXT QM_QCERT_GENERAL_TEXT
QCERT_INSPECTION_METHOD QM_QCERT_INSPECTION_METHOD
QCERT_OFF_SPEC_TEXT QM_QCERT_OFF_SPEC_TEXT
QCERT_OUTPUT_FORMAT_TEXT QM_QCERT_OUTPUT_FORMAT_TEXT
Certificates, certificate profile, simulation, certificate view, SAPscript layout set, standard text, quality certificate QCERT_GENERAL_TEXT
QCERT_INSPECTION_METHOD
QCERT_OFF_SPEC_TEXT
QCERT_OUTPUT_FORMAT_TEXT
You are on the initial screen for maintaining master inspection characteristics. From there, it is not possible to navigate using the menu option 'master data' to other QM master data. You always branch into the screen which you also reach by clicking on 'Back'.
The same occurs if you are the initial screen for maintaining inspection methods.
Program error
SolutionGeneral problems with installation
Cause and prerequisitessee above
see above
Update termination in update module RV_MESSAGE_UPDATE.
A termination occurs when you save or print a sales document.
Error message: Termination 00671 (BCD_FIELD_OVERFLOW). A field overflow occurs in one of the fields LVBDPA-VOLUM, LVBDPA-NTGEW or LVBDPA-BRGEW.
Preconditions: One item has very large weights or volumes.
SolutionTransaction VA05 (List of Sales Orders) does not select sales orders when specifying a sold-to party.
Cause and prerequisitesProgram error
SolutionEnlish translation for Events, Functions or Scenarios missing.
Weitere BegriffeNot labled
Ursache und VoraussetzungenEnglish translation for FCS is only 90% complete and not reviewed.
LösungThe runtime of actual data updates increases in the course of time.
Cause and prerequisitesUnder some ADABAS versions, a SELECT SINGLE FOR UPDATE in module RKEVRK2A causes a performance in proportion to the number of existing actual line items.
SolutionExternal data transfer KE4X
Billing document Billing run Collective billing VF01 VF04
A user only has the authorization "Set operating concern"
Despite this, the user can create cycles or change existing ones via Actual postings, Assessment, Cost center costs, Cycle, Change or Create from Profitability Analysis.
After the new entry or change, the following error message occurs:
No authorization for transaction KEU2.
Authority check in the wrong place in the program.
SolutionSAPMV45A
The possible entries for the sales units in the order entry (F4) are not converted into the logon language.
The logon language is unequal to the internal entry of the units of measure.
SolutionUnit of measure
When you copy an asset main number from a reference asset, the field for the asset main number text is not copied.
Cause and prerequisitesMissing function.
Table ANLH was added to the screen selection at a later date, since it basically contains, except for the main number text, only technical fields that do not have to be copied.
ANLHTXT Master data AS01 AS91
"Posted quantity" and receiver rule "Fixed quantity"
the indefinite credit record is wrongly saved in the
plan (Amount <> 0).
Transaction: KSCB
Program name: ALxxyyyR; SAPMKGA2, SAPMKGAL
Program error
Requirement for error to occur:
Sender rule is "Posted quantity" and receiver rule is "Fixed quantity"
Allocation
When you change a parked document, the field 'Tax code' is processed in the background on the individual screen of the order item.
Cause and prerequisitesProgram error.
SolutionMR42, parking a document, tax
In planning for orders or networks, if you delete the planned costs, then use the "Calculate costs" function, when you display the planned/actual report, the system displays the costs stored in the data base, although the object does not have any costs.
Program error. In the above circumstances, the planned/actual report does not contain the current costs for orders/networks without costs. Instead, it displays the costs from the data base.
The error only affects the display. The actual update of the planned costs is not affected.
Key words: planned costs order planning
Transactions: CN22 CO02
Systems status not set by the system in sales orders.
Cause and prerequisitesFor results analysis for sales order items, the standard system and the IMG for release 2.2 mention a valuation method for the status 'Revenue posted' = 'RVPS'. This method is not relevant since this status cannot be set. This is an error in the standard system and in the IMG.
The following statuses apply to sales orders:
REL The sales order has been released after being opened, and costs
and revenue can be posted.
DLV The sales order is delivered. From release 3.0C, this status
is determined dynamically during results analysis and can be
used for results analysis.
FNBL The sales order has reached final billing. This status must be set
manually up to and including release 3.0B. From 3.0C onwards, this
status is determined dynamically during results analysis, and
therfore no longer has to be set manually.
TECO The sales order is technically completed. All costs and revenues have been posted. This status must be set manually.
A termination occurs in the certificate profile transaction in the certificate view or when creating a certificate for the delivery item:
ABAP/4 runtime error SYSTEM_TYPE_NOT_ELEMENTARY.
Internal defect: Category 14 is not basic but complex.
The used layout set (for example layout set QC02) contains a line /: INCLUDE &QVDM_TKEY& OBJECT QVDM_MAT01 ID QVDM PARAGRAPH HT
with which the long text from the info record of the control data QM in SD is to be printed.
This change must be made for all languages in which a certificate is to be printed.
Certificate profile, simulation, certificate SAPCNVE CONVERSION_EXIT
SAPMQCPA
CALL 'AB_GET_C_PARMS'
Screen SAPMQCPA1106
Long text from the info record of the control data QM in SD QVDM
Layout set QC02
Update termination
Messages for the delivery item
db02 recognizes that the table ONSTATOPT has no primary index
Cause and prerequisitesThis primary index is accidentally deleted (program error) when running RSINFINI.
SolutionFor an order item with order price unit (OPUn), the GR/IR clearing account is not cleared although the delivered quantity equals the quantity invoiced in the order unit.
Cause and prerequisitesThis problem can occur if an invoice is posted before the goods receipt. The system valuates the subsequent goods receipt in accordance with the quantity in the order price unit. If the delivered quantity and quantity invoiced are now different from each other in the order price unit although the delivered quantity and the quantity invoiced are identical in the order unit, this problem occurs.
SolutionPurchase order, scheduling agreement, scheduling agreement item, MB01
When billing a sales order with mixed divisions, the division text was displayed incorrectly in the billing document.
Cause and prerequisitesProgram error
SolutionThe indicator for interval entries is not set for numeric characteristics when creating characteristics by batch input, although the data is maintained accordingly.
Additional key wordscharacteristics
batch input
class system
Program error
SolutionWhen posting the goods receipt for a replenishment delivery for a stock transport order, receive error message M7022 "Withdrawn Quantity exceeded by 98 PC".
Cause and prerequisitesA different unit of measure is specified during batch selection. For example; a stock transport order and subsequent delivery are created with a unit of measure of pieces. Batches are then selected using the unit of measure cartons.
For replenishment deliveries, user should only be able to select batches in the unit of measure specified in the Stock Transport Order, due to MM interface.
VL07 , VL02 , M7022 , SAPMV50A
A time infotype record is entered with times as lasting less than one day. A record lasting less than one day and with times already exists for the same day, but both periods do not overlap. (Example: attendances).
If something other than N is entered for a (real) collision in T554Y, then a warning is issued when the collision screen appears in a case such as this.
Time constraint indicator, time overlap, P2002, I2002
When parking an invoice the user was able to branch from the selection screen to the individual order item and then save. However this only led to the vendor line being saved.
Cause and prerequisitesProgram error.
SolutionMR41; Saving
1. Scheduling parameters cannot be maintained with transaction IP10 (Schedule Maintenance Plan).
2. When you maintain the scheduling parameters with IP02 (Change Maintenance Plan), the following error message is issued:
E002 'Please enter a valid value'.
1. Scheduling parameters in Release 3.00 and 3.0A can only be maintained using the maintenance plan change transaction. When you schedule a maintenance plan (IP10), you can only display the scheduling parameters.
2. Interpretation of radio buttons has been changed in the Basis System.
Different symptoms can occur:
1. Program termination BCD_FIELD_OVERFLOW in SAPLCRK1
2. Poor performance in MRP, MPS, order transactions
During total planning runs that include scheduling and capacity planning, excessive run-times occur: in the spool list of the total planning job a run-time of over 7 minutes for some materials is necessary. If you carry out single-item planning for these materials, the programm runs correctly.
3. Incorrect scheduling results
4. Loop in the requirements planning run (MRP). It jumps back and fort between 2 programs, SAPLCRK1 and SAPLSCAL (visible in the system overview).
MRP, MDBT, requirements planning
MD01: performance (interval of available capacity)
CO01, CO02
Loop
SAPCRK1, SAPLSCAL
The error ONLY occurs, if the available capacity of the work center is split up into time intervals (see active version in the capacity header of the work center).
The internal table XKAPA, which should contain the intervals in sorted order, is unsorted.
Customer would like to know how to transport masterdata from one system to another? Is it possible to do this by clientcopy?
tools and support for configurating and organizing a multi-system szenario (Test-/ Quality-/ Education-/ Production system)
To Migrate data from one system to another there are only 2 techniques supported by SAP. Therefore you have to distinguish between
Master data may only be migrated via batch-input techniques. Only by this method consistency may be guaranteed according to the checks performed during entering data into R/3 system. Transporting configuration data between two R/3 systems is supported via the customizing maintenance functions as follows.
configuration data
When you create batch input sessions using program RFBIBL00 (document transfer), the program terminates with error message F8199 "More than two accounts are transferred" or, as of Release 3.0, error message F8021 "More than two accounts were transferred."
The input file contains a transaction with more than 950 line items (BBSEG).
SolutionRFBIBL00, LFIPIF00
When you try to copy planning data, no data is selected or updated.
Cause and prerequisitesVariables are probably used in the planning set of the planning parameters. However, set variables are not supported until Release 3.0B.
SolutionGP52, GP62
While connecting to an application server of the same database, you receive a remote logon screen to fill out. This should not occur, since you already logged on to the system.
(This occurs, for example, with Transaction SM51 or SM12)
The system determines the wrong database identifier in 3.0 in the following situations:
* you are using different network cards to access your database.
* you are using a AIX SP/2 system.
* you are using Oracle SQLNet V2.
RFC
Incorrect output of the 'ipcs' command in AIX 3.2.5.1
Cause and prerequisitesThe ipcs command in AIX Release 3.2.5.1 leads to an incorrect output.
SolutionR/3 cannot be started - no SHM free
Note 22958 does not eliminate the problem completely. It does not
cover all situations.
Dynamic modification does not take place in cycle DO01 for wage type
/O03.
1. You want to create a sales activity/MAILING by copying using CALL TRANSACTION USING.
After you have entered the reference document number you exit the screen. However, you do not get to the next screen of the sales contact/MAILING processing but to the program code after CALL TRANSACTION USING.
2. If you call the function module RV_CAS_PARTNER_AUSWAHL within a sequence of CALL TRANSACTIONs, you get to the beginning of this transaction chain when using this call.
Program error
Solution1. The order values in the credit master record are always displayed with 2 decimal places (even if the currency of the control area has no decimal places).
2. The same is true of the total liabilities for the reference customer.
Error.
SolutionFD32, FD33, SAPMF02C, credit management, S066, S067
The DME management does not display any data after selecting the overview although data carriers had been created.
Cause and prerequisitesNo data was found for the selection conditions entered.
Possible reasons are:
The control data is no longer in the system because a reorganization run has already been performed or because individual data was deleted using the DME management.
The input values are incorrect.
Check all input values and repeat the transaction. Typical problem sources are:
You cannot create new entries in tables T184, TVEPZ and T184L because a customer name range is reserved for the table/views.
Cause and prerequisitesIf you are encountering any authorization problems, first implement Note 92133.
SolutionDelete the customer name range for the corresponding tables:
T184, V_T184, TVEPZ, V_TVEPZ, V_TVEPZ_V, T184L, V_T184L
'No name range definition is required for the table'
Additional key words
T184, V_T184, TVEPZ, V_TVEPZ, V_TVEPZ_V, T184L, name range
Problems occurs when you copy characteristics into the sales order:
You cannot copy certain fields, for example the bill-to party:
If you change the partner in the sales order after you have entered an item, this is ignored when you copy the characteristics. The partner that was entered as default value when accessing the sales order is copied.
Profitability segment
Branching from the process instruction sheet of PP-PI into results recording of QM does not function, or message QT103 is issued.
Cause and prerequisitesThe inspection point-related results confirmation from the process instruction sheet is implemented only as of Release 3.0B.
SolutionInspection point, CO58, process instruction sheet, results recording, PI sheet, QE11
In already existing delivery schedules or JIT delivery schedules for which the fields for the last delivery posted at the customer (VBLB-LFNKD) and the cumulative received quantity at the customer (VBLB-ABEFZ) are not filled, the cumulative received quantity at the customer is set equal to the cumulative delivered quantity in the delivery schedule when you press ENTER or when you exit the screen. This is incorrect as the cumulative quantities should be set equal only when a new delivery schedule is created.
The situation described above leads to:
Higher-level document is not copied from CV04
Cause and prerequisitesError in the FCS system.
SolutionThe parameter 'statistical documents' is selected but they are still not printed.
Cause and prerequisitesProgram error. The flag for the logical database is not set.
SolutionWhen coyping document info records via batch input, termination CONVT_NO_NUMBER occurs if object assignments for work breakdown structure elements are to be copied.
Cause and prerequisitesThe WBS elements are converted from the external character field in length 24 to the internal numerical format in length 8. The transfer structure DRAD_BI only contains the eight-character field for the internal format. For this reason, the external 24-character number of the WBS element cannot be sent.
SolutionThe selection program RGCSEL00 terminates with the following error:
ABAP/4 runtime error CONVERT_NO_NUMBER
Routine 'RECHNEN' is given as additional information on the point of termination.
The error only occurs if the selection was started using the option 'Calculate ratios'.
Keys were used in the ratio formulas that were not specified with 10 characters, for example, 'K(00010000)' instead of 'K(0000010000)'.
When activating integrated corporate planning with transaction KP96, error message GP623 occurs
"Activity RKPA is not in the number range table".
Program error, occurs only in Release 3.0FCS.
SolutionProgram: SAPMGPLV
Transactions: KP96, KP97
When you try to create a batch search strategy via Logistics -> Materials management -> Inventory management -> Environment -> Batch search strat. -> Create, the following termination message is displayed:
"A: Sequential control: Entry SAPMV13H,A0 is missing in T185V"
No entry found for SAPMV13H in T185V. Which entries have to be inserted in the table ?
The program for posting depreciation does not show a company code in its heading.
Additional key wordsRABUCH00 AFAB
SolutionFor operation TABLE in a cycle with table T511, the following error message is issued:
"Table $ in operation TABLE not supported T511"
This is caused by a typing error in FORM READ-ATAB.
SolutionRPCALCx0
When trying to create cost centers, the error message GS004 "Set 0HK0001_HIER for table CCSS does not exist" was output when you selected the hierarchy level using F4 help.
It is also not possible to display the standard hierarchy of th econtrolling area 0001.
The table SETS does not contain entries in the client in question and is not copied when clients are copied.
The error only occurs in clients not equal to 000 and only for the controlling area 0001 standard by SAP.
The table SETS was not copied by means of client copy when the client was created since it was specified in an exception list.
KS01 KS02 KSH2 KSH3 GS03 SCC0 SCC1 SCC2
1. The program terminates when the block is set because the reason for termination is not trapped by the program.
2. The set blocks are not cancelled.
The production schedulers from the material master and planner group from the routing in each case reference different data elements or data domains.
Cause and prerequisitesoperation_errors
When you enter a goods movement with movement types 325 or 326 for the special stock K (vendor consignment), the system displays message M7001:
E: Please check table XFAUP: entry 0000 does not exist
Incorrect entry in table T156M
SolutionQuantity string
Creating an order item with BOM explosion. However, no object list is found for the material. Message V1113 is displayed that no object list was found. If you then want to delete the item, message V1322 is output: Incorrect index structure for table IVBEP1.
Cause and prerequisitesThe R/3 communication module works if it writes on a local disk drive. However, as soon as a disk drive is mounted via NFS, then the R/3 communication module no longer works.
The HCM programs remain hanging since the transceiver programs themselves are also hanging.
This problem is caused by locking problems.
Eliminate the locking problems. The following situations can cause this problem:
Communications module, RNCSND01, RNCGET01, RNCGET02, RNCGET03, transceiver, PUT_TAB, GET_TAB, SS_STAT, SS_STAT.dat, consulting
This note provides general information about the archiving data in HR.
SARA, PA_LDOC, PA_TRAVEL, PU22, PA_TIME, PA_CALC, PA_PDOC, PA_PIDX, PA_PFUND, payroll data
The following data can be archived in Human Resources (HR)
Archiving of long-term documents from the creation of infotype logs, archiving object PA_LDOC (archives data from: table PCL4, clusters LA and LB)
The scope and time of archiving depend on the legal requirements and evaluations you may want to make. You can archive payroll results for the following countries:
The archiving of payroll results for "Other countries" does not include any legal requirements. It only contains general specifications to provide an archiving for countries that are not yet included in the standard system.
As of Release 4.0B:Archiving of Travel, archiving object PA_TRAVEL (archives data from: tables PCL1, PTRV_HEAD, PTRV_PERIO, cluster TE)
Remember that archiving objects PA_CALC, PA_TIME, and PA_TRAVEL can only be archived after they have been reconciled. For this, transaction PU22 (Archiving Payroll Data) is provided in the system. You can find the transaction in the "Tools" menu of payroll accounting, personnel time management and travel management.
Archiving of pension fund data, archiving object PA_PFUND (archives data from table T5CPK); currently only relevant for Switzerland and the Netherlands.
Archiving of personnel planning data, archiving object BC_HROBJ (archives data from infotypes that have an initial value in the PAPD field in the T777D table; these infotypes are used, for example, in Organizational Management (PA-OS), in Personnel Development (PA-PD) and in Training and Event Management (PE)).
No further archiving of HR master data is currently being planned.
M8159: Tax code & and account & not compatible.
This message is displayed when entering an invoice for a purchase order assigned to an account. The GR/IR account is given in the message.
The cost account from the purchase order does not contain a tax code.
SolutionM8159
The system can display the Quantity (MENGE) and Unit of measure (MEINS) fields (from BSEG) in the line item display, but it does not total the quantities.
Cause and prerequisitesNot programmed
SolutionRFEPOS00
Transactions FBL1, FBL2, FBL3, FBL4, FBL5, FBL6
No change documents are created for status changes.
Additional key wordsStatus, change documents, status change documents, creation of change documents
SolutionA field is suppressed during posting or when displaying a document without any obvious reason.
SolutionShown in an example of field BSEG-KURSR (hedged exchange rate):
FAUNA (1st field): SKB1-FAUS1
Table name : BSEG
Field name : KURSR
Execute -> in "Group" column you will find the field selection item
(here: 032).
(If you know the screen which contains the field, you can also see this from modification 1 of the field attributes.)
FAUNA : SKB1-FAUS1
Group1 : 032
Group
Select all - Execute
-> "1ALLG" group
Language : (for example) E
FAUNA : SKB1-FAUS1
Group : 1ALLG
Name
Select all - Execute
-> "General data" description
Language : (for example) E
FAUNA : SKB1-FAUS1
Group1 : 032
Select all - Execute
-> "Hedging" description
parameters - Control - Field status definition (Transaction OB14) and the entry Field status variant - Field status group (determine, for example, field status variant from T001 using SE17) and "Edit field status"
You can now use the path determined above:
WHEN 010.
and you will find, for example, IF BKPF-WAERS EQ T001-WAERS
OR RFOPT-XNOWA NE SPACE.
D01_RC = 4.
ENDIF.and you can draw your conclusions.
(D01_RC = 4 means: Field is suppressed
D01_RC = 8 means: Field is displayed but not ready for input).
In the example, you can see on screen SAPMF05A/0312 that group 3 = "001" for the business area in the tax items.
Now search for a statement in program MF05AO00 using GROUP3 in module DYNPRO_MODIFIZIEREN and analyze the source code.
Field selection string, SAPMF05A, SAPMF05L, screen modification FB01, FB03, OBC4, OBC5, T004F, TBSL
You want to change the database user passwords.
DBMGUI, DBMCLI, SQLSTUDIO, control, password, password change, user, dbmuser, dbmpwd, superdba, sapr3, sapsid, sapsiddb
The latest versions (7.6) of DBMGUI and SQLStudio are required wherever these are mentioned. Install the DBMGUI of Version 7.6 to change the passwords using the procedure described in this note.
You can use the tools belonging to MaxDB Version 7.6 to manage databases with MaxDB kernel versions lower than Version 7.6 also.
For restrictions in relation to the choice or length of the password, see the MaxDB documentation.
In principle, there are several types of database users. These are described in detail in the documentation (Note 767598).
Note:
To simplify logon procedures, SYSDBA users are also available at DBM user level and the 'primary' DBM user is also in the database.
None
None
Remark: version 3.1.2 is no longer supported.
Striping:
Striping of hard disks or partitions has no advantages for SAP DB
(Adabas)
Operation of SAP DB with RAID systems:
SAP DB systems can also be operated with RAID architectures without limitations as long as the following statements are taken into consideration:
RAID1, mirroring, striping, among other things
SAPDBA reports that control files are missing, although they exist
Cause and prerequisitesIn the init.ora profile, the ORACLE home directory was specified with "$ORACLE_HOME" instead of with "?".
SolutionThe allocation in FI-SL by mistake writes receiver values to the sender records.
Cause and prerequisitesThe error can actually only occur if the distribution or allocation is made to exactly one receiver value and if this dimension is specified only in the receiver.
Example:
Sender:
Account 400,000
Business area 1000
Receiver:
Business area 1000 - 2000
Cost center 4711
In this case, the sender records would by mistake contain cost center 4711 although this is only specified for the receiver.
FI-SL, assessment, distribution