SAP Note 14203 - Table T399X cannot be maintained via OS35 and SM31

Symptom:

If a customer creates a new client, it may occur that table T399X is empty or incomplete. However, you cannot enter new entries with Customizing transaction OS35 or maintain them via transaction SM31.

Cause and prerequisites

The table was not copied.

Solution
Please use transaction COTB to copy data from client 00. In case it does not exist, use transaction SM29 with command file P21A_c_SFC.

SAP Note 14154 - Batchinput on IW31 IW34: operation code VGD3

Symptom:

After operation code VGD3 system sets screen 'Internal Processing'
instead of 'Operation Date'

Cause and prerequisites

Before setting screen 'Operation Date' the screen 'Internal Processing'
is processed in the dark (ABAP-Syntax: 'SUPPRESS DIALOG') to
guarantee full data consistancy.
In case a dialog message has to be sent the screen 'Internal Processing'
appears. But this means an unpredictable system behaviour which is
crucial to batchinput.

Solution
For any operation item operation code VGD1 and VGD2 has to be
processed before VGD3 is executable in batchinput mode.

Key word: VGD3

SAP Note 14149 - Interactive lists in a pop-up

Symptom:

Key word: Lists. If a list is issued from a dialog box window (LEAVE TO LIST-PROCESSING after CALL SCREEN STARTING AT ... ENDING AT) a branching list for this list is output in full-screen mode - that is, in the size of the primary window and not in the size of the basic list

Cause and prerequisites

For technical reasons, branching lists are also output as Call Screen.

Solution
None

SAP Note 14136 - Pricing procedure for credit memo with reference

Symptom:

When creating a credit memo with reference to a billing document, the pricing procedure is copied but with reference to an order it is not. We find it necessary that the pricing procedure be also redetermined when a credit memo is created with reference to a billing document.

Cause and prerequisites

It is programmed this way but it can be changed during system configuration. Due to reasons of compatibility, the standard routine cannot be changed.

Solution
Create a new data transfer routine for orders using transaction VOFM. The number of the routine should be within the user area, for example 952.
In order to avoid the pricing procedure being copied, the routine
should look as follows:


FORM DATEN_KOPIEREN_952.

LOCAL: VBAK-KALSM. " Don't copy the pricing procedure

perform daten_kopieren_052. " Standard field transport

ENDFORM.


Save and activate the routine.
Enter the number of the routine in the copying control (instead of
052). (Sales - Define Document flow - Define document flow for
billing document to sales order)
Important:
Please note that using you own routine for data transfer is a
modification that is not maintained by SAP. Refer also to Notes
170183 and 381348.

SAP Note 14134 - Problems during the output determination

Symptom:

Often the "wrong" layout set is used during the output determination.

Ex.: For other goods receipt, movement type 501 (goods receipt without purchase order), a different layout set is used than for a goods receipt to purchase order (MB01, movement type 101) if the order collective goods receipt/issue slip is selected. This can also be the case for other types of goods receipt/issue slips.

Cause and prerequisites

Providing all settings are correct, this can have two reasons:
1. The access sequence 0003, which is assigned to the condition types WE01, WE02, WE03, WA01, WA02, WA03, is followed by a table (standard 72) that contains the transaction/event type in the key.
2. The transaction/event type is not assigned to the movement type, for example 101 or 501, but 1 : 1 to the transaction. As a result, MB1C and MB1A, for example, have the transaction/event type GI.

Solution
You should first check the results determined by the system. You can do this on the overview screen via Goto -> Details from item... Via Goto -> More functions -> Output, you can also use an analysis on the following screen.
Ex.: The output type WA03 is used for 'Other GR' with movement type 501. However, you want output type WE03. Then proceed as follows:

- Create a new item type with OMBR, for example 9.
- Assign this item type to movement type 501 with OMB5.
- Create a record with key transaction/event type = GI, print version = 3 (for collective slip) and print item = 9 for the condition type WE03 in the condition table(s) (table 72 in standard 0003) which is assigned to the access sequence.

This example refers to standard settings!

Additional key words

Document types, Transaction

Key word: Output

SAP Note 14121 - Using parallel reports

Symptom:

Question: What is to be considered when using parallel reports?
Key word: Report Writer

Cause and prerequisites

Parallel reports do not support the entire functionality.

Solution

The report page in a parallel report is divided into several windows. One report is allocated to each window. This leads to the following restrictions due to technical reasons:

1. If you scroll in the report display, this only applies to the current window (cursor position).

2. The export onto the PC is only possible in the text format. For this reason, numbers cannot directly be exported into spreadsheet cells (MS Excel, Lotus 123, ...).

3. Selection variation is not supported.

Parallel reports can often be avoided by deacitvating the unwanted column blocks for certain row blocks. This way, the report can be set up from different blocks.

Additional key words

----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_REPORT_RW, SGRW_REPORT_RP,
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS

SAP Note 14118 - Authorization: Payroll acc. with remuneration stat.

Symptom:

The user only has read authorization for cluster PCL2.
Report RPCALCx0 is started with parameter NOUPD or the schema used contains function 'UPD NOUP'. Furthermore, the schema contains function 'XEDT' for the output of an additionally remuneration statement via report RPCEDTx0.
Two cases are to be distinguished:

1. There are not yet any payroll results on PCL2 for the accounted period in the test run.

--> No remuneration statement is output.

2. Payroll results exist for this period.

--> A remuneration statement is output, however, it contains the old payroll results!
Cause and prerequisites

All database changes (PCLx) are first carried out in a buffer. This buffer is read by successor programs (here RPCEDTx0).
However, the authorization check has already been carried out when the buffer is changed. If the change authorization for PCLx is missing, the buffer is not changed.

Solution
Assign write authorization for the users involved.

Additional key words

Authorization

SAP Note 14116 - Runtime error CONVERT NO_NUMBER in UNIT_CONVERSION

Symptom:

Runtime error CONVERT_NO_NUMBER in function module
UNIT_CONVERSION: a CHAR field cannot be converted to FLTP, because exponent "E-+55" or something similar.

Cause and prerequisites

UNIT_CONVERSION is unable to process 3 digit exponents.

Solution
- Usually, no numbers with 3 digit exponents occur in the
application.
Apply note 10738 first.
- Should the error occur again, use a function module of group
SCV0 (UNIT_CONVERSION_SIMPLE, CONVERSION_FACTOR_GET) in the
requesting program instead of UNIT_CONVERSION. If you want to
convert depending on the material master, use function module
MATERIAL_UNIT_CONVERSION .

In order to find the name of the requesting program, read the dump
(list of active calls/events).
The change should be carried out by the developer responsible
for the application.

Key word: SAPLSMUN

SAP Note 14104 - PS struct.report: Master data texts longer than 30

Symptom:

In costs structure reports, master data texts could only be displayed up to length 30.

Cause and prerequisites

Restricted length of the set text.

Solution
see note: 27053

Key word: Information system

SAP Note 14097 - Order item cannot be deleted/overwritten

Symptom:

1. An item from make-to-order production cannot be deleted from a sales order. A dialog box appears with message V1128: "For reasons of cost management, item & cannot be deleted".

2. It is not possible to overwrite the material number, item category or plant of an order item.

Cause and prerequisites

There are several reasons why an order item can no longer be deleted or the material number, item category and plant of an item may no longer be overwritten.

a) Subsequent documents already exist for an order item.

b) It is a make-to-order production, i.e. costs for the item may have already accrued.

c) It is an item with account assignment to a project, i.e. costs for the project may have already accrued.

d) It is an item with BOM explosion.

Solution
1.)
Assign a reason for rejection to the item. This reason for rejection is equivalent to a logical deletion of the item. As of Release 3.0, fine tuning for the reason for rejection is possible. This fine tuning allows you, for example, to control whether the item is printed. Please see also note 9678.

Corrections in 3.0E and 3.0F (see appendix)
You can install these corrections only as of 3.0C at the earliest.
In case b), which does not allow a deletion because of the cost management, a check is made whether costs have already been accrued. The deletion is allowed if no costs have been accrued yet. If costs have been accrued, message V1128 will still be displayed.
In this case, also install note 74083. Note that, by installing note 74083, parts of the source code changes in this note are changed again.
If you want to delete order items with configurable materials, you will always have to implement note 61265.
During deletion, if order items with assembly orders or prodution orders are affected also apply note 86797 and if necessary Note 93627 too.

Case c) is not solved by the corrections. The only way to deactivate the item is to set a reason for rejection.

Additional key words

VA02, item exchange, make-to-order production, E128

SAP Note 14089 - Insert Duprec during creation

Symptom:

When you create a material BOM, an insert duprec occurs when you insert in table STZU (Include LCSVBF10).

Cause and prerequisites

Incorrect number range status of number range object STUEM.
The reason for this may be a previously performed client copy.

Solution
Run the following report:

REPORT ZZSTZU01:

TABLES: STZU.

SELECT * FROM STZU
WHERE STLTY = 'M'.

WRITE: / STZU-STLNR.

ENDSELECT.

Then call transaction SNUM and enter number range object STUEM.
Then Goto -> Number ranges and click on button "Change status".
Change the number range status to the last value displayed
by the report.

Additional key words

Create

Key word: CS01

SAP Note 14074 - No delete function for functional locations

Symptom:

There is no user function for deleting functional locations.
Reorganization of technical locations is not possible.

Cause and prerequisites

Not yet programmed.

Solution
- The reorganization program for PM master data will be delivered with
release 3.0B.
- Normally, functional locations are not deleted, even when they
have been taken out of operations. This is because assets that
no longer exist may also be interesting for error statistics.
- The need to delete a location usually only results from incorrect
entries.
- Until a delete function is available, you can do the following:
* Create a location with the meaning "logical scrap value"
* Reassign the locations for logical deletion to the above location
(function: "change higher level location").
--> These locations will no longer interfere with the structure
list.
* If necessary, initialize the data fields in these locations
--> No further match codes will thus be built.

Key word: Delete location

SAP Note 14070 - PRINT-CONTROL in online lists

Symptom:

A report contains PRINT-CONTROL statements. When you
execute the report online, the PRINT-CONTROL statements have no effect.

Cause and prerequisites

The PRINT-CONTROL statement only has an effect during printing - e.g.
when starting a report with "Execute and print", in SUBMIT ...
TO SAP-SPOOL, and after the statement NEW-PAGE PRINT ON. When a list
is output to the screen, the statement is ignored.

The "Print" function in the display of an online list is only
suitable for "test" printouts. The list (which was actually formatted
for screen display) is output on a printer in its present form.
Problems in this printout:
- The online list normally consists of one long page. The page must
be divided into separate pages; in the process, the page header
is copied to the start of each printed page. As a result, page
number 1 generally appears at the top of each page. For this
reason, a value for the page number is displayed in the footer
(in long lists).
- The online list is normally as wide as the user window. The
window size is often changed by the user. As a result, each
printout will have slightly different formatting.
- When the print width is less than the page width, lines will
be cut off at the end.
- The online list does not contain any information on print control
from the PRINT-CONTROL statements.

