LOCL printer defined in material document printout

[Former Member]

All

I have a problem with wrong printer being defined in printout of Material document:

1) We have done setup for material document printout condition in transaction MN21

2) The printer PRINT has been defined in OMJ4 for the condition type/plant/sloc/user group combo

3) The user profile has been updated with parameter ND9=GROUP1 (user group for printing)

But: when the material document gets printed, it is directed to printer LOCL instead of PRINT as specified in transaction OMJ4.

Does anyone know the reason why this might occur?

Thanks in advance,

Lars Tornblom

[Former Member · Accepted solution]

Hi

Use the following note to check if the printer determination is configured properly, Checklist 2:

Note 426554 - Output determination checklist for goods movements

/Manoj

[Former Member · Accepted solution]

Hi

I have gone through the whole list provided in note 426554, but the problem still persists: no matter what printer output determination I set up in OMJ4, it always directs the printout to logical destination LOCL...any ideas, anyone?

//Lars

[Former Member · Accepted solution]

Hi

I think the user profile might have assigned to group , which is assigned to default LOCL printer. Check the NDR parameter.

[Former Member · Accepted solution]

Hi Lars,

What is the Print Parameter set in the tab Print in the output condition type in transaction M706?

Also, check for the different possible parameters in the following documentation:

http://help.sap.com/saphelp_45b/helpdata/en/34/60b2b8ae724effe10000009b38f91f/content.htm

/Manoj

[Former Member · Accepted solution]

Hi

The NDR parameter is set to "X", which means that at the time of MIGO, the print indicator is set by default.

The ND9 indicator is set with group INL2, which is pointing to printer PRINT.

[Former Member · Accepted solution]

Hi,

The print parameter in M076 is set to: Plant/Storage location/User group

Thanks,

Lars

[JL23 · Accepted solution]

What key combinations do you have for your message type in MN22?

if you have several, then check if you have conditions for the others.

And think if they could potentially being pulled prior to your combination.

and if this is case, then check those conditions in detail if you find there the wrong printer.

[Former Member · Accepted solution]

Hi Jurgen,

I have a couple of combos in MN22, but the printer is not defined in the MN22  - but instead in OMJ4.

Brgds,
Lars

[JL23 · Accepted solution]

I understood that you wanted printer is assigned in OMJ4, but you dont get it.

LOCL is not pulled just by chance, there is a certain logic of printer determination

Hence I assume this LOCL printer is somewhere entered in any other condtion, which is found first because it matches the search criteria as well.

so you should look for a condition that has LOCL as printer.

you could then change this LOCL to any other printer name temporarily, just to test if this is the condition that effected your case.

And if you found this condition, then we can think what has to be changed in printer determination.

you could already have answered the Q:

What key combinations do you have for your message type in MN22?

[Former Member · Accepted solution]

Jurgen

Got it now, thanks!

Looks like we need to leave the printer field blank in the conditions in MN22 in order for the OMJ3/OMJ4/OMJR config to kick in. At least it worked.

Thanks,

Lars Tornblom