16.6.11

SAP Note 26179 - PSP,Netzpl. 3.0 A: Abrechnungsempfänger PSP-Element

Symptom:

Dieser Hinweis betrifft nur Rel. 3.0 A !

In den Abrechnungsvorschriften zu Projektdefinition, PSP-Element, Netzplan oder Netzplanvorgang ist als Empfänger ein ungültiges PSP-Element eingetragen. Mögliche Folgen:

  • In der Aufteilungsregel wird ein falsches PSP-Element angezeigt.
  • Programmfehler bei der Abrechnung (Transaktion CJ88).

In Tabelle COBRB sind Sätze sind Sätze zu finden mit Nummern wie 99999... im Feld COBRB-PS_PSP_PNR.

Weitere Begriffe
Ursache und Voraussetzungen

Programmfehler

Lösung
Korrektur

SAP Note 26178 - Line item commitments: wrong document display/master data

Symptom:

Possible Messages:
The function "Document" calls up the wrong document: e.g., the first document is always displayed.
The function "Master data" displays the wrong master data records for projects and WBS elements.
The function "Find" terminates with error A499 after placing the cursor on a document field and initiating the "Find."

Cause and prerequisites

Program error.

Prerequisites:
for 1: The list must have been resorted.
for 2+3: The error always occurs.

Solution
See the repair below.

Additional key words

Program: SAPMK21O, SAPMK21V
Transactions: KSB2, KOB2, CJ76, KOB3

SAP Note 26176 - PPPR: Material withdrawal / quantity units

Symptom:

The quantities in the pick list (PPPRMBRL, PPPR_PICK-LIST) or in the goods issue slip (PPPRWARS, PPPR_GOOD-ISS_SL) are to be output in issue quantity units.

Cause and prerequisites

Only the quantity in the base unit of measure is printed.

Solution

You have to modify the form:

  • Copy the print report and the corresponding form.
  • In the form, substitute the variables as required:
    &RESBD-BDMNG& with &RESBD-MENGE&
    and &RESBD-MEINS& with &RESBD-EINHEIT&

SAP Note 26174 - rslgsend(60)(..): Assertion failed

Symptom:

The transmission process for the central syslog cancelled with the following error message:

Stderr: rslgsend (60)(6987): assertion failed
rslgsend (60)(6987):condition_should_be_true
Syslog:
Program rslgsmc: Guarantee 060 not fulfilled

Cause and prerequisites

The reason for cancellation is an internal error message when writing a status file. Occasionally, the program writes the current status of the file pointers to this status file, to increase speed during a later restart.
The file can be found in the profile parameter 'rslg/send_daemon/status_file' and is called /usr/sap/C11/DVEBMGS00/data/rslgssta or similar
+++ +++++++++
| +-- instance name
+-- system name

The time at which this file is written to is almost impossible to predict because it depends on how long the program has already been running and on how many SysLog entries it has sent.

Solution
Check that the file could have been written to: Directory is available, space on hard disk (only 100 bytes), ..

Restart the SysLog transmission program again (manually if necessary). If you do not know the parameters, wait until the next restart of R/3. The SysLog transmission program is then started and will add everything.

Additional key words

SysLog E06

SAP Note 26172 - AW01 monthly development always only up to period 12

Symptom:

When displaying the monthly development of the book values in the display of the asset values with AW01, always only the development up to period 12 is displayed even if a fiscal year variant with more than 12 periods is used.

Cause and prerequisites

Program error.

Solution
Advance correction in module MA03WF01. Syntax check is possible only in main program SAPMA03W.

Additional key words

Depreciation posting SAPMA03W

SAP Note 26171 - Possible entry values for command field ("OK-code")

Symptom:

Which entry options do I have in the command field (sometimes also called "OK code")?

Reason and Prerequisites

Documentation on this is scattered.

Solution

The design of the R/3 system is such that all programs can be called using menu options. In addition to ergonomic advantages (no need to learn transaction codes), this procedure offers greater security, as the menu path informs the user of the work area to which a program belongs.

Use of the command field should therefore be limited to exceptions. In particular, there is no guarantee that the function of the command field is fully supported.

Entry options are listed below. These are only meant for experts (system administrators). Some of them (for example, "/nex") may also be dangerous since they override safety measures.
"Normal" users should avoid using the command field at all. It is often easier to call a known transaction with "/nxxxx", but this can be achieved just as simply using a user menu.

Direct call of transactions, session handling:
  • /nxxxx
    • This terminates the current transaction, and call transaction "xxxx", for example, "sa38" for reporting.
  • /n
    • This terminates the transaction. This generally corresponds to going back with F15.
  • /nend
    • This terminates all separate sessions and logs off (corresponds to "System -> Log off").
  • /nex
    • This terminates all separate sessions and logs off immediately (without any warning).
  • /oxxxx
    • This opens a new session and starts transaction xxxx in this session.
  • /o
    • This lists existing sessions and allows deletion or opening of a new session.
  • /i
    • This terminates the current session (corresponds to "System -> End session").
  • /i1 , /i2 ,...
    • This terminates the session with the specified number.
  • .xyzw
    • "Fast path": "xyzw" refers to the underlined letters in the menus. This type of navigation is uncommon and is provided more for emergencies (such as a defective mouse).
Background input:

The following commands can be entered in correction mode ("Process in foreground" or "Display errors only") when processing a background input session:

  • /n
    • This terminates the current background input transaction and characterizes it as "Failed".
  • /bdel
    • This deletes the current background input transaction.
  • /bend
    • This terminates background input processing and sets the session to "Failed".
  • /bda
    • This switches from "Display errors only" to "Process in foreground".
  • /bde
    • This switches from "Process in foreground" to "Display errors only".
ABAP/4 debugging:
  • /h
    • This switches into debugging mode.
  • /hs
    • This switches into debugging mode and activates the debugging of system functions.
Buffer commands:

WARNING: Resetting buffers can significantly impact on the performance of the entire system for a long time. It should therefore be executed only in well-founded cases. As of Release 3.0B, system administator authorization is required (authorization object S_ADMI_FCD). The action is noted in the system log.

  • /$SYNC
    • This resets all buffers of the application server.
  • /$CUA
    • This resets the CUA buffers of the application server.
  • /$TAB
    • This resets the table buffers of the application server.
  • /$NAM
    • This resets the nametab buffers of the application server.
  • /$DYN
    • This resets the screen buffers of the application server.
