SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
This note describes how the update program can be deactivated in the currency translation of the components FI-LC and FI GLX (FI-SL).
This can be useful if DEADLOCK problems occur.
GC29, GWUL, OC91, GWUG, RGCUMR00, RGUUMR00, RGUUMR01
SAPLGUWU DBIF_RSQL_SQL_ERROR UPDATE_TT_GLT2 GLT2 LGUWUF10
ORA-00060
Error message V1139 occurs during a goods movement for a sales document which was assigned to a WBS.
Cause and prerequisitesWhen entering a customer independent requirement with transaction MD81, the sales unit is not determined. The stockkeeping unit is also missing. Message V1384.
The function ´vertical relationship´ does not work in the graphic display of a work center hierarchy from transaction CR22 (change work center hierarchy).
Procedure: Activate the higher-level node --> Edit --> Allocate --> vertical: no system response.
The functionality is not linked.
SolutionCM21
CM23
Services file not maintained correctly after installation in the Windows directory.
Cause and prerequisitesWith the installation of the frontend under Windows, a services file is also generated. It is stored in the Windows directory but is not found by Windows NT and other network systems under certain conditions.
Windows NT, for example, expects to find it in the WINNT\SYSTEM32\DRIVERS\ETC directory. Other network systems, e.g., Novell, store the services file in their own directories.
services
After a cycle has run, you can print the result by means of Cycle -> Output -> Print all. If the 'New spool request' field is selected with the subsequently requested print settings, a lot of small spool files are created instead of a large one. During print formatting with 132 columns, a printing termination after the first page is possible.
Cause and prerequisitesProgram error.
Transactions involved:
GA2B,GA4B,GA15,GA35,
KSU5,KSV5,KSUB,KSVB,
KSW5,KEU5.
For accounts which are managed in several currencies or in foreign currency, the output may be incomplete when there are differences:
Program error
SolutionSAPF070, multiple currency accounts
The runtime error DBIF_RSQL_INVALID_REQUEST occurs for reports which use the logical database SDF.
Cause and prerequisitesPreconditions: In the client, there are more than 250 company codes with the same chart of accounts that are to be edited by the report.
Cause: The logical database works with a range table, where a line is entered for all selected company codes for each chart of accounts. As a result, the SELECT statement becomes too large for the database and causes a runtime error.
Key words: SDF, SAPDBSDF, DBIF_RSQL_INVALID_REQUEST
During transaction VC/2 Sales Summary, the value for the 1st customer is always output when calling several customers on the 3rd page (statistics performance measures and last SD documents).
Cause and prerequisitesApplication areas were not deleted.
SolutionSales support RVKUSTA1
In the technical documentation, AAT is always displayed for the sales document type. However, it is not always used.
Cause and prerequisitesLPS17 setup and definition
In the BOM item, you can specify whether the components are to be provided by the customer or the vendor using the "material to be provided" indicator.
Consequently, the indicator has effects on MRP.
These components will not always be calculated in costing.
However, the indicator is not recognized in costing.
The "material to be provided" item is not excluded from costing because the component costing can be variably controlled by the field 'SANKA'.
BEIKZ
When posting an invoice, termination message FF723 occurs 'System error: internal error in table SALTAB'. A company code, in which a second and third local currency is defined, was used.
Cause and prerequisitesProgram error.
SolutionMR01 MRHR MRHG CREATE_BSET_ITEM
Maintenance calls with external operations do not create any purchase requisitions. This results in various follow-up problems in order processing.
Cause and prerequisitesProgram error
SolutionExternal operation IW32, PM_Order, external processing, PReq
Key words: MR01, US, taxes, jurisdiction code.
Error occurs in a number of cases:
Case 1
1) Entering a vendor invoice.
2) Enter tax code on vendor screen
but select tax code TAX-EXEMPT
Do not select "Calculate tax"
3) Tax code and jurisdiction code are copied from the purchase
order.
4) Simulate or post --> error
FF718 'Tax code is not maintained for jurisdiction code'.
If you select "Calculate tax" or you do not enter a tax code on the
vendor screen, the error does not occur.
Case 2
1) PO item with tax code TAX-EXEMPT
2) Invoice for PO: change tax code, do not enter tax
amount, have system calculate tax.
3) Simulate or post -->
Error FF718 'Tax code is not maintained for jurisdiction code'.
MR01 jurisdiction code FF718 TXJCD
Among the parameters that the user must maintain for project editing is
the length of the structure indicator.
As long as there is no project, you can enter any length in the interval
1-5 in table TCJ01.
Once there is a project you can no longer change the indicator.
In previous releases the system did not check whether a project already
existed.
Error in the coding
SolutionEntry of an invoice for a purchase order (MR01, MRHR). Preconditions: Goods-receipt-based invoice verification must be active; a new pricing occurs during goods receipt and a GR reversal occurs. In this constellation, a zero division occurs when entering the invoice.
Cause and prerequisitesProgram error
SolutionThe chart of account CAJP:
The language text of CAJP in 'J' is not replaced by upgrade. The table SKAT with the key '000JCAJP' contains still the data of rel.2.2x.
The chart of account CAJP is completely changed in the rel. 3.0x and the relevant tables SKAT, SKA1 and SKB1 are inconsistence.
The table CSKU with the key '000JCAJP' contains also the data of rel.2.2.
Error of final assembly of upgrade
delivered : SKAT, SKA1, SKB1
not delivered : CSKA, CSKB, CSKU (upto rel.2.2x)
SKAT, CSKU, Country version JP
Inspection for delivery in SD:
If there are cancelled partial lots for an inspection lot, you can in fact make usage decisions for the partial lots that are not cancelled, but, no inspection completion for the overall lot. Message QV147 is issued.
Missing status check concerning cancellation of partial lots
SolutionMessage QV147
The error message PC021 "XXL not installed" appears after the user has run the XXL dialog and therefore called the XXL List Viewer.
Cause and prerequisitesThe error message normally occurs before the XXL dialog is passed, for example because a previous check finds that the XXL macros are not installed on the frontend.
If the error message occurs AFTER the XXL dialog has run, this generally means that the installation of Microsoft Excel on the PC is incorrect. The XXL component reads the Windows Registry database on the PC to determine whether Excel is installed, and if so, in which directory. If there are incorrect entries in the Registry, for example, because Excel was manually deleted or moved into another directory after installation, the existence checks succeed initially, and it is only the attempt to start Excel that fails.
A special case is the 32-bit version of the 3.0C SAPGUI. This version contains a bug which makes it impossible to control external OLE Automation servers using this version. Please use the 16-bit- or a more recent 32-bit-version instead, or read note 37980 to find out where to retrieve a corrected 32-bit- / 3.0C version.
If a user has the authorization to modify change requests in the Workbench Organizer, but not the authorization to release and export change requests, he can still release and export the change requests in transaction SE01.
The same error occurs for tasks if a user has the authorization to change but not to release tasks.
On the other hand, the authorization check functions correctly in transactions SE09 and SE10 (Workbench Organizer or Customizing Request Management).
In SE01, only the modification authorization, and not the release or export authorizations are checked.
The problem only occurs if separate authorizations were created in the customer system for the authorization object S_TRANSPRT, as the authorization objects S_CTS_ADMIN, S_CTS_ALL, S_CTS_APPLIC, S_CTS_DEVELO and S_CTS_PROJEC delivered in the Standard R/3 System always have the change authorization.
With customer-specific reports, which use logical database CNJ and process a REJECT on AUFK1, AUFK2 or AUFK3 at the event GET ACT01, GET ACT02 or GET ACT03, the activities for the AUFK records are incorrectly displayed.
Cause and prerequisitesComponent allocations are not included from the routing, rate routing or rough-cut planning when scheduling planned orders or SOP orders.
Cause and prerequisitesError message 61258 appears during MRP run
The material is subject to management in batches.
The error message appears for deliveries regarding configured materials.
In the delivery, a batch split was carried out for the configured material. In the MRP records for the split BOM items, the CUOBJ of the configuration is missing.
SolutionBatch split, requirements, e258 61258
In the availability check for order creation and order release, message CO288 (no checking rule maintained) is issued, although the component should not be checked.
Cause and prerequisitesProgram error
SolutionProduction order
When maintaining the date categories of billing plans, you get the error SV037: Maintenance dialog for view V_TFPLT is incomplete.
Cause and prerequisitesMissing entry in TVDIR.
SolutionFI documents posted from the SD application have incorrect tax percentages in the display screen.
Cause and prerequisitesRequirement: documents are derived from billing documents and the tax was posted using Jurisdiction Codes.
Cause: program error
SAPLFACI, VF01, VF02, VF04
After upgrading your system to Release 3.0, you no longer find work centers using the matchcode search with short text, although the same search was successful in Release 2.1 or 2.2.
Cause and prerequisitesProgram error during the conversion to Release 3.0 (XPRA)
SolutionArchives that are saved locally by OnArchive cannot be read remotely.
Tapes saved locally with OnArchive can only be read locally. Tapes saved remotely can be read both remotely and locally. Remote means that '
saveset file not found
A network is allocated to a sales order with project settlement.
A network planning component is procured internally. In materials planning, a planned order which is converted into a production order is generated for reservation.
If a goods receipt is now posted for this production order, a message is issued to the effect that only one actual account assignment is to be entered.
The link between IS-H and CO does not work. Runtime errors of the type "CALL_FUNCTION_NOT_FOUND" occur.
Cause and prerequisitesCustomizing is incomplete.
SolutionMaintain the configuration under Configuration Hospital Basic data. Please read the Implementation Guide. Client 000 contains sample entries for the
RNHCO000 service transfer HCO
Planning board: An operation is not scheduled where you expected. There is a gap in capacity commitment.
Cause and prerequisitesAn initial capacity commitment was removed from the planning board. The above scheduling only occurred after this.
SolutionCapacity scheduling
This note describes all steps required to set up a common transport directory between UNIX, AS/400, and WINDOWS.
Other termsWINDOWS TRANSPORT DIRECTORY MIXED SYSTEMS SAMBA AS/400
SolutionOverview
Setting up a central transport directory WINDOWS/UNIX
1. Problem during transport between UNIX and Windows
2. Additional necessary software for UNIX
3. Actions for configuration with TMS
a) Maintain the transport profile
b) Change instance profile of SAP systems under Windows
c) Adjust the SAP profiles to UNIX format
4. Actions for configuration without TMS
a) Tools required under Windows
b) Setting the binary mode for SAP tools
c) Maintain the transport profile TPPARAM
d) Change instance profile of SAP systems under Windows
e) Adjust the SAP profile to UNIX format
5. Example for SAMBA configuration file
6. Example for a mixed transport file
----------> Windows Server Authentication
; Configuration example file for samba using computer pswdf004 as
; password server
[global]
; SECURITY OPTION guest account: the guest has the file access
; rights of this UNIX-user
guest account = nobody
debug level = 0
security = server
password server = pswdf004
getwd cache = yes
wide links = no
password level = 8
case sig names = yes
preserve case = yes
case sensitive = yes
read prediction = yes
[transdir]
comment = us0011:/usr/sap/trans
path = /usr/sap/trans
; SECURITY OPTION public: all users can access the share as a guest
; no password is checked
public = yes
; SECURITY OPTION writable: files + directories can
; be changed if writable = yes
writable = yes
; SECURITY OPTION browsable: Share is visible if browsable = yes
browsable = yes
create mask = 0664
map hidden = no
map system = no
preserve case = yes
wide links = yes
; SECURITY OPTION allow hosts: only specified hosts can access the
; share
allow hosts = us0011
ABAPNTFMODE = b
transdir = /usr/sap/trans/
wnt|transdir = \\trans01\trans4\
syslog = SLOG$(syear)$(yweek).$(system)
alllog = ALOG$(syear)$(yweek).$(system)
r3transstat = $(transdir)log/STATLOG.$(system).#.$(yweek)
BIN/dbhost = hs0055
BIN/dbname = BIN
BIN/r3transpath = /bas/$(system)/exe/dbg/$(cpu)/R3trans
wnt|BIN/r3transpath = \\NTPC\sapmnt\bin\sys\exe\run\R3trans.exe
sapevtpath = /bas/$(system)/exe/dbg/$(cpu)/sapevt
wnt|BIN/sapevtpath = \\NTPC\sapmnt\bin\sys\exe\run\sapevt.exe
BIN/system_pf = /bas/$(system)/profile/DEFAULT.PFL
wnt|BIN/system_pf = \\NTPC\sapmnt\bin\sys\profile\BIN_D53_NTPC
BIN/impdp_by_event = yes
Although the Customizing settings in IS-H are complete, a cost center is not transferred to financial accounting during billing.
Cause and prerequisitesThe cost center is determined correctly but is also removed again in the further development of patient accounting because the account to be posted is a balance sheet account.
SolutionRNAB0000, RNABD000, NOEK
Planning board: If an operation is added after a number of already planned operations, the sequence of these opertaions is reversed.
Cause and prerequisitesA planning strategy is active with planning direction back and 'Add operation'.
SolutionCapacity scheduling
Can you limit or log the download functionality (authorization check)?
Security requirement
Basically you cannot prevent a user from saving data from the display to a file. On the PC, the user has the option to execute this as a screen capture (cut-and-paste), without informing the R/3 System.
Therefore, there is currently no authorization check up to Release 3.0B. There is also no logging.
The first technical preconditions for the executing of an authorization check for a download from the R/3 System were developed on customer request in Release 3.0C. This prevents a fast download of large datasets. However, an authorization check in the applications is not yet contained in the 3.0C Standard System.
Basically, you can call the download in two different ways:
Here, the authorization check is always contained in the application, as the corresponding authorization objects are known there. From 3.0C, you can also (as an alternative) use function module SET_DOWNLOAD_AUTHORITY to register a form routine, which executes some kind of check to see if the download may be carried out and, if necessary, logs the download.
You can use this to protect the list download (b), but a modification in function module 'DOWNLOAD_LIST' (2.x) or 'LIST_DOWNLOAD' (3.x) is to be preferred. A customer-specific check and logging can be implemented in the modification (from Release 3.0C), or the check routine, which could also execute a logging, can be registered. You can also completely prevent the download this way.
...
CALL FUNCTION 'SET_DOWNLOAD_AUTHORITY'
EXPORTING
FORM =
PROG =
FORM
...
ENDFORM.
In the function modules, check whether FORM and PROG are set. If the answer is yes, execute a dynamic perform on the entered routine which is provided by the application and returns 0 or 1. In the case of 'NE 0', the error message PC013 is displayed and function module is exited with EXIT. A check and additional message handling is contained in the form routine.
The effect of the check is limited to the transaction that executes the call.
In addition to the behavior maintained for reasons of compatibility, a CUSTOMER FUNCTION 'EXIT_SAPLGRAP_001' (enhancement 'SGRPDL00') is implemented, that is called for every download - both business application-defined as well as with which general list download.
The function knows the following parameter:
IS_LIST_DL : is set if you are dealing with a list download
NO_AUTH_CHECK: is set if the application does not require a check.
You can use the following fields to find which list should be exported:
SY-TCODE transaction
SY-CPROG report
SY-SLSET variant
SY-TITLE title of the list
Make sure that a list can be protected elsewhere from the download (for example as a spool request, in a report tree or as an office document). If you call the download function afterwards, the fields SY-TCODE, SY-CPROG and SY-SLSET do not contain the values, which were valid during creation of the list.
If a download is rejected, the exception 'NO_AUTHORITY', which is intercepted in function module 'WS_DOWNLOAD' and results in the error message PC013, must be triggered.
This means that you can ensure that certain user groups can be excluded from the option of a download by activating and programming the customer function. You can either execute this by explicit programming or by a separate authorization object. In addition you can implement a TRACE mechanism.
Install the check against the authorization object S_GUI (or Z_GUI) as follows:
authority-check object 'S_GUI'
id 'ACTVT' field '61'.
if sy-subrc ne 0.
raise no_authority.
endif.
Creation of the authorization object S_GUI (or Z_GUI respectively):
Transaction SU21 -> Create
Object S_GUI
Object Class BC_A Basis: Administration
Text Authorization for GUI Activities
Fields ACTVT
Enter the authorized activity 61 for this object afterwards:
Transaction SM31 for table TACTZ
Generate entry S_GUI
Alternative 1) Create authorization object Z_GUI using field ACTVT. This is no modification.After the upgrade to 4.x you should set the profiles to default (S_GUI instead of Z_GUI). The user exit can be deactivitated after the upgrade.
Alternative 2) Create authorization object S_GUI using field ACTVT. This is a modification and results in a message during the upgrade to 4.x. However, you do not need to adjust the authorization profiles after an upgrade to 4.x. The user exit can be deactivated after the upgrade.
If the currency for a sales order is removed, error M2802 occurs after saving: Error determining local currency
Cause and prerequisitesOnly a program error if the user parameter MCL = 'X'.
SolutionVA01, VA02, credit limit
Standard tasks (work flow examples) cannot be used:
- No work items are created.
- The integrated inbox is empty.
- System transaction codes in IDoc processing cannot be maintained.
- The F4 help for tasks does not work.
Language-dependent entries for the standard tasks are missing in table HRS1000. As a result, the standard tasks cannot be found.
SolutionWork item, transaction code, EDI, Inbox, TEDE5
When posting a cross-company code goods movement with the movement types 301 to 304, 309, 310, 351, 352, 641 or 642, message M7001 is displayed:
E: Please check table T030B: entry BUV does not exist
Since Release 3.0, the posting key for company code clearing is no longer allocated via table T030B but via table T001U.
SolutionCompany code clearing
When maintaining a material master record, you specify forecast model 0, resulting in the forecast values being deleted. If afterwards you want to make a forecast for the material, you can no longer do so if the date of the last forecast is in the current period.
Cause and prerequisitesAfter specifying forecast model 0, the date of the last forecast is not reset by the system.
SolutionTransaction: MM02; program: SAPMM03M; fields: MPOP-PRMOD, MPOP-PRDAT
If you use the function 'Reverse with reference to the reservation...', items with the 'Set final issue' indicator are proposed unselected . Furthermore, the final issue indicator must be cancelled explicitly.
If you use the function 'Reverse material document', the final issue indicator is always proposed as initial (blank).
This processing has now been adjusted.
The system now works as follows:
1. Reversal with reference to reservation...
The items with a set Final issue indicator are now proposed selected (new!). The final issue indicator is set on the selection screen. When transferring the item, a check is made on whether the quantity issued is smaller than the requirement quantity. If this is the case, the final issue indicator is reset (new!).
This is only valid if the field 'Marked as completely issued' is not selected in the extended selection for the reservation.
2. Reverse material document
The items are proposed with a set final issue indicator (new!). When transferring the item, a check is made on whether the quantity issued is smaller than the requirement quantity. If this is the case, the final issue indicator is reset (new!).
Under certain circumstances, if the user invoked the function "Back" from within source list maintenance, he or she was liable to be thrown out of the transaction completely instead of being returned to the outline agreement.
Cause and prerequisitesThe error occurred only if you branched directly from the item detail
screen into source list maintenance.
Contrakt, scheduling agreement.
A PO item contains an item text that was copied from a requisition that does not belong to the PO item.
Cause and prerequisitesThe PO was created via the function "Assign and process purchase requisitions" or "Create purchase order via requisition". Prior to the faulty purchase order, the creation of another PO was terminated by the user without saving.
Texts, item texts.