Common Errors at the Time of Executing j1inchln

7/29/2019 Common Errors at the Time of Executing j1inchln

1/4

Common ERRORS AT THE TIME OF EXECUTING J1INCHLN:

Message class 8I

Message Number 702

Message Text No unpaid tax lines exist for the given selection criteria.

Possible Reasons:

9 Incorrect Selection Parameters

9 Non updation of section code for tax lines

9 Incorrect recipient type

9 Mismatch in line item numbers

9 Documents Parked and Posted.

9 Miro Reversal Documents

Code Causing the error:

Report J_1I_CHALLAN_UPDATE

Routines:

Form GET_DOCS

Form GET_WITHITEM

Form PROCESS_MIRO_REVERSALS

Solution:

Incorrect Selection Parameters:

Check the parameters like posting date, section code, vendor account & tax code

Non updation of section code for tax lines

For a document to be picked up during j1inchln, section code must be present for the EWT

lines.

The section code gets copied from the vendor line item.

The following settings are mandatory:

a) Activation of component IND in table TRWCA

b) Presence of Function Module J_1IEWT_UPDATE_SECCO in Table TRWPR. -Refer SAP

Note No.

1273262 in this regard.

c) For Cross Company Code Documents, ensure that SAP Note No. 1118159 is present in

your system.

d) If you have any substitution for Section Code, Please check the same. There is no SAP

predefined

substitution for section code.

Incorrect recipient type

Please ensure that the document has field QSREC filled in table with_item.

The input parameter for recipient type field in j1inchln selection screen should have the

same value as

with_item qsrec.

Mismatch in line item numbers

In a case whether there is a mismatch between line item numbers in table bseg (bseg-

buzei) and line


2/4

item numbers in table with_item ( with_item-j_1ibuzei) for tax lines ( bseg-ktosl = WIT) such

documents

will not get picked up during challan process.

Ensure that the following notes are present in your system.

SAP Note No. 1412211

SAP Note No. 1097101.SAP Note No. 1145001.

For documents which has already been posted before applying the above , please run the

report given in

the note 885213.

Documents Parked and Posted.

In case of documents which are parked and posted, the field wt_stat in table with_item

should be

checked. The said field should be BLANK. In case if contains the value V then such

documents will not

get picked up during challan processing.SAP Note No. 519861 has the solution for this issue. This note has solution in 2 parts.

The code corrections present in note 519861 will take care of future postings.

The report Z_RFWT0540 which is present in note 519861 needs to be executed to correct

the

Database for documents posted before applying the note 519861.

Miro Reversal Documents

If the original MIRO document and the reversed MIRO document are processed in the same

challan,

then both the documents will NOT get picked up for processing.

Ensure that SAP Note No. 1244222 is present in your system so that the system will NOTallow you

To reverse the invoice document once the tax line items are cleared.

To know the system behavior in this regard, put a break point in

Routine process_miro_reversals > program - J_1I_CHALLAN_UPDATE.

In addition to the error mentioned above, the points given in the SOLUTION part above,

needs to be

checked for a case where a document is not getting picked up for challan processing,

*************************************************************************************

Message class 8I

Message Number 703Message Text Withholding section &1 not fully maintained or does not exist

Possible Reasons:

9 Nonmaintenance of tax key in tax code customization.



Routine : Form CHECK_SECTION


3/4

Solution:

Ensure that you have maintained the official tax key at the time of defining withholding tax

code.

*************************************************************************************

Message class 8I

Message Number 704Message Text Number group not maintained for CO code & section & and business place

&

Possible Reasons:

9 Incorrect Customization

9 Non Maintenance of Table entry



Routine : Form VALIDATE_GROUP_RANGE

Solution:

Ensure that you have maintained the required values in the following customization node.SPRO -- > Financial Accounting -- > Financial Accounting Global Settings -- > Withholding

Tax -- >

Extended Withholding Tax -- > Postings -- > India -- > Remittance Challans -- > Maintain

Number Groups.

This will update the table J_1IEWTNUMGR_1.

**************************************************************************

Message class 8I

Message Number 705

Message Text Number key not found

Possible Reasons:9 Incorrect Customization




Routine : Form VALIDATE_GROUP_RANGE

Solution:

Ensure that you have maintained the required values in the following customization node.

SPRO -- > Financial Accounting -- > Financial Accounting Global Settings -- > Withholding

Tax -- >

Extended Withholding Tax -- > Postings -- > India -- > Remittance Challans -- > AssignNumber Ranges to

Number Groups

This will update the table J_1IEWTNUM.

**************************************************************************

Message class 8I

Message Number 706


4/4

Message Text Number range for internal challan numbers not maintained

Possible Reasons:

9 Incorrect Customization



Report J_1I_CHALLAN_UPDATERoutine : Form VALIDATE_GROUP_RANGE

Solution:

Ensure that you have maintained the required values in the following customization node.

SPRO -- > Financial Accounting -- > Financial Accounting Global Settings -- > Withholding

Tax --

>Extended Withholding Tax -- > Postings -- > India -- > Remittance Challans -- > Maintain

Number Ranges

*************************************************************************************

Message class 8I

Message Number 707Message Text Business Place for document &1 could not be determined

Possible Reasons:

9 Missing link between Business Place and Section Code.



Routine : Form CHECK_BUPLA

Solution:

Though we have migrated from Business Place to Section Code, there are a couple of

places where the

EWT program reads/checks for Business Place Also. To overcome this, SAP recommendsyou to create a

Dummy Business Place with the same name as that of Section Code.

************************************************************************************

The above listed errors are the most frequently faced errors during execution of j1inchln.

For any other