Out-of-date commands:
  • Pxxx
    • From the menu system:
      Calls transaction Pxxx.
    • If an ABAP list is displayed:
      Send command Pxxx to the list processor (for example, P+, P--, PRI, and so on)
    • From a transaction screen:
      Send command Pxxx to this transaction
  • xyyy (where x is not 'P', '/', '=' or '.') )
    • From the menu system:
      Calls transaction xyyy
    • Within a transaction:
      Send command xyyy to this transaction
  • /*xxxx
    • Calls transaction xxxx and branches to the next screen. So, it has the same effect as /nxxxx followed by ENTER.
  • =xxxx
    • This entry is still possible for compatibility reasons, but is no longer supported.
  • %sc
    • Searches for a string in lists (like "System -> List -> Find String")
  • %pc
    • Downloads lists
  • %pri
    • Prints lists
  • ?STAT
Displays the status dialog (such as "System -> Status...) )

SAP Note 26168 - Loop when maintaining the investment support areas

Symptom:

When the maintenance transaction is called for the investment support areas, the program loops under certain conditions.

Cause and prerequisites

There are two causes for this:

  • In the chart of depreciation of the customer, no pure investment support areas are defined.
  • For the chart of depreciation of the customer, an incorrect source chart of depreciation is specified. This is taken as a reference and then results in the program error.
Solution
Check the source chart of depreciation of your chart of depreciation using transaction SE16.
You can correct the source chart of depreciation using transaction SM31:
Procedure:
--> Call transaction SM31 --> Enter Table T096 -->
Function 'Maintain' --> after the note:

"Table T096

Maintenance is done through a
CUSTOMIZING function.

Please press ENTER.
---> please enter 'MAST' in the OK-CODE field and press 'ENTER'.
You then reach the SM31 maintenance of the table T096 and can then
correct the source chart of depreciation for your chart of depreciation.

Example of SM31 (last column is the source chart of depreciation).
CofDp a CofDp
--------------
1AT X 0AT for Austria
1BE X 0BE Belgium
1CH X 0CH Switzerland
1DE X 0DE Germany
1ES X 0ES Spain
1FR X 0FR France
1GB X 0GB England
1US X 0US U.S.A.
...

--> you confirm the data change by pressing ENTER.

Additional key words

SAPMA04C investment support termination AFAPLO T096 OIA1

SAP Note 26166 - F5241 No check information for cleared down payment

Symptom:

If a check was issued and entered in the check register for a down
payment or payment on account, and then this payment document is cleared by an invoice, you get the F5421 error message (no check information found) if you access the document display via Environment -> Display check.

Cause and prerequisites

A search in the check register was only made with the clearing document. However, in the aforementioned case, the clearing document is the invoice.

Solution
This error has been corrected for Release 3.0B. Prior to that release,
transaction FCH2 (Check display for payment document) can be of help, or you can install the following advance coding correction.

Additional key words

FBA7, FCH5, F-51, FB03
SAPMF05A, SAPMFCHK

SAP Note 26165 - "SAPLCYBT" "PROGRAM_ERROR"

Symptom:

In program "SAPLCYBT", exception "PROGRAM_ERROR" was triggered by a RAISE statement. The termination occurred in ABAP/4 program "SAPLCYBT" in "CY_BT_KBED_OPR_UPDATE".

Cause and prerequisites

The 'Calculate capacity requirements' indicator is cancelled in an order or a network which was scheduled with capacity requirements calculation. Then an operation or sub-operation or activity element is created and the 'Calculate capacity requirements' indicator is set again or a function, for example, Release Order, is performed which resets the indicator. The above-mentioned error occurs if a scheduling is carried out then.

Solution

First set the 'Calculate capacity requirements' indicator and then carry out the scheduling. Include the operation or sub-operation or activity element and carry out the scheduling again.

Program correction


Additional key words

Scheduling

SAP Note 26164 - No short text in QDE system work center basic data

Symptom:

No explanatory short text on the QDE system is displayed on the basic data screen of the work center.

Cause and prerequisites

The screen has no data field for entering the corresponding text and the flow logic has no module for processing the text.

Solution
Include the field on the screen, create PBO module.

Additional key words

CR01, CR02, CR03, CRC1, CRC2, CRC3

SAP Note 26161 - IH03: RIEQUI10: Termin. in Environment -> BOM item

Symptom:

During the structural display of equipments, functional locations and materials following a BOM item selection and the menu selection Environment -> Display BOM item, a runtime error occurs with message "KEY_INCOMPLETE".

Cause and prerequisites

Program error

Solution
See the source code corrections below.

Additional key words

RIEQUI10, RIIFLO10, RIMARA10, IH01, IH03, maintenance bills of material

SAP Note 26158 - Error during cumulation of available capacity

Symptom:

The cumulation of the available capacity of individual capacities for the main capacity (single machines, persons) does not work.

Cause and prerequisites
  • Capacity leveling in the planning table with periods. (planning table intabular form, SOP-Table, MRP table)
  • Customer settings which cause a corresponding cumulation. (No problem in the standard setting)
Solution
Program correction for release 3.0B

Additional key words

Indicator: Cumulation of available capacity via individual capacities
Capacity requirements planning
Planning table (tabular form)
Period available capacity

SAP Note 26155 - Incorrect target costs for missing operating rate

Symptom:

The target costs are calculated incorrectly.
This is noticed in reporting or when calculating imputed costs.

Cause and prerequisites

If planned activity or actual activity is missing, incorrect operations are used as the basis for calculating the target costs.

Solution
The problem can only be solved by means of a correction.

Additional key words

Target cost calculation, target=actual calculation of imputed costs, operating rate
Target=actual calculation of imputed costs: KSA3 ( SAPMKSZB )
Reporting: GR55

SAP Note 26154 - Error with INSERT for file AUAK

Symptom:

Description: During the settlement, an update termination occurs with
the following error message.
Error message: KD533 'system error during INSERT for file AUAK (Return
code = 4)'
Program: LKO78U01, FUNCTION K_SETTLEMENT_DOCUMENT_INSERT

Cause and prerequisites

An attempt was made to update a settlement document with an existing document number. Presumably, a mistake was made concerning the number assignment for the settlement document numbers.

Solution
With the help of the transaction KO8N (number ranges for settlement documents cost element itemizations; can be accessed by means of various Customizing menus as subfunction of the settlement Customizing), you can determine the number intervals and the current number level for settlement document numbers.
Please set the interval limits or the current number level so that no settlement document numbers exist yet between current number level and upper interval limit.
You can determine the existing document numbers with the help of the transaction SE16 (general table display) for the table AUAK.

SAP Note 26152 - Deletion of a master inspect. charact. or method

Symptom:

A master inspection characteristic version or method version can be deleted even though it is used in a task list.

Cause and prerequisites

A master inspection characteristic version is included in a task list as a reference. The validity status belonging to this version is then changed with history (transaction QS23) and the resulting version is not transferred into the task list (You exit the window which comes up for posting by clicking on 'no').
Corresponding preconditions apply to inspection method.

Solution
Please make the changes mentioned below in the program code.

Additional key words

QS25, QS23, QS35, QS33, history

SAP Note 26148 - MI31 RM07II31 ERROR DBIF_RSQL_SQL_ERROR

Symptom:

Report RM07II31 terminates with DBIF_RSQL_SQL_ERROR.

Cause and prerequisites

ADABAS database. If a table is read with RANGES, the number of entries in RANGE is < 253 (as it is allowed for ORACLE).

Solution
When RANGES R_MATNR is filled in module RM07IBDC, the maximum number allowed is reduced.

Additional key words

This error can also occur in the following reports: RM07IK31
RM07ICN1
RM07IE31
RM07IO31
RM07IV31
RM07IW31

SAP Note 26145 - RFXPRA26 / Posting unearned deductions

Symptom:

After the upgrade to Release 3.0A, the accounts for posting the unearned deductions are missing in Customizing.

Cause and prerequisites

The account determination key was changed from 'UBS' to 'ZDI'. However, the respective conversion program only converted the entries correctly in the client in which the program was started. In all other clients, the unnecessary 'UBS' entries were deleted but the new 'ZDI' entries were not added.

Solution
Since the program is executed within the upgrade to 3.0A, you can correct the program only if the conversion has already been made. In this case, the account determination for unearned deductions has to be set up again. This generally only requires the specification of an account.
Use the following path in the SAP Reference IMG of Financial Accounting:

Financial Accounting
Accounting (General ledger, A/R, A/P)
Business transactions
Accounts Receivable
Incoming payment
Define accounts for payment differences

Enter the chart of accounts in the following window. You get to a screen in which you can determine the rules for the account determination. After you have saved the rules, choose 'Accounts' to enter the required accounts.

The program is corrected in Release 3.0B.

Additional key words

UBS, ZDI, minor differences

SAP Note 26143 - IS-H: No form printout for invoices

Symptom:

Forms are not output from case-related invoice processing; however, the system does not issue an error message. The mass printing program provides the required result when you select single print control.

Cause and prerequisites

Incomplete Customizing in implementation phase

Solution
Customizing -> Hospital -> Services -> Work organizer admin. -> Work organizers -> Output conditions -> With ins.prov./type: for your institution, there must always be an entry of the type work organizer = 'RECH_01', insurance provider = '*' and ins. prov. type = '*' and standard printout = 'x', which sets the indicator for online printing on the detail screen. This entry is also necessary to print non inpatient forms.

Additional key words

Invoice printout, SAPLNFR1, form, form output

SAP Note 26141 - Schdlng log: Date not defined in factory calendar

Symptom:

The scheduling log reports message C7008 "Date is not defined in factory calendar" although the scheduling dates are within the defined factory calendar.

Cause and prerequisites

Intervals of available capacity are maintained in a work center capacity whose 'To date' is after the expiration date of the factory calendar. The error does not occur if the date is 12/31/9999.

Solution
The 'To date' of an interval of available capacity must be maintained so that it is within the validity period of the factory calendar. The exception is the date 12/31/9999, which is allowed.

Additional key words

CR02
Scheduling, capacity leveling

SAP Note 26139 - Calculation of variances: Division by zero

Symptom:

When calculating variances, a termination occurs in the list tool (SAPLKSS1) because of a division by zero.

Cause and prerequisites

Missing value check before the division is made.

Solution
The error can only be eliminated by means of a correction.

Additional key words

Transaction : KSS1
SAP program : SAPMKSS0, SAPLKSS1.
Function modules: K_VARIANCES_FILL_TABLE_KSS03,
K_VARIANCES_FILL_TABLE_KSS04.

SAP Note 26137 - CO13/CN29/IW45: Posting in a closed period

Symptom:

When cancelling a completion confirmation, the actual costs are determined and backflushing takes place for the posting date which was taken from the completed confirmation. If the cancellation takes place at a later time then the posting period can be closed already at the posting date. It is necessary to close the posting period(s) again.

Cause and prerequisites

The posting date for the confirmation cannot be changed when cancelling.

Solution
If the posting period for the posting date is closed, then the posting date can be changed when cancelling. A warning informs the user that the posting date falls in a closed period. However, the date need not be changed, it can be posted in the already closed period.
If the posting date is changed, the actual costs determination can produce a different result when cancelling from that when entering. The reason for this is the different rates of activity types for the changed posting date.
The consequences of this is that the order is credited with costs that are either too high or too low.

Note: The field "posting date" is only ready for entry when cancelling
the confirmation if the posting date of the confirmation is in a

Additional key words

CO13, OKP1


closed period.

SAP Note 26133 - RPCMLI00 Persons not paid in cash in evaluation

Symptom:

If a payroll area with employees paid in cash (wage type /557) and those paid via bank transfer (wage type /559) is evaluated, employees paid via bank transfer also appear on the list.

Cause and prerequisites

Program error.

Solution
Change source code in program RPCMLI00.

SAP Note 26132 - Unit-of-production depreciation for oil industry

Symptom:

For the unit-of-production method of depreciation, changes to the total number of units resulted in the depreciation to be recalculated for the entire year.
As of Release 3.0D or by implementing this note, you can change the total number of units period-specifically so that the changed total number of units only affects future periods.
This procedure applies to the oil industry in particular.

Cause and prerequisites

Missing functionality

Solution

This functionality will be available in the standard system in 3.0D.
************************************************************************
After you have implemented the note, make sure that with upgrades upto and including maintenance level 3.0D, table T090L is in any case included in a repair before the upgrade so that the total number of units will not be lost during the upgrade. ************************************************************************
The correction is contained in the following files on SAPSERV3: files K900870.D02 and R900870.D02, as well as K900902.D02 and R900902.D02. You have to transport these to the customer using FTP. Additional information on the transport is available in note 13719.
************************************************************************
Procedure for 3.0C:

    1. Before (!!!) you import the files, table ANLC must be included in a repair.
    It will be sufficient for this purpose to edit the table in Change mode in the Dictionary.
    2. Import the files as described in note 13719.
    3. Release the repair.
    4. Data element RSTCK must no longer be adjusted since it is already current in 3.0C.
    5. Continue as described below.

************************************************************************
Please also implement note 45922.
Afterwards, modify the depreciation calculation program with the advance corrections below in SAPLAFAR, so that it agrees with the changes.
In addition to the source code changes, you also have to make the modifications outlined below:

    1. Transaction SE54
    2. Table/View: Enter V_T090L and then press the CREATE/CHANGE button.
    3. Environment -> Own routines
    4. New entries
    5. Under T, enter 'AA' and after this, under FORM ROUTINE: 'DATEN_SELEKTIEREN'
    6. Save
You then have to change the data element RSTCK using transaction SE11. The data element has to receive the domain PACK8 instead of PACK4. Then activate the data element. Possibly, you may have to convert table ANLC on the database afterwards (if this did not take place automatically when the data element was activated).

Documentation on handling and maintaining the total number of units.
This concerns the total number of units, not the remaining number of units.

SAP Note 26129 - PSIS: No memory entry for PUT RSTHIE

Symptom:

If you specify several project versions in the Project Information System structure/date, for example, in the structure overview, and do not select the current data, error message OK012 is displayed: Memory entry for time PUT RSTHIE for object 000001 not found
No data is selected.

Cause and prerequisites

The internal version counter was not filled correctly.

Solution
The program logic in FORM routine CHECK_VSNMR has changed.

Additional key words

Logical database PSJ

SAP Note 26128 - PPPR: Sorted output of goods slips

Symptom:

The withdrawal slips are not resorted.

Cause and prerequisites

Request for optimal sorting of the withdrawal slips.

Solution
  • Enter the sort fields in INDEX_TAB.
  • Fill INDEX_TAB
  • Sort INDEX_TAB
  • Output of the slips

SAP Note 26126 - Incorr.layout in plan.tab.(tab.form) in order view

Symptom:

When you access the planning table (tabular form) with the order view, no requirements are displayed in the pool of orders/operations and the heading in the pool of orders/operations is inappropriate for SFC.

Cause and prerequisites

Incorrect Customizing setting.

Solution
Change Customizing accordingly.

Additional key words

Planning table, order view, no requirements, heading

SAP Note 26124 - The field VBRP-VGTYP is not filled

Symptom:

The field VBRP-VGTYP (document category of the preceding document) is not filled in the billing item.

Cause and prerequisites

This is caused by a program error.

Solution
This is corrected in 2.2G
For a correction of the incorrect documents, you can copy and execute program ZVVGTYP from this note.

SAP Note 26116 - FI_SL Rollup: CONVERT_NO_NUMBER (T807R-SEQNR)

Symptom:

The runtime error CONVERT_NO_NUMBER occurs when carrying out a rollup via transaction GL25.

Cause and prerequisites

The error occurs because of an overflow in the T807R-SEQNR (Rollup history) feld.

Solution
Correct program as follows:

Additional key words

Rollup, GL25, T807R

SAP Note 26115 - Conditions not updated during field change

Symptom:

A new condition table which uses, for example the terms of payment (ZTERM) as a key field is used. If the terms of payment are changed in the sales order, the corresponding condition is not automatically determined again from the condition table.

This can also happen if the terms of payment are used by another condition record. The correct condition is only found by a new pricing (condition access).
The problem also occurs for some standard condition tables. If you change the fields

  • Price group (customer) (KONDA)
  • Price list type (PLTYP)
  • Material pricing group (KONDM)
  • Commission group (PROVG)


the changes do not cause the corresponding condition types to be redetermined.

Additional key words

Pricing, change
KONDM, PLTYP, KONDA, PROVG

Cause and prerequisites

The program does not automatically recognize during a document update whether a condition which uses the changed field exists.
Amoung other things, the following changes are dealt with during final processing of the item in the standard system:

  • Pricing type = 'A'
    • Exchange rate for pricing and statistics (VBKD-KURSK)
    • Terms of payment key (VBKD-ZTERM)
    • Cumulative order quantity in sales units (KWMENG or MGAME)
  • Pricing type = 'B'
    • Material number (VBAP-MATNR)
  • Pricing type = 'C'
    • Date for pricing and exchange rate (VBKD-PRSDT)
  • Pricing type = 'G'
    • Ship-to party (KUNWE)
    • Payer (KUNRG)
    • Batch number (VBAP-CHARG)
    • Plant (VBAP-WERKS)
    • Date on which services rendered (VBKD-FBUDA)
  • Pricing type = 'H'
    • Incoterms (part 1) (VBKD-INCO1)


How the program behaves for the corresponding pricing type (KNPRS) that is, which condition types (KNTYP) and condition classes (KOAID) are determined again, can be seen in FORM routine KONDITIONSVORSTEP (up to Release 3.1I in Include LV61AF0K, as of Release 4.0A in Include LV61AA12). For a detailed description of the pricing types, see Note 24832.

Solution
    1. In the user exits
  • USEREXIT_NEW_PRICING_VBKD or
  • USEREXIT_NEW_PRICING_VBAP


(both in Include MV45AFZB), you can react to certain field changes by entering a certain pricing type in the 'NEW_PRICING' field. For a change of the price list type, for example, you can force a completely new pricing.

If VBKD-PLTYP NE *VBKD-PLTYP.

NEW_PRICING = 'B'.

ENDIF.


In addition to the standard pricing types (see Note 24832) you can define your own pricing types. This can be done in USEREXIT_PRICING_RULE (in Include RV61AFZA). In it, you can apply your own pricing types (KNPRS; for example, 'X') to internal table STEU. In the fields of the STEU structure, you can store up to ten condition types (KNTYP) and condition classes (KOAID) which describe those condition types for which a new pricing is executed.

    2. You can also use the condition types reserved for you in the standard system ('5' to '9' and 'X', 'Y' or 'Z') in Customizing of the condition type (T685A-KNTYP).

With these three methods you have the tools to make the system use the required condition type in the case of a field change.

SAP Note 26111 - MI21: User defaults are not copied

Symptom:

The following default values in the user master record are not considered when printing physical inventory documents:
- Output device
- Print immed.
- Delete after print

Cause and prerequisites

Program error

Solution
The error is corrected in 2.2G, 2.1M and 3.0D. For an advance correction, you have to make the following source code changes:

14.6.11

SAP Note 26108 - RABUCH00 Repeated run does not repost area

Symptom:

If a depreciation area was set up later for depreciation posting and if depreciation is then to be posted for a period during the repeated run for which depreciation has already been posted in the other area, no depreciation postings are made.

Other terms

RABUCH00, T093D

Reason and Prerequisites

During the repeated run, only the area is posted for which the requested period is entered as the last posted period in Table T093D.
For new areas, period 000 is entered in Table T093D.

Solution
The new area can be posted to during the next posting run for the next period.
If necessary, you can set the last posted period in Table T093D, or, in normal customizing, you can set the fields T093D-AFBLPE (last period) and T093D-AFBLGJ (last fisal year) in debugging. Field T093D-AFBANZ (number of posting runs) must also be set to the same value as in the areas already posted.

SAP Note 26106 - AA703 during fisc. yr change and shorten. fisc. yr

Symptom:

When you call the fiscal year change in the last posting period of a fiscal year, the unjustified error message AA073 'Not authorized for company code &' is displayed.

Cause and prerequisites

Shortened fiscal year

Solution
Advance correction in program RAJAWE00

Additional key words

RAJAWE00, AJRW, fiscal year changes

SAP Note 26105 - Object list: no quantity in subitems

Symptom:

Input of a sales order with a material with an object list on the double-line fast entry screen. Only a requested delivery date is first entered for the main item, but no quantity. If a quantity is entered later, quantity = 0 remains for the subitems.

Cause and prerequisites
Solution
The following repair can be made as of 2.1E:

SAP Note 26096 - Error CR148 for intervals/avail. cap. profile cap.

Symptom:

When you maintain work center capacities or capacities, error message CR148 "System error: Entry in table XKAPA was not found" is displayed when you branch to the details of an interval of available capacity or into the available capacity profile.

Cause and prerequisites

The database table KAPA (capacity shift values) contains entries with day number (TAGNR) 0 or shift number (SCHNR) 0. This constellation may not be present.
The origin of such entries could not yet be determined.

Solution
The incorrect entries must be removed from the database using the following report. The parameter UPDATE shows the incorrect data records with "blank" without changing the database; the records are
deleted with "X".

*&--------------------------------------------------------------------*
*& Report ZZ-KAPA1 *
*& Author: Peter Anselmann *
*&--------------------------------------------------------------------*
*& Deletes entries in table KAPA, where day number and/or shift *
*& number are 0 *
*&--------------------------------------------------------------------*

REPORT ZZ-KAPA1.

DATA: BEGIN OF LOC_KAPA OCCURS 10.
INCLUDE STRUCTURE KAPA.
DATA: END OF LOC_KAPA.

TABLES KAPA.

PARAMETERS UPDATE.

SELECT * FROM KAPA CLIENT SPECIFIED
INTO TABLE LOC_KAPA
WHERE
TAGNR = 0 OR
SCHNR = 0.

IF SY-SUBRC = 0.
LOOP AT LOC_KAPA.
FORMAT INTENSIFIED OFF.
WRITE: / LOC_KAPA-MANDT,
5 LOC_KAPA-KAPID,
15 LOC_KAPA-VERSN,
18 LOC_KAPA-DATUB.
FORMAT INTENSIFIED ON.
WRITE:
29 LOC_KAPA-TAGNR,
33 LOC_KAPA-SCHNR.
ENDLOOP.
ENDIF.

IF SY-SUBRC = 0 AND UPDATE = 'X'.
DELETE KAPA CLIENT SPECIFIED FROM TABLE LOC_KAPA.
ENDIF.

Additional key words

CR02, CR03, CR12, CR13

SAP Note 26094 - Dunning program: Missing address in dunning notice

Symptom:

Key words: Dunning notice, printing dunning notices, SAPF150D.
As of Release 3.0A, the receiver address is missing in the dunning notice.

Cause and prerequisites

Printing the address on the dunning form was changed in 3.0A:
Up to Release 3.0A, the address on the dunning form was printed by the standard text "F_ADDRESS". In this case, the address was formatted by function module "ADDRESS_INTO_PRINTFORM" called when printing dunning notices.
As of 3.0A, the address is formatted with the command "ADDRESS - ENDADDRESS". Therefore, function module "ADDRESS_INTO_PRINTFORM" is no longer required.
As of 3.0A, all dunning forms were also changed to the altered printing of the address but customer-specific forms probably still have the old status.

Solution

For all dunning forms, you have to make the changes indicated below in the address window:

    1. Delete the line in which the standard text "F_ADDRESS" is included.
    2. Insert the complete section from ADDRESS to ENDADDRESS.
    INCLUDE &T047I-TXTAB& OBJECT TEXT ID ST PARAGRAPH LS
    INCLUDE F_ADDRESS OBJECT TEXT ID ST LANGUAGE &T001-SPRAS& <- DELETE

    ADDRESS PARAGRAPH AS
    TITLE &ADRS-ANRED&
    NAME &ADRS-NAME1&, &ADRS-NAME2&, &ADRS-NAME3&, &ADRS-NAME4&
    STREET &ADRS-STRAS&
    POBOX &ADRS-PFACH& CODE &ADRS-PSTL2& CITY &ADRS-PFORT&
    POSTCODE &ADRS-PSTLZ&
    REGION &ADRS-REGIO&
    CITY &ADRS-ORT01&, &ADRS-ORT02&
    COUNTRY &ADRS-LAND1&
    FROMCOUNTRY &ADRS-INLND&
    ENDADDRESS

SAP Note 26091 - Reorder point is reset or is not displayed

Symptom:

When maintaining a material master record, the reorder point for the material is reset with the warning "Reorder point reset (not reorder point or time-phased materials planning)" (warning M3 440), or it is hidden when displaying a material master record.

Cause and prerequisites

The problem occurs if reorder point planning is not defined for the material.

Solution
As of Release 3.0B, the value is no longer reset automatically after this warning or hidden.

Additional key words

Transactions: MM01, MM02, MM03; program: SAPMM03M; field: MARC-MINBE

SAP Note 26090 - Class. system: Termination SAPSQL_NO_DBTAB_OR_VIEW

Symptom:

Termination in the object list with message:
ABAP/4 runtime error SAPSQL_NO_DBTAB_OR_VIEW

Cause and prerequisites

A dynamic database access is attempted on a table structure because a characteristic of the used class refers to such a structure field.

Solution
P30K014131 in program LCLDYTOP and LCLDYU04.

SAP Note 26088 - VA01: Material determination and info record

Symptom:

The customer material number is entered in the overview screen "Orderer" instead of the material number. If the material number is then also determined from the material info record, material determination or material substitution does not take place.

Cause and prerequisites
Solution
The following repair is possible from 2.1E to 2.2Z:

SAP Note 26087 - "Refresh" in Project Info. System struct/sched.

Symptom:

In Project Information System structure/schedule, the object status (tables JSTO, JEST) is not refreshed when you refresh projects.
This error only occurs if, when working in the information system, you change the status for an object in another mode in a parallel session.

Cause and prerequisites

When data is looked up with the logical database PSJ, the buffer for status data JSTO and JEST is not deleted.

Solution
The status buffer is deleted before the data is read again.

Additional key words

logical database PSJ

SAP Note 26086 - TCP/IP Connection to partner broken

Symptom:

Well running TCP/IP connections break down when sending or receiving larger data packets (about 2000 bytes up to 5000 bytes).
-> "connection to partner broken" at the sapgui
-> "Connection timed out" in the R/3-System

Cause and prerequisites

If applications send data-packets larger than the MTU-size (maximun transmission unit) of the underlying network these data-packets must be fragmented into serveral packets less than or equal MTU-size.

Please note that these kind of problems belong to your specific TCP/IP configruation and are normally no SAP-Problems.

In FDDI networks the normal MTU-Size is 4352 bytes. That can be verified using the command: netstat -i
The normal ethernet packet size is about 1500 Bytes. So Routers between FDDI and Ethernet must fragment and defragment packets larger than 1500 Bytes. WAN-Lines may have other (smaller) MTU-Sizes.

To check wether or not you have that problem you may use the niping program. (SAP Program)

    1. Start the niping server on the R/3-computer. (login as R/3-adm user)
    command: niping -s -I0 &
    2. Start the niping client on the frontend (PC)
    command: niping -c -B 5000 -H


You may vary the blocksize from 1000 Bytes up to 5000 Bytes. Please envolve your networking guys to solve that ploblem.
It may be necessary to use network-analysers to check which component isn't able to do the fragmentation/defragmentation (IP-layer).
May be the PC's TCP/IP-Stack isn't able to reassemble fragmented TCP/IP packets.

Solution
The solution of this problem must be found and done in the networking environment. One possibility is to set MTU-size to the smallest MTU of any data link that packets traverse between the PC and the R/3-Host.

However the data sent by the SAP-applications depend on the amount of application-data and may vary in a wide range.

Additional key words

MSS (maximum segment size) IP-fagmentation

SAP Note 26084 - Objects displayed in cap.planning list after CY112

Symptom:

If you choose Extras -> Evaluation -> Cap. planning list on the planning table, the following message is displayed if no objects were selected:
"Function not possible. Select object for a group". When you press "Continue" they are still displayed together!

Cause and prerequisites

Error in the program code.

Solution
Correction P30K014061

Additional key words

Capacity adjustment, Capacity requirement list, CY112

SAP Note 26083 - Route determination in the delivery

Symptom:

Under certain circumstances, route determination in the delivery is not carried out with the changed transportation zone but with the customer master transportation zone of the ship-to party.

Cause and prerequisites

Program error

Solution
Correction
For Release 2.2, maintain program LV50SF0R in the same way as FV50KF0R.

SAP Note 26082 - During AuC line item settlement, AW002 is issued..

Symptom:

If you settle a cost element itemization (order / WBS element) with transaction KO88 or CJ88 to an asset under construction with open item management, line items are created on asset under construction with the posting date of the period-end. If you settle the asset under construction settled in the same period to an asset in service using the line item settlement transaction AIBU, the line items of the period are not settled if the posting date entered for the line item settlement is before the posting date of the line items.
Example: Order settlement with KO88 Period 08 on 8/15/xxxx -->
on the asset under construction, a line item is created with the posting date 8/31/xxxx
AuC settlement with AIBU posting date 8/15/xxxx --> the line item is not settled and message AW002 "Asset has no line items to settle" is possibly displayed.

Cause and prerequisites
Solution
Use the date of the period-end as posting date to settle the asset under construction.

Additional key words

AIAB, settlement

13.6.11

SAP Note 26080 - Convers. factor during transfer posting material

Symptom:

During a transfer posting material to material (movement type 309) in alternative unit of measure (unit of entry), the quantity of the receiving material is not converted into the unit of entry. The receiving material is only converted into the base unit of measure.

Example: Base unit of measure = Pc
Unit of entry = kg

Material 1: 1 Piece = 2 kg
Material 2: 1 Piece = 5 kg

Transfer posting of 10 kg of material 1 to material 2: the following items are generated:

  • Item 1: 10 kg material 1
    5 Pieces
  • Item 2: 10 kg Material 2 ---> wrong
    5 Pieces
Cause and prerequisites

The system behavior concerning the postings is correct: All conversions are based on the base unit of measure.
The entry quantity in the material document is not relevant.

Solution
This is only a display error in the material document.
The quantity in the unit of entry of the acquiring material should not be taken into account.
The quantities are updated correctly in the material master records as only the base unit of measure is relevant.

If you would neverthesless like to see the correct entry quantities in the material document display, make the attached source code corrections. The repair only becomes effective for the new material documents.

Additional key words

.. MB1B

SAP Note 26074 - MMIM: G/L account check in reservation

Symptom:

If you enter a G/L account in the multiple-entry screen when creating reservations, this is not copied correctly into the individual items. The system still carries out an account determination for the item.
In addition, the check of a G/L account entered for an item may be incorrect.

Cause and prerequisites

Program error.

Solution
Please make the following changes in the source code (Include: MM07RI00, MM07RFK0 and MM07RFP0) and in SAPMM07R, screen no. 0510).

SAP Note 26073 - RABUCH00 table T093D is inconsistent

Symptom:

During depreciation posting using RABUCH00, error messages (for example AA726) are issued because a previous period or even a previous fiscal year instead of the actual last posted period is entered in table T093D.

Other terms

TABA, OAE4, AA683, RABUCH00, RAPOST2000, AFAB, AFABN, AA726, AA 726,

Reason and Prerequisites

The date "Posted upto" was presumably changed for old assets data takeover during the fiscal year in Old Assets Data Takeover Customizing after the last depreciation posting. In the process, the fields for the last posted period were also reset in table T093D.

Solution
After depreciation has already been posted, the parameters may no longer be changed for old assets data takeover. If necessary, this should be ensured by the appropriate restricted authorizations.
Table T093D can be rectified with the following ABAP report.

Report ZZT093DU.
Tables T093D.
Update T093D
Set AFBLPE = 'PPP' " <=== correct period
AFBLGJ = 'YYYY' " <=== correct fiscal year
AFBANZ = '00'
STATUS = ' '
Where BUKRS = 'BBBB' and " <=== company code
AFABER = '01' and " <=== depreciation area
AFBLPE = 'ppp' and " <=== wrong period
AFBLGJ = 'yyyy'. " <=== wrong year

SAP Note 26072 - Delta vers. deletion despite avail. bus. transact.

Symptom:

You can delete a delta version within version maintenance (transactions OKEQ or OKEV) although business transactions have already been defined for it.

Cause and prerequisites

Program error (corrected in 3.0B)

Solution
Please make the following changes in program SAPLCOVS:

Additional key words

Delta version, OKEQ, OKEV, version maintenance

SAP Note 26069 - Delta vers.: Assessment processes always activated

Symptom:

If you copy the business transaction 'Assessment processes' for a delta version from the reference version (no 'X'), this business transaction is marked as being selected when you maintain the delta version again (transaction OKEQ or OKEV).

Cause and prerequisites

Program error (corrected in 3.0B)

Solution
Please make the following changes in program SAPLCOVS:

Additional key words

Delta version, OKEQ, OKEV, version maintenance

SAP Note 26067 - Import format RFDEV310 (multicash)

Symptom:

Customer inquiry concerning field formats for RFDEV310

Cause and prerequisites
Solution
The input file for the report RFDEV310 is be supplied in the multicash format:
Field/format Length Contents
1 alphanum. 3 Currency in ISO code
2 numeric 12 Average exchange rate in format 4.7
(4 places before and 7 places behind the decimal point)
3 numeric 12 Range of fluctuation of the foreign exchange rate in format 4.7

The currency must be transferred in the ISO code format. The program converts the currency into the common house format (with five digits).

Additional key words

Multicash

SAP Note 26061 - FB00: F4308 in LINE_LAYOUT_GENERATE

Symptom:

When you call FB00 (possibly also when calling FB01), a termination occurs with F4308 System error: error in routine LINE_LAYOUT_GENERATE.

Cause and prerequisites

Error occurs only with the first callup of the transaction following a release upgrade.
Error occurs if variants are generated for different applications one after the other.

Solution

1. Correction (see below). Thus the error no longer occurs.
2. Start program RFFAKP01 for the affected application:

  • - SAPMF05A and RE/GU for invoice/credit memo fast entry
  • - SAPMF05A and SAKOP for G/L account fast entry
This corrects the error even without the correction being imported.
3. Using FAKP, select and save the defined variants once so that they are re-generated.

Additional key words

T021D, SAPLF034, entry screens, fast entry, FAKP, SAPDFKA6

SAP Note 26060 - Incorr.disp. of non-working period time on plan.tab.

Symptom:

When you use a capacity interval with a cycle length of one day and several shifts, the available capacity is displayed incorrectly on the planning table (the display of the working hours of the day before or after a weekend).

Cause and prerequisites
Solution
Correction in program code

Additional key words

CM21

SAP Note 26059 - ME27 Transferring a non-valuated material ME062

Symptom:

Non-valuated material in issuing and receiving plant.
When you create a stock transport order, the system unnecessarily demands the entry of an account assignment category and an account assignment.

Cause and prerequisites

Error

Solution
    1. Create the following entries in table T156S:

    BwA WFs MFs S Bew Zug Vbr WStr MStr OWSt LOrt Anz Ref UmR ... VB..PLH
    101 X B X MEU1 X LE1 101 01
    351 X X MAU2 X L01 301 999 999 A 02
    641 X L X MAU2 X 641 999 999 02
    2. Make the source code corrections.

Additional key words

ME27, ME37, EME062.


SAP Note 26058 - Error message: TYPE-POOLS statement not allowed

Symptom:

Syntax error:
The TYPE-POOLS statement is only allowed on program level.

Cause and prerequisites

The TYPE-POOLS statement, with which the types and constants of a type
group are included in a program, is only authorized on program level.
If a TYPE-POOLS statement is used in a type group, a syntax error
erroneously occurs in Release 30A.

Solution
Only a change in the corresponding ABAP coding is possible for 30A.
(Delete the TYPE-POOL statement from the TYPE POOL and insert it
directly in the ABAP program).
The error is corrected for Release 30B.

SAP Note 26055 - Inventory management: Negative stocks

Symptom:

It is not possible to post goods issues to negative stock although the setting was made according to the release notes.

Cause and prerequisites

Missing section in the release notes.

Solution
The following sentence is added to the release notes as of 3.0A and must be considered when using the functionality.
Changes in the procedure
In the material master record (Extras -> General plant data), you have to set the indicator 'Neg. stocks in plant'. Only then are negative stocks allowed for the material in the plant.

Additional key words

MB1A

SAP Note 26053 - Rumpfjahresregelung im Erstattungsantrag

Symptom:

Bei der Erstellung der Erstattungsanträge gemäß § 8 EFZG werden jene Mitarbeiter abgelehnt, deren Fristen gem. Rumpfjahresregelung bestimmt werden.

Weitere Begriffe

Entgeltfortzahlungsgesetz

Ursache und Voraussetzungen

Diese Regelung entstammt Kollektiv-Verträgen, wird jedoch auch im gesetzlichen Teil der Entgeltfortzahlung angewendet.
Somit sollte diese Regelung jener gem. Kalenderjahren entsprechen.

Lösung
Erweiterung des Reports RPCEFZA0 um die Regelung bzgl. Rumpfjahre.

SAP Note 26050 - FIPP:Posting not poss. (SAPMF05A,0700,batch input)

Symptom:

  • When you use Transaction FBV1 to post parked documents in Transaction FBV0, the message is issued that no batch input data exist for screen SAPMF05A/0700 cannot be found.
  • For cross-company-code transactions, the system displays the message that no batch input data exist for screen SAPMF05A/0701.


Furthermore, there are always queries to the effect that customers are missing automatically generated line items (for example, tax line items) in the document overview, or fields that are to be automatically filled are not filled for document parking in the document overview. This is because only the line items actually entered are visible in document parking with Transaction FBV1. The automatically generated line items or fields that are to be automatically filled are only filled when you post the parked document, and so only then become visible to the user.
(Technical background: An accounting document is created from the parked document via batch input.)

Other terms

FBV0, document parking, automatically generated line items, 00344, 700,
required field, AUTTAB O

Reason and Prerequisites

Required-entry fields are defined for accounts of automatic postings (for example, taxes, cash discount, non-deductible taxes) which cannot be filled when making preliminary postings, or the indicator 'Supplement for automatic postings ?' (SKB1-XNKON) has been set in the master record of one of the accounts.

Solution
    1. If required-entry fields are defined, as described above, the field selection of these accounts must be reduced to 'optional' (see Transaction OBC4). If you urgently need a required field check nevetheless, this check can be carried out via a validation at callup point 2. This validation should not be performed under condition SY-TCODE = 'FBVB' (posting a parked document).
    2. If the indicator 'Supplement for automatic postings ?' has been set, you can either remove the indicator or implement the modifications from Note 49893. This will only work if you generate a batch input session from the parked documents and then process it.

    If it is still required to realize required field checks / supplementary account assignments for parked documents, proceed as follows:
    1. Call up Transaction FBV0 and branch to the list.
    2. Select the parked document in which the termination occurs, and create a batch input session via 'Edit -> Create batch input'. Then process the batch input session in the foreground.

This procedure can also be used for error analysis.
or: You create a substitution which tries to 'automatically' make an
an account assignment for the field to be filled.

SAP Note 26048 - HR: incorrect change of absence for collision

Symptom:

A one-day absence and, on the following day, leave lasting several days was entered for a personnel number.
If the start date of the leave record is then brought forward by one day and the data is saved immediately after it is changed, a collision with the one-day absence occurs.

    1. If you exit the collision screen by pressing ENTER, the error message PG080 "E: Insert not possible due to collision" is issued, and you branch back into the detail screen of the leave record.
      a) If you now leave the detail screen by pressing BACK, the leave record has disappeared, but it still exists in the leave deduction in infotype 0005 (Leave Entitlement).
      b) If you now exit the detail screen by pressing ENTER, the changed record is saved despite the fact that a collision exists and an error message was issued. The one-day absence still exists.
    2. If you exit the collision screen by pressing BACK and then, on the detail screen, also press BACK, the POPUP 'Leave current screen'. If you confirm this popup with YES, the leave record disappears.
Cause and prerequisites

Program error

Solution

The error is corrected in Release 3.0B. You can carry out the following advance correction:

    1. Edit program FP50PF99.
      a) In this Include, insert the routines UNDELETE_TEXT, UNDELETE_PREF and UNDELETE_PAFRU listed below.
    2. Edit program FP50PE00.
      a) In this Include, insert the routine UNDELETE_OLD_PS listed below.
      b) Find the routine INSERT_INFOTYP and carry out the changes listed in the section "Source code corrections".
    3. Edit program FP50ME00.
      a) Find the routine UPDATE_BUFFER and make the changes described.

Additional key words

PA61


SAP Note 26047 - CO13: Long texts in completion confirmation disappear

Symptom:

All long texts in completion confirmations of orders are deleted. This
takes place when cancelling a completion confirmation in PP and PM
orders and networks when a long text is entered for cancellation.

Cause and prerequisites

In function module CO_RU_BT_AFRU_BT_CLEAN, unchanged completion confirmations are deleted from the document table before being saved. With each deleted completion confirmation, the long text is
deleted as well.

Solution
Delete only completion confirmation in function module
CO_RU_BT_AFRU_BT_CLEAN, not the long texts.

Additional key words

CO11, CO13, CN29, CN25, IW45, IW41

SAP Note 26045 - Nothing happens in ranking list of planning table

Symptom:

When you branch to the ranking list in the planning table, no ranking list of persons is displayed.

Cause and prerequisites

Error in the program code.

Solution
Correction P30K013411

SAP Note 26044 - KEU5: high number of receivers, Performance

Symptom:

The transfer of cost center costs to CO-PA takes place on the basis of a variable portion. More than one line item is updated for each sender and for each receiver (profitability segment).
You are dissatisfied with the running time.

Cause and prerequisites

Field ARTNR is always generated in the internal field string COMMONKEY. There is consequently no summarization of the tracing factors via item reference.
To check the document number, a block is created for table CE1xxxx and a read-attempt executed.

Solution
    1. Please include the following correction for releases prior to Release 2.2G.

The following measures can further reduce the number of the receiving line items:

    2. Split cycles with several segments in which different characteristics are specified as receiving criteria (for example segment 1 for division, segment 2 for customer or material) into several cycles.
    3. Execute the cycles separately.

Additional key words

Performance.


SAP Note 26043 - Displaying doc. originals from object (e.g. mat.)

Symptom:

If you choose 'Display original' from the list of the linked documents, the popup is highlighted again after the start of the application.

Cause and prerequisites

Due to technical reasons, you cannot use the 16-bit GUI to focus on the application started asynchronously in a modal dialog box. The dialog box is set up again afterwards and is the last to receive the focus. This problem does not occur with the 32-bit GUI.

Solution
With the key combination , you can branch directly to the next application window.

SAP Note 26042 - BOM transfer structures for version 3.0

Symptom:

As CPS customer, we do have access to your 3.0 version but unfortunately we are not authorized to use the Data Dictionary Information System.
Since we are currently preparing a BOM transfer for version 3.0, we would like know what the transfer structures for this procedure look like (BICSK, BICSP, BICSU, ...) in version 3.0.
Send us these structures by FAX, if possible.

Cause and prerequisites
Solution
Below, you will find the requested information. ===============================================BOM subitem:
Name Cat. Length Meaning
BICSU-STYPE CHAR C 1 Record type for batch input
BICSU-XLINE NUMC N 4 Line index for internal
BICSU-EBORT CHAR C 20 Installation point subitem
BICSU-UPMNG CHAR C 17 Subitem quantity
BICSU-UPOSZ CHAR C 4 Subitem number
BICSU-UPTXT CHAR C 40 Subitem text


BOM item:
Name Cat. Length Meaning
BICSP-STYPE CHAR C 1 Record type for batch input
BICSP-XLINE NUMC N 4 Line index for internal
BICSP-UPSKZ CHAR C 1 Indicator: Subitem
BICSP-AUSKZ CHAR C 1 Selection indicator (
BICSP-ALPOS CHAR C 1 Indicator: Alternative
BICSP-AUSCH CHAR C 6 Component scrap in
BICSP-AVOAU CHAR C 6 Operation scrap (BTCI)
BICSP-BEIKZ CHAR C 1 Material provided indicator
BICSP-CADPO CHAR C 1 CAD indicator
BICSP-EKGRP CHAR C 3 Purchasing group
BICSP-ERSKZ CHAR C 1 Spare part indicator
BICSP-FMENG CHAR C 1 Fixed quantity
BICSP-IDNRK CHAR C 18 BOM component
BICSP-LIFNR CHAR C 10 Account number of vendor
BICSP-LIFZT CHAR C 3 Delivery time in days
BICSP-MATKL CHAR C 9 Material group
BICSP-MEINS UNIT C 3 Component unit of measure
BICSP-MENGE CHAR C 18 Component quantity (BTCI)
BICSP-NETAU CHAR C 1 Oper. scrap net indicator
BICSP-NFMAT CHAR C 18 Follow-up material
BICSP-NLFZT CHAR C 3 Follow-up time (BTCI)
BICSP-PEINH CHAR C 6 Price unit (BTCI)
BICSP-POSNR CHAR C 4 BOM item number
BICSP-POSTP CHAR C 1 Item category (bill of material
BICSP-PREIS CHAR C 14 Price (BTCI)
BICSP-POTX1 CHAR C 40 BOM item text
BICSP-POTX2 CHAR C 40 BOM item text
BICSP-PSWRK CHAR C 4 Withdrawal plant
BICSP-REKRS CHAR C 1 Indicator: Recursiveness
BICSP-RFORM CHAR C 2 Formula key
BICSP-ROANZ CHAR C 17 No. of var.-size items (BTC
BICSP-ROAME UNIT C 3 Unit of no. of var.-sized items
BICSP-ROKME UNIT C 3 Component unit of measure
BICSP-ROMEI UNIT C 3 Unit of var.-sized item dimens.
BICSP-ROMEN CHAR C 17 Variable-size item qty (BTCI)
BICSP-ROMS1 CHAR C 17 Size 1 (BTCI)
BICSP-ROMS2 CHAR C 17 Size 2 (BTCI)
BICSP-ROMS3 CHAR C 17 Size 3 (BTCI)
BICSP-RVREL CHAR C 1 Relevancy for sales/distribution
BICSP-SAKTO CHAR C 10 Cost element
BICSP-SANFE CHAR C 1 Indicator: In-production rejection
BICSP-SANIN CHAR C 1 Indicator: Plant maintenance
BICSP-SANKA CHAR C 1 Costing indicator
BICSP-SANKO CHAR C 1 Indicator: Construction
BICSP-SANVS CHAR C 1 Indicator: Relevancy for S&D
BICSP-SCHGT CHAR C 1 Indicator: Bulk material
BICSP-SELAL CHAR C 2 Alternative BOM
BICSP-SELID CHAR C 18 BOM component
BICSP-SELPO CHAR C 4 BOM item number
BICSP-SELSB CHAR C 10 Sort string
BICSP-SORTF CHAR C 10 sort string
BICSP-STKKZ CHAR C 1 Indicator: PM assembly
BICSP-STKTX CHAR C 40 Alternavtive BOM part
BICSP-STLAL CHAR C 2 Alternative BOM
BICSP-STLKZ CHAR C 1 Indicator: Assembly of
BICSP-VERTI CHAR C 4 Distribution key for
BICSP-WEBAZ CHAR C 3 Processing time for maint.
BICSP-WAERS CHAR C 5 Currency key (BTCI)
BICSP-DOKAR CHAR C 3 Document type
BICSP-DOKNR CHAR C 25 Document number
BICSP-DOKVR CHAR C 2 Document version
BICSP-DOKTL CHAR C 3 Document part
BICSP-EWAHR CHAR C 3 Usage probability
BICSP-EKORG CHAR C 4 Purchasing organization
BICSP-LGORT CHAR C 4 Issue storage location for
BICSP-CLASS CHAR C 18 Class number
BICSP-KLART CHAR C 3 Class type
BICSP-POTPR CHAR C 1 Resulting item
BICSP-ALPGR CHAR C 2 Alternative item grouping
BICSP-ALPST CHAR C 1 Alternative item strategy
BICSP-ALPRF NUMC N 2 Ranking order


BOM header:
Name Cat. Length Meaning
BICSK-STYPE CHAR C 1 Record type for batch input
BICSK-TCODE CHAR C 4 Transaction code
BICSK-AENNR CHAR C 12 Change number
BICSK-BMEIN UNIT C 3 BOM base unit of measure
BICSK-BMENG CHAR C 17 Base quantity (BTCI)
BICSK-CADKZ CHAR C 1 CAD indicator
BICSK-DATUB CHAR C 10 Date valid to (BTCI)
BICSK-DATUV CHAR C 10 Date valid from (BTCI)
BICSK-EMENG CHAR C 17 Required quantity (BTCI)
BICSK-EQUNR CHAR C 18 Equipment number
BICSK-EXSTL CHAR C 18 BOM group
BICSK-LABOR CHAR C 3 Laboratory/eng./design off.
BICSK-LOEKZ CHAR C 1 Deletion flag for BOM
BICSK-LOSBS CHAR C 17 Lot size to (BTCI)
BICSK-LOSVN CHAR C 17 Lot size from (BTCI)
BICSK-MATNR CHAR C 18 Material number
BICSK-SELAL CHAR C 2 Alternative BOM
BICSK-SERGE CHAR C 30 Manufacturer serial number
BICSK-STKTX CHAR C 40 Alternative BOM text
BICSK-STLAL CHAR C 2 Alternative BOM
BICSK-STLAN CHAR C 1 BOM usage
BICSK-STLBE CHAR C 4 Authorization group for BOM
BICSK-STYPE CHAR C 1 Record type for batch input
BICSK-TCODE CHAR C 4 Transaction code
BICSK-AENNR CHAR C 12 Change number
BICSK-BMEIN UNIT C 3 BOM base unit of measure
BICSK-BMENG CHAR C 17 Base quantity (BTCI)
BICSK-CADKZ CHAR C 1 CAD indicator
BICSK-DATUB CHAR C 10 Date valid to (BTCI)
BICSK-DATUV CHAR C 10 Date valid from (BTCI)
BICSK-EMENG CHAR C 17 Required quantity (BTCI)
BICSK-EQUNR CHAR C 18 Equipment number
BICSK-EXSTL CHAR C 18 BOM group
BICSK-LABOR CHAR C 3 Laboratory/eng./design off.
BICSK-LOEKZ CHAR C 1 Deletion flag for BOM
BICSK-LOSBS CHAR C 17 Lot size to (BTCI)
BICSK-LOSVN CHAR C 17 Lot size from (BTCI)
BICSK-MATNR CHAR C 18 Material number
BICSK-SELAL CHAR C 2 Alternative BOM
BICSK-SERGE CHAR C 30 Manufacturer serial number
BICSK-STKTX CHAR C 40 Alternative BOM text
BICSK-STLAL CHAR C 2 Alternative BOM
BICSK-STLAN CHAR C 1 BOM usage
BICSK-STLBE CHAR C 4 Authorization group BOM

You will find the standard batch input for creating bills of material in Customizing under Production -> Master data -> Bill of material -> Tools -> Data transfer -> Transfer data now.
The Implementation Guide contains a short description.
For more information on the file structure, refer to the conversion program. Since transaction SE38 is currently not available, refer to the program documentation below:

Description:
With this report, you can take over bills of material from an external system into the SAP System. In this case, the system supports the creation of document lists, equipment lists, materials lists, standard object lists and functional location BOMs.
The program reads the specified sequential file and processes the data contained in it.
The sequential file can be located on your own application server, the presentation server or an external application server.
For the latter case you have to specify the corresponding server name. A possible entries pushbutton is available to determine all available application servers. If you set the report parameter 'Create session' to "X" , one or more batch input sessions are created for the data which you can later process manually. If the report parameter 'Create session' is initial, all bills of material are created online. In this case, only the bills of material for which errors occurred during its creation are collected in batch input sessions. They can be reprocessed afterwards.
Preconditions
Before you can start this report, you must have extracted the BOM data to be copied from the source system and written to a sequential file. To do this, you must implement a program in the source system which lists data in the predefined format and creates the file.
It is required that the BOM data to be copied is available in the format specified below in the sequential file:
One session record for each session (structure BGR00, record type 0)
The session record contains general administrative data on the batch input session to be created. All other records of the sequential file up to the next session record are allocated to the current session.
One header record for each bill of material to be created (structure BICSK, record type 1).
In addition to the transaction code (for example, CS01 Create Material BOMs), the BOM header record contains header data.
With field BICSK-TCODE in structure BICSK, you determine the type of the bill of material and thus the SAP transaction to be called. You can enter the following values into this field:
- CV11 for document structures
- IB01 for equipment BOMs
- CS01 for material BOMs
- CS51 for standard BOMs
- IB11 for functional location BOMs
One item record for each item (structure BICSP, record type 2).
All BOM item records up to the next header record or session record are allocated to the BOM header read before.
One subitem record for each subitem (structure BICSU, record type 3)
All BOM subitem records up to the next item record, header record or session record are allocated to the BOM item read before.
Note
When you create a sequential file, you have to consider the following:
Fields that are not to be filled have to be transferred with their initial values.
If default values of the transaction are to be cancelled, a reset character "!" is to be transferred in the corresponding field. If you, for example, want to set the indicator for bulk material, you have to cancel the costing indicator if this indicator is set as a default by the transaction. Fields which contain a date are to be transferred in the external format according to the default values in the user master record. This does not include the date possibly entered in the session record. This date is always to be transferred in the internal format YYYYMMDD. In this case, YYYY stands for a four-digit year, MM for month and TT for day.
If you enter decimal values in fields which contain quantities or prices, the decimal point defined in the user master record is always to be used as decimal point. Procedure Extract the data to be transferred from the source system using the corresponding program and write the data into the sequential file in this case.
Start the conversion program in the SAP System. Enter the absolute path name under which the sequential file is to be found. A possible entries pushbutton with which a local file manager can be started is available to determine the path name. You have to consider that you can only access the file structure that exists on the presentation server via the file manager.
Determine the server from which the sequential file is to be imported. In this case, you can distinguish between your own application server, an external application server and the presentation server. If you want to import the sequential file from an external application server, you have to specify the server name. A possible entries pushbutton is also available here. Furthermore, you have to determine whether all bills of material to be copied or only the incorrect bills of material are to be collected in sessions. Refer to the log file of the data overview for a list of the created sessions.
Process the sessions to copy the bills of material into the system or reprocess the incorrect bills of material. Output
At the end, the data transfer program issues a log which lists all error situations that occurred when processing and the bills of material that were copied successfully. The log displays the possibly created sessions which can be processed afterwards. Example

Additional key words

Batch input

SAP Note 26040 - FF723 'Internal error in table SKFTABN'

Symptom:

FF723 'SYST: internal error in table SKFTABN' occurred under the following conditions:
- Postings are made to a company code with 'Tax base net'.
- In all items (thus also in the vendor items), the same tax code is explicitly specified (thus no blank and no **).
- The total of the vendor line items is zero (therefore the total of the G/L account line items must also be zero).
Example of such a document:
PKey Account Amount Tax
31 Vendor 100.00 V0
40 Expense 100.00 V0
21 Vendor 100.00 V0
50 Expense 100.00 V0

Cause and prerequisites
Solution
From the point of view of organization, split into invoice and credit memo or do not specify a tax code in the open item account line items (leave '**') or install the following advance correction

Additional key words

FB01, SAPMF05A, SAPLTAX1, determine cash discount

SAP Note 26040 - FF723 'Internal error in table SKFTABN'

Symptom:

FF723 'SYST: internal error in table SKFTABN' occurred under the following conditions:
- Postings are made to a company code with 'Tax base net'.
- In all items (thus also in the vendor items), the same tax code is explicitly specified (thus no blank and no **).
- The total of the vendor line items is zero (therefore the total of the G/L account line items must also be zero).
Example of such a document:
PKey Account Amount Tax
31 Vendor 100.00 V0
40 Expense 100.00 V0
21 Vendor 100.00 V0
50 Expense 100.00 V0

Cause and prerequisites
Solution
From the point of view of organization, split into invoice and credit memo or do not specify a tax code in the open item account line items (leave '**') or install the following advance correction

Additional key words

FB01, SAPMF05A, SAPLTAX1, determine cash discount

SAP Note 26039 - Change to organizational level/forecast profile

Symptom:

When displaying a material, you select "Edit -> Organizational levels". This can result in the following problems, the first of which can also occur if you change a forecast profile and update the materials concerned by a background job:

1. You display the forecast values and then the material for another
plant. If you now also display the forecast values for this plant,
the values for the first plant are displayed and then those for the
second plant.

If you change a forecast profile or a MRP profile the subsequent
updating of the materials concerned by background job can result in
these materials receiving the forecast values of the first material
updated by this job.

2. You display the MRP data for a plant in which a lot size (materials
planning) is specified. You then want to display the MRP data for a
plant for which no lot size is specified. The system thereupon
issues termination message M3 287, "Lot size is not defined".

3. You display the sales/plant data for a plant in which an
availability check is defined. You then display this data for a
plant for which no availability check is defined. However, the
short text for the availability check is not reset.

4. You choose a new sales organization or a new distribution channel on
the Sales Text screen. The long text is not then updated.

5. You display the data on the Sales 1 screen for a combination of
sales organization/distribution channel for which a delivering plant
is maintained. You then display this data for a combination of sales
organization/distribution channel for which the delivering plant is
not maintained. However, the short text for the delivering plant is
not reset.

Cause and prerequisites

Program error

Solution
Problems corrected in Release 3.0B.

Additional key words

Transactions MM03, MM01, MP81; programs: SAPMM03M, RMMM0001

SAP Note 26033 - 3.0 GUI and 3.0 Help screens are not connecting

Symptom:

3.0 GUI and 3.0 Help screens are up. Running Windows frontend. Cannot get the GUI and Help screens to connect. The documentation mentions a file SAPDOCCD.INI that is required to do this however it does not mention where this file should be.
Receive message saying no documentation available.

Cause and prerequisites

Put problem

Solution
We have exported the tables to the transport order K000313 and put it
it to the sapserv4. Please use the error note 13719 to import to your
system. The directory on sapserv4 is /dist/permanent/olin.

SAP Note 26027 - Converting PReq into purchase order: Dialog indic.

Symptom:

When you convert a purchase requisition into a purchase order, the system issues warning message 06240 ´Requisition has different doc. type & and item category >&<´. However, the purchase requisition to be converted has document type NB and no item category just as the purchase order to be created. The warning message is only ignored after pressing the ENTER key twice.

Cause and prerequisites

Table T161A determines the copy rules of different purchasing document types. The dialog indicator causes that a warning message is issued during the copying procedure. Table T161A in the customer system contains an entry in the form NB 0 F NB 0 >< >< X

Solution
Please cancel the dialog indicator using transaction OMEB or by editing table T161A with transaction SM31.

Additional key words

T161A, purchasing document type, reference to purchase requisition

SAP Note 26024 - Special payments: start retro. run for EE leaving

Symptom:

If an event that affects payment is entered in the payroll future, a retroactive run is not performed from the point in time of the general payment of the special payment.

Cause and prerequisites

The general retroactive accounting logic is only activated if master records are entered in the payroll past.

Solution
Please start the general retroactive accounting logic as follows using an infotype 0015 record (Additional Payment). To do this add table
entries in table T588Z:

Inft Subt Field Op No I Variable function part
------------------------------------------------------------------------
0000 MASSN 06 1 *------ RUECKRECHNUNG SONDERZAHLUNG --------
0000 MASSN 06 2 P T001P-MOLGA='03'
0000 MASSN 06 3 P P0000-MASSN='10' a)
0000 MASSN 06 4 P P0000-MASSG='01' b)
0000 MASSN 06 5 P P0000-BEGDA+4>='0801' c)
0000 MASSN 06 6 I INS,0015
0000 MASSN 06 7 W P0015-BEGDA(4)=P0000-BEGDA(4) d)
0000 MASSN 06 8 W P0015-BEGDA+4='0801' e)
0000 MASSN 06 9 W P0015-LGART='X100' f)
0000 MASSN 06 10 W P0015-BETRG='1'

a) This is the event that can start a retroactive accounting run
b) This is the event reason that can start a retroactive run
c) The dynamic event is only activated for records entered after
the date (here: August 1).
d)e) Retroactive run is started on date (here August 1).
f) The wage type is a user-defined marker wage type and should be
coded in table T512W in such a way that it does not affect the
accounting results in any way.

SAP Note 26019 - FI-SL Customizing: Ledgers are not displayed

Symptom:

In FI-SL Customizing, certain ledgers are not displayed or cannot be edited.

Cause and prerequisites

When preparing the configuration for the Extended General Ledger (FI-SL), the ledgers in question (locally or globally) are not activated.

Solution
Before Release 3.0:
In the FI-SL configuration menu, choose 'Environment' -> 'Preparation' and activate the corresponding ledgers.

As of Release 3.0:
Business Engineering -> Customizing -> SAP Reference-IMG ->
Financial accounting -> Spec. Purpose Ledger -> Global settings ->
Carry out preparation

Additional key words

Error message GC810

SAP Note 26018 - Problems when creating relationships in relat. list

Symptom:

If you create a relationship using the 'Create' function in the relationship list and if this relationship is assigned to an external network, it is possible that a termination occurs.

Cause and prerequisites

The pointers on internal tables are not the same.

Solution
Set up the tables again.

SAP Note 26010 - Authorization class AC in transaction table

Symptom:

Customer would like to assign an separate authorization class (instead of the constant AC) to different control tables of Asset Accounting.
However, the allocated transactions always have 'AC' as authorization for authorization object S_TABU_DIS.

Cause and prerequisites
Solution
Change the authorization for the check object of the table in question with transaction SE93.
In Release 3.0B, The authorizations are removed from the check object of the Customizing transactions.
Caution: This requires, of cocurse, that you have already assigned the new authorization to the individual tables in table TDDAT.

Additional key words

Customizing, authorization, OA25

SAP Note 26009 - R/3 System does not print, first steps

Symptom:

All output requests go into the status "Waiting for the editor", "Unknown" or "Output device cannot be reached".

Cause and prerequisites

There are numerous causes.

Solution
    1. A new installation or an update was carried out and nothing has been printed successfully so far.
      a) Submit the command "hostname" on the operating system side and compare the result with the contents of transaction SM51. If a difference exists, please refer to notes 9076, 24485 and 21151. Check this out with your network administrator.
      b) All output requests go into the status "unknown". Simply store your printers again. However, a similar case to a) has probably occurred.
      c) Whenever the output requests go into the status "Output device cannot be reached" or similar and communication method "U" or "S" isused for these devices, please refer to note 25941. As an immediate action, you can make an entry in the Table THOST according to Note 10743.
    2. Printing has already been carried out successfully.
      a) Please go through all the spool requests in SP01. Look for the first spool request with the status "Waiting", "In process" or "Error". Then go into transaction "SM50," choose "Restart after error-no" and then terminate the spool work process. Then delete the corresponding output requests. You can then restart the spool work process. Take a note of the printer name.

a1) The printer is defined with communication method "U" or "S". This is a non-secure network printer or a PC which is often switched off. The best thing to do is set this printer up remotely via the host spool of the R/3 spool server (local "L" or "C" communication method).

a2) The printer is defined using communication method "L". In this case the UNIX print command or lpstat command is stuck. In the first case, you should block this printer from the SAP System and reactivate the printer from UNIX. In the second case, you should deactivate the query for the host spool.

For communication method "L", the print command must work. Check this by printing a small file as adm user on Unix, using the exact command stored in the RSPO/HOST_SPOOL_PRINT parameter. (You can also log the print command in the same way as method 2 using Note 5799 to see which exact command is transmitted from R/3). If the command does not work, this is due to an operating system issue.

For print requests with "Error" status, you should also look out for system log messages.
For the message "Name of destination host unknown", refer to Note 25941.
If your requests stop with the status "Waiting", refer to Note 65109.

SAP Note 26004 - Stock bal. display: GR blocked stock or open PO qty

Symptom:

In the stock balance display, you specify a material and a unit of measure other than the base unit, and then choose "New selection". The quantity of goods receipt blocked stock and/or the open purchase order quantity that is then displayed is, however, incorrect.

Cause and prerequisites

This error can occur if the order unit differs from the base unit of measure, particularly if the differing order unit is maintained in the purchasing info record.

Solution
Problem corrected in 2.2G and 3.0B.

Additional key words

Transaction: MMBE; program: RMMMBEST; fields: WESPB, MENGE, MENGK

SAP Note 26002 - Cust.enhance 1 of results analysis, doc.enhance

Symptom:

Problems in handling customer enhancement 1 (user exit) of results analysis.

Cause and prerequisites

Missing documentation

Solution
Description of customer enhancement 1.

Customer enhancement 1 has been available since Release 2.2B. The interface has been enhanced for maintenance levels 2.2F, 3.0E, 3.0F and 4.0A.

Customer enhancement 1 has two applications:

  • On the one hand, the customer can add to the standard selection. This makes sense if his or her method deviates only a little from one of the methods displayed in the standard system. Here, the corresponding method in Customizing is chosen. The program imports all data, calculates the values according to the selected standard method, branches to the customer enhancement and carries out the individual, additional calculations programmed by the customer, branches back and saves the data.
  • On the other hand, the customer can program a method in the enhancement that deviates completely from the standard system. In this case, it is best to choose the final results analysis setting in Customizing. The program imports all data. All actual costs are copied to the sales costs. It branches to the customer enhancement; there the calculations predefined by the customer are carried out, it branches back and the data is saved.

To use customer enhancement 1, you must execute several actions:

  • Include the customer enhancement using Transaction CMOD.
    • Create a project; this is not a project from the SAP Project Management System.
    • Assign the SAP enhancement KKAG0001 to the project.
    • Choose the component EXIT_SAPLKKAG_001 from this enhancement; this is a function module.
    • The function module contains the Include module ZXKAGU01. Branch to this include and maintain your program code there.
    • When your module is complete, activate the project.
    • After transport, you must regenerate the function group in the target system. For this purpose, call function module EXIT_SAPLKKAG_001 in the ABAP/4 Function Library of the ABAP/4 Development Workbench and choose 'Function module > Gen. function group'.
  • Branch to the Customizing of results analysis and choose the maintenance of the valuation methods. On the detail screen, a letter is to be entered in the 'UsrFtn 1' field (user-defined function 1), which is also copied to the function module. If this field is empty, the module will not be activated.

Interface of the function module EXIT_SAPLKKAG_001:

Import parameters
ABGRENZUNGS_SCHLUESSEL Results analysis key
ABGRENZUNGS_VERSION Results analysis version
STEUERUNG_KUNDENERWEITERUNG_1 Control cust.enhancement 1/val.method
BEARBEITUNGS_GJAHR Fisc.year of res.analysis accounting
BEARBEITUNGS_PMONAT Period (month) of res.anal.accounting
BEARBEITUNGS_WAEHRUNG Currency of res.analysis accounting
COEP_KOKRS Controlling area
COEP_BUKRS Company code
AUFK_AUFNR Order number
PRPS_PSPNR Internal project line item number
PRPS_POSID Work breakdown structure element
VBUK_VBELN Sales and distribution document no.
VBUP_POSNR Line item no. of SD document
OBJEKTNUMMER Cost element itemization number
BASIS_PLANMENGE Planned quantity
BASIS_ISTMENGE Actual quantity

Table parameters for data import
IMPORT_ABGRENZUN Table w. values fr. calc. of imputed costs
determined automatically
IMPORT_BASIS Table w. actual + plan. values for valuation

Table parameters for data download
EXPORT_VERAENDER Table w. changes to values from calc. of
imputed costs

Exceptions
FEHLER_MIT_NACHRICHT Error with message from this module
FEHLER_OHNE_NACHRICHT Error w/o message from this module

The meaning of the import parameters is self-explanatory to a large extent. The 'STEUERUNG_KUNDENERWEITERUNG_1' parameter contains the content of the 'UsrFtn 1' field of the valuation method detail screen. The program flow in the function module can be controlled this way. The values of the imported and the exported tables relate to the year 'BEARBEITUNGS_GJAHR' and the period 'BEARBEITUNGS_PMONAT'.

The table 'IMPORT_ABGRENZUN' imports the values determined by automatic results analysis to the function module. The table 'IMPORT_BASIS' imports the actual and planned values.

The table 'EXPORT_VERAENDER' exports the change to results analysis data determined by the function module. That is, this table is empty if no data has been changed.

Error-related exceptions for extraordinary returns from the function module can be programmed with the statements

  • MESSAGE E300 WITH <... 2> <... 3> <... 4> RAISING FEHLER_MIT_NACHRICHT
  • RAISING FEHLER_OHNE_NACHRICHT


The tables of the interface have underlying structures. In the definitions of the specified domains, a list with fixed values is predefined in each case, the meaning of which is also explained there. The ZLNID field is an exception; its allowed values are defined in the 'Update' table in Customizing. The description 'Period value' refers to the change to a value in the period to be processed. The 'Cumulative value' is the total of all period values, totalled across all periods earlier than or equal to the period to be processed.

The table 'IMPORT_ABGRENZUN' has the structure 'XKAABGR'. The first three fields are the key fields.

Field Domain Meaning
ABGTY ABGR_ABGTY Results analysis form
AWKUS ABGR_AWKUS Transaction Creation/usage/balance
ZLNID ZEILEN_ID Line ID
ABGRKUMKG Accumulated value, total
ABGRKUMKF Accumulated value, fixed portion
ABGRJHRKG Annual value, total
ABGRJHRKF Annual value, fixed portion
ABGRPERKG Period value, total
ABGRPERKF Period value, fixed portion


The table 'IMPORT_BASIS' has the structure 'XKABASIS'. Only the first field is a key field.

Field Domain Meaning
ZLNID ZEILEN_ID Line ID
BEWKZ ABGR_BEWKZ Valuation indicator
KATEG KATEGORIE Category
ISTKUMKG Accumulated actual value, total
ISTKUMKF Accumulated actual value, fixed portion
ISTPERKG Actual period value, total
ISTPERKF Actual period value, fixed portion
ISTJHRKG Annual value, total
ISTJHRKF Annual value, fixed portion
PLANBEWKG Overall planned value, total
PLANBEWKF Overall planned value, fixed portion
ISTMNGKUM *** currently not used ***
ISTMNGPER *** currently not used ***
PLANMNG *** currently not used ***


The table 'EXPORT_VERAENDER' has the structure 'XKAVABGR'. The first three fields are the key fields.

Field Domain Meaning
ABGTY ABGR_ABGTY Results analysis form
AWKUS ABGR_AWKUS Transaction Creation/usage/balance
ZLNID ZEILEN_ID Line ID
ABGRVERKG Change of a value, total
ABGRVERKF Change of a value, fixed portion

Additional key words

The description 'Work in process calculation' is also used instead of the description 'Results analysis'.

Keyword: EXIT_SAPLKKAG_001, KKAG0001, ZXKAGU01, KKA3, KKA2