SAP Note 11415 - A034 - Update termination ANLZ.

-
Symptom

Program : SAPMA02S
Error ID: aa034
Creating a sub-number leads to update termination AA034 when the system tries to update Table ANLZ.

Cause and prerequisites

The customer has migrated from R2 to R3; date specifications in fields ANLZ-BDATU and ANLZ-ADATU are incorrect.
for example:

Incorrect data rec.: BDATU ADATU

00000000 19000101 <-- BDATU is incorrect
99991231 19000001 <-- Month '00'

Solution
1. Correct and repeat the conversion.
or
2.a. ADATU 19000001 must be changed to 19000101.
b. The record with BDATU '00000000' must be deleted.

See coding for utility report.

Additional key words

AS11 AS94 AS02 AS92 Time-dependent data

Comments

Post a Comment

Popular posts from this blog

SAP Note 11489 - What to do when there are print problems in QM.

-
Symptom Either an incorrect inspection instruction or sample drawing instruc- tion is printed, or none at all. Errors in the print control settings in the Customizing application cannot be ruled out. If no inspection instruction or sample drawing instruction is printed, two different situations can exist: a) In the inspection lot transactions, no sample drawing instruction or inspection instruction can be printed after the sample has been calculated. b) In the inspection lot transactions, the documents can be printed, but not immediately from the stock postings. Error messages: QA162, CO412 (among others) Transaction codes: QA01, QA02, QA03, MB01 (among others) Cause and prerequisites There can be several reasons for this situation: 1. The print form does not exist, the print form does not exist in the required language nor does it exist in the client concerned, or the print form is not activated (system installation). 2. The table settings are incorrect (Customizing...
Read more

SAP Note 11507 - Fields returned wrong in elec. bank statement.

-
Symptom The bank sends an incorrect business transaction code. This code does not exist in the system. It is not possible to process the corresonding line in the electronic bank statement. Cause and prerequisites Bank error Solution Either a) or b) a) Temporarily define the incorrect business transaction code in the system, process the statement, then delete the transaction code afterwards. b) Change the business transaction code in the database: 1.) Transaction : SE16 Table : FEBKO Application : 0001 Sender bank : 'Bank code' (15-digit) 'Account number' Statemnt ID : 'Year'(4-digit) 'Statement number'(5-digit) ShortKey : select "Output" --> Note the displayed ShortKey! 2.) Transaction : SE16 Table : FEBEP ShortKey : noted value BusTransCode : select "Output" --> Note the incorrect BusTr...
Read more

SAP Note 11438 - Error GI207 when writing line item index

-
Symptom The function module G_GLDB_POSTING cancels the process with the error message GI207 'Error when writing line item index for ' or the error message GI201 'An error occurred when writing the record for table Cause and prerequisites This error message usually occurs if the customer has not reset test data before the production startup. Then, there still is data in the user-specific tables (for example GLS1, GLIDXB). If the document number ranges are reset afterwards in the sending applications, documents with numbers which have already been stored in the GLX tables are now posted directly in GLX. A 'duplicate record' occurs. Solution Often the customer has unintentionally activated the GLX. Using the diagnostic tool (TA GCD1), they should check which ledgers are posted directly under a certain transaction. If direct posting of these ledgers is not required, the GLX can either be switched off completely as a component (TO GCVO, however, caution is advisable ...
Read more