Solution
Print with "Execute and print", SUBMIT ... TO SAP-SPOOL, or
NEW-PAGE PRINT ON

Key word: ABAP/4 printing

SAP Note 14068 - Log: Error when converting into other quantity unit

Symptom:

The message 'Error when converting into other quantity units' (message C7023) is written into the scheduling log when none of the standard values has a unit of time as its unit of measure.

Cause and prerequisites

During scheduling the operation duration is calculated using a formula
in a unit of time, that can be derived from the units of time of the
standard values.

Solution
At least one standard values must have a time unit.
Note: When calculating the duration using the formula, the system
first converts all standard values into the corresponding
SI unit. This value is then put into the formula. The result
is interpreted as a value in seconds which is then converted
into the time unit of the result.

Key word: Scheduling

SAP Note 14040 - Error during planning period calculation

Symptom:

Program: SAPMM61X
Error ID: 123
The materials planning in transaction MD01, MD02 or MD03 terminates with error message 61123 'Error determining planning periods calendar &'.

Cause and prerequisites

This may be due to several reasons:

1. The planning calendar is insufficiently maintained. There are MRP items (requirements, planned orders, production orders, purchase orders, and so on, ... ) with a requirements date or an input date before or after the period that is defined in the planning calendar.

2. Program error in Releases 3.0F and 3.1G. The program error only occurs if you are working with planned finish = period end in the lot-sizing procedure.

Solution

1. Check the requirements dates and delivery dates of the MRP items of the material in question with the current stock/requirements list in transaction MD04. Enhance the calendar with transaction MD26 'Change Planning Calendar' so that these dates will be considered.

2. Implement correction P30K141474.

Additional key words

E61123

Key word: Planning period

SAP Note 14034 - SQL error "INF-908: Attempt to connect...failed."

Symptom:

The connection via the network to the database ('remote connect') can (no longer) be established. The following symptoms can occur:

1. Starting the R/3 System using 'startsap' terminates with the error message:

R3trans test connect to the database failed
Return code: 12

The explicit checking of the connection to the database using 'R3trans -d' terminates with the error message:

2EETW169 no connect possible: "DBMS = INFORMIX --- ...

In the log file of the R3trans you can find entries of the type:

***LOG (BY2): sql error -908 performing CON
***LOG (BY0): INF-908: Attempt to connect to database server
() failed.

2. The R/3 processes cannot correctly log on to the database. In the R/3 trace files (2.xy: 'dev_db*'; 3.xy: 'dev_w*') you can find entries of the type:

***LOG (BY2): sql error -908 performing CON
***LOG (BY0): INF-908: Attempt to connect to database server
() failed.

Cause and prerequisites

This error occurs if the combinations of IP address and port number used for the communication by application program ('client') and database ('server') do not correspond to each other.
If the client sends a message to a combination of IP address and port number which is not 'received' by the server, then this message remains unanswered, and the client terminates after some time with the symptom described above.

Solution

To solve the problem you must synchronize the selected IP addresses and port numbers of client and server. The selection is made as follows:

1. Client

Procedure

a) First the client interprets the environment variables INFORMIXSERVER and INFORMIXSQLHOSTS and scans the file defined by INFORMIXSQLHOSTS for the first line whose first word corresponds to the value of INFORMIXSERVER. The third word of this line is used as hostname, and the fourth word as servicename.

b) The client scans the file /etc/hosts for the first line whose second word corresponds to the hostname. The first word of the found line is interpreted as IP address of the server.

c) The client scans the file /etc/services for the first line whose first word corresponds to the servicename. The second word of the found line is then interpreted as port number of the server followed by the log type.

d) The client now sends its database requests in accordance with the entered log type to the respective port number of the IP address determined.

Example:

a) Environment variables

...
INFORMIXSERVER = dbhost01c11tcp
INFORMIXSQLHOSTS = /informix/C11/etc/sqlhosts.soc
...

b) File /informix/C11/etc/sqlhosts.soc:

...
dbhost01c11tcp onsoctcp dbhost01 sapinfC11
...

c) File /etc/hosts:

...
123.45.67.89 dbhost01
...

d) File /etc/services:

...
sapinfC11 3800/tcp
...

Now the client sends its database requests via tcp to the port number 3800 of the IP address 123.45.67.89.

Problems:

If one of the errors described under symptoms occurs, then check the following:

a) The host name must be unique in the file /etc/hosts. Different IP addresses can only be called via different hostnames.

b) The service name must be unique in the file /etc/services. Different port numbers can only be called via different service names.

2. Server

Procedure:

a) During the start the database server reads the values of parameter DBSERVERNAME and DBSERVERALIASES from the configuration file $INFORMIXDIR/etc/$ONCONFIG. With each of these dbservernames it proceeds in the same way as the client with the INFORMIXSERVER (determination of hostname, service name, IP address and port number).

b) For every pair of port number and IP address determined this way which want to access via a network protocol (for example tcp), the database server starts a listen thread, which checks the network address assigned to it for incoming database requests and therefore makes communication possible.
With the command 'onstat -g ntt | grep lst' you can check which combinations of port number and IP address are processed by the database server.

c) Accesses to the database via different network cards can thus be realized via different dbservernames and corresponding entries in $INFORMIXSQLHOSTS.

Example:

a) File $INFORMIXDIR/etc/$ONCONFIG:

...
DBSERVERNAME dbhost01c11shm
DBSERVERALIASES dbhost01c11tcp,dbhost02c11tcp
...

b) Environment variables

...
INFORMIXSQLHOSTS = /informix/C11/etc/sqlhosts.soc
...

c) File /informix/C11/etc/sqlhosts.soc:

...
dbhost01c11shm onipcshm dbhost01 sapinfC11
dbhost01c11tcp onsoctcp dbhost01 sapinfC11
dbhost02c11tcp onsoctcp dbhost02 sapinfC11
...

d) File /etc/hosts:

...
123.45.67.89 dbhost01
123.45.67.90 dbhost02
...

e) File /etc/services:

...
sapinfC11 3800/tcp
...

In each case the server starts a listen thread for the pairs
- Port number 3800 of IP address 123.45.67.89 and
- Port number 3800 of IP address 123.45.67.90
and can thus process database requests of two network cards.

Problems:

If one of the errors described under symptoms occurs, then check the following:

a) Each hostname used must be unique in file /etc/hosts. Different IP addresses can only be called via different hostnames.

b) Each service name used must be unique in the file /etc/services. Different port numbers can only be called via different service names.

c) All combinations of port number and IP address used by clients must be processed by the server. If necessary, extend or modify the file $INFORMIXDIR/etc/$ONCONFIG, $INFORMIXSQLHOSTS, /etc/hosts and /etc/services correspondingly. After a modification of these files you must restart the database so that the changes become active.

d) The hostname and the corresponding IP address of the client must be known under the same name on the server. Otherwise, the response from server to client cannot be sent and received correctly.

Additional key words

STARTSAP, R3TRANS, CONNECT, INF908, HOSTS, SERVICES, INFORMIXSERVER,
INFORMIXSQLHOSTS, DBSERVERNAME, DBSERVERALIASES, ONCONFIG, INFORMIXDIR

SAP Note 14032 - Payables consignment in local currency

Symptom:

The list of payables from the consignment stores are displayed in
the currency of the company code and not in the currency of the
purchase order.

Cause and prerequisites

Programmed this way

Solution
Functionality is not yet available.

Key word: MRKO

SAP Note 14029 - Fiscal year change AM / RAJABS00 -> EM EAU037

Symptom:

When carrying out a fiscal year change (RAJABS00), error message EAU037 is displayed:
EAU037:" Asset &-& in company code & : Error in determining the base ins. value". When double-clicking on the long text, the actual error message cannot immediately be recognized. (-> periodic processing -> incorrect asset)

Cause and prerequisites

Error in documentation.

Solution
Unfortunately, the long text for the error message does not contain the actual cause. This can be found via Master data - Display => scroll forward to the insurance data. Then choose Edit - Fiscal year change insurance value. The system then gives the actual error, for example, that the index series is not maintained for 1994.

Additional key words

year-end closing RAJABS00

SAP Note 14028 - Error message AA660 or 632 during retirement/transfer

Symptom:

When posting a partial retirement or a partial transfer, error messages AA632:
'Line items reduce the cut-off value by &'
or AA660:
'Transaction in area & contradicts the net book value rule',
are given, if the transferred fixed asset has already reached the memo value or cut-off value.
The error message especially occurs, if the memo value is very low (1 cent) or if the indicator for rounding the net book value corresponds to the memo value (memo value 1,00 and rounding the net book values with two places behind the decimal point).

Cause and prerequisites

The rounding-off indicator or the memo value do not leave any room for rounding-off the depreciations.

Solution
Until the rounding-off differences are cleared automatically for these special cases, you have to write up.
The write-up amount depends on the retirement amount and can be determined as follows:
Retirement 50 % - Write-up amount = Memo value
Retirement 33 % - Write-up amount = 2 x memo value
Retirement 25 % - Write-up amount = 3 x memo value
Retirement 1/n - Write-up amount = (n-1) x memo value

Key word: Retirement/transfer

SAP Note 14005 - Eval. of cost element characteristics in the report

Symptom:

The attribute fields of the cost elements are to be evaluated.

Cause and prerequisites

Is not provided in standard reporting.

Solution
The customer can define own reports. To do so, field EIGEN from reporting table CCSS must be used for the definition of the reports.

Key word: attributes

SAP Note 14004 - Description of the call options for BRRESTORE

Symptom:

Parallel restoration of the database and archive logs

Other terms

BR*Tools

Reason and Prerequisites

Support for restoring the entire database
Support for parallel restoration from multiple tape drives
Support for restoration into other target directories

Solution
BRRESTORE is bundled directly in SAPDBA as of Version 3.0. The program, however, can also be used directly or interactively if you are using an older version of SAPDBA (< 3.0) or if the restore using SAPDBA is denied or fails for other reasons:

Call options of BRRESTORE
-----------------------------

With BRRESTORE, you can restore parts of, or an entire database backup from an offline or online BRBACKUP backup, including files unrelated to the database and directories of which a backup was made.
The subdirectories in sapdata directories are automatically created if they do not already exist.
You can also restore the Redo log files stored with BRARCHIVE (possibly at the same time as restoring the database).

BRRESTORE supports the following call options:

[-a|-archive|-a1|-archive1 [=]|-
[=]|]
,- - Log sequence number of Redo log files, which are to be restored from the first copies of the offline Redo log files.
- Restore directory into which the Redo log files are to be restored, otherwise the original directory is used.

