Tag Archives: SAP

ABAP: Overbooking BAPI_ACC_DOCUMENT_POST error reported FI/CO interface: inconsistent FI/CO voucher header data to be updated

Problem: When using BAPI_ACC_DOCUMENT_POST, the reason for the error is “FI/CO interface: inconsistent FI/CO voucher header data to be updated” when automatically posting the account.

Reasons:

1. If the company in the header data and the line item company are consistent, check the line item and do not assign company bukrs to the line item.

“it_item-comp_code = wa_account-bukrs.

2, check whether the amount is 0, if the line item amount is 0, it will report this error.

3, whether the positive and negative of the amount of debit and credit are consistent. Example: The bookkeeping code is 40, debit, should be a positive value; the bookkeeping code is 50, credit, is a negative value.

it_curr-amt_doccur = wa_account-wrbtr.

Solution:

Follow the above reasons, troubleshoot the program, and modify it.

[Solved] SAP MDG Create View Error: unexpected error while activating search view ZMDG_XXX

Problem Description:
unexpected error while activating search view zmdg_XXX

SAP system version: S/4 Hana 1909 SP2

Reproduction steps:
Tcode: mdgimg



when you click generate, the following errors appear

Solution:

    1. 1. using the system user to authorize SAPHANADB


    1. 2. if there is an error after generate; You need to manually create a temporary attribute view, and then click generate to succeed

Refer to configuring SAP Hana based search for MDG

[Solved] Error occurred during connect to primary: exception 3000301: Connection could not be established

Problem:
the Hana system replication standby machine cannot take over the host, and the Hana host can be used normally.

The following errors are reported in the trace file:
SR_dataaccess DisasterRecoverySecondaryImpl.cpp(00882) : Error occurred during connect to primary: exception 3000301: Connection could not be established

Solution:
this problem is generally caused by a network problem between the active and standby computers
for the above error reports, you can first check whether the 3xx00-3xx99 port segment of the standby machine to the host is occupied or blocked.

SAP Migo 101 receives the work order and reports an error – check table tfbefu_ CR entry 10 does not exist – Countermeasures

SAP Migo 101 receives the work order and reports an error – check table tfbefu_ CR entry 10 does not exist – Countermeasures

Execute transaction code Migo, move type 101, perform receipt posting for a work order, and the system reports an error: check table tfbefu_ Cr: entry 10 does not exist

F1help documentation:

Check table TFBEFU_ CR: entry 10 does not exist

Message no. M7001

Diagnosis

In table TFBEFU_ CR the entry 10 is missing.

Procedure

Make sure your entries are correct.

If table has not been maintained correctly, please inform your systems administrator.

This error report is the first time I have encountered it, so I am very curious and hope to find out the reason. It is found that the background configuration of a co module is missing, and the transaction code is opk9. The configuration path is as follows:

You need to add an entry to this configuration for the factory code corresponding to the work order. After configuration, you can post the work order receipt normally.

-Finish-

Written on October 12, 2021

SAP SQL error “SQL code: -10692“ occurred while accessing table “ZTXXXX“.

report errors

resolvent

Note：SQL code: -10692 occurred while accessing table < TABLE_ NAME> Use the report cucastat to reset the statement cache for the instance.

The instance list can be viewed through transaction sm51. Execute the program cucastat in transaction se38; Alternatively, call transaction al12 and select monitor – & gt; cursor cache from the menu.

Select this server. Then select the reset button.

[ABAP] sproxy opens ESR and reports an error has occurred during communication ESR

Recently, an error has occurred during communication ESR is reported by clicking sproxy → source → ESR when publishing the Po agent class. The following is the error message. Figure 1 shows the Chinese environment and Figure 2 shows the English environment:

Query SAP notes and try to solve the problem. It is found that the description of notes: 2957501 – an error has occurred during communication with ESR is consistent with the problem.

Sm59: SAP was checked step by step according to the method provided in notes_ PROXY_ ESR connection;

SPROX_ CHECK_ IFR_ CONNECTION -> Enterprise Services Builder data not understood
SPROX_ CHECK_ IFR_ ADDRESS -> Cannot determine Repository Version, An error has occurred during communication with ESR
SPROX_ CHECK_ IFR_ RESPONSE -> Requested Repository is down., An error has occurred during communication with ESR
SPROX_ CHECK_ HTTP_ COMMUNICATION -> HTTP communication functioning

