Standard report for GR in specific storage location

[Former Member]

Hi experts,

Is there any standard report that displays amount produced monthly (GR) by storage location?

I'm trying to extract this information using tcode MB51 with moviment type 101, 102, 131 and 132, (We have discrete and repetitive manufacturing) but there are many data and occurs runtime error.

I also tried MCP5, but it works with material and plant level.

Thanks in advance.

Marcos

[rupesh_brahmankar3 · Accepted solution]

Hi Marcos,

You can use MB51, MB59 with some selection criteria like posting date movement type  and Trans./Event Type  like WF and WS etc.

Also you can try the report like MCP8.

Apart from that you can develop your own report by using standard report RM07DOCS.

Regards,

R.Brahmankar

[Former Member · Accepted solution]

Hi Rupesh,

Thanks for help!

I tried MCP8 (items produced with Repetitive Manufacturing) and MCRO (items produced with Discrete Production) but both t-codes work with material and plant as selection criteria.

I created a Query to extract MSEG and performed in background mode with some selection criteria like you said. Then there was a  bit of rework but it solved the problem.

We haven't developed a Z report because it would be used only once.

Is possible create a report like this using flexible analysis?

Regards,

Marcos

[former_member211676]

Hi Marcos

If you wants see the produced materials against storage location and movement type the execute Tcode COOIS in list select the documented goods movement. Then execute by inputs required plants and dates. In the information you can filter by movement type and storage location wise.

Regards

Kesava

[Former Member]

Dear friends,

Thanks for replies.

I will try to use COOIS again and evaluate the notes with MM team.

These informations were excellent.

Regards,

Marcos

[former_member209265]

Dear Marcos,

Easy way is to generate a Z report.

You can implement below notes.

To implement the below notes in sequence to optimize MB51 transaction execution.

1.    1516684--MKPF fields added to MSEG – Performance Optimization

2.    1550000 --- Redesign of selection for performance optimization     

3.    1558298 MB5B: Redesign of selection for performance optimization

4.     Note 1481757 - MB5B: Access to archived MM documents

5      Verify data conversion according to note 1516684

6.     1567602--DB dependent steps to support the redesign of MB51

We have implemented this in our client system and the advantages are;

1.    MB51 processing time would be reduced further.

2.    Easy to retrieve the data quickly.

3.    Run time errors are prevented for large volume data execution.

4.    If the material documents for the restricted period under review have already been archived,   transaction MB5B returns incorrect results before implementation of Note1481757.

Try this. It will work.

Success.

Regards,

Krish.

[Former Member]

Dear Marcos,

If run time error occurs, you can try by executing the report in background.

In MB51 enter the input details and goto Program --> Execute in Background (F9).

Regards,

[Former Member]

Hi,

Thanks for replies.

I would like a standard report from Logistic Information System (LIS).

Is there any that display GR from production by storage location?

Regards,

Marcos

[Former Member]

Hi Marcos,

Why don't you use COOIS report. Its Order Headers Report will show the produced quantity report along with Storage Location.

Regards,

[Former Member]

Hi Vinodh,

Thanks for your reply.

I can't use COOIS because we use Repetitive Manufacturing and many GR are made without planned order.

Regards,

Marcos

[arivazhagan_sivasamy]

Hi Marcos Favoni,

Ask your technical team to create a new report with the copy of MB51 and ask them to display the details report directly instead of going header and then detail.

Then you can execute the report in background.

Arivazhagan S

[former_member184701]

runtime errors come due to the size of MSEG - usually it is huge

if you need such report on regular basis talk to abaper, custom one may play the trick...