cancel
Showing results for 
Search instead for 
Did you mean: 

WM - How to not split Transfer Requirement - Goods issue to cost center

Former Member
0 Kudos

Dear All,

I have this case:

- MIGO \ mvt 201: post Goods issue to cost center. The posted material document has many line items, say some belong to cost center A, some other belong to cost center B.

--> System auto creates one TR per each cost center. In my case, it creates 2 TRs. The 1st TR includes all line items belong to cost center A. The 2nd TR includes all line items belong to cost center B.

Question:

- Can the system just create one TR per material document, regardless that this document has different cost centers? How to do it in the configuration?

Thanks,

Trang

Accepted Solutions (0)

Answers (1)

Answers (1)

mihailo_sundic
Active Contributor
0 Kudos

In table LTBK (TR header), there is a field BENUM which gets populated from Cost center, and since it is on transfer requirement header level, there is no possible way to create only 1 TR per this type of material document (more than 1 cost center).
You will get as many TRs as you have cost centers.

I'm not sure what you want to achieve in the process, but maybe grouping transfer requirements could help you in that.
If not, I'm affraid you have no solutions to create a single TR for many CC's.

Regards,
Mihailo