SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
ME61/ME63/RM06LBAT:
------------------
When determining the score for the criterion price history, the prices of the previous year were not converted into the price unit of the prices of the current{latest year. This resulted in an incorrect market change. This in turn resulted in an incorrect score determination for this criterion.
Although table T166C classifies the fields of table EKES as non-print- relevant, change-IDOCs are nevertheless generated for PO changes.
Cause and prerequisitesProgram error.
SolutionEDI
Message: Line item commitment has very bad runtimes
Cause and prerequisitesThe Select was previously called with an object number table. The Select optimizer of the database, therefore, does not work.
The Select is now relocated for each object.
During line item reporting (actual and commitment) for projects, a significant potentiality is available for improved performance in Release 2.2A - 2.2G. See Note 32181.
Programs: SAPMK21O
Transactions: KSB2, KOB2, CJ76
The purchase requisition is not deleted upon technical completion.
This is caused by a program error.
SolutionPurchase requisition, TECO, technical completion, IW32
ADDITIONAL-DESCRIPTORS
Deletion flag, DLT
Capacity requirements splits: Standard values of the splits and therefore also the requirements are zero if splits were created. Error occurs if the split were deleted and should then be created again subsequently in the same transaction.
Cause and prerequisitesCapacity leveling, resource planning
A user is processing a transaction and chooses one of the functions, System -> User defaults, System -> Services or System -> Utilities
A new transaction is started and the old one is terminated without warning.
This was implemented this way, as the ideal technical preconditions were missing up to now.
SolutionReleasing blocked invoices: The list generated by the system can be displayed in various ways. The display variants are defined in Customizing; the display variants delivered in the standard system cannot be changed there.
Sometimes the standard display variants contain formating errors.
Wrong entries in tables T180S and T180U
SolutionMR02 Release header MRO2 List variant
For schedule lines that are not relevant to requirements but that check availability, a requirement is set up when you set a requirement relevant delivery block.
Schedule line without requirement relevance but with availability check.
Requirement relevant delivery block.
Sales order type without delivery and transportation scheduling.
Project earned value analysis
If the milestone method is used for the last object (WBS element, activity or activity element) of the selected structure, these milestones are not taken into consideration when the percentage of completion is calculated. This however only affects the milestones for the last object.
Program error
SolutionTransaction CNE5
The following two errors occurred during the adoption of a text from the vendor master record as a header text in a PO (true adoption, i.e. with status ' '):
Program error.
ME21 ME22 ME23.
Drill-down reporting: for example, transaction KE30, function breakdown change, breakdown...
The dialog box has a scroll bar, which leads the user to believe that further characteristics exist. However, when you scroll down you only find the line: Page 0 of 0.
KCR0
Only affects ledgers in which alternate accounts are stored (not the 00 G/L ledger).
When posting to a prior fiscal year, a balance is automatically carried forward to the current fiscal year. Under some circumstances, the balances carried forward are not found in the expected account.
Cause: Balance sheet accounts are carried forward to a carry-forward account, and profit and loss accounts are carried forward to themselves instead of to a carry-forward account.
Cause:
The analysis which determines whether a balance sheet or profit and loss account is involved is not carried out correctly. Therefore a balance sheet account could be interpreted as a profit and loss account,or vice versa.
Within the program, the classification of the original account (XBILK) is passed on in BSEG. Interpretation of the alternate account is based on this indicator.
Prerequisite: The alternate account must have a different account classification (SKA1-XBILK) than the operative (company code) account, for example, account 400000 is a balance sheet account in the operative chart of accounts, and a profit and loss account in the alternate chart of accounts.
Customers should check whether they actually want this master data specification, and correct it where applicable.
Balance carried forward, SAPFGVTR, RGVTRnnn, alternate accounts
If a line-item report is displayed via KE24, an overview list of the line items is displayed.
However, if the user branches into the detailed display using a double-click, then the system hangs with the hourglass.
Checking in SM50 shows that the system is performing a range scan on CE1.
Program error.
SolutionThe amount from the previous check is output on a check instead of the correct amount in words.
The error log contains the message that an entry in table T015Z is missing (error message F0277).
On the one hand, an entry can actually be missing for converting the numbers into words in system table T015Z. You should then analyze whether this error is a delivery error on the part of SAP or whether it is a table maintenance error on the part of the customer.
On the other hand, a language can be entered in a vendor master for which a conversion into words is not maintained (for example due to a typing error in the language). The language is to be corrected here in the master record.
RFFOD__S, RFFOUS_C, RFFOD__W, RFFOD__T, RFFOAT_L
Change documents causes an update termination in VK11 / VK12, etc.
In Transaction SM13, one can see the error message:
"The number range interval is not available"
Program error
Change document, condition
Transactions: VK11, VK12
Purchase requisitions can be created from material requirements planning for transfer posting a material of unrestricted-use stock of one plant to the special stock E (sales order stock) of another plant. However, transfer posting is not supported in inventory management.
Cause and prerequisitesThis function was not yet supported.
SolutionVL02, MB1B, MB01, BWA351, BWA641, BWA101
The requirement is that if a Backdated change is put into a wage type
that affects arrestable pay, the positive or negative amount should be rolled forward to the current open payroll period and be included in arrestable pay for that period. That way any arrears can be recovered, and for the salary band types the employee pays the extra in the period
that they receive the extra money, or conversely they pay less in the period that total pay is reduced. Like all deductions court orders should never be recalculated retro-actively.
Scrolling to the next and at the same time last page is sometimes (see below) not possible in different transactions of Asset Accounting. In particular, a display of the last entry is not possible.
Cause and prerequisitesThe last entry is the only entry on the next page to be displayed.
SolutionF23 TABLE_SCROLL
If a component for sales order stock is allocated in a network with allocation to sales order item and WBS elemement, item category 'E', instead of item category 'D' is set in the reservation/purchase requisition. This can cause subsequent errors in purchasing or in materials planning/inventory management.
Cause and prerequisitesMessage: Line items are missing if you return to the initial screen by pressing F3 and then access the transaction again.
Program error
Preconditions:
You use F3 to return to the initial screen from the list.
Call the transaction again or install the following repair.
Additional key words
Programs: SAPMK21A, SAPMK21O
It is no longer possible to enter sequence keys in transaction 'OP84'.
Cause and prerequisitesThe screen sequence control of the detail screens is no longer required, now that a number of detail screens have been converted to one large screen in the routing.
SolutionDespite the setting "any operation sequence for confirmations" in the confirmation parameters (transaction OPK4 field MRFLG), when you try to confirm a production order not in accordance with the operation sequence, error message RU024 is displayed.
Cause and prerequisitesThe milestone indicator is set for one of the control keys of the production order (can be set in Customizing OPJ8).
SolutionOperation, sequence, confirmation, CO11, milestone
The error message VD346 appears when you create a sales order with date type P (period):
VD346 "Period indicator 4 is not defined".
However, table TPRG contains an entry with language D, Deliv.date P, date type 4. This means that date type P is proposed as a possible entry by means of F4.
Date type 4 (period indicator P) is not defined. This is hard checked during the date conversion.
SolutionVA01, VA02, PERIOD_AND_DATE_CONVERT_INPUT, LVDATU01
The upgrade appears to hang in the phase CON
On the system tables systables, sysindexes and syscolumns, no 'Update statistics' was carried out.
SolutionFORMINF, performance, upgrade, update
Message: After a release upgrade, the headings and their column break characters do not fit the columns with the values.
It can happen that the column break character separates a heading such as Cost element in the form Cos|element.
Cause: The generated program code does not fit the definition in Customizing.
Preconditions:
Release upgrade or a client was copied
Programs: SAPMK21A, SAPMK21O, SAPMK21V, SAPMK21T
Transactions: KSB1, KSB2, KOB1, KOB2, CJ74, CJ76.
There are correctly configured process orders with phases and capacity requirements. You can find them in the capacity evaluation, but not in the planning table (neither in the tabular nor in the graphical one).
You are using the standard profile within the Capacity Leveling menu (transaction CMC0) and select the following function:
Capacity_Leveling->Resource_View->Plan._Table_(graph.) transaction CM29 or
Capacity_Leveling->Resource_View->Plan._Table_(table) transaction CM35
You are working in a customer client (e.g. <> client 000).
You have created a new client with client copy.
CM29 or CM35
ADDITIONAL-DESCRIPTORS
Update termination when saving network in update module NW_VB_MST_POST after changing milestone.
Affected transactions: CN22, CJ27
The error only occurs if the affected milestone was originally created without a short text and was then maintained when you made changes.
SolutionSAPSQL_ARRAY_INSERT_DUPREC
Error message: GA727 "Sender base in period & is 0; therefore, no
allocation is possible"
Description: For tracing factors for variable portions, the
allocation bases are stored with value 0 if a master data
validation must be performed for the allocation bases
according to table T800D (=fields for master data
validation).
Transactions: KSU5, KSUB, KSW5, KSWB, KSC5, KSCB, KEU5, GA15, GA35,
GA2B, GA4B
Program name: SAPMKGAL, ALxxyyyR
Program error when importing the data records
SolutionAllocation
The RFSBWA00 program always allocates accounts that are allocated to different items with debits/credits according to the year-end balance, independently of the period selection used at the beginning of the program.
Cause and prerequisitesIs programmed to do this. The reason is the option to interactively change the displayed periods in the program. The selection at the start of the program is then only the restriction for the displayed period. The allocation is always carried out according to the total balance.
SolutionRFSBWA00, F.54, structured list of account balances
As of Release 3.0, the short text (short description) for items with material can be changed in the following purchasing documents:
RFQ, purchase order, contract and scheduling agreement.
The changed short texts are also adopted in follow-on documents (e.g. contract text is adopted in the release order).
Restrictions:
As of Release 3.0F, it is possible to decide by field selection whether the short text of the material as described above can be changed or not.
Cause and prerequisitesMaterial short text.
When extending the material number to more than 32 characters, all characters after the 32nd are truncated after selecting a matchcode value using F4 help when resetting the values on the screen.
Cause and prerequisitesThe screen processor checks whether the information on the length of the value is available. If not, the value is limited to 32 characters.
SolutionF4, matchcode help, material number, reset values, Double byte