SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
You could create a physical inventory document for a customer and a material for special stock V or W, even if no special stock segment for this customer was created for this material.
Now the error message 'Special stock V(W) "CUSTOMER" of this material does not exist' is output.
Program error
SolutionChange messages (indicator NAST-AENDE is selected) that were created with "Repeat message" are not output.
ME90 or report RSNAST00 generate the following message: 'Messages output' (ME257), but no spool request is created.
For messages with transmission medium EDI, message ME760 is generated.
It is not possible to repeatedly output change messages because the print program always reads the purchase orders from the database and, of course, cannot determine any changes since the last printing. You can always create a change message, but the decision whether it is printed out is made by the print program. Especially in the case of change messages, all change documents since the last printout are read. And if you repeat the printout without any changes, the system does not find any, of course. However, you can always create a new printout, but then you always have to use the latest database status. Here, no change documents are interpreted. For this reason, you can always print it out.
SolutionPurchase order, request for quotation, outline agreement, delivery schedule ME22, ME42, ME32, ME38, printout of changes
If you are using the internal number assignment when you create a vendor and at the same allocate a plant (Additional data - Purchasing), INTERN is written as number into the field 'Vendor number' in table T001W.
Program error
SolutionABAP runtime error "Program MC_PREM missing" (or other MC_-program)
Cause and prerequisitesError in the SAP upgrade procedure, the XPRA programs RSMCSRGA and SAPUMCNV were not executed during the upgrade.
SolutionMC_MERK MC_EQUI
Printout of a graphic in SAP R/3 3.0.
Cause and prerequisitesNetwork graphic, hierarchy graphic, cluster editor, bar chart
The planning log of the planning board contains the message "Operation ends after basic date for order" although the dates are within the basic dates.
Cause and prerequisitesFinite scheduling
In backorder processing (transaction CO06) and in the MRP display (MRP list, stock/reqmts list...) with period totals, the quantities displayed may be incorrect:
As a result, the following is displayed for length specifications (m) when you display, for example, available capacities in SD quotations.
' .970,00 '.
10000.000 is displayed in the availability overview (e.g. VA02).
Error in member MM61XCON
SolutionCO06 MD02 MD03 MD04 MD05 MD06 MD43
Short dump with function Print cycle
Cause and prerequisitesProgram error.
An ABAP/4 runtime error CALL_FUNCTION_PARM_MISSING occurs when calling the Print cycle function when using a maintenance transaction for assessments and distributions.
The following transactions are affected:
KSU1 KSU2 KSU3 KSU7 KSU8 KSU9 KSV1 KSV2 KSV3 KSV7 KSV8 KSV9
KSW1 KSW2 KSW3 KSW7 KSW8 KSW9 KEU1 KEU2 KEU3
GA11 GA12 GA13 GA27 GA28 GA29 GA31 GA32 GA33 GA47 GA48 GA49
For materials handled in batches, you cannot enter a valuation type.
As of Release 3.0B, you can predefine a valuation type from which the batch is referenced later. Valuation type and batch are checked against each other if both are available.
Batch, valuation type
The partner function DP (different payee) is not proposed and cannot be created manually.
Cause and prerequisitesThe partner function DP was only proposed if it was marked as mandatory role in the partner determination procedure. In this case, there was no proposal from field LFA1-LNRZA.
SolutionThe reports for printing routings (RCPDRK00) and inspection plans
(RQPDRK00) use values in the WRITE statements for column output based
on an 18-digit material number. The output format of the reports was
changed such that material numbers up to 35 digits could also be issued.
Output of material number up to and including 35 digits.
SolutionIncluding 35-digit material number in RQPDRK00, RCPDRK00.
QP05
The customer wants to define authorization groups for authorization objects in FI-SL or for the cost center summarization.
Cause and prerequisitesF1 and F4 help not sufficient
SolutionIn FI-SL, the authorization group is used in the following authorization objects:
For Reporting, there are also the following objects:
Please maintain the table/view V_TBRG with the help of the extended table maintenance for the corresponding authorization object.
If you want to define the authorization group 'TEST' for sets, you must proceed as follows:
Authorization, cost center summarization, KR05 ----- SUPPORTGUIDE 20010208103353 -----
REPORTWRITER, SGRW_AUTHORITY, SGRW_DOCU_CONS_NOTE
SGRW_SL
If a document with "Calculate tax" was entered within preliminary posting, this setting could not be cancelled. As a consequence, documents were not posted, for example, when the tax was manually specified later.
Cause and prerequisitesFBV1, FBV2, FBV0, preliminary posting
When printing addresses, a mandatory blank line is output between the line for P.O. Box / Street and the line for the city.
This is not required for the current destination country.
The country-specific formatting routines are coded in the function module ADDRESS_INTO_PRINTFORM.
The formats were set up according to official requirements.
For all countries, with the exception of USA (routine 004), Canada (005), Great Britain / Ireland (006), Switzerland (011) and Austria (014), a mandatory blank line is output between the line for P.O. Box / Street and the line for the city, providing the number of available lines is sufficient.
Address, print, mandatory blank line
BAS_PRINT
BAS_EXITS
Termination with duplicate records on table AFPO
Cause and prerequisitesProgram error
SolutionTransaktion VORF, route determination, detail screen 'weight group route':
Screen shows one or more lines with weight group = blank and a related text <> blank (e.g. 'up to 10 kg'). Pressing a key like
Table TVLGT (Routes: Weight Groups for Deliveries: Texts) contains an entry with weight group = blank and text <> blank.
Second possible cause is that table TVROT (Route texts) contains an entry in login-language with route = blank and bezei <> blank.
If a work center was maintained in an operation within a production order and you wanted to execute an external processing for this operation, the created purchase requisition contained the account assignments cost center and order. However, only an account assignment is allowed here. As a result, the purchase requisition could not be used as a reference for a purchase order. In the attempt to convert the purchase requisition into a purchase order, the error message KI249 may occur.
Cause and prerequisitesCertain item categories (for example BOM components) should not be relevant for export. However, the billing document cannot be transferred to FI since the export data in the billing document is recognized as incomplete.
Cause and prerequisitesVF02
When copying a service contract with serial numbers to another service contract, the result will be update termination, if during this action the serial number list screen was accessed (without changes being made).
This can also occur when creating a sales order or service contract
with reference to a sales order.
The number of transferred serial numbers was not correctly determined.
Also, an entry was made twice in an internal table.
Transactions: VA01 , VA41 , DUPREC
Only in 2.2D (2.1J):
If after an ORA, EXP, or IMP error, the SAPDBA restart option is used, the message "Export/Import not successfully processed" appears after a successful import or export, and processing is terminated.
If the number of errors which occurred is very large (several hundreds or thousands) (for example if during the import the DB is accidentally shutdown -> error messages for each table), this error, that is the termination after the actual successful export or import, can also occur in versions 2.2D to 2.2G and 3.00 to 3.0B.
SAPDBA incorrectly interprets the error messages that were already already in the log file before the restart as being current.
SolutionSAPDBA, export, import, restart
Runtime error BCD_FIELD_OVERFLOW occurs in FB01 in program SAPLTAX1, if you worked with large amounts (99,999,999,999.99) and several of these lines were in the document and you, for example, first entered all debit lines and then all credit lines.
Cause and prerequisitesSome of the totals fields were only defined as normal amount fields, but the totaling meanwhile calculated greater values.
SolutionTaxes, SAPMF05A.
Message RW013, when order groups are settled to fixed assets.
Cause and prerequisitesProgram error
SolutionKO88, CJ88
If you append a long text to an activity of a WBS element and press F3, a popup is displayed whether you want to schedule although no changes relevant to scheduling were made.
Cause and prerequisitesIncorrect source code
SolutionProject planning board, time scheduling, project time scheduling, planning according to structure
CJ21, CJ23, CJ20, CJ27, CJ2A, CJ2B, CJ2C, CJ2D, activity text
You want to post subsequent debits/credits for a purchase order containing so many items that these items cannot all be displayed on one screen page of the order item selection screen. You enter a "subsequent debit" indicator on the initial screen as a default value for all items. Then you choose 'Select all' on the selection screen and enter unplanned delivery costs.
When you post the invoice, all lines as of a certain line are no longer characterized as subsequent debits/credits. As a result, the purchase order history in the respective order items is updated differently than required.
Program error.
SolutionMR01, MRHG, MRHR, TBTKZ
only AIX:
BRBACKUP or BRARCHIVE report the error BR278E with the subsequent AIX system message "dd: write error: Invalid argument"
The AIX operating system blocksize for tape drives is not 0.
SolutionBRBACKUP, BRARCHIVE, SAPDBA, SMIT, block size
During a goods receipt (backflushing) in repetitive manufacturing, the following error message is displayed if, according to the Customizing setting, the storage location for the goods receipt is to be created automatically: 'To storage location 0007 does not exist for material JS-F-01 in plant 0001'.
Message number RM102
Program error
SolutionTermination when saving the planning
Cause and prerequisitesTransport error. The error is corrected in 3.0A.
SolutionLong texts for operations of networks/orders and so on are not saved.
Cause and prerequisitesProgram error
SolutionLong text, operation text, component long text
During settlement, it is unclear what the processing type does in the initial screen of the settlement or what the settlement type does in the sender distribution rules. It is also unclear exactly when posted quantities are transferred to the receiver.
Other termsKO8G, KO88, CJ8G, CJ88, KOB5, CJ70, investment profile, AuC (asset under construction), PER, FUL, SLCSinfo
In general, you can differentiate between the settlement type in the sender settlement rule and the processing type selected for the settlement.
The quantity update occurs as follows:
Release 3.0/3.1:
Activity quantities (and sending cost center/activity type) are generally updated except during settlement on profitability segment. The actual activity price calculation, the elimination of internal business volume and variation calculation in Cost Center Accounting can be performed correctly.
The system updates primary cost elements if these are settled by cost element. If you post different units of measure under one cost type to the sender and the quantity on the order is therefore incomplete, the system does not settle the quantity.
Release 4.0/4.5 and subsequent releases:
Activity quantities (and sending cost center/activity type) are generally updated except during settlement on profitability segment. They are displayed in the CO document in both the total quantity entered field (MBGBTR) and the total quantity field (MEGBTR). The actual activity price calculation, the elimination of internal business volume and variation calculation in Cost Center Accounting can be performed correctly.
In the CO document, the system updates primary cost element quantities in the total quantity entered field (MBGBTR) if these are settled according to the cost element or if the settlement cost element has a unit of measure. Only if the settlement cost element has a unit of measure, the system also fills the field 'Total quantity' (MEGBTR) in the CO document and then fills the quantity in the CO totals record as well. If the sender was posted to using different units of measure under one cost element, and if the quantity on the sender is therefore incomplete, the system settles the incomplete quantity.
The following is valid for the quantity update:
Release 3.0/3.1:
The system updates only quantities for primary cost elements that are settled according to the cost element. There is no guarantee that the actual activity price determination, the elimination of internal business volume and the variation calculation will be performed correctly. If the sender was posted to with different units of measure under one cost element and the quantity on the order is therefore incomplete, there is no settlement. Therefore, we recommend that you do not use the settlement type FUL for receiver cost centers.
Release 4.0/4.5 and subsequent releases:
Activity quantities and primary cost element quantities are updated in the total quantity entered field (MBGBTR) in the CO document only if the cost elements for the activity allocation or the primary cost elements are settled according to the cost element or if the settlement cost element has a unit of measure. Only if the settlement cost element has a unit of measure, the system also fills the total quantity field (MEGBTR) in the CO document and then displays a quantity in the CO totals record.
For the settlement of activity quantities, the activity type that was originally performed is not updated on the receiver. Therefore, we recommend that you do not use the settlement type FUL for cost center receivers because the actual activity price determination, the elimination of internal business volume and the variation calculation also require the activity type information.
If the sender was posted to using different units of measure under one cost element, and if the quantity on the sender is therefore incomplete, the system settles the incomplete quantity.
When you try to display the change documents for a user for a specific period, the system sometimes does not display the complete data.
Cause and prerequisitesProgram error
SolutionSU01
The incompletion status is incorrectly determined if the first two positions of the client number equal the number of an existing incompleteness status profile. For example, client 030 and profile 03.
Cause and prerequisitesThe following error occurs when transporting output types in object export:
Transport object TEXT OCS,xxyyyy,STAM,z is processed
E ERROR: The object does not exist or is incorrect
When transporting output types, an attempt is made to transport standard texts for all mail message titles (entries in table TNATI)
SolutionIf you reach the depreciation area screen in the master data transactions, a popup is displayed to you in which you are offered to leave the data screen including the save option.
If you choose 'Save', the system does not perform a save but branches to the depreciation area screen.
Program error
SolutionAS01, AS02, saving popup, last screen, D190
When branching from FS10 -> FBL3 (Balances -> Line items), amounts in parallel local currencies are then not displayed currency-specifically if the number of places behind the decimal point is unequal 2.
When calling up FBL3 directly, the display is correct.
Error.
SolutionRFEPOS00 SAPMF42B T001A
In standard SOP (transaction MC76 or MC77), the quantity unit of the product group members cannot be converted with reference to the conversion factors in the material master record.
Message MA022 is displayed: 'Not possible to convert from & to & - & will be set'.
Program error
SolutionA condition which refers to a sales deal cannot be deleted when maintaining the sales deals so that the same condition can be maintained again. Only the deletion flag is set. The reference to the deal remains.
The reference to the deal can only be deleted using transaction VK11 in the additional SD data. Afterwards, the condition is also no longer displayed for the sales deals.
SAPMV13A, VB22, VK11
Help returns: No Help information is available
Cause and prerequisitesIf a structure was created on a Dictionary structure in ABAP with LIKE or INCLUDE STRUCTURE, and a field of this structure is used in the screen, the Help information from the derived dictionary field is not transferred.
This constellation occurs frequently in conjunction with STEP-LOOP or TABLE-CONTROL (LOOP AT ITAB).
On the other hand, the ABAP list processor is also able to produce the reference to the Dictionary for a field of this type for the Help ID.
If you perform a new check of the missing parts in the missing parts overview, the list is not changed regardless of the check result if it was empty because of the new check.
Cause and prerequisitesProgram error
SolutionAvailability check, production order
1. The remarks entered in transaction ME61 for each main criterion were not outputted on the evaluation sheet.
2. The standard layout set MELDRUCK can now be customized so that the user can store his own layout sets for each purchasing organization.
The confirmed quantity in the 'Online versus batch' mode of the availability check for sales orders is incorrect.
Cause and prerequisitesError in member LM61VF60
SolutionQuestion: For an invoice receipt in the GR/IR clearing item, why is the CO account assignment object (for example, the cost center or the order) set, and why is the consumption account additionally stored in the BSEG-SAKNR field?
Cause and prerequisitesTransaction MR01, MR11, MRHR, CO interface
For the report RFBIBL00, the customer-specific structure ZBSEG should be used. ZBSEG indeed does not exist in the Data Dictionary, but it cannot be created since a TADIR entry already exists.
Cause and prerequisitesDelivery of a TADIR- and a TDKZ entry
SolutionThe two values for the maximum and current delivery schedule on the scheduling screen of the purchase order, request for quotation and scheduling agreement are too large.
Cause and prerequisitesProgram error
SolutionME22, ME23, ME32, ME33, ME38
The end of the planning time fence does not only refer to the value defined in the material master. For existing predefined inputs whose date is after the end of the planning time fence, the planning time fence is set to the most distant date of input.
This is not described in the documentation for Release 2.2.
In the MRP list (MD05), with firming type '3' or '4', the end of the planning time fence is always set to the date of the last firmed receipt. This is then incorrect if the last firmed receipt lies before the end of the PTF from the material master record. If no firmed receipt is available, the end of the PTF was not displayed at all.
MD01, MD02, MD03, MD04, MD05, MD43, Planning time fence, Firming type
This allows the MRP controller, who dispatches the inputs during this process (manual planning), to protect planning as well outside of the planning time fence from the material master against automatic changes.
If, for example, a production order is dispatched outside of the planning time fence or firms planned orders, the automatic materials planning should 'accept' his planning up to this date.
If you do not want this function behaviour, you can switch it off using a modification (test and maintenance by customer). A modification proposal for Releases 3.0A - 3.0I is contained in the attachment.
If several delivery schedules are made for a contract, the contract number must be entered each time.
Cause and prerequisitesTransaction OPKP causes a termination.
A: Program "SAPL0C24": Source for screen "0190" is missing.
Delivery error
SolutionIf you transfer the scheduled dates into the basic dates or forecast dates during the project time scheduling, an online termination can occur if the WBS element has no scheduled dates.
Cause and prerequisitesIncorrect source code
Additional key words
CJ21, CJ23, time scheduling, project planning board, planning according to structure
The creation date during a planned order scheduling is determined incorrectly. The creation date is approximately one day after the order start date and the following error message is displayed: 'Dates are not entered in ascending order'.
Cause and prerequisitesThe planned order duration is 0.
SolutionCapacity leveling, capacity requirements planning
You can enter a reason for rejection using fast change in a sales order which has items with subitems. The reason for rejection is entered for all items in this case. If all the items are selected later on and the reason for rejection is cancelled again using fast change, you get message number V1512 "Item &: Please change the reason for rejection in the main item".
Cause and prerequisitesThe user enters a condition record (VK11 VK12) for a condition table that has material on the line level and receives an error when the unit of measure is not defaulted (for various reasons). The user then enters the correct unit of measure, BUT THE MATERIAL SHORT TEXT IS NOT DISPLAYED.
When the error message occurs, the field that the material text is stored in is cleared. Then, the material text is never read again because the program thinks it has previously been read.
If released sales orders are changed with VA02, they are blocked again from the credit view even though the change was not credit-relevant.
Cause and prerequisitesProgram error
SolutionVA02, Credit limit, High priority fields, Terms of payment
When transporting/importing/translating an operating concern, the program SAPLKXOB stops at a BREAK-POINT. The attempt to continue causes the dump SAPSQL_WHERE_ILLEGAL_VALUE.
The program refuses to transport data which could lead to inconsistencies in the target system. Every transport would cause inconsistencies due to an incorrect table entry in the delivery 30A. For this reason, every transport is refused.
Transactions: KE3I, KE3J, KETR.
When the user schedules a job that prints the logs for a costing run (with CK32), error message CK267 is issued because no logs yet exist. The user, however, wants to run the job as a follow-up job for selection, structure explosion or costing so that logs will exist when the print job is run.
The system checks whether logs exist at AT SELECTION-SCREEN.
This check, however, is not actually needed until START-OF-SELECTION.
When entering bank data (master record maintenance, posting to OTA) for countries with which the bank key is assigned internally (is numbered, T005-BNKEY = '3'), the error message F4211 appears.
Possible cause is a text element translated by mistake in program SAPLBANK:
Text element 001 must be called: 'INTERN' (in upper case) and not 'intern' or 'internal'.
T005 bank key SAPLBANK BNKA CHECK_BANK_ADDRESS
No collective orders are created during the collective conversion of planned orders.
Cause and prerequisitesProgram error
SolutionCollective order, planned collective order
A material has a bill of material. A sales document is created with this material with an item category so that the bill of material is not exploded. The item category is then later changed so that the bill of material is exploded. In this case, a delivery group is not set up, although this is provided for the new item category in Customizing.
Cause and prerequisitesProgram error
SolutionThe work items of a workflow have different languages. (Some of) the work items have a different language to the respective workflow.
All work items which were created due to asynchronous communication mechanisms in workflow are in the language that is entered for the user of the destination WORKFLOW_LOCAL, which was maintained in workflow Customizing.
All work items that were created due to an event have the language of the event.
Missed deadlines are in the language in which the background job SWWDHEX, which monitors the deadlines, was scheduled.
Work item, WIM
Changes to the address are not stored when you maintain addresses for organizational units in Customizing or when you maintain business or private addresses of customer contact persons.
If the addresses are on organizational units in Customizing, the note only applies if exactly the following symptom occurs:
If, from the overview of Customizing maintenance (for example, company codes or plants), you choose Edit -> Address (or, on the detail screen, you press "Address" or F17 "Address"), you reach the maintenance screen for addresses.
You make a change and save it (F11).
As of Release 3. 1I message SM813 is displayed: "Data inconsistency, address & in table SADRP. Change not possible".
If you branch to the address maintenance screen again, the changes no longer exist but instead the original status before the change.
The error can occur for the following Customizing objects:
Additionally in 2.2 and 3.0:
Additionally in 3.0:
A corresponding error can also occur in Transaction FSAP (company code-dependent reply addresses) since the same address maintenance module is used.
However, here the address maintenance is not called up via the maintenance of an organizational unit but from a separate transaction, which you can find in the Customizing tree under Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions -> Closing -> Count -> Balance Confirmation Correspondence -> "Define reply addresses for balance confirmation".
The note also applies, if business addresses or private addresses are changed by customer contact persons and the following phenomenon occurs:
This may, for example, occur when you maintain debtor contact persons (Transaction XD02).
Cause and prerequisites
Inconsistency in the central address table SADR generally caused by a transport.
The SADR-STDCOM field (type of communication, under the "Country" field) is empty or contains a value other than 'LET'.
The central function module also used for other address maintenance transactions expects a valid entry from table TSADC here.
If you use the maintenance dialog itself, this inconsistency does not occur; the entry 'LET' is always generated in this case.
This problem can occur up to Release 3.x; Release 4.0 uses a new function module for address maintenance in the Customizing.
Inconsistency between the address tables SADR and SADRP (the same address number is contained as a key in both tables). Also generally caused by a transport.
This has the same cause as in Case 1.
This problem can occur in the contact address maintenance up to Release 4.0B. As of release 4.5, the system uses a new function module.
//////////////////////////////////////////////////////////////////////
Caution: This note does not describe the error that two Customizing objects point to the same address number (see 'Related notes').
Solution
The inconsistency can be corrected as follows:
Example: The address for company code 4321 is specified in the T001-ADRNR field under the key T001-BUKRS = 4321.
You can display the contents of the respective table using Transaction SE16.
Further fields with address reference are:
Plants/branches T001W-ADRNR
Sales/purch.tax grps Address T007F-ADRNR (only 2.2 and 3.0)
Address tax office T007F-FAADR (2.2 and 3.0)
Personnel areas T500P-ADRNR (only 3.0)
Organizational unit: Transp.plan.points TTDS-ADRNR (only 3.0)
Organizational unit: Sales offices TVBUR-ADRNR
Organizational unit: Sales organiz. TVKO-ADRNR
Organizational unit: Shipping points TVST-ADRNR
Enter the value 'LET' in the "Communication type" field (SADR-STDCOM) in the maintenance screen that follows.
Fill any further required fields with useful values, if necessary.
Save the changes.
If the error message SM306 "Maintain table TSAVT" is output after you have entered the address number and chosen "Change", maintain the table TSAVT using Transaction SM31.
Include the following entry:
After saving the value with 'ENTER', the error message SM306 may no longer appear.
Upon completing Transaction SAD0, you can delete the entry from table TSAVT.
Change the number range interval ADRNR 01 as described in the OSS Note 25182 and then apply report RSADRNNR as described in the OSS Note 25182.
For this, you must use the latest version of report RSADRNNR as described in Note 25182 in order to consider the special inconsistency with message SM810/SM813.
This corrects the data inconsistency.
Additional explanation:
At the program position where error message SM810 is issued up to Release 3.1G, another error message ought to be issued.
The following modification is necessary for this:
Replace the message I810 in Include LSAD2U08 with the message I813. (approximately at line nnn).
Create the message SM813 with the text:
"Data inconsistency, address & in table SADRP. No change is possible"
This program correction is not absolutely necessary to correct the error since the misleading message SM810 does not normally appear, except for the described data inconsistency.
It is sufficent to correct the data inconsistency.
As of Release 3.1H this program correction is contained in the standard system.
If only individual addresses are concerned, proceed as described in the solution for error cause one.
If several or many SADR records in field SADR-STDCOM do not contain any entry, create report ZRSADR27846 in your system and transfer the source code from the attached correction instructions 117861. After executing the report, all SADR records in the field SADR-STDCOM receive an entry and address maintenance will be possible again.
In addition, Note 122916 describes a correction which results in an s message after successful storage.
Additional key words
FSAP, SM810, SM813, T5G52
BAS_OLD
No billing block is transferred to the delivery header for deliveries without order reference.
Cause and prerequisitesThe billing block is a feature of the payer which is not checked in the delivery.
SolutionWorkflow definition: Although a container element with an addressee was entered in the step definition for the missed deadline or the processing end, the addressee in not informed when carrying out the workflow. That is, the specification of the container element is ignored in these cases.
Cause and prerequisitesProgram error in the function modules
Swp_create_ei_for_receptorstep and swp_create_wi_for_step.
Notification agent, deadline agent, agent via container element.
When updating key figures the 'CALL_FUNCTION_CONFLICT_TYPE' ABAP/4 runtime error occurs.
Termination occurs in the 'PERIODE_ERMITTELN' routine of ABAP/4 program RMCS1000.
This is caused by a missing check for update definition. In the update rules, a date field is specified by means of which the period is determined in which the key figure is to be updated.
When you specify this date field, a check is not run to see if it is in fact a date field. If a field with another category (value field, quantity field ..) is entered here, the above termination occurs during updating.
Update, date field, SIS, LIS
The routing scheduling calculates another in-house production time for forward scheduling than for backward scheduling.
Cause and prerequisitesThe in-house production time is always calculated as for forward scheduling even for backward scheduling. This could lead to miscalculations when you are using different operating times.
SolutionThe display of the contract conditions is not sorted according to the entry but according to condition type. RA01, for example, is printed after RA00 although RA01 was entered first.
Cause and prerequisitesIncorrect sorting.
SolutionPrint SAPLMEKO
An abnormal termination occurs in function module 'READ_MDFA_FOR_SO', if a search is run for more than 254 run schedule headers on production orders.
A 'SELECT' statement is executed with a 'RANGES' table containing more than 254 records. This is translated for the Oracle database into a 'SELECT' statement with more than 254 conditions.
Every database system can process only a certain number of conditions; if this number is exceeded, abnormal termination occurs.
In the spool, you can give spool requests a priority which is then passed on to the generated output requests.
Where does this have its effect?
- Inforamtion -
SolutionSP01, TSP01, TSP02, rspo/host_spool/print
Key word: INF DBACCESS
The status query of a table with 'dbaccess -> table -> info -> status' does not return all values.
The query 'Commit/Rollback?' appears when leaving the menu
The selected table or the Informix Dictionary are blocked by another transaction.
SolutionIn the purchase requisition list displays ME5A, ME55, various data changed on detail screen. However this data was not updated.
Cause and prerequisitesThe fields on the detail screen were ready to accept input although no changes to the requisition data should be possible on the list displays.
If you enter a new period for the time-dependent data of asset master data which is one day only, error message AA232 is displayed: 'FROM date earlier than TO date (Please correct).
Cause and prerequisitesProgram error
SolutionAS02, AS92, master data, SAPLAIPS, ANLZ, history, period under consideration
Changes to data medium exchange with banks in the UK for Release 3.0
Cause and prerequisitesRelease 2.2* Status:
Release 3.0* Status:
Note
The refence number specified in the DTA management always comprises complete payment document numbers of a BACS data carrier. If debit memos or credit memos are processed within a file, or if payments to several execution days are combined, then several CONTRA master records are created. The account statement always relates to the reference number ('SAPBACS...') specified in the CONTRA record.
Additional key words
Account statement, BTCI, DME administration, RFFODTA1, BACS, Telepay, RFFOGB_T, RFEBGB00, RFEBGB20, FDTA
The input data concerning the change status from the initial screen of transaction CA01 are no longer available if the message CP115 (the material has the material status &) is issued as an information
message.
engineering change management
The following message appears when calling up the transaction 'ST11':
C_DIR_READ_NEXT SUBRC 3
And the list layout is affected.
The following message appears when you press [Refresh]:
3 <- CALL C_DIR_READ_NEXT(,infupdstat.log,..)
or another file name. The file named has a length of more than 10 MB.
Only 9 characters were provided for intermediate storage of the file name.
This can also affect unchosen files in a scanned directory. Reason: depending on the search pattern, large parts of the directory may have to be scanned.
ST11 RSTR0006 ST01 RSTRAC24
Although an alternative ordering address is specified in the purchasing document (under Owner -> Partner) (in the contract it is an alternative contract address), the address of the vendor (EKKO-LIFNR) is printed.
Cause and prerequisitesPossible causes:
ME90
If the presentation graphics are started from a query, the places after the decimal point are not taken into account. As a result, the values in teh graphic are displayed incorrectly scaled.
Cause and prerequisitesError in the function module GRAPH_MATRIX_2D, together with the call from the query.
SolutionWhen you display the asset master data, the pushbutton for simulating the fiscal year change for insurance data is deactivated.
When you create a fixed asset, the function is unnecessarily activated.
Program error
SolutionAS01, master data, AS93, AS92
Fast data entry PA71. Creating infotype 2006 with option "create batch input". When the user processes batch input the error message E347 "fields P2006 enduz cannot be filled" occurs. Without batch input everything works fine.
Cause and prerequisitesProgram error
SolutionThe error is corrected in Release 3.0B. You can implement the following temporary workaround:
MP200000 screen 2250
You are using access method L to print from within the SAP system on a remote printer in UNIX. This printer sends the print request to another host spooler.
Some spoolers (for example Novell) attach an empty page to every SAP printout.
SAP pads the last page of every printout with blank lines in order to output the last page from the printer. This works for most spoolers, but some still generate another form feed at the end, resulting in an additional empty page.
When you execute a report in a client > 0 dump DBIF_SETG_INVALID_CURSOR occurs.
Cause and prerequisitesThis report can be executed in SAP client 0.
You have imported this report from SAP client 0 into your customer client by means of the import function provided by the application.
For some operating systems, the import of reports does not work correctly. For this reason, it is possible that not all report data is read during the import.
CO-PA, EC-BPC, PS
The CVS table (cumulative variable balances) in cluster B2 contains incorrect cumulations.
Cause and prerequisitesProgram error
SolutionRPCLSTB2, RPTGET00, CVS, OCVS, VS, OVS, B2, cluster
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
VF01 VF02 VF04
Cause and prerequisitesProgram error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
VF01 VF02 VF04
Cause and prerequisitesProgram error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
VF01 VF02 VF04
Cause and prerequisitesProgram error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
VF01 VF02 VF04
Cause and prerequisitesProgram error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
VF01 VF02 VF04
Cause and prerequisitesProgram error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
The correct accounts are not determined by the function 'Release for accounting' in the billing document.
The account determination analysis shows that the incorrect condition type - KOFK instead of KOFI and vice versa - is determined in the account determination.
Customizing is, however, set correctly. That is, the condition type KOFI has condition '3' (without CO account assignment) and KOFK has condition '2' (with CO account assignment) in account determination procedure KOFI00.
Program error
The first item of the billing document is taken and determines whether it is an assigned transaction (-> condition type KOFK) or not (-> KOFI). The following items are then incorrectly determined with the account assignment type of the first item.
VF01 VF02 VF04
If you enter a document with data for fixed asset retirement and this document is then held, all data for fixed asset retirement disappears.
Cause and prerequisitesIt is not programmed that this data on fixed asset retirement is buffered.
SolutionHold document; FB11
Requested correspondences are not stored during a purely clearing transaction.
Cause and prerequisitesProgram error
SolutionSAPF140
CRN036 New Mode of Transportation required. We need another Mode of transportation for Intank Book Transfers. The logic would be similar to the pipeline. This is a business requirement for excise taxes. Based on the mode of transportation, certain taxes apply, therefore, when we sell "Book Transfers" we need to identify each movement. This is everyday industry practice.
If for incoming payments a payment with a reason code is posted by means of the On account field on the OI screen or separately posted manually, no reason code-dependent payment notice is generated in spite of the respective configuration settings.
Instead, the default correspondence is created.
Program error
SolutionRFKORD00, SAPF140
The payment notice for a follow-on document of a payment has the payment amount 0.
Cause and prerequisitesProgram error
SolutionRFKORD00
The selection "Balance in local currency" does not work correctly for the account statement and for the customer statement.
Cause and prerequisitesProgram error
SolutionRFKORD10, RFKORD11
You change a GR item when reprocessing incorrect goods movements by entering the storage location, for example. When you save the goods movement, an update termination occurs in function module MB_CHANGE_RESERVATION_WA. The error message in the dump is as follows: "Please check table RESB: Entry 0000000000 0001 does not exist".
Cause and prerequisitesAfter a change, function module MD_BEARBEITEN_KOMPONENTEN returns field RSPOS with value 1 for BOM items for which RSPOS is initial. However, GR items may not have RSPOS because then they are interpreted as a GI component.
SolutionIf you referenced a reference operation set from the last operation of a routing, the referenced operations were not numbered according to the predefined interval.
Cause and prerequisitesrefer_to reference_operation_set
If you call the function 'Graphic -> Gantt chart' in the PM order, an error occurs in the flow control: SAPLCOIH, AOBG, GR,* ,*.
Cause and prerequisitesTransport errors
SolutionIW31, IW32, IW38, flow control, SAPLCOIH, AOBG
If you call the function 'Graphic -> Network structure' in the PM order, an error occurs in the flow control: SAPLCOIH, GRBP, GR,* ,*.
Cause and prerequisitesTransport errors
SolutionIW31, IW32, IW38, flow control, SAPLCOIH, GRBP
How do you do a database backup of
a) an individual client
b) an individual development class
Only one part of the system data is important, and must be saved.
SAPF100 can only run once on each system. If a second job is to be started parallel to the first one, you get error message FR369 'A valuation is already running in &'.
The customer wants to/must be able to start several runs at the same time.
The system was designed so that only one SAPF100 can run for each system.
SolutionWhen you create a task list for functional locations, error message CV711 is displayed: 'Object ROUTING_T number range 01 does not exist'.
Cause and prerequisitesThere are no number ranges defined in Customizing for the functional location.
SolutionIf you maintained a maintenance strategy including maintenance packages in the task list, you cannot create relationships or, the other way around, if you first maintained the relationships, you cannot allocate a maintenance strategy to the task list.
Cause and prerequisitesA parallel maintenance of maintenance packages and relationships for operations of the very same task list is no longer permitted.
Reason:
When you schedule a preventive maintenance plan, orders are generated automatically. The order operations are determined automatically because of the maintenance packages allocated to the operation in the task list.
If relationships were allowed between operations, the system would have to determine the relationships to be taken over into the order automatically based on the operations taken over. Unlike the material or PRT, however, the relationships are not directly allocated to the operation, but describe the dependency of two operations concerning procedure and time separately.
The only useful solution for such an automatic function would be not to take over the respective incoming and outgoing relationships for all operations that are not taken over.
However, an order with relationships which are determined that way leads to a result during scheduling which cannot be interpreted usefully.
IA01, IA02, IA05, IA06, IA11, IA12
If line items were entered for one-time accounts and this one-time data was not entered in the last line of the document, the bank data was not stored. "INTERN1" was displayed in the bank key during the internal number assignment of the bank keys.
Cause and prerequisitesProgram error
SolutionPreliminary posting, FBV1, FBV2
Workflow 3.0: When execution a workflow, work items for the steps are sometimes created twice after a parallel section.
Example: FIPP pattern workflow WS10000051, step 136 'Change document', after the join node 20/25.
Program error in the FORM routine cancel_wis_between_2_nodes in the program LSWP1F02 (function group SWP1):
The problem can occur after a parallel section if all parallel branches for ending the section do not need to be processed to end the parallel section (a so-called "n of m" join) and the parallel section is in a loop. In the second and any following passes of the loop, several work items can be created for the next task after ther joining. The cause is that the corresponding counter is not reset to zero for the terminated parallel branches when Workflow exits the parallel section.
When you process the posting session, or when you are in the log, you see that incorrect document numbers were assigned. The document number assignment generally does not start with the directly preceding posting run but with the posting run from the previous year.
When you process the session, you receive error message
F5152 Document number & & & was already assigned.
At least one posting run terminated (TABA-XBUKZ = 0 or 1) or, in at least one posting run, no documents were created (TABA-XBUKZ = N).
SolutionRABUCH00, RABUCH, TABA, RABUCH20
When using the scrolling function in the log entry of export control, a dump occurs with the error message 'ASSIGN_NEGATIVE_LENGTH'.
Cause and prerequisitesThe text item Z04 in reports RVEXSIAU and RVEXPROT is not translated.
SolutionExport control
Export
- RVEXSIAU
- RVEXPROT
- RVEXAUAU
Conditions and information structures cannot be transported, for example because the user does not have the authorization to change a correction. The system does not display a correct message, but instead issues the invalid message number E000.
Cause and prerequisitesThis is due to an error in Include LMCSCU01.
SolutionV/57, V/58
When you create an ISH customer (business partner - customer or patient), a FI transaction screen is displayed when you save and all the predefined FI data has disappeared.
Mostly, one of the two following error messages appear:
Business partner, customer, patient, self-payer
Field or screen has been hidden or set as a display field via FI Customizing.
In table TN02Q, either default values for the corresponding field have been defined or patient or customer master data should be transferred to FI.
Unsupported screens of Financial Accounting were displayed.
Check whether the following screens are active and the named fields are not hidden:
Customizing -> Financial Accounting -> Accounts Receivable and Accounts Payable -> Customer Accounts -> Master records -> Preparations for Creating Customer Master Records ->
-> Define account groups with screen layout (customers)
-> Define screen layout per company code (customers)
-> Define screen layout per activity (customers)
For the field or screen in question, check per activity (create, change), for the company code and the account group whether the field has indeed been hidden or set as a display field.
If all fields have been hidden on a screen, the entire screen is no longer visible in the screen sequence in Transaction FD01 or FD02.
Based on the possible customizing possibilities, you can only examine the screen list by executing Transaction FD01 to create the customer and Transaction FD02 online to change the customer.
After each screen change you have to determine the respective screen (program and screen number) via 'System -> Status'.
Program involved: SAPMF02D.
The following screens of Financial Accounting are part of the run and should be active:
Program: SAPMF02D
0105 - Create customer
0106 - Change customer
0110, 0111, 0120, 0125, 0130, 0210, 0215, 0220, 1221, 0230, 610.
Program: SAPLBANK
0100
Program: SAPLSZA6 (Central Address Management)
0200, 0500
The following fields should be active when data is transferred to FI:
0105 - Create customer:
RF02D-KUNNR RF02D-BUKRS RF02D-KTOKD RF02D-REF_KUNNR RF02D-REF_BUKRS
0106 - Change customer:
RF02D-KUNNR RF02D-BUKRS RF02D-D0110 RF02D-D0130 RF02D-D0210 RF02D-D0215
RF02D-D0220
0110:
KNA1-NAME1 KNA1-NAME2 KNA1-NAME3 KNA1-NAME4 KNA1-SORTL KNA1-STRAS
KNA1-ORT01 KNA1-ORT02 KNA1-PSTLZ KNA1-PFACH KNA1-PSTL2
KNA1-LAND1 KNA1-SPRAS KNA1-TELF1 KNA1-TELFX KNA1-TELX1
KNA1-ANRED KNA1-PFORT
0120:
KNA1-BEGRU KNA1-BRSCH KNA1-STCD1 KNA1-STCD2
0125:
-------
0130:
KNBK-BANKS KNBK-BANKL KNBK-BANKN KNBK-XEZER KNBK-BKONT KNBK-BVTYP
KNBK-BKREF KNBK-KOINH
KNA1-KNRZA KNA1-XZEMP
0210:
KNB1-AKONT KNB1-ZUAWA KNB1-BEGRU KNB1-FDGRV KNB1-ALTKN
KNB1-VZSKZ KNB1-ZINDT KNB1-ZINRT
0215:
KNB1-ZTERM KNB1-HBKID KNB1-ZWELS KNB1-TOGRU KNB1-ZAHLS
KNB1-XZVER
0220:
KNB5-MAHNA KNB5-BUSAB KNB1-BUSAB KNB1-MGRUP KNB1-ZSABE KNB1-XAUSZ
1221:
KNB5-MABER KNB5-MAHNA KNB5-BUSAB
0230:
------
SAPLBANK 0100
BNKA-BANKA BNKA-PROVZ BNKA-STRAS BNKA-ORT01 BNKA-SWIFT BNKA-BGRUP
BNKA-XPGRO
SAPLSPO1 0300