[-a2|-archive2 [=]|-
[=]|]
,- - Log sequence number of Redo log files, which are to be restored from the second copies of the offline Redo log files.
- Restore directory into which the Redo log files are to be restored, otherwise the original directory is used.

[-b|-backup |last]
- Name of the BRBACKUP log file used for restoring the database, "last" - the last successful backup default: last.

[-c|-confirm]
Unsupervised mode - in contrast to BRBACKUP/BRARCHIVE, only tape mount confirmations are suppressed. All other BRRESTORE confirmation requests must be answered.

[-d|-device tape|tape_auto|disk|pipe|pipe_auto|util_file]
Device type for restoring. Default: tape.

[-h|-help [version]]
Help info about the BRRESTORE options (Version of BRRESTORE).

[-k|-compress [no|yes|hardware]]
Type of compression - if software compression was activated for the backup, you should use "yes". BRRESTORE does not differentiate internally between "no" and "hardware." Default: no.

[-l|-language D|E]
Language in which BRRESTORE messages are issued, "D" - German, "E" - English. Default: E.

[-m|-mode all|full|[=]|
[=]|-[=]

List of the objects (tablespaces, database files, files or directories not related to the database) to be restored.
"all" restores all the tablespaces without control files or online Redo log files.
"full" restores the entire backup including files not related to the database, directories, control files and online Redo log files.
refers to the Oracle file ID for data files. File ID 0 identifies the control file.
IDs with leading zeros - Online Redo log files.
If is a complete path name, one database file, one file not related to the database or one directory is restored, otherwise must at least include Oracle home.
In this case, the system selects all the database DATA files whose name starts with this path.

- Restore directory to which the files are restored, otherwise the original directory is used.
is a list of the tablespace/file specifications separated by commas.
Default: all.

[-n|-number |init_ora|init_sap|reorg_log|det_log|sum_log]
[=]
This option is only supported for:
backup_dev_type = tape | tape_auto | pipe | pipe_auto
You can use this option to restore a file directly from tape (without specifying the log name of the backup or the log sequence number).
Specify the position of the file on the tape.
- Position of the file on the tape.
init_ora - init.ora is restored, corresponds to position 2.
init_sap - init.sap is restored, corresponds to position 3.
reorg_log - reorg.log is restored. Corresponds to the third from last position on the tape det_log - the detailed BRBACKUP/BRARCHIVE log is restored. Corresponds to the second from last position on the tape.
sum_log - the summary BRBACKUP/BRARCHIVE log is restored, corresponds to the final position on the tape.
Caution:
Corresponds to the third from last position on the tape from which you called BRRESTORE. You can change this by explicitly entering a directory . For example, if you want to restore the detailed log of BRBACKUP, you can use the following calls:
brrestore -n det_log=/oracle/C11/sapbackup
or
cd /oracle/C11/sapbackup
brrestore -n det_log

[-o|-output dist|time[,time|dist]]
Extended output in the detailed log. Default: normal output.
-o|-output dist - generates information about the distribution of the files on the media used (tape/disk).
-o|-output time - generates additional information about the backup duration of the individual files.

[-p|-profile ]
BRRESTORE profile name.
Default: init.sap. [-q|-query [check]]
Query option - the restore process is not started. Only tape names and other resources that are necessary for the restore are issued. "Check" also checks whether the correct tapes have been placed in the tape drives.

[-r|-parfile ]
Parameter file for an external backup program.
Default: no parfile.

Comments:
------------
Options -d, -k, -m and -r can be preset by the corresponding BRRESTORE profile parameter.
Only one of the options -a, -b or -n may be set. If no setting is made, "-b last" is assumed.
BRRESTORE with option -a can be started in parallel to BRRESTORE with the options -b or -n.
To restore a complete offline backup (restore database), you must use the "-m full" option.
The keyword "all" can be combined with other specifications in an (for example, files not related to the database or directories).
All the s used and the file IDs occurring in the area - must be known to the database.
Files and directories not related to the database must be defined with a complete path.
Database data files can be defined with a complete or a generic path. The generic path must contain the Oracle home directory plus one additional generic specification, such as a sapdata directory. This specification is then regarded as a wildcard:
*
Online Redo log files can only be explicitly accessed with the group number of the Redo log files, which must also be provided with a leading zero.
The Oracle control file can only be explicitly accessed with the file ID 0.

Example:
----------

brrestore -b last -m all
Restoring all tablespaces without Oracle control files and online Redo log files from the last successful backup.

brrestore -b bcnmhluz.aft -m full
Restoring all files from the backup bcnmhluz.aft, including Oracle control files and online Redo logs files.

brrestore -m all,/usr/sap/C11/SYS/exe/run,/usr/sap/C11/SYS/profile
Restoring all tablespaces, SAP executables and profiles

brrestore -m /oracle/C11/sapdata1/=/oracle/C11/sapdata5
Restoring all database data files from the subdirectories of /oracle/C11/sapdata1 into the directory /oracle/C11/sapdata5.

brrestore -b last -m 1-10,01-04,0
Restoring all database data files with Oracle file IDs between 1 and 10 inclusive, the four online Redo log files and the control file.

brrestore -m 0
Restoring the Oracle control file.

brrestore -b last -m /oracle/C11/sapdata2/ddicd_5/ddicd.data5
Reloading a database data file.

brrestore -a 200-220
Restoring the archived Redo log files with log sequence numbers between 200 and 220 inclusive into the archive directory.

brrestore -a 40-70=/oracle/C11/sapbackup,71-90=/oracle/C11/sapreorg
Restoring archived Redo log files with log sequence numbers between 40 and 70 inclusive into the directory /oracle/C11/sapbackup, and log sequence numbers between 71 and 90 inclusive into the directory /oracle/C11/sapreorg.

New init.sap parameters
----------------------------

Three new init.sap parameters have been introduced to support the database restore by means of SAPDBA:

cpio_in_flags - cpio options for importing the files from tape
Default: -iuvB
Example:
cpio_in_flags = -iuvB

uncompress_cmd - command for decompression,
(no default)
Example:
uncompress_cmd = "uncompress -c $ > $"

tape_pos_cmd - Command for positioning on tape,
(no default)
Example:
tape_pos_cmd = "mt -f $ fsf $"

Keyword: BRRESTORE

SAP Note 13994 - Long runtimes when saving with BRBACKUP

Symptom:

Runtimes are much longer than normal when you save.

Reason and Prerequisites

Cause 1.
----------
There is a high CPU load, possibly due to looping processes. This has a negative effect in particular if you use software compression (compress = yes in init.sap)

Cause 2.
----------
The dd ouput on tape is not blocked when you save to a remote host.
AIX only: The SMIT setting for "tape block size" is not equal to 0.
The "cpio_flags" do not define a block for the cpio output.

Cause 3.
----------
The cpio performance is poor on Windows NT.

Solution

Solution 1.
---------
Check the CPU load: using process lists (command ps), for example. Identify processes that have used more than 1,000 CPU seconds. If these are looping processes (for example, the CPU load grows quickly), kill them or boot the host.

Solution 2.
---------
Include the option bs=5k in init.sap parameter copy_in_cmd and copy_out_cmd:
copy_in_cmd = "dd bs=64k if=$"
copy_out_cmd = "dd bs=64k of=$"
You can also use block sizes other than 64k.
AIX only: Set the SMIT setting for "tape block size" to 0 (variable block size).
The init.sap parameter cpio_flags should define a block for the cpio output, for example, cpio_flags = -ovB. "B" means that blocks of 5120 bytes are written to tape.
If this burdens the operating system, you can work with larger blocking factors and therefore achieve shorter save times.

Solution 3.
---------
As of BRBACKUP 3.1, you can use the dd command for backups of the database files along with the cpio. This can improve the performance. For more information, see Note 71058.
If this does not solve the problem, your only solution is to change the backup method:

3.1. Using the SAP backup library with RMAN. To do this, change the following inittape_copy_cmd = rman
and activate the SAP backup library (Note 142635).

3.2. Use an external backup tool through the BACKINT interface:
backup_dev_type = util_file | util_file_online
You can find information about partners who support this interface in Note 83792.

Keyword: BRBACKUP

SAP Note 13984 - MB1B: Manual entry of account for transfer postings

Symptom:

1. When you enter an account in the case of a transfer posting, this account will not be accepted by the system, because the system always uses the G/L account defined via the automatic account determination function.

2. When you enter an account assignment (such as a cost center, an order, a project...) in the case of a transfer posting, this account assignment will not be accepted by the system, because the system always uses the account assignment determined automatically.

Cause and prerequisites

In the case of transfer postings, postings are carried out from one stock account to another. Since the stock account is taken from the material master record, these accounts cannot be entered directly.

In adddition, it is not possible to enter an account assignment for inventory postings. This is the reason why any account assignment entered manually will not be considered by Financial Accounting.

Any postings to the account for expenditure or income resulting from transfer postings (account key AUM) can only be automatically assigned to the relevant account. You cannot manually enter an account assignment for these postings.

However, it is useful to be able to manually enter the account for expenditure or income from transfer postings and/or an account assignment for this posting. For this case, however, the indicator "Check account assignment" is not set.

Solution
Please maintain table T156X using transaction SM31.

Example for movement type 309 (as of Release 3.0F)

MvT Val.update Qty update S MvT Cns Value str. Cn Acct modif Check
309 X X WA04 6 X

Example for movement type 309 (prior to Release 3.0F)

MvT Val.update Qty update S MvT Cns Value str. Cn Acct modif Check
309 X X WA04 5 X

Note: 1. This change is only possible for movement types which use
the value string WA04.
2. This change only takes effect if the system actually
creates a posting line "expenditure/income from transfer
postings".

Additional key words

Account assignment, stock transfer, tranfer posting, MB1B, MB11, AUM

SAP Note 13979 - Logical database QTQ: Renaming of field QMTBV-LTEXTV

Symptom:

The field QMTBV-LTEXTV in the logical database QTQ (program SAPDBQTQ) was renamed in QMTBV-LTEXTKZ.
This causes a syntax error in all programs which are using the logical database QTQ and which are inquiring the corresponding field.

Cause and prerequisites

see above

Solution
Please replace the field QMTBV-LTEXTV by QMTBV-LTEXTKZ in those programs that are using the logical database QTQ.

Key word: Inspection method

SAP Note 13962 - RPITUM00: calculation of seniority (customer soln.)

Symptom:

Program : RPITUM00
Report RPITUM00 performs a reclassification according to period of
membership to a pay scale group or level (pay jump due to seniority),
even for a period outside the data selection period entered.

Cause and prerequisites

In the standard system, the report allows the compilation of a new
record for the day after the end date of the data selection period
entered. This is in keeping with the report standard and is consequently
not an error.

Solution
If you only want new records to be formed within the data selection
period you enter, you can modify the report standard as follows:

Insert all lines marked "insert" below in report RPITUM00 and
deactivate the lines marked "deactivate".

Excerpt from the source code of report RPITUM00:
...
*-----Reportspezifische Hilfsfelder
DATA: SEIT TYPE D, KEYDATE TYPE D, BIBEGDA TYPE D, GBDAT TYPE D,
KONV1(6), "insert
...
*-----Zugehörigkeitsdauer berechnen
DZ = KEYDATE - SEIT.
* DX = 1000 * DZ / 36525. "deactivate aussternen
DAUER = 1000000 * DZ / 36525. "insert
* DAUER = DX * 10. "deactivate
* UNPACK DAUER TO DJJMM. "deactivate
UNPACK DAUER TO KONV1. "insert
DAUER = DJJMM = KONV1. "insert
DAUERJJ = DJJMM(2). "konvertieren "JJMM".
* IF DAUERJJ LT 10. "deactivate
* MOVE '0' TO DAUERJJ(1). "deactivate
* ENDIF. "deactivate
* DAUERMM = DJJMM+2(2) * 12 / 100. "deactivate
DX = DJJMM+2(2) * 1200 / 100. "insert
UNPACK DX TO KONV1. "insert
MOVE KONV1+2(2) TO DAUERMM. "insert
* IF DAUERMM LT 12. "deactivate
* DAUERMM = DAUERMM. "deactivate
* IF DAUERMM LT 10. "deactivate
* MOVE DAUERMM(1) TO DAUERMM+1(1). "deactivate
* MOVE '0' TO DAUERMM(1). "deactivate
* ENDIF. "deactivate
* ELSE. "deactivate
* DAUERJJ = DAUERJJ + 1. "deactivate
* IF DAUERJJ LT 10. "deactivate
* MOVE '0' TO DAUERJJ(1). "deactivate
* ENDIF. "deactivate
* MOVE '00' TO DAUERMM. "deactivate
* ENDIF. "deactivate
PERFORM RE001. "XRKK11K068898
RP-READ-T001P P0001-WERKS P0001-BTRTL 'X'. "XRKK11K048234
...
End of the excerpt from the source code of report RPITUM00.

Examine the report for check errors and save the report.

Key word: RPITUM

SAP Note 13957 - Index is now unusable

Symptom:
The performance of certain SAP transactions is all of a sudden extremely slow or terminates with the ABAP/4 runtime error DBIF_RSQL_SQL_ERROR or DBIF_RTAB_SQL_ERROR. In the SYSLOG and in the detail information of the ABAP/4 runtime error you find the following entries:
"SQL error -243 occured when ... within a table ."
"INF-243: Could not position within a table."
"ISAM-101: file is not open."

Previously you may have found (it may have been some time prior to the occurance of this problem) in the database log file ("online.log file") messages of the type:
hh:mm:ss ...
hh:mm:ss Results: Index is now unusable
hh:mm:ss Action: Run 'oncheck -cI ...'
hh:mm:ss ...
Additional key words

INF243, INF101, ISAM101, INF271, INF131, ISAM131, INDEX, UNUSABLE

Cause and prerequisites

In your system a dbspace overflowed while an index modification was being cancelled (rollback of a different transaction). You may find in your SYSLOG previous entries of the type:
"SQL error occurs when...within table

."
"INF-: ..."
"ISAM-131: no free disk space."
Solution

Check the specified index with 'oncheck -cI ...' as described in the database log file ("online.log file") and, if necessary, recreate the index with the tool SAPDBA. (Caution: deleting and recreating an index may take some time). Proceed as follows:

1. Stop the R/3 System (as user adm):
$ stopsap r3

2. Repair the index with the tool SAPDBA. For this refer to the related Note 38401.

3. Start the R/3 System (as user adm):
$ startsap r3

SAP Note 13944 - Default partner does not appear at first position

Symptom:

The partner indicated as default partner in the customer master does not appear in the first position during order processing.

Cause and prerequisites

The problem is caused by a program error.

Solution
Check the following coding locations:
1. LV05EF0P (only in Releases 2.2A-2.2D)

FORM PARTNER_BEARBEITEN.

....

SORT LKUPAV BY KUNNR PARVW PARZA.
SORT LTPAER BY MANDT SORTF PARGR PARVW. "<-- new as of 2.2A
LOOP AT LTPAER WHERE PARVW NE *VTCOM-PARVW AND
HERTAB = ' '.

2. LV05EFMO (only in Release 2.2A to 2.2D):

FORM MOVE_KNVP_TO_LKUPAV.

....


MOVE KNVP-VTWEG TO LKUPAV-VTWEG .
IF KNVP-DEFPA = 'X'.
LKUPAV-PARZA = '000'.
ELSE. "<=== New
IF LKUPAV-PARZA = '000'. "<=== New
LKUPAV-PARZA = '001'. "<=== New
ENDIF. "<=== New
ENDIF.

Keyword: default partner

SAP Note 13936 - Handling of trading unit in R/3

Symptom:

Different trading units of a material cannot - in contrast to R/2 - be saved like batches under one material master.

Cause and prerequisites

Trading unit handling is not planned.

Solution
Please define a separate material master for each trading unit.

Key word: Trading unit

SAP Note 13921 - DTAZV - House bank missing receiver bank info

Symptom:

When data medium exchange is used for foreign wire transfers (DTAZV format for the Federal Republic of Germany), the customer receives a notice from the bank that the information about the payee bank is missing.

Cause and prerequisites

1. The house bank agreed with the customer to share the address as well as the SWIFT code of the payee bank. This agreement is due to the obvious assignment of the receiver to the corresponding receiver bank, and the resulting fewer complaints and charges for this from the foreign bank.

2. In accordance with an agreement with his/her house bank, the customer does not place the SWIFT address of the payee bank in the SWIFT code (vendor data), but instead the correspondence bank in the payee's country to provide the house bank with the routing.

When the SWIFT code is filled in DTAZV format, however, no data is passed on other than the account number. This means that

1. there may be problems determining the receiver bank which leads to costs due to additional research;

2. the correpsondence bank in the payee's country is missing the information regarding the bank the payee actually uses. As a result, no payment is possible.

Solution
Despite the above agreement, the bank routing code of the payee must be entered instead of the SWIFT address in the vendor master record.

As of Release 3.0, you have the option of filling the empty fields in accordance with the regulations of the house bank by means of a user exit, and to forward the information in such a way. Refer to the program documentation for further details.

Additional key words

RFFOD__L

SAP Note 13915 - MD19: No authorization

Symptom:

Program: SAPMM61P
Error ID: 61402
Transaction MD19 for firming up a planned order cannot be called. An error message is issued on the initial screen, "No authorization for...", although the user has authorization profile SAP_ALL.

Cause and prerequisites

Authorization profile for planned orders is incomplete

Solution
1) Select menu path: Tools -> Administration -> User maintenance
-> Profiles.
2) Enter profile 'M_PLAF_ALL'.
3) Select the profile on the following screen by double-clicking
4) Add authorization 'M_PLAF_5_ALL', the authorization for firming
up planned orders.
5) Activate profile 'M_PLAF_ALL'.
6) Log off and then on again.
7) Finished!

