Symptom
Does R/3 support OSI protocols?
Cause and prerequisites
Customer inquiry
Solution
1. Communications from R/3 to external systems
2. Communications within R/3
1. Communications from R/3 to external systems
----------------------------------------------
OSI protocols are supported in the communications to external systems via MAIL and EDI. The SAP applications use non-SAP products (e.g. CoCoNet, SoftSwitch) to implement the actual data transmission. These are based on OSI protocols (e.g. X.400 via OSI transport and X.25).
2. Communications within R/3
----------------------------
For communications within a distributed R/3 System (communication between the database server, application servers, and frontends), only TCP/IP is currently supported.
SAP is currently examining the feasibility of porting R/3 to OSI protocols (including check of the required prerequisites, e.g. that OSI products are available on the required platforms).
Key word: OSI
SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
27.11.10
SAP Note 10295 - Rejection due to absence during non-active period.
Symptom
Program : RPCALCD0
RPCALCD0 rejects a personnel number and displays the message: Absence not available in active time period.
Cause and prerequisites
An absence intersects with a time period in which the employee is identified as not active in Infotype 0000.
Solution
The employee data must be corrected. For various reasons (tax breakdown, DUEVO reporting) the absence must be available and is the primary information.
Infotyp 0000 may not set the employee to 'not active' and must therefore be corrected or deleted. If you want correct headcount statistics in the case of long-term absences (long-term maternity leave, military service), the employee muist be appropriately identified in Infotype 0001 (e.g., personnel group).
Key word: RPCALCD0
Program : RPCALCD0
RPCALCD0 rejects a personnel number and displays the message: Absence not available in active time period.
Cause and prerequisites
An absence intersects with a time period in which the employee is identified as not active in Infotype 0000.
Solution
The employee data must be corrected. For various reasons (tax breakdown, DUEVO reporting) the absence must be available and is the primary information.
Infotyp 0000 may not set the employee to 'not active' and must therefore be corrected or deleted. If you want correct headcount statistics in the case of long-term absences (long-term maternity leave, military service), the employee muist be appropriately identified in Infotype 0001 (e.g., personnel group).
Key word: RPCALCD0
SAP Note 10285 - Connection ABAP/4 Query to SAP-EIS
Symptom
Query data cannot be transferred to SAP-EIS. The function keys and
selection parameters are not displayed.
Cause and prerequisites
The query may have been created as a multiple-line query, in which case
a transfer to SAP-EIS is not possible.
Solution
Create the query as a one-line query.
Key word: Query -> EIS
Query data cannot be transferred to SAP-EIS. The function keys and
selection parameters are not displayed.
Cause and prerequisites
The query may have been created as a multiple-line query, in which case
a transfer to SAP-EIS is not possible.
Solution
Create the query as a one-line query.
Key word: Query -> EIS
SAP Note 10283 - Inconsistencies between T162 and T162T.
Symptom
Inconsistencies between field selection keys (T162) and their
descriptions (T162T).
Cause and prerequisites
Some table entries missing in standard system.
Solution
As the tables can also be maintained by customers via SM31, not all
errors are necessarily stem from the SAP side. However, the following
entries in table T162T are missing in the system supplied by us:
PT3L Subcontracting item, scheduling agreement
PT5A 3rd.-party item RFQ
PT5B 3rd.-party item requisition
PT5F 3rd.-party item purchase order
PT5L 3rd.-party item scheduling agreement
However, if an entry is missing in table T162, the customer should add
one as required.
In Rel. 3.0, T162 and T162T will be synchronized again.
Key word: T162 T162T
Inconsistencies between field selection keys (T162) and their
descriptions (T162T).
Cause and prerequisites
Some table entries missing in standard system.
Solution
As the tables can also be maintained by customers via SM31, not all
errors are necessarily stem from the SAP side. However, the following
entries in table T162T are missing in the system supplied by us:
PT3L Subcontracting item, scheduling agreement
PT5A 3rd.-party item RFQ
PT5B 3rd.-party item requisition
PT5F 3rd.-party item purchase order
PT5L 3rd.-party item scheduling agreement
However, if an entry is missing in table T162, the customer should add
one as required.
In Rel. 3.0, T162 and T162T will be synchronized again.
Key word: T162 T162T
SAP Note 10280 - Account assignment project or WBS element.
Symptom
The field project or WBS element is not displayed within the sales
order on the account assignment screen in the standard system for
the item category TPK.
Additional key words
Cause and prerequisites
The incorrect requirement class is used.
Depending on the consumption indicator from the requirement class
(T459k), the field is displayed or not.
Consumption indicator = P.
Solution
Check material with its requirements type and requirement class.
Key word: Acct assignment
The field project or WBS element is not displayed within the sales
order on the account assignment screen in the standard system for
the item category TPK.
Additional key words
Cause and prerequisites
The incorrect requirement class is used.
Depending on the consumption indicator from the requirement class
(T459k), the field is displayed or not.
Consumption indicator = P.
Solution
Check material with its requirements type and requirement class.
Key word: Acct assignment
SAP Note 10274 - EM: AA937 "Index series nnnnn has several base years"
Symptom
When you enter an index series in AM master data maintenance,
you get error message AA937: "Index series nnnnn has several
base years". The description indicates that an index series
with several base years may not be used in AM (only in
real-estate management).
Cause and prerequisites
The index series used is assigned to an index class,
in which the indicator for several base years is set.
Solution
Only index series assigned to a class where the indicator for
several base years is not set can be used.
Keyword: Indexing
Technorati : index series
Del.icio.us : index series
SAP Note 10270 - Release strategy independent of acct. assgn. cat.
Symptom:
The release strategy is selected regardless of the
account assignment category.
Cause and prerequisites:
For the account assignment to be taken into account in
the selection of the release strategy, all the fields
(criteria) must be maintained for every entry (OME6) for
which the account assignment is to determine the strategy
selection. Therefore, the material group and the plant must
be maintained.
As of Release 3.0, two release procedures are available.
The release procedure without classification (release procedure as in
Release 2.0, 2.1, and 2.2) exhibits the same problem in Release 3.0.
In addition to the release procedure without classification, a release
procedure with connection to classification was created. In this
release procedure, it is possible to establish a strategy dependent on
the characteristic 'account assignment category'.
Key word: ME51 Release
Technorati : ME51, account assignment, release strategy
Del.icio.us : ME51, account assignment, release strategy
SAP Note 10262 - LIST_ILLEGAL_PAGE or LIST_NO_PAGETAB
Symptom
ABAP/4 runtime error LIST_ILLEGAL_PAGE or LIST_NO_PAGETAB
Cause and prerequisites
This error occurs when NEW-PAGE PRINT ON is used with TOP-OF-PAGE.
Solution
Do not use NEW-PAGE PRINT ON with event TOP-OF-PAGE.
Keyword: LIST_ILLEGAL_PAGE
Technorati : LIST_ILLEGAL_PAGE
Del.icio.us : LIST_ILLEGAL_PAGE
SAP Note 10217 - Object numbers missing in index tables
Symptom
Entries are missing in Tables ONRKS, ONRKL, ONROR (together in ONR00),
although the corresponding master data still exists.
ONRKS <-> CSKS (field OBJNR)
ONRKL <-> CSSL (field OBJNR)
ONROR <-> AUFK (field OBJNR) .
Correction program RKCORR03 (available from 2.1J and 2.2A in Standard, preliminary correction available) which reads the master data and enters the missing entries to the ONR tables during the production run. This can be used for object types KS (Cost Centers), KL (Cost Centers with acitivty type) and OR (Orders).
The report for the preliminary correction can be found on SAPSERV3 in
the directory
dist/permanent/note.0010217
K014792.P22
R014792.P22
You will find information on loading corrections from this directory in Note 13719. For information about how to implement a preliminary correction, refer to note 8550.
If list editing is used for the cost centers, install the following correction to prevent the entries from being deleted on posting. The correction is contained in Standard as of 2.2C.
1. Select "Maintain function module" (SE37)
2. Enter the name of the function module RK_COSTCENTER_UPDATE
Select subobject 'Import/export parameter interface'. Select
'Change'
3. Set the default for both parameters KHINR_NEW and KHINR_OLD to
'-dummy'
Import/export parameters for function module RK_COSTCENTER_UPDATE:
Parameters Ref.field/structure Default
KHINR_NEW CSKS-KHINR '-dummy' <<
NOTE!
The new default value in the lines marked must be entered within quotation marks as specified above!
Key word: OBJNR
Additional key words
Entries are missing in Tables ONRKS, ONRKL, ONROR (together in ONR00),
although the corresponding master data still exists.
ONRKS <-> CSKS (field OBJNR)
ONRKL <-> CSSL (field OBJNR)
ONROR <-> AUFK (field OBJNR) .
This results in missing selections in CO reports.
The effect occurs for cost centers if cost centers are changed using list editing.
Inconsistent transports, client copy of individual tables or editing cost centers with cost center list editing (KS08). Here the numbers of the cost centers selected are deleted on posting.
Cause and prerequisitesCorrection program RKCORR03 (available from 2.1J and 2.2A in Standard, preliminary correction available) which reads the master data and enters the missing entries to the ONR tables during the production run. This can be used for object types KS (Cost Centers), KL (Cost Centers with acitivty type) and OR (Orders).
The report for the preliminary correction can be found on SAPSERV3 in
the directory
dist/permanent/note.0010217
K014792.P22
R014792.P22
You will find information on loading corrections from this directory in Note 13719. For information about how to implement a preliminary correction, refer to note 8550.
If list editing is used for the cost centers, install the following correction to prevent the entries from being deleted on posting. The correction is contained in Standard as of 2.2C.
1. Select "Maintain function module" (SE37)
2. Enter the name of the function module RK_COSTCENTER_UPDATE
Select subobject 'Import/export parameter interface'. Select
'Change'
3. Set the default for both parameters KHINR_NEW and KHINR_OLD to
'-dummy'
Import/export parameters for function module RK_COSTCENTER_UPDATE:
Parameters Ref.field/structure Default
KHINR_NEW CSKS-KHINR '-dummy' <<
NOTE!
The new default value in the lines marked must be entered within quotation marks as specified above!
Key word: OBJNR
Additional key words
CO REPORTS, GR601, client copy, missing data, KB420, KSB1 ----- SUPPORTGUIDE 20010411140028 -----
REPORTWRITER, SGRW_AMOUNT, SGRW_RC_STRUCTURE, SGRW_DATA, SGRW_DOCU_CONS_NOTE
SGRW_OM
SAP Note 10212 - CLOSE_FORM is invalid, OPEN_FORM is missing (TD423)
Symptom
The most frequent cause is that the form does not exist.
Up to and including Release 2.0, the forms must physically exist in the client. You can achieve this by using Transaction SE71 to copy the forms from client 000 to the current client (Utilities - Copy by client).
Cross-client access has been implemented from Release 2.1 onwards - that is, when a form does not exist in the current client, it is read from client 000.
You can refer to Customizing for the form. Make sure that an active version exists.
If this is not the cause, you should determine which exception is triggered by debugging (break point for function module OPEN_FORM). Alternately you can also use the form debugger (Transaction SE71, Utilities -> Activate debugger). For more information refer to Note 19104.
Note that you might have to activate the update debugging if the application is printing in the update.
When you print a termination occurs: CLOSE_FORM is invalid, OPEN_FORM is missing (error message TD423)
Sap script, TD423, termination
Cause and prerequisitesThe program that calls the Sap script modules does not react to the situation that the form could not be opened at all after the OPEN_FORM function call - that is, the CLOSE_FORM function call is performed anyway, and the exception was not trapped.
In the following cases the function module OPEN_FORM returns an exception to which the print program should react:
Can celled by user
Invalid output device
Form not found
Previous print not exited with CLOSE_FORM
The most frequent cause is that the form does not exist.
Up to and including Release 2.0, the forms must physically exist in the client. You can achieve this by using Transaction SE71 to copy the forms from client 000 to the current client (Utilities - Copy by client).
Cross-client access has been implemented from Release 2.1 onwards - that is, when a form does not exist in the current client, it is read from client 000.
You can refer to Customizing for the form. Make sure that an active version exists.
If this is not the cause, you should determine which exception is triggered by debugging (break point for function module OPEN_FORM). Alternately you can also use the form debugger (Transaction SE71, Utilities -> Activate debugger). For more information refer to Note 19104.
Note that you might have to activate the update debugging if the application is printing in the update.
SAP Note 10206 - Print payment advice: RFFOAVIS selects nothing
Symptom
Start the print programs for data carriers; these start with RFFO*
Key word: RFFOAVIS
Payments, F110:
After payment, customer attempts to print payment advice with RFFOAVIS.
However, the program does not select anything.
No actual clearing (that is, credit memos and invoices balance to
zero, no payment required) exists; RFFOAVIS was intended for
clearing. For payment advice forms associated with a payment (e.g.
due to form overflow when many items are involved), use the
appropriate print program for the data carrier.
Start the print programs for data carriers; these start with RFFO*
Key word: RFFOAVIS
Payments, F110:
SAP Note 10194 - Menu texts maintained by customers have disappeared
Symptom
Advance correction:
In function module RS_CUA_MOD_DEACTIVATE, mark the line
FUN-LONGTEXT = FUN-SHORTTEXT.
with an asterisk (around line 390 in the source text).
When an add-on project is deactivated, menu texts
maintained by the customer are replaced by the SAP texts.
Advance correction:
In function module RS_CUA_MOD_DEACTIVATE, mark the line
FUN-LONGTEXT = FUN-SHORTTEXT.
with an asterisk (around line 390 in the source text).
SAP Note 10190 - Not all table entries are transported
Symptom
Advance correction: change transport objects CMOD, SMOD:
Start program RDDTLOGO (select "Change" in the pop-up), select CMOD
(SMOD) in the subsequent list, then Table view --> Other view.
In this screen, remove the second asterisk ("*") from entry
R3TR TABU MODACT (R3TR TABU MODSAP)
Therefore, the correct entries are:
CMOD: R3TR TABU MODACT
/&/*
SMOD: R3TR TABU MODSAP
/&/*
Any add-ons (add-on projects) that have already been transported
must then be transported again using SMOD (CMOD):
SMOD (CMOD) --> Enter add-on (add-on project) --> Change and save
--> A correction is opened. Use the Correction System to release
the correction to a transport request and transport it.
"Restart Import", or taking the command file from an existing
transport request, will not correct the error.
Key word: SMOD, CMOD
During the transport of SAP enhancements (R3TR SMOD ...) or add-ons,
the entries from table MODSAP are not transported.
During the transport of customer enhancement projects (R3TR CMOD ...),
the entries from table MODACT are not transported.
Error in the definition of transport objects SMOD and CMOD.
Advance correction: change transport objects CMOD, SMOD:
Start program RDDTLOGO (select "Change" in the pop-up), select CMOD
(SMOD) in the subsequent list, then Table view --> Other view.
In this screen, remove the second asterisk ("*") from entry
R3TR TABU MODACT (R3TR TABU MODSAP)
Therefore, the correct entries are:
CMOD: R3TR TABU MODACT
/&/*
SMOD: R3TR TABU MODSAP
/&/*
Any add-ons (add-on projects) that have already been transported
must then be transported again using SMOD (CMOD):
SMOD (CMOD) --> Enter add-on (add-on project) --> Change and save
--> A correction is opened. Use the Correction System to release
the correction to a transport request and transport it.
"Restart Import", or taking the command file from an existing
transport request, will not correct the error.
SAP Note 10187 - Users with large master rec. missing authorizations
Symptom
Use 'User maintenance -> Info -> Overview -> User values' to see whether the missing authorizations are actually preset in the master record. Log on under the user ID with the missing the authorizations and call Transaction SU56. Check the list below to see whether all the authorizations are displayed (for example, the authorizations for objects S_USER...) that you saw in Info...
If not, then a master record with a large number of authorizations is usually involved.
Remove any unnecessary or redundant authorizations from the receptive master record. Too many authorizations per authorization object in a master record have a detrimental effect on the performance of authorization checks.
If you do, however, require a user with many authorizations, then you have the option of setting the following system parameter:
auth/auth_number_in_userbuffer
Depending on the release you are using, it has the following default values:
| 3.1G | 3.1H | 4.0A | 4.0B
--------------------------------------------
Minimum value | | | 800 | 1000
Standard value | 800 | 2000 | 1000 | 2000
(Maximum value | 2000 | 5000 | 3000 | 5000 planned!)
Maximum value | 2000 | 2730 | 2730 | 2730
To be exact, the release specifications are as follows:
3.1G: 3.0x, 3.1G, 3.1H to patch level 177, 3.1I to 49
3.1H: 3.1H from patch level 178, 3.1I from patch level 50
4.0A: 4.0A, 4.0B to patch level 72
4.0B: 4.0B from patch level 73
Caution: At present a value greater than 2730 leads to authorizations being cut off. See Note 120300. Kernel patches are in preparation.
You can set the higher maximum values provided by the corrected kernel in spite of the maximum value (2000) displayed by RZ11.
The check-program sappfpar generates the error message: "unexpected parameter: auth/auth_number_in_userbuffer". The message can be ignored, since it is not used during system start.
As of Release 3.1G
After you have restarted the system, reset the user buffer. You can find the required function in Transaction SU01 under the menu options 'Environment -> Mass changes -> Reset all user buffers'.
This is no longer necessary (and, at the second call, may even lead to warnings or error messages) from kernel patch 3.1H level 163, 3.1I level 1 (on CD), 4.0B level 73.
Key word: User buffer
The system may deny a user the execution of a function, even though that user has the appropriate authorization in the master record.
The system log contains entries such as:
'User buffer too small for user xxxxx'.
Cause and prerequisites
The user has many authorizations, (normally more than 800), so that the user buffer overflows.
Use 'User maintenance -> Info -> Overview -> User values' to see whether the missing authorizations are actually preset in the master record. Log on under the user ID with the missing the authorizations and call Transaction SU56. Check the list below to see whether all the authorizations are displayed (for example, the authorizations for objects S_USER...) that you saw in Info...
If not, then a master record with a large number of authorizations is usually involved.
Remove any unnecessary or redundant authorizations from the receptive master record. Too many authorizations per authorization object in a master record have a detrimental effect on the performance of authorization checks.
If you do, however, require a user with many authorizations, then you have the option of setting the following system parameter:
auth/auth_number_in_userbuffer
Depending on the release you are using, it has the following default values:
| 3.1G | 3.1H | 4.0A | 4.0B
--------------------------------------------
Minimum value | | | 800 | 1000
Standard value | 800 | 2000 | 1000 | 2000
(Maximum value | 2000 | 5000 | 3000 | 5000 planned!)
Maximum value | 2000 | 2730 | 2730 | 2730
To be exact, the release specifications are as follows:
3.1G: 3.0x, 3.1G, 3.1H to patch level 177, 3.1I to 49
3.1H: 3.1H from patch level 178, 3.1I from patch level 50
4.0A: 4.0A, 4.0B to patch level 72
4.0B: 4.0B from patch level 73
Caution: At present a value greater than 2730 leads to authorizations being cut off. See Note 120300. Kernel patches are in preparation.
You can set the higher maximum values provided by the corrected kernel in spite of the maximum value (2000) displayed by RZ11.
The check-program sappfpar generates the error message: "unexpected parameter: auth/auth_number_in_userbuffer". The message can be ignored, since it is not used during system start.
As of Release 3.1G
After you have restarted the system, reset the user buffer. You can find the required function in Transaction SU01 under the menu options 'Environment -> Mass changes -> Reset all user buffers'.
This is no longer necessary (and, at the second call, may even lead to warnings or error messages) from kernel patch 3.1H level 163, 3.1I level 1 (on CD), 4.0B level 73.
SAP Note 10170 - BRARCHIVE does not find archive logs to save
Symptom
First possibility:
Change the last line in the summary log of brarchive
/$ORACLE_HOME/saparch/arch.log (begins with #ARCHIVE..)
using a text editor. Reset the specified log sequence number
(the first field after #ARCHIVE..) to 0.
Example:
Last line:
#ARCHIVE.. 2786 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
is changed to:
#ARCHIVE.. 0 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
Once you have performed the backup, undo the change again so that the
log contains the correct information. The changed line before the last
line is now the last but one.
As of SAP version 2.1I or 2.2C, this change will no longer be necessary
if the backup with brarchive is made with an open DB because brarchive
recognizes that a RESETLOGS took place. If the first archive log backup
takes place with a closed DB, however, this manual action will still be
necessary.
Second possibility:
First use option -s.
Key word: BRARCHIVE (with option -s or -sd)
"BR013W No archive logs found to be processed."
Message arrives although the logs were never saved.
1.
If the DB is opened after a recovery with
ALTER DATABASE OPEN RESETLOGS;
the "log sequence number" is also reset to 1. However, since the
brarchive log arch
contains entries for successful archive log backups with higher numbers,
brarchive does not recognize the new logs as logs to be saved.
The same may happen after a database migration from ORACLE version 6 to
ORACLE version 7 in a SAP Release upgrade from 2.0F/2.0G/2.0H to 2.1,
where the above-mentioned ORACLE command is given inplicitly.
2,
BRARCHIVE was started with option -sc/-scd before option -s was
used - second backup before the first one took place.
First possibility:
Change the last line in the summary log of brarchive
/$ORACLE_HOME/saparch/arch
using a text editor. Reset the specified log sequence number
(the first field after #ARCHIVE..) to 0.
Example:
Last line:
#ARCHIVE.. 2786 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
is changed to:
#ARCHIVE.. 0 /usr/ora/P20/saparch/P20arch_2786 1994-05-18 15.55.55
Once you have performed the backup, undo the change again so that the
log contains the correct information. The changed line before the last
line is now the last but one.
As of SAP version 2.1I or 2.2C, this change will no longer be necessary
if the backup with brarchive is made with an open DB because brarchive
recognizes that a RESETLOGS took place. If the first archive log backup
takes place with a closed DB, however, this manual action will still be
necessary.
Second possibility:
First use option -s.
SAP Note 10168 - Wildcard specification of texts in correction
Symptom
Releases 3.0A, 2.2A, and 2.1G contain a report RSTXTRAN that performs the task described above. For more details, please refer to the report documentation.
Key word: Text transport
How can you enter a set of text keys in a correction or repair without having to enter them "manually" in the correction using R3TR TEXT ....? In earlier releases, specifications of transport entries for texts according to the scheme
R3TR TEXT object,name,id,lang
allowed the use of the asterisk (*) for wild card selection. The transport system no longer allows the entry of wild card keys.
RSTXR3TR, R3TR, Text transport, Sap script
For security reasons, the transport system no longer allows wild card keys to be specified for transport objects.
SolutionReleases 3.0A, 2.2A, and 2.1G contain a report RSTXTRAN that performs the task described above. For more details, please refer to the report documentation.
SAP Note 10163 - Problems with invoice printing
Symptom
Re 1. Using an invoice from online selection, check causes 1 and 2
and, after any necessary correction to the Customizing
configuration, restart the invoice printing run with repeat
printing. In the case of d, in customizing Hospital-Services,
complete the input/output allocation 'printer' by entering '*'
where 'printer' is the output device, to which all
printing jobs go which are not clearly specified to an output
device. It is possible to enter and allocate all batch input
devices (instead of using '*').
Caution: In case in this table the entry ' ', ' ' is present, it has tobe deleted by means of an ABAP/4 program, since with the entry '*', 'printer' is bypassed.
With ISH Release 2.24, the selection fields 'printer' and 'terminal' have been newly organized for invoice printing. Especially, by using 'terminal' a pseudo-terminal can now be specially supported for invoice printing in the background. With correct customizing the above described problems may be avoided. Please see the report documentation (expanded help).
Re 2. Check the Customizing configuration. Typical error:
a. "Standard print" not specified everywhere; this specification has to be entered for each type of invoice as in
'Event-Organization level allocation' and 'Organization level (with/without conditions)'
b. The invoice printing for the list runs by 'Organization level without conditions', as opposed to individual invoices. Thus there may not be any entry present for the organization level RECH_02 in the column 'Type of organization level', as opposed to the individual invoices.
Invoice printing problems:
1. No invoices are printed during invoice printing run in batch input;
instead, only a list of the invoices is printed.
2. Online: no printing (e.g. invoice list not printed), but no
error message either.
Invoice printing, printing problems, form control, printer, batch, background, consultant
Cause and prerequisitesRe 1. a. Invoices had already been printed and "No repeat printing"
was specified in the report variant.
b. Selection criteria are too restrictive.
c. Problems with printing Customizing; because printing was
in batch, however, this is not readily apparent.
d. The batch input device has not been allocated to a
printer. This error does not appear Online, because the
terminal has been allocated to a printer.
Re 2. Incorrect customizing of invoice printing.
Re 1. Using an invoice from online selection, check causes 1 and 2
and, after any necessary correction to the Customizing
configuration, restart the invoice printing run with repeat
printing. In the case of d, in customizing Hospital-Services,
complete the input/output allocation 'printer' by entering '*'
where 'printer' is the output device, to which all
printing jobs go which are not clearly specified to an output
device. It is possible to enter and allocate all batch input
devices (instead of using '*').
Caution: In case in this table the entry ' ', ' ' is present, it has tobe deleted by means of an ABAP/4 program, since with the entry '*', 'printer' is bypassed.
With ISH Release 2.24, the selection fields 'printer' and 'terminal' have been newly organized for invoice printing. Especially, by using 'terminal' a pseudo-terminal can now be specially supported for invoice printing in the background. With correct customizing the above described problems may be avoided. Please see the report documentation (expanded help).
Re 2. Check the Customizing configuration. Typical error:
a. "Standard print" not specified everywhere; this specification has to be entered for each type of invoice as in
'Event-Organization level allocation' and 'Organization level (with/without conditions)'
b. The invoice printing for the list runs by 'Organization level without conditions', as opposed to individual invoices. Thus there may not be any entry present for the organization level RECH_02 in the column 'Type of organization level', as opposed to the individual invoices.
Subscribe to:
Posts (Atom)