The error report provided is consistent with the document, and the method provided in notes: 2370153 is used to solve the problem.

Solution: view sm59: SAP in Po_ PROXY_ The ESR service found that the Po account was locked, and the unlocked account sproxy returned to normal.

Extension: create/lock/unlock/modify password, etc. change the address of Po user:

  http://< server>:& lt; port>/ startPage   →   User Management

ABAP edit screen click layout to dump

Yesterday, when I was developing an OO ALV, I found the customer’s system. After creating the screen, I click layout to edit the screen.

SAP dumps directly, as shown in the figure

 
After consulting the data, the solutions are as follows:  
SM59–> TCP/IP CONNECTIONS–> EU_ SCRP_ WN32

After entering, click Edit — “logo & amp; security–> Add call function

 
  The code is as follows

RS_SCRP_GF_PROCESS_640	RFC_GET_FUNCTION_INTERFACE
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_PROCESS_640RFC_GET
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RBUILDINFO
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RDDICFIELDS
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RELEMTABLE
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RICONS
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RKEYS
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RKEYTEXTS
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RMESSAGES
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RPROPTABLE
RS_SCRP_GF_PROCESS_640	RS_SCRP_GF_RSTATUS_40
RS_SCRP_GF_PROCESS_640 RS_SCRP_GF_RTEXTS

  Just save it

When SAP receives the goods, the system prompts that it can only be recorded in the period 2009 / 09 and 2009 / 08 of company code 1101

Error: when receiving goods according to PO, the system prompts can only be accounted for in the period 2009/09 and 2009/08 of Company code 1101. The current date is 2009-10-8.
Answer: this is an old problem, it is the problem of MM opening account,< a target=”_blank” class=”link_tag” href=”http://blog.vsharing.com/Tag/%3Ca%20href=” http:=”” www.vsharing.com=”” sap”=”” style=”line-height: 21px; color: rgb(85, 66, 15); Font: Verdana, Arial, Helvetica, Sans-serif; font: Verdana, Arial, Helvetica; sans-serif; text-decoration: underline; “> SAP”> MM in SAP can only open accounts for 2 months, which should be opened in sequence.
You can use the transaction code: MMRV to check the current accounting period, and then use MMPV to adjust month by month, if the prompt is not the current calendar year, enter can be past.

How to Fix Error in module RSQL of the database interface

