cancel
Showing results for 
Search instead for 
Did you mean: 

Good Issue to Order with Order and Cost Center

Former Member
0 Kudos

Hi All,

Client used transaction code MB1A for Good Movements to Order and in account assignment has given Order and cost center. They wanted to reverse it as cost center was not supposed to be entered.

They reversed the material document through MB1A and which did not pick up the cost center while reversing. Now the posting remained on the cost center.

I cancelled the reversed document and tried to reverse the original Material document through MIGO transaction which picks up cost center, but it is giving error material document already reversed.

Can any please let me know how the amount charged to cost center be cancelled or reversed, is there any alternative to this.

Thanks

Satish

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

I found the resolution, if we reverse the material document through MB1A all cost objects will not be picked, we have to reverse it through MIGO.

Former Member
0 Kudos

Hi Sudhakar,

Thanks for the reply, when I try KB61 and give accounting document it is giving error "Document already reversed".

Thanks

Satish

Former Member
0 Kudos

Hi,

Check then the reversal document and follow on Controlling document which is created for the reversed document. Check which cost object/s it posted. Here too you should be able to find the cost center in addition to the order. If cost center not found, then use this financial document in the earlier mentioned tcode to put the cost center as a second cost object.

Regards

Sudhakar Reddy

Former Member
0 Kudos

Hi,

The posting went as statistical to Cost Center now we need to cancel the posting. But we are unable to do it as the material document is already reversed trought MB1A which did not pick cost center during reversal.

So Is there any other way to adjust posting made to cost center.

Thanks

Satish

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

This message was moderated.