Key word: MD19

SAP Note 13907 - System error in the block handler, overflow lock table

Symptom:

FM: A system error has occurred in the block handler
The following error message is displayed in syslog: Lock table overflowed

Reason and Prerequisites

The lock table has overflowed.
Cause 1: The dimensions of the lock table are too small.
Cause 2: The update lags far behind or has shut down completely, so that the lock entries of the update requests that are not yet updated cause the lock table to overflow.
Cause 3: The application programs are poorly designed. A lock is issued for each object in an application program, for example a collective run with many objects.

Solution
Determine the cause:
Call transaction SM12 and choose "Goto" -> "Diagnosis" (old)
Call transaction SM12 and choose "Extras" -> "Diagnosis" (new)
checks the effectiveness of the lock management

Call transaction SM12 and choose "Goto" -> "Diagnosis in update" (old)
Call transaction SM12 and choose "Extras" -> "Diagnosis in update" (new)
checks the effectiveness of the lock management in connection with updates

SM12 -> OkCode TEST -> Error handling -> Statistics (old, only in the enqueue server)

SM12 -> Extras -> Statistics (new)
shows the statistics of the lock management, including the previous maximum fill levels (peak usage) of the partial tables in the lock table

If the owner table overflows, cause 2 generally applies.

In the alert monitor (RZ20), an overrunning of the (customizable) high-water marks is detected and displayed as an alert reason.

The size of the lock table can be set with the profile parameter "enque/table_size =". specifies the size of the lock table in kilobytes. The setting must be made in the profile of the enqueue server ( ..._DVEBM.. ). The change only takes effect after the restart of the enqueue server.

The default size is 4 MB for releases below 701 and 32 MB (32 Bit) or 64 MB (64 Bit) as of kernel release 701.

The maximum sizes for the individual tables are (example size: 4 MB):
Owner table: approx 5400
Name table: approx 5400
Entry table: approx 5400

Example: With the profile parameter
"enque/table_size =32000" , the size of lock table is set to
32000 KB (32 MB). With this setting, the tables can contain around 40000 entries.

Note that the above sizes and numbers depend on various factors such as the kernel release, patch number, platform, address length (32/64-bit), and character width (Ascii/Unicode). Use the statistics display in SM12 to check the actual capacity of the lock table.

If cause 2 applies, increasing the size of the lock table only delays the overflow of the lock table, but it cannot generally be avoided.
In this case you need to eliminate the update shutdown or accelerate the throughput of the update program using more update processes. Using CCMS (operation modes, see training BC120), the category of work processes can be switched at runtime, for example, an interactive work process can be converted temporarily into an update process to temporarily increase the throughput of the update.

For cause 3, you should consider a tuning of the task function Instead of issuing a large number of individual locks, it may be better to use generic locks (wildcard) to block a complete subarea. This will also allow you to considerably improve the performance.

Other terms

M3021, MM02, F5 288, F5288, FBRA

Keyword: Enqueue

SAP Note 13905 - OB42: Interest indicators not deleted

Symptom:

Key word: Interest indic. When you maintain the interest indicators in the configuration fo the dunning program, entries with a validity period of the form
" . .0000" cannot be deleted.

Cause and prerequisites

A validity period must be entered from Rel. 3.0 onwards. Old entries without a date cause error message SG102.

Solution
Use the following help program to delete the entries:

REPORT ZFT056Z .
TABLES: T056Z.

DELETE FROM T056Z WHERE DATAB = '99999999'.
IF SY-SUBRC = 0.
WRITE: 'deleted'.
ELSE.
WRITE: 'not found'.
ENDIF.

