cancel
Showing results for 
Search instead for 
Did you mean: 

ME59N batch jobs skipping PRs

0 Kudos

Hello All,

We have created and schedule a background job in SM36 for program RM06BB30 (ME59N) with a variant of ME59N that selects the requisitions you wish to convert to orders with DAILY run options.

User can see Jobs in FINISHED status in SM37 but skipping few PRs though the PRs matching the very same Variant. User is inconvenienced by this as slowing down the procurement process for the requisitioners ...

As an work around , user then runs the same Variant + missing PRs in foreground thus converting it into POs ....

What could go wrong with SM37 jobs ?

a) I tested & realised PRs being edited spanning the JOB run duration skipping SENSIBLY --- Perfectly fine

b) What else could amount to this few PRs skipping with SM37 jobs showing FINISHED green.

Lights in that directions will be rewarded.

Regards

MM

Accepted Solutions (0)

Answers (1)

Answers (1)

JL23
Active Contributor
0 Kudos

flag the box for detailed log in the middle of selection screen, then this log should be able to help you.

There exists a SAP note 786303, which has analysis reports tat help you as well to see why a requisition was not converted to a PO

0 Kudos

Hello Jurgen,

I'm still investigating this issue as constrained by the magnitude / volume of Test data to be replicated to test it in Test environment...

My client's procurement process is as follows

a) There is a centrally agreed Contract

b) User raises PRs manually and ME51N traces if any item referencing the Contract items & adds contract# in the PR line#.

c) Daily batch jobs Run ME59N to convert PRs into POs (PO grouping criteria Per CCod, Per Plant, Per Contract)

Ideally Contracts would have been converted directly into Release Orders / Call-Offs as opposed to the process above ...Don't you think step b) is quite unusual...??

As an work around user then runs ME59N manually punching those PR items on emergency & it converts to PO strangely..

Please shed lights on this issue of ME59N daily batch jobs skipping some PR items despite they match the variant parameters.

Hope words are self-explanatory & comprehensive..

Rgds

MM

JL23
Active Contributor
0 Kudos

if b is unusual or not depends on the material. if the PR is created for stock material, then I think yes it is unusual, as requisitions should be created with a MRP run instead.

if it is for text items (no material number) then it is the usual way.

Have a look into OSS Note 1433446 - ME59N - Omit faulty items work incorrectly with error 06 076

The described problem could cause your skips too.

0 Kudos

Hello Jurgen,

Thanks for the help.

Note 1433446 is to "Select the field if faulty purchase requisition items are to be omitted" and apparently doesn't suit to my problems simply because I don't want to skip any faulty items during ME59N conversion and we have'nt checked that field.

The process adhered here is fine as the auto source determination taking place & all the PR line items bearing the fixed vendor from Contract.

Rgds

MM