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 here since profit center accounting
is then also disconnected), or
he can interrupt or block the allocation of his unintentionally
posted ledgers to his company codes using transaction GCL2:
Choose ledger, function 'Assign.comp.cd/comp.' (F6), choose
assigned company code, set block indicator to '0', save default
setting.
Furthermore, it is also possible to delete transaction data from
ledgers unintentionally posted using the transaction GCDE:
Choose the option 'Selective deletion of an individual ledger' ,
cancel the indicator 'Test run', F8='Execute', then enter the
ledger to be deleted and press the function key 'Continue'.

Key word: GI207, GI201

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 11477 - Check deposit: fields are not printed.

-
Symptom You want to print out more fields than those specified in the standard form, F_M40S_CHEQUE, on the check deposit list (for example, FEBSCK-KUNNR = Customer number, ...). Cause and prerequisites Outputting other fields on the check deposit form is not supported. Output is not possible for most fields because the relationship between form and check is not 1:1, but instead N:1. For example, one check could be used to pay the invoices of several customers. In addition to the fields available in the standard form, the fields in table FEBEP can be output for each check. However, only a few of the fields in FEBEP are filled. Solution If organizational measures can guarantee a 1:1 relationship, you can enter the required field in the "Issuer" field manually and print it on the form. Of course, you can do this only if you are not using the "Issuer" field. Additional key words SAPMF40S, FF68
Read more