SAP Note 13898 - Short texts with customer batch input program

Symptom:

If customers use self-defined programs to supply a short text
for a material, problems occur in the screen required for entry.

Cause and prerequisites

A different screen is used in batch input for the short texts
in the material master than in the normal transaction.

Solution
The best way is to use the standard report for BTCI. If you do not
want to do this, you must specify OkCODE KTBT in field BDC_OKCODE
to make sure that the correct screen, SAPMM03K 110, is used.
Of course, screen fields MAKT-SPRAS and MAKT-MAKTX must then be
provided with data directly.

Key word: BTCI MM01 MM02

SAP Note 13884 - Handling the rejection indicator in a bid

Symptom:

If an RFQ is created with reference to a purchase requisition,
and the rejection indicator is set later in the vendor's bid,
the system does the following:
1. If a purchase order is created with reference to this purchase
requisition for the vendor whose bid was rejected, no message
is issued; the purchase order is created.
2. If a purchase order is created with reference to a rejected bid,
no message is output either. The purchase order is created
(system reacts the same even when the RFQ is created without
reference to a purchase requisition).

Cause and prerequisites

Works as programmed

Solution
1. No change is planned for this, as many RFQs can be created
for one purchase requisition, and in turn many items can be
rejected.
2. Will be changed in Rel. 3.0

Key word: ME21 ME51 ME47

SAP Note 13882 - Handling of POPUP_TO_CONFIRM in batch input

Symptom:

You find a confirmation dialog box (pop-up window) in an application and want to provide it with data in batch input. You do not know how to do so because the OK code input does not work.

Cause and prerequisites

These dialog boxes (POPUP_TO_CONFIRM) do not have any input-capable fields; only pushbuttons.

Solution

Solution 1:
Enter the prefix '=' for OK CODE field (function code) BDC_OKCODE.
For example:

=NO or
=YES or
=CANC

Do not use notation '/00' in BDC_OKCODE for data release!


Solution2:
You position the cursor on the pushbutton and press Enter.
How does this work technically?

• Use F1 and technical info to find out the name of the key field behind the pushbutton.

Provide batch input field "BDC_CURSOR" with the key field name and do not enter BDC_OKCODE.
(Do not use notation '/00' in BDC_OKCODE for data release!)

Example: 'POPUP_TO_CONFIRM_STEP'
Screen: SAPLSPO1 0100
-------------------------------------------------------------------

Field name Value Description
---------- -------------- ------------------------------
BDC_CURSOR SPOP-OPTION1 for YES
or
BDC_CURSOR SPOP-OPTION2 for NO
or
BDC_CURSOR SPOP-OPTION2 for CANCEL

Additional key words

Batch input
SAPLSPO1 0100
SAPLSPO1 0200
SAPLSPO1 0300
SAPLSPO1 0400

SAP Note 13876 - SAPGUI: Abnormal Termination, SAP_CODEPAGE <> 1100

Symptom:

Frontend cannot communicate with the application server if the frontend environment variable SAP_CODEPAGE is set to a character set unlike that of the application server.
This is normally the case for the R/3 Systems, which use the code page ISO8859-x, x=2...,9 (for example Russian: ISO8859-5 = Codepage 1500, frontend SAP_CODEPAGE=1504).
Whenever R/3 is automatically regenerated, and the message "Compiling ..." appears in the status line of the SAPGUI: The SAPGUI terminates with the error message "Abnormal Termination ...".
Even Windows must then be restarted in order to be able to use SAPGUI again.

Cause and prerequisites

The conversion file for character conversion does not exist in Frontend. This file is needed if the RFC interface is to send data to the SAPGUI (for example, during regeneration).
The SAP_CODEPAGE parameter has two effects:

1. The character set of the frontend is sent to the R/3 kernel. The kernel undertakes further conversions by using conversion tables in the databank (maintain with transaction SPAD).

2. The RFC receiver in SAPGUI is set to this codepage. Since during RFC the receiver must perform the conversion and the frontend has no direct access to the databank, a conversion file must be available for the conversion.

Solution
The corresponding conversion file must be recognized by the SAPGUI and generated from R/3:
1. Login R/3, user SAP*. client 0002. Call SM59 menu option RFC -> Generate conv. tab. or start the report RSRFCPUT using SE38.

Parameter:
a) Source code page (= APPL server character set, for example, 1500 for Russian), (Check: SE38: RSPARAM: parameter value install/codepage/appl_server)b) Target code page: Code page, which is set as the DOS Paremeter SAP_CODEPAGE, and runs in the SAPGUI.
(check: DOS shell, then "set" shows the SAP_CODEPAGE)
c) Path: The path on the application server (on UNIX, for example, /tmp/), in which the generated conversion file is stored.
Caution:
The path must end with a path identifier (for UNIX: SLASH)
Effect: A file .CDP is generated.
File format:
Each line contains a number in Hex format. For example: during a
conversion in which all characters are transferred indentically,
each line contains the line number in Hex format--as follows
0x00 (Meaning: Character 0x00=Line 0 is changed to character 0x00)
0x01
0x02
....
0xFF

2a. If 2. is not possible because SM59 is also compiling and the SAPGUI terminates once again, it is possible (from 3.0B) to switch off the conversion at the front end temporarily. Simply set PATH_TO_CODEPAGE to NONE. The path is "fixed" only when the codepage is generated with SM59.

2b. If you have 3.0A or an older release, you can call the c program ldcdprfc on the application server. Enter the appropriate connect options and do not forget -3 as an option.
Example: ldcdprfc -d C11 -3 =s 00 -h myhost -u SAP -p PASS -S 1100
-T 1105 -P /usr/sap/C11/
This program creates the codepage files without using the GUI.

3. The file generated must be transferred to the frontend (for example with ftp, binary), into the SAPGUI working directory.
The file has the extension CDP.

4. In the AUTOEXEC.BAT file on the frontend, a line must be created with the DOS environment variable:
SET PATH_TO_CODEPAGE=
Do not forget the platform specific path identifier at the end.


Example:
a) the application server uses code page 1500 (Russian ISO8859-5)
b) The Frontend uses CP 1504 = MS Windows CP 1251 (Russian MS Windows);, the SAPGUI working directory is C:\SAPGUI
- The conversion file should be called: 15001504.CDP - in AUTOEXEC.BAT: SET SAP_CODEPAGE=1504
SET PATH_TO_CODEPAGE=C:\SAPGUI\
- in R/3 SM59: source CP: 1500, target CP: 1504, Path: /tmp/- on the application server, the file /tmp/15001504.CDP is generated, which must then be transferred to the C:\SAPGUI directory on the PC.

Additional key words

Error in the application program, SAPGUI crash, code page, conversion

Key word: Code page. Conversion, character set, SAP_CODEPAGE, SAPGUI

SAP Note 13847 - Entry 101 _ _ _ B not in table T156S

Symptom:

When you enter a goods receipt for a purchase order (transaction MB01,
MBOA), the system displays the following error message:
Please check table T156S: entry 101_ _ _ B missing.

Cause and prerequisites

A new account assignment category was entered in table T163K (with
Customizing transaction OME9). The new account assignment category was
given the consumption indicator Blank (field T163K-KZVBR).

Solution
Please assign a valid consumption/usage indicator to the relevant
account assignment category. The standard system supports A (asset),
V (consumption), E (sales order stock), and P (project).

Key word: T156S

SAP Note 13844 - Acquisition tax 0% / inverse +/- sign

Symptom:

An acquisition tax code 0% is created and by doing so, 0% is specified for input and output acquisition tax (both as 0%-). In the advance return for tax on sales/purchases, the base amount of output tax is then displayed as a positive and not a negative amount, the second line (input tax) is not mentioned at all if the base for it was the amount of the output tax (that is, zero).

Cause and prerequisites

Our programs cannot distinguish a positive zero from a negative zero after the data has been saved. The programs for calculating tax thus calculate the amount zero twice and you do not know anymore for which base amount the +/- sign is to be changed.

Solution

You can either
- use the normal code for tax-exempt deliveries,
or
- create a separate tax code for "Exempt from acquisition tax"
which, however, is defined just as "Exempt from input tax".
As a result, the base amounts for tax-exempt imports from other EC
member states can then be calculated separately in the advance
return for tax on sales/purchases.
From our point of view, it is not necessary to display a tax-exempt acquisition from other EC member states in both parts of the advance return for tax on sales/purchases (input tax and output tax).

Subsequent activities
(only for german customers who use the tax form printing program)
When using the tax code for "Exempt from acquisition tax", the relevant base amounts are displayed in the advance return for tax on sales/purchases in exactly the same way as the base amounts in "Exempt from input tax". The base amount is therefore displayed with a negative sign on the F_RFUVD____01 tax on sales/purchases form (program RFUVDE00). What you require, however, is the display to be the same as the output tax portion of the acquisition tax, that is without a +/- sign. This can be done in the form as follows (MAIN window):

Base amount without decimal places for group nn in the standard system:
AM ,,&UMSVP-BASnn(IZ13.0)&
With an inverse +/- sign:
/: IF &UMSVP-BASnn+20(>)& EQ '-'
/: DEFINE &SIGN& = ' '
/: ELSE
/: DEFINE &SIGN& = '-'
/: ENDIF
AM ,,&SIGN&&UMSVP-BASnn(CSIZ13.0)&

Additional key words

Taxes, SAPLTAX1
RFUMSV00, RFUVDE00, F.36

SAP Note 13840 - Reorganization of NAST records

Symptom:

Dataset in table NAST contain keys from reorganized application objects.

Cause and prerequisites

There is no special reorganization for table NAST. This table is reorganized with the application documents (to which it is allocated through the application keys).
The messages represented by the NAST records are attributes of the related application objects. NAST records must therefore be reorganized together with the application documents to avoid inconsistencies caused by uncoordinated reorganization runs and NAST records for reorganized documents.
NAST datasets can be deleted with the functions RV_MESSAGES_DELETE and RV_MESSAGES_UPDATE. This also deletes the processing logs in table CMFP.

Solution
Check the reorganization program as far as the reorganization of NAST is concerned.
As of Release 3.0D, the report RSCLNAST is contained in the delivery. You can use it to explicitly delete NAST records, if this is necessary.

Additional key words

Message, entry, deletion, removal, message record, NAST

Key word: Reorganization

SAP Note 13838 - Report line structure reset

Symptom:

If discrepancies exist in the basis entries of a report line structure,
(Entries Line structure ' ', elements 9001+), you can reset
these entries in the Tables 237A, 237T and 237.

Cause and prerequisites

The same program error described in note 12343.

Solution
SE37: Start function module RKE_FILL_TABLES_T237FF in test mode:
ERKRS XXXX - current operating concern
MODE N - reconstruct basis entries
TABNAME CE1XXXX - current line item file
Execute function module using F8.

