cancel
Showing results for 
Search instead for 
Did you mean: 

Issue of short closed sub-con orders

Former Member
0 Kudos

Hello,

I have an issue on the subject matter.

Scenario is:

Purchase SA - xxx SA type : Sub con

Purchase Part: A

BOM: A --> B

(To procure A from the sub con I am sending the material B to him.)

I have put initial schedule of 100 nos. for agreement xx using transaction ME38.

I sent material B qty. 100 nos. to sub con.

I received (GR) 50 nos. of material A

Later through a "Z" development I have changed the schedule line qty. from 100 to 50. ( Delivered Qty = Scheduled Qty.)

But in the background the requirment of B is not cleared.

And thus after each MRP run the system shows subsequent requirement of A in stock /requirment list of B and qty is 100 nos.

After this procedure, I have agregated the schedule lines. But the MD04 screen shows same old sch. line no. as sub.req.

I disagregated the lines but it is giving new number.

Since I am transferring this requirement of B in to Product Costing, the costing is calculating excess activity unnecessarily.

Can anyone please help, how do I remove this requirement from the system?

Regards,

Rahul Puranik.

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member201758
Contributor
0 Kudos

Hi Rahul,

breaking SAP standard processes cause such inconsistent data. My sencere advice is to avoid these.

You can run report RM06C020 to correct this inconsistency.

Please read very carefully the information provided in SAP note 115899 and remember that this report is intended only to be used for correction once; it should never be planned periodically as a background job.

Hencefore you should check first that all notes mentioned in SAP note 128061 have been applied in order to prevent the creation of new inconsistencies.

Sanjeev

Former Member
0 Kudos

Dear Sanjeev,

Thanks for the reply. I am checking the notes as well as the report you have suggested.

I will be back with correct feedback on the issue soon.

Thanks once again.

Regards,

Rahul Puranik.