keywords
Error in module RSQL of the database interface error key: RFC_ERROR_SYSTEM_FAILUREdbtran ERROR (set_input_da_spec): statement too big[dbtran.c#4854] marker count = 18655 > max. marker count = 16000 [dbtran.c#4854] sap note:13607

Problem description
[Problem] After EP was tested by the development machine, the EP was executed after it was released to the production machine, and this Problem occurred:

Error message:
Error in module RSQL of the database interface, Error key: RFC_ERROR_SYSTEM_FAILURE
Problem analysis
You can first try the following operations:
1, check, test the RFC, and transfer the related requests to the production environment; 2. Reimport RFC in NWDS and republish the project (note that the operation of production environment release is different from that of development machine); 3. Restart EP;
if the problem is still unresolved, read on.
Check the ABAP Runtime Error log

through the transport code ST22. Double-click the corresponding Error log to enter the Runtime Error Long Text interface, where there are detailed Error reports.
Some of the error messages I picked:
Kategorie (category) : ABAP Programming Error
Laufzeitfehler (runtime Error) : DBIF_RSQL_INVALID_RSQL
Ausnahme (exception) : CX_SY_OPEN_SQL_DB
ABAP Programm: SAPLZEWM_RFC2
【Kurztext】 (German, meaning category)
Error in module RSQL of the database interface

Error in the ABAP Application Program
the current ABAP Program “SAPLZEWM_RFC2” had to be terminated because it has come across a statement that unfortunately cannot be executed.

An exception that is explained in detail below once again occurred.
The Exception, which is assigned to class ‘CX_SY_OPEN_SQL_DB’, was not caught in procedure “ZTM_RFC_YSQSD_GETORDER_V2” (FUNCTION) “, nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated.
The reason for the exception is:
The SQL statement generated from the SAP Open SQL statement violates a restriction imposed by the underlying database system of the ABAP system.
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
You can generally find details in the system log (SM21) and in the developer trace of the relevant work process (ST11).
Cause analysis,
1. In the ABAP Select statement, when range Table is used in the WHERE clause, the type of range Table exceeds the maximum limit of the database (the maximum value is determined by DB).
2. The source code location is already listed above the error message:

The solution
1. Search SAP Note: 13607. Extract the contents of Note


2. So I modified my code:

DATA r_so LIKE RANGE OF vbak-vbeln WITH HEADER LINE. 
DATA lines LIKE LINE OF r_so.
DESCRIBE TABLE r_so LINES lines.
IF lines EQ 0.
    SELECT
      vbak~vbeln AS vbeln
      adrc~name1 AS name1 
      vbpa~kunnr AS kunnr
      vbpa~parvw AS parvw
      adrc~city1 AS city1
      FROM vbpa
      INNER JOIN vbak ON vbak~vbeln EQ vbpa~vbeln
      INNER JOIN adrc ON vbpa~adrnr EQ adrc~addrnumber
      INTO CORRESPONDING FIELDS OF TABLE gt_display_vbpa_ag
      WHERE adrc~name1 IN r_shippername 
        AND vbpa~kunnr IN r_shipper     
        AND vbpa~parvw EQ 'AG'.
...
ELSE.
    TRY.
      SELECT
         vbak~vbeln AS vbeln
         adrc~name1 AS name1
         vbpa~kunnr AS kunnr
         vbpa~parvw AS parvw
         adrc~city1 AS city1
         FROM vbpa
         INNER JOIN vbak ON vbak~vbeln EQ vbpa~vbeln
         INNER JOIN adrc ON vbpa~adrnr EQ adrc~addrnumber
         INTO CORRESPONDING FIELDS OF TABLE gt_display_vbpa_ag
         FOR ALL ENTRIES IN r_so 
         WHERE vbak~vbeln EQ r_so-low
           AND adrc~name1 IN r_shippername 
           AND vbpa~kunnr IN r_shipper     
           AND vbpa~parvw EQ 'AG'.

   CATCH cx_sy_open_sql_db.
   ENDTRY.
...
ENDIF.

3. After modifying the RFC, it is necessary to re-import Model
in WD4J
4. Re-transmit the Request to production and re-publish it to EP. Problem solved
Summarize the ideas for solving THE SAP problem
1, do not do hand party, do not ask a mistake, be sure to read the error message, analysis of the possible part of the error, is RFC error or WD4J error; 2. Error messages can be viewed through Tcode ST22 or ST11 or sm21; 3. About search engines:
SAP search: http://search.sap.com/ (this SAP note the number 13607 is found in the above) SAP note: https://websmp206.sap-ag.de/NOTES (search keywords are provided in the error log)

SAP custom Google search engine, https://cse.google.com/cse/home?cx=013447253335410278659:k8ob9ipscwg

bug-JAVA call SAP function Connect to SAP gateway failed

Problem: com. SAP. Conn. Jco. JCoException: (102) RFC_ERROR_COMMUNICATION: Connect to SAP gateway failed
Recently, my colleague made a mistake in the following figure when he called SAP system function with Java. Later, my colleague asked for my assistance. I used its code to run the machine and report the same error. Finally, the problem is solved by searching and trying in many ways.
Summarize the processing methods:
1. First, check whether the code has been written and whether the JAR package and DLL file have been added. Ping/Telnet can try to check whether the network is normal.
2, adjust the JDK version, you can use 1.7/1.8 try it;
3, modify the computer user name, not including Chinese, (after the modification, please shut down, and then start, sometimes restart is really unreliable).

Finally, I successfully solved the problem by modifying the computer name, and ran on JDK1.7 and 1.8 without any problem.

TSV_TNEW_PAGE_ALLOC_FAILED

Premise:
foreground runs the program and processes 10 million pieces of data.

status:
will extract 10 million pieces of data from the database to the inner table, if a one-time extraction will occur memory TSV_TNEW_PAGE_ALLOC_FAILED dump.
that is: select XXXX
into table XXX
where…

if the package size is adopted, 1 million pieces of data are extracted once and processed.
select XXXX
into table XXX
package size 1000000
where…

perform XXXX “processed the 1 million pieces of data.

Endselect.

service really needs under the premise, the solution can only ask basis to change the kernel parameters, either to increase the buffer, or to extend the front running time.