As of release 4.0, the function module copies the operating concern
into the table name. Thus the third import parameter is omitted.


Do this while you are logged on in the language in which the
operating concern was originally generated.

Foreign-language entries in Table 237T need to be translated manually
using Transaction SM31. This goes for both the entries 9001+ and for
created report line structures.

Key word: Line structure

SAP Note 13829 - Canc. billing docs influence sales qual. for rebate

Symptom:

Cancelled billing documents are considered in the sales qualifying for rebate. They increase the sales qualifying for rebate and are displayed in the drill-down.

Cause and prerequisites

The cancellation billing document type (for example, S1) is marked as not qualifying for volume-based rebate. As a result, the cancellation billing document does not reduce the sales qualifying for rebate.
The cancellation billing document contains the same values as the cancelled billing document. Only the values of the cancellation
billing docuement have a different +/- sign. For this reason, the total of cancellation billing document and the cancelled billing document is 0. If the cancellation billing document and the cancelled billing document are qualifying for volume-based rebate, the cancellation is correctly taken into account during the rebate settlement.

Solution
1) Mark the cancellation billing document as qualifying for volume-based rebate.
-> Customizing SD -> Functions -> Rebate processing -> Control data
-> Billing documents.

Caution: If the cancellation billing document is marked as qualifying for volume-based rebate, you may only cancel billing documents qualifying for volume-based rebate with this cancellation billing document type. If you cancel a billing document not qualifying for volume-based rebate with a cancellation billing document qualifying for volume-based rebate, this would reduce the sales qualifying for rebate although the original billing document is not qualifying for volume-based rebate.

Key word: Rebate

SAP Note 13827 - Problems with your own reference screens for selection scree

Symptom:

The following error can occur when using your own reference screens for the selection screen of a report:

1.) Comments and underscores, which were defined with SELECTION-SCREEN COMMENT or SELECTION-SCREEN ULINE and were left on the reference screen, do not appear on the selection screen.
2.) The database program SAPDBldb has several selection screens; i.e., there are more objects defined in DBldbSEL than fit on a screen. All these objects, as well as pushbuttons to scroll between the screens appear without the use of your own reference screens. However, when you use your own selection screens, only those objects which are exactly on the that screen and the scroll buttons are missing if additional screen are not created via report-specific select options or parameters.

Additional key words

() ABAPNOTE SELECTION SCREEN LDB

Cause and prerequisites

Re: 1
The names of the corresponding fields on the selection screen are structured as follows:

- %_xxxnnn for SELECTION-SCREEN COMMENT TEXT-xxx ... FOR TABLE tab
- %_Unnn%% for SELECTION-SCREEN ULINE ... FOR TABLE tab

In this case, 'xxx' is the number of the comment and 'nnn' is a consecutive number that was used in the report generation to number the SELECT-OPTIONS, PARAMETERS and SELECTION-SCREEN statements.
When generating a selection screen based on a reference screen, the system searched for the corresponding object in the currently generated version of the report to decide whether a reference screen is to be copied or ignored.
The error occurred if, after creating the reference screen in the database INCLUDE DBxyzSEL (xyz = name of the logical database), a SELECT-OPTIONS, PARAMETERS or SELECTION-SCREEN statement was included or removed from it before the SELECTION-SCREEN statement. Because of the resulting shift in the consecutive number, the fields were not found in the current load and as a result they were not copied to the selection screen.
Re: 2
Only this is supported. When using your own reference screens only the onjects found in the screen are taken into consideration.

Solution
Re: 1
In such a case, generate Dynpro 1000 of the databank program SAPDBxyz (SE38, Prgram --> Generate). Then copy the filed names from this dynpro, which contains correct consecutive numbers) onto the reference screen.
Afterward, the selection screen of the report must also be regenerated.

Re: 2
When using your own selection screen, the database-specific portion is limited to a maximum of one page. In any case, objects in a selection screen can appear which are split across several dynpros in the "normal case."

From 3.0:
There are no longer any reference screens; they have been replaced by the defining selection screen versions SELECTION-SCREEN BEGIN/ END OF VERSION.

Keyword: Reference screens

SAP Note 13816 - Account group missing for the partner func. (VP303)

Symptom:

The following error message is displayed when creating a delivery: Customer in a certain partner function cannot have a certain account group. Error message: VP303 in transaction VL01.

Cause and prerequisites

The account group was not assigned to the partner function of the customer. When creating an order, a partner function was entered which is defined in a hierarchy, and for which no account group is assigned.

Solution
Assign the account group to the partner function via:
Tools -> Customizing -> Configuration -> Logistics -> Sales/ distribution -> Functions -> Partner determinat. -> Partner functions, place the cursor on the affected function -> Environment ->
Acct grp assignment. Here you have to enter the account group for the required partner.

Key word: Customer hierarchy

SAP Note 13814 - File name differs from MATERIAL_MASTER_BTCI

Symptom:

If during the batch input for material master data the customer
enters a name that diffes from the one proposed by the system, he
might receive the error message MG016:
For ...., no physical file name can be determined.

Cause and prerequisites

Table FILENAME not maintained.

Solution
Call SF01 and create the new name as a logical file name and
specify the corresponding physical file name (including path).
Here it is useful to take the entries for MATERIAL_MASTER_BTCI as
a reference.

Key word: RMMMBIM0 MG016

SAP Note 13809 - SAP enhancement concept: support for cust. modif.

Symptom:

Key word: SMOD, CMOD
Customer wants to add proprietary functions to the SAP standard or
change SAP programs; would like support.

Solution
1. SAP enhancement concept: transaction CMOD (SMOD), documentation:
transaction CMOD (SMOD), (--> Documentation: menu Environment->
Manual).
2. "Traditional" modifications

SAP Note 13807 - Analyzing Correction & Transport System problems

Symptom:

The information you provided the SAP Hotline about your reported
problem is not sufficient to guarantee fast processing.

Cause and prerequisites

This note should help you speed up the processing of your
reported problem.

Solution
You have to find the information that the Correction and Transport
System writes to its logs and provide it to the SAP Hotline.
Please fill out the form below and send it to the SAP Hotline, along
with the relevant log excerpts.

--> At operating system level.......................................

o Which action caused the problem (termination, error message) ?

.____________________________________________________________________.

o How was this action started (e.g. tp import C11K900001 P11 u1) ?

.____________________________________________________________________.

o Are other SAP systems connected in the network ?

.____________________________________________________________________.

o Under UNIX, analyze the errors by examining the following:

a. /usr/sap/trans/log/SLOG*
b. /usr/sap/trans/log/LOG
c. /usr/sap/trans/log/<>?9nnnnn.
= source SID
= target SID
? = Abbreviation for import step
(fourth column in SLOG in lines with ERROR
)
d. grep /usr/sap/trans/bin/T_hugo
e. ls -ltr /usr/sap/trans/bin

Extract the relevant portions for the SAP Hotline.

o Under WINDOWS NT, analyze the errors by examining the following:

a. \usr\sap\trans\log\SLOG*
b. \usr\sap\trans\log\LOG
c. \usr\sap\trans\log\<>?9nnnnn.
= source SID
= target SID
? = Abbreviation for import step
(fourth column in SLOG in lines with ERROR
)
d. dir /OD \usr\sap\trans\bin

Extract the relevant portions for the SAP Hotline.

--> In the R/3 System ................................................

o Transaction SM37: are there any terminated batch jobs for user DDIC?
If so, what is the complete text of the job log(s)?
Please find the section relevant to the time in question in the local system log.

Additional key words

r3sl

SAP Note 13797 - ontape -s: Archive failed with errno 28

Symptom:

Archiving the DB with "ontape -s" terminates with the following error message:

"Archive failed - function write to tape failed code -1 errno 28"

Cause and prerequisites

The value of parameter TAPESIZE in the configuration file ($ONCONFIG) of the OnLine DB system is set too large.

Solution
Reduce the value of $ONCONFIG parameter TAPESIZE accordingly. For example, for HP non-compressed 4 mm DAT tapes

60 m to 1250000 [1.3 GB capacity according to manufacturer]
90 m to 195000 [2.0 GB capacity according to manufacturer]

For HP non-compressed 8mm DAT tapes

112m to 2095000 [2.3 GB capacity according to manufacturer]

To active these prarmeter changes the databank system must be restarted.

Additional key words

archive ontape INF1 INF28 ontape -s Archive failed code -1 errno 28,
errno28

SAP Note 13793 - Connect to SAPLPD sometimes fails

Symptom:

Sometimes, you cannot set up the connection to SAPSprint (see Note 894444).
This happens whenever the PC issues a previously received list with device type SAPWIN, or when another application on the PC hands control over to SAPSprint too rarely.
the error appears in the system log as 'Connect failed'. It appears in the SAPSprint log as
Error: socket_read: l_rc = -1
or as
Error: lpxxslpd: read on socket ...
An NILIB message normally appears just before it, for example:
'***ERROR: NiPRecv: errno: 132'.

The spool work process tries to rescue the situation by repeating the transmission twice after a short wait (the default is five minutes). Nothing can be printed on the affected PC during the waiting period!
If all three attempts fail, the print request is marked as faulty and must be triggered manually later.

Other terms

SAPLPD

Reason and Prerequisites

Device type SAPWIN lets the Windows driver prepare the print data for the connected printer. Some of these drivers are slow, and do not pass control to other tasks while they are preparing a page. Since the TCP software in Windows does not receive control either, the connection request is not answered, and the spool work process reports a problem.

Solution

The problem can be solved only partially, as the main problem, the poor printer driver, is outside our control.

The only way to reduce the problem is to reduce the time required by the printer driver. There are several ways to do this:

• If your printer understands Postscript, PCL or Prescribe, you can change the device type in R/3 from SAPWIN to the relevant type. Then R/3 takes over the data formatting and relieves the computer because now it only has to transfer the data.
  

• Try other printer drivers for the printer.
  

• Configure the printer using the host spooler in UNIX and access it using access method 'U' from the SAP system. The host spooler then generates a separate process for each printer that can wait for the connection "as long as necessary". While this does not speed up the printer output, it avoids the terminations and delays in the SAP editor.

SAP Note 13789 - Recovery on error ORA-1113

Symptom:

Oracle rturns ORA1113 although a complete off-line backup of all file systems was restored and it should be consistent with all objects.

Cause and prerequisites

Unknown.
The following tables will help you to examine the recovery situation in more detail:
V$RECOVER_FILE: Display of the files, which require a recovery.
V$RECOVERY_LOG: All OFFLINE Redologs that are required to do this.
The select commands can be performed in the MOUNT status of the database. If no logs appear in V$RECOVERY_LOG, a recovery with the online redologs is sufficient.

