RECONCILIATION ERROR IN SUBCONTRACTING

[former_member398195]

Hi Folks,

We have recently carried up gradation from 4.7 version to ECC6.0 EHP5.

We are facing the following problem in subcontracting scenario.

1. End user raised a subcontracting PO with a material BOM number 125742 (125741+133010. PO# 4502000430 and Vendor# 10368.
2. Carried MB1B for 125741 - referring the PO.
3. Created Subcontracting challan through J1IF01 referring the Material Documenet generated above. Challan#  0001300113.
4. MIGO - entered the above created subcontracting challan - 1300113(for material 125741 and same vendor # 10368)
   and other challan 1300050 (Which is already created for the same Vendor# 10368).
5. While doing Subcontracting Reconciliation - J1IFQ, the end user add another challan 1300045 (Which was
   created for material 133010 and same vendor# 10368) the following error comes.

"The document does not exist"

Message no. 8I072"

The above error was not occurring in the 4.7 version and appearing only after upgrade. Moreover in the 4.7 version, even if the user did not select the chalans in MIGO, they used to enter in J1IFQ by adding them as a new line item

I checked all the prerequisite configurations in SPRO and J1ID is also maintained perfectly.

Please find the screen shot attached.

Please suggest a solution.

Regards,

Vikranth

[former_member187965]

Hi,

Apart from the Note 1755696, i can see the '101' movement type in your second screenshot. '101' movement type should not be assigned to any of the subcontracting movement type groups. It creates reconciliation quantity inconsistency issue. Go through below SAP Note,

Note 1559145 - Frequently asked questions for Procurement in India: CIN

Question no 6 under sub-contracting head.

[former_member398195]

Hi Sailesh and Ashok,

Thank you very much for your suggestions. We have taken up with SAP and the issue is a Process Change. Please find the communication we recieved from SAP.

Whenever you do goods receipt for subcontract process please refer the challan in material document itself and not in J1IFQ. This is because if you refer challans while doing MIGO system always captures GR and challn information in standard table J_1IGRXSUB. This is like a proof that for this particular material document you have referred these many challans. If you do it in J1IFQ system cannot link it with the GR and this process is wrong. Which will also affect in auditing. Before this it use to work because there was no check for excise or series group in J1IFQ and user was allowed to refer any number of challans and which was a bug and not only that we provided a check for excise group and series group because before system never used to consider excise and series group so if you have maintained same number range for multiple series group for same excise group then system use to post duplicate challans entries which was big issue so we fixed it with the note 1755696.

We have informed the user about the Process change and closed it.

Thanks once again,

Vikranth.

[former_member192897]

Thanks for sharing the same.

[former_member192897]

Ensure you have assigned the EBELN field as optional entry in OMJJ for 541 movement type.

Also check the Movement type groups for subcontracting. If everything is perfect, you may take up this issue with sap.

[former_member398195]

Hi Ashok,

Thank you very much for you quick reply.

I've carried over the settings you've mentioned. The movement type groups are properly maintained, still the problem occured. We have takent the issue with SAP and they have asked us to implement a note - 0001755696 : Subcontracting issues when same number range maintained-57FC.

Once the notes have been implemented, they've suggested to test with new cycle. We are in process of implementing the notes.

Will keep you posted on the results.

Best Regards,

Vikranth.

0001755696Subcontracting issues
when same number range maintained-57FC

0001755696   Subcontracting issues
when same number range maintained-57FC