Solution
If V$RECOVERY_LOG does not return any file, you can perform:
sqldba> recover database
and if this was successful;
sqldba> alter database open;
irectly in the MOUNT status.

Otherwise, we always recommend the program SAPDBA, which however is based on correct information of Oracle in the V$ tables. Therefore the workflow is also incorrect if the information in V$ tables in SAPDBA is incorrect.

Key word: RECOVERY

SAP Note 13788 - Variable name 'TEXT'

Symptom:

Conflicts with structures with the name "TEXT" and text elements
(numbered TEXTS).

Cause and prerequisites

Elements of a structure with name "TEXT" whose names are 3
characters long are interpreted as text elements by the ABAP/4
compiler

Solution
Treat "TEXT" as a reserved word; do not name your variables
"TEXT".

Key word: ABAP/4

SAP Note 13777 - Scrolling in partner overview of a sales activity

Symptom:

When you scroll in the partner overview of a sales activity,
a partner is skipped whether the step loop is activated or not.

Cause and prerequisites

Program error

Solution
Change to program DV02PF55:

- in module SAVE_CURSOR_5555.

old : IVBPA51_LOOPIND1 = HTABIX2 - HTABIX1 + 1.
new : IVBPA51_LOOPIND1 = HTABIX2 - HTABIX1.

Key word: Scrolling

SAP Note 13757 - RFC error: no free connection available

Symptom:

Error ID: CALL_FUNCTION_*
Remote function call terminates with the message

"No free connection available".

Cause and prerequisites

One of the administration tables in the SAP System overflowed

Solution
The administration tables for open connections can be set using
the following parmeters:

The max. number of all active connections via one SAP gateway is
set using profile parameter

gw/max_conn

The default value is 20. It can be set to 100 (or more) without
causing any problems.

An additional restriction exists for the maximum number of open
connections for one application server. This is controlled by the
parameter

rdisp/max_comm_entries

The default value is 100. You only need to increase this value when you have increased the parameter gw/max_conn.

Please note: changes to profile parameters only become effective after the instance has been restarted.

Key word: ABAP/4

Symptom:

Sometimes, you cannot set up the connection to SAPSprint (see Note 894444).
This happens whenever the PC issues a previously received list with device type SAPWIN, or when another application on the PC hands control over to SAPSprint too rarely.
the error appears in the system log as 'Connect failed'. It appears in the SAPSprint log as
Error: socket_read: l_rc = -1
or as
Error: lpxxslpd: read on socket ...
An NILIB message normally appears just before it, for example:
'***ERROR: NiPRecv: errno: 132'.

The spool work process tries to rescue the situation by repeating the transmission twice after a short wait (the default is five minutes). Nothing can be printed on the affected PC during the waiting period!
If all three attempts fail, the print request is marked as faulty and must be triggered manually later.

Other terms:
SAPLPD

Reason and Prerequisites

Device type SAPWIN lets the Windows driver prepare the print data for the connected printer. Some of these drivers are slow, and do not pass control to other tasks while they are preparing a page. Since the TCP software in Windows does not receive control either, the connection request is not answered, and the spool work process reports a problem.
Solution

The problem can be solved only partially, as the main problem, the poor printer driver, is outside our control.

The only way to reduce the problem is to reduce the time required by the printer driver. There are several ways to do this:

* If your printer understands Postscript, PCL or Prescribe, you can change the device type in R/3 from SAPWIN to the relevant type. Then R/3 takes over the data formatting and relieves the computer because now it only has to transfer the data.

* Try other printer drivers for the printer.

* Configure the printer using the host spooler in UNIX and access it using access method 'U' from the SAP system. The host spooler then generates a separate process for each printer that can wait for the connection "as long as necessary". While this does not speed up the printer output, it avoids the terminations and delays in the SAP editor.

15.12.10

SAP Note 13749 - PS: Delete project definition, WBS elements

Symptom:

You want to delete project master data (project definition, WBS element).

Cause and prerequisites
Solution
This note contained a reference to Report RCJDEL01 with which you could delete WBS master data in test systems before project archiving was supported in the R/3 system.
Do not use this report any longer.
To delete and archive, use functions Deletion flag, Delete, Archiving, Reorganization which are now contained in the standard system.
Refer to the documentation for further information.

Key word: WBS, Delete

SAP Note 13740 - Reversal after archiving not possible

Symptom:

Error message: Reversal cannot be run due to missing CO documents
Description: A revaluation must be performed. The system requires you
to reverse the data first. An error occurs when the
reversal is run: Reversal not possible due to missing
CO documents
Transactions: KSPU / Revaluation
Program: SAPMKPU2

Cause and prerequisites

Inconsistency between CO documents (Header: Table COBK) and allocations
document management (Table T823D).

Conditions: This error occurs if revaluation documents were deleted
(using archiving objects for cost centers or using other programs)
without the corresponding T823D entries.

Solution
Install the correction program (K11K102786),
which removes the superfluous entries for Table T823D:
*---------------------------------------------------------------------*
REPORT RKCORR06.

PARAMETERS: KOKRS LIKE CSKS-KOKRS,
TESTLAUF LIKE KREO-TESTLAUF DEFAULT 'X'.

TABLES: COBK, T823D.

DATA: COUNTER LIKE SY-TABIX.

SELECT * FROM T823D WHERE TAB = 'CCSS'
AND UMGRP = KOKRS .

SELECT SINGLE * FROM COBK WHERE KOKRS = KOKRS
AND BELNR = T823D-DOCNR .
CHECK SY-SUBRC <> 0.
ADD 1 TO COUNTER.
CHECK TESTLAUF = SPACE.
DELETE T823D.

ENDSELECT.

WRITE: / TEXT-001 COLOR 6 INTENSIFIED, "Verwaltungseinträge ohne
COUNTER. "CO-Beleg:

IF TESTLAUF = 'X'.
WRITE: TEXT-003. "ermittelt
ELSE.
WRITE: TEXT-002. "gelöscht
ENDIF.
*---------------------------------------------------------------------*
Title: Reorganize Revaluation Document Management
*---------------------------------------------------------------------*
Selection texts: Name Text
KOKRS Controlling area
TESTLAUF Test run
*---------------------------------------------------------------------*
Numbered texts: 001 Admin. entries without CO documents:
002 deleted
003 determined
*---------------------------------------------------------------------*

Key word: Revaluation

SAP Note 13734 - OB08 incorrect validity date cannot be deleted

Symptom:

A date stored in table TCURR, whose form contradicts the date standards when being displayed using transaction OB08, cannot be deleted.

Cause and prerequisites

An entry with an incorrect date was delivered by SAP which you cannot maintain online. The program outputs the FC236 error message "Enter valid date", to which you cannot react.

The same problem could be generated with Report RFDEV310 up to Release 3.1H if nothing had been entered in the field date.

Solution
The incorrect entry can be deleted via an ABAP program you have to
write yourself.
Example:

REPORT ZZDTCURR.
TABLES: TCURR.
DELETE FROM TCURR WHERE KURST = 'B' "Exchange rate type
AND FCURR = 'BEF' "From currency
AND TCURR = 'DEM' "To currency
AND GDATU = '50000000'. "Valid from

The entry for the GDATU field is to be determined using transaction SE16 (Release 2.2) or SE17 (Release 3.0) and applied to table TCURR. The value stored in the database is displayed under the 'Valid from' field.
Delete your program after running it.

Key word: TCURR

SAP Note 13731 - Reversal after archiving not possible

Symptom:

Error message: Message ID 'GA' stating that the reversal
cannot be reversed due to missing CO documents.
Description: Example: A CO allocation transaction is to be repeated.
The system requests the reversal. The error occurs if
the reversal is carried out:
Reversing is not possible because of missing documents.
Transactions: KSW5 / Perform Periodic Transfers
KSV5 / Perform Actual Distribution
KSU5 / Actual Assessment
KSVB / Perform Planned Distribution
KSUB / Perform Planned Assessment
Program: SAPMKGA2

Cause and prerequisites

Inconsistency between CO documents (Header: Table COBK) and
allocation document numbers (table T811D).
Requirements: The error occurs if allocation documents were
deleted (for example, using archiving objects for cost centers or
by means of other programs) and the respective T811D entries were
not deleted.

Solution
Import or maintain a correction program (K11K102786) which
eliminates the unnecessary T811D entries:
********************************************************************
The correction program makes possible only the repetition of the
coresponding documents. A previous reversal no longer takes place. That
means that the totals records contain double values. If you do not
want this to be the case, contact SAP.
*********************************************************************
*---------------------------------------------------------------------*
REPORT RKCORR05.

PARAMETERS: KOKRS LIKE CSKS-KOKRS,
TESTLAUF LIKE KREO-TESTLAUF DEFAULT 'X'.

TABLES: COBK, T811D.
DATA: CYCLE(5) TYPE C VALUE '&&&&%',
COUNTER LIKE SY-TABIX.
REPLACE '&&&&' WITH KOKRS INTO CYCLE.
SELECT * FROM T811D WHERE TAB = 'CCSS'
AND CYCLE LIKE CYCLE .

SELECT SINGLE * FROM COBK WHERE KOKRS = KOKRS
AND BELNR = T811D-DOCNR .
CHECK SY-SUBRC <> 0.
ADD 1 TO COUNTER.
CHECK TESTLAUF = SPACE.
DELETE T811D.

ENDSELECT.

WRITE: / TEXT-001 COLOR 6 INTENSIFIED, "Verwaltungseinträge ohne
COUNTER. "CO-Beleg:

IF TESTLAUF = 'X'.
WRITE: TEXT-003. "ermittelt
ELSE.
WRITE: TEXT-002. "gelöscht
ENDIF.

*---------------------------------------------------------------------*
Überschrift: Bereinigung Allocations-Beleg-Verwaltung
*---------------------------------------------------------------------*
Selection text : Name Text
KOKRS COntrolling area
TESTLAUF Test run
*---------------------------------------------------------------------*
Numbered texts: 001 Administration entries without CO documents:
002 deleted
003 determined
*---------------------------------------------------------------------*

Key word: Allocations

SAP Note 13725 - Several line items for transfer postings

Symptom:

When you create a transfer posting by entering a line item, the
system automatically generates a second line item as soon as the
document is posted.
The first line item updates the issuing stock, the second line item
updates the receiving stock. This procedure is primarily used for the
following movement types: 301-304, 309-314, 321-324, and 401-404.

However, this procedure is not used in the case of placements in
storage from or (in the case of reversals) to an in-transfer stock or
an in-transit stock. This applies primarily to movement types
101-102, 122, 305-306, 315-316.

Cause and prerequisites

This procedure ensures that a separate line item is generated for
every material segment for which inventory can be posted.

Solution
Please consider these facts for your analyses and reports.

Key word: Transfer postng

SAP Note 13722 - DBIF_RSQL_INVALID_CURSOR when creating biling doc.

Symptom:

When you create a billing document, ABAP/4 run-time error
DBIF_RSQL_INVALID_CURSOR occurs in program SAPLV60A. The error
occurs at command SELECT * FROM VBPA WHERE VBELN = XKOMFK-VBELN

Cause and prerequisites

In the text scheme for determining the item texts, at least one
TEXT-ID was assigned the MUST (display) indicator with value
Y (text displayed when copied).

Solution
For billing document item texts, the must (display) indicator must
have value "X" or " ".
Entering the value 'Y' leads to value ' '.
The following information appears:
"No text dialog window can be sent for billing document texts"

Key word: Billing doc.

SAP Note 13719 - Preliminary transports to customers (note for customers)

Symptom:

An SAP consultant or support representative has made data available to the customers in the form of a note attachment (or - possible until January 2003 - on sapservX) for the import into the customer system (as described in the internal Note 11920).

Other terms

sapserv3 Walldorf
sapserv4 Foster City
sapserv5 Tokyo
sapserv6 Sydney
sapserv7 Singapore

Reason and Prerequisites

As of Release 3.0, preliminary transports (delivery of preliminary corrections) have been delivered in the form of Support Packages. There are also preliminary transports of developments that are imported using the manual procedure described here.

When importing requests from SAP systems, you must ensure that requests in area 900000 - 999999 (for example, Q30K90821), possibly collide with customized transports, especially if there are customer systems with the same name (in the example, this would be Q30). These jobs should be rejected if the names are the same.

In systems with Releases older than 4.6C the following is important: When you import jobs from SAP systems, note that jobs in the range 900000 - 999999 (for example Q30K900821) are treated as customer- specific transports. The transport objects are considered modified. Such jobs should therefore be rejected if the system is older than 4.6C. As of Release 4.6C, this restriction does not apply.

The transport properties will be imported with the transported objects. After the import the original system will therefore no longer be SAP but for example, P30 if the export was carried out in P30. As user DDIC, you can maintain this in Transaction SM31 in Table TADIR, and change it to SAP again. This is required if a system with the same name as the export system exists in your system landscape.

Solution

Two files are generated when exporting:

• The R3trans file which contains the actual data.

• The transport information file which contains the control-data for the transport.
  

This data has been made available to your either as a note attachment or directly on a sapservX host.

1. Situation: The data is available as a note attachment (procedure as of February 2003).

a) Download the data from the note dealing with preliminary transport, as described in Note 480180.

b) The data is contained either in a ZIP or in a SAR archive that you will need to unpack.

2. Situation: The data is available on sapservX and has to be transferred using ftp. You can find the data in directory general/R3server/abap/note.0012345.

The following describes the procedures for UNIX, WINDOWS, and OS/400.

a) UNIX:

The binary mode MUST be switched on for the data transfer, otherwise the R3trans file will be destroyed.
The customer calls ftp as follows:

cd /usr/sap/trans/tmp /* cd at customer site */
ftp sapservx /* Start file transfer program */
/* Enter 'ftp' as user and password */
cd general/R3server/abap/note.nnnnnnn /* directory */
bin /* Switch to binary mode */
get Rnnnnnn.xxx /* Fetch R3trans data file, name */
/* depends on the transport request.*/
get Dnnnnnn.xxx /* Fetch SDO file if it exists. */
get Knnnnnn.xxx /* Fetch the transport info file. */
bye /* End ftp. */
mv Rnnnnnn.xxx ../data /* Copy R3trans file into data dir. */
mv Dnnnnnn.xxx ../data /* SDO file into the data dir. */ mv Knnnnnn.xxx ../cofiles /* info file into cofiles dir. */

b) Windows
Since the text mode on WINDOWS is different from the text mode on UNIX, using ftp the text files (command files and buffer) have to be transferred in text mode and the data files in binary mode.
Example: Assuming that the transport request is called P21K000123, then the following files have to be transferred in the specified mode using ftp:

Name Contents Mode Target directory Exists
R000123.P21 data bin \usr\sap\trans\data always
K000123.P21 info ascii \usr\sap\trans\cofiles always
D000123.P21 data bin \usr\sap\trans\data only for ADO

It is essential to use the correct mode when transferring data, otherwise the import cannot be carried out successfully.
The customer calls up ftp as follows:
<>
cd \usr\sap\trans\tmp /* cd at the customer site */
ftp sapservX /* start file transfer program */
/* enter 'ftp' as user and password */
cd dist general/R3server/abap/note.0012345 /* directory */
bin /* switch to binary mode */
get Rnnnnnn.xxx /* fetch R3trans data file, name */
/* depends on the transport request */
get Dnnnnnn.xxx /* fetch SDO file, if it exists */
ascii /* switch to text mode */
get Knnnnnn.xxx /* fetch transport info file */
bye /* end ftp */
/* Copy..... */
move Rnnnnnn.xxx ..\data /*R3trans file to data dir. */
move Dnnnnnn.xxx ..\data /*SDO file to data directory */
move Knnnnnn.xxx ..\cofiles /*Info file to cofile directory*/

c) AS/400
Use command APYABFIX: APYABFIX SID() FROMHOST('sapserv3')
FROMDIR('general/R3server/abap/note.0012345')
TRANSPORT('*FROMDIR')
TPIMPORT(*YES)

Replace the place-holders , sapserv3 and note.0012345.
The parameter value TRANSPORT(*FROMDIR) controls the automatic determination of the transport request number while the system searches through the specified directory for transport files. The last parameter TPIMPORT initiates the calls tp 'addtobuffer ...' and tp 'import ...' for the transport request.
If the execution of this command causes the error 'Too many files found in directory' copy the files manually into your data and cofile directory using ftp.

<>
ftp sapservX /* start file transfer program */
/* enter 'ftp' as user and password */
cd dist general/R3server/abap/note.0012345
/* to change to the directory that */
/* contains the transport */
namefmt 1
/* to access the file system of AS/400 */
lcd '/usr/sap/trans/data'
/* change to the transport data directory locally*/
bin /* Switch to binary mode */
get Rnnnnnn.xxx /* fetch R3trans data file, name of */
/* file depends on transport request. */
get Dnnnnnn.xxx /* fetch SDO file if it exists. */
lcd '/usr/sap/trans/cofiles'
/* change to cofile directory locally */
ascii /* following transfer in text mode */
get Knnnnnn.xxx /* fetch transport info file. */
quit /* end ftp. */

Manual import of the transports:
Logon as OFR
tp 'pf= addtobuffer '
tp 'pf= import U26'

Starting the import:

• Start the import as follows:

a) UNIX:
as user adm:
/usr/sap//SYS/exe/run/tp addtobuffer \
pf=
/usr/sap//SYS/exe/run/tp import U26 \
pf=

Replace with the current SID, for example, C11.
Example:
/usr/sap/C11/SYS/exe/run/tp addtobuffer P21K000123 C11 pf=/usr/sap/trans
/bin/TP_DOMAINABC.PFL
/usr/sap/C11/SYS/exe/run/tp import P21K000123 C11 U26 pf=/usr/sap/trans
/bin/TP_DOMAINABC.PFL

b) Windows:
as user adm:
cd \usr\sap\trans\bin
\usr\sap\\SYS\exe\run\tp addtobuffer
\usr\sap\\SYS\exe\run\tp import U26
Replace by the current SID which is for example C11.
Example:
cd \usr\sap\trans\bin
\usr\sap\C11\SYS\exe\run\tp addtobuffer P21K000123 C11
usr\sap\C11\SYS\exe\run\tp tst P21K000123 C11
\usr\sap\C11\SYS\exe\run\tp import P21K000123 C11 U26

c) AS400: Already completed by the command above.

• A prerequisite for the import is that the periodic background job RDDIMPDP has been scheduled in the target system (see manual BC System Administration, Appendix D).

• Specifying unconditional modes 2 and 6 (u26) results in original objects and objects in unconfirmed repairs being overwritten as well. If the "tp tst" call (test import) ends with return code 8 as a result of such objects, we recommend the release of the open repairs before the import so that the corresponding versions of the modified objects will be generated in the version database.

Subscribe to: Posts (Atom)

Search

Top 10 SAP OSS Notes

• SAP OSS Notes

  Get the SAP OSS Notes widget and many other great free widgets at Widgetbox ! Not seeing a widget? ( More info )
• SAP Note 22640 - ABAP/4 query: Add. structures in logical databases

  Symptom: Question: How can structures which are connected to logical databases as an extension be used by ABAP/4 query? Some logical databa...
• SAP Note 16083 - Standard jobs, reorganization jobs

  Symptom: There are a number of jobs that must periodically run in a live R/3 installation, for example, to delete outdated jobs or spool o...
• SAP Note 24832 - Pricing rules / TVCPF

  Symptom: Depending on the situation, the system should redetermine conditions or not. For this, a differentiated control is required, for ex...
• SAP Note 18023 - Jobs EU_INIT, EU_REORG, EU_PUT

  Symptom: What are the jobs EU_INIT (program SAPRSEUC), EU_REORG (program SAPRSLOG), and EU_PUT (program SAPRSEUT), which are automatically...
• SAP Note 11162 - Invoice split criteria in billing document .

  Symptom From a number of deliveries or sales orders more than one billing document is created. Cause and prerequisites The invoice split ma...
• SAP Note 25528 - Parameter rdisp/max_wprun_time

  Symptom: The meaning of parameter rdisp/max_wprun_time is not clear. Other terms TIME_OUT, timeout, SY 098, Time limit exceeded, instance p...
• SAP Note 22559 - BTCI material - Add. costing functions are impossible

  Symptom: Basic data transfer for the material master with standard batch input program RMMMBIM0. The field contents for the additional cos...
• SAP Note 28869 - Printout of changes although field not print-relevant

  Symptom: When a field (item or header) is changed in a purchasing document, a change message is generated although the field is non-print-...
• SAP Note 11104 - PPPR: General note on printing production orders.

  Symptom Lack of knowledge about the general printing procedure in PPSFC. Other terms Print, production order, CO04, CO04N, shop paper printi...

Labels

\ abap account assignment Allocation authorization book books certification CO controlling areas CPIC download free GA715 help view Help view prior index series javascript:void(0) LIST_ILLEGAL_PAGE Master data ME51 Number Ranges pdf rapidshare release strategy RKCORR01 SAP SAPcomm SAPFAX.DLL SAPLPD.EXE Service submit T800 table unknown

• ABAP
• SAP
• Help View
• Certification
• Books

Latest Posts

Subscribe Enter your email address: Delivered to your inbox instantly

Articles

• Home
• Where to find SAP OSS NOTES?
• How to implement SAP OSS NOTES?
• What is SAP OSS NOTES?
• How to create new SAP OSS Note?
• Top SAP Downloads